Related
Hey all, just got my 128GB VZW Pixel XL, unlocked the BL via dePixel8 and so far I love the phone, but cannot figure out why TWRP won't even boot for me to obtain root. I've now tried fastboot boot twrp.img with both TWRP RC1 and Alpha 2 .img's on NOF27B and cannot get TWRP to boot at all - I get a bootloop of sorts with TWRP's main screen rapidly flashing on and off, which persists until I do a hard reboot. This is also the case when I tried it on the Android O Dev Preview. Anyone know why this is happening or have a fix?
Did you download the latest platform tools directly from Google and then try again? They are available as a separate download now without needing to download the SDK. Don't use the minimal ones that were floating around
aholeinthewor1d said:
Did you download the latest platform tools directly from Google and then try again? They are available as a separate download now without needing to download the SDK. Don't use the minimal ones that were floating around
Click to expand...
Click to collapse
I'm fully updated on that front. Fastboot itself works just fine, it's specifically TWRP that won't boot at all.
EDIT: Sorry, on second thought FlashFire requires root, so what I posted wouldn't work. I don't remember this sort of thing being reported in the TWRP threads, so I might also try starting with a new install to see if the same thing happens.
StrizzMatik said:
I'm fully updated on that front. Fastboot itself works just fine, it's specifically TWRP that won't boot at all.
Click to expand...
Click to collapse
No idea but I'd it were me I'd start from scratch. Flash a factory image with fastboot so you are completely back to square 1. Go through initial setup and then enable a passcode in the settings. Then try TWRP again.
aholeinthewor1d said:
No idea but I'd it were me I'd start from scratch. Flash a factory image with fastboot so you are completely back to square 1. Go through initial setup and then enable a passcode in the settings. Then try TWRP again.
Click to expand...
Click to collapse
Updated my ADB / fastboot files and got it running no problem. Thanks again!
Sent from my Pixel XL using Tapatalk
Anybody have any more ideas on this other than what is mentioned. I have the latest platform-tools installed and the latest adb. I've flashed the latest 8.0.0 factory image. I've got no PIN or password setup, but I've tried it with that as well. All I get every time I do "fastboot boot path/to/twrp.img" is the flash TWRP bootscreen, but it nevers loads up. If I go back to bootloader and choose recovery, I get the android no recovery installed screen. This is driving me nuts already!
sharkie405 said:
Anybody have any more ideas on this other than what is mentioned. I have the latest platform-tools installed and the latest adb. I've flashed the latest 8.0.0 factory image. I've got no PIN or password setup, but I've tried it with that as well. All I get every time I do "fastboot boot path/to/twrp.img" is the flash TWRP bootscreen, but it nevers loads up. If I go back to bootloader and choose recovery, I get the android no recovery installed screen. This is driving me nuts already!
Click to expand...
Click to collapse
Have you tried:
1. setting up pin
2. Putting TWRP.img in the platform-tools folder
3. opening command prompt
4. Fastboot boot TWRP.img
Homeboy76 said:
Have you tried:
1. setting up pin
2. Putting TWRP.img in the platform-tools folder
3. opening command prompt
4. Fastboot boot TWRP.img
Click to expand...
Click to collapse
Having the same issues I've unlocked already but I can't get it to boot the twrp.img. I've set a PIN already, and updated sdk with no dice. It just flashes the twrp startup screen over and over. Found it I'm golden now.
UPDATE: Here you go if anyone gets stuck like I did:
https://forum.xda-developers.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896
StrizzMatik said:
Hey all, just got my 128GB VZW Pixel XL, unlocked the BL via dePixel8 and so far I love the phone, but cannot figure out why TWRP won't even boot for me to obtain root. I've now tried fastboot boot twrp.img with both TWRP RC1 and Alpha 2 .img's on NOF27B and cannot get TWRP to boot at all - I get a bootloop of sorts with TWRP's main screen rapidly flashing on and off, which persists until I do a hard reboot. This is also the case when I tried it on the Android O Dev Preview. Anyone know why this is happening or have a fix?
Click to expand...
Click to collapse
Are you using this TWRP: twrp-3-1-pixel-bootable-mod.img
Hello friends!
Alternatively, Try this: https://forum.xda-developers.com/lg-k10/how-to/mtk-lg-k10-2016-t3660872
Since DM-Verity is the only major hurdle for getting Custom ROMs to run on LG K10 MTK (2016) devices. I need all the boot images of K10 (2016) MTK models.
I will not be able to download each and every firmware file of MTK that's why I am requesting you just the boot image.
Here is one I had uploaded a year ago
https://github.com/berkantkz/misc/raw/master/boot_157696.bin
I believe our problem lays in the "lk" (bootloader) partition:
"Bootloader integrity is always verified using a hardware root of trust. For verifying boot and recovery partitions, the bootloader has a fixed OEM key available to it. It always attempts to verify the boot partition using the OEM key first and try other possible keys only if this verification fails."
https://source.android.com/security/verifiedboot/verified-boot
So i guess the bootloader has to be tweaked first to allow us modify the boot image/kernel so we can flash any custom rom.
This issue only exists on firmwares after the 2017 february patch dates. Before that patch date the boot verification is missing from the bootloader so we could flash any custom rom however each custom rom should be ported for the firmware (for the bootloader and recovery) thats on the phone already.
@Singular777 started building a custom rom that was the rigth direction i guess (since it only consisted of the boot and the system images):
https://forum.xda-developers.com/lg-k10/development/lineageos-13-0-k10-mtk-t3617227
it's just that is should be ported for each firmware just as the twrp...
gottlasz said:
I believe our problem lays in the "lk" (bootloader) partition:
"Bootloader integrity is always verified using a hardware root of trust. For verifying boot and recovery partitions, the bootloader has a fixed OEM key available to it. It always attempts to verify the boot partition using the OEM key first and try other possible keys only if this verification fails."
https://source.android.com/security/verifiedboot/verified-boot
So i guess the bootloader has to be tweaked first to allow us modify the boot image/kernel so we can flash any custom rom.
This issue only exists on firmwares after the 2017 february patch dates. Before that patch date the boot verification is missing from the bootloader so we could flash any custom rom however each custom rom should be ported for the firmware (for the bootloader and recovery) thats on the phone already.
@Singular777 started building a custom rom that was the rigth direction i guess (since it only consisted of the boot and the system images):
https://forum.xda-developers.com/lg-k10/development/lineageos-13-0-k10-mtk-t3617227
it's just that is should be ported for each firmware just as the twrp...
Click to expand...
Click to collapse
Then go on and do it...
What about to create a new custom key and flash it to /dev/block/[mtk-folders]/by-name/oemkeystore and then sign the all custom firmwares with this key. So that, it'd boot because the keys will match.
do you see any possibility pvineeth97?
berkantkz said:
What about to create a new custom key and flash it to /dev/block/[mtk-folders]/by-name/oemkeystore and then sign the all custom firmwares with this key. So that, it'd boot because the keys will match.
do you see any possibility pvineeth97?
Click to expand...
Click to collapse
Why do that when you can simply disable/turn off dm-verity ?
Professor Woland said:
Why do that when you can simply disable/turn off dm-verity ?
Click to expand...
Click to collapse
It's not that easy You must haven't read the post of @gottlasz
berkantkz said:
What about to create a new custom key and flash it to /dev/block/[mtk-folders]/by-name/oemkeystore and then sign the all custom firmwares with this key. So that, it'd boot because the keys will match.
do you see any possibility pvineeth97?
Click to expand...
Click to collapse
i hard bricked two k8's by flashing anything via fastboot... idk why but it's quite risky. Good idea anyways.
gottlasz said:
i hard bricked two k8's by flashing anything via fastboot... idk why but it's quite risky. Good idea anyways.
Click to expand...
Click to collapse
What did you flashed?
Professor Woland said:
What did you flashed?
Click to expand...
Click to collapse
First time i ereased recovery, boot, and system partitions via fastboot... -> hard brick (i expected download mode - which is on laf partition should have worked but no luck)
Second time i flashed lk partition (i modified it a little expecting getting rid of secure boot but got hard brick instead...)
No more tries on fastboot. I stick with twrp.
gottlasz said:
First time i ereased recovery, boot, and system partitions via fastboot... -> hard brick (i expected download mode - which is on laf partition should have worked but no luck)
Second time i flashed lk partition (i modified it a little expecting getting rid of secure boot but got hard brick instead...)
No more tries on fastboot. I stick with twrp.
Click to expand...
Click to collapse
I don't understand why it won't work in first case.
However I will not play with lk even if that is only way. My warranty won't cover that, actually it expires soon but I can't afford to kill the phone.
gottlasz said:
First time i ereased recovery, boot, and system partitions via fastboot... -> hard brick (i expected download mode - which is on laf partition should have worked but no luck)
Second time i flashed lk partition (i modified it a little expecting getting rid of secure boot but got hard brick instead...)
No more tries on fastboot. I stick with twrp.
Click to expand...
Click to collapse
You wouldn't have done the patching of lk partition properly or lk partition must have been signed.
I flashed whole stock rom 2016 on top of a 2017 system... got my phone's dead x_x but recovered it using circuit-bridge! (thread here) now's also soft bricked but at least recognized by PC but not by LGUP or Uppercut. idk what to do!
How can I get my boot image? IDK how.
Without fail, when running the latest twrp, I get an error when flashing different rom zips. It's always the same error during step 1 and sometimes during step 2. I am on slot A when flashing the room, by the way.
The error just says it can't flash, there is no error code or description or anything like that.
When I was able to flash a rom, I tried to reboot into B for the vendor image, but none of my files were viewable, only folders with numbers and letters.
I'm confused, and I'm not a noob. I came from the regular Pixel and I was able to flash no problem.
stevew84 said:
Without fail, when running the latest twrp, I get an error when flashing different rom zips. It's always the same error during step 1 and sometimes during step 2. I am on slot A when flashing the room, by the way.
The error just says it can't flash, there is no error code or description or anything like that.
When I was able to flash a rom, I tried to reboot into B for the vendor image, but none of my files were viewable, only folders with numbers and letters.
I'm confused, and I'm not a noob. I came from the regular Pixel and I was able to flash no problem.
Click to expand...
Click to collapse
Is this when you fastboot into twrp, or do you have twrp already installed? Have you tried disabling screen lock before you enter twrp? And I assume you've run both bootloader unlocking commands as well?
This is when using skipsoft.
Do I need to run the critical flashing command manually or something? The reason I ask is because I'm not sure skipsoft does that.
I'd love to be able to flash alll this stuff without even using twrp but I'm not sure that's possible.
So I boot twrp, wipe and flash the ROM. But it fails right there. Is there a step I'm missing?
I do know how to flash individual images thru fastboot by the way, like when going to stock. Here is where I did do the critical flash command.
No I haven't tried to disable screen lock.
stevew84 said:
This is when using skipsoft.
Do I need to run the critical flashing command manually or something? The reason I ask is because I'm not sure skipsoft does that.
I'd love to be able to flash alll this stuff without even using twrp but I'm not sure that's possible.
So I boot twrp, wipe and flash the ROM. But it fails right there. Is there a step I'm missing?
I do know how to flash individual images thru fastboot by the way, like when going to stock. Here is where I did do the critical flash command.
No I haven't tried to disable screen lock.
Click to expand...
Click to collapse
Typically you need to have fully unlocked the bootloader with these 2 commands...
fastboot flashing unlock
and.....
fastboot flashing unlock_critical
Especially the critical, or else you won't be able to flash any roms. I don't know if skipsoft will do this. I know the Deuces scrip will. To find out what is/isn't unlocked run.....fastboot getvar all....
Then you'll know. If you have to unlock critical, which I think you will, it'll wipe your phone completely. So backup your files and such before you do :good:
Any manual methods that work? I mean to flash the roms.
stevew84 said:
Any manual methods that work? I mean to flash the roms.
Click to expand...
Click to collapse
I believe there is, but I can't find what it is. I think it's adb push (name of file) or adb sideload through twrp, butI could be wrong. Either way, you first need to be sure your fully bootloader unlocked before you can flash anything.
Badger50 said:
I believe there is, but I can't find what it is. I think it's adb push (name of file) or adb sideload through twrp, butI could be wrong. Either way, you first need to be sure your fully bootloader unlocked before you can flash anything.
Click to expand...
Click to collapse
Ok I almost forgot.
When I first unlocked the phone I was able to flash Nitrogen, both the ROM and twrp. But when I rebooted recovery to get to slot B, all I saw were various numbered and lettered folders. Looked like registry folders for Windows.
stevew84 said:
Ok I almost forgot.
When I first unlocked the phone I was able to flash Nitrogen, both the ROM and twrp. But when I rebooted recovery to get to slot B, all I saw were various numbered and lettered folders. Looked like registry folders for Windows.
Click to expand...
Click to collapse
Well that changes things a little. You at least have unlocked one partition then. And you can update factory images via fastboot? If so, then your fully unlocked. So you've got a twrp decryption error on slot B. You may want to disable screen lock security, and try again. You could also try fastbooting into twrp as well with screen lock also disabled.
Thanks. I'll try that out later.
But after I was unable to get into Nitrogen, I flashed stock manually and tried it all over. From this point I kept getting error after error in twrp.
After the errors, I got the Device is Corrupt screen, and freezing on the Google splash. From there I'd have to again start all over.
stevew84 said:
Thanks. I'll try that out later.
But after I was unable to get into Nitrogen, I flashed stock manually and tried it all over. From this point I kept getting error after error in twrp.
After the errors, I got the Device is Corrupt screen, and freezing on the Google splash. From there I'd have to again start all over.
Click to expand...
Click to collapse
Again, run the.....fastboot getvar all....and see what you get :good:
Thanks.
Badger50 said:
Again, run the.....fastboot getvar all....and see what you get :good:
Click to expand...
Click to collapse
Alright. I'm all unlocked and I disabled any sort of screen lock. I'm trying to flash Nitrogen now and seeing what happens...
and it failed again. I'm at a loss, I've never experienced this before.
The error is "updater process ended with ERROR: 1. Error installing zip........
Trying again because why the hell not. Maybe I'l try another TWRP version.
stevew84 said:
Alright. I'm all unlocked and I disabled any sort of screen lock. I'm trying to flash Nitrogen now and seeing what happens...
and it failed again. I'm at a loss, I've never experienced this before.
The error is "updater process ended with ERROR: 1. Error installing zip........
Trying again because why the hell not. Maybe I'l try another TWRP version.
Click to expand...
Click to collapse
Are you using the latest twrp from here? https://dl.twrp.me/taimen/
Also, you might want to try fastbooting the factory image with the -w removed from the flash-all.bat file to slot B. Then fastboot into twrp and try again. You will not lose any data by doing this.
Badger50 said:
Are you using the latest twrp from here? https://dl.twrp.me/taimen/
Also, you might want to try fastbooting the factory image with the -w removed from the flash-all.bat file to slot B. Then fastboot into twrp and try again. You will not lose any data by doing this.
Click to expand...
Click to collapse
I've read up on how to flash stock images without formatting data, but how would one flash directly to a particular slot? The only way I know how to get into a slot is through TWRP, but aren't there adb commands for this as well?
stevew84 said:
I've read up on how to flash stock images without formatting data, but how would one flash directly to a particular slot? The only way I know how to get into a slot is through TWRP, but aren't there adb commands for this as well?
Click to expand...
Click to collapse
In fastboot mode run...fastboot --set-active=a or b...
In your case select b.
Then, fastboot reboot bootloader
Now your on slot b, and can fastboot the factory image :good:
Badger50 said:
In fastboot mode run...fastboot --set-active=a or b...
In your case select b.
Then, fastboot reboot bootloader
Now your on slot b, and can fastboot the factory image :good:
Click to expand...
Click to collapse
Jesus christ. I'm in a cmd window right now, with the latest platform tools installed.
I ran the command just as you typed, (I'm in bootloader, bootloader version tmz20j by the way). Also, my bootloader version has changed a couple of times during all of this. It was tmz20bb, then tmz12g when I flashed the latest June image...now it's this 20j version.
Anyway, this is what I'm typing and this is what I get in return:
fastboot --set-active=b
fastboot: error: Device does not support slots
I'm at a real loss, obviously this damn device supports slots.
EDIT: OK hold on, when I flashed the June image bootloader version, ran the slot command in ADB, I was able to navigate to the right slot.
Little update.
Followed this guide:
https://forum.xda-developers.com/pixel-xl/how-to/slota-b-how-to-flash-roms-magisk-kernel-t3754175
Rebooted into slot a and the touch screen stopped working. So now I'm going back to stock yet again. Just leaving it that way for now I can't deal with this crap.
stevew84 said:
Little update.
Followed this guide:
https://forum.xda-developers.com/pixel-xl/how-to/slota-b-how-to-flash-roms-magisk-kernel-t3754175
Rebooted into slot a and the touch screen stopped working. So now I'm going back to stock yet again. Just leaving it that way for now I can't deal with this crap.
Click to expand...
Click to collapse
Fwiw, after you flash a rom and twrp, if it doesn't boot up, go back to twrp and flash the rom and twrp again. Flashing roms or taking OTA's automatically switches slots on you. Always best to keep screen lock disabled until you are done.
Badger50 said:
Fwiw, after you flash a rom and twrp, if it doesn't boot up, go back to twrp and flash the rom and twrp again. Flashing roms or taking OTA's automatically switches slots on you. Always best to keep screen lock disabled until you are done.
Click to expand...
Click to collapse
Thanks.
I have TWRP installed as my permanent recovery on my device. My question is what would happen if I flash (for example) system-arm64-aonly-gapps-su.img using TWRP on my device? Will it bricked? Can I restore it by flashing stock using ODIN?
I posted on a wrong thread. Kindly move it to https://forum.xda-developers.com/project-treble/trebleenabled-device-questions-and-answers since this is a question.
ECOTV said:
I have TWRP installed as my permanent recovery on my device. My question is what would happen if I flash (for example) system-arm64-aonly-gapps-su.img using TWRP on my device? Will it bricked? Can I restore it by flashing stock using ODIN?
I posted on a wrong thread. Kindly move it to https://forum.xda-developers.com/project-treble/trebleenabled-device-questions-and-answers since this is a question.
Click to expand...
Click to collapse
It won't brick, it just won't boot. The system image is designed to look for boot vendor etc in different partitions, not in the system as it previously was
miffymiffy said:
It won't brick, it just won't boot. The system image is designed to look for boot vendor etc in different partitions, not in the system as it previously was
Click to expand...
Click to collapse
So if I flash it and if it won't boot, can I return to stock using ODIN?
ECOTV said:
So if I flash it and if it won't boot, can I return to stock using ODIN?
Click to expand...
Click to collapse
No idea how you'd go back. The moral is don't flash it. It won't work
miffymiffy said:
It won't brick, it just won't boot. The system image is designed to look for boot vendor etc in different partitions, not in the system as it previously was
Click to expand...
Click to collapse
I have a Samsung Galaxy J4 Plus and it has treble support (A ONLY) but when i flash GSI it wont boot. it end up in a bootloop and i cant get it to boot. What should i do ??
dewin_prins said:
I have a Samsung Galaxy J4 Plus and it has treble support (A ONLY) but when i flash GSI it wont boot. it end up in a bootloop and i cant get it to boot. What should i do ??
Click to expand...
Click to collapse
Just wipe system and data and flash an specific rom for your device.
Schnedi said:
Just wipe system and data and flash an specific rom for your device.
Click to expand...
Click to collapse
i am at the boot screen of pixel experience gsi rom but it wont boot to system.. or it just takes a long time its been on the google logo for about an hour now and its not in the os yet should i wait or do something else i dont know what to do to make it go to the system..
Precautions for a gsi rom flash
If your device is supported then you must boot up with gsi
Do you wiped dalvik /cache / data partitions before booting with gsi or i say before flashing gsi rom
Hello!
I installed the new Android 11 stable and everything went well. I installed OTA and was able to flash a modified boot.img for root. I then wanted to re-enable the modules I turned off for the update. That's when I got stuck in a boot loop. I'm not sure the correct procedure for re-enabling the modules but immediately after restarting to let the modules take effect I ran into a boot loop.
To remedy this I tried re-flashing the modified boot image, which always leads to a boot loop.
I have also tried the "adb shell magisk --remove-modules" command during the boot loop but that immediately brings me to the fastboot screen with the reason "Invalid boot slot" and then it stays there until I flash another boot.img.
I've tried unpacking and repacking a magisk_patched.img with both the Pixel 3a XL's "core only" and "remove modules" but those lead to a fastboot error where it doesn't like the image and won't boot from it.
If I flash the stock Android 11 boot.img the phone boots up fine but doesn't have root obviously. I am also using the newest (30.0.4) version of android platform tools.
I was wondering if anyone else had some insight as to what I'm doing wrong or where to go from here?
Thank you in advance
scyther3989 said:
Hello!
I installed the new Android 11 stable and everything went well. I installed OTA and was able to flash a modified boot.img for root. I then wanted to re-enable the modules I turned off for the update. That's when I got stuck in a boot loop. I'm not sure the correct procedure for re-enabling the modules but immediately after restarting to let the modules take effect I ran into a boot loop.
To remedy this I tried re-flashing the modified boot image, which always leads to a boot loop.
I have also tried the "adb shell magisk --remove-modules" command during the boot loop but that immediately brings me to the fastboot screen with the reason "Invalid boot slot" and then it stays there until I flash another boot.img.
I've tried unpacking and repacking a magisk_patched.img with both the Pixel 3a XL's "core only" and "remove modules" but those lead to a fastboot error where it doesn't like the image and won't boot from it.
If I flash the stock Android 11 boot.img the phone boots up fine but doesn't have root obviously. I am also using the newest (30.0.4) version of android platform tools.
I was wondering if anyone else had some insight as to what I'm doing wrong or where to go from here?
Thank you in advance
Click to expand...
Click to collapse
Sounds like an incomparable magisk module. You need to isolate which module is the problem and leave it disabled or look for an updated version
adm1jtg said:
Sounds like an incomparable magisk module. You need to isolate which module is the problem and leave it disabled or look for an updated version
Click to expand...
Click to collapse
I would be fine with this but I have no idea how to disable the modules without root. And the adb shell isn't working for me either.
scyther3989 said:
I would be fine with this but I have no idea how to disable the modules without root. And the adb shell isn't working for me either.
Click to expand...
Click to collapse
I think it's in the themes forum here but they're is a magisk module disabler. They're are also other utilities to do so.
adm1jtg said:
I think it's in the themes forum here but they're is a magisk module disabler. They're are also other utilities to do so.
Click to expand...
Click to collapse
The only things I've seen for Module disablers are...
the adb shell magisk module disable
the patched "core only" and "module remover" repacked boot images
magisk uninstaller that requires a recovery to run it
I've tried the first two and I can't find a TWRP that works with a Pixel 3a XL running Android 11.
scyther3989 said:
The only things I've seen for Module disablers are...
the adb shell magisk module disable
the patched "core only" and "module remover" repacked boot images
magisk uninstaller that requires a recovery to run it
I've tried the first two and I can't find a TWRP that works with a Pixel 3a XL running Android 11.
Click to expand...
Click to collapse
And you won't find one. Twrp only works on Android 9 or older. Starting with 10 the partitions are dynamic and to date twrp can't handle them at all. Since we haven't had a working twrp in over a year i wouldn't get my hopes up.
adm1jtg said:
And you won't find one. Twrp only works on Android 9 or older. Starting with 10 the partitions are dynamic and to date twrp can't handle them at all. Since we haven't had a working twrp in over a year i wouldn't get my hopes up.
Click to expand...
Click to collapse
Yeah I'm hoping for some kind of insight on how to disable modules without root or maybe some new patch I haven't tried.
Try booting into safe mode, this is supposed to disable all modules. When you boot back into regular mode they should still be disabled and you can delete or update the bad one.
Sent from my SM-T860 using XDA-Developers Legacy app
rifraf1 said:
Try booting into safe mode, this is supposed to disable all modules. When you boot back into regular mode they should still be disabled and you can delete or update the bad one.
Sent from my SM-T860 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Wow this actually worked!!
For anyone having a similiar issue:
I flashed the magisk_patched.img from Android 11 and let it go back into it's bootloop
As soon as the booting animation started I pressed volume UP and volume DOWN and it booted into safe mode
I restarted once I successfully made it into safe mode
The modules causing the bootloop were disabled and I am now able to have root in Android 11
Thank you @rifraf1