Related
Hi Guys,
Hoping you can help me with this.
I was originally running Slimkat 4.4.4 and had the latest TWRP installed.
I downloaded the file for LPX13D and extracted all of the files right down to the Flash-all.bat and the images for bootloader, radio, and the system.
I ran the Flash-all.bat, and it installed everything successfully. The device booted, and voila, I am on 5.0 now.
The problem now, is that when I reboot into recovery, I am instead met with the little android guy laying on his back, with a red triange/exclamation point in his chest.
No problem, I say to myself. I'll just flash TWRP manually.
So I go to the bootloader, and try the command fastboot flash recovery recovery.img (renamed to make it faster to type.)
It goes through the motions, and says it was successful.
But when I go to recovery, it's the same red triange guy still.
I tried pressing volume up, power+volume up, etc. No dice. After about 30 seconds, it reboots on it's own back to system.
When I connect it to the Nexus Root Toolkit, and click on Flash recovery, and then choose TWRP latest, I get a window that pops up that tells me :
______
File Dependency Download
Status: Stock Kernel: Not Present - Need to download (this is in red)
Then a button that says "Download + Update All File Dependencies"
So what's my best option here? Should I let the NRT update the dependencies?
Try to flash cwm and tell me what happens
Isus <3 said:
Try to flash cwm and tell me what happens
Click to expand...
Click to collapse
D:\DOWNLOADS>fastboot flash recovery cwm.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11312 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.491s
D:\DOWNLOADS>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I then selected recovery, and lo and behold, it worked! I'm in CWM.
So then i flashed TWRP again, and now it's working properly too.
I don't know why it refused to work the first time, but now it seems to be okay. How strange.
Thanks for your time and help. I appreciate it.
deleted
Stupendousman2012 said:
D:\DOWNLOADS>fastboot flash recovery cwm.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11312 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.491s
D:\DOWNLOADS>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I then selected recovery, and lo and behold, it worked! I'm in CWM.
So then i flashed TWRP again, and now it's working properly too.
I don't know why it refused to work the first time, but now it seems to be okay. How strange.
Thanks for your time and help. I appreciate it.
Click to expand...
Click to collapse
Twrp is not optimized yet well like cwm is for andorid l
Recovery won't work AT ALL no matter what you do until you reflash a KK userdata.img, which also wipes all data in the process.
Lethargy said:
I flashed the new developer preview for 5 minutes or so then went to revert. Recovery wouldn't boot not matter what I flashed, until I flashed a KK userdata.img. So it seems like the new developer preview changes the internal storage/data partition more then the old one.
Click to expand...
Click to collapse
Don't try getting around it. Nothing to do with anything else.
Isus <3 said:
Twrp is not optimized yet well like cwm is for andorid l
Click to expand...
Click to collapse
What? CWM is outdated.
Lethargy said:
Recovery won't work AT ALL no matter what you do until you reflash a KK userdata.img, which also wipes all data in the process.
Don't try getting around it. Nothing to do with anything else.
What? CWM is outdated.
Click to expand...
Click to collapse
Well, Twrp worked until I rebooted and then tried going back to it. Then bam! back to the error dude with the triangle.
So, I flashed cwm again, and that one seems to be persisting after a reboot, so I guess I'm stuck with cwm for now....
I also flashed the boot.img and the supersu update to get root working, and it seems to be going well now.
Cwm tells me that I may have lost root immediately after flashing the supersu update, but when I reboot, root is actually working. What a weird bunch of crap to go through.
Stupendousman2012 said:
Well, Twrp worked until I rebooted and then tried going back to it. Then bam! back to the error dude with the triangle.
Click to expand...
Click to collapse
Flash userdata.img and your TWRP will work properly.
Stupendousman2012 said:
So, I flashed cwm again, and that one seems to be persisting after a reboot, so I guess I'm stuck with cwm for now....
Click to expand...
Click to collapse
It isn't whether its persisting or not. TWRP just won't boot properly until you reflash a KK userdata.img. I don't know why CWM would even boot up, nor why anyone would want to really use it anyways.
Stupendousman2012 said:
Cwm tells me that I may have lost root immediately after flashing the supersu update, but when I reboot, root is actually working. What a weird bunch of crap to go through.
Click to expand...
Click to collapse
It says that because CWM is outdated.
Lethargy said:
Flash userdata.img and your TWRP will work properly.
It isn't whether its persisting or not. TWRP just won't boot properly until you reflash a KK userdata.img. I don't know why CWM would even boot up, nor why anyone would want to really use it anyways.
It says that because CWM is outdated.
Click to expand...
Click to collapse
Okay:
So I extract the userdata from a 4.4.4 stock image, yes? If not, can you point me in the direction of the correct userdata.img
I assume the correct order and syntax is:
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastbook flash recovery twrp.img
Fastboot reboot-bootloader
Select recovery
Wipe data/Factory reset, and then and reboot system.
Set up phone as normal.
Have I overlooked anything?
Stupendousman2012 said:
Okay:
So I extract the userdata from a 4.4.4 stock image, yes? If not, can you point me in the direction of the correct userdata.img
I assume the correct order and syntax is:
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastbook flash recovery twrp.img
Fastboot reboot-bootloader
Select recovery
Wipe data/Factory reset, and then and reboot system.
Set up phone as normal.
Have I overlooked anything?
Click to expand...
Click to collapse
Yeah. Don't need to boot into recovery and wipe data since flashing a .img with fastboot while in bootloader erases it first then flashes. Just make sure you backup your stuff, including internal storage, off to a PC first if you have anything important.
Until L is officially released, we're using the below thread
http://forum.xda-developers.com/show....php?t=2796217
Android "L" Developer Preview Help, Troubleshooting, Q&A
Sent from my Nexus 5 using Tapatalk
I wanted to flash the latest update of RR7 but when i tried to get into the recovery the phone would reboot and show the twrp starting screen and then it would reboot again and start normally. I figured something must have gone wrong and reflashed twrp from my pc, however the issue persists. Flashify doesn't work either. So aside from a clean install, is there a workaround?
BoredDude said:
I wanted to flash the latest update of RR7 but when i tried to get into the recovery the phone would reboot and show the twrp starting screen and then it would reboot again and start normally. I figured something must have gone wrong and reflashed twrp from my pc, however the issue persists. Flashify doesn't work either. So aside from a clean install, is there a workaround?
Click to expand...
Click to collapse
You can try to boot directly into twrp with "fastboot boot TWRP.img"
zys52712 said:
You can try to boot directly into twrp with "fastboot boot TWRP.img"
Click to expand...
Click to collapse
Just tried it, same thing happens i can see the twrp starting screen but i can get to the main menu.
EDIT.
Changed the twrp version to an older one. No results, tried both flashing and booting from fastboot.
i get the following message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp2.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14796 KB)...
OKAY [ 0.479s]
writing 'recovery'...
OKAY [ 1.566s]
finished. total time: 2.049s
zys52712 said:
You can try to boot directly into twrp with "fastboot boot TWRP.img"
Click to expand...
Click to collapse
BoredDude said:
Just tried it, same thing happens i can see the twrp starting screen but i can get to the main menu.
EDIT.
Changed the twrp version to an older one. No results, tried both flashing and booting from fastboot.
i get the following message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp2.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14796 KB)...
OKAY [ 0.479s]
writing 'recovery'...
OKAY [ 1.566s]
finished. total time: 2.049s
Click to expand...
Click to collapse
Then something is really wrong with your internal memory. Because that boot command in the post above does not use TWRP installed on your phone, it's a "temporary" TWRP booted from your PC folder.
Even if you've never installed TWRP on your phone (still have stock recovery) you can still boot to TWRP for a one-time/one-off session by using those commands. Do whatever you want, like install SuperSu, and when you reboot, you'll still have stock recovery!
ChazzMatt said:
Then something is really wrong with your internal memory. Because that boot command in the post above does not use TWRP installed on your phone, it's a "temporary" TWRP booted from your PC folder.
Even if you've never installed TWRP on your phone (still have stock recovery) you can still boot to TWRP for a one-time/one-off session by using those commands. Do whatever you want, like install SuperSu, and when you reboot, you'll still have stock recovery!
Click to expand...
Click to collapse
I fixed it erasing the TWRP folder in my internal storage
I tried to root by flashing the patched boot image as describe in https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280. After that, the phone went into a bootloop.
When I get to the eRecovery screen, I tried 'Download latest version and recovery.' It got to 'getting package information from server' but then stopped with 'getting package info failed.'
I then tried 'Wipe data/factory reset' and it rebooted but nothing changed.
I don't know what else to try with this phone. None of the current versions of twrp would run on it. I've never bricked a device in years of rooting.
thecdn said:
I tried to root by flashing the patched boot image as describe in https://forum.xda-developers.com/ho...gisk-root-honor-view-10-mate-10-pro-t3749280. After that, the phone went into a bootloop.
When I get to the eRecovery screen, I tried 'Download latest version and recovery.' It got to 'getting package information from server' but then stopped with 'getting package info failed.'
I then tried 'Wipe data/factory reset' and it rebooted but nothing changed.
I don't know what else to try with this phone. None of the current versions of twrp would run on it. I've never bricked a device in years of rooting.
Click to expand...
Click to collapse
You need to restore your original ramdisk. Also, you have to patch your own ramdisk.img with Magisk Manager if you want to try rooting your device.
And btw, this is a development forum, not General or Q&A one. Read carefully before trying to mod this device, or you will end up with an expensive brick.
please contact me on hangouts i may be able to help [email protected]
You can download the appropriate images to restore your device below. These are for the US variant (BKL-L04)
https://drive.google.com/open?id=1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
Edit: Link updated
[email protected]_USA said:
You can download the appropriate images to restore your device below. These are for the US variant (BKL-L04)
https://drive.google.com/open?id=1kf...yiH2t-srYBBvN3
Click to expand...
Click to collapse
I"m getting a web page not found 404 when I try that link.
thecdn said:
I"m getting a web page not found 404 when I try that link.
Click to expand...
Click to collapse
Same
thecdn said:
I"m getting a web page not found 404 when I try that link.
Click to expand...
Click to collapse
freeza said:
Same
Click to expand...
Click to collapse
look like chris didnt updated the link,
bdw here you guys go https://drive.google.com/open?id=1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
I flashed the system.img and the recovery_ramdisk.img. It booted to the eRecovery screen again.
I tried 'Download latest version and recovery' and it failed with the 'getting package info failed' error again.
I then tried 'Wipe data/factory reset' and unlike before, it actually went through and said it was successfully completed. But then it rebooted twice and went back to the eRecovery screen again.
Any ideas on how to proceed from here?
ETA: When I pressed vol up/power after this it went to a screen which said 'software install failed' instead of the recovery screen I thougt it would go to. After the first time, pressing vol up/power goes to the EMUI screen with the options of 'Reboot' 'Wipe data/factory reset' and 'Wipe cache partition.'
thecdn said:
I flashed the system.img and the recovery_ramdisk.img. It booted to the eRecovery screen again.
I tried 'Download latest version and recovery' and it failed with the 'getting package info failed' error again.
I then tried 'Wipe data/factory reset' and unlike before, it actually went through and said it was successfully completed. But then it rebooted twice and went back to the eRecovery screen again.
Any ideas on how to proceed from here?
ETA: When I pressed vol up/power after this it went to a screen which said 'software install failed' instead of the recovery screen I thougt it would go to. After the first time, pressing vol up/power goes to the EMUI screen with the options of 'Reboot' 'Wipe data/factory reset' and 'Wipe cache partition.'
Click to expand...
Click to collapse
You need to restore ramdisk, not recovery_ramdisk.
Pretoriano80 said:
You need to restore ramdisk, not recovery_ramdisk.
Click to expand...
Click to collapse
I did 'fastboot flash ramdisk ramdisk.img' and it still does a couple of reboots and then goes back to the EMUI screen with the recovery/reset/reboot/shutdown options.
In summary, this morning I did:
'fastboot flash system system.img' which resulted in 7 occurances of 'sending sparse system x/7 (xxxx KB)...' - which I have never seen before but all finished with OKAY
'fastboot flash recovery_ramdisk recovery_ramdisk.img'
'fastboot flash ramdisk ramdisk.img'
Is there something else I could do or redo in a particular order?
thecdn said:
I did 'fastboot flash ramdisk ramdisk.img' and it still does a couple of reboots and then goes back to the EMUI screen with the recovery/reset/reboot/shutdown options.
In summary, this morning I did:
'fastboot flash system system.img' which resulted in 7 occurances of 'sending sparse system x/7 (xxxx KB)...' - which I have never seen before but all finished with OKAY
'fastboot flash recovery_ramdisk recovery_ramdisk.img'
'fastboot flash ramdisk ramdisk.img'
Is there something else I could do or redo in a particular order?
Click to expand...
Click to collapse
Try to also flash kernel : fastboot flash kernel kernel.img
Pretoriano80 said:
Try to also flash kernel : fastboot flash kernel kernel.img
Click to expand...
Click to collapse
No joy yet but I do appreciate all the help.
thecdn said:
No joy yet but I do appreciate all the help.
Click to expand...
Click to collapse
Did you tried a factory reset from stock recovery?
Pretoriano80 said:
Did you tried a factory reset from stock recovery?
Click to expand...
Click to collapse
I've tried two factory resets after completing the above mentioned actions. Both times reported they were successful it still won't boot to the os, goes to the EMUI screen after several boot attempts.
Same problem here on a US BKL-L04 =(
I flashed a magisk modified ramdisk.img and have been in bootloop ever since.
I've downloaded and flashed recovery_ramdisk.img, ramdisk.img, and kernel.img from the link earlier in this thread: https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
I've then did "Wipe data/factory reset" from Huawei eRecovery - no luck
$ fastboot flash ramdisk ramdisk.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (16384 KB)...
OKAY [ 0.401s]
writing 'ramdisk'...
OKAY [ 0.083s]
finished. total time: 0.484s
$ fastboot flash recovery_ramdisk recovery_ramdisk.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 0.807s]
writing 'recovery_ramdisk'...
OKAY [ 0.164s]
finished. total time: 0.971s
sek stock2 $ fastboot flash kernel kernel.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.615s]
writing 'kernel'...
OKAY [ 0.128s]
finished. total time: 0.745s
Aside from fastboot happing very quickly (< 1 second even for 32 meg recovery_ramdisk.img) everything seems to work fine... The phone just no longer boots - it trys a few times - displaying the "Your device has been unlocked and can't be trusted" screen for quite a while and the non-animated blue honor screen briefly and then ends up in EMUI eRecovery.
Are these files still up to date? Or perhaps there were newer versions on my phone and that's why flashing the older ones isn't working?
Also worth noting, I'm flashing from a mac with Android sdk fastbook:
$ fastboot --version
fastboot version 0.0.1-4500957
Installed as /Users/sek/Library/Android/sdk/platform-tools/fastboot
Thanks for any help / tips!
akasek said:
I flashed a magisk modified ramdisk.img and have been in bootloop ever since.
I've downloaded and flashed recovery_ramdisk.img, ramdisk.img, and kernel.img from the link earlier in this thread: https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
I've then did "Wipe data/factory reset" from Huawei eRecovery - no luck
$ fastboot flash ramdisk ramdisk.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (16384 KB)...
OKAY [ 0.401s]
writing 'ramdisk'...
OKAY [ 0.083s]
finished. total time: 0.484s
$ fastboot flash recovery_ramdisk recovery_ramdisk.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 0.807s]
writing 'recovery_ramdisk'...
OKAY [ 0.164s]
finished. total time: 0.971s
sek stock2 $ fastboot flash kernel kernel.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.615s]
writing 'kernel'...
OKAY [ 0.128s]
finished. total time: 0.745s
Aside from fastboot happing very quickly (< 1 second even for 32 meg recovery_ramdisk.img) everything seems to work fine... The phone just no longer boots - it trys a few times - displaying the "Your device has been unlocked and can't be trusted" screen for quite a while and the non-animated blue honor screen briefly and then ends up in EMUI eRecovery.
Are these files still up to date? Or perhaps there were newer versions on my phone and that's why flashing the older ones isn't working?
Also worth noting, I'm flashing from a mac with Android sdk fastbook:
$ fastboot --version
fastboot version 0.0.1-4500957
Installed as /Users/sek/Library/Android/sdk/platform-tools/fastboot
Thanks for any help / tips!
Click to expand...
Click to collapse
Flash stock kernel, ramdisk and recovery ramdisk for your model in fastboot and you'll be able to boot again
Rommco05 said:
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Use this tool for flash full fw
Click to expand...
Click to collapse
Thanks for the info, that tool looks interesting. Where can I get the stock files for BKL-L04 US version Honor View 10?
I have now tried flashing kernel, ramdisk, recovery_ramdisk and system from both of these sources:
- https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
- http://arter97.com/browse/v10/stock/BKL-L04/
They all appear to flash fine. I tried flashing vendor.img as well, but get an error on that:
$ fastboot flash vendor vendor.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magic
sending sparse 'vendor' 1/2 (445713 KB)...
OKAY [ 9.718s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 9.724s
It still doesn't want to boot. I end up in eRecovery each time.
I am able to flash TWRP from Pretoriano80: https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917
It seems to be working properly, perhaps that helps me somehow?
Finally back up and running - Thanks Tecalote!
FYI: I am finally back up and running - Tecalote's post worked perfectly (and BKL-L04 update zips are linked earlier in the thread also): https://forum.xda-developers.com/showpost.php?p=76331841&postcount=46
akasek said:
Thanks for the info, that tool looks interesting. Where can I get the stock files for BKL-L04 US version Honor View 10?
I have now tried flashing kernel, ramdisk, recovery_ramdisk and system from both of these sources:
- https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
- http://arter97.com/browse/v10/stock/BKL-L04/
They all appear to flash fine. I tried flashing vendor.img as well, but get an error on that:
$ fastboot flash vendor vendor.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magic
sending sparse 'vendor' 1/2 (445713 KB)...
OKAY [ 9.718s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 9.724s
It still doesn't want to boot. I end up in eRecovery each time.
I am able to flash TWRP from Pretoriano80: https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917
It seems to be working properly, perhaps that helps me somehow?
Click to expand...
Click to collapse
akasek said:
Thanks for the info, that tool looks interesting. Where can I get the stock files for BKL-L04 US version Honor View 10?
I have now tried flashing kernel, ramdisk, recovery_ramdisk and system from both of these sources:
- https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
- http://arter97.com/browse/v10/stock/BKL-L04/
They all appear to flash fine. I tried flashing vendor.img as well, but get an error on that:
$ fastboot flash vendor vendor.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magic
sending sparse 'vendor' 1/2 (445713 KB)...
OKAY [ 9.718s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 9.724s
It still doesn't want to boot. I end up in eRecovery each time.
I am able to flash TWRP from Pretoriano80: https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917
It seems to be working properly, perhaps that helps me somehow?
Click to expand...
Click to collapse
try to install twrp and then do hruupdate from twrp
get your files from firmware finder and search xda forums to how to install those files
its very easy and your system will be back in stock format
after that you can try to root and install custom rom
thecdn said:
No joy yet but I do appreciate all the help.
Click to expand...
Click to collapse
Hi, what helped you there? I have a similar situation.
"Hi,
I need some advice on what can be done with my Honor View10 as it keeps gracing a bootloop followed by fasrboot mode.
Mine is a C675 variant and I was on 190 when I decided to unroot and update the device to 218. Once that was done, I flashed a patched recovery_ramdisk boot image that was patched using magisk to support it. Worked fine. Did a reboot and it got stuck in a bootloop.
I have tried flashing other patch.imgs too, due instance tried extracting recovery.img of the current version of rom, flashed it, no luck!
Tried flashing the patched version of that, still did not help.
I am on EMUI9, any help please?
Also can anyone help me with the link of one of the latest versions of C675 update please? "
This is what happened to me
So I have been trying to flash the Pixel Factory Image, I have used the most recent SDK Platform Tools and I still can't get past the boot loop. I also have tried to flash the TWRP recovery but I am getting this:
Code:
C:\Users\MyName\Documents\Pixel\minimal_adb_fastboot_1.4.3_portable>fastboot flash recovery twrp-3.3.0-0-sailfish.img
target reported max download size of 536870912 bytes
sending 'recovery' (31000 KB)...
OKAY [ 0.828s]
writing 'recovery'...
(bootloader) Flashing active slot "_b"
FAILED (remote: partition [recovery] doesn't exist)
finished. total time: 0.938s
I have even tried but the bootloop is still there:
Code:
PS C:\Users\MyName\Documents\Pixel\minimal_adb_fastboot_1.4.3_portable> ./fastboot boot twrp-3.3.0-0-sailfish.img
downloading 'boot.img'...
OKAY [ 0.727s]
booting...
OKAY [ 1.010s]
finished. total time: 1.740s
There are a couple things wrong here:
Pixels don't have a recovery partition, everything happens in the boot one (root, twrp, custom kernel)
The first command in the first code block you wrote is wrong because the recovery partition is not there. In case you wanna flash a stock boot image, maybe for recover your device faulty kernel/twrp etc, without have to reflash the whole rom, the command should be "fastboot flash boot boot.img"
The command you sent in the second code block (./fastboot boot twrp-3.3.0-0-sailfish.img) in fact is correct because you just boot the twrp image (= no errors).
But when you wanna flash the recovery, you have to boot the twrp img and when it booted you have to flash the twrp.zip that you can download from the official site from the twrp screen, not the .img
Hope this helps
I'll add that you should also use the official platform-tools downloaded from Google. The minimal (and other alternatives) can give you problems when trying to flash.
The latest platform-tools is here. Note that Google hasn't updated the changelog, and the latest version is actually 28.0.3, not 28.0.2.
For TWRP, you need both the latest .img and .zip files from here, and transfer the .zip file to the Pixel. Use the boot command to boot from the .img, then from within the temporarily-booted TWRP install the .zip file.
Hi all, I just updated to April 2020 firmware with no issues. Just waiting on a Kirisakura update and we'll be right back to where we left off. =)
edit: nevermind, Kirisakura 4.2.0 works perfectly fine!
In case anyone is looking for them, here is the stock and Magisk Patched boot images:
Magisk v20.4 patched boot image: https://www.androidfilehost.com/?fid=4349826312261763705
Stock boot image: https://www.androidfilehost.com/?fid=4349826312261763704
I'll also post my update procedure in case it helps anyone else out. This was my first OTA on this device (just got it last month), and I was able to update with absolutely no problems, no loss of root, no need to change Magisk or EdXposed settings/modules/etc. SafetyNet still passes, etc. Very seamless and I'm definitely happy with going with a Pixel as my next device. =D Will be doing my wife's phone next (regular Pixel 4) and I'll probably do a separate post on those forums with the boot images and stuff.
This is ONLY for QQ2A.200405.005 firmware - it goes without saying, PLEASE ONLY FLASH IF YOU KNOW WHAT YOU'RE DOING.
UPDATE PROCEDURE (using a PC. I know there are other posts covering other methods, but this was the fastest, easiest, most reliable and intuitive way for me, and I didn't need to do any additional research, so I chose to do it this way)
** I was previously on March 2020 firmware and these steps therefore correspond as such.
I DID NOT BOOT BACK INTO O/S UNTIL ALL STEPS WERE COMPLETED - I DID THIS TO ENSURE EVERYTHING WOULD BOOT BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
this may not be necessary, but I didn't want to find out, plus this was the quickest and most intuitive way for me anyway.
1. boot into bootloader
----------------
** I was on Kirisakura kernel, so I needed to flash BOTH the stock boot and dtbo March 2020 images - make sure you flash the proper corresponding images to your current pre-update firmware.
2. fastboot flash boot boot.img
3. fastboot flash dtbo dtbo.img
- these steps to restore stock recovery, dtbo.img also necessary for some kernel installations
-----------------
4. use volume keys to change selection to boot to Recovery Mode
* when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-qq2a.200405.005-e9ad5990.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-qq2a.200405.005-magisk_patched-20.4.img
9. done, start the phone
This was a 100% seamless update that required no additional / re-setup of any of my Magisk or EdXposed setups. So far, no issues at all for both me and my wife's phone (P4 XL and P4). Magisk and Xposed are playing nice with these builds so far.
All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
Edit: To be nice to the noobs, and also because I have nothing better to do at this moment thanks to the pandemic, here are the stock boot and dtbo images (FOR MARCH 2020) as well as a direct link to the April 2020 OTA zip:
coral-qq2a.200305.003-factory-dtbo.img: https://www.androidfilehost.com/?fid=4349826312261763739
coral-qq2a.200305.003-factory-boot.img: https://www.androidfilehost.com/?fid=4349826312261763738
April 2020 OTA Zip from Google: https://dl.google.com/dl/android/aosp/coral-ota-qq2a.200405.005-e9ad5990.zip
8. fastboot flash boot coral-qq2a.200405.005-magisk_patched-20.4.img
thx. fast, safe, root retained.
This makes me lol. You got Kirisakura and dirtly flash the whole stuff and don't get any problem
Nice. I did it the safe way with disabling everything, I hate bootloops^^
lapapunk said:
8. fastboot flash boot coral-qq2a.200405.005-magisk_patched-20.4.img
thx. fast, safe, root retained.
Click to expand...
Click to collapse
Thanks, fixed it lol. I typed it all up really quick from memory, whoops. In my head there was definitely "boot" in there =)
Morgrain said:
This makes me lol. You got Kirisakura and dirtly flash the whole stuff and don't get any problem
Nice. I did it the safe way with disabling everything, I hate bootloops^^
Click to expand...
Click to collapse
Yeah, I mean essentially flashing the stock boot and dtbo reverts the kernel back to stock. Then I figure if I ended up with bootloop, it's just a matter of either booting into Magisk core mode, or flashing the factory boot image at worst and working from there. Either way, since I'm doing the update from / with access to my computer, the risk isn't too big. Definitely would think twice if I were doing it away from home without my computer (which no one should be right now anyway! STAY AT HOME!!!) =)
omg
thank you for this, i have been trying to flash the factory image and getting it stuck at the boot screen, nothing would help
followed this to a T and its working... back up and running
So thank you!
Thank you!
Thank you, @i5lee8bit, for this very useful and detailed guide. Needless to say, it worked a treat. Much appreciated and many thanks! :good:
Thanks for your files and guide, it worked superb.
Working great!
Ty!
Bruh this really worked been looking for an easy way of updating. Thanks a million!
the Guide works fine
Thank you[emoji106]
Gesendet von meinem Pixel 4 XL mit Tapatalk
Just updated! Thanks man, this is definitely the easiest method of updating while rooted.
Hmm, I always have to do it like this x.x
Code:
D:\Downloads>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.645s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 1.721s
D:\Downloads>fastboot flash dtbo dtbo.img
target reported max download size of 268435456 bytes
sending 'dtbo' (8192 KB)...
OKAY [ 0.305s]
writing 'dtbo'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 0.380s
D:\Downloads>fastboot flash boot_a boot.img
target reported max download size of 268435456 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 1.645s]
writing 'boot_a'...
OKAY [ 0.662s]
finished. total time: 2.310s
D:\Downloads>fastboot flash boot_b boot.img
target reported max download size of 268435456 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.646s]
writing 'boot_b'...
OKAY [ 0.532s]
finished. total time: 2.180s
D:\Downloads>fastboot flash dtbo_a dtbo.img
target reported max download size of 268435456 bytes
sending 'dtbo_a' (8192 KB)...
OKAY [ 0.305s]
writing 'dtbo_a'...
OKAY [ 0.194s]
finished. total time: 0.501s
D:\Downloads>fastboot flash dtbo_b dtbo.img
target reported max download size of 268435456 bytes
sending 'dtbo_b' (8192 KB)...
OKAY [ 0.305s]
writing 'dtbo_b'...
OKAY [ 0.194s]
finished. total time: 0.501s
hans_meier said:
Hmm, I always have to do it like this x.x
Click to expand...
Click to collapse
I would try keeping all your fastboot files in your platform tools folder
I'm stuck on Jan 20 ota and gets any any new updates? Would this fix my issue? Does this wipe data?
qman66 said:
I'm stuck on Jan 20 ota and gets any any new updates? Would this fix my issue? Does this wipe data?
Click to expand...
Click to collapse
I just got the phone last month so I haven't tried jumping multiple security patches. Nor am I sure whether official updates normally would jump or whether they're incremental.
IF official updates can normally jump (skip updates inbetween), then I would imagine you just need to flash the January 2020 stock boot / dtbo images and follow the guide just as it's posted. Just download the correct Factory Image that you're currently on (FACTORY IMAGE, not Full OTA Image), which will have the stock untouched boot / dtbo images. You can get it here: https://developers.google.com/android/images
This method does NOT in any way wipe data. However, you would wanna ask someone who's owned the phone longer whether you can normally jump multiple OTA patches.
sharpz811 said:
I would try keeping all your fastboot files in your platform tools folder
Click to expand...
Click to collapse
Also, not sure if @hans_meier is using an older platform tools version, but I'm pretty sure when you run those fastboot flash commands, it should just flash the currently selected slot. Maybe older versions of the platform tools don't have such logic built in so you need to flash each slot manually? This is all speculation and I haven't tested (and won't bother, lol). With my guide, it's basically flashing the boot / dtbo partitions of the active slot, and then the adb sideload ota.zip is just the standard mechanism of sideloading an OTA zip on A/B devices which installs to the alternate slot, hence why next time you reboot into bootloader, it has the other slot selected, so when you flash the magisk patched boot image as the final step the correct slot is already selected. Run-on sentence ftw
Finally, if you already have Minimal ADB and Fastboot (or in my case, even HTC Sync Manager!), you'll want to uninstall those and just use the latest platform tools from Google (https://developer.android.com/studio/releases/platform-tools). They also modify the Environment Variables (in Windows systems at least) so when you run your adb/fastboot commands, the other versions will fight and try to run. Often the case when you see adb server doesn't match client type errors.
@hans_meier, I highly recommend just downloading the latest platform tools, extracting them to an accessible location on your PC, and then setting up the Environment Variable (start - just type in the word "environment" and click the control panel item that shows up (OR) start - sysdm.cpl - advanced tab - environment variables...). Add the path to the platform tools folder to the "Path" variable. You'll need to log off and back in, then you can run the commands from any directory in cmd prompt. Again, the Minimal ADB and Fastboot package, and possibly other 3rd party Android OEM tools, tend to add environment paths to their own folders, which can cause issues when trying to use your own adb/fastboot packages.
Just updated from January.
No issue with skipping releases if using the full image (probably an issue with an OTA).
To do so, download full factory image, extract, edit "flashall.bat" to remove the "-w" flag (which will wipe your phone), then run flashall.bat with the phone on the bootloader (make sure to disable magisk modules prior to putting into the bootloader for safety).
Will update everything to the latest image (in this case April) and then restart back into the OS.
Then reboot back to bootloader to flash the latest magisk image, reboot into the OS, and install a custom kernel via EX KM if desired.
So, i made it myself (was just rooting, so i did all the steps, including the mandatory wipe).
After flashing it my phone bootlooped, so my instinct was to flash the factory image, which errored when sending the sparce vendor file, so my phone was "corrupetd".
I then read about trying A to C cable, instead of the stock C to C, and that worked. (got back to the initial setup screen).
Flashed my modified boot again, bootloop again. (maybe doing it or transfering it with the c to c cable?).
I then flashed yours, no bootloop.
After initial setup Magisk Manager is not there, i am letting my phone restore everything for now.
cocchiararo said:
So, i made it myself (was just rooting, so i did all the steps, including the mandatory wipe).
After flashing it my phone bootlooped, so my instinct was to flash the factory image, which errored when sending the sparce vendor file, so my phone was "corrupetd".
I then read about trying A to C cable, instead of the stock C to C, and that worked. (got back to the initial setup screen).
Flashed my modified boot again, bootloop again. (maybe doing it or transfering it with the c to c cable?).
I then flashed yours, no bootloop.
After initial setup Magisk Manager is not there, i am letting my phone restore everything for now.
Click to expand...
Click to collapse
Just flashing the magisk patched boot image won't install Magisk Manager. You need to install that separately. Just go to the Magisk GitHub and download the latest Magisk Manager apk: https://github.com/topjohnwu/Magisk/releases/tag/manager-v7.5.1
can you please make me a core magisk boot image please for dp3?