Related
Hello everyone.
I come to you because I've searched a lot about S5 VRZ on the XDA forum. My purpose is to root my phone with the latest Magisk version (at least 14.0) and maybe to install a custom Rom on it too (I saw Phoenix v15 which could work f I'm not wrong). But I'm new in rooting and in customizing my phone, so I come here to request your help.
Those are my phone informations :
1) Before doing anything on it I had this : Galaxy S5 VRZ - Android 4.4.4 - BootLoader version ANK2
2) I followed this guide with CID 15 : [GUIDE] Root, Bootloader Unlocks, and More!
At this point I didn't saw this thread which told me I probably did the wrong thing in step 2: [GUIDE] painiac's Essential Guide to Galaxy S5 Flashing, Rooting, Fixing, Customizing
But now I did and after doing step 2 guide I'm in this configuration : Galaxy S5 VRZ - Android 6.0.1- BootLoader version QB2
My phone still work but I don't really know what to do, if I'm right or wrong ? I'm unrooted now, trying to reinstall Magisk on another way.
So my questions are:
What to do with this configuration to get rooted with Magisk version 14.0 at least ?
And after, which custom ROM may I install on my phone and how ? (links are welcomed ofc)
I would really be glad if someone could help me to solve this situation. And I thank everyone who'll fully read this thread for the attention you paid to it (and also because I'm french and probably don't speak a really good englsih ^^')
Thank you for you help and have a good day ! :good:
What I've alrdy read on xda-developper.com :
[GUIDE] Root, Bootloader Unlocks, and More! - eMMC_CID_Checker_.apk
[GUIDE] Root, Bootloader Unlocks, and More!
[GUIDE] Unlocking the Galaxys S5 Bootloader using DEV Bootloader [KK-MM]
[VZW_Stock TW Rom][6.0.1 MM QA1 Build Odex For Locked Bootloader SafeStrap Only]
How To Flash Custom 6.0.1 Roms On Locked Bootloader That Cannot Be Unlocked
[PORT][ROM][G900V][VZW]PhoeniX ROM V15.0 MM 6.0.1[Aroma Installer Dev Bootloader]
Verizon Samsung Galaxy S 5
If you want Magisk, you probably should install it.
It's usually is installed via TWRP recovery as a flashable zip file.
http://tiny.cc/latestmagisk
If you don't have TWRP recovery, you probably should install it.
It's usually is installed via Odin as a flashable tar file.
https://dl.twrp.me/klte/
You can only flash TWRP into SM-G900V if the bootloader is unlocked.
Unlocked bootloader looks like this (MODE: Developer):
If you still have not unlocked the bootloader, then you probably should try to do it.
It can be unlocked on the devices with CID15 (determined with this tool, first two digits in CID line).
Hello,
I am looking for a guide to root and install TWRP on Sprint Note 5 upgraded to Android 7.0.
Some background information:
Note 5 was on Android 5.11 and was having random reboots, caused by unstable Noble kernel.
I used the following guide to root, install TWRP and stable Beastmode kernel.
https://forum.xda-developers.com/sprint-galaxy-note5/general/how-to-root-instructions-t3187895
Note 5 went south after i attempted to install Xposed on rooted 5.1.1.
I experienced bootloops and was never able to boot in 5.1.1 ever again.
I failed to flash stock 5.1.1 to Note 5, despite multiple tar's and versions of ODIN.
I though my phone was unrecoverable.
Fast forward 2 days and i was able to successfully flash Android 7.0 via ODIN.
I can successfully boot into Android 7.0, though i prefer to be rooted.
Now i need to root Android 7.0, install TRWP, upgrade to stable kernel, and install Xposed, if possible.
Knox has already been tripped and I was not going to use Samsung Pay anyway.
Phone details:
Model number: SM-N920P
Software version: N920PVPU3DQC5 (Nougat 7.0)
Hardware version: N920P.04
Baseband version: N920PVPU3DQC5
Build Number: NRD90M. N920PVPU3DQC5
Please let me know if more information is needed.
Thank you in advance.
cynflux said:
Hello,
I am looking for a guide to root and install TWRP on Sprint Note 5 upgraded to Android 7.0.
Some background information:
Note 5 was on Android 5.11 and was having random reboots, caused by unstable Noble kernel.
I used the following guide to root, install TWRP and stable Beastmode kernel.
https://forum.xda-developers.com/sprint-galaxy-note5/general/how-to-root-instructions-t3187895
Note 5 went south after i attempted to install Xposed on rooted 5.1.1.
I experienced bootloops and was never able to boot in 5.1.1 ever again.
I failed to flash stock 5.1.1 to Note 5, despite multiple tar's and versions of ODIN.
I though my phone was unrecoverable.
Fast forward 2 days and i was able to successfully flash Android 7.0 via ODIN.
I can successfully boot into Android 7.0, though i prefer to be rooted.
Now i need to root Android 7.0, install TRWP, upgrade to stable kernel, and install Xposed, if possible.
Knox has already been tripped and I was not going to use Samsung Pay anyway.
Phone details:
Model number: SM-N920P
Software version: N920PVPU3DQC5 (Nougat 7.0)
Hardware version: N920P.04
Baseband version: N920PVPU3DQC5
Build Number: NRD90M. N920PVPU3DQC5
Please let me know if more information is needed.
Thank you in advance.
Click to expand...
Click to collapse
Use Odin to root with c.f. auto root just Google cf auto root and download the file for your phone you know the rest. After being rooted you can install twrp with the official app in the play store they give you simple instructions but what they don't tell you is DO NOT FLASH THE .img.tar file FLASH the .img file only .tar files are for pc and will soft brick you. Again FLASH the .img file to recovery. Bang you have twrp if you can't get into recovery download quick reboot from play store works great im rooted with twrp on note 5 7.0 nougat that's all I can confirm. I accomplished this all by reading the forums for 2 days
Anything with CF Auto Root is obsolete. Just follow this guide: http://galaxynote5root.com/galaxy-n...galaxy-note-5-on-android-7-0-nougat-w-magisk/
SAMSUNG ANTI ROOT REMOVAL OR ANY OTHER SUPER USER APP IS NOT NEEDED ANYMORE. JUST INSTALL THE MAGISK .ZIP AND REBOOT.
Files are:
Latest TWRP: https://dl.twrp.me/nobleltespr/
Magisk 15.3: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
This will work for ALL NOUGAT builds, including the latest DRA1 (I've tested it myself) This phone is over 2 years old so development is kinda dead to be honest. There is only one custom kernel available here: https://forum.xda-developers.com/sp...nel-twisted-note-7-0-nougat-april-15-t3590280
cachanilla86 said:
Anything with CF Auto Root is obsolete. Just follow this guide: http://galaxynote5root.com/galaxy-n...galaxy-note-5-on-android-7-0-nougat-w-magisk/
SAMSUNG ANTI ROOT REMOVAL OR ANY OTHER SUPER USER APP IS NOT NEEDED ANYMORE. JUST INSTALL THE MAGISK .ZIP AND REBOOT.
Files are:
Latest TWRP: https://dl.twrp.me/nobleltespr/
Magisk 15.3: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
This will work for ALL NOUGAT builds, including the latest DRA1 (I've tested it myself) This phone is over 2 years old so development is kinda dead to be honest. There is only one custom kernel available here: https://forum.xda-developers.com/sp...nel-twisted-note-7-0-nougat-april-15-t3590280
Click to expand...
Click to collapse
Its not obsolete I got a free hotspot buddy. I dont need supersu remover because i dont care about fancy samsung or andriod pay i will continue to use cf auto root until its exhausted because i have never bricked a phone using it
Thank you all for your replies.
I was able to root via CF Auto Root and installed TWRP recovery.
Does the free hotspot need to be flashed via Recovery?
Thank you in advance.
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!
Hey There Were No Posts Regarding Latest Bootloaders, Firmwares, Twrp, Etc... For C7 And C7 Pro.
So I Thought Of Making This Thread Which Will Be Useful For My Other Rom Threads
OK , So Here Are The Shortcut Links To The Specific Post Directly -
#1 Latest Official Full Firmware -
#2 Latest Official Bootloader -
#3 Root Guide -
#4 Latest TWRP Recovery -
#5 OEM Unlock Guide -
#6 Soft/Hard Brick Recovery -
Basics-
-Our Samsung Android Devices Have Three Modes, Namely -
2 System
1 Recovery Mode
3 Download Mode
1) System-
It Is The Normal Workaround That Every Device Normally Boot To Which We Also Call As TouchWiz, One UI, Etc...
You Normally Have To Just Power On Your Device And It Directly Boots To System And The System Is Normal Under Control Of The Vebdor (ie: Samsung, One Plus,etc..) Who Deny Full System Access There By Restricting The User From Modifying All Thats There In The Root Directory, So Here Is What We Mean By Rooting Your Device -
And Custom Rom Means Nothing But Replacing Your Stock System With A modified Or With A Custom System ....
2)Root -
There Is A Thing Called Root Folder Which Is The Very First Directory In Your Device And Usually These Directories Cannot Be Accessed Directly Because Of OEM Control Over The Device And What We Mean By Rooting Is Nothing But
The Process Of Handing Over The Control Of Device From Oem To A Root Manager (A App That Monitors Root Activity) Is Called Rooting..
3) Bootloader (AKA Download Mode In Android) -
It Is The Program That Manages The Booting Process (Before Kernel) And Also Service As A Recovery Point In Most Cases. Where You Will Use Tools To Communicate With It And Use The Bootloader As Medium To Intsall Other Firmware Including Root & Custom Recoveries. So For Installing Latest Firmware Files Latest Bootloader Is Needed ...
Official Bootloaders Are Usually Preferred, Which Has To Be Unlocked Via Developer Options (OEM Unlock)
4) Recovery -
This Is The Place Where We'll Be Hangin Out Most Of The Time For Installing Roms, Kernel, etc...
Basically Your Device Comes With A Stock Recovery Which Can Do Nothing But Just Format Data,Clear Cache & Redirect b/t System And Bootloader.... But Thats Not What We Need, So What We Do Is Install A Custom Version Of Recovery Which Can Be Replaced With Stock Recovery And Do What Ever Stuff We Want To ..
Why Go For Custom Recovery ?
Just Imagine A State Where Your System & All The System Security Have No Control (Or It Is Switched Off), That Is What A Custom Recovery Takes Advantage Of.....
OK, So In That Case The Custom Recovery Can Access The Root Directories And Can Make Modification To System Without The Systems Knowledge Or With The System Along Side,
These Days The Oem System Have Hardened Custom Recovery Detection And Stuff Like That, So We Need A Recovery & Also A system That Supports Custom Mods With It .... Inorder To Do That We Make Use Of Custom Recoveries To Delete The Existing System and Replace It With A Similar/Modified System Which We Call It As A Custom Rom, Which Allows Modification To Any Part Of The Device Without Interruption ... This Is What An Super User Basically Does When He/She Unlocks Bootloader And Makes Modification To System
The Most Common Recovery Is TWRP Recovery
5) Hard/Soft Brick -
Is A State Where You Cant Boot To System (Usually Soft Brick) & Face Bootloops Etc... This State Is Usually Recoverable By Flashing The Original Firmware Again..
When You Have Messed Something With The Kernel/Recovery (Recovery In Most Cases) ,Your Phone Wont Boot, Turn On, Literally Anything ...(Hard Bricked) In This Case You Have Only On Option That Is To Boot To Download Mod (It Wont Boot Via 3 Button Combo) But Still There Are Ways To even Recover From This State Like Using Usb Jibb Or By Plugging Into The Device Into The PC With The Flash Tool Running .... etc
6) Kernel -
A Kernel Is A Platform Below System And Hardware, It What Controls The Clock Speed, Cores, Etc And Other Hardware/Software Related Things In A Device, These Often Determine The Performance Of A Device & There Fore ppl Tend To Move To A Custom Kernel For Flexibility ....
Will Add More Basic Tips
Official Fimware C7 / C7 Pro
Official Firmware -
C7 Pro -
C701f -
Link To The Latest Oreo [8.0] Firmware For C701f - C701F 8.0 FIRMWARE
C7010 -
Link To The Latest Oreo [8.0] Firmware For C7010 - C7010 TGY 8.0 FIRMWARE
C7018 -
Link To The Latest Oreo [8.0] Firmware For C7018 - C7018 CHC 8.0 FIRMWARE
Click to expand...
Click to collapse
C7 -
C7000 -
Link To The Latest Oreo [8.0] Firmware For C7000 - C7000 tgy 8.0 FIRMWARE
Click to expand...
Click to collapse
Instruction For Installing The Stock Firmware-
•Download the The Correct Firmware For your Device From The Above Links
•Download The Latest Odin (v3.13)
•Extract The Firmware Using The Extraction Tool (7zip,winter,etc)
•Install The Proper Drivers For Your Device - Samsung Drivers
•Run Odin In Your Windows and click on "bl" and locate the bl***********.md5 ( "**" Reprsents Some Similar File In The Firmware Zip) file in the file browser
Similarly Locate "ap","csc" In The Same Way , (do not click on "home csc")
•Go To Odin Mode Or Download Mode In Your C7/C7 pro By Pressing Vol Down + Power + Home Key for 30 sec.
•Then Connect Your Phone To The PC & Click On Start In Odin Once You See A "added" Text .
•Click On Start When Everything Is Ready .... And If Everything Goes Well You'll See A Green Pass Icon In Odin & And Your Device Will Boot To System Within (7-15) Min .
Click to expand...
Click to collapse
root ----WILL ADD, GIMME SOME TIME---
Ill make a guide if possible... rn ill just provide the links for twrp -
TWRP (C7)
TWRP (C7 Pro)
Custom ROMS For C7 & C7 Pro -
C7 Pro -
1) Eulah Rom
Supported Devices - C701F/C7010/C7018
Current Version - v2
One UI Based Rom
Maximum Feature Packed
Fully Customizable Via Installer
With Latest One UI
Several Mods & Ports
The Best Rom So Far
Thread Link - Eulah Rom
2) Sudo Rom
Supported Devices - C701F/C7010/C7018 | C7000
Current Version - v1
Samsung Experience Based Rom
Super Lite Package with Lite & Smooth Environment
Hyper Performance (Best Rom For Gaming)
Multi Variant & Csc Support
The So Far Latest Rom
Thread Link To - Sudo Rom
3) Sudo Lite Rom
Supported Devices - C701F/C7010/C7018
Current Version - v1
Samsung Experience Based Rom
C9 Pro Port With Minimal & Easy Installation Process
Lightest Package with Lite & Smooth Environment
Super Fast Booting Speed
Thread Link To - Sudo Rom Lite
4) Jesvi Stock Oreo Rom
Supported Devices - C701F
Current Version - v1
Samsung Experience Based Rom
No Edits No Nothing, Just Pure Stock With Needed Patches
Base Rom & Can Be Used For Development
Thread Link To - Jesvi Stock Oreo Rom
5) Lite Rom
Supported Devices - C701F
Current Version - v6
Dream UX Based Rom
Lite Rom
Comes With Nougat Mods
Smooth Environment
Thread Link To - Lite Rom Nougat
6) Lineage OS 14.1
Supported Devices - C701F
Current Version - v1
AOSP Based Rom
You Get All The Benefit Of Lineage OS Nougat
Light Package
Alpha State
Thread Link To - Lineage Os 14.1
Click to expand...
Click to collapse
C7 -
1) Sudo Rom
Supported Devices - C701F/C7010/C7018 | C7000
Current Version - v1
Samsung Experience Based Rom
Super Lite Package with Lite & Smooth Environment
Hyper Performance (Best Rom For Gaming)
Multi Variant & Csc Support
The Latest Rom
Thread Link To - Sudo Rom
Click to expand...
Click to collapse
Latest Bootloader -
C7 Pro -
C701f -
Link To The Latest Oreo [8.0] Bootloader For C701f - C701F Latest Bootloader
C7010 -
Link To The Latest Oreo [8.0] Bootloader For C7010 - C7010 Latest Bootloader
C7018 -
Link To The Latest Oreo [8.0] Bootloader For C7018 - C7018 8.0 Bootloader
Click to expand...
Click to collapse
C7 -
C7000 -
Link To The Latest Oreo [8.0] Bootloader For C7000 - C7000 Latest Bootloader
Click to expand...
Click to collapse
Instruction For Flashing The Latest Bootloader-
•Download the The Correct Bootloader File For your Device From The Above Links
•Download The Latest Odin (v3.13)
•Extract The Firmware Using The Extraction Tool (7zip,winter,etc)
•Install The Proper Drivers For Your Device - Samsung Drivers
•Run Odin In Your Windows and click on "bl" and locate the bl***********.md5 ( "**" Reprsents Some Similar File In The Firmware Zip) file in the file browser. Similarly click on " " and locate the " **********.md5".
•Go To Odin Mode Or Download Mode In Your C7/C7 pro By Pressing Vol Down + Power + Home Key for 30 sec.
•Then Connect Your Phone To The PC & Click On Start In Odin Once You See A "added" Text .
•Click On Start When Everything Is Ready .... And If Everything Goes Well You'll See A Green Pass Icon In Odin & And Your Device Will Boot To System Within (7-15) Min .
Click to expand...
Click to collapse
Oem Unlock (Not Visible bug) ----WILL ADD, GIMME SOME TIME, im feling sleepy right now---
jesvi said:
Oem Unlock (Not Visible bug) ----WILL ADD, GIMME SOME TIME, im feling sleepy right now---
Click to expand...
Click to collapse
did you wake up?
agritux said:
did you wake up?
Click to expand...
Click to collapse
Hahaha, *slept to death..
sry man , give me aome time
jesvi said:
Twrp 3.2.3 ----will add, gimme some time---
Click to expand...
Click to collapse
How much time do you need?
mrdeepmind said:
How much time do you need?
Click to expand...
Click to collapse
Check out the for some threads in c7 or c7 pro section in xda till i fully complete this thread..:good:
EDIT : I have added the links for twrp.
jesvi said:
Ill make a guide if possible... rn ill just provide the links for twrp -
TWRP (C7)
TWRP (C7 Pro)
Click to expand...
Click to collapse
I cant flash any ROM with any TWRP, i downloaded from all possible places (ROMs and TWRPs), it just crashes when i try, and restarts. I am not able to find official TWRP for my Samsung C7 Pro (C701F), But there are ROMs available and some youtube guy also installed it, dont know how.
Deval99 said:
I cant flash any ROM with any TWRP, i downloaded from all possible places (ROMs and TWRPs), it just crashes when i try, and restarts. I am not able to find official TWRP for my Samsung C7 Pro (C701F), But there are ROMs available and some youtube guy also installed it, dont know how.
Click to expand...
Click to collapse
Hello, this twrp works fine with the latest firmware and roms in the forum...
Make sure u have completely erased your data,system,cache & do a 'format data' in twrp before installing any rom or anything... coz this removes the system encryption...
And make sure the rom file is good and not corrupt...
jesvi said:
Hello, this twrp works fine with the latest firmware and roms in the forum...
Make sure u have completely erased your data,system,cache & do a 'format data' in twrp before installing any rom or anything... coz this removes the system encryption...
And make sure the rom file is good and not corrupt...
Click to expand...
Click to collapse
Yup i ensured all of these (even md5 checksum of file downloaded), But not working. I will follow the steps you given and try to install.
Hello,
I have a Samsung Galaxy S10e, and recently I've decided to flash a custom ROM on it.
I upgraded from Android 10 Stock Samsung to Android 11 LineageOS 18.1 following this and this guide.
All successful.
However, after some minutes, I wanted to try out a different ROM, so I installed Pixel Experience (which was based on Android 10 -- big mistake). This ended up resulting in a soft brick, throwing me an 'REV Check Fail Device 9 Binary 8' error everytime I turned on the device. I couldn't get into recovery mode - only download mode.
I managed to fix this by waiting for the Samsung's Stock Firmware (based on Android 11) to come out (did after some hours, I was so lucky I didn't have to wait that long) so I could flash it and go back to stock using Odin. All good, the phone boots, everything works as expected -- no problems what so ever.
I should've made a backup in TWRP, in case something went wrong before flashing Pixel Experience (?), but I didn't. I also should've known that I couldn't downgrade. Anyway...
When I enter download mode, the following important info is displayed:
PRODUCT NAME: SM-G970F
KG STATE: Checking
FRP LOCK: OFF
OEM LOCK: OFF (U)
Secure Download: Enabled
WARRANTY VOID: 1 (0x0e03)
I believe my bootloader is unlocked, since it's enabled and grayed out in developer otions. I also believe that I have no custom recovery (since I flashed Samsung's Stock Firmware), because when I press the recovery button combination, it doesn't boot into TWRP.
My questions:
1. Should I repeat the process in here when flashing TWRP again since I literally flashed the samsung stock firmware? I'm guess I'm comming from "stock" even though I already have some steps complete? Should I flash the " multidisabler-samsung-2.* " too? I already did once, do I need to do it again since I flashed the Stock Samsung firmware?
2. Is there anything you'd recommend me doing to prevent stupid actions like I had above?
3. As long as I have the Stock Samsung Firmware and the phone boots into download mode, I'm good right?
4. Is TWRP 3.5.0 compatible with the S10e Android 11? Or does android versions not matter with recoveries?
5. Which ROM would you recommend to have a good Pixel-Like Stock Android experience? I'm debating wether I should use the PixelExperience again (I used it on my nexus 5x and was happy with it) or if I should try out something else. I also believe it's not yet available unofficially, so I'd have to wait.
6. Would you recommend me installing a GSI?
Thanks!
Questions updated
bump!
Too bad you didn't get an answer... Did you find anysolution ?
Having issues installing TWRP with odin on a s10e..