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..
Related
I've tried to install CM11 on xperia V (rooted) with T4.3_PhilZCWM_6.0.4.7_LB_v1.7 but I got error 7 and when reboot my device dont boot I tired to going to costume recovery but can't do it (broken recovery) so I can't install recovery flash-able .zip file again. and can't find *.img file in it!
How I can get stock or costume recovery file as .img for use flash in fastboot? or Can I flash custom recovery .zip file via fastboot?
and tried: fastboot flash recovery T4.3_PhilZCWM_6.0.4.7_LB_v1.7.zip
Get:
sending 'recovery' (3201 KB)...
(bootloader) USB download speed was 16392kB/s
OKAY [ 0.218s]
writing 'recovery'...
(bootloader) Flash of partition 'recovery' requested
FAILED (remote: Partition not found)
thank you for help
Answer is:
Sony phones doesn't have separate recovery partition. Its recovery is incorporated to the boot.img, which contains also the kernel.
Custom kernels normally comes with the recovery. You only need to "fastboot flash boot boot.img"
source: http://forum.xda-developers.com/member.php?u=4023029
So: extract boot.img from CM11.zip file and fastboot flash boot.img and recovery will accessible
Stock flashable kernel 23.1.A.0.690 with integrated TWRP
ONLY FOR UNLOCKED BOOTLOADERS!
Works fine with D6503
Flash via recovery or unpack and flash boot.img via fastboot.
In kernel repacked ramdisk with:
-ric disabled
-adb enabled
-camera api 2
-security 0
-tad off
-init.d enabled
Changelog:
v1 TWRP 2.8.5.0 Download v1, mirror v1
v2 TWRP 2.8.6.0 Download v2
THX my friend from russian comunity for huge help!
For root flash latest SuperSu via recovery.
I have fine working xposed without bootloops with this steps:
1. fresh ftf install with full wipes
2. install kernel from this thread
3. install supersu via recovery
4. boot system
5. install titanium backup
6. remove useless system apps
7. clean dalvik via titanium backup
8. reboot system
9. boot recovery and install xposed zip file via recovery
10. boot system and clean dalvik via titanium backup
11. reboot
12. install xposed apk
13. reboot
14. install gravity box module
15. reboot
16. done
With this steps I never have bootloops with xposed.
DRM Restore Function
Any difference with the AdvanceKernel_V2 for LP by @AndroPlus ? Thanks
Borz93 said:
Any difference with the AdvanceKernel_V2 for LP by @AndroPlus ? Thanks
Click to expand...
Click to collapse
Desperanto86 kernel supports insecure adb and init.d.
Borz93 said:
Any difference with the AdvanceKernel_V2 for LP by @AndroPlus ? Thanks
Click to expand...
Click to collapse
I don't have Z2, but @AndroPlus already answer you
AndroPlus said:
Desperanto86 kernel supports insecure adb and init.d.
Click to expand...
Click to collapse
@AndroPlus,
Does your's support Camera API 2?
Puffin617 said:
@AndroPlus,
Does your's support Camera API 2?
Click to expand...
Click to collapse
its just shows applications that camera api functions enabled in kernel, but it doesn't mean that they are presented Sony didn't include new camera drivers in kernel maybe later thay will add them
Just flash via stock recovery? I'm running official lollipop w/o root!
zaryab360 said:
Just flash via stock recovery? I'm running official lollipop w/o root!
Click to expand...
Click to collapse
unlock bootloader and flash boot.img from zip via fastboot.
Flashed with fastboot .. working great! Thanks!
Thank you! This will come in hand! :good:
Desperanto86 said:
unlock bootloader and flash boot.img from zip via fastboot.
Click to expand...
Click to collapse
Will you please provide me a fastboot tutorial?
I searched but found nothing!
zaryab360 said:
Will you please provide me a fastboot tutorial?
I searched but found nothing!
Click to expand...
Click to collapse
here
zaryab360 said:
Will you please provide me a fastboot tutorial?
I searched but found nothing!
Click to expand...
Click to collapse
extract boot.img
reboot to fastboot
in command line :
fastboot flash boot boot.img
fastboot reboot
done
pattsy said:
extract boot.img
reboot to fastboot
in command line :
fastboot flash boot boot.img
fastboot reboot
done
Click to expand...
Click to collapse
:crying:
23/046/2015 13:46:01 - INFO - FASTBOOT Output:
downloading 'boot.img'...
OKAY [ 0.529s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.562s
skizzo_d said:
:crying:
23/046/2015 13:46:01 - INFO - FASTBOOT Output:
downloading 'boot.img'...
OKAY [ 0.529s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.562s
Click to expand...
Click to collapse
place boot.img in fastboot folder, and fastboot folder place in C:\
The sd card shows corrupted
Sent from my D6503 using XDA Free mobile app
Which kernel app would you recommend?
Desperanto86 said:
place boot.img in fastboot folder, and fastboot folder place in C:\
Click to expand...
Click to collapse
fastboot flash boot boot.img
sending 'boot' (16746 KB)...
OKAY [ 0.554s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.569s
skizzo_d said:
fastboot flash boot boot.img
sending 'boot' (16746 KB)...
OKAY [ 0.554s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.569s
Click to expand...
Click to collapse
This is happen to me too!
zaryab360 said:
This is happen to me too!
Click to expand...
Click to collapse
skizzo_d said:
fastboot flash boot boot.img
sending 'boot' (16746 KB)...
OKAY [ 0.554s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.569s
Click to expand...
Click to collapse
at first unlock your bootloader!
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
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.
I'm trying to install custom recovery and ROM on my Redmi 9. I've used XiaoMiToolV2 (https://github.com/francescotescari/XiaoMiToolV2) built on my mac to unlock the boot loader.
But I seem to be stuck trying to replace the recovery.
I tried TWRP- this sent me into a boot loop,
so I tried orangefox from here: https://orangefox.download/device/garden which fixed the bootloop, but everytime I go into recovery it shows me the MIUI Recovery tool.
I also tried pitchblack recovery from here: https://pitchblackrecovery.com/lancelot/ which gives me the same problem.... booting into recovery always shows MIUI Recovery tool.
This is the command I've been using to flash the recovery:
adb reboot bootloader
fastboot flash recovery recovery.img
then a restart, then:
adb reboot recovery
Am I missing something?
supagu said:
I'm trying to install custom recovery and ROM on my Redmi 9. I've used XiaoMiToolV2 (https://github.com/francescotescari/XiaoMiToolV2) built on my mac to unlock the boot loader.
But I seem to be stuck trying to replace the recovery.
I tried TWRP- this sent me into a boot loop,
so I tried orangefox from here: https://orangefox.download/device/garden which fixed the bootloop, but everytime I go into recovery it shows me the MIUI Recovery tool.
I also tried pitchblack recovery from here: https://pitchblackrecovery.com/lancelot/ which gives me the same problem.... booting into recovery always shows MIUI Recovery tool.
This is the command I've been using to flash the recovery:
adb reboot bootloader
fastboot flash recovery recovery.img
then a restart, then:
adb reboot recovery
Am I missing something?
Click to expand...
Click to collapse
Unlock the bootloader before installing the Twrp.
https://miui.blog/any-devices/mi-unlock-tool-mac-linux/
https://www.xiaomitool.com/MiUnlockTool
Twrp:
https://androidfilehost.com/?w=files&flid=318235
.\fastboot flash recovery twrp.img
.\fastboot boot twrp.img
Yes I have unlocked my device using XiaoMiToolV2, I see a little unlocked padlock when booting my phone now.
I tried downloading twrp from the above url (thanks for that!)
I renamed it to recovery.img then:
[email protected] twrp % fastboot flash recovery recovery.img
Sending 'recovery' (65536 KB) OKAY [ 3.746s]
Writing 'recovery' OKAY [ 1.123s]
Finished. Total time: 4.874s
[email protected] twrp % fastboot boot recovery.img
Sending 'boot.img' (65536 KB) OKAY [ 3.733s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
[email protected] twrp % fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.001s
[email protected] twrp % fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' OKAY [ 0.046s]
Finished. Total time: 0.047s
[email protected] twrp % fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
[email protected] twrp % adb reboot bootloader
[email protected] twrp % fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.001s
[email protected] twrp %
So your command to boot the image is incorrect, so I tried some other reboot commands but still when I did the reboot recovery it comes up with MIUIRecovery 5.0.... I should be seeing twrp here right instead?
supagu said:
Yes I have unlocked my device using XiaoMiToolV2, I see a little unlocked padlock when booting my phone now.
I tried downloading twrp from the above url (thanks for that!)
I renamed it to recovery.img then:
[email protected] twrp % fastboot flash recovery recovery.img
Sending 'recovery' (65536 KB) OKAY [ 3.746s]
Writing 'recovery' OKAY [ 1.123s]
Finished. Total time: 4.874s
[email protected] twrp % fastboot boot recovery.img
Sending 'boot.img' (65536 KB) OKAY [ 3.733s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
[email protected] twrp % fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.001s
[email protected] twrp % fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' OKAY [ 0.046s]
Finished. Total time: 0.047s
[email protected] twrp % fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
[email protected] twrp % adb reboot bootloader
[email protected] twrp % fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.001s
[email protected] twrp %
So your command to boot the image is incorrect, so I tried some other reboot commands but still when I did the reboot recovery it comes up with MIUIRecovery 5.0.... I should be seeing twrp here right instead?
Click to expand...
Click to collapse
After flashing TWRP press volume+and power button
MIUI is automatically replacing TWRP with MIUI Recovery. So to fix this after flashing the recovery, you will need to flash the vbmeta image with the flag --disable-verity:
Code:
fastboot flash recovery recovery.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot recovery
This is the vbmeta image: https://forum.xda-developers.com/attachments/vbmeta_redmi9-img.5449805/
Also use this recovery: https://forum.xda-developers.com/t/recovery-twrp-unofficial-twrp-recovery-3-6-1_11-0.4421301/
Thanks guys!
Sergi, your combination of vbmeta and recovery has worked!
Proper url is here:
[RECOVERY][TWRP][UNOFFICIAL] TWRP recovery 3.6.1_11-0
TWRP recovery 3.6.1 for lancelot (redmi 9 | lancelot/galahad) I am not responsible for your brick devices. The recovery is fully working and has been tested. If you encounter a problem, write here, maybe they will help you. Before you accuse me...
forum.xda-developers.com
(you had a typo in your post)
supagu said:
Thanks guys!
Sergi, your combination of vbmeta and recovery has worked!
Proper url is here:
[RECOVERY][TWRP][UNOFFICIAL] TWRP recovery 3.6.1_11-0
TWRP recovery 3.6.1 for lancelot (redmi 9 | lancelot/galahad) I am not responsible for your brick devices. The recovery is fully working and has been tested. If you encounter a problem, write here, maybe they will help you. Before you accuse me...
forum.xda-developers.com
(you had a typo in your post)
Click to expand...
Click to collapse
No problem , and ahh I will correct the link . So glad it worked.