Related
Hi, since this is my wife's HTC hero from Orange UK, I'm being particularly careful with it. I'm new to xda-developers/HTC platforms (but not new to doing horrible things to embedded platforms) :>
I've been messing about with the phone all evening - downloaded that ROM image from the other thread and pulled it apart to look at the OS files etc - the standard break-a-new-embedded-linux-platform routine.
Anyway, if you hold down BACK when powering on, it enters the bootloader mode with a "FASTBOOT USB" prompt, which sounded interesting. I got a copy of the fastboot binary, and extracted the kernel and the ramdisk images from "boot.img" in the "HEROIMG_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed.zip" (using split_bootimg.pl).
Just as a quick test, I tried booting them with:
fastboot boot kernel.img boot.img
since the above just boots a kernel from RAM, and not actually flash it. Anyway, fastboot claims it downloaded and booted it ok, and the phone shows the "HERO" logo. Unfortunately that is as far as it gets. However, if I reset the phone, it boots perfectly fine from the kernel/ramdisk in flash (phew!)
Since it doesn't actually boot into android proper (and doesn't show up as a USB device), I don't know if (a) its showing the HERO logo, but failing the signature check, or (b) actually booting, but crashing 'cos the kernel/ramdisk aren't quite right. I'd guess (a) myself, but I'm new to messing with HTC bootloaders.
Anyway, in case they're useful, the details of the phone from the fastboot mode are:
HERO CVT SHIP S-ON
HBOOT-1.76.0004 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.04.25
Jul 3 2009,15:22:21
That method of entering fastboot is the same as the magic. Check the magic / sapphire wiki and have a read as I suspect the magic is its closest relative and a lot of the magic stuff will work...
daisy xx
Aha, thank you very much, that gives me more information!
Anyway, I just tried booting the boot.img itself instead of splitting it up with:
fastboot boot boot.img
This time, it booted right into the full android! Checking /proc/config.gz:
On the phone booting normally, it says:
# Linux kernel version: 2.6.27
# Fri Jul 3 07:52:06 2009
On the phone booted with boot.img extracted from that zip, it starts:
# Linux kernel version: 2.6.27
# Thu Jun 25 14:16:01 2009
So it seems as though it can boot the boot.img: AFAIK config.gz is hardcoded into the kernel binary. Now: is there a signature in the boot.img file?
Erm, I'm either hallucinating from lack of sleep, or I appear to have a root shell on it now. e.g. I can see the contents of /data from "adb shell":
ps reports: [snip]
root 43 1 3332 164 ffffffff 0000e8f4 S /sbin/adbd
root 619 43 748 340 c005ef5c afe0d08c S /system/bin/sh
# ls /data/app
org.oep.pong.apk
com.google.android.stardroid.apk
se.illusionlabs.labyrinth.lite.apk
com.google.zxing.client.android.apk
com.innovativelanguage.wordpowerlite.jp.apk
com.funambol.android.apk
com.massorbit.sword.apk
com.soundroid2012.piano.apk
jg.entertainment.abook.four.apk
com.maplekeycompany.apps.shake.apk
net.peterd.zombierun.apk
All I did was
1) pull the boot.img apart with split_bootimg
2) gunzip the ramdisk
3) hexedit the ramdisk to set ro.secure=0 (couldn't be bothered faffing about with cpio)
4) gzip the ramdisk
5) rebuild the image with mkbootimg. Oh you need to specify a different base address. Example command line:
/tmp/mkbootimg --kernel boot.img-kernel --ramdisk boot.img-ramdisk.insecure.gz --cmdline 'no_console_suspend=1 console=null' -o test-insecure.img --base 0x19200000
Then I just booted it with "fastboot boot test-insecure.img"
adq said:
Erm, I'm either hallucinating from lack of sleep, or I appear to have a root shell on it now. e.g. I can see the contents of /data from "adb shell":
ps reports: [snip]
root 43 1 3332 164 ffffffff 0000e8f4 S /sbin/adbd
root 619 43 748 340 c005ef5c afe0d08c S /system/bin/sh
# ls /data/app
org.oep.pong.apk
com.google.android.stardroid.apk
se.illusionlabs.labyrinth.lite.apk
com.google.zxing.client.android.apk
com.innovativelanguage.wordpowerlite.jp.apk
com.funambol.android.apk
com.massorbit.sword.apk
com.soundroid2012.piano.apk
jg.entertainment.abook.four.apk
com.maplekeycompany.apps.shake.apk
net.peterd.zombierun.apk
All I did was
1) pull the boot.img apart with split_bootimg
2) gunzip the ramdisk
3) hexedit the ramdisk to set ro.secure=0 (couldn't be bothered faffing about with cpio)
4) gzip the ramdisk
5) rebuild the image with mkbootimg. Oh you need to specify a different base address. Example command line:
/tmp/mkbootimg --kernel boot.img-kernel --ramdisk boot.img-ramdisk.insecure.gz --cmdline 'no_console_suspend=1 console=null' -o test-insecure.img --base 0x19200000
Then I just booted it with "fastboot boot test-insecure.img"
Click to expand...
Click to collapse
You're ready to build your own rom images ;-)
You could start by preparing your own rooted recovery with nandroid.
For a quick and dirty basic recovery image, just download one from sapphire development forum, replace the boot.img-kernel with a working copy for your hero.
Then rename init.sapphire.rc in init.hero.rc in ramdisk image.
You can simply extract ramdisk image with:
mkdir boot.img-ramdisk
cd boot.img-ramdisk
zcat ../boot.img-ramdisk.gz | cpio -idv
make your changes to ramdisk files
search internet for a script named repack-bootimg.pl
add the new base parameter to mkbootimg line in the script
cd to directory where you unpacked your boot.img
repack-bootimg.pl boot.img-kernel boot.img-ramdisk newboot.img
fastboot your recovery
then you can use nandroid in the recovery image to make a full dump of your rom and use the newer version of boot.img you have in your device to rebuild an up-to-date recovery or any kind of rom (you could start by preparing a copy of your original rom by changing ro.secure=0 in both boot.img and recovery.img).
By the way, I noticed that kernel in HERO uses sapphire fixup. The currently available version on the net is not booting on sapphire (magic) 32A, but it resets after a few minutes.
Maybe the kernel version in your orange hero introduces compatibility with sapphire boards. Well, really I suppose it won't, but if you get a nandrod backup and post your current original boot.img, magic 32A board owners could give it a try while we are waiting for HTC to release updated kernel sources for Magic and Hero.
Bye
daldroid
adq said:
[...]
So it seems as though it can boot the boot.img: AFAIK config.gz is hardcoded into the kernel binary. Now: is there a signature in the boot.img file?
Click to expand...
Click to collapse
No, no signature in standard boot.img, you have to zip it and sign the resulting zip. But no signing keys except for test-keys are available to the public, so I suppose your spl (S-ON) wil not allow you to directly flash rom images from fastboot command line.
However it seems your SPL allows you to fastboot a repacked boot image, so it should not be a problem to use a recovery image to flash whichever rom mod you like.
I suggest you not to flash any SPL you can find on the net, I suppose you have the newest ad no image of your original SPL is available (there is one from a leaked hero image, but yours seems to be newer)
Bye
Yeah, my thoughts exactly, I'd rather not flash the SPL if I can help it: I don't fancy explaining to my wife why I have to rip her phone apart to find the JTAG contacts I'll upload the boot.img later though.
Thats odd about the reset after a few minutes thing: hardware watchdog timer of some sort?
adq said:
Yeah, my thoughts exactly, I'd rather not flash the SPL if I can help it: I don't fancy explaining to my wife why I have to rip her phone apart to find the JTAG contacts I'll upload the boot.img later though.
Thats odd about the reset after a few minutes thing: hardware watchdog timer of some sort?
Click to expand...
Click to collapse
Well, really it's a little bit mor than a minute or so.
I suppose it's not an hardware watchdog, I don't have access to console debug messages.
Really the reset is a good sign, if you try booting dream or sapphire 32b kernel on 32A boards, it hangs forever.
If you extract piggy.gz from the kernel and hexedit it,you can find hero kerel initializes the hardware using the sapphire fixup.
It could only be that htc reused the same source and fixed hardware details and forgot to change the fixup routine name or that they are prepare to build a kernel able to boot on both hero and magic 32A boards.
32A and hero use the same new base address for kernel and ramdisk loading 0x19200000.
our boards have more memory than dream and 32b boards.
I suspect htc is using a stacked ram configuration and they changed the init code for the number of banks in memory.
In 32A they changed ram location for fb, ram console and maybe gpu1. It was a real mess to guess every change, so I stopped recompiling and rebooting the kernel after a dozen of times ;-) Waiting for htc to release the patched source code ;-)
The radio rom on hero seems to be is newer than 32a's latest available but I don't want to try a flash, you know what I mean ;-)
The available hero SPL shoud work on sapphire (and on blackstone and topaz too) and maybe the newer radio rom requires it, but... I prefer not to brick my Magic.
Have a nice rom rooting time. You could want to give superuser.apk a try.
People on this forum is asking for rooting status on hero, I suppose you'll be able to announce them your succes in a short time.
Wow! That was Fast! Lol..... even thought there is still some work to do.
i feel honoured to have been one of the first to read this i still dont have a hero yet =[ gotta wait till august when i get my ema might start scrounging and saving what i can get so i can get it sooner
Well done to you sir what a fine job uve done, gz =]
I'm waiting for my Hero as well and I'm completely new to android.
But like you I develop for and work with embedded Linux systems so tearing ROMs apart was pretty much on top of my list when my device should arrive .
I don't know what the 'recovery' image does on Android systems, but as I read it like this: You can temporary boot a rom (or at least a kernel and it will get the rest of the system from the rom area) through the fastboot method.
So yes, then you have temporary booted into a rooted ROM. But how to make it permanent? Because if you modify the ROM and flash it back it will probably not work because it detects its modified, right?
Trying to make a "dirty recovery image" to dump full roms using Nandroid Backup
Hello Dalroid,
I read your post and was able to do the following:
1. Using split_bootimg, extract the ramdisk files from the Stock HTC HERO Rom found in the XDA forums.
2. I downloaded the cm-recovery 1.4 image from Sapphire and used split_bootimg on it as well.
3. I copied the extracted kernel from the HTC Hero ROM and replaced the one from the cm-recovery of sapphire.
4. I renamed init.sapphire.rc to init.hero.rc in the extracted recovery image folder.
5. This is where i have trouble. I am using the repack-bootimg.pl, but I am unable to repackage the image.
I did note that you stated that some base parameters needed to be changed in the script for this to work. Could you please shed some light on what I need completed in order to repackage. Thank you in advance.
EDIT: I found one problem so far, I do not have mkbootimg or mkbootfs on my computer. How do I get these on my computer?
JWallstreet said:
Hello Dalroid,
I read your post and was able to do the following:
1. Using split_bootimg, extract the ramdisk files from the Stock HTC HERO Rom found in the XDA forums.
2. I downloaded the cm-recovery 1.4 image from Sapphire and used split_bootimg on it as well.
3. I copied the extracted kernel from the HTC Hero ROM and replaced the one from the cm-recovery of sapphire.
4. I renamed init.sapphire.rc to init.hero.rc in the extracted recovery image folder.
5. This is where i have trouble. I am using the repack-bootimg.pl, but I am unable to repackage the image.
I did note that you stated that some base parameters needed to be changed in the script for this to work. Could you please shed some light on what I need completed in order to repackage. Thank you in advance.
EDIT: I found one problem so far, I do not have mkbootimg or mkbootfs on my computer. How do I get these on my computer?
Click to expand...
Click to collapse
I built my mkbootimg from android source code (android.git.kernel.org), but if you prefer you can find a prebuilt binary from http://rapidshare.com/files/249629878/PortTools.rar. I'm not the author neither I tested it, just searched for mkbootimg in forums and pasted the link for you.
If you use the standard mkbootimg, just add --base 0x19200000 the the mkbootimg line, otherwise the boot.img will be generated with standard load address which won't work for hero (or for my 32A Magic).
This is pretty exciting stuff
I really want to remove the SIM lock from the Hero - is this something you can do now you've got su access?
Is it going to be possible to have a 'how to' guide for the Hero to tell us what to do to get the phone unlocked?
I want to see someone install the Magic image on the Hero - it should fly with the extra RAM
Just out of curiosity, what would happen if I booted the original cm-recovery-1.4.img on the Hero?
My phone will hopefully arrive tomorrow, and the first thing I'd like to do is create a backup with the nandroid script.
wossName said:
Just out of curiosity, what would happen if I booted the original cm-recovery-1.4.img on the Hero?
My phone will hopefully arrive tomorrow, and the first thing I'd like to do is create a backup with the nandroid script.
Click to expand...
Click to collapse
It wont boot. You can instead use the modified(only trackball press event and kernel) cyanogen's recovery here: http://forum.xda-developers.com/showthread.php?t=541807&page=2
enlightener said:
It wont boot. You can instead use the modified cyanogen's recovery here: http://forum.xda-developers.com/showthread.php?t=541807&page=2
Click to expand...
Click to collapse
I'm new to all this, so I'd be grateful for some more information: is the Dream and Hero hardware too different to boot the same image? Or would it be possible to create multi-platform images?
I already downloaded the modified image from that thread and have extracted the same kernel, so I should be all set.
This rooted kernel is for the "rooting beginners" and those who want to keep as close to stock as possible. CF-Root takes the kernel from an original Samsung firmware, and just adds root, busybox, and (unprotected recovery and CWM compatibility) OR (CWM3)
If you are looking for highly optimized kernels or kernels that perform specific functions, look elsewhere. All CF-Root's are based on original Samsung kernels, they are NOT recompiled, and thus ensure maximum compatibility.
THIS IS NOT A ROM - it is only a kernel. You need to have a firmware already on your device. You do NOT need to wipe anything for this patch. You DO need to read the instructions.
MAKE SURE YOUR PHONE CAN ENTER DOWNLOAD MODE USING THE KEYCOMBINATION WHILE BOOTING BEFORE FLASHING CF-ROOT (or anything, really)
Donate
There have now been over 200.000 downloads of CF-Root for various devices, and many more if you include ROMs, kernels, etc that use it. Don't be a leech, buy me a beer (and use the "Thanks" button!)
Features
- The kernel is fully stock and taken from the original firmware, with just the following added:
- Root
- Superuser 2.3.6.1
FROYO ( CF-Root < 2.4 versions )
---- Busybox 1.15.3 or 1.17.1 (if not mentioned in the filename it is 1.15.3)
---- "2e" recovery (can flash unsigned update.zip's)
---- Integrated fix for ClockworkMod's nandroid (2.5.0.4+)
GINGERBREAD ( CF-Root >= 2.4 versions, JVK and newer )
---- Busybox v1.16.2androidminimal (from CWM)
---- Integrated CWM 3.0.0.5 / RFS
CF-Root v4.3 (JVT and newer)
--- Superuser updated to v3
--- Kernel is now in "insecure" mode (rooted ADB shell)
CF-Root v4.4 (JW4 and newer)
--- SuperSU
--- ro.secure=1, patched adbd to act as if ro.secure=0
Instructions (short)
- Flash CF-Root-xxx-vX.X.tar (from the attached zip) as PDA in ODIN, without repartition. Done.
Instructions (long)
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached CF-Root-xxx-vX.X.zip
- (USB) Disconnect your phone from your computer
- Start ODIN
- Click the PDA button, and select CF-Root-xxx-vX.X.tar
- Put your phone in download mode
- (USB) Connect the phone to your computer
- Make sure repartition is NOT checked
- Click the START button
- Wait for the phone to reboot
- Done (if it took you more than 30 seconds, you need practise!)
Instructions (alternative if you are already running CF-Root 2.5 or newer)
- Copy the zip file to your SD card
- Stop sharing SD card with computer over USB, unplug the cable, etc
- Applications -> CWM -> Flash kernel. Select the ZIP file on your SD card.
- Done
Other kernels
Replacing CF-Root with other kernels (speedmod, voodoo, etc) and vice-versa sometimes works, sometimes it doesn't. I don't have a list.
When going from CF-Root to another kernel, root will usually stay, while 2e recovery will be lost (unless the other kernel also includes it), but there should not be issues.
CF-Root is made to be applied on a stock kernel. Going from a lagfixed kernel to CF-Root usually does not work. Unlagfix first.
Voodoo If you are running the latest Voodoo, you probably do not need CF-Root at all. Voodoo has the basic root features in place, but not the applications. Voodoo does not come with 2e recovery, but it does come with CWM, so there is no need for 2e on Voodoo. To get Superuser and Busybox on Voodoo, simply open Market and search, download, and install them ! Voila !
ClockworkMod on FROYO ( CF-Root versions < 2.4 )
CF-Root is ClockworkMod compatible, it does not include CWM itself. It uses 2e recovery, which means it can flash unsigned update.zip's, like CWM.
To use CWM, either place the update.zip in the correct location ( /sdcard ), or install it through the ROM Manager application.
When you boot into recovery, you will get the 2e recovery, even if CWM is installed. It does not boot directly into CWM (though it may do so when you boot into recovery from the ROM Manager application). Select "flash update.zip" in recovery to start CWM.
Important note: The very first time you do this on a ROM, it will usually not work. The phone will reboot normally after you flashed the update.zip. You need to reboot into recovery a second time and flash update.zip again. Then you will be launched into CWM. After this, it will work the first time you select it.
ClockworkMod on GINGERBREAD ( CF-Root versions >= 2.4, excluding JV1 on which CWM is broken )
CF-Root includes a special version of CWM3, modified to work with RFS. CWM3 by default does not support RFS, koush' versions are all based on ext4. The RFS compatibility is done with heavy scripting, the same method used on CF-Root for Galaxy Tab. For SGS CWM3 is also recompiled from source with some slight modifications to handle key input correctly.
CF-Root/CWM3 is NOT compatible with ROM Manager! Manage/perform your backup/restores from CWM directly.
- Booting into recovery will immediately give you CWM. The standard recovery is completely gone.
- A "CWM" icon is added to your applications, which will reboot your device into recovery mode (CWM).
- ADB is functional in recovery, however it may take up to a minute for it to start up after booting into recovery.
- When connected to ADB in recovery, you need to use "rootsh" command to get root, instead of "su". This will not prompt you, it will just give you root. Obviously the "rootsh" command does not work when booted normally.
- Version jumped from 1.3 to 2.4 to keep the cross-device CF-Root versioning in-sync (CF-Root is also available for Galaxy Tab).
- If you wonder where your bootup/shutdown sounds have gone, CF-Root probably removed them to make sure it has enough space available.
- ( CF-Root versions < 2.6 ) Make sure to boot up your device fully at least once before flashing CF-Root. This is because the device may have some code it needs to run at first boot. CWM disables this code.
CWM Manager on GINGERBREAD ( CF-Root versions >= 2.5 )
Because of incompatibility with ROM Manager, I wrote and included "CWM Manager". This is a new app (as of March 30, 2011) and beta. You can find it under Applications -> CWM. It is much faster to use than manually booting into CWM and selecting these options.
Features:
- Boot to CWM
- Backup firmware
- Restore backups
- Delete backups
- Install APKs ( CF-Root versions >= 2.8 )
- Flash CWM3 update.zip's
- Flash kernels (zImage, zImage in TAR, zImage in ZIP, zImage in TAR in ZIP)
Note: If you flash a different kernel, CWM Manager may remain installed. However, functions may not work, because they need kernel compatibility ! At this version of CWM Manager this does not produce errors, it just doesn't do what you expect it to
Tweak Manager on GINGERBREAD ( CF-Root versions >= 2.8 )
CF-Root includes a number of tweaks that are applied on startup. From CF-Root versions 2.8 and up a "Tweaks" application is included you can use to select which tweaks to apply.
Ext4 Manager on GINGERBREAD ( CF-Root versions >= 2.8 )
CF-Root supports ext4 mounts for the main mount points. Converting between rfs and ext4 however requires a secondary external package (which you can find in the download area a great many posts below this one), because it is all too large to fit inside the kernel. Download the APK from below, put it on your sd card, start CWM Manager, select "Install APK", find the APK and tap to install. Now you can use the "ext4" app to convert between filesystems, manually check the filesystem, etc.
Obviously you should revert back to rfs before flashing a new stock ROM. A lot of custom ROMs support ext4 as well, but it is still advised to revert to rfs before installing them.
Please note that when first using the tool to convert, you will probably notice /system is not converted. If this happens, it is because /system does not have enough free space for the extra space overhead of ext4. You will need to free up some space on /system before the conversion will succeed.
Features:
- Show current filesystem status
- Convert between rfs <=> ext4 and back
- Manual fsck
- Selects either internal or external sdcard for temporary storage, depending on which has the most space
- Automatically reverts on conversion failure
- If it tells you to PANIC !, please do so
Custom boot / init scripts on GINGERBREAD ( CF-Root versions >= 2.8 )
CF-Root will execute the following scripts if present, in the order listed:
- /system/etc/init.d/* (there can be many files here, no extensions! use #!)
- /system/bin/customboot.sh (busybox sh)
- /system/xbin/customboot.sh (busybox sh)
- /data/local/customboot.sh (busybox sh)
Please make sure you chown / chmod the scripts correctly so they can be executed.
Custom boot animations and binaries on GINGERBREAD ( CF-Root versions >= 2.9, broken in 2.8 ! )
CF-Root also supports custom boot animations:
- /system/media/bootanimation.zip
- /data/local/bootanimation.zip
CF-Root v3.0 and up also support:
- /data/local/bootanimation.bin
Installing busybox over the included version on GINGERBREAD ( CF-Root versions >= 3.0 )
It is possible to install a custom busybox over CF-Root v3.0 and newer. However, this is not without risk. CF-Root makes heavy use of scripting, and many CF-Root scripts rely on the internal busybox version. If you do install a seperate busybox version (always use "stericson" installer!), install it to /system/xbin. Installing it to /system/bin will mess things up for sure. Even if you do that part right, it may still break CF-Root, so make sure to make a backup before trying.
Notes
- (FROYO) ADB in recovery is flaky. Sometimes it works, sometimes it doesn't. If you go into ClockworkMod it usually works, though.
- (FROYO) An older version of BusyBox is used (in some versions) because the newer versions drive me absolutely crazy with throwing color codes into the shell while it isn't supported.
How ?
I wrote my own toolchain to ease patching of initramfs, and that is what all this is based on. Took me a few days to get it to this state. If this works right, however, next time it will probably take me a few hours tops
Help! I don't know which file to pick! The filenames confuse me!
First thing: don't panic! It's all rather easy, and you won't easily do something bad! I am personally attentive to use the exact same version as the ROM I am running, but it's not that important.
First, go to Settings -> About phone -> Build number. It should say something like FROYO.xxJPy. It's primarily the JPy that we are interested in. Try to match that with a download link available in this (and the next few) posts. Some of the downloads dont just have JPy file name format, but are called xx_xxx_JPy.
Let me explain that. Samsung isn't always very precise in naming/marking their different (leaked) firmwares. CF-Root's are modified kernels, the filenames explain in more detail which exact firmware ROM the base kernel was taken from, for those experts who understand.
If you are not one of those people, go back to the JPy thing. The "y" in JPy is 0-9, A-Z. If they run out of numbers, they use letters. So A would be 10 (9 + 1), while Z would be 35 (9 + 26). Find the one that is closest to yours, if yours is not present, and flash that one.
The truth is, these kernels, they don't differ all that much. It's quite likely that the very latest version (at time of writing: JPY) will work perfectly fine on your ROM. There are some small differences, but using a different version is unlikely to cause serious issues. The closer the versions are, the less likely there are to be issues, BUT it is still quite possible that the latest version will work better for you than the matching version (or not!).
If you are just installing CF-Root to flash a custom ROM like Darky, make sure you have ROM Manager already installed, ClockworkMod flashed, then simply install the latest CF-Root, reboot once normally, then reboot in recovery and run the Darky update.zip. In this case it does NOT need to be a near match at all!
Download
LOOK WELL AT THE FILENAMES, MAKE SURE YOU ARE GETTING THE RIGHT VERSION !
DOWNLOADS CONTINUED IN NEXT POSTS !
CF-Root-JPH-v1.0.zip
CF-Root-JPH-v1.1.zip
CF-Root-JPK-v1.1.zip
CF-Root-JPM-v1.2-Busybox-1.15.3.zip
CF-Root-JPM-v1.2-Busybox-1.17.1.zip
CF-Root-JP6-v1.2-Busybox-1.15.3.zip
CF-Root-JP6-v1.2-Busybox-1.17.1.zip
--- more downloads ---
CF-Root-JPJPA-v1.2-Busybox-1.15.3.zip
CF-Root-JPJPA-v1.2-Busybox-1.17.1.zip
CF-Root-XX_XEU_JPO-v1.2-Busybox-1.15.3.zip
CF-Root-XX_XEU_JPO-v1.2-Busybox-1.17.1.zip
CF-Root-XW_XEE_JPA-v1.2-Busybox-1.15.3.zip
CF-Root-XW_XEE_JPA-v1.2-Busybox-1.17.1.zip
CF-Root-XX_OXA_JPU-v1.3-BusyBox-1.15.3.zip
CF-Root-XX_OXA_JPU-v1.3-BusyBox-1.17.1.zip
--- more downloads ---
ROOTING JVK: See this post instead. It contains a CF-Root version specifically for JVK, you do not need to flash back the original kernel again. I also strongly advise you to read the first post of this thread.
ROOTING JV1: The JV1 version is not compatible with ANY version of ClockWorkMod (CWM).
CF-Root-XX_XEU_JPX-v1.3-BusyBox-1.15.3.zip
CF-Root-XX_XEU_JPX-v1.3-BusyBox-1.17.1.zip
CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.15.3.zip
CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.17.1.zip
CF-Root-XW_OXX_JV1-v1.3-BusyBox-1.15.3_NO-CWM.zip
CF-Root-XW_OXX_JV1-v1.3-BusyBox-1.17.1_NO-CWM.zip
--- more downloads ---
CF-Root-XW_OXF_JS2-v1.3-BusyBox-1.15.3.zip
CF-Root-XW_OXF_JS2-v1.3-BusyBox-1.17.1.zip
CF-Root-XW_XEN_JS3-v1.3-BusyBox-1.15.3.zip
CF-Root-XW_XEN_JS3-v1.3-BusyBox-1.17.1.zip
CF-Root-XW_XEN_JS5-v1.3-BusyBox-1.15.3.zip
CF-Root-XW_XEN_JS5-v1.3-BusyBox-1.17.1.zip
CF-Root-XW_XEE_JS7-v1.3-BusyBox-1.15.3.zip
CF-Root-XW_XEE_JS7-v1.3-BusyBox-1.17.1.zip
--- more downloads ---
Note: it is NO PROBLEM to flash new JVK version over old JV1 or JVK version!
Release notes for v2.5: http://forum.xda-developers.com/showpost.php?p=12507221&postcount=1188
Release notes for v2.6: http://forum.xda-developers.com/showpost.php?p=12526079&postcount=1211
Release notes for v2.7: http://forum.xda-developers.com/showpost.php?p=12563930&postcount=1256
Fix for iptables / Droidwall for JVK: http://forum.xda-developers.com/showpost.php?p=12527335&postcount=1212
Note that v2.8 is available in the next post
CF-Root-XX_DBT_JQ3-v1.3-BusyBox-1.15.3.zip
CF-Root-XX_DBT_JQ3-v1.3-BusyBox-1.17.1.zip
CF-Root-XW_NEE_JS8-v1.3-BusyBox-1.15.3.zip
CF-Root-XW_NEE_JS8-v1.3-BusyBox-1.17.1.zip
CF-Root-XX_OXA_JVK-v2.4-CWM3RFS.zip
CF-Root-XX_OXA_JVK-v2.5-CWM3RFS.zip
CF-Root-XX_OXA_JVK-v2.6-CWM3RFS.zip
CF-Root-XX_OXA_JVK-v2.7-CWM3RFS.zip
--- more downloads ---
Note: it is NO PROBLEM to flash new JVK version over old JV1 or JVK version!
Release notes for v2.8: http://forum.xda-developers.com/showpost.php?p=12652182&postcount=1332
Release notes for v2.9: http://forum.xda-developers.com/showpost.php?p=12672516&postcount=1400
Release notes for v3.0: http://forum.xda-developers.com/showpost.php?p=12736616&postcount=1536
Release notes for v3.1: http://forum.xda-developers.com/showpost.php?p=12823970&postcount=1663
Release notes for v3.1 JVB: http://forum.xda-developers.com/showpost.php?p=12950723&postcount=1774
Release notes for v3.2 JVH: http://forum.xda-developers.com/showpost.php?p=13619653&postcount=2012
Release notes for v3.7 JVP: http://forum.xda-developers.com/showpost.php?p=14582942&postcount=2227
Apparently this CIFS patch works for JVB/JVK CF-Root: http://forum.xda-developers.com/showpost.php?p=12997697&postcount=123
More downloads after the ext4 and license posts!
CF-Root-XX_OXA_JVK-v2.8-CWM3RFS.zip
CF-Root-XX_OXA_JVK-v2.9-CWM3RFS.zip
CF-Root-XX_OXA_JVK-v3.0-CWM3RFS.zip
CF-Root-XX_OXA_JVK-v3.1-CWM3RFS.zip
CF-Root-XW_XEE_JVB-v3.1-CWM3RFS.zip
CF-Root-XW_NEE_JVH-v3.2-CWM3RFS.zip
CF-Root-XX_OXA_JVO-v3.2-CWM3RFS.zip
CF-Root-XX_OXA_JVP-v3.7-CWM3RFS.zip
ext4 tools
Note: don't link to this post directly, as it will move down in the thread when more CF-Root downloads become available!
The ext4 tools addon for CF-Root requires CF-Root version 2.8 or later
Release notes for v1.0: http://forum.xda-developers.com/showpost.php?p=12652182&postcount=1332
Release notes for v1.1: http://forum.xda-developers.com/showpost.php?p=12672516&postcount=1400 (non-essential update)
Release notes for v1.2: http://forum.xda-developers.com/showpost.php?p=12736616&postcount=1536 (non-essential update)
Release notes for v1.3: http://forum.xda-developers.com/showpost.php?p=13619653&postcount=2012
LICENSE for CF-Root v3.0+, ext4 tools v1.2+
As it seems a number of kernels are being based on CF-Root, and CF-Root is being included in custom ROMs, I'm going to set up a number of rules. The rules are meant to be fair to both you and me, and futher cooperation, not limit it. If you are an end-user, do not distribute kernels based on CF-Root, and do not distribute ROMs using it, you can skip this post, it is not for you. If you make kernels based on CF-Root, or your ROMs include CF-Root, read this post and follow the rules.
I don't mind you using the CF-Root hacked kernels, in fact I think it's great All parts of CF-Root are free to use/include in your own stuff, if these rules are followed.
If something doesn't work for you, feel free to PM/ask for a change. None of these rules are set in stone, maybe you have a good reason to want something different.
Usage of "CWM Manager", "Tweak Manager", and "ext4 tools" apps
- You may not modify these APKs in any way, if you include or redistribute them. The only exception to this rule is modifying the icons to match your ROM's theme.
- You may not re-post these files anywhere else (separately from CF-Root), but you may of course link to the post (not the download directly!) in the CF-Root thread containing these files. In other words, either you include them or you don't, but you can't offer them as a separate download.
- You must use the appropriate versions, released at the same time as the kernel, or any newer version released by me. For example, if you are using CF-Root v3.0, if you use/include these apps, you must use CWM Manager 1.50+, Tweak Manager 1.20+ and ext4 Manager 1.20+.
- You must test that their functionality remains 100% intact regardless of your (kernel/ROM) modifications. If the functionality is not as expected with your (kernel/ROM) modifications but you still include the apps, you must clearly state what you know is broken.
If you are just using CF-Root in your custom ROM, but do not modify the CF-Root kernel in any way (except icons)
- You must include a notice that the ROM uses CF-Root, and the version of CF-Root used.
- You should (not required but strongly encouraged) also include a link to this thread ( http://forum.xda-developers.com/showthread.php?t=788108 )
- You should (not required) include a link to donate to me, Chainfire ( http://www.jongma.org/dx.php )
- You should (not required) inform me that you are using it either by posting in the CF-Root thread or sending me a PM. (Thanks!)
- As you are not modifying CF-Root in any way (except icons), you can skip the rest of this post
Modifications to CF-Root (aside from the icons)
- Due to a lot of bickering and argueing, I'm simply no longer allowing this at all
- You can still kang a script or two left and right, I don't mind, as long as you are not basing an entire kernel on mine, or re-branding it, etc. Use common sense, you know exactly what I mean.
--- more downloads ---
JVI: Untested by me
JVQ: Untested by me
JVT: v4.3, Superuser updated to v3.0.2, and "insecure" mode
JVA: Untested by me
JVU: Untested by me
JVZ: Untested by me
CF-Root-XW_DBT_JVI-v3.7-CWM3RFS.zip
CF-Root-XX_UNK_JVQ-v3.7-CWM3RFS.zip
CF-Root-XX_OXA_JVR-v4.1-CWM3RFS.zip
CF-Root-XX_OXA_JVS-v4.1-CWM3RFS.zip
CF-Root-XX_OXA_JVT-v4.3-CWM3RFS.zip
CF-Root-XF_TSR_JVA-v4.3-CWM3RFS.zip
CF-Root-XW_TMN_JVU-v4.3-CWM3RFS.zip (OLD !! Not the 2012 version !!)
CF-Root-XX_OXA_JVZ-v4.3-CWM3RFS.zip
This is the December 29, 2011 / Android 2.3.6 / JVU / Value Pack ? build:
CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS.zip
March 2012 / Android 2.3.6 / JW4 / Value Pack build:
CF-Root-XX_OXA_JW4-v4.4-CWM3RFS.zip
In Odin, repartition unchecked?
Awesome news saves me a lot of battery in battery out hassle - here's the kicker - I'm going back to JPC because of MODEM file issues and touchwiz lag - anychance of a JPC version ?
This is good stuff. I will test it tomorrow.
ed10000 said:
In Odin, repartition unchecked?
Click to expand...
Click to collapse
Don't touch anything except the PDA and START buttons, as per the instructions.
DangerMUK said:
Awesome news saves me a lot of battery in battery out hassle - here's the kicker - I'm going back to JPC because of MODEM file issues and touchwiz lag - anychance of a JPC version ?
Click to expand...
Click to collapse
Making a JPC version requires testing and some trial and error... not something I'm looking forward to be doing, as JPH is newer.
Thank you so much.
Can I flashed this if I have lagfix ?
poowe893 said:
Thank you so much.
Can I flashed this if I have lagfix ?
Click to expand...
Click to collapse
It should not be a problem. I flashed it myself over an active installation of CF-LagFix. Cannot guarantee it will be without issues, but I do not expect it to be a problem.
Flashed like a charm for me. But on restart, I got totally wierd settings, frequent FCs etc, those were very anxious 10 minutes, the I pulled the battery, reinserted, restarted the phone, & everything is normal. Thanks.
Hi there. Thanks for this release. I already have a JPH ROM flashed. How do I reflash this one, meaning, do I need to erase/wipe cache or format my SD card? Or just simple over writing will work?
Thanks so much.
ragin said:
Flashed like a charm for me. But on restart, I got totally wierd settings, frequent FCs etc, those were very anxious 10 minutes, the I pulled the battery, reinserted, restarted the phone, & everything is normal. Thanks.
Click to expand...
Click to collapse
I had this myself in one of my tests. Not completely sure what causes it but I suspect it is because in the background SU is being installed/upgraded. Waiting a few minutes and rebooting solved the issue for me as well. As it only occurred once for me I did not mention it, but I have now updated the first post with this info.
rajuki said:
Hi there. Thanks for this release. I already have a JPH ROM flashed. How do I reflash this one, meaning, do I need to erase/wipe cache or format my SD card? Or just simple over writing will work?
Thanks so much.
Click to expand...
Click to collapse
Yes, you already need the JPH firmware installed. You do NOT need to wipe cache, data, SD card, etc. Just follow the instructions - this patch only overwrites a small partion of the ROM.
Works for me..great it's fast and easy. Good Job
Great job, I'll test it asap.
Just one question for you: did you symlink available busybox commands or just put in the BB executable?
PLEASE NOTE: this script is no longer updated
###################################
FULL PACKAGES
###################################
EasyFlash for Linux v6.9
EasyFlash for Windows v4.9 ~ link was broken, now it's working
--## At the moment, both scripts will flash ##--
#- 1.26, 1.28 and 1.29 stock boot images
#- 1.26, 1.28 and 1.29 stock recovery images
#- clockworkmod touch recovery 5.8.4.0 image
#- TeamWin Recovery 2.2.0 image
#- leedroid one xtreme 6.4.0 boot image
#- android revolution 6.1.1 boot image
#- android revolution 7.2.1 boot image
#- franco kernel r12 boot image
#- it will also flash any other boot image that is placed in it's
'custom' folder and renamed to 'boot.img
--## It will also: ##--
#- find your CID and MID
#- push franco's latest modules to your device
so that you can just boot into recovery and flash the modules
#- push superwipe to your device
so you can boot into recovery and superwipe
#- push Aroma File Manager to your device
so you can boot into recovery and manage your files..
#- push ROMCleaner (and other necessary files/ directories) to your device
so you can boot into recovery and clean your rom..
###################################
BEFORE YOU RUN THE SCRIPT
###################################
--## Please make sure that: ##--
1. your HOX must be plugged into your computer
a) linux users won't need any extra files
b) windows users will need to install the Google USB Drivers
note: if your having trouble installing the usb drivers
try googling the problem: how to install drivers with cat files
alternatively you can install:
HTC Sync
you won't need the Google USB Drivers if you install HTC sync
--## REGARDING ROMCLEANER: ##--
it is recommended that you make the change that you want to the
text file in the files/ROMCleaner directory, before using the script
--## PLEASE NOTE: ##--
you DON'T NEED TO PUT THE PHONE INTO FASTBOOT yourself,
THIS SCRIPT WILL DO IT FOR YOU!!
just plug it in and flash. EASY!
###################################
RUNNING THE SCRIPTS
###################################
--## For the Linux version: ##--
just run the 'flash-boot-linux.sh' in the folder, it's already executable.
--## For the Windows version: ##--
just run the 'easyflash-windows.bat' file in the folder
###################################
MY MESSAGE and CHANGELOG
###################################
If there's any issues with the script, or you just wanna chat about it, feel free to hit me up.
Thanks, go out to:
Try4Ce - treebill - vladnosferatu - franciscofranco - LeeDroid - mike1986. - broncogr - koush
----------------------------------------------------------------------------------
linux v6.9 & windows v4.9
- the script now has the option to push ROMCleaner
~ will also create the necessary directories and push necessary files
for ROMCleaner to work
- completely fixed the bugs with quick tools
- added updated version of ARHD kernel (7.2.1)
- the script will now flash TeamWin Recovery (2.2.0)
- the script will now allow for booting into TeamWin recovery
- GUI has had more changes made to it
linux v6.4 & windows v4.4:
- the script now has the option to push the Aroma File Manager
- fixed the pushing (quick tools) scripts bug
- made necessary adjustments to the 'GUI'
linux v6.3 & windows v4.3:
- the script now has the option to push superwipe
instead of automatically pushing when you try to flash ARHD boot.img
- the script now has the option to push franco module
instead of automatically pushing when you try to flash franco kernel
- the 'GUI' has been revamped again
linux v5.2 & windows v3.2:
- removed the need to boot into fastboot yourself
now you can just plug it into your computer and choose the options you want
- the script will now push franco's modules to your SDcard
- the script will now push Superwipe to your SDcard
~ the script does this automatically ~
~ next version will give you a choice ~
linux v5.0 & windows v3.0:
- added updated version of franco kernel (r11)
- added updated version of ARHD boot.img (7.0.x)
- revamped the script prompts (better navigation)
linux v4.3 & windows v2.3:
- added updated version of franco kernel (r10)
- fixed erase cache loop bug
linux v4.1 & windows v2.1:
- added updated version of ClockworkMod Touch Recovery
(5.8.4.0)
linux v4 & windows v2:
- added 1.29 recovery image
- added option to get CID and MID
windows v1:
- ported code over from linux version
- all future version will get the same updates as the linux version
linux v3:
- reworded some prompts
- added 1.29 stock boot image
linux v2:
- fixed up the flashing ARHD boot image problem
- changed/reworded some of the prompts
- made script more robust, it can handle uppercase letters
- fixed looping problems, you can now do multiple things during one session
linux v1:
- flashed 1.26 & 1.28 stock boot images
- flashed 1.26 & 1.28 stock recovery images
- flashed clockworkmod touch recovery 5.8.3.x image
- leedroid one xtreme 6.4.0 boot image
- flashed android revolution 6.0.0 boot image
- flashed franco kernel r9 boot image
- flashed any boot.img that was placed in the
'custom' folder and renamed to 'boot.img
- flashing ARHD boot image would return an error
- prompts fairly vague to read
Good job mate........this will certainly help our felow xda members..
Sent from my HTC One X using xda premium
Really wish for a Windows version, but better yet, a way to do it without the need of any computer, just the HOX.
Sounds like a day-dreaming?
Thanks for the kind words.
I'll start looking up some scripting for windows tonight.
and the 1.29 problem tonight too
Sent from my HTC One X using xda premium
voryzen said:
Thanks for the kind words.
I'll start looking up some scripting for windows tonight.
and the 1.29 problem tonight too
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
havent had a chance to look at how you set out the folders etc. but hope this helps for the windows one.
Code:
@ECHO off
cls
:start
ECHO.
ECHO 1. flash 1.29
ECHO 2. flash cwm
ECHO 3. flash 1.26
set /p choice=type the number to start flashing.
if not '%choice%'=='' set choice=%choice:~0,1%
if '%choice%'=='1' goto one
if '%choice%'=='2' goto two
if '%choice%'=='3' goto three
ECHO "%choice%" is not valid please try again
ECHO.
goto start
:one
ECHO flashing 1.29
fastboot flash boot /129/boot.img
goto end
:two
ECHO flashing cwm
fastboot flash recovery cwm/recovery.img
goto end
:three
ECHO flashing 1.26
fastboot flash boot /1.2/boot.img
goto end
:end
ECHO finished flashing
pause
exit
sure you can get it working as you want
edit: for kernel flashing you can add "fastboot boot clockworkmod.img" after the flashing of boot.img that will make the phone boot into recovery right from fast boot.
thanks for the code snippet, treebill.
it was a great place to start learning some batch scripting
Willy318is said:
Really wish for a Windows version, but better yet, a way to do it without the need of any computer, just the HOX.
Sounds like a day-dreaming?
Click to expand...
Click to collapse
ha... when we finally get s-off, this will become a reality!
since I have posted last, I've:
- added some functionality
- updated this script to ensure everything is working
- updated script to be more robust
- added update zips (that work from version 4 onwards) incase people don't want to download everything again
hopefully this can help a few people out
and remember, if I have helped you out, hit the 'thanks' button on the OP
or shoot me a pm, if you have any questions about anything
Q&A for [KERNEL][AOSP/CAF][NOV 16] Glitch for Flo/Deb - r303
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][AOSP/CAF][NOV 16] Glitch for Flo/Deb - r303. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Root not working
Hello!
First of all :good: :good: :good: I am using your kernel more or less since I own the Nexus 7 (2013) in combination with Multirom and some custom ROMs, installed as secondary. It is working like a charm and I never saw any problems on "KK".
With "L" root is not (yet?) working for me. This might however been caused by the way of using it. I have two scenarios: 1.) "L" as secondary ROM and 2.) "L" as primary ROM. For both cases I used Tassadar's build. For the latter I copied the installed secondary ROM to the primary slot. With Tassadar's kernel I have root. When installing GlitchKernel root is gone. By flashing Tassadar's boot.img I regain root. As far as I can say right now this -- regaining root -- does not work for the secondary ROM.
To have it said: I also tried flashing GlitchKernel and Chainfire's SuperSU directly afterwards before rebooting with no effect. One thing I haven't tried is to NOT inject Multirom after flashing your kernel.
It would be great if you could help. If there is anything I could/should test, let me know!
Finally, my prayers are also with you!!!
Best Regards,
tungdil
@tungdil
Hello tungdil,
I'll start by asking what revision of Glitch are you running ?
r300 didn't come with root support out of the box, and it is required to flash a root-enabled boot.img (the ramdisk in it to be exact) prior to flashing r300 to enable the rooting technique of your choice (SELinux Permissive (potentially with system R/W access) or just Chainfire's partial root "trick"). Lollipop's security enhancements are modifying how root works for us (users), so until some kind of standard takes place I did want to wait and see.
However, considering many users didn't find that easy (either to understand or to find what boot.img to get for what result), I did release r303. This new revision comes with various ramdisk patches you can enable through Aroma to get anything from Chainfire's partial root to full root with SELinux Permissive, system partition R/W access and PIE bypassing (it will obviously lower Lollipop security though).
I'm using this new revision on primary and secondary roms using MultiROM with no rooting issue.
If you're running r300, get the r303 update. If you're already on r303, what apps are you running that won't get root access ? You may want to use more patches to "open the can".
Have a nice day !
Tk-Glitch said:
@tungdil
Hello tungdil,
I'll start by asking what revision of Glitch are you running ?
r300 didn't come with root support out of the box, and it is required to flash a root-enabled boot.img (the ramdisk in it to be exact) prior to flashing r300 to enable the rooting technique of your choice (SELinux Permissive (potentially with system R/W access) or just Chainfire's partial root "trick"). Lollipop's security enhancements are modifying how root works for us (users), so until some kind of standard takes place I did want to wait and see.
However, considering many users didn't find that easy (either to understand or to find what boot.img to get for what result), I did release r303. This new revision comes with various ramdisk patches you can enable through Aroma to get anything from Chainfire's partial root to full root with SELinux Permissive, system partition R/W access and PIE bypassing (it will obviously lower Lollipop security though).
I'm using this new revision on primary and secondary roms using MultiROM with no rooting issue.
If you're running r300, get the r303 update. If you're already on r303, what apps are you running that won't get root access ? You may want to use more patches to "open the can".
Have a nice day !
Click to expand...
Click to collapse
Hello Tk-Glitch!
Thanks a lot for your feedback! My feeling is I am doing something wrong because you wrote you don't have problems using it with MultiROM. But let me answer your questions:
Actually I tried both r300 and r303 using the following sequence:
"install" with TWRP (or delete and inject if it is the secondary ROM) the boot.img which is packaged with Tassadar's lrx21p_flo.zip. Note: I do have root afterwards
Flash GlitchKernel, reconfigure everything in the Aroma installer. Usually I don't use permissive mode or PIE Patch but have tried it as well with no success
Reboot, which results in not having root.
For the primary ROM: Re-install the Tassadasr's boot.img; which results in having root again.
That means, I start with a situation where root is working (btw. Kernel: 3.4.0-g0356b90-00001-gd0e79e3 [email protected] #240)! Yesterday I have also updated the bootloader to 04.04 with no effect. Just right now I tried it again and after flashing Glitch-N7-r303.zip (leaving all options as is but selecting PIE patch and permissive mode) the Kernel is: 3.4.0-Glitch-N7-AOSP-r303 [email protected] #1, dated 16.11.14 08:08:49 PST but I don't have root.
The following "apps" are not working AFWall+, MultiROM Manager, Reboot Menu Widget, and su itself if directly "called" from within Terminal Emulator. Just to have it said: ES File Explorer also won't work, but that's because it needs at least the PIE patch. The log of SuperSU tells, for example for AFWall+:
Code:
iptables v1.4.20: can't initialize iptables table ... : Permission denied
When I try launching su from the Terminal, SuperSU will ask to confirm root access even if I previously allowed root acces permanently. If I allow root nothing happens and the Terminal is "dead". The same applies for the other apps. I also tried this via an adb shell with the same effect, i.e. from the adb shell with root I'll see:
Code:
[email protected]:/ $ whoami
whoami: unknown uid 2000
1|[email protected]:/ $ su
[email protected]:/ #
and without
Code:
[email protected]:/ $ whoami
whoami: unknown uid 2000
1|[email protected]:/ $ su
i.e. the shell will not return.
Anything else I could test or check?
Best regards,
tungdil
Solved
Hello Tk-Glitch,
I "just" saw that Chainfire released an update to SuperSU (Beta 2.23) and ... that did it for both, primary and secondary ROM. I was on SuperSU Beta 2.19 before. My installation procedure for 2.23 was as follows:
Start with root NOT working for the primary ROM and working for the secondary ROM
For primary ROM use a TWRP queue for flashing GlitchKernel r303 and SuperSU Beta 2.23, and for the secondary ROM first flash GlitchKernel and then SuperSU
reboot and ... :good:
Notes:
currently not using the PIE patch when installing Glitch kernel, i.e. no root for ES File Explorer. All other apps I mentioned above do have root!
the same installation procedure did not work with SuperSU 2.19
Best regards!
tungdil
@tungdil
Hi again tungdil,
It's nice you got it sorted, though it convinces me something must be wrong with your installation process. Latest SuperSU is able to mod the ramdisk to enable root support (pretty similar to what Glitch r303 is supposed to do), so yes it works, though the question is why didn't it work with r303 for you ?
It may very well be an error on my side (I'll verify that), though it worked for me and most it seems, as you're the only one to encounter the issue since r303 release, or at least to talk about it. I checked my secondary ROM to be sure, but I'm indeed running SuperSU 2.19 on it.
By the way, injecting multirom shouldn't be required with Glitch, and leaving it checked will only lead to multirom detecting it's not needed and skip the injection (so basically you don't have to worry about it).
If you're okay, let me ask a few questions :
- Do you have screen timeout disabled in TWRP ? And if you don't, are you able to hit the reboot button after Glitch install ?
- What ROM are you running ?
- Could you please install r303 and save the installation log for me ?
- Could you please copy the /fstab.flo content from a ROM you got Glitch installed to for me?
- Why to use "delete and inject" for secondary ROM instead of "classic" install ?
Thank you !
Hello Tk-Glitch,
thanks a lot for your feedback and giving me the chance to learn something. I'll be happy to supply additional information:
- Do you have screen timeout disabled in TWRP ? And if you don't, are you able to hit the reboot button after Glitch install ?
Click to expand...
Click to collapse
The screen timeout in TWRP is not disabled but set to 300, and it is possible to hit the reboot button (or do something else before rebooting).
- What ROM are you running ?
Click to expand...
Click to collapse
As mentioned I am using the ROM which Tassadar has packaged (lrx21p_flo.zip).
- Could you please install r303 and save the installation log for me ?
Click to expand...
Click to collapse
Yes! I did a fresh install, i.e. added another secondary ROM and stored the LOG. Note: I didn't touch the "options" during install so everything was as preset. After GlitchKernel I flashed SuperSU 2.19 and verified via adb shell that root is not working.
Contents of the log (mr_update.zip.log.txt):
Code:
AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
ROM Name : Glitch kernel
ROM Version : N7-AOSP
ROM Author : Tk-Glitch
Device : Nexus 7 (2013)
Start at : Wed Nov 19 21:24:46 2014
installing samsung updater extensions
Installing Glitch kernel...
Extract: /tmp/buildconfig.sh
Extract: /tmp/busybox
Extract: /tmp/compatibility.sh
Extract: /tmp/compatibility2.sh
Extract: /tmp/glitch-settings.conf
Extract: /tmp/systemcheck.sh
Cleaning up
about to run program [/tmp/systemcheck.sh] with 1 args
Installing system files for real.
Extract: /system/bin/fstrim
Extract: /system/etc/init.d/99glitchsetup
about to run program [/tmp/buildconfig.sh] with 1 args
about to run program [/tmp/busybox] with 4 args
Fluxi's MSM Hotplug enabled
Renaming binaries...
/system/bin/mpdecision -> mpdecision_bck
/system/bin/thermald -> thermald_bck
about to run program [/tmp/compatibility.sh] with 1 args
Extract: /tmp/abootimg
Extract: /tmp/cmdline.cfg
Extract: /tmp/edit_ramdisk.sh
Extract: /tmp/edit_ramdisk_permissive.sh
Extract: /tmp/fstab.tmp
Extract: /tmp/glitch.zImage
Extract: /tmp/max_oc.sh
Extract: /tmp/restore.sh
Extract: /tmp/sepolicy.tmp
Applying init settings
about to run program [/tmp/busybox] with 4 args
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.472290 seconds, 33.9MB/s
about to run program [/tmp/abootimg] with 6 args
writing boot image config in /tmp/bootimg.cfg
extracting kernel in /tmp/zImage
extracting ramdisk in /tmp/initrd.img
about to run program [/tmp/max_oc.sh] with 1 args
about to run program [/tmp/edit_ramdisk.sh] with 1 args
2372 blocks
CIF hack found!
about to run program [/tmp/abootimg] with 9 args
reading config file /tmp/cmdline.cfg
reading kernel from /tmp/glitch.zImage
reading ramdisk from /tmp/initrd.img
Writing Boot Image /tmp/boot.img
Glitching your device...
about to run program [/tmp/busybox] with 4 args
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.952729 seconds, 16.8MB/s
Finished!
script result was [Finished!]
Installer Sucessfull (Status 0)
End at : Wed Nov 19 21:24:49 2014
- Could you please copy the /fstab.flo content from a ROM you got Glitch installed to for me?
Click to expand...
Click to collapse
Yes, of course. Here we go ... Note: I compared this fstab.flo with a version from a secondary ROM which has root. They are in fact identical!
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered,nomblk_io_submit,errors=panic wait,check
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,nomblk_io_submit,errors=panic wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-[CODE]
name/metadata
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 nosuid,nodev,barrier=1,data=ordered,nodelalloc wait
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/misc /misc emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl1 /sbl1 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl2 /sbl2 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl3 /sbl3 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/tz /tz emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/rpm /rpm emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/aboot /aboot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl2b /sbl2b emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl3b /sbl3b emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/tzb /tzb emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/rpmb /rpmb emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/abootb /abootb emmc defaults defaults
[/CODE]
- Why to use "delete and inject" for secondary ROM instead of "classic" install ?
Click to expand...
Click to collapse
Since Tassadar's boot image was working for me this was the easiest way. Just extract boot.img from lrx21p_flo.zip and use "delete and inject" for exchanging the boot image. Note: While writing this post I verified what I found yesterday, i.e. after flashing GlitchKernel and SuperSU 2.19 I do not have root. Flashing SuperSU 2.23 enables root. Reflashing Glitch and 2.19 leads to no-root again.
Best regards,
tungdil
Additional Information
Hello TK-Glitch,
it's me again
I did some further "research" in my secondary "L- ROMs" (the one I created for providing the information above and the one that does have SuperSU 2.23 installed and has root). I had a more detailed look on the boot images. In both cases your kernel is installed. I pulled the boot images using adb and unpacked them using unpackbootimg and then also unpacked the ramdisk. Binary the two images are not identical since the Glitch kernel configuration was slightly different:
Code:
console=ttyHSL0,115200,n8 androidboot.hardware=flo user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 l2_opt=1 vdd_uv=1 max_oc0=1728000 max_oc1=1728000 max_oc2=1728000 max_oc3=1728000 min_clock=384000 abc
v.s.
Code:
console=ttyHSL0,115200,n8 androidboot.hardware=flo user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 l2_opt=3 vdd_uv=3 max_oc0=1890000 max_oc1=1890000 max_oc2=1890000 max_oc3=1890000 min_clock=162000 abc
but I could not see any difference in the RAMdisk and the other main components dspite the fact that SuperSU 2.19 was used in one case and 2.23 in the other.
[EDIT] After reading TK-Glitch's next Post I realized that I made a mitsake and picked a wrong boot image when trying to compare so the following is wrong:
Tassadar's boot image is, of course, very different. One thing that I saw (because I remembered that SuperSU 2.23 "...fixes a number of SELinux policy issues...") is the difference in selinux-version. In Tassadar's image I find:
Code:
Android/aosp_flo/flo:5.0/LRX21M/scott11042320:userdebug/test-key
while your selinux_version says:
Code:
google/razor/flo:5.0/LRX21P/1570855:user/dev-keys
[/EDIT]
Maybe I am wrong but I think my problem was caused by the combination of Tassadar's build of the ROM and the Glitch kernel and, I was just lucky that the latest Beta of SuperSU helped curing it.
Best regards,
tungdil
Latest glitch and lollipop stock
I can't unlock many times the screen I have enable the swipe options
@tungdil
Thank you for your patience and researches tungdil !
The files SuperSU 2.23 would modify are most likely init.rc and sepolicy I guess. These are the two only files Glitch is potentially patching in the extracted ramdisk(from the current boot.img) when using root settings (fstab.flo is for F2FS partition mounting). Glitch doesn't come with its own ramdisk to enhance compatibility and will instead extract the current one, patch it with the options you've selected then repack it with the Glitch zImage in a new boot.img that'll be flashed at the end of the Aroma installer script. The selinux_version you have came either with the rom's default kernel or the previous kernel you flashed, not from Glitch itself.
I did ask in my previous post what ROM you were using because I thought you weren't using the same one both as internal and secondary. I may be right in thinking they're not the same when I'm looking at your selinux_version files content if you didn't switch kernels. You know what you did anyway.
It could indeed very well be something in Tassadar's build or some ramdisk changes he made breaking my patches. I didn't test his rom thinking that after an AOSP built rom and the official Google image were both getting root for me after applying Glitch it would work for every other AOSP based Lollipop roms. I may have been wrong.
I'll check Tassadar's build and search for a fix. Thanks again tungdil !
Hi again, Tk-Glitch!
Thanks for your comments! I appreciate having the chance to learn something.
.. the selinux_version you have came either with the rom's default kernel or the previous kernel you flashed, not from Glitch itself.
Click to expand...
Click to collapse
Oh, I see! I should have had a closer look at your flashable zip. After doing so, and looking into what "I found" I had to realize I made a mistake in picking the wrong boot image for the analysis (I have multiple secondary ROM's installed) In fact the selinux_version is, of course, the same (google/razor/flo:5.0/LRX21P/1570855:user/dev-keys) before and after flashing Glitch kernel.
I did ask in my previous post what ROM you were using because I thought you weren't using the same one both as internal and secondary
Click to expand...
Click to collapse
They should be the same (as mentioned forget about selinux-version I guess it was just too late yesterday night).
I tried to explain how I installed the ROM in my first post: "... For both cases [secondary and primary ROM] I used Tassadar's build. For the latter [primary] I copied the installed secondary ROM to the primary slot [using TWRP] ...".
If there is anything else I could do to help let me know! I'd be more than happy.
Best regards,
tungdil
@tungdil
I can understand better now, thanks for the confirmation.
My english is pretty limited to be honest so I may be understanding things wrong sometimes. I can also feel that I'm not able to express fully what I'd like to from time to time. It can be another limiting factor in some cases where my explanations or questions could be unclear for someone speaking better than I am.
I didn't find the time yet to check for Tassadar's build so I'm not in need for more for now. I'll get back to you as soon as I've made some progress on the matter - even if it's just to keep you informed - as it could also help someone else.
Thank you for your support and dedication.
Have a nice day tungdil
W.O.W
Thank you for this kernel!! It turns my adreno 320 to adreno 330
I'm on Lollipop (stock,rooted) and I'm having ghost touches with the latest version of glitch installed. I had an older version installed when I was on PA 4.6 but I did not have this issue. Any solutions?
Hey @Tk-Glitch,
First of all i want to say thank you for this wonderful Kernel .
I'm using the r307 Glitch Kernel in combination with Stock 5.0.2 rooted Rom.
The perfomance ist just awesome, unfortunately the battery is draining to quick compare to stock Kernel.
I would to ask what setup you're running and which settings you use. With CPU 1700mhz and GPU 450mhz i hardly reach 4-5 hours Sot of normal web browsing. Could you or anybody recommend me your personel settings.
Thank you in advance .
pranauk said:
I'm on Lollipop (stock,rooted) and I'm having ghost touches with the latest version of glitch installed. I had an older version installed when I was on PA 4.6 but I did not have this issue. Any solutions?
Click to expand...
Click to collapse
Strange to say the least since you didn't have issues previsouly. I've seen ghost touches on a friend's N7 and the only true fix was unplugging and replugging the display cable on the motherboard. BTW, ghost touches are almost always linked to the bad manufacturing of the N7.
I don't have any myself, on both r306 and r307, but my tab was never affected.
pk-sanja said:
Hey @Tk-Glitch,
First of all i want to say thank you for this wonderful Kernel .
I'm using the r307 Glitch Kernel in combination with Stock 5.0.2 rooted Rom.
The perfomance ist just awesome, unfortunately the battery is draining to quick compare to stock Kernel.
I would to ask what setup you're running and which settings you use. With CPU 1700mhz and GPU 450mhz i hardly reach 4-5 hours Sot of normal web browsing. Could you or anybody recommend me your personel settings.
Thank you in advance .
Click to expand...
Click to collapse
My battery is lasting much longer since Lollipop, so you may want to check for wakelocks.
These days I'm using 1.7GHz CPU, 600MHz GPU, -75mV on each CPU step, -100mV on each GPU step, ondemand governor, Glitchy L2/cache OC, and S2W/DT2W disabled.
Hope it helps !
@Tk-Glitch
Thank you for your answer Tk-Glitch, i will check the wakelocks.
And thank you for sharing your setup,
i will test it in my device. May you share how much mw Volt you need for 1,7Ghz and how i undervolted -100mw on GPU in all steps?
pk-sanja said:
@Tk-Glitch
Thank you for your answer Tk-Glitch, i will check the wakelocks.
And thank you for sharing your setup,
i will test it in my device. May you share how much mw Volt you need for 1,7Ghz and how i undervolted -100mw on GPU in all steps?
Click to expand...
Click to collapse
Of course mate.
My CPU needs 1.025V for 1.7GHz (PVS 3). For the GPU, I did make the GPU undervolting selectable (for all steps at once) in Aroma. You can tweak the values in the glitch script (init.d) if needed.
@Tk-Glitch
I see very nice , mine does 1050mV in 1,7Ghz not much differenc. Ups my mistake i thought the GPU undervolting in Aroma Installer is behaving like the CPU undervolting, only for the lowest Frequenz.
Thank you very much for you time, at home i will do a full factory reset and flash your kernel of top with the settings.
Have a nice day Tk-Glitch.
@pk-sanja
My pleasure.
Have a nice day as well pk-sanja
Hola! There's little information or resources for this phone so far so I'm gonna give a summary of the ways to get root and install ROMs on the phone with a lot of links.
First you can install Magisk on the stock ROM using the Armor 6 method as described in this thread (via this post).
Secondly I built latest TWRP, download it here. I included my sloppy build for the Armor 7, and also the more proper Oppo RenoZ build that I slimmed down to fit into the 32MB recovery partition and confirmed it works. I don't know who made the Oppo ReonZ build, it's more complete but you have to switch from Chinese to English on init. I had to remove the SuperSU and unroot zips to slim it down. You might be able to remove some unused flash partitions and load bigger recovery images.
Via TWRP you can sideload magisk, SuperSU, gapps and whatever you wish on custom ROMs.
Thirdly you can load Phhusson's Quack Treble ROM (AOSP) or LineageOS, possibly many other custom GSIs too. Here's a list of known GSIs assembled by user phusson. These all come with the su binary pre-installed. The Android 9 (Pie) versions seem to work out of the box. The Android 10 (R) versions currently require that you run the following command from a PC during boot, otherwise bootup never finishes:
Code:
adb shell setprop debug.stagefright.ccodec 0
I'm told this has been fixed in the upstream code but it's not in the R releases yet. Additionally there are some screen artefacts on those builds which can be worked around by disabling the HW compositing feature in:
System -> Developer -> HW Accelerated Rendering -> Disable HW overlays
You may also want to disable the annoying "Wake-on-lift" feature in Display settings.
Pretty much everything works in those ROMs, battery life seems good, but the Armor 7 Camera features are not enabled in the stock Camera apps. I'm going to try to get the Camera app from the stock ROM copied and update this post with instructions.
The default firmware has the downside that it runs a service that basically kills all background processes and there are reports that it's hard to disable -- there's no such problem in the custom ROMs.
For the record, the official stock ROM is downloadable here (click EU or non-EU), for whenever you want to go back to the factory system or factory recovery (to remove TWRP). Remember you need to enable or disable dm-verity in the vbmeta partition, depending on which firmware you want to run. This is done by extracting the vbmeta.img file from the stock ROM linked above, rebooting into fastboot and running one of the following commands:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
or
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Also remember after flashing LineageOS (fastboot flash system lineage-17.1-20200607-UNOFFICIAL-treble_arm64_bvN.img), if you want GApps on the system, you should boot into TWRP and use ADB sideload to load the .zip downloaded from opengapps.org before doing the setup wizard on LineageOS for the first time.
Post here aboue whatever new ROMs and solutions you find for this phone.
Also quick info on how to modify the boot logo partition from Linux, there are already Windows tools for that (probably works for the Armor 7) but no info on how to do this from under Linux so here's how I flashed my own logo from my Ubuntu pc. Requires mono and Imagemagick installed.
1. Download and unzip that same Windows LogoBuilder utility for mediatek phones,
Code:
$ unzip ~/Downloads/LogoBuilder_v1.6.1.zip
$ cd LogoBuilder_v1.6
2. Extract the logo partition image from the phone or from the Armor 7 stock ROM package, in my case:
Code:
$ unzip ~/Downloads/GQ3083TF1_KSX90T_ulefone_EEA_20200327_V02\(EU\).zip X90T88C.GQU.Ulefone.EEA.HB.FHD.AYAZ.1225.V3.02/logo-verified.bin
3. Unpack the 40+ individual images from the logo partition using Windows/C# utility under mono:
Code:
$ mkdir unpacked
$ mono logo.exe unpack X90T88C.GQU.Ulefone.EEA.HB.FHD.AYAZ.1225.V3.02/logo-verified.bin unpacked
3. The bootloader splashscreen/bootlogo is now in unpacked/block1.dat and we need to convert it to a format that you can edit in Gimp or any other editor:
Code:
$ cp unpacked/block1.dat logo.rgba
$ convert -size 1080x2340 -depth 8 logo.rgba logo.png
4. Edit logo.png or replace it with a new PNG file. The file *must* be 1080x2340px in size and be a 24-bit RGB colors with alpha (transparency.)
5. Convert new logo back to .rgba. Use the command below and then check the size of the resulting new logo.rgba -- it must be exactly 10108800 bytes which is 1080 * 2340 * 4. If it's 7581600, or 1080 * 2340 * 3, that will mean you forgot to add the alpha channel to your png file (in Gimp, it's in Layer -> Transparency -> Add Alpha Channel).
Code:
$ convert logo.png logo.rgba
If the new file size is 10109312 instead, strip the 512 header using dd:
Code:
$ dd if=logo.rgba of=logo2.rgba bs=512 skip=1 # only if the file size was 10109312 instead of 10108800
6. re-pack the logo partition image:
Code:
$ cp logo.rgba unpacked/block1.dat # or logo2.rgba...
$ mono logo.exe pack unpacked logo-new.bin
The new img size is not exactly as the original img but it works nevertheless.
7. flash it over the logo partition, as root:
Code:
# fastboot flash logo logo-new.bin
A big thanks to you. I successfully installed LineageOS on my Ulenfone Armor 7
The biggest problem is this line to type on each reboot
Code:
adb shell setprop debug.stagefright.ccodec 0
atricault said:
A big thanks to you. I successfully installed LineageOS on my Ulenfone Armor 7
The biggest problem is this line to type on each reboot
Click to expand...
Click to collapse
Couldn't this be added to build.prop?
clewis.it said:
Couldn't this be added to build.prop?
Click to expand...
Click to collapse
Yeah, I think I added it to default.prop eventually, I'm back to the stock ROM for now so can't check. Try:
Code:
adb shell
su
mount -o remount,rw /
echo debug.stagefright.ccodec=0 >> /default.prop
I'm back to the stock ROM because I can't get the Camera app working on lineageos, I managed to extract the stock app and fix some missing class errors but I think it depends on all those mediatek services. Maybe there's an Android 10 stock ROM from some other device from which those could be copied...
balrog-kun said:
Yeah, I think I added it to default.prop eventually, I'm back to the stock ROM for now so can't check. Try:
Code:
adb shell
su
echo debug.stagefright.ccodec=0 >> /default.prop
I'm back to the stock ROM because I can't get the Camera app working on lineageos, I managed to extract the stock app and fix some missing class errors but I think it depends on all those mediatek services. Maybe there's an Android 10 stock ROM from some other device from which those could be copied...
Click to expand...
Click to collapse
I got this error :
/system/bin/sh: can't create /default.prop: Read-only file system
But I'll go back to stock ROM too, because of Camera and I don't have enought knowledges to try to solve the problem
Oh right I forgot, for future reference you need to remount the filesystem read-write before that last command:
mount -o remount,rw /
Adding this to the previous post.
balrog-kun said:
Oh right I forgot, for future reference you need to remount the filesystem read-write before that last command:
mount -o remount,rw /
Adding this to the previous post.
Click to expand...
Click to collapse
Sorry I'm back to stock ROM.
But before that I tried this line
Code:
mount -o rw, remount /
And got this error
Code:
mount: 'remount'->'/': No such file or directory
Do you fix the background process killer on stock ROM?
atricault said:
Code:
mount -o rw, remount /
And got this error
Code:
mount: 'remount'->'/': No such file or directory
Click to expand...
Click to collapse
That's gonna be because of the space between rw, and remount.
atricault said:
Do you fix the background process killer on stock ROM?
Click to expand...
Click to collapse
Honestly I haven't had this problem so far. I have Don't keep activities disabled in System->Developer Options->Apps but I think it was off by default. Maybe Standby apps also affects this?
I was recording a hike track in Strava today for a few hours, and I took pictures, made calls, googled, etc. while Strava was running.
balrog-kun said:
Secondly I built latest TWRP
Click to expand...
Click to collapse
Do you have any instructions on how to build TWRP for the armor phones? I would like try building one for the Armor 3W.
Camera works well in daylight (but not in the dark) on the latest Havoc-OS 3.6 20200613 arm64-ab. Screen artefacts still there though unless HW overlays is disabled.
clewis.it said:
Do you have any instructions on how to build TWRP for the armor phones? I would like try building one for the Armor 3W.
Click to expand...
Click to collapse
Not really, I roughly followed https://forum.xda-developers.com/showthread.php?t=1943625 and one or two other places. I used the omni "minimal" manifest which includes TWRP:
Code:
repo init -u git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-9.0
(the branch "twrp-9.0" is because the stock kernel is for Android 9, if Armor 3 comes with Android 8, use twrp-8.0)
Then I needed to create the "device tree" (apparently not related to Linux device trees...), I started with https://github.com/TeamWin/android_device_ulefone_Armor_6 and went about renaming files and updating all the values in all the files based on the values in build.prop / default.prop in the stock system.img. Also replaced prebuilt/kernel with the kernel from stock boot.img. Apparently using a prebuilt kernel is deprecated but it worked and I guess the build is faster.
I also replaced the init.*.rc files with the ones from the stock recovery.img but honestly I can't tell you exactly which files to use. I didn't exactly know what needs to go in which init.*.rc file and when they're called, and I didn't bother looking for documentation for that, but I did have to move some fragment between files to make adb work.
Another caveat was making sure the build system uses python 2 because apparently most scripts are not python 3-compatible.
CodeParadise said:
Camera works well in daylight (but not in the dark) on the latest Havoc-OS 3.6 20200613 arm64-ab. Screen artefacts still there though unless HW overlays is disabled.
Click to expand...
Click to collapse
Do you never get the "can't connect to camera" errors?
The main thing about the stock camera app is that you can be almost sure that you're getting the max available performance from the camera in terms of zoom, color, etc. I.e. it probably automatically switches to the 2x camera when you zoom in (no idea), there's the fast HDR mode, UHD mode, slow motion, etc.
With any 3rd party app my guess it's only using one of the rear cameras. With the stock app honestly I can't know for sure if/when it ever uses the aux rear cameras, I hope it does though. Honestly the 3-camera setup on this phone doesn't seem very useful but hopefully there's some logic behind it...
And BTW even on the stock ROM I'm unable to record in more than 30fps using HedgeCam 2 (OpenCamera). It looks like it detects the frame rates supported by the hardware (30, 60, 120) but it crashes when I start recording.
balrog-kun said:
Do you never get the "can't connect to camera" errors?
The main thing about the stock camera app is that you can be almost sure that you're getting the max available performance from the camera in terms of zoom, color, etc. I.e. it probably automatically switches to the 2x camera when you zoom in (no idea), there's the fast HDR mode, UHD mode, slow motion, etc.
With any 3rd party app my guess it's only using one of the rear cameras. With the stock app honestly I can't know for sure if/when it ever uses the aux rear cameras, I hope it does though. Honestly the 3-camera setup on this phone doesn't seem very useful but hopefully there's some logic behind it...
And BTW even on the stock ROM I'm unable to record in more than 30fps using HedgeCam 2 (OpenCamera). It looks like it detects the frame rates supported by the hardware (30, 60, 120) but it crashes when I start recording.
Click to expand...
Click to collapse
I do get those errors, more so after trying different camera apps. The GSI camera implementation on this phone certainly needs more work. I notified the phh GSI group on Telegram and hopeful newer GSI versions will begin to fix the issue but as you say, getting the full camera functions equivalent to the stock ROM camera may be a long stretch.
this version of twrp does not work with the armor 7 made my phone bootloop and I had to reflash stock recovery.
grenskul said:
this version of twrp does not work with the armor 7 made my phone bootloop and I had to reflash stock recovery.
Click to expand...
Click to collapse
Could be wrong vbmeta image, they work for me.
Anyone tired this with the Armor 7E ?
Hi,
I'm stuck in a pickle here and would much appreciate any guidance.
Firstly, I'm a bit of a noob. So please bear with me.
I managed to unlock my Armor 7 and I'm able to fastboot into it (I see the device appearing through the shell after typing 'fastboot devices').
I followed balrog-kun guidance and downloaded his/her modified TWRP, and even Oppo's one, and flashed firstly balrog's TWRP onto the phone, but that made my phone keep booting, get a message of 'Orange State - Your device has been unlocked and cannot be trusted. Your device will restart in 5 seconds', takes about 10 seconds, restarts, and the same thing keeps happening.
I then tried flashing Oppo's. The same thing keeps happening.
When I flash them, I use the following:
fastboot flash recovery recovery.img
EDIT: If I may add, I also tried:
fastboot boot recovery.img
and the same thing happens.
Update: I managed to get the stock recovery flashed back into the phone and it is back up and running. Now, how do I flash barlog's TWRP successfully without running into a boot loop?
Any guidance would be much appreciated.
Thank you.
grenskul said:
this version of twrp does not work with the armor 7 made my phone bootloop and I had to reflash stock recovery.
Click to expand...
Click to collapse
Hey grenskul, I think I'm facing the same issue. Can you please share where you got the stock recovery? Thanks.
Update: I managed to find it from Ulefone's website, flahsed it and the phone is back up. Thanks.
Further update: after reading towards the end of Balrog's first post, I got the vbmeta.img from the stock and flashed it using the first command from the same post. That made flashing balrog and Oppo's TWRPs smoothly - the phone doesn't get stuck in a bootloop anymore.
BUT, when I go into recovery, I still get the stock recovery and not TWRP....?
Any thoughts?
UPDATE: For some reason, I had to reflash the recovery a couple of times (!) - used the TWRP supplied by balrog and now I got TWRP working (thank you!).
By the way: In my journey I'm following this post to upgrading my Amror 7 from Android 9 to Android 10 using the supplied Lineage version (17.1), but I also found 18.1 from the same contributor (Andy).