I've tried several times and searched around but just want to know is this update rootable and if so how
I believe some people reported it was possible by flashing the 2.3.5 through odin, then using odin to flash infusion 1.1 kernel which includes root script. then you can either use the infusion (RUXKG) kernel, or if you want the 2.3.5 stock kernel you can flash it back and the root should remain.
all 2.3.3+ roms need to be rooted on insecure boot (custom kernel) or pre rooted. rage against the cage was being used to push malware to android phones and that exploit has been locked out. so your choices are to use magic iso to push su and superuser.apk to /system/xbin and /system/app respectively in factoryfs.rfs from the odin/heimdall package and flash in odin/heimdall or to use odin or heimdall to flash the zimage from any one of the custom rogers kenrels
if you do this i would use entropys kernel as the wifi works do to initramfs mods pulled from the 2.3.5 kernel. problems with entropys kernel include no dock audio sound redirect (audio over usb) due to a bug with the voodoo port and no hdmi. infusion has audio over usb but no wifi or hdmi
flashing back to the factory 2.3.5 kernel will restore hdmi and work correctly but have no recovery (use kernel flasher from the market and keep a backup of the custom kernel you choose) and it doesnt have the custom tweaks (obviously) like init.d support, jhash update, memory mods, vm management mods, and voodoo so it is all a compromise till sources are posted. but removing the custom kernel will leave the phone rooted.
Dani897 said:
all 2.3.3+ roms need to be rooted on insecure boot (custom kernel) or pre rooted. rage against the cage was being used to push malware to android phones and that exploit has been locked out. so your choices are to use magic iso to push su and superuser.apk to /system/xbin and /system/app respectively in factoryfs.rfs from the odin/heimdall package and flash in odin/heimdall or to use odin or heimdall to flash the zimage from any one of the custom rogers kenrels
if you do this i would use entropys kernel as the wifi works do to initramfs mods pulled from the 2.3.5 kernel. problems with entropys kernel include no dock audio sound redirect (audio over usb) due to a bug with the voodoo port and no hdmi. infusion has audio over usb but no wifi or hdmi
flashing back to the factory 2.3.5 kernel will restore hdmi and work correctly but have no recovery (use kernel flasher from the market and keep a backup of the custom kernel you choose) and it doesnt have the custom tweaks (obviously) like init.d support, jhash update, memory mods, vm management mods, and voodoo so it is all a compromise till sources are posted. but removing the custom kernel will leave the phone rooted.
Click to expand...
Click to collapse
Wait, wifi DOES work in UCKI3/I4 with my kernel? I saw multiple reports that it still didn't. (e.g. my experiment failed.)
I may try tonight, now that I own two devices I can be a little more adventurous with one of them.
Related
Copied From ChainFire's Post
Click to expand...
Click to collapse
This rooted kernel is for the "rooting beginners" and those who want to keep as close to stock as possible. CF-Root takes the kernel from an original Samsung firmware, and just adds root, busybox, and ClockWorkMod (CWM4/5) recovery. For Galaxy Fit You Need To Flash Clockwork Mod Separately. The Kernel is Custom Supporting Ext4 FS, OC, UV and other Features
THIS IS NOT A ROM - it is only a modified kernel. You need to have the relevant firmware already on your device. You do NOT need to wipe anything for this patch. You DO need to read the instructions. PLEASE READ THIS ENTIRE POST!
Donate
Please Donate to Chainfire or Press Thanks button Here
Click to expand...
Click to collapse
There have now been nearly 1.000.000 downloads of CF-Root for various devices (see for example Galaxy S1, Galaxy Tab 7", and Galaxy S2), and many more if you include ROMs, kernels, etc that use it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user had donated me $1...
Features
- Root
- Busybox v1.16.2androidminimal (from CWM)
- Integrated CWM 4.0.0.2
- Integrated Tweaks Manager
- Running All Scripts in /system/etc/init.d
- Custom Bootanimation Workin on All Roms
CF-Root v4.1 and older
- Superuser 2.3.6.1
- In-Secure mode
Instructions - CWM
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Flash CWM Recovery.
- Download the File To Your Sd-Card
- Flash via CWM Recovery
- No Need to Data Wipe
- Initial/First Boot May Take Long Time,Very Long Maybe .
Other kernels
Replacing CF-Root with other kernels and vice-versa sometimes works, sometimes it doesn't. I don't have a list.
When going from CF-Root to another kernel, root will usually stay, while CWM will be lost (unless the other kernel also includes it), but there should not be issues. The CWM Manager app may remain, but probably won't do anything useful. For Galaxy Fit CWM Recovery Wont Go Flashing Other Kernels
CF-Root/CWM4 is NOT compatible with ROM Manager! Manage/perform your backup/restores from CWM directly or using the CWM Manager application included with CF-Root
- ADB is functional in recovery, however it may take up to a minute for it to start up after booting into recovery.
- When connected to ADB in recovery, you need to use "rootsh" command to get root, instead of "su". This will not prompt you, it will just give you root. Obviously the "rootsh" command does not work when booted normally.
CWM Manager
Because of incompatibility with ROM Manager, I wrote and included "CWM Manager". This is a new app (as of March 30, 2011). You can find it under Applications -> CWM. It is much faster to use than manually booting into CWM and selecting these options.
Features:
- Boot to CWM
- Backup firmware
- Restore backups (CF-Root v5.0: including partition selection)
- Delete backups
- Install APKs
- Flash CWM3/4/5 update.zip's
- Flash kernels (zImage, zImage in TAR, zImage in ZIP, zImage in TAR in ZIP) - without changing warning triangle status or increasing flash counter
--- without changing warning triangle status or increasing flash counter
- CF-Root v5.0: Flash complete firmwares (seperate files as well as .tar and .tar.md5 archives, dump files in /sdcard/external_sd/firmware folder)
--- without changing warning triangle status or increasing flash counter
--- can pre-root new firmwares during flash
Note: If you flash a different kernel, CWM Manager may remain installed. However, functions may not work, because they need kernel compatibility !
Custom boot / init scripts
CF-Root will execute the following scripts if present, in the order listed:
- /system/etc/init.d/* (there can be many files here, no extensions! use #!)
- /system/bin/customboot.sh (busybox sh)
- /system/xbin/customboot.sh (busybox sh)
- /data/local/customboot.sh (busybox sh)
Please make sure you chown / chmod the scripts correctly so they can be executed. Pretty much root:root / 755.
Custom boot animations and binaries
CF-Root also supports custom boot animations:
- /system/media/bootanimation.zip
- /data/local/bootanimation.zip
And custom boot binaries:
- /data/local/bootanimation.bin
Installing busybox over the included version
It is possible to install a custom busybox over CF-Root v3.0 and newer. However, this is not without risk. CF-Root makes heavy use of scripting, and many CF-Root scripts rely on the internal busybox version. If you do install a seperate busybox version (always use "stericson" installer!), install it to /system/xbin. Installing it to /system/bin will mess things up for sure. Even if you do that part right, it may still break CF-Root, so make sure to make a backup before trying.
How ?
I wrote my own toolchain to ease patching of initramfs, and that is what all this is based on. Took me a few days to get it to this state. If this works right, however, next time it will probably take me a few hours tops
Downloads (Will Work On Every GB Rom Formatted to Ext4 Partition)
Initial Release-http://www.mediafire.com/?y8242yhozcgvok6 (Flash via CWM Recovery)
Credits
-Chainfire (Please Donate Him or Press Thanks)
-Special Thanks To Ketut.Kumajaya
-zcop
What is that supposed to mean?
Sent from my GT-S5670 using XDA
Great Job Mr. Creed
CF Root kernel is very popular, now come to FIT device ^^
Congratulatioonnn
Hehe im a noob and i dont get it ... This will work on custom and stock roms or only on custom with ext4 support?
Sent from my GT-S5670L using xda premium
Can't you guys read its all described in the op
Sent from my GT-S5670 using xda premium
Mr.Oug said:
Can't you guys read its all described in the op
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
I read it ... But creed put something that made me confuse ... He put will work on every gb ext4 partition ... And the original post says its for stock ... So u tell me works on both or just in ext4 partition gb?
Sent from my GT-S5670L using xda premium
Deshabilitado said:
I read it ... But creed put something that made me confuse ... He put will work on every gb ext4 partition ... And the original post says its for stock ... So u tell me works on both or just in ext4 partition gb?
Sent from my GT-S5670L using xda premium
Click to expand...
Click to collapse
nt stock for us , because our stock kernel dosnt support ext4 ,which is required by the CWM,CWM app and tweaks manager !!! i will soon add a way to make stock roms cf-root and cwm supported !!
I add this one nice job Thanks. it works nice
Sent from my GT-S5670 using xda premium
pratyush.creed said:
nt stock for us , because our stock kernel dosnt support ext4 ,which is required by the CWM,CWM app and tweaks manager !!! i will soon add a way to make stock roms cf-root and cwm supported !!
Click to expand...
Click to collapse
that would be nice, thanks Creed
Jus tell guys if the bootanim is working/
I hope u do something to make stock kernel ext4 support and that way use this
Sent from my GT-S5670L using xda premium
Deshabilitado said:
I hope u do something to make stock kernel ext4 support and that way use this
Sent from my GT-S5670L using xda premium
Click to expand...
Click to collapse
if i mod the stock kernel to add ext4 support it will be called custom kernel, kernels cant be modified they cn be built only !!
Thanks waiting for it...
pratyush.creed said:
if i mod the stock kernel to add ext4 support it will be called custom kernel, kernels cant be modified they cn be built only !!
Click to expand...
Click to collapse
What kernel base for is it?
for CM?
I think it works on Rom using ext4 fstype.
If there ppl.using stock.
Just format em to ext4, and flash a kernel.
Kernel base CM can be used on GB ROM (not CM), too.
I jst share my opinion n my experiences
Sent from my GT-S5660 using Tapatalk
Delanoister said:
What kernel base for is it?
for CM?
I think it works on Rom using ext4 fstype.
If there ppl.using stock.
Just format em to ext4, and flash a kernel.
Kernel base CM can be used on GB ROM (not CM), too.
I jst share my opinion n my experiences
Sent from my GT-S5660 using Tapatalk
Click to expand...
Click to collapse
not fr CM.
i usd chainfire's Ext4 convert app bt it didnt workd, i will try with cwm flashable scripts...do u have one ??
Just Refreshed this Cf-root ..
*Removed that Boot Splash of Creed(i forgot to remove it before )
*New Kernel
*OC upto 870Mhz
*New Shedulers
I havnt tested it, cuz my phone has gone for repairing ...
someone pls test if this is stable or not..so that i can add this to the main thread!!
Flash via CWM ...working on all roms
pratyush.creed said:
Just Refreshed this Cf-root ..
*Removed that Boot Splash of Creed(i forgot to remove it before )
*New Kernel
*OC upto 870Mhz
*New Shedulers
I havnt tested it, cuz my phone has gone for repairing ...
someone pls test if this is stable or not..so that i can add this to the main thread!!
Flash via CWM ...working on all roms
Click to expand...
Click to collapse
870 Is it a good idea.... o_0
Was running Gee One's 9.2.1.17 rooted stock ROM ( http://forum.xda-developers.com/showthread.php?t=1552303) + guevor kernel 17c and init.d scripts ran fine.
Recently wiped everything with Android HD wipe script to start over and install 9.2.1.24 via instructions: http://forum.xda-developers.com/showthread.php?t=1634634
However, my init.d scripts won't run at boot. I have guevor's kernel flashed and busybox installed. I can manually run the script and it works, but it doesn't run automatically at boot.
The script I'm running is at: http://forum.xda-developers.com/showthread.php?t=1433436
Help?
EDIT: Redid everything again but this time flashed TastyMeh kernel which worked with init.d scripts just fine. But the script still won't run at boot. Must be something with the ROM. I'll just use Script Manager as a clunky workaround.
No matter what I tried via kernel modules (mmcfix), I was not able to fix the issues with writing to certain sdcards under 2.6.29 kernel (of our 'vulnerable' recovery that we use to start OpenRecovery).
So I decided to give a try to 2ndboot from 2.6.29 to 2.6.32 kernel under recovery.
Here is a version of OpenRecovery 1.46 that runs under custom 2.6.32 kernel using 2ndboot:
Download: http://code.google.com/p/cyanogenmod4milestone/downloads/detail?name=OpenRecovery_2ndbootOR_v1_2.zip
Fixes:
- all issues with writing to some sdcards under recovery ("DMA transaction error with device 61" in dmesg)
- missing huge_file feature of ext4 filesystem under recovery
New features:
- battery charging under recovery
Please let me know if you encounter any problems.
The start of OpenRecovery with 2ndboot takes a bit longer, so be patient.
You can see a phone reboot during the start of OR under certain conditions - it's intentional, just wait, the OR will start automatically afterwards.
Kernel source: https://github.com/nadlabak/kernel/tree/recovery
UPDATE 30.01.2013
- prevent watchdog reboot (by automatic reboot of recovery if it was not started via /cache/recovery/command)
- use 10% battd for better compatibility with 3rd party batteries
- modversion set to 2ndbootOR v1.2
UPDATE 03.11.2012
- kernel and 2ndboot files updated (2.6.32.60, L2 cache enabled etc.)
- patches by justcsdr from issue #773 included (power off, mass storage with complete access to all sdcard partitions etc.)
- modversion set to 2ndbootOR v1.1
UPDATE 26.09.2012 (2)
- fixed linker issues - IMPORTANT! please update from the previous version
- modversion set to 2ndbootOR v1.0
UPDATE 26.09.2012
- battery charging and status display added
UPDATE 23.09.2012
- workaround for occasionally non-working adb
- clean kernel build (no change in functionality)
UPDATE 21.09.2012:
- fixed backup of logo, bpsw, lbl and devtree partitions
- added 2ndboot splash screen
Seems to be working for me. No issues
Sorry for the dumb question, but what is the purpose of this OR?
Erovia said:
Sorry for the dumb question, but what is the purpose of this OR?
Click to expand...
Click to collapse
Read the first post...
LuigiC6 said:
Read the first post...
Click to expand...
Click to collapse
Oh god, i really should go to sleep..
By the way, i tried it, works fine, no issues so far. :good:
Works great, slowest but for me without issues
Now my nandroid backups are not hanging on system dump anymore. Great work man. Thanks a lot.
Update:
- fixed backup of logo, bpsw, lbl and devtree partitions
- added 2ndboot splash screen
Download: http://d-h.st/AeS
Kabaldan I have one question.
Is there possibility to run rom on this second kernel? Maybe this is the way to make kernel more complatible for rom
Just a suggestion/question - can't you change version numbers so not to confuse new 1.46 with old 1.46?
DJPatriX said:
Kabaldan I have one question.
Is there possibility to run rom on this second kernel? Maybe this is the way to make kernel more complatible for rom
Click to expand...
Click to collapse
DJ,
As far as I understand, Rom already runs on this "second" kernel. This second kernel is the Motorola Froyo Kernel, recovery was using an older kernel to boot. Both are signed by motorola, so, it is not a custom kernel.
It actually is a custom kernel (2.6.32.59), not signed by Motorola (the last kernel released by Motorola for Milestone is 2.6.32.9 from early 2011).
Check 'cat /proc/version' and see when it was compiled .
You could even use swap with this kernel, if it would make sense under recovery .
But you're right that it's not the main point - this OR release is about recovery to be run under 2.6.32 kernel to achieve reliability in sdcard operations, which was not possible under 2.6.29 kernel of our old recovery.
The problem with 2ndboot (or kexec) method to run custom kernel is that there is no known way to get the Wrigley 3G BP working afterwards (BP = Baseband Processor - the gsm/umts phone features).
This is fine under recovery as the phone functionality is not needed there.
But there's no known way to run a custom kernel on Milestone (or any other Wrigley 3G BP phone such as Defy(+), Milestone 2 etc.) while the device would still be able to function as a phone.
Thanks for the update. Seems to be working fine. Console, nandroid backup/delete (haven't tried restoring yet), scripts...
Btw., indeed very nice 2nd boot splash image
Thank you
Thank you for this update, everything is working just fine!
the dl-link does not work for me. could you reupload it, please?
As dev-host seems to be off-line, I've uploaded new update to issue-tracker site
http://code.google.com/p/cyanogenmo...nRecovery_v1_46_SHOLS_2ndboot_2_6_32_kern.zip
UPDATE 23.09.2012
- added workaround for occasionally non-working adb
- clean kernel build (no change in functionality)
Thanks for the reply. I've seen some issues with radio an other roms who runs on "second kernel". Now everything is clear 4 me.
Cheers
battery charging under recovery added
Link
That is amazing... Thank you.
Btw., you might have forgotten a link http://code.google.com/p/cyanogenmo...1_46_SHOLS_2ndboot_2_6_32_Charge.zip&can=2&q=
New version uploaded:
http://code.google.com/p/cyanogenmod4milestone/downloads/detail?name=OpenRecovery_2ndbootOR_v1_0.zip
It contains important fix for a nasty bug introduced with the addition of battery charge support. Please update.
TouchWiz-4.4 ROM FIXER for Developer Edition devices
WARNING: These files are for Developer Edition devices ONLY. Kernels cannot be flashed on the retail VZW Note 3 devices!
THIS PROCESS ALSO SETS KNOX 0x1
Own a DevEd? Flashed the firmware/modem bits to the new TW4.4 in hopes of seeing some of the improvements or running a stock-modded ROM?
FIRST: Big shout out to @Imoseyon who has a VERY nice kernel for unlocked devices here:
http://forum.xda-developers.com/showthread.php?t=2488082
Go over there and tell him thanks, because I had spent a day or so trying to fix up a boot.img but wasn't having much luck due to a crash in TIMA memory. But, then I read that someone had gotten the leak booted w/ Imoseyon's kernel and was able to rip it apart and pull just the absolute minimum changes to get a VERY close to stock kernel / ramdisk setup for the 4.4 leak.
WHAT IS THIS?
Several issues were noticed immediately on DevEd devices due to the fact that we can't flash certain portions of the updated ODIN files (aboot, sbls, etc):
Play Movies won't stream
External SD card won't mount
Lockscreen settings don't work
Imoseyon's kernel was the only boot.img which would run 4.4 leak due to aboot/devicetree changes and TIMA crashes
The files below fix these issues and provide a VERY close to stock boot.img for use on DevEd devices.
FIX FILES: 2 flashable .zip files (for use in recovery):
1st flash.zip file is for a new stock-based kernel with CONFIG_TIMA disabled, dt.img created from NC2 sources but combined with 1st ed dtbTool, and default.prop changes for disabling TIMA, securestorage and KNOX (default.prop changes pulled from Imoseyon's leanKernel 2.4 -- thanks!) This file only needs to be flashed once (as long as you don't swap to AOSP ROMs). You can also use leanKernel by @Imoseyon if you like his work. The difference between this kernel and his are: I used the identical settings as the stock NC2 kernel (Kernel modules are enabled, etc) in an attempt to eliminate as many differences between the DevEd and the retail device. His kernel has a TON of tweaks and updates. But, could in theory have issues running the stock NC2 VZW leak.
Kernel source: https://github.com/Hashcode/android_kernel_samsung_hlte/tree/hlteatt-kk-nc2
2nd flash.zip file is a set of file changes which fix the issues noted by DevEd users on the leak (this file should be flashed after EVERY TW-based ROM is flashed)
Downloads:
Mirror 1 (Goo.im)
Mirror 2 (Crackflashers)
Instructions:
Download the above files and place them on your device's storage
Reboot into recovery
Flash flash-vzw-de-4.4-kernel-v1.0.zip if you need to fix kernel (coming from AOSP)
Flash flash-tw44-sys-files-fixes-v1.0.zip after ANY flash of TW-based 4.4 ROMs to fix system files
Reboot, no need to wipe cache, etc
XDA:DevDB Information
TW-4.4 ROM-FIX DevEd Devices, a Tool/Utility for the Samsung Galaxy Note 3
Contributors
Hashcode
Version Information
Status: Beta
Stable Release Date: 2014-04-27
Created 2014-04-27
Last Updated 2014-04-27
Reserved
Thanks
Sent from my SM-N9005 using Tapatalk
How do you know if you have a DevEd device?
Any way to check it? Just curious
Edit: Nevermind... just found it
Only for Veryzon
I used this script to make my rom to be flashed on multiple variants with different kernel, ideal for Samsung devices but it will work on any device, either use whole script or just use the kernel flash script
Master branch includes full script including rom, kernel and magisk flash
Experimental branch includes only kernel flash script (copy and paste to end of your updater script)
https://github.com/Dyeide/multikernel-flash-script