Database Develop

Download Lollipop LRX21P Factory Image for 2012 Nexus 7 WiFi Leaked!

Have at it boys!
http://dl.google.com/dl/android/aosp/nakasi-lrx21p-factory-93daa4d3.tgz
MD5: e68948c23c918436680bd28fc6aaf983)
http://goo.gl/aYbCwf

IM guessing we can flash only system and boot...since the bootloader is the same. Plus, we don't wanna reflash the factory recovery.
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
ADB and Fastboot files attached below, if needed.

Mikey said:
IM guessing we can flash only system and userdata....since the bootloader is the same. Plus, we don't wanna reflash the factory recovery.
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
ADB and Fastboot files attached below, if needed.
Click to expand...
Click to collapse
Don't think that radio needs to be flashed on the N7
Cheers
Tom

I wouldn't flash the recovery partition, either.
The recovery-from-boot.p is in /system. I renamed it before the first boot using TWRP's file manager. I also flashed supersu. It's booting now...need to get to bed, though. Will report tomorrow.
Edit: Boot is successful. L.
Edit: This is my first go around with L. The checking for updates thing at sign on is interesting.

Flashed via fastboot and setting up now. I will report back with initial results and fire away any question you may want specifically answered.
FYI, first boot took about 6 minutes...

tom1807 said:
Don't think that radio needs to be flashed on the N7
Cheers
Tom
Click to expand...
Click to collapse
there is no radio in this....its wifi only....... the commands are generic

Hmmm...I am not getting supersu to work. Flashing the 2.16 zip in TWRP. The app says the binary is not installed.

brizey said:
Hmmm...I am not getting supersu to work. Flashing the 2.16 zip in TWRP. The app says the binary is not installed.
Click to expand...
Click to collapse
Probably needs a patch like for the N9.
Cheers
Tom

tom1807 said:
Probably needs a patch like for the N9.
Cheers
Tom
Click to expand...
Click to collapse
brizey said:
Hmmm...I am not getting supersu to work. Flashing the 2.16 zip in TWRP. The app says the binary is not installed.
Click to expand...
Click to collapse
http://www.ibtimes.co.uk/chainfire-releases-quick-root-fix-android-5-0-lollipop-preview-builds-how-install-1470680
https://plus.google.com/+Chainfire/posts/ZzXaU1W7Uzm

Mikey said:
http://www.ibtimes.co.uk/chainfire-releases-quick-root-fix-android-5-0-lollipop-preview-builds-how-install-1470680
https://plus.google.com/+Chainfire/posts/ZzXaU1W7Uzm
Click to expand...
Click to collapse
Yep...thanks.
Hmmm...this is not all that useful without Titanium. Will go back to KK in the AM and wait for a patched kernel.

Mikey said:
http://www.ibtimes.co.uk/chainfire-releases-quick-root-fix-android-5-0-lollipop-preview-builds-how-install-1470680
https://plus.google.com/+Chainfire/posts/ZzXaU1W7Uzm
Click to expand...
Click to collapse
Have to try probably, not sure whether this will run on a newer build of Lollipop
Cheers
Tom

Kernel version?

Any major differences than the couple of versions built from source?
Fyi, you will probably need SuperSU beta 2.19 and modified boot image for root. There is a titanium backup that works with l (beta). There may be a command that reflashes stock recovery on reboot (it's in /system /bin).
Tibu:
https://docs.google.com/file/d/0Bwj2Hf45t6uMSElfSXR6YXdVdVU/edit?usp=docslist_api
SuperSU:
http://forum.xda-developers.com/showthread.php?t=2868133
Nexus 7 5.0

Mikey said:
http://www.ibtimes.co.uk/chainfire-releases-quick-root-fix-android-5-0-lollipop-preview-builds-how-install-1470680
https://plus.google.com/+Chainfire/posts/ZzXaU1W7Uzm
Click to expand...
Click to collapse
tom1807 said:
Have to try probably, not sure whether this will run on a newer build of Lollipop
Cheers
Tom
Click to expand...
Click to collapse
Not good, the Boot.img is for Nexus 7 (2013)
Hangs at the Google logo.
Back to original Boot.img
Cheers
Tom

Mikey said:
IM guessing we can flash only system and boot...since the bootloader is the same. Plus, we don't wanna reflash the factory recovery.
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
Click to expand...
Click to collapse
Can I use these steps to clean flash the factory image?
I want to wipe everything and start from a fresh and clean flash.
I haven't flashed a factory image for a long time so I'm out of shape ?

Could someone make a flashable zip for multirom or normal flashing. ?

Nexus Root Toolkit
has anyone tried flashing this via nexus root toolkit? that software recently goot updated to 1.9.3 and has the abiloity to flash the Lollipop factory preview on those devices that got it.

That is exactly way I did. Started fresh and running smooth so far!

I used the toolkit to flash latest TWRP but that was all.

qualitymove13 said:
Flashed via fastboot and setting up now. I will report back with initial results and fire away any question you may want specifically answered.
FYI, first boot took about 6 minutes...
Click to expand...
Click to collapse
I was just going to ask about the boot time lol taking forever

Unable to install OTA LRX21O

Yesterday I recieved my phone and I unlocked the bootloader as well as rooted using CF. Today I tried to flash the OTA LRX21O (I'm on LNX07M) in TWRP but I'm getting the error "Package expects build fingerprint of google/shamu/shamu:5.0/LNX07M/1543455: user/release-keys or google/shamu/shamu : 5.0/LRX210/1570415 : user/release-keys; this device has Android/aosp_shamu/shamu:5.0LRX21M/dees_troy11191312:userdebug/test-keys"
What the heck does this mean? I also tried flashing back to stock recovery but it just ended up with an android image with "error" below it. I'm assuming it ran into the same problem. Do I need to wipe and start all over??

RandoTheKing said:
Yesterday I recieved my phone and I unlocked the bootloader as well as rooted using CF. Today I tried to flash LRX21O in TWRP but I'm getting the error "Package expects build fingerprint of google/shamu/shamu:5.0/LNX07M/1543455: user/release-keys or google/shamu/shamu : 5.0/LRX210/1570415 : user/release-keys; this device has Android/aosp_shamu/shamu:5.0LRX21M/dees_troy11191312:userdebug/test-keys"
What the heck does this mean? I also tried flashing back to stock recovery but it just ended up with an android image with "error" below it. I'm assuming it ran into the same problem. Do I need to wipe and start all over??
Click to expand...
Click to collapse
You can't install the OTA if you rooted. You'll probably need to just install the factory images via fastboot.

akellar said:
You can't install the OTA if you rooted. You'll probably need to just install the factory images via fastboot.
Click to expand...
Click to collapse
I thought you could always just flash them manually? When did this change? No point in rooting if I'm going to stay stock, it seems.

RandoTheKing said:
I thought you could always just flash them manually? When did this change? No point in rooting if I'm going to stay stock, it seems.
Click to expand...
Click to collapse
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).

Dr Faustus said:
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Click to expand...
Click to collapse
well what will you do for future updates? Full wipe?

RandoTheKing said:
well what will you do for future updates? Full wipe?
Click to expand...
Click to collapse
http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
not really - you can just flash the "old" stock system image file and then install the update (or just flash the "new" system file)

Dr Faustus said:
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Click to expand...
Click to collapse
jj14 said:
http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
not really - you can just flash the "old" stock system image file and then install the update (or just flash the "new" system file)
Click to expand...
Click to collapse
Any instructions on how to do that? I'm assuming I can still get the update that way

RandoTheKing said:
Any instructions on how to do that? I'm assuming I can still get the update that way
Click to expand...
Click to collapse
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
Edit - flash the cache.img instead of just erasing cache

I had trouble flashing the factory image initially. I kept getting an error so I used this method and it worked perfectly. Hope it helps. http://www.ibtimes.co.uk/how-fix-er...roid-5-0-factory-images-nexus-devices-1474865

So i am root and have done a bit of work on my Nexus 6 (changing system sounds, setting it up and a few other things) If i want to install LRX21O, what is the step by step to do that and after i install it if i do a Nandroid Backup, can i restore the backup on LRX21O? I am currently on LNX07M.

I am curious as well. Also do you happen to have a link to the file to just update.?
EDIT... Found it. Will flash when home
Sent from my Nexus 6 using XDA Free mobile app

jj14 said:
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
Click to expand...
Click to collapse
Should that be `fastboot format cache`?

jm77 said:
Should that be `fastboot format cache`?
Click to expand...
Click to collapse
Actually, you should just flash the cache.img

jj14 said:
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
You don't reboot into recovery if you are using fas boot. You boot into boot loader at least that's how I've done it on every Nexus that I've had.
Edit - flash the cache.img instead of just erasing cache
Click to expand...
Click to collapse
jm77 said:
Should that be `fastboot format cache`?
Click to expand...
Click to collapse
You can use both commands to first format, then flash the new one it doesn't really matter. I've used both methods
jj14 said:
Actually, you should just flash the cache.img
Click to expand...
Click to collapse

Taking OPW28.3 OTA (June, 2018) Update with TWRP and Magisk Installed

I have an Android One Moto x4 running 8.1.0 OPW28.2 (OPW28.46-18) and I am getting a notification for the OPW28.3 OTA update. I want to install it, but I have TWRP and Magisk installed.
I tried to uninstall Magisk and then install the OTA, but it said "update failed". Did I do something wrong? Do I also need to uninstall TWRP/restore a 100% stock boot.img?

You have to be completely stock to apply otas.

Thanks, that helps. The only "non-stock" things are TWRP and Magisk. Hopefully restoring a stock boot.img should be enough to let me install it.

Try this method.

Tried to restore images in Magisk but got the message "Stock backup does not exis!"
I think when I installed Magisk I chose Direct Install (recommended). Does Magisk only create a backup boot file if installed another way? (Patch Boot Image File)

Ok, so not only did I completely uninstall Magisk, I also restored a stock boot.img (from https://forum.xda-developers.com/showpost.php?p=77096052&postcount=2).
When I went to install the OTA, it said "failed". I'm not sure what else I need to do.
Well, I have a few other ideas... when I opened TWRP, it said I was on slot B. Is that right? What if I switch to A? Or what if I stay on B, but I erase A's system partition? Do I need to copy system from B to A or something?
OH! What if I use TWRP to restore the backup I downloaded to slot A, boot to that, then try to install the OTA?
Why is this failing even though I have a stock system and boot?

Do you have stock recovery? Because OTA uses that, not TWRP.

MacFett said:
Do you have stock recovery? Because OTA uses that, not TWRP.
Click to expand...
Click to collapse
installing stock boot.img would have installed stock recovery.

MacFett said:
Do you have stock recovery? Because OTA uses that, not TWRP.
Click to expand...
Click to collapse
Yeah, the recovery is back to stock. There's something I'm missing, but I'm not sure what it is. Something to do with the A/B slots, I think.

I've been messing around with installing the OTA on an A1 phone today as well. I've flashed back to stock at least a half-dozen times. So far all I've been able to determine is that the OTA updates are supremely touchy.
If I do nothing in fastboot after flashing back to stock 28.1 then 28.2 and 28.3 will install just fine, and if I do anything with booting TWRP or flashing images the OTAs fail.
Also, the 28.3 update seems to take way longer to install than the 28.2.

NTICompass said:
Yeah, the recovery is back to stock. There's something I'm missing, but I'm not sure what it is. Something to do with the A/B slots, I think.
Click to expand...
Click to collapse
Do you need to relock the boot loader?

MacFett said:
Do you need to relock the boot loader?
Click to expand...
Click to collapse
Wouldn't that factory reset the phone?

tormin said:
I've been messing around with installing the OTA on an A1 phone today as well. I've flashed back to stock at least a half-dozen times. So far all I've been able to determine is that the OTA updates are supremely touchy.
If I do nothing in fastboot after flashing back to stock 28.1 then 28.2 and 28.3 will install just fine, and if I do anything with booting TWRP or flashing images the OTAs fail.
Also, the 28.3 update seems to take way longer to install than the 28.2.
Click to expand...
Click to collapse
That's what I wound up doing to get all the way up to date. I flashed the stock 28.1 (modifying the flash_stock.sh script to not flash the partition file or erase userdata) and then I was able to OTA update to 28.2 and then 28.3

MacFett said:
Do you need to relock the boot loader?
Click to expand...
Click to collapse
Unlocked bootloader worked fine for me.

boot image it's your stock kernel, not your recovery. I don't understand how you get stock recovery. The only way I know to do that, its flashing a stock recovery and then fully unroot your phone, Now try to installed the OTA update. You can get the recovery image from a stock firmware, but to be sure it would work, try to use the same version as your phone is (Europe, Latam, India...)

downface said:
boot image it's your stock kernel, not your recovery. I don't understand how you get stock recovery. The only way I know to do that, its flashing a stock recovery and then fully unroot your phone, Now try to installed the OTA update. You can get the recovery image from a stock firmware, but to be sure it would work, try to use the same version as your phone is (Europe, Latam, India...)
Click to expand...
Click to collapse
I think the moto x4 is a little weird and the recovery is actually part of the boot image.

NTICompass said:
That's what I wound up doing to get all the way up to date. I flashed the stock 28.1 (modifying the flash_stock.sh script to not flash the partition file or erase userdata) and then I was able to OTA update to 28.2 and then 28.3
Click to expand...
Click to collapse
How'd you do that? If you dont mind me asking, how to edit it? Thanks

nabhse90 said:
How'd you do that? If you dont mind me asking, how to edit it? Thanks
Click to expand...
Click to collapse
I grabbed the stock image from https://forum.xda-developers.com/moto-x4/how-to/oreo-8-1-official-firmware-available-t3805173 and grabbed a "flash_all" script from https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
I opened up the flash_all.sh script and just removed the line "fastboot erase userdata" (I also removed "fastboot flash partition gpt.bin", not sure if I really needed to).

NTICompass said:
I grabbed the stock image from https://forum.xda-developers.com/moto-x4/how-to/oreo-8-1-official-firmware-available-t3805173 and grabbed a "flash_all" script from https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
I opened up the flash_all.sh script and just removed the line "fastboot erase userdata" (I also removed "fastboot flash partition gpt.bin", not sure if I really needed to).
Click to expand...
Click to collapse
Yey! Thank you thank you! I can now update without having to go through all that process of updating multiple times just to have the latest version. So just removing the "erase userdata" is fine right? If I dont do the other it still works fine? Just making sure because I think Im just gonna boot TWRP and flash Magisk so I can stick to stock boot.img and just update whenever they pop. Thanks again!!!

nabhse90 said:
Yey! Thank you thank you! I can now update without having to go through all that process of updating multiple times just to have the latest version. So just removing the "erase userdata" is fine right? If I dont do the other it still works fine? Just making sure because I think Im just gonna boot TWRP and flash Magisk so I can stick to stock boot.img and just update whenever they pop. Thanks again!!!
Click to expand...
Click to collapse
I'm not 100% sure what all the lines in the flash_all.sh script do, so I can't provide any guarantees. It worked for me to remove the 2 lines: "fastboot flash partition gpt.bin" and "fastboot erase userdata". Then I was able to flash the original/stock 28.1 image to the system. When it booted, I installed the 28.2 OTA, rebooted and then I was able to install the 28.3 OTA.
I had to do this craziness because the 28.3 OTA was failing to install for me otherwise.

DP3 Q Beta T-Mobile Guide

Not used to giving guides
TWRP Backup - https://forum.xda-developers.com/oneplus-6t/how-to/dp3-twrp-backup-t-mobile-magisk-t3952304
But you need to download the the QB3 update zip and upack the payload.bin with a payload dumper
Make sure your device is on international and unlocked of course
Boot into Twrp recovery and copy the system.img and vendor.img onto device
Flash both images in respective partitions and on both A and B slot
Wipe data after flashing and reboot into bootloader
From directory of the rest of IMG you've extracted you'll want use fastboot and flash:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
Then reboot and done
Don't delete files just yet
Haven't tried but certain you can root this way:
After you've setup your device you can download magisk manager. Select the boot.img on you pc, in your dump folder, and copy it to your device again. In the magisk manager patch the boot image you copied, and copy that onto your PC
Now boot into bootloader and use command
fastboot flash boot magisk_patched.img
Or if that doesn't work try
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
And if device doesn't boot for any reason just flash back the stock boot.img
Enjoy

-About TWRP- (from my knowledge)
DON'T FLASH TWRP
I think recovery is running in boot.img now I'm not sure
But it seems we may need to patch the bootloader to have the recovery in there
Ive unpack both boot IMG from dp3 and Twrp IDK if they're made different but they look different unfortunately I don't understand enough to patch but hopefully that helps idk
So I wouldn't try flashing or booting into recovery it'll just freeze and flashing will mess up the whole device and you'll have to use msmtool again and redo process

ayjays said:
-About TWRP- (from my knowledge)
DON'T FLASH TWRP
I think recovery is running in boot.img now I'm not sure
But it seems we may need to patch the bootloader to have the recovery in there
Ive unpack both boot IMG from dp3 and Twrp IDK if they're made different but they look different unfortunately I don't understand enough to patch but hopefully that helps idk
So I wouldn't try flashing or booting into recovery it'll just freeze and flashing will mess up the whole device and you'll have to use msmtool again and redo process
Click to expand...
Click to collapse
It's not about patching.
Flash stock boot.img to both slots as I'm guessing you aren't sure which one your on.
I'll give u a twrp that works for qb3 also proper instructions.
T-Mobile version downside is we can't flash ota and we can't boot qb3 wth fastboot twrp so flashing the twrp.img now replaces kernel in boot.img.

Thanks, so I'll have to use the "flash recovery Twrp.img" command now?
Or, is it a custom one Twrp only for dp3?
And thank you by the way I'll probably post a guide using a backup from Twrp then
And I'm aware of checking the active slot with a command but I have trouble switching to the opposite after rebooting because of set_active command maybe I'm doing something wrong

ayjays said:
Thanks, so I'll have to use the "flash recovery Twrp.img" command now?
Or, is it a custom one Twrp only for dp3?
And thank you by the way I'll probably post a guide using a backup from Twrp then
Click to expand...
Click to collapse
Our recovery is built in boot.img.
Uploading now
---------- Post added at 10:10 PM ---------- Previous post was at 09:42 PM ----------
Boot to fastboot
fastboot getvar all
See which slot is active.
If it's slot a then this
fastboot flash boot_a qb3-twrp.img
If it's slot b then this
fastboot flash boot_b qb3-twrp.img
Once flashed choose boot recovery and once it boots u can flash stock boot.img back then flash magisk 19.4 while in twrp.
U must use USB drive decryption isn't working yet. Or adb sideload.
I've only tested this on T-Mobile version running qb3.
All credits to @mauronofrio I used his source with some modifications
https://www.androidfilehost.com/?fid=6006931924117924335

ayjays said:
Thanks, so I'll have to use the "flash recovery Twrp.img" command now?
Or, is it a custom one Twrp only for dp3?
And thank you by the way I'll probably post a guide using a backup from Twrp then
And I'm aware of checking the active slot with a command but switching to it after rebooting because I of set_active command maybe I'm doing something wrong
Click to expand...
Click to collapse
Did you try what I posted

twinnfamous said:
It's not about patching.
Flash stock boot.img to both slots as I'm guessing you aren't sure which one your on.
I'll give u a twrp that works for qb3 also proper instructions.
T-Mobile version downside is we can't flash ota and we can't boot qb3 wth fastboot twrp so flashing the twrp.img now replaces kernel in boot.img.
Click to expand...
Click to collapse
twinnfamous said:
Did you try what I posted
Click to expand...
Click to collapse
Not yet, but if you flash the stock boot image after then would there be any point in flashing the patch boot before hand? And, what I was looking for is a more permanent solution. So, that it'll boot and you can go to Twrp whenever without having to use a PC.
If that's the case and it works then nevermind but I remember and if I'm mistaken that, even if you flash the Twrp installer it'll still boot loop after the installation.
If that's still a problem maybe someone more skilled than I, or even you, can patch the stock bootimg themselves. And, eveb get it working for the future time on Q
Maybe unpacking and looking inside the boot.img and Twrp.img, the repacking with the proper adjustments

ayjays said:
Not yet but if you flash the stock boot image after then would there any point in flashing the patch boot before hand. And, what I was looking for is a more permanent solution. So, that it'll boot and you can go to Twrp whenever without having to use a PC.
If that's the case and it works then nevermind but I remember and if I'm mistaken that, even if you flash the Twrp installer it'll still boot loop after the installation.
If that's still a problem maybe someone more skilled than I, or even you, can patch the stock bootimg themselves. And, eveb get it working for the future time on Q
Maybe unpacking and looking inside the boot.img and Twrp.img, the repacking with the proper adjustments
Click to expand...
Click to collapse
I'm aware of the permanent solution your looking for. This is the first step. With magisk installed u can simply use the installer in my android file host by selecting modules push the + sign and find the installer then without rebooting install magisk direct install. Then u can boot to recovery with advanced reboot menu. U can also just do everything in twrp. After u flash twrp.img .

ayjays said:
Not used to giving guides
But you need to download the the QB3 update zip and upack the payload.bin with a payload dumper
Make sure your device is on international and unlocked of course
Boot into Twrp recovery and copy the system.img and vendor.img onto device
Flash both images in respective partitions and on both A and B slot
Wipe data after flashing and reboot into bootloader
From directory of the rest of IMG you've extracted you'll want use fastboot and flash:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
Then reboot and done
Don't delete files just yet
Haven't tried but certain you can root this way:
After you've setup your device you can download magisk manager. Select the boot.img on you pc, in your dump folder, and copy it to your device again. In the magisk manager patch the boot image you copied, and copy that onto your PC
Now boot into bootloader and use command
fastboot flash boot magisk_patched.img
Or if that doesn't work try
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
And if device doesn't boot for any reason just flash back the stock boot.img
Enjoy
Click to expand...
Click to collapse
Just like my guide last month on OnePlus forums as I am jacksummers, even if u do this we still have no calling ability whatsoever. SMS is barely working and it still blows for us. I have been trying everything to get the whole thing to not only flash and install but be able to boot with no hardware mismatch... It won't work unless we can resign the firmware with OnePlus signing keys after changing everything to say "single" still. Since we cannot change the phone. There is still something in the phone that comes back as op6tsingle

fullofhell said:
Just like my guide last month on OnePlus forums as I am jacksummers, even if u do this we still have no calling ability whatsoever. SMS is barely working and it still blows for us. I have been trying everything to get the whole thing to not only flash and install but be able to boot with no hardware mismatch... It won't work unless we can resign the firmware with OnePlus signing keys after changing everything to say "single" still. Since we cannot change the phone. There is still something in the phone that comes back as op6tsingle
Click to expand...
Click to collapse
My phone is off rn but I receive calls and texts and I've been receiving calls on my T-Mobile OnePlus 6t since I flashed it... Make sure you're on international version
the only problems i ran in myself so far are app optimzations and when i'd recieved calls and answer my voice would sound weird to them but id hear them perfectly (not my problem lol jk jk)

ayjays said:
My phone is off rn but I receive calls and texts and I've been receiving calls on my T-Mobile OnePlus 6t since I flashed it... Make sure you're on international version
the only problems i ran in myself so far are app optimzations and when i'd recieved calls and answer my voice would sound weird to them but id hear them perfectly (not my problem lol jk jk)
Click to expand...
Click to collapse
Yeah u need to flash every other partition in the bin dump. If it tells u u cannot bc it's a critical partition then ya can't. Once u do so u will have full function and on calls. It's basically everything in the payload.bin but abl,xbl, hyp, and a few others that tell ya they're critical partitions. Once u do that everything works Perfectly.. my main issue was the call issue u described..but do as I suggest and all will work

​
fullofhell said:
Yeah u need to flash every other partition in the bin dump. If it tells u u cannot bc it's a critical partition then ya can't. Once u do so u will have full function and on calls. It's basically everything in the payload.bin but abl,xbl, hyp, and a few others that tell ya they're critical partitions. Once u do that everything works Perfectly.. my main issue was the call issue u described..but do as I suggest and all will work
Click to expand...
Click to collapse
That's why I said to flash system and vendor in Twrp wipe data then flash the other ones I stated above in fastboot mode everything should be flashed without a problem just follow my guide it's not hard

I'm uploading twrp backup soon with root

DO AT YOUR OWN RISK I WONT BE RESPONSIBLE FOR ANYTHING!!!!!!
EVERYTHING SO FAR WORKS WITH JUST A LIL LAG HERE AND THERE
Tmo oneplus 6t fastboot flash one click Android Q DP3. i test it with and without wiping data. i just put all the files together. just run the flash bat. You need to be on latest beta. i tested myself twice.
root= Download patch q boot.img.
fastboot flash boot img after first boot. then just download canary magisk manager. a quick google search will bring it up
have fun and remember anything goes south you can msm tool back to stock!
flash all: https://drive.google.com/open?id=1D_-B5z-rHGDr6RHjDQA0hz-janrsypdv
patch boot img: https://drive.google.com/open?id=1nbiapy6HZH4VNK4JuEF9KxSIlsBRKgsX

omariscal1019 said:
DO AT YOUR OWN RISK I WONT BE RESPONSIBLE FOR ANYTHING!!!!!!
EVERYTHING SO FAR WORKS WITH JUST A LIL LAG HERE AND THERE
Tmo oneplus 6t fastboot flash one click Android Q DP3. i test it with and without wiping data. i just put all the files together. just run the flash bat. You need to be on latest beta. i tested myself twice.
root= Download patch q boot.img.
fastboot flash boot img after first boot. then just download canary magisk manager. a quick google search will bring it up
have fun and remember anything goes south you can msm tool back to stock!
flash all: https://drive.google.com/open?id=1D_-B5z-rHGDr6RHjDQA0hz-janrsypdv
patch boot img: https://drive.google.com/open?id=1nbiapy6HZH4VNK4JuEF9KxSIlsBRKgsX
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6t/development/dp3-twrp-backup-t-mobile-magisk-t3952304 TWRP backup good job on the not wiping data though

ayjays said:
That's why I said to flash system and vendor in Twrp wipe data then flash the other ones I stated above in fastboot mode everything should be flashed without a problem just follow my guide it's not hard
Click to expand...
Click to collapse
Hi, yes we are saying the same thing.. also note, for me, Calls last for a day, then broken again. Cannot use daily if u need to make phone calls. Testing with TMobile modem.img to see if resolved.

fullofhell said:
Hi, yes we are saying the same thing.. also note, for me, Calls last for a day, then broken again. Cannot use daily if u need to make phone calls. Testing with TMobile modem.img to see if resolved.
Click to expand...
Click to collapse
i made a one click fastboot let me what happens so.ican remove it and add t mo modem

omariscal1019 said:
i made a one click fastboot let me what happens so.ican remove it and add t mo modem
Click to expand...
Click to collapse
Will do buddy. Setting mine up as we speak.. I am down to just my fajita right now, bricked my pixel 3 again as I'm working on an exploit to unlock my locked down version ....

Can you relock bootloader after this? Don't want twrp or root

supaet said:
Can you relock bootloader after this? Don't want twrp or root
Click to expand...
Click to collapse
Not sure try "fastboot oem lock" in the bootloader after

"error boot prepare" in fastboot trying to flash magisk patched boot.img

Hi,
I'm coming from a rooted November image for my Pixel 4XL and am having trouble getting the December magisk_patched.img to take. I've successfully applied google stock December image, rebooted to Android, patched boot.img with magisk, but when I try to flash magisk_patched.img in fastboot, it flashes, but reboots to fastboot with "error boot prepare" displayed. Flashing stock boot.img gets back to Android without issue (but no root).
I've tried flashing with both cmd and powershell. I've tried "fastboot flash boot magisk_patched.img" (and also fastboot flash boot_a magisk_patched.img and fastboot flash boot_b magisk_patched.img). I'm using Magisk Manager 7.4.
Not sure what else to try. I'd rather not do a factory reset at this point.
Any suggestions?

DoughMucker said:
Hi,
I'm coming from a rooted November image for my Pixel 4XL and am having trouble getting the December magisk_patched.img to take. I've successfully applied google stock December image, rebooted to Android, patched boot.img with magisk, but when I try to flash magisk_patched.img in fastboot, it flashes, but reboots to fastboot with "error boot prepare" displayed. Flashing stock boot.img gets back to Android without issue (but no root).
I've tried flashing with both cmd and powershell. I've tried "fastboot flash boot magisk_patched.img" (and also fastboot flash boot_a magisk_patched.img and fastboot flash boot_b magisk_patched.img). I'm using Magisk Manager 7.4.
Not sure what else to try. I'd rather not do a factory reset at this point.
Any suggestions?
Click to expand...
Click to collapse
Just a couple things to try.
1. Did you fastboot the factory image to both slots? If not I would try that first, without the -w of course.
2. When you patched the boot.img, was dm-verity checked off? If not, enable it, then patch it again.
3. Have you tried from a cmd....
fastboot flash boot magisk_patched.img --slot=all
Whatever it is, I hope you get it working :good:

Badger50 said:
Just a couple things to try.
1. Did you fastboot the factory image to both slots? If not I would try that first, without the -w of course.
2. When you patched the boot.img, was dm-verity checked off? If not, enable it, then patch it again.
3. Have you tried from a cmd....
fastboot flash boot magisk_patched.img --slot=all
Whatever it is, I hope you get it working :good:
Click to expand...
Click to collapse
Thanks for the suggestions. I tried each one. Unfortunately, no luck.

DoughMucker said:
Thanks for the suggestions. I tried each one. Unfortunately, no luck.
Click to expand...
Click to collapse
Bummer man! How about different 2.0 USB A to USB C cables and ports??

Badger50 said:
Bummer man! How about different 2.0 USB A to USB C cables and ports??
Click to expand...
Click to collapse
Just tried that too. :crying:

DoughMucker said:
Just tried that too. :crying:
Click to expand...
Click to collapse
Sheesh! You using canary or stable magisk? Either way, I'd switch to the other one and try that as well. If that doesn't work, then you may have no choice but to either factory reset, or remove all your drives, platform-tools, redownload everything, and start over. I can't think of many other things to try

Badger50 said:
Sheesh! You using canary or stable magisk? Either way, I'd switch to the other one and try that as well. If that doesn't work, then you may have no choice but to either factory reset, or remove all your drives, platform-tools, redownload everything, and start over. I can't think of many other things to try
Click to expand...
Click to collapse
I was stable before, but had just tried canary. Same situation.
I'm reading https://forum.xda-developers.com/pixel-3-xl/help/december-update-rootable-t4013605/page6 and wondering if it's related to systemless hosts for adaway which i did not disable.

DoughMucker said:
I was stable before, but had just tried canary. Same situation.
I'm reading and wondering if it's related to systemless hosts for adaway which i did not disable.
Click to expand...
Click to collapse
I don't think so, but I suppose anything is possible. I've left magisk modules intact before, but never had the trouble like your having. Shoot, you might even try flashing a different factory image image other than what was recommended by google. People seem to have had the best luck with the .012.A1 version which is supposedly for AT&T only.

Badger50 said:
I don't think so, but I suppose anything is possible. I've left magisk modules intact before, but never had the trouble like your having. Shoot, you might even try flashing a different factory image image other than what was recommended by google. People seem to have had the best luck with the .012.A1 version which is supposedly for AT&T only.
Click to expand...
Click to collapse
I'm using 012.A1. Google updated their factory image/OTA site and removed the reference to ATT. I had double checked someone else's phone here that got the Dec OTA update and she had 012.A1 after being on 007.A3.
Going to take a break from trying things for a day or so because it's frustrating. Arrghh.
And thanks for the help!

Badger50 said:
I don't think so, but I suppose anything is possible. I've left magisk modules intact before, but never had the trouble like your having. Shoot, you might even try flashing a different factory image image other than what was recommended by google. People seem to have had the best luck with the .012.A1 version which is supposedly for AT&T only.
Click to expand...
Click to collapse
I did one final thing and it worked...I flashed your patched boot.img from here and it worked. Was it .012.A1? What version of Magisk Manager are you using?

DoughMucker said:
I did one final thing and it worked...I flashed your patched boot.img from here and it worked. Was it .012.A1? What version of Magisk Manager are you using?
Click to expand...
Click to collapse
Yep, that was from the .012.A1 factory image. I'm using stable magisk. Question, did you have dm-verity checked off before you patched the boot.img, and, did you disable all magisk modules before you patched and flashed the boot.img? Either way, I'm glad you got it to boot up :good::good:

Badger50 said:
Yep, that was from the .012.A1 factory image. I'm using stable magisk. Question, did you have dm-verity checked off before you patched the boot.img, and, did you disable all magisk modules before you patched and flashed the boot.img? Either way, I'm glad you got it to boot up :good::good:
Click to expand...
Click to collapse
The first time I successfully patched the November boot.img I did not check off dm-verity. I didn't either for the first time(s) I tried the December image. I only tried, unsuccessfully, with dm-verity checked after you mentioned it here.
I did have the Systemless Hosts module enabled when patching the December image. This is what I was referring to earlier when I mentioned I thought it was related to systemless hosts for adaway. I actually didn't realize that when you enabled that in Magisk Manager, that it installed a module. So I never thought I had a module active, but I did.

To end this saga...after getting root again, I did a Titanium Backup, Factory Reset, and re-rooted by patching boot.img again with Magisk Manager canary. It went smoothly, as it should have originally. Now to restore....

This error seems to occur when you flash a boot.img that doesn't match the exact firmware version.
=> Download the correct, currently installed full firmware package, extract the boot.img and flash it.

Solution
This occurs when you're on Android 11 build and try to install the Android 10 build.
There's a simple fix though, thankfully.
Download the Android 10 ota image for Pixel 4 XL from google, and extract the dtbo.img from it. Flash it using
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
If that doesn't work, you can flash the whole stock Android 10 build and then you can boot whatever you were trying to.
Please click "Thanks" if this worked for you so that others can see.

Same Issue on Pixel 3a XL - please Help
DoughMucker said:
Hi,
I'm coming from a rooted November image for my Pixel 4XL and am having trouble getting the December magisk_patched.img to take. I've successfully applied google stock December image, rebooted to Android, patched boot.img with magisk, but when I try to flash magisk_patched.img in fastboot, it flashes, but reboots to fastboot with "error boot prepare" displayed. Flashing stock boot.img gets back to Android without issue (but no root).
I've tried flashing with both cmd and powershell. I've tried "fastboot flash boot magisk_patched.img" (and also fastboot flash boot_a magisk_patched.img and fastboot flash boot_b magisk_patched.img). I'm using Magisk Manager 7.4.
Not sure what else to try. I'd rather not do a factory reset at this point.
Any suggestions?
Click to expand...
Click to collapse
Pixel 3aXL with LineageOS 17
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
I am stuck in Fastboot now. No ADB Connection.
How can I get out of that?
I used the boot.img from the firmware I built Lineage on. Should I use a boot.img from LineageOS .zip?
What is dm-verity?
Can I get to my previous unrooted device?
''bootslot: b
enter reason: error boot prepare''

dadu1257 said:
Pixel 3aXL with LineageOS 17
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
I am stuck in Fastboot now. No ADB Connection.
How can I get out of that?
I used the boot.img from the firmware I built Lineage on. Should I use a boot.img from LineageOS .zip?
What is dm-verity?
Can I get to my previous unrooted device?
''bootslot: b
enter reason: error boot prepare''
Click to expand...
Click to collapse
Post your question on the Pixel 3a XL 'Question and Answer' thread, not the Pixel 4 XL 'Question and Answer' thread.
or
Post your question on the LineageOS 17 thread.