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 One GSM Unified (m7)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Notice: m7ul, m7att and m7tmo variants are no longer updated. Use the new unified m7
Click to expand...
Click to collapse
XDA:DevDB Information
[m7][CWM Advanced Edition] PhilZ Touch, Tool/Utility for the HTC One
Contributors
Phil3759
Version Information
Status: Stable
Created 2014-06-02
Last Updated 2014-06-02
its looks like that the recovery have the wrong resolution
Thanks
Blindie said:
its looks like that the recovery have the wrong resolution
Click to expand...
Click to collapse
description, pic?
Phil3759 said:
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Click to expand...
Click to collapse
Big problems with AROMA and HTC One
thank you for porting your recovery
migascalp said:
Big problems with AROMA and HTC One
thank you for porting your recovery
Click to expand...
Click to collapse
This can be sorted out in a second time, using a stock kernel/ramdisk fixed this issue for all phones affected till now
However, I need to have first a few feedback about how it is now and if there are issues
After that, we sort out bugs
Phil3759 said:
description, pic?
Click to expand...
Click to collapse
sorry, cant make pics.
The background ist green and pink and the layout ist double(i see the options on the left änd right side), sorry, cant discribe better, my english is bad
Phil3759 said:
description, pic?
Click to expand...
Click to collapse
double vertical display
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
adb don't work. Wrong driver?
migascalp said:
double vertical display
adb don't work. Wrong driver?
Click to expand...
Click to collapse
I used last CM source
They are modifying it every few mn. I will do a sync an release a new version
If it fails, I will repack around stock ramdisk
Thank you for the report
will this feature ability to mount /data/media as a USB disk drive?
Nekromantik said:
will this feature ability to mount /data/media as a USB disk drive?
Click to expand...
Click to collapse
that you cannot
Phil3759 said:
I used last CM source
They are modifying it every few mn. I will do a sync an release a new version
If it fails, I will repack around stock ramdisk
Thank you for the report
Click to expand...
Click to collapse
Hey. Check out my git for the m7 and the correct configs there. Use the twrp kernel in the thread linked to my goo. Its zarboz kernel. Better for aroma. Hope this helps.
Edit: someone took out the recovery config out of the m7. I got to see if I can get it back in. I'll be updating the official recovery with zarboz kernel soon.
Sent from my ADR6425LVW using Tapatalk 2
Flyhalf205 said:
Hey. Check out my git for the m7 and the correct configs there. Use the twrp kernel in the thread linked to my goo. Its zarboz kernel. Better for aroma. Hope this helps.
Edit: someone took out the recovery config out of the m7. I got to see if I can get it back in. I'll be updating the official recovery with zarboz kernel soon.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Thanks
I will wait for you to update your device repo to release next update
The display issue is strange as I compiled using stock cm-10.1 tree
Phil3759 said:
Thanks
I will wait for you to update your device repo to release next update
The display issue is strange as I compiled using stock cm-10.1 tree
Click to expand...
Click to collapse
Just updated my device tree with his kernel.
The discolor might be because you need to add TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888" and maybe RECOVERY_GRAPHICS_USE_LINELENGTH := true but hopefully you don't. Had the exact same problem with TWRP.
Flyhalf205 said:
Just updated my device tree with his kernel.
The discolor might be because you need to add TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888" and maybe RECOVERY_GRAPHICS_USE_LINELENGTH := true but hopefully you don't. Had the exact same problem with TWRP.
Click to expand...
Click to collapse
Thanks for the support (keep in mind I do not own the device or any HTC phone)
Except the device tree with precompiled kernel, do I need some ramdisk post compile ramdisk changes for your kernel?
Phil3759 said:
Thanks for the support (keep in mind I do not own the device or any HTC phone)
Except the device tree with precompiled kernel, do I need some ramdisk post compile ramdisk changes for your kernel?
Click to expand...
Click to collapse
Not to my knowledge you shouldn't need any. Just make sure you compile...
BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 androidboot.hardware=m7 user_debug=31
BOARD_KERNEL_BASE := 0x80600000
BOARD_KERNEL_PAGESIZE := 2048
BOARD_MKBOOTIMG_ARGS := --ramdisk_offset 0x01400000
Which you already have that since previous post shows a photo of your recovery
Flyhalf205 said:
Not to my knowledge you shouldn't need any. Just make sure you compile...
BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 androidboot.hardware=m7 user_debug=31
BOARD_KERNEL_BASE := 0x80600000
BOARD_KERNEL_PAGESIZE := 2048
BOARD_MKBOOTIMG_ARGS := --ramdisk_offset 0x01400000
Which you already have that since previous post shows a photo of your recovery
Click to expand...
Click to collapse
Yes, those are already defined in BoardConfigCommon.mk
Thank you for the support (out of the daily limit for :good
Will try to compile it tomorrow
Just one question: stock CWM has also broken graphics for your phone? Still wondering why my compiled one went broken if stock cwm is ok for your device
Phil3759 said:
Just one question: stock CWM has also broken graphics for your phone? Still wondering why my compiled one went broken if stock cwm is ok for your device
Click to expand...
Click to collapse
No. Never has broken graphics. Only TWRP has and has been fixed with those two lines. Not sure why yours is.
Flyhalf205 said:
No. Never has broken graphics. Only TWRP has and has been fixed with those two lines. Not sure why yours is.
Click to expand...
Click to collapse
I will sync the repo, who knows
It could be the png is too big as a background, but strange anyway
New update, using Flyhalf205 device tree
http://d-h.st/users/philz_touch/?fld_id=16699#files
Let me know if graphics are fixed and about eventual other bugs
Related
SO HERE WE GO MY GT-6210 FRIENDS.
I sold my tab because I got an iPad 2 for work and used the money to get a Galaxy Nexus I will probably keep building this ROM once the kernel is worked out and everything is working. Most likely Build AOKP
Just like the GT-6200 Developer Release this is a very basic preview build of CM9. That being said, if you choose to flash this build, YOU DO SO AT YOUR OWN RISK.
I am not a Dev or claim to be one, I just spent a lot of time the last few monthes learning how to build from AOSP and CM9, and figured I'd share my success with the community. I am not resposible for any one bricking their devices by not reading all the information that is all hear on XDA.
Please atleast read through this if you are a n00b: http://forum.xda-developers.com/showthread.php?t=1452716
And this if you are not Rooted yet: http://forum.xda-developers.com/showthread.php?t=1379532
ONCE AGAIN
FLASH AT YOUR OWN RISK
All credit and thanks goes out to:
-Google
-The whole Cyanogen team
-aorth (for getting this moving on out TABs)
-locerra (for his quick work on the p6210 device tree & framework tweaks)
-garyd9 (for all his work on the p6210 and this forum)
-Anyone else that made this possible THANK YOU
I will try to maintain this thread as much as I can, but I have a full time job, school, family and a life
I will at the least be folowing any changes in the source code or on github and post any builds I compile.
I WILL NOT BE:
-Responding to any questions that can be found by simply searching
-Spending a lot of time helping people to get this up and running
This is what I did to get it up and running:
-Put the ZIP file on the TABs internal sd partition (NOT THE SD CARD YOU PUT IN TO THE TAB)
-Reboot into Recovery
-Wipe data/factory reset
-Wipe cache partition
-wipe Dalvik Cache
-format /cache
-format /system
-format /data
-Install update-cm-9.0.0-RC0-p6210-UNOFFICIAL-signed.zip
-Reboot and enjoy!!! Not much is working though.
What's working:
Accelerometer
Hardware-accelerated launcher
Touch input
Vibration
Physical buttons (volume + power)
Audio
What's not working:
Bluetooth
Wifi
Camera
GPS
Hardware-accelerated video
Ambient light sensor(working for the most part in new build 2)
Here is the link: http://www.mediafire.com/?jrcehwgewyxi6kb
Any Mirrors for downloads are welcome, not sure how for the free mediafire account will go.
New Build with working Audio
Thanks to locerra!!!
DP2: http://goo.gl/6mXTQ
md5: 79bdbb1e44d8e4421221525c00947688
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reserved
Sent from my GT-P6210 using xda premium
Hey! This is awesome, i'm glad you were able to get this running. I was gonna try to get it running, but I ran outta space on my ubuntu partition lol.
I was wondering if we could get wifi working by porting this..
https://github.com/psyke83/AR6kSDK.3.1
fyi, locerra = ohanar
locerra said:
fyi, locerra = ohanar
Click to expand...
Click to collapse
Good to know lolz
Sent from my GT-P6210 using xda premium
Woooo yes bring it on! Great to see people chipping in and getting this off the ground! Really looking forward to seeing this finished.
Would be abysmally funny if they finish before Samsung gets their ICS out even though that circumstance is not likely to happen.
bdds13 said:
Hey! This is awesome, i'm glad you were able to get this running. I was gonna try to get it running, but I ran outta space on my ubuntu partition lol.
I was wondering if we could get wifi working by porting this..
https://github.com/psyke83/AR6kSDK.3.1
Click to expand...
Click to collapse
Not sure if I could get this worked into a build. Do you have more info on what and where this code comes from?
Sent from my GT-P6210 using xda premium
This is great and really inspiring. I really wish I knew where to begin to help out on moving this forward. Thanks for all the work guys
kmmxracer said:
Not sure if I could get this worked into a build. Do you have more info on what and where this code comes from?
Sent from my GT-P6210 using xda premium
Click to expand...
Click to collapse
Yeah, I got it from this old post here on the general forum.
http://forum.xda-developers.com/showpost.php?p=23262686&postcount=18
It's supposed to be from one of sony's e-book reader devices.
Good to see you up and running. Congrats! Now you guys get to work on wifi and I'll start working on telephony .
kmmxracer said:
Not sure if I could get this worked into a build. Do you have more info on what and where this code comes from?
Sent from my GT-P6210 using xda premium
Click to expand...
Click to collapse
i found something similar quite some time ago.
https://github.com/DerArtem/AR6kSDK.3.1
it's from derartem, he and nopy is working on ICS for Folio 100 too currently.
http://forum.xda-developers.com/showthread.php?t=1470823
it is the same thing with some modification from DerArtem.
Progress on wireless... sorta.
P6200/P6210 use an Atheros 6003 wireless chip (also for bluetooth?). The open-source atk6kl driver from compat-wireless supports this chip. I found some interesting information about building this module on the HP Touchpad forum over at RootzWiki. I can compile the module, but I just can't load it.
Here's how:
1. Compile kernel:
Code:
cd ~/src/git/kernel_samsung_c210
LOCALVERSION="" ARCH=arm CROSS_COMPILE="/home/aorth/src/android-ndk-r7b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-" make -j8 zImage
2. Compile compat-wireless
Code:
cd ~/src/compat-wireless-3.3-2-n
./scripts/driver-select ath6kl
ARCH=arm CROSS_COMPILE="/home/aorth/src/android-ndk-r7b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-" KLIB=~/src/git/kernel_samsung_c210 KLIB_BUILD=~/src/git/kernel_samsung_c210 make -j4
But attempting to insert the resulting modules spits out errors like:
Code:
# insmod compat.ko
insmod: can't insert 'compat.ko': invalid module format
# dmesg | tail -n3
<4>[ 365.244149] load_module: umod=4015c000, len=1311485, uargs=01a1f008
<3>[ 365.266659] compat: unknown relocation: 96
<6>[ 382.490328] BAT : soc(100), vcell(4152mV), curr(0mA), temp(26.7), chg(0), full(1), rechg(0), cable(1)
@ohanar... help!
Nice start!
aorth said:
P6200/P6210 use an Atheros 6003 wireless chip (also for bluetooth?). The open-source atk6kl driver from compat-wireless supports this chip. I found some interesting information about building this module on the HP Touchpad forum over at RootzWiki. I can compile the module, but I just can't load it.
Here's how:
1. Compile kernel:
Code:
cd ~/src/git/kernel_samsung_c210
LOCALVERSION="" ARCH=arm CROSS_COMPILE="/home/aorth/src/android-ndk-r7b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-" make -j8 zImage
2. Compile compat-wireless
Code:
cd ~/src/compat-wireless-3.3-2-n
./scripts/driver-select ath6kl
ARCH=arm CROSS_COMPILE="/home/aorth/src/android-ndk-r7b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-" KLIB=~/src/git/kernel_samsung_c210 KLIB_BUILD=~/src/git/kernel_samsung_c210 make -j4
But attempting to insert the resulting modules spits out errors like:
Code:
# insmod compat.ko
insmod: can't insert 'compat.ko': invalid module format
# dmesg | tail -n3
<4>[ 365.244149] load_module: umod=4015c000, len=1311485, uargs=01a1f008
<3>[ 365.266659] compat: unknown relocation: 96
<6>[ 382.490328] BAT : soc(100), vcell(4152mV), curr(0mA), temp(26.7), chg(0), full(1), rechg(0), cable(1)
@ohanar... help!
Click to expand...
Click to collapse
I need to learn to compile a kernel. Where did you get the kernel from and where did you get the toolchain/cross compiler from? Is it the one inside the cyanogen repo or codesourcery or what?
Sorry if the dumb questions, but I'm just getting started/interested in kernels
kmmxracer said:
I need to learn to compile a kernel. Where did you get the kernel from and where did you get the toolchain/cross compiler from? Is it the one inside the cyanogen repo or codesourcery or what?
Click to expand...
Click to collapse
The kernel we are currently using is the one at https://github.com/ohanar/kernel_samsung_c210, however, in the long run we should move over to https://github.com/teamhacksung/android_kernel_samsung_smdk4210, although this is currently broken for our devices (so we need to fix it ).
I am using the latest ndk toolchain that comes with in cm repo.
---------- Post added at 02:35 AM ---------- Previous post was at 02:33 AM ----------
aorth said:
@ohanar... help!
Click to expand...
Click to collapse
Haven't really looked into this too much. I'm more interested in getting the smdk4210 kernel working (and that already includes the atheros drivers).
Thanks, I just found some good reading on compiling kernels. I allways find what I need right after asking in a thread
I'll start with the teamhacksung git. Thanks!!!!
locerra said:
Haven't really looked into this too much. I'm more interested in getting the smdk4210 kernel working (and that already includes the atheros drivers).
Click to expand...
Click to collapse
Yeah, you're right. It's likely the same ath6kl driver, though, as compat-wireless is where the mainline kernel gets linux-wireless-next (and smdk4210 kernel is based on mainline, or at least will be soon... it might be based on origen board kernel right now, see OpenGalaxy).
btw, this module loading issue isn't strictly a wireless issue. I can't load j4fs or scsi_wait_scan either. I swear I loaded these once before, recently...
btw, this module loading issue isn't strictly a wireless issue. I can't load j4fs or scsi_wait_scan either. I swear I loaded these once before, recently...
Click to expand...
Click to collapse
Yeah, I'm having that issue too...
locerra said:
Yeah, I'm having that issue too...
Click to expand...
Click to collapse
Question... when you were still using kernels compiled with Samsung's LOCALVERSION string, did you ever get the ar6000.ko to load?
NOTICE: I am not the developer of TWRP. I just compiled it for the HTC Desire with permission from TeamWin. Huge thanks to them and to Dees_Troy for his help. Source code is available at their website.
Click to expand...
Click to collapse
Team Win Recovery Project 2.2, 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:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CHANGELOG:
Complete changelogs can be found here.
DOWNLOADS:
- TWRP 2.3.1.1 recovery.img md5:7126C885B1673D9C4066644D4A315967
- TWRP 2.2.0 recovery.img md5:36DC01E924BD5853859C912ECAD46123
BUGS:
Since this is not an official release, bugs are to be expected. That said, after some extensive testing I did not discover any bugs, but you are free to report anything you find.
IMPORTANT NOTICE: Currently due to some restrictions in the source code, this build of the recovery can mount the sd-ext partition ONLY if it is formatted as ext4. Other filesystems (such as ext3) are currently unsupported.
This will be fixed in future versions. --- FIXED
Click to expand...
Click to collapse
SUPPORT:
Live support is available via #twrp on Freenode.
INSTALLATION INSTRUCTIONS:
Download the recovery from the link in the first post
Unzip on your computer
Flash the recovery using your favorite tool (Android Flasher, Fastboot Commander, etc)
Alternatively you can flash with fastboot:
1) Boot Your phone in fastboot mode
2) Connect usb cable. It should now say Fastboot USB.
3) In cmd type:
Code:
fastboot devices
fastboot erase recovery
fastboot flash recovery c:\path.to.recovery\recovery.img
4) Unplug and reboot.
If you encounter any errors with the recovery during or after the installation refer to Bortak's guide on Desire Q/A.
Downloading now
Thanks for your hard work, looks great...
john9 said:
Thanks for your hard work, looks great...
Click to expand...
Click to collapse
Thanks, but I didn't make it, all credit goes to TeamWin. I just compiled it for the Desire
Very good …
Sent from my HTC Desire using xda premium
island3r said:
Thanks, but I didn't make it, all credit goes to TeamWin. I just compiled it for the Desire
Click to expand...
Click to collapse
Thanks, it doesnt matter that you didnt make it, important is that all of us can use something new and keep the Desire forum alive!
:thumbs up:
Would this work with the CDMA desire?
Sent from my HTC Desire CDMA using xda app-developers app
afterthought325 said:
Would this work with the CDMA desire?
Sent from my HTC Desire CDMA using xda app-developers app
Click to expand...
Click to collapse
Hmm, no but I can make a different version for it if you want.
island3r said:
Hmm, no but I can make a different version for it if you want.
Click to expand...
Click to collapse
Please do, I have a cdma desire and would love to have this also.
island3r said:
Hmm, no but I can make a different version for it if you want.
Click to expand...
Click to collapse
Yes that would be amazing! i use twrp on my Transformer Prime and love it. it would be amazing to have for my phone too. its very hard to find developers who are willing to develop for cdma counterparts for this i thank you even just to offer to do so. also if you need a tester. i'll be glad. just pm me
afterthought325 said:
Yes that would be amazing! i use twrp on my Transformer Prime and love it. it would be amazing to have for my phone too. its very hard to find developers who are willing to develop for cdma counterparts for this i thank you even just to offer to do so. also if you need a tester. i'll be glad. just pm me
Click to expand...
Click to collapse
Ok then, I'll definately need a beta tester because I don't have a bravoc. Hopefully I'll pm you tonight
Does this recovery use any of the networking features of the CyanogenMod kernel? I've reduced the size of recovery.img from 3.5 to 2.9 MB by disabling many of the networking features in the kernel and using LZMA for the ramdisk compression. For the kernel features, I have used 90 % of the 4ext Touchcovery kernel configuration. Does this recovery know to align the partitions when creating them?
THis look awesome
Thankx
Has anyone found any themes for this recovery for our Desire's resolution? Doesn't appear to be much around.
AlxMAX said:
I've reduced the size of recovery.img from 3.5 to 2.9 MB by disabling many of the networking features in the kernel and using LZMA for the ramdisk compression.
Click to expand...
Click to collapse
You reduced the size of TWRP or the stock CWM recovery? I don't see why the recovery needs to be any smaller, since that doesn't make any difference to the end user.
AlxMAX said:
Does this recovery know to align the partitions when creating them?
Click to expand...
Click to collapse
Yes the created partitions are aligned automatically.
guy_smiley said:
Has anyone found any themes for this recovery for our Desire's resolution? Doesn't appear to be much around.
Click to expand...
Click to collapse
Here are two themes that are compatible:
http://rootzwiki.com/topic/25762-480x800-21-icscyan-system-style-theme/
http://rootzwiki.com/topic/23782-480x80021-ice-cream-sandwich/
There are many other themes as well but they do not support 480x800 so they need some tinkering. I'll look into it when I have some free time.
island3r said:
You reduced the size of TWRP or the stock CWM recovery?
Click to expand...
Click to collapse
Since the topic was dedicated to TWRP, I have meant the size of TWRP.
island3r said:
I don't see why the recovery needs to be any smaller, since that doesn't make any difference to the end user.
Click to expand...
Click to collapse
That's true, but it does matter to the developers since it might allow adding more features. The recovery partition is limited in size after all!
AlxMAX said:
Since the topic was dedicated to TWRP, I have meant the size of TWRP.
That's true, but it does matter to the developers since it might allow adding more features. The recovery partition is limited in size after all!
Click to expand...
Click to collapse
From that perspective yes you are right. From what I understand a this moment future versions are most likely going to be bugfixes. So space isn't going to be a problem in the near future. However what you did was very clever. Did you use lzma for compression?
island3r said:
(...) Did you use lzma for compression?
Click to expand...
Click to collapse
Yes, I used LZMA for the ramdisk compression!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Recovery
Download
Version 0.5
- Fixed ramdisk address (Thanks to Flyhalf205)
Issues:
- None found yet
How to flash:
- unlock your bootloader via htcdev site
- rename the file to "recovery.img"
- go to bootloader ---> fastboot
- type "fastboot flash recovery recovery.img"
More recoveries:
CWM by Flyhalf205
TWRP by Flyhalf205
Rooting Tools
Download
How to flash:
- from inside recovery
You flash it all at your own risk!
YAY! Not to criticize. But building HTC recoveries with builders.clockworkmod usually doesn't work well.
1.) The font is going to be extremely tiny. Going to be using like size 12 on a 23 size screen
2.) The sdcard path in the recovery.fstab is wrong.
3.) It is missing about 4 files in the sbin folder. Famous file is offmode_charging.
But congrats man on starting it.
If you want to break mine down and look inside at the init script/recovery.fstab and compare. The one I built last week at http://forum.xda-developers.com/showpost.php?p=38384371&postcount=24
Flyhalf205 said:
YAY! Not to criticize. But building HTC recoveries with builders.clockworkmod usually doesn't work well.
1.) The font is going to be extremely tiny. Going to be using like size 12 on a 23 size screen
2.) The sdcard path in the recovery.fstab is wrong.
3.) It is missing about 4 files in the sbin folder. Famous file is offmode_charging.
But congrats man on starting it.
If you want to break mine down and look inside at the init script/recovery.fstab and compare. The one I built last week at http://forum.xda-developers.com/showpost.php?p=38384371&postcount=24
Click to expand...
Click to collapse
I just wanted to post some basic stuff so that someone with HTC One can root his device and f.g. use dd to dump boot and system partition for us. I have no doubts that much better recoveries will come soon. It's just something to begin with.
Anyway, thanks for your tips! HTC One X+ also had wrong sdcard path as far as I remember.
For anyone who does get the mounts list or partition sizes. Fix and send me a pull request so we can get official CWM. https://github.com/Flyhalf205/android_device_htc_m7
Yeah one click build tool was never fine, use CM source
AW: [RECOVERY] Rooting HTC One | ClockworkMod Recovery 0.1 [02.03.2013]
Nice starting mike
Will it be possible to get soff with the new one or do we have still be son? Further do you guys think that it is possible to open bootloader without HTC dev so that you can have your guarantee further?
Sharpi1 said:
Nice starting mike
Will it be possible to get soff with the new one or do we have still be son? Further do you guys think that it is possible to open bootloader without HTC dev so that you can have your guarantee further?
Click to expand...
Click to collapse
You're not loosing your warranty with HTCdev.com
mike1986. said:
You're not loosing your warranty with HTCdev.com
Click to expand...
Click to collapse
Sorry to spam the second thread again - but REALLY? i lost mine while unlocking my sensation.
1887 said:
Sorry to spam the second thread again - but REALLY? i lost mine while unlocking my sensation.
Click to expand...
Click to collapse
Is there anywhere stated that you loose your warranty? Nope. All is written there is:
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty.
Click to expand...
Click to collapse
Which means, that if you brick your device while flashing custom ROM, which unlocked bootloader allows you, you may have no warranty claim for that.
If you read carefully it you can conclude 2 important things:
1) If "not all claims" may be covered under warranty, then (logic conversion) some claims may be still covered under warranty.
2) Even if you can't claim something under warranty because of unlocked bootlader, that doesn't mean you lost your warranty. You still have your warranty and you still can have claims under warranty, but this warranty wont cover those claims caused by or from the unlocking of the bootloader.
I hope that explains things
Thank you - it does.
I'm full of anticipation about first flashing Roms etc.
1887 said:
Thank you - it does.
I'm full of anticipation about first flashing Roms etc.
Click to expand...
Click to collapse
You inspired me to write new article on my blog, so shortly you'll be able to read there more!
When a recovery is fully working, I'll release my toolkit with it. I already made the base for this device!
When I will get my One hopefully soon, I will build one from CWM source and maybe TWRP if there won't be anyone faster than me
hasoon2000 said:
When a recovery is fully working, I'll release my toolkit with it. I already made the base for this device!
Click to expand...
Click to collapse
torxx said:
When I will get my One hopefully soon, I will build one from CWM source and maybe TWRP if there won't be anyone faster than me
Click to expand...
Click to collapse
Sounds great guys!
BTW you might be interested in reading this - http://android-revolution-hd.blogspot.com/2013/03/unlocking-bootloader-or-flashing-custom.html
Re: [RECOVERY] Rooting HTC One | ClockworkMod Recovery 0.1 [02.03.2013]
torxx said:
When I will get my One hopefully soon, I will build one from CWM source and maybe TWRP if there won't be anyone faster than me
Click to expand...
Click to collapse
I've got twrp built. I will upload it tonight when I get home. And cwm from source with the correct dev blocks.
cwm from source at http://forum.xda-developers.com/showpost.php?p=38384371&postcount=3
I haven't posted the version with the correct dev/blocks yet
TWRP doesn't support our screen size so when you do install it. It will not cover the entire screen.
Make sure your TWRP config looks like
DEVICE_RESOLUTION := 800x1280
TW_INCLUDE_DUMLOCK := true
RECOVERY_SDCARD_ON_DATA := true
BOARD_HAS_NO_REAL_SDCARD := true
TW_INTERNAL_STORAGE_PATH := "/data/media"
TW_INTERNAL_STORAGE_MOUNT_POINT := "data"
TW_NO_USB_STORAGE := true
RECOVERY_GRAPHICS_USE_LINELENGTH := true
EDIT: Posted the new recovery at http://forum.xda-developers.com/forumdisplay.php?f=2120
Sent from my HTC6435LVW using Tapatalk 2
Thread cleaned
It's not another users business to decide which thread is necessary and which is not. Please keep that in mind.
Thank you very much
Awesome stuff Mike, see you in the ARHD HTC ONE ROM thread
Could anybody with a rooted HTC One, dump the contents or screenshot the thermald.conf file (system/etc/thermald.conf). I'm trying to confirm the GPU clock of the Snapdragon 600
Re: [RECOVERY] Rooting HTC One | ClockworkMod Recovery 0.2 [07.03.2013]
Hey to let you if you want to link it or whatever. I got Koush to add this recovery to Rom manager.
Sent from my HTC6435LVW using Tapatalk 2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flashalot said:
Click to expand...
Click to collapse
Congratulations, now if us One M7 users can get the updated Mrom ui and twrp so we can flash L then I will be extra happy
dd98 said:
Congratulations, now if us One M7 users can get the updated Mrom ui and twrp so we can flash L then I will be extra happy
Click to expand...
Click to collapse
Since all its been ported already I can update it but I would need you to test it pm me on hangouts if that sounds like something you want to do [email protected]
Edit : If anyone would like to test out multirom for ville pm me on hangouts or here in xda you MUST have some experience with fastboot and adb and able to pull logcats
Flashalot said:
Since all its been ported already I can update it but I would need you to test it pm me on hangouts if that sounds like something you want to do [email protected]
Edit : If anyone would like to test out multirom for ville pm me on hangouts or here in xda you MUST have some experience with fastboot and adb and able to pull logcats
Click to expand...
Click to collapse
Next thing that is needed is for kernel developers like @flar2 @rmbq and @AKToronto to add kexec-hardboot patch to their kernels so Multirom can actually work
dd98 said:
Next thing that is needed is for kernel developers like @flar2 @rmbq and @AKToronto to add kexec-hardboot patch to their kernels so Multirom can actually work
Click to expand...
Click to collapse
Here's my patch https://github.com/flashalot/Nightmare_Kernel_Ville?files=1 last thing that needs to be done is the hardboot part which I'm stuck on here the error
I keep getting this error about CONFIG_KEXEC_HARDBOOT = y not found in proc/config.gz same with atags here's the log http://pastebin.com/SMMpqTU2
Flashalot said:
Here's my patch https://github.com/flashalot/Nightmare_Kernel_Ville?files=1 last thing that needs to be done is the hardboot part which I'm stuck on here the error
I keep getting this error about CONFIG_KEXEC_HARDBOOT = y not found in proc/config.gz same with atags here's the log http://pastebin.com/SMMpqTU2
Click to expand...
Click to collapse
Try asking @Tasssadar
I might be able to help when I return from my trip next week. I just did kexec-harboot on the m8 so it's fresh in my mind.
Also, my One S underwent successful surgery last night, and has a brand new LCD panel.
Can someone send me a pm next Tuesday to remind me?
dd98 said:
Next thing that is needed is for kernel developers like @flar2 @rmbq and @AKToronto to add kexec-hardboot patch to their kernels so Multirom can actually work
Click to expand...
Click to collapse
i already implemented kexec-hardboot patch to my kernel but it's untested so probably/maybe memory addressees are wrong
Yea I tried but a lot of it was erroring so I started from scratch I'll try it again to see any luck
Also I think I got to the bottom of it and why its not allowing you to switch ROMs
@flar2 hopefully I'll have it dome by then if not I'm pretty sure you know how to do it ?
Dual Post
Flashalot said:
Yea I tried but a lot of it was erroring so I started from scratch I'll try it again to see any luck
Also I think I got to the bottom of it and why its not allowing you to switch ROMs
@flar2 hopefully I'll have it dome by then if not I'm pretty sure you know how to do it ?
Click to expand...
Click to collapse
how is everything going, I finally got into kernel development and the help is here when needed
dd98 said:
how is everything going, I finally got into kernel development and the help is here when needed
Click to expand...
Click to collapse
Well I'm stuck on adding the address in memory.h once that's done the kernel should be fine
I also tried @rmqb patch but the phone would freeze and reboot when trying to boot the zImage or repacking the boot
Here's the kernel patch, tested and fully working using latest ElementalX source:
https://github.com/flar2/android_ke...mmit/16382d51802b3f335808efba7f4f7d57f5d3632a
https://github.com/flar2/android_ke...mmit/bdd9b2d008906987c23e719b6eb7bff17d9dff8b
I booted into the second kernel using this command:
Code:
kexec --load-hardboot <your zImage> --ramdisk=<your ramdisk> --mem-min=0x85000000 --command-line="$(cat /proc/cmdline)"
flar2 said:
Here's the kernel patch, tested and fully working using latest ElementalX source:
https://github.com/flar2/android_ke...mmit/16382d51802b3f335808efba7f4f7d57f5d3632a
https://github.com/flar2/android_ke...mmit/bdd9b2d008906987c23e719b6eb7bff17d9dff8b
I booted into the second kernel using this command:
Code:
kexec --load-hardboot <your zImage> --ramdisk=<your ramdisk> --mem-min=0x85000000 --command-line="$(cat /proc/cmdline)"
Click to expand...
Click to collapse
Fantastic [emoji2]
I'll compile a updated recovery with the kexec hardboot number and then it should be ready
So could we use multirom on our htc one s??
My current problem is that once I load up a sense Rom(4.4.2/4.4.3) the multirom boot menu is gone but on aosp it's still there so I'm currently redoing the patch to a aosp kernel instead of sense
Flashalot said:
My current problem is that once I load up a sense Rom(4.4.2/4.4.3) the multirom boot menu is gone but on aosp it's still there so I'm currently redoing the patch to a aosp kernel instead of sense
Click to expand...
Click to collapse
did you remember that liberty has aroma installer?
dd98 said:
did you remember that liberty has aroma installer?
Click to expand...
Click to collapse
That was my first though that it was from aroma m8 has the same problem but alas that's not it I'm down to 2 errors on the kernel then I'm done hopefully
so we could have both sense 6 and cm11s with multirom? i've seen that in oneplusone rom you've added multirom support. how does it work?
Tanque97 said:
so we could have both sense 6 and cm11s with multirom? i've seen that in oneplusone rom you've added multirom support. how does it work?
Click to expand...
Click to collapse
i just edited the updater script to ensure that there is no problems flashing if its released, but that means no aroma installer
Hello everyone
user @santeri3700 built oc kernel for our samsung galaxy core plus
but I wanted him even more tweak cpu ... and it worked!
Present *DANiO* Kernel; which is overclocked to 1.7GHz!
Advantages:
Overclocked to 1.77GHz,
It has drivers ntfs and exFAT
It uses anykernel2; now it's more elegant
bugs:
Not yet discovered
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://www.youtube.com/watch?v=BEpb3kOtn8U
Correction of graphics; changed the logo when starting kernel
Automatic builder is on my github
If you still want to test it here is a link.
Updated "updater-script" in zip file "Modules for DANiO Kernel.zip" faulting installation via twrp or cwm
DOWNLOAD UPDATE FOR THIS FILE
Wifi still dont work
Edit
Now works
QGM said:
Wifi still dont work
Edit
Now works
Click to expand...
Click to collapse
you're welcome
PS: Do u using my kernel in this time?
No because i back to stock rom
Wysłane z mojego SM-G350 przy użyciu Tapatalka
Danielisko said:
you're welcome
PS: Do u using my kernel in this time?
Click to expand...
Click to collapse
QGM said:
No because i back to stock rom
Wysłane z mojego SM-G350 przy użyciu Tapatalka
Click to expand...
Click to collapse
@Danielisko
If you rebase your changes on top of the current Salmiakki Super V2 source, it should most probably work on Stock 4.2.2 and CM/Lineage 13 :good:
EDIT: You need to use the prepared AnyKernel 2 flashable ZIP from the Salmiakki Super thread and put your kernel in it, else it won't be compatible with all ROMs (because if you do it by boot.img, it overwrites the Ramdisk). Also, remember to put the kernel modules you have built into the appropriate folder, else WiFi and some other stuff won't work.
EDIT2: I saw that you have a seperate ZIP for the modules. Still, AnyKernel 2 is easier to use and privides more functionality (and it preserves the ramdisk)
EDIT3: Salmiakki Super V2 source is here:
http://www.github.com/SiniTurk/android_kernel_samsung_cs02/tree/salmiakki
EDIT4: Also, make sure you publish the source of your kernel somewhere and link it, because you are technically violating the License right now
@TimSchumi thx .... btw: You requested me to use a anykernel2 from @osm0sis user... now I request you to test this my kernel.
Greetings
Later I will give the source of the kernel
Danielisko said:
@TimSchumi thx .... btw: You requested me to use a anykernel2 from @osm0sis user... now I request you to test this my kernel.
Greetings
Later I will give the source of the kernel
Click to expand...
Click to collapse
This kernel bootloops on Lineage 13 (how did you add that bootimage btw?), didn't test Lineage 11 yet
i did it fast.... maybe it's bad 'anykernel.sh' file?
Code:
# AnyKernel2 Ramdisk Mod Script
# osm0sis @ xda-developers
## AnyKernel setup
# begin properties
properties() {
kernel.string=*DANiO* OC Kernel
do.devicecheck=1
do.modules=1
do.cleanup=1
do.cleanuponabort=1
device.name1=cs02
}
# end properties
# shell variables
block=/dev/block/mmcblk0p5;
is_slot_device=0;
## AnyKernel methods (DO NOT CHANGE)
# import patching functions/variables - see for reference
. /tmp/anykernel/tools/ak2-core.sh;
## AnyKernel install
dump_boot;
write_boot;
## end install
And what is the difference between 'base', 'cm-11.0'+ (and up)?
I'm trying to compile 'base' for all cm-* (? - Need confirmation)
PS: As I remember it is probably 'cm-11.0' version of kernel.
Danielisko said:
i did it fast.... maybe it's bad 'anykernel.sh' file?
And what is the difference between 'base', 'cm-11.0'+ (and up)?
I'm trying to compile 'base' for all cm-* (? - Need confirmation)
PS: As I remember it is probably 'cm-11.0' version of kernel.
Click to expand...
Click to collapse
Did you base it of the 'normal' version of AnyKernel or did you take the AnyKernel zip from the Salmiakki Super thread? Because the latter should work fine if you only switch out the zImage and the modules.
The kernel source should be the same over all branches (except for salmiakki ofc, which ships OC and the nethunter kernel, which ships OC and a USB HID driver)
I recommend you to take the 'salmaikki' branch and reapply your changes on top of it.
ok you can test my repo for building kernel....
It has a build procedure that clones a github repository (it just is not a fork), then downloads the 'danio_oc_kernel-prepared.tar.bz2' file, unpack it and merges it into the previously downloaded repo and builds the kernel. Such a philosophy!
EDIT: You maybe try this, when i compile a while ago from 'salmiakki' branch . @berkantkz , @santeri3700 and @Logiel - Will you test it?
Danielisko said:
ok you can test my repo for building kernel....
It has a build procedure that clones a github repository (it just is not a fork), then downloads the 'danio_oc_kernel-prepared.tar.bz2' file, unpack it and merges it into the previously downloaded repo and builds the kernel. Such a philosophy!
EDIT: You maybe try this, when i compile a while ago from 'salmiakki' branch . @berkantkz , @santeri3700 and @Logiel - Will you test it?
Click to expand...
Click to collapse
I actually couldn't quite understand what did you mean to. I haven't been following the thread for long time so I don't know the affair
berkantkz said:
I actually couldn't quite understand what did you mean to. I haven't been following the thread for long time so I don't know the affair
Click to expand...
Click to collapse
simply download, flash it and test if it's working and wi-fi
Danielisko said:
simply download, flash it and test if it's working and wi-fi
Click to expand...
Click to collapse
Well, I don't own your devices man I just helped to Santeri and Tim
Danielisko said:
ok you can test my repo for building kernel....
It has a build procedure that clones a github repository (it just is not a fork), then downloads the 'danio_oc_kernel-prepared.tar.bz2' file, unpack it and merges it into the previously downloaded repo and builds the kernel. Such a philosophy!
EDIT: You maybe try this, when i compile a while ago from 'salmiakki' branch . @berkantkz , @santeri3700 and @Logiel - Will you test it?
Click to expand...
Click to collapse
I'm currently preparing everything for vacation, I'll test it when I have some free time (I need to flash Lineage 11 anyways to confirm a bug)
TimSchumi said:
I'm currently preparing everything for vacation, I'll test it when I have some free time (I need to flash Lineage 11 anyways to confirm a bug)
Click to expand...
Click to collapse
and how?
Danielisko said:
and how?
Click to expand...
Click to collapse
Still did not boot.
TimSchumi said:
Still did not boot.
Click to expand...
Click to collapse
sorry for my late
according in "ak2-core.sh" file uses only gzip...
i added some decompressor for initrd (such as: xzcat, bzcat, etc....).
---
You can test it again.
Danielisko said:
sorry for my late
according in "ak2-core.sh" file uses only gzip...
i added some decompressor for initrd (such as: xzcat, bzcat, etc....).
---
You can test it again.
Click to expand...
Click to collapse
This ZIP doesn't even flash.
Everything was ok about the ZIP itself, the kernel was unbootable.
i see :/
the kernel bumped to the latest version and maybe its need rebuilding? btw travis-ci is building the kernel
the new content with kernel source and flashable zip will be here
and the logging is here