I am building CyanogenMod for my Samsung Galaxy Note 10.1 N8000. Here is the guide.
When I typed
Code:
breakfast n8000
, the output was as follows.
Code:
including vendor/cm/vendorsetup.sh
ls: cannot access device/*/n8000/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_n8000". Stop.
Device n8000 not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Traceback (most recent call last):
File "build/tools/roomservice.py", line 76, in <module>
result = json.loads(urllib.request.urlopen(githubreq).read().decode())
File "/usr/lib/python2.7/urllib2.py", line 126, in urlopen
return _opener.open(url, data, timeout)
File "/usr/lib/python2.7/urllib2.py", line 406, in open
response = meth(req, response)
File "/usr/lib/python2.7/urllib2.py", line 519, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib/python2.7/urllib2.py", line 444, in error
return self._call_chain(*args)
File "/usr/lib/python2.7/urllib2.py", line 378, in _call_chain
result = func(*args)
File "/usr/lib/python2.7/urllib2.py", line 527, in http_error_default
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 403: Forbidden
ls: cannot access device/*/n8000/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_n8000". Stop.
** Don't have a product spec for: 'cm_n8000'
** Do you have the right repo manifest?
I executed breakfast without a device as the guide suggests.
If you do not put a device, the script will output a list of available devices to build for (limited to those CM builds nightlies for, which isn't necessarily complete), and you can then choose yours.
Click to expand...
Click to collapse
And there was nothing containing n8000
Code:
including vendor/cm/vendorsetup.sh
You're building on Linux
Breakfast menu... pick a combo:
1. full-eng 19. cm_e980-userdebug 37. cm_jfltexx-userdebug 55. cm_serranoltexx-userdebug
2. cm_apexqtmo-userdebug 20. cm_evita-userdebug 38. cm_m7att-userdebug 56. cm_skyrocket-userdebug
3. cm_captivatemtd-userdebug 21. cm_exhilarate-userdebug 39. cm_m7spr-userdebug 57. cm_superior-userdebug
4. cm_crespo-userdebug 22. cm_flo-userdebug 40. cm_m7tmo-userdebug 58. cm_t0lte-userdebug
5. cm_d2att-userdebug 23. cm_galaxysbmtd-userdebug 41. cm_m7ul-userdebug 59. cm_tilapia-userdebug
6. cm_d2cri-userdebug 24. cm_galaxysmtd-userdebug 42. cm_m7vzw-userdebug 60. cm_toroplus-userdebug
7. cm_d2mtr-userdebug 25. cm_grouper-userdebug 43. cm_maguro-userdebug 61. cm_toro-userdebug
8. cm_d2spr-userdebug 26. cm_hammerhead-userdebug 44. cm_mako-userdebug 62. cm_tsubasa-userdebug
9. cm_d2tmo-userdebug 27. cm_hercules-userdebug 45. cm_manta-userdebug 63. cm_ville-userdebug
10. cm_d2usc-userdebug 28. cm_i9300-userdebug 46. cm_mb886-userdebug 64. cm_vs980-userdebug
11. cm_d2vzw-userdebug 29. cm_jflteatt-userdebug 47. cm_mint-userdebug 65. cm_xt897-userdebug
12. cm_d800-userdebug 30. cm_jfltecan-userdebug 48. cm_odin-userdebug 66. cm_xt897c-userdebug
13. cm_d801-userdebug 31. cm_jfltecri-userdebug 49. cm_otter-userdebug 67. cm_xt907-userdebug
14. cm_d802-userdebug 32. cm_jfltecsp-userdebug 50. cm_otter2-userdebug 68. cm_xt925-userdebug
15. cm_deb-userdebug 33. cm_jfltespr-userdebug 51. cm_p1-userdebug 69. cm_xt926-userdebug
16. cm_dlx-userdebug 34. cm_jfltetmo-userdebug 52. cm_pollux-userdebug 70. cm_yuga-userdebug
17. cm_dogo-userdebug 35. cm_jflteusc-userdebug 53. cm_pollux_windy-userdebug
18. cm_e975-userdebug 36. cm_jfltevzw-userdebug 54. cm_serrano3gxx-userdebug
... and don't forget the bacon!
Which would you like? [aosp_arm-eng]
Then I tried lunch
It’s used EXACTLY like breakfast, the only difference being the choices you have to build with it, and how it configures the device. Using lunch, you can choose non-official or non-standard builds for your device
Click to expand...
Click to collapse
The output was the same.
There is nothing about N8000 again.
Has anybody built CyanogenMod Android for Samsung Galaxy Note 10.1 N8000 successfully?
Have you included the 8013 as well I believe the only difference is the cellular radio file which I believe can be added for your device?
tubas..... tubas everywhere....
n8000 only has cm-10.2 and I'm guessing you're trying to build cm-11.
mamenyaka said:
n8000 only has cm-10.2 and I'm guessing you're trying to build cm-11.
Click to expand...
Click to collapse
I ran
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
So the version I'm trying building is 10.2
Red Planet said:
I ran
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
So the version I'm trying building is 10.2
Click to expand...
Click to collapse
Then you have to manually add the n8000 repos.
Look at this file: https://github.com/mamenyaka/android/blob/phablet-saucy/local_manifest_samsung.xml
and use appropriate CM repos and branches. Place file in .repo/local_manifests/
Hi, I'm trying to build androidarmv6 for Cooper. I synced all the repositories and then ran lunch and chose cm_cooper-userdebug, but the command fails with
Code:
lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng 7. cm_goldfish-userdebug 13. cm_cooper-eng 19. cm_gio-userdebug 25. cm_icong-userdebug
2. aosp_x86-eng 8. cm_goldfish-user 14. cm_cooper-userdebug 20. cm_tass-userdebug 26. cm_liberty-userdebug
3. aosp_mips-eng 9. mini_mips-userdebug 15. cm_p500-userdebug 21. cm_tassve-userdebug 27. cm_marvel-userdebug
4. vbox_x86-eng 10. mini_x86-userdebug 16. cm_beni-userdebug 22. cm_totoro-userdebug
5. mini_armv7a_neon-userdebug 11. cm_callisto-eng 17. cm_cooperve-userdebug 23. cm_skate-userdebug
6. cm_goldfish-eng 12. cm_callisto-userdebug 18. cm_galaxy5-userdebug 24. cm_chacha-userdebug
Which would you like? [aosp_arm-eng] cm_cooper-userdebug
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/samsung/cooper/cm.mk]]: "device/samsung/msm7x27-common/common.mk" does not exist. Schluss.
Device cooper not found. Attempting to retrieve device repository from androidarmv6 Github.
Found repository: android_device_samsung_cooper
Default revision: cm-11.0
Checking branch info
androidarmv6/android_device_samsung_cooper already exists
Syncing repository to retrieve project.
Fetching project repo
Fetching project androidarmv6/android_device_samsung_cooper
fatal: Invalid gitfile format: /ansys/android/.repo/repo/.git/clone.bundle
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Fetching projects: 100% (2/2), done.
Repository synced!
Looking for dependencies
Done
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/samsung/cooper/cm.mk]]: "device/samsung/msm7x27-common/common.mk" does not exist. Schluss.
** Don't have a product spec for: 'cm_cooper'
** Do you have the right repo manifest?
Can somebody explain to me what the problem is and/or where I might find the product spec / right repo manifest?
PsirusGT said:
Hi, I'm trying to build androidarmv6 for Cooper. I synced all the repositories and then ran lunch and chose cm_cooper-userdebug, but the command fails with
Code:
lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng 7. cm_goldfish-userdebug 13. cm_cooper-eng 19. cm_gio-userdebug 25. cm_icong-userdebug
2. aosp_x86-eng 8. cm_goldfish-user 14. cm_cooper-userdebug 20. cm_tass-userdebug 26. cm_liberty-userdebug
3. aosp_mips-eng 9. mini_mips-userdebug 15. cm_p500-userdebug 21. cm_tassve-userdebug 27. cm_marvel-userdebug
4. vbox_x86-eng 10. mini_x86-userdebug 16. cm_beni-userdebug 22. cm_totoro-userdebug
5. mini_armv7a_neon-userdebug 11. cm_callisto-eng 17. cm_cooperve-userdebug 23. cm_skate-userdebug
6. cm_goldfish-eng 12. cm_callisto-userdebug 18. cm_galaxy5-userdebug 24. cm_chacha-userdebug
Which would you like? [aosp_arm-eng] cm_cooper-userdebug
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/samsung/cooper/cm.mk]]: "device/samsung/msm7x27-common/common.mk" does not exist. Schluss.
Device cooper not found. Attempting to retrieve device repository from androidarmv6 Github.
Found repository: android_device_samsung_cooper
Default revision: cm-11.0
Checking branch info
androidarmv6/android_device_samsung_cooper already exists
Syncing repository to retrieve project.
Fetching project repo
Fetching project androidarmv6/android_device_samsung_cooper
fatal: Invalid gitfile format: /ansys/android/.repo/repo/.git/clone.bundle
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Fetching projects: 100% (2/2), done.
Repository synced!
Looking for dependencies
Done
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/samsung/cooper/cm.mk]]: "device/samsung/msm7x27-common/common.mk" does not exist. Schluss.
** Don't have a product spec for: 'cm_cooper'
** Do you have the right repo manifest?
Can somebody explain to me what the problem is and/or where I might find the product spec / right repo manifest?
Click to expand...
Click to collapse
Make sure common.mk exists in device/samsung/msm7x27-common. If it is not there download it from androidarmv6 github(dirty solution-download whole msm7x27-common folder & manually & place it inside device/samsung folder). And try brunch command.
"brunch cooper".
You will need google cardboard or some other VR headset.
This project is built on top of Deploy Linux. It uses SDL Xserver as well as a custom x11 compositor for VR graphics
To install do the following:
(Install base)
1: install openSuSE 13.2 with "Linux Deploy"
1.1: Installation type: FIle
1.2: Desktop Environment: LXDE
1.3: X Server2: /usr/sbin/sshd (start ssh)
3: Run: zypper in pango* (this will fix the issue with text being all boxes [])
At this point you should have a working SuSE install
4: Download the project https://bitbucket.org/ruapotato/vrsuse.git
5: Install python-xpyb-1.3.1-4.fc22.armv7hl.rpm (zypper in /path/to/vrlinux/python-xpyb-1.3.1-4.fc22.armv7hl.rpm)
6: Run: sed -i -e 's/RECTANGLE/xproto.RECTANGLE/g' /usr/lib/python2.7/site-packages/xcb/damage.py
Now we should be able to run the project
In a terminal run:
(With xserver sdl open)
7: source vrlinux/display.sh
8: lxsession &
9: vrlinux/pycompmgr &
OTG works alternatively you can use synergyc -f HOSTCOMPUTER for mouse/keyboard input
http://postimg.org/image/wbftuwg7t/
http://postimg.org/image/66fl8m251/
Done:
OTG mouse/keyboard input!
TODO:
better graphics (smaller with some correction for blur around the edges)
auto startup
head tracking
Add other distro (Ubuntu, Arch, etc)
fix systemd (to run properly in a chroot)
XDA:DevDB Information
VR Linux, Tool/Utility for the Google Nexus 5
Contributors
ruapotato
Source Code: https://bitbucket.org/ruapotato/vrsuse.git
Version Information
Status: Alpha
Created 2016-04-03
Last Updated 2016-04-08
Dose anyone know how to apply effects in x render (python). I suck on the resizing windows part.
What is Android?
Android is the open-source operating system used for smartphones. Full Freedom for people using it
What is Android Source Code?
Android is an open-source software stack created for a wide array of devices with different form factors. The primary purposes of Android are to create an open software platform available for carriers, OEMs, and developers to make their innovative ideas a reality and to introduce a successful, real-world product that improves the mobile experience for users.The result is a full, production-quality consumer product with source code open for customization and porting.
So basically Android Allows to customize the things you like and make new things without any Restrictions. Cool isn’t it?
What is Android ROM ?
The Android ROM is the Android operating system. This is the User interface (Sense UI in HTC phones) and the file system for maintaining contacts etc. It is composed of a Linux kernel and various add-ons to achieve specific functionality.
What does a Android Rom Contain ?
Basically a Android Rom Contains following main things :
· Kernel
· Bootloader
· Recovery
· Radio
· Framework
· Apps
· core
· android-runtime,Etc
Some Basics About Above Terms
Kernel :
A kernel is critical component of the Android and all operating systems. It can be seen as a sort of bridge between the applications and the actual hardware of a device. Android devices use the Linux kernel, but it's not the exact same kernel other Linux-based operating systems use. There's a lot of Android specific code built in, and Google's Android kernel maintainers have their work cut out for them. OEMs have to contribute as well, because they need to develop hardware drivers for the parts they're using for the kernel version they're using. This is why it takes a while for independent Android developers and hackers to port new versions to older devices and get everything working. Drivers written to work with the Gingerbread kernel on a phone won't necessarily work with the Ice Cream Sandwich kernel. And that's important, because one of the kernel's main functions is to control the hardware. It's a whole lot of source code, with more options while building it than you can imagine, but in the end it's just the intermediary between the hardware and the software. So basically if any instruction is given to mobile it first gives the command to kernel for the particular task execution.
Bootloader :
The bootloader is code that is executed before any Operating System starts to run. Bootloaders basically package the instructions to boot operating system kernel and most of them also have their own debugging or modification environment. Think of the bootloader as a security checkpoint for all those partitions. Because if you’re able to swap out what’s on those partitions, you’re able to break things if you don’t know what you’re doing. So basically it commands the kernel of your device to Boot the Device properly without any issues. So careful with bootloader since it can mess things very badly.
Recovery :
Recovery is defined in simple terms as a source of backup. Whenever your phone firmware is corrupted, the recovery does the job in helping you to restore or repair your faulty or buggy firmware into working condition. It is also used for flashing the Rom’s , kernel and many more things.
Radio
The lowest part of software layer is the radio: this is the very first thing that runs, just before the bootloader. It control all wireless communication like GSM Antenna, GPS etc.
What you’ll need
A relatively recent 64-bit computer (Linux, OS X, or Windows)(Virtual Machine will work as well) with a reasonable amount of RAM and about 100 GB of free storage (more if you enable ccache or build for multiple devices). The less RAM you have, the longer the build will take (aim for 8 GB or more). Using SSDs results in considerably faster build times than traditional hard drives.
A decent internet connection & reliable electricity
Some familiarity with basic Android operation and terminology. It would help if you’ve installed custom roms on other devices and are familiar with recovery. It may also be useful to know some basic command line concepts such as cd for “change directory”, the concept of directory hierarchies, that in Linux they are separated by /, etc.
Install the SDK
If you haven’t previously installed adb and fastboot, you can download them from Google. Extract it running:
Code:
unzip platform-tools-latest-linux.zip -d ~
Now you have to add adb and fastboot to your PATH. Open ~/.profile and add the following:
Code:
# add Android SDK platform tools to path
if [ -d "$HOME/platform-tools" ] ; then
PATH="$HOME/platform-tools:$PATH"
fi
Then, run source ~/.profile to update yur environment.
Install the build packages
Several packages are needed to build LineageOS. You can install these using your distribution’s package manager.
To build LineageOS, you’ll need:
bc bison build-essential curl flex g++-multilib gcc-multilib git gnupg gperf imagemagick lib32ncurses5-dev lib32readline-dev lib32z1-dev libesd0-dev liblz4-tool libncurses5-dev libsdl1.2-dev libssl-dev libwxgtk3.0-dev libxml2 libxml2-utils lzop pngcrush rsync schedtool squashfs-tools xsltproc zip zlib1g-dev
For Ubuntu versions older than 16.04 (xenial), substitute:
libwxgtk3.0-dev → libwxgtk2.8-dev
Java
Different versions of LineageOS require different JDK (Java Development Kit) versions.
LineageOS 14.1: OpenJDK 1.8 (install openjdk-8-jdk)
LineageOS 11.0-13.0: OpenJDK 1.7 (install openjdk-7-jdk)*
https://askubuntu.com/questions/761127/how-do-i-install-openjdk-7-on-ubuntu-16-04-or-higher
Create the directories
You’ll need to set up some directories in your build environment.
To create them:
Code:
mkdir -p ~/bin
mkdir -p ~/android/lineage
Install the repo command
Enter the following to download the repo binary and make it executable (runnable):
Code:
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
Put the ~/bin directory in your path of execution
In recent versions of Ubuntu, ~/bin should already be in your PATH. You can check this by opening ~/.profile with a text editor and verifying the following code exists (add it if it is missing):
Code:
# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi
Then, run source ~/.profile to update your environment.
Initialize the LineageOS source repository
Code:
cd ~/android/lineage
repo init -u https://github.com/LineageOS/android.git -b cm-14.1
Download the source code
Code:
repo sync -c -f --force-sync --no-clone-bundle --no-tags --optimized-fetch --prune
Prepare the device-specific code
Code:
git clone https://github.com/SamarV-121/android_device_google_sprout4 -b cm-14.1 device/google/sprout4
git clone https://github.com/SamarV-121/android_device_google_sprout-common -b cm-14.1 device/google/sprout-common
git clone https://github.com/TheMuppets/proprietary_vendor_google -b cm-14.1 vendor/google
git clone https://github.com/SamarV-121/android_kernel_mediatek_sprout kernel/mediatek/sprout
Turn on caching to speed up build
Code:
export CCACHE_DIR=./.ccache
ccache -C
export USE_CCACHE=1
export CCACHE_COMPRESS=1
prebuilts/misc/linux-x86/ccache/ccache -M 50G
Configure jack
Jack is the new Java compiler used when building LineageOS 14.1. It is known to run out of memory - a simple fix is to run this command:
Code:
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
Make Clean Build
Code:
make clean && make clobber
Initialize the build command
Code:
source build/envsetup.sh
Start Build
Code:
croot
brunch sprout4
For More info:
https://source.android.com/source/requirements
https://wiki.lineageos.org/devices/cheeseburger/build
hmm nice guide... hope other users will start building roms for sprout
Good Work
Keep it UP
TechExhibeo said:
Good Work
Keep it UP
Click to expand...
Click to collapse
Thoinx
Any solution for this error?
Code:
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/harshone/android/lineage/out/target/product/m8/obj/KERNEL_OBJ/usr', needed by '/home/harshone/android/lineage/out/target/product/m8/obj/STATIC_LIBRARIES/libsdcard_intermediates/sdcard.o', missing and no known rule to make it
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/home/harshone/android/lineage'
#### make failed to build some targets (02:30 (mm:ss)) ####
I want some help regarding kernel building....
I am new to XDA, coz my previous account has been deleted,
I want some help regarding building a custom kernel for sprout/....
Anyone willing to help, plz reply.....:angel:
P.S. I am using self made kernel for my device riit now
Thanks
Hello Guys,
I need Twrp for My Tab A8 SM-X205. I've already try to build but no success and is not list on twrp.me please i need HELP !
device tree for Tab A8 SM-X205 : https://github.com/U4I5/twrp_device_samsung_Tab_A8_4G who can build img file ?
rename ~/TWRP/twrpdtgen/output/samsung/gta8/omni_gta8.mk to twrp_gta8.mk
delete vendorsetup.sh
Make a copy of recovery.fstab and rename to twrp.flags
Move both files recovery.fstab and twrp.flags to recovery/root/system/etc
(create these folders)
open twrp_gta8.mk and :
1. delete the 3 lines below # Inherit from those products, Most specific first.
replace those 3 lines with this
$(call inherit-product, $(SRC_TARGET_DIR)/product/aosp_base.mk)
2. delete $(call inherit-product, vendor/omni/config/gsm.mk)
3. change omni to twrp (2 places)
open AndroidProducts.mk
change omni to twrp (4 spots)
4. Optional: add extra items to BoardConfig.mk
cd ~
sudo apt install git aria2 -y
git clone https://gitlab.com/OrangeFox/misc/scripts
cd scripts
sudo bash setup/android_build_env.sh
sudo bash setup/install_android_sdk.sh
• Make a directory called ~/a12s-twrp
cd ~/twrp
repo init --depth=1 -u https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp.git -b twrp-11
repo sync -c --no-clone-bundle --no-tags --optimized-fetch --prune --force-sync -j1
copy ~/TWRP/twrpdtgen/output/samsung to /twrp/device
Building
========
. build/envsetup.sh
lunch twrp_gta8-eng
mka recoveryimage –j1
Recovery.img at out/Samsung/gta8/...img
Dkpost3 said:
rename ~/TWRP/twrpdtgen/output/samsung/gta8/omni_gta8.mk to twrp_gta8.mk
delete vendorsetup.sh
Make a copy of recovery.fstab and rename to twrp.flags
Move both files recovery.fstab and twrp.flags to recovery/root/system/etc
(create these folders)
open twrp_gta8.mk and :
1. delete the 3 lines below # Inherit from those products, Most specific first.
replace those 3 lines with this
$(call inherit-product, $(SRC_TARGET_DIR)/product/aosp_base.mk)
2. delete $(call inherit-product, vendor/omni/config/gsm.mk)
3. change omni to twrp (2 places)
open AndroidProducts.mk
change omni to twrp (4 spots)
4. Optional: add extra items to BoardConfig.mk
cd ~
sudo apt install git aria2 -y
git clone https://gitlab.com/OrangeFox/misc/scripts
cd scripts
sudo bash setup/android_build_env.sh
sudo bash setup/install_android_sdk.sh
• Make a directory called ~/a12s-twrp
cd ~/twrp
repo init --depth=1 -u https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp.git -b twrp-11
repo sync -c --no-clone-bundle --no-tags --optimized-fetch --prune --force-sync -j1
copy ~/TWRP/twrpdtgen/output/samsung to /twrp/device
Building
========
. build/envsetup.sh
lunch twrp_gta8-eng
mka recoveryimage –j1
Recovery.img at out/Samsung/gta8/...img
Click to expand...
Click to collapse
Hey bro thank but I have to rename omni to twrp of these ligne : PRODUCT_NAME := omni_gta8 $(call inherit-product, vendor/omni/config/common.mk) ?
Dkpost3 said:
rename ~/TWRP/twrpdtgen/output/samsung/gta8/omni_gta8.mk to twrp_gta8.mk
delete vendorsetup.sh
Make a copy of recovery.fstab and rename to twrp.flags
Move both files recovery.fstab and twrp.flags to recovery/root/system/etc
(create these folders)
open twrp_gta8.mk and :
1. delete the 3 lines below # Inherit from those products, Most specific first.
replace those 3 lines with this
$(call inherit-product, $(SRC_TARGET_DIR)/product/aosp_base.mk)
2. delete $(call inherit-product, vendor/omni/config/gsm.mk)
3. change omni to twrp (2 places)
open AndroidProducts.mk
change omni to twrp (4 spots)
4. Optional: add extra items to BoardConfig.mk
cd ~
sudo apt install git aria2 -y
git clone https://gitlab.com/OrangeFox/misc/scripts
cd scripts
sudo bash setup/android_build_env.sh
sudo bash setup/install_android_sdk.sh
• Make a directory called ~/a12s-twrp
cd ~/twrp
repo init --depth=1 -u https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp.git -b twrp-11
repo sync -c --no-clone-bundle --no-tags --optimized-fetch --prune --force-sync -j1
copy ~/TWRP/twrpdtgen/output/samsung to /twrp/device
Building
========
. build/envsetup.sh
lunch twrp_gta8-eng
mka recoveryimage –j1
Recovery.img at out/Samsung/gta8/...img
Click to expand...
Click to collapse
Can you do it for me i got some error please : build/make/core/dex_preopt_libart.mk:18: error:
Ur!el said:
Can you do it for me i got some error please : build/make/core/dex_preopt_libart.mk:18: error:
Click to expand...
Click to collapse
Google
Ur!el said:
Hey bro thank but I have to rename omni to twrp of these ligne : PRODUCT_NAME := omni_gta8 $(call inherit-product, vendor/omni/config/common.mk) ?
Click to expand...
Click to collapse
omni_gta8 NO
twrp_gta8.mk - yes
Dkpost3 said:
rename ~/TWRP/twrpdtgen/output/samsung/gta8/omni_gta8.mk to twrp_gta8.mk
delete vendorsetup.sh
Make a copy of recovery.fstab and rename to twrp.flags
Move both files recovery.fstab and twrp.flags to recovery/root/system/etc
(create these folders)
open twrp_gta8.mk and :
1. delete the 3 lines below # Inherit from those products, Most specific first.
replace those 3 lines with this
$(call inherit-product, $(SRC_TARGET_DIR)/product/aosp_base.mk)
2. delete $(call inherit-product, vendor/omni/config/gsm.mk)
3. change omni to twrp (2 places)
open AndroidProducts.mk
change omni to twrp (4 spots)
4. Optional: add extra items to BoardConfig.mk
cd ~
sudo apt install git aria2 -y
git clone https://gitlab.com/OrangeFox/misc/scripts
cd scripts
sudo bash setup/android_build_env.sh
sudo bash setup/install_android_sdk.sh
• Make a directory called ~/a12s-twrp
cd ~/twrp
repo init --depth=1 -u https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp.git -b twrp-11
repo sync -c --no-clone-bundle --no-tags --optimized-fetch --prune --force-sync -j1
copy ~/TWRP/twrpdtgen/output/samsung to /twrp/device
Building
========
. build/envsetup.sh
lunch twrp_gta8-eng
mka recoveryimage –j1
Recovery.img at out/Samsung/gta8/...img
Click to expand...
Click to collapse
Why not to create twrp file instead of this for every normal user like me to flash it and use
Did this worked with anyone
Dkpost3 said:
rename ~/TWRP/twrpdtgen/output/samsung/gta8/omni_gta8.mk to twrp_gta8.mk
delete vendorsetup.sh
Make a copy of recovery.fstab and rename to twrp.flags
Move both files recovery.fstab and twrp.flags to recovery/root/system/etc
(create these folders)
open twrp_gta8.mk and :
1. delete the 3 lines below # Inherit from those products, Most specific first.
replace those 3 lines with this
$(call inherit-product, $(SRC_TARGET_DIR)/product/aosp_base.mk)
2. delete $(call inherit-product, vendor/omni/config/gsm.mk)
3. change omni to twrp (2 places)
open AndroidProducts.mk
change omni to twrp (4 spots)
4. Optional: add extra items to BoardConfig.mk
cd ~
sudo apt install git aria2 -y
git clone https://gitlab.com/OrangeFox/misc/scripts
cd scripts
sudo bash setup/android_build_env.sh
sudo bash setup/install_android_sdk.sh
• Make a directory called ~/a12s-twrp
cd ~/twrp
repo init --depth=1 -u https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp.git -b twrp-11
repo sync -c --no-clone-bundle --no-tags --optimized-fetch --prune --force-sync -j1
copy ~/TWRP/twrpdtgen/output/samsung to /twrp/device
Building
========
. build/envsetup.sh
lunch twrp_gta8-eng
mka recoveryimage –j1
Recovery.img at out/Samsung/gta8/...img
Click to expand...
Click to collapse
??
And if worked ,why no one published ithe file ??
I have a bit of experience building TWRP for the Galaxy Tab A 8.0 (2019), Galaxy Tab A 10.1" (2019) and Galaxy Tab A7 (2020), so when I saw the $149 deal this week I thought I'd give the A8 a try. I unlocked the bootloader, updated to XAR-X200XXU1AVG1-20220804205906, and made my first build of TWRP 3.6.2_11.
My first attempt generated a boot loop, which isn't all that unusual. I pulled my camera out to capture the diagnostic log that was flashing on the screen, but the boot loop stopped after about a dozen iterations. I didn't worry at the time, since I assumed I could force a reboot using Power & Vol Down...but that's not working, no matter how long I hold the two buttons.
Unfortunately, without the ability to force restart, I can't get back to Download Mode to flash the stock recovery in Odin. I'm basically dead in the water until my battery is depleted, which could be weeks.
Any suggestions on how to force restart if Power & Vol Down isn't working? I've never had an issue doing this with Samsung tablets based on Qualcomm or Exynos chipsets, but this is my first experience with Unisoc.
UPDATE: A week was sufficient reset time and connecting USB with Vol Up & Down got me to Download Mode. I'm back in business. Moral of the story is to catch a boot loop quickly to return to Download Mode. Don't let it loop more than a few times.
(And the X200XXU1AVG1 kernel source is now posted.)
Okay, I have a TWRP 3.6.2_11 build booting and running on SM-X200 except for user data encryption, which I'll continue to work on tomorrow. If anyone has any insights into how to get TWRP to recognized metadata encryption on this device, please let me know.
Update: Now posted here: https://forum.xda-developers.com/t/...-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691/
Can't use the TWRP user interface. no function available. what am I doing wrong. had to install stock recovery again
I have TWRP ready for SM-X205. However, this will not work because there is such a thing as Android Verified Boot. It can be disabled by patching vbmeta.img
Now I'm trying to do it, but so far without success. TWRP starts, but instead of the system. Android does not start, TWRP starts. If any of you are ready to help in resolving this issue, I would be very grateful.
unpack and add magiskboot in orangefox.zip
OK, I'll try this.
AndrewMarkov621 said:
OK, I'll try this.
Click to expand...
Click to collapse
send me a tree, I'll make twrp
TWRP is already there
Dkpost3 said:
unpack and add magiskboot in orangefox.zip
Click to expand...
Click to collapse
Does not work, Odin refuses to flash the device.
Actually, here is the result of the TWRP build. When booting into the system, it writes something like "Warranty bit: boot" "Warranty bit: recovery". And goes into the bootloop. At the moment I'm trying to assemble a patched vbmeta, however, so far without success, I can't even get the encryption keys, because a lot of time has passed since writing the guide on the Internet and Android protection has stepped far ahead. I hope that someday I will be able to at least get off the ground.
P.S. The version that one of the participants of the SM-X200 theme put together works on the SM-X205 in the same way as mine. Magisk is installed on the device, root is received.
I was able to install TWRP definitively. It works fine with Android. However, it cannot perform any functions, the internal storage does not see, it gives this:
If you remount the partitions to ext2 and then to ext4, then everything works. However, the Storage section is not mounted in any way, it was in vfat, and remained. The system does not load after these manipulations, only the installation of stock firmware helps. Something like that.