CM11 M for d605
it is based on Varcain kernel and device tree, much thanks for your work and releasing source code!
Just woke up from my slumber, because I realized, that my domain expired and links get broken.
Sorry, but nothing new, only links fix
Kernel
what is new:
More free ram, over 35MB
Screenshot: http://forum.xda-developers.com/attachment.php?attachmentid=3146159&d=1422877546
Added new cpu governor - Interactive, default scheduler is noop
Kernel modules for zRam, usb storage, gamepads, and others
Support for USB-OTG with external charger, based on ziddey's work for Mako
Source: http://forum.xda-developers.com/nexus-4/orig-development/usb-otg-externally-powered-usb-otg-t2181820
Fixed offline charging
zRam control
what is that:
Very simple app, setup zram by yourself and watch stats. zRam settings won't survive reboot!
After creation zram device, for short time, one value in stats is temporally broken because no data .
Screenshot: http://forum.xda-developers.com/attachment.php?attachmentid=3146160&d=1422877546
Framework
patched framework and settings for usb flashdisk
few UI colors changes
Install
Wipe data and cache. Then just flash archive in recovery.
Download: http://46.28.109.28/cm.zip
Source
Somehow stable source code is on my github, PM me for questions.
https://github.com/puresoul
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU Affero General Public License for more details.
OTG will work only with external charger. So you need something like that.
shall I wipe something after installation? if something goes wrong, will cmw recovery start anyway(i've installed v3 today)?
You may wipe cache and dalvik cache, but it is not needed to wipe something. Nope, installation process will not touch recovery partition.
cescom said:
shall I wipe something after installation? if something goes wrong, will cmw recovery start anyway(i've installed v3 today)?
Click to expand...
Click to collapse
Puresoul_CZ said:
You may wipe cache and dalvik cache, but it is not needed to wipe something. Nope, installation process will not touch recovery partition.
Click to expand...
Click to collapse
It works perfectly also without any wipe (i was too happy to try this that i forgot to wipe), thanks! :fingers-crossed:
No problem, thanks.
Puresoul_CZ said:
No problem, thanks.
Click to expand...
Click to collapse
Great work for RAM:good:, but i've gone to the gallery and sdcard is not recognised anymore
I have the same problem. Where I can find zRam settings?
Could you include rtl8192cu driver with your build?
edit: everything is now bundled together as a whole rom.
dundee81 said:
I have the same problem. Where I can find zRam settings?
Click to expand...
Click to collapse
Ok, thx What about mounting sdcard?
please send me dmesg log
immediately after reboot type in terminal, su; dmesg > /cache/dmesg.log
and send me that file
Thanks
Puresoul_CZ said:
please send me dmesg log
immediately after reboot type in terminal, su; dmesg > /cache/dmesg.log
and send me that file
Thanks
Click to expand...
Click to collapse
where can i send it?
Using terminal emulator, shall i use adb? because terminal emulator takes a lot to start
yes, adb is way batter
cescom said:
where can i send it?
Using terminal emulator, shall i use adb? because terminal emulator takes a lot to start
Click to expand...
Click to collapse
i suspect kernel modules, but for sure need to check log.
this may be the case, i forgot to add the permision file. Update: http://frame.jailbrake.cz/boot_v2.zip
boot_v2
I don´t read sd card
Puresoul_CZ said:
this may be the case, i forgot to add the permision file. Update: http://frame.jailbrake.cz/boot_v2.zip
Click to expand...
Click to collapse
set perm:some changes failed (cwm)
did you flash boot.zip or boot_v2.zip?
sinnombrexxl said:
I don´t read sd card
Click to expand...
Click to collapse
check please file handheld_core_hardware.xml
if exists at /system/etc/permissions/handheld_core_hardware.xml
here is that file: http://frame.jailbrake.cz/hch.zip
cescom said:
set perm:some changes failed (cwm)
Click to expand...
Click to collapse
Related
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app
For downloads and instructions please visit our TWRP website and choose your device in the dropdown menu
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
ReverendJKR posted a great video on TWRP and Goo Manager working together.. Much more to come with this relationship
http://youtu.be/OA0S275XO3U
Oh man. Awesome!
Looks nice...looking forward to trying it out.
This looks very slick!
Sent from space
Can this recovery be used on any phone/tablet?
Sent from my Desire HD using xda premium
Super cool, thanks guys, I am now into Nook Color... HD2, AMAZE 4G...
Jainyankee1993 said:
Can this recovery be used on any phone/tablet?
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
We have a list of supported devices on the main twrp2 page: http://teamw.in/project/twrp2
So I see you got that stuck in recovery bug all worked out ehh? nice work.
eyeballer said:
TeamWin is proud to present TWRP 2.0 for Nook Color!!
Click to expand...
Click to collapse
Congrats TeamWin... this is supercool.
eyeballer one of the install steps is to push "kernel" to uRecImg but there is none? Am I missing something obvious?
hm, anyway to install this on an existing install?
Midnitte said:
hm, anyway to install this on an existing install?
Click to expand...
Click to collapse
Right from their page? Though idk what kernel they are talking about.
Download the above file. Connect your Nook Color to the PC via the USB cable. This assumes you have working ADB.
Execute the following:
adb shell busybox remount / -o rw,remount
adb shell busbbox mkdir /boot
adb shell busybox mount /dev/block/mmcblk0p1 /boot
adb push twrp-encore-2.0.0RC0.ub /boot/uRecRam <--- You can change uRecRam to uAltRam for alternate boot.
adb push kernel /boot/uRecImg
adb shell busybox umount /boot
Click to expand...
Click to collapse
RileyGrant said:
eyeballer one of the install steps is to push "kernel" to uRecImg but there is none? Am I missing something obvious?
Click to expand...
Click to collapse
Nburnes said:
Right from their page? Though idk what kernel they are talking about.
Click to expand...
Click to collapse
Sorry guys, the page is updated now with the kernel link. However, we just use a stock AOSP kernel so if you had CWM on emmc already you don't need to push the kernel since it's the same.
eyeballer said:
Sorry guys, the page is updated now with the kernel link. However, we just use a stock AOSP kernel so if you had CWM on emmc already you don't need to push the kernel since it's the same.
Click to expand...
Click to collapse
Actually what I thought, thanks for clarifying man .
Oooh, i look forward to trying this.
I was not having success installing this on emmc with the adb instructions probably because busybox was not set up the same way.
So I tried an different approach which was to use the NookColor UMS app to mount the boot partition so it shows up as a USB drive on PC called boot. I then just renamed uRecRam to uRecRamOld and copied in twrp-encore-2.0.0RC0.ub and renamed that to uRecRam. I didn't bother copying the kernel as per the previous posts.
Rebooting into recovery then brought up the TWRP recovery which looks very nice to use. Also works off the power up N after emmc recovery selected as expected.
Clockwork has given me good service but I think I'll be using this going forward.
bobtidey said:
I was not having success installing this on emmc with the adb instructions probably because busybox was not set up the same way.
So I tried an different approach which was to use the NookColor UMS app to mount the boot partition so it shows up as a USB drive on PC called boot. I then just renamed uRecRam to uRecRamOld and copied in twrp-encore-2.0.0RC0.ub and renamed that to uRecRam. I didn't bother copying the kernel as per the previous posts.
Rebooting into recovery then brought up the TWRP recovery which looks very nice to use. Also works off the power up N after emmc recovery selected as expected.
Clockwork has given me good service but I think I'll be using this going forward.
Click to expand...
Click to collapse
I had to do the same thing. Kept getting an error that "applet not found" for busybox in adb.
Thanks for the alternate method.
This is a much better implementation of our hardware in backup.
Thanks TeamWin.
Nburnes said:
Right from their page? Though idk what kernel they are talking about.
Click to expand...
Click to collapse
It wasn't there before! I swear! /thanks
Hm, is usb storage working for anyone?
The only thing I don't really care for is... and I know I am doing things in a unique way....
I have SASD with CM7 on it... verygreen's recovery as alt-boot and replaced CWM with TWRP as recovery mode on the uSD... when in TWRP and reboot... it boots stock on eMMC instead of a normal boot... it should do a normal boot (uSD first)
Update: Just flash the flashable zip and use the app in my signature!
Download
-------------------- OLD POST BELOW ------------------------
I am trying to get support for USB OTG and NTFS support for FXP kernel too..
Hence I have compiled required modules against the FXP kernel source.
I am posting here to get maximum eyeballs of FXP kernel users.
If you are willing to test, please download and extract the files to /data/local/tmp
Then on terminal (adb shell / terminal emulator / script manager console ), try to insmod these modules like so (one line at a time)
Code:
insmod /data/local/tmp/usb-storage.ko
insmod /data/local/tmp/ntfs.ko
insmod /data/local/tmp/fuse.ko
insmod /data/local/tmp/isofs.ko
lsmod
Please post your output here..
Thanks for your time.
Download
shardul_seth said:
I am trying to get support for USB OTG and NTFS support for FXP kernel too..
Hence I have compiled required modules against the FXP kernel source.
I am posting here to get maximum eyeballs of FXP kernel users.
If you are willing to test, please download and extract the files to /data/local/tmp
Then on terminal (adb shell / terminal emulator / script manager console ), try to insmod these modules like so (one line at a time)
Code:
insmod /data/local/tmp/usb-storage.ko
insmod /data/local/tmp/ntfs.ko
insmod /data/local/tmp/fuse.ko
insmod /data/local/tmp/isofs.ko
lsmod
Please post your output here..
Thanks for your time.
Download
Click to expand...
Click to collapse
Is this for FXP 125 kernel?
I'm on FXP 126 + official CM9 for a day or two and it doesn't work here. The scripts were executed successfully but I still get "No Drives found to mount error"
But I gotta thank you for your quick response!! :good:
rakmth said:
Is this for FXP 125 kernel?
I'm on FXP 126 + official CM9 for a day or two and it doesn't work here. The scripts were executed successfully but I still get "No Drives found to mount error"
But I gotta thank you for your quick response!! :good:
Click to expand...
Click to collapse
Connect your drive and enter
Code:
dmesg | tail -n 30
lsmod
ls /dev/block/sd??
And copy-paste the output
shardul_seth said:
Connect your drive and enter
Code:
dmesg | tail -n 30
lsmod
ls /dev/block/sd??
And copy-paste the output
Click to expand...
Click to collapse
here are the screenshots.
rakmth said:
here are the screenshots.
Click to expand...
Click to collapse
Your modules are not live.. What was the output of insmod?
Is working
Do not know if I did right. But it worked, put a couple of screen shots to confirm.
Thank you for the work, I appreciate.
juninromualdo said:
Do not know if I did right. But it worked, put a couple of screen shots to confirm.
Thank you for the work, I appreciate.
Click to expand...
Click to collapse
If you just type insmod it does nothing at all, you need to write path to the module after as in OP.
juninromualdo said:
Do not know if I did right. But it worked, put a couple of screen shots to confirm.
Thank you for the work, I appreciate.
Click to expand...
Click to collapse
Yes, congrats! You got it right.. Did you test the app.. It should work now. I will make a CWM flashable zip (or just push the modules to /system/lib/modules/ folder and chmod 644 /system/lib/modules/*)
adridu59 said:
If you just type insmod it does nothing at all, you need to write path to the module after as in OP.
Click to expand...
Click to collapse
See his 2nd try in attached screenshot. Exit code is [ ! $? -gt 0 ]
Flashable zip added, see OP
adridu59 said:
If you just type insmod it does nothing at all, you need to write path to the module after as in OP.
Click to expand...
Click to collapse
So I did the procedure with the correct path, the problem that the terminal android just shows all the way if you are in landscape mode.
Thank you (shardul_seth) for .Zip and have solved a lot of research and questions.
shardul_seth said:
Flashable zip added, see OP
Click to expand...
Click to collapse
After flashing the zip, would it load modules automatically upon boot? Or should I create init.d script to load it upon boot.
ameer1234567890 said:
After flashing the zip, would it load modules automatically upon boot? Or should I create init.d script to load it upon boot.
Click to expand...
Click to collapse
No, just use the app in my signature.. It will do the rest for you!
shardul_seth said:
No, just use the app in my signature.. It will do the rest for you!
Click to expand...
Click to collapse
Oh! I see! Your app is great, btw!
OTG, if implemented correctly, will allow us to plug usb mass storage devices into the phone.. Am I right?
What about USB HID? will this be possible?
What cable shoul be used?
vovkav said:
OTG, if implemented correctly, will allow us to plug usb mass storage devices into the phone.. Am I right?
What about USB HID? will this be possible?
What cable shoul be used?
Click to expand...
Click to collapse
Yes, all of these are already implemented. See the app in my signature!
phone reboots
shardul_seth said:
Yes, all of these are already implemented. See the app in my signature!
Click to expand...
Click to collapse
I'm currently on FXP 136. I've flashed the modules and installed the app but whenever I open the application, my phone reboots.
Possible reason for this???
shardul_seth said:
Yes, all of these are already implemented. See the app in my signature!
Click to expand...
Click to collapse
Shardul is there any chance that the modules would work with JB AOKP rom and kernel - this one for example?
http://forum.xda-developers.com/showthread.php?t=1614562&highlight=fxp
Abhilesh7 said:
I'm currently on FXP 136. I've flashed the modules and installed the app but whenever I open the application, my phone reboots.
Possible reason for this???
Click to expand...
Click to collapse
Same issue for me too, any fix for this???
-Arturo- said:
Shardul is there any chance that the modules would work with JB AOKP rom and kernel - this one for example?
http://forum.xda-developers.com/showthread.php?t=1614562&highlight=fxp
Click to expand...
Click to collapse
freaktechz said:
Same issue for me too, any fix for this???
Click to expand...
Click to collapse
The modules given by shardul don't work for jb, they are only for ics, I guess.
Searching XDA, i came across this thread http://forum.xda-developers.com/showthread.php?t=1780326&page=92.
1) Download the modules for CM10 FXP136.
2) Flash the zip through recovery
3) Mount the USB drive using Shardul's app.
These modules worked for me and I was able to mount a 2GB Transcend Pen Drive.
@Arturo - Try this for AOKP.
@freaktechz - This should solve the issue.
Download the Modules here.
http://www.faircode.eu/freexperia/
Credits to:
1) M66B - for the modules
2) shardul_seth - for the app.
Abhilesh7 said:
The modules given by shardul don't work for jb, they are only for ics, I guess.
Searching XDA, i came across this thread http://forum.xda-developers.com/showthread.php?t=1780326&page=92.
1) Download the modules for CM10 FXP136.
2) Flash the zip through recovery
3) Mount the USB drive using Shardul's app.
These modules worked for me and I was able to mount a 2GB Transcend Pen Drive.
@Arturo - Try this for AOKP.
@freaktechz - This should solve the issue.
Download the Modules here.
http://www.faircode.eu/freexperia/
Credits to:
1) M66B - for the modules
2) shardul_seth - for the app.
Click to expand...
Click to collapse
After flashing that module application says No NTFS Write support.Fails to load any usb drives too...
Unofficial build of SlimKat
Dont post in official threads please. I may have messed something up and i dont want to bother other people because of my mistakes.
After leeching for years on XDA (didnt even had an account) i finaly decided to give something back to the community.
Features:
Im using the build scripts from Slimsaber
Features of Slimsaber but not all are working!
Used newest Linaro 4.8.3 (2014.04) optimized for cortex-a15 from here for kernel and rom.
Did some patches so it compiles with strict-aliasing :victory:. But i hate those freaking pointers. So maybe i messed something up.
all the nice placebo compile flags: -O3 -mcpu=cortex-a15 -mfpu=neon-vfpv4 -mfloat-abi=softfp -funroll-loops -fomit-frame-pointer
Other flags:BOARD_USES_HGL := true, BOARD_USES_OVERLAY := true, USE_OPENGL_RENDERER := true, TARGET_USES_ION := true, TARGET_USES_C2D_COMPOSITION := true
all the nice placebo build.prop tweaks: debug.sf.hw=1, debug.composition.type=c2d, debug.performance.tuning=1, persist.sys.composition.type=c2d, persist.sys.ui.hw=1, hw3d.force=1, hw2d.force=1, video.accelerate.hw=1, force_hw_ui=true, debug.egl.hw=1, debug.overlayui.enable=1 (actualy i dont know which ones are working and which ones arent even in the code )
f2fs for data and cache partition. (I think the first released z ultra rom with f2fs. Correct me if im wrong please)
DPI set to 280 (tablet layout).
Install instructions:
Be running at least Android 4.3 or 4.4.2 with an unlocked BL (14.2.A.0.290, 14.2.A.1.136, 14.3.A.0.681 or 14.3.B.0.757 etc)
Make a backup of everything on your phone. Im not responsible for any loss of data!
Boot into recovery
Factory reset/wipe data
Flash FormatPartitions-userdata_cache.zip
This will format data and cache partition to f2fs
WARNING: this will DELETE ALL DATA on your data partition. Even InternalSD! Make a backup beforehand!
Flash PlaceboRom
Install Gapps (I use this one)
Optional: for even more placebo install this soundmod.
Not Working:
Nothing known
Not Tested (would be nice if someone could test it):
ART
Miracast
Other models then C6833
Bugs:
WARNING: ADB/USB Debbuging is always enabled on reboot! So if you have sensitive data on your phone this ROM is NOT for you! (maybe someone can help. tried to disable it via build.prop and settings.db but didnt work . I think it has something todo with the build scripts from Slimsaber but hadnt had time to check it.)
[*]After installing the ROM for the first time you have to go to developer settings and disable root and reenable it in order for it to work!
Its already set to apps only after installing but it wont work! You only have to do this once. If you reflash you dont have to do it again.
Some graphics glitches because of "USE_OPENGL_RENDERER := TRUE" in some system apps (like Browser).
Actualy i read somewhere that its not needed but it wouldnt be placebo without it
If you use MHL some of the screen will not be displayed (It displays only like 1900*1000)
Downloads:
FormatPartitions-userdata_cache.zip. Credits goto legolas83
PlaceboRom-togari-4.4.2-20140515.zip
RestorePartitions_ext4_userdata_cache. If you want to go back to another rom. Credits goto legolas83
I will try to build every two weeks.
I had only one freeze on my device (C6833) in over 1,5 months (with older builds) but consider these build as NOT STABLE. I dont want that you lose your job because of me.
Special thanks to team slimroms.
Visit official website at http://www.slimroms.net
Slimsaber is the inspiration for this rom. High five @fusionjack.
If I have time i will setup a github account so contributions will be clear.
At the moment im using repos from Slimkat, Slimsaber, CyanogenMod, VanirAOSP, AOKP, Linaro
If i missed something or didnt gave proper credits i can assure that this is a mistake.
Contact me please so i can correct it.
XDA:DevDB Information
PlaceboRom, ROM for the Sony Xperia Z Ultra
Contributors
MusterMaxMueller, fusionjack, [vertigo], dboliver, blueether, Christopher83, legolas83, prbassplayer, SlimRoms, CyanogenMod, VanirAOSP, AOKP, Linaro, FreeXperia, CodeAurora, Google
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 14.2.A.0.290, 14.2.A.1.136, 14.3.A.0.681, 14.3.B.0.757 or newer
Based On: SlimKat, CynanogenMod, VanirAOSP, AOKP
Version Information
Status: Testing
Created 2014-05-15
Last Updated 2014-05-15
Reserved
Only changes i did to slimkernel was enabling f2fs in defconfig and some buildflags in the Makefile for kernel.
Does anyone know do i have to release my changes to be GPL compliant? defconfig is generated so i think not but what about Makefile?
Im not familiar with GPL but want to do everything correct.
Reserved
OK my install instructions seems to be wrong after reading them again. :silly:
Can anyone confirm? It shouldnt work the first time.
Sorry to anyone who had problems.
I think you have to:
Boot into recovery
Flash PlaceboRom (you have to flash it the first time. Otherwise there might be no f2fs support in your current kernel+recovery)
Reboot to recovery (after that you will have f2fs support)
Flash FormatPartitions-userdata_cache.zip
This will format data and cache partition to f2fs
WARNING: this will DELETE ALL DATA on your data partition. Even InternalSD! Make a backup beforehand!
Flash PlaceboRom again!
Install Gapps (I use this one)
Optional: for even more placebo install thissoundmod.
Could someone be kind and when installing the rom for the first time report back if this new install instruction is working?
It was some time ago i did it so im not sure anymore.
If somone confirms i will update op.
Looks promising, yah the first F2FS! :highfive:
MusterMaxMueller said:
Only changes i did to slimkernel was enabling f2fs in defconfig and some buildflags in the Makefile for kernel.
Does anyone know do i have to release my changes to be GPL compliant? defconfig is generated so i think not but what about Makefile?
Im not familiar with GPL but want to do everything correct.
Click to expand...
Click to collapse
Any changes in the kernel need to be published, and the aosp/cm/slim code, what is less clear is whether compile flags etc (changes to make files) need to be published - my feeling is that yes they do need to be published. That's some thing I haven't done for carbon as of yet.
At the moment I think you are probably ok?
keep it up mate...looking forward for this rom. :good:
@blueether
I think i dont get you. AOSP/Slim is released under ASL. So changes made to rom dont need to be published? Altough i will when i have time. And is defconfig considered part of the kernel? Because of "make menuconfig"? Does anyone know for sure? If i interpret this and this correctly changes to Makefile have to be published but defconfig not. They even mention build flags!I know its pedantic just want to know. It seems there is no defenite time frame when sources have to be published?
blueether said:
Any changes in the kernel need to be published, and the aosp/cm/slim code, what is less clear is whether compile flags etc (changes to make files) need to be published - my feeling is that yes they do need to be published. That's some thing I haven't done for carbon as of yet.
At the moment I think you are probably ok?
Click to expand...
Click to collapse
I would interpret it as everything that is needed to build the same binary
Not looked at the details of asl
Sent from CarbonROM on my Z-Ultra
I followed direction to the t. and it's hanging at boot animation now for ten minute. Now. What am doing wrong?
cameljockey1 said:
I followed direction to the t. and it's hanging at boot animation now for ten minute. Now. What am doing wrong?
Click to expand...
Click to collapse
did you flash gapps..I did with gapps and even w dalvik and cache wipe it was hanging up...so i redid procedure again without gapps..booted fine
mac231us said:
did you flash gapps..I did with gapps and even w dalvik and cache wipe it was hanging up...so i redid procedure again without gapps..booted fine
Click to expand...
Click to collapse
That did it thank you.
reread it. i think youre right
blueether said:
I would interpret it as everything that is needed to build the same binary
Not looked at the details of asl
Sent from CarbonROM on my Z-Ultra
Click to expand...
Click to collapse
i have no problems using minimal gapps from op.
try using the one from op.
cameljockey1 said:
I followed direction to the t. and it's hanging at boot animation now for ten minute. Now. What am doing wrong?
Click to expand...
Click to collapse
F2FS mount and sysfs options
For those interested in tweaking F2FS, check my post here.
wrong install instructions
OK my install instructions seems to be wrong after reading them again. :silly:
Can anyone confirm? It shouldnt work the first time.
Sorry to anyone who had problems.
I think you have to:
Boot into recovery
Flash PlaceboRom (you have to flash it the first time. Otherwise there might be no f2fs support in your current kernel+recovery)
Reboot to recovery (after that you will have f2fs support)
Flash FormatPartitions-userdata_cache.zip
This will format data and cache partition to f2fs
WARNING: this will DELETE ALL DATA on your data partition. Even InternalSD! Make a backup beforehand!
Flash PlaceboRom again!
Install Gapps (I use this one)
Optional: for even more placebo install thissoundmod.
Could someone be kind and when installing the rom for the first time report back if this new install instruction is working?
It was some time ago i did it so im not sure anymore.
If somone confirms i will update op.
download not working
The download anyway at Google Drive is not generating any download dialog box upon clicking:
Google Drive can't scan this file for viruses.
SlimSaber-togari-4.4.2-20140515.zip (198M) exceeds the maximum size that Google can scan. Would you still like to download this file?
Download anyway
Please upload to mega or somewhere else
Premananda_laishram said:
The download anyway at Google Drive is not generating any download dialog box upon clicking:
Google Drive can't scan this file for viruses.
SlimSaber-togari-4.4.2-20140515.zip (198M) exceeds the maximum size that Google can scan. Would you still like to download this file?
Download anyway
Please upload to mega or somewhere else
Click to expand...
Click to collapse
I'm uploading to mega atm, should be up in about 20 - 30 min
Google Drive mirror: https://drive.google.com/a/fryett.net/file/d/0B2qGRw4S7bAuUkxWVzVXQzNJOXc/edit?usp=sharing
Mega mirror: https://mega.co.nz/#!9pt1xSQL!ozJyip-yzATId0_Po7sG1_sisWH8UfnNVOhHmxh-4fA
Premananda_laishram said:
Please upload to mega or somewhere else
Click to expand...
Click to collapse
you could also use the download tab ?
not working
Flashing instructions not working. Hangs at boot logo
Premananda_laishram said:
Flashing instructions not working. Hangs at boot logo
Click to expand...
Click to collapse
which install instructions doesnt work?
the first or the second one?
try first without flashing gapps.
Was this already known ? Thought not, right ?
Anyway look for source : https://dl.twrp.me/ailsa_ii/
raystef66 said:
Was this already know ? Thought not, right ?
Anyway look for source : https://dl.twrp.me/ailsa_ii/
Click to expand...
Click to collapse
Ey buddy I need your help , magisk keep forgetting my rooted apps ... I forgot whats the command I have to run on terminal emulator can you please help me !
luisaet82 said:
Ey buddy I need your help , magisk keep forgetting my rooted apps ... I forgot whats the command I have to run on terminal emulator can you please help me !
Click to expand...
Click to collapse
if it's this what you're referring too...
In terminal :
Code:
su
reboot disemmcwp
or adb :
adb shell reboot disemmcwp
raystef66 said:
if it's this what you're referring too...
In terminal :
or adb :
adb shell reboot disemmcwp
Click to expand...
Click to collapse
The first one ... Thank you so much .. great night
So its about twrp and first reaction is off topic...why you dont pm him?!!
Predatorhaze said:
So its about twrp and first reaction is off topic...why you dont pm him?!!
Click to expand...
Click to collapse
Big deal...that's called helping someone out you know.
You could have pm me or him too you know
And really? All those exclamation marks too? I suggest to ease down (and I know you already a bit longer then yesterday...) your comments are from time to time most inappropriate. I leave it with that
Can i flash the latest version when i have the treble recovery from nfound?
@BaamAlex the version 3.2.3.0 has as far as I could see that on my axon 7 no treble support
Chris axon 7 said:
@BaamAlex the version 3.2.3.0 has as far as I could see that on my axon 7 no treble support
Click to expand...
Click to collapse
Have you installed this here?
Yes
raystef66 said:
Was this already known ? Thought not, right ?
Anyway look for source : https://dl.twrp.me/ailsa_ii/
Click to expand...
Click to collapse
Wow. This completely flew past me (and probably most of the xda community lol). Gonna check it out later. Thanks for telling us
Was this the same release that Nfound said was using older sources than his custom release?
This version boots as it should even with a fully loaded f2fs data partition. Finally the f2fs bug in TWRP has been solved!!!!!
Oki said:
This version boots as it should even with a fully loaded f2fs data partition. Finally the f2fs bug in TWRP has been solved!!!!!
Click to expand...
Click to collapse
Can we use that TWRP on treble? It will be better if we format all partitions to f2fs?
Aviver said:
Can we use that TWRP on treble? It will be better if we format all partitions to f2fs?
Click to expand...
Click to collapse
This TWRP works perfectly with treble roms. The main limitation is the inability to wipe, format, backup and restore the vendor partition using the menu system. You can always use the terminal to manage all that. For integrated vendor management, your only option so far is TWRP 3.2.1-8 Treble.
F2FS is a filesystem aimed to ssd storage devices. It provides an efficient and elaborated write policy that takes advantage of the flash memory. Reads are not specially efficient, this is why ext4 is used for read only partitions and f2fs for read/write partitions. So, system and vendor are ext4 while data and cache should be f2fs.
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices.
*/
Click to expand...
Click to collapse
Here is the latest iteration of kuailexs's Ubuntu Touch 16.04 build, alpha V0.1.4. I've uploaded it to Googledrive for your convenience... (this is not my work)
Click Here To Download
Github
UBPorts Website
Supposedly the following is working:
Boot - OK
Bluetooth - OK
Camera
Cellular Radio-OK
GPS
Graphics - OK
Resume - OK
Rotation - OK
Sound - OK
Touch - OK
Wifi - OK
anbox-kernel-OK
Here is a brief news article in Chinese relating to the V0.1.3 build, with mention of Anbox support, including brief instructions.
Original article: https://hacpai.com/article/1543854794147
Translated article: https://translate.google.co.uk/tran...en&u=https://hacpai.com/article/1543854794147
Lastly, the build was obtained from here: https://pan.baidu.com/s/1dEZDZbj#list/path=/ROM/ubuntu-touch-cancro for future reference.
Installation instructions:
...................................
< IMPORTANT INFO > MAKE SURE YOU HAVE ENOUGH FREE SPACE IN INTERNAL STORAGE OTHERWISE YOU WILL GET STUCK AT THE SPLASH SCREEN < IMPORTANT INFO >
1) Boot to TWRP
2) Wipe data, system, cache & dalvik cache
3) Install provided rom package "ubuntu-touch-16.04-cancro-Alpha-0.1.4.zip"
The default lockscreen passphrase is: 0000 which is set automatically with no prompt for the user to change/set on device setup wizard.
The passphrase can be removed or changed from within the settings though...
Also please note, this rom package replaces your installed recovery with a UBPorts based recovery.
Click to expand...
Click to collapse
When returning to android, I recommend replacing the UBPorts recovery with TWRP via fastboot.
...................................
1) Volume Down + Power Btn
2) Fastboot flash recovery /location/of/your/recovery_image.img
3) Fastboot reboot
4) Enter Recovery with Volume Up + Power Btn
5) Wipe data, system, cache & dalvik cache
6) Install your ROM zip.
Click to expand...
Click to collapse
Have fun.
May I will try this. Thanks for sharing.
Working. ...a little bit buggy, but very nice!
Sooo...
https://i.ibb.co/tbxb1Sb/IMG-20191111-150301.jpg
https://i.ibb.co/gFyC4Gd/IMG-20191111-150509.jpg
https://i.ibb.co/94bLSD8/IMG-20191111-150753.jpg
https://i.ibb.co/RDj0dtG/IMG-20191111-150810.jpg
https://i.ibb.co/X5byZKX/IMG-20191111-150556.jpg
https://i.ibb.co/pKmFNbW/IMG-20191111-150727.jpg
https://i.ibb.co/WkKPcCY/IMG-20191111-150742.jpg
MI3 is an immortal phone! This is unimaginable!
小米6X全网通6GB64GB 银灰MIUI11
App store working correctly. Applications are updated without problems.
But. About Ubuntu Touch updater found 390MB, but it unable to download beacuse on incorrect protocoll...it ttried to download from http:// path but the correct is https:// path.
I can download update file from correct protocol/path...I have no idea what can I do with the downloaded "ubports-8fe6a3624913e47121f89aa9f4b5a7975b4897ca50691a4debbdda409cd69083.tar.xz" update file...
Really, Camera freezes again and again...sadly, unfortunately this is a very critical mistake.
Increase Cache partition size
JulianJenner said:
App store working correctly. Applications are updated without problems.
But. About Ubuntu Touch updater found 390MB, but it unable to download beacuse on incorrect protocoll...it ttried to download from http:// path but the correct is https:// path.
I can download update file from correct protocol/path...I have no idea what can I do with the downloaded "ubports-8fe6a3624913e47121f89aa9f4b5a7975b4897ca50691a4debbdda409cd69083.tar.xz" update file...
Really, Camera freezes again and again...sadly, unfortunately this is a very critical mistake.
Click to expand...
Click to collapse
In order to successfully update, you need to increase your cache partition. The default partition size is around 370mb and you need almost 500mb so resize your partition size to about 750mb. If you do not know how to resize your partition refer to the following link :
https://iwf1.com/how-to-re-partitio...ll-options-included-change-size-fs-type-etc/2
or
https://forum.xda-developers.com/android/general/info-android-device-partitions-basic-t3586565
use parted program from adb shell in twrp recovery.
This is great! I installed this a some time ago, to give ubports a try. Other than it feeling a little slow at times its pretty cool to have full Linux on my MI3
Anyone figured out how to speed some things up? Or is it really the age of the device showing up here?
can someone update the download link to Alpha 0.1.5? I tried downloading on Baidu but I cant understand chinese and it seems that you need to download their client and an acc before downloading
So I tried install 0.1.4 since i cant get the 0.1.5 so far its working just fine but how do I install anbox?
alpha 0.1.5 always reboot in minutes
(MIUI_7.5.6.0_cn……fastboot flash TWRP_recovery_3.5.2……resize cache to 750MB……wipe……install 0.1.5.zip……reboot system)