Database Users

[ROM] « Serendipity 6.4 » **4/13** [FINAL]

"...the best choice for a custom ROM on the Captivate" - AndroidCentral
Number One In Random And Plausibly Flawed Battery Testing By Random Persons
6.4
Added 2048 SD Card Script
Added Ram Booster Script
Added Permissions Fix Script
Updated Market
UI Tweaks
SERENDIPITY WEBSITE

A few words about the Optional But Totally Awesome Steam Kernel
Ok, so hopefully you read a bit about it in SzutpY's post. I compiled Steam recovery in English and made a kernel utilizing it. The kernel is similar in many ways to the Universal Lagfix Kernel SztupY also created. It has many of the same lagfix schemes, kernel tweaks, etc, again, all with a touchscreen interface. Other than Steam recovery, this kernel is identical to my 12-23 oc/uv kernel, so it's overclocked, and undervolt configurable, and it should be just as stable as that one.
Do not attempt to take the zImage with Steam recovery and place it in a flashable zip. You'll be a sad panda if you do. I'd advise waiting a few minutes after your system has booted to flash with Neldar's app. If you're using Odin, or Heimdall, reboot to download mode and flash like normal. Those are the options, either Neldar's app (AND NOT Tuxility!!) There are issues with flashing this via redbend_ua - the regular kernel can be flashed via redbend_ua, Steam cannot be.)
Steam recovery is based on ClockworkMod, but you have a touchscreen interface at recovery. Steam has many options to lagfix your system. So, you can have an all ext4 system (including /system), an all jfs system (again, including /system) or something in between. Read through sztupy's posts about Steam, or spend some time playing with it. I have to admit I was a little skeptical of it at first, but after using it for the last week or so, I absolutely love it.
If you're doing a filesystem conversion from Steam recovery, the zeroth thing you should do is check to make sure you have enough room on your SD card to copy /system, /data, /dbdata, and /cache. Then, make a backup. Occasionally after a filesystem conversion, the system will bootloop. Performing a three button forced reset and rebooting solves this. (In my experience at least. Like I said, make sure to backup first.)
If you do choose a No-RFS lagfix in Steam - Make sure you disable it before flashing another kernel/ROM. No-RFS uses a fake /efs to get a completely-rfs free ROM (only works if /system is set to be mounted as rw).
If it seems as though you've lost su (root)
So, I don't know why Steam does this, but the reason people were losing su was because it was automatically mounting /system nosuid. So, to fix this, there's probably more than one way to do this, but an easy way is to go into Steam, under boot options, select 'Always run adb as root' or something like that. Then reboot, open a terminal and type
Code:
mount -o remount,suid /dev/block/stl9 /system
. That will remount su access to /system (pretty important ), and then you will have root again, and Steam is finally usable again. Flash another kernel or whatever) I was really hoping I could blame this on something MikeyMike did, hmm...I may still find a way. ( Alternatively, it seems if you do a filesystem conversion on /system, /system will be remounted suid so you won't have to go through this, and I think /system conversions don't end up in boot loops like /data and /dbdata.
Credits
Xcaliburinhand - without whom we'd all be on JJ4 and JI6. *shudder*
SztupY - Steam recovery is the shiz.
raspdeep, neldar, xan
I'll probably edit this a few more times as there will be things that I want to add but have slipped my mind for the moment.
Ok - I uploaded a copy of the Steam kernel here. It deserves its own thread and it will get one, just don't feel like doing it right now. Read through this post, realize there are some errors with filesystem conversion. Make sure you do backups, if you get into a boot loops, do a hard reset and reboot normally, you should be good. This is meant to be flashed via Neldar's SGS Kernel Flasher app, or something like Heimdall or Odin.

Alright...lets get started
Sent from my liberated Captivate via XDA App.

Just when I think I've finally found a ROM to stick with (Phoenix 1.0) after flashing just about every ROM I see on XDA.......along come some new candy!

yes!!!! definetely gonna donate thanks so much for the hard work mikey!!

Am I the only one that prefers the original clock/alarm that was on the phone? Select custom ringtone is nice and it seems easier than the car/home.
Sent from my SGH-I897 using XDA App

gdbusby said:
Am I the only one that prefers the original clock/alarm that was on the phone? Select custom ringtone is nice and it seems easier than the car/home.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
i love the original too. :/

Weeee!!! Finally!!!! Let see the awesomeness!!!
Running Assonance 5.0 - SpeedMod 256hz K12H - JL2

Mikey, does this contain the jpa wifi fix and external SD mount fix? Thanks.
Sent from my liberated Captivate via XDA App.

This post is no longer relevant. STOP LOOKING AT IT

I have two kernels in this, why do I have to keep hitting F5?

I guess my first post got deleted so I will do another one. This looks like it is going to be good.i actually enjoy the simplistic look.
Sent from my SGH-I897 using XDA App

Download's up.

Trying it out. Thank you.
Sent from my GT-I9000 using XDA App

and I was about to download your other rom.

madjsp said:
and I was about to download your other rom.
Click to expand...
Click to collapse
I was waiting for you to be about to download the other one so I could release this one.

just when i thought i would stop flashing today i see another rom come out.. life of a rom addict

Does this have the AOSP MMS App as well?

How is your Guy's battery life with this
Sent from my SAMSUNG-SGH-I897 using XDA App

LolBoot xD SGS2 dualboot - NEW 12.12.11: Easy-Setup App v2.51

(I wasn't really sure if this might fit into "Development", so I put it here, maybe a mod will move it, if it's a dev topic )
Anyways, here we go, I DUALBOOTED two different, independant ROMs on the S2
Video of dualboot in action: http://www.youtube.com/watch?v=l9-V_6Ua_D0
** THIS IS NOT (YET) COMPATIBLE **
** WITH ICS (ANDROID 4.0.x) ROMS! **
-- this goes for custom ROMs as well as stock ROMs --
Icey Sammich compatibility will be added once Sammy released their ICS kernel sources.​
!!! There now is an app for more convinient and easy setup of the dualboot !!!
(04.11.2011) DualBoot setup app v2.00: http://forum.xda-developers.com/showpost.php?p=19049047&postcount=94
(12.12.2011) App has been updated to 2.51, lot's of good new stuff! >> Free Version -- Donate Version <<
Click to expand...
Click to collapse
First off:
This is only a little experiment I did like "c'mon, has to be possible" - this is NOT (at least yet) tweaked for usability and anything the like, just a humble experiment.
That said, don't flame me if things are rather complexicated to do this ATM.
Maybe I'll come up with a more userfriendly way of setting this up, maybe someone else does, maybe no one does.
Also now that I found a base on what to do, there might be different ways (more easy ones maybe) to set this up, I'll keep toying around with it.
But let's cut to the chase, shall we
So, how was this set up? I'll give a brief rundown of what I did:
I edited a few .rc files in the initramfs of the kernel to make it actually perform a full boot when recovery mode was triggered and to fire up recovery mode when in battery-charging mode.
I also edited a few mounts in the boot .rc for the 2nd OS (in "recovery" mode) to use different partitions for /system and /data, so that we'd end up with really independant installs.
What partitions did I missuse for that:
partition 12 (mostly unused, only when installing a stock ROM AFAIK) for /system - that's a neat choice IMO as p12 is 512MB in size, just as p9 where /system usually sits on
partition 7 (which is usually /cache) for /data
gives us only 100MB of user data space, but for now that's OK, as said, it's only an experiment on how such a thing could be done.
with the original partition for /cache "gone", I mounted a tmpfs for it.
So the OS still has a usable /cache
Then I set up the two OSes:
(dualboot kernel not yet flashed)
Launchprep part 1:
I made a CWM backup of my normal installation I was running (stock XXKG6 at the time).
I installed DevNull-Test AOSP as to it's instructions
Some su'ed voodoo via a terminal while having the 2nd OS (the DevNull AOSP one, in this case) installed - best done in recovery mode via ADB:
rm -Rf /cache/*
cp -Rp /data/* /cache/
dd if=/dev/block/mmcblk0p9 of=/dev/block/mmcblk0p12 bs=4096
That did "set up" the 2nd OS to where it's supposed to go.
Launchprep part 2:
Then, "advanced restore" of the backup made a few minutes earlier:
- boot
- system
- data
Reboot
At this point OS #1 is running again and OS #2 is sitting in hiding, prepared to roll - so, let's roll:
Flashed the modified "dualboot kernel" (via an App or Odin or magic, doesn't matter).
---> DONE <---
reached the point to where everything works as shown in the video.
As said above already, yes it needs some manual work to set it up, yes there's a lot of things that might not work, yes there are other/better ways to set it up.
It's only a humble experiment - lot's of space for improvement.
Maybe you like it - for those who do, I wanted to share this
Attached to this post you find the modified kernel I used, it's based on my v1.20 custom kernel (see sig) but with the above mentioned changes.

I've seen the video m8, this is totally different approach, ur giving this device a new dimension. love u "in a straight way" hahaa

there currently an app called Bootmanager which also handle up to quadruple booting. But sadly currently only support HTC phones.
http://www.appbrain.com/app/bootmanager/com.drx2.bootmanager
well, one can hope!

Thanks OP this is an awesome concept! Very happy to see you posted it with a video! and nice boot animation!

sunwee said:
there currently an app called Bootmanager which also handle up to quadruple booting. But sadly currently only support HTC phones.
Click to expand...
Click to collapse
Yeah, that's the thing.... that app is HTC only.... but we have Samsung S-II and want dualboot as well.
I'm already brainstorming on how to enhance the actual usability of this, i.e. flashing a 2nd OS directely to it's place instead of first installing it to the main system partition. But there is problems when /data is not mounted to the original partition, at least stock doesn't like it on initial boot.... well, well....

That is great. Going to use this for sure. This should be in development for sure.
Congratulations already.
Sent from my GT-I9100 using Tapatalk

This is impressive bro sure will use it
but i want to ask one thing
SD card needed for this or not ?

That would be really cool (and definitely should goes to original development). Does it work with CM7/MIUI + custom rom?

vikas776 said:
SD card needed for this or not ?
Click to expand...
Click to collapse
No, so far this completely works with all internal storage.
But I have a few ideas I have yet to try to get mounted from other places - like images in /sdcard for example (I *so* hope that'll work.... )

Hi
Does this kernel include any of the Hellcat kernel tweaks or are they work in progress.
Sent from my GT-I9100 using Tapatalk

Tricky103 said:
Does this kernel include any of the Hellcat kernel tweaks or are they work in progress.
Click to expand...
Click to collapse
I made this build based on my v1.20 custom kernel, so it has everthing that one has - plus the touchfix already

exactly what i was hoping for.
great job - pls continue your work

Hi i tried this with instanity rom last night. When I use the three buttons to boot it just sits there not booting. My guess is the kernel is not compatible. Unless I made a mistake somewhere.
Sent from my GT-I9100 using Tapatalk

Hm, yah, might be that the kernel isn't fully compatible with that ROM, what kernel does the ROM usually use?
Did you boot it up fully at least once before copying /data to /cache ?

Yes I did fully boot up. But his kernel didn't have advanced activated in recovery so I flashed your kernel and moved the cache okay. But it said /data not found when I ran the 2nd command line.
I will flash aosp later. I like that rom.
I am not sure what kernel nitr8 uses. I think it is his own, Insane.tar would you like it to see if they can work together.
Sent from my GT-I9100 using Tapatalk

Tricky103 said:
But it said /data not found when I ran the 2nd command line.
Click to expand...
Click to collapse
Hm, yeah, that sounds like something didn't work.... make sure you run those commands as root, i.e. "su" as very first command (I'll add that to the first post).
Give me a direct link to the ROM and I'll try it.
Make take a few days though as I'm away from my computer a lot because of work the next two days, but I'll try once time permits.
Well yeah, and this still is in highly experimental stage, if I (or someone else) should ever get this to more stable and reliable state, I'll make an easy to use installer/setup tool
But I got a few other ideas on setting it up I have to try first....

http://goo.gl/2uZCh
This is the complete rom. Only 47mb. I thought you would like the whole rom

Tricky103 said:
Hi
Does this kernel include any of the Hellcat kernel tweaks or are they work in progress.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
May be someday WINDOWS Mo 7 and Android on our sweet beast

Hi
I tried again with Aosp Dev-null. I still get this error "cp: can't stat '/data/*': No such file or directory "
after running this command line " cp -Rp /data/* /cache/ "
Any Ideas ?
It still doesn't boot if I press 3 button it brings up the boot logo and then black screens until it boots to the 1st partition.

Thanks for the link, will download and try as soon as time permits.
Also, try this command sequence, I got an idea what the issue maybe might be, give it a shot:
Code:
su
rm -Rf /cache/*
busybox cp -Rp /data/* /cache/
dd if=/dev/block/mmcblk0p9 of=/dev/block/mmcblk0p12 bs=4096
(use "busybox cp" instead of plain "cp", maybe it helps)
And some update on my ongoing thoughts for those interested:
- got an idea on how to make a more easy to use App for prepping and setting up the dualboot environment
- managed to do a neat thing I didn't really think it would work: issued a "mount" command and the OS thought it was mounting a partition of the internal flash (/dev/block/mmcblk0p12 in this test, but was testing for later on actually doing it with p9 - you might see where I'm headed here ) but instead of the partition it actually mounted from an .img file! (loopback)
i.e. "mount /dev/block/mmcblk0p12 /somedir" actually mounted "/somepath/someimage.img" to "/somedir" instead of the partition from /dev/block/... (you just gotta love Linux and it's flexible way of handling things....)
NOW, imagine /dev/block/mmcblk0p9 (the partition carrying the system) and p10 (data) being (kinda) transparently mounted from an IMAGE FILE
I "only" have to find a way to sneak this in before init starts mounting stuff.
If there's a way to do THAT.... unlimited multiboot from OS images, anyone?
(so far this is kinda dreaming, but would be cool to get it working )

[RECOVERY] ClockworkMod 6.0.3.7 for Xiaomi Mi3 tegra4 (pisces)

This is a modified ClockworkMod recovery for the Xiaomi Mi3 tegra4 (pisces). It includes some changes from M1cha's CWM for Mi2 to support the dual-system design of the Mi2 (same thing on Mi3), while leaving out "true dualboot" feature for now. I think TDB is useless as long as there is only MIUI available for this device. See source for details.
Working so far:
adbd in recovery
nandroid backup/restore, including system1, boot1
running any update.zip (including AROMA)
choose system to install update to
set active system
Anything else untested.
Installing:
(1) Flash using fastboot:
adb reboot-bootloader
{wait for fastboot screen}
fastboot flash recovery cwm-*-pisces-*.img
(2) Boot new recovery:
Type fastboot reboot and press enter while holding Vol+ key should take you directly to CWM.
(3) Let CWM disable recovery flashing (offered automatically when selecting reboot)
I didn't test this method so far (feedback welcome) -- in case it doesn't work, try this instead:
Alternative installation method:
(1) Disable automatic recovery reflashing (while running MIUI, requires busybox installed and a root shell, eg "adb root; adb shell")
Code:
mount -o remount,rw /system
chmod 444 /system/etc/install-recovery.sh
mount -o remount,ro /system
(2) Flash using fastboot
Code:
adb reboot-recovery
{wait for fastboot}
fastboot flash recovery cwm-*-pisces-*.img
Use at your own risk, right now this is largely untested
Download: cwm-6.0.3.7-pisces-a20131110a.img
Older Releases: cwm-pisces
Source:
Device tree (stub)
Recovery
Note: As there's no kernel source available yet, the kernel is left out of device tree. For building yourself, extract stock kernel from your boot image and place it in the device tree (filename "kernel")
History:
a20131110a:
Integrated all fixes by M1cha that are not related to TDB -- backup/restore of boot1 now working
Set default storage to /sdcard/0, nandroid backups now accessible via MTP
a20131110:
Integrated boot-system selection and recovery-check for both systems
Used biggest font for readability on fullHD display
a20131109a: Integrated the first dualsystem support modification by M1cha
a20131109: Unmodified CyanogenMod source, no dualsystem support at all

This is my future phone.. So thanks

Thanks, but keep in mind this phone comes with 2 different SoCs, Tegra4 and Snapdragon800 -- this here is for Tegra4, which is found in TD-SCMA version... maybe I should update OP to explicitly state that.
Btw, it's not complete yet, it doesn't flash original ROM updates correctly, I think thats because named partition nodes are missing ... I'll add support for these soon
Gesendet von meinem MI 3 mit Tapatalk

No third-party ROM MI3 brothers now seems less useful but thank you
I did a card brush pack Share
Attachment Download：
recovery-clockwork-cwm-6.0.3.7-pisces-a20131110a.zip
http://115.com/lb/5lbdstd81pd#
recovery-clockwork-cwm-6....3.7-pisces-a20131110a.zip
115 network disk packs code：5lbdstd81pd

yao85930101 said:
No third-party ROM MI3 brothers now seems less useful but thank you
Click to expand...
Click to collapse
Well, I need some time to improve it, because there's two possible uses with stock ROM:
- nandroid
- re-flashing mods after upgrade
I'm especially interested in the second, because I want some apps to reside in /system/app permanently. Unfortunately, it doesn't work yet, as it doesn't flash official upgrades (right now need updater app for this) -- as I said, probably the named device nodes for partitions, need time to work on this.
For 3rd-party ROM ... There COULD be. I assume stock kernel is somehow based on this:
http://nv-tegra.nvidia.com/gitweb/?p=linux-2.6.git;a=tree;hb=refs/heads/linux-tegra-nv-3.4
(seems to contain platform drivers for tegra pluto board, has android drivers and it's even exactly the same linux version)
So, it COULD be possible to build a working kernel from these sources. Well, I didn't even get anything to boot far enough for giving useful error info to me But if you want to "waste" hours and days, please try yourself A custom kernel would be an excellent start.
yao85930101 said:
I did a card brush pack Share
Attachment Download：
recovery-clockwork-cwm-6.0.3.7-pisces-a20131110a.zip
http://pan.baidu.com/s/1Dwmj9
Click to expand...
Click to collapse
Nice! :good: Is this installable from stock recovery, too?
A little remark: I'd prefer not to modify /system automatically from the installer but better boot directly into CWM and then let the user decide. Of course thist would require rebooting to recovery from updater-script. I didn't do edify script for quite some time -- is this possible? If not, maybe we could throw together a little arm7 binary for the boot to CWM for some kind of "final" release. I'd consider thios CWM version "final" as soon as it can flash official updates (from xiaomi)

Oh look forward to updating you again Come on you are the best

However, a day to focus on the brothers really no way to track it?

Hello, I don't have time for this right now. I'll get back to the project probably after christmas.
But, as I said, it's probably the missing partition names -- so this SHOULD be fixable in the device tree, adding init scripts to the recovery (no need to modify CWM itself further). Feel free to clone the repo (AND you need an original kernel image extracted from the phone)

Any reason this wouldn't work on Tegra Note 7?

e8hffff said:
Any reason this wouldn't work on Tegra Note 7?
Click to expand...
Click to collapse
At least two.
1. The kernel. It's taken from an original Mi3 tegra phone, unfortunately, there are no sources yet from Xiaomi. Although it's the same platform, the chances this kernel would boot on any other device are low.
2. "Dual-system". I don't know much about the Tegra Note 7, but I doubt it has 2 system and boot partitions. Most android devices don't -- the Xiaomi phones are the only ones I'm aware of. CWM code in this zip is modified/extended to handle this (mostly taken from modifications done by M1cha for the Mi2). It won't work on a normal single-system device. In fact, there's no need to modify CWM source for a standard single-system device, a device-tree would be enough for building a working CWM recovery.

Zirias said:
At least two.
Click to expand...
Click to collapse
Ok thanks for the reply.

any progress on this work? is this CWM fully working now?

Don't Copy Others Work
If u Copy some ones Post Then Plzzz........... Mention
http://forum.xda-developers.com/showthread.php?t=2521125

new cwm but in chinese dor tegra 4
i have find these two but i think it is in chinese
http://4pda.ru/forum/index.php?showtopic=541742&st=5360#entry32916655
http://www.miui.com/thread-2069908-1-1.html
if any one could help and translate them to english we can have true dual boot and try the new custom roms for tegra 4 xiaomi
Android - 5.0 Lollipop for tegra 4 xiaomi but this must be in chinese too
http://www.miui.com/thread-2111749-1-1.html

[recovery][e7] TWRP 2.7.1.0 [unofficial]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its 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.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
DOWNLOAD:
Instructions to flash:
(Make sure you are rooted prior to this.)
1. Install Recovery Tools from above link.
2. You will get a prompt to backup your stock recovery. DO IT.
3. Download recovery file from here and copy it to your phone.
4.Select 'Flash Recovery' option.
5. Select 'from storage' and select it from your phone.
6. flash it.
You're done!
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 40 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!
DEVICE BUGS:
None that I know of.
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
LINK TO STOCK GiONEE RECOVERY: https://www.mediafire.com/?uwlp6ohz2hmunk1

Versions:
2.7.1.0 : http://d-h.st/APy
2.7.0.0 : http://d-h.st/U5Z

Great news. I'll check it now
Gửi từ E7 của tôi bằng cách sử dụng Tapatalk
---------- Post added 4th June 2014 at 12:42 AM ---------- Previous post was 3rd June 2014 at 11:50 PM ----------
Stuck at boot logo. How can i flash back to stock recovery?

Thanks mate.
What features does it work?
Sorry for my English
Google Translate

ibo1996 said:
Thanks mate.
What features does it work?
Sorry for my English
Google Translate
Click to expand...
Click to collapse
Pretty much everything.. As of now, the terminal emulator and SD card don't work.. That's all..
Sent from my E7

Holy crap!. You finally did it Ravi. Jus came after last exam and saw this,amazing man how did you solved display problm find 7a?
Anyways cool. This guy deserves a buttload of upvotes
Sent from my E7 using Tapatalk

Ravikirancg said:
Pretty much everything.. As of now, the terminal emulator and SD card don't work.. That's all..
Sent from my E7
Click to expand...
Click to collapse
I think SD card don't work because nexus 5 uses FUSE mount

dhirajranger said:
Holy crap!. You finally did it Ravi. Jus came after last exam and saw this,amazing man how did you solved display problm find 7a?
Anyways cool. This guy deserves a buttload of upvotes
Sent from my E7 using Tapatalk
Click to expand...
Click to collapse
Well, I didn't build it from source. Instead, I dumped the dt.img from the stock kernel. Simply put I managed to unpack a boot image and repack it without losing anything.
dhirajranger said:
I think SD card don't work because nexus 5 uses FUSE mount
Click to expand...
Click to collapse
Yup.. I will build it from sources again but that won't be the latest. 2.7.0.0 does not support devices without selinux.
Sent from my E7

Ravikirancg said:
Well, I didn't build it from source. Instead, I dumped the dt.img from the stock kernel. Simply put I managed to unpack a boot image and repack it without losing anything.
Sent from my E7
Click to expand...
Click to collapse
But you managed to repack it how?
When i tried i couldn't even repack stock boot img. For sm reason its size shrunk always
Sent from my E7 using Tapatalk

dhirajranger said:
But you managed to repack it how?
When i tried i couldn't even repack stock boot img. For sm reason its size shrunk always
Sent from my E7 using Tapatalk
Click to expand...
Click to collapse
That is because you were missing the dt.img.. Compiling one is the biggest issue without source. That is why I used a hexviewer, investigated the boot images and dumped out the dt image from there. You want the dt.img? As of now it's not very useful. It won't work with the kernel sources that burak provided. We need to start off with caf sources and incorporate what ever we can from burak's sources and either experiment to bring up backlight and touchscreen or we need to update the sources exactly to what gionee had updated to. Or we could just wait for gionee to release sources. Sources say It is likely that they are going to release the sources soon.
Sent from my E7

Ravikirancg said:
That is because you were missing the dt.img.. Compiling one is the biggest issue without source. That is why I used a hexviewer, investigated the boot images and dumped out the dt image from there. You want the dt.img? As of now it's not very useful. It won't work with the kernel sources that burak provided. We need to start off with caf sources and incorporate what ever we can from burak's sources and either experiment to bring up backlight and touchscreen or we need to update the sources exactly to what gionee had updated to. Or we could just wait for gionee to release sources. Sources say It is likely that they are going to release the sources soon.
Sent from my E7
Click to expand...
Click to collapse
I don't think they are gonna release sourcees anytime soon.
As for backlight and touch screen we can take find 7a and 1+1 for referance I was just checking there modifications and both seems same hopefully we can do same too
Sent from my E7 using Tapatalk

UPDATE: SDcard fixed.
DOWNLOAD:http://d-h.st/U5Z

Great Work!! Very, very thanks!!
Sent from my E7

Works fine, just did a Nandroid backup without problems. Although to recognize the "sdcard-ext" , you must mount it previously from the corresponding option in "mount" , if I'm not mistaken?
Sent from my E7

Thanks man
Ravi Kiran the gionee e7 hero for all the e7 lovers and customisation fans , Great job . Thanks man we owe you for the great effort and you will be remembered for your service as long as e7 will be there

sheraz1015 said:
Ravi Kiran the gionee e7 hero for all the e7 lovers and customisation fans , Great job . Thanks man we owe you for the great effort and you will be remembered for your service as long as e7 will be there
Click to expand...
Click to collapse
Ok by mistaked i deleted the OS and all files on the phone instead of doing a factory reset :|
I have the nori ROM on the comp how can i connect the phone via usb and copy that so i can flash via TWRP ??
phone i bootlooping but it still goes into recovery please help :|
the mount option isn't working .

berz said:
Ok by mistaked i deleted the OS and all files on the phone instead of doing a factory reset :|
I have the nori ROM on the comp how can i connect the phone via usb and copy that so i can flash via TWRP ??
phone i bootlooping but it still goes into recovery please help :|
the mount option isn't working .
Click to expand...
Click to collapse
use adb push. download the adb files from net, open a cmd or terminal and type in the code.
Code:
adb push filename.zip /sdcard-ext/update.zip
then using twrp, flash update.zip.
you can also use usb otg if you have one. and this kind of question goes to Q&A subforum.
And stop spamming the forum.

Ravikirancg said:
use adb push. download the adb files from net, open a cmd or terminal and type in the code.
Code:
adb push filename.zip /sdcard-ext/update.zip
then using twrp, flash update.zip.
you can also use usb otg if you have one. and this kind of question goes to Q&A subforum.
And stop spamming the forum.
Click to expand...
Click to collapse
Thanks a ton figured it out and flashed rom
I know this is off topic not sure if u can help. But is there way to enable on screen home buttons on the phone without crashing system apps like cam n stuff ?

berz said:
Thanks a ton figured it out and flashed rom
I know this is off topic not sure if u can help. But is there way to enable on screen home buttons on the phone without crashing system apps like cam n stuff ?
Click to expand...
Click to collapse
yes. pimp my rom.

Ravikirancg said:
yes. pimp my rom.
Click to expand...
Click to collapse
Tried works well but Stock camera crashed bah

[Discussion & Guide] OnePlus 5/5T now have unofficial Project Treble by MoKee

(My English isn't very practice. If you have any question reading this post, please feel free to ask. I'll try my best to express.)
## 0. Update: 2018/04/16
Some information I got today:
1. OnePlus is doing a repartition in OP5 Open Beta 8 / OP5T Open Beta 6 (or earlier, who knows). It'll split the 1.5GB "last_parti" partition into a 1.0GB "vendor" and a ~500MB "reserve3" partition while booting the system.
2. Yes, the repartition process was done in system, not during OTA in recovery.
3. The official vendor partition is still unused (not formatted). OnePlus will fill it in a future OTA, said their engineer.
4. I think it won't be conflicted with our "homemade" unofficial Treble. I just tested that the stock H2OS/OxygenOS can run on our homemade partition table.
5. It's very easy to undo the unofficial treble. I'll make an undo flashable zip later (through it's unnecessary in this time).
6. Of course, MoKee now (since 20180417) can run on the official partition table too.
==========
The MoKee ROM is now shipping unofficial Treble update for OnePlus 5/5T since 20180411. As the maintainer, I would like to share some information here.
## 1. How is this possible for OP5/5T?
Project Treble requires 2 keys: a standalone /vendor partition, and fully binderized HALs.
In fact, OnePlus have a 1.4GB unused, unformatted partition "sdf6" on OnePlus 3, 3T, 5 and 5T. This partition was possibly left by the ODM company, OPPO. OPPO R11/R11s series have a simular partition layout with OnePlus, and OPPO really did release an OTA update to enable Project Treble for their products.
The other key is binerized HALs. More specifically, the Camera HAL. The good news is, OnePlus recently released OP5 Open Beta 6 and OP5T Open Beta 4, with all fully binerized HALs, including the Camera HAL.
So as these 2 majar problems were solved. Project Treble is possible.
## 2. How did this come true?
To make Project Treble come true for OnePlus 5/5T, these should be done:
1. All vender-specific blobs should be moved to /vendor
2. Some blobs load config files from /system/etc. Just hex-edit them to load from /vendor/etc instead
3. Label and format that unused sdf6 partition as /vendor - this should be automatically done with an OTA script
4. The kernel should mount sdf6 as /vendor as well
## For users - How to enable Treble for OP5/5T?
The most easy way now is, flash the latest MoKee MK81.0 nightly build with latest TWRP (OP5: http://rom.mk/?device=cheeseburger, OP5T: http://rom.mk/?device=dumpling). The updater script will do the job automatically for you.
It's possible to make a flashable zip contains only the kernel and vendor image, without the MoKee system. But I'm busying on some other features. I'll do it later.
Tested fully works with Phh-treble system image, including:
- Audio
- Camera
- Phone & data
- Bluetooth & Wi-Fi
- Fingerprint
## For developers - How to ship Treblize update with my ROM?
(I'm organizing the patch list, I'll updte this section later)
## Can I flash non-Treble ROMs? How to "undo" this change?
You don't need to undo it, I think. For those non-Treble ROMs, including H2OS and OxygenOS, the /vendor partition is invisible. So you can flash back to any other ROMs at any time you want.

This is good news for us, thank you for your hard working!

So, once we flash the Mokee ROM, will we then be able to flash the other treble ROMs like RR and Lineage?

Skeptico said:
So, once we flash the Mokee ROM, will we then be able to flash the other treble ROMs like RR and Lineage?
Click to expand...
Click to collapse
Of course.

Great job!

Any specific instructions to install this or like a normal install ???

Amanpreetsingh said:
Any specific instructions to install this or like a normal install ???
Click to expand...
Click to collapse
Please, read OP message fully

you are awesome, big thank you from every OP5/5t owner

Damn, Oppo enabled Treble but 1+ didn't
What a shame...

Does this mean that the camera quality will be as good as stock on a custom room?

@chenxingyu If we flash Oxygen OS again on the treblized 5/5T, won't it again repartion the device again and create the sdf6 partition again? Just a doubt.

hemant_jeengar said:
@chenxingyu If we flash Oxygen OS again on the treblized 5/5T, won't it again repartion the device again and create the sdf6 partition again? Just a doubt.
Click to expand...
Click to collapse
No, as the normal update packages don't touch that partition. On the other hand, there's no repartitioning involved - the type, filesystem and mount point of /sdf6 are changed.

hemant_jeengar said:
@chenxingyu If we flash Oxygen OS again on the treblized 5/5T, won't it again repartion the device again and create the sdf6 partition again? Just a doubt.
Click to expand...
Click to collapse
No, Oxygen OS doesn't know there's a partition named sdf6.

First of all appreciate your effort for bringing treble support for op5t.. am currently running xxx ROM and decrypted..questions I have is does blu_spark or codeworkx twrp support flashing system image..also if I flash mokee latest update then will it wipe all my internal storage data..also I read no_verity zip doesn't work so when we go back to other non-treble roms then format data is mandatory..am I right..

Can someone who has already installed a treble gsi try and install oneplus camera apk and see what's happens? Or maybe even gcam? Thanks

Jamie_oppo said:
Can someone who has already installed a treble gsi try and install oneplus camera apk and see what's happens? Or maybe even gcam? Thanks
Click to expand...
Click to collapse
Gcam is crashing..tested and confirmed by a user in the group.. thanks

Can someone post a mirror link. For some reason I cant download from the main site, the countdown disappears at 56 seconds.

This is all I see

cubandanger05 said:
Can someone post a mirror link. For some reason I cant download from the main site, the countdown disappears at 56 seconds.
Click to expand...
Click to collapse
Had the same issue, downloading work on internet explorer on PC so maybe Safari on Mac? Give that a shot

BenisMusical said:
Had the same issue, downloading work on internet explorer on PC so maybe Safari on Mac? Give that a shot
Click to expand...
Click to collapse
Tried bunch of different browsers on my phone, desktop mode and all, but nothing, I'm going to have to try on my laptop tonight. Unless someone posts a mirror link.
Not working on the computer at work ?, getting frustrated ?.