Hi all!
So, I don't own a tilapia, and I don't know anyone that does, but I build ROMs for fun and wanted to cover a base not already covered!
Today I have for you a pure AOSP build for Tilapia (Nexus 7 2012 3G)
Flashing instructions
Code:
1) Backup Everything [SIZE="7"] I MEAN EVERYTHING! THIS WIPES INTERNAL SD[/SIZE]
---YOUR WARANTY IS NOW VOID. THIS INCLUDED NO GUARANTEES---
2) Reboot into fastboot
3) run "fastboot -w update tilapia-lollipop.zip"
4) Boot into the ROM and run through setup
5) Download the Gapps and the fix zip from below to the device
6) Reboot into fastboot
7) run "fastboot flash recovery twrp.img" (or "fastboot boot twrp.img"
8) Flash gapps.zip and the fix zip
9) Reboot and report back
WHAT WORKS?
Code:
Confirmed:
Boots
Wifi
Data
Not complained about yet:
Sound
Bluetooth
NFC
Camera
Video Playback (Yes this could be an issue on some devices, but I doubt this one)
etc,
NOT WORKING
Code:
[STRIKE]Data[/STRIKE] Works now. Flash the fix in the next post
Downloads!
ROM:
V 1.0
Data Fix zip thanks @rjwil1086
GApps Thank @hema for these and @sykopompos for pointing me to them
Source: Google AOSP Source (android-5.0.0_r2)
Proprietary Blobs: 4.4.4 blobs with one small edit (one file changed locations back in 4.3 and the blobs were never updated...I don't recall the file or the location change, but I posted about it in the grouper 5.0 AOSP thread)
FAQ
I CANT FLASH ROOT WTF MAN?!?
It will bootloop if I'm not mistaken
Don't flash root yet
WOAH WHERE'S MY RECOVERY?!?!?
You need root to remove the script that installs the stock Nexus recovery each time you boot up the device
Get me (nonalcoholic) beer: [email protected]
I do this in my spare time around school, music production, and my social life. (I'm only 16 and try to have one of those...unsuccessfully)
ajbiz11 said:
FAQ
I CANT FLASH ROOT WTF MAN?!?
It will bootloop if I'm not mistaken
Don't flash root yet
WOAH WHERE'S MY RECOVERY?!?!?
You need root to remove the script that installs the stock Nexus recovery each time you boot up the device
Get me (nonalcoholic) beer: [email protected]
I do this in my spare time around school, music production, and my social life. (I'm only 16 and try to have one of those...unsuccessfully)
Click to expand...
Click to collapse
Root works with the modified kernel.
http://forum.xda-developers.com/showthread.php?p=56530439
I have the grouper version on my tilapia now. I'll try a dirty flash first.
I'll keep you posted on the progress.
Thanks for the built.
GOOD!
It's good!
My 3G doesn't work...
What's wrong??
But WiFi is OK
Thank for your sharing ^_^!
Baseband not found, new radio lollipop?
Performance is amazing!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG][/IMG]
doiutzu said:
Root works with the modified kernel.
http://forum.xda-developers.com/showthread.php?p=56530439
I have the grouper version on my tilapia now. I'll try a dirty flash first.
I'll keep you posted on the progress.
Thanks for the built.
Click to expand...
Click to collapse
I cant imagine that a grouper kernel would work on tilapia for data
zxc490710 said:
It's good!
My 3G doesn't work...
What's wrong??
But WiFi is OK
Thank for your sharing ^_^!
Click to expand...
Click to collapse
I kinda figured RIL would be broken
IIRC, lollipop changed a lot about how networking works for mobile data
Can someone grab me a logcat and a dmesg? (I believe dmesg might actually need root, but I ask that you get me at least a logcat on the stock kernel, dmesg if you can, and then both with a modified root kernel)
Fransis88 said:
Baseband not found, new radio lollipop?
Performance is amazing!!!
[/IMG][/IMG]
Click to expand...
Click to collapse
You can't really use benchmark apps, as they haven't been optimized for ART, especially the newest changes that have come about
That, and benchmarks are just numbers that never reflect real world performance
ajbiz11 said:
I cant imagine that a grouper kernel would work on tilapia for data
Click to expand...
Click to collapse
I don't have data now. just Wi-Fi. Lollipop is more important for me?
doiutzu said:
I don't have data now. just Wi-Fi. Lollipop is more important for me?
Click to expand...
Click to collapse
Well, if you can flash the stock kernel and get me a logcat, I could get working on getting data working again
Hey - I compiled the AOSP source from Google as well and my RIL isn't working. Here is my dmesg and logcat. The dmesg shows it isn't seeing the SIM card. I used the precompiled kernel that was with the source.
holy...what the heck
Honestly, I have to look a bit more at this, but it might actually be just the radio and firmware aren't compatable with the new RIL style
I should ask @manups4e if he sees anything. He was a bit smarter than I about RIL issues
if you can get me the logcat -b radio > radio.txt it should be better
then, ^^ can you see the baseband version? because dmesg shows that ril is working... also if i remember correctly 5.0.0_r1 is for phones and tablet, r2 is for a videogame console.. try to build the r1 and ask someone to test it
manups4e said:
if you can get me the logcat -b radio > radio.txt it should be better
then, ^^ can you see the baseband version? because dmesg shows that ril is working... also if i remember correctly 5.0.0_r1 is for phones and tablet, r2 is for a videogame console.. try to build the r1 and ask someone to test it
Click to expand...
Click to collapse
Are you sure? The way Google has usually done things like that is just the rX is a major milestone internally
People have said that r1 is branched into r2
...I can try it though...
just try i still need the radio logcat thou
Here is the radio logcat from 5.0.0_r2. I will rebase and recompile 5.0.0_r1 if you want me to. In lollipop, baseband says unknown. I can reflash KTU84P and see what the baseband is from there if that will produce the correct answer.
manups4e said:
just try i still need the radio logcat thou
Click to expand...
Click to collapse
Baseband unknown means that rild can't read radio firmware files.. Check proprietary files I think qmuxd and libril-qc-qmi-1.so
---------- Post added at 05:02 PM ---------- Previous post was at 05:00 PM ----------
From logcat I can read that radio and modem are not activating like the system hasn't radio framework or codes..
I just fixed
Code:
D/TelephonyManager( 139): No /proc/cmdline exception=java.io.FileNotFoundException: /proc/cmdline: open failed: EACCES (Permission denied)
D/TelephonyManager( 139): /proc/cmdline=
and after a restart the output has the baseband version
Code:
D/TelephonyManager( 139): /proc/cmdline=tegra_wdt.heartbeat=30 tegraid=30.1.3.0.0 m[email protected] android.commchip=0 vmalloc=512M androidboot.serialno=015d4b33bd241405 video=tegrafb no_console_suspend=1 console=none debug_uartport=hsport usbcore.old_scheme_first=1 [email protected] [email protected] core_edp_mv=0 audio_codec=rt5640 board_info=f41:a00:1:44:2 tegraboot=sdmmc gpt gpt_sector=61079551 androidboot.bootloader=4.23 androidboot.baseband=1231_0.18.0_0409
rjwil1086 said:
I just fixed
Code:
D/TelephonyManager( 139): No /proc/cmdline exception=java.io.FileNotFoundException: /proc/cmdline: open failed: EACCES (Permission denied)
D/TelephonyManager( 139): /proc/cmdline=
and after a restart the output has the baseband version
Code:
D/TelephonyManager( 139): /proc/cmdline=tegra_wdt.heartbeat=30 tegraid=30.1.3.0.0 [email protected] android.commchip=0 vmalloc=512M androidboot.serialno=015d4b33bd241405 video=tegrafb no_console_suspend=1 console=none debug_uartport=hsport usbcore.old_scheme_first=1 [email protected] [email protected] core_edp_mv=0 audio_codec=rt5640 board_info=f41:a00:1:44:2 tegraboot=sdmmc gpt gpt_sector=61079551 androidboot.bootloader=4.23 androidboot.baseband=1231_0.18.0_0409
Click to expand...
Click to collapse
What did you do?
Also, I take it that baseband is still blank in Settings?
Either that, or the SIM is still read as inactive?
I changed the permissions for /proc/cmdline using init.tilapia.rc.
I added this to the "on boot" section. Baseband it still "unknown". I think I misinterpretted the first time. In dmesg is shows sim state: 0 but if you look at the logcat it shows SIM-COUNT: 1. Attached is the logcat for anyone interested.
Code:
# RIL permissions fix
## Added by rjwil1086
chmod 0644 /proc/cmdline
ajbiz11 said:
What did you do?
Also, I take it that baseband is still blank in Settings?
Either that, or the SIM is still read as inactive?
Click to expand...
Click to collapse
Related
I built a cm-kernel from Cyanogen's git repository for you to use. For now it is just a boot.img and wlan.ko, but I am going to make an update.zip for you as soon as I have time
Thanks to: cyanogen, rikupw, bcrook and Radix
This boot.img is only tested on CyanogenMod 4.1.11.1 and might work with older versions. But not on non-CyanogenMod roms!
I've also made some instructions for you to use if you want to build your own kernel: http://ostebaronen.dk/?p=210
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Get the two files here:
BFS-300:
http://ostebaronen.dk/android/cm-kernel-2.6.29-bfs300/boot.img
http://ostebaronen.dk/android/cm-kernel-2.6.29-bfs300/wlan.ko
BFS-302:
http://ostebaronen.dk/android/cm-kernel-2.6.29-bfs302/boot.img
http://ostebaronen.dk/android/cm-kernel-2.6.29-bfs302/wlan.ko
To put it on your phone do as follows.
Code:
adb shell mount -o rw,remount /system
adb push wlan.ko /system/lib/modules
adb push boot.img /sdcard
adb shell
cat /dev/zero > /dev/mtd/mtd2
ignore no space left error.
flash_image boot /sdcard/boot.img
ignore read all-zero errors.
DISCLAIMER: I take no responsibility of bricking your phone, remember always to do nandroid backups! I will try to answer questions you ask here, off-topic questions will be ignored.
Lemme know if you need any help making a kernel update.zip. I would be happy to help out.
Oste
Thanks again! worked 100% well for me
i thing this kernel work for 32b
Very nice information. How about a guide for the pre build?
eViL D: said:
Very nice information. How about a guide for the pre build?
Click to expand...
Click to collapse
What do you mean, for making the boot.img?
I've found out compcache doesn't work, going to look at it.
Or wait, module works fine if I load it myself. So compcache can be enabled with.
Code:
modprobe ramzswap
/system/bin/rzscontrol /dev/block/ramzswap0 --init
swapon /dev/block/ramzswap0
Strange though, because the a2sd script should do this for us...
I know why compcache isn't working for you
Kernel versions and modules are intrinsicly linked by 'uname -r'
Cyanogen's kernel uses 2.6.29-cm41 and you've changed the name with yours to be different - so it's not going to load the modules automagically.
Those modules are slightly hidden from view too - they're in modules.sqf which is a squash4 volume that is mounted on boot.
Good job on documenting the git commands to track cyanogen's builds tho - this is what I need!
cat: write error: No space left on device
????
kchau said:
cat: write error: No space left on device
????
Click to expand...
Click to collapse
i get the same thing
i skipped cat zero
and it hangs at the mytouch screen:
K:\>adb logcat
I//system/bin/sh( 51): /system/bin/sh: Can't open /system/bin/a2sd
I/logwrapper( 51): /system/bin/sh terminated by exit(2)
on dwangs 1.6 rom, never had a2sd to begin with
OK, going to rebuild it for you with the correct uname. Lets see if that solves the modules problems, after that I will look at putting it inside a update.zip. bcrook gave me some guidance so it should be fairly easy
Updated kernel recompiled with the correct uname!
kchau said:
cat: write error: No space left on device
????
Click to expand...
Click to collapse
This is because cat continues filling the device with zeroes until the device is full. So you are ought to get the error No worries. Though this command is not necessary, but good to do since you are sure that nothing is left on it.
OK, for some reason no matter what I do on my phone it will not activate compcache automatically. I tried wiping and installing stock cm4.1.11.1 it didn't work there aswell. So I am sure it is not the kernels fault.
Could someone please confirm compcache is working for them?
will i still have the same a2sd hang on the mytouch screen now?
kchau said:
will i still have the same a2sd hang on the mytouch screen now?
Click to expand...
Click to collapse
What do you mean?
UPDATE:
Ok compcache is working. It seems the a2sd script does not like it when you dont have partitioned your SDcard. If you need help setting it up, ask away!
So what is the difference between the BFS in this kernel & the BFS is cm4.1.11.1? Is this one faster?
Edit: You just stated compcache is working if the sdcard is partitioned... so if we are already partitioned, we shouldn't have any problems, correct? Or do we have to reformat?
Cheesebaron said:
What do you mean?
UPDATE:
Ok compcache is working. It seems the a2sd script does not like it when you dont have partitioned your SDcard. If you need help setting it up, ask away!
Click to expand...
Click to collapse
when im on dwangs rom, it hangs at the mytouch screen, and adb logcat has this message
K:\>adb logcat
I//system/bin/sh( 51): /system/bin/sh: Can't open /system/bin/a2sd
I/logwrapper( 51): /system/bin/sh terminated by exit(2)
i dont think dwang's rom is a rom with a2sd, and i dont have it partitioned in my sd either.
however, when im on 4.0.4, and still dont have a partitioned sdcard, everything works fine
This is a CM10.1 (Jelly Bean, Android 4.2.2) firmware for Photon Q. It's not a official CyanogenMod, not supported by the CM team.
Credits: razrqcom-dev-team (epinter, Hashcode, dhacker29, nadlabak, Skrilax_CZ): Photon Q support is by nadlabak and Skrilax_CZ. And of course, CyanogenMod Team.
Disclaimer
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installation
The proprietary files come from stock JB firmware! It is necessary to flash stock JB first to flash CM10.1!!!
Unlocked bootloader required!!!
1) Download the build and gapps.
2) Boot into recovery
3) Backup your firmware + data !!!
4) Flash CM10.1 (install zip ...)
5) Flash gapps (install zip ...)
6) Wipe data / cache (factory reset)
7) Reboot & Enjoy
To update, just download newer CM10.1 zip file and install it from recovery.
Working
QWERTY keyboard (with multipress)
GSM: Call, SMS, MMS, Mobile Data
CDMA / LTE: Call, SMS, MMS, Mobile Data, 4G
Wifi (network scan may take a long time)
Wifi tethering
USB tethering
Camera (front, back)
Video Camera
HW acceleration
GPS / Glonass
Rotation / Sensors
Torch
NFC
Bluetooth
HDMI (incl. audio)
Not Working
Reading contacts from simcard
Minor Issues
Sometimes back virtual button has wrong icon as if virtual keyboard was out.
USB not working after the phone is plugged to charger (requires reboot).
Mass storage mode absent.
Changelog
See http://skrilax.droid-developers.org/cm10.1nightly/razrqcom/changelog.php.
Official builds
Note
The following features are not present in official builds:
- multipress (works only in some apps)
- cardock hack
- volume orienation awareness at lower level (for apps using NDK)
- 4 key navigation bar setup improvements (WIP, pending review)
- ability to specify SIM id and own phone number via persist.radio.iccid and persist.radio.msisdn properties
- ability to use SD Card as primary storage
Download
See http://download.cyanogenmod.org/?device=xt897 (GSM) and http://download.cyanogenmod.org/?device=xt897c (CDMA)
Source
See CyanogenMod wiki.
My builds
Download
Nightly builds: http://skrilax.droid-developers.org/cm10.1nightly/razrqcom/
Google apps: http://goo.im/gapps/gapps-jb-20130301-signed.zip
Source
Github: https://github.com/razrqcom-dev-team
Build steps:
Code:
mkdir cm
cd cm
repo init -u git://github.com/razrqcom-dev-team/android.git -b cm-10.1
repo sync
vendor/cm/get-prebuilts
For GSM:
Code:
. build/envsetup.sh && brunch xt897
For CDMA:
Code:
. build/envsetup.sh && brunch xt897c
Notes
1) Any QPST / SPC related things should be done on stock firmware.
2) If you want to ged rid of the "unlocked BL logo", download: http://skrilax.droid-developers.org/xt897/stock_logo.zip, unpack it, reboot the phone to fastboot open command line in the folder and type "moto-fastboot flash logo stocklogo_swapped.bin" to get stock boot logo.
3) If there is a filesystem check it will take a while to get past the CM bootanimation
Nice!! I like your disclaimer :good:
Skrilax_CZ said:
Sometimes back virtual button has wrong icon as if virtual keyboard was out
Click to expand...
Click to collapse
Noticed the same on CM10 2013-04-18.
This minor bug is also present in CM10 (all builds), yes.
Nice job Skrilax and nadlabak
I want to try it but I think I will wait until video recording will be OK.
I heard that new kernel is needed? Who is developing this new kernel (if someone is doing this)? Motorola or it must be some modified custom kernel?
And what is wrong with keyboard backlight? Is it non-working at all or it's just some problem with automatic turning on and off?
brunch xt897
Click to expand...
Click to collapse
Shouldn't it be "branch"?
micx_pl said:
Shouldn't it be "branch"?
Click to expand...
Click to collapse
No, brunch is breakfast + mka bacon.
Please read more here about this.
kubago said:
Nice job Skrilax and nadlabak
I want to try it but I think I will wait until video recording will be OK.
I heard that new kernel is needed? Who is developing this new kernel (if someone is doing this)? Motorola or it must be some modified custom kernel?
And what is wrong with keyboard backlight? Is it non-working at all or it's just some problem with automatic turning on and off?
Click to expand...
Click to collapse
3.4 kernel is in work by Hashcode, this uses heavily patched 3.0.y kernel (shared with all Motorola QC phones on MSM8960) and I don't expect that video camera will work until 3.4 kernel is used.
Keyboard backlight works, only automatic brightness will not work (yet).
I have an issue flashing ROM from 29/04/2013.
The are two errors (chown 0 1000 and chmod 750) to the /system/bin/iptables binary, because the file does not exist.
//Update: Attached report.log
Bad download (minzip: inflate read failed (32 vs 32768)).
CDMA nightly builds will start tonight.
Skrilax_CZ said:
CDMA nightly builds will start tonight.
Click to expand...
Click to collapse
Awesome news can't wait! This is exciting.
Sent from my XT897 using Tapatalk 2
Skrilax_CZ said:
Bad download (minzip: inflate read failed (32 vs 32768)).
Click to expand...
Click to collapse
I already thought about this. The md5sum is correct. I have the same problem with the build from today.
Maybe I'm having issues with my external sdcard, i discovered some strange files on it.
---------- Post added at 09:47 AM ---------- Previous post was at 09:00 AM ----------
Well... Seems like a sdcard issue. Flashing from internal storage worked perfectly.:good:
Please remember that in regard to CDMA, we totally rely on your feedback.
Just let us know what works and what not, thanks.
So Stock JB is needed to use this? Where could I get that, from my understanding I´d have to wait for the OTA or use the SOAK, right?
Anyway, as long as Video ain´t working, CM10 will do fine
At the moment I'm at the ROM of 30/04/2013. But I can't upgrad the the one from 01/05/2013 or 02/05/2013. Checksum is correct, ROM has been loaded from internal storage, so this can't be an issue with the external sd card. Unfortunately I can't find the recovery.log file. It is not at /sdcard/clockworkmod where it should have been copied to.
An other issue I have is with NFC. On the CM10.0 build there was a point in the settings under "wireless&networks/more" where NFC could be activated/deactivated and so on. At the CM10.1 build there is nothing. So I can't test if it works or not. Could you reactivate this please?
Also if you enable NFC it would be great to have a point for NFC in the quick settings.
Skrilax_CZ said:
The proprietary files come from stock JB firmware, I recommend you to flash it first before you put CM10.1 on.
Click to expand...
Click to collapse
Where can I get the stock JB firmware? I have CM10 flashed on my phone already.
Armadill0 said:
An other issue I have is with NFC. On the CM10.0 build there was a point in the settings under "wireless&networks/more" where NFC could be activated/deactivated and so on. At the CM10.1 build there is nothing. So I can't test if it works or not. Could you reactivate this please?
Also if you enable NFC it would be great to have a point for NFC in the quick settings.
Click to expand...
Click to collapse
Missing NFC should be fixed in the next nightly:
https://github.com/razrqcom-dev-tea...mmit/1b8358dd4e3800f489e8aa291518d398520f8d7e
https://github.com/razrqcom-dev-tea...mmit/3cfb2bf42bfc660a52abfd482402a4857a4d01cc
kabaldan said:
Missing NFC should be fixed in the next nightly:
https://github.com/razrqcom-dev-tea...mmit/1b8358dd4e3800f489e8aa291518d398520f8d7e
https://github.com/razrqcom-dev-tea...mmit/3cfb2bf42bfc660a52abfd482402a4857a4d01cc
Click to expand...
Click to collapse
Great, thank you! :good:
So I only have to understand why the flashing doesn't work for me.
Ok, I was able to flash the last two ROMs.
NFC works!
But you should add the following to the build.prop:
Code:
#NFC
debug.nfc.fw_download=true
debug.nfc.se=true
This enables nfc for the Play Store. Otherwise it is not possible to get nfc specific apps like nfc taginfo and several others!
Posting this here because it seems that @Chainfire prefers to do technical work publicly, and I think we need his help.
This is the userdebug boot image for the LG G5. I also have a flashable TOT with this in it so it it is actually usable, but I (nor anyone else that I am aware of) will provide that until we have it 100% working as we don't want any possibility or rooting someone's phone. These were both provided by tungkick, so if anyone wants to donate or give thanks they belong to her (I am just the messenger for now as her english is not very good).
The userdebug boot has root enabled by default, but the system is in read-only mode (just like how the Galaxy S7 was with its eng boot). It would be EXTREMELY helpful if someone who knows what they are talking about (i.e. Chainfire) could take a look at this and talk to tungkick through Skype or PM. We also have a Skype chat and if you would like to to contribute ways to get this to work I can add you to it
EDIT: I am adding the flashable TOT with the userdebug boot.img. If you attempt to flash this PLEASE have a backup of your data in case something goes wrong!!! I believe this should work on all variants, so please post if this works for you!
*You may brick your device, break your phone, or start a nuclear war with this. I am warning you now, please take this into consideration before you go around flashing things*
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bumping this
Although you caused us to lose the main people working towards root originally, if this works I may take back my feelings about you
Can you not run
Code:
mount -o remount,rw /system
Any news with this? I want muh roots
tabp0le said:
Can you not run
Code:
mount -o remount,rw /system
Click to expand...
Click to collapse
Doesn't work, we tried... This is why we need @Chainfire help. We think is has to do with modifying the actual SU binary
Nathamio said:
Any news with this? I want muh roots
Click to expand...
Click to collapse
Lol so do we. I promise we will keep you updated!
I just want to thank everyone who has been working on rooting our device. If I had a way to contribute I would, but sadly I do not. Keep up the good work!
I thought there was root for the G5 available already?
mkdr said:
I thought there was root for the G5 available already?
Click to expand...
Click to collapse
Only for certain models (T-Mo and H850 international in Europe). This could mean we can root all models.
I hope root will come to the H860 . C'mon @Chainfire, I'm sure you can find the key easily ^^
It's really a great phone, but I'm missing the good optimizations we can have with root...
YassGo said:
I hope root will come to the H860 . C'mon @Chainfire, I'm sure you can find the key easily ^^
It's really a great phone, but I'm missing the good optimizations we can have with root...
Click to expand...
Click to collapse
me too waiting for root. @Chainfire
please make it happen
Guys, please stop summoning him. He has been asked already.
It is actually the userdebug kernel, not eng. Fixed that.
Honestly Annoying said:
It is actually the userdebug kernel, not eng. Fixed that.
Click to expand...
Click to collapse
Ah, hmmm. Again, I might be talking out my buthole but.....
If this is a user-debug build, ADB commands that didnt work before might work now no? An enginering build would have root by default but a user debug build might have enough for you to push through & use commands that might not work on a normal build.
For example, Have you guys tried to use 'adb disable-verity' on this build? Pushing SU for root would be easy at this point no?
JF-GINO said:
Ah, hmmm. Again, I might be talking out my buthole but.....
If this is a user-debug build, ADB commands that didnt work before might work now no? An enginering build would have root by default but a user debug build might have enough for you to push through & use commands that might not work on a normal build.
For example, Have you guys tried to use 'adb disable-verity' on this build? Pushing SU for root would be easy at this point no?
Click to expand...
Click to collapse
You are 100% correct, but in order to do that we have to run the system as userdebug also.
When we put the userdebug kernel inside the userdebug TOT, it gives a bootloop. This is because on a standard user build the data is set to encrypt, while userdebug is unencrypted. Since our userdebug system is TECHNICALLY a user system (all we did is change the build.prop to userdebug), it throws a bootloop. If we can get past that then we would be good to go and everything would work, such as disabling dm-verity and then pulling that dm-verityless boot.img and pushing it regularly.
Honestly Annoying said:
You are 100% correct, but in order to do that we have to run the system as userdebug also.
When we put the userdebug kernel inside the userdebug TOT, it gives a bootloop. This is because on a standard user build the data is set to encrypt, while userdebug is unencrypted. Since our userdebug system is TECHNICALLY a user system (all we did is change the build.prop to userdebug), it throws a bootloop. If we can get past that then we would be good to go and everything would work, such as disabling dm-verity and then pulling that dm-verityless boot.img and pushing it regularly.
Click to expand...
Click to collapse
Wait,. so if the kernel already has encryption disabled,. then Im not sure where the problem is. Encription is not on the Rom level, its located in the ramdisk on of the kernel.
Maybe you should :
A) flash your TOT
b) then push your kernel
c) then 'fastboot format userdata' - wipe it,
reboot and see if it takes?
Or is there encryption or a hash check in the bootloader?
Also, what are you adding to your build.prop?
ro.secure=0
ro.debuggable=1
ro.kernel.android.checkjni=1 ??
JF-GINO said:
Wait,. so if the kernel already has encryption disabled,. then Im not sure where the problem is. Encription is not on the Rom level, its located in the ramdisk on of the kernel.
Maybe you should :
A) flash your TOT
b) then push your kernel
c) then 'fastboot format userdata' - wipe it,
reboot and see if it takes?
Or is there encryption or a hash check in the bootloader?
Also, what are you adding to your build.prop?
ro.secure=0
ro.debuggable=1
ro.kernel.android.checkjni=1 ??
Click to expand...
Click to collapse
Do you have a skype? I would like to add you to a chat we have and explain more in depth
What model are you working on? And also how did you build a TOT? I can't find it anywhere on XDA.
JF-GINO said:
Wait,. so if the kernel already has encryption disabled,. then Im not sure where the problem is. Encription is not on the Rom level, its located in the ramdisk on of the kernel.
Maybe you should :
A) flash your TOT
b) then push your kernel
c) then 'fastboot format userdata' - wipe it,
reboot and see if it takes?
Or is there encryption or a hash check in the bootloader?
Also, what are you adding to your build.prop?
ro.secure=0
ro.debuggable=1
ro.kernel.android.checkjni=1 ??
Click to expand...
Click to collapse
Bootloader checks if the further images (boot, recovery, system) are signed digitally - if not, either it won't boot, or if the BL is unlocked, it will display a quite nice warning about the system being insecure.
Encryption check is not enforced, but if encryption is disabled WHILE userdata is encrypted, it will bootloop. Your method of wiping data should work (or flashing the TOT without userdata and formatting the device).
CLOSED PER OP REQUEST
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
DOWNLOAD officail
Kernel source:
Source
Selinux Status:
Enforcing
MAJOR BUGS:
?
flash on your own risk.
FLASHING
flash open gapps nano (ONLY GAPPS NANO ARE CURRENTLY SUPPORTED
Updating: (WILL WORK ONCE OFFICIAL)
Use OTA inside rom for updates
May the force be with you
XDA:DevDB Information
OmniRom, ROM for the Xiaomi Mi Pad 4
Contributors
darkobas, darkobas
Source Code: [url]https://github.com/omnirom/android_kernel_xiaomi_clover[/URL]
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Created 2019-01-13
Last Updated 2019-01-13
WOW, did you get an Mipad?
Thanks for the rom, need to test asap
Update: installs nicely, boots into black screen. Full wipe install
Update 2: no boot,LTE Mipad
NisseGurra said:
WOW, did you get an Mipad?
Thanks for the rom, need to test asap
Update: installs nicely, boots into black screen. Full wipe install
Update 2: no boot,LTE Mipad
Click to expand...
Click to collapse
so i cant guess whats going on.
recent gapps are derped again without correct permissions. use older ones. or try first just without.
darkobas said:
so i cant guess whats going on.
recent gapps are derped again without correct permissions. use older ones. or try first just without.
Click to expand...
Click to collapse
I tried with and without gapps, no luck. I guess its the LTE version that gives some bugs
NisseGurra said:
I tried with and without gapps, no luck. I guess its the LTE version that gives some bugs
Click to expand...
Click to collapse
you can munt /system in twrp and edit /system/etc/prop default
change ro.secure and ro.adb.secure to 0 and then adb logcat should work
darkobas said:
you can munt /system in twrp and edit /system/etc/prop default
change ro.secure and ro.adb.secure to 0 and then adb logcat should work
Click to expand...
Click to collapse
Will do, have to wait until tomorrow tho. Thanks for bringing omni to mipad, VERY nice addition.
Although i don't use gapps, the firmware boots fine :goodn my base (non LTE Mi Pad 4) model.
Thanks god!
Glad to see you here!:fingers-crossed:
Alex Kane said:
Although i don't use gapps, the firmware boots fine :goodn my base (non LTE Mi Pad 4) model.
Click to expand...
Click to collapse
I have a question, how do people live without Gapps? All the best games and apps are on the Play Store.
ibooth2004 said:
I have a question, how do people live without Gapps? All the best games and apps are on the Play Store.
Click to expand...
Click to collapse
MicroG
ok so new build is up. squashed a few bugs. wifi model is now super stable and everything seems to work.. please let me know if u come accross any bugs.
sadly no ideas about lte model... hope some1 can pitch in and do some work on the lte model on my device tree.
So selinux is enforcing, safety net pass out of the box, no need for magisk for this.
device will probably go official starting on sunday. take note that u can not dirty flash official over this builds.
I have a go tonight and try to provide you some logs on the LTE boot bug
Thany you for your awesome job, @darkobas. I followed your project since Oneplus One and 5. Very awesome to have this project on Clover.
Good news .
Waiting for official
darkobas said:
you can munt /system in twrp and edit /system/etc/prop default
change ro.secure and ro.adb.secure to 0 and then adb logcat should work
Click to expand...
Click to collapse
Any hint in this logcat?
(remove zip ext)
NisseGurra said:
Any hint in this logcat?
(remove zip ext)
Click to expand...
Click to collapse
push this https://drive.google.com/open?id=1fZsbW2JXYc_xU5Nc1nfzPo-ub-SNKFiQ to /vendor/lib64/
darkobas said:
push this https://drive.google.com/open?id=1fZsbW2JXYc_xU5Nc1nfzPo-ub-SNKFiQ to /vendor/lib64/
Click to expand...
Click to collapse
Tried it, still dark boot. Adb see the device and i think its seen by windows. I tried mokee boot img, it shows the boot-animation but don't boot into omni tho
NisseGurra said:
Tried it, still dark boot. Adb see the device and i think its seen by windows. I tried mokee boot img, it shows the boot-animation but don't boot into omni tho
Click to expand...
Click to collapse
are you sure its a clean flash ? log looks 'dirty'
darkobas said:
are you sure its a clean flash ? log looks 'dirty'
Click to expand...
Click to collapse
Wiped data, system and caches. Not sure twrp does an proper wipe tho. I have a look
Update: Full wipe: data, system. vendor. Device clean.
Installed latest Omni, reboot: same black scren during boot.
Added prop adb mod, new logs (attached)
Note: Screen backlit is on
Seems boot.img related?
Logcat: "06-14 15:36:54.456 1196 1253 I DisplayManagerService: Display device changed state: "Built-in Screen", ON
06-14 15:36:54.464 1196 1196 E System : ******************************************
06-14 15:36:54.466 1196 1196 E System : ************ Failure starting system services
06-14 15:36:54.466 1196 1196 E System : java.lang.IllegalStateException: PMS compiler filter settings are bad.
06-14 15:36:54.466 1196 1196 E System : at com.android.server.pm.PackageManagerServiceCompilerMapping.checkProperties(PackageManagerServiceCompilerMapping.java:92)"
NisseGurra said:
Wiped data, system and caches. Not sure twrp does an proper wipe tho. I have a look
Update: Full wipe: data, system. vendor. Device clean.
Installed latest Omni, reboot: same black scren during boot.
Added prop adb mod, new logs (attached)
Note: Screen backlit is on
Seems boot.img related?
Logcat: "06-14 15:36:54.456 1196 1253 I DisplayManagerService: Display device changed state: "Built-in Screen", ON
06-14 15:36:54.464 1196 1196 E System : ******************************************
06-14 15:36:54.466 1196 1196 E System : ************ Failure starting system services
06-14 15:36:54.466 1196 1196 E System : java.lang.IllegalStateException: PMS compiler filter settings are bad.
06-14 15:36:54.466 1196 1196 E System : at com.android.server.pm.PackageManagerServiceCompilerMapping.checkProperties(PackageManagerServiceCompilerMapping.java:92)"
Click to expand...
Click to collapse
since u have already wiped everything can you just try to format data partition ?
fastboot format userdata
but this will completely wipe all data..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project, with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub organization. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the changelog for a full list of changes & features.
Instructions :
https://wiki.lineageos.org/devices/discovery/install
Downloads :
https://download.lineageos.org/discovery
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel, or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
I'm gonna try to flash this today,
any gapps recommendation perhaps please?
also second question, does this rom recieves OTA updates?
maxis123 said:
I'm gonna try to flash this today,
any gapps recommendation perhaps please?
Click to expand...
Click to collapse
No.
maxis123 said:
also second question, does this rom recieves OTA updates?
Click to expand...
Click to collapse
No.
installed and rom is nice everything is fine, except.. Can't get connection to Internet, tryed reseting APNs, writing them on my own, can't get connection to Internet no way...
please ignore post above, turns out it was only my sim card issue..
Ty i will test it this weekend.
Awesome ROM, flawless!
Thanks for keeping this old phone alive.
But i hate the look of Android12...
michaaa62 said:
But i hate the look of Android12...
Click to expand...
Click to collapse
Yes, same here... I am building Android 11 (last amazing version IMO) for my Xperia 5 at the moment, I dont know how to port LineageOS 18.1 but I am building a SODP AOSP ROM atm.
May I ask if the system cannot be updated, have you deleted anything to keep the data?
I am facing issue with SIM2. only one sim is detected at a time.. Any help?
drakost said:
I am facing issue with SIM2. only one sim is detected at a time.. Any help?
Click to expand...
Click to collapse
Can you try to run these commands and let me know if that fixes it? You'll need to enable "Rooted debugging" in developer options before running these commands. FYI
Code:
adb root
adb remount
adb shell "curl https://raw.githubusercontent.com/LineageOS/android_device_sony_nile-common/6aa83e6e8cc00638004bbb3eca6eb347b16e1bbb/rootdir/etc/init.qcom.rc -o /vendor/etc/init/hw/init.qcom.rc"
adb reboot
LuK1337 said:
Can you try to run these commands and let me know if that fixes it? You'll need to enable "Rooted debugging" in developer options before running these commands. FYI
Code:
adb root
adb remount
adb shell "curl https://raw.githubusercontent.com/LineageOS/android_device_sony_nile-common/6aa83e6e8cc00638004bbb3eca6eb347b16e1bbb/rootdir/etc/init.qcom.rc -o /vendor/etc/init/hw/init.qcom.rc"
adb reboot
Click to expand...
Click to collapse
It worked! You are a life saver
Is it a temporary fix or permanent?
drakost said:
It worked! You are a life saver
Is it a temporary fix or permanent?
Click to expand...
Click to collapse
Permanent, now that you confirmed that my patch works.
LuK1337 said:
Permanent, now that you confirmed that my patch works.
Click to expand...
Click to collapse
It stopped working again after the restart... The same issue persists!
drakost said:
It stopped working again after the restart... The same issue persists!
Click to expand...
Click to collapse
Ehh, restart again? idk.
LuK1337 said:
Ehh, restart again? idk.
Click to expand...
Click to collapse
SIm 2 works and Sim1 doesn't.
Might be a bit late. Everything works now.. Took a few restart to fix this. But everything is fine now.
Thank you for the ROM. Amazing work!
first of all thanks for god job
plz i want ask you about crash of dvb finder and other apps on Lineage 19.1 how to fix that plz?
I was trying to sideload days ago from 16 to 19, but first boot never came out, it was just stuck on logo no matter how long I waited.. Any fix for that please?
also second question, long ago when 19 first became available and I tryed clean flash it and it booted, I had annoyance wich wasn't possible to turn off back then, it was when unlocking device with fingerprint it was vibrating everytime, so I'm inteteresed does 19 nowdays still vibrates when doing fingerprint unock ?? if does, can it be turned off somehow?
Thanks!
<3