Hi devs,
I've started to port CM11 4.4 to my beloved Original Padfone (A66).
The first step was to compile the kernel sources that ASUS made available (Kernel 3.4), which as far as I understand will work with KitKat.
Am I correct to assume this?
Also, if the kernel compiled correctly what will be the next steps to test it (flash) in my device? The bootloader is unlocked, but I'm still with the original recovery. I think I will have to flash CWM or simmilar, right?
Thanks!
rafatz said:
Hi devs,
I've started to port CM11 4.4 to my beloved Original Padfone (A66).
The first step was to compile the kernel sources that ASUS made available (Kernel 3.4), which as far as I understand will work with KitKat.
Am I correct to assume this?
Also, if the kernel compiled correctly what will be the next steps to test it (flash) in my device? The bootloader is unlocked, but I'm still with the original recovery. I think I will have to flash CWM or simmilar, right?
Thanks!
Click to expand...
Click to collapse
The 3.4 kernel should work with KitKat. In order to properly test any CM11 builds you'll have to compile Clockworkmod Recovery for your device first by pulling your stock recovery.img and then compiling Clockworkmod Recovery using that. Additionally to test your kernel the best way is to take the zimage that's produced from compiling the kernel and make a boot.img out of it and boot it using fastboot. Let me know if you still have questions I'll be happy to answer them.
Sent from my SCH-I535 using XDA Premium 4 mobile app
shimp208 said:
The 3.4 kernel should work with KitKat. In order to properly test any CM11 builds you'll have to compile Clockworkmod Recovery for your device first by pulling your stock recovery.img and then compiling Clockworkmod Recovery using that. Additionally to test your kernel the best way is to take the zimage that's produced from compiling the kernel and make a boot.img out of it and boot it using fastboot. Let me know if you still have questions I'll be happy to answer them.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've follow the XDA University guide for building CWM, at http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
But the second step is failing:
Step 2 : Now that the otatools are ready, we need to get a dump of our current boot.img. To do this, use ‘adb shell’ and launch this command
“ dump_image boot /sdcard/boot.img “
This command do not exist in my phone.
Do you have any tip on this?
Thanks in advance!
rafatz said:
I've follow the XDA University guide for building CWM, at http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
But the second step is failing:
Step 2 : Now that the otatools are ready, we need to get a dump of our current boot.img. To do this, use ‘adb shell’ and launch this command
“ dump_image boot /sdcard/boot.img “
This command do not exist in my phone.
Do you have any tip on this?
Thanks in advance!
Click to expand...
Click to collapse
You have a couple of options of obtaining your stock recovery image (It's better to use your stock recovery.img rather then boot.img when compiling recovery as the recovery.img has more information in it that will make process of building an actual working recovery image easier) the easiest way is to boot into stock recovery, wipe cache in recovery, then reboot the phone. Then from adb run the following command:
Code:
cat /cache/recovery/last_log
This should give you an output, if you read the logfile you will see that one of the partition blocks is called /recovery. Record the name of the recovery partition block and then run the following command:
Code:
su
cat /dev/block/{name=of-recovery-partition-block} > /mnt/sdcard/recovery.img
This will dump a copy of your stock recovery.img to your internal storage. That you can then use to continue in the CWMR compiling process. By all means if you still have questions let me know I'm here to help.
shimp208 said:
You have a couple of options of obtaining your stock recovery image (It's better to use your stock recovery.img rather then boot.img when compiling recovery as the recovery.img has more information in it that will make process of building an actual working recovery image easier) the easiest way is to boot into stock recovery, wipe cache in recovery, then reboot the phone. Then from adb run the following command:
Code:
cat /cache/recovery/last_log
This should give you an output, if you read the logfile you will see that one of the partition blocks is called /recovery. Record the name of the recovery partition block and then run the following command:
Code:
su
cat /dev/block/{name=of-recovery-partition-block} > /mnt/sdcard/recovery.img
This will dump a copy of your stock recovery.img to your internal storage. That you can then use to continue in the CWMR compiling process. By all means if you still have questions let me know I'm here to help.
Click to expand...
Click to collapse
OK, I was able to successfully compile CWMR, but when booting to recovery I only get a blank screen and the devices reboots to Android. Is there a way to find any information on the error?
I know that TWRP works in padfone, but I'm not sure if they are compatible.
rafatz said:
OK, I was able to successfully compile CWMR, but when booting to recovery I only get a blank screen and the devices reboots to Android. Is there a way to find any information on the error?
I know that TWRP works in padfone, but I'm not sure if they are compatible.
Click to expand...
Click to collapse
It's possible that something is wrong with your recovery's graphics. Try taking the zimage of the kernel sources you compiled and swapping that zimage with the one in your CWMR recovery.img (Replace the zimage in your CWMR .img with the one you obtained when compiling the kernel source from ASUS). You could also try compiling TWRP and seeing that results in the same problem there are times on devices TWRP has been working before CWMR was working properly.
shimp208 said:
It's possible that something is wrong with your recovery's graphics. Try taking the zimage of the kernel sources you compiled and swapping that zimage with the one in your CWMR recovery.img (Replace the zimage in your CWMR .img with the one you obtained when compiling the kernel source from ASUS). You could also try compiling TWRP and seeing that results in the same problem there are times on devices TWRP has been working before CWMR was working properly.
Click to expand...
Click to collapse
No way Simply not working
But TWRP is 100%
I've tested the original recovery back and it is perfect as well.
Only CWMR is not working
I've even used the builder tool without success.
I've followed this guide:
http://www.imajeenyus.com/computer/20130301_android_tablet/android/unpack_repack_recovery_image.html
and this
http://forum.xda-developers.com/showthread.php?t=1877807
Anyway, do you think that TWRP will work to flash my CM11 (if I ever build one)?
I think that the next problem is related on how to get the proprietary binaries from the phone to place in the vendor/asus/padfone folder.
rafatz said:
No way Simply not working
But TWRP is 100%
I've tested the original recovery back and it is perfect as well.
Only CWMR is not working
I've even used the builder tool without success.
I've followed this guide:
http://www.imajeenyus.com/computer/20130301_android_tablet/android/unpack_repack_recovery_image.html
and this
http://forum.xda-developers.com/showthread.php?t=1877807
Anyway, do you think that TWRP will work to flash my CM11 (if I ever build one)?
I think that the next problem is related on how to get the proprietary binaries from the phone to place in the vendor/asus/padfone folder.
Click to expand...
Click to collapse
The CWMR builder tool has been not working for a while now. If you were able to compile the latest version of TWRP and you said it was working 100% then that will be fine to test your CM11 test builds. For getting the vendor files I would take a look at this guide on the Cyanogenmod wiki regarding porting and pull vendor files. A extract-files.sh script for a pre-existing device such as the Sprint Galaxy Nexus is a decent place to start for getting an idea how to setup extract-files.sh.
shimp208 said:
The CWMR builder tool has been not working for a while now. If you were able to compile the latest version of TWRP and you said it was working 100% then that will be fine to test your CM11 test builds. For getting the vendor files I would take a look at this guide on the Cyanogenmod wiki regarding porting and pull vendor files. A extract-files.sh script for a pre-existing device such as the Sprint Galaxy Nexus is a decent place to start for getting an idea how to setup extract-files.sh.
Click to expand...
Click to collapse
Yes, TWRP is 100% working
I've checked the extract scripts but my main problem is to identify in the filesystem which files I should pull.
Anyway, I tried to use the "chipset" method and "guess" based on the system information which files/drivers I would need, but that was not very helpfull (http://specdevice.com/showspec.php?id=0429-3576-ffff-ffffa98be330).
Well, I'll continue my studies on this
rafatz said:
Yes, TWRP is 100% working
I've checked the extract scripts but my main problem is to identify in the filesystem which files I should pull.
Anyway, I tried to use the "chipset" method and "guess" based on the system information which files/drivers I would need, but that was not very helpfull (http://specdevice.com/showspec.php?id=0429-3576-ffff-ffffa98be330).
Well, I'll continue my studies on this
Click to expand...
Click to collapse
Another suggestion would be to take a look in the /vendor folder on your device to extract the proprietary files and use that as a starting point to build off. Then you could try and compile a test build using that. Studying other devices device tree's is like you said another way to gain hints about what to do for your own device.
shimp208 said:
Another suggestion would be to take a look in the /vendor folder on your device to extract the proprietary files and use that as a starting point to build off. Then you could try and compile a test build using that. Studying other devices device tree's is like you said another way to gain hints about what to do for your own device.
Click to expand...
Click to collapse
HURRAY!
This saved the day
https://www.codeaurora.org/cgit/qui...tree/proprietary-blobs.txt?h=aosp-new/idea133
It is not for Padfone, but it is close enough.
rafatz said:
HURRAY!
This saved the day
https://www.codeaurora.org/cgit/qui...tree/proprietary-blobs.txt?h=aosp-new/idea133
It is not for Padfone, but it is close enough.
Click to expand...
Click to collapse
Awesome! Glad you could find a very similar device, best of luck on your CM11 builds :good:.
shimp208 said:
Awesome! Glad you could find a very similar device, best of luck on your CM11 builds :good:.
Click to expand...
Click to collapse
After a few attempts I was able to finish a build for CM 10.2, but it will not boot
I found that maybe I did something wrong with the fstab.padfone, using the new standards with 5 settings instead of only 3.
Well, in order to eliminate these kind of problems, I will make a CM10.1 building, which still uses the old standards.
rafatz said:
After a few attempts I was able to finish a build for CM 10.2, but it will not boot
I found that maybe I did something wrong with the fstab.padfone, using the new standards with 5 settings instead of only 3.
Well, in order to eliminate these kind of problems, I will make a CM10.1 building, which still uses the old standards.
Click to expand...
Click to collapse
Does it not boot at all or does it get to the boot-animation at least? Did you try pulling a log to see if you could get any information on the problem? But best of luck on your building :good:.
shimp208 said:
Does it not boot at all or does it get to the boot-animation at least? Did you try pulling a log to see if you could get any information on the problem? But best of luck on your building :good:.
Click to expand...
Click to collapse
SO far I couldn't even flash the ROM
TWRP is build with name A66, and the ROM is based on padfone.
I tried to change it, but the build fails
I think that I need to continue my efforts to make a working CWMR. So far the issue is the same, I can build and flash the recovery, but it simply do not enter the recovery. I get a flash on the screen and the phone automatically reboots to enter android.
I wonder if there's any way to get logs or more information from this error, so I can at least start to understand why CWMR is not booting.
fastboot boot recovery.img fails as well.
Bad day
rafatz said:
SO far I couldn't even flash the ROM
TWRP is build with name A66, and the ROM is based on padfone.
I tried to change it, but the build fails
I think that I need to continue my efforts to make a working CWMR. So far the issue is the same, I can build and flash the recovery, but it simply do not enter the recovery. I get a flash on the screen and the phone automatically reboots to enter android.
I wonder if there's any way to get logs or more information from this error, so I can at least start to understand why CWMR is not booting.
fastboot boot recovery.img fails as well.
Bad day
Click to expand...
Click to collapse
To clarify the ROM fails to flash in recovery what is the error it gives you when it fails to flash? To get ADB working on your CWMR build so you can pull log information add these lines in the correct place to your init.rc file in your recovery ramdisk:
Code:
service adbd /sbin/adbd recovery
disabled
socket adbd stream 660 system system
# Always start adbd on userdebug and eng builds
on property:ro.debuggable=1
#write /sys/class/android_usb/android0/enable 1
#start adbd
setprop service.adb.root 1
# Restart adbd so it can run as root
on property:service.adb.root=1
write /sys/class/android_usb/android0/enable 0
restart adbd
write /sys/class/android_usb/android0/enable 1
shimp208 said:
To clarify the ROM fails to flash in recovery what is the error it gives you when it fails to flash? To get ADB working on your CWMR build so you can pull log information add these lines in the correct place to your init.rc file in your recovery ramdisk:
Code:
service adbd /sbin/adbd recovery
disabled
socket adbd stream 660 system system
# Always start adbd on userdebug and eng builds
on property:ro.debuggable=1
#write /sys/class/android_usb/android0/enable 1
#start adbd
setprop service.adb.root 1
# Restart adbd so it can run as root
on property:service.adb.root=1
write /sys/class/android_usb/android0/enable 0
restart adbd
write /sys/class/android_usb/android0/enable 1
Click to expand...
Click to collapse
Thanks man! I was able to get a working CWMR.
The GITHUB I created for the device is at:
https://github.com/rafatzbr/android_device_asus_A66
I was able to build CM10.1 to Padfone, but it simply wont boot
stucked in the initial screen (not the bootanimation).
Any help is much appreciated.
Thanks!
** UPDATE **
Still stucked in boot screen
Any ideas?
rafatz said:
** UPDATE **
Still stucked in boot screen
Any ideas?
Click to expand...
Click to collapse
The ROM build? If it's still stuck pull a log file and post the upload of the log here.
shimp208 said:
The ROM build? If it's still stuck pull a log file and post the upload of the log here.
Click to expand...
Click to collapse
Thanks!
The problems is that the device is not in a bootloop. It is stucked in the first screen (on nexus devices it's the first google screen).
How I can get any logs from there, and which logs I would need?
Related
NOTICE: I no longer have a copy of the recovery image since goo.im went down. If anyone still has it, feel free to post a link. I'll leave the instructions here. Also, I won't be updating this since I no longer have a TF201 and ROM development seems to have shifted to a modified bootloader, which requires a different recovery image anyway.
Original post:
Warning: You must be on the 4.1.1 Bootloader to use this. Androwook and other stock based ROMs supply their own recovery.
With 4.4 based ROMs starting to come to our tablet, and official TWRP not flashing them, I thought I'd take a crack at updating it. As some of you may know, attempting to flash a KitKat ROM using the current version of TWRP fails, resulting in a "set_metadata_recursive" error. This updated version, based on the OmniROM fork of TWRP, fixes that.
Latest Version: 2.7.0.0-Voyager2k_v1.2
Instructions:
1.(Highly Recommended) Enable NVFlash if you haven't already. Check here for details.
2. Make sure you are on the 4.1.1 Jellybean Bootloader. If you are already running ParanoidAndroid or CyanogenMod, you're fine.
3. Download the recovery image here. The latest file is recovery1.2.img. EDIT: Links are broken. See above
4. You can use the same instructions that are on the TWRP page, but for convenience, I'll add them here. You have two options:
A. Fastboot. Boot the tablet into fastboot and use "fastboot -i 0x0b05 flash recovery recoveryX.X.img" (no quotes, replace X.X with whatever numbers are in the filename) from your computer to flash the recovery.B. Flash from terminal within the tablet. Open a terminal emulator within android and type "su" (no quotes) to get root access. Then type "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4" (no quotes, replace X.X with whatever numbers are in the filename) to flash the recovery and reboot normally. This is critical, as the recovery won't flash until the system has rebooted normally.
If successful, the version number should read: "2.7.0.0-Voyager2k-vX.X" (X.X being my revision number)
Known Issues:
1. /system/media doesn't get backed up for some reason. Restoring backups works, but you won't have sounds or a boot animation. (I think this is fixed in the newest version, but I'm waiting on other reports before I remove this item)
Ususal disclaimer: I am not responsible if this messes up your tablet in any way.
Credits:
TWRP for making the recovery
Built from the OmniROM fork. Source is here.
Changelog:
Version 1.1 - 2/19/2014
Added support for the dock keyboard
Fixed /system/media not backing up properly
Synced with latest OmniROM recovery sources
Version 1.2 - 3/25/2014
Updated to TWRP version 2.7.0.0
A little cleanup behind the scenes
one more.
Works Great! Flashed without problems via fastboot :victory:
Thank You!
Now I just need an awesome 4.4. ROM to flash :fingers-crossed:
works also with the second instruction over the tablet
Excellent news
I tried through the Terminal but despite no error was presented it didn't worked. The recovery presented was the old CWM. After flashing through fastboot the new recovery popped out like a charm
Thanks.
thanks, it works through terminal. jut make sure to be root (su) and adjust the path of the recovery image
Sent from my EPAD using Tapatalk
thanks! This rec works and I have flashed cm11. Terminal works. U should insert "su" first
Sent from my GT-N7102 using Tapatalk
To use the second method you need to run su command first before using dd
Sent from my TF300T on OmniROM (4.4.2) using Tapatalk 4
Terminal
Just would like to ditto.
The process worked in the terminal on the device.
Thank you for this!
Bug report!
BUG REPORT!
There is a BUG in this version of TWRP:
It does not make any backup folder named media!
For example /system/media.
As result after recovery the folder /system has no this subfolder media and correspondingly missing boot animation and system sounds.
Dasdranamin said:
BUG REPORT!
There is a BUG in this version of TWRP:
It does not make any backup folder named media!
For example /system/media.
As result after recovery the folder /system has no this subfolder media and correspondingly missing boot animation and system sounds.
Click to expand...
Click to collapse
Thanks for the report. I'll look in to it.
Cyrozo said:
Excellent news
I tried through the Terminal but despite no error was presented it didn't worked. The recovery presented was the old CWM. After flashing through fastboot the new recovery popped out like a charm
Thanks.
Click to expand...
Click to collapse
Are you sure you placed the new "recovery.img" in the root directory of the sdcard? Won't work if the file is anywhere else.
Note 3 4.4.2
Does it work on note 3 with 4.4.2??
SAMERKAD said:
Does it work on note 3 with 4.4.2??
Click to expand...
Click to collapse
Nope, check your devices fora for compatible recoveries.
Bastaerd said:
Nope, check your devices fora for compatible recoveries.
Click to expand...
Click to collapse
can i bring back backed up data with other recovery?
SAMERKAD said:
can i bring back backed up data with other recovery?
Click to expand...
Click to collapse
You should be able to do so. Anyways, this isn't the recovery for your device.
Bastaerd said:
You should be able to do so. Anyways, this isn't the recovery for your device.
Click to expand...
Click to collapse
yeah i know, but i had it on 4.3 and backed up data via TWRP
now im on 4.4.2 with CWM Recovery...
want to restore my System data
Thankss
What bootloader is this compatible with? Does it work with the TF300T Bootloader? I am guessing not but someone from the Androwook thread might try it and that will not be good.
Seeing this is for kk support/ROMs, why would a wookie fastboot this?
Thank you Voyager for the ongoing support for the prime!
Sent from my VS980 4G using Tapatalk
NOTICE
As i no longer own this tab, i will no longer be providing support for it.
As devhost is slowly and surely deleting my files, i have moved them
to androidfilehost https://www.androidfilehost.com/?w=files&flid=23547
As androidfilehost does not delete files, these recoveries will remain hosted indefinitely.
m
Update 1 Uploaded - Choose v2
i am doing a new build as i may have missed setting support for extended attributes.
will update shortly.
v2 is up - link updated
changed default security module to selinux and modified source /bootable/recovery-cm/updater/install.c
as follows:
<cm11 source dir>/bootable/recovery-cm/updater/install.c
in line 586 (under the function ParsePermArgs(int argc, char** args):
654:- parsed.has_capabilities = true;
654:+ parsed.has_capabilities = false;
mainly for testing. still functional as before.
on v2
okay,
i have been using v2 quite a lot since i posted it and it works pretty solidly.
A major note- to flash supersu update zip you must use most recent version from chainfire's site.
The adb experience is good provided you remember to mount data and system.
I will be getting to Philz Advanced after a little more practice with building.
Right now my attempt in th recovery arena will be to get aromafm built and working.
Both versions of my cwm build will remain posted.
m
edit- uploaded v2 Alien - i know, it's goofy but it looks pretty cool. =)
Philz Adv CWM 6.55.0 - CWM 6.0.5.0
sorted.
screen shots
Philz Adv CWM - Update August 2, 2014
Before all other things, @Hazou , Dude you rock !!
Unending thanks to @Phil3759 for making your source available.
okay so this is Philz Advanced Touch for GT-P5210 [fixed, no lag].
If anyone needs CWM rebuilt let me know.
This time i have released it in a flashable zip [CWM]. I wil be pulling the clunky one [Philz]
And with that, I think I am done with recovery building for now. Enjoy
the name of the file is PhilzAdvCWM-6_55_0-gtp-5210.zip. See OP for link.
m
AROMAFM
yup, aromafm :victory:
okay so,
issues are lag, resolution and possibly a ram related crash, in which event, force reboot [will return you to recovery] and then reboot normally.
i'm working on it. NOTE- enabling automount seems to reduce occurence of crash/hang.
in terminal ~#whoami
returns ~#uid0 :good:
busybox :good:
see OP for link. this is an initial offering and requires work.
thanks a million times to @amarullz for making his source available
thanks to @Hazou as ever :good:
please pm me to report bugs and issues. enjoy !
m
TWRP v2.7.1.0 for GT-P5210
Reserved for TWRP
Will be attemtping to improve/fix/sort terminal.
Didn't want to be unfair to TWRP users.
Will update.
m
Thanks @Siberian Tiger :good:
Okay so, TWRP is up. See OP for link.
I am still looking for what i need to know to make the terminal in twrp a less-suck experience.
No lag and, I am actually starting to like TWRP alot. I have tested on my tab, backup/recovery are good. aromafm installs and runs well. adb seems to be in order. I did trim the fstab leaving system, data/internal storage, cache, recovery, boot and external storage.
If other variants need different setup please let me know.
As always please do not post thank-you's. Bugs and issues only.
thank you for reading
m
Notes
I did not generate any new or additional code.
All sources are already available - CWM, PHILZ, TWRP, AROMAFM
However the patches applied to cm11 build environment are
@Hazou , infinitely thankable :good:
https://github.com/HazouPH/android_system_core/commit/54cf228097d58713d71a13a6c79794bfa373eab0
https://github.com/HazouPH/android_device_motorola_smi/blob/jellybean/patch/cwm_0001.patch
m
if i try to flash philz it keep saying my device is santos103g and not santos10wifi
i have 100% sure gt-p5210 it is on the back of the tablet
damian312 said:
if i try to flash philz it keep saying my device is santos103g and not santos10wifi
i have 100% sure gt-p5210 it is on the back of the tablet
Click to expand...
Click to collapse
hi,
you need to follow this thread from first post, hear me out,
you must first download, extract to /sdcard and dd write cwm 6.0.5.0 [recovery.img] with the following terminal command
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11
from that point you can flash philz normally. the assert in the updater script is correct. it calls to your
/system/build.prop
and verifies whether or not you have the correct device. The issue is with your process and your build prop.
if you are unable to resolve the issue, you may extract the recovery.img from the zip and write it in the same
fashion as cwm 6.0.5.0 to your recovery block.
m
Thanks @stamatis
moonbutt74 said:
hi,
you need to follow this thread from first post, hear me out,
you must first download, extract to /sdcard and dd write cwm 6.0.5.0 [recovery.img] with the following terminal command
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11
from that point you can flash philz normally. the assert in the updater script is correct. it calls to your
/system/build.prop
and verifies whether or not you have the correct device. The issue is with your process and your build prop.
if you are unable to resolve the issue, you may extract the recovery.img from the zip and write it in the same
fashion as cwm 6.0.5.0 to your recovery block.
m
Thanks @stamatis
Click to expand...
Click to collapse
Awsome. With the instruction spelled out to me, even I might be able to have a go att it.
BIG thanx for your patients with us end-users (that have no talent for coding )
/H
hmm...
Hey friend I have a question . How can we install twrp on the new 4.4.2 stock rom? I can't install it.it says some errors and reboots
FurFur_ said:
Hey friend I have a question . How can we install twrp on the new 4.4.2 stock rom? I can't install it.it says some errors and reboots
Click to expand...
Click to collapse
Read the OP completely.
moonbutt74 said:
Read the OP completely.
Click to expand...
Click to collapse
Of Course! thaaanks~~
moonbutt74 said:
dev-host link - http://d-h.st/users/moonbutt74/?fld_id=38524#files TO RECOVERIES
dev-host link - http://d-h.st/users/moonbutt74/?fld_id=38598#files TO AROMAFM - W.I.P.
NOTE- This is not a flashable/odin-able file. You must dd write to /dev/block/mmcblk0p11 [or appropriate recovery block]
Click to expand...
Click to collapse
"PhilzAdvCWM-6_55_0-gtP-5210.zip
Description: good 2 go kitkat kapable cwm flashable thanks Hazou @xda"
Is it flashable or not?
Edit it was not flashable, don't know why download states that.
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11
"/dev/block/mmcblk0p11 Cannot open for write: Permission denied"
kgyirhj said:
"PhilzAdvCWM-6_55_0-gtP-5210.zip
Description: good 2 go kitkat kapable cwm flashable thanks Hazou @xda"
Is it flashable or not?
Edit it was not flashable, don't know why download states that.
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11
"/dev/block/mmcblk0p11 Cannot open for write: Permission denied"
Click to expand...
Click to collapse
You need to execute the command as the root user, or what we call the superuser. Execute: su root. And then you are good to go.
Thanks @Divine_Madcat
m
moonbutt74 said:
hi,
you need to follow this thread from first post, hear me out,
you must first download, extract to /sdcard and dd write cwm 6.0.5.0 [recovery.img] with the following terminal command
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11
from that point you can flash philz normally. the assert in the updater script is correct. it calls to your
/system/build.prop
and verifies whether or not you have the correct device. The issue is with your process and your build prop.
if you are unable to resolve the issue, you may extract the recovery.img from the zip and write it in the same
fashion as cwm 6.0.5.0 to your recovery block.
m
Thanks @stamatis
Click to expand...
Click to collapse
Okay i would like to flash this but because i currently have twrp installed and am not a fan cause it won't let me install 4.4. However i have know idea what this means. Can i flash this cwm using twrp?
Made TWRP Friendly
@jyerly
Okay so, this is Philz Recovery with the assert removed to be Old TWRP Friendly
TESTED, WORKING. I don't do it any other way.
devhost link - http://d-h.st/SSY
m :good:
HI Moonbutt74,
sorry for my maby silly question, but always just flashed via ODIN, CW; TWRP on my SGSII.....the Tab3 is differnet here and seems I have no clue .
I have rooted my Tab via the Root.zip and use the CWM from DutchDanny, still on stock firmware (see my sig).
I'd like to update to one of your new recoveries and go with Restl3ss Pimpdroid....but have no clue from terminal command.
Is there any hint how I execute the command you posted in OP?
Thanks for your kind help,
GeScha
Hi everybody!
On our 4pda.ru forum we are struggling with this phone in two ways- rootin it and unlocking in order to update manually to 2.0 and even 2.2; and other way- working android (already have beta rom which is exact copy of rom from another alcatel 6014x which runs android and similar to our Fire E 6015x).
if there are any enthusiasts about android, i can translate the guide for you and share the needed files and programs. Almost everything works except sim-card(when there is no one- phone asks to insert it, when there is one- phone says its not registered) but we are working on it
i came over a https://www.soeren-hentzschel.at/mo...ch-verteilt-firefox-os-2-0-und-firefox-hello/ that states that in Germany some people already received 2.0 update on their Fire E. Here arises my question- are here people who own updated Fire E? I mean update to 2.0.
If there are ones, would you be so kind to make a copy of your rom for our little development? I can provide you with guides and software on how to do it.
I can post guides for making this an android phone.
Hi my dear russian brother - greetings from Germany.
I do have an updated 6015x device to FFOS2.0 and I could dump the rom for U. Just gimme links to the needed info. My russian is not one of my strength, but I think I can manage it - I'm a bulgarian after all.
hej, i also have a 6015X (fire e) with firefox os 2.0 running
tell me how to make a rom which i can send to you
root
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
cybervitexud said:
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
Click to expand...
Click to collapse
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
dermartinac said:
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
Click to expand...
Click to collapse
I wonder how do you use it though, can you build it on its own? The B2G by Mozilla still hasn't got an option for this device.
Svinka said:
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Click to expand...
Click to collapse
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
sybiam said:
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
Click to expand...
Click to collapse
Flashing the recovery image works though, then sideloading the SU image works from clock work mode recovery.
Ok, here's some news. I built a boot image that enables adb as root. All you need is to flash it on the boot partition and reboot the phone. I made a few changes to the boot image.
default.prop
Code:
ro.secure = 0
ro.debuggable = 1
To flash:
Code:
fastboot flash boot boot3.img
and replaced /sbin/adbd by an adbd built with "ALLOW_ADBD_ROOT". (I used the sources fetched using b2g repo).
Cool thing..wish I am able
Sent from my SM-G7102 using XDA Free mobile app
Hi. Update firefox os 3.0?
lirondeespaña said:
Hi. Update firefox os 3.0?
Click to expand...
Click to collapse
As far as i know even Firefox OS 2.2 is not officially released yet.
There are only pre Versions.
Has anybody else troubles with FFOS 2.0 on the Alcatel Fire E?
The phone sometimes hangs completely while it was sleeping. (Can´t wake up or even call the phone)
Only if i press the start button for some seconds the phone starts again.
I hope someone builds a FFOS 2.2 Rom for the Fire E --> Copy and paste :good:
How can I switch this piece of **** called smartphone to bootloader mode?
Softbricked 6015x
Hey guys,
I got stuck with creating the boot.img and figured out that the backed up one doesn't work.
Does anybody have a working boot.img for the 6015x, NOT the 6014x?
I tried also getting the venezuelian one, but those TLDs are not reachable anymore - all gone.
The custom boot images from the russian 4pda forum are also not working.
I currently have only access to ADB, the TWRP recovery mod (temporarily) and fastboot, so I need a fastboot working image.
The Mobile Upgrade Q / TCL Updater / QDST distribution updater is Windows only - and crawling the binaries for URLs is a dead-end. The tool also requires
a fully booted OS, so it's pretty much the dumbest update tool out there and not practical to use. As I don't have Windows, the imgc files for the eMMC flashing tool are also a dead-end.
I really need only the boot.img file.
I really need only the boot.img file.
Click to expand...
Click to collapse
Did you try my boot img?
sybiam said:
Did you try my boot img?
Click to expand...
Click to collapse
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
cmartensms said:
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
Click to expand...
Click to collapse
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
sybiam said:
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
Click to expand...
Click to collapse
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
cmartensms said:
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
Click to expand...
Click to collapse
That's weird, my custom boot works on my own phone. 6015x, it's a russian phone. Firmware revision: 01005, hardware revision 01, platform version: 28. Firefox OS 1.3.0.0 .
I guess, if you had a newer version of Firefox, there could be something wrong with the boot image.
Hi everyone. I recently bought an Alcatel 1t 7 (8067) tablet, 1Gb ram, 16Gb rom, just wifi (no 4G), mt6580 processor, android oreo go edition; a very simple and cheap tablet, but it seemed me a very nice one, because is slim and lightweight; worhty of root access, but also a custom recovery. I prefer TWRP recovery because it's more organized... ¡Anyway!... So I got down to work, but at first, as I didn't know how to backup all firmware, and when I learned how to do it and did it (esentially I could "tame" sp flash tools, hehe), I had already lost my original recovery file. Is needless to say that TWRP recovery, as far as I know, isn't available for this model, so I needed to port it, but as at first, I didn't know how to back it up, I overwritten it with other recoveries that didn't work. I mean, at this time, the tablet is working but is without recovery tool. I'm not going to talk about root access, because I already could get it, by using magisk manager, but I need my recovery image file, back; both to reinstall it and port it to TWRP.
So finally, if anyone has this stock recovery file, the full stock rom for it, or even better the ported TWRP for this tablet, please share it to me.
Thanks in advance for your attention.
just boot into android, stock recovery will be repaired from /system/recovery-from-boot.p automatically
aIecxs said:
just boot into android, stock recovery will be repaired from /system/recovery-from-boot.p automatically
Click to expand...
Click to collapse
Thank you for reply. Ok, I booted android. I have enabled usb debugging so, when android booted, I connected it to adb, and opened "adb reboot recovery" command, to be sure that android would reboot into that mode; but it didn't, it just rebooted several times on boot screen, and when it "got tired" of rebooting, it booted into android. Didn't boot into recovery, so I guess, It didn't repair it.
PS: I was looking for that file "recovery-from-boot.p" on that path, and there isn't such file, i can't find it.
on older devices it is /system/etc/install-recovery.sh or something, it's maybe disabled if your device isn't completely stock anymore?
you can port TWRP with kernel from boot. you can use this TWRP as base
aIecxs said:
on older devices it is /system/etc/install-recovery.sh or something, it's maybe disabled if your device isn't completely stock anymore?
Click to expand...
Click to collapse
¿Must that file have the same size that the original recovery image? Because the only file named recovery that i can find on that path is named "recovery-resource.dat" and its size is 807kb, and as I have seen before, is that recovery images have several Mb of size.
aIecxs said:
you can port TWRP with kernel from boot. you can use this TWRP as base
Click to expand...
Click to collapse
Two questions about it; as far as I can remember twrp image must be compatible not only for the same chipset, but the same screen resolution ¿Am I right? Also, this tablet is 600x1024 px, or 1024x 600 on landscape mode. All TWRP that I have installed on former machines, worked on portrait mode, so I wonder miself ¿Could TWRP also work on landscape mode?
/system/etc/recovery-resource.dat "generates a binary patch that creates the recovery image starting with the boot image. (Most of the space in these images is just the kernel, which is identical for the two," so the resulting patch is a executable file with smaller file size than the actual recovery.) It's just few lines of code.
https://android.googlesource.com/platform/build/+/b32161a^!/
TWRP is available in landscape mode. you can read more about here
[GUIDE]Porting TWRP without source
I don't think touchscreen will work at all, so resolution doesn't matter. you can use TWRP from cmd line
https://twrp.me/faq/openrecoveryscript.html
aIecxs said:
/system/etc/recovery-resource.dat "generates a binary patch that creates the recovery image starting with the boot image. (Most of the space in these images is just the kernel, which is identical for the two," so the resulting patch is a executable file with smaller file size than the actual recovery.) It's just few lines of code.
https://android.googlesource.com/platform/build/+/b32161a^!/
Click to expand...
Click to collapse
Ok... I can find that file on my tablet, but I'm not so skilled android user, as for rebuild recovery from that file or even port TRWP from that file, so ¿Is there an easy way to do it ( or at least, comprehensible for middle skilled android users) ? ¿How? (and supposedly this machine is easy to port and root, they say on internet. I also have a huawei y7 2018 for rooting, that seems harder to root. But that's a another (my next) struggle in here, hehe)
aIecxs said:
TWRP is available in landscape mode. you can read more about here
[GUIDE]Porting TWRP without source
Click to expand...
Click to collapse
Another question. ¿Are those programs who claim to help to port TWRP with just some clicks, reliable? (for instance TWRP porter for mediatek)
aIecxs said:
I don't think touchscreen will work at all, so resolution doesn't matter. you can use TWRP from cmd line
https://twrp.me/faq/openrecoveryscript.html
Click to expand...
Click to collapse
All the TWRP recoveries that i have ported before, have had a working touchscreen, but as I understand, resolution requirement is not only for touch calibration, but for correct displaying of TWRP GUI (that all buttons and options fit on the screen), Now I've read that new versions of TWRP adjust automatically to any screen resolution, ¿Is that right?
dump boot.img off device. you can use SP Flash Tool read back. download base TWRP and unpack with AIK. replace kernel and see what happens. if TWRP booted with black screen try to enter adb shell. get partition list from adb shell. create proper twrp.fstab and flash again. you should have functional TWRP now even without working GUI.
if touchscreen is disabled it might possible to hexpatch kernel with ghidra like I did for mine.
HCU-client needs 4 credits for Huawei.
I may reply in new thread.
aIecxs said:
dump boot.img off device. you can use SP Flash Tool read back. download base TWRP and unpack with AIK. replace kernel and see what happens. if TWRP booted with black screen try to enter adb shell. get partition list from adb shell. create proper twrp.fstab and flash again. you should have functional TWRP now even without working GUI.
if touchscreen is disabled it might possible to hexpatch kernel with ghidra like I did for mine.
Click to expand...
Click to collapse
¡No, man! If TWRP porting is kinda hard having the stock recovery image, without it, is a brain smashing task (or at least for me). I mean, I really don't understand well, how to port twrp starting only with boot.img, I mean, without recovery img. I've saw tutorials about the use of carliv kitchen (windows version), and seems easy, but all tutorials are made with stock recovery.img available, not with boot.img. So, what can I do there?
as I said. replace kernel with that from boot.img and see what happens? the generic base TWRP actually is recovery.img already, so you might lucky and it works? trial + error...
aIecxs said:
as I said. replace kernel with that from boot.img and see what happens? the generic base TWRP actually is recovery.img already, so you might lucky and it works? trial + error...
Click to expand...
Click to collapse
I saw a tutorial about. It said that I must to unpack stock recovery and twrp recovery, and replace some files of unpacked twrp recovery, with respective unpacked stock recovery files, and edit some files on twrp unpacked folder, and finally repack it.
Until that point, I assume that it should work, I mean, having stock recovery. But I did that, but using boot.img, I renamed all boot resources, to recovery, for instance, boot.imgkernel to recovery.imgkernel; and replaced it, repacked it, and reflashed it, but nothing happened, I mean, it didn`t want to boot into recovery. It`s interesting to "experiment", but I`m gonna try to find its original stock recovery, to at least get it back.
Hello!
I would like some help, alcatel 1T7" 8086 no4g I likely bricked it. There's nothing else than a black screen. The tablet doesn't react to anything. The computer finds it as unknown USB tool. No visibilty is shown. What can i do with it,for it to work? Or should i just put it in the trash?
Thank you for the reply.
** UNOFFICIAL A-TEAM RELEASE**
*******Testing ONLY*******
**testing has only been done on GN2200 July patch device but should atleast boot into twrp on other sec patch on GN2200 devices***
***Let us know if not***
*****HEED THE WARNING OF IMPENDING APOCALYPSE, DOOM, BOOTLOOPS , BRIMSTONE AND FIRE, AND ALSO TWRP ******
***NOBODY IS RESPONSIBLE FOR WHAT YOU DO WITH THIS EXCEPT YOU***
***DO NOT BUILD AND FLASH THIS UNLESS YOU KNOW EXACTLY WHAT YOUR DOING***
****DONT DO ANYTHING I SAY, I CANT BE HELD RESPONSIBLE FOR WHAT I SAY OR DO*****
**THIS IS AN ** UNOFICIAL RELEASE ** SO DONT GO CRYING TO ANYONE THAT YOU MADE YOURSELF AN EXPENSIVE PAPERWEIGHT IF YOU USE ANYTHING IN THIS POST***
********* THE RESPNSIBILITY LIES SOLELY UPON YOU***
***FLASHING IN CURRENT STATE DOES NOT BOOT INTO SYSTEM****
****READ EVERYTHING BEFORE YOU DO ANYTHING******
******ONLY POSTING THIS FOR DEV PURPOSES*******
******Huge THANKS to PizzaG for this!!!******
***Thanks to Eduardo as well for his contributions, he may still be working on his own release***
Am posting this with a copy/paste i posted in telegram group..
We need people with the knowledge/skills and experience to help get this TWRP finished AND/OR work out the bugs.
GitHub - PizzaG/recovery_device_oneplus_OP515AL1
Contribute to PizzaG/recovery_device_oneplus_OP515AL1 development by creating an account on GitHub.
github.com
*this is not ready for release but the source is here for anyone who can build upon it*
touch is not working
you cant fastboot boot on this device so DO NOT flash this to your device without a backup of your stock/current boot image
issues we are having is no touch, can't mount /data, and so far cant boot into system with the recovery installed so if you want to use it youll need to flash this to boot, use it for whatever and then flash stock boot back, if your magisk patched youll need to flash the backup of that patched boot image you made before flashing this in order to get back into your system....... i have sort of found a slight work around for having to keep flashing the boot partitions until someone can get this to boot by placing my current boot image on an sdcard along with the twrp, flash the twrp to the active boot partition, boot into twrp, install image and install your backed up boot image to the current slot, then go back to advanced and install twrp to ramdisk and select and install the twrp image to the ramdisk, if your magisk patched you need to flash magisk zip right now, you can adb shell into twrp to pull a copy of this boot image if you want and i have flashed my "twrp-ramdisk installed boot image" on the Slot that my system is on and stock/backup boot image to inactive slot because its the only way to boot back to system for now without reflashing the stock(backed up) boot image back to the slot. and reboot into bootloader, change active and reboot and your back into your system.... when you need twrp you can set active to the other slot, it will bootloop once into bootloader and choose recovery to get back to twrp... when done reboot to bootloader and set active back to the other slot and reboot into system.............otg mouse works, adb works, mtp works, some work has been done on the touch but thats still not working yet, everything seems to be mounting except data............. big shout out to PizzaG for this
***this is a very round-about way to get a currently buggy twrp on the device but if you have a usb-c adapter and mouse you can navigate twrp....***
PizzaG doesnt have the device and has spent more time than anyone could possibly ask someone to spend on this for free... I dont have the skills required yet to really work on this. I have tested as much as possible and here it is for those who can build and work on it. i dont recommend releasing in its current form because im sure alot of people will be complaining and bricking their devices. if you can build it im sure you can work on it and should have the skills to atleast recover and have the sense to make backups first.......
Thanks again to everyone who has already donated the valuable time working on this for us and to everyone who will follow and build upon this!
You can find the telegram group for our device here:
You can find the A-Team in telegram
Also FYI in case you missed the post about our kernel source, it can be found here:
GitHub - OnePlusOSS/android_kernel_msm-5.4_oneplus_sm6375 at oneplus/sm6375_r_12.0.1_oneplus_nord_n20_5g
Contribute to OnePlusOSS/android_kernel_msm-5.4_oneplus_sm6375 development by creating an account on GitHub.
github.com
If anyone with experience building twrp and especially for OnePlus devices needs a tester or any files from the device hit me up on telegram @PsYk0n4uT2 and I will do my best to provide whatever you need and test builds along with providing logs.
heres a compiled boot image from the above tree as of 10/02/2022.
**remeber it DOES NOT boot to system, this is twrp only, not installed into recovery ramdisk yet. so BACKUP YOUR STOCK(current) boot image FIRST**** you will have to flash your stock(current) boot image back to boot back into your system. you can sort of get around this by above mentioned method BUT here it is for the GN2200 anyways. working on my July patched device and my May patched device so it should work for other GN2200 sec patches too...
***BACKUP BACKUP BACKUP*****
also cant change active slot from twrp, must reboot to bootloader to change active slot
Heres TWRP installed to ramdisk on a july patched boot image. does not boot to system but since it doesnt you should still be able to use this on any patch for testing purposes.....
You can backup your boot image and flash your current boot image to inactive slot and flash this to active slot by selecting recovery from bootloader after it loops once.... use twrp then go back to bootloader and change active and reboot to get back into your system.
**BACKUP YOUR CURRENT BOOT IMAGE****
***DOES NOT BOOT TO SYSTEM**
***YOU WILL NEED YOUR CURRENT BOOT IMAGE TO BOOT YOUR SYSTEM< YOU SHOULD ALREADY HAVE A BACKUP OF YOUR STOCK IMAGE IN THE CASE THAT YOU ARE MAGISK PATCHED ALREADY< KEEP A COPY OF BOTH IN CASE YOU DECIDE TO WIPE DATA< YOU WILL NOT BOOT BACK INTO YOUR SYSTEM WITH A MAGISK PATCHED BOOT IMAGE IF YOU WIPE DATA*******
if someone can get their system to boot after installing the TWRP from post 4 or their own build after personal edits please post here how you were able to achieve the install and maintain booting into system..
currently twrp indicates that path to /mnt could not be found and cant mount /data .. i think if someone could fix this maybe some progress could be made
ScarletWizard said:
I wonder if TWRP will work for devices with a serial number defeicy
Click to expand...
Click to collapse
halfway working on mine, just isnt finished yet, we need someone who knows alot more about this than i do. another dev is working on twrp but needs a device. the serial wont affect anything else other than the oneplus care app and getting the unlock token..... other than that u have full functionality.... the one posted above needs ALOT of work to finish. no touch yet but it could work for SOME things....
I know C/C++ at a decent level, however; I don't have much experience with low level stuff (especially dealing with bootloaders and other specific proprietary android kernel stuff). If there is anything that needs testing, I am down for it since this is just a secondary phone for me and I won't be too upset if it explodes.
I'm going to attempt this
[ SOLUTION ] [ MTK ] to Fix Touch not Working on TWRP / Philz Due to Kernel Disabled Touch.
In this tutorial, i'm going to show how i managed to patch kernel to enable touch in recovery TWRP / Philz. WARNING : This worked fo...
factopea.blogspot.com
It's written for mtk device but might have similar enough instructions to port for qcom kernel,
But I believe this is what is needed to get the TWRP touch going
Is the trwp.fstab using the right version? Both have different
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,inlinecrypt,reserve_root=32768,resgid=1065,fsync_mode=nobarrier latemount,wait,resize,check,formattable,fileencryption=aes-256-xts:aes-256-cts:v2+inlinecrypt_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,quota,reservedsize=128M,checkpoint=fs
Try this instead in twrp.fstab
Code:
/data f2fs /dev/block/bootdevice/by-name/userdata flags=fileencryption=ice:aes-256-cts;wrappedkey;keydirectory=/metadata/vold/metadata_encryption
Techted89 said:
Is the trwp.fstab using the right version? Both have different
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,inlinecrypt,reserve_root=32768,resgid=1065,fsync_mode=nobarrier latemount,wait,resize,check,formattable,fileencryption=aes-256-xts:aes-256-cts:v2+inlinecrypt_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,quota,reservedsize=128M,checkpoint=fs
Try this instead in twrp.fstab
Code:
/data f2fs /dev/block/bootdevice/by-name/userdata flags=fileencryption=ice:aes-256-cts;wrappedkey;keydirectory=/metadata/vold/metadata_encryption
Click to expand...
Click to collapse
i just unpacked the twrp image with AIK and made the suggested edits and repacked, reflashed, same...... another person is working on twrp and has gotten much of the fstab corrected in their build but their keeping their source closed til they get it ready for release and is still very far from being finished with it and doesnt have much time to work on it right now so we are just kinda stuck waiting on someone that knows what their doing to help get this going. the other person has touch working on theirs so i know its possible i just dont know how long it will be before we see a beta even
Techted89 said:
Is the trwp.fstab using the right version? Both have different
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,inlinecrypt,reserve_root=32768,resgid=1065,fsync_mode=nobarrier latemount,wait,resize,check,formattable,fileencryption=aes-256-xts:aes-256-cts:v2+inlinecrypt_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,quota,reservedsize=128M,checkpoint=fs
Try this instead in twrp.fstab
Code:
/data f2fs /dev/block/bootdevice/by-name/userdata flags=fileencryption=ice:aes-256-cts;wrappedkey;keydirectory=/metadata/vold/metadata_encryption
Click to expand...
Click to collapse
also i see a recovery.fstab instead of twrp.fstab in /system/etc. is this what your referring to?
You need both from what iv read ,. TWRP.flags is a module that rewrites the stab at a certain point which may be the reason it's not compiling but I will post. Recovery.fstab is supposed to be a copy paste from the boot.img and gives the general mount partitions locations,. TWRP.fstab is mounted using the same partitions but different format/flag structure to be available to TWRP .
Techted89 said:
You need both from what iv read ,. TWRP.flags is a module that rewrites the stab at a certain point which may be the reason it's not compiling but I will post. Recovery.fstab is supposed to be a copy paste from the boot.img and gives the general mount partitions locations,. TWRP.fstab is mounted using the same partitions but different format/flag structure to be available to TWRP .
Click to expand...
Click to collapse
Interesting article above. Were you able to get that to work? I know it says MTK but seems like mechanism should be the same, or atleast I would assume anyways that the function would be very similar in the case of a flag. Was told you needed to use original kernel but then I couldn't get that to boot period. I'm out of my area of knowledge at this point but always willing to learn.
Also I tried messing around a little with the f stab and TWRP flags I was told that TWRP flags is pretty much the same as the twrp.fstab... also this build needs to have something added to the drivers I do believe that this is somehow related to USB touch it is a goodix gt9886 touch panel using the Samsung 9886 drivers. Maybe the init's need some help here as well.
I have the programming knowwledge that TWRP would require, but have not as of yet created one as my devices were typically readily complete before-hand. Once my device is back up, and running I am going to boot into Ubuntu and give it a go.
I need some excuse to have learned assembly x86, c, c++, Java, Python, and rust and have been eyeing learning scripting so it could be a fun side project assuming it is still incomplete as of the moment?
Is it normal for manufacturers to use components from other's in their builds? The kernel posted seemed to indicate at least a couple Samsung files included.
Well C is a guarantee possibly some C++ as well and definitely some sh scripting if you know rust and know how to attach it to C well enough that could add more possibilities I would imagine. The recovery is from my understanding in the boot image Android Image Kitchen would help you see it unmodified if that is the case.
I found a unofficial TWRP that flashes to the boot partition, and works pretty damn well, id have to say! I am not an experienced developer, I just like to flash around on my phone in my spare time.. Anyways here y'all go:
I am down while I got partitions backed up to the cloud.