[RECOVERY][OFFICIAL] TWRP 3.5.2_9-0 [I9100]
- Thread starter ripee
- Start date
TWRP 3.2.3.0
Hi all.
I have recently upgraded from ICS to TWRP 3.1.0.0 / Nougat 14.1. (it's an old spare phone) and all was well. I thought I'd try TWRP 3.2.3.0 / Oreo 15.1.
This is where I'm now really stuck. I had to flash the 15.1 zip first, go back and flash TWRP 3.2.3.0. I then flash 15.1 again and get a
"failed to map file'/sdcard1/ lineage-15" and "Error installing zip file" etc.
I then tried flashing the rom boot image via TWRP which in itself was successful, the install still brought up the same error.
I then tried reverting to 14.1 via TWRP 3.2.3.0 and the failed map error happened again.
Has anyone else come across this and found a solution?
Many thanks
Faff
Hi all.
I have recently upgraded from ICS to TWRP 3.1.0.0 / Nougat 14.1. (it's an old spare phone) and all was well. I thought I'd try TWRP 3.2.3.0 / Oreo 15.1.
This is where I'm now really stuck. I had to flash the 15.1 zip first, go back and flash TWRP 3.2.3.0. I then flash 15.1 again and get a
"failed to map file'/sdcard1/ lineage-15" and "Error installing zip file" etc.
I then tried flashing the rom boot image via TWRP which in itself was successful, the install still brought up the same error.
I then tried reverting to 14.1 via TWRP 3.2.3.0 and the failed map error happened again.
Has anyone else come across this and found a solution?
Many thanks
Faff
Last edited:
To quote the developer of LOS15.1: "I'm currently using TWRP 3.0.2 on my dev-phone to install the ROM. Other versions of TWRP I haven't tried." https://xdaforums.com/galaxy-s2/development-derivatives/rom-lineageos-15-0-t3674567/post73830198Flashed TWRP down to 3.2.1.0 and 15.1 flashes and boots 1st time.
It's always a good idea to read the op carefully...
Thanks for the advice guest4711. I have seen seen this advice many times in other posts but I had read "you need TWRP 3.2.3.0 for Oreo 15.1 install" somewhere and it must have stuck in my mind.
Faff:good:
Faff:good:
Hi @Faffendecker,
You are not alone, I've read that too... But there appears to be little to no info, backing this statement up? So I guess TWRP 3.2.3 isn't needed after all?? Norr is it clear, if it supersedes all previous, or if older versions are still required??
As much as I am grateful for the continued development of TWRP and all things... I think I'll stick to the older version, until I hear otherwise....
Cheers, Lister
You are not alone, I've read that too... But there appears to be little to no info, backing this statement up? So I guess TWRP 3.2.3 isn't needed after all?? Norr is it clear, if it supersedes all previous, or if older versions are still required??
As much as I am grateful for the continued development of TWRP and all things... I think I'll stick to the older version, until I hear otherwise....
Cheers, Lister
Hi Lister.
Agreed there is very little inf on what versions of TWRP cover which OSes. Also, it is all to easy to become misinformed when trying to find out.
A good reason not to use the web when you have health worries!
Faff.
Agreed there is very little inf on what versions of TWRP cover which OSes. Also, it is all to easy to become misinformed when trying to find out.
A good reason not to use the web when you have health worries!
Faff.
3.2.1, 3.2.2 and 3.2.3 don't work. 3.1.0 is the latest working version.
You have to flash an IsoRec compatible kernel image separately, ie. boot.img, then all versions above 3.1 will work.
Last edited:
I have LOS 14.1 installed. Should this be enough to allow 3.2.3 to work?
For reference I had CM13.0 installed and that didn't let me use >=3.2.1.
Last edited:
14.1's kernel is enough for twrp 3.2.3-0 to install properly, and 14.1 will work with 3.2.3-0, ie. flashing, backing up, restoring, etc.
can not boot into twrp recovery. followed the instructions on wiki lineageos
download mode,
installed zadiag.exe driver
using heimdall for flashing twrp
"heimdall flash --RECOVERY twrp-x.x.x-x-i9100.img --no-reboot"
"Recovery upload successful" ending session
after that i boot into recovery mode by pressing "button up" "power" "home"
It boots into recovery, BUT there is NO twrp. It is the standard android recovery?????
Any help?
download mode,
installed zadiag.exe driver
using heimdall for flashing twrp
"heimdall flash --RECOVERY twrp-x.x.x-x-i9100.img --no-reboot"
"Recovery upload successful" ending session
after that i boot into recovery mode by pressing "button up" "power" "home"
It boots into recovery, BUT there is NO twrp. It is the standard android recovery?????
Any help?
First flash one of the older IsoRec twrps, then the boot.img of your rom, then the official twrp. You only need to jump through all these hoops once, then you can update twrp and your rom normally.
Hi Ripee got one question, theorically there should be a way to keep an isorec recovery on it, while flashing 16.1,
Two days ago I needed to move files from external to internal storage, but on cell it's called gti9100 or smthg like that, on twrp was called ... dunno,
Didn't really know where i could copy my files,
Gone flashing a twrp updated img and same prob as some others,
Ended up with Los Unnof 16.1 on i9100 and an old recovery.
I could just adb push a recovery with Heimdall Suite,
But i dunno if internal will be accessible.
I remember you or smeone else saying there was a specific twrp available.
So one question:
Is there such a recovery somewhere?
Maybe on AndroidHost?
Edit : Will just follow your advice, thanks
Oxydeme
Two days ago I needed to move files from external to internal storage, but on cell it's called gti9100 or smthg like that, on twrp was called ... dunno,
Didn't really know where i could copy my files,
Gone flashing a twrp updated img and same prob as some others,
Ended up with Los Unnof 16.1 on i9100 and an old recovery.
I could just adb push a recovery with Heimdall Suite,
But i dunno if internal will be accessible.
I remember you or smeone else saying there was a specific twrp available.
So one question:
Is there such a recovery somewhere?
Maybe on AndroidHost?
Edit : Will just follow your advice, thanks
Oxydeme
Last edited:
Thank you.
Is there a step by step tutorial for dummies?
Because otherwise i would have a lot of questions :-/
(which isorec, where to get it, how to Flash it (which program, what to type, click), where to get boot.img, how to Flash it. how to save the original Rom file before?)
Can you please read the first post in this thread. Click on the link in the sentence mentioning IsoRec and read that thread as well.
Hello.
Sorry, I'm not an IT specialist and I do not have a PC. I'm just Galaxy S2 user for a long time.
How I can install any working version of TWRP recovery to my i9100 remaining with the latest original Samsung's firmware, which I use currently because it is the reliable firmware?
Please, if it is possible then provide detailed step by step instruction.
I have rooted my smartphone. I can use Mobile Odin on it. I even got TWRP 3.1.0 on it via Philz recovery but after that I can reboot the device into TWRP recovery only but with TWRP 3.1.0 it does not reboot to normal functioning as a smartphone with Samsung's latest firmware Android 4.1.2.
What can I do?
Please, help.
May if I upload here the official Samsung's firmware, which I use, then someone can modify it adding there TWRP support and then I will be flashing it via Mobile Odin for get TWRP with original Samsung's firmware?
Sorry, I'm not an IT specialist and I do not have a PC. I'm just Galaxy S2 user for a long time.
How I can install any working version of TWRP recovery to my i9100 remaining with the latest original Samsung's firmware, which I use currently because it is the reliable firmware?
Please, if it is possible then provide detailed step by step instruction.
I have rooted my smartphone. I can use Mobile Odin on it. I even got TWRP 3.1.0 on it via Philz recovery but after that I can reboot the device into TWRP recovery only but with TWRP 3.1.0 it does not reboot to normal functioning as a smartphone with Samsung's latest firmware Android 4.1.2.
What can I do?
Please, help.
May if I upload here the official Samsung's firmware, which I use, then someone can modify it adding there TWRP support and then I will be flashing it via Mobile Odin for get TWRP with original Samsung's firmware?
Last edited:
I recommend to install easy Philz touch recovery v4.88 and do a custom backup of everything on your smartphone via it to an external microSD. It will take about 30 minutes.
When you will want go back then just easy install same Philz again, choose 'Restore from custom backups', select your backup file and restore.
This easy old way did saved my device few times already and I recommend it to everyone.
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
23
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
Code:* [B][U]Your warranty is now void.[/U][/B] * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or your 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 me for messing up your device, I will laugh at you.
This phone does not have a separate recovery partition, only a virtual recovery partition in the boot (kernel) partition. After flashing an IsoRec kernel and recovery, you will then be able to flash all non-IsoRec kernels and recoveries (such as this official TWRP) without any problems (see instructions below).Q: Whenever I try flashing any ROM, I get a Fail to map file error.
More information about IsoRec can be found in the [MOD] IsoRec: Isolated Recovery for the Galaxy S2 Family thread, courtesy of Lanchon.
FREQUENTLY ASKED QUESTIONS
(Please read them BEFORE posting anything in the thread!)
A: This error appears whenever you try to flash a rom zip file without first flashing the boot.img file from the rom zip file before attempting to flash the rom itself (see instructions below).
Q: How do I flash anything if TWRP displays an error that it cannot mount any partition?
A: This error appears after re-PITing your phone's internal storage but without re-formatting the partitions:
1. In the main menu, tap "Wipe" then "Advanced Wipe".
2. Perform the following steps for each of these partitions individually one by one: System, Internal Storage, Data:
a) Tap "Repair or Change File System".
b) Tap "ext4".
c) Move the slider to the right to format.
3. Follow the flashing instructions below.
Heimdall
- Glass Echidna
TWRP for Samsung Galaxy S II (International)
How to flash the latest official TWRP when coming from stock or another custom recovery1. Flash an IsoRec recovery and kernel, which can be found here.
2. Extract the boot.img file (kernel) from the zip file of the ROM you wish to flash.
3. Copy both the boot.img file and the latest official TWRP onto your phone or SD card.
3. Boot into the IsoRec TWRP, regardless of which version it is.
4. In the main menu, tap on "Install" then "Install Image".
5. Flash the boot.img file by selecting the "Boot" radio button.
6. Flash the latest official TWRP by selecting the "Recovery" radio button.
7. Reboot into Recovery. You should now be on the latest official TWRP.
8. Proceed with flashing the ROM and GApps package, either clean or dirty.
You will ONLY need to follow the above steps when flashing the official TWRP when you are coming from stock or another custom recovery!
Changelog
- See post #2.
Bugs
- You tell me!
Credits
- arnab, Lanchon, the.gangster, rINanDO, and every other open source developer and user who contributes directly or indirectly to the TWRP community in the development of and in providing feedback for the i9100.
Sources
- arnab
- Lanchon
- rINanDO
- i9100 repository
- TWRP repository
XDA:DevDB Information
TWRP 3.5.2_9-0, ROM for the Samsung Galaxy S II
Contributors
ripee
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Current Stable Version: 3.5.2_9-0
Stable Release Date: 2021-04-06
Created 2018-01-25
Last Updated 2022-12-0912Progress update
I managed to get it to flash and boot. If you wipe all partitions except External storage and USB-OTG, you will see both Internal and External storage in their proper partition sizes.
But I'm still working on "Failed to map file".
Edit: after wiping all partitions except external storage and usb-otg, twrp's settings finally persist after rebooting back into recovery.
Edit 2: it seems that Open GApps flash normally, but neither official nor unofficial LineageOS 14.1 does back to it...7The problem may lie in re-PITting
I've taken another look at my logs and I'm going to go back to square one, re-flash stock, then flash TWRP again, but this time without re-pitting my system partition. Lineage should be small enough to flash, so we'll see if the maximum allowable file size that twrp interprets that can be flashed is determined by re-PITting or if twrp determines what can fit some other way.6I re-built my device tree again, this time adapting from rINanDO's cm-14.1-emu branch. The SD card and the TWRP folder in internal storage mount fine, allowing for flashing from both internal and external storage, which TWRP refers to as "Micro SD card".
