I flashed newest twrp for gs3 with flashify. Now when I hit the button to reboot, the screen has samsung and at the top says recovery booting for a second then goes black. I posted this in the noob forumin reply to the person that told me to flash but i am not getting an answer
↧
flashed newest twrp for gs3 now have black screen
↧
ROOT TWRP on G4 H815 Marsmallow possible???
Hi
I´ve searched a lot but could find a way to install custom ROMs, or more precisely: I can´t root, custom recovery, etc
I´ve searched a lot but could find a way to install custom ROMs, or more precisely: I can´t root, custom recovery, etc
Does anyone knows how I can be rooted? My G4 is H815 (not european) and it came with Android 6 on it. My main reason is to install custom roms.
Please help
↧
↧
Help can’t flash TWRP in S-ON state?
Just got my HTC 10 and I’m trying to root and install twrp. I have the unlocked version from HTC. I’ve unlocked the bootloader and installed all drivers. Everytimei try to flash twrpvia fastboot I get an error saying cannot write to this partition in s-on state. See screenshot. If anyone can help it will be greatly appreciated. I have the unlocked version straight from HTC. TIA
↧
Deleted system with Twrp
Hi
I accidently deleted my system on my huawei p8 MAX with TWRP.
What can i do? Please help me….
I am lost without my phone
TWRP IS STILL ON
Sent from my HUAWEI MT7-L09 using XDA Premium HD app
↧
[TWRP][gemini] TWRP 3.0.2-0 Testing | Need help of gemini
I” just move straight into topic. I have compiled TWRP using Omni 6.0 sources, Compile went success, I am gonna make it official support for this device if TWRP boots
Test:
Downloads:
twrp-3.0.2-0-gemini.img
Device Tree: Not available for security reasons.
– HostZero
XDA:DevDB Information
[TWRP][gemini] TWRP 3.0.2-0 Testing, Tool/Utility for the LeEco Le Max 2
Contributors
HostZero
Version Information
Status: Testing
Created 2016-06-11
Last Updated 2016-06-11
↧
↧
[How To] Install TWRP on LG G2, noob friendly guide
Hi,
I made this guide after struggling to install TWRP using several guides on XDA and other forums which fail to mention few other steps needed.
I am using a verizon lg g2 on stock lollipop 5.0.2 , rooted using LG ONE CLICK ROOT. But i guess this guide goes for all g2 variants who cannot simply install twrp on their stock firmware using flashify or autorec.
ISSUE :
I have tried flashify but this app is only useful if you already have an older version of recovery installed since i failed to install any version of twrp and cwm while trying. After installing a twrp , you can flash upgrade recovery using this.
Autorec gives me unresponsive button when tapping on the FLASH TWRP icon.
Other solution requires manual installation such as THIS GUIDE which i haven’t tried because i am not that advanced android user yet since i came from using iOS.
The easiest way to install TWRP is autorec but to fix the unresponsive button, follow below steps:
** Ofcourse you need root in order to install custom recovery
1. Install AUTOREC from HERE. There are different app for different g2 variant so install accordingly.
2. Go to SuperSU settings , uncheck " Enable Superuser" and then scroll bottom where you see " reinstall" under CLEANUP section. Tap on that and proceed. Wait few seconds and when done, reboot your device.
3. Go to THIS LINK and download supersu 2.46
4. After its downloaded, tap and install it. Update binary and reboot.
5. Go to autorec, give it superuser permission and tap on the "Flash TWRP" icon and you will see it working.
** note : in order to install latest twrp, you must first install the initial img version and then flash the latest version zip from within. Update link : TWRP 3.0.2-1
Feel free to post below if it worked for you or if you need further assistance.
↧
TWRP not working on NXT-L29C432B320
Hi,
I’ve installed the ROM NXT-L29C432B320, I then wanted to reinstall TWRP using fastboot.
Got the following output:
C:\adb-1>fastboot flash recovery TWRP-2.8.7.0-ENG.img
target reported max download size of 471859200 bytes
sending ‘recovery’ (31330 KB)…
OKAY [ 0.990s]
writing ‘recovery’…
OKAY [ 0.231s]
finished. total time: 1.226sC:\adb-1>fastboot reboot
rebooting…finished. total time: 0.022s
C:\adb-1>
When attempting to boot into recovery mode (using ‘Volume up’ + ‘power’)the screen is stuck at the bootloader:
Your device has been unlocked and can’t be trusted.
To learn more, visite:
htt*p://zh.ui.vmallcom/emotiondownload.php?mod=restoreYour device is booting now…
The screen is stuck here, noting is happening.
Already attempted to refllash mutliple times. No difference.
Already attempted to use ‘Volume up’ + ‘Volume down’ + ‘power’, does not work either.
Pressing the ‘Volume up’ button during boot (without ‘power’), shows me the Huawai eRecovery.
Please help me making TWRP work again as I’m now unable to flash any new rom on it!
↧
Please if anyone having cwm or twrp .img for panasonic p55, plz give me…
Please if anyone having cwm or twrp .img for panasonic p55, plz give me…
↧
Can’t flash TWRP from either Heimdall or Odin
I dug out my old trusty SGS2 to install CM13, the last time I used it was at the time of CM10.
I familiarized myself with the tutorials, and realized I have to re-partition the phone first, which requires TWRP. I downloaded the latest TWRP for the i9100 (3.0.2) and the Heimdall suite. Steps I took until failure:
1. Disable driver signature enforcement (I’m on W10)
2. Boot into download mode
3. Use zadig to replace the driver to libusb0
4. Use Heimdall to download the PIT file
5. Doesn’t work – it gives me
Quote:
|
Initialising connection… |
Since I didn’t get Heimdall to work, I thought to give Odin a try:
1. Downloaded Odin3 v3.11
2. TAR’d the TWRP IMG file
3. Tried to flash via Odin
4. Doesn’t work – gives me:
Quote:
|
<ID:0/005> Odin engine v(ID:3.1101).. |
My laptop only has USB3 ports, I tried all of them. The cable is fine, I tried another good one which also didn’t change anything. I’m not sure if I miss some crucial step or doing something wrong, as I haven’t touched the device in years and am not very familiar with flashing it. I’m just looking for the ‘easiest’ way to get to CM13.
Appreciate any help!
↧
↧
Boot loader unlock and twrp related
Guys anybody tell how to unlock Boot loader and flashing twrp in steps clearly…as there are no clear guide to do this in main thread I have opened a thread here so share it here…Thanks for the devs who are working for us[emoji3]
Sent from my F1f using XDA-Developers mobile app
↧
Re-install TWRP?
I have my op2 with runing with exodus rom. but i think my son playing with the phone deleted twrp, cause i cant enter recovery mode. When I do that my phone simply shows the 1+ logo for the eternity.
Tried with the TWRP manager, selected de TWRP and downloaded, but it gets an error when trying to intall.
Is there a way to re-install the twrp recovery tool?
↧
[Guide] [TWRP] [LB] Root .224 firmware BONUS Xperia X SystemUI + N-Style
Hello, before I share anything else, I did not create any of these mods. All credits go to the creators, and I am very thankful to them.. I am just excited to share this to people who are still undecided to flash these mods because of bootloops/softbricks.
I am not responsible to anything that happens to your device. ALWAYS MAKE A BACKUP FIRST BEFORE PROCEEDING
So without further ado:
Step 1. Root, Recovery, Backup Restore DRM key
I always have been using this trick to root my Xperia Z5 Dual E6633. Just remember that the link below is for Z5 Compact, but this method should work on any Z5 model, using a Z5 firmware.
http://twigstechtips.blogspot.ca/201…losing-ta.html
Step 2: Deodex your phone
I have found this Deodex patch thread by lordriguez to deodex .224 firmware. I was doubting at first if it will work on E6633 Dual .224, i risked it, and it worked with no problems. No more .odex in system/app..
http://forum.xda-developers.com/xper…e-200-t3301572
Step 3: Flash Xperia X SystemUI and N-Style
Flash away!
http://forum.xda-developers.com/xper…hemes-t3368086
Thats it! Now you have:
1. Latest Marshmallow ROM (.224)
2. Root, TWRP recovery
3. Locked Bootloader
4. DRM Keys intact
5. Deodexed rom
6. Xperia X and Android N themed device
BIG Thanks and credits to:
@Twig for the complete guide to root Z5
@zxz0O0 for the awesome root
@tobias.waldvogel for the rootable kernel w/ dm-verity and SONY RIC off
@lordriguez for the deodex patch
@machao and @nreuge for the ports and sharing of Xperia X SystemUI and N-Style theme
↧
Can I undo twrp v.2.8.6.1?
I have two problems with my lg g3 att rooted phone.
1st Problem – I have tried to get rid of the android.process.acore error but have had no luck THIS time. (Last time part of the fix was completely uninstalling the facebook app from my phone). This time (and last time) I cleared caches, stopped them, deleted my contacts and the contacts storage, unclicked the app sync button…. I can’t really remember what else I did to restore it to normal.
2nd problem – So I clicked on update software from ATT and a TWRP v.2.8.6.0 screen comes up. I don’t know what to do with it. Do I click install, restore, reboot, backup? Can I just undo this and try and find some other way to remove the android.process.acore error message without losing all my data with a factory reset? If this twrp is complicated I would prefer to just undo what I just did. I really need some help as soon as possible. Thank you in advance.
↧
↧
LG G3 VS985 Verizon TWRP and MM, Help is requested
Hi All,
I am on LG official MM on my LG G3 VS985 Verizon
I downgraded and installed TWRP using the method in the following thread:
http://forum.xda-developers.com/veri…tions-t3326775
I am on LG official MM on my LG G3 VS985 Verizon
I downgraded and installed TWRP using the method in the following thread:
http://forum.xda-developers.com/veri…tions-t3326775
and then flashed VS98547A Firmware using TWRP, from following thread:
http://forum.xda-developers.com/veri…mware-t3304365
PS: I had generated and flashed a debloating script to debloat Amazon and Verizon Apps from following link, hoping it will help to extend battery timing
h**p://jfsoftware.com/android/lgg3/debloat.php#2000102030405060y1f1g1h1i1j1k1l1m1n1o1 q1r1s1t1u1v1w1x
I m glad that my phone is now rooted; Amazon and Verizon Apps are gone too, however there are couple of problems I observed which are as per:
- I can’t go into download mode now
- TWRP isn’t working now. Instead I get into official LG recovery when booted into recovery mode
- Battery is being drained more quickly than when it was running on official MM
Any help to fix above-mentioned problems would be appreciated.
Regards
↧
Impossible to flash other ROM or Gapps with twrp
Hi all, i have a problem with my device, i’ts a KIW-L21
I flashed TWRP 3.0.0.0, and CyanogenMod 13.0 (this rom http://forum.xda-developers.com/hono…ghtly-t3344499 )
I flashed TWRP 3.0.0.0, and CyanogenMod 13.0 (this rom http://forum.xda-developers.com/hono…ghtly-t3344499 )
I would like flash Gapps pico with arm64 and 6.0
Ok, but wen i flash this one, nothing is happening
i test with a other rom, such, impossible nothing is happening
I tried to flash twrp 3.0.2.0, it’s ok for installalation, but nothing is happening for flash gapps or other rom
So, i’m blocked in this rom and impossible to flash a gapps or other rom
:mad::mad::mad::mad::mad::mad:
please help me .. 
Sorry for my language i’m french and i have school level
↧
A couple questions about TWRP
I’ve just got the bootloader unlock code and I’m balancing wheter I unlock it or not. But in the mean time, I have a "couple" questions about the process:
1. Why do people recommend installing TWRP as recovery2?
2. Is the warranty void by unlocking the bootloader?
3. Is it worth unlocking the bootloader?
1. Why do people recommend installing TWRP as recovery2?
2. Is the warranty void by unlocking the bootloader?
3. Is it worth unlocking the bootloader?
↧
Help with compiling / porting MultiRom / TWRP for Aquaris E5?
I would like to have a dual boot (Android / Ubuntu Touch) on an Aquaris E5 HD phone ( the Ubuntu Touch variant can be flashed with stock Android and vice versa, see mibqyyo.com/en-articles/2015/09/16/ubuntu-android-installation-process-for-bq-aquaris-e4-5-and-e5 ). ((sorry for the links, new user))
Unfortunately, the instructions from wiki.ubuntu.com/Touch/DualBootInstallation do not work with this phone anymore: it seems that the software in those instructions relies on the device having custom ClockworkMod (CWM) recovery — and, it seems ClockworkMod does not support this device anymore, if it ever did ( see askubuntu.com/questions/666070/cant-install-ubuntu-touch-dual-boot-on-mobile-stuck-in-waiting-for-device/776357 ).
The only other option I could see for dual boot is MultiROM Manager, unfortunately it fails with "This is unsupported device (Aquaris_E5_HD)!"
However, it is possible to root this phone using a TeamWin Recovery Project (TWRP) custom recovery image ( v3.0.2-0, see mibqyyo.com/comunidad/discussion/77467/how-to-root-a-bq-aquaris-e5-hd-phone ), which seemingly does support this phone. Furthermore, from twrp.me/devices/bqaquarise5hd.html there is a reference to:
- Device Tree / files: github.com/TeamWin/android_device_bq_vegetahd – and from there:
- Kernel source available on: github.com/bq/aquaris-E5
So, I thought – maybe it would be possible to port / build MultiROM from source, with support for this device? I tried something, and maybe I even got part of the way – unfortunately I cannot get the build to complete, so I hope I can get some assistance here. I will outline the steps I did below. First of all, I use this as my PC:
Code:
$ uname -a
Linux MYPC 4.2.0-38-generic #45~14.04.1-Ubuntu SMP Thu Jun 9 09:27:51 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/issue
Ubuntu 14.04.4 LTS \n \l
Then I looked at github.com/Tasssadar/multirom/wiki/Porting-MultiROM:
Quote:
|
Prerequisites * Android 4.1+ tree Downloading sources Just clone TWRP, MultiROM and libbootimg repos into your Android Tree, the commands would look something like this: […] |
I was somewhat puzzled about what this "Android Tree" is, but eventually I guessed it is the Android Open Source Project (AOSP) source code. So, I looked and did this:
- source.android.com/source/initializing.html
(Note: http removed from links in code below, because I’m a new user and cannot post links):
Code:
cd /tmp
wget archive.ubuntu.com/ubuntu/pool/universe/o/openjdk-8/openjdk-8-jre-headless_8u45-b14-1_amd64.deb
wget archive.ubuntu.com/ubuntu/pool/universe/o/openjdk-8/openjdk-8-jre_8u45-b14-1_amd64.deb
wget archive.ubuntu.com/ubuntu/pool/universe/o/openjdk-8/openjdk-8-jdk_8u45-b14-1_amd64.deb
sudo dpkg -i openjdk-8-jre-headless_8u45-b14-1_amd64.deb
sudo dpkg -i openjdk-8-jre_8u45-b14-1_amd64.deb
sudo dpkg -i openjdk-8-jdk_8u45-b14-1_amd64.deb
sudo apt-get -f install
# already have libgl1-mesa-dev-lts-wily mesa-common-dev-lts-wily
# so removed libgl1-mesa-dev from list below:
sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 \
lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev ccache \
libxml2-utils xsltproc unzip
sudo apt-get autoremove --purge
wget -S -O - source.android.com/source/51-android.rules | sed "s/<username>/$USER/" | sudo tee >/dev/null /etc/udev/rules.d/51-android.rules
# for the aquaris:
echo "SUBSYSTEM==\"usb\", ATTRidVendor==\"2a47\", ATTRidProduct==\"201d\", MODE=\"0600\", OWNER=\"$USER\"" \
| sudo tee -a /etc/udev/rules.d/51-android.rules
sudo udevadm control --reload-rules
then
- source.android.com/source/downloading.html
Code:
mkdir ~/bin
PATH=~/bin:$PATH
curl storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
cd /path/to/src
mkdir AOSP
cd AOSP
repo init -u android.googlesource.com/platform/manifest -b android-4.1.2_r2.1 2>&1 | tee repo.log
repo sync
Note that here, I took the `4.1+` requirement quite literally, so just chose to checkout the last 4.1 branch, `4.1.2_r2.1`.
Also, repo sync took 14+ hours to complete, for my PC+Internet connection combo (!)
With that done, I have this in the directory:
Code:
AOSP$ ls
abi cts docs hardware ndk prebuilts
bionic dalvik external libcore packages repo.log
bootable development frameworks libnativehelper pdk sdk
build device gdk Makefile prebuilt systemNow, at this point, we should be running build/envsetup.sh and lunch; however, that will cause only the default Google devices (Nexus etc) to be recognized. So, here I did cloned the "device tree" (I guess) into the "Android tree":
Code:
AOSP$ mkdir device/bq
AOSP$ git clone github.com/TeamWin/android_device_bq_vegetahd device/bq/vegetahd
AOSP$ chmod +x device/bq/vegetahd/vendorsetup.sh
AOSP$ ls device/bq/vegetahd/
AndroidBoard.mk BoardConfig.mk kernel omni_vegetahd.mk recovery
AndroidProducts.mk device.mk mkbootimg.mk README.md vendorsetup.sh
AOSP$ ls device/samsung/crespo # for comparison
Android.mk full_crespo.mk libsensors recovery
AndroidProducts.mk gps.conf libstagefrighthw recovery.fstab [...]
vendorsetup.sh
and also cloned the Omnirom TWRP recovery sources (note that if you just mv bootable/recovery bootable/old.recovery, then the builds process may also pick some of those files up, so that directory should be deleted, as guides elsewhere recommend):
Code:
AOSP$ rm -rf bootable/recovery
cd bootable
git clone https://github.com/omnirom/android_bootable_recovery.git recovery-twrp
cd ..Since build/envsetup.sh should be running the vendorsetup.sh when it finds them, after running it, the Aquaris device should be visible:
Code:
AOSP$ source build/envsetup.sh
including device/asus/grouper/vendorsetup.sh
including device/bq/vegetahd/vendorsetup.sh # ***
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/moto/wingray/vendorsetup.sh
including device/samsung/crespo/vendorsetup.sh
including device/samsung/maguro/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including sdk/bash_completion/adb.bash
AOSP$ lunch
You're building on Linux
Lunch menu... pick a combo:
1. full-eng
2. full_x86-eng
3. vbox_x86-eng
4. full_grouper-userdebug
5. omni_vegetahd-eng # ***
6. mini_armv7a_neon-userdebug
7. mini_armv7a-userdebug
8. full_wingray-userdebug
9. full_crespo-userdebug
10. full_maguro-userdebug
11. full_panda-userdebug
Which would you like? [full-eng] 5
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.1.2
TARGET_PRODUCT=omni_vegetahd
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.2.0-38-generic-x86_64-with-Ubuntu-14.04-trusty
HOST_BUILD_TYPE=release
BUILD_ID=JZO54M
OUT_DIR=out
============================================
Now, it seems that for such an old version like 4.1.2_r2.1, there is no mka command (not found), which should otherwise be ran at this point – however, I can run make instead of it.
Also because it’s so old, I get "You are attempting to build with the incorrect version of java. Your version is: openjdk version "1.8.0_45-internal". The correct version is: Java SE 1.6.", which it so happens, I have – but I have to set environment variables. So here I run:
Code:
AOSP$ export RECOVERY_VARIANT=twrp
AOSP$ ANDROID_PRE_BUILD_PATHS=/path/to/jdk1.6.0_45/bin \
ANDROID_JAVA_TOOLCHAIN=/path/to/jdk1.6.0_45/bin \
JAVA_HOME=/path/to/jdk1.6.0_45 \
PATH=/path/to/jdk1.6.0_45/bin:$PATH \
make -j3 recoveryimage
...
target thumb C: adbd <= system/core/adb/log_service.c
make: *** No rule to make target `out/target/product/vegetahd/obj/EXECUTABLES/recovery_intermediates/recovery', needed by `out/target/product/vegetahd/recovery.img'. Stop.
make: *** Waiting for unfinished jobs....
target thumb C: adbd <= system/core/adb/utils.c… but as you can see, it fails. This was for the Omnirom sources of TWRP recovery.
Then I thought of going back to the Multirom porting, and so did this:
Code:
AOSP$ rm -r bootable/recovery-twrp
git clone github.com/Tasssadar/Team-Win-Recovery-Project.git bootable/recovery
git clone github.com/Tasssadar/multirom.git system/extras/multirom
git clone github.com/Tasssadar/libbootimg.git system/extras/libbootimg
cd system/extras/multirom
git submodule update --init
cd ../../..Then I checked the touchpad from adb shell as root:
Code:
cat /proc/bus/input/devices
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="mtk-tpd"
P: Phys=
S: Sysfs=/devices/virtual/input/input3
U: Uniq=
H: Handlers=mouse0 event3 cpufreq
B: PROP=2
B: EV=b
B: KEY=10 0 0 0 0 0 0 0 400 0 0 0 0 1000 40000000 100000 0 0 0
B: ABS=6630000 1000003… so definitely "type b"; then by doing `find /sys | grep uevent` and comparing as in the porting guide, I put together this file as device/bq/vegetahd/mr_init_devices.c:
Code:
#include <stdlib.h>
// These are paths to folders in /sys which contain "uevent" file
// need to init this device.
// MultiROM needs to init framebuffer, mmc blocks, input devices,
// some ADB-related stuff and USB drives, if OTG is supported
// You can use * at the end to init this folder and all its subfolders
const char *mr_init_devices[] =
{
"/sys/devices/platform/mtkfb.0/graphics/fb0",
"/sys/devices/platform/mtkfb.0",
"/sys/devices/platform/mtk-msdc.0",
"/sys/devices/platform/mtk-msdc.0/mmc_host/mmc0",
"/sys/devices/platform/mtk-msdc.0/mmc_host/mmc0/mmc0:0001",
"/sys/devices/platform/mtk-msdc.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0",
"/sys/devices/platform/mtk-msdc.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0boot0",
"/sys/devices/platform/mtk-msdc.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0boot1",
"/sys/devices/platform/mtk-msdc.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0rpmb",
"/sys/devices/platform/mtk-msdc.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p1",
"/sys/devices/platform/mtk-msdc.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p2",
"/sys/devices/platform/mtk-msdc.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p3",
"/sys/devices/platform/mtk-msdc.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p4",
"/sys/devices/platform/mtk-msdc.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p5",
"/sys/devices/platform/mtk-msdc.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p6",
"/sys/devices/platform/mtk-msdc.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p7",
"/sys/devices/platform/mtk-msdc.1",
"/sys/devices/platform/mtk-msdc.1/mmc_host/mmc1",
"/sys/devices/platform/mtk-msdc.1/mmc_host/mmc1/mmc1:0007",
"/sys/devices/platform/mtk-msdc.1/mmc_host/mmc1/mmc1:0007/block/mmcblk1/mmcblk1p1",
"/sys/devices/platform/mtk-msdc.1/mmc_host/mmc1/mmc1:0007/block/mmcblk1",
"/sys/bus/mmc/uevent",
"/sys/bus/mmc/drivers/mmcblk/uevent",
"/sys/bus/sdio/uevent",
"/sys/devices/virtual/input/*",
"/sys/devices/virtual/misc/uinput",
"/sys/devices/platform/mtk-tpd",
"/sys/devices/platform/mtk-kpd",
"/sys/devices/platform/mtk-kpd/input/input0",
"/sys/devices/platform/mtk-kpd/input/input0/event0",
"/sys/devices/platform/mtk-kpd/misc/mtk-kpd",
// for adb
"/sys/devices/virtual/tty/ptmx",
"/sys/devices/virtual/misc/android_adb",
"/sys/devices/virtual/android_usb/android0/f_adb",
"/sys/bus/usb",
NULL // must be NULL-terminated
}
Then I inspected boot.img of the stock Android firmware:
Code:
$ /path/to/bootimg_tools/boot_info /path/to/bq/2.1.0_20151104-0859_E5HD_bq-FW/boot.img
Page size: 2048 (0x00000800)
Kernel size: 3747904 (0x00393040)
Ramdisk size: 615529 (0x00096469)
Second size: 0 (0x00000000)
Board name: fbcdadc
Command line: ''
Base address: 2147483648 (0x80000000)… and also did:
Code:
mkdir device/bq/vegetahd/mrom-infos/
wget raw.githubusercontent.com/Tasssadar/device_asus_grouper/cm-10.2-mrom/mrom_infos/ubuntu_touch.txt -O device/bq/vegetahd/mrom-infos/ubuntu_touch.txt… and confirmed paths, and could finally add this to device/bq/vegetahd/BoardConfig.mk :
Code:
#MultiROM config. MultiROM also uses parts of TWRP config
MR_INPUT_TYPE := type_b
MR_INIT_DEVICES := device/bq/vegetahd/mr_init_devices.c
MR_RD_ADDR := 0x82500000
MR_DPI := hdpi
MR_DPI_FONT := 216
MR_FSTAB := device/bq/vegetahd/recovery/etc/twrp.fstab
MR_KEXEC_MEM_MIN := 0x85000000
MR_INFOS := device/bq/vegetahd/mrom_infosHere, if I run … make … (after first exiting the old terminal shell, and repeating envsetup.sh / lunch in a new one), I get "build/core/base_rules.mk:103: *** user tag detected on new module – user tags are only supported on legacy modules. Stop." So, I did these changes:
Code:
# bootable/recovery/Android.mk:
LOCAL_MODULE := recovery
LOCAL_MODULE_TAGS := optional # add
# bootable/recovery/tests/Android.mk:
LOCAL_MODULE := asn1_decoder_test
LOCAL_MODULE_TAGS := optional # add
Then, a … make … at this point fails with: "make: *** No rule to make target `out/target/product/vegetahd/system/xbin/busybox’, needed by `out/target/product/vegetahd/obj/SHARED_LIBRARIES/libbmlutils_intermediates/teamwin’. Stop.".
Here I found "[DEV]How to compile TWRP touch recovery – Pg. 150 | Android Development and Hacking" ( forum.xda-developers.com/showthread.php?p=65556586 ), and I downloaded busybox.zip from that page – and did:
Code:
AOSP$ unzip busybox.zip
AOSP$ mv busybox external/Now, the … make … at this point is a bit funny, because it will exit not reporting an error, as if it finished:
Code:
AOSP$ ANDROID_PRE_BUILD_PATHS=/path/to/jdk1.6.0_45/bin \
ANDROID_JAVA_TOOLCHAIN=/path/to/jdk1.6.0_45/bin \
JAVA_HOME=/path/to/jdk1.6.0_45 \
PATH=/path/to/jdk1.6.0_45/bin:$PATH \
make -j3 recoveryimage
...
GEN include/usage_compressed.h
GEN include/applet_tables.h
HOSTCC applets/usage_pod
GEN include/bbconfigopts.h
CC applets/applets.o
LD applets/built-in.o
make[1]: Leaving directory `/media/Data1/src/AOSP/external/busybox'
AOSP$But here it is apparently just done with applets in busybox! So, I try running … make … again, and get:
Code:
external/busybox/android/librpc/bindresvport.c:41:13: error: conflicting types for '__set_errno'
bionic/libc/include/errno.h:45:15: note: previous declaration of '__set_errno' was hereThis I fix by changing external/selinux/libsepol/include to external/libsepol/include in:
Code:
# external/busybox/Android.mk:
BUSYBOX_C_INCLUDES = \
$(BB_PATH)/include $(BB_PATH)/libbb \
bionic/libc/private \
bionic/libm/include \
bionic/libc \
bionic/libm \
libc/kernel/common \
external/libselinux/include \
external/libsepol/include \
...… and at this point, … make … will fail with:
Code:
external/busybox/android/librpc/pmap_rmt.c:235:8: warning: implicit declaration of function 'inet_makeaddr' [-Wimplicit-function-declaration]
external/busybox/android/librpc/pmap_rmt.c:238:8: warning: implicit declaration of function 'inet_netof' [-Wimplicit-function-declaration]
external/busybox/android/librpc/pmap_rmt.c:235:19: error: incompatible types when assigning to type 'struct in_addr' from type 'int'Here I found stackoverflow.com/questions/27762475/incompatible-types-when-assigning-to-type-struct-in-addr-from-type-int/27763398, which notes:
Quote:
|
The error message is misleading, the function is simply missing from earlier versions of the NDK. |
So, as a final try, I tried forcing a newer NDK through an environment variable, as in:
Code:
NDK_HOME=/path/to/android-ndk-r10e \
ANDROID_PRE_BUILD_PATHS=/path/to/jdk1.6.0_45/bin \
ANDROID_JAVA_TOOLCHAIN=/path/to/jdk1.6.0_45/bin \
JAVA_HOME=/path/to/jdk1.6.0_45 \
PATH=/path/to/jdk1.6.0_45/bin:$PATH \
make -j3 recoveryimage… but this fails in exactly the same manner (with "implicit declaration of function ‘inet_makeaddr’", etc).
At this point, I really don’t know what I should do… Should I:
- Try to use the BQ Kernel sources for this device (even if mentioned above, I haven’t used them anywhere yet) somewhere (say clone them in the Android tree)? If so – where?
- Try to find a busybox for AOSP 4.1.2? If so – what version is OK, and where do I find it?
- Try to bump the AOSP repo version up from 4.1.2? If so, what would be the minimum version required so this builds – and would I have to wait 14+ hours again?
… or is there anything else I could try?
Again, I’m mostly interested in building MultiROM and the recovery image (TWRP?) required for it on the Aquaris E5 – but it would be nice to know how to build TWRP proper recovery image as well…
Thanks in advance for any hints…
↧
↧
Root without flashing TWRP
So, does anyone know if it’s possible to boot twrp without flashing it and then root from there? I’m only asking because it would be nice to retain the ota feature in stock. Yet, would rooting make OTAs not work?
↧
softbricked…orange twrp
my idiot little brother accidentally wiped everything….i can only boot in orange twrp recovery(hydrogen os version)..but there is nothing to back to recover from or zip file to flash from….
so i tried to adb push zip file and adb sideload rom but it says…device not found
how can i repair my phone guys…big help needed![:(]()
when i fastboot..the device is recognized but when i adb push device not found…help guys…
so i tried to adb push zip file and adb sideload rom but it says…device not found
how can i repair my phone guys…big help needed
when i fastboot..the device is recognized but when i adb push device not found…help guys…
↧
[Q] MTK6582 TWRP 2.8.2.0 set_metadata_recursive Issue
I have a Blu Studio X+ running 4.4.2 stock firmware with 3.4.67 kernel. When I try to flash a CM13 port (that also uses the same kernel) in both MTKDroidTools-generated CWM and TWRP 2.8.2.0 (generated from an automated tool as well), I get the following error and the ROM stops flashing:
ApplyParsedPerms: lsetfilecon of /system/lost+found to u:object_r:system_file:s0 failed: Operation not supported on transport endpoint set_metadata_recursive: some changes failed
Looking through the updater-script, the problem seems to lie within this line:
set_metadata_recursive("/system", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644, "capabilities", "0x0", "selabel", "u:object_r:system_file:s0");
From my research it appears this is an SELinux incompatibility problem. I thought TWRP 2.8.2.0 was supposed to support SELinux. What do I do to fix this?
↧