A
AndroidSlave
Guest
READ SEARCH = NO! = stock kernel = NO™any answer ??!!
Sent from my GT-N7000 using Tapatalk 2
READ SEARCH = NO! = stock kernel = NO™any answer ??!!
The new option to clean before a new rom install will fix thisYes I must have missed format system before when I reported an issue.(couldn't replicate it) I normally - format/system, data, cache, and preload. And then mount them all before flashing. This tends to bypass flaws in updater script.
Sent from my GT-N7000 using xda app-developers app
Nandroids do work as they are supposed. I fully tested them@philz:
hello mythical mod .. ehehe
however on the forum where I also recorded "androidiani.com"
a user with the 3.65 kernel has had problems with the nandroid backup ...
here is the error message:
"error while making a backup image of /data"
someone tell me if it is able to do a backup??
Philz thanks again for your wonderful work ...
jely bean would not exist without you ...:good:
edit: now another user and it did restore the backup without any problem ...
thx :laugh:Nandroids do work as they are supposed. I fully tested them
Sent from my GT-I9100 using Tapatalk 2
i also have no problems with backup.Nandroids do work as they are supposed. I fully tested them
Sent from my GT-I9100 using Tapatalk 2
- 3.70 --> 3.71: added format /preload on special wipe before install new rom
- Merge Koush last changes: (+ add credit inside code source)
- dedupe: fix buffer overflow, the length of key was incorrect, 4.2's libc detects the overflow and crashes
- fix bug where you cannot partition internal sd
- add wipe all before install ROM: wipe all user data + wipe system
- second pass at fixing partition sdcards menu by PhilZ, now it should work as supposed
Read post 2Hi Phil - just one clarification required and i am sorry to bother you. I see DDLRB-ODD link - currently the latest ROM for India is DDLRB (and not LR9) - is it safe for me to flash the DDLRB-ODD kernel image ?
Please advise.
- Can you implement overclock, voltage control, voodoo, special drivers... ?
This is a stock kernel, not recompiled from source. It is only repacked with changes in ramdisk to add new features and an enhanced cwm based recovery. I do not have plans to start building kernels from source. There are big names in the scene already doing a great job there.- Why I can't see your kernel version Phone / About dialog ?
That's how stock kernels behave. Version info is in build.prop and comes with the ROM. I can add it but won't as it is that way that stock kernels are supposed to work.
You can know the exact kernel version by typing in terminal: getprop
Also, in my recovery, there is an About dialog to give you more info about actual recovery which is also tight to kernel- Why your kernel drains more battery ?
It cannot be. It will act like stock kernel, not better, not worst- Does your kernel perform better than stock ?
Same answer as previous- Why sometimes I need to touch twice to validate an option in recovery ?
This is by design and not a bug. A special feature I added is the option to highlight/validate touched menu. After you scroll in a menu, your first touch will act as select without validation. This is to avoid any false validation during scroll, the worst limitation for many of the actual touch recoveries including original one- Will you implement exFAT support in recovery ?
Read this
http://www.epiccm.org/2012/06/why-not-exfat.html?m=1
I am still looking at it, but not sure it will be achieved any soon. Use FAT 32 meanwhile