Link to app. - https://dbp.noobdev.io/downloads/
https://dbp.noobdev.io/files/9.2.0....atcherAndroid-9.2.0.r25.g0638efb-snapshot.apk
Official website. dpb.noobdev.io
Offcial thread -
https://forum.xda-developers.com/showthread.php?t=2447534
All the steps on how to use are on the official thread
Please note it is not created nor tested by me
All the credits goes to official developer chenxiaolong
And @ndrancs who commited changes for Z00T
Z00L support will come i am committing changes for that
Thanks to rom developers also
Great news again for Z00T user!!
But, unfortunately i can't use it at all -_-
First, i attemp to backup the current rom, but error coz the app can't locate my boot.img (because magisk, maybe? It's patching the boot.img btw.)
Second, i attemp to flash the stock one, but still error (old marshmallow they said)
And lastly, i tried to flash the new Oct-OS N, but error bcoz the updater script contain the script to read asus trust zone, but they can't read it.
XTprion said:
Great news again for Z00T user!!
But, unfortunately i can't use it at all -_-
First, i attemp to backup the current rom, but error coz the app can't locate my boot.img (because magisk, maybe? It's patching the boot.img btw.)
Second, i attemp to flash the stock one, but still error (old marshmallow they said)
And lastly, i tried to flash the new Oct-OS N, but error bcoz the updater script contain the script to read asus trust zone, but they can't read it.
Click to expand...
Click to collapse
I cant test this coz i have Z00L
Once support for that phone comes i will test and tell how to get it work
Coz both are same Z00T and Z00L
Have same partitions
XTprion said:
Great news again for Z00T user!!
But, unfortunately i can't use it at all -_-
First, i attemp to backup the current rom, but error coz the app can't locate my boot.img (because magisk, maybe? It's patching the boot.img btw.)
Second, i attemp to flash the stock one, but still error (old marshmallow they said)
And lastly, i tried to flash the new Oct-OS N, but error bcoz the updater script contain the script to read asus trust zone, but they can't read it.
Click to expand...
Click to collapse
I suggest u to use this app for only custom roms
Coz stock roms have errors in many devices
addy692 said:
I suggest u to use this app for only custom roms
Coz stock roms have errors in many devices
Click to expand...
Click to collapse
Thanks for the suggestion, but I've already test it and error trustzone (can't read the trustzone)
New: I replace the updater script, deleting the line to bypass checking, but it's stuck in the "Patching system unconditionally" without any move -_-.
XTprion said:
Thanks for the suggestion, but I've already test it and error trustzone (can't read the trustzone)
New: I replace the updater script, deleting the line to bypass checking, but it's stuck in the "Patching system unconditionally" without any move -_-.
Click to expand...
Click to collapse
Yeah may be there's something wrong with partition details provided in tha app
Once support for Z00L comes i will solve it
Still, my problem isn't solved. I think you should to see this:
1. Asus Z00T variant, including Z00U, Z00UD, Z00UDH, Z00U_1 and Z00UD_1 is similar in every specs, so i think you should make Z00T variant is rrecognized the other codename too... (Z00U, etc)
2. When trying to install opengapps, it's aborted bcoz they detect my primary rom os (primary: stock 6.0), instead of secondary 7.1.1, but if it doesn't happend, the secondary rom can't boot bcoz the 1st problem..
XTprion said:
Still, my problem isn't solved. I think you should to see this:
1. Asus Z00T variant, including Z00U, Z00UD, Z00UDH, Z00U_1 and Z00UD_1 is similar in every specs, so i think you should make Z00T variant is rrecognized the other codename too... (Z00U, etc)
2. When trying to install opengapps, it's aborted bcoz they detect my primary rom os (primary: stock 6.0), instead of secondary 7.1.1, but if it doesn't happend, the secondary rom can't boot bcoz the 1st problem..
Click to expand...
Click to collapse
Ok i will add all these codenames in the next update
addy692 said:
Ok i will add all these codenames in the next update
Click to expand...
Click to collapse
Thaaankkss...
BTW, all codenames from Z00T family:
Z00T / Z00TD, Z00U / Z00UD / Z00UDH / Z00UDB, Z011 / Z011D / Z011DD
Source: LuK1337 LineageOS Thread...
XTprion said:
Thaaankkss...
BTW, all codenames from Z00T family:
Z00T / Z00TD, Z00U / Z00UD / Z00UDH / Z00UDB, Z011 / Z011D / Z011DD
Source: LuK1337 LineageOS Thread...
Click to expand...
Click to collapse
Added will be there in next update
XTprion said:
Thaaankkss...
BTW, all codenames from Z00T family:
Z00T / Z00TD, Z00U / Z00UD / Z00UDH / Z00UDB, Z011 / Z011D / Z011DD
Source: LuK1337 LineageOS Thread...
Click to expand...
Click to collapse
all codemanes added
Just download new update
addy692 said:
all codemanes added
Just download new update
Click to expand...
Click to collapse
Yess the update.... Thanks man...
Edit: it's still not work, unfortunately.
I think you forget to add Asus_ to device codename (my device is Asus_Z00U, and the apps can't recognize it bcoz you add Z00U device codename only -_-)
Sometimes i think vendor like asus make everything complicated with their awkward codename, even if the device can share the same software -_-.
XTprion said:
Yess the update.... Thanks man...
Edit: it's still not work, unfortunately.
I think you forget to add Asus_ to device codename (my device is Asus_Z00U, and the apps can't recognize it bcoz you add Z00U device codename only -_-)
Sometimes i think vendor like asus make everything complicated with their awkward codename, even if the device can share the same software -_-.
Click to expand...
Click to collapse
Oh .....
Yeah that asus missed
Now have to wait for another update
I will update all codenames with asus added
XTprion said:
Yess the update.... Thanks man...
Edit: it's still not work, unfortunately.
I think you forget to add Asus_ to device codename (my device is Asus_Z00U, and the apps can't recognize it bcoz you add Z00U device codename only -_-)
Sometimes i think vendor like asus make everything complicated with their awkward codename, even if the device can share the same software -_-.
Click to expand...
Click to collapse
U can change ur codename in build.prop also
addy692 said:
U can change ur codename in build.prop also
Click to expand...
Click to collapse
I do it before you say it man...
But the probem is, my build.prop list my device as Z00T
XTprion said:
I do it before you say it man...
But the probem is, my build.prop list my device as Z00T
Click to expand...
Click to collapse
can u attach a ss
addy692 said:
can u attach a ss
Click to expand...
Click to collapse
Ok...
XTprion said:
Ok...
Click to expand...
Click to collapse
try using any other rom or stock rom
Also
I will add al codenames with asus_ added
addy692 said:
try using any other rom or stock rom
Also
I will add al codenames with asus_ added
Click to expand...
Click to collapse
Its same guys, i dont know where i should change
(In my old Zenfone 5, there's a different build.prop that contain T00F model or T00J. Rename it will make my phone model changed, but in this phone (even on the stock), it's useless -_-)
Plus: i think you should use Asus_ instead of asus_ to avoid useless things again wkwk)
XTprion said:
Its same guys, i dont know where i should change
(In my old Zenfone 5, there's a different build.prop that contain T00F model or T00J. Rename it will make my phone model changed, but in this phone (even on the stock), it's useless -_-)
Plus: i think you should use Asus_ instead of asus_ to avoid useless things again wkwk)
Click to expand...
Click to collapse
yeah Asus_ i will add
And just for testing can u upload ur build.prop to gdrive and give link
Related
Stock Deodexed, Debloated, pre-rooted ROM for Zenfone Laser 2 is here.
I have removed most of the unwanted bloatware but kept few useful apps like Playstore, AsusBackup, PClink, Remotelink, Filemanager, etc.
List of removed apps (from 1.17.40.1234 ) From 1.17.40.1531
System/App:
Asus Browser
Asus DrawRes
Asus fmradio (Added back in .1531)
Asus Fmservice (added back in .1531)
Asus mirror
AWS
Bbbleractor
BRapps
CleanMaster
Data transfer
DrEye
Drive
Drive Activator
eMusic (added back)
Gameloft
Hangouts
Kindle
KKbox
Maps
MyAsus
Music2 (google)
Omlet-stub
Photos (google)
Puffin Browser
Trip advisor
Videos (Google)
What's next
Yahoo auction
YahooECShopping
YahooMall
Zenflash
ZenTalk
ZenUI help
Zenio
Zenioservice
Viso
System/priv-app:
Applocker
Asus Calculator
Asus fresh green theme
Asus lovely pink theme
Asus quick search (Google)
Asus task (do it later)
Game center
Laser Ruler
Microfilm (mini movie)
ShareRimBinary (share link)
Supernote
ZenCircle
/system/etc
Amazon.kindle.pro
Ezding
Features
➪Pre-rooted
➪Deodexed
➪Debloated
➪Both TWRP and Fastboot flashable
1.17.40.1531 is Zipaligned too.
DOWNLOADS
1.17.40.1234 1.17.40.1531
Flashable zip :
Z00L_1.17.40.1531_deodexed [Google Drive link]
1.15.40.871
Fastboot .img : [Google Drive link] | [AndroidfileHost Link]
Instructions
Method 1: Via Custom recovery- [Get TWRP]
1. Download Flashable zip
[file name: Z00L_deodexed_10may2016_fixed2.zip]
2. Put it in your External sd-card.
3. Boot you phone in recovery mode.
4. Wipe System, Data, Cache, Dalvik Cache.
5. Install/Flash the ROM zip!
6. Reboot
Method 2: via fastboot-
1. Download Fastboot .imgs
2. Install Asus drivers.
3. Download adb_fastboot.zip and extract its contents to the same folder where you have system-deodexed.img and boot.img files.
4. Reboot your phone to 'bootloader mode'. To do this turn of your phone completely. Hold volume down button and then press and hold power button. Release power button after Asus logo appears and then release volume down button. Your phone is now in bootloader mode.
5. Connect your phone to pc via a reliable usb cable. Look at your phone screen. It should display "Fastboot mode!"
6. Now go to the folder where you have extracted all the files. Holding down shift key, Right click on any point on white screen. Then click on 'open command window here' from the menu that appears. Command Prompt will open now
7. On command prompt type
Code:
fastboot devices
and check if it is detecting your device.
8. Now run the following commands in the given sequence
Code:
fastboot flash boot boot.img
fastboot.exe flash system system.img
fastboot erase userdata
fastboot erase cache
fastboot reboot
"fastboot flash system system.img" will take 10-20 mins to start flashing, so be patient.
Flashable Zip of Removed apps
Use this if you want any of the removed apps.
Download Link: [Google Drive] | [Android File Host]
All apps are deodexed
Bugs
1. Calculator FC - Fixed in 24 May update
Credits:
@xpirt - Guide for handling system.new.dat
@SuperR. - kitchen for deodexing
@Chainfire - for superSU
@luca020400 - for twrp
Go thank all these awesome developers!!!
XDA:DevDB Information
Optimized Z00L Stock ROM, ROM for the Zenfone 2 Laser
Contributors
sziraqui
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked Bootloader
Based On: Stock build-v1.17.40.1234
Version Information
Status: Beta
Current Stable Version: NA
Created 2016-05-04
Last Updated 2016-06-15
#Reserved
Future tasks: All tasks completed
-Rebuild from 1.17 WW firmware :good: Done
-Flashable zips for flashing removed apps :good: Done
-Deodex /system/vendor/app :good: Not found in 1.17.40.1234 firmware
-Remove more bloatware. :good: 437mb of bloat removed
CHANGELOG-
24 May 2016
1. Fixed Calculator FC
2. Fixed missing root
3. Added busybox
Click to expand...
Click to collapse
15 June 2016
1. Rebuilt from 1.17.40.1531
2. supersu within system.new.dat
3. Retained FMservice, FMRadio, eMusic as these were potentially causing headphone issue
Click to expand...
Click to collapse
Really loving the upsurge in development for the ZF2L. Awesome work mate!
Sent from my ASUS_Z00TD using Tapatalk
Can you do this for the WW1.16.40.763 version? I think they removed the 1.15.40.871 version for some unknown reason(security compromise may be?)
OMIT
souravipc53 said:
Can you do this for the WW1.16.40.763 version? I think they removed the 1.15.40.871 version for some unknown reason(security compromise may be?)
Click to expand...
Click to collapse
Yeah, I can, but I was thinking to rebuild from 1.17 stock version. By the way, have you tried it? I would like to have your reviews
sziraqui said:
Yeah, I can, but I was thinking to rebuild from 1.17 stock version. By the way, have you tried it? I would like to have your reviews
Click to expand...
Click to collapse
So far its smooth. I was using CM version due to the bloated Asus rom but it has returned my faith in stock ROM again. Thanks OP
souravipc53 said:
So far its smooth. I was using CM version due to the bloated Asus rom but it has returned my faith in stock ROM again. Thanks OP
Click to expand...
Click to collapse
Please don't compare ROMs. CM is built from source. I have just modified a ROM.
I am not even a nail dust of the developers of CM. They are the real developers!!!
sziraqui said:
Please don't compare ROMs. CM is built from source. I have just modified a ROM.
I am not even a nail dust of the developers of CM. They are the real developers!!!
Click to expand...
Click to collapse
Agreed, however, your work is much appreciated! My other DD is a Moto E 2015 4G LTE, and this phone seems to be taking off with mad developer love as the Moto E did at the end of last year. Much respect!
On a side note,, other than the big LITTLE issue, would this work on Z00TD?
lenigma1too said:
Agreed, however, your work is much appreciated! My other DD is a Moto E 2015 4G LTE, and this phone seems to be taking off with mad developer love as the Moto E did at the end of last year. Much respect!
On a side note,, other than the big LITTLE issue, would this work on Z00TD?
Click to expand...
Click to collapse
Nope, this won't work on Z00TD, don't even try.
Z00T runs 615 snapdragon while this rom is for Z00L running 410 Snapdragon. Many more hardware differences
sziraqui said:
Nope, this won't work on Z00TD, don't even try.
Z00T runs 615 snapdragon while this rom is for Z00L running 410 Snapdragon. Many more hardware differences
Click to expand...
Click to collapse
Fair enough! The irony here is as I mentioned before my other DD is a Moto E 2015 4G LTE, which also runs the Snapdragon 410, LOL ... same bored too I believe the msm8916
lenigma1too said:
Fair enough! The irony here is as I mentioned before my other DD is a Moto E 2015 4G LTE, which also runs the Snapdragon 410, LOL ... same bored too I believe the msm8916
Click to expand...
Click to collapse
I really doubt if it will even boot on surnia, the ROM depends on 64 bit libs which surnia doesnt support (correct me if i am wrong)
sziraqui said:
I really doubt if it will even boot on surnia, the ROM depends on 64 bit libs which surnia doesnt support (correct me if i am wrong)
Click to expand...
Click to collapse
That's one of the odd Snippets about the Moto E 2015 4G LTE. Although all of the hardware is 64-bit capable, it has been, for lack of a better word, restricted to 32bit. Squid2, a
kernel developer and ROM maintainer for several Moto devices, had a couple of solid xtheories as to why, but the fact that it only has 1 gig of RAM makes it proof positive that 64-bit would be a waste of time on that unit. And I was never even thinking about trying to flash this ROM on a Motorola! LOL
If you do decide to work your magic on the z00 TD, PM me and I will jump at the chance, first in line!
New version is out . Rebuilded from 1.17.40.1234.
457mb of bloatware removed.
Download it from my Gdrive
Error while flashing
Thank you so much for your hard work sir. I appreciate your contribution to this device. Sadly i would like to say that while i was trying to flash your May6 update i encountered an error. It was not ready to flash and got aborted. I would really be thankful if you see to the problem and solve it ASAP. thank you.
Santanuhbk30 said:
Thank you so much for your hard work sir. I appreciate your contribution to this device. Sadly i would like to say that while i was trying to flash your May6 update i encountered an error. It was not ready to flash and got aborted. I would really be thankful if you see to the problem and solve it ASAP. thank you.
Click to expand...
Click to collapse
Can you provide more info-
What error message you got?
Which phone model you were flashing?
Do you unlocked bootloader?
What is your SKU? (Found in build.prop)
IF your phone model is ZE550KL (ASUS Z00LD) download updater-script.zip attached. extract the file from it.
Replace updater-script from downloaded rom with this new updater-script.
Detailed instructions-
In your ROM zip, goto META-INF/com/google/android
You will see two files, "update.binary" and updater-script"
Rename the original updater-script to "updater-script.bak"
Now copy the EXTRACTED "updater-script" to the same folder where update-binary exists.
ZE601KL
Does this work for ZE601KL?
Alucarde said:
Does this work for ZE601KL?
Click to expand...
Click to collapse
No. But if there are enough users of of this variant, I will make a deodexed ROM for it. I will need testers. So tell me if you are in for testing. Mostly, there won't be any issues in even the first build but I need someone to confirm.
final version released (Z00L_deodexed_10may2016.zip)
Download link updated in original post
sziraqui said:
final version released (Z00L_deodexed_10may2016.zip)
Download link updated in original post
Click to expand...
Click to collapse
Hi thanks! it seems there's a new update for ze550kl
Due to several reasons I have stopped the deployment of the "monthly Update.Zip packages" !
Thanks for your understanding.
This thread will be used for the unified tegra-3.18 kernel only.
Twelve:
tegra-3.18_unified_dragon_kernel_12_v211213.zip
Eleven:
tegra-3.18_unified_dragon_kernel_11_v201218.zip
Ten:
tegra-3.18_unified_dragon_kernel_10_v201010.zip
Pie:
tegra-3.18_unified_dragon_kernel_p_v200310.zip
Oreo:
tegra-3.18_unified_dragon_kernel_o_v200310.zip
Changes/Features:
- Upstream to kernel version 3.18.140
- Various patches and security updates
- Added Wireguard support
- Added/Enabled various file systems (exFat, NTFS, Network Filesystems .. etc.)
- Changed kernel config to enable/improve support for varioius services (tethering .. etc.)
- Added "fix cpu frequency limitation"
- etc.
Installation:
1. Boot into TWRP
2. Install the Kernel Update.Zip file
3. Reboot into system .. no need for SuperSU / Magisk !
The package contains an Image.fit kernel binary only - and no ramdisk part !
This way the kernel should run on all available Android Oreo/Pie/Ten ROMs for the dragon device.
And there is no need for a new SuperSu/Magisk installation afterwards, unlike to "full boot.img" installation.
Sources:
https://github.com/followmsi/android_kernel_tegra
https://github.com/followmsi/lazyflasher/tree/followmsi-dragon
https://github.com/followmsi/AnyKernel2/tree/dragon
Download:
https://drive.google.com/drive/folders/18cqluw7lp1S720QdV0p-OtHfY9MNpSwn
Big thanks to @NYCHitman1 (Dirty Unicorn), @cheep5k8 (xceed), @Vartom and updateing from Team Mokee for the nice kernel sources !
Big thanks to @osm0sis (Anykernel2) and @jcadduono (lazyflasher) for the nice tools !
Enjoy
flashed your system image
devices does not boot
flashed back to stock
boots
edit: further details
every boot just dumps me into recovery.
dmitrygr said:
flashed your system image
devices does not boot
flashed back to stock
boots
edit: further details
every boot just dumps me into recovery.
Click to expand...
Click to collapse
Thanks for feedback .. no good news.
Sorry, I can not reproduce your problem.
Tested the system_vendor udapte.zip several times on my Pixel C.
No problem so far ...
You flashed the complete .zip via TWRP ?
What was your previous firmware level ?
Did you upgrade bootloader as well ?
What kernel do you have in use ?
EDIT:
Which Version of TWRP ?
Pls use xceed version for now.
The NYChitman1 version seems to have problems.
http://forum.xda-developers.com/pix...ock-bootloader-install-custom-t3307183/page14
followmsi said:
The NYChitman1 version seems to have problems.
http://forum.xda-developers.com/pix...ock-bootloader-install-custom-t3307183/page14
Click to expand...
Click to collapse
Only the latest one I released because I didn't put the proper flag in place -- the previous one works perfectly fine as indicated by myself and others.
Also, I find it interesting that you've created a development thread while you aren't actually developing anything.
Thanks for the update.
Still like to test your version.
Ok, the version from here is recommended .. http://forum.xda-developers.com/showpost.php?p=66557703&postcount=101
In the one from yesterday you fixed vendor image flashing via TWRP.. sounds nice.
When do you re-release this version ?
You may open a new thread for your TWRP releases ..
Thanks a lot for all your work!
New kernel released ... pls test
Update.ZIP_Nexus_Ryu_chromeos-3.18-kernel_v160519_followmsi.zip
There are lot of changes in compare to latest stock kernel .. https://chromium.googlesource.com/chromiumos/third_party/kernel/+log/chromeos-3.18/
Cheers
followmsi said:
New kernel released ... pls test
Update.ZIP_Nexus_Ryu_chromeos-3.18-kernel_v160519_followmsi.zip
There are lot of changes in compare to latest stock kernel .. https://chromium.googlesource.com/chromiumos/third_party/kernel/+log/chromeos-3.18/
Cheers
Click to expand...
Click to collapse
Many thanks for your work The kernel is for stock / AOSP roms? Running Dirty Unicorns and I think it´s not compatible :/
redukt said:
Many thanks for your work The kernel is for stock / AOSP roms? Running Dirty Unicorns and I think it´s not compatible :/
Click to expand...
Click to collapse
There are so many fixes since MXC89F kernel .. which was commited on Arpil 5th .. even it's the May release. Ok, was tagged on May, 4th.
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/MXC89F
Last changes .. 6 weeks ..
https://chromium.googlesource.com/c...+log/9c052efad6e651d33334b84c8f1feaf8945e8e7a
I am running the new kernel on latest M stock release .. MXC89F.
No problems so far .. really stable.
The kernel should run on all stock M releases for PixelC.
Used latest stock ramdisk to build the kernel .. maybe the dirty unicorn ramdisk is different.
But the actual kernel should work as well ..it's a dragon kernel.
Repack DU ramdisk with my kernel and it will most probably work as well .. maybe even with the same ramdisk, without repacking. Needs to be tested ..
Give it a try .. it will not hurt.
Cheers
Any chance of getting a port of multirom? Let me know if there's any interest, and what I can do to help.
nic. said:
Any chance of getting a port of multirom? Let me know if there's any interest, and what I can do to help.
Click to expand...
Click to collapse
Sounds good .. have it running on Nexus 7 flo .. really like it.
MultiROM for PixelC would be really nice .. the chromeos is part is maybe tricky.
But like SuperSU .. automatic chromeos image unpack and repack, if required at all.
It seems Tassadar is not around anymore .. not sure if he will come back.
Some new guys have taken over .. they just made a new update release for TWRP and MultiROM..
Works fine
Are you able to port it to Pixel C ?
Thanks
followmsi said:
Give it a try .. it will not hurt.
Cheers
Click to expand...
Click to collapse
Bootloop
Restored my Nandroid and device is up
DU is CM based and unfortunately incompatible :/
followmsi said:
Sounds good .. have it running on Nexus 7 flo .. really like it.
MultiROM for PixelC would be really nice .. the chromeos is part is maybe tricky.
But like SuperSU .. automatic chromeos image unpack and repack, if required at all.
It seems Tassadar is not around anymore .. not sure if he will come back.
Some new guys have taken over .. they just made a new update release for TWRP and MultiROM..
Works fine
Are you able to port it to Pixel C ?
Thanks
Click to expand...
Click to collapse
I am wanting to dig into the Linux4Tegra side of this, and was hoping that some of the work for multirom could or had been done. I don't know anything about the chromeos bootloader. Looking into it, Chrubuntu might be a viable path for this. I feel like this device is gimped with Android.
redukt said:
Bootloop
Restored my Nandroid and device is up
DU is CM based and unfortunately incompatible :/
Click to expand...
Click to collapse
Thanks for the test ..
Restore DU boot.img and you are back to normal ..yep
I will unpack the DU boot.img and have short look .. just to check it.
nic. said:
I am wanting to dig into the Linux4Tegra side of this, and was hoping that some of the work for multirom could or had been done. I don't know anything about the chromeos bootloader. Looking into it, Chrubuntu might be a viable path for this. I feel like this device is gimped with Android.
Click to expand...
Click to collapse
Sounds like a lot of work .. but if you have the right people involved ..
Maybe xceed or nychitman will know better how to "manage" the bootloader ..
As I know, until today, "nobody" knows how to remove the 30 second warning time beep sound ****.
Right now I am happy to "manage" the layer above .. boot.img and recovery.img
redukt said:
DU is CM based and unfortunately incompatible :/
Click to expand...
Click to collapse
What are you talking about? We're not CM based.
followmsi said:
There are so many fixes since MXC89F kernel .. which was commited on Arpil 5th .. even it's the May release. Ok, was tagged on May, 4th.
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/MXC89F
Last changes .. 6 weeks ..
https://chromium.googlesource.com/c...+log/9c052efad6e651d33334b84c8f1feaf8945e8e7a
I am running the new kernel on latest M stock release .. MXC89F.
No problems so far .. really stable.
The kernel should run on all stock M releases for PixelC.
Used latest stock ramdisk to build the kernel .. maybe the dirty unicorn ramdisk is different.
But the actual kernel should work as well ..it's a dragon kernel.
Repack DU ramdisk with my kernel and it will most probably work as well .. maybe even with the same ramdisk, without repacking. Needs to be tested ..
Give it a try .. it will not hurt.
Cheers
Click to expand...
Click to collapse
I had been keeping up with the chromeos-3.18 branch upstream, but I realized that a majority of the commits do not even apply to Dragon -- so it wasn't all that worthwhile to have in the majority of cases. With that said, I decided to go back to the MXC89F source until the next batch of source is released in June.
NYCHitman1 said:
What are you talking about? We're not CM based.
Click to expand...
Click to collapse
Well my bad...DU is AOSP based. I get mixed up with all several custom roms on my devices :silly:
NYCHitman1 said:
What are you talking about? We're not CM based.
I had been keeping up with the chromeos-3.18 branch upstream, but I realized that a majority of the commits do not even apply to Dragon -- so it wasn't all that worthwhile to have in the majority of cases. With that said, I decided to go back to the MXC89F source until the next batch of source is released in June.
Click to expand...
Click to collapse
You are right .. there also many fixed not relevant for dragon at all.
But it´s a fresh kernel .. upstream
I was so free .. and made a new DU kernel now .. used your ramdisk and my fresh chomeos-3.18 build from today.
@redukt, please test this kernel again .. on DU
Update.ZIP_PixelC_Ryu_chromeos-3.18-kernel_DU_v160519_followmsi.zip
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks .. still bootloop ?
redukt said:
Well my bad...DU is AOSP based. I get mixed up with all several custom roms on my devices :silly:
Click to expand...
Click to collapse
Please test this one ... Update.ZIP_PixelC_Ryu_chromeos-3.18-kernel_DU_v160519_followmsi.zip
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks !
followmsi said:
Please test this one ... Update.ZIP_PixelC_Ryu_chromeos-3.18-kernel_DU_v160519_followmsi.zip
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks !
Click to expand...
Click to collapse
!!! Device is booting!!!
Meh... forget to install SU lol.... Will have a look in kernel auditor
Many thanks
edit: I have to flash the latest supersu (beta v2.74-2) to get root again. Will test your kernel til the next DU weeklie as dd. I´ll have a look at the frequency overview and kept stock settings / governor. System runs fluid with no hickups or so. Great work!
Looks also very interessting ..stabilize-smaug-7897.B-chromeos-3.18
https://chromium.googlesource.com/c...kernel/+/stabilize-smaug-7897.B-chromeos-3.18
Will see .. today they released the 3rd N preview ... maybe it´s time for some N testing.
As I understand correct .. using N ramdisk and the same kernel from today should work on N as well.
We will see ...
Cheers
*Only tested on TA-1032 but it should work on other models too*
Downloads:
Build 1:
https://mega.nz/#!qIhFkKia!AkUMvQJ0PGVnSePabTvOgO-oUAMZahlCNaZfy2gE4vE
This TWRP now supports removing data encryption on Oreo.
General Changelog for TWRP version:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Changelog:
Build 1:
- Initial release
What works:
- Touch
- OTG
- Backup (system.img backup doesn't work but don't worry, you can backup System and you'll be fine)
- Restore
- Flashing IMGs and ZIPs
What doesn't work:
- Battery percentage is incorrect (it's possible to fix but need some time)
- MTP (it's possible to fix but need some time)
- you tell me
For full backup you need to remove encryption so you can backup /data too.
If you're wondering why protect_f, protect_s, para and uboot partitions have 0MB it's because these partitions have less then 1MB.
Comment if link need to be updated.
Credits:
@mohancm for Lenovo K4 Note TWRP
Screenshots:
i can't install it with sp flashtools ... now i bricked my phone and i downgrated it to 7.1
Riadh300 said:
i can't install it with sp flashtools ... now i bricked my phone and i downgrated it to 7.1
Click to expand...
Click to collapse
i installed it without problems, tell me your device model and how you installed it.
Worst thing that could happen is that recovery got bricked, to recover simply flash new recovery. it worked for me, with twrp flash img, with flashify and with SP Flash Tool. Maybe you flashed it in wrong way.
Also please can someone flash/test this twrp so i can see does it work for others.
System and Data can be backed up and restored on oreo with this twrp?
Hey! Why Ported One? I did upload the Twrp Recovery Source! https://github.com/ChalapathiRevanth/twrp_device_nokia_heart
You are Free to Compile It
ChalapathiRevanth said:
Hey! Why Ported One? I did upload the Twrp Recovery Source! https://github.com/ChalapathiRevanth/twrp_device_nokia_heart
You are Free to Compile It
Click to expand...
Click to collapse
Top.
Thank you
Reygal21 said:
System and Data can be backed up and restored on oreo with this twrp?
Click to expand...
Click to collapse
data can be backed up only after removing encryption, system can be backed up without problems.
As for restore, it works on Nougat (i restored whole rom when i tried substratum theme)
but i didn't tested for Oreo.
I think that will work on Oreo too because there is no change in partition mount points between Nougat and Oreo.
Update:
I found out that incorrect battery percentage and MTP are not kernel issue so it is possible to fix it.
Is it still ported, or you used twrp kernel source in new version ?
What is the diff between this and mediafire007 ver ? This second one can't find the thread about it.
Thank you Skabo !
Nikola Jovanovic said:
Is it still ported, or you used twrp kernel source in new version ?
What is the diff between this and mediafire007 ver ? This second one can't find the thread about it.
Thank you Skabo !
Click to expand...
Click to collapse
it's ported from Lenovo K4 Note TWRP which have MT6753 CPU
Though i noticed that medifire007 is smother, especially when changing storage. This TWRP have latest TWRP version and touch works smoothly while on mediafire007 TWRP you need to wait in beginning to work.
Can this work on Nokia 1 with Android Oreo 8.1?
abdul_manan said:
Can this work on Nokia 1 with Android Oreo 8.1?
Click to expand...
Click to collapse
no, but i can try to port it, i just need testers.
Edit: Bro you already have twrp for Nokia 1, just search xda Nokia 1 forum.
SkaboXD said:
no, but i can try to port it, i just need testers.
Edit: Bro you already have twrp for Nokia 1, just search xda Nokia 1 forum.
Click to expand...
Click to collapse
Thanks Bro! It worked! But there is a new problem Now. Here it is..
https://forum.xda-developers.com/nokia-1/help/stock-recovery-error-nokia-1-black-t3798928
Tested and working on TA-1028 variant with Android nougat. Installed SuperSU and everything seems okay. Thx dev:victory:
Is there any custom Rom and kernel for Nokia 3 .
Stock Nokia 3 Rom and kernel is really bad
Can i use for Nokia 3 locked bootloader???
How to install ?
please Post Nokia 3 TA1032 Android 8.1 Custom recovery
Umairali321 said:
please Post Nokia 3 TA1032 Android 8.1 Custom recovery
Click to expand...
Click to collapse
Doesn't work on 8.1? Did you tried it?
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
What's new in 3.2.2-0:
</> CHANGELOG : ? </>
Code:
Code:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
</> DOWNLOAD ? </>
https://twrp.me
$ TIP $
You can update it from previous TWRP recovery if you already have it installed, else install it as fresh by using adb or Official TWRP Installer app from google play store or similar
To flash with Fastboot/Adb:
Code:
Code:
make sure OEM-Unlocking is ON
$ adb reboot bootloader
$ fastboot flash recovery twrp-3.2.2-0-woods.img
To contribute:
TWRP Code Review
TeamWin
XDAevDB Information
Moto E4 ROMs, Kernels, Recoveries, & Other Development
Contributors
iykeDROID™ {dumbDevpr*}
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created: 2018-07-12
Last Updated: 2018-07-13
Great news. Now I'm waiting for stable and fully working Oreo ROM and start flashing.
ka4o_pi4a said:
Great news. Now I'm waiting for stable and fully working Oreo ROM and start flashing.
Click to expand...
Click to collapse
from the looks of things on my side, i don't think that will happen in anytime too soon.
let's just hope for a God sent dev to take over the Moto E4(woods) development .
if any bug with the TWRP, create/open an issue regarding such bug on GitHub :
https://github.com/omnirom/android_bootable_recovery
( make sure to see how other issues were created and follow such trend )
thanks
I am getting a wrong architecture error (error 64 in twrp) when trying to flash ARM gapps.
EstebanxZ said:
I am getting a wrong architecture error (error 64 in twrp) when trying to flash ARM gapps.
Click to expand...
Click to collapse
wait for next update or use this at your own risk
https://t.me/motoe4woods/12179
Same here. Wrong architecture. Even the backup was corrupted and I wasn't able to flash back my stock ROM. This is my last Motorola device.
ka4o_pi4a said:
Same here. Wrong architecture. Even the backup was corrupted and I wasn't able to flash back my stock ROM. This is my last Motorola device.
Click to expand...
Click to collapse
i used it to install Both XOSP & Gapps Pico today.
Few days ago I was spent my day on trying to flash some ROM, but didn't manage to flash any (Pico,nano, micro, etc) gapps... All finished with the same error 64. Then I install last beta of twrp and successfuly install gapps, but can't boot into system (boot into recovery every time).
ka4o_pi4a said:
Few days ago I was spent my day on trying to flash some ROM, but didn't manage to flash any (Pico,nano, micro, etc) gapps... All finished with the same error 64. Then I install last beta of twrp and successfuly install gapps, but can't boot into system (boot into recovery every time).
Click to expand...
Click to collapse
please your issues on that specific ROM's thread.
As far as i know, the TWRP recovery works fine even before the unofficial beta... woods has come to it's best so far.
thanks.
Already do that. Also try with two or three different ROMs and get the same error. Doesn't matter, I'LL wait for some more stable version of twrp and some ROM.
Tks
Thanks man!
Laruzzo said:
Hi, this TWRP version to Moto E4 woods is not good.
It does not install GAPPS, and do not install SUPER SU.
With GAPPS the error is about 64 bits version. And with supersu it says that "Bad recovery no Unzip."
I tried with a unnoficial version and worked everything.
Please update in TWRP site to a new version with bug fix.
Look a this thread with the version that worked with Moto E4 woods.
https://forum.xda-developers.com/mo...rp-3-1-1-r1-port-xt1760-t3772249/post76177524
Click to expand...
Click to collapse
Dude,
learn how to read a full post with instructions & proper way of reporting an issue anywhere you find yourself.
Know you device SoC, Architecture, etc ... don't just talk any how.
also, commits has not been merged
see on gerrit.twrp.me :=> https://gerrit.twrp.me/#/c/android_device_motorola_woods/+/63/
Finally, always check to see if no one has report similar issue and been solved before you start writing sh*t into the air
https://postimages.org/
https://forum.xda-developers.com/showpost.php?p=77250466&postcount=6
NOTE : MOTO E4 SERIES IS ARM(32bit) Architecture Device, stop trying to flash/install ARM64 Gapps as you stop being dumb.
OK
Ok, I´m sorry you are the developer and I should thanks for your great work. May you please share here the alternative file that works with gapps? Because I cannot access telegram at the momment. Thank you very much and sorry again if my words was not good. I respect and admire your work.
Laruzzo said:
Ok, I´m sorry you are the developer and I should thanks for your great work. May you please share here the alternative file that works with gapps? Because I cannot access telegram at the momment. Thank you very much and sorry again if my words was not good. I respect and admire your work.
Click to expand...
Click to collapse
Download ⍖ ?
TWRP-323.0-Unofficial-woods.img
iykeDROID™ said:
TWRP is an open source, community project.
..
..iykeDROID™[/URL] {dumbDevpr*}
Source Code: https://github.com/TeamWin
[/SIZE][...his other way cause I doubt about official ¿‽
Click to expand...
Click to collapse
Abish4 said:
Format Data Partition with F2FS format is not available which is usually available with every Moto Device Kernel
Click to expand...
Click to collapse
please deal with the kernel source here : https://github.com/MotorolaMobilityLLC/kernel-mtk/tree/nougat-7.1.1-release-woods
Abish4 said:
Can you help with this other way cause I doubt about official ¿‽
Click to expand...
Click to collapse
due to negligence, you couldn't check the source code here : https://github.com/TeamWin/android_device_motorola_woods
also check the twrp site : https://twrp.me/motorola/motorolamotoe4.html
I cannot flash gapps arm 7.1.x
Hi. I have one MotoE4 XT1763 Mediatek MT6735 with unlocked bootload.
would you recommend flashing the
twrp-3.2.3-0-woods.img 15.1M
Or the
TWRP-323.0-Unofficial-woods.img 15.5M
for the Lenovo Moto E4(XT1762)
?
Thank you peoples. TWRP unofficial working fine
Hey peoples. Accidentally i wiped my system. I have a backup in pc. I dont have sd card right now. How can i put the backup wich is in pc back to TWRP backup folder in order to restore ?
As we all know the Oreo is something that is quite distant for our device.
We need testers for Oreo Builds who can report bugs with accuracy, provide the logs required and have basic experience in software testing.
Be aware that the current & later releases are unstable & cannot be used as daily drivers.
BUG:
I don't have device test
Installation Instructions:
- Download the ROM
- Put the downloaded zip files on your SDCard
- Reboot in Recovery
- Wipe System, Cache, Dalvik Cache, Internal and Data Partition
- Flash rom
- Reboot system
Download from google drive: https://drive.google.com/drive/folders/1ktJvwxpb6aFHIr36gOZmv9I32e6gZd2M
XDAevDB Information
[WIP] Oreo Testing & Bug Fixing (T00F/T00J), ROM for the Asus ZenFone 5
Contributors
@nutcasev1.5, @tank0412, @flex1911, @nguyenhung9x
Source Code: github.com/Zentalk-VN
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: Lineage
Version Information
Status: Alpha
Current Stable Version: None
Current Beta Version: None
Created 2018-08-17
New build flash to fastboot : lineage 15.1
good work
I have updater eror 7 when flash rom
aman3378 said:
I have updater eror 7 when flash rom
Click to expand...
Click to collapse
I will update again file zip , please wait
aman3378 said:
I have updater eror 7 when flash rom
Click to expand...
Click to collapse
https://drive.google.com/file/d/1jouImtwKCEjnKdrWLQ7lig8AdRvxtOtD/view?usp=sharing
Flash again , i have try fix it
nguyenhung9x said:
Flash again , i have try fix it
Click to expand...
Click to collapse
at the end flashing updater eror 11 and bootloop with reboot
Plz fix camera
as the title says, can you please fix the camera? I had no issues with the camera when unlocking the bootloader but when i flash this rom, it says cannot connect to the camera. thx
aman3378 said:
at the end flashing updater eror 11 and bootloop with reboot
Click to expand...
Click to collapse
I have update file zip new , please downloads and flash again
nguyenhung9x said:
I have update file zip new , please downloads and flash again
Click to expand...
Click to collapse
where can i download this ZIP , the link under the post has an old version
nguyenhung9x said:
I will update again file zip , please wait
Click to expand...
Click to collapse
Hello. Seems like you are doing Z00T Z00F builds for lineage 15 using my sources.
You should atleast inform me that you were going to use my sources. Even if they were open. So that we could inform you of bugs & other things.
Also, you can not just plaigarize my original post in a thread I opened.
This feels like you want to use my work & take credit for it.
nutcasev1.5 said:
Hello. Seems like you are doing Z00T Z00F builds for lineage 15 using my sources.
You should atleast inform me that you were going to use my sources. Even if they were open. So that we could inform you of bugs & other things.
Also, you can not just plaigarize my original post in a thread I opened.
This feels like you want to use my work & take credit for it.
Click to expand...
Click to collapse
kkkk I have build lineage 15.0 and it boot last years , https://github.com/VTEK-TEAM , omg
https://forum.xda-developers.com/zenfone-5/development/rom-lineageos-15-0-nguyenhung9x-t3673940
nutcasev1.5 said:
Hello. Seems like you are doing Z00T Z00F builds for lineage 15 using my sources.
You should atleast inform me that you were going to use my sources. Even if they were open. So that we could inform you of bugs & other things.
Also, you can not just plaigarize my original post in a thread I opened.
This feels like you want to use my work & take credit for it.
Click to expand...
Click to collapse
I use device base fugu oreo and + hardware/intel branch 8.1 of you , i have thanks you in post
is there any point to test on the zenfone 6?
nguyenhung9x said:
kkkk I have build lineage 15.0 and it boot last years , https://github.com/VTEK-TEAM , omg
https://forum.xda-developers.com/zenfone-5/development/rom-lineageos-15-0-nguyenhung9x-t3673940
Click to expand...
Click to collapse
Yes. I have mostly you to thank for the ril somewhat working on Z00A/8.
Sorry.
nguyenhung9x said:
I use device base fugu oreo and + hardware/intel branch 8.1 of you , i have thanks you in post
Click to expand...
Click to collapse
Yes. I get it. I don't want a full banner in my name. But this thread is new. 2 days old. & you have mostly copied my threads original post. The opening paragraph is an exact copy. Layout is the same.
I guess it doesn't make a difference.
I apologize. I didn't know that you were actually contributing to the community & not just compiling someone's work.
nutcasev1.5 said:
Yes. I have mostly you to thank for the ril somewhat working on Z00A/8.
Sorry.
Yes. I get it. I don't want a full banner in my name. But this thread is new. 2 days old. & you have mostly copied my threads original post. The opening paragraph is an exact copy. Layout is the same.
I guess it doesn't make a difference.
I apologize. I didn't know that you were actually contributing to the community & not just compiling someone's work.
Click to expand...
Click to collapse
I'm sorry, I'm lazy so I'm copying your post, but I'll milk it in the future
nutcasev1.5 said:
Yes. I have mostly you to thank for the ril somewhat working on Z00A/8.
Sorry.
Yes. I get it. I don't want a full banner in my name. But this thread is new. 2 days old. & you have mostly copied my threads original post. The opening paragraph is an exact copy. Layout is the same.
I guess it doesn't make a difference.
I apologize. I didn't know that you were actually contributing to the community & not just compiling someone's work.
Click to expand...
Click to collapse
If you and I help each other build the android device, I think maybe Ril will work on Zenfone 2
nguyenhung9x said:
If you and I help each other build the android device, I think maybe Ril will work on Zenfone 2
Click to expand...
Click to collapse
Most of my development happens on telegram.
Let's get in touch there.
t.me/nutcasev1_5
There are 5 or 6 things to fix in the data structures & then some shimming to do.
@nguyenhung9x Based on 8.1? I'm gonna try it once I get my screen repaired.
error 11 and bootloop
just at the end in twrp it shows error 11 and when tried to reboot to system, it sends me to recovery