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!
Related
I have tried TWRP (twrp.me/devices/googlepixel.html) and the Unified Android Toolkit (skipsoft.net/download/uat-v156/) to root the Pixel I bought directly from Google. With TWRP, I cannot see the .zip I downloaded (the phone is encrypted and /sdcard/* are all gibberish names; I'm never prompted for a decrypting password when booting for recovery) and with the Toolkit I end up in a reboot loop (I've tried twice with the same results).
I'm surprised that the Toolkit thinks my build is "Verizon" (NDE63X). I'm not sure if that matters.
Thoughts? Pointers? Diagnostics? TIA.
go get the new alpah2 of twrp.
---------- Post added at 01:51 PM ---------- Previous post was at 01:48 PM ----------
Save v4 root on sd. Save alpha 2 img on desktop, and .zip on sd on phone. fastboot img, enter pin or pattern, then flash alpha2 zip. restart in recovery, flash v4 root. Done.
computercarl said:
go get the new alpah2 of twrp.
---------- Post added at 01:51 PM ---------- Previous post was at 01:48 PM ----------
Save v4 root on sd. Save alpha 2 img on desktop, and .zip on sd on phone. fastboot img, enter pin or pattern, then flash alpha2 zip. restart in recovery, flash v4 root. Done.
Click to expand...
Click to collapse
Thanks. That gets me further. I put twrp-pixel-installer-sailfish-3.0.2-0-alpha2.zip and SR3-SuperSU-v2.78-SR3-20161103171345.zip on the SD card. I booted with twrp-3.0.2-0-alpha2-fastboot-sailfish.img and I could see the zips. I installed alpha2.zip, reboooted, installed SuperSU, rebooted. I don't see SuperSU in my app list. I'm missing something. I'm not sure what you mean by "v4 root".
ChrisNelsonPE said:
Thanks. That gets me further. I put twrp-pixel-installer-sailfish-3.0.2-0-alpha2.zip and SR3-SuperSU-v2.78-SR3-20161103171345.zip on the SD card. I booted with twrp-3.0.2-0-alpha2-fastboot-sailfish.img and I could see the zips. I installed alpha2.zip, reboooted, installed SuperSU, rebooted. I don't see SuperSU in my app list. I'm missing something. I'm not sure what you mean by "v4 root".
Click to expand...
Click to collapse
Since you have to temp boot twrp, I just use adb sideload to flash the twrp and SuperSU zips.
I reflash stock boot img
Boot into twrp from fast boot
Sideload twrp zip
Reboot recovery
Sideload supersu sr4 zip
GeekMcLeod said:
Since you have to temp boot twrp, I just use adb sideload to flash the twrp and SuperSU zips.
...
Sideload supersu sr4 zip
Click to expand...
Click to collapse
I found download.chainfire.eu/1013/SuperSU/SR4-SuperSU-v2.78-SR4-20161115184928.zip. Trying that shortly.
ChrisNelsonPE said:
I found download.chainfire.eu/1013/SuperSU/SR4-SuperSU-v2.78-SR4-20161115184928.zip. Trying that shortly.
Click to expand...
Click to collapse
Just let me know if you need any help. I'd happily help you get your phone rooted.
GeekMcLeod said:
Just let me know if you need any help. I'd happily help you get your phone rooted.
Click to expand...
Click to collapse
SU4 did it for me.
And a shout out to the Helium app for moving my data, even without root. Best $5 I spent this year!
ChrisNelsonPE said:
SU4 did it for me.
And a shout out to the Helium app for moving my data, even without root. Best $5 I spent this year!
Click to expand...
Click to collapse
I'm curious, I think I have ADB set up correctly but I have never had any luck I. Using it before ( mainly because of ADB language and commands to do what I want to do). Is there a guide that tells people like myself what to type and where to put files? Man that would be nice .
quinejh said:
I'm curious, I think I have ADB set up correctly but I have never had any luck I. Using it before ( mainly because of ADB language and commands to do what I want to do). Is there a guide that tells people like myself what to type and where to put files? Man that would be nice .
Click to expand...
Click to collapse
I highly recommend that if you're going to be doing stuff like this to your phone you get familiar with ADB and fastboot otherwise you're just asking for trouble. Each of the threads on custom recovery and root have the links and instructions including commands, read everything twice since you're new to this and I mean everything.
Flash using TWRP. This will flash all files in the MCG24.251-5 update except for recovery.
New features in this update that I've noticed:
-Marshmallow, aged to perfection in Verizon's own servers. Only one major release version obsolete, and with outdated security patches!
-WiFi calling (woooooo! Those custom roms just got another carrier-specific, unportable feature to compete with)
-The command center widget has been replaced with the Droid Turbo 2 version
Get it here: https://mega.nz/#!G1xg1aYa!fm2hUL7hDDVaxTAj_iPbtY61P-8VrQEvoOJiVsDtdho
Here's the stock recovery image if you want it: https://mega.nz/#!r1wDQRCJ!KHbo_Q6L-WE_VyB1x8W4FbT6PrerPEyn9H1C6VUAyf8
Flashing this rom updates the bootloader to a version that can communicate with the kernel to tell SafetyNet that it is unlocked, causing it to fail. Fret not, however, as there are two options to fix this:
OPTION 1: Flash the SU4TL-49 bootloader using the following TWRP package: https://mega.nz/#!6logEaIQ!q8qPJw65Upt38Hxiu1JyxErmwbgL7CBzuGzzPC0C9pQ
OPTION 2: Flash this patch made by @bhb27: https://www.androidfilehost.com/?fid=745425885120696423
Wipe cache and dalvik/art cache after either of these options.
NOTE that these options only fix failures due to SafetyNet checking the bootloader status. It will still fail due to root, xposed and the like. There are no known consequences or side effects to either of these options, so just pick whichever one you feel like.
If you notice weird things after you flash this rom (long boots other than the first one which is supposed to be long, random reboots, etc.) try flashing the stock recovery image and factory resetting.
If you want root, flash this version of SuperSU first, then flash whatever newer version you want: https://download.chainfire.eu/751/SuperSU/
If you have trouble flashing this, try TWRP Mod 3 instead of Mod 4.
Ouch, you have almost full flash inside archive, with bootloader too... Who is the most brave, introduce yourself ))
+ mirror
I can confirm that it works on old bootloader.
I had SULT-49 5.1 installed before and I just flashed this via TWRP. I haven't taken the OTA. It works perfectly. Thank you.
PS: My bootloader now is moto-apq8084-70.95 (2016-06-29). Do you have same version after taking OTA?
Did you have to wipe the system, data and cache first like you would with a new ROM or just dirty flash it?
Sent from my XT1254 using Tapatalk
Thanks OP
rickyblaze13 said:
Did you have to wipe the system, data and cache first like you would with a new ROM or just dirty flash it?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
When in doubt, always wipe.
Hey everyone, what is your safetynet status with this rom? It's failing for me, and I can't figure out why.
rickyblaze13 said:
have to wipe the system, data and cache first
Click to expand...
Click to collapse
It works w/o, but, IMO, better wipe, than not. You don't need extra bugs, right )
It's completing setup now, I did a wipe after I backed up my phone. It's unlocked and rooted before I flashed the zip
Sent from my QMV7A using Tapatalk
Can we get this ULed to Dropbox or Google Drive? The Mega link and the mirror are taking forever...
Crowick said:
Can we get this ULed to Dropbox or Google Drive? The Mega link and the mirror are taking forever...
Click to expand...
Click to collapse
My google drive is full and I don't have Dropbox. But if you wanted to mirror it, I will gladly add the link to the OP.
Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg
Crowick said:
Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg
Click to expand...
Click to collapse
thanks for gdrive mirror
Crowick said:
Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg
Click to expand...
Click to collapse
I don't. I don't know how I would get it since I need root access to get it, and I can't get root access without TWRP, and I have to overwrite the stock recovery to get TWRP.
TheSt33v said:
I have to overwrite the stock recovery to get TWRP.
Click to expand...
Click to collapse
fastboot boot TWRP.img
s5610 said:
fastboot boot TWRP.img
Click to expand...
Click to collapse
Nice! Good call.
https://mega.nz/#!r1wDQRCJ!KHbo_Q6L-WE_VyB1x8W4FbT6PrerPEyn9H1C6VUAyf8
Is anyone else having exceptionally long reboot/start times for their phone after flashing this rom?
Just the first boot after flashing
Sent from my XT1254 using Tapatalk
Thanks for that! Did anybody try to install it right over SU4TL-44? Just in case, I'm rooted, using xposed and twrp.
TheSt33v said:
Hey everyone, what is your safetynet status with this rom? It's failing for me, and I can't figure out why.
Click to expand...
Click to collapse
Perhaps this:
https://www.xda-developers.com/android-safetynet-now-reportedly-tripped-by-unlocked-bootloaders/
I just tried using AP a few hours ago and it failed with the screen in the article. OTA with unlocked bootloader.
I have a Google version Pixel 2 and have unlocked the bootloader (unlocked/relocked multiple times) and cannot flash any bootloader. I have tried flashing the "production" BL and the Dev Preview BL. I get the same error each time.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38728 KB)...
OKAY [ 0.110s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.125s
I have tried using the fastboot flashing unlock and fastboot flashing unlock_critical commands. I have relocked the BL then booted into the OS and used ADB to reboot to the BL, I still get the same error. I have tried changing the active slot to with no change.. I have tried the google version of platform tools, minimal adb, and another adb version I had from previous phones. I have downloaded the latest drivers from google no change.. I can flash and format other partitions, just not the BL (although I haven't tried format/erase bootloader, and I don't plan to)
I have tried different USB C cables, Google OEM, Samsung OEM, AUKEY .. different USB ports, different computers (although both with Windows 10 64bit).
Any suggestions?
lazarus2297 said:
I have a Google version Pixel 2 and have unlocked the bootloader (unlocked/relocked multiple times) and cannot flash any bootloader. I have tried flashing the "production" BL and the Dev Preview BL. I get the same error each time.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38728 KB)...
OKAY [ 0.110s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.125s
I have tried using the fastboot flashing unlock and fastboot flashing unlock_critical commands. I have relocked the BL then booted into the OS and used ADB to reboot to the BL, I still get the same error. I have tried changing the active slot to with no change.. I have tried the google version of platform tools, minimal adb, and another adb version I had from previous phones. I have downloaded the latest drivers from google no change.. I can flash and format other partitions, just not the BL (although I haven't tried format/erase bootloader, and I don't plan to)
I have tried different USB C cables, Google OEM, Samsung OEM, AUKEY .. different USB ports, different computers (although both with Windows 10 64bit).
Any suggestions?
Click to expand...
Click to collapse
Your not the only one there are others that have had similar issues, though i don't know the fix.
There is a script somewhere on another thread that might help. I will link.
---------- Post added at 05:19 AM ---------- Previous post was at 05:18 AM ----------
Hey you go.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Hopefully something in that will help
Just to be clear, are you using the latest fastboot? That's often an issue.
Some have had trouble with computers with usb-c ports. Have you tried a computer with usb-a and, of course, a usb-a to usb-c cable.
razrlover said:
Your not the only one there are others that have had similar issues, though i don't know the fix.
There is a script somewhere on another thread that might help. I will link.
---------- Post added at 05:19 AM ---------- Previous post was at 05:18 AM ----------
Hey you go.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Hopefully something in that will help
Click to expand...
Click to collapse
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
foosion said:
Just to be clear, are you using the latest fastboot? That's often an issue.
Some have had trouble with computers with usb-c ports. Have you tried a computer with usb-a and, of course, a usb-a to usb-c cable.
Click to expand...
Click to collapse
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..
lazarus2297 said:
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..
Click to expand...
Click to collapse
I'm not sure if this question will help, are you flashing the bootloader into the correct slot? I had issue early on with this and found that I needed to direct the flash to the correct slot. Just a thought
phonefreedom said:
I'm not sure if this question will help, are you flashing the bootloader into the correct slot? I had issue early on with this and found that I needed to direct the flash to the correct slot. Just a thought
Click to expand...
Click to collapse
Not exactly sure but I have tried changing the active slot to a or b.
I am using the command Fastboot flash bootloader "filename.img" (no quotations) I don't know how I would tell it to flash a specific slot other than whatever is the current active slot..
lazarus2297 said:
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..
Click to expand...
Click to collapse
lazarus2297 said:
Not exactly sure but I have tried changing the active slot to a or b.
I am using the command Fastboot flash bootloader "filename.img" (no quotations) I don't know how I would tell it to flash a specific slot other than whatever is the current active slot..
Click to expand...
Click to collapse
+Natahranta had shared the following with me and I hope it helps in your case...
"Download factory image from Google, unpack it, insidebis another zip, there is boot.img file
Flash it to both slots A and B. It must be the same version/update your phone was on.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
If you're not sure which exactly stock rom build your phone is on, use the flash_all.bat to flash the whole image on your phone, to be sure you have no mismatch between system and boot. Just remove "-w" from the bat file so it doesn't erase your user data"
So i got it working here is what I did..
I used the factory image to flash back 100% stock and relocked the bootloader, I then signed my device up for the Dev Preview, and surprisingly I got the notification to install DP pretty quickly. After DP installed I rebooted into the bootloader and noticed that my bootloader version had changed to the DP BL version. I then unlocked with the standard Fastboot Flashing Unlock command and unlocked the bootloader. After the phone rebooted I shut it down and booted into the BL and flashed the stock BL (a downgrade) it was successful, so i flashed the DP BL version and it was successful as well. Rebooted normally into the OS and all is well.
Hopefully this will help anyone else having the same problem.
lazarus2297 said:
I have relocked the BL then booted into the OS
Click to expand...
Click to collapse
I don't have any suggestions for your issue. But don't relock it, ever. You are playing with fire, if it goes bad and it's locked you are done.
lazarus2297 said:
So i got it working here is what I did..
I used the factory image to flash back 100% stock and relocked the bootloader, I then signed my device up for the Dev Preview, and surprisingly I got the notification to install DP pretty quickly. After DP installed I rebooted into the bootloader and noticed that my bootloader version had changed to the DP BL version. I then unlocked with the standard Fastboot Flashing Unlock command and unlocked the bootloader. After the phone rebooted I shut it down and booted into the BL and flashed the stock BL (a downgrade) it was successful, so i flashed the DP BL version and it was successful as well. Rebooted normally into the OS and all is well.
Hopefully this will help anyone else having the same problem.
Click to expand...
Click to collapse
I had this problem and created a thread about it a month ago: https://forum.xda-developers.com/pixel-2/help/failed-remote-command-flash-error-t3701929. A couple other people in that thread are now also reporting the problem.
No one seemed to know what the " FAILED (remote: Command Flash Error)" means. I never figured it out.
At the time of the November update, however, I was able to sideload OTA images with adb without problem. I assume that the OTA method also updates the bootloader, like the Dev Preview did for you. I couldn't tell with the November update, though, because it had the same version of the bootloader in it as the one that shipped with the phone.
So I'm wondering if simply sideloading the current December OTA image with adb would accomplish the same thing you did, without having to lock the bootloader, unlock it again, and go through the pain of wiping the device. I wonder if there was just something weird about the original version of the bootloader. Weirdness like this was discussed early on with the Pixel 2 in this XDA article: https://www.xda-developers.com/pixel-2-failing-flash-factory-images/ If I'm right, then once one sideloads the December OTA image and gets a new bootloader, there may not be an issue flashing bootloaders with fastboot in the future. I assume that the Dev Preview also used the OTA method to update the device.
In other words, I'm wondering if the step of unlocking and relocking the bootloader was not necessary. You just had to do it to get the Developer Preview (right?).
Just guessing here. I haven't had time yet to try this.
Okay, I tried my idea above and I was correct. Simplying sideloading the December OTA image updates the bootloader. After that the problem is solved. I can successfully flash the bootloader .img file directly (from the factory image zip) using fastboot. So I assume going forward there should not be any problems flashing factory images, instead of sideloading OTA images.
This solution also avoids having to lock and unlock the bootloader and wipe the whole device in the process.
cb474 said:
Simplying sideloading the December OTA image updates the bootloader.
Click to expand...
Click to collapse
My problem is that I have TWRP installed and it won't sideload nor flash the OTA file. I am trying to figure out how to flash the factory recovery. Unlike the factory images of before, there is no obvious recovery image in the zip.
-----------
Nevermind. I figured out that recovery is part of boot now. I flashed the factory boot and flashing OTA now.
snovvman said:
My problem is that I have TWRP installed and it won't sideload nor flash the OTA file. I am trying to figure out how to flash the factory recovery. Unlike the factory images of before, there is no obvious recovery image in the zip.
Click to expand...
Click to collapse
I'm not really sure how to solve that problem. Perhaps you should ask in the TWRP thread. I thought that when you install TWRP it backs up the recovery and has a way to restore it. But I could be wrong about that. You're correct that the recovery image does not seem to be included in the factory image zip like it used to be. I have seen other people mention that.
cb474 said:
I'm not really sure how to solve that problem. Perhaps you should ask in the TWRP thread. I thought that when you install TWRP it backs up the recovery and has a way to restore it. But I could be wrong about that. You're correct that the recovery image does not seem to be included in the factory image zip like it used to be. I have seen other people mention that.
Click to expand...
Click to collapse
Thanks for replying. Silly me, I was thinking the old way of doing business, where the recovery had its own image/partition. I figured out that recovery is part of boot, so I flashed boot and got the factory recovery back. I'm on 8.1 now.
snovvman said:
Thanks for replying. Silly me, I was thinking the old way of doing business, where the recovery had its own image/partition. I figured out that recovery is part of boot, so I flashed boot and got the factory recovery back. I'm on 8.1 now.
Click to expand...
Click to collapse
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.
cb474 said:
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.
Click to expand...
Click to collapse
So you know, TWRP for the first gen Pixels never left beta. They worked well enough... For Pixel 2s, I use the current beta for backups and they are handy for certain things. For now I am booting to TWRP to flash Magisk. For me, it is more convenient than patching.
cb474 said:
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php
kendong2 said:
https://forum.xda-developers.com/showpost.php
Click to expand...
Click to collapse
That link leads to nothing.
---------- Post added at 01:13 AM ---------- Previous post was at 01:11 AM ----------
snovvman said:
So you know, TWRP for the first gen Pixels never left beta. They worked well enough... For Pixel 2s, I use the current beta for backups and they are handy for certain things. For now I am booting to TWRP to flash Magisk. For me, it is more convenient than patching.
Click to expand...
Click to collapse
Yeah, I saw that. I'm just hoping with what was learned from the original Pixel and given that supposedly most phones will eventually use the A/B partition scheme that maybe TWRP will advance further on the Pixel 2. I really miss nandroid backups. I miss LineageOS too. Everything was so much simpler on my old Nexus 4. And I wasn't constantly feeling like I was going to brick my device every time I tried to do something.
cb474 said:
That link leads to nothing.
Click to expand...
Click to collapse
Sorry, did that on the phone. Was supposed to go here: https://forum.xda-developers.com/showpost.php?p=74704694&postcount=155
TWRP 3.2.0.0 final release (as I understand it) has been announced a few days ago. Don't know why the thread title still says beta.
This is freaking weird. Anyway, followed post #11 to sideload DEC OTA zip in stock recovery, and now finally I have a bootloader that is 0066 on both slot a and b. Thanked @cb474 !
Hello,
i need your help with my htc u 12+., please (
What happened
While I was happily using the phone a pop up from Magisk manager showed up, asking if I wanted to update. I said ok.
Magisk manager updated. Then it asked to update Magisk itself to 17.1. Checked on XDA if it was stable. It was. I chose the suggested method and tapped ok.
Here's where the nightmare begins. The installation seemed successful but the phone couldn't boot properly. The HTC animation stopped suddenly on the three green dots and the phone didn't react at all. It was not really a bootloop, it was like it couldn't boot any more.
What I did
Tried not to freak out and managed to boot into bootloader and then recovery. Tried to uninstall magisk through the magisk uninstaller, couldn't do it.
I didn't know if I could install Magisk 16.0 over a newer version, and I preferred not to try by luck. So I decided to restore a previous NAND Back up I had made. The NAND backup could restore everything but the /vendor partition.
Now, the phone successfully reboots but:
- I have no root (Magisk is gone)
- when I plug my USB cable, it only charges. No communication between the phone and the PC, unless I boot into bootloader (then the connection is there again and I can use fastboot commands). When I go to Developer options, no matter what communication protocol I choose for USB, it sticks to "Charge". Debug USB is ON, of course.
Tried to install Magisk again through a temporary TWRP, but the issue is still there: I can't mount /vendor partition and it fails.
I've looked for a solution here and there; what I found out is that I should use a treble-enabled TWRP, but my limited knowledge doesn't help me with that.
Please could you help me? It's crazy how messy can be just tapping ok on a notification :crying:
EDIT - FIXED:
To restore the USB communication, flashing the RUU solved the problem.
Using the patched boot.img method to install Magisk could succesfully work around the /vendor issue.
Huge thanks to the guys who helped, that was essential.
Easy fix. Flash the RUU and be on your marry way.
Thatll flash EVERYTHING back to stock. Then restore your data via TWRP that you had saved on a USB or microsdcard.
I also updated to the latest magisk, but everything is working just fine for me. (64Gig US unlocked version)
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
https://www.htc.com/us/support/updates.aspx
I had the same issue this morning and finally figured it out. Just use the new uninstaller from the magisk thread. Once you flash that in twrp you will be able to install the new magisk without any problems!
MNoisy said:
I had the same issue this morning and finally figured it out. Just use the new uninstaller from the magisk thread. Once you flash that in twrp you will be able to install the new magisk without any problems!
Click to expand...
Click to collapse
Unfortunately, the new uninstaller is the one that doesn't work for me due to the /vendor partition, that my TWRP is not able to mount..
Tachi91 said:
Easy fix. Flash the RUU and be on your marry way.
Thatll flash EVERYTHING back to stock. Then restore your data via TWRP that you had saved on a USB or microsdcard.
I also updated to the latest magisk, but everything is working just fine for me. (64Gig US unlocked version)
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
https://www.htc.com/us/support/updates.aspx
Click to expand...
Click to collapse
Thank you, maybe this one will help me.
Should I check something before trying ? (like CID.. or.. something else?)
And can I launch the RUU when I'm in bootloader mode? It's the only way I have to make the PC recognize the device.
EDIT: trying to launch the RUU, but after a few clicks it closes.. maybe my PC can't find a device, even in bootloader mode, and the software is shut down.
Tachi91 said:
Easy fix. Flash the RUU and be on your marry way.
Thatll flash EVERYTHING back to stock. Then restore your data via TWRP that you had saved on a USB or microsdcard.
I also updated to the latest magisk, but everything is working just fine for me. (64Gig US unlocked version)
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
https://www.htc.com/us/support/updates.aspx
Click to expand...
Click to collapse
[canceled]
sbiricuda said:
Unfortunately, the new uninstaller is the one that doesn't work for me due to the /vendor partition, that my TWRP is not able to mount..
Click to expand...
Click to collapse
I was having the same issue with error 2 and 255 (Maybe 225?) with the vendor mount problem. I think I rebooted/changed from slot a to slot b then back again. Then I was able to run uninstaller and the new installer. System and vendor were both unchecked and automatically mounted with the magisk script during the new install.
I actually recommend flashing the stock boot image before you do any of this to. You should not have to RUU. I had the identical problems today.
MNoisy said:
I was having the same issue with error 2 and 255 (Maybe 225?) with the vendor mount problem. I think I rebooted/changed from slot a to slot b then back again. Then I was able to run uninstaller and the new installer. System and vendor were both unchecked and automatically mounted with the magisk script during the new install.
I actually recommend flashing the stock boot image before you do any of this to. You should not have to RUU. I had the identical problems today.
Click to expand...
Click to collapse
So basically I should give:
fastboot --set-active=a
fastboot --set-active=b
(or vice versa if i'm on A)
right?
And where can i get the stock boot? The NAND-restore restored the /boot I had just after unlocking the bootloader, it's a very early nand-backup. Should I still flash the stock boot image?
Anyway, if only I could connect my phone stuck on "just charge" USB option, I wouldn't mind to RUU and start over again. The phone only has two days, it won't take long to set it up again.
sbiricuda said:
So basically I should give:
fastboot --set-active=a
fastboot --set-active=b
(or vice versa if i'm on A)
right?
And where can i get the stock boot? The NAND-restore restored the /boot I had just after unlocking the bootloader, it's a very early nand-backup. Should I still flash the stock boot image?
Anyway, if only I could connect my phone stuck on "just charge" USB option, I wouldn't mind to RUU and start over again. The phone only has two days, it won't take long to set it up again.
Click to expand...
Click to collapse
I did mine through a temporary boot of twrp
Stock boot images can be found in the spreadsheet linked in the second post of the image/firmware/boot/OTA thread here
Boot to download mode
temporary boot twrp
install stock boot image only (From thread linked above)
After the boot image is installed, to be safe, you might want to reboot again to download mode and then temporary boot twrp again just to ensure the boot image installation completed fully and is recognized (Just a guess based on my experience)
Now that you are back in twrp with the stock boot image installed, run the new magisk uninstaller (You should not need to worry about mounting anything since the magisk script does it automatically if not mounted)
Once uninstaller is complete, install the new magisk 17.1 through twrp and you should be good to go.
If you have issues with errors, try the process again. If still having issues, use the reboot menu in TWRP to switch slots back and forth and then try again.
It took me a good 30 min to find the combination that worked but it consisted of the steps above. 7 minutes of it was trying to get the damn phone to stop boot looping but my finger kept double tapping or screwing up the pressure to hold down power!
MNoisy said:
I did mine through a temporary boot of twrp
Stock boot images can be found in the spreadsheet linked in the second post of the image/firmware/boot/OTA thread here
Boot to download mode
temporary boot twrp
install stock boot image only (From thread linked above)
After the boot image is installed, to be safe, you might want to reboot again to download mode and then temporary boot twrp again just to ensure the boot image installation completed fully and is recognized (Just a guess based on my experience)
Now that you are back in twrp with the stock boot image installed, run the new magisk uninstaller (You should not need to worry about mounting anything since the magisk script does it automatically if not mounted)
Once uninstaller is complete, install the new magisk 17.1 through twrp and you should be good to go.
If you have issues with errors, try the process again. If still having issues, use the reboot menu in TWRP to switch slots back and forth and then try again.
It took me a good 30 min to find the combination that worked but it consisted of the steps above. 7 minutes of it was trying to get the damn phone to stop boot looping but my finger kept double tapping or screwing up the pressure to hold down power!
Click to expand...
Click to collapse
Seems that I have no luck. The provided boot.img in the spreadsheet is for US unlocked variant, while I have the european version. Maybe it's the same, but the point is that when I open the AFH page to download, it says "for HTC U11".
Did you try extracting the boot image from the RUU that corresponds your current firmware version? The needed decryption tool is linked in the same thread in which you found the spreadsheet.
Flashing a US RUU on a European phone without S-OFF isn't possible, btw. That's why you faced those errors, earlier.
Sent from my HTC U12+ using XDA Labs
The U11 is just a typo, it is the right stuff. You have a couple options since there is no signed stock boot available on the spreadsheet. Simply download the RUU and decrypt the payload using the instructions in the OP of the post I already provided or go to here and find yours (It is there, I checked )
Tachi91 said:
Easy fix. Flash the RUU and be on your marry way.
Thatll flash EVERYTHING back to stock. Then restore your data via TWRP that you had saved on a USB or microsdcard.
I also updated to the latest magisk, but everything is working just fine for me. (64Gig US unlocked version)
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
https://www.htc.com/us/support/updates.aspx
Click to expand...
Click to collapse
Good news and bad news.
The good news is that I managed to flash the RUU through TWRP. That flashed everything to stock, as you said.
This is particularly good because it also fixed the USB problem.
I have now a working stock device.
The bad news is: I can't flash Magisk any more.
I did just the same I did two days ago, when everything worked perfectly.
This time I keep getting the same error (photo: https://s8.postimg.cc/b6plbphx1/20180902_182259.jpg).
If I try to restore a NAND back up, I always get the /vendor error and I can't restore. The device then bootloops (meaning that I have to flash the RUU again to make it work).
So the main problem is now this one:
how can I deal with this /vendor error and install Magisk?
Thank you (to Mnoisy as well, of course, for his help in the previous post!).
sbiricuda said:
Good news and bad news.
The good news is that I managed to flash the RUU through TWRP. That flashed everything to stock, as you said.
This is particularly good because it also fixed the USB problem.
I have now a working stock device.
The bad news is: I can't flash Magisk any more.
I did just the same I did two days ago, when everything worked perfectly.
This time I keep getting the same error (photo: https://s8.postimg.cc/b6plbphx1/20180902_182259.jpg).
If I try to restore a NAND back up, I always get the /vendor error and I can't restore. The device then bootloops (meaning that I have to flash the RUU again to make it work).
So the main problem is now this one:
how can I deal with this /vendor error and install Magisk?
Thank you (to Mnoisy as well, of course, for his help in the previous post!).
Click to expand...
Click to collapse
Have you tried switching to slot A in TWRP? Since it can't mount /system_B maybe it'll mount system A?
Flippy498 said:
Did you try extracting the boot image from the RUU that corresponds your current firmware version? The needed decryption tool is linked in the same thread in which you found the spreadsheet.
Flashing a US RUU on a European phone without S-OFF isn't possible, btw. That's why you faced those errors, earlier.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Since I was facing USB issues (no communication via USB betwenn the device and the PC), I flashed the whole RUU. I'm now completely stock 1.21.
As I mentioned, the problem is now that I can't root again.
Tachi91 said:
Have you tried switching to slot A in TWRP? Since it can't mount /system_B maybe it'll mount system A?
Click to expand...
Click to collapse
I have read that this is very dangerous, and in fact I have no clue about what the consequences may be.
Do you suggest to switch to slot A and flash magisk?
You might want to try going through my steps to ensure you have a stock signed boot image on there and proceed through the steps listed.
sbiricuda said:
I have read that this is very dangerous, and in fact I have no clue about what the consequences may be.
Do you suggest to switch to slot A and flash magisk?
Click to expand...
Click to collapse
It's not dangerous. You'll get stuck on a bootloop since more often than not most phones don't have anything on there. If you did have an OTA you end up on the older system. Which would cause issues since your data partition would be cached to newer software.
Either way you have an RUU that will fix the phone. S-OFF isn't permanent and I'm assuming you don't have it. With S-ON the odds of a bricking is minimal.
MNoisy said:
You might want to try going through my steps to ensure you have a stock signed boot image on there and proceed through the steps listed.
Click to expand...
Click to collapse
I'm not sure TWRP does a good job since RUU when done correctly puts the phone in OEM RUU mode. TWRP possibly doesn't flash all the partitions since it might not have access to them. I'm surprised the zip worked in TWRP.
Full RUU zip is about 2gigs. (Single Sim)
MNoisy said:
You might want to try going through my steps to ensure you have a stock signed boot image on there and proceed through the steps listed.
Click to expand...
Click to collapse
Tachi91 said:
It's not dangerous. You'll get stuck on a bootloop since more often than not most phones don't have anything on there. If you did have an OTA you end up on the older system. Which would cause issues since your data partition would be cached to newer software.
Either way you have an RUU that will fix the phone. S-OFF isn't permanent and I'm assuming you don't have it. With S-ON the odds of a bricking is minimal.
I'm not sure TWRP does a good job since RUU when done correctly puts the phone in OEM RUU mode. TWRP possibly doesn't flash all the partitions since it might not have access to them. I'm surprised the zip worked in TWRP.
Full RUU zip is about 2gigs. (Single Sim)
Click to expand...
Click to collapse
I have installed the RUU through TWRP. I had to use the 1.15 because the 1.21 gave me an error about the CID that was not coincident (but I'm sure I picked the right RUU in the spreadsheet, for my CID, the HTC__034).
So i restored the 1.15, and then installed the OTA update to 1.21. This is my current situation. And yes, I'm S-ON.
What I could do is either:
- I try to decrypt the boot.img from the RUU in the spreadsheet (but using the tool seems sooo complicated, I'm reading the thread over and over not understanding much), or
- I use the .exe version of the 1.21 RUU, from the HTC official website. If I do that, can we be sure that I have a signed boot.img? And can this work around the TWRP limits about partitions?
Oh, something I forgot to mention: I did try the switching trick MNoisy suggested (switching the slots and then switiching back), but it didn't work.
In case anyone of u ever needs to flash stock boot.img's to restore things,
The twrp telegram group kindly provided me with those backups, i just sorted them and made them available for download...
Currently I have all patches after 4.88 base so may to october security patch...
You can find all stock images here:
https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
and Magisk(v17.2) prerooted patched myself here:
https://cloud.vault81.de/s/AeHiE5HR2qonb3N
Mirror: (All Images)
https://mega.nz/#F!QQp1jQQZ!k5ejlU2NJyic0HusCa_IAQ
Nice job, i have been waiting for this for a long time. Thank you so much ??.
Trissi said:
In case anyone of u ever needs to flash stock boot.img's to restore things,
The twrp telegram group kindly provided me with those backups, i just sorted them and made them available for download...
You can find all stock images here:
https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
Magisk Prepatched Images will be added later...
Click to expand...
Click to collapse
Thanks sir
Greatttttt
Thank you for the img files. Unfortunately i have a problem. When i try to boot the October image with fastboot on A slot where my phone is updated to the october patch - it stucks on android logo. When i switch to B slot which is September patched and use the september img u provided - again the same thing. Any idea?
Mo4o293 said:
Thank you for the img files. Unfortunately i have a problem. When i try to boot the October image with fastboot on A slot where my phone is updated to the october patch - it stucks on android logo. When i switch to B slot which is September patched and use the september img u provided - again the same thing. Any idea?
Click to expand...
Click to collapse
Thats weird... what model do you have? , I thought they work on all Models...
On my device (TA-1012)[Single sim 128gb/6gb], I have exactly the same patches on a and b and both work like a charm with their specific images... Just redownloaded and tested it again...
To narrow down your problem further:
Did you flash anything else? Is your device booting normally when just rebooting? Root? Twrp?
Mo4o293 said:
Thank you for the img files. Unfortunately i have a problem. When i try to boot the October image with fastboot on A slot where my phone is updated to the october patch - it stucks on android logo. When i switch to B slot which is September patched and use the september img u provided - again the same thing. Any idea?
Click to expand...
Click to collapse
If you have another model and some time leftover I would greatly appreciate if you(and everyone else reading this with Another model):
1. could reflash the 4.88 Stock Image
2. Turn off automatic update
3.follow this Upgrade guide over and over again
https://forum.xda-developers.com/no...root-nokia-8-ability-to-t3848390/post77751877
4. Afterwards send me the stock_boot_(randomstuff).gz Magisk generates as Backups in the folder /data or (only viewable with root explorer) AND a screensho of the file creation dates so I know which is which...
I would then upload them and add them to the thread to help others with your model...
No worry's if you don't have time...
Trissi said:
Thats weird... what model do you have? , I thought they work on all Models...
On my device (TA-1012)[Single sim 128gb/6gb], I have exactly the same patches on a and b and both work like a charm with their specific images... Just redownloaded and tested it again...
To narrow down your problem further:
Did you flash anything else? Is your device booting normally when just rebooting? Root? Twrp?
Click to expand...
Click to collapse
Thanks for the replay! My device is TA-1012 [4/64]. I haven't flashed anything. I neither have TWRP or root. When rebooting it is showing the warning that my bootloader is unlocked (offical method). But i noticed something strange. Maybe you will laugh at me :laugh: but the thing is when i boot the phone and the warning pops up it says to press the power button to continue but that doesn't work. I have to wait to boot itself. In the other hand when i boot the stock images you provided the power button works and when i press it, the warning disappears and the android logo pops up. I dont know if this was helpful in some way but i wanted to mention it. Also i will post the backed up img soon that you wanted up there.
Ok so i came up with another idea. I forgot to mention that all these steps i did on Linux so i have Windows also and switched to see if the things are the same. When i enter in cmd, adb recognizes the device without problem. When i write adb reboot bootloader everything is fine. BUT when i write fastboot devices when my phone is in download mode , nothing happens. When i try something like fastboot reboot or fastboot boot xyz.img it says <Waiting for device>. I tried adb and fastboot installer but again nothing. I cannot find nokia drivers, but in OST LA there are 3, i installed them and again nothing. So what should i do?
Edit: It worked when i downloaded new version of adb and fastboot CLI but again - booting the oct img even in Windows cmd makes the phone stuck on android logo
Mo4o293 said:
Thanks for the replay! My device is TA-1012 [4/64]. I haven't flashed anything. I neither have TWRP or root. When rebooting it is showing the warning that my bootloader is unlocked (offical method). But i noticed something strange. Maybe you will laugh at me :laugh: but the thing is when i boot the phone and the warning pops up it says to press the power button to continue but that doesn't work. I have to wait to boot itself. In the other hand when i boot the stock images you provided the power button works and when i press it, the warning disappears and the android logo pops up. I dont know if this was helpful in some way but i wanted to mention it. Also i will post the backed up img soon that you wanted up there.
Click to expand...
Click to collapse
The Power Button stuff is exactly the same for me... Don't think thats the issue...
Really weird, would love to debug further but really have not much other ideas...
Did you try newest fastboot/adb binaries on windows too?
Do you have access to another pc to try it on?
Switched out cables/ports used?
Trissi said:
The Power Button stuff is exactly the same for me... Don't think thats the issue...
Really weird, would love to debug further but really have not much other ideas...
Did you try newest fastboot/adb binaries on windows too?
Do you have access to another pc to try it on?
Switched out cables/ports used?
Click to expand...
Click to collapse
I've switched ports, tried another pc even with different OS (win7). Downloaded the newest adb and fastboot binaries from Android Developers site - nothing. Also i ran a test in fastboot and its says:
bootloader unlocked: true
critical unlocked: false. But i dont think critical is necessary, isnt it?
Mo4o293 said:
I've switched ports, tried another pc even with different OS (win7). Downloaded the newest adb and fastboot binaries from Android Developers site - nothing. Also i ran a test in fastboot and its says:
bootloader unlocked: true
critical unlocked: false. But i dont think critical is necessary, isnt it?
Click to expand...
Click to collapse
If critical was never unlocked it can't have been modified(I think)
Really outta ideas here sorry mate...
Have you tryed booting the prerooted imgs?
Trissi said:
If critical was never unlocked it can't have been modified(I think)
Really outta ideas here sorry mate...
Have you tryed booting the prerooted imgs?
Click to expand...
Click to collapse
Yep the same thing
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
I think i should try to flash the stock firmware provided in the forum i think it was the June one. Maybe that will make my device able to flash your images
I have similar issues. I have ta-1012 4/64. When it was of september patch, no september image worked (modified or not), it stucks at "android powered" logo. This is the volatile booting which is performed by "fastboot boot" command.
I use a linux desktop. I tried the latest fastboot executable which came with android-studio and also the one on archlinux android-tools package. (they are a bit different) Results are same.
Now it has october patch. No success with october boot images, too
---------- Post added at 21:59 ---------- Previous post was at 21:53 ----------
Mo4o293 said:
Yep the same thing
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
I think i should try to flash the stock firmware provided in the forum i think it was the June one. Maybe that will make my device able to flash your images
Click to expand...
Click to collapse
I think you should wait for TWRP.
Dr. Slump said:
I have similar issues. I have ta-1012 4/64. When it was of september patch, no september image worked (modified or not), it stucks at "android powered" logo. This is the volatile booting which is performed by "fastboot boot" command.
I use a linux desktop. I tried the latest fastboot executable which came with android-studio and also the one on archlinux android-tools package. (they are a bit different) Results are same.
Now it has october patch. No success with october boot images, too
---------- Post added at 21:59 ---------- Previous post was at 21:53 ----------
I think you should wait for TWRP.
Click to expand...
Click to collapse
Yep. We are the black sheeps. Anyway i will definitely wait for TWRP because the other things are risky and thats my daily driver. BTW Im on Manjaro which is based on Arch.
Mo4o293 said:
think i should try to flash the stock firmware provided in the forum i think it was the June one. Maybe that will make my device able to flash your images
.
Click to expand...
Click to collapse
If you do happen to do that please remember this if you have Time....
If you have another model and some time leftover I would greatly appreciate if you(and everyone else reading this with Another model):
1. could reflash the 4.88 Stock Image
2. Turn off automatic update
3.follow this Upgrade guide over and over again
https://forum.xda-developers.com/no...root-nokia-8-ability-to-t3848390/post77751877
4. Afterwards send me the stock_boot_(randomstuff).gz Magisk generates as Backups in the folder /data or (only viewable with root explorer) AND a screensho of the file creation dates so I know which is which...
Click to expand...
Click to collapse
Trissi said:
In case anyone of u ever needs to flash stock boot.img's to restore things,
The twrp telegram group kindly provided me with those backups, i just sorted them and made them available for download...
Currently I have all patches after 4.88 base so may to october security patch...
You can find all stock images here:
https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
and Magisk(v17.2) prerooted patched myself here:
https://cloud.vault81.de/s/AeHiE5HR2qonb3N
Click to expand...
Click to collapse
You can download it on GoogleDrive? links do not open
Anatoly64RUS said:
You can download it on GoogleDrive? links do not open
Click to expand...
Click to collapse
Problem seems on your side
Anatoly64RUS said:
You can download it on GoogleDrive? links do not open
Click to expand...
Click to collapse
Works fine for me too...
I have A pretty restrictive https configuration on that server...
Do you use A massively outdated browser? If Not it should work...
Trissi said:
Works fine for me too...
I have A pretty restrictive https configuration on that server...
Do you use A massively outdated browser? If Not it should work...
Click to expand...
Click to collapse
Browsers are all updated, I'm just from Russia, so a big request to anyone is easy, upload to google drive