Please has anyone been able to port TWRP recovery for an a/b partitioned device, I mean devices that contains the recovery ramdisk in the boot.img and doesn't have a separate recovery partition.
Thanks in advance.
Kelexine said:
Please has anyone been able to port TWRP recovery for an a/b partitioned device, I mean devices that contains the recovery ramdisk in the boot.img and doesn't have a separate recovery partition.
Thanks in advance.
Click to expand...
Click to collapse
What do you mean by "port"?
TWRP is supported on multiple A/B devices such as the Google Pixel. However, TWRP does not support the compression necessary to replace the stock recovery in the boot image, so TWRP may only be used "live", where the TWRP image is booted via command, instead of being flashed to /boot.
V0latyle said:
What do you mean by "port"?
TWRP is supported on multiple A/B devices such as the Google Pixel. However, TWRP does not support the compression necessary to replace the stock recovery in the boot image, so TWRP may only be used "live", where the TWRP image is booted via command, instead of being flashed to /boot.
Click to expand...
Click to collapse
By porting I mean changing some files, like copying the kernel and other device specific files to a prebuilt TWRP boot image for a related device.
For example I was able to do that for my android 8 based device and it worked flawlessly, but my problem is that I don't know how to do that for a/b partitioned devices cause my device is not officially supported and i can't seem to find any unofficial version for my device, plus my phone's kernel source and device are not published on GitHub or anywhere.
But some devices specially some Mediatek and Unisoc based devices don't support live boot and so it's necessary two flash it to the boot partition.
Finally built twrp for this device after so many attempts, here is the file for those that owns this device too.
NOTE: This file is for KG5j variant not KG5k or any other variant
Kelexine said:
Finally built twrp for this device after so many attempts, here is the file for those that owns this device too.
Click to expand...
Click to collapse
hello how is the twrp for tecno spark 8c it works fine for me but when I restart the phone it enters a bootloop to the recovery
Jermaine22martinez said:
hello how is the twrp for tecno spark 8c it works fine for me but when I restart the phone it enters a bootloop to the recovery
Click to expand...
Click to collapse
I don't understand, please explain your issues so I can know how to help
Follow this guide https://forum.xda-developers.com/t/...hat-does-not-have-recovery-partition.4572311/
Jermaine22martinez said:
hello how is the twrp for tecno spark 8c it works fine for me but when I restart the phone it enters a bootloop to the recovery
Click to expand...
Click to collapse
You can use the updated version with crypto support and automatic data partition decryption.
Download from https://github.com/dextterblog/Twrp-builder/releases
Jermaine22martinez said:
hello how is the twrp for tecno spark 8c it works fine for me but when I restart the phone it enters a bootloop to the recovery
Click to expand...
Click to collapse
After flashing run fastboot reboot, it will reboot directly to TWRP recovery enter your lock screen password to unecrypt data, then click on advanced install recovery ramdisk and select the twrp.img you downloaded or click on advanced then install current TWRP and let the recovery do the rest.
Check it out on hovatek forum
Kelexine said:
Here is a copy of you can't download from GitHub.
Click to expand...
Click to collapse
Make A TWRP Tree For Your Device & Build.md
GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
This Guide will help you!
FiniteCode said:
Make A TWRP Tree For Your Device & Build.md
GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
This Guide will help you!
Click to expand...
Click to collapse
Thanks but I already compiled for my device
Kelexine said:
Thanks but I already compiled for my device
Click to expand...
Click to collapse
Great! No Problem...
(*Sigh* Why Am I So Late At Everything?)
FiniteCode said:
Great! No Problem...
(*Sigh* Why Am I So Late At Everything?)
Click to expand...
Click to collapse
Just keep trying your best
New release: TWRP recovery for TECNO SPARK 8C
Link to files are here for latest build look here and for direct download click here
Related
DisclaimerThis software comes wth no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device.
Note: Currently Oreo 8.1 custom roms are supported only on BKL-L04 with EMUI 8.1
Download and Installation
* Download twrp recovery
* Start your device in fastboot mode
* Install the recovery using the following command:
Code:
fastboot flash recovery_ramdisk [name of the file].img --> ex: fastboot flash recovery_ramdisk twrp_blanc_0.1.img
* Restart with this command:
Code:
fastboot reboot
* As soon as you execute the restart command,remove the USB cable and keep pressing Volume UP,so the device will boot to TWRP.This is to avoid that the device boot to OS,overwritting TWRP recovery.
Features
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
Note: There are no sources for this yet,because is based on the work of @zxz0O0 ,from Honor 9 forum.
Credits
**** @zxz0O0 - This wouldn't be possible without this guy,so big big thank to him.I used his base to make this recovery work ,so in sign of respect his nick will also be on the TWRP boot screen.Thank again buddy!
**** TeamWin project ,obviously.
Download links
twrp_blanc_0.1.img - initial test release
twrp_bkl_0.2.img - OEMinfo partition is available for backup
twrp_bkl_0.3.img - /cache mounting is fixed,backup /vendor as image (vendor still can't be mounted)
twrp_bkl_0.4.img - /vendor mounting/unmounting is now fixed (thx @ante0 for the script)
twrp_bkl_0.5.img - mounting/unmounting issues shound be fixed , added a new option to exclude OEM path from wiping with Factory Reset and can be enabled/disabled in settings (thx Team OpenKirin for this), this version will work even with newer updates that bump security patch version.
twrp_bkl_0.6.img - Cache wiping issue is now fixed
twrp_bkl_0.7.img - fixed decryption on EMUI 8.1 (now you can use the same password/pin/pattern to decrypt in TWRP), /recovery_ramdisk no longer available for backup./vendor no longer available for backup (use /vendor_image instead),/system and /data can be unmounting issue with 8.1 devices is now fixed.
Pretoriano80 said:
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
Click to expand...
Click to collapse
Thanks man! :laugh: Need to test this!
IcipherPT said:
Thanks man! [emoji23] Need to test this!
Click to expand...
Click to collapse
No problem! Please report back if it's working or not.
Pretoriano80 said:
No problem! Please report back if it's working or not.
Click to expand...
Click to collapse
wipe everything to decrypt?
ngoralph said:
wipe everything to decrypt?
Click to expand...
Click to collapse
Nope, just decrypting, like you do when your phone is starting and asks for PIN! [emoji6]
Pretoriano80 said:
No problem! Please report back if it's working or not.
Click to expand...
Click to collapse
Just tested on my honor view 10. It was asking for a password to decrypt. I entered my lockscreen pass and everything was decrypt.
so TWRP CAN decrypt
@youtuber123
did you try a nandroid backup?
youtuber123 said:
Just tested on my honor view 10. It was asking for a password to decrypt. I entered my lockscreen pass and everything was decrypt.
so TWRP CAN decrypt
Click to expand...
Click to collapse
Ok, so it's working!Great,please let me know if something it's broken (backup, restore, MicroSD mounting, etc).
Pretoriano80 said:
Ok, so it's working!Great,please let me know if something it's broken (backup, restore, MicroSD mounting, etc).
Click to expand...
Click to collapse
nandroid (backup and restore) is working
mtp is working too
and micro usb mounting is working
didn't tested to flash something using twrp
youtuber123 said:
nandroid (backup and restore) is working
mtp is working too
and micro usb mounting is working
didn't tested to flash something using twrp
Click to expand...
Click to collapse
There's not much stuff to flash for this device! [emoji16]
Good, finally a useful twrp....
Can we flash LOS using this now?
@Pretoriano80
tried your recovery at my view 10. flashed it via fastboot. had no success. your twrp is hanging at the start screen. tried to flash it via the twrp of dees_troy, the same result. recovery is not booting completely, remains at the twrp start screen. any ideas?
kurvenmeister said:
@Pretoriano80
tried your recovery at my view 10. flashed it via fastboot. had no success. your twrp is hanging at the start screen. tried to flash it via the twrp of dees_troy, the same result. recovery is not booting completely, remains at the twrp start screen. any ideas?
Click to expand...
Click to collapse
Which version? Another user reported that is working.
Edit: More details about your device?Which version do you have exactly?
the twrp_blanc_0.1.img
the dl-link of twrp_bkl_0.2.img is not working
kurvenmeister said:
the twrp_blanc_0.1.img
the dl-link of twrp_bkl_0.2.img is not working
Click to expand...
Click to collapse
Ok thank,link is fixed .but if the initial one didn't booted ,i don't think this will do.Which version of Honor 10 do you have (european,usa,etc)?I'm not sure it will work on the US version or any other version which is based on Oreo 8.1.
@Pretoriano80
dl-link worked. tried the second version of your recovery. still no success. it is hanging at the start screen. nothing else happend. european bkl-l09, resurrection remix, oreo 8.1
kurvenmeister said:
@Pretoriano80
dl-link worked. tried the second version of your recovery. still no success. it is hanging at the start screen. nothing else happend. european bkl-l09, resurrection remix, oreo 8.1
Click to expand...
Click to collapse
The custom rom might be the culprit!I didn't tested on custom roms.
Pretoriano80 said:
Ok thank,link is fixed .but if the initial one didn't booted ,i don't think this will do.Which version of Honor 10 do you have (european,usa,etc)?I'm not sure it will work on the US version or any other version which is based on Oreo 8.1.
Click to expand...
Click to collapse
Hey mate nice to see you here
Nice job with the recovery! I've been handed out an US View 10 a couple weeks ago (with Android 8.1 pre-release stuff), I'll test it out for you.
twrp-3.2.1-0-berkeley.img didn't boot on BKL-L04 (dark screen and reboot), but Ethan made some changes and twrp-3.2.1-1-berkeley.img does work fine.
I've been told that some selinux changes were needed to boot 8.1 stuff, some critical service that fails to run because it can't find the right policy, something related to recovery_vendor partition that runs it.
It will work in 8.0 setups also just fine.
I'll let you know how it goes :fingers-crossed:
Hope we get 8.1 kernel sources soon so I blu_spark this blue beauty
Rommco05 said:
I succesfuly make full backup (except data) and flashed busybox. I dont need decrypted data all seems to be fine. In backup section just missing OEM
Click to expand...
Click to collapse
Latest version should have Oeminfo available for backup! Did you tested that version?
eng.stk said:
Hey mate nice to see you here
Nice job with the recovery! I've been handed out an US View 10 a couple weeks ago (with Android 8.1 pre-release stuff), I'll test it out for you.
twrp-3.2.1-0-berkeley.img didn't boot on BKL-L04 (dark screen and reboot), but Ethan made some changes and twrp-3.2.1-1-berkeley.img did.
I've been told that some selinux changes were needed to boot 8.1 stuff, some critical service that fails to run because it can't find the right policy, something related to recovery_vendor partition that runs it.
It will work in 8.0 setups also jsut fine.
I'll let you know how it goes :fingers-crossed:
Click to expand...
Click to collapse
Hi! My favourite kernel developer is here, nice!
I have a guess on what may be wrong, but i'm not sure. Let me know if you figure out! [emoji6]
https://mega.nz/folder/spBwXZoL#D1Wf8xLl1WacstfVnLnKhA
Any chance of some info on how to install?
TYIA.
what is this
Can you give a bit more details where you got this? Did you compile it? Was it pulled from another sony device? Do you have a github link?
Once again @M-Rom ! First TWRP for the Xperia 2019 Flagships and now the 2020 Series...
Same as for the Xperia 1 II:
-Download and extract the ZIP File to Your fastboot Location and rename it to recovery.img (for ease use)
-Use:
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
-Disconnect Your Device from USB and wait for it to turn off
-Press and hold VolumeDOWN & the Power Button together until You see the TWRP Logo (or use the reboot recovery option)
Miustone said:
Once again @M-Rom ! First TWRP for the Xperia 2019 Flagships and now the 2020 Series. Guide:
-Download and extract the ZIP
-Rename the file inside to boot.img
-fastboot flash boot_a boot.img
-fastboot flash boot_b boot.img
-Disconnect from USB and wait for the Device to run off
-Press and hold VolumeDOWN together with the Power Button
-TWRP should Start (in Chinese again!? lol)
Happy testing!
You can join My Discord Server if You need help with that... Ask Jayram which has successfully booted and used TWRP on his Xperia 5 II
MOD EDIT: Link removed, please read the STICKY!
Click to expand...
Click to collapse
Tried these steps and it worked perfectly, it is in chinese by default.
Updated My Instructions since 2020 Xperia Devices have a seperated recovery partition against the boot image/ramdisk ones on the older Devices. That's a huge win for Android Devices! Happy flashing Dear MARK II Users!
This installs successfuly, but it's kind of useless with the storage encryption. I tried wiping, but after restarting the device it becomes encrypted again. You need to change the language every time too. Is there any way to keep the internal storage decrypted? like the disabler .zip for samsung devices?
palamosteliaro said:
This installs successfuly, but it's kind of useless with the storage encryption. I tried wiping, but after restarting the device it becomes encrypted again. You need to change the language every time too. Is there any way to keep the internal storage decrypted? like the disabler .zip for samsung devices?
Click to expand...
Click to collapse
Doesn't TWRP support decrypting? On my previous devices it wasn't a problem, I never had an urge to decrypt the device.
Nezorflame said:
Doesn't TWRP support decrypting? On my previous devices it wasn't a problem, I never had an urge to decrypt the device.
Click to expand...
Click to collapse
Different TWRPs support different features. To get this one to support decrypting it will have to be worked on by the dev.
Unfortunately the internal storage decryption is broken since the December security patch update (58.0.A.28.51)...
OhayouBaka said:
Unfortunately the internal storage decryption is broken since the December security patch update (58.0.A.28.51)...
Click to expand...
Click to collapse
I recently got a 5 ii, currently on 58.0.A.10.3 and received 58 0.A.28.51 update notification. Should I not update if I want root?
mtshure said:
I recently got a 5 ii, currently on 58.0.A.10.3 and received 58 0.A.28.51 update notification. Should I not update if I want root?
Click to expand...
Click to collapse
You can still update if you want root via Magisk, but you will need to patch the boot img instead of flashing the Magisk zip in TWRP.
That would be soooo great to get TWRP or OrangeFox for Xperia 5 ii turning on Android 12!
Yoannjap said:
That would be soooo great to get TWRP or OrangeFox for Xperia 5 ii turning on Android 12!
Click to expand...
Click to collapse
Soon
King081 said:
Soon
Click to expand...
Click to collapse
No... Really?
But untill when could we hope for that?
Whoever is trying to adapt OrangeFox for X5ii_A12... Thanks a million!
Yoannjap said:
No... Really?
But untill when could we hope for that?
Whoever is trying to adapt OrangeFox for X5ii_A12... Thanks a million!
Click to expand...
Click to collapse
Yeah I'm being serious, we have it in private testing currently
Can somebody please confirm both recoveries (twrp / orangefox) currently available for (x5ii / pdx206 / XQ-AS52) only work on android 11 or prior? I tried both and they bootloop.
go0 said:
Can somebody please confirm both recoveries (twrp / orangefox) currently available for (x5ii / pdx206 / XQ-AS52) only work on android 11 or prior? I tried both and they bootloop.
Click to expand...
Click to collapse
Yes it will not work, new one will be out real soon
m
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Mi 11 lite 5G
bugs:
backup/restore is unreliable
adb sideload and fastbootd
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
Send me a beer: Crypto (Preferred) | PayPal
Contributors:
@VladV1V , @TheMalachite
Tree:
GitHub - TeamWin/android_device_xiaomi_renoir
Contribute to TeamWin/android_device_xiaomi_renoir development by creating an account on GitHub.
github.com
Kernel:
https://github.com/VladV1V/kernel_xiaomi_renoir
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomimi11lite5g.html
Sorry, but the installation did not work for me... :-( What i have done:
- i renamend the downloaded file to "twrp.img"
- i copied this file to the internal storage
- i startet the phone in fastboot mode
- then i startet adb
- i used the command "fastboot boot twrp.img"
Then i saw the following:
downloading 'boot.img'...
OKAY [ 2.826s]
booting...
OKAY [ 0.201s]
finished. total time: 3.027s
But the phone only switched off and nothing happend. What's wrong?
EDIT: i solved the problem! I forgot to put the file "twrp.img" into the adb folder. After doing this, the installation worked! Now i tried to make a backup, but it was not possible to select the external sd-card. How can i solve this problem?
Hi, thank's for your work for our device...
I read somewhere, that if we have TWRP installed, that we cannot flash update with fastboot...I want to know if it's true and if yes, how can we flash update..we have to find recovery update, or we can extract from fastboot archive and flash it??
thanks for your answer
Rainman67 said:
Now i tried to make a backup, but it was not possible to select the external sd-card. How can i solve this problem?
Click to expand...
Click to collapse
certainly not available yet...you have to backup in internal storage and then copy to SD...
Another question: how to go back to stock recovery?
Rainman67 said:
Another question: how to go back to stock recovery?
Click to expand...
Click to collapse
I'm on Xiaomi EU ROM. After last update via fastboot Miui Recovery 5.0 comes back.
Great hopefully this leads to development of some easy to flash roms, cant wait to get rid of this buggy MIUI trash.
I tried last version (16th July). Sadly no touchscreen.
Anyway many thanks!
same with #8 boot into twrp and no touchscreen
Peterpaulmarie said:
I tried last version (16th July). Sadly no touchscreen.
Anyway many thanks!
Click to expand...
Click to collapse
FuLuLu said:
same with #8 boot into twrp and no touchscreen
Click to expand...
Click to collapse
Boot TWRP from fastboot and touch will work.
Peterpaulmarie said:
I tried last version (16th July). Sadly no touchscreen.
Anyway many thanks!
Click to expand...
Click to collapse
FuLuLu said:
same with #8 boot into twrp and no touchscreen
Click to expand...
Click to collapse
How did you flash it?
Nebrassy said:
How did you flash it?
Click to expand...
Click to collapse
Fastboot boot twrp.img
Advanced - > flash current recovery
As well tried
Fastboot flash recovery twrp.img
Failed
Also
Advanced - > install recovery ramdisk
But magisk said ramdisk Yes
Peterpaulmarie said:
Fastboot boot twrp.img
Advanced - > flash current recovery
As well tried
Fastboot flash recovery twrp.img
Failed
Also
Advanced - > install recovery ramdisk
But magisk said ramdisk Yes
Click to expand...
Click to collapse
pm me on telegram if you can get logs and have adb access
dannejanne said:
Boot TWRP from fastboot and touch will work.
Click to expand...
Click to collapse
Nebrassy said:
How did you flash it?
Click to expand...
Click to collapse
i just boot to try if it can boot in twrp lol, no need to flash it so far,if needed it i will use the method u guys said(real flash in)
Well then both of you make sure you're actually using the build from afh and only use it for fastboot boot, when you want to flash use flash current twrp don't flash it with fastboot
Touch works when using fastboot boot and when flashed, it Was already tested on multiple devices
@Nebrassy Thanks for your contribution. Looking forward to the stable version with the known bugs fixed and touch works normally, without fastboot.
Thanks again.
doclucas said:
@Nebrassy Thanks for your contribution. Looking forward to the stable version with the known bugs fixed and touch works normally, without fastboot.
Thanks again.
Click to expand...
Click to collapse
Touch already works normally without fastboot
Nebrassy said:
Touch already works normally without fastboot
Click to expand...
Click to collapse
Nebrassy said:
Touch already works normally without fastboot
Click to expand...
Click to collapse
Yes, I can confirm. After start recovery wait 10-15sec touchscreen will work
With the test builds from telegram twrp was not able to recognize my SD card. Is this now fixed?
Is it possible to flash Xiaomi.eu weekly rom only by starting twrp from fastboot without installing it?
Hello, I have a tablet Xperia Z2 andriod 6.0.1, the original sony rom. I can't upload TWRP, everything loads fine with fastboot and TWRP won't boot because I'd like to install LineageOS. Bootloader unlocked correctly.
Sorry for my bad english and please help
From what I found out, it is possible to upload a custom rom via NUT'S Dual Recovery. Only the download page of this program and the links are inactive. If anyone has it, please link to the NUT'S Dual Recovery program
As you know fastboot, try this and see if you have luck.
Extract your custom rom zip and reveal your .img files.
Put the .img files into the same folder with fastboot.exe
fastboot erase cache
fastboot erase data
fastboot flash system system.img
fastboot flash boot boot.img
If you have luck, it will boot into system. Backup, always, beforehand as it will delete all your data.
Thank you very much, thanks to this I somehow managed to launch TWRP. I have installed LineageOs 18.1, the system works.
Silny033 said:
Thank you very much, thanks to this I somehow managed to launch TWRP. I have installed LineageOs 18.1, the system works.
Click to expand...
Click to collapse
Could you please describe your steps? I followed the instructions in lineage's wiki, tried flashing the latest castor compatible lineage recovery, tried different TWRP versions... It's always the same: fastboot prints "OKAY" but I can't boot into recovery.
My device is unlocked, but not rooted.
Testing Tester said:
Could you please describe your steps? I followed the instructions in lineage's wiki, tried flashing the latest castor compatible lineage recovery, tried different TWRP versions... It's always the same: fastboot prints "OKAY" but I can't boot into recovery.
My device is unlocked, but not rooted.
Click to expand...
Click to collapse
Hello, did you try fastboot boot twrp twrp.img, and flash TWRP in TWRP as soon as you get into it?
Testing Tester said:
Could you please describe your steps? I followed the instructions in lineage's wiki, tried flashing the latest castor compatible lineage recovery, tried different TWRP versions... It's always the same: fastboot prints "OKAY" but I can't boot into recovery.
My device is unlocked, but not rooted.
Click to expand...
Click to collapse
I'm in the same situation except I only tried with Lineage recovery for now. What did you end up doing? Many thanks.
LR7875 said:
Hello, did you try fastboot boot twrp twrp.img, and flash TWRP in TWRP as soon as you get into it?
Click to expand...
Click to collapse
Shall I try this? At this stage I haven't even tried TWRP. I only tried LineageOS Recovery but same situation as @Testing Tester : impossible to boot into it. What TWRP version do you recommand? @Silny033 which version worked for you?
Bonpotiron said:
Shall I try this? At this stage I haven't even tried TWRP. I only tried LineageOS Recovery but same situation as @Testing Tester : impossible to boot into it. What TWRP version do you recommand? @Silny033 which version worked for you?
Click to expand...
Click to collapse
I did everything as LR7875 advised, boot twrp first and then LineageOS 18.1 and it works fine. I have twrp 3.2.1-1
Silny033 said:
I did everything as LR7875 advised, boot twrp first and then LineageOS 18.1 and it works fine. I have twrp 3.2.1-1
Click to expand...
Click to collapse
LineageOS 18.1 really? I'm confused because the instructions on Lineage website say that the last nightly built is LineageOS 17.1 – [ Android 10.0.0 (Android 10) ] of 2021-10-06
LR7875 said:
As you know fastboot, try this and see if you have luck.
Extract your custom rom zip and reveal your .img files.
Put the .img files into the same folder with fastboot.exe
fastboot erase cache
fastboot erase data
fastboot flash system system.img
fastboot flash boot boot.img
If you have luck, it will boot into system. Backup, always, beforehand as it will delete all your data.
Click to expand...
Click to collapse
What do you call 'system' please? is it the custom rom or the recovery?
Is this procedure similar to yours? the user also has the SGP511 device. https://forum.xda-developers.com/t/...for-castor-castor_windy.4210181/post-84710741
Bonpotiron said:
What do you call 'system' please? is it the custom rom or the recovery?
Click to expand...
Click to collapse
1. Unzip the lineageos zip
2. Find system.img (special case it is system.new.dat.br, tell me if it is)
3. Execute the aforementioned command
LR7875 said:
1. Unzip the lineageos zip
2. Find system.img (special case it is system.new.dat.br, tell me if it is)
3. Execute the aforementioned command
Click to expand...
Click to collapse
it is system.new.dat.br
Bonpotiron said:
LineageOS 18.1 really? I'm confused because the instructions on Lineage website say that the last nightly built is LineageOS 17.1 – [ Android 10.0.0 (Android 10) ] of 2021-10-06
Click to expand...
Click to collapse
This is the latest unofficial version from this topic: https://forum.xda-developers.com/t/rom-unofficial-lineageos-18-1-for-castor-castor_windy.4261491/
It is stable on this
Bonpotiron said:
it is system.new.dat.br
Click to expand...
Click to collapse
Ok and what happens if you 'fastboot boot twrp.img'?
Try this
If it gets into twrp immediately wipe and flash lineageos
@LR7875 the device enters recovery in a hidden way, as the display stays black.
I managed to install Lineage 17.0 with these instructions: https://forum.xda-developers.com/t/...for-castor-castor_windy.4261491/post-85738643
Boy, that was tricky !
Seems like the graphics driver of the recovery is broken.
Team Win Recovery Project or TWRP for short. Its a fully touch driven user interface, completely theme-able & you can change just about every aspect of the look and feel.
Now ported to the Galaxy Tab A7 Lite.
Download - You'll always find the latest release in here: https://github.com/DevZillion/android_device_samsung_gta7litewifixx/releasesKnown Issues / Report Issues - https://github.com/DevZillion/android_kernel_samsung_gta7litewifixx/issuesTelegram support group - https://t.me/gta7litegroup
How to install
[Boot Into Download mode by inserting an usb cable while holding both volume buttons]
Flash the latest .tar release from releases.
Hold the recovery combination (Volume Up + Power) while the .tar is flashing via the odin tool.
When booted up into TWRP go Flash and flash this zip, then go to Wipe > Format Data, all your data will be lost.
You can now boot into your system and do whatever you want.
Click to expand...
Click to collapse
Flashing Disabled vbmeta (To boot a modified system)
Spoiler: View
Extract the vbmeta.img.lz4 from the AP slot in your firmware.
Remove it's lz4 compression [for Windows use lz4]:
Code:
sudo apt-get install lz4 -y
lz4 vbmeta.img.lz4
Click to expand...
Click to collapse
Reboot into fastboot from TWRP flash vbmeta using this command line:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Sources
TWRP Source - https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-11
Device Tree - https://github.com/DevZillion/android_device_samsung_gta7litewifixx/
Kernel Source - https://github.com/DevZillion/android_kernel_samsung_gta7litewifixx
Click to expand...
Click to collapse
Special thanks to:
TeamWin for the Recovery Project.
Zillion for doing the device tree & kernel.
Click to expand...
Click to collapse
Actual TWRP status: Bugfixing; Try at your own risk and only if you know what you're doing.
Genial!!
Zillion said:
Team Win Recovery Project or TWRP for short. Its a fully touch driven user interface, completely theme-able & you can change just about every aspect of the look and feel.
Now ported to the Galaxy Tab A7 Lite WiFi.
Download - You'll always find the latest release in here: https://github.com/DevZillion/android_device_samsung_gta7litewifixx/releasesKnown Issues / Report Issues - https://github.com/DevZillion/android_kernel_samsung_gta7litewifixx/issuesTelegram support group - https://t.me/gta7litegroup
How to install
Flashing Disabled vbmeta (To boot a modified system)
Sources
Special thanks to:
Actual TWRP status: Bugfixing; Try at your own risk and only if you know what you're doing.
Click to expand...
Click to collapse
it boots, touch does not work but its usable with a mouse and gives an error "unable to mount /data"
dda7lite said:
it boots, touch does not work but its usable with a mouse and gives an error "unable to mount /data"
Click to expand...
Click to collapse
Please, read the How To Install section.
Zillion said:
Please, read the How To Install section.
Click to expand...
Click to collapse
I did but the file that needs to be flashed is unavailable in that link
dda7lite said:
I did but the file that needs to be flashed is unavailable in that link
Click to expand...
Click to collapse
Thanks for reporting the issue, link fixed.
Zillion said:
Thanks for reporting the issue, link fixed.
Click to expand...
Click to collapse
i have other problem error "E:unable to open block device /dev/block/sda: No medium found"
What is vbmeta?
I want to install Elixir Project. Is it necessary to do something from the vbmeta? Or just flashing the rom is enough?
chocovo said:
What is vbmeta?
I want to install Elixir Project. Is it necessary to do something from the vbmeta? Or just flashing the rom is enough?
Click to expand...
Click to collapse
Flash vbmeta is necessary to boot a new system but it's easy to flash too.
dda7lite said:
Flash vbmeta is necessary to boot a new system but it's easy to flash too.
Click to expand...
Click to collapse
I understand that the vbmeta is pulled from original samsung firmware, lz4 format stripped and flashed by AP. Then we implement the command by TWRP and the desired rom is installed.
Is that so?
Does the vbmeta step have to be done every time I put a new rom or only once?
Sorry for my english
chocovo said:
I understand that the vbmeta is pulled from original samsung firmware, lz4 format stripped and flashed by AP. Then we implement the command by TWRP and the desired rom is installed.
Is that so?
Does the vbmeta step have to be done every time I put a new rom or only once?
Sorry for my english
Click to expand...
Click to collapse
I only did once and I didn't use the stock vbmeta I just searched "vbmeta disabled Samsung" it should show up with vbmeta disabled android 11 but works the same on 13 and I didn't use TWRP only fastboot so i don't know how to flash it there.
Btw your English is good don't worry.
After installing TWRP I can't install the fbe. TWRP doesn't recognize my device's internal memory either.
chocovo said:
After installing TWRP I can't install the fbe. TWRP doesn't recognize my device's internal memory either.
Click to expand...
Click to collapse
Yeah
chocovo said:
After installing TWRP I can't install the fbe. TWRP doesn't recognize my device's internal memory either.
Click to expand...
Click to collapse
Because you need to flash the fbe_disabler using some usb otg, external sd card or by pushin the zip to /tmp, flash it and then format /data.
Zillion said:
Because you need to flash the fbe_disabler using some usb otg, external sd card or by pushin the zip to /tmp, flash it and then format /data.
Click to expand...
Click to collapse
Bootloop after
Zillion said:
Because you need to flash the fbe_disabler using some usb otg, external sd card or by pushin the zip to /tmp, flash it and then format /data.
Click to expand...
Click to collapse
My device is a T220.
The touch does not work in TWRP and I use a mouse. I use Micro SD to install the FBE. But when trying to install it gives me an error in the data folder. Although apparently it seems to be installed.
I format data as you indicate and restart in fastboot in TWRP to put the vbmeta by ADB and install a GSI. But it generates bootloop.
I don't know if I'm missing some step.
chocovo said:
My device is a T220.
The touch does not work in TWRP and I use a mouse. I use Micro SD to install the FBE. But when trying to install it gives me an error in the data folder. Although apparently it seems to be installed.
I format data as you indicate and restart in fastboot in TWRP to put the vbmeta by ADB and install a GSI. But it generates bootloop.
I don't know if I'm missing some step.
Click to expand...
Click to collapse
If you really want to flash a gsi and can't get it to work use a fastboot enabled recovery that's what I did
dda7lite said:
Bootloop after
Click to expand...
Click to collapse
Disable vbmeta, it's the only thing I can see you missed.
um i flashed the recovery to my sm-t220 but i do not have a usb otg i am buying it today in the meanwhile i tried to boot back to one ui 5.1 the one i have but it only shows twrpto reboot i used power + volume down but it shows twrp and power + volume up dosnt do anything
Gian-D said:
um i flashed the recovery to my sm-t220 but i do not have a usb otg i am buying it today in the meanwhile i tried to boot back to one ui 5.1 the one i have but it only shows twrpto reboot i used power + volume down but it shows twrp and power + volume up dosnt do anything
Click to expand...
Click to collapse
Force restart and keep the usb cable connected to the PC and tablet then as soon as screen blinks hold volume +and-