ok, i made this port with help of Dees_Troy from TeamWin.
its still in beta stage, but it works.
so, flash it, only if you know, what you are doing...
Changelog
Code:
beta1
------
- full screen theme is working
alpha1
------
- initial release
here is how to flash it:
0. download and extract attached file
1. reboot to bootloader (fastboot)
2. fastboot flash recovery recovery-twrp-kamma-alpha1.img
3. fastboot reboot
4. profit...
If you find this usefull, you can buy me a beer : MOD EDIT: RULES STATE ONLY ONE DONATION LINK
RESERVED
You got to be kidding me!! Already! Sucks being in the USA right now, and can't try this. Hopefully we can get some ROMs coming out
---------- Post added at 12:19 PM ---------- Previous post was at 12:13 PM ----------
Keep up the work on the Oppo Find 5 btw Much needed
i found one bug in beta1. clock is not set correctly... i will fix it soon.
anyone know if any custom rom is available yet?
gerardo66 said:
anyone know if any custom rom is available yet?
Click to expand...
Click to collapse
Yes made by kamma https://mega.co.nz/#!vVQXCK6a!Ry6SbAF9mvYpBIAoEkU1iXXLTEQxcpGZFBwje3LplQI
acer73 said:
Yes made by kamma https://mega.co.nz/#!vVQXCK6a!Ry6SbAF9mvYpBIAoEkU1iXXLTEQxcpGZFBwje3LplQI
Click to expand...
Click to collapse
Are sources out?
Edit: i follow link and i got my answer
I still hope they release source some day...
how to install this recovery i go crazy please help i looking every where
Is the Oppo Find 5 going to get its own forums? We need to request this.
drvsbsm said:
Is the Oppo Find 5 going to get its own forums? We need to request this.
Click to expand...
Click to collapse
They need to release source first afaik.
Ontopic: Thanks for this man!
Doesn't work for me.
I'm getting this:
D:\MOJE\MOTO>fastboot flash recovery recovery-twrp-kamma-beta1.img
sending 'recovery' (8938 KB)...
OKAY [ 0.672s]
writing 'recovery'...
OKAY [ 1.812s]
finished. total time: 2.484s
D:\MOJE\MOTO>fastboot reboot
rebooting...
finished. total time: 0.000s
That means it should work, but after reboot, phone is starting system without recovery window.
What am I doing wrong?
ok, so the problem is, that the original rom have standard android functionality, that on every boot reflash recovery partition with original recovery. there are 2 possible solutions.
1. flash my deodex rom, where this is disabled
2. use adb shell to disable it, but you have to be rooted. here is command flow :
Code:
adb shell
su
mount -o rw,remount /system
cd /system/etc
mv install-recovery.sh install-recovery.sh.old
exit
exit
adb reboot
It works!
kamma said:
ok, so the problem is, that the original rom have standard android functionality, that on every boot reflash recovery partition with original recovery. there are 2 possible solutions.
1. flash my deodex rom, where this is disabled
2. use adb shell to disable it, but you have to be rooted. here is command flow :
Code:
adb shell
su
mount -o rw,remount /system
cd /system/etc
mv install-recovery.sh install-recovery.sh.old
exit
exit
adb reboot
Click to expand...
Click to collapse
You are the man!
Hai friends , is it possible to rewrite and backup imei on find 5 ? thanks ..
Sources are out...prepare yourselves gentlemen,custom roms are coming.
Allanitomwesh said:
Sources are out...prepare yourselves gentlemen,custom roms are coming.
Click to expand...
Click to collapse
Great News!!! Cant wait to see what the devs have in mind and what they are able to create for this device. Full HD with the 5 inch display and capacitive buttons that don't take up any of screen real estate. I hope that a port of Paranoid Android? I think that would be so slick on the OF5, I have it on my Nexus 7 and is is super smooth. I'm pretty sure we need CM first though if I'm correct to build Paranoid Android from, correct? Also cant wait fr some custom kernels to crank this bad boy up to about 1.89GHz Quad Core and then overclock the GPU too. I think some good camera mods and tweaks will come out also, that will make this 13MP Exmor camera shine. I see a lot of modding in the future, especially after people start getting their orders from the new batch shipped, some people have said they have stared to ship the second batch already.
^^CM doesn't need to be available beforehand because Paranoid is based on AOSP, not CM.
But CM is bound to be available first because it always is
how i could restore stock rom or stock recovery?
Really nice, pls keep on.
I have TWRP Recovery ,
about 2 weeks ago and still no one single custom rom !!!!! :crying:
Related
This is a build at a really early stage so take care !
Ok, so the method I propose is absolutely non intrusive. You might want to flash the recovery you'll find here-under but I personally haven't done it so feel free to go first Flashing back the original recovery shouldn't be a big deal anyway.
Prerequisite
You should have installed:
K910 ADB Driver (available on the CD that appear when you connect the device)
ADB
Fastboot
Rooting
So the method is pretty easy:
Download the latest SuperSU update.zip and put it at the root of your Internal SD Card
(Optional) Download Google Apps for Android 4.2.2 (thanks to TeamAndroid) and put it at the root of your Internal SD Card
Download the recovery.img (build 140205)
un-7zip it
Restart your device in the bootloader:
Code:
adb reboot-bootloader
Boot your phone into the ClockworkMod recovery:
Code:
fastboot boot cwm_recovery_custom.img
Install zip, wipe partition, backup/restore, adb sideload, ...
Reboot
The phone is left untouched except for the zip you flashed.
Update on the 6th of February (Build 140205):
Bigger font
/sdcard mounted on the first user's internal storage (= symlink /sdcard /data/media/0)
Makes use of the latest kernel
The old recovery.img stays available.
For those who would be stuck on K910_SS_S_2_040_0039_131101, I posted the official update.zip here
How to build my own recovery
If you are curious about building the recovery, I'll post here a few tips.
First of all, you'll need a good tutorial like the one on XDA University. The steps are the following:
Prepare your OS to receive a cyanogenmod repository. I would advice an Ubuntu so you can following this guide. Note that this is for a plain Android so you need to stop following it when they issue the first repo command
Then you need to carefully read this guide on porting CyanogenMod ROM. You don't need to build the full system (which is a completely other story) but only the recovery. I prepared the vendor directory for you (base on LG Optimus and a lot of research).
The building happens according to this guide.
You could be done by now if it wasn't for the dtb. If you try to boot your recovery as is, fastboot will complain about it. You'll find other people having the same issue, just follow their solution.
csu333 said:
This is a build at a really early stage so take care !
Ok, so the method I propose is absolutely non intrusive. You might want to flash the recovery you'll find here-under but I personally haven't done it so feel free to go first Flashing back the original recovery shouldn't be a big deal anyway.
So the method is pretty easy:
Download the recovery.img
un-7zip it
Restart your device in the bootloader:
Code:
adb reboot-bootloader
Boot your phone into the ClockworkMod recovery:
Code:
fastboot boot recovery-clockwork-6.0.4.6-kiton.img
Install zip, wipe partition, backup/restore, adb sideload, ...
Reboot
The phone is left untouched except for the zip you flashed.
More precisions to come in a next edit.
Click to expand...
Click to collapse
Yess!!! Thanks!!!
creating boot image...
creating boot image - 4493312 bytes
downloading 'boot.img'...
OKAY [ 0.142s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.155s
What rom version did you have when boot .img?
cwm (loki) .img from lg g2 says ok afterall, but phone restarts after showing me a nice blue line .
take a look https://gitlab.com/itsmikeramsay/mkbootimg/tree/master and this http://looollll.doorblog.jp/archives/29337755.html and this http://forum.xda-developers.com/showthread.php?t=2469510
I believe this really may be helpful to you http://forum.xda-developers.com/showthread.php?t=2073775
katalinscrob said:
creating boot image...
creating boot image - 4493312 bytes
downloading 'boot.img'...
OKAY [ 0.142s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.155s
QUOTE]
Same result for me too.
Click to expand...
Click to collapse
katalinscrob said:
creating boot image...
creating boot image - 4493312 bytes
downloading 'boot.img'...
OKAY [ 0.142s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.155s
What rom version did you have when boot .img?
cwm (loki) .img from lg g2 says ok afterall, but phone restarts after showing me a nice blue line .
take a look https://gitlab.com/itsmikeramsay/mkbootimg/tree/master and this http://looollll.doorblog.jp/archives/29337755.html and this http://forum.xda-developers.com/showthread.php?t=2469510
I believe this really may be helpful to you http://forum.xda-developers.com/showthread.php?t=2073775
Click to expand...
Click to collapse
I have K910_SS_S_2_040_0109_131226 but it shouldn't be an issue anyway. This sounds like I uploaded the wrong recovery (I have so many) because "dtb not found" is the message you receive when, well, the DTB doesn't appear in the recovery. Adding the DTB is the very last step to build the recovery.
Try this one instead.
Just for your information, note that following the guide I mentioned earlier did work but I have to add a custom init.rc because there was no backlight on the screen.
csu333 said:
I have K910_SS_S_2_040_0109_131226 but it shouldn't be an issue anyway. This sounds like I uploaded the wrong recovery (I have so many) because "dtb not found" is the message you receive when, well, the DTB doesn't appear in the recovery. Adding the DTB is the very last step to build the recovery.
Try this one instead.
Just for your information, note that following the guide I mentioned earlier did work but I have to add a custom init.rc because there was no backlight on the screen.
Click to expand...
Click to collapse
Other possible root???
http://lenovobbs.cnmo.com/thread-14620407-1-1.html
sakilxda said:
Other possible root???
http://lenovobbs.cnmo.com/thread-14620407-1-1.html
Click to expand...
Click to collapse
I honestly doubt it: all the 1 click root I've seen until know are based on a bug in the backup mechanism that have been fixed for a while now. But since it seems pretty recent, anything is possible. I can't confirm since I'm rooted now
Right now with this method, and when I get my Lenovo steps that I can do?
Update first and then use this method to root?
I do not understand English, use google translate, and as I see there seems to be no problems?
Still it take at least 2 weeks to receive it and I'm sure there will be changes and improvements ...
Thanks again for sharing your experiences.
Big thanks button should be available too...
Managed to boot in cwm, root from cwm (btw very nice option ), Gapps full reinstall and finally a backup. EVRIKA! YOU DID IT ! Respect man ! permanent img flash would be next step I assume...
sakilxda said:
Right now with this method, and when I get my Lenovo steps that I can do?
Update first and then use this method to root?
I do not understand English, use google translate, and as I see there seems to be no problems?
Still it take at least 2 weeks to receive it and I'm sure there will be changes and improvements ...
Thanks again for sharing your experiences.
Click to expand...
Click to collapse
You're right: best method is to upgrade then root with this method. If it seems difficult to get the upgrades, I can post the zip files (it took me more than a week to get the first one).
katalinscrob said:
Big thanks button should be available too...
Managed to boot in cwm, root from cwm (btw very nice option ), Gapps full reinstall and finally a backup. EVRIKA! YOU DID IT ! Respect man ! permanent img flash would be next step I assume...
Click to expand...
Click to collapse
You're very welcome
Well, actually, there should be no problem flashing this recovery, it's just that it could break the OTA process (and that I haven't tested it myself yet)
So next step after testing is to find a way to make this menu readable. I mean, I almost need a magnifying glass to read it :laugh:
It isn't really an issue, maybe to correct the dafult push backup folder to internal sdcard clockworkmod instead of root folder (mnt...). I suppose that until seriously modded ROM's will appear it's best to mantain non flashed anyway for the OTA capability IMHO. Anyway, very nice job, put a paypal to receive some beers from us.
I still cannot install zips (SuperSU / gapps) from recovery, though recovery.img was flashed without any error. Am I missing anything?
Hello friends, you have seen this guide?
http://lenovo-forums.ru/topic/4131-...-lenovo-vibe-z-k910-пока-только-wcdma-версия/
sakilxda said:
Hello friends, you have seen this guide?
http://lenovo-forums.ru/topic/4131-...-lenovo-vibe-z-k910-пока-только-wcdma-версия/
Click to expand...
Click to collapse
It is based on csu333's work. I linked thid thread to russian fellows.
katalinscrob said:
It is based on csu333's work. I linked thid thread to russian fellows.
Click to expand...
Click to collapse
Ok, just thought it was a copy
nlohani said:
I still cannot install zips (SuperSU / gapps) from recovery, though recovery.img was flashed without any error. Am I missing anything?
Click to expand...
Click to collapse
Are you sure you are in the custom recovery? The Lenovo one look similar but doesn't have the clockwork mod logo in the background. It lets you install zip...as long as they are signed by Lenovo.
csu333 said:
Are you sure you are in the custom recovery? The Lenovo one look similar but doesn't have the clockwork mod logo in the background. It lets you install zip...as long as they are signed by Lenovo.
Click to expand...
Click to collapse
You are right, after re-flashing your recovery I was able to install SuperSU.zip, but still couldn't find it in the device.
Just to share further-
1. Titanium backup still fails to get root access
2. One root checker application says my device is rooted, but 'rescue root checker' says it is not
katalinscrob said:
It isn't really an issue, maybe to correct the dafult push backup folder to internal sdcard clockworkmod instead of root folder (mnt...). I suppose that until seriously modded ROM's will appear it's best to mantain non flashed anyway for the OTA capability IMHO. Anyway, very nice job, put a paypal to receive some beers from us.
Click to expand...
Click to collapse
Good suggestions. I'll take a look.
Now that I know what it takes to build a recovery, I'll think twice before starting a project of a really modded ROM
nlohani said:
You are right, after re-flashing your recovery I was able to install SuperSU.zip, but still couldn't find it in the device.
Just to share further-
1. Titanium backup still fails to get root access
2. One root checker application says my device is rooted, but 'rescue root checker' says it is not
Click to expand...
Click to collapse
I 've had the same behavior with the oldest ROM. This is why I provided a custom ROM with busybox installed even if I knew most people wouldn't need it. It was just impossible to install it afterwards. It might then be version related. Which version are you running?
Has anyone else made any serious attempts at compiling a kernel? Prompted by doctorow's thread about the wakelock issue, I got interested in compiling a kernel so it could actually be fixed. For anyone who's tried at all, there are obviously some missing files in Lenovo's release.
I tried copying over the missing files from ASUS's Zenfone kernel release (since it uses the same SoC and their kernel had all the files that make was complaining about). Between that and commenting out some references to a nonexistent tablet_config.h header, it managed to at least finish compiling. Unfortunately I don't have a bootloader-unlocked device to test on yet, so I'm not terribly confident that it actually works.
P.S.: I'm not really sure if this belongs in the dev section or not? Sorry if it's in the wrong place, but I can't start threads there anyway at my current post count.
iampanis said:
I tried copying over the missing files from ASUS's Zenfone kernel release (since it uses the same SoC and their kernel had all the files that make was complaining about). Between that and commenting out some references to a nonexistent tablet_config.h header, it managed to at least finish compiling. Unfortunately I don't have a bootloader-unlocked device to test on yet, so I'm not terribly confident that it actually works.
Click to expand...
Click to collapse
Interesting, I haven't even gotten that far when I tried to compile them. The sources are most likely not up to date or even representative of the actual firmware kernel. For example, when I looked at the battery driver, I noticed in the published sources, the polling interval was hard-coded in such a way that it would completely ignore the setting of the poll_interval kernel parameter. But we know that this is not true for the actual firmware which is in fact respecting the setting of said parameter.
@Grarak and me have managed to get the messy "source code" of Lenovo to build. I have additionally added some security patches and stripped some kernel modules. Since we don't want to violate the GPL like Lenovo, we have pushed the kernel to GitHub.
Bear in mind that there may be some issues, given the kernel is a work in progress. It boots on stock as well as on cm-12.1, though.
Olivier said:
@Grarak and me have managed to get the messy "source code" of Lenovo to build. I have additionally added some security patches and stripped some kernel modules. Since we don't want to violate the GPL like Lenovo, we have pushed the kernel to GitHub.
Bear in mind that there may be some issues, given the kernel is a work in progress. It boots on stock as well as on cm-12.1, though.
Click to expand...
Click to collapse
Same kernel works for both 830f and 1050f?
Could you please post a compiled kernel? (which I assume can be flashed simply via fastboot)
Thanks!
raenye said:
Same kernel works for both 830f and 1050f?
Could you please post a compiled kernel? (which I assume can be flashed simply via fastboot)
Thanks!
Click to expand...
Click to collapse
Sure, here you go: kernel-yt2-20160327.img. I think it will boot on 1050F.
Olivier said:
Sure, here you go: kernel-yt2-20160327.img. I think it will boot on 1050F.
Click to expand...
Click to collapse
Hello, I have a 1050F too is somebody tried this kernel on 1050F? Is it possible to support wake gesture kernel extensions with this kernel?
Olivier said:
Sure, here you go: kernel-yt2-20160327.img. I think it will boot on 1050F.
Click to expand...
Click to collapse
I was able to unlock bootloader, install TWRP and flash this kernel via fastboot on both 830F and 1050F.
It works fine (and the battery life seems better since there's no wakelock bug).
Thanks!
Looking forward to alpha-grade CM....
raenye said:
I was able to unlock bootloader, install TWRP and flash this kernel via fastboot on both 830F and 1050F.
It works fine (and the battery life seems better since there's no wakelock bug).
Thanks!
Looking forward to alpha-grade CM....
Click to expand...
Click to collapse
Did you use.
Fastboot Flash recovery recoveryname.img.
or
Fastboot flash boot bootname.img
To send it to the tablet.
corasman said:
Did you use.
Fastboot Flash recovery recoveryname.img.
or
Fastboot flash boot bootname.img
To send it to the tablet.
Click to expand...
Click to collapse
The kernel goes to the boot partition. So 2nd option.
raenye said:
The kernel goes to the boot partition. So 2nd option.
Click to expand...
Click to collapse
Thanks ,I'll give it a try.
O.K tried this
I put the file in to my ADB folder
from a command prompt I typed Fastboot flash boot c:/adb/kernel-yt2-20160327.img and it returned
FAILED (remote: unknown command) any suggestion please.
corasman said:
Thanks ,I'll give it a try.
O.K tried this
I put the file in to my ADB folder
from a command prompt I typed Fastboot flash boot c:/adb/kernel-yt2-20160327.img and it returned
FAILED (remote: unknown command) any suggestion please.
Click to expand...
Click to collapse
Using windows? paths are c:\directory\file and not c:/directory/file
I used the fastboot executable from the tethered recovery package.
Checklist:
Did you unlock bootloader? it won't boot otherwise.
Did you backup current boot partition from TWRP/CWM?
Did you boot the tablet in fastboot mode? (down+pwr)
Can fastboot detect your tablet? (fastboot devices)
raenye said:
Using windows? paths are c:\directory\file and not c:/directory/file
I used the fastboot executable from the tethered recovery package.
Checklist:
Did you unlock bootloader? it won't boot otherwise.
Did you backup current boot partition from TWRP/CWM?
Did you boot the tablet in fastboot mode? (down+pwr)
Can fastboot detect your tablet? (fastboot devices)
Click to expand...
Click to collapse
Yes to all.
I wondered if the command slashes were the right way / or \ the way I used is what I used to unlock the bootloader and install TWRP.
I have tried the slashes the other way and get the same result, as in \ .
raenye said:
I was able to unlock bootloader, install TWRP and flash this kernel via fastboot on both 830F and 1050F.
It works fine (and the battery life seems better since there's no wakelock bug).
Thanks!
Click to expand...
Click to collapse
Hmm, I'm getting a high battery_wake_lock (on the April OTA firmware) -- even when running this kernel!
Any idea how can this be?
Hi,
I was trying to play a little bit with kernel provided by @Olivier and @Grarak ...
1. Binary Image kernel-yt2-20160327.img boots up fine on 1050l, but LTE is not working. Rest seems to be fine...
2. In next steps I replaced initrd.img with a little modified stock one - and LTE started to work - I removed from initrd almost all modules leaving only bcm43241.ko.
3. Battery wakelock problem seems not be resolved - brief check at bq27x00_battery.c in repository shows that wake_lock is still set under bq27x00_battery_suspend_resume()
... so I trying to fix this battery driver but I have problem with kernel - I can compile it successfully, but it doesn't boot
@Olivier:
1. Which branch was used to build kernel-yt2-20160327.img?
2. Which config did you use ?
My procedure using android-ndk-r12b toolchain:
# git clone ...github.com/lenovo-yt2-dev/android_kernel_lenovo_baytrail
# export PATH=~/android_yoga/toolchain/bin:$PATH
# export CROSS_COMPILE=x86_64-linux-android-
# export ARCH=x86
# make cyanogenmod_YT2_10_defconfig --- if this right config?
# make -j8 ----- lot's of warninigs, but kernel is compiled sucesfully.
# abootimg --create boot_test5.img -f bootimg.cfg -k bzImage -r initrd.img ---- bzImage from arch/x86/boot
> fastboot.exe flash boot boot_test5.img
... kernel stuck somewhere, it's doesn't even come to Zygote phase (lenovo animation). Is there any way to see kernel boot messages ?
Hi
I would also like to experiment with the Kernel, but I need to unlock the bootloader. unfortunately the thread is deleted files and I can not, can anyone help me even for private?
I have a 1380F in KitKat
Kind regards
airmalaga said:
Hi
I would also like to experiment with the Kernel, but I need to unlock the bootloader. unfortunately the thread is deleted files and I can not, can anyone help me even for private?
I have a 1380F in KitKat
Kind regards
Click to expand...
Click to collapse
I used this procedure: mobility.forumsee.com/a/m/s/p12-9574-0973888--yoga-tab-unlocking-daaa-deee-daaa-dooo.html
Patched ESP file I found on another forum: forum.android.com.pl/topic/259763-odblokowanie-bootloader%C3%B3w-yoga-tab-2/#entry4598175
For me it worked on Lolipop, but I as know bootloader changed arch x32->x64 during Lolipop->KK upgrade... I don't know if this esp will work on KK (at least do backup of ESP and boot partitions before).
---------- Post added at 12:07 PM ---------- Previous post was at 11:52 AM ----------
BTW: I was able finally to compile and startup my modified kernel using CM building engine from this thread .
I removed all wakelock code from bq27x00_battery_x8.c
For 1050L I merged: kernel from @Olivier repository + my patch on bq27x00_battery_x8.c + my initrd based on stock + stock Lolipop.
First tests seems to be very promising:
- finally NO battery_wakelock in Wakelock Detector
- LTE is working
- GPS is working
- Sound system is working
- No crashed till now
If anybody is interested i can attach img file.
Thx :good:
jasfasola said:
I used this procedure: mobility.forumsee.com/a/m/s/p12-9574-0973888--yoga-tab-unlocking-daaa-deee-daaa-dooo.html
Patched ESP file I found on another forum: forum.android.com.pl/topic/259763-odblokowanie-bootloader%C3%B3w-yoga-tab-2/#entry4598175
For me it worked on Lolipop, but I as know bootloader changed arch x32->x64 during Lolipop->KK upgrade... I don't know if this esp will work on KK (at least do backup of ESP and boot partitions before).
---------- Post added at 12:07 PM ---------- Previous post was at 11:52 AM ----------
BTW: I was able finally to compile and startup my modified kernel using CM building engine from this thread .
I removed all wakelock code from bq27x00_battery_x8.c
For 1050L I merged: kernel from @Olivier repository + my patch on bq27x00_battery_x8.c + my initrd based on stock + stock Lolipop.
First tests seems to be very promising:
- finally NO battery_wakelock in Wakelock Detector
- LTE is working
- GPS is working
- Sound system is working
- No crashed till now
If anybody is interested i can attach img file.
Click to expand...
Click to collapse
jasfasola said:
I removed all wakelock code from bq27x00_battery_x8.c
For 1050L I merged: kernel from @Olivier repository + my patch on bq27x00_battery_x8.c + my initrd based on stock + stock Lolipop.
Click to expand...
Click to collapse
Cool, could you push your patch to GitHub?
jasfasola said:
First tests seems to be very promising:
- finally NO battery_wakelock in Wakelock Detector
- LTE is working
- GPS is working
- Sound system is working
- No crashed till now
Click to expand...
Click to collapse
The kernel should be working, but the ALS is broken (seems to be a sensor from Avago) - you'll notice that if you use automatic brightness.
Olivier said:
The kernel should be working, but the ALS is broken (seems to be a sensor from Avago) - you'll notice that if you use automatic brightness.
Click to expand...
Click to collapse
Fixed. That was quite easy. Driver al3320 was in place. The problem was permissions set by script init.byt_t_ffrd8.rc in initrd. By default it's root/root, but it should be system/system. I already corrected paths and checked it - it's working. If you could give me permission to repo I can push the patch.
BTW: I see lot's of things are being hard-coded into initrd scripts. Since we changed config kernel, all those scripts must be checked. I can try to do it in free time...but some things are platform depended so, another original initrd from lolopop on 830f would be nice to compare...
jasfasola said:
so, another original initrd from lolopop on 830f would be nice to compare...
Click to expand...
Click to collapse
What do you need exactly? @jasfasola
Hi. As a result of Androplus stoppage of his kernel support I decided to create this theme. I'm not a developer.
I use LineageOS more than two months, and it's stable. Originally it was built by andralex, he didn't create this threat as he was waiting the permission from other developer whose groundwork he used. But I lost contact with him. Seems he is very busy.
Now the other developer builded the rom, his nickname is kv123.
--------------
To get usb otg working use this in terminal when you inserted usb stick
Code:
su
echo 1 > /sys/module/qpnp_smbcharger_extension/parameters/start_id_polling
------------
After any lineageos update dont forget about play store to give permissions for storage. Otherwise it wont download any apps larger the 20 mb.
Lineage camera is a bit buggy, so it's better to use open camera.
---------
There are the links
[STRIKE]https://www.androidfilehost.com/?fid=745425885120730219[/STRIKE]
https://yadi.sk/d/Zfxi3agx3HkLQL
Some developer links:
https://review.lineageos.org/#/q/project:LineageOS/android_kernel_sony_msm8994
https://github.com/LineageOS/android_kernel_sony_msm8994
If you want I can ask kv123 to build the rom for sgp712 too.
------------
Some screenshots:
Oh. You need also replace wifi calibration file here: /system/etc/firmware/wlan/bcmdhd/bcmdhd.cal and reboot
It's forgotten to be added.
Updated fixed version at yandex disk.
Thanks for this. It is exactly what I am looking for and I hope my tech skills are up to the task.
BTW, this link comes up "404 not found. Can't find it!"
https://www.androidfilehost.com/?fid=745425885120730219
Would you have another we can try?
Thats because kv123 removed version with wifi buggy.
Use my mirror link or this.
https://www.androidfilehost.com/?fid=817550096634767960
alex009988 said:
Hi. As a result of Androplus stoppage of his kernel support I decided to create this theme. I'm not a developer.
I use LineageOS more than two months, and it's stable. Originally it was built by andralex, he didn't create this threat as he was waiting the permission from other developer whose groundwork he used. But I lost contact with him. Seems he is very busy.
Now the other developer builded the rom, his nickname is kv123.
--------------
To get usb otg working use this in terminal when you inserted usb stick
------------
After any lineageos update dont forget about play store to give permissions for storage. Otherwise it wont download any apps larger the 20 mb.
Lineage camera is a bit buggy, so it's better to use open camera.
---------
There are the links
https://www.androidfilehost.com/?fid=745425885120730219
https://yadi.sk/d/Zfxi3agx3HkLQL
Some developer links:
https://review.lineageos.org/#/q/project:LineageOS/android_kernel_sony_msm8994
https://github.com/LineageOS/android_kernel_sony_msm8994
If you want I can ask kv123 to build the rom for sgp712 too.
Click to expand...
Click to collapse
Hi, could you please add some screenshots?
Ok. Added to the top.
need rom for SG712 please...
Thanks for sharing. SGP712 build would be great
Charsher47 said:
Thanks for sharing. SGP712 build would be great
Click to expand...
Click to collapse
Kv123 told me that he's gonna build the rom for 712 too.
I don't have SPG712, so i cannot test it. I was lazy to download firmware for 712, so libs are from 771. Hope they are the same. Who have please leave some feedback.
SGP712_lineageos_14_1
P.S. Nfc may not work. I will need to do some tests.
kv123 said:
I don't have SPG712, so i cannot test it. I was lazy to download firmware for 712, so libs are from 771. Hope they are the same. Who have please leave some feedback.
SGP712_lineageos_14_1
P.S. Nfc may not work. I will need to do some tests.
Click to expand...
Click to collapse
I flashed the rom with Androplus' TWRP-3.0.2-0-20160604, Error 7 because target device is karin_windy but the recovery says the device is karin (actually SGP712, it's karin_windy).
So i deleted the device verification in the updater-script, and it's Error 6 now...
Phil_Libra said:
I flashed the rom with Androplus' TWRP-3.0.2-0-20160604, Error 7 because target device is karin_windy but the recovery says the device is karin (actually SGP712, it's karin_windy).
So i deleted the device verification in the updater-script, and it's Error 6 now...
Click to expand...
Click to collapse
Why do you use androplus recovery? Use normal recovery, take it from yandex disk. And boot by vol- and power till it vibrates.
alex009988 said:
Why do you use androplus recovery? Use normal recovery, take it from yandex disk. And boot by vol- and power till it vibrates.
Click to expand...
Click to collapse
Nothing happens after I flashed the recoveries from yandex disk（both 3.0.3 and 3.1), so I tried androplus recovery...
Is there a modified boot.img for those recoveries?
P.S. I flashed 32.3.A.2.33.ftf first.
---------- Post added at 10:29 AM ---------- Previous post was at 10:22 AM ----------
I flashed 32.3.A.2.33 with flashtool, then flash the recovery in fastboot mode with:
Code:
fastboot flash recovery [I]recovery name[/I]
then pressed vol- and power, nothing happens and the tablet boots to the system.
Maybe it's better: fastboot flash recovery twrp.img ?
This twrp only requires updated bootloader from 7.0 stock.
Also i need to keep these buttons pressed untill it vibrates that is 2-3 seconds.
You can find kv123 at this thread http://4pda.ru/forum/index.php?showtopic=706675
Also you can try to contact with andralex8. He has just 712 tablet. And it worked for him. But I'm not sure if he answers you quickly.
If you keep trouble with the recovery, try twrp from this https://forum.xda-developers.com/z4-tablet/general/guide-nougat-drm-fix-root-twrp-sgp771-t3555265
Phil_Libra said:
Nothing happens after I flashed the recoveries from yandex disk（both 3.0.3 and 3.1), so I tried androplus recovery...
Is there a modified boot.img for those recoveries?
P.S. I flashed 32.3.A.2.33.ftf first.
---------- Post added at 10:29 AM ---------- Previous post was at 10:22 AM ----------
I flashed 32.3.A.2.33 with flashtool, then flash the recovery in fastboot mode with:
Code:
fastboot flash recovery [I]recovery name[/I]
then pressed vol- and power, nothing happens and the tablet boots to the system.
Click to expand...
Click to collapse
Sorry if I have missed something obvious, but are you attempting to flash LineageOS? In which case I am confused as to why you are flashing the Sony Rom 32.A.2.33?
For my part I am gearing up to attempt the LineageOS install but would like to have a backup copy of the Sony firmware in case it goes wrong.
Assuming you installed an English version, which one did you select from here:-
https://xpericheck.com/device/SGP771
Indeed, if you try something especially unchecked, better to have a backup.
But you also need to have last sony rom(any of android 7.0) in order to update bootloader and have last twrp working.
alex009988 said:
Maybe it's better: fastboot flash recovery twrp.img ?
This twrp only requires updated bootloader from 7.0 stock.
Also i need to keep these buttons pressed untill it vibrates that is 2-3 seconds.
You can find kv123 at this thread http://4pda.ru/forum/index.php?showtopic=706675
Also you can try to contact with andralex8. He has just 712 tablet. And it worked for him. But I'm not sure if he answers you quickly.
If you keep trouble with the recovery, try twrp from this https://forum.xda-developers.com/z4-tablet/general/guide-nougat-drm-fix-root-twrp-sgp771-t3555265
Click to expand...
Click to collapse
Androplus‘ recovery need a modified boot.img so I wonder if the same as the recovery in yandex disk?
And recovery from https://forum.xda-developers.com/z4-tablet/general/guide-nougat-drm-fix-root-twrp-sgp771-t3555265 is the same as Androplus’ recovery.
Ok. If you've done everything right I guess 712 dosent work with 771 recovery. I'll tell about it to kv123 and you can say it on your own on 4pda.
Please anybody who has 712 model. Test 3.1 recovery from yandex disk and confirm or contradict if it dosent work for you.
Phil_Libra said:
Nothing happens after I flashed the recoveries from yandex disk（both 3.0.3 and 3.1), so I tried androplus recovery...
Is there a modified boot.img for those recoveries?
P.S. I flashed 32.3.A.2.33.ftf first.
---------- Post added at 10:29 AM ---------- Previous post was at 10:22 AM ----------
I flashed 32.3.A.2.33 with flashtool, then flash the recovery in fastboot mode with:
Code:
fastboot flash recovery [I]recovery name[/I]
then pressed vol- and power, nothing happens and the tablet boots to the system.
Click to expand...
Click to collapse
alex009988 said:
Please anybody who has 712 model. Test 3.1 recovery from yandex disk and confirm or contradict if it dosent work for you.
Click to expand...
Click to collapse
I'm seeing the same results. Tried the same recoveries to no avail.
Install Android 9.0 Pie AOSP GSI
Warning
You will loose all your data. Make sure to backup. You are doing this at your own risk. Neither me nor xda is responsible for any bricked devices.
Pre-Requisites
Please read carefully. Any questions which are already answered in OP will be ignored.
If you have a question, not answered in OP read last 2-3 pages. Any questions which are already answered in last 2-3 pages will also be ignored.
Not being rude, but people need to start reading.
Make sure you have unlocked the bootloader.
Text Guide
Install Android 9.0 Pie AOSP GSI
1. Download AB Arm64 GSI from link in downloads. Unzip it. Windows users can use Winrar. Mac users can use the Unarchiver.
2. Download and unzip adb & fastboot linked in downloads section.
3. Place the extracted system image (step 1) in platform-tools folder. Rename it to system-arm64.img.
4. Power off phone.
5. Press and hold volume down and power button at the same time. You will now boot into fastboot boot.
6. Connect phone to computer.
7. Windows users open command prompt. Mac/Linux users open Terminal. Navigate to the folder where you unzipped adb & fastboot.
Windows
Code:
fastboot devices
Mac & Linux
Code:
./fastboot devices
If your device shows up, drivers were installed correctly. If not, then drivers were not installed and you need to install them.
8. Erase System
Windows
Code:
fastboot erase system
Mac & Linux
Code:
./fastboot erase system
9. Flash Android Pie GSI
Windows
Code:
fastboot flash system system-arm64.img
Mac & Linux
Code:
./fastboot flash system system-arm64.img
10. Wipe/Factory Reset
Windows
Code:
fastboot -w
Mac & Linux
Code:
./fastboot -w
11. Reboot
Windows
Code:
fastboot reboot
Mac & Linux
Code:
./fastboot reboot
11. Profit. Android 9.0 Pie. Rooting might result in broken Wi-fi. So, flash back stock boot.img if your wifi is broken after rooting.
Video Guide
Downloads
MiUnlock Tool - http://xiaomi-miui-ota-3rdrom.ks3-c...1/3.3.525.23/miflash_unlock-en-3.3.525.23.zip
Latest ADB & Fastboot :- https://developer.android.com/studio/releases/platform-tools
Setup ADB and Fastboot (if above adb & fastboot do not work) - https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Android 9.0 Pie GSI Thread :- https://forum.xda-developers.com/pr...velopment/aosp-9-0-phh-treble-t3831915/page12
Android 9.0 Pie GSI Download Links :- https://github.com/phhusson/treble_experimentations/releases
Winrar (Windows) :- https://www.rarlab.com/
The Unarchiver (Mac):- https://theunarchiver.com/
@munchy_cool wow!!!, Thanks man. But sorry but i have to ask, did you try this on your A2 is it working fine without any issues?
crazykas said:
@munchy_cool wow!!!, Thanks man. But sorry but i have to ask, did you try this on your A2 is it working fine without any issues?
Click to expand...
Click to collapse
the A2 in the video is mine. I tried it for some time. Camera works, wifi works, sound works, charging works, couldnt check calls and lte as I am at work and cannot have my sim turned off for even a minute. But yes it works.
munchy_cool said:
the A2 in the video is mine. I tried it for some time. Camera works, wifi works, sound works, charging works, couldnt check calls and lte as I am at work and cannot have my sim turned off for even a minute. But yes it works.
Click to expand...
Click to collapse
much appreciated man!! Reason i asked this is i ****edup my phone before cause of that fastboot boot twrp > set active b slot thing. So my warranty covered me and gave a new phone. lol. BTW what do you mean by "cannot have my sim turned off for even a minute"? Finally it will be great if you can add how to flash back the stock rom as well.. Thanks mate :good:
crazykas said:
much appreciated man!! Reason i asked this is i ****edup my phone before cause of that fastboot boot twrp > set active b slot thing. So my warranty covered me and gave a new phone. lol. BTW what do you mean by "cannot have my sim turned off for even a minute"? Finally it will be great if you can add how to flash back the stock rom as well.. Thanks mate :good:
Click to expand...
Click to collapse
not sure how you bricked it but glad you got a new phone.
"cannot have my sim turned off"
So, I have only one sim which is in my work phone. to test LTE, data etc i will have to remove the sim from that phone and put it in the Mi A2. Now, I cannot do that as I cannot have my sim (phone number) turned off for even a minute due to work.
As for going back to stock. Download stock firmware, extract it and replace pie gsi img with system.img from factory firmware zip and you will be back to stock.
munchy_cool said:
not sure how you bricked it but glad you got a new phone.
"cannot have my sim turned off"
So, I have only one sim which is in my work phone. to test LTE, data etc i will have to remove the sim from that phone and put it in the Mi A2. Now, I cannot do that as I cannot have my sim (phone number) turned off for even a minute due to work.
As for going back to stock. Download stock firmware, extract it and replace pie gsi img with system.img from factory firmware zip and you will be back to stock.
Click to expand...
Click to collapse
How did i bricked my phone. Simple. First of all no desrepect for any dev, since i did this by my one. What i did was tried to flash unofficial twrp and fastboot set slot b did not worked. Once i reboot it got stuck on a bootloop. i couldn't flash xiaomi stock fastboot zip due to "critical partition flashing is not allowed" and before you asked yes my A2 was bootloader unlocked one. Unlock critical partition thing is not for our devices like for pixel series as far as i know. So simply i couldn't fix it, neither the software guy from my purchased center. That's why im afraid. I know you are besy, but highly appreciate if you can write down how to go back to stock guideline as well. Thanks again :good:
crazykas said:
How did i bricked my phone. Simple. First of all no desrepect for any dev, since i did this by my one. What i did was tried to flash unofficial twrp and fastboot set slot b did not worked. Once i reboot it got stuck on a bootloop. i couldn't flash xiaomi stock fastboot zip due to "critical partition flashing is not allowed" and before you asked yes my A2 was bootloader unlocked one. Unlock critical partition thing is not for our devices like for pixel series as far as i know. So simply i couldn't fix it, neither the software guy from my purchased center. That's why im afraid. I know you are besy, but highly appreciate if you can write down how to go back to stock guideline as well. Thanks again :good:
Click to expand...
Click to collapse
did you try fastboot set slot a, and then reboot? that should have fixed it.
As for a guide for going back to stock from Pie.
LIke i said.
dowload fastboot firmware from here.
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
extract the zip file. open images folder. grab system.img. put it in fasboot folder. and in step where we flash pie gsi image, flash the system.img you just pasted in fastboot folder.
munchy_cool said:
did you try fastboot set slot a, and then reboot? that should have fixed it.
As for a guide for going back to stock from Pie.
LIke i said.
dowload fastboot firmware from here.
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
extract the zip file. open images folder. grab system.img. put it in fasboot folder. and in step where we flash pie gsi image, flash the system.img you just pasted in fastboot folder.
Click to expand...
Click to collapse
Thanks man. Will try at night. Can't wait ????
MTP doesn't work.
Streect said:
MTP doesn't work.
Click to expand...
Click to collapse
It works. Enable it in Developer Tools.
Thank you very much for sharing, i will try it soon
---------- Post added at 10:02 AM ---------- Previous post was at 09:39 AM ----------
No problem on Linux? Simple adb /fastboot installed on Ubuntu
---------- Post added at 10:09 AM ---------- Previous post was at 10:02 AM ----------
Again: which one img do you choose, aonly or ab?
HTCDevil said:
Thank you very much for sharing, i will try it soon
---------- Post added at 10:02 AM ---------- Previous post was at 09:39 AM ----------
No problem on Linux? Simple adb /fastboot installed on Ubuntu
---------- Post added at 10:09 AM ---------- Previous post was at 10:02 AM ----------
Again: which one img do you choose, aonly or ab?
Click to expand...
Click to collapse
did you read the OP at all? it's mentioned step 1 which file you need.
How to install Gapps?
munchy_cool said:
[...]
Click to expand...
Click to collapse
Two things:
1) Thank you for the guide! You got yourself another subscriber on YouTube This is my first device that supports Treble. From your experience, how stable are GSI ROMs?
2) Update your signature
speedunderx said:
How to install Gapps?
Click to expand...
Click to collapse
i didnt get time to check that. may have to install some apks. maybe the same apks which are needed for amazon fire tablets to get play store working.
soulicro said:
Two things:
1) Thank you for the guide! You got yourself another subscriber on YouTube This is my first device that supports Treble. From your experience, how stable are GSI ROMs?
2) Update your signature
Click to expand...
Click to collapse
gsi's are pretty stable, check xda thread for bugs. will update signature soon
munchy_cool said:
did you read the OP at all? it's mentioned step 1 which file you need.
Click to expand...
Click to collapse
About my last question ok, i see on YouTube it is ab. Other question not answered yet. Thanks.
HTCDevil said:
About my last question ok, i see on YouTube it is ab. Other question not answered yet. Let him answer by itself. Thanks.
Click to expand...
Click to collapse
no problem on Linux.
munchy_cool said:
no problem on Linux.
Click to expand...
Click to collapse
Great, hope gapps work and camera is mostly Stable. Thank you
HTCDevil said:
Great, hope gapps work and camera is mostly Stable. Thank you
Click to expand...
Click to collapse
it does not have gapps. you may have to manually install some apks. try with apks needed for Play Store on amazon fire tablets.
if you figure those out, please let us know.
So currently I'm running AOSP Extended V6 on my 002. The rom itself runs great BUT I can't get Gapps to stick. Unlocked bootloader with TWRP 3.1.0. After I resize system Gapps will install and say Successful but when I clear cache and reboot I have no nothing installed. I'm new to this device so be easy if i'm missing something obvious.
EDIT: I've tried multiple version of Gapps from a few different places.
I have yet to have any GSI rom work, so I stopped trying and just ran a debloat script I wrote
It's weird how hit and miss GSI is on the exact same model. I may end up reverting back to stock and unlock/root and use your script and then just call it a day if I can't figure this out. I SO wanted AOSP Ext to work but kinda useless to me without Gapps.
razredge said:
It's weird how hit and miss GSI is on the exact same model. I may end up reverting back to stock and unlock/root and use your script and then just call it a day if I can't figure this out. I SO wanted AOSP Ext to work but kinda useless to me without Gapps.
Click to expand...
Click to collapse
I honestly even uninstalled gapps on my 10 inch because its one purpose is gonna be an in-car OBD II monitoring tablet with Torque Pro for my car.
GSI roms are so strange. I have 3 G7 Play's. 2 of them took the same GSI just fine, then the third just bricked and boot looped. I had to change the boot animation in TWRP to get it to boot. Even then, camera and bluetooth didn't work, but the other 2 were 100% functional. Reflashed quite a few times
razredge said:
It's weird how hit and miss GSI is on the exact same model. I may end up reverting back to stock and unlock/root and use your script and then just call it a day if I can't figure this out. I SO wanted AOSP Ext to work but kinda useless to me without Gapps.
Click to expand...
Click to collapse
I believe the hit and miss comes from the gsi's being developed on specific devices by different developers. They are supposed to work on any project treble enabled devices but it's just not so. This is just my thought from trying almost all available and a lot of time reading. The whole idea has slowly began a full circle movement to custom gsi's. The oxymoron of that last sentence kind of sums it up from my experience. Custom generics are what are being produced for the most part. If one looks at the different maintainers threads they will see what device it is supposed to work on. A.O.S.P should work a little better than most and the builds I have tried from ci.android.com have worked really well. Personally didn't see much point in the stock android gsi over debloated stock in this case. Much simpler to maintain device integrity by debloating the very few unwanted apps. All that said I am still running Beast ROM as I actually like it, the only issue I know of is device theme(takes forever+know-how) and I don't use gapps. So it works great on my tablet and I am not sure what options I will have in the future. All the changes have me sitting with a tablet that if flashed back to stock will not take ota's and a serial# of 0123456789ABCDEF. Happy Modding.
Don't know if you've seen them but there are a couple gsi's that have gapps installed with no other options, can't remember which they were, but may work better.
I appreciate the info and insight you always give. My 002 I actually went back to stock and just rooted and debloated it. I wanted it to be stable since it's my couch tablet lol. I picked up a 007 on Black Friday just for the hell of it. I'm gonna play with it and experience some different roms. BTW, they changed the model numbers on them. It's not with me right now but the model number is all numbers now. Looks more like the serial number.
Sent from my Pixel 2 using Tapatalk
razredge said:
I appreciate the info and insight you always give. My 002 I actually went back to stock and just rooted and debloated it. I wanted it to be stable since it's my couch tablet lol. I picked up a 007 on Black Friday just for the hell of it. I'm gonna play with it and experience some different roms. BTW, they changed the model numbers on them. It's not with me right now but the model number is all numbers now. Looks more like the serial number.
Click to expand...
Click to collapse
The model number I remember for the 8" was ONA19TB002 and 10" was ONA19TB003 and 007 was kboard model. Did they change to something other than that ? I remember a different number when looking at fccid page but it seemed shorter. When it's nearby give update if you don't mind, I'm curious it may help in search for firmware.
The new model number is 100005209. I took the back off of the new one and my old one and they are identical with the same part numbers. They're also all branded Surf now.
Sent from my Pixel 2 using Tapatalk
I am venturing to flash ohh aosp -10 v107.
Needed to flash the vanilla version, because the gapps version was too big.
All I get is stuck at the onn splash screen.
Do I need to flash anything to vbmeta to get this to boot a gsi?
Update:
Self test result
Yes. Even after unlocking bootloader, still need to flash vbmeta with --disable-verification before you can boot gsi.
Then there is a setprop that is needed to get the gsi to boot
While device is stuck on the"Android" logo bootanimation from aosp. Enter commands into ad shell.
Code:
adb shell setprop debug.stagefright.ccodec 0
This will get tablet to boot. But the setprop (which should become persistent) does not remain after a reboot. So the line needs to be added to the boot script built into phh gsi. "rw-sysyem.sh"
Code:
adb shell
su
mount -o rw,remount /
echo "setprop debug.stagefright.ccodec 0" >> /system/bin/rw-system.sh
These steps worked for me. And should work for you. But as with any modifications to your device , by you , are your responsibility to confirm are done correctly.
The main problem I've been having has not been with the ROM itself. I had a few vanillas that after resizing and installing GAPPS the actual apps don't show up. I'd go back into TWRP and reflash the GAPPS and it would respond with a success after seeing all the apps install but after a reboot none was there.
razredge said:
The main problem I've been having has not been with the ROM itself. I had a few vanillas that after resizing and installing GAPPS the actual apps don't show up. I'd go back into TWRP and reflash the GAPPS and it would respond with a success after seeing all the apps install but after a reboot none was there.
Click to expand...
Click to collapse
I just had that with gapps install I was trying. And in recovery after the gapps flash, before reboot I looked around with twrp file manager. I see all the apps installed. But they are not in the correct location.
They are getting installed in the /system-root/app folder rather than the /system-root/system/app folder.
I don't know the fix yet. I mentioned it in the twrp thread and diplomatic has said he does not know why it didn't go as it was supposed to .
mrmazak said:
I just had that with gapps install I was trying. And in recovery after the gapps flash, before reboot I looked around with twrp file manager. I see all the apps installed. But they are not in the correct location.
They are getting installed in the /system-root/app folder rather than the /system-root/system/app folder.
I don't know the fix yet. I mentioned it in the twrp thread and diplomatic has said he does not know why it didn't go as it was supposed to .
Click to expand...
Click to collapse
Interesting.... I'll have to keep an eye on that. I didn't even pay attention where they installed to. Thanks for the heads up!
mrmazak said:
I just had that with gapps install I was trying. And in recovery after the gapps flash, before reboot I looked around with twrp file manager. I see all the apps installed. But they are not in the correct location.
They are getting installed in the /system-root/app folder rather than the /system-root/system/app folder.
I don't know the fix yet. I mentioned it in the twrp thread and diplomatic has said he does not know why it didn't go as it was supposed to .
Click to expand...
Click to collapse
Are you sure that is not correct? Because I just checked on my Onn 8 with the stock rom and they are in /system/app/.
There system privileged apps in: /system/priv-app. Updates are in /data/app, I believe.
Has anyone had success in installing opengapps on one of these tablets? Also, has anyone tried installing it with System mounted in TWRP? Even if it doesn't work in TWRP, I believe the install script supports running on Android too.
How has anyone been able to flash a gsi. Ive even tried disabling avb but cant get it to boot. After reboot twrp dosent even recognize an os installed
Sent from my SM-G975U1 using XDA Labs
diplomatic said:
Has anyone had success in installing opengapps on one of these tablets? Also, has anyone tried installing it with System mounted in TWRP? Even if it doesn't work in TWRP, I believe the install script supports running on Android too.
Click to expand...
Click to collapse
I haven't so far. I'll try with mounting system and post the results.
razredge said:
I haven't so far. I'll try with mounting system and post the results.
Click to expand...
Click to collapse
Fast forward 20 days... any progress?
diplomatic said:
Fast forward 20 days... any progress?
Click to expand...
Click to collapse
Woops.... No it still doesn't work. Actually it made one of my 8's bootloop after.
I found this solution in another thread:
- Format data partition and reboot recovery.
- Open terminal in twrp without system, data, and cache mounted.
- Enter the following commands:
e2fsck -y /dev/block/by-name/system
e2fsck -f /dev/block/by-name/system
resize2fs /dev/block/by-name/system
- Then reboot twrp
- Flash system img reboot recovery
- After that flash pico gapps without system mounted
Thats how i was able to successfully flash gapps on aosp phh 10. You may need to try a couple times but it should work.
Sent from my SM-G975U1 using XDA Labs
jwarrior319 said:
I found this solution in another thread:
- Format data partition and reboot recovery.
- Open terminal in twrp without system, data, and cache mounted.
- Enter the following commands:
e2fsck -y /dev/block/by-name/system
e2fsck -f /dev/block/by-name/system
resize2fs /dev/block/by-name/system
- Then reboot twrp
- Flash system img reboot recovery
- After that flash pico gapps without system mounted
Thats how i was able to successfully flash gapps on aosp phh 10. You may need to try a couple times but it should work.
Click to expand...
Click to collapse
So you got phh 10 to boot? How does it run any major bugs? Thanks