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
CyanogenMod
CyanogenMod is an aftermarket firmware for a number of cell phones based on the open-source Android operating system. It offers features not found in the official Android-based firmwares of vendors of these cell phones.
Not Working:
FM Radio
Sources
Device: - https://github.com/SaNek011/android_device_huawei_u8500
Installation
Install ClockworkMod recovery
Boot into recovery using the 3-button combo (Call+Volume Up+Power button)
Wipe (wipe data/factory reset + wipe cache partition)
Install the ROM from the SD card using ClockworkMod Recovery
DOWNLOAD ROM - UPDATE_10
DOWNLOAD CWM
CWM 5.0.2.8 by $aNek011 (Fastboot version)
CWM 5.0.2.8 by $aNek011 (Recovery version)
DOWNLOAD Google Apps
GoogleApps - http://goo-inside.me/gapps
Changes:
Update_10:
Updated CyanogenMod Sources
New Wpa_supplicant v.0.6(Allows you to connect to hidden networks wifi)
Updated Kernel (It has become even more productive)
Patched audio library, new audio filter (sound became clearer) - http://review.cyanogenmod.com/#/c/17091/
-----------------
Update_9:
Updated CyanogenMod Sources (19.06.2012)
------------------
Update_8:
Kernel([email protected] #4)
Added HTC driver vocpcm.c
ZRAM Removed
-----------------------
New boot-logo
Auto-start load_oemlogo
Recompiled opengl
Added RAMZSWAP
Update_7:
Repo sync(14.05.2012)
Added CIFS to kernel
Added TUN to kernel
Working RomManager
Updated RomManager
Updated keylayout
Updated RootExplorer
New Splash Logo Huawei + auto-script SplashLogo
Update_6:
ZRAM(Integrated to kernel)
New libaudio
New Audiofilter
Update_5:
Repo sync (19.04.2012)
Fixed Brightness
Update_4:
Repo sync (18.03.2012)
Enabled JIT
Interface usb modem rndis changed to
Replaced by a camera on the original from the android 2.3.7
Proximity Sensors tweaks
Update_3:
Repo sync(15.03.2012)
New kernel
Optimized apk files
Unlock lock screen by pressing the MENU key - Disabled
New gralloc,copybit,lights,sensors
Update_2:
Repo sync (11.04.2012)
New libaudio
New AudioFilter
Updated kernel
New keylayout and keychars
Thanks
aorth - for device tree
psyke83 - for device tree
tilal6991 - for device tree
BPaul - for helping with development
destruct0r - for assistance in the implementation of htc vocpcm driver
Good work!
Good work! Keep up!
Whats new is in the update7?
______________________________________
[Send by Tapatalk 2 from my u8500]
Posted ClockWorkMod Recovery 5.0.2.8
thanks
My father thanks you
Today should be posted Update 7 By $aNek011!
added UPDATE_7
$aNek011 said:
added UPDATE_7
Click to expand...
Click to collapse
i'll try IT!!
I hope with this update, sygic gps mobile now works....
$aNeK! have you any idea for more of free ram?
not swap
Hi $anek!!
Any idea to work WIFI, because in wifi, options advanced say:
Macadress: no avalaible....
have u activated wifi?
mine is working just fine
NAZUnlimited said:
have u activated wifi?
mine is working just fine
Click to expand...
Click to collapse
yes, but no work!!!
in advanced option say: Macadress no avalaible........
can you help me and teach me , how can you done it?
moche_bcn said:
yes, but no work!!!
in advanced option say: Macadress no avalaible........
can you help me and teach me , how can you done it?
Click to expand...
Click to collapse
The mac isnt available because wifi is disabled
I'll suppose that one of these options is the one u experience
A) u turn wifi on and after a few seconds it say error
B) u turn wifi on and it auto-disable itself even before showing wireless networks or giving any error
Either one, in most cases, result from a bad flashing or the wifi files have the wrong permission, since i dont want to make u go to a goose chase after the permissions, flash the rom again but before do a full wipe (the normal + format boot + system. They are the advanced option) and fix permissions before reboot
Sent from my U8500 using xda premium
Muito Obrigado!!!
I am spanish speaker..
I'll try it!!!
Hi !!
Now work the wifi...
One question?.....
can I change in the nvram.txt,(In the path system/etc/firmware) the
macaddr=00:90:4c:14:43:01 for my macadress of my phone??
Can I add too direct to the folder system/app the current apks from google(googlequicksearch.apk, voicesearch.apk, vending.apk,maps.apk,etc) ? before install...
doing so, Can the ROM works?.....
Funny thing, in the other rom someone asked about the mac address too
In theory, u can do that, i havent tryed that, mine reports the correct mac (some things in every rom are weird, different results for the same kind of phone)
about gapps, yes, u can flash those apps at the system folder but before doing that, check if u have enough free space in that folder. Use the root explorer, enter that folder and see how much free space is there ( it is written above the file listing) and compare with the size of those apps. The rom just needs 10mb of free space in system to boot without any problems. Download the gapps zip for gingerbread and paste them inside the app folder of that zip and flash it. This way, if u want the updated versions of those, u can place them in the zip and flash, the new ones will replace the old ones. Just remember to fix permissions before reboot.
And yes u can flash them after flashing the rom, it wont affect boot just the time it needs to start the 1st time. Will take a minute (give or take) more to boot (more apps mean more time to write the dalvik cache, but it will only do that the 1st boot)
Sent from my U8500 using xda premium
hi
respect to fastboot
What is it for? can you teach me more about ?... forgive my ignorance.....
I just know to install the ROM's and clockwordmod ...
by the way, I installed the CWM 5.5.0.4 of $anek011
Update
I have to install all updates or just the latest?
Just the lastest
______________________________________
[Send by Tapatalk 2 from my u8500]
Description:
This android application, FlashImageGUI, is basically a GUI interface for the linux binary, flash_image provided by google in AOSP for loading custom kernels and recovery images onto the phone.
This app allows the flashing of kernels and custom recovery images in normal android mode!
Current Device Support:
Full Kernel, Logo and Recovery flashing: Samsung Moment, Transform, Intercept and Acclaim - the s3c6410 series of devices
Full Kernel (Anykernel and boot.img) Flashing and Recovery (zip file or image) flashing: HTC One XL, One S, EVO 4G LTE, EVO 3D CDMA and GSM, Amaze, Vivid/Holiday, EVO 4G, EVO Shift, Nexus 4, Nexus 10, Nexus 7, Samsung Google Galaxy Nexus (GSM & CDMA), Nexus S/Nexus S 4G & LG Optimus
Full Kernel (zImage) Flashing: Samsung Epic
Check application version for updates
Credits for HTC One XL Testing:
Special Thanks to: dorkboy69 and DvineLord
Old tester thread
Credits:
birbeck for the usual random java guidance, slushpupie for his previous java guidance, dodgejcr for extreme amounts of testing, and one_love_420 and shift for some great graphics!
testers: JT-, couga6442, happytweak and many others I might have forgot in the furry of three days I built the initial app from scratch.!
Thanks to SDX
Background:
flash_image (bmlwrite) is an extremely useful utility for flashing custom kernels, boot logos (so far ONLY Samsung devices) and recoveries. This binary has made it possible to easily flash all these items and is used almost everywhere behind the scenes (i.e. in custom recoveries, packaged into kernel /sbin, etc).
Custom Recovery
Supports both CWM and TWRP!
Future Support:
Will continue to test kernels as they are released to ensure compatibility!
Install Directions:
Install process is the same as any other .apk. Download to computer and adb push or mount sdcard on computer and copy over or download directly to the phone. Use any file manager, adb, connectbot/terminal emulator to install.
My preferred method, maybe a bit more technical: ./adb install c:\downloads\FlashImageGUI.apk
Download Locations
Market (99 cents!): Flash Image GUI
Release version (free): Flash Image GUI
Contact:
Any questions, comments, concerns, or issues, please post in this thread or send me an email! Thanks for all the help and support!
FAQ:
Q: Will this app support a marketplace to pick and chose kernels from?
A: No. Use Kernel Manager!
Screenshots:
{
"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"
}
Feedback:
Please post any helpful feedback. I'm always looking to improve the application!
HTC Unlock - User Guides for Flash Image GUI!!
HTC Unlock - Users Guide for ROMs with a Kernel (boot.img file):
1) Unlock using Official HTC method
2) Load this application, Flash Image GUI, onto the device, either through the Market or the link provided in this OP.
3) Download ROM .zip file to the sdcard on the device.
4) Open up Flash Image GUI, select Browse and select the ROM .zip file, downloaded to /sdcard in the previous step.
5) Flash Image GUI will provide a warning, reminding that the ROM .zip file will *need* to be flashed in the custom recovery afterward.
6) Flash Image GUI will index the full ROM .zip file searching for the kernel and kernel modules. Once located, the Flash Image button should be enabled.
7) Select the Flash Image button and Flash Image GUI will load the kernel modules and kernel from inside the ROM zip file.
8) Select reboot recovery.
9) Inside the custom recovery, wipe cache and dalvik-cache (consult specific ROM directions) then load/flash the ROM zip file.
10) Reboot to normal Android mode and all should work including Wifi!
HTC Unlock - Users Guide for flashing ONLY a Kernel (zip file):
1) Make sure the selected Kernel is compatible with the currently loaded ROM. If not, this will result in a lot of frustration!!! See troubleshooting steps below.
2) Download kernel zip file to /sdcard.
3) Open Flash Image GUI, browse and select kernel zip file, downloaded/loaded to sdcard in previous step.
3) Flash Image GUI will validate the kernel zip file is contains the minimum required files
4) Select the Flash Image button and Flash Image GUI will load the kernel and the kernel modules from the source kernel zip file.
5) Reboot
Basic Troubleshooting:
Troubleshooting after Rebooting:
First step, when experiencing issues flashing is to RE FLASH the files again. Many times, re flashing again will clear up any issues.
If not, as a courtesy, I've provided general guidelines and suggestions below.
If the device is not booting, the majority of the time, this is not related to Flash Image GUI and therefore outside the scope of this application and thread. Generally, the root cause is due to user error in flashing a bad kernel or wrong kernel/ROM combination. Please refer to other threads/posts to learn more about the specific device limitations imposed by the HTC unlock process and generally accepted practices of recovering from a mistake.
Issue #1: If the device hangs or reboots while on the splash screen, the kernel (or packaged ramdisk in the kernel) is NOT compatible with your device!!!
Solution for #1: 1) Boot into fastboot. 2) Load the custom recovery (Command: fastboot boot c:\downloads\recovery.img). 3) Flash a known good kernel or restore a previously known good nandroid backup
Issue #2: If the device hangs or reboots while on the boot animation, the ROM is likely NOT compatible with the kernel!!!
Solution for #2: 1) Boot into fastboot. 2) Load the custom recovery. 3) Flash a known good ROM/kernel combination either from a zip file or restore from a known good nandroid backup.
Sweet, that was quicker then expected.
Going to do a video review on this in a few hours.
Thank you dev for your hard work
Sent from my HTC One X using Tapatalk 2
Awesome app thanks for all your work
Sent from my One X using Tapatalk 2
Here is a video if you guys want to see it in action, I didnt know at the time but you can select the rom from the app and it will extract and install the boot.img for you so you dont have to extract anything like i did in my video.
http://www.youtube.com/watch?v=EP5dX23aZ1M
review
XsMagical said:
Here is a video if you guys want to see it in action, I didnt know at the time but you can select the rom from the app and it will extract and install the boot.img for you so you dont have to extract anything like i did in my video.
http://www.youtube.com/watch?v=EP5dX23aZ1M
Click to expand...
Click to collapse
Great video!
dorkboy69 said:
Great video!
Click to expand...
Click to collapse
Thank you, Ill get better with time lol.
Will this work on other android devices?
I'm using Sony and figuring on how to enable this feature!!!
Add the epic 4g??
Sent from my SPH-D700 using xda app-developers app
Allen Hu said:
Will this work on other android devices?
I'm using Sony and figuring on how to enable this feature!!!
Click to expand...
Click to collapse
henslo said:
Add the epic 4g??
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
Go to the market and look at the supported devices list people
Sent from my HTC One XL using Tapatalk 2
[APP] Flash Image GUI
joeykrim main thread, you can also catch him on freenode in #gen-dev
Allen Hu said:
Will this work on other android devices?
I'm using Sony and figuring on how to enable this feature!!!
Click to expand...
Click to collapse
Haven't had any knowledgable Sony testers. If you are familiar with ADB and a custom recovery, send me a PM and we can setup a time to test. Thanks!
henslo said:
Add the epic 4g??
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
Partial support, as indicated in the application and in the market. Tricky situation with that kernel being in two partitions. I didn't own the device and didn't have a tester with enough time to work out the kinks. If you're familiar with ADB and a custom recovery, send me a PM and we can coordinate testing. Thanks!
I'm loving this app I haven't used it for a ROM yet just kernels bit it makes it a breeze I bought 2 of them ( one for me on my account and one for the misses on hers)
Sent from my One X using XDA Premium HD app
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
I do have one request if possible can it have the ability to flash apps and what not
Sent from my One X using XDA Premium HD app
This app is sweeeet! :good: Sure saves a lot of hassle.
What exactly happens when you try to load a ROM zip and the app tries to zero in on the boot.img ? I see it loads a few lib files and finally flashes the boot.img as opposed to just pointing the app to the extracted boot.img and letting it flash it?
This makes switching Roms a breeze on the Hox 2.20 users that have to use fastboot for boot.img. This is a great and time saving app. Thanks Joey!!!
Sent from my One X using xda premium
ripnhack said:
I'm loving this app I haven't used it for a ROM yet just kernels bit it makes it a breeze I bought 2 of them ( one for me on my account and one for the misses on hers)
Sent from my One X using XDA Premium HD app
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
I do have one request if possible can it have the ability to flash apps and what not
Sent from my One X using XDA Premium HD app
Click to expand...
Click to collapse
Appreciate the support and positive feedback! Could you provide more detail along with your feature request? Perhaps could you link to an example set of "apps" you want the ability to flash? The more detail the better I can research and provide a good reply.
metalhead2791 said:
This app is sweeeet! :good: Sure saves a lot of hassle.
What exactly happens when you try to load a ROM zip and the app tries to zero in on the boot.img ? I see it loads a few lib files and finally flashes the boot.img as opposed to just pointing the app to the extracted boot.img and letting it flash it?
Click to expand...
Click to collapse
Great question. I suppose I should provide more information around this process in a FAQ or some type of supportive documentation.
Due to common HTC kernel standards, the WiFi module, as well as a few other modules are loaded externally, meaning they are separate files from the boot.img. Some manufacturers compile WiFi and other modules into the kernel zImage file which is a large portion of the boot.img file.
Flash Image GUI loads not only the boot.img file, but also loads the associated modules to ensure, if just a kernel is flashed, WiFi will work when the device is rebooted. In dealing with ROM .zip files, if the user promptly reboots to the custom recovery and flashes the same ROM .zip, the modules will be loaded twice and this makes the FIG feature more a safety feature than a necessity. In the case the user doesn't flash the ROM .zip from the custom recovery, for whatever reason, this process ensures WiFi will work with the kernel preventing any WiFi not working issues.
Hope that makes sense and provides a little more background!
cmky8132 said:
This makes switching Roms a breeze on the Hox 2.20 users that have to use fastboot for boot.img. This is a great and time saving app. Thanks Joey!!!
Sent from my One X using xda premium
Click to expand...
Click to collapse
Appreciate the feedback and support!
So if Im switching ROMs... going from sense to aosp. I flash boot img using app, enter recovery, wipe data and system and flash rom? Would it delete what I just did with boot.img?
Sent from my One X using Tapatalk 2
InflatedTitan said:
So if Im switching ROMs... going from sense to aosp. I flash boot img using app, enter recovery, wipe data and system and flash rom? Would it delete what I just did with boot.img?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Short answer: No
Longer answer: The boot.img is essentially a kernel and a ramdisk that following android's standards and is stored in a partition labeled as "boot", on most devices. Wiping the partition labeled "data" and "system" and copying over the ROM which goes into "system" will not delete the "boot" partition.
Hope that makes sense. Thanks for the support!
Thanks bro! Trying to help my buddy with flashing ROMs on the fly since his computer pooped on him haha.. awesome job on this app.
Sent from my One X using Tapatalk 2
joeykrim said:
Appreciate the support and positive feedback! Could you provide more detail along with your feature request? Perhaps could you link to an example set of "apps" you want the ability to flash? The more detail the better I can research and provide a good reply.
Great question. I suppose I should provide more information around this process in a FAQ or some type of supportive documentation.
Due to common HTC kernel standards, the WiFi module, as well as a few other modules are loaded externally, meaning they are separate files from the boot.img. Some manufacturers compile WiFi and other modules into the kernel zImage file which is a large portion of the boot.img file.
Flash Image GUI loads not only the boot.img file, but also loads the associated modules to ensure, if just a kernel is flashed, WiFi will work when the device is rebooted. In dealing with ROM .zip files, if the user promptly reboots to the custom recovery and flashes the same ROM .zip, the modules will be loaded twice and this makes the FIG feature more a safety feature than a necessity. In the case the user doesn't flash the ROM .zip from the custom recovery, for whatever reason, this process ensures WiFi will work with the kernel preventing any WiFi not working issues.
Hope that makes sense and provides a little more background!
Appreciate the feedback and support!
Click to expand...
Click to collapse
Thanks for the response some apps would be the android 4.2 camera with the gallery the 4.2 keyboard with emoji heres a link to a few http://forum.xda-developers.com/showthread.php?t=1970625
maybe custom boot & down animations (i usually disable mine but others may enjoy it)
That's all i can think of off the top of my head i hope that helps
AUTORAMDISK™ EXCHANGE PROJECT alpha™
『Moved by touch™』Inc.
In association with
Google Nose beta™
Presents
AUTORAMDISK™ EXCHANGE PROJECT alpha™
Current version: 0.0.0.0.072 Alpha
Created with Es explorer 1.6
Created on HTC explorer Pico a310e
Intro:
It's a common experience for newbies , when a new kernel is released by developers for a particular Rom and we want it for our Rom,but just can't wait for someone to change the ramdisk. For those, this is a noob friendly guide to change your ramdisk. And also, to make a universal zip for new kernel, so that no separate kernel zips for cm9,10,aokp exist.
Prerequisites:
Files:
New kernel boot.img and modules
Zip below
Software:
Android 2.3+ rooted
cwm 5+/twrp any other recovery with dump_image binary
Hardware:
Any Android smartphone
Features:
No PC/Linux needed
No different zips needed for different roms ~universal zip[One kernel-one zip project]
Credits:
trevd,rd for helping me along the way and for arm executable binaries .
So, a huge thanks to him.
Xda university
Procedure:
Short version:
Just add the new boot image and modules to generic kernel.zip and Flash on any Rom
Long version:
1.Download the generic kernel below
2. Open it with Es explorer 1.6 app
3. Select all and extract it into generic kernel folder
4. Download your favorite kernel.zip
5. Unzip your favorite kernel.zip into kernel folder
6. Copy boot.img from kernel folder to generic kernel folder
7. Copy modules present in /system/lib/modules in kernel folder and put it in /system/lib/modules in generic kernel folder
8. Now zip up your generic kernel folder and Flash
9. Voila
10. New kernel on any Rom.
11. So, is that easy /what?
Bugs and conditions
Even though this project is in alpha stage, if your Rom doesn't boot, blame the new kernel and your script first.
1. This is a simple method to change ramdisk and it doesn't work ,if you need anything more than that.
The binaries can also be used to open ramdisk and probably kernel as well using terminal emulator on your phone. If you face something unable to do on phone, go here for full PC workout
2. Essentially sense4 kernels cannot be used with this project to make it cm kernels,since it almost always need more work than just ramdisk changing
3. You need a working kernel present in boot partition. Wiping your boot and flashing will not work. It needs ramdisk from your phone and only updates the kernel part.
4. Does it work on other phones?
Yes. It bases itself on update script used. So, change update binary to suit your device
Try to change kernel address in the command for mkimg binary to make it work on other phones.
4.2 Does this mean that I can Flash kernel from any other phone to my Pico?
No. You can't. This only means you can Flash any other kernel made for other roms and your Pico to your Rom and Pico only.
4.3 Not tested fully guys.
Tired of 15 to 20 flashings to make it work. Test and try. I only tested aokp jb bhargz16`s kernel #1 on cm10b6 with twrp.
Reuse it,and try not to edit ui print and sleep parts
5. If it doesn't work, copy recovery log to SDcard and post here.
Original binaries from here
http://forum.xda-developers.com/showthread.php?p=36931024
(1.not the same script here~that is used to update ramdisk. This is used to update kernel and modified usage of binary to suit Pico
2. Without the binaries there, it would have been impossible. Don't forget to thank him. )
Reserved
LâTêS†↭ⓛⓘⓝⓚⓢ™CM10 HTC A310E.
If I haven't given you link, it's above. Just click it
Reserved 2
LâTêS†↭ⓛⓘⓝⓚⓢ™CM10 HTC A310E.
If I haven't given you link, it's above. Just click it
One more
LâTêS†↭ⓛⓘⓝⓚⓢ™CM10 HTC A310E.
If I haven't given you link, it's above. Just click it
All I can say is an ingenious piece of work bro. Nice use of the updaterscripts and good and simple way to swap ramdisks without much hassles.
:good: :good:
All the best !
akshat.shenoy said:
How does this work ?
All the best !
Click to expand...
Click to collapse
It's ramdisk changer... uses arm executable binaries from trevd to unpack and remake boot.îmg to change ramdisk.
Literally, it changes only kernel and doesn't touch ramdisk and so, we can use universal zips for cm7,9, 10,aokp.
That's the aim..
LâTêS†↭ⓛⓘⓝⓚⓢ™CM10 HTC A310E.
If I haven't given you link, it's above. Just click it
New poll added. Just fill up the no poll, if you don't like it.
Thread cleaned
Cleaned thread of some nonsense. Some ppl have to learn the hard way to not post spam or OT obviously
Deleted: Never mind
ptcpayme said:
New poll added. Just fill up the no poll, if you don't like it.
Click to expand...
Click to collapse
so that means now i can flash any kernel from any phone to my pico?? If not,plz explain.
THnx.
salil.bajaj said:
so that means now i can flash any kernel from any phone to my pico?? If not,plz explain.
THnx.
Click to expand...
Click to collapse
Without a kernel , we cannot use our phone. Learn more about " Kernels "
NOTE : Kernel == Boot.img ( Actual kernel is the zImage.. but never mind)
Yes we have to flash a kernel everytime we flash a ROM on our phone. It is simplified for our phone cause it gets flashed by itself ( thru the updater script )... And you could flash a kernel from our phone even normally thru
Code:
fastboot flash boot boot.img
What this tool does swaps Ramdisks of 2 kernels . Why is that useful ?
Cause then it makes one kernel of a particular ROM compatible with another ROM.
And I just forgot, this isnt the Q and A.
Got ya man!! Now this is really awesome work u hv cme up with!! :thumbup:
Sent from my HTC Explorer using xda premium
akshat.shenoy said:
Without a kernel , we cannot use our phone. Learn more about " Kernels "
NOTE : Kernel == Boot.img ( Actual kernel is the zImage.. but never mind)
Yes we have to flash a kernel everytime we flash a ROM on our phone. It is simplified for our phone cause it gets flashed by itself ( thru the updater script )... And you could flash a kernel from our phone even normally thru
Code:
fastboot flash boot boot.img
What this tool does swaps Ramdisks of 2 kernels . Why is that useful ?
Cause then it makes one kernel of a particular ROM compatible with another ROM.
And I just forgot, this isnt the Q and A.
Click to expand...
Click to collapse
Thanks for sharing usefull Information...........!!
Hey @BANNED i tried today and its working great. And nice updater-script troll.
Sent from my HTC Explorer A310e using xda app-developers app
thank you for your guide.
#-------------------------Disclaimer----------------------------#
I am in no way responsible for dead NAND/EMMC chips, SD cards Lost basebands, nuclear war or anything else for that matter YOU the users are soley responsible for any and all actions you make the build is 100% tested & confirmed working on UBIFS R11 max chinaphone with board variant Q6_M144_GT-018_MB_1.0
#-----------------------Device info----------------------------#
Android OS : 4.4.2 Kit Kat SDK:19
Kernel Version: 3.4.67
File System: UBIFS
BaseBand CPU: MT6572_S00
BaseBand CPU Secure Version: FF
BaseBand CPU Bootloader Version: 01
Board Variant: HS_Q6_MB_V1.0
Storage Capacity=512Mb (4Gb ext through recovery)
Ram Capacity= 497Mb
Resolution= 480×854
#-----------------CyanogenmodOS--------------------------#
Version = 11
SDK-ver = 4.4.4
SDK-API = 20
B-TYPE = userdebug
Build id = XNG3C
Linux Kernel = 3.4.67
LCD- density = 240
LCD-Dpi = 320
• Deodexed
• IO_scheduler set to CFQ
• Performance adjustments
• Preloaded with Gapps
• Cyanogen account support
• CyanogenMod Logo
• Ram flag optimisations
• Default runtime set to art
• Voice unlock support
• Pre rooted with Cyanogenmod SU 1.34
• addon.d support
• init.d support
• BT NFC support
• addon.d & init.d slinked in cpio in bootimg
• Custom CM bootimg with storage fix.
• Ad and popup blockers
• CM ambient updater
• CM InCallUi
• google voice search
• CM Device management
• CM SetupWiz
• factory test mode [ *#*#0#*#* ]
• CM Live lockscreen
• CM MusicFX
• CM Trebuchet Launcher
• Chrome based browser
• CM Voice +
• Voice command support
• Camera interpolated and tweaked
• camera path changed to added cameraserver in vendor/bin/cameraserver instead of system/bin/mediaserver
• Added Clearmotion props to default & build.prop
• Added Clearmotion config to /etc
• Added Clearmotion support libs
• Added Clearmotion FW to /lib
#---------------------------NOTICE------------------------------#
I do this in my free time DO NOT ask for Eta's,
Includes storage modified CM boot.img which will be flashed with the rom please use the partiton sd card option in advanced options in recovery to make up to a 4096mb /data partition before transferring zip to sd and flashing.
#----------------------------BUGS------------------------------#
• update #003 is having a whinge with storage for downloaded apps from store so they wont install after download will be fixed in build #004,
• NFC is working properly but you must purchase NFC bluetooth module tags to support nfc transfer, i have compiled & added an nfc.ko module to use bluetooth instead of newer modules which use the wifi reciever as the antenna and due to there being no NFC compatibile HW on these extremely poor low end devices i do not wish to see comments about this as a bug.
#-------------------------LINKS------------------------------#
CM CTR recovery.
https://drive.google.com/file/d/1UErBsSe2DLFEtcgwXz-hZR_fQINxpn9H/view?usp=drivesdk
Stock touch recovery to replace original
https://drive.google.com/file/d/14Y-WQHDLfqlEdjmu-PTujNqGkkUpcpLn/view?usp=drivesdk
CyanogenmodOS #001-BETA 20190412
https://drive.google.com/file/d/1Xuf-gSHPHr5CGsZjFu3pgT44FdR5GFx5/view?usp=drivesdk
CyanogenmodOS update #002 20190414
https://drive.google.com/file/d/19Nt1pVo8ruvTCugsgejtMQvJDe2xZIb7/view?usp=drivesdk
CyanogenmodOS update #003 20190504
[ Has play store issue ]
https://drive.google.com/file/d/1D4sCf1oflvSTFJxFzH1WwMJL_1j8H5-G/view?usp=drivesdk
Welcome to CyanogenMod 11
BUILD #002 is up get it from the OP
CHANGELOG
Camera works now with slow motion & fast motion video recording, picture quality is still **** but is tons better than it was on stock rom.
Rebuilt the system layout and merged most /vendor files and folders to /system
Fixed gallery keeps stopping error even though it wasnt
Cleaned up the GUI scaling to produce cleaner icons etc etc changelog is in /etc for anyone that wants to look
Changed the Live lockscreen wallpaper to something much simpler & better looking.
Converted entire system to single sim & removed Gemini where i could & set props to disable what i couldnt find of it, repathed ril to run through mtk-ril.so also added init.volte.rc, volte_imsm.so/volte_stack.files to help ril call clarity as certain parts of the stack are interacting with ril even though its a GSM Radio
Added getenforce & setenforce to /bin and file_contexts to try and get my init.rc props for setenforce to run the kernel permissively for some extra init processes, BUT setenforce for some reason is receiving permission denied cannot symlink so i hope to have this completed & working in build #003
Added /product/build.prop dir to deal with zram for swap & ext4 /data partitiion under logical boot partitions.
Added new android apple crime screen power off logo
Added some misc ringtones, notification tones and ringtones other than the cyanogen tones.
Nice Work Matty1993!!
You have been a busy bee :highfive:
Hello,
I am new to ROMs, Could you give me detailed instructions on how I would install this?
Thanks,
Robby
bigrammy said:
You have been a busy bee :highfive:
Click to expand...
Click to collapse
Haha yeah one of my old projects ive been meaning to get finished for ages, finding out how to attach android to UBIFS on top of UBI was a pain in the ass lol got to experiment with ril on this one as it was dual sim and tried running gemini through it but as it was a source build dual sim compatibility dosent work so had to depract gemini and set single sim still been working on the tuba build tho taking my time with it as sony really like to mix things up, also finishing a lineage OS 14.1 build for Alcatel Pixi 3.5 that was from source also but dualsim works on this one even though this phones a single sim phone haha go figure lol
DJ Robby said:
Hello,
I am new to ROMs, Could you give me detailed instructions on how I would install this?
Thanks,
Robby
Click to expand...
Click to collapse
What model is your R11 max clone phone it must be HS_Q6_MB_V1.0 board revision or it wont boot on your device and i will need to build one for your revision if so as the kernel will be different,
You can find the board variant by taking the backing off the phone and looking at the sim slot see pic attached,
Check this out first or youll brick it 100% i gaurantee it, google how to take a firmware backup using SP flash tool before doing anything SP flash tool can be downloaded from here aswell as the MTK Vcom drivers for flash tool,
https://spflashtool.com
If your board is different i need the BOOTIMG.file from your SP Tool backup so please do this first before anything or i wont be able to build you anything as i need your stock kernel from boot.img to decompile and make changes for my rom aswell as the boot.img is highly modifed with CM source
Hello,
I can't find a number like that, I looked everywhere.
Here is a full backup of the phone: https://drive.google.com/file/d/15P9KutXb0FrxHRTj4qrQ-KW94XA6J2SI/view?usp=sharing
The kernel is the same though because if I go to settings it shows the same kernel number as the one in this post.
Thanks,
Robby
DJ Robby said:
Hello,
I can't find a number like that, I looked everywhere.
I have the boot.img, I will edit this message with the boot.img when I have a chance. The kernel is the same though because if I go to settings it shows the same kernel number as the one in this post.
Thanks,
Robby
Click to expand...
Click to collapse
Hey mate the kernel number may be the same but the config of the kernel will be diff, if it dosent have a number in the sim slot it will deffo not be a HS_Q6_MB you may have the ZMA_12_MB or ZMA_9_MB board
So deffo dont flash any of this stuff if you get me the stock boot.img & recovery img from your R11 max i can build the recoveries and rom for your board revison just upload them here in a .zip file when you get the chance
Thanks
Matty1993 said:
Hey mate the kernel number may be the same but the config of the kernel will be diff, if it dosent have a number in the sim slot it will deffo not be a HS_Q6_MB you may have the ZMA_12_MB or ZMA_9_MB board
So deffo dont flash any of this stuff if you get me the stock boot.img & recovery img from your R11 max i can build the recoveries and rom for your board revison just upload them here in a .zip file when you get the chance
Thanks
Click to expand...
Click to collapse
I added the link to a full backup of the phone through the SP flash tool on my above post which includes the boot.img and recovery.img, Also thanks so much for all the help!
DJ Robby said:
I added the link to a full backup of the phone through the SP flash tool on my above post which includes the boot.img and recovery.img, Also thanks so much for all the help!
Click to expand...
Click to collapse
Hey mate,
Sweet ill get onto it and post link here to a new thread ill make for your variant r11 max.
Ive got a new build just about ready also which is build #003 so ill start your variant from #003 which has vast improvements from build #002
# edit
Glad you didnt flash your R10 is eMMC ext4 fs and not ubifs just finished the boot.img off anyhow
DJ Robby said:
I added the link to a full backup of the phone through the SP flash tool on my above post which includes the boot.img and recovery.img, Also thanks so much for all the help!
Click to expand...
Click to collapse
Try these recoveries tell me if they boot uo and everything is ok with them
Oppo touch recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1ZUZ3jmNhVkWSTB-57ifPh9_Lmm_jjkCB/view?usp=drivesdk
CWM recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1WO44rtoWttfeeAvCdff_97JqbuXboeXB/view?usp=drivesdk
Open sp flash tool & load your scatter file,
Then click on the recovery path and load a recovery into the slot,
MAKE SURE that download only is selected and NOT format all + download this is very very important
Click download with phone switched off plug into pc & recovery will now flash,
Once flash is complete remove then re insert the cord wait for the charging screen to appear,
You can now boot to either recovery by holding the volume up button and power button until the first boot logo appears then release only the power button and keep holding power up to see if they will boot or not,
If they boot all sweet ill upload the rom as its just about finished being built
Matty1993 said:
Try these recoveries tell me if they boot uo and everything is ok with them
Oppo touch recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1ZUZ3jmNhVkWSTB-57ifPh9_Lmm_jjkCB/view?usp=drivesdk
CWM recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1WO44rtoWttfeeAvCdff_97JqbuXboeXB/view?usp=drivesdk
Open sp flash tool & load your scatter file,
Then click on the recovery path and load a recovery into the slot,
MAKE SURE that download only is selected and NOT format all + download this is very very important
Click download with phone switched off plug into pc & recovery will now flash,
Once flash is complete remove then re insert the cord wait for the charging screen to appear,
You can now boot to either recovery by holding the volume up button and power button until the first boot logo appears then release only the power button and keep holding power up to see if they will boot or not,
If they boot all sweet ill upload the rom as its just about finished being built
Click to expand...
Click to collapse
I can try when I get home but I already got TWRP with the Easy Magic Installer except it is an older version: https://forum.xda-developers.com/showthread.php?t=2798257
DJ Robby said:
I can try when I get home but I already got TWRP with the Easy Magic Installer except it is an older version: https://forum.xda-developers.com/showthread.php?t=2798257
Click to expand...
Click to collapse
More or less just to test for device compat is all glad you told me youve got TWRP tho as my rom dosent have mount asserts in the script as they were causing error 7 so ill have to rebuild the meta-inf again as ive got set for perm aswell whereas TWRP uses meta-data to set file permissions
Matty1993 said:
More or less just to test for device compat is all glad you told me youve got TWRP tho as my rom dosent have mount asserts in the script as they were causing error 7 so ill have to rebuild the meta-inf again as ive got set for perm aswell whereas TWRP uses meta-data to set file permissions
Click to expand...
Click to collapse
So when do you think the ROM will be ready?
Edit: Oppo Touch Recovery works, I'd rather not bother with CWM if that's ok? And if you could port a TWRP instead of Oppo Touch Recovery I would appreciate that since it is more advanced.
DJ Robby said:
So when do you think the ROM will be ready?
Edit: Oppo Touch Recovery works, I'd rather not bother with CWM if that's ok? And if you could port a TWRP instead of Oppo Touch Recovery I would appreciate that since it is more advanced.
Click to expand...
Click to collapse
Rom will be ready soon it takes time to convert things to ext4 from ubifs patience is a must for these things unless you want a brick ? Lol plus ive got another 5 projects on the go so lots to do and not enough time to do it all, just finished lineage 14.1 android 7.1.2 for alactel pixi 4027A using a stock kernel on android 4.4.4
as for TWRP probably not due to the size of your recovery and the size of most twrp is about 3mb to short for your partition youll need to use cwm ive added mount points to the script for your data & system partitions so if it dont flash mount in CWM and then flash if it still dosent use the take a log option in my installer and forward it to me so i can see if it was the mounts or what,
Also i havent set meta-data for permissions ive set perm & perm_recursive which is specifically for CWM so please flash with that,
I make no gaurantee it will boot as i dont have one in front of me to work on & debug but everything should work ok though link will be up in roughly half hour max
Links up tell me if it installs and boots ok is based off my cyanogenmod 11 new unreleased build #003 for ubifs
CyanogenMod 11 R10
emmc + ext4
BETA TEST BUILD
https://drive.google.com/file/d/1CvP3TPjo5fxXi6tHKI388WFN5KnWTyZ4/view?usp=drivesdk
If it dosent flash remember to get the log from my modified installer
if it dosent boot past first logo tell me it will be fstab issue which ill need to adjust
If it gets stuck on infinite bootanimation tell me ill need to adjust the vold
If any errors just flash back your backup with SP flash tool using download only mode and youll be back up and running with it until i get it fixed if it does need fixing.
Matty1993 said:
Links up tell me if it installs and boots ok is based off my cyanogenmod 11 new unreleased build #003 for ubifs
CyanogenMod 11 R10
emmc + ext4
BETA TEST BUILD
https://drive.google.com/file/d/1CvP3TPjo5fxXi6tHKI388WFN5KnWTyZ4/view?usp=drivesdk
If it dosent flash remember to get the log from my modified installer
if it dosent boot past first logo tell me it will be fstab issue which ill need to adjust
If it gets stuck on infinite bootanimation tell me ill need to adjust the vold
If any errors just flash back your backup with SP flash tool using download only mode and youll be back up and running with it until i get it fixed if it does need fixing.
Click to expand...
Click to collapse
So does that mean Oppo Touch Recovery is useless? So I should just put CWM in the recovery and then flash the CyanogenMod11 with CWM If I could get more detailed instructions that would be helpful as you know I am a noob...
Edit: So I flashed it with CWM and it failed, Here is the log: https://pastebin.com/i2F55g08
What I think happens is the first image that says welcome comes up, Then the boot animation comes up but it doesn't finish before returning to the welcome image that was at the start and it stays on that forever.
Edit 2: I also don't know how to restore the backup with SP Flash Tool but that is ok since this isn't my everyday phone so i'll just wait until you fix the ROM.
DJ Robby said:
So does that mean Oppo Touch Recovery is useless? So I should just put CWM in the recovery and then flash the CyanogenMod11 with CWM If I could get more detailed instructions that would be helpful as you know I am a noob...
Edit: So I flashed it with CWM and it failed, Here is the log: https://pastebin.com/i2F55g08
What I think happens is the first image that says welcome comes up, Then the boot animation comes up but it doesn't finish before returning to the welcome image that was at the start and it stays on that forever.
Edit 2: I also don't know how to restore the backup with SP Flash Tool but that is ok since this isn't my everyday phone so i'll just wait until you fix the ROM.
Click to expand...
Click to collapse
Hey mate i took a look at the log,
For some reason it didnt symlink any of the system files or set the perms for them
Modified boot.img didnt flash either for some reason so surprised it started playing animation so all my adjustments from ubifs to ext4 must be correct
In the script
Format was ok
Mounting was ok
Extract system files was ok
I think it may have something to do with CWM possibly as thats the only reason its not booting none of the files have correct perms everything else went ok though, so ill see what i can do today about another recovery for you,
The oppo touch recovery is just a stock recovery i added to get rid of the 3e recoveries these phones originally come with, much nicer is all,
To restore your backup using SP flash tool open flash tool, select the scatter box,
Navigate to your backuo folder & double click on the scatter_file.txt,
All of your partitions and files will automatically load up for flash,
Change the download mode to download only
Power off phone click start download
Connect phone & wait for flash
I will just wait for the new Recovery and ROM to work because like I said before this is a device that I didn't use at all but I will probably use it once I get the ROM. Again I just want to thank you for all your help since because of you I don't need to throw out this horrible phone.