Related
This is a guide on rooting the new Chuwi Vi7 Phablet as a result of spending lots of hours on this proyect with the hope that others find it useful.
This is work in progress, do not attempt it if you are not ready to flash back the original rom in case you soft brick your Chuwi
PREREQUISITES:
A) For LINUX users:generally install the android-tools package so you have the adb command available.
In Manjaro linux and Arch Linux just do
Code:
sudo pacman -Sy android-tools
In Ubuntu probably
Code:
apt-get update && apt-get install android-tools
A) windows users would need to (presumibly; not tested)
For WINDOWS users:
install the intel drivers for android and user the attached adb.exe with dm-verity support
Most ADB.EXE do not have dm-verity. Try installing Java (prerequisite to install Android Studio) and installed Android Studio (download full package, but only install SDK part).
The file reported to work fine is android-studio-bundle-141.2117773-windows.exe
The ADB version is 1,011,200 bytes with date of 02/14/2015 07:12 PM.
1) (Recommended) Apply the over the air update; you know you have it when you can see the Google Playstore installed.
2) Connect your Chuwi Vi7 to your PC with a microusb cable
First we need the ability to write to the system partition so in order to do this, run these commands:
Code:
adb root
adb disable-verity
adb reboot
wait 30 seconds now we are going to do a backup of SYSTEM and DATA just in case
(if you are in Windows remove the ./ before system_068 and data_069)
This will take some minutes
Code:
adb boot recovery
Wait a few seconds until you are in the stock recovery
Code:
adb root
adb pull /dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID068 ./system_068
adb pull /dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID069 ./data_069
adb reboot
3) unzip the attached file and transfer all the individual files contained to the Chuwi´s /data/local/tmp folder
Code:
adb root
# Now we are going to push the whole folder contained in the archive we just extracted
adb push RootChuwiVi7 /data/local/tmp/
4) Now from a terminal run this command:
Code:
adb shell /system/bin/sh -x /data/local/tmp/vi7root
alternatively run
Code:
./rootnow
and that´s it!
Now open Root Verifier (it´s an app) to check if your Chuwi is rooted...
If you like my work dont forget to press the THANKS button and/or donate
TIPS: If you do not get prompted to allow root access by superSU, do adb root from the command line
If you need to flash the phablet here you can download the rom and flashing tool:
https://mega.nz/#!QVFCGDCa!oz4jXrxdsE6pJ4rVt4AlbUHN-VY9NwTF7SNfeir0mSk
Password: jopasaps
You need to install the intel drivers and the flash drivers and run Flash E2, load all the rom files, click on custom order, tick all the boxes, select generic usb, click on NEXT, turn off the phablet, then click on USB1 and very very quickly plug the phablet to your PC while holding VOLUME- you will see some activity in the screen and within 1 minute it will be ready.
If it is ready within 5 seconds then you did not load all the files. Depending on why your phablet is soft bricked it may be enough to flash only some of the files.
KNOWN ISSUES: Open Source superuser by koush does not work as the su binary needs recompiling. We are therefore using SuperSU by chain, I suggest you don't update SuperSU in the Play Store.
TROUBLESHOOTING: the command adb reboot ptest_clear is reported to work with soft bricked devices (put here as a courtesy, not needed in principle)
UPDATE: Download this file to update your SYSTEM partition to the latest version of the firmware, including some debloating and with English as default language. This update is done from recovery, through an adb push command
Thanks for this! I'm trying but can't get it to work. Running the script generates errors and I've boiled it down to doing the permissions -- I can't mount /system as RW no matter what syntax I've tried. I'm in the ADB shell and running under SU (#). Also tried mounting explicit as /dev/block/dm-0 but it still only comes back as "mount: Read-only file system".
Try again from the beginning, you will be able to mount read/write system now...
ALSO VERY IMPORTANT, download the new attachment and use instead ...
Thanks, I tried to disable verity before and it didn't work. I'll try again this time.
---------- Post added at 11:14 AM ---------- Previous post was at 11:11 AM ----------
Can you by any chance post your ADB.exe which has support for disable-verity command?
My adb is simple to install...
1) Install Manjaro linux
2) Run: pacman -Sy android-tools
and... that´s it! you get adb and fastboot
and no need to install android drivers
the sequence then I use to be able to write to the system partition on the Chuwi Vi7 is:
adb root
adb disable-verity (that needs to be done only once)
adb remount
Let me know whether it works in windows ...
TheAndroidGeek said:
Thanks, I tried to disable verity before and it didn't work. I'll try again this time.
---------- Post added at 11:14 AM ---------- Previous post was at 11:11 AM ----------
Can you by any chance post your ADB.exe which has support for disable-verity command?
Click to expand...
Click to collapse
casacristo said:
My adb is simple to install...
1) Install Manjaro linux
2) Run: pacman -Sy android-tools
and... that´s it! you get adb and fastboot
and no need to install android drivers
the sequence then I use to be able to write to the system partition on the Chuwi Vi7 is:
adb root
adb disable-verity (that needs to be done only once)
adb remount
Let me know whether it works in windows ...
Click to expand...
Click to collapse
For WINDOWS users:
I had various flavors of ADB.EXE and none of them had the dm-verity. Finally installed Java (prerequisite to install Android Studio) and installed Android Studio (download full package, but only install SDK part).
The file I used as android-studio-bundle-141.2117773-windows.exe
The ADB version is 1,011,200 bytes with date of 02/14/2015 07:12 PM.
Now rooted... but not sure what to do with this very low spec tablet I have so many other tablets (Onda, Teclast, Acer, etc).
Thanks casacristo!
Yeoh Master Shifu Arturo, its been awhile, how are you, only today notice your thread here, sorry for a little OT...
i own the first variance of x3(c3130), damn intel for making it so hard to root... :laugh:
Code:
[[email protected] ~]$ adb root
[COLOR="blue"]adbd cannot run as root in production builds[/COLOR]
[[email protected] ~]$ adb disable-verity
[COLOR="blue"]error: closed[/COLOR]
i was trying a different approach, root via recovery & i wonder if you have tried the FlsTool, can't figured out the correct commands to repack back ported custom recoveries...
Code:
[URL="https://github.com/android-ia/vendor_intel_build/blob/master/FlsTool/FlsTool"]FlsTool[/URL]
FlsTool v.1.21
This tool can do several different operations of FLS files.
Use the 'Action' option to select to required operation.
Actions:
-p [ --pack ] Packing multiple FLS files into one
-i [ --inject ] Inject NVM, Certificates or Security into FLS file
-x [ --extract ] Extract all image parts from the FLS file(s)
--extract-fls Extract embedded files from the FLS file(s)
--extract-prg Extract PRG file
-b [ --to-bin ] Convert a single Hex file to binary file
--hex-to-fls Create an Fls from a Prg file
--sign Formerly known as FlsSign
--to-fls2 [ arg ] Force output file format to Fls2
--to-fls3 [ arg ] Force output file format to Fls3
-d [ --dump ] Dump the meta data of an FLS file.
--sec-pack Dump all SecPack data of an FLS file.
HexToFls options:
--prg arg Choose a PRG file to create the Fls from
--psi arg Add a PSI to the Fls file (replaces if '-r' option)
--ebl arg Add an EBL to the Fls file (replaces if '-r' option)
--meta arg Inject any meta file to the Fls file (Equal to --version or -v in HexToFls)
--xml arg Add an XML file to the Fls file (replaces if '-r' option)
--zip arg Add a ZIP file to the Fls file (replaces if '-r' option)
--script arg Add a Script file to the Fls file (replaces if '-r' option)
--tag arg Specifies the memory region tag to insert the input file (replaces if '-r' option)
Inject options:
-n [ --nvm-path ] arg Path to the NVM input files
Generic Options:
-o [ --output ] arg Output path
-r [ --replace ] [ arg ] Defaults to replace when trying to add a section which is already existing
-v [ --verbose ] [ arg ] Set verbosity
--prompt [ arg ] Prompt before quitting
--version Show the version of this tool
-h [ --help ] Show command line help
Please specify an input file
@jasonx3
try this file:
https://mega.co.nz/#!UMVwTQIR!w04Pidyd2TRDLyWnqMfCL_qxXRtJmapD0UFmp0hQnx4
it is a full rom with root and gapps, with a script that flashes it (provided
you have a root shell)
@Vadim Shved
Can you be more specific?
I use link2sd without problems to convert apps to system apps.
do this:
adb root
adb remount
what is the output?
Hello Yuweng, good to see you, yes it has been a while... I don´t change hardware very frequently nowadays and not always I feel I can make a substantial contribution to the community
I have not used FlsTool but I have something to offer you....
Download this file:
https://mega.co.nz/#!UMVwTQIR!w04Pidyd2TRDLyWnqMfCL_qxXRtJmapD0UFmp0hQnx4
It is a complete dd copy of my system partition with a script that will verify the md5sum is correct and flash it.
I think this should work fine if you can be root though a recovery.
This system image has already root, busybox, google updates integrated
yuweng said:
Yeoh Master Shifu Arturo, its been awhile, how are you, only today notice your thread here, sorry for a little OT...
i own the first variance of x3(c3130), damn intel for making it so hard to root... :laugh:
Code:
[[email protected] ~]$ adb root
[COLOR="blue"]adbd cannot run as root in production builds[/COLOR]
[[email protected] ~]$ adb disable-verity
[COLOR="blue"]error: closed[/COLOR]
i was trying a different approach, root via recovery & i wonder if you have tried the FlsTool, can't figured out the correct commands to repack back ported custom recoveries...
Code:
[URL="https://github.com/android-ia/vendor_intel_build/blob/master/FlsTool/FlsTool"]FlsTool[/URL]
FlsTool v.1.21
This tool can do several different operations of FLS files.
Use the 'Action' option to select to required operation.
Actions:
-p [ --pack ] Packing multiple FLS files into one
-i [ --inject ] Inject NVM, Certificates or Security into FLS file
-x [ --extract ] Extract all image parts from the FLS file(s)
--extract-fls Extract embedded files from the FLS file(s)
--extract-prg Extract PRG file
-b [ --to-bin ] Convert a single Hex file to binary file
--hex-to-fls Create an Fls from a Prg file
--sign Formerly known as FlsSign
--to-fls2 [ arg ] Force output file format to Fls2
--to-fls3 [ arg ] Force output file format to Fls3
-d [ --dump ] Dump the meta data of an FLS file.
--sec-pack Dump all SecPack data of an FLS file.
HexToFls options:
--prg arg Choose a PRG file to create the Fls from
--psi arg Add a PSI to the Fls file (replaces if '-r' option)
--ebl arg Add an EBL to the Fls file (replaces if '-r' option)
--meta arg Inject any meta file to the Fls file (Equal to --version or -v in HexToFls)
--xml arg Add an XML file to the Fls file (replaces if '-r' option)
--zip arg Add a ZIP file to the Fls file (replaces if '-r' option)
--script arg Add a Script file to the Fls file (replaces if '-r' option)
--tag arg Specifies the memory region tag to insert the input file (replaces if '-r' option)
Inject options:
-n [ --nvm-path ] arg Path to the NVM input files
Generic Options:
-o [ --output ] arg Output path
-r [ --replace ] [ arg ] Defaults to replace when trying to add a section which is already existing
-v [ --verbose ] [ arg ] Set verbosity
--prompt [ arg ] Prompt before quitting
--version Show the version of this tool
-h [ --help ] Show command line help
Please specify an input file
Click to expand...
Click to collapse
Mine is a dual-sim c3130, ro.secure=1, ro.adb.secure=1, no adb while at stock 3e recovery, fastboot flash recovery twrp-recovery.img doesn't work, non of the existing exploit rooting software works, in fact, nothing works on this piece of sh#t but its so cheap... :laugh:
Got mine for less than a month, its a rebrand of Teclast X70, only last week the oem release the firmware, thats where i found out about FlsTool, its actually also available on Windows, i'll leave the linux copy here for everyone to explore...
Thanks! and by all means let us know if you succeed...
yuweng said:
Mine is a dual-sim c3130, ro.secure=1, ro.adb.secure=1, no adb while at stock 3e recovery, fastboot flash recovery twrp-recovery.img doesn't work, non of the existing exploit rooting software works, in fact, nothing works on this piece of sh#t but its so cheap... :laugh:
Got mine for less than a month, its a rebrand of Teclast X70, only last week the oem release the firmware, thats where i found out about FlsTool, its actually also available on Windows, i'll leave the linux copy here for everyone to explore...
Click to expand...
Click to collapse
casacristo said:
@Vadim Shved
Can you be more specific?
I use link2sd without problems to convert apps to system apps.
do this:
adb root
adb remount
what is the output?
Click to expand...
Click to collapse
I did everything from your tutorial. Root checker says that root is present. BUT! I cant do opearations with system partiotion. I tried to: 1)adb root 2)adb remount. After that in command promt I see that remount succeeded. Root checker say that root is present... But I still cant do anything. System partiotion cant be r/w
Edit: Sorry, but I thing that it is a problem of some apps that are not ready for android 5.1.x
Is there original rom available anywhere with tools to flash it? (got my vi7 in a state where it show only first "chuwi" logo, no "intel" logo - just black screen (but PC for example sees ADB interface; unfortunately "no permission"). I'm hoping that's only software problem.
Edit: CRANE_EVB firmware (seems to be some vi7 compatible device, not vi7 itself) finally worked. Required that I force (in devices manager) "intel usb driver for android devices" to be used for my detected chuwi vi7 "adb interface", then "adb.exe reboot ptest_clear" and it starts, no more black screen, no more "PTEST VER 1.41" problem etc.
Anyway still looking for original vi7 rom (not that crane_evb thing).
Anyone dare to flash TWRP pack with FlsTool, it should just brick the recovery only, if it doesn't work :fingers-crossed: then just flash back stock 3e recovery...
WARNING : Might brick your Vi7 but then again, you have the Firmware uploaded by OP to unbrick it... :laugh:
You might need to unlock the bootloader too...
Code:
adb reboot fastboot
fastboot oem unlock confirm
Updates - 01-Sept-2015
Huge Thanks to best98 for carrying out numerous of tests... :good:
Conclusion : No point to further develop custom recoveries, after unlocking bootloader, vi7 will refuse to boot unless you press Vol+ for 3 seconds then only it will boot up normally, no one would wanna do that...
{
"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"
}
best98 said:
Hi
So, I tried to flash stock 3e recovery..
Code:
"Warning: Chip mismatch. HW is [Sofia_3G_R] SW expects [Sofia_3G]
Device synchronized.
Using: Faster CRC, Writing all blocks , Skip data CRC , Skip protocol CRC
Start downloading item 'CUST:recovery.fls'' from file 'C:\Android\Chuwi_V7\stock-3e-recovery.fls''.
Checksum OK (0x0000)
Process time was 656 msec.
Total time was 1359 msec.
Channel 1 is succesfully closed."
Still boots with the green/red/black screen..
Did the fastboot eom lock
Code:
PS C:\> fastboot oem lock
...
(bootloader) Please confirm the device state action using the UI.
(bootloader) got key event 1
(bootloader) EV_DOWN received
(bootloader) got key event 2
(bootloader) EV_POWER received
(bootloader) Userdata erase required, this can take a while...
OKAY [ 11.506s]
finished. total time: 11.511s
Now, got the bootloop.. -> flashing the whole firmware : boots ok.
adb reboot fastboot
fastboot oem unlock
Code:
PS C:\> fastboot oem unlock
...
(bootloader) Please confirm the device state action using the UI.
(bootloader) got key event 1
(bootloader) EV_DOWN received
(bootloader) got key event 2
(bootloader) EV_POWER received
(bootloader) Userdata erase required, this can take a while...
OKAY [ 11.299s]
finished. total time: 11.300s
Black/green/red screen..
fastboot format cache + fastboot format data = same Black/green/red screen..
I hit 'Vol+' it goes forward.. shows Intel logo and boots..
Pierrick
Click to expand...
Click to collapse
fastboot oem unlock confirm
gets
< waiting for device >
and nothing else happens
yuweng said:
Anyone dare to flash TWRP pack with FlsTool, it should just brick the recovery only, if it doesn't work :fingers-crossed: then just flash back stock 3e recovery...
WARNING : Might brick your Vi7 but then again, you have the Firmware uploaded by OP to unbrick it... :laugh:
You might need to unlock the bootloader too...
Code:
adb reboot fastboot
fastboot oem unlock confirm
Click to expand...
Click to collapse
Is it possible to overclock this device? 900mhz.... it sucks.
Hmm.. I could try.. nothing to loose, but can't get the communication to work.
I unlocked the bootloader throug the Developer Option menu. Is it enough ?
yuweng said:
Anyone dare to flash TWRP pack with FlsTool, it should just brick the recovery only, if it doesn't work :fingers-crossed: then just flash back stock 3e recovery...
WARNING : Might brick your Vi7 but then again, you have the Firmware uploaded by OP to unbrick it... :laugh:
You might need to unlock the bootloader too...
Code:
adb reboot fastboot
fastboot oem unlock confirm
Click to expand...
Click to collapse
Thank You so much for participating in Development... :good:
Fyi, OP can't test b'cos he drop & break his vi7 while i'm having a different variance of x3...
First you need to unlock the bootloader & if you didn't then it will brick your vi7 but then again, you guys have the firmware to unbrick it...
Steps
If you're using Windows then download fastboot from here, if you're using linux then follow tips from OP
To reboot to fastboot => adb reboot fastboot -> There is no intel Droidboot, only green distorted screen but fastboot command works
To unlock bootloader -> fastboot oem unlock then follow PC on-screen for instructions & for formatting data & cache partition too. Mine have to issue the command fastboot oem unlock confirm
After this to reboot -> fastboot reboot
At PC, setup intel USB driver -> right click -> Run As Administrator
Start FlsTool -> Switch off your vi7 -> wait awhile -> Click at Next -> Click Start USB1 -> Plugin your vi7 & it'll download
After boot up Android -> adb reboot recovery & if TWRP doesn't boot then unplug USB, press & hold Power for 10 seconds & it power off then follow the same procedure to reinstall back stock 3e recovery
For more info, refer to the FlsTool attach pdf file for details
Additional info
At the Russian forum mentioned you'll need to check the option Manual (no auto start) while on my x3 with default Auto Start works fine...
Hi
Not changing the bootloader butusing a mix of the OP script and Chinese tablet -Intel Root- script worked.
One of the big deal was to have the ADB compatibility with "disable-verity" which is the last release.
Now, I will try to focus on TWRP.. but FLS with COM to USB mapping makes it a little bit complicated !
Pierrick
OK.. just tried this, and now, I have a green screen ..
Rolling back the 3e recovery worked but the result is still showing me, black/green and red lines.
Right now, tablet does not boot anymore, except those lines in green/black and red.. where no text is written - looks like locked inl in fastboot.
Willing to hear from you to get back the control of the tablet
Here are the settings I used - thumbnail !
BTW - attaching adb.exe that handles the disable-verity
yuweng said:
Thank You so much for participating in Development... :good:
Fyi, OP can't test b'cos he drop & break his vi7 while i'm having a different variance of x3...
First you need to unlock the bootloader & if you didn't then it will brick your vi7 but then again, you guys have the firmware to unbrick it...
Steps
If you're using Windows then download fastboot from here, if you're using linux then follow tips from OP
To reboot to fastboot => adb reboot fastboot -> There is no intel Droidboot, only green distorted screen but fastboot command works
To unlock bootloader -> fastboot oem unlock then follow PC on-screen for instructions & for formatting data & cache partition too. Mine have to issue the command fastboot oem unlock confirm
After this to reboot -> fastboot reboot
At PC, setup intel USB driver -> right click -> Run As Administrator
Start FlsTool -> Switch off your vi7 -> wait awhile -> Click at Next -> Click Start USB1 -> Plugin your vi7 & it'll download
After boot up Android -> adb reboot recovery & if TWRP doesn't boot then unplug USB, press & hold Power for 10 seconds & it power off then follow the same procedure to reinstall back stock 3e recovery
For more info, refer to the FlsTool attach pdf file for details
Additional info
At the Russian forum mentioned you'll need to check the option Manual (no auto start) while on my x3 with default Auto Start works fine...
Click to expand...
Click to collapse
Preface: I'm currently using this device and really like it, and as you all may have realised, that this device is considered as a low activity device on XDA, and no developers that I know of have taken a crack at this phone. This thread is to consolidate all information pertaining to the device.
If some area are empty, they will have more content in the future as we progress with this awesome device.
Feel free to post any mods that have worked (preferably in systemless mode)
Table of Contents:
Post 1) Rooting, TWRP and useful Links
Post 2) Info for Developers
Post 3) Roms & Mods
Post 4) Reserved
Useful Links:
My Github (Matt07211) containing kernel source code, to keep with the GPL licenses.
Samsung Kernel Source Code 4.4.4/5.1.1 and 6.0.1
Firmware Samsung xCover 3 and Samsung xCover 3 Value Edition
TWRP for Samsung xCover3 (Kit Kat)
TWRP for Samsung xCover3 Value Edition Credits: @Heledir for the link
SuperSU
Prerequisites:
ADB Installed
USB Debugging Enabled
Samsung USB Drivers Installed
Samsung ODIN (Preferably Odin3_v3.10.7 or above)
A Brain that can use common sense, or Google
Disclaimer:
Anything you do with your own phone is done at your own risk. Don't complain if you accidentally brick your phone. Fix it by using Google, flash back stock firmware or post on XDA for help.
Knox will probably be voided, and so will your warranty.
We cannot say what works for us, may or may not work for you.
Good luck
Using ODIN:
1) Enable USB Debugging, and OEM Unlock (If available), these can be reached from the developer menu. The develpoer menu can be activated by taping "Build Number" 7 times in the about section.
Don't disable OEM Unlock (Ever) once modifing your phone, because FRP (Factoy Reset Protection) will be activated, and then you will be forced into reinstalling stock firmware, aalnd losing all your data in the process.
2) Turn phone off, boot into download mode (Power + Volume Down + Home) and then press Volume Up to use download mode when greeted with a yellow warning.
3) Launch ODIN, and plug phone into Computer. You should see some text like this "ID:COM" in blue.
4) Click the AP button (If it says PDA then you have an older version of ODIN, and are recommended to use a newer version) and Select the file that will be flashed. E.g. TWRP or a Boot.img. Making sure the only options ticked are "F.Reset Time" and "Auto-Reboot". If you are flashing a recovery (E.g. TWRP) then make sure "Auto-Reboot" is unticked, and when ODIN says successful flash then you'll have to then reboot the phone your self(Either by holding any combination of Volume Keys (Any one) + Power + Home or Removing the Battery and Placing back in) and reboot straight into recovery (at least once, else the stock recovery will replace TWRP on a normal boot bu a script called "install-recovery.sh").
5) If "Auto-Reboot is ticked, then the phone will automatically reboot once flashing has been completed.
Root:
SM-G388f:
KitKat:
1) Enable USB Debugging
2) Download the Newest TWRP from the above TWRP Link (the one marked with KitKat), making sure you download the file with the .img.tar extension.
3) Download the Newest SuperSu and place on the internal phone memory.
4) Flash the downloaded TWRP file, make sure "Auto-Reboot" is unticked (Refer to "Using ODIN" if needed). Click Start
5) Once flashed, reboot into recovery (Power + Volume Up + Home) straight away and Flash SuperSu.zip via the Flash Zip section.
Congrats you got root on KitKat
Lollipop:
Installation:
1) Make sure you have the prerequisites installed, and "xcover3-lollipop-root.zip"
unzipped. Then type
Code:
adb devices
to make sure adb recognises the phone and that its authorized.
2) Type (or copy) exaclty as below. *Please be paitent, as the first command
takes about 20 seconds to complete.
Code:
adb push su.img /data/local/tmp
adb install Superuser.apk
3) Once thats completed, turn off the device and then boot into download
mode (Volume Down + Home + Power).
4) Open the ODIN program, click "AP" then navigate to the "boot.tar.md5"
file that is in the "xcover3-lollipop-root: folder, then click open/okay.
Click start to flash.
5) The phone should auto-reboot. Once its fully booted, reboot once more
(perferabbly twice), this is to allow the script placed in the ramdisk to
move the su.img to /data.
6) Profit? Yay you've now got root. You can go and test it out by downloading
terminal emulator and typing "su", you then should be prompted to grant root
permissions to the app. Once granted, the "$" symbol will change to "#" to
signify root.
Thanks to:
@akuhak Thanks for build the custom tools necessary to modify the boot.img
@proguru Thanks for compiling a custom kernel for me, (for testing purposes) allowing me to test various things.
@kniederberger Thanks for providing the boot.img and su.img from the Value edition of the phone, allowing me to base my work around what was done on the value editon.
SM-G389f:
Marshmallow:
*Verified by @Heledir and @kniederberger
A user has uploaded a YouTube video HERE in case anyone wants a video tutorial.
1) Enable "OEM UNLOCK" and "USB Debugging" in developer settings (This can be found by tapping build number 7 times, then developer mode will be activated) then procedded to Flash TWRP.
2) Flash the Value Edition version of TWRP, Link at the top of this thread, making sure it has ".img.tar" extension (Refer to "Using ODIN" if needed).
3) Flash SuperSu.zip inside of TWRP via the Flash Zip section
Update to Newer Firmware while rooted:
Note: You'll lose root (re-root via relevant method) and modifications done to /system, but you're Apps and Data (/data and internal storage) will remain untouched.
0)Although you won't lose any apps/data, it's always recommended to make a backup. Perferrable a Nandroid backup or the backup of apps and data via the means of Titanium Backup and such.
1) Download Newest firmware matching the phones region and carrier (basically if the phone is from one country, dont download the firmware intended for a different country. Links at top of OP/Thread.
2) Out phone into download more, launch Odin and Flash the firmware package Downloaded. (Refer to the Using Odin section as needed.)
3) Give it some time for the inital reboot, and allow it to get setup and booted.
Optional) Re-root via relevant methods.
Un-root Samsung XCover 3 Devices:
1) Click un-root from SuperSu APP
*5.1.1 and 6.0.1: Flash Stock boot.img (Found in stock firmware) (Will post a Link for stock boot.tar.md5 soon, or read on in the next post to figure out how to create your own boot.tar.md5 file)
TWRP:
KitKat: Working
Lollipop: Not Working (I'm looking into it) The is a hacked together version of TWRP HERE, in case people want to flash files. I wouldn't recommend it for anything else other then flashing, as i would perfer to build a proper working TWRP for lollipop.
Note: You'll have to hold, Volume Up + Home + Power buttons straightafter flashing from Odin, keep hold of the key combo untill you see the TWRP logo (2 reboots).
Marshmallow: Working
Flash Stock Firmware:
1) Download the stock firmware from above links, making sure the version and region matches your phone
2) As with the other steps, boot into download mode and connect it to Odin, click the AP button and click on the stock firmware. Then Click Start. (Refer to "Using ODIN" if needed)
3) Give it some time after flashing (Max 10mins) to boot and setup for the first time, if it doesn't after a long time, re-flash the stock firmware again.
FAQ:
- Where is a ROM/Custom Kernel/ TWRP(for lollipop) for our devices? I currently can't provide/make these due to internet limitations, and no access to a 64 bit computer(of course these may change for me in the future). Feel free to build and provide these, and they can get linked to one of the opening pots for easy access.
- What is this thread? It aims to bring all the current work being done on this device into a single thread, so its easily accessible for everyone
- XYZ App doesn't detect root (systemless root)? These apps haven't been updated to work with systemless root, and therefor require SuperSu compatibility mode to be enabled to work with systemless root. Refer to the Troubleshooting section below to fix.
- My Device is sluggish/slow at each boot, how can I fix this? I have noticed that certain apps when used, E.g. CF.Lumen, Livebootetc. require patching the sepolicy at each boot, and this is a memory intensive task. This may not be the only cause for sluggishness, other things can include alot of apps checking for notifcations by pinging their servers, or alot of apps auto starting at boot. There are two different ways about fixing this, one, uninstall offending apps (or disbale their automatic launch), or two, live with it, just wait a couple of minutes after booting before unlocking and using the phone, becuse by then their tasks should be done and android should have cleared up some RAM.
- I keeping getting notifications that my device is unsafe/had unautorized actions have taken place, how to stop this notification/warning? Refer to the Troubleshooting section below to fix.
Troubleshooting:
- XYZ App doesn't detect root (systemless root):
For Value Edition (Android 6.0.1):
1) Type "(or paste)
Code:
echo "BINDSYSTEMXBIN=TRUE" >> /data/.supersu[/CODE
2) Reflash the latest SuperSu.zip via TWRP][/INDENT]
[INDENT][B]For the Normal/Original xCover 3[/B] [I](Android 5.1.1., using my root method)[/I]:
Note: This fix is for the root developed by me, once/if we get a working TWRP for lollipop, then the above instructions should suffice. These 2 scripts creates and mounts a folder to xbin, allowing for apps that check for system root to work properly with systemless. Also daemonsu should mount the folder at boot automatically, but I was having problems with it, so that's why I have a second script to automatically mount the needed folder. Now to the instructions :)
1) Download the "systemless-compatability-fix-lollipop.tar.gz" onto the device and unzip it
2) Using a file explorer that works with systemless root, E.g. Solid Explorer, Copy and paste the 2 files inside the "/su/su.d" directory, making sure it's permissions is "0700" or "700", if the permissions are incorrect you can use the file explorer or terminal emulator and "chmod 0700" on both of the files, Refer to both of the files below for reference.
[img]http://forum.xda-developers.com/attachment.php?attachmentid=3948945&d=1480154633[/img]
[img]http://forum.xda-developers.com/attachment.php?attachmentid=3948946&d=1480154633[/img][/INDENT]
Now all root apps should work (I'm loooking at you Secure Settings and ES File Explorer Pro)
- I keeping getting notifications that my device is unsafe/had unauthorized actions have taken place, how to stop this notification/warning:
I haven't formmaly looked into the cause of this problem as of yet, but some users reported that disabling/removing "SecurityLogAgent" and/or "Smart Manager" Fixs the problem. This can be achieved using Titanium Backup (or similar apps).
[I][B]Planned Work:[/B][/I]
[HIDE]
- Do the next post write up on how to modify the boot.img (or other files) of the devices.
- Get working TWRP on Lollipop
- Get Magisk v9 working
- Look it what is need to flash MM from the xCover 3 Value Edition devices onto the Normal xCover 3 Most users have. (Might be difficult, as they have different hardware)
- Get some ROM creators onto this device [/HIDE]
Anything else?
Development for the xCover3
By Matt07211
This post aims to cover some relevant info for developers, aspiring developers, or tinkers that are missing a crucial piece or knowledge need for it to work on this device (xCover3). This thread will be more bias towards the Original xCover 3 running Lollipop, this just means my knowledge might be lacking in some areas due to differences in hardware (They have different chip-sets)therefor a difference in procedure. This Post assumes your using Linux and is biased towards Ubuntu, as its easiest for anyone to setup.
These post will be split up into categories, and when needed will indicate a difference in procedure between the devices.
Table of Contents:
1) General Setup (Dependices and Tools)
2) Boot and Recovery Modifications
3) System image modification (Also applicable to cache and hidden images found in firmware package)
4) Miscellaneous
Links:
- XCover3:
android_device_samsung_xcover3ltexx(To be added)
platform_manifest (To be added)
local_manifests (To be added)
android_kernel_samsung_xcover3ltexx
proprietary_vendor_samsung(To be added)
- XCover3 Value Edition:
android_device_samsung_xcover3ltexxve(To be added)
platform_manifest (To be added)
local_manifests (To be added)
android_kernel_samsung_xcover3ltexxve(To be added)
proprietary_vendor_samsung(To be added)
- General Setup
# Installing dependices (assuming Ubuntu >=15.04).
A 64-bit Operating system is needed when compiling ROMS, Kernels or Recoverys.
The dependices used are gathered from Android Establishing a Build Enviromentpage and Android Image Repack tools thread.
Code:
sudo apt-get update
sudo apt-get install git git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev libncurses5-dev x11proto-core-dev libx11-dev lib32z-dev ccache libgl1-mesa-dev libxml2-utils xsltproc unzip openssl libsdl-dev libesd0-dev valgrind libreadline6-dev x11proto-core-dev libz-dev gawk texinfo automake libtool cvs libsdl-dev
# Create Working Directory
It is also recommended to create a working directory for when working with android, keeping everything centeralized is helpful.
Code:
cd ~
mkdir android
# Compiling Android Image Repack Tools: Android Image Repack Tools is a kit of utilites for unpack/repack of android ext4 and boot images(Useful for working with android).
Refer to the thread linked above on different examples/instructions on using the binary files.
Note: I've provdided a copy of the precompiled binary files, compiled agianst android-5.1.1 branch on a 32-bit machine (meaning compatabile with 64/32 bit machines).
For Marshmallow:
Code:
cd ~/android
git clone https://github.com/ASdev/android_img_repack_tools
cd android_img_repack_tools
git checkout android-6.0.1
chmod +x configure
./configure
make
This creates the directory, downloads the source code, and creates the binary files.
For Lollipop (@AkuHaks version, extra tools included for the SM-G388F):
Code:
cd ~/android
git clone https://github.com/AkuHAK/android_img_repack_tools
cd android_img_repack_tools
chmod +x configure
./configure
make
# mkbootimg_tools, from xiaolu (Use for Value edition)
Code:
cd ~/android
git clone https://github.com/xiaolu/mkbootimg_tools
- Boot and Recovery Modifications
# Unpack boot and recovery
For Marshmallow:
Code:
cd ~/android/mkbootimg_tools
mkdir boot
./mkboot boot.img boot
usage: mkboot
unpack boot.img & decompress ramdisk:
mkboot [output dir]
[/INDENT]
Example output:
[CODE]
dt.img
img_info
kernel
ramdisk
ramdisk.cpio.gz
[/CODE]
For [B]Lollipop[/B]:
[CODE]
cd ~/android/android_img_repack_tools
mkdir boot
./pxa1088-unpackbootimg -i boot.img -o boot -p 2048
[/CODE]
Example output:
[CODE]
boot.img-base
boot.img-cmdline
boot.img-dt
boot.img-pagesize
boot.img-ramdisk.gz
boot.img-ramdisk_offset
boot.img-second
boot.img-second_offset
boot.img-signature
boot.img-tags_offset
boot.img-uImage
boot.img-unknown
[/CODE]
# Repack boot and recovery
For [B]Marshmallow[/B][I](Example, substitute names as necessary)[/I]:
[B]Note:[/B] I have yet to try a repacked boot.img on a Value Edition Variant
[CODE]
cd ~/android/mkbootimg_tools
./mkboot boot boot-new.img
[/CODE]
usage: mkboot
Use the unpacked directory repack boot.img(img_info):[INDENT]
mkboot [unpacked dir] [newbootfile]
[/INDENT]
For [B]Lollipop[/B][I](Example, substitute names as necessary)[/I]:
[CODE]
cd ~/android/android_img_repack_tools
./pxa1088-mkbootimg --kernel boot.img-uImage --ramdisk ramdisk-custom-supersu.cpio.gz --dt boot.img-dt --signature boot.img-signature --unknown 0x3000000 -o ../boot-supersu.img
[/CODE]
usage: mkbootimg [INDENT]
--kernel <filename>
[ --ramdisk <filename> ]
[ --second <2ndbootloader-filename> ]
[ --cmdline <kernel-commandline> ]
[ --board <boardname> ]
[ --base <address> ]
[ --pagesize <pagesize> ]
[ --dt <filename> ]
[ --ramdisk_offset <address> ]
[ --second_offset <address> ]
[ --tags_offset <address> ]
[ --id ]
[ --signature <filename> ]
-o|--output <filename>
[/INDENT]
# Ramdisk Unpack/Repack
Unpack
[CODE]
mkdir ramdisk
cd ramdisk
gunzip -c ../ramdisk.cpio.gz | cpio -i
[/CODE]
Repack
For [B]Marshmallow[/B]:
[B]Note:[/B] I have yet to repack the Value-edition/Marshmallow ramdisk so cannot verify it works (unlike lollipop), so if any errors please contact me. Feel free to try and unpack/repack the Value editon ramdisk/boot.img with lollipop instructions, if below doesn't work.
[CODE]
find . | cpio -o -H -R 0.0 newc | gzip > ../ramdisk-new.cpio.gz
[/CODE]
For [B]Lollipop[/B]:
[CODE]
./mkbootfs ramdisk-directory-name | ./minigzip > ramdisk-new.cpio.gz
[/CODE]
# Compile Kernel
Assumes kernel source is like "~/android/kernel" adapt paths as necessary.
For [B]Marshmallow[/B]:
[CODE]
cd ~/android
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9
export CROSS_COMPILE=~/android/arm-linux-androideabi-4.9/bin/arm-linux-androideabi-
cd kernel
make ARCH=arm xcover3velte_eur_defconfig
# You can run "make menuconfig" now if you want to customize the config file. E.g. Adding driver support, enable other features etc.
make ARCH=arm -j<number-of-cpus>
# E.g. "make ARCH=arm -j4"
[/CODE]
[B]Note:[/B] Replace the "<number-of-cpus>" in "-j<number-of-cpus>" with the number of processors you have plus one. For example if you have 4 cores then enter 5. If your getting errors then rebuild it with "-j1" then scroll up till you found the source of the error.
If the compile succeded the you should see "kernel: arch/arm/boot/zImage is ready"
For [B]Lollipop[/B]:
[CODE]
cd ~/android
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.8
export CROSS_COMPILE=~/android/aarch64-linux-android-4.8/bin/aarch64-linux-android-
cd kernel
make ARCH=arm64 pxa1908_xcover3lte_eur_defconfig
# You can run "make menuconfig" now if you want to customize the config file. E.g. Adding driver support, enable other features etc.
make ARCH=arm64 -j<number-of-cpus>
# E.g. "make ARCH=arm64 -j4"
[/CODE]
[B]Note:[/B] Replace the "<number-of-cpus>" in "-j<number-of-cpus>" with the number of processors you have plus one. For example if you have 4 cores then enter 5. If your getting errors then rebuild it with "-j1" then scroll up till you found the source of the error.
If the compile succeded the you should see "kernel: arch/arm64/boot/Image.gz is ready"
# Package Kernel into uImage (SM-G388F ONLY)
[CODE]
mkimage -A arm64 -O linux -T kernel -C gzip -a 01000000 -e 01000000 -d Image.gz -n "pxa1928dkb linux" "boot.img-uImage.new"
[/CODE]
# Generate kernel Specific device tree table (From Kernel Sources, Post-Compile)
[B]NOTE:[/B] This shouldn't need to be done as stock dt.img is the same, so use that. This is only here for educational purposes.
This assumes ~/android/kernel/ is you kernel source code directory. Substite paths as neccessary
For [B]Marshmallow[/B]:
Place either dtbTool or dtbToolCM (Depending on what your using), into ~/android/kernel/scripts and run the binary files from there.
If unable to create use the below binarys then try the lollipop instructions.
dtbTool
[CODE]
cp ~/android/mkbootimg_tools/dtbTool ~/android/kernel/scripts
cd ~/android/kernel
scripts/dtbTool -s 2048 -o arch/arm/boot/dt.img -p scripts/dtc/ arch/arm/boot/
[/CODE]
usage: DTB combiner:
Output file must be specified
dtbTool [options] -o <output file> <input DTB path>
options:
--output-file/-o output file
--dtc-path/-p path to dtc
--page-size/-s page size in bytes
--verbose/-v verbose
--help/-h this help screen
OR
dtbToolCM (support dt-tag & dtb v2/3)
[CODE]
cp ~/android/mkbootimg_tools/dtbTool ~/android/kernel/scripts
cd ~/android/kernel
scripts/dtbToolCM -s 2048 -d "htc,project-id = <" -o arch/arm/boot/dt.img -p scripts/dtc/ arch/arm/boot/
[/CODE]
For [B]Lollipop[/B]:
[CODE]
cd ~/android/android_img_repack_tools
./pxa1088-dtbTool -o boot.img-dt-new -p kernel/scripts/dtc kernel/arch/arm64/boot/dts/
[/CODE]
# Repack as Flashable Odin File (Substitute name as neccessary)
tar -H ustar -c boot.img > boot.tar
md5sum -t boot.tar >> boot.tar
mv boot.tar boot.tar.md5
[/CODE]
[/HIDE]
- System image modifcation
[HIDE]
<To be ADDED>
[/HIDE]
- Miscellaneous
[HIDE]
<To be ADDED>
[/HIDE]
Kernels:
- MyKernel - Custom power kernel series ! (SM-G389f) (Originally called: Devhost97 Kernel's ....) @Devhost97
-DiXCOVERy kernel (SM-G388f) @IXgnas
Roms:
- Flint & Steel ROM (Modded Firmware), planned realse is hopefully at beginning of next year. Follow its progress at the post HERE . Creator is @Matt07211 (Me)
Recommended Mods:
- Xposed using wanam's framework (Lollipop & Marshmallow),HERE, and use the newest XposedInstaller apk from, HERE. Flash the framework via TWRP.
- Arise Sound Mod, HERE. Flash via TWRP.
Recommend Root Apps, by Matt07211:
- Liveboot
- CF.Lumen
- Titanium Backup
- Adaway
- Kernel Auditor
- Terminal Emulator
Recommend Xposed Apps, by Matt07211
- <To be added>
Miscellaneous:
- Debloater Thread by @Sonof8Bits
<Reserved for Future Use>
<Reserved for Future Use>
Problem
Matt07211 said:
Preface: I'm currently using this device and really like it, and as you all may have realised, that this device is considered as a low activity device on XDA, and know developers I know of have taken a crack at this phone. This is where I come in, I like hacking into stuff for the challenge it presents, and I have set myself the challenge that is this device. This is a continuous learning experience for me and all, so I am by far not considered an expert.
If some area are empty, they will have more content in the future as we progress with this awesome device.
Feel free to post any mods that have worked (preferably in systemless mode)
Table of Contents:
Post 1) Root and TWRP
Post 2) Mods (Mostly Systemless versions)
Post 3) Roms
Post 4) --Reserved for future use--
Useful Links:
My Github (Matt07211) to keep with the GPL licences I will upload evrything onto my github (Also its a shameless plug )
My Github Pages Blog for guide on how I manually applied systemless update to boot.img (To be linked)
Samsung Kernel Source Code 4.4.4/5.1.1 and 6.0.1
Firmware Samsung xCover 3 and Samsung xCover 3 Value Edition
TWRP
SuperSU
Prerequisites:
ADB Installed
USB Debugging Enabled
Samsung USB Drivers Installed
Samsung ODIN
A Brain that can use common sense or google
Disclaimer:
Anything you do with your own phone is done at your own risk. Don't complain if accidentally brick your phone, use google, flash back stock firmware or post on XDA for help.
Knox will probably be voided, and so will your warranty.
We cannot say what works for use may work for you.
Good luck
Root:
KitKat:
1) Download the Newest TWRP from the above links, making sure you download the file with the .img.tar extension
2) Download the Newest SuperSu and place on the internal phone memory
3) Turn on USB Debugging
4) Turn phone off, boot into download mode (Power + Volume Down + Home) and then press Volume Up for use when greeted with a yellow warning.
5) Launch ODIN, and plug phone into Computer. You should see some text like this "ID:COM" in green
6) Click the AP button and Select the Downloaded TWRP file, make sure "re-partition" is unticked. Click Start
7) Once flashed, reboot into recovery and Flash SuperSu.zip
Congrats you got root on KitKat
Lollipop (Systemless Root) (EXPERIMENTAL, USE WITH CAUTION):
NOTE: This is currently in the experimental phase as I need users to test and verify that this works
1) Turn on USB Debugging and Download "xCover3-Lollipop-Root-Matt07211.zip" from here.
2) Turn phone off, boot into download mode (Power + Volume Down + Home) and then press Volume Up for use when greeted with a yellow warning.
5) Launch ODIN, and plug phone into Computer. You should see some text like this "ID:COM" in green
6) Click the AP button and Select the Downloaded ".tar.md5, make sure "re-partition" is unticked. Click Start
7) Once flashed, reboot the phone normally, making sure USB Debugging is turned on
8) Copy over "su.img", "Superuser.apk" and "xCover3-root.bat" (For Windows Users) or "xCover3-root.sh" (For Linux Users) into your ADB directory (E.g. android-sdk\platform-tools)
9) Open up a command prompt in the ADB Directory and type either "xCover-root.bat" for windows and for Linux run "xCover-root.sh"
10) Your Device should reboot, and you should have root. Now get an app and verify its existence
NOTE: This is EXPERIMENTAL so this might not work, or will take a few trys to get working, please post if this has worked for you.
Marshmallow:
*To Be looked into, please be patient
Un-root Lollipop and Marshmallow Devices:
1) Click un-root from SuperSu APP
2) Flash Stock Firmware or Stock boot.img (Will post a Link for stock boot.tar.md5 soon)
TWRP:
KitKat: Working
Lollipop: Not Working (I'm looking into it)
Marshmallow: Not Working (I'm looking into it)
Flash Stock Firmware:
1) Download the stock firmware from above links, making sure the version matches your phone
2) As with the other steps, boot into download mode and connect it to Odin, click the AP button and click on the stockfirmware. Then Click Start
3) Give it some time (Max 10mins) to boot and setup for the first time, if it doesn't after a long time, reflash the stockfirmware again.
Now look at the next post
Click to expand...
Click to collapse
When I click on AP in Odin and choose boot_systemless_root_matt07211.tar.md5 ,it just says md5 error binary is invalid. (tested on ODIN 3.12.3 and 3.10)
Oh sorry you said its not working nvm
EzChillzz said:
When I click on AP in Odin and choose boot_systemless_root_matt07211.tar.md5 ,it just says md5 error binary is invalid. (tested on ODIN 3.12.3 and 3.10)
Oh sorry you said its not working nvm
Click to expand...
Click to collapse
I tryed the root for Lollipop. Odin will no flash the tar.md5. There is one mistake by md5. If you rename the file to *.tar odin accept the file. if try to flash odin hang of with outprint analyse file. i wait on this for 10 min nothing goes happen.
I can try to flash with heimdall. for this i need the *img file
sorry for my bad english
EzChillzz said:
When I click on AP in Odin and choose boot_systemless_root_matt07211.tar.md5 ,it just says md5 error binary is invalid. (tested on ODIN 3.12.3 and 3.10)
Oh sorry you said its not working nvm
Click to expand...
Click to collapse
yy1 said:
I tryed the root for Lollipop. Odin will no flash the tar.md5. There is one mistake by md5. If you rename the file to *.tar odin accept the file. if try to flash odin hang of with outprint analyse file. i wait on this for 10 min nothing goes happen.
I can try to flash with heimdall. for this i need the *img file
sorry for my bad english
Click to expand...
Click to collapse
Well I'm stupid when I created it I was pretty tired, so I only included the md5 hash of the .tar file but not the .tar file itself as @yy1 has stated, it should be reuploaded in a couple of minutes. It should all work then, and now you have the file to flash and an md5 hash to compare it to make sure it isn't courrupt. Good luck and please report back to me of it was succesful @yy1 and @EzChillzz
Try to flash your boot.img. Reboot stop with KERNEL IS NOT SEANDROID ENFORCING (Android 5.1.1.)
yy1 said:
Try to flash your boot.img. Reboot stop with KERNEL IS NOT SEANDROID ENFORCING (Android 5.1.1.)
Click to expand...
Click to collapse
The question is does it boot up? If so then that message can be ignored, if not then I will look into it. Just flash original boot.img or firmware to go back to a useable phone. Thanks for testing
Did you get a message with both these sentences in or just the first sentence"KERNEL IS NOT SEANDROID ENFORCING. Custom binary blocked by FRP Lock" ???
It doesn't boot up. Black screnn with boot logo and red warning on top. i flash the original boot.img anything okay.
what means fap lock?
yy1 said:
It doesn't boot up. Black screnn with boot logo and red warning on top. i flash the original boot.img anything okay.
what means fap lock?
Click to expand...
Click to collapse
Was ment to FRP not FAP, autocorrect strikes again. FRP = Factory Rest Protection.Google it if you want more info, basically another barrier to stop thieves. As I reading up on this user's are stating (in a sepolicy patch thread) that when flashing boot.img via odin their phone wouldn't boot up, but said flashing bootmimg via TWRP works.
Questions:
1) When you flash the custom boot.img, does it freeze and nothing happens? Or does it reboot automatically?
2) are you using heimdall or Odin?
Tasks:
1) Flash the boot.img via Heimdall (if you've been using odin) and report back if it was a succes.
2) if possible, if adb is running, can you pull the dmesg off the device before restoring the original boot.img as this will help in debugging this problem.
E.G. "G:\" is the hard drive plugged into my computer, adjust as necessary.
Code:
adb shell dmesg >> G:\dmesg.txt
3) ALSO TRY, after you flash the custom boot.img can you try booting into recovery (Volume Up + Home + Power Button) and try wiping cache before trying to properly boot the phone. Maybe you could also when in recovery tell me what the log files say? @yy1
Still currently searching what is blocking the custom boot.img from booting the phone.
I really appreciate the help
Flash your boot.img via heimdall once again. with no reboot option. go to recovery and wipe cache. after start the phone boot anytime in recovery. flash via heimdall original boot img anyhing okay.
adb not work. there are logfiles in recovery but i don't know they way to put that from phone to pc. Sorry for that.
yy1 said:
Flash your boot.img via heimdall once again. with no reboot option. go to recovery and wipe cache. after start the phone boot anytime in recovery. flash via heimdall original boot img anyhing okay.
adb not work. there are logfiles in recovery but i don't know they way to put that from phone to pc. Sorry for that.
Click to expand...
Click to collapse
I won't be able to look into it today as i have important stuff happening. Will post back later with some more info, sorry about the wait then. Thanks for the help
===================================
Can you try this, as it will greatly help in diagnosing the problem.
Flash the custom boot.img, don't boot the phone yet. Then can you run
Code:
adb start-server
In a terminal/command prompt, then turn on the phone with the adb dmesg command from the previous post already in the terminal for you to hit enter when needed.
Turn on the phone now, and hit enter to run the above command before the phone stops and reboots itself.
Thanks.
Edit 2: When devloping the boot.img, I had to use chainfires supolicy binary to patch the sepolicy in boot.img, with one of it tasks is to patch the recovery from enforcing to permissive mode.
So in an educated geuss, and with information in other forms (user reported that they are unable to flash a custom boot.img via odin but able to via TWRP), that we may be able to flash the boot.img via recovery. See instructions for testing this below.
1) Download both the 3.0.2-1 and 2.0.8-* version of twrp (.img.tar) as we should try both of them <Linked in original post>
2) Flash my custom boot.img and then the twrp files with auto reboot turned off
3) once they both flash, boot into recovery (give it 5-10 mins, if nothig happens then it didn't work)
4) if it actually worked and booted into recovery, flash the custom boot.img in TWRP and try rebooting normally
5) If it managed to get this far, then continue from my original post by tuning either the root script/bat file
Please Report how far you got in this process or if it worked.
===================================
I am currently trying different versions of my boot.img, will post once I have it working properly
No way for me to give you adb log-file, because adb find no device if phone in download- or recovery-mode.
try the second way. Flash boot.img and recovery.img (TWRP) start the phone in recovery-mode. red warning on top RECOVERY IS NOT SEANDROID ENFORCING.
wait 5 minutes phone starts automatic in normal-mode.
yy1 said:
No way for me to give you adb log-file, because adb find no device if phone in download- or recovery-mode.
try the second way. Flash boot.img and recovery.img (TWRP) start the phone in recovery-mode. red warning on top RECOVERY IS NOT SEANDROID ENFORCING.
wait 5 minutes phone starts automatic in normal-mode.
Click to expand...
Click to collapse
Yea thanks for that, I had been trying a bunch of combinations yesterday with none of them working. And when trying to find what blocks custom boot.img from booting up, all I come across is stuff staying to flash back stock firmware, but nothing for the reasons why.
But I have some stuff to look in to and will replie back when done (if I'm succesful or not)
These include:
- looking more into pains secure download mode and what it does
- having a go with exploiting a bug that had happend with stock recovery. Running 4.0 (we are not running this version of android) and recovery version 3e(our stock recovery version ) where you could flash updates.zip signed with testkeys instead of the manufacturers keys
- OR try getting TWRP to run on lollipop (probably have to rebuild it) this leaves us with two options in twrp. 1) Flash SuperSu and get system install (probably won't be able to unpack the boot.img) or then flash my customized boot.img for the Systemless version of root.
Either way it may be a little while before lolipop root is working.
I have important exams coming up so this project is gonna have to be out onto the backburner for about 4 weeks or so, meaning I won't be putting much effort into this for a while, but will continue it after the exams. @yy1
- '
@yy1 I belive I have found out why the phone won't boot when using the custom boot.img
I belive it has to do with the unpacking/repacking of the ramdisk.cpio.gz file. When ever I try to boot an image with a repacked ramdisk the phone won't boot.
I know that the phone can boot custom boot.img 's as I removed the word "SEANDORID" from the original and flashed it to my phone. My phone booted up, even when the red text (KERNEL IS NOT SEANDROID ENFORCING) was shown at the top of my phone.
So once I got it got it booting I will post back here.
My previous post, was somewhat on par. What I mean by this is yes, the ramdisk was a reason why it was not boot, but not for any reasons like permissions, ownership or the like, it was in fact that when unpacking and repacking the cpio archive increase the size, and from what I have reduced from my trial and errors is when the boot.img size is changed by even one byte in size it won't boot. But you are able to modify its contents with a hex editor, E.G. Zeroing out the word SEANDROIDENFORCING at the bottom of the raw image file, would still let the phone boot fully with the text show "KERNEL is not SEANDROIDENFORCING" and it showing up as a custom binary in Download more. I belive it may be becuse of some outside security verifying the boot.img. maybe download mode (it's in secure mode, haven't looked into it yet) or some script, I am not sure. And its all most impossible to get any errors logs or dmesg via adb or otherwise, with my only way to read them is via stock recovery, which is a bit impractical and inelegant reading as it speeds past lines you want to read when trying to scroll down (if anyone knows how to pull these logs from cache without a custom recovery or root, please tell me.
Now when I try to replace the ramdisk in boot.img via hex editor the size increase and thus unable to boot. When I try to repack it with various versions of mkbootimg, including Google's python script, other bi nary compiled versions of it by various people and mkbootimg's binary modified to also with with Device Tree Files which get appended onto the boot.img. I have analysed and reverse enginered the boot.img file, and analyzed the other files included with the stock firmware downloadable from sites like sammobile, sam-firmware etc.
I will be updating one of the is original post with all the information that I have uncovered, I'm great detail and when my internet situation allows (my mobile data is running low, lol), upload the reversed enginered files of boot.img for anyone else to inspect and have a crack at creating their own custom kernel/boot.img.
TL;DR: Uploading detailed information and reverse enginered files of boot.img. Any of my custom boot.img's won't boot if the size changes at the minimum one byte from the original boot.img, but the phone can boot a custom version if the size of the file size deos not change a single byte.
Hi;
TWRP is ready for SM-G389F :
https://twrp.me/devices/samsunggalaxyxcover3ve.html
Heledir said:
Hi;
TWRP is ready for SM-G389F :
https://twrp.me/devices/samsunggalaxyxcover3ve.html
Click to expand...
Click to collapse
This currently only works for Kit Kat, after I unpacked it I read the files at it was aimed at android 4.4.4. I am, after I have my exams in the next few weeks I am gonna try and get TWRP working on lollipop (after I got root )
Software for Samsung Galaxy Xcover 3 VE (SM-G389F) is Android 6.0, so I think it's for MM. The links:
- Device Tree / files
https://github.com/TeamWin/android_device_samsung_xcover3velte
Say its Android 6.0 branch.
I've install it yesterday with Odin and it works fine on my SM-G389F.
But i haven't find root for SM-G389F and MM.
How to unpack and repack boot.img
For Windows user
1. Download CarlivImageKitchen from here http://forum.xda-developers.com/attachment.php?attachmentid=3798926&d=1467275078
all credit goes to bluefirebird http://forum.xda-developers.com/member.php?u=5186178
2. extract it using 7zip or similar program
3.. Put your boot.img in boot-resources folder
4. Double click carlive batch file
now select B and Enter
Now choose your boot.img and enter
5. To unpack it type 1 and Enter
that's it. now you can find extract boot.img in boot folder. type enter for continue and keep this window open if you want to repack it again after
making change in boot folder
edit your files in boot folder and for repacking it again keep reading
Repacking
type 2 for repacking
now you can find you new boot.img in output folder
For Linux user
i am using ubuntu as my linux machine
1. Download Boot.img Tool from here https://github.com/jsharma44/bootimg-tools
2. cd bootimgtools
Type following in terminal
./unpackbootimg -i "boot.img path"
For example
./unpackbootimg -i /home/user/Desktop/boot.img
find your files in bootimgtools
I hope you like it. Please visit my website http://azodik.com/ for more interesting guide
Thank You
Extracting boot.img from your device
Extracting boot.img from your device
What we need
1. A rooted phone
2. Enable Usb Debugging in Developer Mode
3. ADB command knowldge
connect your phone via usb cable ensure that usb debugging is enabled
open terminal and type adb devices
if it is showing your device’s serial no than we are ready to go
C. type
adb shell
su
ls -l /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name
please note this command may vary by device to device. What we are doing here we want to know partition scheme of your device.
note down block name of /boot partition
example it will be like boot -> /dev/block/mmcblk0p7
d. type this
dd if=/dev/block/mmcblk0p7 of=/sdcard/boot.img
now boot.img succesfully transfered to your SD card Copy it to your Desktop
How To Extract System Folder From Android device
1. Connect your phone to computer with USB debugging enabled
2. Type following command to check
adb devices
if it is showing your device's serial no then go to step 3. If not then make sure drivers are installed for your device.
3. To pull system folder use following command
adb pull system
it will pull system folder to your current adb directory. If you want to pull it to some specific directory use following command
adb pull system "output directory"
Example
1. adb pull /system C:/Users/user_name/Desktop/ (For Windows)
2.adb pull /system /home/user/Desktop (for linux)
Your link to Windows zip is no longer there. Getting a 410 error
ianmb said:
Your link to Windows zip is no longer there. Getting a 410 error
Click to expand...
Click to collapse
link updated..Please check now. Thanks for pointing out it
jai44 said:
How to unpack and repack boot.img
For Windows user
1. Download CarlivImageKitchen from here http://forum.xda-developers.com/attachment.php?attachmentid=3798926&d=1467275078
all credit goes to bluefirebird http://forum.xda-developers.com/member.php?u=5186178
2. extract it using 7zip or similar program
3.. Put your boot.img in boot-resources folder
4. Double click carlive batch file
now select B and Enter
Now choose your boot.img and enter
5. To unpack it type 1 and Enter
that's it. now you can find extract boot.img in boot folder. type enter for continue and keep this window open if you want to repack it again after
making change in boot folder
edit your files in boot folder and for repacking it again keep reading
Repacking
type 2 for repacking
now you can find you new boot.img in output folder
For Linux user
i am using ubuntu as my linux machine
1. Download Boot.img Tool from here https://github.com/jsharma44/bootimg-tools
2. cd bootimgtools
Type following in terminal
./unpackbootimg -i "boot.img path"
For example
./unpackbootimg -i /home/user/Desktop/boot.img
find your files in bootimgtools
I hope you like it. Please visit my website http://azodik.com/ for more interesting guide
Thank You
Click to expand...
Click to collapse
Your link no longer exists. I want to download the software to Windows. I would love for you to update the link. Thank you!
Hey guys,
This is for people who already unlocked the bootloader!!
Since there hasn't been any flashable images via twrp or fastboot, I have decided to create one for the stock 20e. Now it's semi stock because the twrp is included with the boot image I uploaded. I'm doing just 20e because im too lazy to go back and forth firmwares just to upload different versions of fw of stock.
You can flash them via fastboot or twrp.
To access fastboot you need to be rooted in your custom rom or stock:
1. Use terminal or adb shell and do these commands
Code:
Su
dd if=/dev/zero of=/dev/block/bootdevice/by-name/laf_a
Then reboot and hold the vol+ button while it's plugged into the PC
Don't worry about losing download mode on slot_a cause the other slot will still have it and you can switch to the other slot via fastboot or twrp then you can have download mode
To flash via fastboot:
Code:
Fastboot flash boot_a twrpboot_a.img
Fastboot flash system_a system_a.img
Fastboot flash vendor_a vendor_a.img
To flash via twrp:
1. Move these files to your internal sd or external.
2. Get into recovery mode and then hit install
3. Tap on select image and find the image files
4. Then flash them one by one.
5. Format data and reboot.
https://drive.google.com/folderview?id=1-1tRMeDK7sVzta9kKhAvfVF2B9XZu2ki
If you want to help out and upload the other firmwares, here are the steps:
1. Be on the firmware you want to make the image files for.
2. Make sure you are rooted!!
3. Use terminal from the play store or use adb shell
4. And do the following for each partition.
A. First SU in shell then
For system-
Code:
dd if=/dev/block/bootdevice/by-name/system_a of=/sdcard/system_a.img
For boot:
Code:
dd if=/dev/block/bootdevice/by-name/boot_a of=/sdcard/boot_a.img
For vendor:
Code:
dd if=/dev/block/bootdevice/by-name/vendor_a of=/sdcard/vendor_a.img
Then upload them to Google drive or wherever and share them if you can.
Does it work on G710EM?
Resync said:
Does it work on G710EM?
Click to expand...
Click to collapse
In theory it should.
can you upload the twrpboot for ulm21d?
Can you make the v35 twrp , thanks
In this guide a describe how you can easily fix the touchscreen issue in TWRP for Moto G 5G.
Before providing the necessary steps, I would like to express my gratitude to the guys here, especially Andrew Hexen for providing the sources and instructions to build the TWRP for this great device.
Building the TWRP from source might result in a recovery without the touchscreen support. To fix that, you can follow these simple steps.
First, we need to extract the touchscreen drivers from the phone. To do this, you need to boot to TWRP. Connect your phone to your PC, open up the terminal and type:
Bash:
# reboot to bootloader
adb reboot bootloader
# boot to recovery
fastboot boot twrp.img
Wait for the phone to boot to recovery. If your phone uses password/PIN or other forms of protection you might have to decrypt the filesystem before proceeding. You can use OTG mouse to do that.
On your PC, in terminal type:
Bash:
adb pull "/vendor/lib/modules/" <path to where you want the modules folder to be pulled>
This will pull from the phone all the necessary drivers, among those are the drivers for the touchscreen. (Probably you could pull just the touchscreen driver, but to be sure I pulled everything.)
On you PC, use Android Kitchen to unpack the recovey image. I usually use the terminal to go to the Android Kitchen folder and I run:
Bash:
./unpacking.sh <path to your twrp.img>
Then go to ramdisk folder that was created by Android Kitchen
Bash:
cd ramdisk
and manually create the following folder:
Bash:
sudo mkdir -p vendor/lib/modules
Then copy the drivers you previously pulled from your phone to this folder:
Bash:
sudo cp <path to modules folder with drivers>/* vendor/lib/modules/
In the ramdisk folder open the init.rc file. We need to open it as su user. You can use:
Bash:
sudo gedit
and then open the file from the editor.
Find the following lines:
Code:
# Load properties, Android 6.0+, vendor init lives here
on load_persist_props_action
load_persist_props
and add a line after load_persist_props so that you get:
Code:
# Load properties, Android 6.0+, vendor init lives here
on load_persist_props_action
load_persist_props
start load_modules # this is the line you must add
Use Android Kitchen to repack the image:
Bash:
cd .. # to move back to the folder where Android Kitchen is
./repacking.sh
You'll get a file called image-new.img. That's your new recovery with a working touchscreen!
I'm sure there's a better way to do this so feedback is welcome.
I tired your method and completed with a newimage file, and flastboot booted off it. Still had touch problems, files attached. Vendor.zip was placed in ramdisk\vendor\lib\modules. Any ideas?
Thankyou
PS (edit): would anything needed to be added to ramdisk/vendor/manifest.xml?
Lostwon said:
I tired your method and completed with a newimage file, and flastboot booted off it. Still had touch problems, files attached. Vendor.zip was placed in ramdisk\vendor\lib\modules. Any ideas?
Thankyou
Click to expand...
Click to collapse
Lostwon said:
I tired your method and completed with a newimage file, and flastboot booted off it. Still had touch problems, files attached. Vendor.zip was placed in ramdisk\vendor\lib\modules. Any ideas?
Thankyou
PS (edit): would anything needed to be added to ramdisk/vendor/manifest.xml?
Click to expand...
Click to collapse
PPS I am trying this on the Moto G stylus xt2043-4. I just noticed thats not the phone you wrote this for, Im going to pull and umpack my stock recovery and compre that to the Twrp3.4 image and see whats missing .