Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
To take a screen shot, just slide left
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
HTC Desire X (protou)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Another Dev here! Good job!
xpirt
Is this official release? Or chances of getting official support? Will be testing it later on.
prototype-U said:
Is this official release? Or chances of getting official support? Will be testing it later on.
Click to expand...
Click to collapse
Sure, it is official. Just untested for your device, until now
Look in main thread link and supported devices list to get an idea
This thread is meant to give specific support for this device and sort bugs when reported
When reporting bugs, please:
- give a detailed description how to reproduce it
- Advanced / "Report Error" and attach here the log
- eventually, if phone unresponsive: adb pull /tmp/recovery.log
xpirt said:
Another Dev here! Good job!
xpirt
Click to expand...
Click to collapse
:good::good::good:
As soon as someone test it working (at least booting and not bricking your phone ), I will remove the red warning. That's meant to keep noobs away until it is tested
I tihnk as we can't flash a new recovery through recovery (due to S-On), it would be more practical to load up the recovery.img directly, so we can flash it through fastboot
dansou901 said:
I tihnk as we can't flash a new recovery through recovery (due to S-On), it would be more practical to load up the recovery.img directly, so we can flash it through fastboot
Click to expand...
Click to collapse
Good to know
Next updates will be only recovery.img renamed like the zip
For now, just extract the recovery.img from the zip and flash it
First testing report: Recovery is booting, aromafm works. Nothing else tested so far...
---------- Post added at 09:57 PM ---------- Previous post was at 09:47 PM ----------
Further testing: Would be nice to have the opportunity to mount the sdcard so it can be accessed via USB (like UMS in TWRP). Is this possible?
dansou901 said:
First testing report: Recovery is booting, aromafm works. Nothing else tested so far...
---------- Post added at 09:57 PM ---------- Previous post was at 09:47 PM ----------
Further testing: Would be nice to have the opportunity to mount the sdcard so it can be accessed via USB (like UMS in TWRP). Is this possible?
Click to expand...
Click to collapse
As it is based on CWM, I believe you can: mounts and storage>all the way down>mount USB storage.
Sent from my awesome fridge
dansou901 said:
First testing report: Recovery is booting, aromafm works. Nothing else tested so far...
---------- Post added at 09:57 PM ---------- Previous post was at 09:47 PM ----------
Further testing: Would be nice to have the opportunity to mount the sdcard so it can be accessed via USB (like UMS in TWRP). Is this possible?
Click to expand...
Click to collapse
Thanks for the feedback :good:
Did you try the menu: Mounts and Storage / Mount USB Storage?
After boot, you have to wait about 1mn for this to activate and before trying the USB mount storage
Phil3759 said:
Thanks for the feedback :good:
Did you try the menu: Mounts and Storage / Mount USB Storage?
After boot, you have to wait about 1mn for this to activate and before trying the USB mount storage
Click to expand...
Click to collapse
It's working... must have missed that. A second thing: Is it possible to remove the haptic feedback? For me, it's just annoying that the phone is vibrating each time...
dansou901 said:
It's working... must have missed that. A second thing: Is it possible to remove the haptic feedback? For me, it's just annoying that the phone is vibrating each time...
Click to expand...
Click to collapse
Start by browsing a bit the new features please
There is a lot to discover in PhilZ Settings menu
Vibrator and a lot more are there
Read the main thread also (link in op) + features + Guide to set up
Thanks again and report any issue
Will do tomorrow... Thanks for this great recovery!
Saw your recovery for the Nexus 7, but I never tried it... Will try this today, but is it for jb hboot or for ics?
Sent from my HTC Desire X using Tapatalk HD
Hi OP,
Just thinking if i can contribute in some way.
Desire X 1.24 hboot (ics) and 1.25 hboot (jb), has different mount points and sizes. If you need to make a CWM for ICS and JB desire x users, then you can use recovery.fstab and BoardConfig.mk sizes from my github linked below:
https://github.com/ProtoU/device_protou_recovery
Branch: "twrp" for ICS stuff
Branch: "twrp-jb" for JB stuff.
Glad to help.
Regards
Yasir
EDIT: Maybe this commit will clarify everything:
https://github.com/ProtoU/device_protou_recovery/commit/eba386989c92f656c247c4d2942f64cf16e74eb8
neXus PRIME said:
Hi OP,
Just thinking if i can contribute in some way.
Desire X 1.24 hboot (ics) and 1.25 hboot (jb), has different mount points and sizes. If you need to make a CWM for ICS and JB desire x users, then you can use recovery.fstab and BoardConfig.mk sizes from my github linked below:
https://github.com/ProtoU/device_protou_recovery
Branch: "twrp" for ICS stuff
Branch: "twrp-jb" for JB stuff.
Glad to help.
Regards
Yasir
EDIT: Maybe this commit will clarify everything:
https://github.com/ProtoU/device_protou_recovery/commit/eba386989c92f656c247c4d2942f64cf16e74eb8
Click to expand...
Click to collapse
Thank you
HTC is amazing me...
You mean, when updating from ics to jb you have to reformat phone partitions?
Anyway. The current recovery is based on cm-10.1 tree. However, I see that the recovery.fstab is same as the ics one you posted. Can anyone enlighten me for your device?
If i guess right, currently, cm10.1 will not run properly on new hboot?
If that's the case, it is important to let me know. I will rename my release tagged with hboot 1.24 and look to release another for 1.25
Sent from my GT-I9100 using Tapatalk 2
Phil3759 said:
Thank you
HTC is amazing me...
You mean, when updating from ics to jb you have to reformat phone partitions?
Anyway. The current recovery is based on cm-10.1 tree. However, I see that the recovery.fstab is same as the ics one you posted. Can anyone enlighten me for your device?
If i guess right, currently, cm10.1 will not run properly on new hboot?
If that's the case, it is important to let me know. I will rename my release tagged with hboot 1.24 and look to release another for 1.25
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
RECOVERY.FSTAB is DIFFERENT
# mount point fstype device [device2]
/recovery emmc /dev/block/mmcblk0p21
-/boot emmc /dev/block/mmcblk0p22 ICS
-/cache ext4 /dev/block/mmcblk0p27 ICS
-/data ext4 /dev/block/mmcblk0p26 ICS
+/boot emmc /dev/block/mmcblk0p27 JB
+/cache ext4 /dev/block/mmcblk0p26 JB
+/data ext4 /dev/block/mmcblk0p25 JB
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
-/system ext4 /dev/block/mmcblk0p25 ICS
+/system ext4 /dev/block/mmcblk0p24 JB
/misc emmc /dev/block/mmcblk0p17
/devlog ext4 /dev/block/mmcblk0p28
/emmc vfat /dev/block/mmcblk0p31
Well, that i saw...
But my question remains: does official cwm work on you jb 1.25?
If yes, then this one will.
The reason is simple. names can be implemented in kernel too. When we boot into recovery, it is kernel from recovery that will handle it
Maybe that's why recovery partition did not change!
So, can you enlighten me now and be more precise? Have no much time to start searching this from scratch
Sent from my GT-I9100 using Tapatalk 2
Phil3759 said:
Thank you
HTC is amazing me...
You mean, when updating from ics to jb you have to reformat phone partitions?
Anyway. The current recovery is based on cm-10.1 tree. However, I see that the recovery.fstab is same as the ics one you posted. Can anyone enlighten me for your device?
If i guess right, currently, cm10.1 will not run properly on new hboot?
If that's the case, it is important to let me know. I will rename my release tagged with hboot 1.24 and look to release another for 1.25
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Phil3759 said:
Well, that i saw...
But my question remains: does official cwm work on you jb 1.25?
If yes, then this one will.
The reason is simple. names can be implemented in kernel too. When we boot into recovery, it is kernel from recovery that will handle it
Maybe that's why recovery partition did not change!
So, can you enlighten me now and be more precise? Have no much time to start searching this from scratch
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Hy. No, the official recovery isn't working with JB, and yes, 1.25 hboot have new partition table (because JB kernel is bigger than the boot partition in 1.24 hboot.. I don't know that a simple resize why not enough, but we got it so), but you don't need to rebuild the recovery, just change the recovery.fstab to this: http://pastebin.com/t3QNcXh3 I use your recovery with this now. Great work! Thank you very much!
EDIT: I can upload the recovery with the JB recovery.fstab, if you want to save your time.
Related
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app
For downloads and instructions please visit our TWRP website and choose your device in the dropdown menu
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
ReverendJKR posted a great video on TWRP and Goo Manager working together.. Much more to come with this relationship
http://youtu.be/OA0S275XO3U
Oh man. Awesome!
Looks nice...looking forward to trying it out.
This looks very slick!
Sent from space
Can this recovery be used on any phone/tablet?
Sent from my Desire HD using xda premium
Super cool, thanks guys, I am now into Nook Color... HD2, AMAZE 4G...
Jainyankee1993 said:
Can this recovery be used on any phone/tablet?
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
We have a list of supported devices on the main twrp2 page: http://teamw.in/project/twrp2
So I see you got that stuck in recovery bug all worked out ehh? nice work.
eyeballer said:
TeamWin is proud to present TWRP 2.0 for Nook Color!!
Click to expand...
Click to collapse
Congrats TeamWin... this is supercool.
eyeballer one of the install steps is to push "kernel" to uRecImg but there is none? Am I missing something obvious?
hm, anyway to install this on an existing install?
Midnitte said:
hm, anyway to install this on an existing install?
Click to expand...
Click to collapse
Right from their page? Though idk what kernel they are talking about.
Download the above file. Connect your Nook Color to the PC via the USB cable. This assumes you have working ADB.
Execute the following:
adb shell busybox remount / -o rw,remount
adb shell busbbox mkdir /boot
adb shell busybox mount /dev/block/mmcblk0p1 /boot
adb push twrp-encore-2.0.0RC0.ub /boot/uRecRam <--- You can change uRecRam to uAltRam for alternate boot.
adb push kernel /boot/uRecImg
adb shell busybox umount /boot
Click to expand...
Click to collapse
RileyGrant said:
eyeballer one of the install steps is to push "kernel" to uRecImg but there is none? Am I missing something obvious?
Click to expand...
Click to collapse
Nburnes said:
Right from their page? Though idk what kernel they are talking about.
Click to expand...
Click to collapse
Sorry guys, the page is updated now with the kernel link. However, we just use a stock AOSP kernel so if you had CWM on emmc already you don't need to push the kernel since it's the same.
eyeballer said:
Sorry guys, the page is updated now with the kernel link. However, we just use a stock AOSP kernel so if you had CWM on emmc already you don't need to push the kernel since it's the same.
Click to expand...
Click to collapse
Actually what I thought, thanks for clarifying man .
Oooh, i look forward to trying this.
I was not having success installing this on emmc with the adb instructions probably because busybox was not set up the same way.
So I tried an different approach which was to use the NookColor UMS app to mount the boot partition so it shows up as a USB drive on PC called boot. I then just renamed uRecRam to uRecRamOld and copied in twrp-encore-2.0.0RC0.ub and renamed that to uRecRam. I didn't bother copying the kernel as per the previous posts.
Rebooting into recovery then brought up the TWRP recovery which looks very nice to use. Also works off the power up N after emmc recovery selected as expected.
Clockwork has given me good service but I think I'll be using this going forward.
bobtidey said:
I was not having success installing this on emmc with the adb instructions probably because busybox was not set up the same way.
So I tried an different approach which was to use the NookColor UMS app to mount the boot partition so it shows up as a USB drive on PC called boot. I then just renamed uRecRam to uRecRamOld and copied in twrp-encore-2.0.0RC0.ub and renamed that to uRecRam. I didn't bother copying the kernel as per the previous posts.
Rebooting into recovery then brought up the TWRP recovery which looks very nice to use. Also works off the power up N after emmc recovery selected as expected.
Clockwork has given me good service but I think I'll be using this going forward.
Click to expand...
Click to collapse
I had to do the same thing. Kept getting an error that "applet not found" for busybox in adb.
Thanks for the alternate method.
This is a much better implementation of our hardware in backup.
Thanks TeamWin.
Nburnes said:
Right from their page? Though idk what kernel they are talking about.
Click to expand...
Click to collapse
It wasn't there before! I swear! /thanks
Hm, is usb storage working for anyone?
The only thing I don't really care for is... and I know I am doing things in a unique way....
I have SASD with CM7 on it... verygreen's recovery as alt-boot and replaced CWM with TWRP as recovery mode on the uSD... when in TWRP and reboot... it boots stock on eMMC instead of a normal boot... it should do a normal boot (uSD first)
Ok guys, im awful at writing tutorials so i spent the past hour or so looking for the best one, as a few of you have pm'd me asking me to tell you guys how to build recoveries:
First, let's check out the CyanogenMod tree. The CyanogenMod repository contains Clockwork Recovery, which is part of a full Android build.
repo init -u git://github.com/CyanogenMod/android.git -b ics-release
repo sync
make -j4 otatools
Now, use dump_image or dd to dump your recovery or boot image from a running phone and copy it to your computer somewhere.
dump_image boot boot.img
To build Android from source for a new device, you need to set up a board config and its makefiles. This is generally a long and tedious process. Luckily, if you are only building recovery, it is a lot easier. From the root of your Android source directory (assuming you've run envsetup.sh), run the following (substituting names appropriately):
build/tools/device/mkvendor.sh device_manufacturer_name device_name /your/path/to/the/boot.img
You will receive the confirmation "Done!" if everything worked. The mkvendor.sh script will also have created the following directory in your Android source tree:
manufacturer_name/device_name
Now, type the following:
lunch full_device_name-eng
This will set the build system up to build for your new device. Open up the directory in a file explorer or IDE. You should have the following files: AndroidBoard.mk, AndroidProducts.mk, BoardConfig.mk, device_.mk, kernel, system.prop, recovery.fstab, and vendorsetup.sh.
The two files you are interested in are recovery.fstab and kernel. The kernel in that directory is the stock one that was extracted from the boot.img that was provided earlier. For the most part, recovery.fstab will work on most devices that have mtd, emmc, or otherwise named partitions. But if not, recovery.fstab will need to be tweaked to support mounts and their mount points. For example, if your /sdcard mount is /dev/block/mmcblk1p1, you would need the following lines in your BoardConfig.mk:
/sdcard vfat /dev/block/mmcblk1p1
Once the recovery.fstab has been properly setup, you can build the recovery using:
make -j4 recoveryimage
Your recovery can then be found at $OUT/recovery.img. If you are in need of building a fakeflash recovery, you will need to run the following to create the update.zip that hot replaces the recovery:
make -j4 recoveryzip
Once this is done, build, and tested, notify me, "koush", on Github and I can build official releases and add ROM Manager support!
Tip: Run "make clobber" between builds if you change the BoardConfig.mk, or the change will not get picked up.
Credits to Koush and his tutorial here
Hey Lloir was just checking your guide (I'm from the X8 scene). The funniest bit was "Notify...me, "koush"". I guess it's a typo. Anyways good guide.
I think you guys should look into getting Lloir a dev Desire X, he could do a lot more for you guys if he actually had the device
He has done some great work on the One V, including porting both CM9 and CM10, and he could do the same over here for you guys. I'm just dropping by to say that I vouch for Lloir He also has his own ROM in the works
Hopefully you can snag one of these devices soon Lloir, its always nice to get a fun device to play around on and to develop CM for
thanks for that endorsement Rohan, didn't expect that at all..
Lloir said:
thanks for that endorsement Rohan, didn't expect that at all..
Click to expand...
Click to collapse
I tried to compile a CWM based on gingerbread to get the earlier version of nandroid backups, but I just can't get it to work. Props and thanks again for making a CWM 6 for us, without it, we'd be nowhere
Thanks
Hi,
I managed to successfully built CWM using your guide.
It kinda works but i did not adjust recovery.fstab so i get errors saying failed to find cache partition to mount at /cache and some related to recovery.log.
Anyways, have you found the reason for the graphical glitch yet??
Thanks for the guide, it helped me to get started.
Got CWM working (still testing) for my rk3066 based tablet.
One thing I could not figure out - what to does one need to put into recovery.fstab to be able to mount a USB stick from CWM?
hi
Jin^eLD said:
Thanks for the guide, it helped me to get started.
Got CWM working (still testing) for my rk3066 based tablet.
One thing I could not figure out - what to does one need to put into recovery.fstab to be able to mount a USB stick from CWM?
Click to expand...
Click to collapse
On github, find a device tree with similar setup (a similar tab with option for mounting sd card) and use its fstab as reference. You'll also need to add BOARD_LUN_PATH or TARGET_LUN_FILE_PATH or something like that in the BoardConfig.mk of your device to make USB mounting work. Hope it helps.
Regards
Yasir
Yasir Javed Ansari said:
On github, find a device tree with similar setup (a similar tab with option for mounting sd card) and use its fstab as reference. You'll also need to add BOARD_LUN_PATH or TARGET_LUN_FILE_PATH or something like that in the BoardConfig.mk of your device to make USB mounting work. Hope it helps.
Regards
Yasir
Click to expand...
Click to collapse
Yasir, that was one of the things I noticed about the CM9 boardconfig : the paths you just mentioned need fixing
yes, i fixed it, then broke it again.... now figuring out what broke it
any ideea how i can build a touch recovery?
---------- Post added at 03:13 PM ---------- Previous post was at 03:11 PM ----------
neXus PRIME said:
Hi,
I managed to successfully built CWM using your guide.
It kinda works but i did not adjust recovery.fstab so i get errors saying failed to find cache partition to mount at /cache and some related to recovery.log.
Anyways, have you found the reason for the graphical glitch yet??
Click to expand...
Click to collapse
it it cannot find cache partition, the fstab is not correct
for the graphics, what are the bugs?
dany547 said:
any ideea how i can build a touch recovery?
---------- Post added at 03:13 PM ---------- Previous post was at 03:11 PM ----------
it it cannot find cache partition, the fstab is not correct
for the graphics, what are the bugs?
Click to expand...
Click to collapse
The method lloir posted is from koush, it needs some tweaking to work properly. Are you interested in building one yourself?
Compile from a new device
Hello,
I have a BLU Dash 3.5 and would like to build recovery.
I followed the steps in the guide and compilation errors did not return put the recovery did not work. The phone connects but gets the BLU logo on the screen.
The ADB recognizes the device.
The / system / data / cache / sdcard and / sd-ext is mounted correctly.
but the phone's screen does not pass soon.
I noticed that the ROM Manager can make and restore backups normally.
What am I doing wrong?
dump_image
i tried dump_image of boot boot terminal emulator says dump_image not found... i m running jelly bean 4.1.2 Samsung gt-s5282
Disclaimers :
#i am no-developer.im just a geek xperian..like many of u.i have created this ,my first ever thread typing on my mob keypad.so forgive me for short words and untidy post.
#links included below is noway related to me.respective links are included as per my findings to support the main moto of this thread.im thankfull to all of them who have tried to scratch on this through their posts and threads
#with all do respect,this thread is intended for our devs who can take this as pre-requsites for development.
#its a humble request for devs to put there effort on this.
#i request all xperians...from devs to simple users...whoever thinks this post worth discussing/developing,ur valueable words on this are highly appreciated.
#and please no trollers
Click to expand...
Click to collapse
I was doodling around today,i got my eyes poped-up wen i encounterd this
[samsung kernel flashing from cwm zip] -> http://forum.xda-developers.com/showthread.php?t=1301756 and this
[samsung general cwm kernel updater] ->http://forum.xda-developers.com/showthread.php?t=2132208
It all began then when i had to be far from my pc.then flashing new kernls for new custom roms began to be a problem.i presume their are a lot of users like me who cant access pc with as ease as many can.or simply to them who dont want to connect to pc just to flash kernels.if this would be success,just imagine how ease it would be?
But before starting to dream lets put together what i have come across till now.
Then i started digging more...on google & found this Tutorial [many devs might be intrestd &could help xperia users& start to run xperiment in our xperia ] --> http://www.modaco.com/topic/360180-howto-build-and-update-kernel-using-cwm/
In my findings i did aknowledge that this matter has/have/had been left out in corner just for some taboos/nerms like our xperia doesnt ship with normal recovery partition or like our custm recovry doesnt support some disk formats.
But whatsoever, i was little arosed by above things....then came a point whereafter i was too excited,wen i found this in our very xperia forum,xperia p forum ->> http://forum.xda-developers.com/showthread.php?t=2409021
Here the dev has created a zip with updatr script writng the kernel image,which stays inside the boot.img file .i couldnt dig more on this zip,as it was not so popular thread.i dont even know for it works or not,all i know is there are devs wanting to build,which is the main moto of this thread to let devs rethink the possibilty.
And yes, its a convincing reason for acceptance that our xperia doesnt have recovry partition like as other vendors device..and what we get as a recovry is hard coded to ramdisk.but like as ,A xperia s user,i too want to question an enlightning point on this...like using recovry fota partition,wich gets blokd and remains unusable aftr bootloader unlockd....why not use that...if not what about repartitioning empty space in device for recovry usage partition... http://forum.xda-developers.com/showthread.php?t=2163643
i too presume, even though we dont have that heavy intrnl space,but i guess we have enough for just a recovry partition.i guess so.correct me.
FOTA partition :
The FOTAKernel partition is used by Sony to do FOTA updates when updating the boot image. Unlocked devices can't take Sony FOTA updates so using this partition for storing the recovery ramdisk seems like a good idea. Unlocked users aren't able to use this partition anyway and the FOTAKernel partition is effectively the "recovery" partition on Sony devices.
Kernel changes : extract_elf_ramdisk setup in kernel
if some body wants a detailed info it can be found here (( **thanks to @officiallysonyrebel ,for the supportive conversation.above words are his ** )) -- http://forum.xda-developers.com/showpost.php?p=38640389&postcount=2
*** Summing up in total ***
It may b a horizon-touching dream..but as a geek user, like me,we dream of it.
Our charming devs can unlock bootloaders/root/giv us custm roms/give us a taste with unimaginable upgrowing ever, android version updates in roms/ ports.these all would also be impossible without their immense hardwork/researchs/xperimnts...i do aknowledge its a lot to ask for this.but with all do respect i wish devs get ther hands on it.
I predict most of xda-ians might already know abt all this,if yes do enlighten us more...ur comments and findings are most needed thing currently.
but truely saying i really dream of using cwm @ its maximum capacity,as of its easeness,isnt it? Different vendors like samsung,zte,etc evn can get rooted simply from cwm only...even most htc can. So why cant our xperia?is it coz of less devs in our xperia?i humbly request all devs to put some work on this so that me,like users who cant access pc with ease/dont want to,can easily get the work done.i also presume there r a lot of xperians,who want this.it cant be more handy than this...can it?
Hope in near future ,we xperians could getwith like these features as others.(rootng/flashng kernels from cwm).
Cheers!!
Xperia-lover!!
Most Xperia kernels are probably including CWM by default in the boot image. About a month ago Dees_Troy submitted some changes to the CyanogenMod repos that were accepted. Newer builds of CM include a special extract_elf_ramdisk utility that Dees_Troy wrote to read and extract a recovery ramdisk from the FOTAKernel partition instead of using the ramdisk that is included in the boot image. If the ramdisk in the FOTAKernel partition is a stock Sony ramdisk or not present, then the existing ramdisk in the boot image is used instead. This setup allows users to choose which recovery they want to keep installed.and whole a lot possibilites
but my major concern is if after unlocking bootloader FOTA partition gets blocked then how can we access it ..
so, first we have to acess FOTA partion then we can start dreaming on
officiallysonyrebel said:
Most Xperia kernels are probably including CWM by default in the boot image. About a month ago Dees_Troy submitted some changes to the CyanogenMod repos that were accepted. Newer builds of CM include a special extract_elf_ramdisk utility that Dees_Troy wrote to read and extract a recovery ramdisk from the FOTAKernel partition instead of using the ramdisk that is included in the boot image. If the ramdisk in the FOTAKernel partition is a stock Sony ramdisk or not present, then the existing ramdisk in the boot image is used instead. This setup allows users to choose which recovery they want to keep installed.and whole a lot possibilites
but my major concern is if after unlocking bootloader FOTA partition gets blocked then how can we access it ..
so, first we have to acess FOTA partion then we can start dreaming on
Click to expand...
Click to collapse
Ya i had read in the link u dirctd...i got to know that aftr unlockng bootloadr, that partition becomes unusuable/inaccessble.if that could be attained...then we can hope...isnt it?if i undrstud... wish devs could wave their magicstick soon.
Sent from my Xperia Ray using xda premium
I'm not sure but what about installing the recovery in /system?
Then we could write a script that detects if the recovery is installed in /system and it will choose the /system recovery over the kernel recovery while booting in recovery. Then we could try mounting the kernel partition and flash the boot.img. Then you flash a zip to remove the /system recovery and boot the new kernel
Not sure if that's possible, and don't have any idea how to do that. It was just an idea :good:
Sent from my Nexus 4 running Android 4.3
mihahn said:
I'm not sure but what about installing the recovery in /system?
Then we could write a script that detects if the recovery is installed in /system and it will choose the /system recovery over the kernel recovery while booting in recovery. Then we could try mounting the kernel partition and flash the boot.img. Then you flash a zip to remove the /system recovery and boot the new kernel
Not sure if that's possible, and don't have any idea how to do that. It was just an idea :good:
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
we can't do it in /system basicially we have to do this thing using only FOTA partition ..but our main concern is when we unlock our bootloaders that partition becomes inaccesible for us...
if we somehow gets access to FOTApatition then script will do work..
mihahn said:
I'm not sure but what about installing the recovery in /system?
Then we could write a script that detects if the recovery is installed in /system and it will choose the /system recovery over the kernel recovery while booting in recovery. Then we could try mounting the kernel partition and flash the boot.img. Then you flash a zip to remove the /system recovery and boot the new kernel
Not sure if that's possible, and don't have any idea how to do that. It was just an idea :good:
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Nope...You are still using the same kernel....just booting from different ramdisk when "installed in /system"...
We need to boot from a "second" kernel which can be used to flash the primary kernel ...Most other phone can boot into two kernels ,one stock and one recovery ,hence they can be used to flash kernels via recovery and use flash_image to install recovery in system ...
The problem is not where kernel/recovery is installed
The problem is how to boot the secondary kernel after installation ...It's very difficult to do that ...
lets say I dd the recovery.img to /mmcblk0p4 which is the fourth partition in an SD card
How do I instruct the bootloader to boot the device from /mmcblk0p4(or fota 1 or whatever) instead of /boot ...Thats the problem ...
Okay that's sad
But what about checking the partitions and if we know which blocks contain the Fota partition, could we try to mount it?
The problem would be how to tell the bootloader to boot the recovery or the 2nd kernel right?
Sent from my Nexus 4 running Android 4.3
Still the same problem ,how to instruct the bootloader to boot from fota 1 instead of /boot !!
Check that. It's exactly the same what we want to do, right?
Okay not exactly but we could use that too. But I'm not sure if he is able to install another kernel in the recovery...
Sent from my Nexus 4 running Android 4.3
mihahn said:
Check that. It's exactly the same what we want to do, right?
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Exactly ...we can use Multi partitioned SD card but thats extremely wishful thinking ...Also we need a lot of devices to brick :rofl:
Edit: He can use recovery to install kernels since ,the S1 boot boots LK from mmcblk0p4 (equivalent to /boot) which in turn gives an option to boot to fota1(which is recovery ) or the mmcblk016(which is the new place from which the system boots)
karandpr said:
Exactly ...we can use Multi partitioned SD card but thats extremely wishful thinking ...Also we need a lot of devices to brick :rofl:
Edit: He can use recovery to install kernels since ,the S1 boot boots LK from mmcblk0p4 (equivalent to /boot) which in turn gives an option to boot to fota1(which is recovery ) or the mmcblk016(which is the new place from which the system boots)
Click to expand...
Click to collapse
But later in OP they said it could be possible to reflash the stock rom to restore the partition table. So if we don't touch fastboot and flashmode partitions we should be able to recover the phone
I wrote the OP a PM if he could help us, let's see what happens
Sent from my Nexus 4 running Android 4.3
mihahn said:
But later in OP they said it could be possible to reflash the stock rom to restore the partition table. So if we don't touch fastboot and flashmode partitions we should be able to recover the phone
I wrote the OP a PM if he could help us, let's see what happens
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Unlike them we aren't modifying partitions ...we can use multi SD card but then we need to get SD card mounted by LK ...
There is a fundamental diffrence in two phones ,that they are using an emmc+ext4 and we are using a raw nand/yaffs device . i think the difference is night and day ...I dont think we can modify partitions easily ...
If however we get to mount SD card with LK then it's a different story ...
karandpr said:
Unlike them we aren't modifying partitions ...we can use multi SD card but then we need to get SD card mounted by LK ...
There is a fundamental diffrence in two phones ,that they are using an emmc+ext4 and we are using a raw nand/yaffs device . i think the difference is night and day ...I dont think we can modify partitions easily ...
If however we get to mount SD card with LK then it's a different story ...
Click to expand...
Click to collapse
So you mean we partition the sdcard and use a partition as the recovery partition?
I read about that with multiboot for xperia play (I guess). So maybe it could work for us too?
Sent from my Nexus 4 running Android 4.3
mihahn said:
So you mean we partition the sdcard and use a partition as the recovery partition?
I read about that with multiboot for xperia play (I guess). So maybe it could work for us too?
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
it's more logical(and safer) than editing nand ...AFAIK ,the partition setup of nand is included in kernel ...we can partition SD card to whatever we want and is more feasible
karandpr said:
it's more logical(and safer) than editing nand ...AFAIK ,the partition setup of nand is included in kernel ...we can partition SD card to whatever we want and is more feasible
Click to expand...
Click to collapse
Okay so how to start? What could we do to get the project to a higher level?
We have to find out how to get the bootloader to boot the 2nd kernel/recovery partition, right?
Sent from my Nexus 4 running Android 4.3
mihahn said:
Okay so how to start? What could we do to get the project to a higher level?
We have to find out how to get the bootloader to boot the 2nd kernel/recovery partition, right?
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Not really ....we can attempt/try/wish to do what the Xperia T folks did ,flash a bootloader at /boot instead of boot image ...
First thing we really need to know how actually LK works and can it be made to boot a kernel stored in a memory card ,
Editing a nand partition is currently out of question imo ,there is no free space for two kernels...
Edit : TBH ,We should look at HTC HD2 development more than anything since that section has "Android SD development" and Nand development ..
Even saying that we might just be scratching the surface :/
karandpr said:
Not really ....we can attempt/try/wish to do what the Xperia T folks did ,flash a bootloader at /boot instead of boot image ...
First thing we really need to know how actually LK works and can it be made to boot a kernel stored in a memory card ,
Editing a nand partition is currently out of question imo ,there is no free space for two kernels...
Edit : TBH ,We should look at HTC HD2 development more than anything since that section has "Android SD development" and Nand development ..
Even saying that we might just be scratching the surface :/
Click to expand...
Click to collapse
Yes the HTC HD2 has great development support and I already worked with a HD2 of a friend, but I have actually no idea how to use the method they are using for the HD2 for our devices. I think I will dive into it when I'm back at home from my vacation trip
Sent from my Nexus 4 running Android 4.3
maybe at deeper lok of possibiltes
i was searching on sd card booting nd found this
http://glasskeys.com/2011/06/27/how...-card-running-cyanogenmod-for-the-nook-color/
we need to make a seprate partition and kernel to use triggers to boot like we always do but it will call from SD card..
i think it may not work cause calling a kernel from SD card
officiallysonyrebel said:
maybe at deeper lok of possibiltes
i was searching on sd card booting nd found this
http://glasskeys.com/2011/06/27/how...-card-running-cyanogenmod-for-the-nook-color/
we need to make a seprate partition and kernel to use triggers to boot like we always do but it will call from SD card..
i think it may not work cause calling a kernel from SD card
Click to expand...
Click to collapse
Ehh...no it won't work ...the S1boot boots only from /boot...
The thread you cited is too old and worked probably due to an exploit in nook color ...
I think something like LK should work ,provided it waits for sd card to mount...
officiallysonyrebel said:
we can't do it in /system basicially we have to do this thing using only FOTA partition ..but our main concern is when we unlock our bootloaders that partition becomes inaccesible for us...
if we somehow gets access to FOTApatition then script will do work..
Click to expand...
Click to collapse
Correct me if i m wrong.its a noobish thought.
Can we access fota partition before bootloader is unlocked?if we can so what r we waiting for?
lets rehearse for the magick show,do what u have thought of.
(I presume when device is still locked....or if we revert back to locked state from unlocked... we could acces that partition.. .we get space for secondry kernel...if still quesn is letting bootloader know we want to boot from that,then again we r far behind)
Sent from my Xperia Ray using xda premium
Q&A for [Kernel] [12/1] FIRE-ICE [R14]
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] [12/1] FIRE-ICE [R14]. 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!
flashed ok on new factory image
5.0.1 stock / flashed cf autoroot/flashify/twrp ... flashed your rom/su/gapps/ set up the tablet and then flashed fire/ice. Tablet seems smooth and zippy . also of note previous to flashing your rom I also flashed the new factory image unencrypted if that matters. Thanks for your efforts on the rom.
fazbender said:
5.0.1 stock / flashed cf autoroot/flashify/twrp ... flashed your rom/su/gapps/ set up the tablet and then flashed fire/ice. Tablet seems smooth and zippy . also of note previous to flashing your rom I also flashed the new factory image unencrypted if that matters. Thanks for your efforts on the rom.
Click to expand...
Click to collapse
Cheers
ROM? What ROM
posted in the wrong thread : - / . meant to post in the lollipolosa rom thread. so in my previous post just swap out the word rom and insert kernel ,,,,hmmm still doesn't work .
lol - ty for your efforts with the kernel.
Just a quick heads up for those that don't know.
Since some of the terminal emulators don't seem to work and the one that I was able to get working doesn't allow copy and paste.
ROM toolbox pro, and I'm sure plenty of other apps allow you to make the value changes a lot easier and quicker than typing it all out.
jaben2 said:
Just a quick heads up for those that don't know.
Since some of the terminal emulators don't seem to work and the one that I was able to get working doesn't allow copy and paste.
ROM toolbox pro, and I'm sure plenty of other apps allow you to make the value changes a lot easier and quicker than typing it all out.
Click to expand...
Click to collapse
You need to copy it to clipboard
What is the "lite version of the Nexus 9"?
Sent from my Nexus 9 using Tapatalk
TriadX1 said:
What is the "lite version of the Nexus 9"?
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
The nexus 9 with data
Encryption still enabled
First off, I'd like to say that I love your kernel, as it has solved my main issue of overheating on my tablet.
My problem is that despite my best efforts, it still says that the tablet is encrypted. I'm currently on the latest Lollipopalooza running the latest Fire and Ice Kernel and the your modified TWRP recovery (I've tried both R1 and testR2). Doing a factory reset displays the message that it was successfully decrypted, but it still shows up as encrypted under Security settings. I'm also unable to perform a factory reset from adb because it says that the file system f2fs is not supported, and it shows this message despite the fact that I had formatted it back to ext4 through TWRP in a previous attempt to get things in working order. I've attached some screen shots of my security settings as well as the output from fstab.flounder and fstab.flounder64, both showing that it is encryptable. I apologize if this has been posted before, but for the life of me I was not able to find anything that could help. I appreciate any help
JackTheRipper1891 said:
First off, I'd like to say that I love your kernel, as it has solved my main issue of overheating on my tablet.
My problem is that despite my best efforts, it still says that the tablet is encrypted. I'm currently on the latest Lollipopalooza running the latest Fire and Ice Kernel and the your modified TWRP recovery (I've tried both R1 and testR2). Doing a factory reset displays the message that it was successfully decrypted, but it still shows up as encrypted under Security settings. I'm also unable to perform a factory reset from adb because it says that the file system f2fs is not supported, and it shows this message despite the fact that I had formatted it back to ext4 through TWRP in a previous attempt to get things in working order. I've attached some screen shots of my security settings as well as the output from fstab.flounder and fstab.flounder64, both showing that it is encryptable. I apologize if this has been posted before, but for the life of me I was not able to find anything that could help. I appreciate any help
Click to expand...
Click to collapse
Ok hmm
do this
in Recovery
enter adb
and do
cat /proc/version
Give me the output
You know what
screw it I make a flashable zip I would do the same thing
as a factory reset
USBhost said:
Ok hmm
do this
in Recovery
enter adb
and do
cat /proc/version
Give me the output
You know what
screw it I make a flashable zip I would do the same thing
as a factory reset
Click to expand...
Click to collapse
I appreciate the speedy response . Anyway, here is the output I got from recovery:
Code:
/ # cat /proc/version
I:Actual command is: 'cd "/" && cat /proc/version 2>&1'
Linux version 3.10.40[FIRE-ICE]RECOVERY ([email protected]) (gcc version 4.9.3 20141031 (prerelease) (Linaro GCC 4.9-2014.11) ) #1 SMP PREEMPT Fri Dec 5 20:58:57 PST 2014
JackTheRipper1891 said:
I appreciate the speedy response . Anyway, here is the output I got from recovery:
Code:
/ # cat /proc/version
I:Actual command is: 'cd "/" && cat /proc/version 2>&1'
Linux version 3.10.40[FIRE-ICE]RECOVERY ([email protected]) (gcc version 4.9.3 20141031 (prerelease) (Linaro GCC 4.9-2014.11) ) #1 SMP PREEMPT Fri Dec 5 20:58:57 PST 2014
Click to expand...
Click to collapse
Hmm dont know why it does not work
But any way
In about 5min the flashable zip will be ready
---------- Post added at 04:19 PM ---------- Previous post was at 03:56 PM ----------
ok just boot this recovery
like
fastboot boot test.img
then go to install
and move to /res
then you will see a zip called
factory reset.zip
then flash
note i have not tested it so its up to you
to flash it
https://drive.google.com/file/d/0B1cOHQ70J9vlNEN3bHpyVmkzb3M/view?usp=sharing
USBhost said:
Hmm dont know why it does not work
But any way
In about 5min the flashable zip will be ready
---------- Post added at 04:19 PM ---------- Previous post was at 03:56 PM ----------
ok just boot this recovery
like
fastboot boot test.img
then go to install
and move to /res
then you will see a zip called
factory reset.zip
then flash
note i have not tested it so its up to you
to flash it
Click to expand...
Click to collapse
I get an error
Code:
E:Mount: Unable to find partition for path '/res'
Error flashing zip '/res/factory reset.zip
JackTheRipper1891 said:
I get an error
Code:
E:Mount: Unable to find partition for path '/res'
Error flashing zip '/res/factory reset.zip
Click to expand...
Click to collapse
Hmm ok
1 sek
But in the mean time
manually format data to ext4
then back to f2fs
USBhost said:
Hmm ok
1 sek
But in the mean time
manually format data to ext4
then back to f2fs
Click to expand...
Click to collapse
Alright I'll give it a try when I return home in a few hours. Thank you for the help so far
JackTheRipper1891 said:
Alright I'll give it a try when I return home in a few hours. Thank you for the help so far
Click to expand...
Click to collapse
ok i feel so stupid now lol
just format data to f2fs
and your awesome
USBhost said:
ok i feel so stupid now lol
just format data to f2fs
and your awesome
Click to expand...
Click to collapse
I really don't want to be a bother, but it's still encrypted
I even tried manually changing it to ext4 and back again to f2fs, but no change
JackTheRipper1891 said:
I really don't want to be a bother, but it's still encrypted
I even tried manually changing it to ext4 and back again to f2fs, but no change
Click to expand...
Click to collapse
NP at all
Thats one stubborn nexus 9
You know what
I will edit my kernel to
Not support encrypted data
To see if that does it
Also can you give me the output of
su -c mount
USBhost said:
NP at all
Thats one stubborn nexus 9
You know what
I will edit my kernel to
Not support encrypted data
To see if that does it
Also can you give me the output of
su -c mount
Click to expand...
Click to collapse
Thanks for the help
Ive attached a screenshot of the output.
JackTheRipper1891 said:
Thanks for the help
Ive attached a screenshot of the output.
Click to expand...
Click to collapse
ok lets get this on the shell lol
ok download force format data.zip && boot.img
then move force format data.zip to /cache
then boot to recovery
then flash it
then format cache to f2fs
then boot to bootloader
then do
fastboot flash boot boot.img
then reboot
lets hope this does it lol
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
Direct device link
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Releases including and past 3.0.2-2 will work on both the L and M bootloader. The screen update issues plaguing unofficial 3.0.0 do not happen on these newer builds either. The OP is a little different from other TWRP threads because I don't want to keep updating the changelog and version numbers, but those can be found on the twrp homepage linked there. Enjoy.
Don't you love the smell of success in the morning? :laugh:
Finally, official status!
Nice! Nice! Nice!
Time for me to get some more roms out I guess
ro.product.device missing?
Not sure if I'm an isolated case for this, but I couldn't flash anything with this recovery because the updater script in ROMs would fail at ro.product.device, basically instead of shieldtablet being there it was blank. Went back to unofficial TWRP and now no problems.
Can anyone care to confirm if this is an issue with the official recovery image?
DaveTheRave said:
Not sure if I'm an isolated case for this, but I couldn't flash anything with this recovery because the updater script in ROMs would fail at ro.product.device, basically instead of shieldtablet being there it was blank. Went back to unofficial TWRP and now no problems.
Can anyone care to confirm if this is an issue with the official recovery image?
Click to expand...
Click to collapse
Yes, It is an issue I am working on.. :good:
Thx for the feedback, I will be posting a working version soon..
Thx Josh
EDIT:
Can I get some feedback on this, seems to be working as expected... :good:
Changelog:
Remove vendor init, cm is able to install now.
TWRP 2.8.7.1 DOWNLOAD LINK !!
Thx Josh
Hi Josh,
I'm trying to use the TWRP build on my new replacement device (received it last Monday). All I've done since unboxing is set a PIN and enable encryption. On booting, the /data partition isn't mounted, with the following error:
Code:
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details...
E:Unable to mount '/data'
...done
E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E:Unable to mount '/data'
MTP Enabled
I tried using the
Code:
adb shell twrp decrypt <pin>
command to decrypt using adb, but get the following response:
Code:
Attempting to decrypt data partition via command line.
E:No crypto support was compiled into this build.
This is with both the 2.8.7.0 official build, and the 2.8.7.1 build you reference above. Is it possible to get crypto support enabled please?
el3ctrik said:
Hi Josh,
I'm trying to use the TWRP build on my new replacement device (received it last Monday). All I've done since unboxing is set a PIN and enable encryption. On booting, the /data partition isn't mounted, with the following error:
Code:
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details...
E:Unable to mount '/data'
...done
E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E:Unable to mount '/data'
MTP Enabled
I tried using the
Code:
adb shell twrp decrypt <pin>
command to decrypt using adb, but get the following response:
Code:
Attempting to decrypt data partition via command line.
E:No crypto support was compiled into this build.
This is with both the 2.8.7.0 official build, and the 2.8.7.1 build you reference above. Is it possible to get crypto support enabled please?
Click to expand...
Click to collapse
Yes, this is a HUGE issue.....
I need to look at making this happen....
Thx Josh
EDIT:
Ok lets give this a go
Changelog:
Added decryption support.
TWRP 2.8.7.2 DOWNLOAD LINK !!
Thx Josh
The recovery does not work with the Nvidia shield k1 tablet. It cant write to the system partition.
philipp21897 said:
The recovery does not work with the Nvidia shield k1 tablet. It cant write to the system partition.
Click to expand...
Click to collapse
I am going to need just a bit more
Please run: adb pull /tmp/recovery.log
Upload or pastebin the output
Thx Josh
I'm a bit confused - how does this version relate (or not) to the version released in this previous thread?:
http://forum.xda-developers.com/showthread.php?t=2877117
Is it that this version has official status compared to the other (and is a newer version as well - 2.8.7.2 vs. 2..8.7.1 as of this post)?
Sent from my SHIELD Tablet using XDA Free mobile app
Correct. This is officially available on the TWRP website. The unofficial one should be almost exactly the same, but I don't think I've ever seen the device tree it was built from, so I can't say for certain.
@lj50036: I'm probably blind, but I can't find the source you're using for newer builds? Is it in a public repo somewhere? I'll want to pull the decryption support into the multirom twrp builds since I assume it's not enabled there either. Haven't tried, though.
An Droid said:
I'm a bit confused - how does this version relate (or not) to the version released in this previous thread?:
http://forum.xda-developers.com/showthread.php?t=2877117
Is it that this version has official status compared to the other (and is a newer version as well - 2.8.7.2 vs. 2..8.7.1 as of this post)?
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
I started with a similar device tree, but did some cleaning up
The device tree is linked in post #2
Thx Josh
Steel01 said:
Correct. This is officially available on the TWRP website. The unofficial one should be almost exactly the same, but I don't think I've ever seen the device tree it was built from, so I can't say for certain.
@lj50036: I'm probably blind, but I can't find the source you're using for newer builds? Is it in a public repo somewhere? I'll want to pull the decryption support into the multirom twrp builds since I assume it's not enabled there either. Haven't tried, though.
Click to expand...
Click to collapse
Dont forget to check gerrit...
http://gerrit.twrp.me/#/c/1115/
Thx Josh
lj50036 said:
Dont forget to check gerrit...
http://gerrit.twrp.me/#/c/1115/
Click to expand...
Click to collapse
Oh duh. Though I'm not certain why I had to register to even look at it? Meh.
*peruses changesets*
*is skeptical that it will work right*
I put the vendor init in to make all the recoveries and roms run across all models. And I think just about every rom uses it now. Without it... I suppose most popular roms will install since they assert as shieldtablet. But if someone has one specifically for wx_na_wf or such, that won't work. Do you know why the vendor init isn't running? It works on my multirom twrp builds built in an omni 5.1.1 tree. But if you really want to revert to a non-unified build, you should add the fingerprints back and probably split to three separate builds, one for each model.
Also, why is selinux being removed? Won't that break labeling on install? Is there a bug/missing rule I'm missing?
The decryption support seems simple enough, one line. I'll pull that in tomorrow and credit you and the review for it. Maybe I can finagle a formatted patch into my repo to keep authorship and all.
Steel01 said:
Oh duh. Though I'm not certain why I had to register to even look at it? Meh.
*peruses changesets*
*is skeptical that it will work right*
I put the vendor init in to make all the recoveries and roms run across all models. And I think just about every rom uses it now. Without it... I suppose most popular roms will install since they assert as shieldtablet. But if someone has one specifically for wx_na_wf or such, that won't work. Do you know why the vendor init isn't running? It works on my multirom twrp builds built in an omni 5.1.1 tree. But if you really want to revert to a non-unified build, you should add the fingerprints back and probably split to three separate builds, one for each model.
Also, why is selinux being removed? Won't that break labeling on install? Is there a bug/missing rule I'm missing?
The decryption support seems simple enough, one line. I'll pull that in tomorrow and credit you and the review for it. Maybe I can finagle a formatted patch into my repo to keep authorship and all.
Click to expand...
Click to collapse
Ok, that is a lot to take in......
I am more then willing to work with anyone that is willing to work with me.....
I am still learning everyday...
If you would like to join us on irc feel free, that is going to be the best for me....
Thx Josh
lj50036 said:
If you would like to join us on irc feel free, that is going to be the best for me...
Click to expand...
Click to collapse
Sure, I can do that. Which channel? I don't know twrp's infrastructure.
Steel01 said:
Sure, I can do that. Which channel? I don't know twrp's infrastructure.
Click to expand...
Click to collapse
TWRP IRC
Network: freenode
Channel: #twrp
Thx Josh
EDIT:
Huge thx to @Steel01 for all his help with this project..... :good:
Changelog:
Reforked kernel source, vendor init is working as expected....
TWRP 2.8.7.3 DOWNLOAD LINK !!
Thx Josh
Hi Josh - just had a chance to test 2.8.7.3 on my encrypted device and working perfectly.
Thanks!
lj50036 said:
TWRP IRC
Network: freenode
Channel: #twrp
Thx Josh
EDIT:
Huge thx to @Steel01 for all his help with this project..... :good:
Changelog:
Reforked kernel source, vendor init is working as expected....
TWRP 2.8.7.3 DOWNLOAD LINK !!
Thx Josh
Click to expand...
Click to collapse
did you already saw this?
http://forum.xda-developers.com/showthread.php?p=64143425
ti fix just define the props correctly via override (i dont know if its shield or shieldtab or anything like that )
Sent from my Xperia T using XDA Free mobile app