LineageOS13-port-R1-HD (camera-mostly- works) - BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel

known issue:
1> camera occasionally stops working and needs reboot to work again
2> gps not working
3> Mic not working
,,,V3.5 fixed mic,gps, and added open camera as default camera(removed CM snap), include gps test,
4> video camera not recording--V3.7 has fixed back video recording front still not working--also camera has still crashed on V3.7(but less often)
V3.8 synch up to changes made in SLIM6 port. Audio has not dropped out in this RoM like it has been for SLIM.
Files listed here under /system/lib/hw came from slim port. Other files under added and changed come from BLU R1_HD V21
Addional files under /priv-app came from apk mirror . com
V5.2
Removed extra apps previously added for testing.
Changed boot.img init files to change permissions.
Sim card 2 not tested by me I only have one card. Sim one works phone, text, and data.
Rom ported from BLU_Max_Life
need unlocked bootloader
need TWRP => Latest TWRP 3.1.1-0
gapps (google apps) not included. If want/ need playstore add gapps.
As with any and all modifications to your phone, you do at your own risk
.
.
.
XDA:DevDB Information
LineageOS 13 Port, ROM for the BLU R1 HD
Contributors
mrmazak, @vampirefo
ROM OS Version: 6.0.x Marshmallow
Based On: @vampirefo 'sLineageos-13-BLU_Max_Life
Version Information
Status: Beta
Current Beta Version: port-3.8
Beta Release Date: 2017-06-18
Created 2017-06-14
Last Updated 2018-02-27

updated link and photos and thanks :]

When I click the rom link it sends me to aliexpress?

is that the right image to flash >> lineage-13.0-20170527-UNOFFICIAL-Life_Max.zip
from TWRP 3.0.3-0 by Vampirefo or we need a newer TWRP version?

no that is not the right file. that is the rom this was ported from.
the download for this device is in the download tab

That also, the other one points to wrong device...only gapps link works properly
---------- Post added at 09:55 PM ---------- Previous post was at 09:48 PM ----------
mrmazak said:
no that is not the right file. that is the rom this was ported from.
the download for this device is in the download tab
Click to expand...
Click to collapse
My apologies , I always forget about dl tab...and use to the direct links...

I recently flashed this and latest openGapps.
Seems to be working fine, only bug I've found so far is CM setup thought my phone had a fingerprint sensor.
Better than the stock rom.
---------- Post added at 03:06 AM ---------- Previous post was at 02:57 AM ----------
Actually it appears to have trouble accessing the front facing camera... I will try with opencamera instead of the stock CM camera app.

roboman2444 said:
I recently flashed this and latest openGapps.
Seems to be working fine, only bug I've found so far is CM setup thought my phone had a fingerprint sensor.
Better than the stock rom.
---------- Post added at 03:06 AM ---------- Previous post was at 02:57 AM ----------
Actually it appears to have trouble accessing the front facing camera... I will try with opencamera instead of the stock CM camera app.
Click to expand...
Click to collapse
Trouble, as in what.
I just took multiple shots front and back both.
No problem.
edit;:
right after that opened camera from lock screen, now having trouble connecting to camera at all. and some icons have gone(phone in particular). doing reset now

mrmazak said:
Trouble, as in what.
I just took multiple shots front and back both.
No problem.
Click to expand...
Click to collapse
It was complaining about not being able to access it...
Just required a reboot, works fine now.

I just flashed the lineage-13.0-R1-HD-Port-2.zip rom from TWRP, it says a success flash but when rebooting, it always goes to recovery ???

pas7771 said:
I just flashed the lineage-13.0-R1-HD-Port-2.zip rom from TWRP, it says a success flash but when rebooting, it always goes to recovery ???
Click to expand...
Click to collapse
I had similar issue once before, it was due to not mounting system partition then booted correctly...

So cameras working or not, You mentioned it's hanging?

Mae7 said:
So cameras working or not, You mentioned it's hanging?
Click to expand...
Click to collapse
It works when you first boot, but after short time it will no longer connect.
Appears to happen more if the selfie side is on. (i never remember if that is front or back)

kormend said:
I had similar issue once before, it was due to not mounting system partition then booted correctly...
Click to expand...
Click to collapse
do I flash this rom with system mounted in twrp or umounted? then I need to mount the partition before reboot.
I'm so confused...

pas7771 said:
do I flash this rom with system mounted in twrp or umounted? then I need to mount the partition before reboot.
I'm so confused...
Click to expand...
Click to collapse
you shouldnt have to touch the mount
99.9% of the time, unless you are doing stuff in terminal from recovery , the mount screen should look like the photo attached

So I got rom flashed and gapps loaded all seems fine except wifi won't turn on/connect and also I have no network access via sim1/sim2, flashed slimrom 6 got same outcome, now trying to recover my previous stock rom....
Update stock rom recovered and wifi/network access is restore, so not sure why either Slimrom6/Lineage not allowing wifi/network access, under the system settings IP are showing blank on sim 1/2 and wifi.

mrmazak said:
It works when you first boot, but after short time it will no longer connect.
Appears to happen more if the selfie side is on. (i never remember if that is front or back)
Click to expand...
Click to collapse
I disabled stock camera and installed open camera now. It has not "hug-up" again since. So as long as this trend holds up, I will just add a note to disable camera. And I do not have gapps, (gapps replaces camera, I do not know if that newer app is better)

mrmazak said:
you shouldnt have to touch the mount
99.9% of the time, unless you are doing stuff in terminal from recovery , the mount screen should look like the photo attached
Click to expand...
Click to collapse
Ok great I flashed the rom like the picture but still. it always go back to recovery. I tried installing from the internal and from the micro sd card
wipe everything, did all flashing again still it boot in recovery.
my phone is a PRIME BLU R1 HD v 6.6 unlocked successfully with tool V11
what you guys thing I should do now to get at least something going?

pas7771 said:
Ok great I flashed the rom like the picture but still. it always go back to recovery. I tried installing from the internal and from the micro sd card
wipe everything, did all flashing again still it boot in recovery.
my phone is a PRIME BLU R1 HD v 6.6 unlocked successfully with tool V11
what you guys thing I should do now to get at least something going?
Click to expand...
Click to collapse
you also had some problem with flashing wrong recovery. right.
perhaps you should also format /data.
from twrp => wipe menu => lower right corner button "format data" => must type "yes" to confirm.
then will need to install from micro sd card. Just in case remove sdcard before format

mrmazak said:
you also had some problem with flashing wrong recovery. right.
perhaps you should also format /data.
from twrp => wipe menu => lower right corner button "format data" => must type "yes" to confirm.
then will need to install from micro sd card. Just in case remove sdcard before format
Click to expand...
Click to collapse
yes, I re-flashed the recovery image from fastboot..
Could I have a boot img partition corrupt ?
I did all the wipe possible, format the data with "yes" re-flashed the rom and still it goes back to recovery
any other solution I can use?

Related

[CWM][TWRP] For the Samsung X Cover 2 aka GT-S7710 aka skomer

Hi,
a few weeks ago I got a Samsung X Cover 2 after my loved Defy boke down...Thanks to the rooted image that theboegl created I examined the device and started to port CWM to the device. Some photos of CWM on the S7710 are here. Sorry - cant post outside links before I did 10 posts....attached.:silly: Thanks to OliverG96 who worked on CM for the S3 mini that is quite similiar to the skomer it wasn't a hard job to get it running.
The source is on my github account. (no link - see above - just google: github flxo). Feel free to comment and improve....
Code:
sudo heimdall flash --pit skomer.pit --Kernel2 recovery.img
DISCLAIMER: Use this recovery image at your own risk! You are responsible to any harm that is caused to your device during the use of this software.
Download
Mirror
CWM Changelog:
2013/07/08: Added kernel build with source from Samsung Open Source. Fixed external_sd stuff that enabled restore and backup to the sd.
2013/07/09: Fixed CWM boot loop (reboot recovery menu item or reboot syscall). Updated j4fs and param kernel modules.
2013/07/11: Added ext4 capabilities to installer (needed for otapackage). Updated fstab with reserved area at the partition end.
2013/07/19: Updated to version 6.0.3.3. edit: weird reboot issue.
2013/07/19: Updated to version 6.0.3.6 (cm-10.1). Sideload still not functional.
2013/11/03: Updated to version 6.0.4.4 (cm-10.2).
2013/11/09: Fixed USB and sideload. Do not use.
2013/11/14: Updated to version 6.0.4.5. Added param and j4fs modules to recovery.
2014/01/12: Updated to version 6.0.4.6. <-- USE THIS VERSION​
TWRP Changelog:
2013/12/07: Initial TWRP version from Omnirom 4.3 branch
2013/12/21: Source update. Minor kernel fixes.​
Thanks for your work!
For those who want to try this beta-build:
download the newest odin-flashable build from here - thanks to @flxo
start Odin >= 3.07
select the downloaded CMW in the PDA section
unselect autoreboot if you would like to test it after flashing immediately
plug your XCover2 in
flash it
let it reboot/if you want to test cwm now:
power off by holding the power button
hold Volume +, Home and Power button simultaneous
you should see cwm
done
BTW: no one should just follow me by doing a reboot recovery, though I have created an odin-flashable restore - build 12.07.2013 for getting out of the "boot to recovery" loop without loosing data.
flxo said:
Hi,
a few weeks ago I got a Samsung X Cover 2 after my loved Defy boke down...
Thanks to the rooted image that theboegl created I examined the device and started to port CWM to the device. Some photos of CWM on the S7710 are here. Sorry - cant post outside links before I did 10 posts....attached.:silly:
Thanks to OliverG96 who worked on CM for the S3 mini that is quite similiar to the skomer it wasn't a hard job to get it running.
The source is on my github account. (no link - see above - just google: github flxo). Feel free to comment and improve....
I did not try yet to flash a zip with the CWM port but so far the graphics look good and the SD is mounted. I attached the recovery image to this post:
Hang on.
cheers,
flxo
sorry for the short description, but it's Friday 9pm and I really shouldn't sit in front of my computer...
Click to expand...
Click to collapse
I'll try this out. Oh and if this works, I'll see if I can start porting any roms to this device now
---------- Post added at 11:28 AM ---------- Previous post was at 10:50 AM ----------
Yo, I made a flashable odin.tar! Enjoy testing guys, cheers
http://rapidshare.com/files/2716144166/recovery.tar.md5
I keep my fingers crossed for it.
It will open new world for our phone.
Wysyłane z mojego Nexus 7 za pomocą Tapatalk 2
TheBoegl said:
BTW: no one should just follow me by doing a reboot recovery, though I have created an odin-flashable restore for getting out of the "boot to recovery" loop without loosing data.
Click to expand...
Click to collapse
Thanks. That fix is exactly what I need right now...
Everyone be carefull - this image is absolutely untested and may brick your device....
Lum_Os said:
I'll try this out. Oh and if this works, I'll see if I can start porting any roms to this device now
---------- Post added at 11:28 AM ---------- Previous post was at 10:50 AM ----------
Yo, I made a flashable odin.tar! Enjoy testing guys, cheers
http://rapidshare.com/files/2716144166/recovery.tar.md5
Click to expand...
Click to collapse
Has anyone tried
kolmanb said:
Has anyone tried
Click to expand...
Click to collapse
Tried flashing, works like a charm. Just hold volume up, home and power, let go of power when you feel vibration and keep hold volume up and home button and you're in cwm! Gonna try port first custom rom, cm10 from s2 and see if it truly works
Hello,
I have just tested : very good ! very good !
Thanks a lot.
:laugh:
Works perfectly super !:laugh::good:
backup: ok
restore: ok
Apology : restore works fine
install zip : from sd card; ext.sd card ok
kolmanb said:
Apology : restore works fine
install zip : from sd card; ext.sd card ok
Click to expand...
Click to collapse
Thanks!
I changed the recovery.fstab to mount the external SD on /sdcard. Storing backups on the real SD is IMHO more convenient.
The updated image is: 20130606_recovery.img
Thanks to TheBoegl for the hint.
flxo said:
I changed the recovery.fstab to mount the external SD on /sdcard. Storing backups on the real SD is IMHO more convenient.
Click to expand...
Click to collapse
Thats great. For everyone who want to flash this with odin try this image - it is the packed version of @flxo.
I have reupped the previous recoveries because they were unflashable with odin.
I really apologize for that mistake my Finnish, Slovenian and Bulgarian members if Odin is stuck, just unplug your phone and select the new image, plug it in again and flash.
This double post is to inform the few of you who have downloaded the file already.
I created an Odin flashable .tar.md5 of the 20130606_1_ version. I tried it myself, works fine.
One nitpicky question: flxo, shouldn't it be 20130706? It's July after all
flxo said:
[*]reboot recovery: reboots device normally. failed.
Click to expand...
Click to collapse
20130606_1_ fixed that for me, the device froze for half a minute and then rebooted into recovery.
EDIT:
Bad news: Somehow, the phone exclusively reboots into recovery now. I don't know if it's due to choosing "reboot recovery" or something else...
HeavyMoertel said:
Bad news: Somehow, the phone exclusively reboots into recovery now. I don't know if it's due to choosing "reboot recovery" or something else...
Click to expand...
Click to collapse
I guess you found my fix for that in the second post :good:
TheBoegl said:
I guess you found my fix for that in the second post :good:
Click to expand...
Click to collapse
Yeah, well, I really shouldn't have followed you on that, I guess.
But many thanks for reminding me of your fix. :highfive:
---------- Post added at 12:45 AM ---------- Previous post was at 12:13 AM ----------
Issue: factory reset formats the whole SD card.
I'm so sorry, can you tell me how to install CWM, I tried to Odin MOD but nothing Nest, thank you very much.
you were faster than i thought.
I've added the description and link in the second post.
Let me know if you need more information.

LG L5II E460 PhilZ Touch CWM Advanced

Hello XDA
I'm releasing recoverys since I'm not able to port Cyanogenmod on our phone even if we have all opensource released by LG,
just for the lack of the knowledge, I'm pretty begginer. Hopefully some kind people see this and feel sad about our orphan child L5II and port us CM
This is the second recovery I release for our devices, this seems to be the best in my opinion.
I take no credits for this as I only built it for our device.
So yeah the beautyful PhilZ Touch Recovery is now avaible for our L5IIs.
This is the PhilZ Touch Recovery 6.57.9 Andvanced Edition with CWM v6.0.5.1
We're going to use the same way as for previous recoverys to flash it.
PRE-REQUISITES
1. Root Permissions on your LG L5II
2. Unlocked bootlader
3. Terminal Emulator (can be downloaded from Play Store)
NOTE: I tested this only on E460, I hope this works also on other L5IIs but I'm not sure.
I DO NOT ASSUME ANY RESPONSABILITY FOR BRICKED DEVICES OR ANY OTHER DAMAGE
DURING THIS PROCEDURE, DO THIS ON YOUR OWN RISK.
DOWNLOAD:
(If someone wants to provide any mirror will be appreciated)
http://uppit.com/pbjhcmfju47z/recovery.rar
1. Extract the downloaded file.
MD5 sum:
Code:
[COLOR="red"]BD8BDDD56E50100795F437E7449A20F5[/COLOR]
2.Then place it in your SDcard and open your terminal emulator
and type the following text:
Code:
su
dd if=/mnt/sdcard2/recovery.img of=/dev/recovery
3. When you have successfuly executed the previous commands in terminal emulator reboot in recovery mode to test it
Type this in terminal emulator
Code:
su
reboot recovery
Or switch off your phone and hold VOLUME DOWN + QUICKBUTTON + POWER BUTTON until LG logo shows and then release, it will boot into recovery mode in few seconds.
I really hope it worked for you and you can now enjoy your beautyful recovery.
Let me know about bugs and on which models it works!
Thank you for your attention!
IMPORTANT NOTES:
-As this is based on stock recovery source it seems that LG left us a bug. It won't mount\format sdcard0(internal sdcard). So I've found out that this isn't the fault of revovery in itself but recovery.img containing a bug left by manufactor. So my objective now is to solve it, I can't actually say when it will get fixed, I don't have much time to work on it because of my real life issues.
link is not working
It's working, I just checked it now.
In these days I'll provide some mirrors so there won't be problems.
I can confirm it is working on my e450
it doesn't mount internal storage. not sure if this is because mine is a e450 or if it is the recovery. havent tried flashing any zips yet but will let you know how it goes.
If you send me your stock recovery.img I may build it for e450 and we'll see if that will resolve the issue.
Beershake said:
If you send me your stock recovery.img I may build it for e450 and we'll see if that will resolve the issue.
Click to expand...
Click to collapse
https://dl.dropboxusercontent.com/u/51036208/Android/Stock/mtkdroid/recovery.img
There you go.
You are a legend.
slipsystem said:
https://dl.dropboxusercontent.com/u/51036208/Android/Stock/mtkdroid/recovery.img
There you go.
You are a legend.
Click to expand...
Click to collapse
I will do it today if I have time, if not tomorrow for sure. I'm not a legend, You are a legend because of all development you have done so far this lovely device
EDIT: It seems to be the recovery's in itself issue, I"m encountering this issue even on my E460. I'm trying to figure out what causes it and hopefully resolve.
Just flash slimsystem with no issue s
aroma installer works and it writes to the system partition properly.
very nice recovery
slipsystem said:
Just flash slimsystem with no issue s
aroma installer works and it writes to the system partition properly.
very nice recovery
Click to expand...
Click to collapse
I'm glad you like it, altough credits goes to it's original ideator.
Updated main post with some important notes.
worked on E460 without a problem! Thank you, awesome stuff!
---------- Post added at 01:05 PM ---------- Previous post was at 12:10 PM ----------
Since we have unlocked bootloader and custom recovery, is it possible to custom roms will arrive? Maybe CM or SlimRoms?
0b4 said:
worked on E460 without a problem! Thank you, awesome stuff!
---------- Post added at 01:05 PM ---------- Previous post was at 12:10 PM ----------
Since we have unlocked bootloader and custom recovery, is it possible to custom roms will arrive? Maybe CM or SlimRoms?
Click to expand...
Click to collapse
can you do a backup??
t-driver said:
can you do a backup??
Click to expand...
Click to collapse
I haven't tried it. But I think it should work. I can't try it out because I do not have much free space. (Usually CWM backups are minimum 1 GB)
has anyone done a backup yet? or is there still something missing??
t-driver said:
has anyone done a backup yet? or is there still something missing??
Click to expand...
Click to collapse
I did a back up and restore. Select custom backup and select boot recovery and system
t-driver said:
has anyone done a backup yet? or is there still something missing??
Click to expand...
Click to collapse
slipsystem said:
I did a back up and restore. Select custom backup and select boot recovery and system
Click to expand...
Click to collapse
Full backup is working too, it takes a lot of space if you don't set compression level to high in advanced options. It also may depend on data that you have in your internal sdcard as it backs up that too.
The full backup minimum size for me was 4.9 GB with default compression level(default is set to none).
Instead with maximun compression level(tar+gz enabled, and compression level set to high) the minimum size was less that 2.5GB.
Please note that sizes may be different, it all depens on you. I'd suggest you to do what slipsystem said here. So do a Custom Backup and select following:
Boot(x)
Recocery(x)
System(x)
By doing this way your personal data on internal memory won't be included into backup. This way also the backup max size wont be higher than 1GB(it depends on what did you put system resources, normally its slightly higher than 800MB).
how to check if bootloader is locked or not?
Flash recovery if you get secure boot when trying to enter recovery then the bootloader is locked.
Can you give a mirror? The link dosn't work for me :/
The link also not worked or me please provide a mirror

[DOWNLOAD] Android Wear update MEC23G to MWD48B

Just got an update on my watch and, as always, pulled the update.zip for you guys!
If you're having troubles installing this ZIP please refer to this post here: http://forum.xda-developers.com/showpost.php?p=67403296&postcount=19
----------
Quick Install "Guide" if it's still failing for you:
1) Install TWRP from THIS THREAD HERE
2) Reboot into fastboot mode by turning the watch off and on again and while the black screen shows up constantly swipe from the left upper corner to the lower right corner.
3) Flash the TWRP provided above and reboot into recovery, then push the unpacked TWRP backup into "/sdcard/TWRP/BACKUPS/xxxxxxxxxxx/" (to get the last folder simply make a backup of only your boot partition first, it's the fastest)
4) Restore the backup provided IN THIS POST HERE onto your watch via the in 1 flashed TWRP
1) MUCH EASIER: Flash these instead the TWRP way, far far easier!
2) Let the OTA update install automatically
----------
ZIP MD5: 6844d45bf6d4a1e1d6b15e908579d354
>> DROPBOX <<
>> GOOGLE DRIVE <<
>> OneDrive <<
EpicLPer said:
Just got an update on my watch and, as always, pulled the update.zip for you guys!
ZIP MD5: 6844d45bf6d4a1e1d6b15e908579d354
>> DROPBOX <<
>> GOOGLE DRIVE <<
Click to expand...
Click to collapse
I've got TWRP 3.0.?? on the watch and it refuses to flash, error is
Code:
Unable to statfs '/system/.'.
I've flashed the stock recovery in LG G Watch tools. It went fine, so I've proceeded to install the update the standard way. It seemed to be fine, but than it stopped, with the "Dead Android" image. After using the reset button the built in recovery is dead, but the watch boots. Any ideas?
EDIT: TWRP won't mount /system for some reason, you tap the checkbox and nothing happens. Not even as RO.
kokesh said:
I've got TWRP 3.0.?? on the watch and it refuses to flash, error is
I've flashed the stock recovery in LG G Watch tools. It went fine, so I've proceeded to install the update the standard way. It seemed to be fine, but than it stopped, with the "Dead Android" image. After using the reset button the built in recovery is dead, but the watch boots. Any ideas?
EDIT: TWRP won't mount /system for some reason, you tap the checkbox and nothing happens. Not even as RO.
Click to expand...
Click to collapse
You have to use the edited one on my '' how to root guide'' as the official TWRP those not support squashfs
Xmaster24 said:
You have to use the edited one on my '' how to root guide'' as the official TWRP those not support squashfs
Click to expand...
Click to collapse
Thank you. Your recovery mounts /system, but I am still getting the same error.
kokesh said:
Thank you. Your recovery mounts /system, but I am still getting the same error.
Click to expand...
Click to collapse
yeah it can't write to it, you have to use the stock recovery for that. You are able to write to it but you must first format the partition as writable and then flash your system image/ backup. I'm getting the usual "old keys" error of TWRP not error you mentioned, just means The TWRP is too old base
---------- Post added at 11:13 AM ---------- Previous post was at 11:02 AM ----------
Those anyone have a link to the 6.0.1 stock recovery?
Those anyone have a link to the 6.0.1 stock recovery?
Click to expand...
Click to collapse
Isn't it possible to get it from the 6.0.1 OTA?
kokesh said:
Isn't it possible to get it from the 6.0.1 OTA?
Click to expand...
Click to collapse
No, its stored in a propietary .dat file so good luck with that. Hopefully someone wasn't as foolish as me and deleted their recovery backup
Xmaster24 said:
No, its stored in a propietary .dat file so good luck with that. Hopefully someone wasn't as foolish as me and deleted their recovery backup
Click to expand...
Click to collapse
We could try flashing an older version of Android Wear (the one provided with the one Toolbox someone made here) and let it update to the latest version again.
EpicLPer said:
We could try flashing an older version of Android Wear (the one provided with the one Toolbox someone made here) and let it update to the latest version again.
Click to expand...
Click to collapse
Nope I found it thank god. I had kept a backup of the awful stock kernel just in case when I was initially testing invisiblek's kernel. Luckily its still there in all its awful glory and I will share it here as when you boot up with the stock kernel the system auto flashes the stock recovery because thats how stock is for everything
Xmaster24 said:
Nope I found it thank god. I had kept a backup of the awful stock kernel just in case when I was initially testing invisiblek's kernel. Luckily its still there in all its awful glory and I will share it here as when you boot up with the stock kernel the system auto flashes the stock recovery because thats how stock is for everything
Click to expand...
Click to collapse
Btw. I tried going back to stock yesterday (without locking the bootloader tho) but I may have used a wrong or too old stock recovery version.
Also the only reason why the OTA is reporting an issue while flashing the package with the squashfs enabled TWRP is because the script gets a string back that's not identical with the one it expects. Maybe someone could "hack out" that check and make it TWRP flashable.
EpicLPer said:
Btw. I tried going back to stock yesterday (without locking the bootloader tho) but I may have used a wrong or too old stock recovery version.
Also the only reason why the OTA is reporting an issue while flashing the package with the squashfs enabled TWRP is because the script gets a string back that's not identical with the one it expects. Maybe someone could "hack out" that check and make it TWRP flashable.
Click to expand...
Click to collapse
No the problem is the TWRP was built on an old base of the LG G watch specifically the last 5.1.1 update so the zip thinks the whole system is still on 5.1.1 as TWRP is still on that. I don't think the 6.0.1 source has been released yet so I don't think a recovery could be built with a 6.0.1 base of the lg g watch.
Xmaster24 said:
No the problem is the TWRP was built on an old base of the LG G watch specifically the last 5.1.1 update so the zip thinks the whole system is still on 5.1.1 as TWRP is still on that.
Click to expand...
Click to collapse
That's exactly what I mean with the check and the "wrong" string it gets back I have no clue on how to disable this check inside the ZIP-script tho.
EpicLPer said:
That's exactly what I mean with the check and the "wrong" string it gets back I have no clue on how to disable this check inside the ZIP-script tho.
Click to expand...
Click to collapse
it's not worth it, just flash the stock boot.img once I upload it, waiting for the ART cache to build now
---------- Post added at 12:10 PM ---------- Previous post was at 12:05 PM ----------
xmaster24 said:
it's not worth it, just flash the stock boot.img once i upload it, waiting for the art cache to build now
Click to expand...
Click to collapse
omfg the new kernel actually has a hotplug!!!!!!!!!!!!!!!!!! Finally more than 1 core on stock!!!!!!!!!!!!!
Xmaster24 said:
it's not worth it, just flash the stock boot.img once I upload it, waiting for the ART cache to build now
---------- Post added at 12:10 PM ---------- Previous post was at 12:05 PM ----------
omfg the new kernel actually has a hotplug!!!!!!!!!!!!!!!!!! Finally more than 1 core on stock!!!!!!!!!!!!!
Click to expand...
Click to collapse
You mean the new OTA kernel or the 6.X kernels?
EpicLPer said:
You mean the new OTA kernel or the 6.X kernels?
Click to expand...
Click to collapse
the stock kernel and nvm it was just AIDA64 glitching out, actually thought more than one core was in use The upside it thought the reboot button is back! don't know why they ever removed it but collio
Xmaster24 said:
nvm it was just AIDA64 glitching out, actually thought more than one core was in use ;-(
Click to expand...
Click to collapse
I actually think there are more than 1 cores activate at a time now, the watch has gotten pretty fast with the latest updates and so on, I don't even feel the need for a custom kernel anymore since that.
EpicLPer said:
I actually think there are more than 1 cores activate at a time now, the watch has gotten pretty fast with the latest updates and so on, I don't even feel the need for a custom kernel anymore since that.
Click to expand...
Click to collapse
Nope after about 1 minute after boot the phone locks to 787mhz with userspace governor and I can confirm there is no CPU hotplug aswell. I don't know how you survive with the abysmal lag but ok cool. During the first minute of boot for whatever reason it uses 2 cores and ondemand, would rather have that always lol.
EpicLPer said:
We could try flashing an older version of Android Wear (the one provided with the one Toolbox someone made here) and let it update to the latest version again.
Click to expand...
Click to collapse
Tried, didn't work. My guess is that it didn't handle squash FS. I was left with dead Android guy on the screen
For everyone to enjoy HERE is the stock kernel, @EpicLPer add this to the op to save everyone some trouble. NOTE: you have to boot to system once before the stock recovery is restored. Also it is a twrp backup so you have to adb push it to /sdcard/TWRP/BACKUPS/ to use it. If someone could just get the boot.img raw that would be great, I was too lazy to do it lel.
Xmaster24 said:
Nope after about 1 minute after boot the phone locks to 787mhz with userspace governor and I can confirm there is no CPU hotplug aswell. I don't know how you survive with the abysmal lag but ok cool. During the first minute of boot for whatever reason it uses 2 cores and ondemand, would rather have that always lol.
Click to expand...
Click to collapse
Actually... mine's running pretty well, no lag, no freezing animations, apps take 1 second to open and scrolling is smooth too.
Either I have some leftovers of an old kernel (which I don't think, or, hope) or I'm having a magic LG Watch

z016D TWRP

i found this trwp recovery floating around i dont know who made it.
it boots fine but no touch screen hopefully someone can fix it
https://www.androidfilehost.com/?fid=457095661767138152
kvip60 said:
i found this trwp recovery floating around i dont know who made it.
it boots fine but no touch screen hopefully someone can fix it
https://www.androidfilehost.com/?fid=457095661767138152
Click to expand...
Click to collapse
What's the easiest way to install this?
I didn't install it I just used" fastboot boot image-name"
kvip60 said:
I didn't install it I just used" fastboot boot image-name"
Click to expand...
Click to collapse
Ok Thanks. I am in and generating a backup. The touch screen was working for me mostly. It won't let me select Micro SDCard to save my backup.
Yeah like I said it need some repair I am pretty sure the mount points aren't perfect and I didn't compile it I had to use an otg and mouse to navigate
kvip60 said:
Yeah like I said it need some repair I am pretty sure the mount points aren't perfect and I didn't compile it I had to use an otg and mouse to navigate
Click to expand...
Click to collapse
What I did to navigate was I had to push the power button then it would bring the screen up where you can swipe the bottom to unlock the screen and use touchscreen. Navigating the storage was odd because it shows it is stuck on Internal storage, but If i click on SDCard, it will take me to that directory. I hope there is a nice update to this is the near future, so we don't have to access it through "adb reboot recovery"
You can flash it if you like I just don't trust this copy yet waiting for an update before I flash it
You can use" fastboot flash recovery twrp.img" to flash rather than "fastboot boot twrp.img " to boot it
kvip60 said:
You can flash it if you like I just don't trust this copy yet waiting for an update before I flash it
You can use" fastboot flash recovery twrp.img" to flash rather than "fastboot boot twrp.img " to boot it
Click to expand...
Click to collapse
Oh man you were so right. I had it flashed and it caused me all kinds of problems, like booting the screen upside down etc. I was finally able to find the recovery.img in another thread and get back the stock recovery. I think I will also wait until there is a more stable TWRP version.
I always use boot to test and I always backup my recovery before flashing because I had that happen to me before
Any idea on when a decent working custom recovery will be available?
blahforme said:
Any idea on when a decent working custom recovery will be available?
Click to expand...
Click to collapse
Probably when someone will have the will & time to work on it.
Maybe you'd like to take on this topic?
Lol. I hear you. I have very little understanding of Linux I have tried to make one but there aren't enough information about compiling device /vendor tree for a new device to go on
Just visit this page and you will get TWRP for Z016D. It's a Taiwan website with Chinese but you can see the blue link marked as "TWRP" and there you are.
https://www.asus.com/zentalk/tw/thread-214217-1-1.html
lssong99 said:
Just visit this page and you will get TWRP for Z016D. It's a Taiwan website with Chinese but you can see the blue link marked as "TWRP" and there you are.
https://www.asus.com/zentalk/tw/thread-214217-1-1.html
Click to expand...
Click to collapse
Thanks for this. Posting the Mega so people don't have to make an Asus account to grab it.
https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
The 20170218 recovery works perfectly with my phone (6/64gb, 820). The first one posted in the OP worked, but was a bit glitchy. The updated one has working SD reading and touchscreen works without having to lock it first.
Could someone please tell me why twrp is booting upside down on my device, and how do I fix it? I just tried to run it in fastboot boot twrp-3.0.3-0-Z016D-20170218.img and once again it loads upside down, however the touch screen is where it normally is suppose to be, which makes it very difficult to navigate the menus. It is very frustrating. This has happened to me multiple times this week. I can't seem to get it to boot/load properly.
blahforme said:
Could someone please tell me why twrp is booting upside down on my device, and how do I fix it? I just tried to run it in fastboot boot twrp-3.0.3-0-Z016D-20170218.img and once again it loads upside down, however the touch screen is where it normally is suppose to be, which makes it very difficult to navigate the menus. It is very frustrating. This has happened to me multiple times this week. I can't seem to get it to boot/load properly.
Click to expand...
Click to collapse
Are you using the Snapdragon 821 version by any chance? Cause people with the s820 seem to be working fine.
I am using 821 my screen is flipped and no touch even after locking it
Huffy1 said:
Are you using the Snapdragon 821 version by any chance? Cause people with the s820 seem to be working fine.
Click to expand...
Click to collapse
No, I am using the sd820.
---------- Post added at 08:25 PM ---------- Previous post was at 08:07 PM ----------
I really don't want to wipe everything and start all over from scratch because everything else is working great right now. I guess if there is no easy solution, then I will just leave it alone. I ran it with fastboot and then made a backup and saved it on my microSD card. But I am worried if I wipe everything and start all over again, then I will have to call my bank again to verify my cards for Android pay. I am running the stock firmware version 1698, with stock recovery, an unlocked bootloader, & rooted. Also have Magisk & Titanium Pro installed, and I verified that Andoid pay works for me. (I already bought something using Android pay).
blahforme said:
No, I am using the sd820.
---------- Post added at 08:25 PM ---------- Previous post was at 08:07 PM ----------
I really don't want to wipe everything and start all over from scratch because everything else is working great right now. I guess if there is no easy solution, then I will just leave it alone. I ran it with fastboot and then made a backup and saved it on my microSD card. But I am worried if I wipe everything and start all over again, then I will have to call my bank again to verify my cards for Android pay. I am running the stock firmware version 1698, with stock recovery, an unlocked bootloader, & rooted. Also have Magisk & Titanium Pro installed, and I verified that Andoid pay works for me. (I already bought something using Android pay).
Click to expand...
Click to collapse
How did you install Magisk having stock recovery? Using the in-app installation?
---------- Post added at 01:08 PM ---------- Previous post was at 01:05 PM ----------
It seems @EypCnn is the developer of this TWRP builds...
sebastiandg7 said:
How did you install Magisk having stock recovery? Using the in-app installation?
Click to expand...
Click to collapse
I flashed Magisk v11.1 with TWRP, then installed Magisk Manager from the Google Play Store, after I rebooted my device. I did that by booting in to TWRP with fastboot to flash the .zip file. I did not flash TWRP to install Magisk.

[ROM][GSI] AOSP 10 - Discussion

Hi, I have been testing this on this device, and finally I was able to make AOSP 10 (GSI) run on our device.
Our device needs overlay to fix this issues. I will try to work into that
How to flash
WARNING: Your device must have unlocked bootloader
1. Download the latest TWRP Recovery: https://forum.xda-developers.com/mi...overy-unofficial-twrp-xiaomi-mi-note-t4015805
2. Download the latest AOSP 10 GSI (ab with gapps): https://github.com/phhusson/treble_experimentations/releases/
3. Download vbmeta.img: https://github.com/TadiT7/xiaomi_ce...9.3.1-release-keys/firmware-update/vbmeta.img
4. Disable vbmeta partition by flashing vbeta.img
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5. Flash TWRP
Code:
fastboot flash recovery <twrp_file_name.img>
6. Boot TWRP, make wipe (Format Data only!)
7. Flash the AOSP system.img file to System partition
NOTE: Trying to flash system.img using fastboot causes bootloop.
Aditionally here you can flash GAPPS and Magisk
- Flash GAPPS: https://opengapps.org/
- Flash Magisk: https://github.com/topjohnwu/Magisk/releases
10. Reboot system & enjoy!
Bugs
- Fingerprint
- Auto-brightness
- NFC
-Weird notification audio: can be fixed flashing this -> https://github.com/hmuny99/GsiSystemAudioFix/raw/master/fixaudiogsi.zip
-Video recording: can be fixed by flashing this -> https://forum.xda-developers.com/attachment.php?attachmentid=4374464&d=1514638461
-Flashing Magisk causes bootloop
- GCAM Camera starts to lag when the device has been on for a long time
Since we have a complete kernel sources/device tree, we can have this as a daily diver :good:
For now, I'd need the framework-res.apk from Stock rom, if someone could provide it, that would be really helpful
iFlashed said:
For now, I'd need the framework-res.apk from Stock rom, if someone could provide it, that would be really helpful
Click to expand...
Click to collapse
I saw this on another topic.
https://forum.xda-developers.com/showpost.php?p=81824837&postcount=50
Hi, what do you think, this flashing method will work with phhussons GSI too?
https://github.com/phhusson/treble_experimentations/releases
---------- Post added at 08:00 AM ---------- Previous post was at 07:43 AM ----------
If you need it still, I can copy it now, if you tell me the full path of this file.
technoboi1 said:
Hi, what do you think, this flashing method will work with phhussons GSI too?
https://github.com/phhusson/treble_experimentations/releases
---------- Post added at 08:00 AM ---------- Previous post was at 07:43 AM ----------
If you need it still, I can copy it now, if you tell me the full path of this file.
Click to expand...
Click to collapse
Same steps, Boots up, I recommend the system-quack-arm64-ab-gapps from your link, as it includes Gapps.
However, With that both I couldn't flash Magisk or I would get a bootloop. With LoS It would also not install gapps. But would boot just fine without Gapps or Magisk.
Currently Phhussons is working with Gapps. LOS Is not, atleast for me, but neither is working with Magisk 20.4.
thank for your reply, it has same bugs like LOS?
deathhall said:
Same steps, Boots up, I recommend the system-quack-arm64-ab-gapps from your link, as it includes Gapps.
However, With that both I couldn't flash Magisk or I would get a bootloop. With LoS It would also not install gapps. But would boot just fine without Gapps or Magisk.
Currently Phhussons is working with Gapps. LOS Is not, atleast for me, but neither is working with Magisk 20.4.
Click to expand...
Click to collapse
technoboi1 said:
thank for your reply, it has same bugs like LOS?
Click to expand...
Click to collapse
Yup, Same bugs
Sent from my Mi Note 10 using Tapatalk
I remember when Android P GSI comes, we have distorted audio bugs, maybe its same bug again.
Deleting folder vendor/lib64/soundfx fixed bug in Android P.
Bugs
- Fingerprint
- Auto-brightness
- NFC
-Weird notification audio
I have been working on an overlay, but seems like I couldn't fix any bug.
Fingerprint works, but for any reason the Google API/Fingerprint config app is not recognizing it, but I can see in logcat that sensor recognizes when I use the fingerprint with any problem, so maybe problem from the GSI?
For the rest of the bugs, nothing for now
Is there an improvement?
UtkuAblak said:
Is there an improvement?
Click to expand...
Click to collapse
I'm trying to contact with phhusson. Audio can be fixed flashing a .zip
This rom use stock camera or? And what about current photo quality?
Good work and thank you guys!
Hudinited said:
This rom use stock camera or? And what about current photo quality?
Good work and thank you guys!
Click to expand...
Click to collapse
I recommend using a Gcam in order to get better quality, for example: https://www.celsoazevedo.com/files/android/google-camera/dev-urnyx05/ (tell me if you find something better!)
how did you fix the fingerprint?
iSonik said:
how did you fix the fingerprint?
Click to expand...
Click to collapse
It's not fixed yet, What I just said is that 'works' in terms that if you touch the fingerprint it will be recognized in logcat, but nothing will happend on the fingerprint setup app. Currently I'm talking with phhusson about this and thinks that this could be a GSI related issue because he told me he will make a test image
technoboi1 said:
Hi, what do you think, this flashing method will work with phhussons GSI too?
https://github.com/phhusson/treble_experimentations/releases
---------- Post added at 08:00 AM ---------- Previous post was at 07:43 AM ----------
If you need it still, I can copy it now, if you tell me the full path of this file.
Click to expand...
Click to collapse
iFlashed said:
It's not fixed yet, What I just said is that 'works' in terms that if you touch the fingerprint it will be recognized in logcat, but nothing will happend on the fingerprint setup app. Currently I'm talking with phhusson about this and thinks that this could be a GSI related issue because he told me he will make a test image
Click to expand...
Click to collapse
My fingerprint is recognized in logcat as well as the button lighting up, but it doesn't work even in stock rom funny enough.
deathhall said:
My fingerprint is recognized in logcat as well as the button lighting up, but it doesn't work even in stock rom funny enough.
Click to expand...
Click to collapse
What do you mean when you say It doesn't work in stock rom funny enough?
iFlashed said:
What do you mean when you say It doesn't work in stock rom funny enough?
Click to expand...
Click to collapse
When I flashed this GSI for Lineage 17 when the other thread first started, even after Miflashing back to Global Stock my fingerprint doesn't work anymore, If i use the testing options, it'll activate the fingerprint and register me using my finger on it, but wont activate fingerprint settings as a password, it goes to the input screen then kicks back out immediately
deathhall said:
When I flashed this GSI for Lineage 17 when the other thread first started, even after Miflashing back to Global Stock my fingerprint doesn't work anymore, If i use the testing options, it'll activate the fingerprint and register me using my finger on it, but wont activate fingerprint settings as a password, it goes to the input screen then kicks back out immediately
Click to expand...
Click to collapse
This could be something related to unlocked bootloader? u tried to relock the bootloader?
iFlashed said:
This could be something related to unlocked bootloader? u tried to relock the bootloader?
Click to expand...
Click to collapse
Are you asking if i did, or i should? Also, I don't wanna hijack the thread, maybe chat in PM or Discord or whatever you prefer?

Categories

Resources