Android Kitkat 4.4.4
Let’s emphasize that-- THIS IS AN ALPHA, RELEASED FOR YOU TO PLAY WITH AND GET A SENSE OF WHAT’S TO COME. AND SOME THINGS DOESN’T WORK. REALLY. IF YOU ARE EXPECTING ANYTHING CLOSE TO PERFECTION, WALK AWAY FROM YOUR COMPUTER, LOWER YOUR EXPECTATIONS FOR AN HOUR OR SO, THEN COME BACK. MORE EXCITING DISCLAIMERS/WARNINGS IN ALL CAPITAL LETTERS CAN BE FOUND BELOW. READ THEM.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
KNOWN BUGS (what doesn't work):
- Modem in 2G mode work incorrect(Network registration don't work with some SIM cards, permanent full signal straight, problem is with audio in calls)
With 3G all is OK, Use this: Settings -> More.. in "wireless&network" category -> Mobile Network -> Preferred Network type -> 3G only
- Conference Calls
- Some problems with audio codec settings, but generally it should
- After Recovery time to time incorrect capacity of battery
Maybe something else, what i forgot
SUPPORT
You get none. Zero. Zip. We obligate ourselves to providing nothing further. You are on your own and will have to help each other via this thread. This is provided “as-is”, and if you don’t like it, use Bada or other releases.
We basically lack time to give full dedication to this rom, and we’re looking for skilled devs who know the Android, and/or other things that might be relevant.
Please join us on IRC: some people are on #badadroid (freenode).
NOTE: DEVELOPERS WANTED. Please contact us if you are a developer with something to contribute.
I do heavily encourage to work together on the better, common project instead of making kang releases and demanding money for somebody else's work.
Read as: If you think you can make something better than this by doing less and muchazo Ctrl+C Ctrl+V - you suck, go figure the rest.
INSTALLATION
FIRST INSTALLATION
Bada 2.0 is required
Warning! It will remove Bada!
Download BOOTFILES, Kernel and FOTA for your device:
for 8500:
BOOTFILES https://yadi.sk/d/KhxqKyg4bP2nu
"start" kernel https://yadi.sk/d/PhY11Rvnmq99T
FOTA https://yadi.sk/d/OtpVoaXpfNggE
for 8530
BOOTFILES https://yadi.sk/d/cBPD41VEbP2od
"start" kernel https://yadi.sk/d/xWwb8r3RmpZxK
FOTA https://yadi.sk/d/-WnbHbFHfNgZK
Flash BOOTFILES, "start" kernel and FOTA using Multiloader.
After reboot it will open android recovery
Advanced -> Terminal Command -> Select -> Type "sh partition.sh"
wait before on screen you will see "Partitions had been prepared"
if you have external SD card:
- Back -> Back -> Back -> Mount -> Mount USB storage
On PC you will see SD card mounted, and copy ROM there -> Unmount -> Back
- Install -> choose zip with ROM(mount point /external_sd) -> Swipe to Confirm Flash -> Reboot System
if you have no external SD card
- Back -> Back -> Back -> Reboot -> Recovery -> Swipe to Reboot
- Mount -> Enable MTP (if you see disable MTP - it is already activated) on this step PC can ask to install driver, use Android MTP driver
- Copy Zip with ROM Internal Storage -> Disable MTP -> Back
- Install -> choose zip with rom -> Swipe to install -> wait for flashing -> Reboot system
Enjoy OMNI!
You can remove installation .zip from Android level by connecting through USB in MTP mode.
TWRP Recovery mode is available using VolUp + End keys
Every next update you can just flash .zip through CWM.
UPDATE from OMNI older that 09.09.2014
- Make backup in TWRP(Backup -> Select Data -> Swipe to backup)
- Flash FOTA and "start" kernel via Multiloader
- Advanced -> Terminal Command -> Select -> Type "sh partition.sh"
- wait before on screen you will see "Partitions had been prepared" -> Back -> Back -> Back
- Mount -> Mount USB storage
- Copy zip with Rom from PC to External SD card -> Unmount -> Back
- Install -> choose zip with ROM -> Swipe to Confirm Flash -> Home
- Restore backup in TWRP (Restore -> Select packge for restore -> Swipe to restore)
- Reboot -> System
For activation Performance and Developer Options categories in Settings you need Settings->About Phone and tap 7 times on Build number
ROOT
Omni is without root support from default
To activate root flash zip via Recovery from XDA thread http://forum.xda-developers.com/showthread.php?t=1538053
GAPPS
GAPPS make our ROM slowler, because also slim GAPPS take about 15-20 MB RAM permanently
SLIM GAPPS: http://d-h.st/users/ZordanKV/?fld_id=28623#files
HOW TO UNINSTALL
Just reflash bada via Multiloader
CHANGELOG:
26.01.2016 https://yadi.sk/d/lY5ZEJc6noBVH
- Big kernel update from https://github.com/Coldwindofnowhere/android_kernel_samsung_aries/tree/android-5.1
Big thanks to @Coldwindofnowhere
It enable many additional settings in Settings-Performance
Also enabled boost for incall volume in Advanced Settings
- Added Battery saver mode from Omni Gerrit, Experimental- not really tested
- GPS fixes, still we have no A-GPS
11.01.2016 https://yadi.sk/d/pTSrLBykmpVVz
- Omni sources 11.01.2016
- Sensors update and cleanup
- Added Bigmem support in Advanced settings
with default settings we have 270 mb RAM with working 720p video recording
with Bigmem we have 283 mb RAM without working 720p video recording(as was by default in previous versions)
with Max RAM we have 315 mb RAM and camera, video playback and torch is not working at all
- Updated kernel with last omni changes
RIL update 20.12.2014 https://yadi.sk/d/kvYUiq6QdWSdD
- SMS fixes
just flash it via TWRP
11.12.2014 https://yadi.sk/d/80q05wvrdKW3t
- Omni sources 11.12.2014
- Added roaming indication
- Re-worked SMS
- Updated some Zram parameters
maybe something else
25.10.2014 https://yadi.sk/d/qCh-swftcJ7tg
- Omni sources 25.10.2014
- Moved to omni aries kernel
- Updated audio driver
- Updated charger driver
09.09.2014 https://yadi.sk/d/H5lEBmQvbLiSH
- Omni sources 09.09.2014
- New partition layout and new installation procedure(Read carefully! Device will be wiped).
Now you can use android without SD card
- Compass fixed
- Added phone reboot in case of modem crash.
15.08.2014 https://yadi.sk/d/jKCEMrAEZkZGr
- Omni sources 15.08.2014
- Hopefully fixed LCD wake-up bug on wave2, thanks to Blue59 for so many tests
- Corrected voltage for some on-board chips
13.07.2014 https://yadi.sk/d/DoaSRX3EWY9Hk
- Omni sources 13.07.2014
- Fixed updater script
- Fixed power off, thanks to Tigrouzen
11.07.2014
Updated FOTA links
Changed background from white to black
Added start of Bada - Call+End, we can use offline bada charger, in case if battery is fully empty
Added checking kernel size on SD card, sometimes boot.img exist but it is 0mb
04.07.2014 https://yadi.sk/d/Rw2UmkaoVxwdP - forgot to fix updater script, so please re-copy boot.img manually to SD card
- Omni sources 04.07.2014
- Small kernel optimizations
- Bring back Advanced Settings (TVout, vibration intensity and etc )
- Updated framework overlay
- Added OmniTorch
- Added USD OTG support (not tested), based on http://forum.xda-developers.com/showpost.php?p=53803247&postcount=8 Thanks to Tigrouzen
29.06.2014 https://yadi.sk/d/M0XEIgJMVTtCi
- Initial Release
THANKS TO
Special thanks to Rebellos for his CM10 ROM, for his good sources and many time, what he spent for my learning
Another Badadroid devs: Oleg_k, mijoma, nbates66, anghelyi, mikegapinski, hunktb, autra, Tigrouzen, Benzox and many others.
OMNI team for base ROM
Pawitp, kasper_h and all other aries developers
Paulk and Replicant project for good base for bada-modem RIL
and many other who help us.
Reserved
great work and really great rom thanks @volk204
i want install rom but no mount sd card on recovery wave 2
full flash bada but again no mount sd card
nima.yavari said:
i want install rom but no mount sd card on recovery wave 2
full flash bada but again no mount sd card
Click to expand...
Click to collapse
Mount point for SD card is /external_sd
Today Blue59 installed it successfully on Wave2
Also try to catch recovery.log via ADB http://rootzwiki.com/topic/24120-how-to-get-a-log-from-twrp/
volk204 said:
Mount point for SD card is /external_sd
Today Blue59 installed it successfully on Wave2
Also try to catch recovery.log via ADB http://rootzwiki.com/topic/24120-how-to-get-a-log-from-twrp/
Click to expand...
Click to collapse
change format sd card fat to fat32 correct
thanks blue59 and volk
Quick Review
USB OTG for badadroid kernel KitKat rom :
https://github.com/Tigrouzen/android_kernel_samsung_wave
This example based on ICZen(ICS) KitKat's very different :
vold.fstab :
Code:
dev_mount usbdisk /mnt/usbdisk auto /devices/platform/s3c_otghcd/usb
init.wave.rc :
Code:
mkdir /mnt/usbdisk 0000 system system
symlink /mnt/usbdisk /usbdisk
storage_list.xml (device/samsung/wave/overlay/frameworks/base/core/res/res/xml/) :
Code:
<storage android:mountPoint="/mnt/usbdisk"
android:storageDescription="@string/storage_usb"
android:primary="false"
android:removable="true"
android:allowMassStorage="true" />
Where is the link for FOTA ??
@Tigrouzen
Can i use Zendrokat FOTA and BOOT?
FOTA SD
couldn't find link for FOTA SD on other forums. can anyone supply?
Ok, it works with Zendrokat fota. But me and my friend (he flash your fota) cant install ROM. Because we have error next to formating. Updating partition details and Failed. How to repair it? ;/
thanks man ...
Hey "wavers" how 'bout the performance ?
I am able to install zendrokat v2.2 but this one is so hard.. Always some error please guys a clear demo or a video on flashing will be very helpful. I really love to try this rom as its very slim.Thanks. B.R:good:
msprakashmmc said:
I am able to install zendrokat v2.2 but this one is so hard.. Always some error please guys a clear demo or a video on flashing will be very helpful. I really love to try this rom as its very slim.Thanks. B.R:good:
Click to expand...
Click to collapse
As explained in OP,
-Flash bada 2.0
-Flash BF and Fota (SD fota)
-Put all files on SDcard
-Boot recovery, choose flash zip, go to /external-sd and choose the zip.
-this part is important : "- Wipe -> Advanced wipe -> Check "data" -> Repair or change File Sytem -> Change File System -> Ext4 -> Swipe to change ->Back -> Back ->Back -> Back "
-reboot, enjoy.
if you do this carefully step by step, it will work
BenzoX said:
As explained in OP,
-Flash bada 2.0
-Flash BF and Fota (SD fota)
-Put all files on SDcard
-Boot recovery, choose flash zip, go to /external-sd and choose the zip.
-this part is important : "- Wipe -> Advanced wipe -> Check "data" -> Repair or change File Sytem -> Change File System -> Ext4 -> Swipe to change ->Back -> Back ->Back -> Back "
-reboot, enjoy.
if you do this carefully step by step, it will work
Click to expand...
Click to collapse
where's the FOTA SD
Help help help
I have copied kernel and zip
Run recovery
Wipe all complete no error
Try to install zip
Updating partition details
Failed.
What i make wrong?
//
@BenzoX
Thank you. you are the best. Big thanks Bro for help!
my phone has gone in to boot loop. It starts with samsung 8500 then switches off then again starts and switches off and so on. If i try to go to download moad then it goes but again restarts. I cannot hold on a screen so cant even reflash bada...
If i try to go to download moad then it goes but again restarts.
Click to expand...
Click to collapse
If DL Mode not stable... then 2 reasons possible.
With luck only Battery empty.
So charge battery external... or use other battery...
If no luck...
Then Bootloader could be damaged or something else bad...
Best Regards
nileshlog said:
my phone has gone in to boot loop. It starts with samsung 8500 then switches off then again starts and switches off and so on. If i try to go to download moad then it goes but again restarts. I cannot hold on a screen so cant even reflash bada...
Click to expand...
Click to collapse
Battery probably empty, either boot any recovery and let it charge for a while, or plug phone and let charge on bada charge mode, or do it with some wires and a 5v power supply...
Then you should be able to go on DL mode.
Related
This is a custom recovery based on Cyanogen's recovery source with a lot of things added by me. The purpose of this recovery is to avoid using adb by accessing all features directly from the menu.
This recovery is for the HTC Nexus One only, if you have a :
- HTC Dream/G1 you should go here.
- HTC Magic/MT3G you should go here.
- HTC Hero you should go here.
- HTC Sprint Hero you should go here.
- HTC Eris you should go here.
- HTC Tattoo you should go here.
Important notes
Always check recovery.log before posting your issues!
You can do this by doing :
"cat /tmp/recovery.log" OR "cat /cache/recovery/log" right after you had the issue.
Use the "move log to sd" option in the "others" menu right after you had the issue. This will move the log to /sdcard/recovery.log so you can easily open it with a text editor.
Features
Use the trackball (up+down) to navigate through the menu, press the trackball to select items. Use the Volume-down key to go back to a previous menu.
Features
full ADB access in recovery mode
Alternative CM and JF version
Busybox v1.15.3
Kernel (2.6.35.7) with ext3 + ext4 support
SLCD and AMOLED support
HW-Key navigation (Trackball + Volume-key) option
Extended menu :
Reboot system now :: reboot your phone
USB-MS Toggle :: enable/disable USB mass storage (use when the phone is connected to your PC)
Backup/Restore
Nand backup :: Make a selective Nandroid backup
Nand restore :: Restore a Nandroid backup
Backup Google proprietary system files :: Makes a backup of the Google proprietary system files in /cache/google
Restore Google proprietary system files :: Restores the Google proprietary system files from /cache/google
Flash zip from sdcard.
Choose zip from sdcard :: Flash a zip update file from any (sub)-directory on your sdcard
Toggle signature verification :: Toggles the signature verification for zip files.
Wipe
Wipe ALL data/factory reset :: wipes /data + /cache + entire ext partition + all apps installed on your sdcard (froyo a2sd).
Wipe /data :: wipes /data.
Wipe /cache :: wipes /cache.
Wipe /sdcard/.android_secure :: wipes all apps installed on your sdcard (froyo a2sd).
Wipe /sd-ext :: wipes the entire ext partition on your sd (if present).
Wipe Dalvik-cache :: wipes the dalvik-cache located in /cache + /data + /sd-ext is present.
Wipe battery stats :: reset the battery calibration.
Wipe rotate settings :: reset the sensor calibration.
Partition sdcard
Partition SD :: Interactive SD partitioning
Repair SD:ext :: Repair the ext partition
SD:ext2 to ext3 :: Convert ext2 to ext3
SD:ext3 to ext4 :: Convert ext3 to ext4
Mounts
(Un)Mount /system
(Un)Mount /cache
(Un)Mount /data
(Un)Mount /sd-ext
(Un)Mount /sdcard
Other
Fix apk uid mismatches :: Does extacly that
Move recovery.log to SD :: Moves the recovery log file to your sdcard. (Use when you want more detailed recovery log information)
Power off :: Powers off your phone
Scripts available via adb :
Nandroid v2.2.1 : enter "nandroid-mobile.sh" to start.
sdparted v0.6 : enter "sdparted" to start.
Install
Pre-Requirements :
Root
Make sure that init.rc isn't calling any install-recovery.sh script, otherwise you'll boot back to stock recovery (exclamation mark with a little Android). More info on this here.
via Rom Manager
Download "Rom Manager" from the Android market
Start "Rom Manager"
Select "Flash ClockworkMod Recovery" and wait for it to finish
Select "Flash Alternate Recovery" and wait for it to finish -> this will install the latest version of RA recovery.
via fastboot
Code:
Copy recovery-RA-passion-v2.2.1.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-passion-v2.2.1.img
via terminal app
Code:
Copy recovery-RA-passion-v2.2.1.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery-RA-passion-v2.2.1.img(press enter)
reboot recovery(press enter)
How to boot in Recovery Mode
Boot the phone while holding down the VOLUMEDOWN-key.
Navigate to RECOVERY with the the VOLUMEDOWN-key.
Press the POWER-key to select.
Download
ALWAYS check the md5sum to make sure the zip isn't corrupted.
Latest version :
recovery-RA-passion-v2.2.1.img - MD5Sum: 3def709ab1c9e051a92a1c8b1504a36a
CyanogenMOD themed version :recovery-RA-passion-v2.2.1-CM.img - MD5Sum: e8262ae23943ce50fd346001812fae79
JesusFreke themed version : recovery-RA-passion-v2.2.1-JF.img - MD5Sum: e94484905a8f39d0985f14e2a5aea403
Previous versions :
recovery-RA-nexus-v2.1.1.img - MD5Sum: 2efdfa4c4adf386d5182c7b290d78c37
CyanogenMOD themed version :recovery-RA-nexus-v2.1.1-CM.img - MD5Sum: 413802bfab420b81946984da988a5be2
JesusFreke themed version : recovery-RA-nexus-v2.1.1-JF.img - MD5Sum: f5238022493deb434e594b36bf43ef02
Change-log :
v2.2.1
Nandroid backup is now selective, boot/system/cache/data are selected by default.
Nandroid checks if there's at least 500MB free on SDcard before starting a backup.
Added/updated error/warning messages.
v2.1.1
Fixed ext4 support in kernel! Update from v2.x if you are using sd-ext!
v2.1.0
Reduced recovery size by 800kb so it fits any hboot version to date :
Set Kernel compression mode to LZMA (33% smaller kernel)
Switched kernel debugging off
Removed : Networking support - Bluetooth subsystem support
Removed : Device Drivers - Misc device - AKM8973 Compass Driver
Removed : Device Drivers - Misc device - A1026 Voice Processor Driver
Removed : Device Drivers - Multimedia support
Removed : Device Drivers - MSM 3D Graphics driver for Adreno class GPU's
Nandroid now backups the entire content of /sd-ext , not just the apps. This fixes bootloops of certain restored roms.
Moved the "Toggle signature verification"-option from the Other- to the main flash-submenu.
Re-ordered the wipe menu.
v2.0.0
Some things in v2.0.0 were kanged with a twist from the Clockworkmod recovery.
Updated kernel to 2.6.35 (SLCD and AMOLED are now both supported).
Added SDEXT support for update scripts.
Added "filebrowser" support when you select a zip to flash.
Added "/.." support to the filebrowser so you can navigate up.
Added a mount menu so you can manually (u)mount stuff.
Added a toggle verification switch so you can flash those awesome unsigned winrar rom releases...
Fully re-wrote the wipe menu (it's not using a script anymore), added a few new wipe options.
Added "/sdcard/.android_secure" support , nandroid now backups/restores .android_secure (Froyo a2sd apps) by default.
Added a few new Google apps to the Google app backup script.
Special thanks to :
packetlss for all the hours of support and awesome coding skills, THANKS man ^^, donate to Haiti
Koushik Dutta for all his recovery work ^^
Cyanogen for his dedicated work! , buy him a beer!
Chris Soyars for the new Apps2SD method ^^
JesusFreke for his awesome JFv1.43's recovery , donate
pensive for adding awesome features to Nandroid
Bkmo for his utility script!
Devsk for his switchrom script!
51dusty for his sdparted script!
k4str0 for his fix_permissions v2.03 update.
Devsk, Dumfuq, Overground for creating BART
rikupw for the ideas and toggle_ums script.
http://www.androidspin.com for hosting ^^
[Recovery] [27-Dec-2010] RA-nexus-v2.1.1
Reserved for future use
Wow, great! hopefully the nexus one will get more love from the devs than the hero
please make this sticky @ mods
qvert said:
Wow, great! hopefully the nexus one will get more love from the devs than the hero
Click to expand...
Click to collapse
Who doesn't want a 1Ghz processor to play with?
how is this possible if the nexus one didnt even come out yet?? lol
damn you are fast amon...i hope to have the phone asap
Amon_RA: I love this dude in a manly way. This guy is quick!
Keep up the good work amon, looking forward to flashing this asap.
i'm so psyched that the devs are jumping on the N1 so quick. I foresee lots of good dev work ahead for this apparently awesome phone. can't wait to see what comes of it.
j.books said:
i'm so psyched that the devs are jumping on the N1 so quick. I foresee lots of good dev work ahead for this apparently awesome phone. can't wait to see what comes of it.
Click to expand...
Click to collapse
Exactly, already rooted AND now a niice recovery . Nice work man, cant wait for the phone to come in !!!
THANK YOU!
LOL Amon_RA, you are faster than sound!...
Greetz
Andfreek!
Thanks to the devs!!!
Thanks guys for all your work!!!!!! Can't wait to get my Nexus One!!
Amon_Ra Please help us with our HTC Droid Eris, We have not been able to get root.
Nice image thanks!
Awesome, lookin forward to getting my N1 to try this on
Good lord man I just ordered mine and you already got a recovery made?? Great job man!
Bigup!
Nice work Amon..
Awesome job!
NICE, amazing work as always and you seemed to have mastered time travel this time around
Are the touch sensitive buttons hard to code for or did I just overlook that, it seems as if they are not available from reading the feature list
I would love it if you could add HOME = Accept / BACK = Cancel
Can't wait to get my Nexus tomorrow, the future looks bright, blinding even
now time to kill some time, going to see Laker game live
OMG FLASHING NOW!
I got some goodies coming up too!
CM10.2 for WAVE and WAVE 2
Android Jellybean 4.3.1
Hi All,
So once again it’s time to upgrade our project to Android 4.3.1
Previous versions:
CM10: forum.xda-developers.com/showthread.php?t=1851818
CM10.1: http://forum.xda-developers.com/showthread.php?t=2400126
Let’s emphasize that-- THIS IS AN ALPHA, RELEASED FOR YOU TO PLAY WITH AND GET A SENSE OF WHAT’S TO COME. AND SOME THINGS DOESN’T WORK. REALLY. IF YOU ARE EXPECTING ANYTHING CLOSE TO PERFECTION, WALK AWAY FROM YOUR COMPUTER, LOWER YOUR EXPECTATIONS FOR AN HOUR OR SO, THEN COME BACK. MORE EXCITING DISCLAIMERS/WARNINGS IN ALL CAPITAL LETTERS CAN BE FOUND BELOW. READ THEM.
FEATURES
Android 4.3.1
CM sources of 21.10.2013
Updated to linux kernel version 3.0.101
270 MB RAM
KNOWN BUGS (what doesn't work):
- Network registration don't work with some SIM cards
- GPS - http://forum.xda-developers.com/showpost.php?p=47209249&postcount=1371
- Conference Calls
- Some problems with audio codec settings, but generally it should
- Impossible to shut down phone in android, only restart
- Don't leave phone charging without supervising - if it gets enormously hot, disconnect it - this can literally blow up battery as there is no overheating protection yet. Do not leave it connected on 100% - it'll discharge by 1% all the time, and then recharge, what's very unhealthy for battery.
Maybe something else, what i forgot
SUPPORT
You get none. Zero. Zip. We obligate ourselves to providing nothing further. You are on your own and will have to help each other via this thread. This is provided “as-is”, and if you don’t like it, use Bada or other releases.
We basically lack time to give full dedication to this rom, and we’re looking for skilled devs who know the Android, and/or other things that might be relevant.
Please join us on IRC: some people are on #badadroid (freenode).
BUG REPORTS
This is the format for a bug report: “XXXXX isn’t working. Here is how to fix it: [INCLUDE SOLUTION]” Don’t have source? Too bad. You’ll have to wait then.
If you report bugs, please don’t be disappointed if we can’t fix them immediately (or even never). It’s not because we don’t care, but because we don’t have time or don’t know how to fix it.
Please attach logcat and dmesg dump in your bug report. Dmesg should contain messages from both - bootup and issue occuring (you can't dump it 1 hour after bootup, rather 2 minutes after)
How to dump logs - Google for "android logcat dmesg" Or... whatever, here's one of 3204109 methods available.
In the Terminal Emulator enter:
"su"
Accept request for SuperUser access.
"dmesg > /storage/sdcard1/dmesg.txt"
"logcat -b system -b radio -b events -b main -d -f /storage/sdcard1/logcat.txt *:V"
"logcat -b radio -d -f /storage/sdcard1/radiolog.txt *:V"
Download them from phone, archive and upload them.
Privacy warning: Your logcat might contain sensitive information like your IMEI, IMSI, cell stations you were nearby, numbers you called and got calls from and SMS sent and received. If you don't want to publish this info - send them privately to one of developers.
Click to expand...
Click to collapse
If the Badadroid is restarting before you're able to catch any log:
Download http://goo.im/devs/Rebellos/wave/bterm.exe
Try to start kernel normally, when you see Badadroid logo start holding the middle key pressed. Keep the middle key pressed until phone restarts and shows the text: FOTA DOWNLOAD MODE & bTerm
Connect phone to PC.
Start bterm.exe
Type 4 commands:
Code:
open
dumpram 0x4FF00000 0x100000
close
exit
There should appear file called dump_ram_0x4FF00000.0x00100000.bin - pack it and attach it to your bug report.
Click to expand...
Click to collapse
Bug reports without logs are completely useless.
NOTE: DEVELOPERS WANTED. Please contact us if you are a developer with something to contribute.
I do heavily encourage to work together on the better, common project instead of making kang releases and demanding money for somebody else's work.
Read as: If you think you can make something better than this by doing less and muchazo Ctrl+C Ctrl+V - you suck, go figure the rest.
HOW TO BUILD
I do recommend perfect tutorial by fattire: https://docs.google.com/document/d/19f7Z1rxJHa5grNlNFSkh7hQ0LmDOuPdKMQUg8HFiyzs/edit?hl=en_US
Of course you have to init with -b cm-10.2 and modify some steps.
local manifest to use: https://raw.github.com/Badadroid/android_wave_local_manifest/cm-10.1/local_manifest.xm
I do it like this:
Code:
cd ~
mkdir wave
cd wave
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
cd .repo
wget [url]https://raw.github.com/Badadroid/android_wave_local_manifest/cm-10.2/local_manifest.xml[/url]
cd ..
repo sync -j8
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
brunch wave
device name is wave so the build invocation can be brunch wave
FIRST INSTALLATION
Bada 2.0 is required
Enter Bada Settings->General->Memory and make sure you have at least:
370MB of free "System" memory
160MB of free "User" memory
400MB of free "Applications" memory
Download BOOTFILES, armlinux_boot for your device:
for 8500:
http://yadi.sk/d/W4RjnjQRC6TfP
http://yadi.sk/d/Yz7_dfpkC6TkC
for 8530
http://yadi.sk/d/kxJ0CZ20C7AKF
http://yadi.sk/d/zqzWZ9LmC7AJA
(please pay attention if it's S8500 or S8530 BOOTFILES and FOTA you're choosing!):
Download ROM from CHANGELOG section
Start Bada.
Extract zImage from zip and copy it to the Bada's User partition (the one about 390MB big).
Copy whole .zip to the Bada's User partition or SD Card.
Flash BOOTFILES and FOTA using Multiloader.
Reboot the phone holding Power and Call key.
FOTA set of red messages should appear, after about 15seconds Badadroid logo shows up.
Be patient, first bootup will keep unresponsible on Badadroid logo for up to 5 minutes.
CWM Recovery starts, pick:
- "install zip"
- "choose zip from from storage/sdcard1"(Bada's User partition) or "choose zip from storage/sdcard0"(SD Card)
- cm-10.2-wave-<release id>.zip
- Yes - install
Reboot holding the Power key
You can remove installation .zip from the User partition from Android level by connecting through USB in MTP mode.
Do not remove zImage file.
Normal bootup is available using Power+Call keys
CWM Recovery mode is available using Power+Volume Up keys
CWM Flashing does overwrite zImage. So every next update you can just flash .zip through CWM.
After first installation i recommend to disable Screen-off Animation by Settings->Display-> uncheck Scren-off animation
And also for better performance activate zRAM. Settings->Performance->Memory Management->zRam-> and choice Value. I use 26%
For activation Performance and Developer Options categories in Settings you need Settings->About Phone and tap 7 times on Build number
GAPPS
GAPPS make our ROM slowler, because also slim GAPPS take about 15-20 MB RAM permanently
SLIM GAPPS http://d-h.st/mBO from http://forum.xda-developers.com/showthread.php?p=47934744
Minimized by -CALIBAN666- from PA GAPPS: http://forum.xda-developers.com/sho...ers.com/showpost.php?p=35107469&postcount=393
THANKS TO
Special thanks to Rebellos for his CM10 ROM, for his good sources and many time, what he spent for my learning
Another Badadroid devs: Oleg_k, mijoma, nbates66, anghelyi, mikegapinski, hunktb, autra, Tigrouzen and many others.
CyanogenMod team for base ROM
Paulk and Replicant project for good base for bada-modem RIL
and many other who help us.
CHANGELOG:
Kernel update
http://www.multiupload.nl/TWJAP1T4C9
kernel with removed +10 RAM patch for v3.1 with working camera and video playback
v3.1 - http://www.multiupload.nl/1E85FRD1ES
- +10mb RAM
- Updated audio codec settings for RCV and HP
- Added 15 volume levels for Calls
- Reworked SMS sending
- Fixed torch toggle in quick settings.
Kernel update for Wave2
for fixinginstallation problems
http://www.multiupload.nl/O2CVN5R9EQ
Replace zImage in Zip with this and re-copy it on Bada User Partition
and after flash step by step.
If you forgot or don't want to pack zImage in zip archive you need again replace zImage on Bada User's partition, because during flashing zImage will be replaced by one from zip archive.
Big Thanks to Rebellos for logs and RedDerRed from badapps.ru for testing all my test versions
v3 Initial CM10.2 release: http://www.multiupload.nl/8UUFOIQQE1
- Updated kernel 3.0.101
- CM Sources 30.11.2013
- CM team fixed power menu on lock key. Now we can show power menu by long press of lock key.
So i don't see any reason to use Navbar. We back to Galaxy S mapping:
Call key = MENU
Middle key = HOME
End Call key = BACK
Lock key = POWER
- Removed VideoEditer, LiveWallpapers, CMUpdater
- Fixed BT headset in calls
- Set of patches for GPRS RIL interface
- Fixed memory leaks in SIM_IO requests
MORE LINKS
Overall project thread - http://forum.xda-developers.com/showthread.php?t=1459391
Nice Work Volk & Rebellos
Work this Version faster ?
Greets
Sent from my GT-N7100 using xda app-developers app
Nice work
very fast and smooth........awesome work :good::good::good:
incredible speed without gapps
anyway of installing just google calendar and google contact sync? (without the whole gapps package)
thank u so much @volk204.
but this rom still not smooth and its slow , and there is no Bigmem , bigmem 325mb ram will make this rom competely usable and really realy faster and great for gaming
i m 101% sure latest games like asphalt8:airborne , Modern combat 4,5 will not work.
even normal apps will lag too
wave 2 does not work ...
Gunter33 said:
wave 2 does not work ...
Click to expand...
Click to collapse
same too.
gonghwa said:
same too.
Click to expand...
Click to collapse
for me can get into recovery mode but when it's Chose zip from/storage/sdcard0 shows me E: Can mount/storage/sdcard0. hmmm something is strange: (
jon.marius87 said:
for me can get into recovery mode but when it's Chose zip from/storage/sdcard0 shows me E: Can mount/storage/sdcard0. hmmm something is strange: (
Click to expand...
Click to collapse
same too(((
4.3
volk204 said:
CM10.1 for WAVE and WAVE 2
Android Jellybean 4.3.1
Click to expand...
Click to collapse
Sorry to point out but Android 4.3 is CM 10.2...
Gunter33 said:
wave 2 does not work ...
Click to expand...
Click to collapse
djkoloda said:
same too(((
Click to expand...
Click to collapse
Very verbose bug report.
jon.marius87 said:
for me can get into recovery mode but when it's Chose zip from/storage/sdcard0 shows me E: Can mount/storage/sdcard0. hmmm something is strange: (
Click to expand...
Click to collapse
gonghwa said:
same too.
Click to expand...
Click to collapse
Do you have SD CARD? Can you mount storage/sdcard1(Bada user's partition)?
Sandeep Srikantam said:
Sorry to point out but Android 4.3 is CM 10.2...
Click to expand...
Click to collapse
Fixed
Very good job :good:
at the choice of Chose zip from/storage/sdcard0 shows me E : Can mount/storage/sdcard0. at a copy on sd-card the same result. wave s8530
lack of torch in quick settings
Hello. I've noticed there's no torch in quick settings. I think it maye be fixed by adding:
Code:
<bool name="has_led_flash">true</bool>
in:
Code:
https://github.com/Badadroid/android_device_samsung_wave/blob/cm-10.2/overlay/packages/apps/Settings/res/values/config.xml
but i'm not sure (cm-10.1 had this line and torch was in there, as u can see)
Code:
https://github.com/Badadroid/android_device_samsung_wave/blob/cm-10.1/overlay/packages/apps/Settings/res/values/config.xml
i can't find anything that could change it in rom .zip package so i think it will be just information for future roms.
very good sir
Good job
Good job bro continue like that !
Hi volk204,
I am unable to install new ROM on wave 2.
In CWM mode,its showing message..
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
when i click on "install zip"..
it showing "choose zip from /storage/sdcard0"
also,I am able to mount /bada-user.
Thanks,
Waveguru
waveguru said:
Hi volk204,
I am unable to install new ROM on wave 2.
In CWM mode,its showing message..
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
when i click on "install zip"..
it showing "choose zip from /storage/sdcard0"
also,I am able to mount /bada-user.
Thanks,
Waveguru
Click to expand...
Click to collapse
Maybe memory corruption, happened to me also, try to reflash bada then reinstall android
waveguru said:
Hi volk204,
I am unable to install new ROM on wave 2.
In CWM mode,its showing message..
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
when i click on "install zip"..
it showing "choose zip from /storage/sdcard0"
also,I am able to mount /bada-user.
Thanks,
Waveguru
Click to expand...
Click to collapse
I have a same problem with you. it's not working on Wave II
I installed Bada again and tryed once more but same. I'm choosing -choose zip from/storage/sdcard0 but nohing happening. I also formated sd card again and tryed to put 10.2 v3 zip to phone memory but same...
volk204 said:
Very verbose bug report.
Do you have SD CARD? Can you mount storage/sdcard1(Bada user's partition)?
Fixed
Click to expand...
Click to collapse
I referred to this Q&A
Badadroid is stuck in animation with rotating circle where Cyanogenmod is written in
It happens if you don't comply with installation requirements. Enter Bada Settings->General->Memory and make sure you have at least:
370MB of free "System" memory
150MB of free "User" memory
400MB of free "Applications" memory
Solution: make a clean installation of bada: full flash
Related XDA posts: http://forum.xda-developers.com/showthread.php?p=39859136#post39859136
and after I checked the phone the answer is yes, I have less memory than required. After a full flash I got no luck to get v3 running. I guess it is related with the kernel because if I change kernel to v2.1's it can flash the v3 zip and later show some progress during the rolling circle. If I use kernel in v3 zip it just can't mount sdcard0 as others. That's all I can provide.
Note to developers, Philz touch is fully open source. Please feel free to create your own builds. However, this thread is sanctioned officially by Phil. The builds posted here have been built under the conditions set out by Phil. Please do not post your own builds in this thread. I cannot support builds made by other people so please don't use them then post for help here.
Note from the thread author, please note - I am not the developer of Philz Touch. @Phil3759 is. I am merely an avid follower of Philz amazing efforts and the official Nexus 5 maintainer.
Please take a moment to thank Phil for his work by clicking "Thanks" on THIS POST
Click to expand...
Click to collapse
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please note, USER queries / support for the Nexus 5 should be posted in THIS THREAD, and NOT in the main DEV thread.
I won't be compiling every build. I will skip builds that do not add /alter functionality to the Nexus 5 for obvious reasons.
I will only compile if we have:
New or updated Features relevant to N5
Bug Fixes
Code clean-up or libtouch_gui shouldn't affect the user experience. I don't want to keep bugging Phil to upload trivial builds to goo.im - so please don't get disheartened if not every version number from Philz master thread makes it to N5
Features:
F2FS migration support
Recovery Lock
Root directly from Recovery menu
browse phone with root access using full GUI in Aroma File Manager
terminal access from recovery with root access through Aroma File Manager
Multi Zip Install menu: check multiple zip files to install in a row
Custom Install Zip Mode: set a default folder to start with + browse backward up to the root
TWRP backup and restore support, include full md5 sum support (single and multivolume, compressed and non compressed formats)
Advanced statistics during backup operations shown in color: total backup size, backup size progress, backup time, compression ratio...
optional reboot after custom backups/restores
set special nandroid settings: time zone, toggle md5 check for lightning fast backup and restore, toggle /preload backup and restore, enable nandroid compression using pigz (multi-cpu gzip compression) and choose ors backup target volume
recreate md5 sum check for your cwm backups for compatibility with stock CWM if you need to revert
you can cancel any nandroid operation with back button
create custom_rom.zip from current ROM or from a pre-existing nandroid backup (based on boot, /system and optionally /preload)
nandroid backup path now will be named with current ROM id from build.prop (ro.modversion, then ro.romversion, then ro.build.display.id)
custom backup and restore job list: backup and restore freely any partition combo
support flash modem.bin image files in addition to custom modem.img files, now support for multiple *.bin versions under dedicated folder
during custom restore, you can see the contents of the folder you want to restore from
delete custom or TWRP backups from recovery menu
full wipe before flashing new ROM: wipe user data + format /system and /preload. SD card content is not affected
full support for openrecovery script specifications include all backup and restore options
run openrecovery scripts in 2 modes: on start goomanager boot scripts + one touch menu to either directly open a default path or freely browse for scripts
define ors backup target volume from within Nandroid Settings menu
ors restore path supports stock clockworkmod path or TWRP path
poweroff, reboot to recovery and reboot to download/bootloader mode options
adb root in recovery: just wait about a minute to activate
Download links
Latest version can be found here:
http://d-h.st/users/rootsu/?fld_id=34576#files
Click to expand...
Click to collapse
Backup versions (updated monthly):
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hammerhead
Click to expand...
Click to collapse
*Zip is custom recovery flashable, or you can extract the .img and fastboot flash in the normal way
Please note, not every new version contains commits that benefit every device, so the version in this thread title may not always match the version in the development thread title. Please do not ask for ETA in this thread or the development thread. New versions come as-and-when.
Main thread (device support) + features (extended)
http://forum.xda-developers.com/showthread.php?t=2201860
Please note, USER queries / support for the Nexus 5 should be posted in THIS THREAD, and NOT in the main DEV thread.
{
"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"
}
Nexus 5 known issues / FAQ
Nexus 5 specific changes:
Nexus 5 specific changes are listed below. Please note, not all of these changes were in a single release of Philz. This is a list of changes for the latest version released for the Nexus 5 and all skipped versions released since the previous release for the Nexus 5.
For full change log, please click HERE
Changes between 6.57.9 and 6.57.5
Fixes
-Fix Free Browse mode
Changes between 6.57.5 and 6.50.2
Fixes
-Potential failure to reboot
-Potential failure of TWRP backups
-Regression bug in Advanced menu
-Crash by calling ui_print or LOGE on early recovery init
-Wake-up screen could fail or take a few seconds to reset brightness
-Memory overflow potential issue
Visual
-Group all wipe otions under a same men
-Enhance menu titles
-Keep only mount and storage options in the corresponding menu
-Enhance highlight of virtual keys
-Tweak default recovery keys
-Don't show mount usb storage menu when it is not available
-Always show text in sideload mode
New
-enable screen capture through adb shell
-option to disable md5 from edify restore_rom command line
-support wipe_cache and clear_display edify script commands
Improvements and updates
-SuperSU 2.02
-use built in busybox tar instead of libtar
-drop fb2png binary support
-restore custom rom: preserve selinux attributes
-do not wipe /data/media on wipe_data recovery start command
-do not show mount/unmount /sdcard on /data/media devices …
-support more moint points for /data/media detection
-enhance code to toggle /data/media multi user support
-enhance code to mount auto file system
-do not double confirm formatting /data/media during ext4 <-> f2fs con
-optimize memory resources
-never confirm wipe in ors scripts
-mounts: match aosp sources
Changes between 6.50.2 and 6.47.4
- Various (as yet unspecified) changes
- merge multi stage install packages support from AOSP
- CWM 6.0.5.0
- add option to directly parse time_daemon data files
- refresh current time in menu header after time daemon fixes
- fix first passkey prompt screen did not show proper background under some circumstances
- preserve background icon user settings after sideload, install zip and wipe actions
- use real fstype instead of auto in /etc/fstab when converting between ext4 <-> f2fs using extra.fstab
- recovery lock: support use of virtual / capacitive keys as pass key
Changes between 6.47.4 and 6.47.3
Bugfix version. Fixed adb issue when no keypass set
Changes between 6.47.3 and 6.43.6
See recommendations at the bottom of this post for details on recovery lock...
- add recovery lock with passkey on start (secure your data from recovery intruders)
- fix segfault during shell nandroid backup/restore commands
- enable progress display during "adb shell nandroid backup/restore" commands
- enhance and fix bugs of progress display during install/nandroid... operations
- nandroid restore: fix progress bar animation when md5 verify is enabled
- nandroid md5: fix progress bar was not reset for each file
- nandroid md5: fix .android_secure md5 sum was never generated or checked
this could cause md5 check to fail under some circumstances
- limit logging to console in adb shell nandroid and mount commands
- fix detection of real fstype (pointer to in the scope char array bug)
- disable useless sd-ext warnings and errors
Changes between 6.43.6 and 6.30.1
See recommendations at the bottom of this post for details on F2FS...
- f2fs: recreate /etc/fstab after ext4/f2fs conversion for proper use of system mount command
- f2fs: fix nandroid restore to f2fs partitions
- f2fs: support format extra storage to f2fs (vold patch needed)
- f2fs: support switching between f2fs/ext4 (needs f2fs in kernel modules), thanks @KumaJaya
- f2fs: reload volume table after f2fs/ext4 conversion (no reboot needed after conversion)
- f2fs: do not format whole /data when not expected on /data/media devices
- f2fs: allow /data f2fs/ext4 conversion for non data_media devices
- f2fs: compile with prebuilt AOSP kernel as provided by @dennes544 - thanks!!!
- allow ext4 f2fs backup data migration in nandroid
- create /data/media/0 after formsat of /data and /data/media
- nandroid backup: fix 'media' exception
- use libtar as default for backup/restore
- Preserve recovery settings after a wipe
- fix save/restore settings menu label
- create /data/media directory after internal storage is wiped
- fix text print colour could persist after md5 check
Bug Fix version 6.30.1
- fix restore of /data: revert to busybox tar and external selinux backup
Changes between 6.26.6 and 6.29.2
- fix potential bug when verifying root and recovery state on exit
- merge "Fix verify_root_and_recovery menu selections
- hide the Go Back button from confirm menu
- add minitar binary to /sbin instead of busybox tar
- minitar: enable more options, enable long options, fix selinux backup/restore, enhance GNU tar compatibility
- enable seamless backup/restore selinux context using minitar binary
- TWRP mode: support backup/restore of selinux context
- confirm cancel nandroid jobs (prompt to press 'Back' twice or resume after 5 secs)
- vibrate after backup/restore operations
- do not consider su symlink in /system/bin as a broken root
Changes between 6.26.1 and 6.26.6
- CWM 6.0.4.8 rebase
- Fixed rootsu error in fstab
- Removed /efs1 and /efs2 from mounts and storage menu
Changes between 6.23.9 and 6.26.1
- fb2png: better error logging
- sort files using case insensitive order
- remove old no more needed md5 check code
- fix successive gestures
- set these default gesture actions:
* swipe left = screen off
* swipe right = increase brightness
* press 1 sec and lift = show log
* press 2 sec and small move = screen shot
- merge "Only init legacy property environment once"
- revert using ntfs module and drop to fuse for complete write support
- use new md5digest code to generate/verify nandroid backups
- bring progress bar during nandroid md5 generation and check
- exclude log and md5 file when regenerating md5 files
- twrp mode: use new md5digest function with status bar during md5 check/create
- twrp mode: fix double md5 verification bug
- fix delete backup menu failed to reopen base backup folder + wired log message
- fix the "umount: can't umount /data: Invalid argument" log message on start when time daemon was loaded
- show "time daemon loading" message on recovery start when we're waiting for the daemon to load
Changes between 6.23.7 and 6.23.9
- Updated time daemon settings to use hammerhead default dir /data/system/time. Time now works (except Daylight Savings - Change Time zone manually for now to get correct time)
Changes between 6.22.7 and 6.23.7
- Better error checking to avoid segfaulting
- really hammer lazy developers (report outdated binary in ui print)
- Use legacy property environment if old update-binary
- fix fb2png flag to be enabled by default
- fix potential unsafe thread code
- Disable gesture actions during md5 checks as they are not thread safe
Changes between 6.21.2 and 6.22.7
-Qualcomm screenshot (fb2png) functionality added
- USB OTG install zip (black screen) Bug fixed
Changes between 6.20.6 and 6.21.2
- add progress bar while reading zip file to compute md5 check
- add color printing during md5sum checks
- (derp) fix color code printing on md5 check disappears after 5 sec (ui_wait_key() screen refresh)
- md5sum check potential bug fixes and optimizations
- libtouch_gui 1.05
Changes between 6.19.7 and 6.20.6
- add md5 sum calculation and toggle verification during install of zip files
- many bug fixes and code cleanups
- libtouch_gui 1.04
Changes between 6.19.3 and 6.19.7
- add /efs backup support*
Note, efs is split over 2 partitions on the N5. Back them both up in custom backup! DO NOT RESTORE EFS BACKUPS ON ANOTHER PHONE!
Changes between 6.15.4 and 6.19.3
- merge "update-binary: Add collect_backup_data function"
- merge "recovery: add overlay interface for recovery mode"
- merge Aroma patches:
- User selectable colorspace added to settings.
- Unmount /system at exit if mounted.
- Some more logging added
- merge remote cm-11.0 changes
- led state in menu
- more comprehensive menu text display for /data/media/0 toggle
- fix potential memory leak in /data/media/0 toggle
- huge cleanup and potential bug fixes
Changes between 6.12.9 and 6.15.4
- update superSU to 1.93
- sync sources
- fix recovery reboot command (adb and shell) by adding the init sys.powerctl property control
- merge "Fix mkfs.f2fs calling in roots"
- fix display current path when navigating backward in folders
- Nandroid Simple Logging: toggle logging of file names during nandroid to keep screen progress while speed up nandroid operations for some devices
- increase NICE_INTERVAL to 300 msec (faster backup/restore on some devices)
- hide unused settings in Nandroid Settings menu (if we disable all progress on screen, hide non valid options)
- re-order nandroid settings menu
- add a toggle for fall back to pre-built update-binary to permit use of older update-binary in zip packages (doesn't persist on reboot).
this will fix the assert errors due to outdate update-binary. It could still be affected by assert error on device name getprop. However, that one is easier to fix by end users by editing updater-script. This is a workaround. The best is to hammer your ROM cooker to update his scripts and binaries
- setting for signature check toggle on zip updates will be now saved on reboot
- Aroma File Manager: mount vold managed volumes on launch from recovery
- Free Browse Mode: make it possible to install from any custom path even ramdisk
- Free browse mode: fix exceptions when setting up custom path
- Free browse mode: mount known volumes during setup
- Free browse mode: better handling of /data/media devices
Changes between 6.12.8 and 6.12.9
- Update to Stock KOT49H kernel to fix Graphical glitches caused by CM 11 kernel
Changes between 6.09.2 and 6.12.8
- time and date menu text formatting and order
- version display edit
- add ntfs write support to devices using kernel modules instead of fuse
- zip installer: update loki binaries for LOKI devices
- zip installer: use new update-binary sources
- manually set time and date in recovery
- support Qualcom time daemon to sync time with main system (credits to dougiebee)
- support RTC offset hack for Qualcom devices without a proper time daemon in system ROM (credits to dougiebee)
- option to drop to system set time and date commands (credits to dougiebee)
- set default nandroid compression level back to low
- roll out exfat-nofuse sources from dorimanx into various kernels from Samsung and other brands
- code fix and cleanup
- update SuperSU to 1.91
- merge android_system_core changes to adb to fix push to extra storage paths
- do not use performance mode during install zip: fixes hang on unmount /system in updater-script when usb cable is connected
- update to CWM 6.0.4.7
- merge "Fix up bu restore"
- ROM Manager: workaround to backup/restore to/from external storage
- enhance touch init (fix touch on some Sony devices)
- really fix reading device max brightness value
- loki: merge "Support Open EU LG Optimus F6 and US Cellular Optimus F7"
- read the device max brightness setting to fix brightness toggle on some Sony devices
- merge: "Populate mount menu with new mount/format matrix" - final version
- merge: "Use cat for adb backup."
- merge: "Populate mount menu with new mount/format matrix"
- do not error on missing sd-ext when wiping dalvik cache
- merge: "su: Update for latest su daemon compatibility"
- merge "Clean up c formatting - 1"
- merge "Remove "Go Back" option from verify root and recovery options"
- merge "Fix potential chmod failures"
- merge: "Add a copy of the updater binary to the recovery resources"
- merge: "install: Support downgrade scenarios"
- merge: "install: Fix possible overflow condition in the updater "scanner""
- merge: "minui: do not use flexible array initialization"
Changes between 6.07.9 and 6.09.2
- TWRP: merge "support use TW_USE_MODEL_HARDWARE_ID_FOR_DEVICE_ID"
- toggle prompt on low free space during backup
- SuperSU update to v1.89
- loki: merge "Support LG Vu 3."
- code cleanup
- gesture action defaults changed
- long press and lift gesture action is now triggered after finger pressed for more than 1 sec
- do not include fb2png on non supported devices
- stop always rebuilding aroma intermediates
Changes between 6.03.5 and 6.07.9
- fix exiting "pause on logs" mode with virtual keys caused erroneous validation
- fix exiting screen off mode with hardware key could cause erroneous validations
- fix some devices could not exit "pause on logs" mode with screen touch
- bring immediate touch responsiveness after exiting screen off mode and "pause on logs" mode
- fix erroneous first menu validation when exiting screen off mode on some devices
- fix long press and move action could be triggered while swiping outside menus and returning to first touched area
- increase threshold for long press and move action for easier triggering
- small touch scroll optimizations
- improve touch responsiveness on low res devices
- code clean-up and optimization
- fix log text could overwrite clock/battery icons on some low res devices
- after successful zip install with sideload, hide the install background icon
- after installing zip with sideload, do not trigger "pause on logs" mode
- loki: sync latest sources (support LG G2 VS98012b)
- better fit text logs on non HD devices: stop slightly overwrite of bottom virtual keys separation bar and clock/battery area
- fix logs overwriting bottom virtual keys and progress bar in sideload mode
- add 5 extra partitions support in nandroid: can be added in fstab and will be auto detected
- custom backup and restore menu: move reboot item to top of partitions list
- custom backup and restore menu: auto hide all unused items
- advanced menu: hide /data/media toggle for non datamedia devices
- sync loki sources: add new LG devices
- SuperSU update to 1.86
- busybox: merge @Chenglu changes to support selinux (no tar --selinux yet)
- huge code clean ups and fixed
- fix twrp backup/restore default mode
- save loki support user setting (default is now disabled)
- add custom backup and restore options to main nandroid menu for each storage volume
- ditch stock cwm limited advanced restore function
- add toggle to switch between TWRP/CWM as default backup mode
- ors: backup mode is now the default backup mode set for all recovery session
- ors: smart restore mode to override main backup mode depending on path we restore from (TWRP vs CWM auto detection)
- backup/restore validation menu moved to top in custom modes
- sanitize rom name for backup: exclude "&" symbol and fix compiler warnings (size_t)
- when deleting backups, do not exit the menu each time
- fix new line in process_volumes()
- merge: "Don't return immediately from reboot commands."
- merge: "Enable incremental builder to find files that moved"
- merge: "Support recoveries without CONFIG_EXT4_FS_XATTR"
Recommendations
Recovery Lock / Passkey
@Phil3759 has implemented a recovery lock with pass key. This means that you can lock your recovery. Providing you keep your bootloader locked and keep an Android ROM Pattern, PIN, Password lockscreen, this will mean that a "recovery intruder" will not be able to use or replace recovery without unlocking yuour bootloader using fastboot (Which wipes the device). Thieves will no longer be able to look through your photos or find files related to banking on your device.
The Lock comes up at recovery boot. There is no GUI or adb access available until the recovery is unlocked. Please note, this is designed to prevent people getting hold of your data, NOT to prevent them wiping your data. If you decided to use this option, you must ensure that you keep your data backed up on an external device. This recovery is not responsible for data wipe prevention or if you somehow manage to lose access to recovery.
To setup the passkey:
Go into Recovery > Philz settings
Setup recovery lock
Change recovery passkey
You will be prompted to set and confirm your passkey. Passkey is a 6 "character" combination of hardware key presses (Vol up, down and power).
Please note, flashing a ROM will remove the passkey, so you will have to set it up again. Passkey is stored in /system/.recovery_key.lok
F2FS
What is it? - Flash-Friendly File System. designed by Samsung to be used spcifically on Flash media. Can increase Read / write speeds, increasing the overall performance of your phone.
Where to use it? - Since not many read / writes happen anywhere except /data, it's best to use it only on the /data partition (including /sdcard)
Do I need anything special? - Yes, you need an F2FS supported kernel
Can you recommend an AOSP Kernel? - Yes, use the AOSP/CAF kernels created by @dennes544 here. If you need something a bit more custom, flash ElementalX afterwards
Any other kernels that work? - I can't say I have tested them all. So far, I haven't managed to get Faux to work. I have used a custom version of Franco however and that worked fine (see link in thread above). I'm not really here to recommend / catalogue kernels though
Any further advice? - It depends on the kernel if it supports other partitions to be formatted as f2fs. For example, some may not allow /system to be formatted as f2fs - but this is not much use anyway, o please stick to just /data and /sdcard
Do I need to keep swapping between F2FS Philz and Standard Philz? - No, it is all one kernel. No need to flash different ones.
How do I use this? - See below
Here are the steps:
- Ensure you have an F2FS kernel (put it on your sdcard now) or have the .img ready on your computer
- Take a full Nandroid backup
- backup your ENTIRE /sdcard to PC (adb pull is as good as the rest - and also a good test that you know what you're doing)
- Flash the updated recovery
- Go to "mounts and storage"
- Press "toggle f2fs ext4 migration"
- Press "format /data and /data/media (/sdcard)"
- Select f2fs and "Yes" - Your /data and /sdcard are now blank
- adb push your clockworkmod folder back to /sdcard (and f2fs kernel if you're using a zip)
- Nandroid restore your /data partition
- Flash your F2FS kernel
- Copy sdcard data back, (using MTP in Android is best) - You may need to boot into Android and reboot the device again before Internal storage shows (Linux only perhaps?)
Notes:
Please note, the migration toggle is disabled again as soon as you leave that menu. The format options will format to whatever each partition is already formatted to whilst the toggle is disabled. So if you previously formatted to f2fs and then reboot recovery and format again, it will continue to format to f2fs until you enable migration and choose the opposite option (ext4).
Also, whilst migration is enabled, you willbe prompted which fs to format to; ext4 formats to ext4, f2fs to f2sf and default to whatever it is already formatted to.
Recommended time settings
Philz Settings > GUI Pref > Time Set up > change date and time
Use the "Time daemon" setting. Set this then boot into rom. Give it a couple of minutes and boot back into recovery.
Please note, qualcomm time daemon always uses UTC (GMT) so you must manually set your time zone in recovery.
Daylight saving is not yet managed by recovery so please alter time zone manually to compensate.
EFS Backup
In custom backup settings, select efs 1 AND efs 2. The N5 splits over both.
Do NOT restore efs on another phone. EFS must be unique on every handset. Restoring efs from another phone will ruin your phone.
md5 verification
If you're moving zips on and off your phone all the time, they can become corrupt during any one of those moves. The new Md5 functionality allows the md5 to be calculated before flashing a zip and shows you on the recovery screen. This means you can read the screen and compare it to a known md5sum for the zip.
There is additionally an md5 verification setting that will only flash the zip if it matches the md5 stored in an md5 file on your memory. I wrote a script to put in the directory with all your zips on your phone that will create an md5 file for you for each zip you have. This way, as you move your zips on and off your memory, you can take the md5 file too and have Philz prevent flashing of those zips if they become corrupt.
Simply unzip the attachment into the directory where you keep all your zips. In terminal emulator, cd to that directory then run the sh file. In this example, all my zips are in /sdcard/AFlash
Code:
cd /sdcard/AFlash
sh md5.sh
Enjoy
Nice one mate.
ZANGETSU786 said:
Nice one mate.
Click to expand...
Click to collapse
It's working well so far. Try it out, let us know how you get on.
Yes!! Was wanting this for my hammerhead. Thanks!!
sent from my HAMMERHEAD neXus
---------- Post added at 10:38 AM ---------- Previous post was at 10:30 AM ----------
Will you be updating this thread with newer versions?
sent from my HAMMERHEAD neXus
CRIME INC. said:
Yes!! Was wanting this for my hammerhead. Thanks!!
sent from my HAMMERHEAD neXus
---------- Post added at 10:38 AM ---------- Previous post was at 10:30 AM ----------
Will you be updating this thread with newer versions?
sent from my HAMMERHEAD neXus
Click to expand...
Click to collapse
I will. Phil will subscribe for support here too. I have made teh thread to his specifications, so do subscribe
Subscribed:thumbup:
sent from my HAMMERHEAD neXus
rootSU said:
It's working well so far. Try it out, let us know how you get on.
Click to expand...
Click to collapse
Everything appears fine.
The time in recovery was at first incorrect for me though. The default for GMT+0 the recovery had was 10 hours behind (or 14 hours ahead) compared to actual time here in UK.
Misc Stuff.
Buttons = Pass
Virtual Buttons = Pass
Brightness setting = Pass
Vibrator Toggle = Pass
Sent from my Nexus 5 using Tapatalk
Good Job! Waited for it! will try after reviews
sewer56lol said:
Everything appears fine.
The time in recovery was at first incorrect for me though. The default for GMT+0 the recovery had was 10 hours behind (or 14 hours ahead) compared to actual time here in UK.
Misc Stuff.
Buttons = Pass
Virtual Buttons = Pass
Brightness setting = Pass
Vibrator Toggle = Pass
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yep my time is also an hour or two out..
Thanks sir...
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
icecore said:
Good Job! Waited for it! will try after reviews
Click to expand...
Click to collapse
Well its based on Phil's source, official cwm / cm 11 source using official device tree. Not much to go wrong.
If you've never used Philz recovery, try it. Lack of Philz was my only disappointment moving from s3 to n5...
Now that's resolved
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Wouldn't be surprised if this gets closed down as you're not the developer. I had my 'official' CM 11 thread removed as I wasn't a CM team member last night even thought I used CM's Nexus 4 thread and just updated it...
Thank you rootSU for opening the thread
Time is a Qualcom issue. I will look once to see how to fix it properly along all new qualcomm devices that are affected on ALL recoveries
rootSU said:
Well its based on Phil's source, official cwm / cm 11 source using official device tree. Not much to go wrong.
If you've never used Philz recovery, try it. Lack of Philz was my only disappointment moving from s3 to n5...
Now that's resolved
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
used Philz at SGS2, didn't liked it. was a little buggy with CM.
but i'm believe in improvement by time good luck! and ill try it soon (by now i mean : )
EddyOS said:
Wouldn't be surprised if this gets closed down as you're not the developer. I had my 'official' CM 11 thread removed as I wasn't a CM team member last night even thought I used CM's Nexus 4 thread and just updated it...
Click to expand...
Click to collapse
I'll report it to try and ensure that doesn't happen. The development work is original and opened (and maintained) on the behest of Phil...
Edit > well someones already reported it, but I've re-reported as stated.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Philz's supporter here since SGS2, even donated him too. good to see his work here. and thank you too, rootSU :good:
Just used this to make a backup to my flash drive...nice!
Sent from my Nexus 5 using Tapatalk
btbamzao said:
Just used this to make a backup to my flash drive...nice!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yep. I backed up and restored (and wiped) as a test before posting. Works well. Only the time issue which is non-philz specific right now.
Also obviously it's located in the correct location of /data/media/0 unlike official cwm
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
I'll report it to try and ensure that doesn't happen. The development work is original and opened (and maintained) on the behest of Phil...
Edit > well someones already reported it, but I've re-reported as stated.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
Let me know if it gets moved
Many threads were opened by advanced users like you that do provide a great support and help in debugging and releasing things
Without users like you, such projects cannot mature this way. You did a lot when this was first ported to Galaxy S3
I also allowed you to do this to be able to give second line support for advanced tech issues. Most dev threads are cluttered with general/faq questions making support a real full time job
[Kernel] - Only tested with KK Stock Rom 1.64 !
Good afternoon!
After many time of running with me head against the wall, I am glad to be able to deliver the first real version of my modified kernel with F2FS.
After some help from @ PaoloThlw8 (on androidiani) on the initial stage, and with study of multiple git's from other devices, specifically from Dorimanx to G2, AK-Kernel and UBER-N5 (Credits to Them!!), i was able to get our Nubia Z7 Max to work with F2FS.
At this stage, to get this to work, modded recovery (TWRP) and Kernel (with modules installed to system - thanks again @ PaoloTlw8) must be flashed.
I warn you all that this can be risky, i am not responsible if problems occur, but i will try to provide the safest procedure that i follow.
Needed:
- Stock TWRP recovery with EXT4 partitions;
- My 2 zip files on SDCard (Internal or External) - NX505J-NGIAKernelV1.0-F2FS-DC.zip and TWRPNGIA-F2FS-Fixed.zip .
The procedure:
1 - On your stock TWRP recovery make a full backup, then you will always be able to revert;
2 - After Backup, install my modded TWRP ("TWRPNGIA-F2FS-Fixed.zip");
3 - Reboot again to new Recovery;
4 - On new recovery can appear "can't mount /data" , no problem it's normal;
5 - Go to "Wipe", "Advanced Wipe", select "Data" and then press "FS Options";
6 - Then "Change FS", select "F2FS" and swipe to format partition;
7 - Repeat steps 5-6 but selecting "Cache";
8 - Go back to main menu of TWRP, and go to settings(right upper corner) and pick "Use rm -rf instead of formatting" - Make sure is picked! Otherwise on restore it will format back again to EXT4;
9 - Now, all set to restore Data - Go to "Restore" , select your last Backup (made on step 1), select ONLY "Data" (confirm with scroll), and proceed with restore;
10 - Done Restoring;
11 - Now time to flash "NX505J-NGIAKernelV1.0-F2FS-DC.zip" ;
12 - If all suceeded, you can now restart System and enjoy!
Find the necessary zip files here:
https:// drive.google.com/ file/d/0B1unCnE2HRL8WVlrdnNtNW90SUE/view?usp=sharing
https:// drive.google.com /file/d/0B1unCnE2HRL8UDNHaW5hMkcyYUk/view?usp=sharing
Thank You All!
Before install the rom,make sure you backup all your data!
(Warning:do it at your own risk!!! I am not responsible for any damage to your phone!!!)
First of all,credit goes to:
-@hungvip2001
-@CarlosGallego98
-Team 4PDA.ru (Go to official topic page of sm-g318h)
What work?
-Everything
Bugs?
-3G network connection sometimes drop when turning on mobile data.
(Fix in the patch give below)
-No apps to make FM Radio working. (It too mainstream )
-Offline Charging (No charging animation when the phone turn off but it still do charge )
Requirement:
-TWRP (How to get it ? Here:https://forum.xda-developers.com/an...rp-root-sm-t3331182/post65712911#post65712911)
-SD Card (atleast 1gb )
-All requirement file for the installation.
Requirement Files:
-The Rom
-GApps
(Guide to download GApps)
Choose
Platform : ARM
Android : 4.4
Variant: Nano or Pico
-3G Network Patch Fix (download link at the end of the post)
OK lets begin the installation :
(Warning:do it at your own risk!!! I am not responsible for any damage to your phone!!!)
1. Download all file requirement.
2. After that put the rom and the gapps in your external sdcard.
3. Boot in to Recovery mode (Press Power button + Home button + Volume Up at the same time)
4.Warning: This will erase all your data in internal storage!!! Make sure you backup all your data!!!!!
Go to Wipe ---> Advanced Wipe ---> Select :
-Cache
-Internal Storage
-Data
-System
Then Slide to Wipe all of it.
5. After that go to home and select Install :
-Select (Up a Level) then select external_sd.
-After that find where you put the rom and the gapps.
6. First select the rom and install it.
7. Wait for it done then go back and select the gapps.
8. After finish that select Wipe Dalvik Cache.
9. Then Reboot.
10. Enjoy
Bug fixes:
-3G Network Connection Drop
Extract renotify.zip and paste it in to \system\bin
Replace it if it ask.
Press the thanks button if it work for you
Source Rom from hungvip2001 post: https://forum.xda-developers.com/ace-4/development/rom-cyanogenmod-11-12-13-ace-4-neo-ace-t3627637
Source screenshot from 4pda.ru: http://4pda.ru/forum/index.php?showtopic=677369&st=1820#entry56365110
Mtp not bug?
ardimaul17 said:
Mtp not bug?
Click to expand...
Click to collapse
No, MTP and ART runtime are buggy.
Thanks, it's working for me
Is it lag free?