Database Develop

KTU84P (4.4.4) Updater

Your bootloader must be unlocked to use this. If your bootloader is not already unlocked, unlocking it will wipe your data and this method is not recommended.
This is a modified factory image that will not erase your user data or custom recovery. This can be used even if you’re rooted and with modified system files, xposed framework, or custom recovery. Once installed you will lose root, just flash supersu in your custom recovery. Xposed should still be on your device so just go into the app and re-install it. For any modified system files, you will have to re-modify those.
This is intended for those on the stock rom, rooted, and with a custom recovery. It’ll work if you have a custom rom but will put the stock system on.
I am not responsible for anything you do to your device so flash at your own risk. Always backup before doing any significant changes to your device. I would recommend off your device in case something happens
.
To use, download the modified factory image here http://www.androidfilehost.com/?fid=23578570567717696 Use 7-zip or winrar to extract the files.
Mirror https://mega.co.nz/#!oIohmY7a!ZsTx49c150KlXyfc6igm2RH9J1PMtfJlj2J8y3219Qs
Supersu by chainfire can be found here, CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu
Boot into the bootloader. From a cmd window opened where the flash-all file is just type flash-all. You can use shift, right click on the hammerhead-ktu84p-Modified folder to open a command window in the correct folder.
You can also just double click on the flash-all.bat
This is tested on a windows machine; however it should work on a Mac too, flash the flash-all.sh.

jd1639 said:
Your bootloader must be unlocked to use this. If your bootloader is not already unlocked, unlocking it will wipe your data and this method is not recommended.
This is a modified factory image that will not erase your user data or custom recovery. This can be used even if you’re rooted and with modified system files, xposed framework, or custom recovery. Once installed you will lose root, just flash supersu in your custom recovery. Xposed should still be on your device so just go into the app and re-install it. For any modified system files, you will have to re-modify those.
This is intended for those on the stock rom, rooted, and with a custom recovery. It’ll work if you have a custom rom but will put the stock system on.
I am not responsible for anything you do to your device so flash at your own risk. Always backup before doing any significant changes to your device. I would recommend off your device in case something happens
.
To use, download the modified factory image here http://d-h.st/yMl Use 7-zip or winrar to extract the files.
Mirror coming
Supersu by chainfire can be found here, CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu
Boot into the bootloader. From a cmd window opened where the flash-all file is just type flash-all. You can use shift, right click on the hammerhead-ktu84p-Modified folder to open a command window in the correct folder.
You can also just double click on the flash-all.bat
This is tested on a windows machine; however it should work on a Mac too, flash the flash-all.sh.
Click to expand...
Click to collapse
omg as usual thanks a lot
update: issues with minimal adb with windows 8.1 right now using 15 seconds ADB Installer v1.3
C:\Users\eilegz\adb>flash-all.bat
sending 'bootloader' (2508 KB)...
OKAY [ 0.313s]
writing 'bootloader'...
OKAY [ 0.484s]
finished. total time: 0.797s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
sending 'radio' (45409 KB)...
OKAY [ 2.063s]
writing 'radio'...
OKAY [ 3.133s]
finished. total time: 5.196s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ11k
Baseband Version.....: M8974A-2.0.50.1.16
Serial Number........: 0407b84a215be2a3
--------------------------------------------
checking product...
OKAY [ 0.109s]
checking version-bootloader...
OKAY [ 0.094s]
checking version-baseband...
OKAY [ 0.109s]
sending 'boot' (8700 KB)...
OKAY [ 0.547s]
writing 'boot'...
OKAY [ 0.734s]
erasing 'system'...
OKAY [ 1.143s]
sending 'system' (721400 KB)...
OKAY [ 26.376s]
writing 'system'...
OKAY [ 50.008s]
rebooting...
finished. total time: 79.667s
Press any key to exit...
hopefully everything works

Works great!

Thanks for this easy method it worked like a charm!

Thanks once again one of the easiest if not the easiest way to update!

Awesome! Thanks, dude.
Sent from my Nexus 5 using Tapatalk

Will this work with 4.4.2?

used it on a mac and worked like a charm.

Worked perfect once again. Thank you

That was a little too easy.

Can someone make a flashable updateable zip through twrp. I'm not familiar with flashing though cmd in Windows.
Cheers

is it possible to extract the 1.16 radio and flash seperately or will need to ota to 4.4.4? having horrendous signal issues and need to see if 1.16 will improve that

bosna110 said:
is it possible to extract the 1.16 radio and flash seperately or will need to ota to 4.4.4? having horrendous signal issues and need to see if 1.16 will improve that
Click to expand...
Click to collapse
Get the .zip here:
http://downloads.codefi.re/autoprime/LG/Nexus_5/Modems

jonneepuh said:
Can someone make a flashable updateable zip through twrp. I'm not familiar with flashing though cmd in Windows.
Cheers
Click to expand...
Click to collapse
The OTA? It's here:
http://forum.xda-developers.com/showpost.php?p=53534137&postcount=1891

You sir, are a legend

Grazie, amico.

Wakamatsu said:
Get the .zip here:
http://downloads.codefi.re/autoprime/LG/Nexus_5/Modems
Click to expand...
Click to collapse
Is there a difference radio for the Nexus 5 D820 or the Nexus 5 D821 (Europe and US) version??

wietse1988 said:
Is there a difference radio for the Nexus 5 D820 or the Nexus 5 D821 (Europe and US) version??
Click to expand...
Click to collapse
No, read the OP of the modem thread. Same checksums.

For Mac do you have to change the flash-all.sh putting in it ./ in front of every fastboot command? Is that right?
Thank you.

That was easy Thanks for this. and Kudos for getting this out so quickly.

[Q] Can't reinstall Philz, Stuck on Stock recovery!!

after restoring 5.1 again from Indonesian to Indian.. Philz could not Format my user data or wipe cache.. So I flashed without wiping..and it successfully booted but now I can't find philz Recovery in Recovery mode..it booted to stock! What can I do now?

nand.96 said:
after restoring 5.1 again from Indonesian to Indian.. Philz could not Format my user data or wipe cache.. So I flashed without wiping..and it successfully booted but now I can't find philz Recovery in Recovery mode..it booted to stock! What can I do now?
Click to expand...
Click to collapse
Yes That Backup Rom had stock recovery. if u need philz recovery after installed that rom u can flash philz recovery by Android one Tool Kit available in this forum.

Narasimman91 said:
Yes That Backup Rom had stock recovery. if u need philz recovery after installed that rom u can flash philz recovery by Android one Tool Kit available in this forum.
Click to expand...
Click to collapse
i tries android one toolkit.. it is not recognizing my device.. i tried minimal adb.. it recognizes my device... i also went to fastboot ..gave flash recovery command.. it also said succes saying all this-->
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (6626 KB)...
OKAY [ 0.202s]
writing 'recovery'...
OKAY [ 0.400s]
finished. total time: 0.618s
C:\Program Files\Minimal ADB and Fastboot>fastboot reboot
.. but after reboot i m again on stock.. No philZ! plzz help

nand.96 said:
i tries android one toolkit.. it is not recognizing my device.. i tried minimal adb.. it recognizes my device... i also went to fastboot ..gave flash recovery command.. it also said succes saying all this-->
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (6626 KB)...
OKAY [ 0.202s]
writing 'recovery'...
OKAY [ 0.400s]
finished. total time: 0.618s
C:\Program Files\Minimal ADB and Fastboot>fastboot reboot
.. but after reboot i m again on stock.. No philZ! plzz help
Click to expand...
Click to collapse
First Download fastboot unlock scripts. (attached zip file)
1.extract that file
2.press shift key and mouse right key and then select open command here
3. reboot into fastboot mode on ur phone
4. connect to ur phone via usb
5. then type following command: fastboot oem unlock and fastboot format userdata
after did above method andorid one tool kit detect ur phone
now u can flash philz recovery.

Thanks.. Flashed PhilZ successfully! But i can't Root my device using philz now... I tried Adb sideload ,installing zip directly of supersu..zip What can i do now?

Download the latest supersu.zip,google it, then flast it uaing philz recovery.Only the latest supersu.zip can root ur phone as other versions does not support android 5.1

Yes. Flash not less than v2.45 of SuperSU zip as they won't work. I have flashed v2.45 currently n it works fine..

Cannot update from cyanogen recovery to twrp recovert

Hello,
I am trying to update from the old cyanogen recovery to the TWRP recovery in this post: https://forum.xda-developers.com/showthread.php?t=3557606
I have enable to write the cyanogen recovery in the developer options.
I have rebooted into flashboot and executed:
----
[email protected]:/tmp/xperia/TWRP# adb reboot bootloader
[email protected]:/tmp/xperia/TWRP# fastboot flash recovery twrp-3.1.1-0-z3c_V02.img
target didn't report max-download-size
sending 'recovery' (14296 KB)...
OKAY [ 0.572s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.502s
[email protected]:/tmp/xperia/TWRP# fastboot reboot
rebooting...
----
Unfortunately the system boots in the cyanogen recovery anyhow.
does anyone knows what am I doing wrong ?
Many thanks in advance

There's an app called NDR Utils that lets you choose which recovery to boot to, but I don't know of a clean link where you can get it.
I got it with Nut's Dual Recovery:
http://nut.xperia-files.com/path/XZDualRecovery/XZDualRecovery_2.8.26

I mean you have to unlock your bootloader with:
Code:
fastboot -i 0x0fce oem unlock 0xhex_unlock_key
(see here)
also you have to erase the old recovery with:
Code:
fastboot erase recovery
(claimed in this guide here)
Edit: I forgot you used a CyanogenMod Recovery, which is stored in FOTAkernel,
so you have to use also :
Code:
fastboot erase boot
fastboot erase FOTAKernel
I did read it here
Hope that does help you

Thanks a lot !

imascara said:
Thanks a lot !
Click to expand...
Click to collapse
I updated my last posting

Unable to flash any recovery. Please help

I am on 12.5.4.0 stock ROM. I am unable to overwrite the stock MIUI recovery. I always get the error message:
FAILED (Status read failed (Too many links))
The recovery image that i am using is a lineage OS 18.1 recovery image that i obtained from a Telegram group on a new lineage 18.1 ROM. I also tried a TWRP image by wzsx, with the same result.
I also tried disabling vbmeta with the command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta\vbmeta_vd171--V12.5.3.0.RJOMIXM.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.016s]
Writing 'vbmeta' OKAY [ 0.000s]
Finished. Total time: 0.016s
But after reboot it goes back to MIUI recovery.
Previously i had flashed crDroid ROM with an SHRP recovery. I remember getting the same "Too many links" error that time too, but i have forgotten how i managed to flash SHRP that time.
I tried using SP FLash Tool , but here too i get an error message " Invalid scatter file name" or something like that for the scatter file in the 12.5.4.0 stock ROM. Then i tried MTK tool to create a scatter file for my Redmi Note 9 but this time i get an error saying it is unabke to read the ROM storage format. Can anyone please help?

Do:
fastboot flash vbmeta vbmeta_vd171--V12.5.3.0.RJOMIXM.img
Is same to do:
fastboot --disable-verity --disable-verification flash vbmeta original_stock_vbmeta.img

It seens a problem with typing.
Did you try to use quotes?
Like
fastboot flash recovery "here is the place/of/image.img"

VD171 said:
It seens a problem with typing.
Did you try to use quotes?
Like
fastboot flash recovery "here is the place/of/image.img"
Click to expand...
Click to collapse
Thanks for the reply. No i don't think it's a problem with typing:
fastboot flash recovery recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.992s]
Writing 'recovery' OKAY [ 0.881s]
Finished. Total time: 2.878s
Now i tried going back to 12.0.6.0 stock ROM with TWRP-RedmiNote9-V12.0.6.0.QJOMIXM-20201213-wzsx15-sanja56. This time success:
C:\Users\iamam\Downloads\TWRP>fastboot flash recovery recovery.img
Sending 'recovery' (34076 KB) OKAY [ 0.855s]
Writing 'recovery' OKAY [ 0.453s]
Finished. Total time: 1.340s
fastboot boot recovery.img
Sending 'boot.img' (34076 KB) OKAY [ 1.017s]
Booting OKAY [ 0.051s]
Finished. Total time: 1.103s
But IT STILL BOOTS INTO MIUI stock RECOVERY!! I can't understand it. Just for fun i changed recovery.img in the fastboot ROM to the recovery.img that i wanted but MiFlash fails (obviously!!!!). Is there a way to check recovery partition on the phone?

12Frodo said:
Thanks for the reply. No i don't think it's a problem with typing:
fastboot flash recovery recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.992s]
Writing 'recovery' OKAY [ 0.881s]
Finished. Total time: 2.878s
Now i tried going back to 12.0.6.0 stock ROM with TWRP-RedmiNote9-V12.0.6.0.QJOMIXM-20201213-wzsx15-sanja56. This time success:
C:\Users\iamam\Downloads\TWRP>fastboot flash recovery recovery.img
Sending 'recovery' (34076 KB) OKAY [ 0.855s]
Writing 'recovery' OKAY [ 0.453s]
Finished. Total time: 1.340s
fastboot boot recovery.img
Sending 'boot.img' (34076 KB) OKAY [ 1.017s]
Booting OKAY [ 0.051s]
Finished. Total time: 1.103s
But IT STILL BOOTS INTO MIUI stock RECOVERY!! I can't understand it. Just for fun i changed recovery.img in the fastboot ROM to the recovery.img that i wanted but MiFlash fails (obviously!!!!). Is there a way to check recovery partition on the phone?
Click to expand...
Click to collapse
Are you sure are not booting into MIUI after flashing? because MIUI installs back the default recovery.

vagelis199 said:
Are you sure are not booting into MIUI after flashing? because MIUI installs back the default recovery.
Click to expand...
Click to collapse
Exactly.
If you want to use custom recovery but without root/magisk, you need to flash my patched boot image.
This patched boot image does NOT install back the default recovery and does NOT install root/magisk.
[BOOT][IMG][PATCHED] Boot Image Partition without OVERWRITE OF RECOVERY for MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
PATCHED BOOT.IMG for MERLIN by VD171 For what do I need it ? At every boot, MIUI overwrites RECOVERY partition for stock rom recovery partition and replaces any custom recovery like TWRP. This patch disables this overwriting and keep any custom...
forum.xda-developers.com

VD171 said:
Exactly.
If you want to use custom recovery but without root/magisk, you need to flash my patched boot image.
This patched boot image does NOT install back the default recovery and does NOT install root/magisk.
[BOOT][IMG][PATCHED] Boot Image Partition without OVERWRITE OF RECOVERY for MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
PATCHED BOOT.IMG for MERLIN by VD171 For what do I need it ? At every boot, MIUI overwrites RECOVERY partition for stock rom recovery partition and replaces any custom recovery like TWRP. This patch disables this overwriting and keep any custom...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks to everybody who replied. But i am using the command "fastboot reboot recovery" after flashing the recovery. But you are right, i did realise that if you just reboot to a stock ROM it reinstalls the stock recovery. Mea Culpa. But i wish this was explained someplace like a general explainer to a newbie.
Anyway, i downloaded the "Platform tools SDK" and used that fastboot and it now installs SHRP and Lineaage OS 18.1 recovery. But TWRP is still a problem. But at least i can install any custom ROM that i want. And yes, thanks VD171, i won't forget to use your patched boot image from now on.

12Frodo said:
Thanks to everybody who replied. But i am using the command "fastboot reboot recovery" after flashing the recovery. But you are right, i did realise that if you just reboot to a stock ROM it reinstalls the stock recovery. Mea Culpa. But i wish this was explained someplace like a general explainer to a newbie.
Anyway, i downloaded the "Platform tools SDK" and used that fastboot and it now installs SHRP and Lineaage OS 18.1 recovery. But TWRP is still a problem. But at least i can install any custom ROM that i want. And yes, thanks VD171, i won't forget to use your patched boot image from now on.
Click to expand...
Click to collapse
You are welcome, my friend.
Enjoy
Sadly, no one says that to you.
But, if you want to enter in recovery, just type "fastboot reboot" and hold the Vol Up button.

Question Pixel 7 stuck on Fastboot Mode trying to reactivate Magisk after OTA update

Hi everyone!
Today I finally decided to update my Google Pixel 7 to the latest version of Android available, so I followed the instructions here. Just to clarify, my phone was rooted with Magisk and it was running TD1A.220804.031.
After some trouble installing the latest OTA, the phone booted correctly. Then I patched the init_boot.img with Magisk and after flashing it on Fastboot, now it's on a loop.
It doesn't matter if I select the options "Start", "Restart Bootloader", "Recovery Mode" or "Rescue Mode", they all take me back to Fastboot Mode. Do you know if there's anything I could do to fix this? (And maybe without wiping the data, if possible?)
I also tried opening Pixel Flasher, but it doesn't detect any device. It always says:
2022-12-06 05:04:20 Scanning for Devices ...
No Devices found.
2022-12-06 05:04:20 No Device is selected!
Click to expand...
Click to collapse
Thanks!

What I would try is make sure your sdk is up to date and check your device manager to see if the drivers are installed right for fastboot. You can do 'fastboot devices' to list what's detected. The Google USB drivers are easy to find if not just tell it to update the driver from a local folder. Then take the stock boot.img from the latest zip and fastboot flash it

pwnyourace said:
What I would try is make sure your sdk is up to date
Click to expand...
Click to collapse
I've checked and apparently I've got the latest versions. Android Studio shows me the latest version of the Android tools is 33.0.3.
Bash:
$ adb version
Android Debug Bridge version 1.0.41
Version 33.0.3p1-android-tools
Installed as /usr/bin/adb
Bash:
$ fastboot --version
fastboot version 33.0.3p1-android-tools
Installed as /usr/bin/fastboot
pwnyourace said:
check your device manager to see if the drivers are installed right for fastboot. You can do 'fastboot devices' to list what's detected
Click to expand...
Click to collapse
fastboot as is detects "something" even though it's shown as a webcam
Bash:
$ fastboot devices
************** USB2.0 UVC HD Webcam
I can confirm that is the phone because it's the same number as one of the previous calls I had done with adb (and the one I can see on the phone's screen)
pwnyourace said:
Then take the stock boot.img from the latest zip and fastboot flash it
Click to expand...
Click to collapse
I've taken the original init_boot.img extracted from the latest factory image of the Google Pixel 7 and flashed it:
Bash:
$ fastboot flash boot init_boot_tq1a.221205.011_original.img
Sending 'boot_a' (65536 KB) OKAY [ 1.887s]
Writing 'boot_a' OKAY [ 0.161s]
Finished. Total time: 2.110s
After selecting "Start" on the screen, it comes back to Fastboot Mode:
Fastboot Mode
Product revision: panther MP1.0
Bootloader version: cloudriper-1.0-9231809
Baseband version: g5300g-220923-221028-B-9229469
Serial number: **************
Secure boot: PRODUCTION
NOS production: yes
DRAM: 8GB Samsung LPDDR5
UFS: 128GB Micron
Device state: unlocked
Boot slot: a
Enter reason: boot failure
UART: disabled
Click to expand...
Click to collapse

mysteech said:
I've taken the original init_boot.img extracted from the latest factory image of the Google Pixel 7 and flashed it:
Bash:
$ fastboot flash boot init_boot_tq1a.221205.011_original.img
Sending 'boot_a' (65536 KB) OKAY [ 1.887s]
Writing 'boot_a' OKAY [ 0.161s]
Finished. Total time: 2.110s
Click to expand...
Click to collapse
That's the wrong command. If you are trying to flash the stock init_boot.img, the command is:
fastboot flash init_boot init_boot.img

Lughnasadh said:
That's the wrong command. If you are trying to flash the stock init_boot.img, the command is:
fastboot flash init_boot init_boot.img
Click to expand...
Click to collapse
That was it, thank you very much for your help!
For future reference, I took boot.img and init_boot.img from the factory image, and flashed them like this:
$ fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 1.763s]
Writing 'boot_a' OKAY [ 0.275s]
Finished. Total time: 2.040s
$ fastboot flash init_boot init_boot_tq1a.221205.011_original.img
Sending 'init_boot_a' (8192 KB) OKAY [ 0.224s]
Writing 'init_boot_a' OKAY [ 0.058s]
Finished. Total time: 0.284s
$ fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.050s
Click to expand...
Click to collapse