Related
I worked a bit on FOTA bootloader, and i'd like to share some of my work.
Few words about Fota in general
I think lot of people here don't understand fully how Fota work, and this may prevent a lot of questions, please read it.
We use Fota in Badadroid project as a bootloader, it's the piece of code loading modem and android kernel in RAM, and starting android kernel.
Fota decide what key combination does, which system is to be launched if no key are pressed, and where kernel file is searched.
Fota doesn't care if a kernel is Nand or SD or Loop. It just search for a file with a certain name, load it and launch the execution of its code.
This Fota is compatible with ALL roms and ALL versions (nand, SD, loop).
About keys : power key isn't important for Fota, the only function power key have is to power on the device. Once device is powered on (you can use power key but also plug charger or use reboot function), fota will check for other keys. So if i write "Recovery mode : home key", you'll have to press home key and then manage to power on the device, it won't boot if you just press home key.
About this Fota
This Fota is able to load two different kernel. It can be used to load two rom (one Nand and one SD, one Loop and one SD) or if you have a "test" kernel.
If you have only one rom or one kernel, no problem, it will work the same, all the stuff related to second kernel won't work, that's all.
This Fota doesn't allow two Nand rom or two SD rom.
This Fota provide a default "Silent boot" displaying default Bada bootscreen (no more ugly ASCII), however boot is slow so it will be displayed for maybe 15 seconds. If there is an error with kernel, ugly ASCII will appear and tell you there is something wrong.
This Fota also provide an "interactive" mode (or Noob mode). If you press any keys during boot (home, call or volume), it will boot in interactive mode. It's simple and you'll understand fast how it work. Control are vol + and vol - and home key to select.
It also support usual key combination, if you press keys to boot recovery, and when white screen appear you stop pressing, it will boot "interactive mode" and after few seconds boot recovery IF no keys are pressed. If you press sth at this moment, interactive mode will be active.
Test it, you'll understand.
This Fota also boot faster in recovery (no Modem init, who need modem in recovery ?)
However, battery reading won't work anymore in recovery because of that, so don't spend hours in recovery mode.
README
First kernel : boot.img on SDcard
Second kernel : boot_2.img on SDcard
Boot 1st kernel : default
Boot recovery 1st kernel : vol up
Boot 2nd kernel : home
Boot recovery 2nd kernel : vol up + home
Boot bada : call
Yeah, you read well, kernel must be named boot.img and not zImage.
If your rom came with a file named zImage, just rename it boot.img it will work the same. I could have chosen to load a file named MyLittleKernel. Name doesn't matter, only file content is important.
And all the same, rename the second kernel (for your secondary rom, test kernel...) boot_2.img.
All the kernels must be placed on SDCARD
REQUIREMENTS
Bada 2.0
Android Bootfiles (if you have an android rom on your phone, you have it, else, see in badadroid thread to download it.
Bugs
Bada boot doesn't work in interactive mode, it's stuck after Bada bootanimation, maybe someone know why.
Just boot with call key pressed to boot bada.
Please report if there is any other bugs.
Thanks
Big thanks to all Fota contributors, Rebellos, Mijoma, Tigrouzen, ihavenick, Volk204 and all the others i forgot
Sources
My github here, see branch sd.
Downloads
Fixed dual boot broken by little mistake (20/07/2014) :
Mega (s8500 & s8530)
Alternative links :Google Drive
Just flash it with Multiloader
WoW.. Awesome BenzoX.. Congrats for ur work.. Thank u so much..
Regards,
Abhijeet....
Any other links other than mega..??
abhijeet1331 said:
Any other links other than mega..??
Click to expand...
Click to collapse
Updated (Google Drive)
BenzoX said:
Updated (Google Drive)
Click to expand...
Click to collapse
Oh thanks man..
Duude.
Bada+ Android LOOP + Android on SD - It work
Thaaankss
bada is not booting ..
is it possible to boot only bada by using this fota in s8530 ??
when i try to boot bada using press call button ...it won't boot
if it's work then i will boot also android ....but i need bada.
any suggestion...plz
thanks in advanced..
mishail said:
is it possible to boot only bada by using this fota in s8530 ??
when i try to boot bada using press call button ...it won't boot
if it's work then i will boot also android ....but i need bada.
any suggestion...plz
thanks in advanced..
Click to expand...
Click to collapse
For me bada boot work well if i press call key. Not from menu (i have s8530 too).
bada not boot proper
BenzoX said:
For me bada boot work well if i press call key. Not from menu (i have s8530 too).
Click to expand...
Click to collapse
Hi , Benzox
when i boot bada , screen display horrible line with different color (like my bada is crashed).
is it booting normal ??. what should i do. I am using CFW 10.1 Turko
thanks for giving answer ..
mishail said:
Hi , Benzox
when i boot bada , screen display horrible line with different color (like my bada is crashed).
it's booting normal. what should i do.
thanks for giving answer ..
Click to expand...
Click to collapse
I think that's because you have/had a Nand rom installed. Just flash bada (not Fota file) and it will work (you'll loose your nand rom thought)
bada is not booting.
BenzoX said:
I think that's because you have/had a Nand rom installed. Just flash bada (not Fota file) and it will work (you'll loose your nand rom thought)
Click to expand...
Click to collapse
Hi Benzox ,
When u write about this fota like " It can be used to load two rom (one Nand and one SD, one Loop and one SD)" .
So i thought i boot two OS ( bada & nand ) while flash my bada 2.0 with this new fota file.
is it not possible to load Nand & Bada alternative ?
Thanks in advanced.
mishail said:
Hi Benzox ,
When u write about this fota like " It can be used to load two rom (one Nand and one SD, one Loop and one SD)" .
So i thought i boot two OS ( bada & nand ) while flash my bada 2.0 with this new fota file.
is it not possible to load Nand & Bada alternative ?
Thanks in advanced.
Click to expand...
Click to collapse
Nand format and install on nand memory, bada is installed on nand memory...
You need Loop rom (such as badadroid) if you want both to be on internal. memory.
I can allow two kernel but i don't know how to make partitions and storage space appear from nowhere
Questions ...
I want to install two android roms NAND and SD
What do I install first nand ram or rom SD?
The reason for my question is that when a rom on the SD card installed to do partition SD and lost all the contents of the SD.
If installation nand rom first
And after install the second rom in sd
Does the second rom could not delete the first installation nand?
I want to install nand rom and sd rom but not in what order I have to do
I do not want a rom overwrite the other rom because the two are installed in the SD
tofifo said:
Questions ...
I want to install two android roms NAND and SD
What do I install first nand ram or rom SD?
The reason for my question is that when a rom on the SD card installed to do partition SD and lost all the contents of the SD.
If installation nand rom first
And after install the second rom in sd
Does the second rom could not delete the first installation nand?
I want to install nand rom and sd rom but not in what order I have to do
I do not want a rom overwrite the other rom because the two are installed in the SD
Click to expand...
Click to collapse
Nand rom partition Nand (and delete it's content)
SD rom partition SDcard (and delete its content)
A nand rom will never overwrite a SD rom and vice versa, whatever fota you use.
Order doesn't matter.
Of course if you do Nand rom first you'll have to put its kernel on SD again.
You can't install two rom on SD, nand rom is installed on nand (internal memory) and sd rom is installed on SD.
Only kernel is on SD for both rom.
@BenzoX i forgot your codes but if you want to boot from interactive mode to bada mode i remember you must turn on mmu and disable modem (its opens again )
ihavenick said:
@BenzoX i forgot your codes but if you want to boot from interactive mode to bada mode i remember you must turn on mmu and disable modem (its opens again )
Click to expand...
Click to collapse
But in my code Modem init and mmu is called only after the "return rm_BL3 (which is the signal to start bada if i understood well)
Only thing made from the start of Fota.c are
Code:
int mmuctrl = MemMMUCacheEnable(gMMUL1PageTable, 1);
disp_FOTA_Init();
__PfsNandInit();
__PfsMassInit();
MemoryCardMount();
Rest is only displaying and setting some variable used only in Fota.c
I must be doing something wrong
If I knew cuel is my error.... not would have error haha
I installed a rom sd using the SD kernel.
I installed a rom nand using the nand kernel.
But the fota of menu always starts the same rom both when select kernel 1 o when select kernel 2
I have noticed one thing, we make a sd installation or nand installation the folder Android always appears on the sd card.
I see it almost impossible to install two android roms even if one is nand and the other sd because the folder Android always overwrite rom to another rom
tofifo said:
I must be doing something wrong
If I knew cuel is my error.... not would have error haha
I installed a rom sd using the SD kernel.
I installed a rom nand using the nand kernel.
But the fota of menu always starts the same rom both when select kernel 1 o when select kernel 2
I have noticed one thing, we make a sd installation or nand installation the folder Android always appears on the sd card.
I see it almost impossible to install two android roms even if one is nand and the other sd because the folder Android always overwrite rom to another rom
Click to expand...
Click to collapse
If it start the same rom, it's a kernel for same type (SD/Nand)
Take your kernel for SD and name it boot.img, take your kernel for Nand and name it boot_2.img (or vice versa). Put both on sdcard.
I'll test again my Fota but i'm almost sure it work (i did small modification and haven't tested both boot, but it should work)
This folder is not "essential" and distinctive to both rom.
Only issue may be if you have different version of the same apps on both rom, or if you use same apps on both rom. In this case (and only IF apps data are stored on SD, which is a minority), thing may be a bit confused.
nice.. good job.. this is what im waiting for.. something that will replace ugly ASCII on boot.. got some questions though,.
i have bada installed with sd rom and sd kernel installed on a partitioned sd card.. so my questions are..
1) can i install 3 OS?.. 1 bada(call) on nand, 1 android sd (end) and 1 android nand/loop (middle) on nand again?..
2) so if i put ALL kernels in sdcard by just renaming it.. what about the 2 roms, both in sd card as well?.. how will it know which rom the kernel will boot if same on sd card?
3) how long does the new boot take?.. can u show some screenshot or video?
4) what rom and kernel are u currently using?
again.. thank u for this fota!
BenzoX said:
If it start the same rom, it's a kernel for same type (SD/Nand)
Take your kernel for SD and name it boot.img, take your kernel for Nand and name it boot_2.img (or vice versa). Put both on sdcard.
I'll test again my Fota but i'm almost sure it work (i did small modification and haven't tested both boot, but it should work)
This folder is not "essential" and distinctive to both rom.
Only issue may be if you have different version of the same apps on both rom, or if you use same apps on both rom. In this case (and only IF apps data are stored on SD, which is a minority), thing may be a bit confused.
Click to expand...
Click to collapse
I've the 2 kernels renamed boot.img and boot_2.img
But I noticed that only detects one of the kernels
When you start the menu fota options
KERNEL 1
KERNEL 2
No matter which you select because it always opens the same kernel
Do not know if that will be a mistake, it's a question is not affirmation
This is a CyanogenMod 12.1 ROM for the Exynos3470 based Samsung Galaxy Tab 4 7.0 LTE (T235/T235Y).
DO NOT USE IT FOR T230(NU)/T231 OR YOU WILL BRICK YOUR DEVICE
Although T235 and T230(NU)/T231 (T230:WiFi / T231:3G) share the "Galaxy Tab 4 7.0" name they are not related in terms of hardware due to the different SoCs used (Samsung Exynos3470 vs. Marvell PXA1088).
Hence please do not ask for support or ROMs for the T230(NU)/T231.
Working features
Receiving and making calls
Hardware sensors (Acceleration)
Audio
Bluetooth
Wifi
HW accelerated GUI
MTP storage
GPS
USB-OTG (Mass-Storage, Keyboard, Mouse working, USB-Audio untested)
Camera (pictures+video: Back+Front)
Non-working features:
SELinux
Known issues:
See the Bug Report section of this thread
Disclaimer:
You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
Applications that use KNOX (e.g. "Private Mode") might not work anymore when returning to the stock ROM, as the device is regarded as compromised. Do not flash this ROM if you need those applications.
The image is only for Tab 4 7.0 SM-T235 and SM-T235Y (Exynos)
It might be instable, crash your device, drain your battery, or even might damage your smartphone
Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
Click to expand...
Click to collapse
Before you start:
Backup your data, like call history, contacts, sms, WhatsApp messages, favourite app settings that are on internal and external sd (by using Titanium Backup or other apps available on PlayStore). At least all internal data will be lost in any case. If you have bad luck you might also loose data from your external sd card.
Download:
Odin3-v1.85
TWRP 2.8.7.0 recovery image [09/08/2015] (AndroidFileHost Mirror)
CM 12.1 ROM (AndroidFileHost Mirror)
Google Apps (contains Google Play, ...) for Android 5.1.1 from Jajb (Recommended) or the one that suits you best from Consolidated GApps.
Install recovery:
Reboot your device into Odin mode: turn off your device, then press Volume-Down + Home + Power button at the same time and release them.
Confirm the following warning message with the Volume-Up button.
Connect your device to your PC via USB
Make sure the device driver's are installed on your PC
Start Odin
In Odin select PDA and select the recovery image (recovery.tar.md5)
Check that only "Auto Reboot" and "F. Reset Time" is set
Click on "Start": the kernel image should be flashed now and the device should reboot afterwards. By flashing the recovery, your warranty will be void.
After the recovery flashing process was successful, power of your device. If not restart into Download mode and flash again or flash the stock rom.
Before you flash:
You need the latest TWRP recovery (see links above). Otherwise TWRP might not be able to flash the ROM.
Wipe the device to avoid problems with remaining files from the old installation (see instructions below). This also applies if you already installed an older version of CM 12.1.
Flash CyanogenMod:
Reboot into recovery mode (Press Volume-Up + Home + Power button)
If you come from a stock ROM, this is your opportunity to make a Backup of your phone(Backup, then select Boot, System, Data, then swipe to backup). Note that the recovery might fail to restore the backup when you want to go back to the stock ROM (for me it got stuck after a restore during boot. But the backup was made with a different version of TWRP, so it might work in general) - simply do not expect too much of it at the moment.
If you haven't copied the installation files yet, you can now copy the GApps and CyanogenMod zip to your internal sd or external sd (be careful not to put the files into the data directory of the internal sd card as this will be deleted in the next step). Be sure that MTP is enabled (inside Mounts, click on Enable MTP), then, from your pc, copy the files. If MTP does not work from recovery, try it directly from Android or remove the external sd card from the phone and put it into your PC.
Wipe Dalvik Cache, Cache, System and Data (inside Wipe -> Advanced Wipe). Do not report problems if you did not wipe those partitions as the problems are most probably related to this!
Install the CM 12.1 ROM zip-package
Install the GApps zip-package
Reboot the system and enjoy a Lollipop
How to root:
No SuperSu is needed as CyanogenMod already comes with integrated root support. Root access is disabled by default.
You normally do not need root access. If you want to activate root access for apps, do the following:
Open the Settings menu, select "About Phone"
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Open the Settings menu, select "Developer options". Enable root access by selecting "Apps" in the "Root-Access" setting.
In case you want to go back to the stock ROM:
lf you do not have the latest stock ROM you can download it from SamMobile
Reboot your phone into Odin mode
Open Odin on your PC and connect your smartphone with your PC via USB
If you have a zip-file unzip it so that you have a .tar.md5 file
In Odin click on the PDA button and select the .tar.md5 file. Then press "Start".
Normally the stock rom fails to boot as the data from CM12 is still on the data partition. So after flashing the stock rom, reboot into recovery mode (it looks a bit different now). First wipe the data partition, then wipe the cache.
Reboot
Changelog
Code:
09/08/2015:
*Update kernel to T235XXU1AOD1
*Synchronize with newest CM 12.1 sources (contains stagefright patches)
*Fixed black screen on minimal brightness
12/07/2015:
* Charging animation in standby-mode fixed
11/07/2015:
* Update to newest CyanogenMod sources (LMY48G)
* Left touchkey working now (configured as App-Switch button)
* Camera Preview working (saving a picture might still crash)
30/06/2015:
* Image sizes reduced to fix "unable to mount /system" problems
28/06/2015:
* Initial test-build
This section is for developers:
A README file with build instructions can be found here:
https://github.com/cm-3470/patcher_degaslte
Sources:
Code:
https://github.com/cm-3470/android_device_samsung_degaslte
https://github.com/cm-3470/android_vendor_samsung_degaslte
https://github.com/cm-3470/android_kernel_samsung_degaslte
https://github.com/cm-3470/android_device_samsung_smdk3470-common
Developers welcome
Help from other developers is always welcome. See the bug/feature section and this thread to see what is missing. Just give some short info (here in this thread or PM) that you want to work on some issue or feature so that work can be synchronized. Maybe there are also other devs that want to work with you on the same issue.
Knowledge in how the kernel works and good programming skills in C, C++ and Java would be nice but not necessary for all problems. At least you should be able to build the ROM and test your changes yourself but you do not need experience in porting ROMs.
XDA:DevDB Information
[T235][ROM][5.1.1][LMY48G] CyanogenMod 12.1 for T235(Y) [Alpha 09/08/2015], ROM for the Samsung Galaxy Tab 4
Contributors
hennymcc
Source Code: https://github.com/cm-3470
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery [version from 09/08/2015]
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-06-29
Last Updated 2015-09-24
i've tried to test the rom but i can't install so far... i've wiped all but it said it can't mount system again...
http://www.mobosdata.com/samsung-galaxy-tab-4-7-0-lte-sm-t235y
According to this the SM-T235Y is based on Marvel cpu vs exynos on the sm-t235
Does anyone really know the differences ? On another page i read the sm-t235y has a snapdragon 400 ...
Hectic confusing samsung numbering + different devices with same model name .
@hennymcc
do you have included selinux_defconfig in your twrp kernel?
androidboot.selinux=disabled at twrps kernel cmd line should be removed
i wiped system and all partitions using your new twrp but when i install the zip file then /system becomes unmountable
/system is formated ext4
should i try to format it f2fs ?
interstellar22 said:
i wiped system and all partitions using your new twrp but when i install the zip file then /system becomes unmountable
/system is formated ext4
should i try to format it f2fs ?
Click to expand...
Click to collapse
any marvell devices will not work with this or any other custom rom.
sub77 said:
any marvell devices will not work with this or any other custom rom.
Click to expand...
Click to collapse
this is an exynos device not marvell
and now for some reason i cant restore the backup i made
i tryed restorng the backup with twrp 2.8.6.0 recovery from this thread and the 2.8.1.0 from the other.
one gives boot animation loop and the other is stuck at boot
hennymcc said:
In case you want to go back to the stock ROM:
lf you do not have the latest stock ROM you can download it from SamMobile
Click to expand...
Click to collapse
Stock Roms on Android File Host (quicker, free-er host site than Sammobile)
@interstellar22 did you try wiping cache after you restored, before you booted?
thisisapoorusernamechoice said:
Stock Roms on Android File Host (quicker, free-er host site than Sammobile)
@interstellar22 did you try wiping cache after you restored, before you booted?
Click to expand...
Click to collapse
i tryed once without wiping cache, but i had cache backed up also
then i tryed to do a factory reset
still stuck at bootlogo
and adb logcat and adb devices shows nothing
sub77 said:
@hennymcc
do you have included selinux_defconfig in your twrp kernel?
androidboot.selinux=disabled at twrps kernel cmd line should be removed
Click to expand...
Click to collapse
The default selinux setting is enforced. As the selinux configuration files are not complete, Android would not boot.
Setting androidboot.selinux=permissive might work, but when I tested this setting on my S5 mini, it was rather unstable for some reason.
interstellar22 said:
http://www.mobosdata.com/samsung-galaxy-tab-4-7-0-lte-sm-t235y
According to this the SM-T235Y is based on Marvel cpu vs exynos on the sm-t235
Does anyone really know the differences ? On another page i read the sm-t235y has a snapdragon 400 ...
Hectic confusing samsung numbering + different devices with same model name .
Click to expand...
Click to collapse
sub77 said:
any marvell devices will not work with this or any other custom rom.
Click to expand...
Click to collapse
interstellar22 said:
this is an exynos device not marvell
Click to expand...
Click to collapse
T235 and T235Y definitely use Exynos 3470 SoCs. Here an extract from the T235Y default.prop:
Code:
ro.product.model=SM-T235Y
ro.product.name=degasltezt
ro.product.device=degaslte
ro.product.board=universal3470
ro.chipname=exynos3470
The default.prop file of the T235 is similar, only that the product name is degasltexx.
Marvell's PXA1088 SoC is used in the T230/NU which is the non-LTE (WiFi-only) variant of the Tab 4 7.0.
Marvell's PXA1088 and Samsung's Exynos3470 are totally different and have nothing in common (except an ARM core), the same applies to Qualcomm's Snapdragon. There are many websites that mention wrong SoC names as Samsung's naming scheme is rather confusing.
The same applies to the S5 Mini: G800F/M/Y -> Exynos3470, G800H -> Qualcomm Snapdragon.
corneo said:
i've tried to test the rom but i can't install so far... i've wiped all but it said it can't mount system again...
Click to expand...
Click to collapse
Code:
Info: format successful
I:mkfs.f2fs -t 1 /dev/block/mmcblk0p18 process ended with RC=0
Done.
Why was the system partition formatted with f2fs? The default file system is ext4.
The TWRP partition table is hardcoded to ext4 so that's probably the reason for these lines:
Code:
E:Unable to mount '/system'
I:Actual block device: '/dev/block/mmcblk0p18', current file system: 'ext4'
Could you reformat it with ext4?
interstellar22 said:
i tryed once without wiping cache, but i had cache backed up also
then i tryed to do a factory reset
still stuck at bootlogo
and adb logcat and adb devices shows nothing
Click to expand...
Click to collapse
Did you flash the stock ROM with Odin?
And afterwards wipe the data partition and then the cache with the _stock_ recovery (as TWRP is not available after flashing the stock ROM)?
interstellar22 said:
i wiped system and all partitions using your new twrp but when i install the zip file then /system becomes unmountable
/system is formated ext4
should i try to format it f2fs ?
Click to expand...
Click to collapse
Short summary:
interstellar22 and corneo tried it so far and both got the error message "/system unmountable"
Strange that corneo was able to generate an error log.
@corneo: did you create the log with adb?
At least according to corneo's log, it seams that after the F2FS format the partition is reformatted with EXT4 afterwards:
Code:
Formatting system using make_ext4fs function.
It also says:
Code:
erasing 588800 blocks
blkdiscard failed: Invalid argument
writing 134395 blocks of new data
lseek64 failed: Invalid argument
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/cm-12.1-20150627-UNOFFICIAL-degaslte.zip'
Error flashing zip '/external_sd/cm-12.1-20150627-UNOFFICIAL-degaslte.zip'
Not that sure about what causes this error. Maybe the partition sizes have to be changed.
hennymcc said:
Short summary:
interstellar22 and corneo tried it so far and both got the error message "/system unmountable"
Strange that corneo was able to generate an error log.
@corneo: did you create the log with adb?
At least according to corneo's log, it seams that after the F2FS format the partition is reformatted with EXT4 afterwards:
Code:
Formatting system using make_ext4fs function.
It also says:
Code:
erasing 588800 blocks
blkdiscard failed: Invalid argument
writing 134395 blocks of new data
lseek64 failed: Invalid argument
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/cm-12.1-20150627-UNOFFICIAL-degaslte.zip'
Error flashing zip '/external_sd/cm-12.1-20150627-UNOFFICIAL-degaslte.zip'
Not that sure about what causes this error. Maybe the partition sizes have to be changed.
Click to expand...
Click to collapse
i've created the log in recovery and copied it to sd.
now i flashed the tab again with odin and try it again. same issue...
Gesendet von meinem One M8
i managed to get the original firmware back with odin
could it be that the system.new.dat file is corrupted ?
i had formated system with ext4 then did the update and was still getting unable to mount /system afterwards
so most probably the system.new.dat file has some problems or i have no idea why i cant mount /system afterwards
Maybe it is caused by wrong BOARD_...IMAGE_PARTITION_SIZE values in BoardConfig.mk.
Could you please post the contents of /proc/mounts and /proc/partitions:
Code:
cat /proc/mounts
cat /proc/partitions
The above should be performed from the stock ROM. The device must be rooted.
Hmm, the problem might be here:
Code:
Patching system image unconditionally...
blockimg version is 2
erasing 588800 blocks
blkdiscard failed: Invalid argument
writing 134395 blocks of new data
lseek64 failed: Invalid argument
588800 * 4096 = 2411724800 bytes (2,2GB)
This is the value of the BoardConfig.mk taken from the S5 Mini (BOARD_SYSTEMIMAGE_PARTITION_SIZE := 2411724800).
But the system partition is only 2233466880 bytes:
Code:
/system | /dev/block/mmcblk0p18 | Size: 2096MB Used: 1828MB Free: 268MB Backup Size: 1828MB
Code:
I:wipe_path '/system'
Formatting System using make_ext4fs function.
Creating filesystem with parameters:
Size: 2233466880
The system.img itself is only 500MB in size. So I guess reducing the image size should fix the problem.
An updated ROM is available. The image sizes have been reduced. I hope this fixes the problems with the system-partition.
Also use the new TWRP recovery as the partition sizes might be hardcoded in the old one.
good news! new recovery and system image works! very smooth so far, searching for bugs now. the only one i found are the extended settings option. it doesn't work but thats no problem for me. thank you very much!
Gesendet von meinem One M8
[Guide] Samsung Galaxy S2 i9100 Android 7.1 Nougat/Lineage OS 14.1
[Guide/Tutorial/Howto] Samsung Galaxy S2 i9100 Any version to Android 7.1 Nougat without PC
This detailed step-by-step guide helps you transform your Samsung Galaxy S2 i-9100/i-9100P to a powerful one with Android 7.1 Nougat.
Verify your phone is i9100 or i9100P before going further : when you Power on phone, it is written Galaxy SII i9100.
The flashing of recovery is a bit tricky but none of the S2 I had were recognised by the PC. So this tutorial is PC free.
If your S2 is recognised by PC, it's easier to flash directly TWRP recovery using Odin or Heimdall https://forum.xda-developers.com/showpost.php?p=75002977&postcount=343
CHANGELOG OF TUTORIAL
v10. Updated pack with TWRP 3.3.1-0
v9. Updated to Unofficial LOS 14.1
v8. Removed Dorimanx kernel (not maintained)
v7. Added Google Play certification (use instructions with my v5 pack below)
v6. Switched to Dorimanx kernel, swteaks, enhenced tutorial thx to feedback, introduced md5 signatures, Stweaks included
v5. Overclock and optimize
v4. Simpler repit, 2 profiles for repit included
v3.5. More custom partitions, kernel for Android N 1.3
v3. Moved to Lineage OS 14.1, Skyline custom kernel, TWRP 3.1 by the.gangster
v2. Added latest repit, added walkthrough for possible errors
v1. Initial release
1 ) DOWNLOAD ---------------------
- djibe Galaxy S2 i9100 pack (53 MB) v5 : http://bit.ly/GalaxyS2djibepackv5
(contains Philz Touch recovery + kernel Lanchon IsoRec CM13 + the.gangster IsoRec TWRP 3.3.1-0 recovery + lanchon repit djibe edit standard or prefered + Su for LOS 14.1 + Samsung drivers).
- ROM Unofficial Lineage OS 14.1 for GalaxyS2 i9100 : https://androidfilehost.com/?w=files&flid=302540&sort_by=date&sort_dir=DESC
Or AOKP : https://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-aokp-rom-t3606915
- OpenGApps ARM 7.1 pico (alternatives: Pico, Micro) : https://opengapps.org/?arch=arm&api=7.1&variant=pico
- a microSD card. Copy Philz Touch recovery + kernel Lanchon IsoRec CM13 + the.gangster IsoRec TWRP 3.3.1-0 recovery + lanchon repit djibe edit standard or prefered + Su for LOS 14.1 AND THEIR RESPECTIVE md5 files from my pack on microSD card and insert it in phone.
- Charge phone to 100 %
WARNING. Read carefully the sentences starting with ###.
### It will not work if your phone is encrypted. Uncrypt it before starting this tutorial.
### This tutorial works without a PC. So it will work if (like me) you get "Unknown USB device error" message when plugging phone in Windows.
### Warranty is now void.
### Later in this tutorial, if you get error : "Failed to mount */data* (No such device)", just reformat Data partition to Ext4 (Using lanchon-repit's script or TWRP recovery).
2 ) BACKUP DATA -------------------
Install Samsung drivers (you unzipped earlier).
Then plug phone to PC in File transfer mode.
Collect all .jpg or .mp4
Use an app like Backupyourmobile to backup texts, contacts, etc.
Check that backup is located on microSD card.
Then copy the backup on your PC.
3 ) FLASH RECOVERY, KERNEL AND RE-PARTITION----------------
We gonna repartition phone to reduce an unused preload partition of 512 Mo (stored Samsung updates that no more exist).
We gonna increase system partition to 1 GB so Android 7.1 and Gapps have enough space.
We gonna increase data partition so you can have all the apps you like.
ALL YOUR DATA WILL BE LOST.
FLASH RECOVERY FROM STOCK RECOVERY ----
Shut down phone.
Power it back on in recovery mode : Use Volume+ + Home + Power buttons and release them when you see Galaxy S2 logo.
### Alternative and easier process if your S2 can be recognized by PC using Heimdall : https://forum.xda-developers.com/showpost.php?p=75002977&postcount=343
Then wait till the recovery launches.
### If you already have a custom recovery, go to the mark -!-!- below.
Using default recovery, use volume buttons to navigate and power to confirm,
install zip -> choose Philz_touch_6.48*.zip and install it.
When its done, shut down phone, restart in recovery mode. You are now in the Philz touch recovery.
### If it fails, you need to install CWM recovery using Odin software and SGS2 in Download mode.
### Use a good tutorial for Odin and SGS2 i9100 recovery flashing.
### Download CWM for Odin : https://www.androidfilehost.com/?fid=95916177934516900
### Once finished, continue operations below as if you had Philz recovery.
In Philz touch recovery (or your recovery -!-!-) : go to Wipe -> format /cache and format /system partitions.
Then back to install zip -> Flash kernel-lanchon*.zip (FLASH IT OR TWRP RECOVERY WON'T LAUNCH AND PHONE WILL BE BRICKED),
then flash recovery recovery-the.gangster-IsoRec-TWRP-3.1.0-0-i9100.zip.
Reboot phone to recovery again, it is now TWRP 3.1.0-0 Recovery !!!
Swipe to unlock filesystem.
Check never show this screen during boot again and swipe again.
In TWRP, go to Backup -> select Boot, System, Data,
Tap select Storage and select External storage,
then Swipe to Backup.
Backup is located on your microSD in the TWRP folder.
(To have latest TWRP recovery, go to Install > Select TWRP 3.1.1-0.img and swype to flash).
### Don't flash repit files if you don't have a TWRP recovery
### 2 MAIN CONFIGS TO REPARTITION :
- For standard config, just use the djibe-standard-repit*.zip included in my archive, you'll have :
1GB system, 6GB data (for apps), max internal storage (photos, temp files) and minimal preload (useless partition used for OTA offical updates).
- My PREFERED version is djibe-prefered-repit*.zip :
1GB system, 2GB Internal storage (limited size for photos and files because who takes photos with SGS2 ?), max data (about 11,5 GB for apps), minimal preload (useless partition).
### And a failproof repit one. If you get flash errors with repit files above, use this one.
- For more custom partitions, ask us in a post what partition sizes you want.
### Let the lanchon*.zip filename AS IS because the filename gives the instructions for the repit script. Lanchon is smart !
Go back to TWRP Home screen,
Plug phone to charger.
Tap go to Install, select lanchon-VERSIONYOUWANT-djibe-repit*.zip from your microSD (if file not seen, tap Select storage -> External-storage),
then Swipe to flash. There is an error, files have been copied to /tmp folder. It is normal !
Go back to Install -> Select Storage -> Internal Storage, OK.
Now tap on : (Up A Level),
scroll down and enter the "tmp" folder,
### If you use another PIT file to repartition (not mine -djibe-version), plug phone to Power source (not PC !) or you could hard brick your device.
tap on lanchon-VERSIONYOUWANT-djibe*.zip and Swipe to flash.
### never connect phone to PC during repit !!!
Let it process for 2 minutes.
4 ) Wipe partitions
INFO : F2FS is the fastest filesystem for read and write partitions on flash memories. Compared to EXT4, gain is from 15 to 280 %.
No need to format the /System partition because it is Read only and Ext4 is still faster.
Format has been done with repit. No need to manually format anymore.
Go to Wipe -> Advanced wipe,
select Dalvik, Cache, System, Data, Internal Storage then Swipe to Wipe, go back to TWRP Home.
5) INSTALL ROM, GAPPS AND ROOT
Still under TWRP Home screen -> go to Install zip and set Storage to External-Storage.
We need to install files 1 by 1.
Select lineage-14.1-*.zip and Swipe to flash,
Then select addonsu-*.zip (this is the Root) and Swipe to flash,
### You get this error : Updater process ended with signal: 4, Error installing zip file '/sdcard/Download/addonsu*.zip', don't care, root is correctly installed.
then open_gapps-arm-7.1*.zip, and Swipe to flash,
### If you are using ResurrectionRemix, don't flash any custom kernel at all !
Then wipe cache/dalvik,
then reboot system.
Wait for 15 minutes while Android starts for the first time.
6 ) ROOT ACCESS
Once in Android, open the Settings menu, select "About Phone".
Go to Settings -> About -> Hit 7 times on the build number, go back,
Go to the Developer options menu, root access -> activate ADB+apps
and Lower activate Local Terminal.
7) CALIBRATE BATTERY
In Google Play Store, download App Battery Calibration (from IMobS Ltd).
Launch the App.
Confirm root acces.
Plug tab and wait till charge hits 100%, then hit BATTERY CALIBRATION and unplug it.
8) You can use Backupyourmobile to restore data,
you can use GPS Status & Toolbox app to enhance GPS fix.
Enjoy,
djibe
THANKS --------------
Teams of : TWRP, Lineage OS, the.gangster, Lanchon, Resurrection remix, Philz, Skyline, MigoMujahid
Hi, i tried that, the repit file i isntalled was the one that has your name. The whole process went ok, except for the install. please check the image for more info.
I formated cache and data partition back to ext4 and everything went fine. Now I have ressurection remix 7.1 ROM.
hi octaviojss:
- Why did you flash my PIT, cause you got the WARNING. If you got "ERROR: 1 Fatal: file system errors in partition #11 'sdcard' (UMS) could not be fixed error" ?
- What happens if you go back to Wipe -> Advanced Wipe
And reformat every partition (F2FS for cache and data and ext4 for system and internal storage) ?
Keep in touch
Why did you have your PIT file there in first place, if it wasnt needed? I installed it because it was more recent. Anyway, as said, when i reformated the cache and data partitions back to ext4 file format i was able to install the rom smoothly and flawlessly.
Glad you did it !
For the PIT file it doesn't change much, but the original lanchon PIT moves data during partition resize, mine erases data.
Enjoy
I get an error "E: error in /tmp/sideload/package.zip" Please help me fix this
Aly Rezz said:
I get an error "E: error in /tmp/sideload/package.zip" Please help me fix this
Click to expand...
Click to collapse
Hi Aly, at which step are you ?
Did you try reflashing the PITs from the SDcard and moving back to Internal stroage main folder ?
Did you authorize TWRP to mount system partition ?
djibe89 said:
Hi Aly, at which step are you ?
Did you try reflashing the PITs from the SDcard and moving back to Internal stroage main folder ?
Did you authorize TWRP to mount system partition ?
Click to expand...
Click to collapse
I wiped my phone and flashed the Philz Touch Recovery Zip. I got this error while flashing it...
Aly Rezz said:
I wiped my phone and flashed the Philz Touch Recovery Zip. I got this error while flashing it...
Click to expand...
Click to collapse
So you've wiped everything under stock recovery ? It needs to be done later once Philz touch is working !
So, we'll try flashing recovery in Download Mode (Home + Power + Volume-), use Odin to flash Philz Touch recovery in .tar format (in AP/PDA section of Odin).
1 - Download Philz Touch recovery in .tar format :
https://mega.nz/#F!oZ1QDDbC!Ko20UNhowwIlXLVFjJsyKw (it doesn't load for me right now)
+ Odin 3.07 (my pack for i9300) : http://bit.ly/2hqiWsP
2 - From my tutorial here, execute the 3rd chapter with Odin :
https://forum.xda-developers.com/galaxy-s3/help/guide-tutorial-samsung-galaxy-s3-i9300-t3491788
(do not flash TWRP inside my i9300 Archive)
3 - Once flash of Philz touch recovery is done, reboot to recovery and continue further steps.
good to have a full tutorial
Glad it pleases you. Hope your S2 is now fully unleashed
Any constructive comment is welcome to enhence the tutorial.
djibe89 said:
So you've wiped everything under stock recovery ? It needs to be done later once Philz touch is working !
So, we'll try flashing recovery in Download Mode (Home + Power + Volume-), use Odin to flash Philz Touch recovery in .tar format (in AP/PDA section of Odin).
1 - Download Philz Touch recovery in .tar format :
https://mega.nz/#F!oZ1QDDbC!Ko20UNhowwIlXLVFjJsyKw (it doesn't load for me right now)
+ Odin 3.07 (my pack for i9300) : http://bit.ly/2hqiWsP
2 - From my tutorial here, execute the 3rd chapter with Odin :
https://forum.xda-developers.com/galaxy-s3/help/guide-tutorial-samsung-galaxy-s3-i9300-t3491788
(do not flash TWRP inside my i9300 Archive)
3 - Once flash of Philz touch recovery is done, reboot to recovery and continue further steps.
Click to expand...
Click to collapse
Still doesn't work. It's stuck at " Nand Write Start!!"
Try Odin 1.3
or this "Tried to do a rollback from official 4.4.2 to official 4.1.2 via Odin.
Since the new official bootloader doesn't allow rollback procedures, I got the missing magic string error and the NAND write fail at Odin.
The tablet bricked, not even showing Samsung Note 10.1 logo. I could only access to ODIN mode, not recovery even. *YIKES*
After a day and a half trying to recover it, I removed the SIM card, the SD card and I loaded the Samsung Stock recovery file via ODIN, then rebooted. I got as far as the Samsung logo which was an improvement compared to what I had. Then I proceeded to reload the 4.4.2 firmware (INU-N8000XXUDNE6) and rebooted the device. Went into recovery mode, restored factory defailts and, voilá!
It is working now on 4.4.2, though it is not the Spanish firmware it shoud be, at least the tablet is functional. "
Hi.
Oh boy I was happy when I found this complete package with all files in a zip. All other places the files are missing or you "can't find them".
And oh boy I was unhappy when I couldn't install the first file.
My phone is a SGS2 Modelnumber GT-I9100 bought in Sweden a few mounth after the model was released.
So I guess the instructions on this page should work for me?
I've rooted my phone with CWM-SuperSU-v0.97.zip and verified with a root checking app from the store. Otherwise it's only updated to the latest Andorid 4.1.2 from Samsung. The phone is working fine with the installed Android version.
So when I choose to install "Philz_touch_6.48*.zip" the following is printed out:
################
PhilZ Touch Recovery
Full Touch CWM Based
+
Advanced Features
Phone i9100
################
This package is for 'galaxys2.i9100.GT-I9100.GT-
I9100M.GT-I9100P,GT-I9100T,SC-02C devices; this
is a ''.
E:Error in /tmp/sideload/package.zip
(Status 7)
What am I doing wrong here? Have I missed doing something obvious? Do I need to install something more before I use your guide?
BR
Tobbe
Hello,
you are rooted.
So, in Android, what happens if you download the app ROM Manager : https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager ,
grant Root access for the app,
Flash latest ClockworkMod Recovery for i9100,
reboot to recovery, reflash Philz Touch ?
Hi.
I tried to do that you wrote. Didn't seem to work with:
GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9.tar
I downloaded Odin and flashed it instead. Now I got this yellow triangle with an exclamation mark in and phone didn't boot into Android.
Got very worried but I went into recovery mode and voila ClockworkMod was running
After that I followed your instruction. Up to "Format to F2FS". I got errors so I changed back to EXT4 and continued.
Installed CM13 with no problem and got very glad so I forgot step 6-8. Will do them in a few days.
Thank you very much for this guide and zip-archive.
It's actually my daughter who will get the updated phone. She is also very happy
BR
Tobbe
PS. One more thing, is it possible to get rid of the yellow triangle with an exclamation mark in? (only appears at atart up screen) DS.
Glad you did it.
It is strange how bugs can be different for everyone !
Triangle can be removed but it seems rather dangerous for a small benefit : https://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
I have no courage to do it after all these tricky steps we wen't by !
See you,
Thanks djibe. I wanted to flash to CM13 from stock rom, so your guide was really helpful.
I did run into two issues, and want to share how I got around them:
1. I got the "Status 7" problem when trying to flash Philz_touch_6.48*.zip. So instead I flashed the relevant ZIP file from "forum.xda-developers.com/galaxy-s2/development-derivatives/philz-cwm6-stock-kernel-cwm6-root-exfat-t1877270" from stock recovery first. This installed a custom recovery. Then I flashed Philz_touch_6.48 from the custom recovery.
2. After formatting /cache and /data to F2FS, installing CM13 failed. So instead I kept /cache and /data as EXT4 and completed the installation according to the rest of the guide. After rebooting and completing the CM13 Android setup, I redid the installation from step 4 of your guide onwards and F2FS worked this time. I should mention though that before formatting /cache and /data to F2FS, I also repartitioned with a newer repit file from lanchon's github (and increased data to 4G), so I don't know if this had an effect as well.
Hopefully this helps others facing the same problems. I should warn though that this is my first time attempting absolutely anything like this, so please take all this with caution. Your mileage may vary!
S2andCounting said:
Thanks djibe. I wanted to flash to CM13 from stock rom, so your guide was really helpful.
I did run into two issues, and want to share how I got around them:
1. I got the "Status 7" problem when trying to flash Philz_touch_6.48*.zip. So instead I flashed the relevant ZIP file from "forum.xda-developers.com/galaxy-s2/development-derivatives/philz-cwm6-stock-kernel-cwm6-root-exfat-t1877270" from stock recovery first. This installed a custom recovery. Then I flashed Philz_touch_6.48 from the custom recovery.
2. After formatting /cache and /data to F2FS, installing CM13 failed. So instead I kept /cache and /data as EXT4 and completed the installation according to the rest of the guide. After rebooting and completing the CM13 Android setup, I redid the installation from step 4 of your guide onwards and F2FS worked this time. I should mention though that before formatting /cache and /data to F2FS, I also repartitioned with a newer repit file from lanchon's github (and increased data to 4G), so I don't know if this had an effect as well.
Hopefully this helps others facing the same problems. I should warn though that this is my first time attempting absolutely anything like this, so please take all this with caution. Your mileage may vary!
Click to expand...
Click to collapse
Thank you very much for these tips that will surely help others.
Can you send me the direct link to the Philz recovery that was successful for you ?
I'm upgrading my tutorial with your stuff, and making it simpler with a new custom repit file.
Keep in touch
Hi
I own a 100% stock Samsung Galaxy S2 (GT-i9100).
The device is not rooted or modified and is currently running standard Samsung firmware.
Baseband I9100XXMS2
Kernel 3.0.31-1211311
Build numberJZ054K.I9100XWLSW
Android 4.1.2
Whilst I am not a power user I am tired of running out of system memory and having to move apps to the SD card. I am also tired of not being able to load certain apps due to the old Android version. I do want to connect to my car via Bluetooth (audio and internet etc).
It's time for a new operating system ... hence my visit to this web site. I have tried reading the guides but most use a lot of jargon and talk of multiple ROM options. I am a little lost and need some plain English instruction to follow since this is my first step into the ROM flashing world.
Which version should I install? Where do I download it from? What tools do I need for my PC? How do I do the flash?
Anyone out there who can help a complete novice?
Thanks in advance
Jacbjacb said:
Hi
I own a 100% stock Samsung Galaxy S2 (GT-i9100).
The device is not rooted or modified and is currently running standard Samsung firmware.
Baseband I9100XXMS2
Kernel 3.0.31-1211311
Build numberJZ054K.I9100XWLSW
Android 4.1.2
Whilst I am not a power user I am tired of running out of system memory and having to move apps to the SD card. I am also tired of not being able to load certain apps due to the old Android version. I do want to connect to my car via Bluetooth (audio and internet etc).
It's time for a new operating system ... hence my visit to this web site. I have tried reading the guides but most use a lot of jargon and talk of multiple ROM options. I am a little lost and need some plain English instruction to follow since this is my first step into the ROM flashing world.
Which version should I install? Where do I download it from? What tools do I need for my PC? How do I do the flash?
Anyone out there who can help a complete novice?
Thanks in advance
Click to expand...
Click to collapse
Mate, take it easy, i see you are a good English speaker, it should be very easy for you to understand the guides, for me it was hard and i bricked my phone multiple times, I'm not saying that I'm a geek or an android expert or something like that, but i know enough about my phone and i know what it's capable of and what it isn't, you should start easy step by step, and try following a video guide from YouTube like searching in google "i9100 root and custom recovery" and start reading some articles about it, believe me no one would just give you instructions on a silver plate, even if someone did, you will remain a noob who knows nothing about flashing and you won't be able to change your new rom or go back to stock rom..you should dig for it, there are guides that provide you with instructions and information about what you do..all you have to do is do a couple of google searches..
Anyway, all i can do to you is give you a link to this guide
Hope you understand the message
Regards Migo
Well I spent the entire afternoon and evening yesterday reading all I could about the flashing of the this Samsung Galaxy S2 GT-i9100. I then started to collect the files I think I will need:
Heimdall Suite: Inc' zadig.exe 2.0.0147, heimdall-frontend.exe 1.4.0, heimdall.exe
Lineage 14.1 Rom: cm-14.1-20161225-UNOFFICIAL-i9100.zip
Minimal_adb_fastboot_v1.4.2_setup.exe: Inc' adb.exe. cmd-here.exe, fastboot.exe etc
Odin3 v1.85.exe
open_gapps-arm-7.1-nano-20170225.zip
PIT Files: I9100_2GB-STOCK.pit (in case of problems) and I91001GB_6GB.pit
SAMSUNG USB Driver for Mobile Phones 1.5.27.0.exe
TWRP: twrp-3.0.2-1-i9100.img, recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip,
On the phone I activated USB Debugging
I installed the USB drivers and the PC can see the phone
I ran Odin and the phone is seen
I tried to install TWRP using the instructions found here: https://twrp.me/devices/samsunggalaxys2i9100.html .... It didn't work!
I copied recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip to the SD card, entered recovery mode and tried to apply the update from external storage. All seem to go well but then I got E:Error in tmp/sideload/package.zip (Status 7) ..... at the Top of the page it said Android System recovery (3e) ... I take it that is the system recovery currently installed on the phone. I found twrp-3.0.2-0-i9100.zip and tried that .... but got the same System 7 error!
So I have got nowhere really!
I know I have to repartition the drive using the PIT file
I know I have to load a custom recovery file using the TWRP
I then have to load the new ROM
But I don't know the order in which to do the operations .... TWRP first or PIT?
I don't seem to be alone in my fog ... see https://forum.xda-developers.com/ga...twrp-galaxy-s2-i9100-tried-t3539940?nocache=1
I have now realized that the various guides relate to the version of ROM they wish to install .... I am planning to use a Lineage 14.1 Rom. It seems that I can load it using TWRP or Odin.
I think the first step is to load TWRP ....... But I cant seem to be able to do that ..... Can Anyone help me install TWRP if that if the first priority?
Well I spent the entire afternoon and evening yesterday reading all I could about the flashing of the this Samsung Galaxy S2 GT-i9100. I then started to collect the files I think I will need:
Heimdall Suite: Inc' zadig.exe 2.0.0147, heimdall-frontend.exe 1.4.0, heimdall.exe
Lineage 14.1 Rom: cm-14.1-20161225-UNOFFICIAL-i9100.zip
Minimal_adb_fastboot_v1.4.2_setup.exe: Inc' adb.exe. cmd-here.exe, fastboot.exe etc
Odin3 v1.85.exe
open_gapps-arm-7.1-nano-20170225.zip
PIT Files: I9100_2GB-STOCK.pit (in case of problems) and I91001GB_6GB.pit
SAMSUNG USB Driver for Mobile Phones 1.5.27.0.exe
TWRP: twrp-3.0.2-1-i9100.img, recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip,
On the phone I activated USB Debugging
I installed the USB drivers and the PC can see the phone
I ran Odin and the phone is seen
I tried to install TWRP using the instructions found here: https://twrp.me/devices/samsunggalaxys2i9100.html .... It didn't work!
I copied recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip to the SD card, entered recovery mode and tried to apply the update from external storage. All seem to go well but then I got E:Error in tmp/sideload/package.zip (Status 7) ..... at the Top of the page it said Android System recovery (3e) ... I take it that is the system recovery currently installed on the phone. I found twrp-3.0.2-0-i9100.zip and tried that .... but got the same System 7 error!
So I have got nowhere really!
I know I have to repartition the drive using the PIT file
I know I have to load a custom recovery file - TWRP
I then have to load the new ROM
But I don't know the order in which to do the operations .... TWRP first or PIT?
I don't seem to be alone in my fog ... see https://forum.xda-developers.com/ga...twrp-galaxy-s2-i9100-tried-t3539940?nocache=1
I have now realized that the various guide relate to the version of ROM you wish to install .... I am planning to use a Lineage 14.1 Rom. It seems that I can load it using TWRP or Odin.
I think the first step is to load TWRP ....... But I cant seem to be able to do that ..... Can Anyone help?
Jacbjacb said:
I have now realized that the various guide relate to the version of ROM you wish to install .... I am planning to use a Lineage 14.1 Rom. It seems that I can load it using TWRP or Odin.
I think the first step is to load TWRP ....... But I cant seem to be able to do that ..... Can Anyone help?
Click to expand...
Click to collapse
The TWRP you are trying to install requires a kernel that supports isorec, so you must have that kernel first.
To have isorec support:
Note: -the rom and the isorec recovery and nogut rom and gapps -in short: all files- should be put in external sdcard because the internal sdcard will be wiped in the procedure.
1-you should install latest kernel-Lanchon-TRIM-IsoRec, you can easily flash it using a
Kitkat compatible recovery, flash the recovery using Odin along with a pit that has 1GB system or more,
1.5GB PIT Files by the.gangster or 1GB PIT Files by ELgmal 1GB is enough
2-after that, reboot to recovery:
• wipe data
• wipe cache
• navigate to "mount" and format system and format internal sdcard using (default)
• go back and navigate to "advanced" and wipe Dalvik cache.
• then go back and choose "install zip from sdcard1 (external sdcard)"
• and navigate to your kernel-Lanchon-TRIM-IsoRec and flash it.
• install arnab isorec recovery twrp zip by the gangster
• reboot your recovery, you will find the TWRP installed, now wipe system and data and cache and dalvik and install your nogut rom and the correct gapps.
that's it
Alternative Method
DON'T use odin to flash pit, just use it to flash the kitkat compatible recovery.
• flash Kitkat Compatible recovery with odin.
• in recovery flash kernel-Lanchon-TRIM-IsoRec and then flash twrp 3 isorec.
• and reboot recovery, then in TWRP 3 flash lanchon repit tool.
Lanchon repit tool is a simple flashable zip that can be edited to split the partition in desired way, read more about it in the official thread
This method was recommended by @TriboDoP
All credits goes to our great Developers.
MigoMujahid said:
The TWRP you are trying to install requires a kernel that supports isorec, so you must have that kernel first.
To have isorec support:
Note: -the rom and the isorec recovery and nogut rom and gapps -in short: all files- should be put in external sdcard because the internal sdcard will be wiped in the procedure-
1-you should install latest CM11, you can easily flash it using a
Kitkat compatible recovery, flash the recovery using Odin along with a pit that has 1GB system or more,
1.5GB PIT Files by the.gangster or 1GB PIT Files by ELgmal 1GB is enough
2-after that, reboot to recovery:
• wipe data
• wipe cache
• navigate to "mount" and format system and internal sdcard
• go back and navigate to "advanced" and wipe Dalvik cache.
• then go back and choose "install zip from sdcard1 (external sdcard)"
• and navigate to your cm11 rom and install the rom
• install arnab isorec recovery twrp zip by the gangster
• reboot your recovery, you will find the TWRP installed, now wipe system and data and cache and dalvik and install your nogut rom and the correct gapps.
that's it
Alternative Method
• flash Kitkat Compatible recovery with odin.
• in recovery flash cm11 with twrp 3 isorec.
• and reboot recovery, then in TWRP 3 flash lanchon repit tool.
Lanchon repit tool is a simple flashable zip that can be edited to split the partition in desired way, read more about it in the official thread
This method was recommended by @TriboDoP
All credits goes to our great Developers.
Click to expand...
Click to collapse
WOW IT WORKED! THANK YOU THANK YOU THANK YOU!
I used the following files:
SAMSUNG_USB_Driver_for_Mobile_Phones v1.5.51.0.exe
Lineage-11-20170115-UNOFFICIAL-i9100.zip … (CM11)
CWM-KitKatCompatible-i9100.tar
Odin3 v3.07
PIT Files: I91001GB_6GB.pit
Lineage 14.1 Rom: cm-14.1-20161225-UNOFFICIAL-i9100.zip
TWRP: twrp-3.0.2-1-i9100.img, recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip
open_gapps-arm-7.1-nano-20170225.zip
All went well following the upgrade of SAMSUNG USB Driver for Mobile Phones 1.5.27.0.exe to SAMSUNG_USB_Driver_for_Mobile_Phones v1.5.51.0.exe. Odin 3 v3.07 had communication problems in download mode with the earlier drivers.
I followed your instructions to the letter (printed and ticked as I progressed) and only had one issue when it came to formatting the internal sdcard ….. I didn’t know what format so I selected “default” which worked.
I used a PIT file I had rather than your files simply because I didn’t know which one of your files to choose … too many options! I didn't fully appreciate the difference between them?
What can I say but Thank You …. This must be the simplest and BEST GUIDE out there for somebody going from a stock 4.1.2 to 7.1.1
One last question ..... how do I read my SD card (external) now that I have flashed my phone with 7.1.1?
Windows can see the SD card but wont let me read the contents. I have read https://www.reddit.com/r/Android/comments/3nnkaa/cant_access_android_device_internal_storage_from/ and put the phone into MTP for the USB.
Jacbjacb said:
One last question ..... how do I read my SD card (external) now that I have flashed my phone with 7.1.1?
Windows can see the SD card but wont let me read the contents. I have read https://www.reddit.com/r/Android/comments/3nnkaa/cant_access_android_device_internal_storage_from/ and put the phone into MTP for the USB.
Click to expand...
Click to collapse
It should work, I'm using AICP 12.1 (7.1.1) build 7 Feb, and it's working when i set it to MTP, but sometimes i have to change the cable, try changing the cable or use another USB port.
I installed AICP because official LineageOS 14.1 is buggy these days.
Thanks for the tip i forgot when formatting internal sdcard using default, i edited the guide and added it to my signature so every one can easily find it.
There are good talks about other nogut roms like crDroid and xenonHD, i would try them, but it would take time and i only have one s2 and it's my daily driver, so i couldn't, but many people recommended them.
I'm happy that i was able to help you, and thank you for telling me that my guide was easy, i was afraid that it might be complicated or something
Regards Migo
---------- Post added at 10:28 PM ---------- Previous post was at 10:22 PM ----------
Jacbjacb said:
One last question ..... how do I read my SD card (external) now that I have flashed my phone with 7.1.1?
Windows can see the SD card but wont let me read the contents. I have read https://www.reddit.com/r/Android/comments/3nnkaa/cant_access_android_device_internal_storage_from/ and put the phone into MTP for the USB.
Click to expand...
Click to collapse
Oh, you meant the external sdcard, have you mount it after the first boot, you must have got some notification about it.
If you didn't, navigate to storage in settings and choose the external sdcard and you will be asked to mount it as a "portable storage" or an "internal storage", choose "portable storage".
Jacbjacb said:
One last question ..... how do I read my SD card (external) now that I have flashed my phone with 7.1.1?
Windows can see the SD card but wont let me read the contents. I have read https://www.reddit.com/r/Android/comments/3nnkaa/cant_access_android_device_internal_storage_from/ and put the phone into MTP for the USB.
Click to expand...
Click to collapse
You can use recovery to transfer between computer and phone.(in case the rom fails to do that)
Nexus 4 Repartition
No one is responsible for your actions except yourself. Everything written further may potentially brick your device, although risk is reduced to minimum.
This repartition package offers 1.5G /system; a /vendor partition and it is fully backward compatible with any ROM (including stock system.img).
Known-issues
HTML:
- If repartition pack says that device isn't correct,
than, if partition table wasn't modified before,
congrats! your device has different memory chip
that those I worked with. No worry, PM me and
I'll add support for it.
DO THE BACKUPs. Repartition will erase all your data
USB connection to PC is MANDATORY else you will not have opportunity to push ROM to your device
Installation
HTML:
# Before processing further we highly recommend you to use our TWRP which has support of EFS/Persist backup
# Or you might lose your IMEI/WIFI + BT mac addresses
# This mod is backwards compatible with any ROM so we highly recommend NOT to reverse it if repartition went well.
# You should use ONLY recovery from this thread since other don't support all benefits of this mod.
# When installing ROM just after you flashed zip and before installing GAPPs you MUST make a resize in TWRP since all roms are build for ~800M system.
# To restore stock layout use same zip and steps as for repartition.
1. Boot into recovery (You need to allow system partition modification to be able resize /system in recovery).
2. Backup your data & Move your files from flash to your PC.
3. Flash repartition pack zip.
4. Do the actions asked by repartition pack (go to Terminal in ordinary recovery and input word that pack will tell you. Everything else will be done automatically).
5. Phone will reboot into recovery.
6. Install TWRP from below (it is build with support of new partitions layout and sizes. It can be differed from official TWRP by next format 3.x.x-1 UA).
7. Format everything. (mount errors will not affect formatting!)
- In TWRP: Wipe > Format data
- Type yes
- Once this completes go to: Wipe > Advanced Wipe
- Tick all the boxes and wipe. There should be no further mount errors.
8. Install ROM which you like.
9. Enjoy better flash partition layout.
If something gone wrong - we recommend you using this guide to restore your phone back
Downloads:
Repartitioning package: GitHub
Credits:
Special thanks to
- Unlegacy-Android team;
- Sudokamikaze;
- ddaggebi for 8GB model layout;
- surfrock66 for his gide for Nexus 5;
As usual, feedback is appreciated
XDA:DevDB Information
Nexus 4 Repartition, Tool/Utility for the Google Nexus 4
Contributors
Clamor, sudokamikaze
Source Code: https://github.com/clamor95/android_device_unlegacy_recovery
Version Information
Status: Stable
Created 2018-09-19
Last Updated 2019-01-18
Common issues and F. A. Q.
Repartition pack should be safe for most devices. Common mistakes, issues and their solution will be published here.
1. You shouldn't flash any internal parts of repartition pack (*.sh files) only flash whole zip using TWRP. You may use my scripts for personal use or projects but authorship should to be kept.
2. If something isn't mounting after repartition try to format partitions that don't mount using Wipe -> Advanced Wipe in TWPR. Ideally you should format in that way all partitions in Advanced Wipe menu (see 5-th step of installation guide).
3. To be sure that repartition went well I enclose loging zip. Flash it after repartition (when device reboots into TWRP). It won't modify anything only generates a partition.log in root of internal storage and outputs your current partition layout to screen. You shoud check if your layout is same as those fragments I provide under spoiler (file systems doesn't matter). If there are any differences you have to discribe what you did and enclose partition.log to your post.
MAKO STOCK
Code:
21 159383552B 1040187391B 880803840B system
22 1040187392B 1627389951B 587202560B cache
MAKO MODIFIED
Code:
21 159383552B 1732247551B 1572864000B system
22 1732247552B 1994391551B 262144000B vendor
23 1994391552B 2099249151B 104857600B cache
4. If you have touchscreen problems use common instructions till you reach entering word. Than plug your phone to PC while you remain in recovery. Enter adb shell from cmd (if you don't know how - google) and enter word that repartition pack asked. Than your phone will reboot automatically into your old TWRP but with new partition layout.
5. Flashable resize zip for ROMs that support addon.d (automatic resize when dirty flashing updates).
actually the lower left corner of my phone screen doesnt work so can you please elaborate what kind of commands are we used to use and terminal and is there any other way to access terminal
mine q,a,z,1 these key are inaccessible in twrp as screen rotation is not supported
bgoel4132 said:
actually the lower left corner of my phone screen doesnt work so can you please elaborate what kind of commands are we used to use and terminal and is there any other way to access terminal
mine q,a,z,1 these key are inaccessible in twrp as screen rotation is not supported
Click to expand...
Click to collapse
Plug your phone to PC while you remain in recovery. Enter adb shell from cmd (if you don't know how - google) and enter word that repartition pack asked. Than your phone will reboot automatically into your old TWRP but with new partition layout.
What can I do to add support for 8GB models? Can I send you some partition tables that you can tinker with? Or sth else? Anyway, huge thanks for your dedication for this device!
ddaggebi said:
What can I do to add support for 8GB models? Can I send you some partition tables that you can tinker with? Or sth else? Anyway, huge thanks for your dedication for this device!
Click to expand...
Click to collapse
PM me, I need a partition table and I'd ask you to test if you have 8GB model.
Something went wrong and now I have only 552mb space. When I try to flash again it says it's not a Nexus 4.
Can anyone help please?
cyberon said:
Something went wrong and now I have only 552mb space. When I try to flash again it says it's not a Nexus 4.
Can anyone help please?
Click to expand...
Click to collapse
Sure. In PM.
OK so my nexus 4 can't transfer files to or from PC at all so if I do this and have the ROM downloaded it will wipe the ROM and the ROM would be gone and my phone would be a nice brick because I can't transfer any files to my PC like it charges with the PC but data transfer doesn't work so again would I be screwed?
@Nathan4923 correct. Usb connection and PC are mandatory
For those who downloaded repartition pack before this message is published, please redownload pack since previous version might have a problems with repartition. If repartition was already made, don't worry everything should be fine. Just use up-to-date pack.
can i return back to old partition if i want to? i hope someone would post a video tut for this one
@jluspo you can with same zip and same steps as for repartition. You didn't read first post carefully.
Clamor said:
@jluspo you can with save zip and same steps as for repartition. You didn't read first post carefully.
Click to expand...
Click to collapse
im using xda appits different layout on browser
I'm I doing it right? I still can't flash gapps
failed to mount Vendor, any suggestions ?
@jluspo resize /system with TWRP after ROM install before GAPPs because ROMs are designed to use ~800MB system.
@cqloveqc you had to format all partitions available in advanced wipe after repartition.
Clamor said:
@jluspo resize /system with TWRP after ROM install before GAPPs because ROMs are desined to use ~800MB system.
@cqloveqc you had to format all partitions available in advanced wipe after repartition.
Click to expand...
Click to collapse
Thanks for the help !
I've found that even with that error, i still succed the process
Hello ho can I do ,,resize /system with TWRP after ROM,,??? I can't find how to do that...
I installed your TWRP > backup > repartition zip > format all partitions > ROM
And now I'm stuck because I can't flash GAPPS...
Mato_xXx said:
Hello ho can I do ,,resize /system with TWRP after ROM,,??? I can't find how to do that...
I installed your TWRP > backup > repartition zip > format all partitions > ROM
And now I'm stuck because I can't flash GAPPS...
Click to expand...
Click to collapse
just read the OP carefully it already mentioned that you had to resize system after installing rom
you can do that by going to advanced wipe in twrp