Related
When I installed android, I thought the tutorial said to not update clockworkmod as it was specially made for the touchpad. I'm now reading things that say to be on the latest cwm version. Can I update cwm on my touchpad? Will it break any features?
Sent from my rooted HRC Rezound
There is currently no other ClockworkMod besides the one that is in the official thread for the Touchpad.
Do not use any other version of CWM with the Touchpad.
There is only one ClockworkMod. There are, however, other recoveries in development. There is a ClockworkMod touchscreen version, which I read has some bugs still. And then there is TWRP wich is more of a visual style recovery. If you already have ClockworkMod on your device and it works, there is no need to change it.
jsgraphicart said:
There is only one ClockworkMod. There are, however, other recoveries in development. There is a ClockworkMod touchscreen version, which I read has some bugs still. And then there is TWRP wich is more of a visual style recovery. If you already have ClockworkMod on your device and it works, there is no need to change it.
Click to expand...
Click to collapse
Edit:nrvermibd
Sent from my ADR6425LVW using Tapatalk 2
I was just curious if anyone was planning on building TRWP 2.4 for the fassy since its not yet supported by their team.? Or does it still not play nice with the fassy?
BDogg718 said:
I was just curious if anyone was planning on building TRWP 2.4 for the fassy since its not yet supported by their team.? Or does it still not play nice with the fassy?
Click to expand...
Click to collapse
I'd love to see it on the fascinate! I'm rolling with it on my a500 and its freaking awesome
I am going to be receiving a fascinate tomorrow and have plans to install cm10.1 via odin. From my understanding I can then install twrp and goo to install updates from that point on. I presume I have to still use odin to unlock the phone and get CM10.1 working, but goo/twrp should work for updating it from the nightlys after that point, correct?
http://teamw.in/project/twrp2/40
Xceptiona1noob said:
I am going to be receiving a fascinate tomorrow and have plans to install cm10.1 via odin. From my understanding I can then install twrp and goo to install updates from that point on. I presume I have to still use odin to unlock the phone and get CM10.1 working, but goo/twrp should work for updating it from the nightlys after that point, correct?
Click to expand...
Click to collapse
You don't have to unlock the fascinate its all open just put cwm on it and flash cm10.1 twrp won't work on cm10 and above so you have to use cwm use this guide here http://forum.xda-developers.com/showthread.php?t=1238070
Sent from my SCH-I500 using Tapatalk 2
Xceptiona1noob said:
I am going to be receiving a fascinate tomorrow and have plans to install cm10.1 via odin. From my understanding I can then install twrp and goo to install updates from that point on. I presume I have to still use odin to unlock the phone and get CM10.1 working, but goo/twrp should work for updating it from the nightlys after that point, correct?
http://teamw.in/project/twrp2/40
Click to expand...
Click to collapse
cm10 includes it's own "cmupdater" app. Checks for new builds on your schedule (or manually), notifies of new builds, displays change logs, and installs the updates. Works well. It's visible on the "about phone" settings menu. Also available in the app drawer...
Sent from my SCH-I500 using xda premium
I've fixed twrp to work with cm10.1. Works pretty well. Too bad injection doesn't work any more.
jt1134 said:
I've fixed twrp to work with cm10.1. Works pretty well. Too bad injection doesn't work any more.
Click to expand...
Click to collapse
Nice I've never used twrp so I may have to try it
Sent from my SCH-I500 using Tapatalk 2
Linked below is a kernel bundled with the latest version of TWRP modified to work with the fascinate. I've only tested it with my personal cm10.1 build, it should work with other 4.2.2 ROMs, may work with 4.2.1 ROMs. Due to the way the bootloader handles the kernel/recovery partitions, it (currently) has to be bundled with the kernel. If I come up with a way to make it stick across different builds I'll submit the changes to the appropriate upstream repositories, etc.
I haven't tested much other than flashing zip files, backup/restore may break your device into a million pieces. That might be kinda funny.
Updated source code is here:
https://github.com/jt1134/Team-Win-Recovery-Project/commits/twrp2.4
https://github.com/jt1134/android_device_samsung_fascinatemtd/commits/myjb-next
http://www.mediafire.com/?ul4n2gc1ba044sb
jt1134 said:
Linked below is a kernel bundled with the latest version of TWRP modified to work with the fascinate. I've only tested it with my personal cm10.1 build, it should work with other 4.2.2 ROMs, may work with 4.2.1 ROMs. Due to the way the bootloader handles the kernel/recovery partitions, it (currently) has to be bundled with the kernel. If I come up with a way to make it stick across different builds I'll submit the changes to the appropriate upstream repositories, etc.
I haven't tested much other than flashing zip files, backup/restore may break your device into a million pieces. That might be kinda funny.
Updated source code is here:
https://github.com/jt1134/Team-Win-Recovery-Project/commits/twrp2.4
https://github.com/jt1134/android_device_samsung_fascinatemtd/commits/myjb-next
http://www.mediafire.com/?ul4n2gc1ba044sb
Click to expand...
Click to collapse
Thanx JT! Back-up and restore work just fine! Great work as always!
BDogg718 said:
Thanx JT! Back-up and restore work just fine! Great work as always!
Click to expand...
Click to collapse
Good to know. Thanks for testing it
jt1134 said:
Linked below is a kernel bundled with the latest version of TWRP modified to work with the fascinate. I've only tested it with my personal cm10.1 build, it should work with other 4.2.2 ROMs, may work with 4.2.1 ROMs. Due to the way the bootloader handles the kernel/recovery partitions, it (currently) has to be bundled with the kernel. If I come up with a way to make it stick across different builds I'll submit the changes to the appropriate upstream repositories, etc.
I haven't tested much other than flashing zip files, backup/restore may break your device into a million pieces. That might be kinda funny.
Click to expand...
Click to collapse
And it does work on the latest hellybean as long as you 1st flash your cm kernel to it :thumbup:
Sent from my SCH-I500 using xda premium
hhp_211 said:
And it does work on the latest hellybean as long as you 1st flash your cm kernel to it :thumbup:
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
I'd love to see this incorporated into the devil kernel
Seems my changes have been merged in the main TWRP repository
I still can't seem to come up with a decent way to replace the recovery permanently from kernel to kernel, but I've fixed fakeflash to work with the current version of TWRP. Fakeflash allows you to temporarily flash a different recovery by flashing a zip file in your current recovery. This allows it to work regardless of what kernel/recovery you are currently using.
A test version is linked below. Flash it in your current recovery and it will reboot into TWRP. Subsequent reboots will run your previous recovery, the zip needs to be flashed each time to use TWRP. Anyone who has had the fascinate for more than a year and a half should know all about fakeflash it's the original way we used recovery (**** you samsung).
http://www.mediafire.com/?tq0uq2uo24lofcl
Thanks jt. It`s a step forward. You da man that's all I can say. :thumbup::beer:
Sent from my SCH-I500 using Xparent Green Tapatalk 2
if you are on fassy, notta posted a pa twp recovery flashable test as of now
LasVegasRomeo said:
if you are on fassy, notta posted a pa twp recovery flashable test as of now
Click to expand...
Click to collapse
does that kernel notta posted kill your WiFi?
kill type ?my wifi is workin I havent had any issues as far as i know. ran wifi a lil bit earlier and no issues. My wifi has is always crappy for me though here at home. Seems spotty a lil but like i said thats normal for me.
jt1134 said:
Seems my changes have been merged in the main TWRP repository
I still can't seem to come up with a decent way to replace the recovery permanently from kernel to kernel, but I've fixed fakeflash to work with the current version of TWRP. Fakeflash allows you to temporarily flash a different recovery by flashing a zip file in your current recovery. This allows it to work regardless of what kernel/recovery you are currently using.
A test version is linked below. Flash it in your current recovery and it will reboot into TWRP. Subsequent reboots will run your previous recovery, the zip needs to be flashed each time to use TWRP. Anyone who has had the fascinate for more than a year and a half should know all about fakeflash it's the original way we used recovery (**** you samsung).
http://www.mediafire.com/?tq0uq2uo24lofcl
Click to expand...
Click to collapse
is there a way to modify the source to use the prebuilt bootimage.Also when compiling it fails to create the utilities folder.
I have been trying to flash Imonseyon leankernel v5.1 for awhile now and I'm having issues... I don't know if the link doesn't work or what the deal is. I want the 184v undervolt bc I have been having crazy battery drain.. Everytime I flash it I get a status 2 in TWRP. Any suggestions..
lacoursiere18 said:
I have been trying to flash Imonseyon leankernel v5.1 for awhile now and I'm having issues... I don't know if the link doesn't work or what the deal is. I want the 184v undervolt bc I have been having crazy battery drain.. Everytime I flash it I get a status 2 in TWRP. Any suggestions..
Click to expand...
Click to collapse
What rom are you using?
If it's a Sense based GB rom, did you grab the Sense kernel?
If it's an AOSP GB rom, did you grab the Aosp kernel?
If it's an ICS rom, it won't work.
***EDIT
Via TWRP website:
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. If you're getting a status error 2 during zip install, then an outdated update binary is almost certainly to blame.
santod040 said:
What rom are you using?
If it's a Sense based GB rom, did you grab the Sense kernel?
If it's an AOSP GB rom, did you grab the Aosp kernel?
If it's an ICS rom, it won't work.
***EDIT
Via TWRP website:
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. If you're getting a status error 2 during zip install, then an outdated update binary is almost certainly to blame.
Click to expand...
Click to collapse
Ok thank you so much! FAST response lol. Would there be another recovery that is better to use or it doesn't matter?? Currently I am using your, I believe, ICS rooted debloated ROM stock/rooted. I was on liquidsmooth aosp and cm7 thundershed switching between them to get a feel for them... But for some reason I tried to do a full wipe and then reinstall from my restore of those two roms and try the leankernal, it's saying failed after I updated to TWRP 2.4.3
**EDIT:
Where is that zip you are talking about located.. In /system or somewhere else bc I can't seem to find it?
There is a backup bug in the latest release of Twrp. Switch to 4ext and your backups may work again. Someone posted on the n7 he could restore backups in Twrp from the previous version with the version he made them with but restoring backups on the latest version couldn't restore those
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
There is a backup bug in the latest release of Twrp. Switch to 4ext and your backups may work again. Someone posted on the n7 he could restore backups in Twrp from the previous version with the version he made them with but restoring backups on the latest version couldn't restore those
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Thank you!
4ext is definitely the way to go on the Thunderbolt. Best recovery ever, wish the Gnex had it.
Sent from my Galaxy Nexus using xda app-developers app
The zip I was referring to, was the kernel zip you were trying to flash.
And if you have run my rom, you should know I suggest using 4ext recovery.
It's mentioned in all my rom OP's.
santod040 said:
The zip I was referring to, was the kernel zip you were trying to flash.
And if you have run my rom, you should know I suggest using 4ext recovery.
It's mentioned in all my rom OP's.
Click to expand...
Click to collapse
Ok thank you! I have switched to 4ext thank you for the refferal
Do you backups work now?
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Do you backups work now?
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
No actually.. It's ok though. I don't mind starting over.. Thank you for your help! I am running leankernal now at 184mhz unlocked to see what kind of battery improvements it brings, if any.. With JellyBlur ROM.. Any sugesstion on a ROM?
lacoursiere18 said:
No actually.. It's ok though. I don't mind starting over.. Thank you for your help! I am running leankernal now at 184mhz unlocked to see what kind of battery improvements it brings, if any.. With JellyBlur ROM.. Any sugesstion on a ROM?
Click to expand...
Click to collapse
Good luck with the 184mhz, I can not use that on my phone, always does the deep sleep of death.... thats not a good thing.
As for a ROM, I always suggest one of Santod's ... really any of them lol
Milimbar said:
Good luck with the 184mhz, I can not use that on my phone, always does the deep sleep of death.... thats not a good thing.
As for a ROM, I always suggest one of Santod's ... really any of them lol
Click to expand...
Click to collapse
Dude so far no problems with 184mhz.. Speed is no issue, no lag, no reboots, but I'll have to put it through the 24hr test to fully see how it does. And I charge my battery to 100% when installed it, approx. 4hr 41mins with pretty much none stop usage.. at 72% now. On the old kernal I would have been dead..
This is my first attempt at building a kernel. This is strictly a /system write kernel. In the future I may upstream and add features. I have built this from the latest source that came out (m7ul-3.4.10-jb-crc-ddcfb8c)
For 1.28 devices only!
Changelog:
Version1...4/11/13
Disabled perflock
Enable /system write
Download:
v1 - http://goo.im/devs/Flyhalf205/M7/Flyhalf205-boot-v1-m7.zip
Installation:
Download the file above
Flash .zip with TWRP Dumlock or extract boot.img from .zip
Boot into fastboot on your phone
Using a computer with fastboot comands.
fastboot flash boot boot-m7-img
Mine
Flyhalf205 said:
Mine
Click to expand...
Click to collapse
tested, without any issue, only wifi a bit slower than stock on my M7_U version (1.29.709.4 )
Thought more people would have been wanting this type of kernel lol
On your TWRP thread it says that with HTC Dumlock, we can flash kernels while s-on.
Does that apply for this aswell?
If not, I'll have to wait a few days until I've got access to a computer again.
KidCarter93 said:
On your TWRP thread it says that with HTC Dumlock, we can flash kernels while s-on.
Does that apply for this aswell?
If not, I'll have to wait a few days until I've got access to a computer again.
Click to expand...
Click to collapse
I've updated the zip in the OP. It should flash in TWRP Dumlock. No one that I know of has tested Dumlock with this deviceso good luck. Be sure to follow the steps exactly
Flyhalf205 said:
I've updated the zip in the OP. It should flash in TWRP Dumlock. No one that I know of has tested Dumlock with this deviceso good luck. Be sure to follow the steps exactly
Click to expand...
Click to collapse
I'll give it a try when I'm back from work later and let you know how it goes
Flyhalf205 said:
This is my first attempt at building a kernel. This is strictly a /system write kernel. In the future I may upstream and add features. I have built this from the latest source that came out (m7ul-3.4.10-jb-crc-ddcfb8c)
Changelog:
Version1...4/11/13
Disabled perflock
Enable /system write
Download:
v1 - http://goo.im/devs/Flyhalf205/M7/Flyhalf205-boot-v1-m7.zip
Installation:
Download the file above
Flash .zip with TWRP Dumlock or extract boot.img from .zip
Boot into fastboot on your phone
Using a computer with fastboot comands.
fastboot flash boot boot-m7-img
Click to expand...
Click to collapse
Greta work mate, what exactly is this perflock? Hear a lot about it these days
mwilky said:
Greta work mate, what exactly is this perflock? Hear a lot about it these days
Click to expand...
Click to collapse
perflock disables cpu frequency changes so with it off you can use setcpu etc to change frequency.
Does this work ok with any of the custom ROMs about (in using ARHD at the moment), and can we flash with CWM? It seems to flash kernels even with S-ON.
rovex said:
Does this work ok with any of the custom ROMs about (in using ARHD at the moment), and can we flash with CWM? It seems to flash kernels even with S-ON.
Click to expand...
Click to collapse
Must flash it with a computer or using HTC dumlock which no one has tested yet.
Sent from my ADR6425LVW using Tapatalk 2
Ok ill give it a try. I know that ARHD ROMs have a kernel built in that gets flashed in aroma with S-ON. Bit new to HTC flashing.
I'll have to look into that. That will be nice to use in this kernel on my next kernel.
Sent from my ADR6425LVW using Tapatalk 2
This flashed absolutely fine via Dumlock
Anyone want to give this kernel a go? http://goo.im/devs/Flyhalf205/M7/Flyhalf205-Freakazoid-v1-m7.zip Flash it with HTC Dumlock on TWRP or extract the boot and flash with a pc.
I've included a extra goodies for you guys. Not many.
Added lionheart
Wheatly
Hyper
Dancedance
Noop
Sio
Fiops
Maybe more but all I can remember.
Flyhalf205 said:
Anyone want to give this kernel a go? http://goo.im/devs/Flyhalf205/M7/Flyhalf205-Freakazoid-v1-m7.zip Flash it with HTC Dumlock on TWRP or extract the boot and flash with a pc.
I've included a extra goodies for you guys. Not many.
Click to expand...
Click to collapse
Changelog please
m3dd0g said:
Changelog please
Click to expand...
Click to collapse
Added changelog. Two post up.
Sent from my ADR6425LVW using Tapatalk 2
I'm running this kernel on Trickdroid 3.0.1, flashed with Dumlock fine. However I have no in-call sound through the earpiece. If I enable speakerphone I can hear everything fine, and it works through BT, just not through phone earpiece
Dunc001 said:
I'm running this kernel on Trickdroid 3.0.1, flashed with Dumlock fine. However I have no in-call sound through the earpiece. If I enable speakerphone I can hear everything fine, and it works through BT, just not through phone earpiece
Click to expand...
Click to collapse
Weird. What build number are you on?
Sent from my ADR6425LVW using Tapatalk 2
Not sure if this has even been explored yet but I've read qualcomm fast charge has been disabled for the One. Can anyone confirm this and is there a kernel mod to enable this?
Sent from my HTC6435LVW using xda premium
I am currently running Beekos PacMan ROM and I love it so far. I need a little help in flashing back to Viper before I go out of town. I was reading on MDMowers post about flashing back to an older ROM from the modded TWRP recovery. I am trying to install Viper back on my phone and use a recovery that is compatible with the apps2sd mod that is somewhere in the development section. Could someone help point me in the right direction or a quick explanation to what recovery I should use and which ones are compatible with apps2sd mod? I would really appreciate any help, info, links and of course your time.
Thanks In Advance!
TheGOAT232412 said:
I am currently running Beekos PacMan ROM and I love it so far. I need a little help in flashing back to Viper before I go out of town. I was reading on MDMowers post about flashing back to an older ROM from the modded TWRP recovery. I am trying to install Viper back on my phone and use a recovery that is compatible with the apps2sd mod that is somewhere in the development section. Could someone help point me in the right direction or a quick explanation to what recovery I should use and which ones are compatible with apps2sd mod? I would really appreciate any help, info, links and of course your time.
Thanks In Advance!
Click to expand...
Click to collapse
To properly install Viper on this phone, you must use a TWRP recovery. CWM variants will appear to work, but Viper install scripts will not work properly. If you love CWM, then you can use TRWP to install Viper, then change recovery to CWM...
Anything TWRP v2.6.3.0 or higher should work with Viper (and I think the apps2sd mod as well). Official v2.6.3.0 link
You may be able to use mdmower's TWRP 2.7.1.2 build (or higher) for fireball "Standard partition layout". Mdmower Fireball TWRP page
I also suggest flashing the Infernal Kernel for improved performance (and swipe-2-wake)
Huge thanks for all the info, it was exactly what I needed.