Confused - General Questions and Answers

Confused - General Questions and Answers

I have been reading more articles about getting root access on an Android device and am finding the information to be contradictary. It might be the way I am reading it but when it says
"How To Install TWRP Custom Recovery On Any Android Phone (Without Root)"
I assume it actually means any Android, but it requires a custom recovery image for a particular phone so therefore it can only be for an android device where a custom image is available.
When I was running android 5.1 I installed TWRP so as to backup and restore my phone in case things went wrong, now I am running Android 7 it seems I cannot get a version of TWRP.
Can anyone assist as to what recovery tools I could install on a Ruggex 2 phone running android 7 please
thanks Roy

recovery is "independent" from main android OS. if you already have custom recovery installed on your device, it will even work without any OS installed, so it doesn't care if your phone is running Lollipop or Nougat. you can however check download source for newer version

If that is the case then why does the forum state
How to install TWRP on any Android device
but then goes on to say
Downloading TWRP for your device
which implies it is device dependant and not generic?
thanks Roy

Thx, I got it first time. of course custom recovery is device dependant. but that's not what I said. I said recovery mode is independent from android version. (at least till < 11)
btw it's not contradictory to say the Installation is generic for "any" android device (despites the difference device has recovery in partition or in ramdisk) while the Download is device dependant.
also take note that installing custom recovery and rooting android are two different tasks that do not depend on each other.

I think I am just getting more confused the deeper I go, it was fairly easy on my Android 5.1 device but with Android 7 it just seems to fight at every corner. I just cannot install and access TWRP on my device which is important for so many task.

what exactly is the problem?

I am trying to get root access on my Ruggex Rhino device, I had it all working when it was running Android 5.1 but the OS had to be upgraded to Android 6 or above for the new program to work, it is now on Android 7 .
I tryed the original method using King root but that fails to root and having read these forums it appears the way forward is to use Magisk rather than super user but that is another issue. This device on Android 7 does not have any recovery mode, power button and volume up just states no command and not sure if this is anything to do with my problems.
My ideal end goal would be a device running just the one navigation program and all the rest gone including phone module but have been told that is not possible so have to live with the bloated.
Roy

So you are the one who is confusing different things.
King root is so called one-click rooting app that tries to find exploit in its online database and provides root. This method is outdated, you can read more about here
https://android.stackexchange.com/questions/205706
the only one-click rooting app still working I am aware of is mtk-easy-su based on mtk-su exploit and magisk.
the "no command" screen is part of your stock recovery. this indicates your custom recovery has been replaced by stock recovery. read about "no command" screen here
https://android.stackexchange.com/questions/155705
installing custom recovery on android devices will break boot chain of trust. device will boot-loop and deny booting. therefore android will restore stock recovery on each boot, unless you disabled that feature.
read about dm-verity and stock recovery failsafe here
https://android.stackexchange.com/questions/214902
systemless-root is the root method available with SuperSU or Magisk, where system partition no longer is modified (to keep it healthy for updates). instead, the boot partition is modified, that requires bootloader to be unlocked (most devices).
bootloader unlocking will factory reset your device. some older devices allow installing custom recovery on locked bootloader, but you need to find a way to flash it.

Thats good information, move on away from Kingroot due to obsolescence and look into systemless root which from what I have gathered so far is not detected by the system. I will initially look into SuperSu as that was running on Android 5.1, I remember it used to ask for permision to access root and so far Magisk has just taken me round in circles. But first I will look at those articles and see what I can learn.
thanks Roy

actually, rooting with SuperSU is done by flashing SuperSU zip from TWRP. I couldn't find TWRP for your device, but we can help you porting generic TWRP for your device.
rooting with Magisk is done without TWRP
- unlock bootloader (+ factory reset)
- install Magisk apk
- patch boot.img with Magisk app
- flash patched boot.img
(see Installation Instructions)

Related

[Q] Is it impossible to Root and put a custom rom on this device?

I can't find a guide for dummies for it, nor any compatible automatized program or a rom created for it...

Pizzadelivefr said:
I can't find a guide for dummies for it, nor any compatible automatized program or a rom created for it...
Click to expand...
Click to collapse
Been away for a while now so can't vouch if there is a custom ROM available at this moment for your specific K2 variant. However, rooting is very possible. Simply unlocking your bootloader and booting up TWRP recovery is enough to do the job since TWRP will root the device for you. TWRP will or should detect if the device is rooted or not. If it is not then when you select to reboot your system it should ask if you would like to install SuperSU or in lamen terms, to root your device. Obviously you will say yes at this point. When the device reboots then go to the play store to update SuperSU. Once it is updated open the SuperSU app so it can update the su binary. It will ask to update the su binary either normally (by writing to your system with write permissions) or via twrp\cwm. To select the normal option you must either be S-Off or have a custom kernel specific to your K2 variant which has write protection removed. Otherwise, you must select the twrp\cwm method where it will reboot back to the custom recovery and make the change from there. Once the su binary is successfully updated then you are now properly rooted. Do not EVER flash a custom ROM unless the ROM Developer states that it is compatible for your device.

How do I safely root and unlock bootloader on Marshmallow?

My device is European L04, currently running North Africa release (the earliest Marshmallow build uploaded) - L04_2016_0316_0900 (B820)
I'd like to unlock the bootloader and root my Honor 6. I've never done it (on this particular device), because I've read enough here to know it's slightly more risky than on other devices, especially when you plan to update the stock rom soon, so I preferred to wait until I have the last important update the device is likely to receive - Android 6.0.
What I want to know (some of the answers are in the topics which I listed below):
MultiTool - I've seen reports of bricks when using MultiTool with EMUI4/Marshmallow - why does it happen? My understanding is that MultiTool is a bundle of adb/fastboot and some recovery images for older Android versions, so my theory is that instead of using MultiTool, I should simply get the proper recovery for Marshmallow and flash it manually with fastboot, right?
unlocking bootloader, rooting, flashing recovery - I think I understand the process; in a nutshell: 'fastboot oem unlock X', 'fastboot flash recovery imagename.img', then flash the proper SU.zip in recovery. Where do I find the code, the Marshmallow recovery image, the SU.zip file?
will recovery backup in TWRP work without any problems?
what is the procedure to go back to stock completely after rooting? Unroot, (then wipe if it's needed?) so I am able to safely flash stock firmware again (since, from what I know, flashing stock on a rooted phone makes itself brick permanently, right? or is it just a soft-brick and it can be fixed?)
is there anything else I should know before proceeding?
What I found so far:
http://forum.xda-developers.com/showpost.php?p=66615082&postcount=502 - two recovery images, TWRP and another one (stock?) for the Marshmallow release
http://forum.xda-developers.com/honor-6/general/honor6-multi-tool-t2963060/page50 some rooting instructions for the L02 beta, see posts 494 and 498; no idea whether this is applicable to final Marshmallow or L04 at all
http://forum.xda-developers.com/honor-6/general/huawei-honor-6-plus-unlock-bootloader-id-t3357259 an app to get the unlock code, seems a bit shady to me though on the first glance
http://forum.xda-developers.com/honor-6/development/honor-6-rooting-method-t2962795 alternate methods for bootloader (through a website or by email), in case the app won't work; also, detailed instructions on unlocking and rooting
Basically, I need to know whether my procedure is more or less right before I proceed. I think the information is quite hard to find and the risks are quite high, so I'd like to make a promise - when I'm done rooting it and I know the correct process, I'm going to make a "Update to Marshmallow, unlock, root" how-to thread for all the people that will need it in the future.

Another two questions...
1. Where do I get proper SuperSU for Marshmallow? I get a boot loop (yeah, I know I have to wait and I did, but it's a pretty obvious bootloop from watching the logcat content, and nothing new happens...) after flashing http://download.chainfire.eu/supersu-stable (2.65).
2. I have unlocked my bootloader and installed TWRP, so recovery and fastboot are functional. I didn't make a backup before flashing the zip and now I'm in a bootloop. How do I restore working Marshmallow? I assume I can either beg somebody to upload a TWRP backup for my H60-L04, or somehow flash the stock over what I have now. Can I simply use manual update from SD? Can I somehow flash Marshmallow again with fastboot? I'm too scared of bricking my device right now so I guess I'll brace myself for a few days without a phone until somebody helps me :/

I just flashed the Marshmallow release I had before the bootloop (I used Huawei Update Extractor and flashed boot, cust, system and recovery with fastboot; then open up Huawei recovery and factory reset for good measure, I'm not sure it was even needed) and the device is working. I'll restore my stuff, install TWRP, make a backup then try out your ZIP. Thanks
edit: thanks again - your zip works indeed. So after the initial hurdles, now I've got working root and a reasonable way of restoring in case I screw something up along the way.

Before making a new topic with the tutorial I have a few more questions.
First of all, why exactly we weren't supposed to update the rooted devices? I'm not currently interested in OTAs (it's pretty obvious that it needs a functional Huawei recovery, and you need to unroot cause an update can make a mess in a rooted system, making it bootloop for example), but can we flash extracted images with fastboot on rooted devices? Logically, we should be able to... How about sdcard update method?
Can we flash Marshmallow on Kitkat? (fastboot, sdcard, local update methods?) Or do we need to update to Lollipop along the way?
Can I flash stock roms in general (evenbetween different Android versions) by using fastboot with {boot, cust, recovery, system} images only? There's a lot of images that you can extract with Huawei Update Extractor - why there's so many if they're not needed?

Stuck on Main Menu MI-Recovery 3.0

So, i just unlocked my phone and then i wanted to root, so i followed these steps of this website https://www.getdroidtips.com/root-xiaomi-mi-mix-3-magisk/ After flashing that file i tried to reboot into my system, but i always get to that Menu.

Chances are that image is not compatible with the software on your phone. I would recommend downloading whatever version of software was on your phone and running fastboot flash boot boot.img using the file from the version of software you had on your phone. This stuff is not a jigsaw where all the pieces just fit and work together no matter where you got them from.
If you want to root your phone, I recommend reading the forums here and finding the guides on how to install TWRP, and install Magisk. You may need additional files after rooting with Magisk if you have a Chinese phone and global software installed.

[GUIDE] Unlock/Root Lenovo Smart Tab P10 (TB-X705F) by Chaser42

This guide will show you how to unlock the bootloader and root Android 9.0 (Pie) with Magisk on the Lenovo Smart Tab P10 (TB-X705F).
This guide is written for Lenovo Smart Tab P10 (TB-X705F). However, it can also be used for the Smart Tab P10 LTE (TB-X705L), the M10 (TB-X605F), and the M10 LTE. All of these devices are essentially identical plus or minus a couple bells and whistles. The only real important technical difference is that each Smart Tab model uses its own specific stock ROM. Keeping up with each stock ROM can be quite a chore, so I will only provide information and links specific to the P10 (TB-705F) stock ROM in this guide.
All software links including stock ROM files, TWRP, Magisk, etc. can be found at the bottom of this post.
@abramxx has a thread for the TB-X605L: HERE
NOTE THAT THIS GUIDE IS ONLY APPLICABLE IF YOUR DEVICE IS RUNNING ANDROID 9.0 (PIE). If your device shipped with Android 8.0 (Oreo), you must upgrade because the Oreo bootloader does not allow a permanent unlock.
You can determine what version the stock ROM you are running by opening Android Settings -> About Tablet. So far Lenovo has released 9 versions the P10 stock ROM:
TB-X705F_S000017_20180831_ROW (8.0 - Oreo)
TB-X705F_S000037_20181220_ROW (8.0 - Oreo)
TB-X705F_S200095_190528_ROW (9.0 - Pie)
TB-X705F_S210068_190904_ROW (9.0 - Pie)
TB-X705F_S210120_191029_ROW (9.0 - Pie)
TB-X705F_S210135_191212_ROW (9.0 - Pie)
TB-X705F_S210137_200407_ROW (9.0 - Pie)
TB-X705F_S210154_200910_ROW (9.0 - Pie)
TB-X705F_S210164_201119_ROW (9.0 - Pie)
TB-X705F_S210214_220725_ROW (9.0 - Pie) <current version>
If your device has not yet been unlocked and you are not running the current version, I highly recommend that you upgrade by using the Lenovo Moto Smart Assistant (LMSA) tool to perform a "rescue". The LMSA tool will download the full TB-X705F_S210120_191029_ROW stock ROM and flash it to the tablet. This will result in the loss of all data on the tablet. That's fine because unlocking the device will again clear all data (with the exception of the brand new stock ROM that you have just installed).
NOTE: If you can't make the rescue operation work using the LMSA tool, don't feel bad. Half the time I can't get it working either. As an alternative you can eliminate the LMSA tool all together by using the QComDLoader tool directly. You can find a link to the tool with instructions at the bottom of this post.
PREREQUISITES:
The understanding that by making these modifications, specifically unlocking the bootloader, will likely void the warranty of your device.
Be aware that when you modify your device you do so at your own risk. Be sure to follow all steps carefully or you could end up losing all of your data or bricking your device. IF YOU ARE UNSURE ABOUT WHAT YOU'RE DOING THEN STOP NOW.
As stated above, your device needs to be running Android 9.0 - Pie.
You need to make sure you have developer settings turned on so that you can enable the "OEM unlocking" setting and the "USB debugging" setting. There are many guides available on how to turn on developer settings, so that is beyond the scope of this guide.
The fastboot tool must be installed on the device that will be connected to the tablet via a USB cable. Your USB device drivers need to be up to date on that device. In most cases that will be a Windows 10 PC, but the fastboot tool can also be used from devices running Linux or Android. There are a lot of resources already available on how to install the fastboot tool and USB drivers, so that is beyond the scope of this guide.
You should have a basic familiarity with the fastboot tool and the flashing of image files via the command line.
BACK UP ALL OF YOUR DATA THAT YOU WANT TO KEEP ON THE TABLET. WHEN YOU UNLOCK THE BOOTLOADER, EVERYTHING ON THE TABLET WILL BE WIPED. THAT INCLUDES THE INTERNAL SD CARD AS WELL AS ANDROID AND APP SPECIFIC DATA. ALL THAT WILL REMAIN IS STOCK ANDROID PIE THAT HAS BEEN FACTORY RESET.
HOW TO UNLOCK:
Turn the tablet off.
Hold down the volume down button along with the power button so that the tablet goes into fastboot mode.
Using the USB cable, connect the tablet to the device with the fastboot tool installed.
Launch the command line or terminal emulator from the device with the fastboot tool installed.
Unlock the bootloader with the command:
Code:
fastboot oem unlock-go
This will begin the system wipe process and will take around 5 minutes to complete. Once it is complete, the tablet will boot up into Android starting at initial configuration wizard.
HOW TO ROOT:
Power the device off. Don't bother with the initial configuration wizard.
Hold down the volume down button along with the power button so that the tablet goes into fastboot mode.
From the command line, navigate to the directory containing the Magisk prepatched bootloader image (magisk_patched.img) that you downloaded in the prerequisites.
Flash the Magisk prepatched bootloader image with the command:
Code:
fastboot flash boot magisk_patched_boot-TB-X705F_SXXXXXX_XXXXXX_ROW.img
Boot normally into Android with the command:
Code:
fastboot reboot
Go through the Android setup wizard making sure that you at least configure your Wi-Fi connection.
Once you're done with the Android setup wizard, find Magisk Manager in the app drawer and open that app. Download and install the latest release of Magisk Manager from GitHub: LINK
You will be prompted to download and install the latest full version of the Magisk Manager. You will also need to grant permission allowing the APK file you just downloaded to be installed.
Once the newest version of Magisk Manager has been installed, open that app.
Magisk Manager will state that it needs to complete the Magisk setup. Begin that process. It will take a minute or two to complete and then will automatically reboot the tablet.
Congratulations. Your Lenovo Smart Tab P10 (TB-X705F) should now be fully rooted with Magisk. As a final task, it would probably be a good idea to install your favorite version of BusyBox. I highly recommend that you use the systemless version that can be downloaded and installed directly from Magisk Manager.
HOW TO INSTALL OTA UPDATES
If you are rooted with a bootloader that is patched with Magisk, then you will not be able to install OTA updates. The OTA update will look for the original unpatched bootloader image for the current build. If it is not installed then the update will simply fail.
INSTRUCTIONS:
Check to make sure which version of the stock ROM you are currently running.
TB-X705F_S000017_20180831_ROW (8.0 - Oreo)
TB-X705F_S000037_20181220_ROW (8.0 - Oreo)
TB-X705F_S200095_190528_ROW (9.0 - Pie)
TB-X705F_S210068_190904_ROW (9.0 - Pie)
TB-X705F_S210120_191029_ROW (9.0 - Pie)
TB-X705F_S210135_191212_ROW (9.0 - Pie)
TB-X705F_S210137_200407_ROW (9.0 - Pie)
TB-X705F_S210154_200910_ROW (9.0 - Pie) <current version>
Download the original bootloader image for the version of the stock ROM your are currently on.
Flash that bootloader image to the device.
Install the OTA update. You can use the automatic update app inside of Android. You can also install the update manually. Download the OTA update file you need from the software links at the end of this post. Copy that file to your external SD card. Boot the tablet up into recovery (hold power, volume up, and volume down). Choose to apply update from SD card.
Download the Magisk patched bootloader image for the version of the stock ROM your are upgrading to.
Flash that bootloader image to the device. Reboot to system and you're all done.
* NOTE: Installing an OTA update on a device running TWRP with a DECRYPTED data partition, you must follow a few extra steps. @clsA has documented that process HERE.
STOCK ROM FILES
TB-X705F_S000017_20180831_ROW:
Full Stock ROM
Original Bootloader Image
Magisk Patched Bootloader Image
TB-X705F_S000037_20181220_ROW:
OTA Update From Previous Version
Original Bootloader Image
Magisk Patched Bootloader Image
TB-X705F_S200095_190528_ROW:
OTA Update From Previous Version
Original Bootloader Image
Magisk Patched Bootloader Image
TB-X705F_S210068_190904_ROW:
OTA Update From Previous Version
Original Bootloader Image
Magisk Patched Bootloader Image
TB-X705F_S210120_191029_ROW:
Full Stock ROM
OTA Update From Previous Version
Original Bootloader Image
Magisk Patched Bootloader Image
TB-X705F_S210135_191212_ROW:
Full Stock ROM
OTA Update From Previous Version
Original Bootloader Image
Magisk Patched Bootloader Image
TB-X705F_S210137_200407_ROW:
OTA Update From Previous Version
Original Bootloader Image
Magisk Patched Bootloader Image
TB-X705F_S210154_200910_ROW:
OTA Update From Previous Version
Original Bootloader Image
Magisk Patched Bootloader Image
TB-X705F_S210164_201119_ROW:
OTA Update From Previous Version
Original Bootloader Image
Magisk Patched Bootloader Image
TB-X705F_S210214_220725_ROW: <=== LATEST VERSION
Full Stock ROM
Original Bootloader Image
Magisk Patched Bootloader Image
MISC HELPFUL LINKS
Latest Magisk Releases: LINK
Latest TWRP Custom Recovery the P10: LINK *** Many Thanks to @clsA and @drmarble ***
QComDLoader Tool v1.06 with Settings Preconfigured: LINK
SEE ATTACHED QUICK REFERENCE IMAGE FOR THE QCOMDLOADER TOOL.
QComDLoader Tool Info: You can use this tool to perform a rescue without the LMSA tool. I zipped up the tool so that it is pre-configured with the proper settings. It should work with the P10 and the M10. All you have to do is tell the tool where you have unzipped the full stock ROM to. Then in order to actually perform the flash operation, tell QComDLoader tool to start listening for connections. With the tablet powered off, press volume down and simply plug in the USB cable. Keep volume down pressed for about five or six seconds until you see the red LED blink a couple times. Then just let it sit there. It will appear to be doing nothing for a couple minutes. And then all of a sudden the tool will show that it is connected and will start the flash process.

Thank you! But magisk_patched.img can't download

Delete

fidelis2 said:
The download link works fine for me.
Click to expand...
Click to collapse
Thanks,good

Thank you very much! root succeeded

FYI - If you need Xposed Framework functionality, the new EdXposed seems to work fine.
I simply followed the instructions to get it working:
EdXposed Framework version 90.0-v0.4.5.1 _beta (4463) (Sand Hook) is active
There are two versions that you can pick from - Sand Hook and YAHFA. The documentation states that they're both nearly equivalent and to pick one arbitrarily because some variants work better with different Android devices. So I picked Sand Hook and so far so good. I took a screenshot of the EdXposed Manager showing that is happy. That image is attached.
The EdXposed Framework is still in beta so be very cautious with it. Especially considering that there is currently no P10 TWRP image for Nandroid backups. At this time I wouldn't recommend installing it unless you really have a great need for it.
Chaser

Help!
Hello!
I have another build number TB-X705L_S200084_190614ROW. What should I do to root my device?
Thanks in advance,
Irene

Ah, yes. That's the LTE version of the P10. Since it has a different build number, we need the stock bootloader image file (boot.img) that is specific to that model number. That image file would then need to be pre patched with Magisk. I used the magisk installation guide as a reference. That's actually quite easy. The hard part is getting that stock bootloader image file. I was finally able to accomplish this for the TB-X705F by using the Lenovo Moto Smart Assistant tool to revert the tablet back to the original stock ROM and to apply the two OTA updates. The LMSA tool actually saved the files inside if it's application directory in Windows. Inside of the last update zip file I was able to find the stock Pie bootloader. I can only assume that we would have to go to through the same process using the TB-X705L. I'm not sure if I will be able to do it because the LMSA tool requires that you attach the tablet via the USB cable. Then it verifies the serial number and model number. I suspect that I would actually need one of the TB-X705L tablets to get the LMSA tool to download the ROM files specific that device. I will try that a little bit later when I get in front of a PC.
And now that I think about it, there's no guarantee that the TB-X705L bootloader for Pie will allow an OEM unlock. For all we know, allowing the OEM unlock for the TB-X705F bootloader was an oversight on the part of the Lenovo developers. After all, it seems pretty evident that Lenovo doesn't want this device to be unlocked. The Oreo bootloader was not unlockable as far as I could tell. I thought it was strange that the Pie bootloader magically allowed OEM unlock. If the change was intentional, Lenovo certainly didn't provide any documentation about it. They also don't allow those original stock ROM files to be downloaded from the support section of their website. Many other vendors make those files freely available on their websites. I shouldn't have to hunt down those files. They do provide the source code for the original stock ROM, but that's not very useful to the user community.
Hopefully Lenovo just hasn't had time to publish documentation for the bootloader unlock. Otherwise, it would seem that they are intentionally trying to make it difficult for power users to unlock and root these tablets.
Chaser

I should have mentioned in my original post that the Lenovo Moto Smart Assistant Tool is the key to restoring your device in the event that you get a boot loop or if something else wonky happens. That tool is available on the Lenovo website in their support section. Just follow the instructions to do a "rescue" and that tool will revert the tablet back to the first Oreo stock ROM. To get back to Pie you just have to go through the process of installing the two OTA updates. I did a lot of crazy stuff to my test P10 which resulted in boot loops and other problems with Android. Each time I was able to revert the tablet back to its original Oreo state using the LMSA tool.
Chaser

Delete

Can you provide boot.img and Recovery.img files? X705F.
Thanks!

Here are the Lenovo stock ROM files for the Smart Tab P10 (TB-X705F). These are the genuine files directly from the Lenovo. I have left the huge file names intact.
Original Full Stock ROM: TB_X705F_USER_S000017_20180831_Q00020_ROW.zip
OTA Update #1: TB_X705F_USER_S000017_20180831_Q00020_ROW_TO_TB_X705F_USER_S000037_20181220_Q00020_ROW_WCF52C9502.zip
OTA Update #2: TB_X705F_USER_S000037_20181220_Q00020_ROW_TO_TB_X705F_USR_S200095_190528_Q00332_ROW_WCB7188D82.zip
There is also a Qualcomm tool that LMSA uses behind the scenes. I've included it as it may be helpful for some people.
Qualcomm Tool: QcomDLoader_V1.3.0.2_WithDLL.zip
Enjoy!
Chaser

a quick question how were you able to upgrade to Android 9, I just bought mine tablet and android version in 8. I tried to check fro updates but it tells me the system is up to date. I also tried to upgrade my tablet via mobile assistant, but when i choose and model. and download the ROM and try to update it that way it tells me its also up to date...

I have a test P10 and I have taken it from the original Oreo stock ROM to Pie several times. Sometime last week I started experiencing the exact same issue. I had that device up to the first OTA update and was ready to install the second OTA update but it acted as if it was fully up-to-date. I got the same result when trying to update via the Android updater or the LMSA tool. It is almost as if Lenovo has rescinded the update.
So I found a workaround.
This actually works with both OTA updates. Copy the OTA update file to your external SD card. It must be the external SD card. Then boot into stock recovery by pressing volume up and power at the exact same time. After it vibrates and the Lenovo screen comes up keep volume up and power pressed for about three more seconds and let go. This should bring up the stock recovery menu. Choose install from SD card. You will see your update zip file. Select that file and the update should install properly.
I have tested this method a couple times now and it definitely works. Let me know if you have any trouble.
Chaser

Chaser42 said:
I have a test P10 and I have taken it from the original Oreo stock ROM to Pie several times. Sometime last week I started experiencing the exact same issue. I had that device up to the first OTA update and was ready to install the second OTA update but it acted as if it was fully up-to-date. I got the same result when trying to update via the Android updater or the LMSA tool. It is almost as if Lenovo has rescinded the update.
So I found a workaround.
This actually works with both OTA updates. Copy the OTA update file to your external SD card. It must be the external SD card. Then boot into stock recovery by pressing volume up and power at the exact same time. After it vibrates and the Lenovo screen comes up keep volume up and power pressed for about three more seconds and let go. This should bring up the stock recovery menu. Choose install from SD card. You will see your update zip file. Select that file and the update should install properly.
I have tested this method a couple times now and it definitely works. Let me know if you have any trouble.
Chaser
Click to expand...
Click to collapse
oh the problem is i don't have an any SD card I can put into the tablet but also what OTA update are you referring too? are you talking about the link you posted in this thread Update 1 update 2? because my build number is newer then those. my build is TB-X705F_S000041_20190322_ROW and that correspond to Android 8

Unable to update to Android 9
I succesfully went back to the stock version, after that had 2 OTA updates... and now I can't update to Android 9 to get rom-file needed to root my device ( Both Smart assistant and OTA update are writing "your system is up to date"...

Currently I only know of one way to install the second OTA update. That is the update that will bring you up to Android 9. It requires that you use an external SD card (even if you just insert one temporarily for this purpose). Per standard Android documentation, you should be able to install the update using ADB sideload but that method is broken. I have only had success updating manually from the external SD card.
Here are the steps to manually install OTA update #2 (Android 9) via the external SD card:
Download the zip file for OTA #2 (I provided a link in a previous post)
Copy that zip file to the top folder of the external SD card.
Boot into stock recovery (power off device then press volume up and power simultaneously).
From the stock recovery menu, choose "Apply update from SD card".
Select the zip file for OTA #2
Profit
I don't know why the P10 currently thinks it is fully up-to-date at Oreo with OTA update #1. I know that it used to work and now it doesn't. I'm not a big conspiracy theorist, but it's almost like Lenovo rescinded the update. This happened a week after I posted the bootloader unlock instructions. Maybe they never meant for the bootloader to be unlocked and they are cooking up a replacement update. But I don't know why they would bother because we already have the copy of the bootloader that allows the unlock and they can never undo that.
I should just use Occam's Razor and go with the simplest solution... Lenovo doesn't seem to know their head from their ass when it comes to the software support of this tablet. Just look at the LMSA tool. It's practically useless. The only thing it gets right is the rescue feature that brings you to the original stock Oreo. Actually, the Qualcomm update tool should get the credit there as LMSA uses that to install the ROM in the background.
This is really great device device, especially considering the price. I have used a lot of tablets and I am very pleased with the P10. The people that designed the P10 from a hardware standpoint did a good job. Even the people who made the stock ROM for Oreo and Pie did a good job. However, the people in charge of the support software are freaking idiots.
Let me know if you run into any problems installing OTA update #2 (Android 9).
Chaser

Android 9
I've called to Lenovo support and they say that this update is expected to come till the end of September. I hope they don't want to fix the opportunity to unlock the bootloader...
P.S. Sorry for possible mistakes in writing, English is not my language

Wow, so Lenovo has confirmed that they recalled the update and are coming out with another update next month. I don't really know what to think about that. They will probably roll up the latest Android security updates with the new update. It doesn't make sense that they would recall an update unless they found something wrong with that update. But they still have to deal with the fact that OTA update #2 was released and is running on a lot of P10 tablets in the wild. The new update will have to have the ability to upgrade devices at OTA #2 and devices stuck at OTA #1. As it is, I'm never going to delete my copy of OTA #2. I will make it available on my Mega share if they take it down from the official Lenovo download links.
I'll have to double check, but per my understanding of how OEM locking and unlocking works, Lenovo should not be able to force an OEM lock with an OTA update. The whole point of the security mechanism is that it requires physical access to the device. You can't lock or unlock unless you are able to hold the device in your hand. As it stands, they released a copy of the bootloader into the wild that is capable of performing OEM unlock. Lenovo can't undo that. It will forever be available on fine sites like XDA in a thread like this.
Chaser

Very good thing
With thins unlock guide i got know a rooted devices thanks!

2023 EMMC_11 Exploit To Root And Flash Custom Boot And Recovery Images Allowing Custom Roms To Be Used

This process will allow flashing custom boot and recovery images on EMMC11 S5
Yes this will allow the EMMC11 S5 to run custom roms like Lineage
Than You ryanbgSummary Of What This Does
You must be on G900VVRU2DPD1 bootloader for the exploit too work.
The exploit patches the header of the boot or recovery image which forces the phone to skip security check of them and allow them to be used. If on totally stock phone this process flashes combo firmware to your phone which is kitkat based and allows easy rooting. Then I inject safestrap into combo firmware which gives a system based hijack that gives you a custom TWRP like recovery. I then have safestrap recovery flash a minimal QL1 based rom with DPD1 bootloader that updates you back to Marshmallow firmware and a prepatched TWRP recovery. I have to use this method because this prepatched TWRP recovery cannot be flashed in odin because you need unlocked bootloaders to be able too do this. This minimal firmware is also rooted just for good measure but the only thing you will be using this firmware for is to access TWRP so you can flash an actual rom that can be rooted with a magisk root. I have provides some for you to use. If you mess up and loose recovery and dont have a rooted rom you can boot up to. The whole process will have to be done again so take care not too loose your TWRP recovery once using this process.
What You Can Do
Flash custom boot images that allows you to use magisk
Flash custom recovery
Flash custom roms like Lineage
What You Cannot Do
You can not unlock bootloaders on EMMC_11 so all flashing must be done on a device with custom recovery
You cannot flash custom binaries using odin
Downloads
S5_Root_Tools_2023.7z -- Use If Totally Stock
EMMC_11_Rom.zip -- Stock QL1 6.0 Use If Already On Safestrap
Patch_Boot_Recovery_Image.zip
Boot Images Stock EMMC_11 Or 15
boot_ql1_stock.img
Boot Images Custom EMMC_11 Or 15
PhoeniX.Kernel.V13.0.TW6.0.1.img -- Phoenix Kernel Permissive
PhoeniX.Reborn.Kernel.V1.0.TW6.0.1.img -- Close To Stock Permissive
PhoeniX.Kernel.V1.0.TW6.0.1.G900V.img -- VZW Stock Permissive
TWRP Recovery EMMC 11
recovery_twrp_emmc_11.img -- Pre Patched For EMMC_11
TWRP Features
Backup and flash system images
Green color to distinguish between regular twrp
EMMC_11 TWRP image is prepatched flashing patch zip not needed
EMMC_11 TWRP startup screen labeled to identify its patched
Regualr TWRP can be use if you choose on either model
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Technical Questions And Answers Here
Telegram Channel
Directions If Already Running Safestrap
1. If already running safestrap flash EMMC_11_Rom.zip in safestrap this will install very minimal QL1 rom with proper bootloaders and stuff. From here you can flash rom of your choice just make sure you dont update or change bootloaders.
2. Then root with root of choice.
3. Then flash Patch_Boot_Recovery_Image.zip then your done
4. Then from there on in future flashes follow the EMMC_11 Flashing Custom Roms Boot Images And Recovery Images section
5. I recommend you dont mess with recovery. If you accidently flash an unpatched recovery you may not be able to get it back without starting the whole process over. If a rom you are using flashes a recovery image I recommend you remove it or make sure you flash the patch zip
Directions If Totally Stock
I would recommend Windows defender is turned of before starting
1. Download S5_Root_Tools_2023.7z and unzip
2. Make sure Usb debugging is enabled on your phone
3. Plug in phone and run Safestrap.exe and follow directions on command window
4. This process is pretty much 1 click all automatic except following command window prompts
5. This will detect if your phone is EMMC 11 or 15
6. If it detects EMMC 15 it will automatically unlock your bootloaders.
7. EMMC 11 detection will install Twrp recovery where you can install custom stuff from there.
EMMC_11 Flashing Custom Roms Boot Images And Recovery Images
1. The above tool will give you TWRP Recovery and stock 6.0 rom
2. Flash your rom of choice in TWRP or stay on stock one provide. Do not flash a rom that updates bootloaders.
3. Then flash your root zip like magisk this will patch your boot.img
4. Once a boot.img is no longer stock you will need to flash the Patch_Boot_Recovery_Image.zip after the image is patched with magisk. This zip will be placed on your internal storage from the above tool
5. I recommend you dont change recoveries there is really no need too
6. Anytime you flash a new boot.img it will most likely require you to reflash root zip and then make sure you flash the Patch_Boot_Image.zip very last
Source For Kernel
Source Code For Expolit
Source For TWRP

Instructions For Flashing An AOSP Based Rom
1. Download rom that will work for this device.
2. In twrp wipe data
3. Install rom zip
4. Install gapps that match the rom you are flashing and they must be arm gapps.
5. Install Root zip such as magisk zip
6. Install Patch_Boot_Recovery_Image.zip
7. Reboot
8. Anytime you flash a new boot.img it will most likely require you to reflash root zip and then make sure you flash the Patch_Boot_Image.zip very last
9. If using lineage recovery you will also need to flash the Patch_Boot_Image.zip after you flash lineage recovery
Official Lineage Builds For S5
LineageOS Downloads
download.lineageos.org
Open Gapps
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
Regular Magisk
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Magisk Delta
Releases · HuskyDG/magisk-files
Contribute to HuskyDG/magisk-files development by creating an account on GitHub.
github.com
ETFSU
EFTSU Root Solutions
The Largest Database for the Root Solutions on the Internet
eftsu.com
Safteynet Fix Module
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
Disabling Reactivation Lock
Thanks bbsc
1. Follow above directions too obtain safestrap and root
2. Download and flash EMMC_11_NCG_KK_Safestrap_Full.zip in safestrap then wipe data
This has Samsung Setup Wizard removed so you can get through setup
3. Set up a wireless connection or use your SIM-card and internet connection from your provider.
4. Navigate to Settings - Security, find Reactivation Lock and untick it. The phone will ask you for your existing credentials or to register a new Samsung account. Accept too update app then allow google check when it ask
5. Login to your new account and you will be able to untick Reactivation Lock.
6. When it unticked, Navigate to Settings - Backup Reset - Factory data Reset.
7. Phone will reboot too stock recovery and wipe data and remove current samsung account and you are good too go.
8. Now proceed with flashing of rom of choice or unlocking the bootloader if you have EMMC15 device. On this particular rom you have to enter safestrap from the safestrap splash screen on bootup its not installed as a recovery image because stock recovery is needed
Old Root Methods And Downloads
EMMC_11_S5_Root_Tools_2022_V7.7zInstructions To Install Safestrap
**If you already have safestrap installed you can skip to Installing Roms Post 2
**If you already have rooted you can skip to Installing Safestrap
**This process uses Kingroot too root but removes all traces of it when done.
Directions
1. Download and unzip EMMC_11_S5_Root_Tools_2022_V7.7z
2. Reboot phone too Download Mode by holding Power+VolDwn+HomeButton as phone starts up
3. Plug phone into computer and open the Odin provided in the above file in the Odin_Folder
4. In Odin Choose BL slot and choose the COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 Located in the Odin_Folder
5. Flash the file using provided Odin let phone reboot. This will wipe your phone
6. Once phone is rebooted make sure its plugged into computer and phone use recognized by computer
7. Run the Install_One_Click.cmd this should install install safestrap. If this method fails countinue with below methods.
8. If above method fails you can reboot and try again or run the Manual_Install_Root_Apps.cmd and try below methods to root
Towel Root Method
These steps are only needed if above root method failed
1. You need too be connected to a network. Try one of towel root apps and if not successful then try the other one. If it doesn't work go to King root section
2. If towel root succeeds then run the click on the super su app and choose to update su binary and choose normal once successfully updated reboot phone
King Root Method
These steps are only needed if towel root failed
1. You will need to be connected to a network. Click on King root app then click try root
2. Once root is successful don't click on the optimize and close the king root app.
3, Run the Manual_Install_SuperSu.cmd
Installing Safestrap
9. This only needs to be done if 1ckick root bat method failed. Now click on safestrap app and clisk install safestrap click allow in root dialog app once installed click reboot to safestrap
10. Busybox will need to be installed first if you used towel root method to root
Old Safestrap Rom Zips
EMMC_11_NK2_KK_Rooted_Safestrap_Full_V2.zip KIT KAT ROM
EMMC_11_PB1_LL_Rooted_Safestrap_Full_V2.zip LOLLIPOP ROM
EMMC_11_QL1_MM_NonRooted_Safestrap_Full_V2.zip MARSHMALLOW ROM
Entering Safestrap
To Enter Roms From Kit Kat Or Rooted Combo Firmware
1. Reboot phone and click on Recovery Button on safestrap splash screen
To Enter Safestrap On Marshmallow Or Lollipop Roms
2. Reboot to recovery (VolUp+Pwr+Home Buttons) when the bottom navigation lights turn on hold the volume down and power buttons for about 10 seconds until phone boots too Maintenance Boot Mode
Click image for larger version
3. Now use the volume keys to navigate too Factory Reset. Now press the Home button. This will not reset your phone but this is how you enter safestrap. Phone will reboot too safestrap give it about a minute too boot into safestrap it will boot directly too safestrap. Every time you want to enter safestrap you need to follow these steps
4. To leave safestrap simply click reboot system
Installing Roms Using Safestrap
1. If coming from a kitkat rom or the root method above in post 1. You must reboot too stock recovery wipe data and reboot and enter safestrap then Copy Rom Zip To Phone. The data wipe in recovery while on kitkat rom is necessary to partition data correctly too move on too Marshmallow or Lollipop. If on Lollipop or Marshmallow rom skip wiping data in stock recovery because you cannot and copy your rom zip too phone while system is still booted and reboot too safestrap.
2 In safestrap click swipe bar too allow system too be modified
3. Click wipe and swipe to factory reset then click home button then click install and choose EMMC_11_ROM.zip.
4 This will take several minutes too install
5. Once installed click reboot system. If first time in safestrap it will ask you if you want too install TWRP which you cannot. Uncheck the boxes to install twrp and choose Do Not Install and phone will reboot. This is only on first time you enter safestrap after first time it wont ask you this again and simply click reboot system
6. Phone will take several minutes too boot
Features
Stock Deodexed Rom Slightly Debloated
Some Features Added
Safestrap Available On All Roms Root And NonRooted With Ability To Enter Safetrap Without A Computer
Root On Lollipop And KitKat Only
Bugs
1. Lollipop and Marshmallow recovery image is replaced with KitKat boot.img to give ability too boot too safetrap without using a computer. This may cause your sometime to reboot to recovery screen and get stuck when your phone is turned off and you plug in a charger. You can fix by pulling battery with phone unplugged then plug back in if not cycle through a startup then power off
2. There is no recovery image on Lollipop or Marshmallow so you have to wipe cache and data through safestrap
3. If you flash odin files or other roms that flash a recovery image you will loose safestrap ability. There is a safestrap recovery image in files in post 1 that you can flash in odin too get back safestrap abilty.
4. Flashing roms that dont contain safestrap may cause you too loose safestrap so I recommend flashing one of the safestrap zips to add it to roms. This is not necessary on above roms.
5. This is not supported by me anymore. I try and help but I don't check this threads regularly.
6. If you loose safestrap on Marshmallow roms the only way too get it back is to start over from post 1
7. If you find yourself on kitkit rom constantly booting too safestrap flash the KitKat safetrap zip in safestrap
SafeStrap Zips
View attachment Safestrap-4.11-B01-KLTEVZW_MM_LL.zip
View attachment Safestrap-4.11-B01-KLTEVZW-SS-FF-flashable-KK.zip

Bro, you are quite a crack, despite the time that the S5 already has, you keep releasing content to get more out of the s5, I'm still using it and personally I have installed all your roms. Thanks a hug.

Jose_cm001 said:
Bro, you are quite a crack, despite the time that the S5 already has, you keep releasing content to get more out of the s5, I'm still using it and personally I have installed all your roms. Thanks a hug.
Click to expand...
Click to collapse
I just organized stuff better. All this stuff has been around for awhile. I just had it in many different threads so I consolidated it into one thread. I have been cleaning and closing some threads. Im really surprised anyone still uses an s5 but hey im glad someone still gets some use out of this stuff. I made sure all links worked and reuploaded stuff with dead links so should be good now.
Sent from my iPad using Tapatalk

i'm following these instructions but i'm too gumpy to understand:
"7. Run the Install.cmd this should install some apks on your phone then reboot your phone"
i'm connected to a windows 7, i'm supposed to be running a program from the pc then?

chrisco78 said:
i'm following these instructions but i'm too gumpy to understand:
"7. Run the Install.cmd this should install some apks on your phone then reboot your phone"
i'm connected to a windows 7, i'm supposed to be running a program from the pc then?
Click to expand...
Click to collapse
Well yes you have to initially root the phone so you can install safestrap. You have too push the apps to your phone after you install the combination firmware as it has no apk installer so you have too install the apps needed for root and safestrap with adb using the computer. Once that’s done you don’t need computer anymore
Sent from my iPad using Tapatalk

jrkruse said:
Well yes you have to initially root the phone so you can install safestrap. You have too push the apps to your phone after you install the combination firmware as it has no apk installer so you have too install the apps needed for root and safestrap with adb using the computer. Once that’s done you don’t need computer anymore
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
thank you, i was actually able to figure it out eventually i just forgot to timestamp how long it took me (hours)
appreciate the condensed update, though! most s5ers are still holding on because battery swapability is more important than the app du jour

If I flash the Lollipop ROM will I be able to use the settings factory reset option? Or will that cause a brick without reflashing again?
I want to get the phone in a stock state but maintain safestrap otherwise. Remove all personal data, Disable Reactivation Lock etc (I can't turn it off on my current ROM for some reason). Or I guess getting completely stock even without safestrap is okay too since its still possible to re-get it if needed.

hypermetuljason said:
If I flash the Lollipop ROM will I be able to use the settings factory reset option? Or will that cause a brick without reflashing again?
I want to get the phone in a stock state but maintain safestrap otherwise. Remove all personal data, Disable Reactivation Lock etc (I can't turn it off on my current ROM for some reason). Or I guess getting completely stock even without safestrap is okay too since its still possible to re-get it if needed.
Click to expand...
Click to collapse
The factory reset option in settings will only work if you have stock recovery installed. Format data in safestrap will totally wipe internal storage. wiping just data in safestrap will remove all data except media files. You can flash stock and do it or the combination firmware. All will accomplish the same results.
Sent from my iPhone using Tapatalk

jrkruse said:
This Process Will Install On The EMMC_11 Locked Bootloader Verizon S5
Marshmallow QL1 Stock Rom NonRooted With Safestrap.
Lollipop PB1 Stock Rom Rooted With Safestrap.
KK Rom Rooted With Safestrap
What This Does
This gives you the ability to boot into safestrap without a computer like the old way was.
You can use safestrap to modify the rom delete apps flash mod zips and even run xposed. Many xposed modules will work without root
You can use safestrap to go back to earlier roms like lolipop or kitkat were you can have root
You can flash some custom Samsung Based Roms. I have a few in the forum
You cannot root Marshmallow roms with a locked bootloader
You cannot flash asop based roms like Lineage as these require a custom boot image
You cannot unlock your bootloader even though you have safestrap
Downloads
EMMC_11_S5_Root_Tools.7z
Instructions To Install Safestrap
**If you already have safestrap installed you can skip to Installing Roms Post 2
**If you already have rooted you can skip to Installing Safestrap
1. Download and unzip files
2. Reboot phone too Download Mode by holding Power+VolDwn+HomeButton as phone starts up
3. Plug phone into computer and open the Odin provided in the above file in the Odin_Folder
4. In Odin Choose BL slot and choose the
COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5
Located in the Odin_Folder
5. Flash the file using provided Odin let phone reboot. This will wipe your phone
6. Once phone is rebooted make sure its plugged into computer and phone use recognized by computer
7. Run the Install.cmd this should install some apks on your phone then reboot your phone
8. When phone reboots choose the Apex launcher which will make it easier to find stuff
9. There are 3 different options installed to root your phone 2 different towel root methods and a KingRoot method
Towel Root Method
10. You need too be connected to a network. Try one of towel root apps and if not successful then try the other one. If it doesn't work go to King root section
11. If towel root succeeds then run the click on the super su app and choose to update su binary and choose normal once successfully updated reboot phone
King Root Method
These steps are only needed if towel root failed
12. You will need to be connected to a network. Click on King root app then click try root
13. Once root is successful don't click on the optimize and close the king root app.
Installing Safestrap
14. Now that you have rooted from one of the above methods click on the BusyBox app and install busybox click allow in the root dialog box
15. Now click on safestrap app and clisk install safestrap click allow in root dialog app once installed click reboot to safestrap
Click to expand...
Click to collapse
Ok, I followed these steps and made it all the way through this time. HUZZAH!!! (Towelroot didn't work since it said it couldn't connect to the internet) King root worked.
Only problem is, how do I know it worked? There isn't a tool for checking if root worked and this version of ROM doesn't seem to have any apps like Google Play Store to grab more apps. How do I install more apps? Thanks!

OreganoPlanter said:
Ok, I followed these steps and made it all the way through this time. HUZZAH!!! (Towelroot didn't work since it said it couldn't connect to the internet) King root worked.
Only problem is, how do I know it worked? There isn't a tool for checking if root worked and this version of ROM doesn't seem to have any apps like Google Play Store to grab more apps. How do I install more apps? Thanks!
Click to expand...
Click to collapse
The whole point is too get safestrap installed if you can boot to safestrap then the process worked
Sent from my iPhone using Tapatalk

JRKRUSE. Thanks so much for this. I've been stuck for a few days with my dad's old S5 trying to get it back to working. I wiped it, and couldn't get past the Samsung Account Reactivation Lock. Tried flashing a few stock firmwares, but nothing worked. I used your method to install the bootloader successfully. Once installed it boated me into a stripped down version of Android, which displayed all sorts of system diagnostic info on the bottom half of the screen. (Not sure what this is called.) I couldn't get the .cmd file to copy the apk's over but it let me copy them over to the downloads folder and install them all one at a time on the phone. Successfully gained root and followed the rest of your steps. Was successfully installing KitKat and finally getting around the Activation Lock. Thank so much!!!

jmc15john said:
JRKRUSE. Thanks so much for this. I've been stuck for a few days with my dad's old S5 trying to get it back to working. I wiped it, and couldn't get past the Samsung Account Reactivation Lock. Tried flashing a few stock firmwares, but nothing worked. I used your method to install the bootloader successfully. Once installed it boated me into a stripped down version of Android, which displayed all sorts of system diagnostic info on the bottom half of the screen. (Not sure what this is called.) I couldn't get the .cmd file to copy the apk's over but it let me copy them over to the downloads folder and install them all one at a time on the phone. Successfully gained root and followed the rest of your steps. Was successfully installing KitKat and finally getting around the Activation Lock. Thank so much!!!
Click to expand...
Click to collapse
Sorry to reply to such an old post, but which KitKat ROM did you end up using? I have a few phones stuck asking me to log into the last used Samsung account and I need a ROM that will bypass that screen.

This thread saved my mysteriously soft bricked, unlocked & rooted S5 VZW device. Thank you jkrruse.
When I try to download EMMC_11_PB1_LL_Rooted_Safestrap_Full.zip I get no mirrors available. Am I SOL?
edit - now one mirror is available which is flaky slow and drops less than 10% into download.
2nd edit- went with Brave browser and used it's download manager to continuously resume dropped download. Hash looks good so here goes...
Final cut: All is well and once I got everything my way I wanted to backup and could not find Safestrap. On boot I get RECOVERY BOOTING..... and nothing else. Had to pull battery. So I'm at a loss. Finally I took the time to make a check list of every step which really doesn't take long and methodically performed each step until success. Have the device where I want it and including a backup. I have many devices and each is unique but this 900V is a workhorse. I think I task overloaded it before so lesson learned.

Updated files to be more compatible with newer computers

JKruse you are awesome man - I just tried to take an old S5 (cid 11) to try and work some magic to get around the YouTube app "not supporting" it, broke my S5 bad, and used your threads to fix myself back to PHX 15. (NOT the first time ive been totaled before) You been dope since I first bought it! Many thanks!

Well with dozens of phones and most far newer than my s5 I finally had to update it to use a certain mission critical app so I went for LL. Followed the above mostly and it's working although I haven't had the chance to wring out everything yet. Thanks jrkruse again for all your great work! Wondering if I'm the last person on the planet to upgrade 4.4.2 to 5

droidzer1 said:
Well with dozens of phones and most far newer than my s5 I finally had to update it to use a certain mission critical app so I went for LL. Followed the above mostly and it's working although I haven't had the chance to wring out everything yet. Thanks jrkruse again for all your great work! Wondering if I'm the last person on the planet to upgrade 4.4.2 to 5
Click to expand...
Click to collapse
I'm still using 4.4.2 but on a T-Mobile S5 instead of the Verizon one.

I wish to thank jrkruse for making this post two years ago, for a phone that is 9 years old.
I paid $45 for the Verizon version of the Galaxy S5. Obviously, I don’t know what I’m doing. Thanks to this post and all the work that went into researching the problems and packaging the solution into a concise solution, I have a working version of an unrooted Marshmallow.
When I got the phone, it started up from a factory reset but as soon as I connected to the internet I got the message
“Device owner policies aren't supported on this phone.”
The menu key, home key and camera were disabled. I was locked out.
I used the Verizon 6.01 upgrade package, hoping it would do a fresh install. It got worse, I got the Knox security violation. I was double locked out.
So I started reading. It was looking bad, there was an embedded kill switch that permanently bricks the phone. After a bit more reading, I discover that I had the Version with cid starting with 11 from a post that said any manufacture date after the year 2014 was a cid 11. I found this thread, so from a locked up phone. my situation worked out to a smoothly running unrooted version of Marshmallow.
I know I didn’t carefully follow the instructions but I’ll layout my journey, for anyone else who is in similar circumstances. I invite comments to tell me what I should’ve done.
Requirements, I used a Windows PC, cable connecting the PC to phone, a micro SD card and an SD adapter that connects to a PC.
The package EMMC_11_S5_Root_Tools_2022_V3.7z is the complete one stop shopping deal and I went to https://www.7-zip.org/download.html to be able to unzip it.
After you unzip it, everything is ready to go.
The procedures are done by scripts, so there is hardly any typing.
The first routine prepares the phone for rooting and safestrap.
The next instruction reads
‘7. Run the Install_One_Click.cmd this should install safestrap.”
When I first read this, it was confusing to me, because I didn’t see a One_Click program. But all you have to do is double click the file named “Install_One_Click”. This is a command file that does all of the typing, both on the PC and phone.
In my case, everything ran as planned and I could skip the instructions for contingency cases.
The script did more work than the instructions in the post required.
The script stops to ask to allow rooting to install safestrap. Tap allow.
The script ends up with the safestrap screen on the phone, asking to install a rooted TWRP. This second time you decline.
On the PC I copied the EMMC_11_QL1_MM_NonRooted_Safestrap_Full_V2.zip file onto a micro SD card, using a USB SD card adapter.
I inserted the card on the phone.
I tapped the install button in safestrap selecting the file on the SD card.
After the install, you end up with Marshmallow. All I did was a few clicks in Odlin, double click on “Install_One_Click” , one tap to allow rooting, one tap to prevent rooting of TWRP and one tap on the install button in safestrap. All in under 15 minutes.
I got a very sleek, clean Marshmallow.
I then got the pop screen “Unfortunately, Google Store has stopped.”
I followed instructions from
https://www.androidpolice.com/install-google-play-store-any-android-device/
I simply downloaded 4 files.
https://www.apkmirror.com/apk/googl...account-manager-6-0-1-2-android-apk-download/
https://www.apkmirror.com/apk/googl...ervices-framework-6-0-1-android-apk-download/
https://www.apkmirror.com/apk/googl...-42-12-040408-481949630-android-apk-download/
https://www.apkmirror.com/apk/googl...-18-21-0-pr-481699564-3-android-apk-download/
installed them and clicked done not open and then rebooted.
The Google Store message was gone, just like the Knox and owner policy messages.
I could download apps from Google Play.
Everyone’s work turned a broken phone into a fully operational one.
I thank everyone.

Database Info

welcome