Related
Hi,
I been searching for a way to encrypt the data partition with magisk and i didn't succeded at all. No matter if flash magisk in an already encrypted system (it says "using cache walkaround" but it gets stuck in the glowing samsung boot logo) or if i try to encrypt the terminal after having a magisk working system. I even tried to mark in magisk "Keep Forced Encryption" in MagiskManager with no success. It makes the system hang again in the boot secuence after reflashing magisk and rebooting.
I just want root in the stock firmware to be able to debloat and use titanium and a couple of apps.
Any way to have encrypted data and root in nougat?
Yes.
There are two requirements to support rooted stock firmware and encryption:
- You MUST use the stock kernel binary. Custom kernel binaries are blocked by TIMA, which handles encryption.
- You need to change "ro.config.tima" in the system build.prop to 0. This doesn't entirely disable TIMA, but seems to relax the encryption requirements a bit(less salting?) which will allow a modified ramdisk to work properly. It's slightly less secure, but still more secure than going unencrypted
Notes: You will need to wipe /data initially after making the build.prop change. You'll need to disable dm-verity after modifying /system. If you installed a custom kernel before you should reflash the entire firmware as the kernel installer likely deleted the TIMA trustlet binary. Some success was had before with getting custom kernels past TIMA by killing the TIMA service soon after boot, but this had the tendency to brick the data partition. Perhaps in future...
Edit: attached a flashable zip to make the build.prop change from TWRP
CurtisMJ said:
Yes.
There are two requirements to support rooted stock firmware and encryption:
- You MUST use the stock kernel binary. Custom kernel binaries are blocked by TIMA, which handles encryption.
- You need to change "ro.config.tima" in the system build.prop to 0. This doesn't entirely disable TIMA, but seems to relax the encryption requirements a bit(less salting?) which will allow a modified ramdisk to work properly. It's slightly less secure, but still more secure than going unencrypted
Notes: You will need to wipe /data initially after making the build.prop change. You'll need to disable dm-verity after modifying /system. If you installed a custom kernel before you should reflash the entire firmware as the kernel installer likely deleted the TIMA trustlet binary. Some success was had before with getting custom kernels past TIMA by killing the TIMA service soon after boot, but this had the tendency to brick the data partition. Perhaps in future...
Edit: attached a flashable zip to make the build.prop change from TWRP
Click to expand...
Click to collapse
Hey , thanks a lot for the info and the file . I learned more from it than 2 days on the internet struggling with this "issue"!
Actually I already tried another way and it worked!
I'll try to explain for the record.
I just installed TWRM and formated /data (not wiping. cause you have to write a file there afterwards) and from there I opened the terminal of TWRM and created /data/.magisk (as in magisk FAQ is explained) with KEEPFORCEENCRYPT=true in it . Then installed a rom (ambasadii's one with magisk 13.6 root ) and... that's it. it worked.
Afterwards i did a lot of automatic tasks of secure network daily backups since when you're encrypted it's kind of easy to f^ckup the system and lose everything and now I'm happy.
Probably i was lucky since the kernel probably is the stock one as you said in this ROM.
I still have to try more stuff to be sure everything is working and the data is safe (safe enough at least)
one question:
do you think it would work if i activate dm-verity or this firmware and or magisk modify the ramdisk (so it wont.) ?
forocarlos said:
Probably i was lucky since the kernel probably is the stock one as you said in this ROM.
I still have to try more stuff to be sure everything is working and the data is safe (safe enough at least)
one question:
do you think it would work if i activate dm-verity or this firmware and or magisk modify the ramdisk (so it wont.) ?
Click to expand...
Click to collapse
dm-verity likely won't work on a custom ROM(unless the ROM maker specifically re-signed it, but that's unlikely and bloody difficult). Making any changes to /system (including the build.prop tweak I mentioned!) will necessitate disabling it and there are a bunch of changes in custom Roms. Ambasadii's nougat ROM does indeed make use of the stock kernel and most likely has the TIMA prop already toggled. So an ideal setup I think. The data should be pretty solid provided the TIMA trustlet never goes missing(encryption keys basically self-destruct, which bricks the partition )
EDIT: You also might want to check in TWRP if the data was genuinely encrypted. Android generally won't complain if it isn't. If TWRP can mount it it isn't encrypted.
EDIT: You also might want to check in TWRP if the data was genuinely encrypted. Android generally won't complain if it isn't. If TWRP can mount it it isn't encrypted.
Click to expand...
Click to collapse
checked.
/data unmountable.
So wrapping things up:
- Magisk root
- CTC passed
- Encryption
- Custom Rom
- Lastest Nougat
:good::good::good::good::good:
the only thing left is figuring out how to update the rom without losing data or everything actually.
forocarlos said:
checked.
/data unmountable.
So wrapping things up:
- Magisk root
- CTC passed
- Encryption
- Custom Rom
- Lastest Nougat
:good::good::good::good::good:
the only thing left is figuring out how to update the rom without losing data or everything actually.
Click to expand...
Click to collapse
Hey, have you figured out a way of updating without losing data?
charliebigpot said:
Hey, have you figured out a way of updating without losing data?
Click to expand...
Click to collapse
Little late sorry, but if you keep the TIMA prop disabled you can flash the full firmware with HOME_CSC and it will keep the data. Just reflash twrp after it does the update(needs full reboot into stock recovery first to finish update) and flash the TIMA zip in this thread with a root zip.
Step-by-Step-Guide to a S7 with Nougat+Root+Magisk+Encryption
Hi there,
I am glad that there is a way to use Nougat, Root and Magisk on an encrypted S7. For the last months I have tried every so-called-solution (TWRP, CF-AutoRoot, reflash Stock boot.img, Helios' Stock kernel) but always ended up in bootloops or an unencrypted device.
Can someone provide me with a step-by-step-guide how to achieve a rooted-magisked-encrypted S7 running Nougat?f I am now running unrooted stock 7.0 with VIA CSC, Build G930FXXU1DQH9.
Thanks in advance!
A step by step for this would be great.
i tried several variations of the proposed methods and did not succeed in any way, please clarify
i tried these variations, and many many more:
flash stock
reboot
flash twrp
wipe system
format data
terminal: KEEPFORCEENCRYPT=true >> /data/.magisk
flash ambassadi rom, dirty flash, magisk root, wipe cache
reboot
set fingerprint & password + fast encrypt
bootloop
format data
wipe sys caches
terminal: KEEPFORCEENCRYPT=true >> /data/.magisk
flash ambassadi rom, clean, magisk root, wipe cache
reboot
set fingerprint & password
reboot
encrypt
bootloop
flash stock
reboot
set fingerprint&pw
reboot
flash twrp
tima
format data
magisk
no-veri opt enc
reboot
set up fingerprint + pw
reboot
encrypt
unsucessful but bootable
The most sucess i had with the stock rom, though i dont remember how exactly. I didnt take my password, which i suspect to be a verification error since the password was the right one
On the batman rom the ui hanged itself on first encrypted startup.
On ambassadi rom i got into bootloop every time.
Did i miss something??
Regarding stock rooted encryption there are some notes, in addition to the requirements in my post above(stock kernel etc):
- Samsung's encryption never handles post setup encryption that well. At least from my experience. You need to be encrypted from the get-go. This implies re-wiping data the moment you're finished flashing the custom ROM as TIMA won't encrypt unless the partition is blank(which it won't be with the leftover magisk config file).
- The TIMA prop must be changed before first boot. Data encrypted with prop in either state is incompatible with data encrypted during the other state. State "1" bootloops on rooting. State "0" allows it.
So for stock the step-by-step would be:
- Flash full stock and use CSC(NOT HOME_CSC), let it reboot to the initial setup screen. This is important to apply the CSC settings from the firmware package, which if not done will result in an unusable secure keyboard and cause various other issues.
- Flash TWRP
- Flash the TIMA prop zip in the post above
- Flash a verity disable zip which DOESN'T disable Force Encryption. For convenience I have attached a modified version which doesn't.
- Format /data
- Reboot into setup and run through the wizard.
- Reboot back to TWRP and flash a root solution like Magisk. Don't worry about force encryption now as the data partition should be encrypted already by this stage. Magisk should revert to the /cache workaround.
To update:
- Flash the latest full stock firmware package but this time use HOME_CSC
- Let it reboot into stock recovery and do the upgrade process.
- It should end up on the secure Startup page asking for your password. No password will work at this point because your data was encrypted in TIMA state "0".
- Reboot to download mode and flash TWRP.
- Reboot to TWRP
- Flash the TIMA prop and verity zips.
- Reboot into to Android (password should work now)
- Let it finish the upgrade.
- Reboot to TWRP and flash your root solution.
These are the basic processes which worked for me.
CurtisMJ said:
Regarding stock rooted encryption there are some notes, in addition to the requirements in my post above(stock kernel etc):
- Samsung's encryption never handles post setup encryption that well. At least from my experience. You need to be encrypted from the get-go. This implies re-wiping data the moment you're finished flashing the custom ROM as TIMA won't encrypt unless the partition is blank(which it won't be with the leftover magisk config file).
- The TIMA prop must be changed before first boot. Data encrypted with prop in either state is incompatible with data encrypted during the other state. State "1" bootloops on rooting. State "0" allows it.
So for stock the step-by-step would be:
- Flash full stock and use CSC(NOT HOME_CSC), let it reboot to the initial setup screen. This is important to apply the CSC settings from the firmware package, which if not done will result in an unusable secure keyboard and cause various other issues.
- Flash TWRP
- Flash the TIMA prop zip in the post above
- Flash a verity disable zip which DOESN'T disable Force Encryption. For convenience I have attached a modified version which doesn't.
- Format /data
- Reboot into setup and run through the wizard.
- Reboot back to TWRP and flash a root solution like Magisk. Don't worry about force encryption now as the data partition should be encrypted already by this stage. Magisk should revert to the /cache workaround.
These are the basic processes which worked for me.
Click to expand...
Click to collapse
when first reboot into TWRP wich option should get? "keep read only" or "allow modifications"?
if I select "allow mods" when I try to flash TIMA.prop file I get an error about mount\data
is it necesary to format data before?
thanks
xbizkuit said:
when first reboot into TWRP wich option should get? "keep read only" or "allow modifications"?
if I select "allow mods" when I try to flash TIMA.prop file I get an error about mount\data
is it necesary to format data before?
thanks
Click to expand...
Click to collapse
Actually the TIMA prop zip doesnt even need data. Not sure why I made it try to mount, but any error about mounting can probably be ignored. It modifies /system so you should swipe to allow.
CurtisMJ said:
Actually the TIMA prop zip doesnt even need data. Not sure why I made it try to mount, but any error about mounting can probably be ignored. It modifies /system so you should swipe to allow.
Click to expand...
Click to collapse
First of all, thanks for your reply and for your small guide
What I did was flash lastest full stock official rom from sammobile with odin and let it reboot to the initial setup screen
Reboot to download mode and then I flashed TWRP also with odin and reboot manually to recovery
When first time entered into recovery just selected "allow modifications"
After I flashed the TIMA prop zip and verity disable zip modified version
In both cases, I received error messages about mount/data on the screen but the installation seems to be complete
Finally format/data, reboot and complete the wizard and the installation
The last step, reboot again into recovery and flash magisk v14
At the end of this procedure, all seems ok, magisk is running, safetynet test is OK, superuser is OK and root apps with no problem
Also a couple of mods flashed with recovery (zero camera mod and sound mod by zubi) gave me error messages about format/data but both of them were done
So, the question is how can I check now if my phone encryption is OK and working ??
The only thing seems not work is the OTA firmware updates, it doesnt work, error message about modified phone
I tried to hide root with magisk for the apps in relation with the ota updates but no work for me
Is there any solution for that??
Thanks for all and very appreciated for your help
And sorry for my english hehe
xbizkuit said:
First of all, thanks for your reply and for your small guide
What I did was flash lastest full stock official rom from sammobile with odin and let it reboot to the initial setup screen
Reboot to download mode and then I flashed TWRP also with odin and reboot manually to recovery
When first time entered into recovery just selected "allow modifications"
After I flashed the TIMA prop zip and verity disable zip modified version
In both cases, I received error messages about mount/data on the screen but the installation seems to be complete
Finally format/data, reboot and complete the wizard and the installation
The last step, reboot again into recovery and flash magisk v14
At the end of this procedure, all seems ok, magisk is running, safetynet test is OK, superuser is OK and root apps with no problem
Also a couple of mods flashed with recovery (zero camera mod and sound mod by zubi) gave me error messages about format/data but both of them were done
So, the question is how can I check now if my phone encryption is OK and working ??
The only thing seems not work is the OTA firmware updates, it doesnt work, error message about modified phone
I tried to hide root with magisk for the apps in relation with the ota updates but no work for me
Is there any solution for that??
Thanks for all and very appreciated for your help
And sorry for my english hehe
Click to expand...
Click to collapse
If the recovery is giving errors about /data mount then the phone is encrypted. TWRP simply cannot work with Samsung encryption at all at the moment. Also: If there is no "Encrypt" option for the internal storage in the Security section of the settings app, then the device is encrypted(There may still be one for the external SD). There's no way I know of to fool OTA into working, I've always just fully flashed the latest firmware. Samsung firmware is really easy to get so I've never really looked into using OTAs to update. They'd probably fail horribly anyway due to the modified system in which case the OTA tool is probably correct to block the update. (Newer Android standard requires updates to be done via raw block writes so dm-verity remains intact. Could lead to corruption if done wrong...)
CurtisMJ said:
If the recovery is giving errors about /data mount then the phone is encrypted. TWRP simply cannot work with Samsung encryption at all at the moment. Also: If there is no "Encrypt" option for the internal storage in the Security section of the settings app, then the device is encrypted(There may still be one for the external SD). There's no way I know of to fool OTA into working, I've always just fully flashed the latest firmware. Samsung firmware is really easy to get so I've never really looked into using OTAs to update. They'd probably fail horribly anyway due to the modified system in which case the OTA tool is probably correct to block the update. (Newer Android standard requires updates to be done via raw block writes so dm-verity remains intact. Could lead to corruption if done wrong...)
Click to expand...
Click to collapse
OK so it seems my phone is finally encrypted and rooted!!!
anyway, I forgot about OTAs and I´ll continue installing updates manually,
so can I flash the full firmware with HOME_CSC without losing the data?
Only reflash TWRP after the update and flash the TIMA prop zip ???
Thank you very much for your help!!!
Thank you CurtisMJ! It finally works!
xbizkuit said:
OK so it seems my phone is finally encrypted and rooted!!!
anyway, I forgot about OTAs and I´ll continue installing updates manually,
so can I flash the full firmware with HOME_CSC without losing the data?
Only reflash TWRP after the update and flash the TIMA prop zip ???
Thank you very much for your help!!!
Click to expand...
Click to collapse
Whoops. Didn't see those were questions. Yes, full flash with HOME_CSC will keep data intact. The TIMA prop will need to be in state "0" to decrypt, so yes again, reflash TWRP and the TIMA and verity zips and you should be good. Just make sure to have "Auto Reboot" checked in Odin. It will do some stuff in stock recovery first (including a screen with "Erasing..." Don't worry! It's just cleaning up the working files in /cache ).
CurtisMJ said:
Whoops. Didn't see those were questions. Yes, full flash with HOME_CSC will keep data intact. The TIMA prop will need to be in state "0" to decrypt, so yes again, reflash TWRP and the TIMA and verity zips and you should be good. Just make sure to have "Auto Reboot" checked in Odin. It will do some stuff in stock recovery first (including a screen with "Erasing..." Don't worry! It's just cleaning up the working files in /cache ).
Click to expand...
Click to collapse
Thanks again mate!!!!!!
WyRM
Hello Guys
Do you think it would work also on Note8 ?
Im stuck on step when i flash 2 files via TWRP, it shows erros with cant mount Data because it is already encrypted somehow, it wouldnt be issue as you said as it does to system.
But when i finish the installation of the Firmware and came back to TWRP for flashing Root solution it is encrypted and cantbe flashed.
Any idea?
WyRmiE said:
Hello Guys
Do you think it would work also on Note8 ?
Im stuck on step when i flash 2 files via TWRP, it shows erros with cant mount Data because it is already encrypted somehow, it wouldnt be issue as you said as it does to system.
But when i finish the installation of the Firmware and came back to TWRP for flashing Root solution it is encrypted and cantbe flashed.
Any idea?
Click to expand...
Click to collapse
That sounds about right actually. The data is supposed to be already encrypted by the time you flash root. TWRP on the S7 and it appears any recent Samsung device cannot decrypt the stock ROMs encryption. The root solution should revert to using the cache workaround. Both Magisk and SuperSU support this setup. Just flash and ignore the /data mount errors.
Recently I just downgraded my Mi Mix 2s to MIUI V9.6.4.0.ODGMIFD via Miflash and planning to stay on this (global) rom. However, after flashing the latest twrp from the official link (v3.1.1-1) it did not ask for the lockscreen password upon entering the interface and my files just showed up with random filenames.
After some reading, I suppose my device is encrypted and twrp did not let me to decrypt it (without asking for lockscreen password). The random filenames still happens even I remove the lockscreen password before flashing twrp meaning the device is still encrypted. Before I could do anything else (flashing zip files, making backups, etc) I must format data to remove the encryption, but twrp will disappear after I booted into system and did the initial phone configuration. Tried different versions (from 3.2.3-0 to 3.3.1-1) but to no avail. The only way I can retain twrp after booting into system is to flash Magisk zip right after formatting data, but if I enter twrp again the filenames are still in random characters as before and I couldn't do anything in it.
So my question is how can I properly install twrp into my device without having the encryption issues? Could it be the rom that caused the problem or did I missed out any steps that fails to disable the encryption? Thanks for your attention.
WannaFly3721 said:
Recently I just downgraded my Mi Mix 2s to MIUI V9.6.4.0.ODGMIFD via Miflash and planning to stay on this (global) rom. However, after flashing the latest twrp from the official link (v3.1.1-1) it did not ask for the lockscreen password upon entering the interface and my files just showed up with random filenames.
After some reading, I suppose my device is encrypted and twrp did not let me to decrypt it (without asking for lockscreen password). The random filenames still happens even I remove the lockscreen password before flashing twrp meaning the device is still encrypted. Before I could do anything else (flashing zip files, making backups, etc) I must format data to remove the encryption, but twrp will disappear after I booted into system and did the initial phone configuration. Tried different versions (from 3.2.3-0 to 3.3.1-1) but to no avail. The only way I can retain twrp after booting into system is to flash Magisk zip right after formatting data, but if I enter twrp again the filenames are still in random characters as before and I couldn't do anything in it.
So my question is how can I properly install twrp into my device without having the encryption issues? Could it be the rom that caused the problem or did I missed out any steps that fails to disable the encryption? Thanks for your attention.
Click to expand...
Click to collapse
Guess I've found a workaround for this by installing the OrangeFox recovery project (ofrp). For those who stuck at the same issue as mine this is what I did:
1. Flash twrp img through adb fastboot.
2. Format data to remove encryption.
3. Paste ofrp zip file into the device and flash it via twrp, which boots the phone into ofrp interface.
4. Paste the recovery zip file into the device and flash it via ofrp. Under setting - MIUI OTA it should show 'enabled' (for android 9 and above might need to uncheck disable dm-verity first according to ofrp page, but my rom is at android 8 so I left it checked as default before flashing).
5. Reboot to system and complete the initial configuration.
6. Reboot to recovery again and ofrp should remain installed. From there I was then able to perform a backup.
Btw, under phone settings it says my device is still encrypted although I can access to ofrp without having the encryption issue as in twrp (random filenames, cannot transfer files or create backups, etc). Anyhow I now have a working custom recovery on the stock rom, cheers.
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.
Need custom recovery for Mobiistar C1 shine 4g mt 6739 device as m stuck need it urgently and want install android 10 gsi image my device has arm32 a only architecture some suggest me some good and lite gsi images please firstly I need custom recovery twrp please someone help.
It would be hard to support a 2018 device I guess.
[CLOSED] I Will build TWRP for your device!
I wanna build twrp for your device! Pls give info about your device! if possible give stock firmware!
forum.xda-developers.com
i can upload recovery.img file for if you want
its Mobiistar C1 shine (MT6739) arm 32bit a only supported device running on 8.1 i was some how able to root it but unable to install custom recovery if u can please build one for this device i will upload stock recovery.img in few minutes presently its bricked but i will recovery it because i have stock firmware and flashing tool of it....so dont worry just please build a custom recovery like twrp for this device asap if possible
Again: You request a TWRP build for your device going to this thread
[CLOSED] I Will build TWRP for your device!
I wanna build twrp for your device! Pls give info about your device! if possible give stock firmware!
forum.xda-developers.com
any custom recovery bro sorry for that (twrp)
my phone back running again i have flashed it with stock firmware recovery images i have attached earlier and so does phone details screenshot now present situation is 8.1 not rooted stock recovery and firmware so i hope if anyone can help i will be glad
installed latest magisk apk and .zip also by patching boot.img file and flashing that with sp tool to install magisk and got root privilege's
all now i want is proper running and fully functional custom recovery to install custom roms and mods
copvaibhav said:
its Mobiistar C1 shine (MT6739) arm 32bit a only supported device running on 8.1 i was some how able to root it but unable to install custom recovery if u can please build one for this device i will upload stock recovery.img in few minutes presently its bricked but i will recovery it because i have stock firmware and flashing tool of it....so dont worry just please build a custom recovery like twrp for this device asap if possible
Click to expand...
Click to collapse
I am not responsible for any wrongdoing by you. Always have ROM stock files. Any error, install stock recovery again.
First you need to unlock the bootloader if necessary! Unzip file attached and look 2 files.
Then, the installation plan:
0) Flash the TWRP with SPFT or fastboot;
1) Enter TWRP IMMEDIATELY without starting in the system, otherwise TWRP can revert to the stock;
2) When asked to enter the password, select Cancel;
3) Load the file with Magisk (look for any magisk19.zip for TWRP and the decryption file for EXTERNAL memory;
4) Flash Magisk immediately and then install the file data_decrypt_Mobiistar_C1_Shine.zip immediately;
5) Make FORMAT DATA - bottom left button - Type: YES. Go back to the TWRP menu;
6) Make Wipe: data, cache, dalvik (reset to factory settings! Save your data!);
7) Reboot to TWRP (password must not ask);
8) Restart on the system, root is received.
thanks bro for making recovery.img when installing magisk 19.zip its giving error on last step failed to mount /vendor/persist (invalid argument). done
after that i tried to install your data decrypt .zip after one reboot to recovery because i have tried before without reboot recovery once so this time rebooted and installed your data.zip file and again on the last step same error as magisk failed to mount /vendor/persist (invalid argument). done
after that i tried to format by typing yes but again same error failed to mount /vendor/persist (invalid argument).done
just to inform you i have formatted phone from inside by turning it on factory reset but nothing happened....and internal space is not mounting i some how managed to install these things via OTG USB but same error again and again. i am attaching screenshot also which i captured from other phone of mine.
kindly help asap
copvaibhav said:
thanks bro for making recovery.img when installing magisk 19.zip its giving error on last step failed to mount /vendor/persist (invalid argument). done
after that i tried to install your data decrypt .zip after one reboot to recovery because i have tried before without reboot recovery once so this time rebooted and installed your data.zip file and again on the last step same error as magisk failed to mount /vendor/persist (invalid argument). done
after that i tried to format by typing yes but again same error failed to mount /vendor/persist (invalid argument).done
just to inform you i have formatted phone from inside by turning it on factory reset but nothing happened....and internal space is not mounting i some how managed to install these things via OTG USB but same error again and again. i am attaching screenshot also which i captured from other phone of mine.
kindly help asap
Click to expand...
Click to collapse
This is Ok. I made TWRP fast and not remember if the stock partitions has \vendor\persist. So if has that's message is normal. Therefore messages about \vendor\nvdata;nvram;nvcfg is normal too. Very pacth zip files can delete that and the device cannot have IMEI.
First: Is good know the file TWRP worked;
- - You can't install any zip without FORMAT DATA first because FORMAT DATA process can view internal storage. If you don't FORMAT DATA maybe the zip file going wrong with MicroSD & OTG.
In this moment you understand: not use external storage! Put zip in the internal storage an try again.
About MTP: Has anything wrong wiht A8.1 & TWRP. Most devices with A8.1 and TWRP do not have access to MTP. I don't know what happens because I don't know why TeamWin was unable to resolve this.
Now you need put zip with adb command (search how to do) or use sileload on the TWRP.
PS: the picture attached by you show about decrypt. In the first moment you need acept modifications and password you press CANCEL.
lopestom said:
This is Ok. I made TWRP fast and not remember if the stock partitions has \vendor\persist. So if has that's message is normal. Therefore messages about \vendor\nvdata;nvram;nvcfg is normal too. Very pacth zip files can delete that and the device cannot have IMEI.
First: Is good know the file TWRP worked;
- - You can't install any zip without FORMAT DATA first because FORMAT DATA process can view internal storage. If you don't FORMAT DATA maybe the zip file going wrong with MicroSD & OTG.
In this moment you understand: not use external storage! Put zip in the internal storage an try again.
About MTP: Has anything wrong wiht A8.1 & TWRP. Most devices with A8.1 and TWRP do not have access to MTP. I don't know what happens because I don't know why TeamWin was unable to resolve this.
Now you need put zip with adb command (search how to do) or use sileload on the TWRP.
PS: the picture attached by you show about decrypt. In the first moment you need acept modifications and password you press CANCEL.
Click to expand...
Click to collapse
sideload is not starting forgot to mention it i have tried that also booted phone normal put the file in internal but in recovery cant have access to internal storage and yes i have press cancel first and that accepted modification but nothing happened no internal storage access only some how otg thats it i dont know what to do
copvaibhav said:
sideload is not starting forgot to mention it i have tried that also booted phone normal put the file in internal but in recovery cant have access to internal storage and yes i have press cancel first and that accepted modification but nothing happened no internal storage access only some how otg thats it i dont know what to do
Click to expand...
Click to collapse
Okay. Wait my free time and I'll create other TWRP for your device.
Reflash stock recovery if you want & test other file soon.
Update
\|/ Lucky file attached today. So install and test. You can install zip that I put before or Donwload acoording your device cpu has. Read instructions about that again.
Reference Download: https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/
thanks bro i dont know how it worked but it worked again i have to use otg but this time it worked by downloading different force disabler.zip after that i have formatted the data by typing yes it worked then again i flashed your disabler and new recovery image and phone booted magisk installed phone rooted.....thanks a ton i dont know how to say thanks you but thank you all .
can please suggest me as my mt 6739 is 32arm a only device some light gsi for my device actually i want custom mods in gsi so if u can suggest me which also supports my device i will be very thankful
copvaibhav said:
thanks bro i dont know how it worked but it worked again i have to use otg but this time it worked by downloading different force disabler.zip after that i have formatted the data by typing yes it worked then again i flashed your disabler and new recovery image and phone booted magisk installed phone rooted.....thanks a ton i dont know how to say thanks you but thank you all .
can please suggest me as my mt 6739 is 32arm a only device some light gsi for my device actually i want custom mods in gsi so if u can suggest me which also supports my device i will be very thankful
Click to expand...
Click to collapse
Look correct app to know about your device: Treble Info
You need try install AOSP 8 & 9: https://github.com/phhusson/treble_experimentations/releases
Look "bugs"; try solving; keep your time with experiments.....
After you can try LOS, RRMix, Havoc, etc.....
About this thread/ask help about Custom Recovery so Solved. @jerryhou85
Good Lucky!
system-arm-aonly-vanilla-nosu.img.xz
system-arm32_binder64-aonly-vanilla-nosu.img.xz
bro which file shpuld i download as i told you mine is 32bit arm a only (what is arm first link and arm32binder64 aonly difference) kindly tell.
just to clarify i have download both removed.xy from ext. and flashed from recovery system image but phone goes into fastboot after reboot and when rebooting in recovery at the top it shows no os installed.
lopestom said:
Okay. Wait my free time and I'll create other TWRP for your device.
Reflash stock recovery if you want & test other file soon.
Update
\|/ Lucky file attached today. So install and test. You can install zip that I put before or Donwload acoording your device cpu has. Read instructions about that again.
Reference Download: https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/
Click to expand...
Click to collapse
Sir it's stuck on password screen touch not working please fix it, I will always be grateful to you.
Honey2012 said:
Sir it's stuck on password screen
Click to expand...
Click to collapse
The first start need choose the CANCEL. I think you not know about TWRP (unofficial) and the process with device/TWRP without encryption/decryption process.
If you want that so send me some device to develop/have the possibility of getting that option.
Honey2012 said:
touch not working please fix it, I will always be grateful to you.
Click to expand...
Click to collapse
As you read, I not have your device in my hands!
Many 32bits and few 64bits devices have problem with touch screen from kernel. That's not my error! It's from device company.
I not know about touch screen work or not since copvaibhav not write about. But I won't fix this. There is also the possibility to use OTG and plug in a USB Mouse to use in TWRP.
There are solutions to fix the touch screen but I don't have the device and I don't have time to do it. Search and you will know. So solve it yourself and thank your self for it.
Ask copvaibhav for more process and using TWRP.
My new Xiaomi Poco X3 Pro is showing an error screen after some time, like in this post:
https://forum.xda-developers.com/t/cant-load-android-system-lineageos.4314035/
It reads "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device"
This happened so far:
I just unlocked the boot loader of my new phone after week of waiting.
I followed the official lineage instructions to install the OS: https://wiki.lineageos.org/devices/vayu/install
Everything worked including the sideloading via db.
I downloaded those two files for the LineageOS-Site:
- Recovery via fastboot: lineage-18.1-20211203-recovery-vayu.img (recovery works, I can still boot into recovery)
- System via adb: lineage-18.1-20211203-nightly-vayu-signed.zip
I also added Gapps via adb: "open_gapps-arm64-11.0-nano-20211204.zip"
Both adb transfers exited successfully.
After the first error screen
- I tapped Try again,
- When the error occurred again, I tapped "Factory data reset," but the error still occurred. The phone is new, no user data is on the phone.
- I booted into recovery and reset all the data I could. When I tap "Format system partition" it throws an error "E: Failed to open /dev/block/dm-0: No such file or directory. System wipe failed."
- Then I repeated the adb sideload. The error occurs again.
- I removed the SIM card, as someone in the forum suggested this could be a problem source. The error still occurs.
What can I do now?
----
Update [2021-12-05 Sun 20:09]
It seems to be a Problem with the GApps Version.
What I did Try so far is:
- Install 03-12-LOS and latest GApps via LOS recovery (didn't work)
- Install 03-12-LOS and latest GApps via TWRP recovery (didn't work)
- install LOS Build from 26-11-2021 without GApps (works)
- Install LOS Build from 26-11-2021 with latest GApps (didn't work)
- Install LOS Build form 26-11-2021 with GApps from 25-11-2021 (works)
Just use TWRP, flash ROM and AFTER flashing ROM Format Data where you have to type "yes". (Format, not Wipe)
Xiaomi Poco X3 Pro
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Thanks for the Idea. At the moment it has not solved the problem.
This is what I did:
- Flash TWRP
Code:
fastboot flash recovery TWRP-3.5.2-vayu-Nebrassy-2.img
- copy lineage-18.1-20211203-nightly-vayu-signed.zip and "open_gapps-arm64-11.0-nano-20211204.zip" to the Poco device
- install via "install" option, wipe cache at the end of installation
- Format files (via "Wipe" -> "Format Data" -> type "yes")
- Reboot
After some time of the animated Lineage OS logo, the phone reboots into TWRP.
To me this seems very similar to the Lineage recovery before.
Any ideas what could be wrong?
You probably wiped System or Vendor partition or something, you are not supposed to do that.
Most likely you have to reflash MIUI now first. Make sure it's atleast version 12.5.X.X.
Flashing instructions are really simple, this apply to all ROM's.
FIRST INSTALL?:
Remove any fingerprint, PIN, or password in MIUI
Unlock the bootloader
Transfer ROM to internal storage
Install any suitable recovery
Flash ROM zip file
Do a data wipe in recovery (format data)
Reboot to the system, wait and enjoy
FLASHING UPDATES?:
Download via OTA Updater and let it automatically install; OR
Download an update, transfer to internal/external storage (always check file sha256)
Flash ROM zip and reboot.
Do not wipe anything else or add any additional steps. (maybe except Gapps if ROM doesn't have them included)
ps.
In first post there is no mention if you did Format Data or not and when you did it. Like i said before - you have to Formata DATA AFTER flashing ROM . Not before.
This happened so far:
I just unlocked the boot loader of my new phone after week of waiting.
I followed the official lineage instructions to install the OS: https://wiki.lineageos.org/devices/vayu/install
Everything worked including the sideloading via db.
I downloaded those two files for the LineageOS-Site:
- Recovery via fastboot: lineage-18.1-20211203-recovery-vayu.img (recovery works, I can still boot into recovery)
- System via adb: lineage-18.1-20211203-nightly-vayu-signed.zip
I also added Gapps via adb: "open_gapps-arm64-11.0-nano-20211204.zip"
Both adb transfers exited successfully.
Click to expand...
Click to collapse
k3lcior said:
In first post there is no mention if you did Format Data or not and when you did it. Like i said before - you have to Formata DATA AFTER flashing ROM . Not before.
Click to expand...
Click to collapse
I followed the LOS Install Guide: https://wiki.lineageos.org/devices/vayu/install But this procedure does not seem to bee the cause (see below).
Download the LineageOS installation package that you would like to install or build the package yourself.
Optionally, download an application package add-on such as Google Apps (use the arm64 architecture).
If you are not in recovery, reboot into recovery:
With the device powered off, hold Volume Up + Power. When Xiaomi/POCO/Redmi splash appears, release Power and keep pressed Volume Up until recovery appears.
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu.
Sideload the LineageOS .zip package:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
Click to expand...
Click to collapse
Okay so this is what I did (the part that works):
- I downloaded the latest possible stock ROM from https://www.xda-developers.com/down...ut-several-xiaomi-redmi-mi-poco-devices/#vayu The fastboot ROM is more than 5GB.
- Extract the file "vayu_eea_global_images_V12.5.3.0.RJUEUXM_20211015.0000.00_11.0_eea_05cc38de43.tgz"
- then connect the phone via USB cable in fastboot mode and:
Bash:
cd ~/Downloads/vayu_eea_global_images_V12.5.3.0.RJUEUXM_20211015.0000.00_11.0_eea
/bin/bash ./flash_all.sh
- The default MIUI starts flawless, as it dit the first time I turned on the phone. So far so good.
What didn't work:
1. I installed the LOS Recovery again and flashed the OS and Gapps. Only after that I did step 3 - formating. The result ist the same bootloop as in the beginning.
2. I flashed the stock MIUI ROM again (which woks fine). Then I flashed TWRP, transfered the OS and GApps file and installed. I did not wipe anything, just used "format data" like above.
In both cases the OS does not start. After a while displaying the LOS-logo the phone reboots to recovery.
What did work:
I downloaded lineage-18.1-20211126-nightly-vayu-signed.zip, one version before the latest verion and the corresponding recovery lineage-18.1-20211126-recovery-vayu.img
I flashed only the OS, and no GApps -- and it launched successfully. Installing with the latest GApps failed again.
Install older gapp, not all gapp is compatible