Related
I'm trying to reflash the default the original recovery in order to install
OTA_K2PLC_CL_JB422_SENSE50_MR_Cricket_US_3.02.1050.10-2.04.1050.5_release_343402dpsh8ror12wwdww2.zip
(4.2.2 and touch5 OTA)
What is causing this error and how do I get past it?
I'd try flashing the zip, but cwm can't mount the sdcard for some reason
cricket/moonshined/rooted/superCID
what command did you send
I sent
fastboot flash recovery [imagename].img
are you unlocked?
Yes. Unlocked bootloader, rooted, moonshine s-off, with supercid (1s). Not radio, s-off, only moonshined (disables the check, from what I understand)
start with phone connected to computer while booted in OS.
then open command prompt
adb reboot bootloader
adb kill-server
fastboot flash recovery recovery.img
fastboot reboot
russellvone said:
start with phone connected to computer while booted in OS.
then open command prompt
adb reboot bootloader
adb kill-server
fastboot flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
same result
Code:
C:\Users\user\Desktop\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\user\Desktop\platform-tools>adb kill-server
* server not running *
C:\Users\user\Desktop\platform-tools>fastboot flash recovery recovery.img
< waiting for device >
sending 'recovery' (8478 KB)... OKAY
writing 'recovery'... FAILED (remote: not allowed)
C:\Users\user\Desktop\platform-tools>
ok....when in fastboot, unplug usb from computer....
then send command
fastboot flash recovery recovery.img
then plug usb into computer
see if that flashes it
same result
zomgitsanoob said:
same result
Click to expand...
Click to collapse
Windows 8.1?
Okay, I see the problem now. Somehow, somewhere along the line, my bootloader got locked again... no idea how (last OTA update, perhaps?) (says TAMPERED/LOCKED)
Do I simply follow the same procedure I did the first time, or will supercid/s-off be a problem?
lol
#EDIT#
yeah, just
fastboot flash unlocktoken Unlock_code.bin
---------- Post added at 03:41 PM ---------- Previous post was at 03:39 PM ----------
S-OFF and superCID won't be a problem
---------- Post added at 03:46 PM ---------- Previous post was at 03:41 PM ----------
also with s-off, no need to ever lock/relock you're bootloader again...
russellvone said:
lol
#EDIT#
yeah, just
fastboot flash unlocktoken Unlock_code.bin
---------- Post added at 03:41 PM ---------- Previous post was at 03:39 PM ----------
S-OFF and superCID won't be a problem
---------- Post added at 03:46 PM ---------- Previous post was at 03:41 PM ----------
also with s-off, no need to ever lock/relock you're bootloader again...
Click to expand...
Click to collapse
wait, I'm confused. Didn't I have to unlock it again right now, despite being s-off, in order to flash my recovery? Or did you mean the pl80.zip method would have worked without unlocking, since I have s-off?
nope, sorry I posted before I read you 'oops I'm relocked' post
you gotta be unlocked to flash anything, s-on or s-off
keep it unlocked, there is no reason to lock it again after you unlock it this time.....
you can accept OTA updates with unlocked bootloader being s-off
Ah, man! I unlocked the bootloader like you said and upon reboot it went to the initial set-up... it factory reset.... despite not having the stock recovery or anything
So.., back to square one- flash the recovery and I can apply the OTA update that started this whole mess, correct?
Will I lose the OTA update if I restore a remote nandroid backup from obackup?
no, you'll still be able to receive it
and as long as your
/system
is in stock condition it will go through
by /system in stock condition, you mean as in not having removed all the bs I didn't want/use in order to make room, right? because I removed the cricket account app (which did nothing anyway, the default facebook app, the rescue app... a lot o things. I have backups of the apks and the app data, though.
Of course, because f-k me, my nandroid seems to be corrupted :victory:
godammit, I just want to get this OTA update installed because it has touch5 and an updated Android. I'd tery installing from sideload, but CWM can't mount the sd card :highfive:
zomgitsanoob said:
by /system in stock condition, you mean as in not having removed all the bs I didn't want/use in order to make room, right? because I removed the cricket account app (which did nothing anyway, the default facebook app, the rescue app... a lot o things. I have backups of the apks and the app data, though.
Of course, because f-k me, my nandroid seems to be corrupted :victory:
godammit, I just want to get this OTA update installed because it has touch5 and an updated Android. I'd tery installing from sideload, but CWM can't mount the sd card :highfive:
Click to expand...
Click to collapse
what about the zip I linked to you?
just flash it
---------- Post added at 04:22 PM ---------- Previous post was at 04:20 PM ----------
https://www.dropbox.com/s/f2fq45couq54eop/4.1.2_JB_Crkt_2.04.1050.3_stock_odexed.zip
flash this then stock recovery and update after
---------- Post added at 04:30 PM ---------- Previous post was at 04:22 PM ----------
twrp twrp twrp....
I've got a twrp backup too if you want to restore it(with twrp) of course, lol
Since we're s-off, we can then flash cwm or twrp back, install root and supersu from a .zip, and use rom toolbox to start hacking all the garbage back out again (and reinstalling the xposed framwork and all the good stuff) while enjoying sense 5 and android 4.whateverversionIdon'tevenrememberrightnow-2,ithink, correct? So like square one (when we bought the phone), but but with the latest OTA? :silly:
<-- just knowledgeable enough to make a mess, apparently
yes, successfully update to 4.2.2 Sense 5 then hack it up!
Q&A for [ROM][4.4.4] Unofficial LIQUIDSMOOTH Kitkat V3.2 for Huawei Honor 6
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4] Unofficial LIQUIDSMOOTH Kitkat V3.2 for Huawei Honor 6. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Good news, another rom for H6 based on CM11 !
Please, could you say who are the extras of this ROM ?
Thanks for your work
In setting > General > LiquidSmooth.
There are more or less the same features as GravityBox with somes extras
ERROR
hello , i want to ask you , why my h60-L04 dont finish flashing the rom , its say error ... help me please .. thanks
I got some error while flashing the rom , i've tried to format data/cache .. but its still wont boot in this rom .. any solution please ?? thanks
Sent from my H60-L04 using XDA Free mobile app
Now i've found the way how to make the call works , just on the loudspeaker ... Huhuhu ..
Sent from my Honor 6 using XDA Free mobile app
Hello.
I have a problem.
I had setup the gesture lock. Which is insecure.
But suddenly the gesture is not recognising.
It is still a false lock because I can open notification drawer and open my phone.
Still. Anyway to get around this?
It automatically changed the gesture...
Update:- Got around it. For anyone who has this problem just install 'nolock' app from Play Store.
It still doesn't remove the lock. It comes back when rebooted.
Any long term solutions?
Sent from my Honor 6 using XDA Free mobile app
This package is for device h60_l04, this device is hwH60
Hello guyz,
I bought a Honor6 H60-L04 (from Amazon, confirmed on the box sticker).
I saw a tutorial referring to yours about the CM11 ROM and wanted to set it up as I did for all my devices. I unlocked the bootloader to get the PHONE Unlocked.
But I misunderstood I had to use a special CWM and installed CWM 6.0.5.0 and surely couldn't setup any wanted ROM. Then I tried to wipe everything including /system without backing up the stock ROM. So you guess...I'm a bit stuck now.
Then I read carefully the LiquidSmooth tutorial here. And tried for about 2 hours to get the L04 6.0.5.1 CWM using
Code:
sudo fastboot flash recovery cwm-6.0.5.1_20150218_h60_l04.img
&
Code:
sudo fastboot reboot
But it didn't make it. I got a bootloop nothing trying to get the recovery (vol+/- & power). I also tried the 20150212 one but got the same problem. The only CWM allowing me to get to the recovery is CWM 6.0.5.0.
Finally I wiped everything and setup the CWM 6.0.50 (the only one working) for a last try in installing LSmooth ROM. But now I got this message: This package is for device: h60_l04, H60_L04; this device is hwH60.
E:Error in /tmp/update.zip
Satus 7
Installation aborted.
So, I got a H60_L04, bootloader unlocked but nothing else. No even en stock ROM (I didn't manage to re install it).
Any kind help would be much appreciated,
Bud
Tried to flash RECOVERY and SYSTEM (dealing with http://forum.xda-developers.com/showpost.php?p=57271268&postcount=6), files extracted from H60-L04_V100R001C00B370 and I can't even reboot to CWM.
I feel lonely...
I understand the need to cut the Q&A from the official topic but this way nobody looks our problems. And we can get no help.
Not fair... Do we need to spam XDA to get 10 posts to get into the official thread?
---------- Post added at 08:00 PM ---------- Previous post was at 07:41 PM ----------
OK, using the EMUI 2.3 for H60-L01 and fastboot all the files I could get back to a working phone. But I ot the Huawei recovery and lost CWM 6.0.5.0.
Still looking for help to get SL ou CM11.
Thanks,
3rd post, spamming up to 10. To be able to post in the official topic to get some help.
Bud64 said:
3rd post, spamming up to 10. To be able to post in the official topic to get some help.
Click to expand...
Click to collapse
Download the latest recovery and ROM zip to your system,
fastboot flash recovery [full name of the recovery file inclulding extension]
Not boot into recovery and wipe system, cache and advanced/dalvik cache
Go to mounts and storage and format boot, system, cache and data and media on SD card (not sdcard 1)
Now install zip from sdcard1 and flash the ROM and flash the gapps.
Once done factory reset and clear cache and dalvik. Go on to mounts and storage and clear data and media on sd card and reboot.
There is no reason why it should not work
Thanks a lot!
I already did this.
Here's my new try:
Code:
[email protected] ~/dl $ sudo fastboot flash recovery cwm-6.0.5.1_20150212_h60_l04.img
target reported max download size of 471859200 bytes
sending 'recovery' (9654 KB)...
OKAY [ 1.005s]
writing 'recovery'...
OKAY [ 0.266s]
finished. total time: 1.271s
[email protected] ~/dl $ sudo fastboot reboot
rebooting...
finished. total time: 0.000s
Then I reboot to the ROM and I turn off the phone.
I use vol+/- & power button to reboot to CWM: as usual all I got is Honor powered by android - black screen - Honor powered by android - black screen - Honor powered by android - black screen - Honor powered by android - black screen - Honor powered by android...
I also tried with cwm-6.0.5.1_20150218_h60_l04.img, same prob.
The only working CWM (aka I can boot to) is 6.0.5.0. And I can't use it to get any CM based ROM for my H60 L04.
---------- Post added at 12:49 PM ---------- Previous post was at 12:11 PM ----------
I finally installed a dual boot with Windows 7 to use the Honor 6 multi tool (http://forum.xda-developers.com/honor-6/general/honor6-multi-tool-t2963060).
Even using this I couldn't boot into CWM for L04 (codeworkx). I had to tryu the exFAT CWM to be able to get into a CWM boot. I'll now try to setup the LiquidSmooth ROM using this recevovery.
---------- Post added at 12:56 PM ---------- Previous post was at 12:49 PM ----------
And... it failed as usually.
Code:
[email protected] ~/dl $ sudo adb sideload LS-KK-v3.2-2015-02-22-h60_l04.zip
[sudo] password for b:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
sending: 'sideload' 100%
On the phone:
Code:
installing update...
assert failed: getprop("ro.product.device") == "h60_l04" ||*getprop("ro.product.device") == "h60_l04" || getprop("ro.product.device") == "h60_l04"
E:Error in /tmp/update/zip
(Status 7)
Installation aborted.
So I guess I'm back to my starting point 2 days ago.
---------- Post added at 01:18 PM ---------- Previous post was at 12:56 PM ----------
Just tried TWRP too and I still can't boot to recovery.
I'm not sure what to do now. Maybe I'll try to burn it. Or play with a hammer, could be funy too.
...
I tried everything with this DOS tool.
I finally went to brick menu and installed stock recovery, flashed factory images, updated localy to B370 and I have now:
- unlocked bootloader,
- EMUI 3.0
Then I tried one more time to install a custom recovery. Failed for each CWM & TWRP, except CWM 6.0.5.0, as usual....
I'm bored with this. And still missing messages to post to the official thread... f!cking weird...
---------- Post added at 06:23 PM ---------- Previous post was at 06:16 PM ----------
Wow!
INstalling CWM 6.0.50 I could then upgrade to CWM 6.5.0.1 L04. Trying to go further with root & LS ROM...
---------- Post added at 07:14 PM ---------- Previous post was at 06:23 PM ----------
Ok, I could install LS ROM but got a bootloop with their logo (nice one). As for quite all other problems here, I'm sure I won't get helped. I'll try something else.
I could install LS ROM. But my phone is updating apps since about.... 2 hours.
Forgot to swipe after install.
#neversurrender
How to close the screen lock CRT animation? thx
great built! thanks!
great built indeed! but seems to experience some lagged on the recent button and it's transition.. any work around to solve it?
LS-KK-v3.2-2015-03-16-h60_l02.zip - 209.85 MB
Dual sim supprot?
Mobile data repair? @spanorg
what is the battery life like for liquidsmooth as PAC-man rom apparently drains the battery? thanks
---------- Post added at 10:20 AM ---------- Previous post was at 10:12 AM ----------
jiuzhang said:
LS-KK-v3.2-2015-03-16-h60_l02.zip - 209.85 MB
Dual sim supprot?
Mobile data repair? @spanorg
Click to expand...
Click to collapse
no the data for dual sim hasn't been fixed yet for CM11, so then LS won't have it either. but dual SIM should be supported haven't used this function so can't be 100% sure
Hey everyone.
I made this script a while back, and shared it on @dimm0k's thread: https://forum.xda-developers.com/v20/how-to/t-mobile-rooted-lgv20-rctd-root-t3661490
I figured I should probably make a thread for questions/feedback involving the usage of the script. I'm not a BASH expert by any means, and I did very minimal testing (just made sure it worked with everything where it should be). I'd like to hear about any bugs and such.
Right now, this only works on Linux, macOS and Windows 10 with BASH installed (WSL). It may work using Cygwin or Git BASH, but it's unlikely. If someone who knows Batch wants to make this for Windows, please do.
Link: https://www.androidfilehost.com/?fid=961840155545592450
App: https://labs.xda-developers.com/store/app/com.zacharee1.rctdremoverforlg
Any kernels I've modified using this script can be found here: https://www.androidfilehost.com/?w=files&flid=216688
Telegram thread (testing and discussion): https://t.me/joinchat/EkE57g6dCLopBy8xVQRT9w
HUGE thanks to @osm0sis and their work on Android Image Kitchen! Without that backend, this wouldn't be possible.
I will give this a shot this evening when I'm present at my casa.
Is it supposed to flash in TWRP? I got an error when I tried to flash this script. Thanks
@Zacharee1 Actually this wouldn't work on macOS / OSX because mkbootimg is a Linux ELF binary. A better solution would be to use abootimg which is included in most distributions (including WSL), and is available for macOS.
You could replace split_boot.pl and mkbootimg with:
abootimg -x boot.img // extracts kernel and initrd from boot.img
and
abootimg -u boot.img -r new-ramdisk.cpio.gz // This updates the existing boot.img with your modified initrd.
Just some thoughts
-- Brian
Unfortunately I dont have any of those OS.
Please help me modify this kernel https://forum.xda-developers.com/v20/development/h819-nrd90m-modded-stock-rom-t3503658
runningnak3d said:
@Zacharee1 Actually this wouldn't work on macOS / OSX because mkbootimg is a Linux ELF binary. A better solution would be to use abootimg which is included in most distributions (including WSL), and is available for macOS.
You could replace split_boot.pl and mkbootimg with:
abootimg -x boot.img // extracts kernel and initrd from boot.img
and
abootimg -u boot.img -r new-ramdisk.cpio.gz // This updates the existing boot.img with your modified initrd.
Just some thoughts
-- Brian
Click to expand...
Click to collapse
I was considering porting over to Android Image Kitchen, which looks like it's all in BASH. But it'll take some time that I don't have right now. Hopefully over the weekend...
netgar said:
Unfortunately I dont have any of those OS.
Please help me modify this kernel https://forum.xda-developers.com/v20/development/h819-nrd90m-modded-stock-rom-t3503658
Click to expand...
Click to collapse
https://www.androidfilehost.com/?w=files&flid=216688
Zacharee1 said:
https://www.androidfilehost.com/?w=files&flid=216688
Click to expand...
Click to collapse
Thank u so much Zacharee. Basically kernel intact, just rctd removed, right?
Zacharee1 said:
https://www.androidfilehost.com/?w=files&flid=216688
Click to expand...
Click to collapse
so i just flashed that boot image and now my phone wont boot. the screen just flickers. what can i do?
---------- Post added at 02:00 AM ---------- Previous post was at 01:55 AM ----------
i can get it to boot into the factory data reset screen
netgar said:
Thank u so much Zacharee. Basically kernel intact, just rctd removed, right?
Click to expand...
Click to collapse
Right.
Lgv20user said:
so i just flashed that boot image and now my phone wont boot. the screen just flickers. what can i do?
---------- Post added at 02:00 AM ---------- Previous post was at 01:55 AM ----------
i can get it to boot into the factory data reset screen
Click to expand...
Click to collapse
Confirm the factory reset prompts to get into TWRP. That kernel is for the H918, and has problems on other ROMs, since it includes some modified libraries, as well as a SuperSU ZIP. Unless you have NSS, I don't recommend flashing it.
im running nss but also megarom rom
im trying to reflash an old boot image but it keeps failing
damn
Lgv20user said:
im running nss but also megarom rom
im trying to reflash an old boot image but it keeps failing
damn
Click to expand...
Click to collapse
Failing in what way?
Lgv20user said:
im running nss but also megarom rom
im trying to reflash an old boot image but it keeps failing
damn
Click to expand...
Click to collapse
I thought u r using Tilde's ROM.
after i run fastboot flash boot boot.img
says sending 'boot' , okay, writing 'boot' and then failed <remote: unknown command>
---------- Post added at 02:29 AM ---------- Previous post was at 02:27 AM ----------
netgar said:
I thought u r using Tilde's ROM.
Click to expand...
Click to collapse
im on nss 6.5 and mega 4.0
Lgv20user said:
after i run fastboot flash boot boot.img
says sending 'boot' , okay, writing 'boot' and then failed <remote: unknown command>
---------- Post added at 02:29 AM ---------- Previous post was at 02:27 AM ----------
im on nss 6.5 and mega 4.0
Click to expand...
Click to collapse
Fastboot commands are crippled on the H918, aren't they? You have to use TWRP.
Zacharee1 said:
Fastboot commands are crippled on the H918, aren't they? You have to use TWRP.
Click to expand...
Click to collapse
okay im in twrp now, reflashed old boot image, still having the screen flicker after reboot.
reloading megarom 4.0 hopefully that will fix all
damn
---------- Post added at 02:45 AM ---------- Previous post was at 02:42 AM ----------
oh man thank goodness that worked. i was worried i would have to delete everything (so much to restore!)
learned a lot! haha
anyways so that boot image you uploaded earlier for netgar is only for that rom and that kernel correct?
a different rom and the same kernel would not work?
Lgv20user said:
okay im in twrp now, reflashed old boot image, still having the screen flicker after reboot.
reloading megarom 4.0 hopefully that will fix all
damn
---------- Post added at 02:45 AM ---------- Previous post was at 02:42 AM ----------
oh man thank goodness that worked. i was worried i would have to delete everything (so much to restore!)
learned a lot! haha
anyways so that boot image you uploaded earlier for netgar is only for that rom and that kernel correct?
a different rom and the same kernel would not work?
Click to expand...
Click to collapse
That's correct. For the NSS kernel, you either have to flash the entire ZIP (you can remove SuperSU if you want, but you'll have to flash your own SU), or not flash anything.
is there any way to create a boot image for this rom?
https://forum.xda-developers.com/v20/development/rom-natf-1-00-test-5-debloated-stock-t3509750
version 5.0 uses werewolf kernel
Lgv20user said:
okay im in twrp now, reflashed old boot image, still having the screen flicker after reboot.
reloading megarom 4.0 hopefully that will fix all
damn
---------- Post added at 02:45 AM ---------- Previous post was at 02:42 AM ----------
oh man thank goodness that worked. i was worried i would have to delete everything (so much to restore!)
learned a lot! haha
anyways so that boot image you uploaded earlier for netgar is only for that rom and that kernel correct?
a different rom and the same kernel would not work?
Click to expand...
Click to collapse
Im glad u made it...
Experimental twrp for moto one vision (need tester)
Requirements: Bootloader Unlocked
Before installing, test using "fastboot boot TWRP_Kane.img"
link: https://drive.google.com/file/d/1vhNiSuvB99j69wjNXoJn4dycpjUtKkTI/view?usp=drivesdk
I can test it this weekend
I wish I could try it right away, but I'm away from home over the weekend and I left my one vision at home.
can do, sir
---------- Post added at 01:02 PM ---------- Previous post was at 12:52 PM ----------
"Validation image failed"
Booting via fastboot failed.
I'm new to this, contact me any time if you need more info.
Alisson1397 said:
Experimental twrp for moto one vision (need tester)
Requirements: Bootloader Unlocked
Before installing, test using "fastboot boot TWRP_Kane.img"
link: https://drive.google.com/file/d/1vhNiSuvB99j69wjNXoJn4dycpjUtKkTI/view?usp=drivesdk
Click to expand...
Click to collapse
I tried it but I'm getting this error:
Sending 'boot.img' (36236 KB) OKAY [ 1.170s]
Booting FAILED (remote: '')
fastboot: error: Command failed
On bootloader screen it says "Validation image failed"
On adb screen says :
C:\Users\dml02\Downloads>fastboot boot TWRP_Kane.img
downloading 'boot.img'...
OKAY [ 0.825s]
booting...
FAILED (remote failure)
finished. total time: 0.991s
"Validation image failed" on my device.
If anyone knows how to fix the error, please help!
Alisson1397 said:
If anyone knows how to fix the error, please help!
Click to expand...
Click to collapse
sorry to ask mate. Are you the dev of this twrp image?
AndresOrue said:
sorry to ask mate. Are you the dev of this twrp image?
Click to expand...
Click to collapse
Yes, I compiled it, but found a device tree ready for twrp
I made a device tree for this device, successful kernel and twrp compilation, but still the same error as above.
Guys, is it worth the wait for working twrp for motorola one vision?
Tuldon said:
Guys, is it worth the wait for working twrp for motorola one vision?
Click to expand...
Click to collapse
I was near to buy one for developments, I didn't due to his price now is 274 euro was 240 but I arrived too late, it's too high for android one phone :/ .
Tuldon said:
Guys, is it worth the wait for working twrp for motorola one vision?
Click to expand...
Click to collapse
haky 86 said:
I was near to buy one for developments, I didn't due to his price now is 274 euro was 240 but I arrived too late, it's too high for android one phone :/ .
Click to expand...
Click to collapse
Yep, this phone is too expensive and a waste of time. I regret I bought it
I'm in the same situation with my Motorola One Action. I'm looking in both forums because they're almost the same phone (same SoC, different camera config and codename; Vision is Kane and Action is Troika).
I managed to get the stock firmware for my One Action XT2013-1, grabbed the boot.img, patched on Magisk, unlocked the Bootloader and tried to boot the patched image with the same error described in this post "Validation image failed" on device and "Failed" on fastboot.exe.
We need to bypass that validation so we can boot unsigned images on our phones. Sadly, I'm not a developer but will happily test any advance on my device.
Greetings.
From what I know "Validation image failed" error comes up if you haven't unlocked the bootloader or if the firmware you're trying to flash is older than your current firmware.
Did you enabled the "OEM unlocking" toggle from the developer settings? This might block the twrp installation.
@Alisson1397 also are you sure that the source code you're using for this twrp is for our particular device?
SnoopDoggyStyleDogg said:
From what I know "Validation image failed" error comes up if you haven't unlocked the bootloader or if the firmware you're trying to flash is older than your current firmware.
Did you enabled the "OEM unlocking" toggle from the developer settings? This might block the twrp installation.
@Alisson1397 also are you sure that the source code you're using for this twrp is for our particular device?
Click to expand...
Click to collapse
Use this device tree to compile TWRP
https://github.com/AlissonGrizotti/TWRP-device_motorola_kane
Maybe I'm using an outdated boot.img, but I find it unlikely
Is anyone aware of a LineageOS build for the Pixel 3a?
I am aware that it doesn't exist yet. Does that help?
edufur said:
I am aware that it doesn't exist yet. Does that help?
Click to expand...
Click to collapse
That answers it
Not Official (yet); however...
wijewkyoc4gu8krwf4igg said:
That answers it
Click to expand...
Click to collapse
While an official version of Lineage 17 is not available, the GSI/Treble version should work for the Pixel 3/3a/4 (including XL versions of all three), since all three lines are Treble-ready by design. (I have the GSI Lineage 17 image waiting to test over Bird Weekend.)
Here are my personal builds:
Pixel 3a: https://updater.invisiblek.org/sargo
Pixel 3a XL: https://updater.invisiblek.org/bonito
Notes:
On the bottom of the respective pages is a recovery you can fastboot boot in order to adb sideload the rom. These are auto-built on Sunday mornings in addition to when I decide I want a new build. The built in updater works and will pull and install my new builds seamlessly in android. Gapps are included (no I will not make builds without gapps, don't ask me). I really don't plan to support these, so dont PM/email me or anything about them. You're on your own. I run them on my personal device (bonito) so you can be pretty sure things will work fine. Make sure you've gone to official android 10 before trying to go to this as there are bootloader changes that you definitely need. Data wipe is needed, these are signed with my own private keys and will not be compatible with anyone else's builds.
I'll give these a test
invisiblek said:
Here are my personal builds:
Pixel 3a: https://updater.invisiblek.org/sargo
Pixel 3a XL: https://updater.invisiblek.org/bonito
Notes:
On the bottom of the respective pages is a recovery you can fastboot boot in order to adb sideload the rom. These are auto-built on Sunday mornings in addition to when I decide I want a new build. The built in updater works and will pull and install my new builds seamlessly in android. Gapps are included (no I will not make builds without gapps, don't ask me). I really don't plan to support these, so dont PM/email me or anything about them. You're on your own. I run them on my personal device (bonito) so you can be pretty sure things will work fine. Make sure you've gone to official android 10 before trying to go to this as there are bootloader changes that you definitely need. Data wipe is needed, these are signed with my own private keys and will not be compatible with anyone else's builds.
Click to expand...
Click to collapse
I'll test these, as I went back to the latest stock 10. The issue I had was with the latest stock 9 and TWRP; the combo refused to boot with Magisk 20 - so NOT fun).
invisiblek said:
Here are my personal builds:
Pixel 3a: https://updater.invisiblek.org/sargo
Pixel 3a XL: https://updater.invisiblek.org/bonito
Notes:
On the bottom of the respective pages is a recovery you can fastboot boot in order to adb sideload the rom. These are auto-built on Sunday mornings in addition to when I decide I want a new build. The built in updater works and will pull and install my new builds seamlessly in android. Gapps are included (no I will not make builds without gapps, don't ask me). I really don't plan to support these, so dont PM/email me or anything about them. You're on your own. I run them on my personal device (bonito) so you can be pretty sure things will work fine. Make sure you've gone to official android 10 before trying to go to this as there are bootloader changes that you definitely need. Data wipe is needed, these are signed with my own private keys and will not be compatible with anyone else's builds.
Click to expand...
Click to collapse
Is it correct to assume that there should be official builds once these are merged or is there anything still remaining?
PGHammer said:
I'll test these, as I went back to the latest stock 10. The issue I had was with the latest stock 9 and TWRP; the combo refused to boot with Magisk 20 - so NOT fun).
Click to expand...
Click to collapse
I got it working by extracting the boot.img from the lineageos zip file using payload_dumper and patching with magisk. Using the stock boot.img from google does not work properly(although it did kinda boot for me but without the touchscreen working).
Lightsword1942 said:
Is it correct to assume that there should be official builds once these are merged or is there anything still remaining?
Click to expand...
Click to collapse
No, because I have no intention of being an official maintainer anymore.
Lightsword1942 said:
I got it working by extracting the boot.img from the lineageos zip file using payload_dumper and patching with magisk. Using the stock boot.img from google does not work properly(although it did kinda boot for me but without the touchscreen working).
Click to expand...
Click to collapse
By the way, I upload the boot.img for each build as well. If you're in to doing all this magisk stuff you can always grab the boot.img for the rom by appending ".boot.img" to the end of the rom's download url. Saves you a step at least...
invisiblek said:
No, because I have no intention of being an official maintainer anymore.
Click to expand...
Click to collapse
Is that pretty difficult with the state of the LineageOS project right now for this device? I might be willing to give it a shot, I have a lot of embedded Linux experience(I maintain a number of buildroot packages) although not much on the android side.
Flashing Help
hi - i flashed the latest factory image on my phone.. and having issues trying to get this ROM installed.
I downloaded the Recovery image from your page and via 'Fasboot Mode' and getting the below error message.
I am able to get Magisk installed but getting the same message with phone being rooted. Am I doing something wrong?
C:\Users\xxx\Downloads\platform-tools_r29.0.5-windows\platform-tools>fastboot boot sargo-recovery-eng.img
Sending 'boot.img' (65536 KB) OKAY [ 1.521s]
Booting FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
fastboot: error: Command failed
invisiblek said:
Here are my personal builds:
Pixel 3a: https://updater.invisiblek.org/sargo
Pixel 3a XL: https://updater.invisiblek.org/bonito
Notes:
On the bottom of the respective pages is a recovery you can fastboot boot in order to adb sideload the rom. These are auto-built on Sunday mornings in addition to when I decide I want a new build. The built in updater works and will pull and install my new builds seamlessly in android. Gapps are included (no I will not make builds without gapps, don't ask me). I really don't plan to support these, so dont PM/email me or anything about them. You're on your own. I run them on my personal device (bonito) so you can be pretty sure things will work fine. Make sure you've gone to official android 10 before trying to go to this as there are bootloader changes that you definitely need. Data wipe is needed, these are signed with my own private keys and will not be compatible with anyone else's builds.
Click to expand...
Click to collapse
faheem5 said:
hi - i flashed the latest factory image on my phone.. and having issues trying to get this ROM installed.
I downloaded the Recovery image from your page and via 'Fasboot Mode' and getting the below error message.
I am able to get Magisk installed but getting the same message with phone being rooted. Am I doing something wrong?
C:\Users\xxx\Downloads\platform-tools_r29.0.5-windows\platform-tools>fastboot boot sargo-recovery-eng.img
Sending 'boot.img' (65536 KB) OKAY [ 1.521s]
Booting FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
fastboot: error: Command failed
Click to expand...
Click to collapse
I'm getting this same error when trying to boot the recovery.
I actually even tried unzipping the ROM zip, unloading payload.bin, and flashing the images manually. It says my device is not unlocked (it is..) when I get to the system IMG in fastbootd mode. So I don't know how people are getting these, or the recovery, to work. Can someone help me out? Thanks
My process to install it based on https://forum.xda-developers.com/es...lineageos-16-0-appears-to-live-t3939150/page7 and user 12paq for showing me the link.
1) Reboot to bootloader
2) sudo fastboot set_active a
3) sudo fastboot flash boot_a bonito-recovery-eng-3.img
4) Wipe data/factory reset
5) sudo adb sideload lineage-17.0-20191201-UNOFFICIAL-bonito.zip (this will only go to 47%, which I read is normal.)
6) reboot
I successfully installed the rom. thanks so much!
but is it possible to root for it??
sumsum0818 said:
I successfully installed the rom. thanks so much!
but is it possible to root for it??
Click to expand...
Click to collapse
Yes root is possible if you patch and flash the boot image
https://github.com/blekreleases/bon...-17.0-20191208-UNOFFICIAL-bonito.zip.boot.img
---------- Post added at 11:43 AM ---------- Previous post was at 11:33 AM ----------
If anyone has Android Auto in their car, wireless preferred but try the wired. I tried to hook mine up and the phone froze. Tried several times but it works on Stock. On the latest 12-08 bonito.
Meowdib said:
Yes root is possible if you patch and flash the boot image
---------- Post added at 11:43 AM ---------- Previous post was at 11:33 AM ----------
If anyone has Android Auto in their car, wireless preferred but try the wired. I tried to hook mine up and the phone froze. Tried several times but it works on Stock. On the latest 12-08 bonito.
Click to expand...
Click to collapse
thanks for the great help:good:
WHen I flash boot recovery the recovery mode disappears and therefor no option to sideload rom???
---------- Post added at 10:53 PM ---------- Previous post was at 10:52 PM ----------
sumsum0818 said:
I successfully installed the rom. thanks so much!
but is it possible to root for it??
Click to expand...
Click to collapse
How did u get it to work>> still failing for me. If i flash recovery, then the recovery mode is not available anymore..no adb sideload is possible?
---------- Post added at 10:54 PM ---------- Previous post was at 10:53 PM ----------
sumsum0818 said:
I successfully installed the rom. thanks so much!
but is it possible to root for it??
Click to expand...
Click to collapse
How did u get it to work>> still failing for me. If i flash recovery, then the recovery mode is not available anymore..no adb sideload is possible?
oranget said:
WHen I flash boot recovery the recovery mode disappears and therefor no option to sideload rom???
---------- Post added at 10:53 PM ---------- Previous post was at 10:52 PM ----------
How did u get it to work>> still failing for me. If i flash recovery, then the recovery mode is not available anymore..no adb sideload is possible?
---------- Post added at 10:54 PM ---------- Previous post was at 10:53 PM ----------
How did u get it to work>> still failing for me. If i flash recovery, then the recovery mode is not available anymore..no adb sideload is possible?
Click to expand...
Click to collapse
i just flash boot the recovery image first, then erase user data, you can reboot to recovery mode
i thought you should try to boot from the stock november patch first as i failed when i boot from the december patch
Simple install/update instructions
These are the steps I used, which worked flawlessly (I'm on Sargo). Hopefully this simplifies the process for anyone who wants to use this or is having trouble.
Prerequisites:
ADB, Fastboot, and Drivers (https://forum.xda-developers.com/showthread.php?t=2588979)
LineageOS Rom and Recovery (https://forum.xda-developers.com/showpost.php?p=81048663&postcount=5)
Unlock phone:
Go to Settings > About Phone, then tap "Build Number" until it says you are a developer.
Next go to Settings > System > Developer Options and enable the option "OEM Unlocking".
Connect phone to pc, and boot into fastboot. (With the phone off hold Volume Down and Power buttons.)
From the windows console enter "fastboot oem unlock" and your phone will become unlocked.
Install Rom:
Connect phone to pc, and boot into fastboot. (With the phone off hold Volume Down and Power buttons.)
From the windows console enter "fastboot boot <recovery_filename>.img" and you will enter recovery.
From recovery choose "Apply Update from ADB" and in the windows console enter "adb sideload <rom_filename>.zip"
When it has completed choose "Reboot System Now" and the install will be complete.
Special thanks to invisiblek for making these builds available to us!