[GUIDE][PORT] TWRP 3.0.X for Mediatek Devices.
Requirements:
1. Windows/Linux/Mac PCs.
2. OFFICIAL CyanogenMod 13 Support
3. DSIXDA Kitchen.
4. Patience.
5. A bit of Computer Knowledge
6. Getting Recovery Partition Size of MTK Chipset (Google It)!
This Method is Universal Cross-Chipset Method means you can port Snapdragon Recoveries even to your MTK. dosen't matter 32bit or 64bit MTK Processor.
{
"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"
}
Thanks to @Dees_Troy for his Nexus Recoveries.
Step 1: Setting Up!
(i) Download your CyanogenMod Recovery from download.cyanogenmod.com.
(ii) Download DsiXDA Kitchen
(iii) If your on WINDOWS download CYGWIN to launch DSIXDA Kitchen.
(iv) Setup Done!
Step 2: Executing!
EXAMPLES YOU CAN USE OTHER RECOVERIES ALSO BUT AS SAME RESOLUTION AS YOUR DEVICE:
IF YOUR ON 480x850, 480x854 download: https://twrp.me/devices/lgnexus4.html latest TWRP 3.x Available!
IF YOUR ON 720x1280, 800x1280 download: https://twrp.me/devices/asusnexus720123g.html latest TWRP 3.x Available!
IF YOUR ON 1080x1920 download: https://twrp.me/devices/motorolanexus6.html latest TWRP 3.x Available!
Once Downloaded!
Download your CM RECOVERY from download.cyanogenmod.org/ Find your device codename and download.
Step 3: Setting Up Kitchen!
Note: In most cases of Commands Windows/Linux/Mac are same in different i will mention.
If Windows:
Code:
(i) Open Cygwin
(ii) cd <user_name>
(iii) cd kitchen
(iv) ./menu
If Linux/Mac
Code:
(i) Open Terminal
(ii) cd <kitchen_source_dir>
(iii) ./menu
Minimize The Kitchen Never Close.
Step 4: Setting up WORKING Directory
(i) Open Kitchen Installed Directory.
(ii) Make a new folder named WORKING_twrp
(iii) Copy your downloaded nexus_twrp.img to WORKING_twrp
(iv) Rename twrp.img to boot.img
Step 5: Unpacking STOCK and PORT
(i) Open DsiXDA kitchen back.
(ii) Type Options in Line:
Code:
0
12
w
press enter
(iii) Type Options in Line: If your following me as above just follow next command.
Code:
a
(iv) Now a new folder will be created in kitcher_dir named boot.img-xxxxxx (instead of xxxx some numbers) paste your downloaded cm recovery.img to boot.img-xxxxxx folder.
(v) Rename cmrecovery.img to boot.img
(vi) Open Kitchen Press Enter to continue.
NOW: BOOT-EXTRACTED = PORT
boot.img-xxxxxxxx = BASE
Copy Replace Files from BASE TO PORT and delete file in PORT:
Code:
COPY AND REPLACE FROM BASE TO PORT:
/zImage
/boot.img-ramdisk/default.prop
/boot.img-ramdisk/fstab.<codename>
/boot.img-ramdisk/uventd.rc
/boot.img-ramdisk/etc/recovery.fstab
/boot.img-ramdisk/etc/twrp.fstab (if exist no prob if it dosen't exist in PORT)
Code:
DELETE FILES FROM PORT:
/boot.img-ramdisk/fstab.<portcodename>
Step 6: Lets Repack!
Open DSIXDA Kitchen Back On!
Type Option in Line:
Code:
If you didn't close kitchen it will be minimized continue this:
[B]Option:[/B]
b
OUTPUT= /kitchen_dir/WORKING_twrp/boot.img This is your TWRP Recovery the OLD one has been replaced with REPACKED ONE
Make Sure You Provide Me PORT GUIDE Credits
I HOPE YOUR ENJOYING MY WORK :good: :laugh:
Q/A:
1. Will this Work on Above Resolution than 1080p?
A. Yes!
2. Is it mandatory to have official CM Support?
A. Yes! Because, CM and OMNI ROMS are only one which can build TWRP and CM is only one which even makes CM13 Recovery.
3. Must CM13 be based on 6.0.1 itself?
A. No, the CM Recovery Can be also on 6.0 but not 5.1 or bellow.
4. Why CM Recovery?
A. As per my knowledge CM Recovery is based on CWM as well as TWRP. so it will be easy to port TWRP for your device.
4. Bootloop?
A. Make sure you followed Step 5 Properly! and clear command line using kitchen (Options in line: 0, 12, p, press enter, press enter) if still bootloop is being faced try a different recovery!
5. Are you sure this will work? It's Not working for Me!.
A. Yes it will I am making UNOFFICIAL TWRP 3.x for my Sprout Devices: http://forum.xda-developers.com/cro.../unofffical-twrp-3-0-2-0-android-one-t3358636
Good job
Gửi từ EVA-AL00 của tôi bằng cách sử dụng Tapatalk
29y6145 said:
Good job
Gửi từ EVA-AL00 của tôi bằng cách sử dụng Tapatalk
Click to expand...
Click to collapse
Thanx
@HostZero
Err, only the sprout devices have official cyanogenmod support. You should probably change the first step to "extract the stock recovery from your device" but great work anyways! Sorry for being such a wuss over PM. My bad.
Sent from my PixelV1 using XDA Labs
MSF Jarvis said:
@HostZero
Err, only the sprout devices have official cyanogenmod support. You should probably change the first step to "extract the stock recovery from your device" but great work anyways! Sorry for being such a wuss over PM. My bad.
Sent from my PixelV1 using XDA Labs
Click to expand...
Click to collapse
No issue, I am found a new and easy way, you don't even need recovery, you can use boot.img too.. i will update Post soon.
HostZero said:
No issue, I am found a new and easy way, you don't even need recovery, you can use boot.img too.. i will update Post soon.
Click to expand...
Click to collapse
Yeah, if I remember correctly that's how stock ROMs replace the custom recoveries on first boot, by taking the boot.img, applying the recovery-from-boot.p patch on it and then flashing it as recovery.
Sent from my PixelV1 using XDA Labs
touch
im port twrp but touch no working
USB storage can't not mount on pc. Please help me to fix
No Joy in Mudville
Can not get the ported TWRP to recognize ANY storage on my device - MTK 6753. Looks very nice but that's about it. Any suggestions?
HostZero said:
No issue, I am found a new and easy way, you don't even need recovery, you can use boot.img too.. i will update Post soon.
Click to expand...
Click to collapse
please update the thread, show us the new way using boot.img
you might want to ...
If the device you are porting FROM has the same chipset and general parameters (e.g. RAM) as the device you are porting TO, try not moving ANYTHING from the ramdisk folder or sub folders. Just replace all the other stuff from the top level folder with what is in your stock recovery. You will probably need to tweak the recovery.fstab file in 'ramdisk\etc' when you are done but that seems to be a workable approach. At least it worked for me. I just removed a half-dozen or so references to things that don't exist on my unmodified device, TWRP stopped having a canary about them not being there, and I was good to go. And YES, I DID confirm that a backup and restore brought back everything I thought it should.
NOW, if we could just get all these Chinese phone makers to more or less agree on mount points and partition naming - yeah, right. Who am I kidding ??
U think this will work on a samaung device that runs on MTK6737T....GALAXY j2 prime?
hi @HostZero
Need solution ,i port 3.1.0-1 from samsung galaxy s8 on cubot dinosaur mt6735 and booted all ok ,backup worked and all worked fine but restore no ,can you tell me what is problem
error mesages is
e:Unable to find file system first (first period)
e:Unable to find file system first (first period)
e:unknown restore method for ''/system''
e:adb restore failed
thenks again
Hi,
I ported twrp to my device ,I used MTK THAI developer tool to port
I used twrp of intex aqua star power
To intex aqua speed HD
everything working fine but
Its not Detecting internal storage
It gives E:unable to mount internal storage,invalid argument
And in file manager option when I enable the mtp ,pc detecting as intex aqua star power .
When I backup boot it backup whole OS , not only boot.
Please help me ,where its gone wrong
Thank you
Does Device Need CM13 Support?
Thank you for this great post.
You wrote that you can use any recovery image that has the same resolution as your device, but then later wrote that you need to use the CM13 recovery image specific to your device. Do I need both?
I want to root a Digiland DL8006 (MTK8127, 1280x800, Android 7.0), but CM13 does not support it. I’m really hoping I don’t need the CM13 recovery file to do this.
Just a query !
JUST A QUERY :
Which image did you use from stock firmware ? (recovery.img or boot.img)
curious because i saw /boot.img-ramdisk/xxxxxxx in OP.
As far i know both recovery & boot image contains ramdisk,so i was
Again recovery.img or boot.img which one should i use from stock rom ?
Thank you very much for this tutorial !
I would like to ask please:
Usually I find in most "rooting tutorial" that 1st stage is unlocking bootloader.
Isn't that required here ?
Thanks,
ranran
ranchu-panchu said:
Thank you very much for this tutorial !
is unlocking bootloader.
Isn't that required here ?
Click to expand...
Click to collapse
Yes it is required, OP must have forgot to write it.
Android Image Kitchen works better than Android Kitchen. Just ported a TWRP, so I am saying this on experience. A few extra steps like editing recovery.fstab and twrp.fstab are required.
Xiaomi Mi Play - Nickname = Lotus twrp
Hi! I have been struggling with getting twrp recovery for Xiaomi Mi Play - Nickname = Lotus but still could not find anywhere. Can I build my own twrp with this guide? and Some links are dead. Please help if you want to!
Related
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1
Main thread + Features + Dev support
http://forum.xda-developers.com/showthread.php?t=2201860
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1
PhilZ Recovery is a CWM Advanced Edition that adds all the features you could ever miss in CWM.
It is a well proven recovery for many phones.
Please give your feedback, what works, and any bug you could encounter.
Read the features at the Main thread, and check if you are missing something.
To take a screen shot, just slide left!
And don't forget to read about powerful aroma file manager integration and double-tap shortcut (in FAQs).
How to install recovery?
From download link below, you'll get a 'recovery.img' file. Put that recovery.img file at root directory of your
sdcard. (means not in any folder)
Now, go to terminal emulator.
Give command:
Code:
su
You'll be asked to grant superuser permissions, grant it.
Now, give the following command:
Code:
flash_image recoveryonly /sdcard/recovery.img
Wait until it executes the command (4-5 seconds), it is installing the recovery.
Now, normally reboot to recovery and enjoy new recovery!
Download links
Latest version can be found here:
recovery.img (v6.40.1)
https://docs.google.com/uc?id=0B5c3gpyMBJusXzRfRWg4TXhZdVE&export=download
aromafm_cooper.zip (v1.91)
http://www.upload.ee/files/3959191/aromafm_cooper.zip
Click to expand...
Click to collapse
Special thanks to:
@Phil3759 : For this awesome open source recovery.
@chraso: For hosting and compatible flags.
AndroidARMv6 Team: For keeping this device alive.
Cyanogenmod Team: For making all these possible.
XDA:DevDB Information
PhilZ Touch Recovery for Galaxy Ace, Tool/Utility for the Samsung Galaxy Ace S5830
Contributors
Bhargav97, chraso, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.40.1
Stable Release Date: 2014-05-04
Created 2014-05-07
Last Updated 2014-05-07
:FAQs:
Q: Wanna know about Aroma File manager?
Visit the aroma file manager main thread for more info---> Aroma file manager main thread
Aroma file manager is a touch file manager which can be used while in recovery. It has options for copy, paste, delete,
change permissions and many others. Also, it has a Terminal inside. So, if you forgot to give correct permissions to any
file you can do that directly from recovery. This file manager has got many themes, font, icons, etc. options and it's UI
is fully customizable.
Q: How to start this File manager in Recovery?
Rename the downloaded file to 'aromafm.zip'.
Create a folder 'aromafm' inside 'Clockworkmod' folder on your sdcard.
Now, move that 'aromafm.zip' file to the 'aromafm' folder.
We're ready now, when you want to use it in recovery just double tap anywhere OR go to "philz Settings" and select
"Aroma File Manager" and it will start up.
If you also want to browse /data, /system and /sd-ext then mount them in the "mounts & storage" option in recovery.
Q: Problems with Aroma file manager startup?
After doble-tapping OR selecting 'Aroma file Manager' option under 'philz settings' if recovery gives error: 'aromafm.zip
not found at /clockworkmod/aromafm' then, wait for 4-5 seconds and again select 'Aroma file Manager', because it maybe
busy mounting sdcard.
If still doesn't work, you've made mistakes in steps mentioned in first post, please do again carefully.
Q: Does your phone every time reboots to recovery?
This happens very rare when you flash the recovery using any bad app or via any wrong (not proper) method. What you can do
is:
-If you've made a backup of your current ROM then just restore only it's "boot" and then select 'reboot to system'.
OR
-You don't have a backup? Then just flash the ROM which you are using currently again and wipe 'dalvik-cache'. Then reboot
to system. Booting process will take time.
NEW: Now you can enjoy the full version of the recovery! Thanks to @Phil3759 for uploading necessary
commits for armv6. And, everything is expected to be bug-free. Please report the bug here if you find any.
SCREENSHOTS:
Main menu and PhilZ Settings
{
"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"
}
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
27 color settings + 5 alpha transparency levels for every GUI element
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original
cwm image
User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 30mn offset, super wipe option to install a new ROM
Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target
Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root
Very nice... will try it soon... :good:
Wow this should be great
I tried the recovery and it works. Installation is quick and simple and works just as described. Installing, wiping, backups, touch (up and down) and everything else works just as said. Kudos to you OP!
The last thing I wanna know:
After installing/restoring anything, can you successfully reboot to system?
You should also try Aroma File manager, it's the best part of this recovery.
Gonna Try...
@Bhargav97 i tested it , everything is working but there is one big problem , the recovery cannot reboot to system , it only reboot to recovery ,even if i shut down the device and then boot it , still stuck on recovery
hope you fix it
thanks for your hard work
Sent from my GT-S5830 using Tapatalk
nizar.nasani said:
@Bhargav97 i tested it , everything is working but there is one big problem , the recovery cannot reboot to system , it only reboot to recovery ,even if i shut down the device and the boot it , still stuck on recovery
hope you fix it
thanks for your hard work
Sent from my GT-S5830 using Tapatalk
Click to expand...
Click to collapse
Expect a fix soon!
I was understanding the problem for last few days (because same happens to other two devices also) and finally got the solution and I'll be re-compiling recovery as soon as I get some time.
UPDATE:
-Updated philz recovery sources to 6.23.9 (26.03.2014)
-cm-ota compatibility fixes.
-reboot to system bug is now fixed.
Download link updated in first post.
Am I dreaming? Thanks for revive my old Ace
Sent from my Nexus 5 using XDA Premium 4 mobile app
Bhargav97 said:
UPDATE:
-Updated philz recovery sources to 6.23.9 (26.03.2014)
-cm-ota compatibility fixes.
-reboot to system bug is now fixed.
Download link updated in first post.
Click to expand...
Click to collapse
swipe left and right dont work for me ????
Rhievaldo said:
swipe left and right dont work for me ????
Click to expand...
Click to collapse
Always Read OPs of a thread.
See my post #3, I've already stated that Right/Left swipe won't work yet. We're lucky to at least have a basic touch code implemented in our androidarmv6 sources. It is improving...someday if androidarmv6 developers plan to furnish the recovery touch code, right/left swipe will also be fixed. I can't fix that.
Bhargav97 said:
Always Read OPs of a thread.
See my post #3, I've already stated that Right/Left swipe won't work yet. We're lucky to at least have a basic touch code implemented in our androidarmv6 sources. It is improving...someday if androidarmv6 developers plan to furnish the recovery touch code, right/left swipe will also be fixed. I can't fix that.
Click to expand...
Click to collapse
always read it,, but forgot about that. Sorry... cause read it at 23 march, and try at 30 march..
MAJOR UPDATE:
PhilZ Recovery updated to 6.27.9.
PhilZ Recovery FULL VERSION now enabled (Touch, GUI options and everything!).
CWM updated to 6.0.4.8.
Ready for official support!
I seriously want feedback on this version. If it is working, we can now get our phone in "officially supported devices" list.
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJusUkVLRWJ2OVBXak0/edit?usp=sharing
everything seems to be working for me
---------- Post added at 06:43 PM ---------- Previous post was at 06:34 PM ----------
actually, all features work butkeeps rebooting into recovery,, not sure if its a problem restoring a back up ill try installing a new rom
edit,, yes it reboots into recovery no matter what,, damn,, nearly close to perfect
Bhargav97 said:
MAJOR UPDATE:
PhilZ Recovery updated to 6.27.9.
PhilZ Recovery FULL VERSION now enabled (Touch, GUI options and everything!).
CWM updated to 6.0.4.8.
Ready for official support!
I seriously want feedback on this version. If it is working, we can now get our phone in "officially supported devices" list.
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJusUkVLRWJ2OVBXak0/edit?usp=sharing
Click to expand...
Click to collapse
yes right when i reboot to system it reboot to recovery, the same as the previous time.
There was a little bug which caused issue for rebooting to system. I just fixed it and asked @chraso to compile. So, now finally it's done! Updated first, second and third posts.
Report back for the download link put up on first post.
i've test almost everything and i can say this is the best recovery ever made for ace ✌
thanks for bring it to our ace
sent from my kitkat ACE
One Click ROOT+TWRP Recovery for Lollipop Stock Firmware -----------------------------------------------------------------------
I recommend you to use AutoRec For Lollipop 20H from @[B]bender_007[/B]
@ingoljosh includes all version of autorec (D855, D852, D850, LS990 ...) in his post : Flash TWRP With AutoRec
First use OneClic Script ( by @avicohh ) to root your G3
Then install and use AutoRec to install the recovery custom
-----------------------------------------------------------------------Only for D855Only Lollipop (not KitKat)
(16GB/2GB and 32GB/3GB variants)Use only this tuto in case of failure with the previous quoted methodCredit
- @6ril1 for all his advice and convinced me to publish this method here
- @somboons and his post for the LG G2 : [TOOLS] One Click ROOT+TWRP Recovery for Lollipop Stock Firmware
Somboons have modified One Root Script ROOT KitKat / Lollipop firmware that for One Click ROOT+TWRP D802 firmware 30a/30d and I have updated his work for the LG G3 D855
- @avicohh for his One click script
- @thecubed for Bumps!
- @Unjustified Dev for send_command and his New Root Method for LG Devices
- @Chainfire for SuperSU
- G3 tuto on Frandroid
---------------------------------------------Download Link for Lollipop 20H:
Mega LGG3-D855-OneClickRootRecoveryV1.1.zip
Box LGG3-D855-OneClickRootRecoveryV1.1.zip
Dropbox LGG3-D855-OneClickRootRecoveryV1.1.zip
md5 : 33c50a727eecc9402ae1551e818b9615
---------------------------------------------
NEW
Download Link for Lollipop 20P:
Mega LGG3-D855-OneClickRootRecovery-V20P.zip
Dropbox LGG3-D855-OneClickRootRecovery-V20P.zip
md5 : a5f1776215dc6e9792e57efae400dcae
Download Link for Lollipop 20G:
Mega LGG3-D855-OneClickRootRecovery-V20G.zip
Dropbox LGG3-D855-OneClickRootRecovery-V20G.zip
md5 : 624a30b28037a6ed7023ea1f245c2aa8
@6ril1 thank to him for the bump of the 20P and 20G boot :good:
20P and 20G --> If you are not root having applied this tool, copy UPDATE-SuperSU-v2.46.zip on your SDCARD , restart on recovery mode and flash UPDATE-SuperSU-v2.46.zip
For those who used the LGG3-D855-OneClickRootRecoveryV1.1.zip version (for 20H) on the firmware:
- 20P download this file : Kernel fixed by @6ril1 (v20p) --> http://forum.xda-developers.com/showpost.php?p=60770468&postcount=1019
- 20G download this file : Kernel fixed by @6ril1 (v20G) --> http://forum.xda-developers.com/showpost.php?p=60940277&postcount=220
And use Flashify or your custom recovery to install this boot
For more informations see here : http://forum.xda-developers.com/showpost.php?p=60913483&postcount=23
Thank's @black_horse_88
---------------------------------------------
changelog:
http://forum.xda-developers.com/showpost.php?p=59926518&postcount=91
older version:
Mega LGG3-D855-OneClickRootRecovery.zip
Box LGG3-D855-OneClickRootRecovery.zip
Dropbox LGG3-D855-OneClickRootRecovery.zip
md5 : 9f0dfaa556e33457163cb7d57ebc6b1d
(recovery includes in LGG3-D855-OneClickRootRecovery.zip file: TWRP 2.8.6.1 w. Splash Screens/Modem/F2FS)
Backup Data on SDCARD Before doing everything
How to install
1 - Install LG drivers if they are not installed yet.
2 - Make sure you are enable USB Debuging Mode . (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging)
{
"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"
}
3 - Connect your phone to pc on PTP mode
4 - Extract LGG3-D855-OneClickRootRecovery.zip and double click on the OneClick_ROOT_RECOVERY.bat file, to run the script.
5 - Follow the instructions.
If the phone not recognize, try to switch between MTP and PTP options.
Watch the screen of your smarphone you could see this popup asking you to access to the G3
Of course, accept
Your G3 reboot several times.
If you see this message , reboot the G3 manually into Download mode
6 - Enjoy ROOT+TWRP on Lollipop Firmware
7 - Verify if you are root, you have custom recovery and working Download Mode
Problems and solutions
1 - @somboons describes the manual procedure on his original publication for the LgG2. If you have errors during the script you can try the manual procedure.
somboons said:
Normally If doesn't work for people please checking port that connecting between device and computer or checking LG driver and Re-run script again or use Manual method
What does the automate script do ?
(For people can't use automate script we have to use manually ROOT+TWRP)
Make sure you are enable USB Debuging Mode . See this Method > Enable Debugging Mode
1. Pushing all stuff files
Run file
Command Prompt.bat
Click to expand...
Click to collapse
It will be show command DOS windows
C:\Users\M\Desktop\LGG3-D80230a-OneClickRootRecoveryV1.1>
Click to expand...
Click to collapse
Using command as below to push files to device
adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp/ && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp/
adb.exe push aboot.img /data/local/tmp/aboot.img
adb.exe push laf.img /data/local/tmp/laf.img
adb.exe push boot.img /data/local/tmp/boot.img
adb.exe push recovery.img /data/local/tmp/recovery.img
Click to expand...
Click to collapse
2. Reboot to Download mode
3. When enter to Download mode successfully.We need to send command to connect device with computer
Send_Command.exe \\.\COM_PATH
Click to expand...
Click to collapse
COM_PATH . we can find with ports.bat command
Ex.
C:\Users\M\Desktop\LGG3-D855-OneClickRootRecoveryV1.1>ports.bat
C:\Users\M\Desktop\LGG3-D855-OneClickRootRecoveryV1.1>reg query HKLM\hardware\devicemap\SERIALCOMM
HKEY_LOCAL_MACHINE\hardware\devicemap\SERIALCOMM
\Device\LGANDNETMDM0 REG_SZ COM3
\Device\LGANDNETDIAG1 REG_SZ COM4
A command that send to device when connecting to computer with Download Mode is
C:\Users\M\Desktop\LGG3-D855-OneClickRootRecoveryV1.1>Send_Command.exe \\.\COM4
Click to expand...
Click to collapse
4. When we see this prompt
C:\Users\M\Desktop\LGG3-D855-OneClickRootRecoveryV1.1>Send_Command.exe \\.\COM4
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#
Click to expand...
Click to collapse
Try to use this command to ROOT+TWRP
# sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
Click to expand...
Click to collapse
5. When we see this message
ui_print - Disabling OTA survival
ui_print - Removing old files
ui_print - Placing files
ui_print - Post-installation script
ui_print - Unmounting /system and /data
ui_print - Done !
Please press Ctrl+C, and then type N and ENTER to reboot.
#
Click to expand...
Click to collapse
Try to use LEAVE command to restart device.
#LEAVE
Click to expand...
Click to collapse
6. Enjoy ROOT+TWRP
Click to expand...
Click to collapse
2- If you always have errors or blockings try this other manual method
1 - Apply this tuto : [GUIDE] New Root Method for LG Devices
2 - Then this one : http://forum.xda-developers.com/showpost.php?p=59931455&postcount=104
3 - If your G3 don't boot on system but you can go on Recovery and Download Mode
Your boot is not correctly flash and we have to make it by line of commands
Tuto here : http://forum.xda-developers.com/showpost.php?p=59962266&postcount=127
Good find, good job m8
Thanks for this solution and for the work done.
Hi, I'm currently rooted on stock lollipop but do not have recovery. Can I run this to give me custom recovery? Cheers
Smowza said:
Hi, I'm currently rooted on stock lollipop but do not have recovery. Can I run this to give me custom recovery? Cheers
Click to expand...
Click to collapse
+1
Sent from my LG-D855 using Tapatalk
Smowza said:
Hi, I'm currently rooted on stock lollipop but do not have recovery. Can I run this to give me custom recovery? Cheers
Click to expand...
Click to collapse
Yes you can
it's the twrp 2.8.6.1 version
Nice work.
Thx for the credit.
Huge Improvement!
HI @jac10000,
This is great! Way better than what I have posted.
I assume that this can be repackaged to cater to other LG G3 variants, by simply replacing aboot.img, laf.img, boot.img (users need to have this "bump'd" prior), and recovery.img (need to be "bump'd" prior as well) from those of their respective LG G3 variants, correct?
EDIT: I have promoted your approach in my how-to thread: http://forum.xda-developers.com/showpost.php?p=59897649&postcount=455
topet2k12001 said:
HI @jac10000,
This is great! Way better than what I have posted.
I assume that this can be repackaged to cater to other LG G3 variants, by simply replacing aboot.img, laf.img, boot.img (users need to have this "bump'd" prior), and recovery.img (need to be "bump'd" prior as well) from those of their respective LG G3 variants, correct?
EDIT: I have promoted your approach in my how-to thread: http://forum.xda-developers.com/showpost.php?p=59897649&postcount=455
Click to expand...
Click to collapse
Yes I think it's possible. I don't know the others models of G3 and their specific characteristics for installing custom recovery
jac10000 said:
Yes I think it's possible. I don't know the others models of G3 and their specific characteristics for installing custom recovery
Click to expand...
Click to collapse
HI @jac10000,
Great to hear.
Based on my experience in the Imageprep thread, installation of custom recovery is the same. I'll go ahead and try it out with my D858HK. Will let you know!
Does it make any difference if I have the LG G3 D855 16GB/2GB variant?
Can anyone report back?
@afilbit It work for 16go/2go and 32go/3go variants
Any other host for the file? Mega is blocked in India :/
@alsiladka Ok I do that , just a moment
https://app.box.com/s/qyquibqpnsh6tiq0kf8a7on2kyelvmf7
jac10000 said:
@alsiladka Ok I do that , just a moment
Click to expand...
Click to collapse
What would I need to provide to make this work on a f460k G3 Cat6? I have not found a bump'd boot.img to start with and don't fully understand how to make one myself.
Works great for my LG G3 D855 16GB. Big thanks! [emoji2]
Has anybody tried it on D855TR Turkish version?
BoredKender said:
What would I need to provide to make this work on a f460k G3 Cat6? I have not found a bump'd boot.img to start with and don't fully understand how to make one myself.
Click to expand...
Click to collapse
I do not know the specific obligations for the f460k. But for the D855 I extracted from kitkat Kdz the aboot.img and laf.img and copy them in the tools folder. I think you must use specific recovery Twrp for the f460k. For the bump boot, I have ever install recovery and bump boot by this method and I use here le boot.img includes in it.
Bump stock lp kernel can be made with linux :
http://forum.xda-developers.com/showthread.php?p=59806620
You need unpackbootimg and mkbootimg bin (you can compile them from source).
For the recovery, open bump in linux or the windows tool made for open bump should do the job
Success
Successfully completed process. TWRP installed and Download mode works. LG Stock OS (V20h-EUR-XX) was rooted before using "No Downgrade" method.
Details of my phone -
LGD855
32GB (European Model),
Software Version: V20h-EUR-XX
Thank you OP! You have just opened a new world for me.
{
"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"
}
MultiROM is one-of-a-kind multi-boot mod for Oneplus 3. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is encrypted).
MultiROM has 2 parts you need to install:
Modified recovery - You cand download the unified IMG file here, or specific for OP3 from second post and use fastboot or TWRP or Flashify app to flash it.
MultiROM - download the unified ZIP file here, or specific for OP3 from second post and flash it in recovery.
Go into TWRP MultiRom settings and check "Enable No-KEXEC Workaround"
Your current rom will not be erased by the installation.
Download links for specific OP3 version are in the second post.
WORKAROUND for FCs
If you get FC's in your secondary, edit build.prop in that secondary's /system dir and set:
Code:
#ro.sys.sdcardfs=true
...to comment the line (don't delete, don't set to false).
Don't boot before editing this line (flash secondary, edit and then boot).
You can edit in your primary if you are rooted, looking into:
Code:
/sdcard/multirom/roms/<your_sec_rom>/system/build.prop
*You can also try using multiromfix.zip, available in this post, thx to @Startrek852 (to disable sdcardfs support in that secondary).
Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 6.x after first boot takes 900+mb of space.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/MR-op3/multirom
Modified TWRP - https://github.com/MR-op3/android_bootable_recovery
MultiROM device tree - https://github.com/MR-op3/device_oneplus_oneplus3
Thanks a lot to Tasssadar for creating this awesome utility.
And to @nkk71 for the No-KEXEC workaround
MultiROM, Tool/Utility for the OnePlus 3
XDA:DevDB Information
MultiROM OP3/3T, Tool/Utility for the OnePlus 3
Contributors
martinusbe, BitOBSessiOn
Version Information
Status: Alpha
Current Beta Version: 3.0.3-2
Beta Release Date: 2017-02-12
Created 2016-07-10
Last Updated 2019-09-10
Reserved
Downloads
IT WILL NOT WORK WHEN ENCRYPTED
How-To by @bihariel
MultiRom for oneplus3
Recovery 08/03 Fixed usb-otg
multirom-20160814-v33b-UNOFFICIAL-oneplus3.zip
uninstaller
Update 11/26
Recovery 11/26
multirom-20161126-v33e-UNOFFICIAL-oneplus3.zip
Update 02/05/2017 op3
for new firmware 4.0.+, so older roms/kernels will not work on this!
AFH folder here
Update 02/20 by @BitOBSessiOn Unified
In post #1183
Update 03/10 Unified By BitOBSessiOn
recovery https://www.androidfilehost.com/?fid=745425885120713897
mr zip https://www.androidfilehost.com/?fid=817550096634752067
Update 08/07 by BitOBSessiOn
Post #1950
Flashable zip to fix your locksettings can be found here
MR Manager TBO 2016/08/17
Multirom Manager apk with oneplus support
Changelog:
- Darkened UI by @daveyannihilation #WhiteUImustDie
- Added icons for OOS, Tipsy, Tesla, Validus, Slim (needs the new zip flashed)
- Supports all Oneplus devices, Redmi2, Lux unoffically (to use the icons, the MR maintainer will need to update his MR zip)
MR Manager TBO 2017/04/21
Multirom Manager apk with added oneplus3T support
Flash recovery
Flash multirom zip
Enable kexec workaround in TWRP mr settings
Enjoy!
Reserved
Please read all about the no-kexec workaround from the author directly, (to avoid duplicity and get latest information), thanks to @nkk71
http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4
*Updated MultiROM Manager APK available here.
*FCs in secondaries should have been fixed in latest TWRP-MROM versions.
Thank you,
Hope someone can add support for Oxygen OS and a kernel with kexec support.
Hello, MultiRom does not recognize the recovery amends
bihariel said:
Thank you,
Hope someone can add support for Oxygen OS and a kernel with kexec support.
Click to expand...
Click to collapse
Its a first build, give me a minute, i have a family
jejemc said:
Hello, MultiRom does not recognize the recovery amends
Click to expand...
Click to collapse
i know
Great work bro :beer: :good:
Unreal work bro much alohas
And here we are!! Thanks a lot @martinusbe, working like a charm!
Superfast! Many thx! Can´t wait to get my oneplus3
Dope. Nice way to use cm13 if I need dash boot into oxygen OS awesome!!
Hey, booted into a secondary ROM and now Oxygen is throwing an "incorrect pattern" error. I remember there were some files to delete to fix this, but I can't remember which ones. (Maybe add it to the OP to prevent confusion?) Thanks for your time!
cunc-cam said:
Hey, booted into a secondary ROM and now Oxygen is throwing an "incorrect pattern" error. I remember there were some files to delete to fix this, but I can't remember which ones. (Maybe add it to the OP to prevent confusion?) Thanks for your time!
Click to expand...
Click to collapse
I am unable to boot OxygenOs, what process did you folowed?
And for the incorrect patern just go to twrp- file manager, navigate into /data/system and delete the files:
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
bihariel said:
I am unable to boot OxygenOs, what process did you folowed?
And for the incorrect patern just go to twrp- file manager, navigate into /data/system and delete the files:
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Click to expand...
Click to collapse
Thanks so much! By not being able to boot oxygen, do you mean as secondary or as primary? It must be unencrypted. Beyond that I don't know. It might be harder as secondary, I don't know if it would encrypt itself again.
I can boot into oxygen when it's the primary os through the given method, but it does take a few seconds of black before the boot animation shows.
cunc-cam said:
Thanks so much! By not being able to boot oxygen, do you mean as secondary or as primary? It must be unencrypted. Beyond that I don't know. It might be harder as secondary, I don't know if it would encrypt itself again.
I can boot into oxygen when it's the primary os through the given method, but it does take a few seconds of black before the boot animation shows.
Click to expand...
Click to collapse
My phone is decrypted and oxygen as primary. But i cant boot secondary roms, it always shows me the boot menu over and over.. when i select secondaries to boot.
I was able to boot only one time a sacondary rom. Must be there something am doing wrong.
bihariel said:
My phone is decrypted and oxygen as primary. But i cant boot secondary roms, it always shows me the boot menu over and over.. when i select secondaries to boot.
I was able to boot only one time a sacondary rom. Must be there something am doing wrong.
Click to expand...
Click to collapse
Huh. Be sure you checked the custom recovery setting related to kexec, I don't think that is supported on our device. Other than that, I'm as clueless as you
Its checked kexec warkaround. Injected sector boot. When i select secondary to boot, the phone reboots but it always goes back to boot menu... Will investigate a bit more...
touchscreen does not work on boot menu
Huge thanks for this port @martinusbe
FYI, I've tried all these roms as secondary, using the K-exec workaround. All are working very fine (device decrypted)
Beanstalk
ResurrectionRemix
Slim
Tipsy
Bliss
Thank you !
Edit : Just tried the MM apk, and it does not see the MM recovery, even tho it's already installed
Have you been in touch with Tassadar to have it official ?
bud77 said:
Huge thanks for this port @martinusbe
FYI, I've tried all these roms as secondary, using the K-exec workaround. All are working very fine (device decrypted)
Beanstalk
ResurrectionRemix
Slim
Tipsy
Bliss
Thank you !
Edit : Just tried the MM apk, and it does not see the MM recovery, even tho it's already installed
Have you been in touch with Tassadar to have it official ?
Click to expand...
Click to collapse
does touchscreen working for you?
Is anyone working on rooting this device? I just bought one and it seems to be a really nice tablet, except I'd prefer something other than touchwiz. Although I'd be perfectly happy with just rooting at least.
If there's no one rooting it, could someone help me find the resources to learn how to possibly root this device myself? I'm a beginner with modding android but I pick up things quickly so I'd like to at least give it a shot.
Yesterday I has rooted it via Magisk Manager APK v.5.5.3 & Magisk 15.2.
Procedure:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet MM APK.
4. Put "boot.img" on SDCARD.
5. Run MM, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point MM to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google regisery will be wiped.
11. After wiping & reboting install MM APK again... And YEAH!!! You got root!
Mefody said:
Yesterday I has rooted it via Magisk Manager APK v.5.5.3 & Magisk 15.2.
Procedure:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet MM APK.
4. Put "boot.img" on SDCARD.
5. Run MM, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point MM to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google regisery will be wiped.
11. After wiping & reboting install MM APK again... And YEAH!!! You got root!
Click to expand...
Click to collapse
Thank you so much! It worked perfectly!
You should post a thread detailing your instructions. Hell, I'll do it if you're too busy
shahmir_k said:
Thank you so much! It worked perfectly!
You should post a thread detailing your instructions. Hell, I'll do it if you're too busy
Click to expand...
Click to collapse
OK! Make this thread, cause I'm working now on TWRP for this tablet.
Please after thread creating place here link to it... :good:
Thank you for the solution
Mefody said:
Yesterday I has rooted it via Magisk Manager APK v.5.5.3 & Magisk 15.2.
Procedure:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet MM APK.
4. Put "boot.img" on SDCARD.
5. Run MM, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point MM to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google regisery will be wiped.
11. After wiping & reboting install MM APK again... And YEAH!!! You got root!
Click to expand...
Click to collapse
Thank you so much. I am a newbie to the whole rooting android thing. I came across this post when trying to root my SM-T385 tab and thought it was too complicated. I tried many other simpler methods and nothing worked. Finally, I took my time figure out your solution and lo-behold it actually works.:good:
I am now a proud owner of a rooted android tablet.
Thank you for the detailed write-up. Just got a new SM-T380 (already on 7.1.1) and would like to have root.
I followed the instructions and got to the Odin Flash part and the tablet came up with "Only official released binaries are allowed to be flashed". Had to hard reset to get it to boot again (w/o root).
Anyone know of a workaround or why didn't work on this one?
crewdog said:
Thank you for the detailed write-up. Just got a new SM-T380 (already on 7.1.1) and would like to have root.
I followed the instructions and got to the Odin Flash part and the tablet came up with "Only official released binaries are allowed to be flashed". Had to hard reset to get it to boot again (w/o root).
Anyone know of a workaround or why didn't work on this one?
Click to expand...
Click to collapse
You should activate "Developer mode" & in developers menu unlock OEM bootloader.
Mefody said:
You should activate "Developer mode" & in developers menu unlock OEM bootloader.
Click to expand...
Click to collapse
Thanks. I don't see "OEM unlock" in the developer now, so think I'm in the penalty box for a week. Bummer.
Mefody said:
You should activate "Developer mode" & in developers menu unlock OEM bootloader.
Click to expand...
Click to collapse
What's the firmware build number?
Im having the same issue, help please?
ashyx said:
What's the firmware build number?
Click to expand...
Click to collapse
My SM-T380 build number is: NMF26X.T380DXU1AQI7
Can't find a way to boot T380 to fastboot mode to run "fastboot oem unlock" unless it can somehow be done with ADB.
Thanks!!!
ashyx said:
What's the firmware build number?
Click to expand...
Click to collapse
I'm on T385XXU1AQJ3-20171116091340 now:
PDA/AP Version - T385XXU1AQJ3
CSC Version - T385OXE1AQJ1
MODEM/CP Version - T385XXU1AQHE
Build Date - 2017-10-30
OS - Nougat 7.1.1
Link to original firmware.
Link to patched "boot.img".
I see, You are guru in TWRP assembling . . .
So here is some sources & technical infos:
Link to kernel OpenSource.
Tablet technical name: gta2slte
Partition sizes from command "dd i= ... o= ..."
BOARD_BOOTIMAGE_PARTITION_SIZE := 33554432
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 33554432
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 3674210304
BOARD_USERDATAIMAGE_PARTITION_SIZE := 8053993984
BOARD_CACHEIMAGE_PARTITION_SIZE := 314572800
BOARD_PERSISTIMAGE_PARTITION_SIZE := 33554432
joeyw007 said:
Can't find a way to boot T380 to fastboot mode to run "fastboot oem unlock" unless it can somehow be done with ADB.
Thanks!!!
Click to expand...
Click to collapse
There is no "Fastboot Mode" in this model, like in many other from Sansung, HTC ets. Samsung also insert absolutely bad for ROM-creators KNOX system.
So here is S-shot for OEM is unlocked (and tablet is rooted)... But there no chances for "fastboot"
{
"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"
}
Under Linux I use Heimdall. Here is screen, where device are detected & ready to be flashed.
One thing about Heimdall... Version from repos didn't work with our device. So we have to compile it from Benjamin-Dobell github where this bug are fixed yet.
Building source is trivial:
Code:
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release ..
make
OEM Unlock Enabled On New Update
I contacted Samsung and spoke with them about the OEM unlock feature missing from developer options and explained I needed to root my table for development purposes for work. They gave me the usual reply of we don't support rooting. I replied I'm not asking you to. I'm asking you to unlock the boot loader on a device I bought, belongs to me and should be allowed to modify as I see fit. I am aware of security and warranty issues please do something about this. Remember Apples DE boggle. A few days later an OTA update puts the feature in my developer options. Coincidence or did they listen? Who knows. I will be trying the root procedure as soon as the new rom downloads and I can get the boot.img from the AP Block. I'll let you guys know how it comes out.
Root Achieved!!! For Cellular South Build T380XAR1AQK3
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet MM APK.
4. Put "boot.img" on SDCARD.
5. Run MM, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point MM to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google regisery will be wiped.
11. After wiping & reboting install MM APK again... And YEAH!!! You got root!
OK with the new update the boot loader can be unlocked from dev options and the above method for rooting is %100 successful. Just make sure to tell Magisk Manager under settings to output patched boot.img to odin mode "img.tar" then just flash the patched_boot.img.tar via the AP slot with Odin.
joeyw007 said:
Who knows. I will be trying the root procedure as soon as the new rom downloads and I can get the boot.img from the AP Block. I'll let you guys know how it comes out.
Click to expand...
Click to collapse
I know at last 3 person with the same situation... Sometimes, when we try to change region of firmware or try to root it out by progs like Kingo, Kingroot & CF-Autoroot it seems to Samsung, that You are dangerous hacker - and it set the 1-week "penalty" mode. So OEM-unblocking became disabled during this penalty period.
Like I said Who Knows, I am Curious...
I am curious if anyone missing the OEM Unlock feature in dev options running build T380DXU1AQI7 before this morning received an OTA update to build number T380XAR1AQK3 with the ability to unlock your bootloader from dev options. I haven't changed regions successfully flashed anything to this tablet and have had it for a month. OEM unlock appeared after OTA update this morning. Now I'm rooted and all is well. Before restarting your tablet if you root this build I would suggest turning OEM Unlocking on again after rooting, as it wipes your tablet, otherwise you will get an error message about not being able to boot unauthorized binaries and have to repeat the process.
Mefody said:
I'm on T385XXU1AQJ3-20171116091340 now:
PDA/AP Version - T385XXU1AQJ3
CSC Version - T385OXE1AQJ1
MODEM/CP Version - T385XXU1AQHE
Build Date - 2017-10-30
OS - Nougat 7.1.1
Link to original firmware.
Link to patched "boot.img".
I see, You are guru in TWRP assembling . . .
So here is some sources & technical infos:
Link to kernel OpenSource.
Tablet technical name: gta2slte
Partition sizes from command "dd i= ... o= ..."
BOARD_BOOTIMAGE_PARTITION_SIZE := 33554432
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 33554432
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 3674210304
BOARD_USERDATAIMAGE_PARTITION_SIZE := 8053993984
BOARD_CACHEIMAGE_PARTITION_SIZE := 314572800
BOARD_PERSISTIMAGE_PARTITION_SIZE := 33554432
Click to expand...
Click to collapse
If you could try this build of TWRP out. It's built using the T380 kernel, but should work for the T385 also.
https://androidfilehost.com/?fid=889964283620778312
.
ashyx said:
If you could try this build of TWRP out. It's built using the T380 kernel, but should work for the T385 also.
Click to expand...
Click to collapse
Thanks a lot!!! It works commonly fine!
Two moments:
1. CPU Temperature too high, as for me May be path to termal probe not correct.
2. /data partition are unmount. I think it's due to uncorrect "footer".
I started on github TWRP repo, but I have no enough experience - my build on minimal twrp-7. 1. manifest builds OK, but after flashing I have boot-loop.
Maybe You will kindly find some time to look at this repo: https://github.com/mefody1971/android_device_samsung_gta2slte
Some info regardly temperature & /data partition
BOARD_USERDATAIMAGE_PARTITION_SIZE := 8053977600 # 8053993984 - 16384 (footer)
TARGET_USE_CUSTOM_LUN_FILE_PATH := "sys/class/android_usb/android0/f_mass_storage/lun/file"
TW_BRIGHTNESS_PATH := /sys/class/leds/lcd-backlight/brightness
TW_CUSTOM_CPU_TEMP_PATH := /sys/devices/virtual/thermal/thermal_zone1/temp
In attachment I put recovery.log
Mefody said:
Thanks a lot!!! It works commonly fine!
Two moments:
1. CPU Temperature too high, as for me May be path to termal probe not correct.
2. /data partition are unmount. I think it's due to uncorrect "footer".
I started on github TWRP repo, but I have no enough experience - my build on minimal twrp-7. 1. manifest builds OK, but after flashing I have boot-loop.
Maybe You will kindly find some time to look at this repo: https://github.com/mefody1971/android_device_samsung_gta2slte
Some info regardly temperature & /data partition
BOARD_USERDATAIMAGE_PARTITION_SIZE := 8053977600 # 8053993984 - 16384 (footer)
TARGET_USE_CUSTOM_LUN_FILE_PATH := "sys/class/android_usb/android0/f_mass_storage/lun/file"
TW_BRIGHTNESS_PATH := /sys/class/leds/lcd-backlight/brightness
TW_CUSTOM_CPU_TEMP_PATH := /sys/devices/virtual/thermal/thermal_zone1/temp
In attachment I put recovery.log
Click to expand...
Click to collapse
The errors you are seeing are due to an encrypted data partition. TWRP doesn't support Samsungs encryption method yet.
To mount DATA you need to FORMAT the DATA partition and flash my encryption patch to disable encryption which you can find in my sig.
When I post a proper thread all instructions will be there. For now you can consult any one of my TWRP threads for more info.
ashyx said:
The errors you are seeing are due to an encrypted data partition. TWRP doesn't support Samsungs encryption method yet.
To mount DATA you need to FORMAT the DATA partition and flash my encryption patch to disable encryption which you can find in my sig.
When I post a proper thread all instructions will be there. For now you can consult any one of my TWRP threads for more info.
Click to expand...
Click to collapse
OK! Thanks a lot!!! Will find all available info and try to play with formatting /data partition & setting on Your patch.
Awaiting Your special thread for this device. Anyway - You did a great job :good:
{
"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"
}
Fastboot Enhance
What it can do?
- Show fastboot vars
- Switch between fastbootd & bootloader
- Switch between A & B slot
- Flash Payload.bin in fastbootd
- Flash images
- Erase partitions
- Delete logical partitions
- Create logical partitions
- Resize logical partitions
- Unpack Payload.bin
- Extract specific image from Payload.bin
- Show Payload vars
- Show dynamic partition metadata
And above all, it has friendly GUI
Download
Releases · libxzr/FastbootEnhance
A user-friendly Fastboot ToolBox & Payload Dumper for Windows - libxzr/FastbootEnhance
github.com
By using this, you can freely switch between different versions of HydrogenOS & OxygenOS & Custom ROMs.
It is mostly tested on 8T but should work fine on any device shipped with dynamic partitions.
Notes for fastboot visualization
- You need to pre-install related fastboot usb drivers to make sure the device can be recognize by the software.
- Only in fastbootd or bootloader mode can the software recognize your device.
reserved2
I wonder if this would work with kb2007 TMO to go to ColorOS? I will download a check it out, thanks for the contribution!
xzr467706992 said:
Fastboot Enhance
Click to expand...
Click to collapse
Dev
xzr467706992thanks for making this tool! I created (modified) a non-working OTA incremental update Linux program to install 11.0.9.9.KB05AA on my rooted Op8T (not available as a full update yet) and this program notified me that the -cow files, when I clicked on install from payload.bin, had to be deleted as they were temp files and taking up space in super - now I'm running an unreleased build (full update) on my Op8T!!! I have no idea where you found documentation on these temp -cow files, but it was the missing part of all my work!!! Without those logical files present, there was enough room in Super to install the fully updated Super components (odm, product, system, system_ext, and product)! And I have to say, your program is awesome!!! Intuitive interface, high functionality, and makes things just easier to see and do.
mslezak said:
Dev
xzr467706992thanks for making this tool! I created (modified) a non-working OTA incremental update Linux program to install 11.0.9.9.KB05AA on my rooted Op8T (not available as a full update yet) and this program notified me that the -cow files, when I clicked on install from payload.bin, had to be deleted as they were temp files and taking up space in super - now I'm running an unreleased build (full update) on my Op8T!!! I have no idea where you found documentation on these temp -cow files, but it was the missing part of all my work!!! Without those logical files present, there was enough room in Super to install the fully updated Super components (odm, product, system, system_ext, and product)! And I have to say, your program is awesome!!! Intuitive interface, high functionality, and makes things just easier to see and do.
Click to expand...
Click to collapse
Disregard I just found your thread
Great job
mslezak said:
Dev
xzr467706992thanks for making this tool! I created (modified) a non-working OTA incremental update Linux program to install 11.0.9.9.KB05AA on my rooted Op8T (not available as a full update yet) and this program notified me that the -cow files, when I clicked on install from payload.bin, had to be deleted as they were temp files and taking up space in super - now I'm running an unreleased build (full update) on my Op8T!!! I have no idea where you found documentation on these temp -cow files, but it was the missing part of all my work!!! Without those logical files present, there was enough room in Super to install the fully updated Super components (odm, product, system, system_ext, and product)! And I have to say, your program is awesome!!! Intuitive interface, high functionality, and makes things just easier to see and do.
Click to expand...
Click to collapse
Google has mentioned the copy-on-write(COW) device here
Virtual A/B Overview | Android Open Source Project
source.android.com
For virtual a/b, the COW devices are created during the process of update. When there's enough spaces in super, they'll be created there, otherwise they'll be created in /data/gsi/ota.
xzr467706992 said:
Google has mentioned the copy-on-write(COW) device here
Virtual A/B Overview | Android Open Source Project
source.android.com
For virtual a/b, the COW devices are created during the process of update. When there's enough spaces in super, they'll be created there, otherwise they'll be created in /data/gsi/ota.
Click to expand...
Click to collapse
Yes I found it there for "virtual A/B" just an hour or two ago actually. They don't explain it too well, however.
Please don't mind I have few doubts about how to use this.
1. Suppose I have installed a custom rom and now I want to go back to Oxygen OS, can I do it by flashing the payload.bin using this fastboot enhance tool? If yes, what exact steps I have to go through?
2. If I flash the payload bin using this tool, will my all partitions will be recreated automatically as it was in a fresh stock condition when I used this 8T for first time even if the custom rom did any mess up with size or anything else? Also will it cleanup inactive slot too?
Amsal1 said:
Please don't mind I have few doubts about how to use this.
1. Suppose I have installed a custom rom and now I want to go back to Oxygen OS, can I do it by flashing the payload.bin using this fastboot enhance tool? If yes, what exact steps I have to go through?
2. If I flash the payload bin using this tool, will my all partitions will be recreated automatically as it was in a fresh stock condition when I used this 8T for first time even if the custom rom did any mess up with size or anything else? Also will it cleanup inactive slot too?
Click to expand...
Click to collapse
Yes, you can switch between custom ROMs and OOS using this tool.
This tool will only flash partitions listed in payload.bin, that means other partitions will remain unchanged.
Logical partitions will be automatically resized during flashing.
This tool will not create snapshot & switch slot when flashing, which is different from a normal update or sideload. That means the current slot will be flashed with new images in payload.
Note that on 8T, only the current slot you are using is bootable because of virtual ab, DO NOT SWITCH SLOT.
xzr467706992 said:
Yes, you can switch between custom ROMs and OOS using this tool.
This tool will only flash partitions listed in payload.bin, that means other partitions will remain unchanged.
Logical partitions will be automatically resized during flashing.
This tool will not create snapshot & switch slot when flashing, which is different from a normal update or sideload. That means the current slot will be flashed with new images in payload.
Note that on 8T, only the current slot you are using is bootable because of virtual ab, DO NOT SWITCH SLOT.
Click to expand...
Click to collapse
Thanks for your clarification
So the exact steps to flash any rom(OOS, Custom Rom) would be:
1. Boot to fastbootd mode
2. Load the payload.bin in Fastboot enhance v1.8
3. Click the flash payload.bin
4. Reboot to recovery and wipe
5. Reboot to system
right?
Amsal1 said:
Thanks for your clarification
So the exact steps to flash any rom(OOS, Custom Rom) would be:
1. Boot to fastbootd/bootloader mode
2. Load the payload.bin in Fastboot enhance v1.8
3. Click the flash payload.bin
4. Reboot to system
right?
Click to expand...
Click to collapse
Yes but you need to reboot to fastbootd for logical partitions (also theres hint in software)
Btw remember to enter recovery and wipe data after flashing
xzr467706992 said:
Yes but you need to reboot to fastbootd for logical partitions (also theres hint in software)
Btw remember to enter recovery and wipe data after flashing
Click to expand...
Click to collapse
reboot to fastbootd for logical partitions? I didn't got this.
Sure I will wipe from recovery after flashing the rom!
Amsal1 said:
reboot to fastbootd for logical partitions? I didn't got this.
Sure I will wipe from recovery after flashing the rom!
Click to expand...
Click to collapse
That means: flash payload in fastbootd because we have logical partitions.
xzr467706992 said:
That means: flash payload in fastbootd because we have logical partitions.
Click to expand...
Click to collapse
How can I enter fastbootd mode bro ? Thank you
hieu76pro said:
How can I enter fastbootd mode bro ? Thank you
Click to expand...
Click to collapse
If you are in system
adb reboot fadtboot
If you are in bootloader
Press the "reboot to fastbootd" button in software
xzr467706992 said:
If you are in system
adb reboot fadtboot
If you are in bootloader
Press the "reboot to fastbootd" button in software
Click to expand...
Click to collapse
Thanks bro
I am getting this while trying to flash evo x rom payload.bin:
These are the two cow partitions I found:
Is it safe to delete these two partitions?
Amsal1 said:
I am getting this while trying to flash evo x rom payload.bin:
View attachment 5383121
These are the two cow partitions I found:
View attachment 5383123
Is it safe to delete these two partitions?
Click to expand...
Click to collapse
Yes if system update status is none