Database Info

[CWM][TOUCH][Full Working]Xolo Play T1000

Here is the full working CWM Touch recovery for Xolo Play enjoy!!
Build from http://builder.clockworkmod.com with build ID=f1c98dc9e25bfdf38e6fe7437969d8e5
Things required
1.PC with usb drivers and Android SDK tool installed
2.Rooted phone
Procedure:
1.Enable USB debugging in phone.
2.Assure if drivers are installed properly . If not then use Pdanet to install xolo play drivers or try this.
GET recovery.img FROM THE ATTACHMENTS
3.Then open cmd as administrator
[Note: You must have installed Android SDK tools ]
4..Put the downloaded recovery.img in C:\Users\[USER]\AppData\Local\Android\android-sdk\platform-tools.
5.Attach Phone through USB cable.
6.type
Code:
cd C:\Users\[B][USER][/B]\AppData\Local\Android\android-sdk\platform-tools
7.then type
Code:
adb shell
8.now type
Code:
su
9.then
Code:
reboot bootloader
10.continue
Code:
fastboot flash recovery recovery.img
DONE!!
Credit:
Code:
ankur850 for graphics.c
builder.clockworkmod.com
Google

i have added nvidia boot recovery drivers in my post...

devilex94 said:
Here is the full working CWM Touch recovery for Xolo Play enjoy!!
Build from http://builder.clockworkmod.com with build ID=f1c98dc9e25bfdf38e6fe7437969d8e5
Click to expand...
Click to collapse
The build id is outdated. Do u have a permalink?
Build seems to work. Good job! :good: Could you share with the community how you managed to make it work? Touch inside recovery doesnt work but that can easily be ignored. Testing the recovery further now. Will report back.
Edit: Touch works now. :/

deepaktom said:
The build id is outdated. Do u have a permalink?
Build seems to work. Good job! :good: Could you share with the community how you managed to make it work? Touch inside recovery doesnt work but that can easily be ignored. Testing the recovery further now. Will report back.
Click to expand...
Click to collapse
yes i used builder on builder.clockworkmod.com
Uploaded stock recovery.img then recovery.fstab and finally uploaded graphics.c from ankur850's git ( here if you need http://www.mediafire.com/?2dsls2ccps163y0 )
For me touch is working inside cwm recovery
It's full working for me
http://jenkins.cyanogenmod.org/job/recovery/33680/ <= Link to recovery

Good work bro.. :thumbup:
With the pace the development going on, I am sure that we will get custom rom for xolo t1000 soon
Sent from my XOLO Play

anyway to backup original stock recovery?

emptyragnarok said:
anyway to backup original stock recovery?
Click to expand...
Click to collapse
don't worry it's already available here - http://www.mediafire.com/folder/180y8ueauzbcy/Stock

devilex94 said:
don't worry it's already available here - http://www.mediafire.com/folder/180y8ueauzbcy/Stock
Click to expand...
Click to collapse
@devilex94 I think we just need to follow same above steps except for one thing we need to point to stock recovery if we want to revert back! is it right??

emptyragnarok said:
@devilex94 I think we just need to follow same above steps except for one thing we need to point to stock recovery if we want to revert back! is it right??
Click to expand...
Click to collapse
Yes that's right
Sent from my XOLO Play using Tapatalk 2

For those who see their stock recovery even after flashing-
Follow instructions and flash the recovery in fastboot(till step 10.) hold down the power button till it switches off, now boot to recovery by power button + volume down button and you can access CWM.
Upon exit CWM will provide a fix regarding the phone reverting back to stock recovery, accept and reboot now CWM will stick!

Alternate method
You can also Flash CWM through https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Just place the recovery.img in the internal memory.
Open the Recovery Tools - Flasher app
Flash the recovery .
Choose Reboot to recovery.

Guys its high time we see a forum for xolo play!
Threads are all over the place! development would pick up the pace if we had a forum.
Head over to the forum request thread and upvote my request!
link- http://forum.xda-developers.com/showpost.php?p=46486866&postcount=11627

richie.slayer said:
Guys its high time we see a forum for xolo play!
Threads are all over the place! development would pick up the pace if we had a forum.
Head over to the forum request thread and upvote my request!
link- http://forum.xda-developers.com/showpost.php?p=46486866&postcount=11627
Click to expand...
Click to collapse
Yup...+1 to that . we desperately need a thread...come on guys ...need help from devs ..! :laugh:

help needed...Trouble mounting sdcard!!
Okayy...installed recovery using recovery flasher tool from playstore.... rebooted to CWM . Now it seems CWM is not recognizing my sdcard ! Tried different sdcard but of no use. Somehow its not detecting my external sdcard ....I cant take a backup,neither can I flash any zip...searched google for possible solutions but none seemed to work for me...
Log shows:
Can't mount backup path.
W:Failed to mount /dev/block/platform/sdhci-tegra.0/by-num/p1 ( no such file or directory)
I:Can't format unknown volume : /external_sd
I:Can't format unknown volume : /emmc
E:Can't mount /sdcard/
Done...
etc
Any help would be appreciated!

Still no reply....??
111kaustav111 said:
Okayy...installed recovery using recovery flasher tool from playstore.... rebooted to CWM . Now it seems CWM is not recognizing my sdcard ! Tried different sdcard but of no use. Somehow its not detecting my external sdcard ....I cant take a backup,neither can I flash any zip...searched google for possible solutions but none seemed to work for me...
Log shows:
Can't mount backup path.
W:Failed to mount /dev/block/platform/sdhci-tegra.0/by-num/p1 ( no such file or directory)
I:Can't format unknown volume : /external_sd
I:Can't format unknown volume : /emmc
E:Can't mount /sdcard/
Done...
etc
Any help would be appreciated!
Click to expand...
Click to collapse
did anybody face this issue?? DeepakTom? any idea where I should be looking at in order to fix this issue??

Reboot the phone and select external sdcard as primary storage in settings>>Storage

its done!
devilex94 said:
Reboot the phone and select external sdcard as primary storage in settings>>Storage
Click to expand...
Click to collapse
Well, I managed to fix this myself! it seems my sdacrd (8 gb transcend) somehow got corrupted. And everytime I tried to open CWM, It was not detected. So I managed to format it on my digicam. Funnily its now showing 4gb total space. Next I tried opening the CWM and this time it worked! backup went smooth, even flashed custom rom.
This is kinda strange that only half of my sdcard is accessible .Somehow the blocks got corrupted !anyway, at least its working!

Can we install this recovery using mobile uncle tool ?
your help will be really appericuated

decrypt /data

move fstab using official recovery ( adbpull /vendor/etc/fstab.kirin970 and fstab.kirin970.data - remove "avb" and encryption from userdata, replace the encryption line on data with 'encryptable')
format /data in unofficial recovery
install magisk in official recovery
for some reason it only works in that order, if you try and do it all in official or unofficial recovery it doesnt work and magisk recognizes encryption on data.
after each step reboot bootloader and flash respective recovery, then fastboot reboot unplug and hold power and vol up to go straight into recovery and continue, if you boot you have to start over)
when installing magisk zip you should see that it doesnt say keep force encrypt.
and if you go in settings you have the option to encrypt.

virtyx said:
move fstab using official recovery ( adbpull /vendor/etc/fstab.kirin970 and fstab.kirin970.data - remove "avb" and encryption from userdata, replace the encryption line on data with 'encryptable')
format /data in unofficial recovery
install magisk in official recovery
for some reason it only works in that order, if you try and do it all in official or unofficial recovery it doesnt work and magisk recognizes encryption on data.
after each step reboot bootloader and flash respective recovery, then fastboot reboot unplug and hold power and vol up to go straight into recovery and continue, if you boot you have to start over)
when installing magisk zip you should see that it doesnt say keep force encrypt.
and if you go in settings you have the option to encrypt.
Click to expand...
Click to collapse
Hi there
I´m struggling to get lineage 15.1 to install without google framework errors
You mention offical and unofficial recovery. I guess you are talking about twrp
when you say move fstab do you mean remove?
Could this encryption be my problem with lineage and gapps not installing as it should?

buenso80 said:
Hi there
I´m struggling to get lineage 15.1 to install without google framework errors
You mention offical and unofficial recovery. I guess you are talking about twrp
when you say move fstab do you mean remove?
Could this encryption be my problem with lineage and gapps not installing as it should?
Click to expand...
Click to collapse
After you install lineage format /data that should work
Totally irrelevant to OP

If i hadn't tried that i wouldn't ask here.
Not TOTALLY irrelevant, as my question is about the official and unofficial twrp having trouble mounting and wiping before flashing rom..
Please stop trolling

virtyx said:
move fstab using official recovery ( adbpull /vendor/etc/fstab.kirin970 and fstab.kirin970.data - remove "avb" and encryption from userdata, replace the encryption line on data with 'encryptable')
format /data in unofficial recovery
install magisk in official recovery
for some reason it only works in that order, if you try and do it all in official or unofficial recovery it doesnt work and magisk recognizes encryption on data.
after each step reboot bootloader and flash respective recovery, then fastboot reboot unplug and hold power and vol up to go straight into recovery and continue, if you boot you have to start over)
when installing magisk zip you should see that it doesnt say keep force encrypt.
and if you go in settings you have the option to encrypt.
Click to expand...
Click to collapse
If you format data, isn't the device going to be empty?
Only time I've done this before I had to copy a ROM via MTP in recovery and then flash with no Verity.
So forgive me if I'm wrong but if I format data, won't I end up with no operating system?

dladz said:
If you format data, isn't the device going to be empty? J
Only time I've done this before I had to copy a ROM via MTP in recovery and then flash with no Verity.
So forgive me if I'm wrong but if I format data, won't I end up with no operating system?
Click to expand...
Click to collapse
/system is where the system lives
/data is userdata and applications
Noting wrong with formatting, you will lose all apps and data though

virtyx said:
/system is where the system lives
/data is userdata and applications
Noting wrong with formatting, you will lose all apps and data though
Click to expand...
Click to collapse
Legend, thanks for clearing that up.
:good:
I know off topic, but out of interest with the p20 pro, if you did find yourself with no OS how would you get back to a functional phone?
There's no custom ROMs to flash, just never been in this situation before.
Hypothetically

dladz said:
Legend, thanks for clearing that up.
:good:
I know off topic, but out of interest with the p20 pro, if you did find yourself with no OS how would you get back to a functional phone?
There's no custom ROMs to flash, just never been in this situation before.
Hypothetically
Click to expand...
Click to collapse
You can use hurupdater and download the firmware from firmwarefinder on your of
Happened a lot of times for me

Just as a headsup, you dont need to decrypt anything when you just wanna do some changes once and are proper admin level on your desktop machine, ive moved a whatsapp message history from previous phone (also taken from protected space there) to P20P just by attaching it to pc in file transfer mode and then adding myself as full control user in the security tabs of the several system folder properties i went in to, worked like a charm.
The point im trying to make: Android and Windows finally understand each others permission systems (not sure since how long as ive been away from android for a few years) so you can just attach it and use Windows perm system to give yourself access where needed, lots easier & faster then making a bunch of changes to your phone in effect disabling encryption, something you in most cases dont really want to do permanently anyway, so this is a nice workaround that doesn't touch your phone's encryption settings but still lets you mess about with system files.
Just my 2 cents.

virtyx said:
move fstab using official recovery ( adbpull /vendor/etc/fstab.kirin970 and fstab.kirin970.data - remove "avb" and encryption from userdata, replace the encryption line on data with 'encryptable')
format /data in unofficial recovery
install magisk in official recovery
for some reason it only works in that order, if you try and do it all in official or unofficial recovery it doesnt work and magisk recognizes encryption on data.
after each step reboot bootloader and flash respective recovery, then fastboot reboot unplug and hold power and vol up to go straight into recovery and continue, if you boot you have to start over)
when installing magisk zip you should see that it doesnt say keep force encrypt.
and if you go in settings you have the option to encrypt.
Click to expand...
Click to collapse
I did everything step by step, the encryption is gone and yet I still get that stupid permission denied error when I try to do a backup in TWRP. So. F*cking. Annoying.
Update: when I press the "Install" button in TWRP, it shows giberish, but if I go to Advanced>File Manager everything has it's proper name. WTF?!
Hmmm, If I don't tick "Vendor" in the backup, I get this error:
Can not create 'data/media/0/2021-01-20--07-26-51' folder (No such file or directory).
Failed to make backup folder.
Update on update: oof, now everything that's in the internal storage is gibberish, even in the OS.

Guide: How to decrypt data in TWRP for Le Pro 3 AI

As you all know we have been searching for ways to root the Le Pro 3AI but failed. There are even 2 twrp but you can't really do much with them. TWRP 3.1 did not even start for me but 3.0.3 worked but what's the real problem? You can't mount /data and also i found another partition named /custom. It always fails to mount and there is no way to format it.
When you enter TWRP it ask for a password to decrypt. Simply click cancel and go to wipe, advanced wipe and check the data partition. Select repair file system and change it to ext2 and then back to ext4. Reboot to twrp again I don't think this is necessary but better take precautions. Now go to mount and select data you will see that you can actually mount it(~24000mb) .
You can also enable MTP to copy files to your phone in recovery such as .zips. I hope this helps you in way. I hope the devs find a way to make it possible to flash custom ROMs for this phone without any message appearing during boot and that there is no problem with imei. Thanks for reading and don't give up with this phone else it will be money down the drain. If I helped press the thanks button.

how did you install the TWRP?
im a noob in this

okay! so after attempting to install TWRP my phone bricked haha
i had to flash again the rom. geez!
i better not attempt again.

twrp isn't really a problem. it works for the most part, just cant be perma flashed, only booted. you can still flash zips via sideload as it is though, so that was never a *huge issue*. thing is, modifying system partition on official builds (25, 28) will cause security lockup. kernel needs to be patched, and prolly bootloader for this to be bypassed, and it seems its not easy. consequently root will fail too. on 27 though, you can easily boot twrp and flash a custom zip (except root), so there is nothing preventing you from removing bloat. even xposed works. you can even flash 27 kernel on both 25/28 and clean them too using same flashable zips. as far as custom rom goes, yeah, no, mtk device. prolly not gonna happen. be happy if you get root eventually.

sikica133 said:
twrp isn't really a problem. it works for the most part, just cant be perma flashed, only booted. you can still flash zips via sideload as it is though, so that was never a *huge issue*. thing is, modifying system partition on official builds (25, 28) will cause security lockup. kernel needs to be patched, and prolly bootloader for this to be bypassed, and it seems its not easy. consequently root will fail too. on 27 though, you can easily boot twrp and flash a custom zip (except root), so there is nothing preventing you from removing bloat. even xposed works. you can even flash 27 kernel on both 25/28 and clean them too using same flashable zips. as far as custom rom goes, yeah, no, mtk device. prolly not gonna happen. be happy if you get root eventually.
Click to expand...
Click to collapse
can you tell me the procedure on installing twrp?
i really wanted to enable multi window via adb when on recovery mode.
thanks

sikica133 said:
twrp isn't really a problem. it works for the most part, just cant be perma flashed, only booted.
Click to expand...
Click to collapse
I could flash only 3.0.3 . 3.1 never worked for me. Can't even boot.

i never said it could be flashed. it could be booted into. there are plenty of guides around how to boot recovery using fastboot (google fastboot boot recovery.img). once there, you can simply use adb sideload, or integrated file manager to clean system apps and reboot back into os. if you are using 25/28 u'll need to play a bit more to get everything up and running (imei issues), on 27S (multilanguage rom) this is pretty straightforward and no fixing is required

adb devices and uninstall system app
adb devices and uninstall system app
minimal_adb_fastboot_1.4.3_portable --- download androidfilehostcom/?fid=457095661767103465
cmd-here.exe
adb devices
adb shell
pm uninstall -k --user 0 [apk name]
com.letv.agnes
com.icoolme.android.weather
com.letv.android.bugreporter
com.letv.android.carservice
com.letv.android.ecoProvider
com.letv.android.letvyellowpage
com.letv.android.ota
com.letv.android.client
com.letv.android.quicksearchbox
com.letv.android.telextra
com.letv.android.usermanual
com.letv.app.appstore
com.letv.bsp.crashhandler
com.letv.bugpostbox
com.letv.lesophoneclient
com.letv.letvshop
com.singulariti.niapp
com.sohu.inputmethod.sogou.leshi
com.tencent.android.location
sina.mobile.tianqitongletv
com.autonavi.minimap
com.tencent.reading
com.le.share.pro3ai
com.letv.games
com.android.calendar
com.android.noisefield
youtubecom/watch?v=TSwBsw6MgiA
Gapps apk
fex-net/934605209940/246920922 - 4pda
lucky patcher.apk install -- delete all google applications
1-GoogleBackupTransport.apk install and Give all permissions in menu applications
2-GoogleLoginService.apk install and Give all permissions in menu applications
3-GoogleServicesFramework.apk install and Give all permissions in menu applications
4-Phonesky.apk install and Give all permissions in menu applications
5-PrebuiltGmsCore.apk install and Give all permissions in menu applications
İ LOVE TURKEY

Monster 00 said:
As you all know we have been searching for ways to root the Le Pro 3AI but failed. There are even 2 twrp but you can't really do much with them. TWRP 3.1 did not even start for me but 3.0.3 worked but what's the real problem? You can't mount /data and also i found another partition named /custom. It always fails to mount and there is no way to format it.
When you enter TWRP it ask for a password to decrypt. Simply click cancel and go to wipe, advanced wipe and check the data partition. Select repair file system and change it to ext2 and then back to ext4. Reboot to twrp again I don't think this is necessary but better take precautions. Now go to mount and select data you will see that you can actually mount it(~24000mb) .
You can also enable MTP to copy files to your phone in recovery such as .zips. I hope this helps you in way. I hope the devs find a way to make it possible to flash custom ROMs for this phone without any message appearing during boot and that there is no problem with imei. Thanks for reading and don't give up with this phone else it will be money down the drain. If I helped press the thanks button.
Click to expand...
Click to collapse
can you help me enable multi window?
It says that I need to mount system first at the recovery.
Please help me. Thanks a lot.

[Samsung S8+] Unable to bypass FRP

I would like to install TWRP and after that Lineage OS on my Samsung S8+ (Exynos). So i tried flashing TWRP with Odin (Dream2lte version 3.3.1.0). But i ran into a FRP lock so i googled and try to solve this, but so far i am unable to.
I have the password to my Google account, so i removed the Google account from the phone and removed the phone from my Google account. After factory reset i am still getting an error FRP lock when flashing.
Shouldn't the FRP lock be gone after removing google account and doing a factory reset? I have tried a couple of YT Howto's but they don't seem to work.
How do i remove the FRP lock so that i am able to install TWRP and Lineage OS?
Like i said i know the password to my Google account and i 100% own the phone
(Bypass probably isn't the correct word, i am simply trying to turn it off )

Got exactly the same problem, hence like you, ended up here for help.

Well i fixed my problem (Disable USB debug and OEM unlock, couple of reboots and enabled them and it worked). But after that i broke my phone
I am stuck at the screen saying: An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.
I know this is meant to scare me (is kinda working...), but i also know that Odin is still working. So as far as i know i have to flash the original firmware now to fix this. But i keep getting the error: Invalid magic string. When i try to also flash a BL file i get the error: ""Secure CHECK FAIL: (BOOTLOADER)" The option Re-Partition in Odin is switched OFF, as far as i know this is okee... right?
I have tried 3 different versions (Android 9/8/7):
https://www.sammobile.com/samsung/galaxy-s8/firmware/SM-G950F/TNL/download/G950FXXU1AQC9/128974/
https://www.sammobile.com/samsung/galaxy-s8/firmware/SM-G950F/TNL/download/G950FXXU4DSBA/259612/
https://www.sammobile.com/samsung/galaxy-s8/firmware/SM-G950F/TNL/download/G950FXXS4CSA4/256485/
This zip files contain a BL/AP/CP/CSC file, i have tried them all at the same time in Odin as well as the AP and BL files seperate. (from one zip file, NOT different version files together of course)
I tried using Smart Switch 4.1 to do the emergency procedure using model nummer SM-G955F with my serial number but before it does anything it tells me this is not possible with an SM-G955F.
They all give me the same result.
Does anybody know how to fix this?

TheGeneral said:
Well i fixed my problem (Disable USB debug and OEM unlock, couple of reboots and enabled them and it worked). But after that i broke my phone
I am stuck at the screen saying: An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.
I know this is meant to scare me (is kinda working...), but i also know that Odin is still working. So as far as i know i have to flash the original firmware now to fix this. But i keep getting the error: Invalid magic string. When i try to also flash a BL file i get the error: ""Secure CHECK FAIL: (BOOTLOADER)" The option Re-Partition in Odin is switched OFF, as far as i know this is okee... right?
I have tried 3 different versions (Android 9/8/7):
https://www.sammobile.com/samsung/galaxy-s8/firmware/SM-G950F/TNL/download/G950FXXU1AQC9/128974/
https://www.sammobile.com/samsung/galaxy-s8/firmware/SM-G950F/TNL/download/G950FXXU4DSBA/259612/
https://www.sammobile.com/samsung/galaxy-s8/firmware/SM-G950F/TNL/download/G950FXXS4CSA4/256485/
This zip files contain a BL/AP/CP/CSC file, i have tried them all at the same time in Odin as well as the AP and BL files seperate. (from one zip file, NOT different version files together of course)
I tried using Smart Switch 4.1 to do the emergency procedure using model nummer SM-G955F with my serial number but before it does anything it tells me this is not possible with an SM-G955F.
They all give me the same result.
Does anybody know how to fix this?
Click to expand...
Click to collapse
Secure check fail on bootloader is your flashing a older firmware than on the device. Look at the builds 5th from last digit. You need to flash that equal or greater than.
The error screen you see for emergency recovery is ok. It's like a modified version of download mode. Kind of. You can still flash Odin files from said screen. Ii see you've flashed a bit 1. And two bit 4 firmwares. So you must be on a 5 or greater. I don't know the exy bit number but like snapdragon is at or near 7 or 8. I can explain better if you need. But not an exynos expert

TheMadScientist said:
Secure check fail on bootloader is your flashing a older firmware than on the device. Look at the builds 5th from last digit. You need to flash that equal or greater than.
The error screen you see for emergency recovery is ok. It's like a modified version of download mode. Kind of. You can still flash Odin files from said screen. Ii see you've flashed a bit 1. And two bit 4 firmwares. So you must be on a 5 or greater. I don't know the exy bit number but like snapdragon is at or near 7 or 8. I can explain better if you need. But not an exynos expert
Click to expand...
Click to collapse
Thanks for your reply! I am in the normal "Downloading...." screen is there anywhere i can check which number i am at?
But i have just tried this one: G950FXXS7DTA6_G950FOXM7DTA6_PHN and it is not working. But this is the newest one available on sammobile. Still the same bootloader error.
I have tried TWRP 3.3.1.0 and that worked, now i am in the TWRP menu but i don't have the LineageOS 17 + GoApps copied to the root. So i cannot install LineageOS now. What do i do now? My computer sees a SM-G955F but it is not showing any storage, if i can fix this i could copy the LineageOS files to the root...right?

TheGeneral said:
Thanks for your reply! I am in the normal "Downloading...." screen is there anywhere i can check which number i am at?
But i have just tried this one: G950FXXS7DTA6_G950FOXM7DTA6_PHN and it is not working. But this is the newest one available on sammobile. Still the same bootloader error.
I have tried TWRP 3.3.1.0 and that worked, now i am in the TWRP menu but i don't have the LineageOS 17 + GoApps copied to the root. So i cannot install LineageOS now. What do i do now? My computer sees a SM-G955F but it is not showing any storage, if i can fix this i could copy the LineageOS files to the root...right?
Click to expand...
Click to collapse
1. If you are on an S8+ flashing firmware for the S8 will cause you issues. Download firmware for the S8+ only. ie: 955f not 950f.
2. If you can't get into the system but can get into download mode there should be a line saying
AP SWREV: B:? K:? S:?
The B:? Is your bootloader version number. You will need to flash the same or higher.
3. How did you install TWRP?
If you don't have an SD card to store files on then after the Format Data stage you can then copy files from pc to phones internal storage.

spawnlives said:
1. If you are on an S8+ flashing firmware for the S8 will cause you issues. Download firmware for the S8+ only. ie: 955f not 950f.
2. If you can't get into the system but can get into download mode there should be a line saying
AP SWREV: B:? K:? S:?
The B:? Is your bootloader version number. You will need to flash the same or higher.
3. How did you install TWTP?
If you don't have an SD card to store files on then after the Format Data stage you can then copy files from pc to phones internal storage.
Click to expand...
Click to collapse
I am a bit embarrassed, it looks like i have been trying to flash the wrong ROMs last night 950 instead of 955, i am downloading the correct files now and wil try again. Sorry for this dumb mistake!
Just to be sure, i am trying to do this:
https://www.getdroidtips.com/lineage-os-17-samsung-galaxy-s8/
(I do know that this site says S8, but i picked the right files this time and thought the process would be the same)
But i first Flash TWRP with Odin, otherwise i cannot reach the TWRP recovery menu right?
But when i look bullet 5 (not number 5) it looks like i need to flash TWRP from within the TWRP menu. But that is not correct right?
I have placed these zip files on the phone:
lineage-17.1-20200211-UNOFFICIAL-dreamlte.zip
open_gapps-arm64-10.0-pico-20200303.zip
As a zip and unpacked, but when i am in the TWRP menu and i go to install, i cannot find the zip files. I placed them in the highest folder level possible. Why can't i find them now?

TheGeneral said:
I am a bit embarrassed, it looks like i have been trying to flash the wrong ROMs last night 950 instead of 955, i am downloading the correct files now and wil try again. Sorry for this dumb mistake!
Just to be sure, i am trying to do this:
https://www.getdroidtips.com/lineage-os-17-samsung-galaxy-s8/
(I do know that this site says S8, but i picked the right files this time and thought the process would be the same)
But i first Flash TWRP with Odin, otherwise i cannot reach the TWRP recovery menu right?
But when i look bullet 5 (not number 5) it looks like i need to flash TWRP from within the TWRP menu. But that is not correct right?
I have placed these zip files on the phone:
lineage-17.1-20200211-UNOFFICIAL-dreamlte.zip
open_gapps-arm64-10.0-pico-20200303.zip
As a zip and unpacked, but when i am in the TWRP menu and i go to install, i cannot find the zip files. I placed them in the highest folder level possible. Why can't i find them now?
Click to expand...
Click to collapse
I don't use custom roms yet.
Try searching for you device S8+ for installation instructions. Had a quick look the firmware is for S8 only not S8+. Need dream2lit for S8+
Try in separate stages instead of all at once.
I would sort out your stock firmware first get it up and running.
Then install TWRP. Install for S8+ from
http://twrp.me/Devices/Samsung/
They are many guides for this
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
If you need rmm bypass zip
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Get that up and running properly.
Then you can install custom roms,root etc.
In regards to transferring files to phone they need to be a zip file ( .zip ) or an image ( .img ) files to flash in TWRP.
Maybe select internal storage then from menu select sdcard folder check if file is there.

spawnlives said:
I don't use custom roms yet.
Try searching for you device S8+ for installation instructions. Had a quick look the firmware is for S8 only not S8+. Need dream2lit for S8+
Try in separate stages instead of all at once.
I would sort out your stock firmware first get it up and running.
Then install TWRP. Install for S8+ from
http://twrp.me/Devices/Samsung/
They are many guides for this
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
If you need rmm bypass zip
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Get that up and running properly.
Then you can install custom roms,root etc.
In regards to transferring files to phone they need to be a zip file ( .zip ) or an image ( .img ) files to flash in TWRP.
Maybe select internal storage then from menu select sdcard folder check if file is there.
Click to expand...
Click to collapse
I am using dream2lit.
I have the correct factory stock ROM (now), so i can always go back now. But i agree, my preparation wasn't good enough.
I will look at the links, but for now like i said my problem is that i cannot see my files in TWRP. But maybe that will be addressed in one of your links
With regards to your first link, i used the "Odin Method" so as far as i can tell i did this the right way(https://twrp.me/samsung/samsunggalaxys8plus.html):
Odin Install Method (No Root Required):
You will need to download and install Odin on your PC. Once you have Odin installed, download the proper .tar file for your device from the download link above. Power off your device. Turn on your device using the proper key combo to get into download mode and attach the device to your computer via a USB cable. Use the PDA tab or button to browse to and select the tar file that you downloaded and flash the device.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.

TheGeneral said:
I am using dream2lit.
I have the correct factory stock ROM (now), so i can always go back now. But i agree, my preparation wasn't good enough.
I will look at the links, but for now like i said my problem is that i cannot see my files in TWRP. But maybe that will be addressed in one of your links
With regards to your first link, i used the "Odin Method" so as far as i can tell i did this the right way(https://twrp.me/samsung/samsunggalaxys8plus.html):
Odin Install Method (No Root Required):
You will need to download and install Odin on your PC. Once you have Odin installed, download the proper .tar file for your device from the download link above. Power off your device. Turn on your device using the proper key combo to get into download mode and attach the device to your computer via a USB cable. Use the PDA tab or button to browse to and select the tar file that you downloaded and flash the device.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Note: Samsung don't have fastboot commands. Have to use button configurations to enter recovery or download modes.
What stage are you at?
It will give me a better idea to be able to help more.

spawnlives said:
Note: Samsung don't have fastboot commands. Have to use button configurations to enter recovery or download modes.
What stage are you at?
It will give me a better idea to be able to help more.
Click to expand...
Click to collapse
Well i installed Lineage OS 17.1 and Open Apps (lineage-17.1-20200211-UNOFFICIAL-dream2lte and open_gapps-arm64-10.0-pico-20200303) with an OTG plug and an USB stick. After installing i removed the USB Stick. But now i am having a new problem...
When the phone boots it asks: "To start Android, enter your password"
Which password is this? When i enter a password i often use it works but then:
"Decryption unsuccessful
The password you entered is correct, but unfortunately your data is corrupt. (Which is no problem)
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account.
(Button) Erase ALL DATA"
Of course i erase the data. Look at the attachment to see what happens then.
I will not give up, will get Lineage OS on this phone, and after that on my Tablet S2 and maybe even on my primairy phone (S10+)
What should i do now? Many thanks for all the help so far, and for help finishing this proces

TheGeneral said:
Well i installed Lineage OS 17.1 and Open Apps (lineage-17.1-20200211-UNOFFICIAL-dream2lte and open_gapps-arm64-10.0-pico-20200303) with an OTG plug and an USB stick. After installing i removed the USB Stick. But now i am having a new problem...
When the phone boots it asks: "To start Android, enter your password"
Which password is this? When i enter a password i often use it works but then:
"Decryption unsuccessful
The password you entered is correct, but unfortunately your data is corrupt. (Which is no problem)
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account.
(Button) Erase ALL DATA"
Of course i erase the data. Look at the attachment to see what happens then.
I will not give up, will get Lineage OS on this phone, and after that on my Tablet S2 and maybe even on my primairy phone (S10+)
What should i do now? Many thanks for all the help so far, and for help finishing this proces
Click to expand...
Click to collapse
Mounting data errors in twrp generally ( but not always ) means your device is encrypted/re-encrypted when booting into system. Twrp has issues with encrypted devices.
What version twrp are you using?
Have you flashed the no-verity-opt-encypt zip in twrp. This zip file will prevent device from re-encrypting when booting phone back into the system ( after the Format Data stage / reboot back into twrp)
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
What is your process of installing twrp?
If you have any passwords etc. installed delete them until after setting up you phone.

spawnlives said:
Mounting data errors in twrp generally ( but not always ) means your device is encrypted/re-encrypted when booting into system. Twrp has issues with encrypted devices.
What version twrp are you using?
Have you flashed the no-verity-opt-encypt zip in twrp. This zip file will prevent device from re-encrypting when booting phone back into the system ( after the Format Data stage / reboot back into twrp)
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
What is your process of installing twrp?
If you have any passwords etc. installed delete them until after setting up you phone.
Click to expand...
Click to collapse
I am using version twrp-3.3.1-1-dream2lte and no i have not flashed that no-verity-opt-encypt zip. I assume i should flash this one the same way flash the Lineage ROM right?
No passwords used on the phone.
My process:
i put the phone in download mode (POWER+BIXBY+VOL DOWN)
I use ODIN to flash twrp-3.3.1-1-dream2lte, and when the phone reboot i press POWER+BIXBY+VOL UP to enter TWRP menu,
Then i go to WIPE and Advanced Wipe and i select the data, system and davlik cache. Then swipe to wipe it.
Then i go to INSTALL and flash lineage-17.1-20200211-UNOFFICIAL-dream2lte and open_gapps-arm64-10.0-pico-20200303

TheGeneral said:
I am using version twrp-3.3.1-1-dream2lte and no i have not flashed that no-verity-opt-encypt zip. I assume i should flash this one the same way flash the Lineage ROM right?
No passwords used on the phone.
My process:
i put the phone in download mode (POWER+BIXBY+VOL DOWN)
I use ODIN to flash twrp-3.3.1-1-dream2lte, and when the phone reboot i press POWER+BIXBY+VOL UP to enter TWRP menu,
Then i go to WIPE and Advanced Wipe and i select the data, system and davlik cache. Then swipe to wipe it.
Then i go to INSTALL and flash lineage-17.1-20200211-UNOFFICIAL-dream2lte and open_gapps-arm64-10.0-pico-20200303
Click to expand...
Click to collapse
To install TWRP
1. Flash twrp with odin - reboot straight into twrp
2. In wipe menu select Format Data ( bottom right )
Type yes to format
3. Reboot back into twrp ( use twrp menu )
4. Flash no-verity-opt zip and if needed rmm bypass zip ( using install button in twrp ).
5. Reboot back into twrp then reboot to system using twrp menu.
6. From system reboot back into twrp.
To check if device is un-encrypted use backup menu - check data storage size ( If reading 0mb then device is still encrypted ).
Note: If all ok I would do a complete twrp backup at this stage ( keep backup on a separate storage device ).
Then you can install custom Rom's as per the installation guide of that Rom.

spawnlives said:
To install TWRP
1. Flash twrp with odin - reboot straight into twrp
2. In wipe menu select Format Data ( bottom right )
Type yes to format
3. Reboot back into twrp ( use twrp menu )
4. Flash no-verity-opt zip and if needed rmm bypass zip ( using install button in twrp ).
5. Reboot back into twrp then reboot to system using twrp menu.
6. From system reboot back into twrp.
To check if device is un-encrypted use backup menu - check data storage size ( If reading 0mb then device is still encrypted ).
Note: If all ok I would do a complete twrp backup at this stage ( keep backup on a separate storage device ).
Then you can install custom Rom's as per the installation guide of that Rom.
Click to expand...
Click to collapse
how do i make a complete TWRP backup? and what is rmm bypass and how do i know if it is neccessary to install this zip file?

TheGeneral said:
how do i make a complete TWRP backup? and what is rmm bypass and how do i know if it is neccessary to install this zip file?
Click to expand...
Click to collapse
In twrp main menu
Select backup menu - select ( all ) partitions - select storage location ( bottom left of screen ) - then swipe to backup.
Note:
1. If backing up to internal storage copy/move backup to an external storage ie: PC, sd card.etc.
2. Since you want a custom rom backup of the EFS partition is important.
Rmm state can be found in download mode. It will have a line ( near the top ) saying RMM state. It will either say prenormal or normal /disappeared.
It won't hurt to flash it just in case.
See OP in the thread I sent before:
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535

spawnlives said:
To install TWRP
1. Flash twrp with odin - reboot straight into twrp
2. In wipe menu select Format Data ( bottom right )
Type yes to format
3. Reboot back into twrp ( use twrp menu )
4. Flash no-verity-opt zip and if needed rmm bypass zip ( using install button in twrp ).
5. Reboot back into twrp then reboot to system using twrp menu.
6. From system reboot back into twrp.
To check if device is un-encrypted use backup menu - check data storage size ( If reading 0mb then device is still encrypted ).
Note: If all ok I would do a complete twrp backup at this stage ( keep backup on a separate storage device ).
Then you can install custom Rom's as per the installation guide of that Rom.
Click to expand...
Click to collapse
I am really trying to do what you are saying...but when i try to "Format Data" (Step 2) it shows an error "Failed to mount '/preload' (Invalid argument). When i try to install no-verity-opt zip (step 4) at the end it shows the same error "Failed to mount '/preload' (Invalid argument). Which is probably because format data failed?
I am installing the zip from an USB stick with an USB-C to USB-A Converter. I don't think that could be the problem?
As Expected the "Data (excl. storage) is still showing 0MB.

TheGeneral said:
I am really trying to do what you are saying...but when i try to "Format Data" (Step 2) it shows an error "Failed to mount '/preload' (Invalid argument). When i try to install no-verity-opt zip (step 4) at the end it shows the same error "Failed to mount '/preload' (Invalid argument). Which is probably because format data failed?
I am installing the zip from an USB stick with an USB-C to USB-A Converter. I don't think that could be the problem?
As Expected the "Data (excl. storage) is still showing 0MB.
Click to expand...
Click to collapse
Failed to mount preload seems to affect some users.
You could try after the format data and reboot back into twrp ( using twrp 3.3.1.1 ):
Select wipe menu
Select advanced wipe
Select Preload
Swipe to wipe
Reboot back into twrp
Then try flashing no-verity/rmm zips files - reboot back into twrp.
Normally, for me , after this stage If i still get 0mb I will reboot into the Android system and then back into twrp. Then check in backup menu storage. If ok then try to flash custom rom.

spawnlives said:
Failed to mount preload seems to affect some users.
You could try after the format data and reboot back into twrp ( using twrp 3.3.1.1 ):
Select wipe menu
Select advanced wipe
Select Preload
Swipe to wipe
Reboot back into twrp
Then try flashing no-verity/rmm zips files - reboot back into twrp.
Normally, for me , after this stage If i still get 0mb I will reboot into the Android system and then back into twrp. Then check in backup menu storage. If ok then try to flash custom rom.
Click to expand...
Click to collapse
Yes Yes!! After doing the Preload i am able to flash no-verity/rmm zips file.
But Data is still showing 0MB.....
I thought why not give the lineage OS rom flashing another try. That worked, but now the phone seems to hang on a Lineage OS logo with a small circle moving around not straight line.
So i wiped everything again and flashed no-verity/rmm zip file, and will wait what for some advice and what do to next.

TheGeneral said:
Yes Yes!! After doing the Preload i am able to flash no-verity/rmm zips file.
But Data is still showing 0MB.....
I thought why not give the lineage OS rom flashing another try. That worked, but now the phone seems to hang on a Lineage OS logo with a small circle moving around not straight line.
So i wiped everything again and flashed no-verity/rmm zip file, and will wait what for some advice and what do to next.
Click to expand...
Click to collapse
Have you tried to reboot into system through twrp ie: reboot menu - system. Let it start normally, reboot into twrp, then check storage size. ( This is after the flashing of the no-verity/rmm zip and rebooting back into twrp ).
As I said I' m not familiar with custom ROMs. I do know that some custom ROMs do take some time to boot up on installation.
But out of curiosity I have a spare S8 and will give it a go.

Problems after Magisk update - can only enter download mode and recovery

Hey there,
I am currently struggeling with my Samsung Galaxy S7 (Exynos) device, running on superman rom (Android 8).
What happened?
For root I´m using Magisk Manager and for banking apps I have Magisk hide running. Then the program told me that there is an update (Magisk App) available. So, as always and recommended, I choosed "Direct Install" but that failed for some reason. OK I thought´, no problem. Later I wanted to reboot my phone but it didn´t. The screen says "Downloading.... Do not turn off device!". I only can enter "Download Mode" and "Recovery Mode via TWRP".
What I tried so far:
1) Wipe cache/dalvik --> not successful
2) Tried to do a factory reset via twrp --> not successful
3) Tried to flash BL via Odin --> not successful
At this time I realised that the same problem occured to my Galaxy Tablet SM-T580. So I came to the point that I did something wrong with updating magisk on both devides.
What I also tried next:
4) Tried to delete magisk modules via twrp --> not successful
5) Tried to uninstall magisk through twrp by downloading the latest Magisk app and rename it to "uninstall.zip" as recommended in installation guide --> Not successful because of Error installing zip file: Unsupported /Unknown image format (unpacking image format)
What can I do next?
Can anyone please help me, since I have two bricked devices now????

A simple kernel flashing would fix the problem, extract the original boot.img of your current ROM, and flash it via TWRP.
Cause it is clearly a problem with your boot.img, if that didn't work (I'm sure it will), then just dirty flash your current ROM.
P.S. If you are encrypted, you might encounter an error doing a simple factory reset, you'll have to format the whole data partition.

Hi @Mohamedkam000,
many thanks for your help. After hours of browsing the web and trying various methods I was able to get my 2nd device (Samsung Galaxy Tab A from 2016) back to life.
What I did: I installed the latest samsung mobile phone drivers on my PC then I connected the tablet to it. I was able to access the internal memory and in the folder "data" Magisk put a backup of the original boot.img. So I installed this "boot.img" via TWRP and voila.......everything works fine again
I´m very happy now.
But unfortunately this method didn´t work with my Samsung Galaxy S7. I just couldn´t find any boot.img file on the phone.
Mohamedkam000 said:
A simple kernel flashing would fix the problem, extract the original boot.img of your current ROM, and flash it via TWRP.
Cause it is clearly a problem with your boot.img, if that didn't work (I'm sure it will), then just dirty flash your current ROM.
Click to expand...
Click to collapse
How do I have to do this? Sorry I´m a little unexperienced so could I get a kind of an step by step guide please?
Mohamedkam000 said:
P.S. If you are encrypted, you might encounter an error doing a simple factory reset, you'll have to format the whole data partition.
Click to expand...
Click to collapse
Don´t understand this. Could you please explain again?
Thank you so much already.
Kind regards,
cap.

capitarider said:
Hi @Mohamedkam000,
many thanks for your help. After hours of browsing the web and trying various methods I was able to get my 2nd device (Samsung Galaxy Tab A from 2016) back to life.
What I did: I installed the latest samsung mobile phone drivers on my PC then I connected the tablet to it. I was able to access the internal memory and in the folder "data" Magisk put a backup of the original boot.img. So I installed this "boot.img" via TWRP and voila.......everything works fine again
I´m very happy now.
But unfortunately this method didn´t work with my Samsung Galaxy S7. I just couldn´t find any boot.img file on the phone.
How do I have to do this? Sorry I´m a little unexperienced so could I get a kind of an step by step guide please?
Don´t understand this. Could you please explain again?
Thank you so much already.
Kind regards,
cap.
Click to expand...
Click to collapse
Glad your tablet revived again.
Magisk creates a backup of the boot.img found just before flashing magisk, it is compressed in gzip format, so you need to pull it, extract it, and push it back to the phone, then flash it.
The file is usually in /data/stock_boot_${SHA1}.img.gz
You can extract it using the built-in terminal of TWRP, if PC is not accessible at the moment by writing and executing the following command:
gunzip {stock-boot-name}.gz
Replace {stock-boot-name} with your backed-up boot name (without the curleybrackets), or you can use the following command:
gunzip *.gz
That'll extract the gzip archive, and the boot.img will be in /data of which you can navigate to it and flash it.
There's another guaranteed method, if you have the file of the ROM you're using right now, you can just open it (it's just a zip archive) and search for the boot.img of your specific phone model and flash it.
Another guaranteed method will be by flashing a custom kernel compatible with your current ROM, like Moro AiO kernel, of which has a wide support for ROMs starting from Oreo, and up to Q, AOSP, or stock-based, just in one file.
Moro's thread: Moro Kernel

you can't access kernel backup because TWRP does not support encryption and Magisk Manager might removed encryption in boot

aIecxs said:
you can't access kernel backup because TWRP does not support encryption and Magisk Manager might removed encryption in boot
Click to expand...
Click to collapse
Doesn't seem like he's encrypted, he found the boot backup of his tablet in /data so he has probably searched for a similar file on his S7, but since it is compressed, he won't find it solely.
Also he would've told us that his /data is empty or something.

start from scratch with older magisk, current 22 has bug
https://github.com/topjohnwu/Magisk/issues/4008

Thank you for your help.
I had a n old twrp backup on another external hard drive. I extracted the boot file and repached it with 7zip to boot.img and flashed through twrp. That also didn´t work for various times. TWRP always said "failed".
In the end I didn´t manage it to bring my phone back to live. Anyway, I decided to flash the latest LineageOS (Android 11) and now its running smooth again.
Thanks again.

Try using sp flash tools flashing the boot.img