Related
[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
Greetings!
I'd like to present a TWRP recovery for the single-sim Xperia X. This release works on Xperia X F5121 and F5122
DISCLAIMER:
I'm not responsible for any damage done to your device. You have been warned.
REQUIREMENTS
Unlocked bootloader
Working ADB and Fastboot (You can get the latest version through Android Studio or by visiting this site)
FEATURES
MTP support
ADB Sideload
Backups and restores almost every partition
Full SELinux support
Working encryption. You can access /data within recovery
NEEDS TESTING
USB-OTG
DOWNLOADS
INSTALLATION
Unlock the bootloader
Download the file
Put the following code in CMD/Terminal:
Code:
fastboot flash recovery twrp-3.1.1-suzu-*.img
//Replace * with the version you want to flash
Unplug the cable
Press Volume Down + Power to activate the recovery. When installed properly, the device should vibrate funnily, purple LED should appear and after a couple of seconds you should see the TWRP screen.
Enjoy!
BUILD
You need to sync the OmniROM and vendor blobs from DonkeyCoyote. You can find my sources on GitHub.
android_device_sony_loire_common
https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
Thanks:
@grayleshy - for initial TWRP
@AndroPlus for some of his flags
OmniROM team for sources
If you find my work useful, consider buying me a cup of coffee
[TWRP] TWRP 3.1.0 for Xperia X
Old OP below:
Team Win Recovery Project 3.1.0
REQUIREMENT:
- Unlocked bootloader
FEATURES:
- MTP support
- USB OTG storage support
- Covers most partitions for nandroid backups
- ADB root
- Full SELinux support
- Support for partition decryption
Download: Dropbox
Installation via the bootloader (Platform-tools (adb & fastboot))
Code:
fastboot flash recovery recovery.img
Running TWRP: turn the phone off, wait 5 seconds, then pinch at the same time the power key and the volume down key until the device vibrates, release the keys. Recovery starts within 5-10 seconds.
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
Special thanks kistigun for testing recovery on the device.
Changelog: twrp.me
TWRP was going on OmniRom 7.1 sources and XperiaDeveloper.
SOURCEs: Suzu; loire; Common.
Nice work! Finally no more decryption problems on the X!
Working well, thanks!
One question ; is it possible to reboot the recovery via twrp reboot menu (or use an app like flashfire /flashify)? When I've tried the phone boots normally instead.
baddesthad said:
One question ; is it possible to reboot the recovery via twrp reboot menu (or use an app like flashfire /flashify)?
Click to expand...
Click to collapse
Unfortunately the reboot Recovery does not work from the specifics of the section, but in the future maybe will be fixed. If I don't find how to fix that button will be removed.
samavar89 said:
Unfortunately the reboot Recovery does not work from the specifics of the section, but in the future maybe will be fixed.
Click to expand...
Click to collapse
Good to know, thanks for clarifying
Is there a difference to the 3.1.0 TWRP recovery from the Poison thread?
Oel said:
Is there a difference to the 3.1.0 TWRP recovery from the Poison thread?
Click to expand...
Click to collapse
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
kistigun said:
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
Click to expand...
Click to collapse
Ah...
Ok, Thanks!
kistigun said:
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
Click to expand...
Click to collapse
No,
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
someone knows a recovery that finally works?
robby.pgn said:
No, don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
Click to expand...
Click to collapse
This problem is strange, please provide a log recovery.
I flashed this on my xperia x dual on nougat 7.0
I can go to recovery but when i try to turn on the phone normally it says "The phone is corrupt and cant be trusted bluh bluh..."
it says press power button to continue but when i press it screen turns off and nothings happens
what should i do?!
Kianush said:
I flashed this on my xperia x dual on nougat 7.0
I can go to recovery but when i try to turn on the phone normally it says "The phone is corrupt and cant be trusted bluh bluh..."
it says press power button to continue but when i press it screen turns off and nothings happens
what should i do?!
Click to expand...
Click to collapse
In Your kernel there is support for DM-Verity and Sony RIC?
it's stock kernel man, I unlocked bootloader and flashed stock nougat for xperia X dual sim
I just wanna root it, if there is any other way pls help me out
-----
btw after this problem i used flashtool to flash system and kernel from stock rom to be able to use my phone again
robby.pgn said:
No,
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
someone knows a recovery that finally works?
Click to expand...
Click to collapse
Kianush said:
it's stock kernel man, I unlocked bootloader and flashed stock nougat for xperia X dual sim
I just wanna root it, if there is any other way pls help me out
-----
btw after this problem i used flashtool to flash system and kernel from stock rom to be able to use my phone again
Click to expand...
Click to collapse
use this tool/guide to make a rooted kernel(and edit DM-Verity and Sony RIC): https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
grayleshy said:
Team Win Recovery Project 3.1.0
Click to expand...
Click to collapse
I've installed and tried this TWRP in my Xperia X with MM. Very nice that it can access the data partition! I did not try to install any zip yet.
Some problems I've seen:
dmesg.log: no output
recovery.log: https://pastebin.com/EwbtuC9q
What is interesting in the output:
Code:
I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk1p1 /external_sd
CANNOT LINK EXECUTABLE "sh": cannot locate symbol "__fwrite_chk" referenced by "/sbin/busybox"...
I:exfat-fuse failed to mount with result '', trying vfat
I:Unable to mount '/external_sd'
I:Actual block device: '/dev/block/mmcblk1p1', current file system: 'vfat'
Looks like something is not right with the busybox in the image. Maybe it is that what is causing the external sdcard (in my case in exfat filesystem) not being mounted?
Thanks
robby.pgn said:
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup.
Click to expand...
Click to collapse
This problem is almost resolved, just need to test, but I don't have time to compile recovery. In the test version recovery without decryption, problem solved.
juliompinheiro said:
I've installed and tried this TWRP in my Xperia X with MM. Very nice that it can access the data partition! I did not try to install any zip yet.
Some problems I've seen:
dmesg.log: no output
recovery.log: https://pastebin.com/EwbtuC9q
What is interesting in the output:
Code:
I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk1p1 /external_sd
CANNOT LINK EXECUTABLE "sh": cannot locate symbol "__fwrite_chk" referenced by "/sbin/busybox"...
I:exfat-fuse failed to mount with result '', trying vfat
I:Unable to mount '/external_sd'
I:Actual block device: '/dev/block/mmcblk1p1', current file system: 'vfat'
Looks like something is not right with the busybox in the image. Maybe it is that what is causing the external sdcard (in my case in exfat filesystem) not being mounted?
Click to expand...
Click to collapse
This issue failed to reproduce, and yet there is no solution. You the problem is not in Busybox, and something else.
grayleshy said:
Running TWRP: turn the phone off, wait 5 seconds, then pinch at the same time the power key and the volume down key until the device vibrates, release the keys. Recovery starts within 5-10 seconds.
Click to expand...
Click to collapse
For whatever reason I'm not able to boot into TWRP like I should be. I've used the poison version of TWRP before so I know what to do, and yet the phone will just boot normally despite holding volume down and power when off.
I know that TWRP is installed though as I am able to boot to it if I first boot to the bootloader using a USB cable but that is very cumbersome to do though.
grayleshy said:
This issue failed to reproduce, and yet there is no solution. You the problem is not in Busybox, and something else.
Click to expand...
Click to collapse
Clearly for the image available at your dropbox there are some libraries dependency errors, not only for the 'busybox', but also for other binaries that are in /sbin.
I do not know why this issue is only happening on my device since you said you can't reproduce this error. If there is anything I can do to help solve this strange behavior, count on me. I am an advanced linux user, but not too familiar with android specifics.
On latest 333 ROM for UK so that fingerprint scanner works on my Xperia X F5121.
I also modified by kernel/boot so that TWRP doesn't brick (actually boot loop) the device like it did the first time. After using these awesome instructions flashing TWRP recovery from here didn't kill the device any longer: https://forum.xda-developers.com/crossdevice-dev/sony/root-root-stock-firmware-modern-sony-t3558904
I was able to take an early nandroid backup before a bunch of Titanium restores, etc. Now I get stuck at "Backing up data" step and it literally doesn't move to the next file. Attaching an image of where I get stuck. FYI, I do use password encryption on the backup and I did disable MD5 creation... still just stuck.
Next tests are to:
see if the stall is on the same exact file number
try no encryption
do a check disk (fsck) type of repair just in case I have corruption --- on my brand new device
Any suggestions greatly appreciated!
UPDATED:
I only back up Boot, System & Data (the default)
On second attempt it stopped at file 18869 of 22065 --- so it does jump and not consistently stop at a certain file.
[Guide] How to Root Note8 + EFS Backup
Index of post
Must Read - You must read this to know about side effects of rooting device.
OEM Issue - OEM unlock option is must to root device, know about it
PART1: Recommended method to root N8 (exynos)
PART2: Other possible methods to root N8 (exynos) - Use this as knowledge base, we still recommend method said in PART1.
PART3:EFS Backup - You must backup EFS as soon as you root the device and make a copy to other safe place too
.
Must Read :
READ THIS BEFORE ROOTING DEVICE
- Any of below said method to root will trip knox and void warranty forever.
- Root process needs wipe data so make backup of important data (including Internal Device storage) before proceed.
- As of now you will lose Samsung Pay and Secure folder forever if you root once, even unrooting won't help. (hope in future we can get it working on tripped knox device). Also you may not able to run some banking apps, but for that there are some workaround like Magisk Hide or SU hide, google it.
- OTA likely won't work once you root device.
- To unroot device completely, simply flash Samsung stock firmware, Remember, Unrooting won't revokes warranty nor you will be able to use Secure folder/Samsung Pay. Once rooted, these feature gone for you unless some magic happen in future and may find a way to use it.
Click to expand...
Click to collapse
OEM issue
OEM affected device - means OEM unlock option missing out of box and appears 7 days later. If you are uncertain about this, you can consider your device OEM affected .
Workaround to get OEM unlock option if it is not available (Normally it appears after 7 days of clean install but this trick may bring it without 7 days waiting)
- Flash latest stock firmware
- Set clock 8 days prior to current date
- Check for OTA update (check last check date is set to 8days prior from current)
- Reboot
- Set current date
- Check for OTA update (now last check date should be current day
- Check Developer option for OEM option
Click to expand...
Click to collapse
PART1 : For Oreo & Pie
ROOT Note8 (exynos) (Recommended method for all including have OEM issue )
This method is most convenient and give most options in single pack, like root with magisk/SuperSU also it does patch OEM issue (losing OEM toggle on rooting device, follow below said guide to the letter to work it properly)
How to Use
1.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
2.Enable OEM Unlock from developer option (Read above for workaround if you don't have this option)
3.Download and copy N950F_root_OEM_issue_devices.zip according Oreo/Pie to Ext SD card
4.Download TWRP for N8
5.Switch Off device
6.Press Vol down + Bixby + Power to reboot to download mode, press volume up when asked to continue to download mode
7Download Odin and open it, Disable 'Auto reboot' from option menu of Odin
8.Select TWRP (tar image) with AP tab of Odin and Start
9.Once Successfully flashed, you will see 'Passed' in Odin tab
10.Disconnect device and hold Vol down + power till screen goes off, Now immediately press Vol Up + Bixby + Power to reboot to TWRP
11.Select to allow modification
12.From TWRP, Select WIPE menu - Then FORMAT DATA - You need to type 'yes' to perform wipe. WARNING : This will erase all data including Int SD storage from device
13.Once format device completes, go back and select REBOOT' Menu and then - 'RECOVERY', This will reboot to TWRP again
14.Now select Install and navigate path to Ext SD card - N950F_root_OEM_issue_devices.zip, you have copied earlier
15.Once Magisk flash successfully, Reboot to System
Open settings - Developer option - Look for OEM Unlock option. If it is there, it is safe to reboot device.
Credits and Thanks goes to BlackMesa123 for this post for OEM patch script.
Important Note for Pie - There will be OEM unlock option there in developer setting but it will be disabled and can not enabled, this is because of it is hacked. Just ignore it. You can not boot device with TWRP if it is really disabled. Also If magisk app may not appear then simply download Magisk_for_Pie.apk from below attachement and install as regular app.
PART2 : (FOR OREO Only)
ROOT Note8 (exynos) for devices that doesn't have OEM issue
This method is actually for knowledge base purpose about all possible ways to root N950 (exynos), also to note that you shouldn't use this method if your device have OEM issue. We recommend all to use above said method for all in PART1
Here is detailed guide about Root Galaxy Note8. Guide made in two sections, One who want root + Custom recovery and second Root without flashing custom recovery.
1.Root with TWRP (Recommended method) You can root with SuperSU OR Magisk
Root with TWRP is preferred method as it gives option to flash zip like mods,custom ROMs etc
Root with SuperSU
1.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
2.Enable OEM Unlock from developer option (Currently no workaround for those who doesn't have this option)
3.Download SuperSU (I have used SuperSU 2.82 SR4) to Ext SD card. Here is Original thread to see if any update available.
4.Download TWRP for N8
5.Switch Off device
6.Press Vol down + Bixby + Power to reboot to download mode, press volume up when asked to continue to download mode
7.Download Odin and open it, Disable 'Auto reboot' from option menu of Odin
8.Select TWRP (tar image) with AP tab of Odin and Start
9.Once Successfully flashed, you will see 'Passed' in Odin tab
10.Disconnect device and hold Vol down + power till screen goes off, Now immediately press Vol Up + Bixby + Power to reboot to TWRP
11.Select to allow modification
12.From TWRP, Select WIPE menu - Then FORMAT DATA - You need to type 'yes' to perform wipe. WARNING : This will erase all data including Int SD storage from device
13.Once format device completes, go back and select REBOOT' Menu and then - 'RECOVERY', This will reboot to TWRP again
14.Now select Install and navigate path to Ext SD card - SuperSU, you have copied earlier
15.Once SuperSu flash successfully, Reboot to System
Keep patience and allow device to boot, It may take time as we have formated data.
Once device boot, you will have SuperSU in app drwer with working boot.
---------------------------------------------------------------------------------------------------------------------
Root with Magisks
1.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
2.Enable OEM Unlock from developer option (Currently no workaround for those who doesn't have this option)
3.Download and copy latest Magisks zip to Ext SD card
4.Download TWRP for N8
5.Switch Off device
6.Press Vol down + Bixby + Power to reboot to download mode, press volume up when asked to continue to download mode
7.Download Odin and open it, Disable 'Auto reboot' from option menu of Odin
8.Select TWRP (tar image) with AP tab of Odin and Start
9.Once Successfully flashed, you will see 'Passed' in Odin tab
10.Disconnect device and hold Vol down + power till screen goes off, Now immediately press Vol Up + Bixby + Power to reboot to TWRP
11.Select to allow modification
12.From TWRP, Select WIPE menu - Then FORMAT DATA - You need to type 'yes' to perform wipe. WARNING : This will erase all data including Int SD storage from device
13.Once format device completes, go back and select REBOOT' Menu and then - 'RECOVERY', This will reboot to TWRP again
14.Now select Install and navigate path to Ext SD card -Magisks zip, you have copied earlier
15.Once Magisk flash successfully, Reboot to System
Keep patience and allow device to boot, It may take time as we have formated data.
Click to expand...
Click to collapse
2. Root with Stock Recovery
This will give just root access and No custom recovery. (you can't flash custom ROM, mods zip with stock recovery but still can use FlashFire or similar.
There are two ways, you can root with stock recovery
1.CF Auto Root (superSU)
1. Download CF Auto root package Thanks to @ChainFire and MobiFirmware
2.Extract and read ReadMe.txt for details
3.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
4.Enable OEM Unlock from developer option (Currently no workaround for those who doesn't have this option)
5.Switch Off device
6.Press Vol down + Bixby + Power to reboot to download mode, press volume up when asked to continue to download mode
7.Download Odin and open it
8.Select Image.tar.md5 (From you have download CF root package above) with AP tab of Odin and Start
9.Once Successfully flashed, you will see 'Passed' in Odin tab
Device will get Reboot with root access
2.Magisk
1.You need to have stock firmware, Extract boot.img file from that firmware with winzip or similar
2.Install Latest Magisk Manager
3.Open it and explore settings - Patched Boot Output format - select img.tar
4.Now again from main page of Magisk Manager click Install - Install - Patch Boot Image File and patched the boot.img
5.Copy patched_boot.img.tar to a PC from MagiskManager directory on Int Storage
6.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
7.Enable OEM Unlock from developer option (Currently no workaround for those who doesn't have this option)
8.Switch Off device
6.Press Vol down + Bixby + Power to reboot to download mode, press volume up when asked to continue to download mode
7.Download Odin and open it, Disable 'Auto reboot' from option menu of Odin and
8.Select patched_image.tar (You copied as step 5 above) with AP tab of Odin and Start
9.Once Successfully flashed, you will see 'Passed' in Odin tab
10.The phone restarts and ask to reset to factory settings, This will erase all data from device
11. Let reboot device and install Magisk manager again and open it. Now you will have root.
12.You can install FlashFire and re flash Magisk zip again to have magisk module to work.
Click to expand...
Click to collapse
PART3 :
EFS Backup Tool Note8 /S8 /S8+
This is simple EFS backup tool. We are very well knowing about what EFS is and why it is MUST to backup on every rooted device. If you don't know then Read post #3 for more Information
You needs root access to use this tool otherwise app won't open..
Location of stored file :
Device storage/MyEFS
If you unable to see backup, contact me with details of your device variant
Difference between Free/Play store
-Both version makes backup in same format and no difference in backup.
-Pro Version always look for backup, if there is no backup then it will make one just after boot. Also it will make backup if your last backup is made on different ROM than existing. Also it will give warning if backup fails.
-Pro version keeps all previous backup to MyEFSBackup folder (you can choose to make extra copy on Ext SD too) while XDA version overwrites previous one and you need to make manual copy if you want to have multiple copies.
-Pro version have option to Restore with single click
Click to expand...
Click to collapse
This tool using generic name of partition block and you can restore with simple adb shell
dd if=/path of backup files/ of=/partition block according your device
Download EFS Backup Tool :
PlayStore version
XDA version
ChangeLog :
1.0
- Initial Release (4696)
1.1 (2650)
- S9/S9+ added to supported list
- Fix probable issue with SuperSu and Magisk (16.4) on Oreo
1.2
- Compatible with latest magisk
which models of phone it is for or where to find TWRP for the Note 8?
What is EFS
This part of the device contains some important and some basic info related to our device identity like Bluetooth MAC address, wireless devices MAC addresses, product code (also in the nv_data.bin) and the very main IMEI address (nv_data.bin), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things. So you can guess it's will be different for each device and one can't use others. In latest samsung device this information store in other partition so requires to make backup of that partition too.
How it can corrupt :
- Any bad flashing, mishandling system modification can cause this.
- Also It can be corrupted by downgrading stock ROM. If you flash any old ROM on newer ROM it can corrupt EFS. Basically newer ROM believed to have new kernel that changes EFS data which older Modems can't read and results to fail in reading IMEI.
Impact on device/How I know I have corrupted EFS
When there is EFS partition is corrupted, device loses IMEI and due to this device can't gets connected to network. Baseband info also sometimes shows unknown.
-Check your IMEI in setting / by dialling *#06# if it is null OR if it starts with 0049** then IMEI is generic and corrupted. In Normal case IMEI which you can see in device setting or dialing *#06# is exactly same you can see on bill/box/sticker under battery compartment
-If you are unable to connect to network in spite of correct IMEI, chance are
A. Your device is Locked to specific Network OR
B. Your device is banned due to tempered IMEI
-If your AP,CP,CSC all are correct and even you are getting error (unknown CSC XXX) on kies update, it may be due to corrupt Product code in EFS. Read This for detail.
What care should i take
Before flashing anything, first thing you should do is to make EFS backup. Every person who have rooted device should make EFS backup earliest and place it to safer place on PC and /Cloud.
If you are on older ROM, make EFS backup on older ROM as well make another after upgrading ROM too.
If you have already updated to newer ROM, make backup on current ROM.
Exit "Permanent Safe Mode" This condition represent with loss of IMEI + yellow text box on homescreen with device info.here is Screenshot
{
"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"
}
Here is different method to remove it.
Method1 :
Open root explorer.
Navigate to /efs/FactoryApp/
Open "factorymode" file as Text and edit it:
Change this:
Code:
OFF
To:
Code:
ON
Open "keystr" file as Text and edit it:
Code:
OFF
To:
Code:
ON
Reboot device.
Method2:
Open Terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Write the following & click enter:
Code:
rm /efs/FactoryApp/keystr
Write the following & click enter:
Code:
rm /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
echo -n ON >> /efs/FactoryApp/keystr
Write the following & click enter:
Code:
echo -n ON >> /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
chown 1000.1000 /efs/FactoryApp/keystr
Write the following & click enter:
Code:
chown 1000.1000 /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
chmod 0744 /efs/FactoryApp/keystr
Write the following & click enter:
Code:
chmod 0744 /efs/FactoryApp/factorymode
Reboot your device
Method3
Install attached safemode_exit apk as regular app. Open from drawer - Grant su permission - Reboot when asked.
e:failed to mount /efs(invalid argument) error with bootloop
This condition usually happens with using unsupported tool (usually from play store).
To recover this, needs to use adb shell
Code:
adb shell
mke2fs / dev/block/mmcblk0p[COLOR="Red"]x[/COLOR]
mount-w-t ext4 / dev/block/mmcblk0p[COLOR="red"]x[/COLOR] / efs
x means your device EFS partition number
PS : It needs CWM and busybox installed.
You may want to put in your OP that this is for Exgynos only.
OEM Unlock Options
My note 8 doesn't have oem unlock in developer option
any news for oem unlock enabling (tool)?
any idea about how to root?
Regards
Same here, no OEM unlock option in dev tools
Some users reported it appear after 5 days
Here below is separate thread for that.
https://forum.xda-developers.com/galaxy-note-8/help/info-note-8-exynos-n950f-fd-oem-unlock-t3673140
.
any chance for this root to work on the Snapdragon 835 model of Note8 ?
dr.ketan said:
Some users reported it appear after 5 days
Here below is separate thread for that.
https://forum.xda-developers.com/galaxy-note-8/help/info-note-8-exynos-n950f-fd-oem-unlock-t3673140
.
Click to expand...
Click to collapse
i'm not developer
but you can make custom rom and flash with odin
any idea?
Thanks
nader1450 said:
i'm not developer
but you can make custom rom and flash with odin
any idea?
Thanks
Click to expand...
Click to collapse
How one can flash ROM without custom recovery? Also to use FlashFire or similar, you need a rooted device. There is nothing can be done before this option (OEM Unlock toggle) appear, or at least something can be done to make appear this option, it must be through odin by faking samsung binary.
samsung live chat:
that device note 8 after registered also dose not support OEM unlock
any idea?
nader1450 said:
samsung live chat:
that device note 8 after registered also dose not support OEM unlock
any idea?
Click to expand...
Click to collapse
Stop asking the same questions over and over again. All OEM unlock issues should be referred to the thread mentioned above.
Thank you for the guide Dr., much appreciated!
Hello, sir. Thanks for this informative post. I Rooted my Samsung Galaxy Note 8. And published all the steps which I followed to root it at Andro Root. There are some modification in the steps. With Proper Attribution. Here:- How to Root Samsung Galaxy Note 8
nader1450 said:
samsung live chat:
that device note 8 after registered also dose not support OEM unlock
any idea?
Click to expand...
Click to collapse
Samsung Live Chat is staffed by below average imbeciles. You might as well ask your dog.
Wait 7-10 days after you first turned on the device then check in Developer Options for the OEM Unlock option.
nader1450 said:
samsung live chat:
that device note 8 after registered also dose not support OEM unlock
any idea?
Click to expand...
Click to collapse
Cry yourself to sleep
---------- Post added at 07:51 AM ---------- Previous post was at 07:50 AM ----------
AllGamer said:
any chance for this root to work on the Snapdragon 835 model of Note8 ?
Click to expand...
Click to collapse
Can't unlock the bootloader on Snapdragon devices so no.
Op is updated with links as well added different methods to root.
dr.ketan said:
Op is updated with links as well added different methods to root.
Click to expand...
Click to collapse
Thank you Dr.
Any idea when we will see your EFS back up tool?
xxx42069 said:
Thank you Dr.
Any idea when we will see your EFS back up tool?
Click to expand...
Click to collapse
Probably finish by tomorrow. Today working on Folder Mount with magisk
Just rooting , with the third option , does this trip knox ?
Not flashing any recovery I mean , just the simple root .....
Anyone know please ?
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
How I can install twrp and flash gsi rom on Doogee N20?
I found this but I'm doesnt know Russian: pda.ru/forum/index.php?showtopic=955032&st=1220#entry89836105 (I cant post URL because I'm new user, so I delete the "4" from "4pda")
Sorry for my bad English.
צבי זלצברג said:
How I can install twrp and flash gsi rom on Doogee N20?
I found this but I'm doesnt know Russian: pda.ru/forum/index.php?showtopic=955032&st=1220#entry89836105 (I cant post URL because I'm new user, so I delete the "4" from "4pda")
Click to expand...
Click to collapse
That's the Google translation:
A little instruction on how to get RooT. And so, everything that you do, as always, is at your own peril and risk! All data is erased when unlocked! Make BACKUP !!! Is always!!!! I. Unlocking Boorloder-a (required for flashing the phone and everything connected with it): 1. Go to settings -> system -> About phone -> Build number (7 clicks) (Congratulations !!!! You are a developer!) < - About phone -> For developers: Enable USB debugging and OEM unlocking. 2. We connect the phone to the computer and install the ADB usb driver (on the Internet), a connection request should appear on the phone, you need to allow it. 3. Extract files from the N20_utils.rar archive (10.87 MB) (preferably not very far, the root of the disk or the created folder N20 will be there). Go to the Unlocked Bootloader folder and run the bat file, the phone will reboot and display the request "unlock? Yes / no" rocker up - yes / rocker down - no. Naturally, you need to press the volume up, otherwise there were so many actions)) 4. Congratulations! Now, with each reboot, you will have an Orange state (5-second inscription), and the ability to do whatever you want with your phone. II. We sew! 1. For the lazy (who value their time). Download the SP Flash tool (Internet), from the N20_utils.rar archive (10.87 MB) select MT6763_Android_scatter and boot_magisk_20 files for the boot partition, lk_pached for lk, etc. you can even twrp instead of native recovery. Turn off the phone, connect it to the computer and click Download in the SP Flash programs. After the OK circle appears, disconnect and reconnect the cable (easier than a forced reboot). We turn on the phone and put the magisk manager (internet). Congratulations!!! You have a root and no Orange State label! 2. Who wants more and himself: phone to computer -> go to the Unlocked Bootloader folder -> run CMD -> write "fastboot flash recovery" put a space and move the TWRP file with the mouse to the window (fast path to the file) and press ENTER -> reboot the phone to fastboot. Congratulations!!! you have TWRP. Boot into TWRP, skip the encrypted DATE message, go to formatting and format the DATE. Go to mount and connect MTP. A phone will appear on my computer, we drop the files DisableForceEncryption_Treble (disable date encryption), orange_state_disabler_v0.3 (remove orange_state) and magisk.zip (internet) into the memory section. In TWRP, click install all this and rejoice! 3. Who has nothing to do at all: go to the forum thread Development and porting of GSI firmware (Post bullik01 # 71222655) and try what catches your eye. Not all are loaded, but .... (although we do not seem to have an A / B structure, but only "arm64 A / B" were launched) PS: look for additional information here on the forum and for brotherly devices UMiDIGI A5 Pro - Firmware ( Post Xakep1993 # 86772223) Attached files recovery-TWRP_3.3-20191015-1714.img (22.81 MB) DisableForceEncryption_Treble.zip (4.24 MB)
jwoegerbauer said:
That's the Google translation:
A little instruction on how to get RooT. And so, everything that you do, as always, is at your own peril and risk! All data is erased when unlocked! Make BACKUP !!! Is always!!!! I. Unlocking Boorloder-a (required for flashing the phone and everything connected with it): 1. Go to settings -> system -> About phone -> Build number (7 clicks) (Congratulations !!!! You are a developer!) < - About phone -> For developers: Enable USB debugging and OEM unlocking. 2. We connect the phone to the computer and install the ADB usb driver (on the Internet), a connection request should appear on the phone, you need to allow it. 3. Extract files from the N20_utils.rar archive (10.87 MB) (preferably not very far, the root of the disk or the created folder N20 will be there). Go to the Unlocked Bootloader folder and run the bat file, the phone will reboot and display the request "unlock? Yes / no" rocker up - yes / rocker down - no. Naturally, you need to press the volume up, otherwise there were so many actions)) 4. Congratulations! Now, with each reboot, you will have an Orange state (5-second inscription), and the ability to do whatever you want with your phone. II. We sew! 1. For the lazy (who value their time). Download the SP Flash tool (Internet), from the N20_utils.rar archive (10.87 MB) select MT6763_Android_scatter and boot_magisk_20 files for the boot partition, lk_pached for lk, etc. you can even twrp instead of native recovery. Turn off the phone, connect it to the computer and click Download in the SP Flash programs. After the OK circle appears, disconnect and reconnect the cable (easier than a forced reboot). We turn on the phone and put the magisk manager (internet). Congratulations!!! You have a root and no Orange State label! 2. Who wants more and himself: phone to computer -> go to the Unlocked Bootloader folder -> run CMD -> write "fastboot flash recovery" put a space and move the TWRP file with the mouse to the window (fast path to the file) and press ENTER -> reboot the phone to fastboot. Congratulations!!! you have TWRP. Boot into TWRP, skip the encrypted DATE message, go to formatting and format the DATE. Go to mount and connect MTP. A phone will appear on my computer, we drop the files DisableForceEncryption_Treble (disable date encryption), orange_state_disabler_v0.3 (remove orange_state) and magisk.zip (internet) into the memory section. In TWRP, click install all this and rejoice! 3. Who has nothing to do at all: go to the forum thread Development and porting of GSI firmware (Post bullik01 # 71222655) and try what catches your eye. Not all are loaded, but .... (although we do not seem to have an A / B structure, but only "arm64 A / B" were launched) PS: look for additional information here on the forum and for brotherly devices UMiDIGI A5 Pro - Firmware ( Post Xakep1993 # 86772223) Attached files recovery-TWRP_3.3-20191015-1714.img (22.81 MB) DisableForceEncryption_Treble.zip (4.24 MB)
Click to expand...
Click to collapse
Hi, were you by any chance able to get a copy of these files ,Please upload if posssible
The original links are broken and the internet seemed to wipe all traces out, I'm looking for the N20_utils and possibly the Disable force encryption one
Good day
Had the same problem, (English not so good but I know you'll understand). What I did was just installing Corvus OS rom, the 11th version. It's been quite a while since i installed it.
Tried Lineage 18.1 and adding the smallest gapps available, but everytime i get code error 1. I guess it was the twrp 3.3 version i used cause some roms requer the latest TWRP versions. The lineage is installing just right nd can reboot to system with no hiccups.
None of Android 12 gsi versions has ever been able to installed. Cause when i try to install, i get the error of "file too large for the target partition. Tried everything from the net to increase the system partition to at-least 3gig. No success.....
Is anyone who can help to install android 12 even beta version will be ok for my N20 Doogee??
Thanx
flairepathos.info said:
Hi, were you by any chance able to get a copy of these files ,Please upload if posssible
The original links are broken and the internet seemed to wipe all traces out, I'm looking for the N20_utils and possibly the Disable force encryption one
Click to expand...
Click to collapse
The file is in the forum. But to make your life easier here are the link.
https://drive.google.com/drive/folders/18B-srDVia_H4aDt7uvCDUxg2e4R5kVVY?usp=sharing The file is of type .exe and that extracts when you run on the pc, the problem is that I was suspicious about the virus so I threw the file in the total virus (if you don't know what it is, just search) and 6 programs pointed it out as malware but many others didn't find anything including karpersky and bit defender, there to make sure the files were there i renown they from .exe to .zip and I looked and the files really were there but as I don't want to take the risk I didn't extract and I didn't even try anything. The file that fix the encryption are inside doogee n20.exe, the guy said it will be in .exe and when you run it extracts the file in the C folder of the computer I recommend you to rename it from .exe to .zip because if the file have a virus you can screw your pc when running
Da-Judges said:
Good day
Had the same problem, (English not so good but I know you'll understand). What I did was just installing Corvus OS rom, the 11th version. It's been quite a while since i installed it.
Tried Lineage 18.1 and adding the smallest gapps available, but everytime i get code error 1. I guess it was the twrp 3.3 version i used cause some roms requer the latest TWRP versions. The lineage is installing just right nd can reboot to system with no hiccups.
None of Android 12 gsi versions has ever been able to installed. Cause when i try to install, i get the error of "file too large for the target partition. Tried everything from the net to increase the system partition to at-least 3gig. No success.....
Is anyone who can help to install android 12 even beta version will be ok for my N20 Doogee??
Thanx
Click to expand...
Click to collapse
you can use the pixel experience lite https://github.com/ponces/treble_build_pe/releases ( remenber the lite version, because is 2,5 gig) i try and instal in my phone and worked but i cant access my storage so i search and here are the solution https://forum.xda-developers.com/t/...loop-after-any-custom-rom-doogee-n20.4357313/ i dont try it but if you want here are the solution
flairepathos.info said:
Hi, were you by any chance able to get a copy of these files ,Please upload if posssible
The original links are broken and the internet seemed to wipe all traces out, I'm looking for the N20_utils and possibly the Disable force encryption one
Click to expand...
Click to collapse
Hi, did you find N20_utils?