[RECOVERY][OFFICIAL] TWRP 3.5.2_9-0 [I9190][I9192][I9195][L520] - Galaxy S 4 Mini Original Android Development

[RECOVERY][OFFICIAL] TWRP 3.5.2_9-0 [I9190][I9192][I9195][L520] - Galaxy S 4 Mini Original Android Development

Reserved
CHANGELOG
3.2.1-1
* Restored compatibility with SD cards formatted in exFAT.
3.2.1-2
* Restored preload partition being visible when creating a backup.

Reserved

Your member of the TWRP Team ?.
It is nice to see that we have now an official TWRP.
Does new Build also support arco68 unofficial LOS 15.1 Version ?

Thanks @ripee !
Maybe you could link the the materialized theme in the OP : https://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
Clean design with a bunch of extra tools / options to enhance TWRP, this is really useful and handy ?
Sent from my S4 Mini using XDA Labs

lars85destroyer said:
Thanks @ripee !
Maybe you could link the the materialized theme in the OP : https://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
Clean design with a bunch of extra tools / options to enhance TWRP, this is really useful and handy
Sent from my S4 Mini using XDA Labs
Click to expand...
Click to collapse
Ok sure

ripee said:
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Click to expand...
Click to collapse
Thanks but seeing that Nougat version, will it work on a regular KitKat stock ROM ?
If not, which other version of TWRP should I use for an I9195 ?

TheRealKeyserSoze said:
Thanks but seeing that Nougat version, will it work on a regular KitKat stock ROM ?
If not, which other version of TWRP should I use for an I9195 ?
Click to expand...
Click to collapse
I have no reason to believe that 3.2.1-0 wouldn't work with stock KitKat. Just remember to pull the battery as soon as your phone vibrates after the flash finishes or else your stock rom could quickly re-flash its own stock recovery.
Please report feedback if you get it to work or not

That worked a treat!
Flawless flashing followed by installing root from TWRP.
Thanks a lot!

Been waiting on this...

Thank you for your job, but on my i9195 I had troubles with this release. Often it doesn't recognize my 32GB sdcard (it seems to be empty), instead of 3.2.0-1 that works as usual, also with oreo. Maybe I forgot to mount the microsd? But it's strnge, I've never mounted the microsd on previous versions.

Please include the exfat Samsung kernel driver:
https://forum.xda-developers.com/showpost.php?p=75650598&postcount=1638
sacharja said:
Indeed, however there seems to be a solution for Samsung products at least: https://github.com/bkuhn/exfat . Maybe ne0zone75 included this, but the TWRP guys don't use any Samsung device specific drivers.
Click to expand...
Click to collapse
I had the same issues with my SD

Dead here?

fankool said:
Thank you for your job, but on my i9195 I had troubles with this release. Often it doesn't recognize my 32GB sdcard (it seems to be empty), instead of 3.2.0-1 that works as usual, also with oreo. Maybe I forgot to mount the microsd? But it's strnge, I've never mounted the microsd on previous versions.
Click to expand...
Click to collapse
sacharja said:
Please include the exfat Samsung kernel driver:
https://forum.xda-developers.com/showpost.php?p=75650598&postcount=1638
I had the same issues with my SD
Click to expand...
Click to collapse
This has less to do with the exFAT driver and more to do with a missing TWRP flag in my device tree. I'll look into it.
What file format is your SD card in? Please try FAT32, exFAT, and NTFS so we can cover these most frequent possibilities.
sacharja said:
Dead here?
Click to expand...
Click to collapse
Users are used to ne0z0ne's unofficial builds perhaps.

sacharja said:
Please include the exfat Samsung kernel driver:
https://forum.xda-developers.com/showpost.php?p=75650598&postcount=1638
I had the same issues with my SD
Click to expand...
Click to collapse
I remember a similar problem with my TWRP build for the big S4, which I fixed by removing the following line from the BoardConfig.mk file:
Code:
TW_NO_EXFAT_FUSE := true
GT-I9190
twrp-3.2.1-1-serrano3gxx.img
twrp-3.2.1-1-serrano3gxx.tar
GT-I9192
twrp-3.2.1-1-serranodsdd.img
twrp-3.2.1-1-serranodsdd.tar
GT-I9195
twrp-3.2.1-1-serranoltexx.img
twrp-3.2.1-1-serranoltexx.tar

ripee said:
What file format is your SD card in? Please try FAT32, exFAT, and NTFS so we can cover these most frequent possibilities.
Click to expand...
Click to collapse
I'm not 100% sure but I remember last time I formatted using exfat
---------- Post added at 21:55 ---------- Previous post was at 21:31 ----------
GT-I9195
twrp-3.2.1-1-serranoltexx.img
twrp-3.2.1-1-serranoltexx.tar[/QUOTE]
Worked! Just booted in recovery and tried to open sdcard from file manager and I saw the files stored. Thank you.

fankool said:
I'm not 100% sure but I remember last time I formatted using exfat
---------- Post added at 21:55 ---------- Previous post was at 21:31 ----------
GT-I9195
twrp-3.2.1-1-serranoltexx.img
twrp-3.2.1-1-serranoltexx.tar
Click to expand...
Click to collapse
Worked! Just booted in recovery and tried to open sdcard from file manager and I saw the files stored. Thank you.[/QUOTE]
Fantastic! Thanks very much for your feedback! I'll update the official repo and ask TeamWin to compile official 3.2.1-1 builds.

Cool, it also worked for me now with the exfat SD (NTFS is of course working too).
Great job ripee, many thanks for your good work

@ripee
Hi this is the first time i want to install twrp on s4 mini lte version. By odin. But i do not boot in twrp. Always stock recovery.
What am i doing wrong ?

djbosanac said:
@ripee
Hi this is the first time i want to install twrp on s4 mini lte version. By odin. But i do not boot in twrp. Always stock recovery.
What am i doing wrong ?
Click to expand...
Click to collapse
If you have stock installed, you have to very quickly pull the battery as soon as your phone vibrates when Odin says PASSED! The stock rom is very sneaky because, if you don't pull the battery, it will re-flash its own stock recovery before rebooting into system.

Related

[SFOS] [EXPERIMENTAL}SailfishOS 2.0.2.48 for Redmi 2

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The Alpha release was experimental and was not meant for the general public, but still recieved an overwhelming response. This new Beta version is free of most bugs encountered earlier and is suitable for everyone to get a taste of SailfishOS on their phone.
Read the installation instructions carefully.
Changelog from Alpha -->
* Bluetooth fixed.
* Audio now works out of the box.
* Camera Resolutions updated.
* Flash now works in Camera.
* Settings app now shows settings for cellular networks.
* FM-Radio now supported. ( Highly Experimental. Read the FM-Radio section below )
* Stand-by time vastly improved.
* Basic Jolla apps are now pre-installed. ( Before anyone talks about bloatware, you got the option to uninstall them)
* Warehouse, the community appstore is now pre installed.
Sailfish OS’s heritage lies in Nokia times, especially in the MeeGo operating system. Prior to 2011 Nokia and Intel had a vision of an open mobile operating system. Together they invested around 1 billion USD to the project and created an open source based operating system called MeeGo, which was used as a basis for several devices, such as the iconic Nokia N9. Although the Nokia N9 became the beacon of open source operating systems, Nokia decided to end the project and chose instead to continue with Microsoft’s Windows Phone OS. The rest of that is another story.
For more information about SailfishOS click here.
SailfishOS has now been successfully ported to Redmi 2 and here I am sharing the steps to install it on your phone.
Code:
Disclaimer: Your warranty is now void. You will lose all your data on your phone and may render it unusable. This software is provided as is without any warranty of any kind whatsoever. The user shall solely be reponsible for any consequence arising out of following this guide. I, or anyone else shall not be held responsible for bricked devices, dead sd-cards, thermonuclear war, you getting fired because the alarm app failed or any other consequence of following this guide. The linked zip contains some proprietary files.
tl;dr I wont be held responsible for any unfortunate incidence.
Prerequisites -->
1) Latest TWRP recovery installed (Others may work too but I haven't tested). You can get it here-->http://forum.xda-developers.com/redmi-2/development/recovery-recovery-built-source-inside-t3277621
*Note that the Cyanogenmod version is now changed.
2) cm-12.1-20160318-UNOFFICIAL-wt88047 zip by kumajaya. You can get it from his google drive link here--> http://forum.xda-developers.com/redmi-2/development/rom-cyanogenmod-unofficial-builds-t3200883
3) SailfishOS zip file. Download link given below.
This is not an Android ROM and thus the instructions to install are quiet different. Follow them carefully.
1) Boot to recovery. Wipe cache, dalvik-cache, system and data.
2) Copy the Downloaded files to the sdcard via USB.
3) Install cm-12.1-20160318-UNOFFICIAL-wt88047. Do NOT reboot after installing.
4) Install SailfishOS zip file. The installation will take around 10 minutes so don't think that its stuck. Ignore any errors about being unable to mount data partition.
5) Reboot System when installation succeeds.
Notes-->
1) This is not an Android ROM. Android apps will not work right now. But a way for Android apps to work is available but will take quiet some time before it gets on our device.
2) Root access (using devel-su in terminal) requires a password which can be set in Settings>Developer Options.
3) For advanced users, you can ssh into the device after setting a password in Developer options using ssh [email protected] over USB.
4) Do not register for a Jolla account. You will get an error about failed IMEI registration. This will be fixed as soon as Jolla allows ported devices to be registered.
5) The Store will not work. It needs a Jolla account. You can however use the openrepos warehouse for installing apps.
6) MTP over USB does not work.
7) Battery drains faster if screen is ON. Better than alpha but still needs improvement.
FM-Radio -->
You can play FM-Radio now but it is experimental.
Plug in your headphones and launch the PirateFM app for radio.
if it won't start, open terminal and use "harbour-piratefm" to start it.
Once the app starts, it should show a frequency. If its stuck at 0.0 MHz, then close the app(close, not minimise) and restart it again.It should show a frequency now. If you have echoing audio in the headphones, i.e. you hear your own voice in the headphones, then open terminal and " systemctl restart --user pulseaudio" and then try running the app again.
FM will not work through the speakers, and it also cannot be muted.
Download Link -->
The file has been named as alpha-2 because that is how it was initially intended but it would be better to designate this as beta since its almost stable.
https://www.androidfilehost.com/?fid=24591020540823211
DO NOT SHARE MY WORK WITHOUT MY EXPLICIT PERMISSION. IF YOU ARE SHARING, LINK TO THIS POST.
XDA:DevDB Information
SailfishOS 2.0.2.48, ROM for the Xiaomi Redmi 2
Contributors
adeen-s, @mal- @sledges @kimmoli @Stskeeps @spiiroin @Litew @jusa_ @ketut.kumajaya
Source Code: https://github.com/adeen-s/droid-config-wt88047 ; https://github.com/adeen-s/droid-hal-version-wt88047 ; https://github.com/adeen-s/hybris-boot/ ; https://github.com/adeen-s/droid-hal-wt88047 ; https://github.com/adeen-s/android_kernel_cyanogen_msm8916 ;
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Must not have flashed lollipop MIUI update.
Based On: SailfishOS
Version Information
Status: Testing
Current Beta Version: 1
Beta Release Date: 2016-06-30
Created 2016-06-30
Last Updated 2016-09-17

Reserved
For Android app compatibility, I need help from someone with significant experience in compiling cyanogenmod. PM me.

Reserved
Warning : This procedure will wipe all data on your device.
MultiROM thread--> http://forum.xda-developers.com/redmi-2/development/mod-multirom-v33-t3381373
MultiROM Instructions -->
1) Get the modified twrp and multirom zip from the multirom thread.
2) Reboot to recovery, select Install, select install image, choose the modified twrp and flash it to recovery partition.
3) Reboot recovery. It should now boot up to the modified TWRP.
4) Wipe Data,System,Cache and Dalvik-Cache.
5) Select Install from Recovery main menu. Select cm-12.1-20160318 zip. uncheck all options and install it.
6) Again Select Install from Recovery main menu. Select SailfishOS zip file and uncheck all options and install it.
7) Select MultiROM settings ( small button on top right corner in main menu of recovery). Select inject current boot sector. Reboot or install secondary ROM of your choice now.
8) For adding Secondary ROMs of your choice, refer to the MultiROM thread.

I tried the first, alpha build, it was really really good, but can you please tell me how to install it as a secondary ROM havin it's own kernel via multiboot, as I was really tires of switching kernels everytime I had to switch between CM13 and SailFish.
I hope it's possible.
.
Also, will it not work with the latest, Lolipop Bootloader? (As i can make out from the "Required Firmware" section from OP)

shanx_verma said:
I tried the first, alpha build, it was really really good, but can you please tell me how to install it as a secondary ROM havin it's own kernel via multiboot, as I was really tires of switching kernels everytime I had to switch between CM13 and SailFish.
I hope it's possible.
.
Also, will it not work with the latest, Lolipop Bootloader? (As i can make out from the "Required Firmware" section from OP)
Click to expand...
Click to collapse
Since the base cyanogenmod will not work with the lollipop bootloader, it cannot be done. Sailfish will work if a way to run the base cm over the lollipop bootloader is found.
As for the multiboot, I haven't tried it yet but take a look at this http://forum.xda-developers.com/showpost.php?p=67519570&postcount=62 although it was already addressed to you.

@adeen-s well as per the updated devolvement for wt88047, CM now supports Lollipop bootloader. Can you please guide us through the process of having SFOS as secondary? Is it like installing any other secondaries?

@adeen-s can you change base sfos to cm13
Sent from my 2014817 using Tapatalk

NeoDarkness said:
@adeen-s can you change base sfos to cm13
AFAIK Sailfish OS 2.0 Can only run over CM 10.x 11.x 12.1.
Source- Sailfish OS Hardware Adaptation Development Kit
Click to expand...
Click to collapse

iamsubhranil said:
@adeen-s well as per the updated devolvement for wt88047, CM now supports Lollipop bootloader. Can you please guide us through the process of having SFOS as secondary? Is it like installing any other secondaries?
Click to expand...
Click to collapse
CM-12.1 still does not.

SF.OS doesn't work with LP BootLoader. Thanks for the Info.
adeen-s said:
CM-12.1 still does not.
Click to expand...
Click to collapse
Oh, and there I was, wondering why my SFOS wasn't booting on LP Bootloader.

wow sailfish os enters beta
What are remaining issue items? battery drain fixed?

Bugs
Hi, i love this os and hope android apps support is coming soon.
the bugs that i found is the music player seem to show the same mp3 file as 2 different file but one with correct duration and the other one is zero.
for problems, the battery draining quite fast :crying:
thank you for your hard work dev!!!

@adeen-s that means if i flash the rom as secondary having k loader, it'll work?

@adeen-s What a beautiful typographical OS with fluent transitions. Been using it with MultiROM keeping my previous primary RR 5.7.1 as secondary. Everything is pretty good on my side. Just animations are quite unfluent sometimes. And some USSD codes aren't showing when dialed. Like *143*0# and *400# on Aircel(404 91).

Using it, wow!
iamsubhranil said:
@adeen-s What a beautiful typographical OS with fluent transitions. Been using it with MultiROM keeping my previous primary RR 5.7.1 as secondary. Everything is pretty good on my side. Just animations are quite unfluent sometimes. And some USSD codes aren't showing when dialed. Like *143*0# and *400# on Aircel(404 91).
Click to expand...
Click to collapse
How did you return to the KK bootloader, buddy?

iamsubhranil said:
@adeen-s that means if i flash the rom as secondary having k loader, it'll work?
Click to expand...
Click to collapse
Not sure. I tried it once and it didn't work. It may need a workaround to work as secondary.

shanx_verma said:
How did you return to the KK bootloader, buddy?
Click to expand...
Click to collapse
I had backed it up using twrp. Just restored Firmware. U flash any miui kk fastboot
---------- Post added at 04:32 PM ---------- Previous post was at 04:31 PM ----------
adeen-s said:
Not sure. I tried it once and it didn't work. It may need a workaround to work as secondary.
Click to expand...
Click to collapse
Yup MR showed some errors about not founding fstab

Here's some screenshots
Hey guys. It's wonderful!

iamsubhranil said:
Hey guys. It's wonderful!
Click to expand...
Click to collapse
Thanks for the screenshots. I'm glad to know you liked it.

iamsubhranil said:
I had backed it up using twrp. Just restored Firmware. U flash any miui kk fastboot
Yup MR showed some errors about not founding fstab
Click to expand...
Click to collapse
Okay, I have the firmware partition backed up. What all will it restore - will it restore the KK modem as well? (cuz I don't want KK modem, just the bootloader).

[RECOVERY][SM-P605] Unofficial TWRP 3.5.1 for lt03lte (18.03.2021)

This is only for SM-P605 (lt03lte)! Even loading an custom recovery will irreversible trigger Knox to 0x1!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
This is an unoffical build of TWRP from my device sources. It includes a few fixes for some stuff (see list below).
For further information please check the official TWRP thread in Original Android Development Forum.
Installation:
Important: You have to be on 4.4.2 Bootloader or newer (e.g. with flashing 4.4.2/5.1.1 Firmware via Odin)
Using an existing custom recovery: download zip, TWRP: Install > select zip > swipe
Using Odin: download tar, switch on device in download mode, AP: select tar > start
Using Flashify/Flashfire: Use img
What is working:
-MTP
-Brightness settings
-Vibration
-No delay between recovery and splashscreen
-...
What is not working/bugs:
-You tell me
-...
Download:
IMG
TAR
ZIP
Other builds / AFH
Changelog:
20210318: TWRP 3.5.1
20200913: TWRP 3.4.0-0
20190418: TWRP 3.3.0-0
20180923: added unzip (fixes Error64)
20180921: TWRP 3.2.3-0, add support for EFS/Modem backup
20180526: TWRP 3.2.1-0
20170712: first release
Sources:
Kernel:https://github.com/davidmueller13/kernel_samsung_lt03lte_nougat2
TWRP:https://github.com/omnirom/android_bootable_recovery
XDA:DevDB Information
[RECOVERY][SM-P605] Unofficial TWRP 3.4.0-0 for lt03lte, Tool/Utility for the Samsung Galaxy Note 10.1 (2014 Edition)
Contributors
davidmueller13
Version Information
Status: Stable
Stable Release Date: 2020-09-13
Beta Release Date: 2017-07-12
Created 2017-07-12
Last Updated 2020-09-13

Thank you OP!!!
My problem has been resolved!
I will elaborate further when I get back home from current business trip.
Btw, I noticed that the recovery's SEANDROID warning message is now gone, good work!
Edit:
I have installed this recovery by flashing the IMG through v3.0.3 successfully and noted the following changes:-
General result:
When in recovery mode, the "red" warning message of "SEANDROID not enforcing" has been fixed.
Personal:
1. Now, I am able to flash phh's superuser flawlessly without any error message which were the case previously with v2.8.7 -> 3.0.2 and 3.0.3.
2. Now, when my device (with boot.img mod + phh superuser) boot normally, the red SEANDROID warning message is gone too.

Thank you for this new release :good:
I was having a problem to convert my cache and data partitions to F2FS as libf2fs.so was missing from your version 3.0.3 and is now included in this version :good:

This device is the only one where I enabled Adopted Storage, so I don't know if this a common problem. With it enabled I can't flash anything with recovery. Both internal and external SD are not visible or empty, and even if I copy zips into system folder, TWRP doesn't see them. Is there a workaround?
Only solution I found is using a different sd to flash files, but it's complicated and annoying.
Inviato dal mio SM-P605 utilizzando Tapatalk

asusgarb said:
This device is the only one where I enabled Adopted Storage, so I don't know if this a common problem. With it enabled I can't flash anything with recovery. Both internal and external SD are not visible or empty, and even if I copy zips into system folder, TWRP doesn't see them. Is there a workaround?
Only solution I found is using a different sd to flash files, but it's complicated and annoying.
Inviato dal mio SM-P605 utilizzando Tapatalk
Click to expand...
Click to collapse
Your problem (adoptable storage is encrypted) might be resolved if you place your ZIP into "the path of" your TWRP's backup folder.
Source: Google Search

please upload or can anybody
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
twrp-3.0.3-0-lt03lte_20170206.zip
Best Regards
thanks

Hi,
Any specific need for version 3.0.3 ?
There is a new version 3.1.1 by Davidmueller13 which works perfectly :good:
You can have it HERE
You can have version 3.0.3 HERE

mangkon said:
Your problem (adoptable storage is encrypted) might be resolved if you place your ZIP into "the path of" your TWRP's backup folder.
Source: Google Search
Click to expand...
Click to collapse
I tried it but in recovery the folder appear empty.
Inviato dal mio SM-N9005 utilizzando Tapatalk

asusgarb said:
I tried it but in recovery the folder appear empty.
Click to expand...
Click to collapse
Sorry then, just wanted to help when I google and read on its implications, pros and cons.

Everything ok, thanks
I flashed your recovery starting from last 5.1.1 stock. With official 3.1.1.0 I had a loop and I couldn't enter into the recovery but with yours I solved all my issues, thanks. Now my P605 is working well.
Cheers

DO NOT USE the one on the TWRP website, the latest version is giving bootloop. Use this version 12.206 KB or the version 2.8.7.0 initially !

Hi,
Does anyone know if this would work on P600 (n1awifi)?

perapera said:
Hi,
Does anyone know if this would work on P600 (n1awifi)?
Click to expand...
Click to collapse
No ! This is for p605

Hi!
I flashed this with Odin to my p605 and I am getting the "no command" error. I'm in 5.1.1 stock.
I unticked "auto reboot" in Odin, turned off the tablet and tried to enter recovery but I get the "no command" every time!!
Any advice?
EDIT: My god I forgot to enable developer mode and USB debugging!! Argh. It's working now!

SOS !!!
I tried to upgrade TWRP (3.0.x) by flashing the OP's img inside TWRP. Now I get a bootloop: P605 tries to go to recovery, restarts after 1 sec. Can't boot to the system, can't get to download mode and Odin, can't get to recovery. What can I do ?
Luckily, after keeping the power+volume+home buttons for minutes (nothing seemed to be happening, I was getting a reboot every 1 sec after 1st logo and "Booting to recovering" message) and also, in my desperation, starting to press every button randomly I eventually managed to made it to download mode ! I re-downloaded twrp-3.1.1-0-lt03lte_20170712.tar and flashed through Odin at AP. Maybe my previous downloads (had downloaded img for TWRP, tar, and zip) were corrupt or misnamed. The androidfilehost mirrors were too slow, had to download with 10 kbps and had to retry many times to get a valid/verified file.
Everything seems ok now.

Israelleite said:
DO NOT USE the one on the TWRP website, the latest version is giving bootloop. Use this version 12.206 KB or the version 2.8.7.0 initially !
Click to expand...
Click to collapse
YOU DIDN´T READ THIS ?

Israelleite said:
YOU DIDN´T READ THIS ?
Click to expand...
Click to collapse
I read it but probably misrenamed the files and used the bad version instead or the androidfilehost download was corrupted or something.

Does this version save the backup to the external sd card?

Deep Nox said:
Does this version save the backup to the external sd card?
Click to expand...
Click to collapse
Hi,
Yes it does , if you ask it to do so

Hardware issue ?
Dear all,
I was on Oreo and wanted to go back to the nougat version that last was upated beginning of Dec.
I crooked up bc I wanted update first TWRP via the app and stupidly selected the tar.
When I then rebooted the tablet no longer started - unsurprisingly...
Ok - thought no prob as via odin I always can go back to another TWRP - i.e this one.
I no longer get a connection to the tablet - it is not recognised when I am in download mode.
-> cannot flash via odin..
Do I have a prob with the hardware or am I overlooking sth ?
The tablet says the following when in dwnload mode:
Odin mode (in Red)
Product name : SM-P605
Current binary: Custom
System Status: Custom
Knox warranty Void:0x1 (4) )
Qualcomm secure boot: Enable (CSB) - in Grey
AP SWREV: S2, T2, A2, A2, P2 - in Grey
Secure download: Enable - in blue
UDC: Start
and btw - I am doing this via a laptop and I also see a bit of a flickering -> simply not enough juice ?
Tx for any ideas what I might need to do differently ?

[RECOVERY][OFFICIAL] TWRP 3.5.2_9-0 [I9100]

Reserved
CHANGELOG
3.2.1-1
* MTP and ADB work
* Restored compatibility with SD cards formatted in FAT32, exFAT, and NTFS
3.2.1-2
* Fixed proper internal storage mounting in MTP

Reserved

Tried to install latest RR 20171229 and got failed to map file "sdcard0/RR-II-v5.8.5-20171229-I9100-Final.zip". And I have 2 internal storage showing in this twrp. Any explanation?

al5911 said:
Tried to install latest RR 20171229 and got failed to map file "sdcard0/RR-II-v5.8.5-20171229-I9100-Final.zip". And I have 2 internal storage showing in this twrp. Any explanation?
Click to expand...
Click to collapse
I may have overlooked a few permissions entries related to the partitions. Are both of those 2 internal storages labelled as sdcard0 or sdcard1 by any chance? Did you try flashing RR from an SD card or internal memory?
I will run another build in the next couple of hours and let you know when it's available.
In the meantime, on an unrelated matter, please consider flashing the latest bootloader and modem in my BL_CP folder. I know, both the BL and CP are relatively old even for this old phone, but I mixed and matched the most recent ones and put them in a single .tar file.
Edit: Updated files are up. I'd also suggest you re-flash the latest IsoRec-TWRP then this updated 3.2.1-0 version.

Nand write failed when trying to update bootloader and modem - I9100UHMSA_I9100XXMS2.tar with odin. I put the tar file in CP. Even tried putting the file in AP...sorry I'm just the end user here

al5911 said:
Nand write failed when trying to update bootloader and modem - I9100UHMSA_I9100XXMS2.tar with odin. I put the tar file in CP. Even tried putting the file in AP...sorry I'm just the end user here
Click to expand...
Click to collapse
It's my mistake to have linked the latest version of Odin in the OP :silly: The S2 is an old enough device that only older versions such as 3.07 are able to successfully flash anything. I've updated the link in the OP.

Since there has been no other feedback, does that mean the build under the link in the OP works?

ripee said:
Since there has been no other feedback, does that mean the build under the link in the OP works?
Click to expand...
Click to collapse
I'm going to test android oreo with this version and give feedback in a few hours

@ripee, I tried installing on the two methods explained, but it did not work. Would you like to create the zip image for installation or tar with zImage?

linusdan said:
@ripee, I tried installing on the two methods explained, but it did not work. Would you like to create the zip image for installation or tar with zImage?
Click to expand...
Click to collapse
I added the flashable zip to the OP. If this doesn't help, I'll try building with zImage.
Edit: Actually, I think I know the cause I just have to build the kernel with CONFIG_RD_LZMA=y, as described here.
I'll let you know when the new build is available, I'll upload an img, tar, and zip.

ripee said:
I added the flashable zip to the OP. If this doesn't help, I'll try building with zImage.
Edit: Actually, I think I know the cause I just have to build the kernel with CONFIG_RD_LZMA=y, as described here.
I'll let you know when the new build is available, I'll upload an img, tar, and zip.
Click to expand...
Click to collapse
I got install with the zip, however, when trying to install the ROM, this error appeared.
It also happened with ROMS nougat.

linusdan said:
I got install with the zip, however, when trying to install the ROM, this error appeared.
It also happened with ROMS nougat.
Click to expand...
Click to collapse
Ok, so it's unrelated to boot or recovery compression. Has to be the partition mapping. I'll figure it out eventually.

ripee said:
Ok, so it's unrelated to boot or recovery compression. Has to be the partition mapping. I'll figure it out eventually.
Click to expand...
Click to collapse
I think I discovered the possible cause:
The memory of my cell phone is divided with the gangster pit (1.5GB system + 6GB data + 512mb preload). Comparing this version with 3.1.0-0, I realized that with version 3.2.1-0 the other partition is treated as internal and may be causing problems when installing some custom ROM (it was to be treated as an external emulated card and identified such as sdcard0)

linusdan said:
I think I discovered the possible cause:
The memory of my cell phone is divided with the gangster pit (1.5GB system + 6GB data + 512mb preload). Comparing this version with 3.1.0-0, I realized that with version 3.2.1-0 the other partition is treated as internal and may be causing problems when installing some custom ROM (it was to be treated as an external emulated card and identified such as sdcard0)
Click to expand...
Click to collapse
Perhaps this is related to the problem?
Edit: I added the following line from the above commit to my system.prop:
Code:
ro.vold.primary_physical=1
All partitions are accounted for the same in my recovery.fstab and fstab.qcom files as in old TWRP device trees.
New build is under the link in the OP!

ripee said:
Perhaps this is related to the problem?
Edit: I added the following line from the above commit to my system.prop:
Code:
ro.vold.primary_physical=1
All partitions are accounted for the same in my recovery.fstab and fstab.qcom files as in old TWRP device trees.
New build is under the link in the OP!
Click to expand...
Click to collapse
ZIP and tar installations do not work.
The print error has disappeared! I installed Lineage 15.1 and it worked. I'll use it for a few days to test.
Now what confuses me is the naming of the sdcard0 partition that I saw on your github in the fstab file. When selecting in TWRP, the person is in doubt about which partition to choose. My suggestion is to rename as is as Non-Emulated Storage, format as EXT4 and add preload support, as in the link:
https://github.com/rINanDO/android_device_samsung_i9100_emu_twrp/blob/cm-14.1/ramdisk/twrp.fstab
I use these link settings to support TWRP in Slim7 builds and it behaves very well
LineageOS also already uses this setting by default.

linusdan said:
Perhaps this is related to the problem?
Edit: I added the following line from the above commit to my system.prop:
ZIP and tar installations do not work.
The print error has disappeared! I installed Lineage 15.1 and it worked. I'll use it for a few days to test.
Now what confuses me is the naming of the sdcard0 partition that I saw on your github in the fstab file. When selecting in TWRP, the person is in doubt about which partition to choose. My suggestion is to rename as is as Non-Emulated Storage, format as EXT4 and add preload support, as in the link:
https://github.com/rINanDO/android_device_samsung_i9100_emu_twrp/blob/cm-14.1/ramdisk/twrp.fstab
I use these link settings to support TWRP in Slim7 builds and it behaves very well
LineageOS also already uses this setting by default.
Click to expand...
Click to collapse
Ok, I will make this change and let you know when it's ready. You need Odin 3.07 and use the PDA button to flash TWRP. You can also use the PDA button for the bootloader and modem.

I made those changes in my recovery.fstab and uploaded new images. You can try them now.

ripee said:
Ok, I will make this change and let you know when it's ready. You need Odin 3.07 and use the PDA button to flash TWRP. You can also use the PDA button for the bootloader and modem.
Click to expand...
Click to collapse
I did this with that version. Did not work.
ripee said:
I made those changes in my recovery.fstab and uploaded new images. You can try them now.
Click to expand...
Click to collapse
I'll test
I'm going to use it for a few days and I'll tell you how the build behaved :good:

linusdan said:
I did this with that version. Did not work.
I'll test
I'm going to use it for a few days and I'll tell you how the build behaved :good:
Click to expand...
Click to collapse
About flashing with Odin, have you tried a more recent version of it? Normally older phones require older Odin, and 3.07 has always worked for me for older TWRPs.
Does the zip image I posted work from within an older TWRP, or an IsoRec TWRP?
What about flashing the IMG file from within an IsoRec TWRP?
Have any of the old official TWRP tar or img files flashed successfully with Odin or within recovery?

[RECOVERY][UNOFFICIAL] TWRP for Galaxy S10 Lite (Snapdragon)

Changelog:
29.11.2021 - Update to TWRP 3.6.0
- Add Symlinked dynamic partitions to fstab
- Update multidisabler
- fstab clean up
03.03.2021 - Update to latest TWRP source
- Add terminal multidisabler script
- fstab cleanup.
01.01.2021 - Update TWRP to 3.5.0
- Fix fastbootd
- Builds for Q and R.
21.11.2020 - Initial Release.

Everything work perfect. Thank You

Great, thank you.

@afaneh92 you're here too lol

fbs said:
@afaneh92 you're here too lol
Click to expand...
Click to collapse
Yes, Im taking a rest from S5 lol.

Do all versions have snapdragons and is it free bootloader unlock? Im hoping it works the same for the G770U as the G770f right. Im looking at buying one and I have to have root and twrp lol

Moderator Information,
Thread has been cleaned. Selling unlock services through XDA is not allowed.

Stephen said:
Moderator Information,
Thread has been cleaned. Selling unlock services through XDA is not allowed.
Click to expand...
Click to collapse
How is it possible I dont understand if samsung doesnt allow it officially how does that work?

Nice work on the recovery. This phone is tits its just as fast as my S6 tablet. Which partitions should I back up? Im not sure theres so many It wont back up modem.

Techguy777 said:
Nice work on the recovery. This phone is tits its just as fast as my S6 tablet. Which partitions should I back up? Im not sure theres so many It wont back up modem.
Click to expand...
Click to collapse
I though you wont do unlock your device lol.

Never mind it will back it up if I just backup modem by itself. What are the main ones for bootloops? Im guessing data, boot, super img with all the partitions inside.
The way I rooted was unlocked bootloader, flashed the dbmeta dummy file, had magisk canary on a ssd drive with the twrp and samsung disabler. After I flashed twrp I boot into recovery flashed the disabler and formate data yes and than I just flash magisk v21.1 zip and rebooted. Now I have check adb apps unchecked in developer options as migrate says his app works better that way so I dont know if it made a difference or not.

afaneh92 said:
I though you wont do unlock your device lol.
Click to expand...
Click to collapse
I did the easy way. Im a broke bum it was a gift I dont have a 150 dollars so I went with the 770f model. If I had to I would have.

What we need now is a permissive kernel.

Techguy777 said:
What we need now is a permissive kernel.
Click to expand...
Click to collapse
You can use the kernel in TWRP its permissive. I dont have free time to support kernels. but you can build it yourself.
GitHub - mohammad92/android_kernel_samsung_r5q: Kernel source for the Samsung Galaxy S10 Lite (Snapdragon)
Kernel source for the Samsung Galaxy S10 Lite (Snapdragon) - GitHub - mohammad92/android_kernel_samsung_r5q: Kernel source for the Samsung Galaxy S10 Lite (Snapdragon)
github.com
there is a build menu, easy way.

afaneh92 said:
You can use the kernel in TWRP its permissive. I dont have free time to support kernels. but you can build it yourself.
GitHub - mohammad92/android_kernel_samsung_r5q: Kernel source for the Samsung Galaxy S10 Lite (Snapdragon)
Kernel source for the Samsung Galaxy S10 Lite (Snapdragon) - GitHub - mohammad92/android_kernel_samsung_r5q: Kernel source for the Samsung Galaxy S10 Lite (Snapdragon)
github.com
there is a build menu, easy way.
Click to expand...
Click to collapse
I know I was thinking of trying it, ive built Lineage and a couple of roms for the S2 tablet, Nexus 6, and Ive tried twrp but never kernel. I have my build environment setup on ubuntu 14 on another hard drive but I have a cheap TLC hdmi tv and the resolution messed up and now everything is out of view and I can't even afford a 100 used monitor so its been put on hold for 2 years now.
When you restore a backup which partitions do you restore?

Techguy777 said:
I know I was thinking of trying it, ive built Lineage and a couple of roms for the S2 tablet, Nexus 6, and Ive tried twrp but never kernel. I have my build environment setup on ubuntu 14 on another hard drive but I have a cheap TLC hdmi tv and the resolution messed up and now everything is out of view and I can't even afford a 100 used monitor so its been put on hold for 2 years now.
When you restore a backup which partitions do you restore?
Click to expand...
Click to collapse
all but read only, which is modem.

afaneh92 said:
all but read only, which is modem.
Click to expand...
Click to collapse
I was looking into twrp wipe and it doesn't show system? So how do I flash lineage. Its weird because everything is different and I can't find instructions of all of it anywhere note in the note 20 twrp page nowhere.

afaneh92 said:
all but read only, which is modem.
Click to expand...
Click to collapse
Hey android 11 one ui 3.0 just dropped for the s10 lite.

Techguy777 said:
Hey android 11 one ui 3.0 just dropped for the s10 lite.
Click to expand...
Click to collapse
Yes I know long time ago, cant update twrp until we got kernel source.

Techguy777 said:
I was looking into twrp wipe and it doesn't show system? So how do I flash lineage. Its weird because everything is different and I can't find instructions of all of it anywhere note in the note 20 twrp page nowhere.
Click to expand...
Click to collapse
There no system wipe, this is dynamic partition device. System, vendor, product and odm are part of super partition. Do some search.

[RECOVERY][OFFICIAL] TWRP 3.6.0_9-0 [ T03G N7100 T0LTE N7105]

The new builds are online!

Update 16.06.2021:
Brought support for GSI flash & reused old HIDDEN partition as vendor.
Brought support for encrypted /data partition.

Hi, I'm unable to verify any of your new builds with PGP, is there a chance you could do something about that?
Code:
C:\Mike-Data\Android\N2>gpg --verify twrp-3.5.2_9-1-t0lte.img.tar.asc twrp-3.5.2_9-1-t0lte.img.tar
gpg: Signature made 04/20/21 16:22:48 Central Europe Daylight Time
gpg: using RSA key 95707D42307C9D41D09BF7091D8597D7891A43DF
gpg: BAD signature from "TeamWin <[email protected]>" [full]

Mike4 said:
Hi, I'm unable to verify any of your new builds with PGP, is there a chance you could do something about that?
Code:
C:\Mike-Data\Android\N2>gpg --verify twrp-3.5.2_9-1-t0lte.img.tar.asc twrp-3.5.2_9-1-t0lte.img.tar
gpg: Signature made 04/20/21 16:22:48 Central Europe Daylight Time
gpg: using RSA key 95707D42307C9D41D09BF7091D8597D7891A43DF
gpg: BAD signature from "TeamWin <[email protected]>" [full]
Click to expand...
Click to collapse
I have no idea, but I will check this.

Mike4 said:
Hi, I'm unable to verify any of your new builds with PGP, is there a chance you could do something about that?
Click to expand...
Click to collapse
I've asked bigbif and here's his answere:
bigbif:
sometimes the GPG generated is borked I will regenerate it tonight
Click to expand...
Click to collapse

Update 10.12.2021:
Removed bash to bring TWRP 3.6.0_9 up

html6405 said:
Update 16.06.2021:
Brought support for GSI flash & reused old HIDDEN partition as vendor.
Brought support for encrypted /data partition.
Click to expand...
Click to collapse
What kinds of GSI can be flashed ? A ? AB ?

Concept48 said:
What kinds of GSI can be flashed ? A ? AB ?
Click to expand...
Click to collapse
These devices only can support A partition layout, but they are covered in ab script, so they would be called phhgsi_a64_ab for example.
But, there is only one test GSI available from myself so far.
All GSI builders would need to apply some exynos4 specific patches, so this project only could grow if I would get some support.
(Tested AOSP and Bliss as GSI's so far on exynos4 devices, including i9300, except n7100)

html6405 said:
These devices only can support A partition layout, but they are covered in ab script, so they would be called phhgsi_a64_ab for example.
But, there is only one test GSI available from myself so far.
All GSI builders would need to apply some exynos4 specific patches, so this project only could grow if I would get some support.
(Tested AOSP and Bliss as GSI's so far on exynos4 devices, including i9300, except n7100)
Click to expand...
Click to collapse
Wow that is soooo amazing HTML .. Of course I will do a project on that GSI , jCan you link me up with the GSI ,

html6405 said:
The new builds are online!
Click to expand...
Click to collapse
I,m done bro , rendering then upload - Midnight Show !! It runs better then expected , i,m very happy !

Concept48 said:
It runs better then expected , i,m very happy !
Click to expand...
Click to collapse
I've watched your video today, thx for this and btw,
the video recording seems to be corrupted through gCam, I've tested open camera and it worked fine .
But the ROM is for sure not finished.
Concept48 said:
Wow that is soooo amazing HTML .. Of course I will do a project on that GSI , jCan you link me up with the GSI ,
Click to expand...
Click to collapse
[GSI][11][ EXYNOS4 SMDK4412 ][N8000, N801X, N8020, I9300, N5100, N51XX, N7100, ...][ALPHA] [EOL]
Here you will find my exynos4 compatible GSI's. This work is based on the magic of @phhusson, so thank you very much for this. Don't forget, that you need an treblelized ROM to support this. Do you like my work? Than you can simply hit...
forum.xda-developers.com
Here you can find it, but it's untested with the n7100, you need LOS18.1 as basis. (The boot and treblelized vendor image)
But with these basic steps, we would be able to create many A11 ROM's and share them with the community and only the system.img flash is necessary to change the ROM.
And the best thing would be, one image for all exynos 4 devices .
But this is in a real early stage, I have not the time to concentrate on all of my projects yet.

html6405 said:
I've watched your video today, thx for this and btw,
the video recording seems to be corrupted through gCam, I've tested open camera and it worked fine .
But the ROM is for sure not finished.
[GSI][11][ EXYNOS4 SMDK4412 ][N8000, N801X, N8020, I9300, N5100, N51XX, N7100, ...][ALPHA] [EOL]
Here you will find my exynos4 compatible GSI's. This work is based on the magic of @phhusson, so thank you very much for this. Don't forget, that you need an treblelized ROM to support this. Do you like my work? Than you can simply hit...
forum.xda-developers.com
Here you can find it, but it's untested with the n7100, you need LOS18.1 as basis. (The boot and treblelized vendor image)
But with these basic steps, we would be able to create many A11 ROM's and share them with the community and only the system.img flash is necessary to change the ROM.
And the best thing would be, one image for all exynos 4 devices .
But this is in a real early stage, I have not the time to concentrate on all of my projects yet.
Click to expand...
Click to collapse
That's what I saw , but hey I dont care this is first build ever ,, Open Camera works perfectly ,. Some random reboots after trying certain apps , but try them again then they function , I,m sure build 2 will be better - Thanks so much for your amazing work ..and on this last day of the YEAR I wish you all that's good in the new year to come ..Bless you Brother !!

Better Mobile App

welcome