Crashed on flashing Recovery:unknown reboot target recovery - Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans

I was trying to update my system.
The rom is MIUI 12 eu.
After download the ROM, I reboot my device.
It was stuck on the boot interface.
I couldn't enter the recovery.
Then I tried to flash the recovery, the latest TWRP 3.4.2B. I succeeded.
Then I tried the command " flashboot reboot recovery". It failed and returned to me "fastboot: usage: unknown reboot target recovery".
I tried several recovery and flashed the boot.img.
I still can't enter the recovery.

try "fastboot boot recovery.img"

Solved
lostdream said:
try "fastboot boot recovery.img"
Click to expand...
Click to collapse
Thanks,Bro! It solved. You saved me!:good::good:

I'm trying to hard reset a nokia C100, but get "fastboot: usage: unknown reboot target recovery/.img" Fastboot devices works though + I've tried solutions above. Can anyone help me out.

diamant3 said:
I'm trying to hard reset a nokia C100, but get "fastboot: usage: unknown reboot target recovery/.img" Fastboot devices works though + I've tried solutions above. Can anyone help me out.
Click to expand...
Click to collapse
Wrong thread!!
https://forum.xda-developers.com/c/nokia.12020/

Related

[A700] Booting failed

Hi to XDA comunity
... and happy festive season
I tried to install a new ROM. So, I followed tutorials and I have a huge problem
I passed to unlock the tablet
But, when I tried to install the new Recovery, the installation failed and now, the tablet doesn't want to boot
When I boot normaly, in recovery mode or Fastboot mode, I get this message :
Code:
Bootloader Version JB-653b3d3 (Unlock Mode)
Entering boot menu mode
Booting failed
Bootloader VJB-653b3d3(UnlockMode): Starting Fastboot USB download protocol
When I send "Fastboot device", the device is shown
When I send "Fastboot flash recovery twrp-2.6.3.0_a700.img"
Code:
sending 'recovert' <5736 KB>...
But still indefinitely
So I stop and retry and I obtain
downloading 'boot.img'...
FAILED <commande write failed <Unknow error>>
finished. total time: 0.???s
i tried to erase recovery and retry.
Tried with several USB cables.
I don't know what to do...
I guess it's a fastboot problem ? How can I found a fastboot file ?
Thanks for any help !
grimnnir said:
Hi to XDA comunity
... and happy festive season
I tried to install a new ROM. So, I followed tutorials and I have a huge problem
I passed to unlock the tablet
But, when I tried to install the new Recovery, the installation failed and now, the tablet doesn't want to boot
When I boot normaly, in recovery mode or Fastboot mode, I get this message :
Code:
Bootloader Version JB-653b3d3 (Unlock Mode)
Entering boot menu mode
Booting failed
Bootloader VJB-653b3d3(UnlockMode): Starting Fastboot USB download protocol
When I send "Fastboot device", the device is shown
When I send "Fastboot flash recovery twrp-2.6.3.0_a700.img"
Code:
sending 'recovert' <5736 KB>...
But still indefinitely
So I stop and retry and I obtain
downloading 'boot.img'...
FAILED <commande write failed <Unknow error>>
finished. total time: 0.???s
i tried to erase recovery and retry.
Tried with several USB cables.
I don't know what to do...
I guess it's a fastboot problem ? How can I found a fastboot file ?
Thanks for any help !
Click to expand...
Click to collapse
make sure you have the a700 and not the a701 or a510 etc etc....
also, you could try booting directly into fastboot:
1. power off
2. hold power and volume down, while you're doing that, constantly change the rotation switch from lock unlock lock unlock.... keep doing it for about 5 seconds
try flashing from here... it might give you the same result but worth a try.
other possible problems:
1. the recovery you downloaded is corrupt
2. the recovery you downloaded was not a working version
3. you might not have the right usb drivers installed
4. you might have used the wrong recovery commands
5. command (sometimes) needs to be Run as Administrator on Windows (right click)
6. you might have waited too long to reboot to recovery, or used the wrong method to do it
it might make it easier for you if you just rename recovery on computer to recovery.img (so you can just type fastboot flash recovery recovery.img)
also, I have uploaded a copy of the recovery I'm using (it's newer)
you can also try (while in fastboot)
Code:
fastboot boot twrp.img
(or any custom recovery)
It should boot without flashing, and from there you're will be able to flash firmware, ROM, etc...
Shreps said:
you can also try (while in fastboot)
Code:
fastboot boot twrp.img
(or any custom recovery)
It should boot without flashing, and from there you're will be able to flash firmware, ROM, etc...
Click to expand...
Click to collapse
it might be fine but personally I would not try that... recovery and boot are not to be confused and bootloaders are not to be messed with

adb problem

hi
I would like to install twrp image, but adb says device not found, while on the list it sees, the serial nr is there..
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?
When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"
Hunter3U said:
When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"
Click to expand...
Click to collapse
+1 for this.
Folks often mix up fastboot and adb. They are related, but different. Different operation requirements and functions.
adb:
- Only works in OS, or alternately in TWRP.
- Requires debugging toggled on in settings.
Fastboot:
- Only works in bootloader-fastboot mode.
- Does not require debugging to be toggled on.
Fastboot is typically what you want for unlocking bootloader, and booting TWRP (for root, etc.).
---------- Post added at 09:04 AM ---------- Previous post was at 09:00 AM ----------
ii9 said:
adb says device not found
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?
Click to expand...
Click to collapse
Not completely clear based on your description. But is sounds like you are trying to do "adb devices" and then "fastboot flash twrp.img"?
In fastboot, you want to do "fastboot devices" (no quotes) and should see the phone's ID number in response.
Then you want to do "fastboot boot twrp.img" to boot TWRP, then flash the TWRP installer zip within TWRP. This is per the recommended install guide from the TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Although it's hard to determine exactly what you did wrong, unless you provide a more detailed sequence of what you did, and with the exact commands.
And to be clear, your bootloader is unlocked, correct?
well, sorry for being noob, for me was never a problem with older phones. I always managed to root, put twrp, change rom without any pc, but this double slot system kills me
so I managed to wipe everything before, vendor, sytem.., all
I wanted to put the havoc rom after formatting, but there was 5 local disks when I opened the phone folder on the pc, and obviously didn't copy the files on it. Therefore I did reboot to recovery, since that I had only the fastboot screen.
After that I unbricked it, all was fine again on the stock
After opened again the bootloader (yes, also before it was) installed the twrp.img, Installed the twrp zip, reboot it.
I followed the steps from havoc, but it said error 7, few times I tried. I reboooted the recovery again, and now I'm again the fastboot only, doesn't even show the warning msg about open bl, and doesn't go anywhere again.
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?
ii9 said:
*SNIP*
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?
Click to expand...
Click to collapse
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian
Did you do fastboot flash boot imagename or fastboot flash recovery imagename
runningnak3d said:
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian
Click to expand...
Click to collapse
I guess I lost it, time to accept the stock rom :crying:
I' not that old, but I can understand now why my grandma doesn't know even what is a phone
At the end I managed to do the unbrick again, after I installed havoc, I get rid of the error 7, and it showed me st like qualcomm crashdump, I was about to give up, but I went back to twrp installed again, now it's fine. Such a pity that it's not stable yet, I don't dare to touch after this..
tHanks for the info, in case I'll ever need I'll try to read again another 100x maybe I'll find out.
Bradl79 said:
Did you do fastboot flash boot imagename or fastboot flash recovery imagename
Click to expand...
Click to collapse
fastboot flash boot imagename
I did this
ii9 said:
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
Click to expand...
Click to collapse
I think you are doing something wrong.
boot.img is basically a kernel, not TWRP.
Booting TWRP and flashing a boot.img are two completely different things.
It would help if you cut/paste the actual command you typed, so we can see what you did.
The command should be: fastboot boot twrp.img
That isn't what you did.
---------- Post added at 11:55 AM ---------- Previous post was at 11:48 AM ----------
ii9 said:
fastboot flash boot imagename
I did this
Click to expand...
Click to collapse
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Seems similar, but this does something very different from the command you used. Syntax in fastboot/adb is absolutely ciritical. Always type fastboot and adb commands exactly as indicated, and double check everything before issuing the command.
fastboot boot twrp.img This boots the image file that is named. Note that you are not flashing anything with this command. Think of it as a remote boot of the TWRP file that is on your computer.
fastboot flash boot imagename This flashes the named file to the boot partition (basically the kernel)
If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed
redpoint73 said:
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Click to expand...
Click to collapse
Sorry, I messed up with the copy and paste, I didn't sleep too much in the last days for the hot, I'm a bit heavy in the head, pls exuse my bs. I also tried this one that you wrote, but didn't manage to boot still.. I have no clue what went wrong, but again, thanks, in case I can come back to read again.
Hunter3U said:
If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed
Click to expand...
Click to collapse
Not exactly, the end goal to have a clean rom, with basic custumization, that even stock should include in my opinion, like disable headups.., extended screen etc. Plus without google staff, for me it's too strict. As in this moment not so many choice, havoc looked the most near to my wishes, in fact very nice after these hours, I guess I'll be fine with it when the bugs will disappear.
Anyway 1-7 was always without problem. Today after 2 unbrick and bl opening what I did is, through fastboot I entered to the img, from there I flashed the zip, reboot recovery to make sure it stays. I put files on the phone, wiped dalvik and data, install rom+twrp and as it is written here and also on that thread, I rebooted recovery. And I wanted to repeat the flash, but I had the internal storage 0mb thing. So I needed to format data (that's the solition I found) and reboot again, put back files, flash, reboot, flash again, and after I got that qualcomm crashdump screen. I hold the up+power to get back to twrp (or down, not sure) and I flashed again, but only once, so after it worked finally. Since that I'm fine
But sure I need to learn this stuff, it cannot be that I always face st that nobody else does
I hope the managed soon the ota for custom roms and we can do it easy and quick without setting the phone over and over again with all the apps, settings.. (probably only me in the world need to do so, as I start to loose it with the tech staff)
Poor phone is just couple of weeks old, but already saw everything
Thanks for writing
If it means anything to you, I use stock OOS+TWRP+Magisk+Renovate ICE+Xposed (to ignore the secure flag, otherwise Netflix doesn't work over HDMI). Everything works, including Google Pay.

Flash TWRP via fastboot android 10

Hello guys, as we known that it is unable to use command in fastboot to boot into TWRP if we are on Android 10 (both OOS and Custom rom) at the moment, so here is the simple command allow us to do that if you want to roll back android 9 or any rom by TWRP
fastboot flash boot_a <twrp name.img>
fastboot flash boot_b <twrp name.img>
fastboot reboot
Your phone will automatically boot into TWRP, so you can flash another rom
Can anyone confirm this works?
I tried something similar when I first installed OOS 10, and I successfully booted TWRP, but I ended up getting a bootloop (stuck at the g.co/ABH warning thing) when I rebooted to system. I don't know if I did something wrong, or flashing twrp to both boot partitions caused it.
I would try again, but I'm on a critical work trip until the end of the month, so my phone's uptime is expected to be 100% until then.
worked for me while anything else didnt
LazerH said:
worked for me while anything else didnt
Click to expand...
Click to collapse
Does it wipe your data?
Didn't work for me. My boot image was patched already this is probably why.
ok, I tried this, but as reported above, now also stuck on this same: "I tried something similar when I first installed OOS 10, and I successfully booted TWRP, but I ended up getting a bootloop (stuck at the g.co/ABH warning thing) when I rebooted to system. I don't know if I did something wrong, or flashing twrp to both boot partitions caused it."
How do I resrore operation for my phone? (help?)
Well, I met this issue before, and ended up with using this method to successfully boot into twrp.
This issue seems to appear on OOS, when I using `fastboot boot xxx.img` on other ROM like omni, I'm able to boot into twrp, thanks!
can someone help me please. my phone is stuck in a fastboot bootloop. everything I try doesn't work.
fastboot boot TWRP.img NOTHING
tried your solution above and still nothing
Still stuck in fastboot this is what I get:
PS C:\Users\Les Brown\Desktop\OnePlus 6> fastboot boot twrp-3.3.1-17-enchilada-Q-mauronofrio.img
downloading 'boot.img'...
OKAY [ 0.617s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.655s
@killathenoob Download DECRYPTED OOS 10.3.0 with this help if you don't really know what to do with this.
For others people (and you if you want to root or just install TWRP after fresh OOS10 Decrypted install) don't forget to OEM unlock before doing anything.
Download this
Copy "twrp-3.3.1-17-enchilada-installer-mauronofrio.zip" into internal storage of your OP6
Power it OFF
Power it ON in fastboot mode
Launch "Boot TWRP.bat"
Connect your OP6 to your PC and wait for TWRP to boot
Install twrp-3.3.1-17-enchilada-installer-mauronofrio.zip
Reboot to recovery and install magisk if you need to.
Source
Hope I helped a bit.

realme 5i twrp command not working ( fastboot boot twrp.img )

i am trying to root realme 5i. i successfully unlock bootloader. fastboot flash recovery twrp.img working fine.
but when i try command fastboot boot twrp.img it shows
PS C:\Users\hpp\Desktop\adbfastboot> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.415s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.421s
please guide me how to install twpr on m phone . please help
ad_nannnn said:
i am trying to root realme 5i. i successfully unlock bootloader. fastboot flash recovery twrp.img working fine.
but when i try command fastboot boot twrp.img it shows
PS C:\Users\hpp\Desktop\adbfastboot> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.415s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.421s
please guide me how to install twpr on m phone . please help
Click to expand...
Click to collapse
Also same problem ... But after use another twrp it's shown success .. but still no working ... In commed section it's saw successful ... But when boot on recovery mood my phone it's no working ..no recovery option
Yeah right me too
Somehow Wrong Command
ad_nannnn said:
...
But, when I try command fastboot boot twrp.img
...
FAILED (remote: unknown command)
finished. total time: 1.421s
please guide me how to install twpr on m phone . please help
Click to expand...
Click to collapse
After flashing a Custom Recovery, If you want to boot to recovery, the actual command through fastboot is
Code:
fastboot boot recovery
or also in the bootloader screen you can press vol+ button untill you see Recovery mode then hit Power button.
The most important point is After flashing a Custom Recovery you must flash the vbmeta with Verity command To make it permanent. Otherwise it'll just revert back to Stock Recovery. (This method only works in Color Os (ie., Android 9), for RealmeUI you need additional thing to do)
iamvijaypushparaj said:
After flashing a Custom Recovery, If you want to boot to recovery, the actual command through fastboot is
Code:
fastboot boot recovery
or also in the bootloader screen you can press vol+ button untill you see Recovery mode then hit Power button.
The most important point is After flashing a Custom Recovery you must flash the vbmeta with Verity command To make it permanent. Otherwise it'll just revert back to Stock Recovery. (This method only works in Color Os (ie., Android 9), for RealmeUI you need additional thing to do)
Click to expand...
Click to collapse
Where do we get this vbmeta from? I'm having the same problem, that after flashing twrp.img it just reboots back into fastboot mode. Is this because Secure Boot is enabled and does vbmeta disable that?
realme 5 tg
doveman said:
Where do we get this vbmeta from? I'm having the same problem, that after flashing twrp.img it just reboots back into fastboot mode. Is this because Secure Boot is enabled and does vbmeta disable that?
Click to expand...
Click to collapse
realme 5 telegram group
CjConvento said:
realme 5 telegram group
Click to expand...
Click to collapse
iamvijaypushparaj posted it here https://forum.xda-developers.com/showpost.php?p=83251175&postcount=16 but unfortunately it still just boots into fastboot whatever I try.
doveman said:
iamvijaypushparaj posted it here https://forum.xda-developers.com/showpost.php?p=83251175&postcount=16 but unfortunately it still just boots into fastboot whatever I try.
Click to expand...
Click to collapse
After flashing recovery via cmd, you will go back to fastboot on your screen. Navigate the volume buttons til it show Recovery mode on top of the screen. Then press power button and it will boot to recovery.
jokezerious said:
After flashing recovery via cmd, you will go back to fastboot on your screen. Navigate the volume buttons til it show Recovery mode on top of the screen. Then press power button and it will boot to recovery.
Click to expand...
Click to collapse
It turned out the problem was Orangefox. With TWRP it booted into Recovery fine when I selected that option but with Orangefox it would just reboot into fastboot. I'll try some different versions of Orangefox sometime but for now my biggest problem is that it's impossible to set a Lock Screen PIN/Password, let alone use FingerPrint. It seems unlocking the bootloader breaks the security settings.
whats orangefox ? did u found a fix !
I rooted 5i and no use your code. I follow this video
Some code:
adb devices
adb reboot bootloader
fastboot flashing unlock
fastboot devices
fastboot flash recovery REALME5i.img
fastboot flash vbmeta vbmeta.img
adb reboot recovery

[ AIO ] Guide TECNO SPARK 5 PRO (KD7) bootloader unlocking,root,twrp & stock firmware

AIO GUIDE TECNO KD7
1. Bootloader Unlocking
1. Download & install the ADB driver
2.Enable devloper mode by taping on Build verson(setting->my phone) then enable Oem Unlock & usb debugging from (settings->System->Devloper option)
3.Now connect device & open ADB path & run cmd
command: ADB devices
then reboot to bootloader
command: ADB reboot bootloader
4. unlock bootloader
command: fastboot flashing unlock the phone will ask to confirm
5. now reboot to system
command:fastboot reboot
If you are stuck waiting for the device screen
2. TWRP [unoficial]
https://forum.xda-developers.com/t/twrp-recovery-for-tecno-kd7.4378493/
3. Orange state disabler:
Flashing guide & zip file
Click Wipe →Format Data → Yes → Press Enter.
Then Click Reboot → Recovery (Reboot to Recovery ).
After this, TWRP Recovery Mode will be installed on your phone
Link: Orange disabler.zip
4. Root
1.boot into recovery
2. Flash magisk .zip
llink:https://github.com/topjohnwu/Magisk/releases/download/v21.0/Magisk-v21.0.zip
3.1. Unroot
1.boot into recovery
2. Flash magisk unistaller .zip
link:https://github.com/topjohnwu/Magisk/releases/download/v21.0/Magisk-uninstaller-20201003.zip
5.Stock Firmware Files
Stock boot ,stock recovery & Full Firmware are added
To Flash full firmware
Extract zip & run flash.bat
Link: TECNO-SPARK-5-PRO-KD7-H6211FQRSTU-Q-GL-211101V404-fastboot flash full rom.zip
6. Gsi rom / Custom rom Installation guide:
https://forum.xda-developers.com/t/custom-rom-for-tecno-phone-dynamic-partition.4379341/
vendor : ( 3 sim problem guide )
TECNO-SPARK-5-PRO-KD7-H6211FQRSTU-Q-GL-211101V404
7. Phone Hard Brick fix
https://forum.xda-developers.com/t/phone-soft-brick-phone-on-off-poblem-tecno-device.4378501/
7.1. Flash file:
Link :
TECNO-SPARK-5-PRO-KD7-H6211FQRSTU-Q-GL-211101V404
HIT THE THANKS BUTTON IF ABOVE INFORMATION IS HELPFUL TO YOU
Tecno kd7 full guide
https://forum.xda-developers.com/t/...r-unlocking-root-twrp-stock-firmware.4345557/
What do you mean by boot into recovery? Going fastboot mode? And then writing fastboot flash recovery magisk.zip( for step 3(root)) ?
Also should have the updatest kd7 before rooting?
Thanks in advance for your hard work.
Tanjin01: Thanks
Fast time twrp recovery install: (any bulid version)
[command]
adb devices
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
[command]
Now boot into twrp recovery and from there "wipe option->Format Data -> yes Format.
Next, Reboot option -> recovery click Wait reboot recovery and flash magisk.zip
Any time root and unroot:
2.going to recovery
Open recovery and install magisk zip. /Magisk uninstall flash
Parvej789 said:
Tanjin01: Thanks
Fast time twrp recovery install: (any bulid version)
1.Fastboot flash recovery .
Fastboot reboot recovery -
Open recovery -wipe format data-yes.
reboot to recovery
and install magisk zip.
Any time root and unroot:
2.going to recovery
Open recovery and install magisk zip. /Magisk uninstall
Click to expand...
Click to collapse
Thank a bunch for consist help with my nobby question(s)!
Correct me if i am wrong before i procced,
Fire up pc, open terminal/cmd and writing the following one after another
[Command]
adb devices
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
[command]
Now i boot into twrp recovery and from there "wipe data". Then "advanced wipe" with delvic cache.
Next, again, twrp recovery and flash magisk.zip
Right?
Tanzin01
[Command]
adb devices
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
[command]
Now i boot into twrp recovery and from there "wipe ". Then "Format Data" with yes Format.
Next, Reboot to recovery .again, twrp recovery and flash magisk.zip
Right?
Thanks man. Have a nice day&life
hey man, all went well till format. in format i saw some error, eg failed to mount /data(something like this). Any idaea why i got this?
[i got a success msg though]]
also can i access twrp recovery mode via volume and power button?(i tried volume up+power button but got adnroid image with "No command".)
Command]
adb devices
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
[command]
Now boot into twrp recovery and from there "wipe option ->Format Data -> yes Format .
Next,
Reboot options -> recovery click Wait reboot to recovery and magisk.zip flash
Parvej789 said:
Command]
adb devices
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
[command]
Now i boot into twrp recovery and from there "wipe ". Then "Format Data" with yes Format.
Next,
Reboot options to recovery .again, twrp recovery and flash magisk.zip
Right?
Click to expand...
Click to collapse
All the commands worked smoothly but when again tried to go twrp recovery for rooting, I can't seem to find twrp. I got no command with Android pic and after few seconds default device recovery option. From where I can navigate to fastboot, recovery, wipe and etc.
"
Next,
Reboot options to recovery .again, tw
Parvej789 said:
Next,
Reboot options to recovery .again, twrp recovery and flash magisk.zip
Right?
Click to expand...
Click to collapse
Not sure what you mean by this. But tried
[Command]
adb reboot bootloader
fastboot reboot recovery
[Command]
Which took me to deafult recovery, no Twrp this time.
However I spent some time on xda and found this Command "fastboot boot twrp.img". Will try tomorrow again, will let you know if it worked! Man I'm probably bothering you!
Tanzin01 said:
"
Next,
Reboot options to recovery .again, tw
Not sure what you mean by this. But tried
[Command]
adb reboot bootloader
fastboot reboot recovery
[Command]
Which took me to deafult recovery, no Twrp this time.
However I spent some time on xda and found this Command "fastboot boot twrp.img". Will try tomorrow again, will let you know if it worked! Man I'm probably bothering you!
Click to expand...
Click to collapse
[command]
adb devices
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
[command]
Now boot into twrp recovery and from there "wipe option->Format Data -> yes Format and back home menu
Next, Reboot option -> recovery click Wait reboot recovery and flash magisk.zip
Unorganized posts! Its xda's fault. Your edited post wasn't shown to me until my last post was posted!
Thanks man. This time I got it. I wrongly rebooted after "format data". I will reflash the twrp file again tomorrow.
Hey, i got myself in trouble again! Everything was working fine till i clicked on "Erase data" from settings. Now i cant boot into sytem, always booting into twrp.Any help?
Should i try flashing android 11, the one you provided here?
Tanzin01 said:
Hey, i got myself in trouble again! Everything was working fine till i clicked on "Erase data" from settings. Now i cant boot into sytem, always booting into twrp.Any help?
Should i try flashing android 11, the one you provided here?
Click to expand...
Click to collapse
Stock recovery.img flash and reboot
To make sure, i am donig as you described,
download stock firmware and get recovery.img.
now flash it: fastboot flash recovery recovery.img
Now reboot, right?
Btw cant i just flash andoid 11 altogether? (and thanks for your constant help
Tanzin01 said:
To make sure, i am donig as you described,
download stock firmware and get recovery.img.
now flash it: fastboot flash recovery recovery.img
Now reboot, right?
Btw cant i just flash andoid 11 altogether? (and thanks for your constant help :fashfashfashfash)
Click to expand...
Click to collapse
Yes
Or
Full flash
KD7-H6211FQRSTU-Q-GL-210520V392.zip
drive.google.com
how to do full flash?
[command]
fastboot flash system FullFlashfirmware.zip
[command]
or
sideload the zip file and then swipe install via twrp?
No .
PC to mobile(fastboot flash)
Now connect device to PC
Unzip flash file PC
Folder open
Click flash.bat
CMD open:
1.Do you want to Reboot device into fastboot [Y/N]=y type enter
2.wipe user data [Y/N]=y type enter
Then flash started
FLASHING success
Reboot to phone on
sadly im not on windows. Anyway thnx. i will try and see flashing recovery. Will let you know the result.
Stock recovery.img flash and reboot options->system click.
Reboot to phone on
Parvej789 said:
Stock recovery.img flash and reboot options->system click.
Reboot to phone on
Click to expand...
Click to collapse
got error
```
fastboot flash recovery recovery.img
Sending 'recovery' (39936 KB)
FAILED (Write to device failed (No such device))
fastboot: error: Command failed
``
tried changing cable but no change.
Oky so i had a hunch, and it was correct. i mounted system and didnt get that error.
Thanks buddy. Took me few tries and combination. but now im back with my device. And as guessed, twrp was/is the culprit. It was locking the system or something like this, perhaps a glich? anyway had to mount system and already wrote the command on terminal, so as soon as phone screen turns on, i get to send the data from pc to phone before phone starts doing many of its stuff.
Wipe option->format data -yes
Reboot option-> recovery and Twrp open
1.boot.img flash
2.super.img flash
3.recovery.img flash
Than reboot
Tanzin01 said:
Thanks buddy. Took me few tries and combination. but now im back with my device. And as guessed, twrp was/is the culprit. It was locking the system or something like this, perhaps a glich? anyway had to mount system and already wrote the command on terminal, so as soon as phone screen turns on, i get to send the data from pc to phone before phone starts doing many of its stuff.
Click to expand...
Click to collapse
Build version correct
Your build version

Categories

Resources