Database Info

Update from 5.1.1 to 6.0.1

Hello, i'm trying to upgrade my rooted nexus 5 from 5.1.1 LMY48I to 6.0.1 MOB30H without losing my data, but at first boot, stops at android logo. I follow this steps with nexus root toolkit:
- Erasing Boot, Cache, Recovery and System.
- Flashing bootloader, radio, cache, boot and system with official .img files from Google developers webpage
- Flashing recovery with TWRP .img
After all these steps, stops on android logo...
Any ideas?

marios.v said:
Hello, i'm trying to upgrade my rooted nexus 5 from 5.1.1 LMY48I to 6.0.1 MOB30H without losing my data, but at first boot, stops at android logo. I follow this steps with nexus root toolkit:
- Erasing Boot, Cache, Recovery and System.
- Flashing bootloader, radio, cache, boot and system with official .img files from Google developers webpage
- Flashing recovery with TWRP .img
After all these steps, stops on android logo...
Any ideas?
Click to expand...
Click to collapse
Do a factory reset

Do NOT use toolkits!
My first advice is: Do NOT flash using toolkits! You never know what's exactly going on if you don't do it manually. There are plenty of reasons why to not use them...
Okay, now my second advice: Don't flash cache partitions. Caches are built during boot/runtime. However, as far as I know, a corrupted cache partition can lead to bootloops - so it's better to just wipe them before boot...
I don't know what the toolkit did and what not - but try to follow these steps:
1. Install fastboot and adb
Preferred method is via Android Studio command line tools from official source: http://developer.android.com/sdk/index.html - Scroll down to "Get just the command line tools". You can decide between an installer or just a zip. It's your choice.
2. Boot your phone in bootloader mode and execute these commands one by one...
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery twrp-recovery.img
fastboot flash system system.img
Click to expand...
Click to collapse
Use the proper files! Extract bootloader and radio from latest Google factory image and download TWRP from twrp.me!
3. Boot your phone into TWRP and choose wipe -> DO NOT SLIDE TO FACTORY RESET -> advanced wipe -> cache + dalvik ticked, rest unticked -> slide to wipe
4. Try to boot...
Not sure if it works - but that's the only thing I can think of right now
EDIT: @GtrCraft That would definitely solve his bootloop, but he wants to keep his data Hopefully he heeds my advice to keep his hands off of toolkits!

experience7 said:
@GtrCraft That would definitely solve his bootloop, but he wants to keep his data Hopefully he heeds my advice to keep his hands off of toolkits!
Click to expand...
Click to collapse
Then he should do all the ota's instead of flashing the factory image
Sent from my XT1562 using XDA Labs

Don't do full-quotes please.
Seriously? His device is rooted and therefore not receiving OTA (over-the-air!) updates. He'd have to catch all of the zips and flash them manually. So why not just use the system.img?

experience7 said:
Don't do full-quotes please.
Seriously? His device is rooted and therefore not receiving OTA (over-the-air!) updates. He'd have to catch all of the zips and flash them manually. So why not just use the system.img?
Click to expand...
Click to collapse
Because you have to factory reset the device. That's the downside of being rooted and wanting to update, especially with M

I'm sorry to say that you're terribly wrong. I hope you didn't factory reset your device every single time you did an update just because you're rooted! Actually you can use the flash-all.bat file that's provided with the factory image. Just remove the "-w" flag from the "fastboot update" command. This will stop fastboot from wiping your /data partition.
That's what the OP could use as well - however, for his better understanding I listed the commands separately.

For what it's worth, this is the script that I've been using since the monthly updates started (copied from another XDA thread which I've forgotten - apologies to the OP of this script).
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash SuperSU
Start to finish - 15 minutes, including the rebuilding of the apps. No data loss (because you haven't touched the data/userdata partition).
I don't say that every step is essential (I note the comment from experience7 about cache) - but this works fine for me.
Please feel free to amend or correct...

dahawthorne said:
For what it's worth, this is the script that I've been using since the monthly updates started (copied from another XDA thread which I've forgotten - apologies to the OP of this script).
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash SuperSU
Click to expand...
Click to collapse
Same problem again. I'm trying all 6.x.x versions but same problem. All commands running without error.

In that case all I can suggest is that you bite the bullet and run the flash-all.bat. Back up all your important stuff (photos, etc.) because you'll lose them.
I've seen it suggested often that you should always do a full wipe when upgrading between major versions (e.g. 5 to 6), so maybe this will fix your problem and give you a working phone even if you lose some data and have to set up from scratch.
P.S. Please "Quick reply" - don't repeat the entire previous post. We've all read it; we don't need to read it again.

marios.v said:
Hello, i'm trying to upgrade my rooted nexus 5 from 5.1.1 LMY48I to 6.0.1 MOB30H without losing my data, but at first boot, stops at android logo. I follow this steps with nexus root toolkit:
- Erasing Boot, Cache, Recovery and System.
- Flashing bootloader, radio, cache, boot and system with official .img files from Google developers webpage
- Flashing recovery with TWRP .img
After all these steps, stops on android logo...
Any ideas?
Click to expand...
Click to collapse
Search for a full guide thread. I'm sure you will come out with something.
Sent from my GT-I9505 using XDA-Developers mobile app

"Search for a full guide thread. I'm sure you will come out with something."
Excellent advice. It's amazing that so many experienced senior members with all their years of combined knowledge missed that blindingly obvious idea...

Problem solved by unfreezing all frozen apps from Titanium Backup before upgrade.
Thank you!

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.

How can the Ulefone Armor 8 be rooted?

Hello to all,
i've been trying since 1 week now to root an Ulefone Armor 8, but it doesn't work. All drivers are installed. The OS installed on the device is Android 10, the build version is X70WSFFB.GQU.EEA.FHJ.Q0.TJAPA9VDYPTS.0703.V3.01. I have already contacted Ulefone and asked if there is another build version (for EU), but it is the only one currently available.
In the firmware there are two boot.img. One is called "boot.img" and the other is called "boot-debug-img". First I only patched the "boot.img" with Magisk and flashed the patched "magisk-patched.img" via ADB. After that the Armor 8 had a bootloop. The bootloop could be removed by flashing the original "boot.img" via ADB. The Armor started normally again.
After that I patched the "boot.img" and the "boot-debug.img" with Magisk and renamed them to "magisk-patched1.img" and "magisk-patched2.img". After that I flashed first the " magisk-patched1.img" and then the " magisk-patched2.img" via ADB. The Armor 8 then had a boot loop again. To get the bootloop away, the original "boot.img" was flashed back and Armor 8 is back in its factory default state.
How can it be rooted, what should I do differently? Could it be because there are two "boot" files in the firmware?
Sorry if my english is not perfect.
Thanks for your help and tips.
Greetings

https://www.getdroidtips.com/root-ulefone-armor-8/

I have tried that too, but it doesn' t work.
I flashed the "boot.img" with Magisk, from this Magisk created the file "patched_magisk.img". I moved this file to the ADB folder. After that I did it again with the file "boot-debug.img". Then I put the armor in fastboot mode and first I entered the command "fastboot flash boot_a magisk_patched.img".
ADB writes: writing 'boot_ a'... FAILED (remote: This partition doesn't exist)
After that I still moved the patched "boot-debug.img" into the ADB folder and entered the command "fastboot flash boot_b magisk_patched.img".
ADB writes: writing 'boot_b'... FAILED (status read failed (Too many links))
Magisk didn't create 2 patched files from 1 "boot.img", but in the unpacked ROM there are 2 .img files, namely "boot.img" and "boot-debug.img", which I patched one after the other and then flashed.
I have also downloaded the firmware of Armor 7. Of course not to install it, just to see if there are 2 boot.img (= boot.img + boot-debug.img) in it, too. For Armor 7 there is only 1 file "boot.img". For Armor 8 in the firmware there are "boot.img" and "boot-debug.img"
I have now tried overall:
just flash the patched "boot.img" = bootloop
flash only the patched "boot-debug.img" = bootloop
then first the patched "boot.img" and then the patched "boot-debug.img" = bootloop
Now just now again with the command "fastboot flash boot_a magisk_patched.img" = error message and then continue with the command "fastboot flash boot_b magisk_patched.img" = error message.
I think the problem is that there are 2x boot.img files in the ROM?
Edit:
And the SP-Flash-Tool shows that I should remove the battery, but the Armor has a fixed battery.

The SP Flash Tool now works after reinstalling the Vcom driver.
I have now extracted the boot.img of Armor 8 with the SP Flash Tool via "Readback". This file was then patched with Magisk. The file "magisk_patched.img" is together with the file boot.img in the same folder.
This was then flashed to the Armor with the SP Flash Tool in "Download only" mode. The flashing process is running normally and finally "Download Ok".
After that the Armor 8 will start normally and without bootloop, but it still has no root.
Does anyone have an idea?

I also have an armor 8 and I noticed that when u enter developer mode u can unlock the bootloader from there. Which allows you to install root access more successfully
after tapping on the kernel build go back and enter the option where it says system. There u will find the developer options.
after that, I had to follow some steps from this video
I got the stock ROM from the Ulefone website https://www.ulefone.com/support/software-download.html
where I was able to get the boot.img and patch it with magisk however I kept on getting a boot loop so I'll probably figure out another way to root it
1st
2nd

ignore

Have you succeeded yet? I am interested in this phone but want to be sure it can be rooted
Instead of trying to patch it from fastboot, just try booting! Follow the instructions below.
You may want to try the following steps: Just ignore the part about using their rom since it is a different phone. You should be using the Ulefone ROM
[Guide] Install Magisk on your device, updated to handle OTAs easily
[Update in 1st September 2018] Magisk v17 stable has been released, so the August security update: a new method, more OTA-compliant, is written. Hi all, this section is quite gaunt, so I'll post my experience on unlocking and rooting my brand...
forum.xda-developers.com
So save you some clicking, I'll just paste the relevant part below:
How to root
0. You need "debug usb" and "oem unlock" enabled under "developer options" on phone's settings.
1. First, if you don't have already done it, unlock phone's bootloader:
Code:
adb reboot bootloader
fastboot oem unlock
ATTENTION: THIS WILL WIPE YOUR DEVICE, ALL USER DATA WILL BE LOST! And no, when you'll have finish this guide, you can't lock it again (each lock-unlock operation will wipe the device)
2. Download ROM system image from official site. Pay attention to download the corresponding version of your actual OS (look in system settings your current build number).
3. Extract "boot.img" from the just downloaded archive and put somewhere in your device (e.g. in a microSD, just remember where you put it).
4. Download and install Magisk Manager apk.
5. Open Magisk, choosing "yes" when it asks to install Magisk-v*.zip, then choose "patch boot image" and select "boot.img" copied in step 3.
6. At the end of patching process, Magisk will tell you where "patched_boot.img" is been stored, keep a note on it and close.
Now's the updated part, that will make possible to apply OTAs:
7. Copy "patched_boot.img" on your computer, then run this on a terminal:
Code:
adb reboot bootloader
fastboot boot patched_boot.img
fastboot reboot
This will temporarily give you root privileges (until next reboot).
8. Magisk Manager can now make the root permanent: open it and tap "Install", then "direct install (recommended)". This way (instead of flashing directly patched_boot.img) Magisk Manager can remove and reinstall root privileges directly.
9. Just to be sure that your phone doesn't install updates without your acknowledgement, go to Developer Options and disable "Automatic system updates".
Ta-dà! Now you should have Magisk permanently installed (you can check it re-opening Magisk Manager).
-------------------------------------------------------
Time to update? Here's how
If you've followed what is written above, applying an OTA should be quite easy now.
a. Go to Magisk Manager → Uninstall → Restore Images. Do not reboot now or you will have Magisk uninstalled!
b. Now go to Settings → System → System Update and apply OTA. If it fails you've some tweak on system partition that you've forgot to remove, so try to figure it out and retry. Wait for the installation to complete. DO NOT RESTART NOW.
c. Open Magisk Manager again and press Install → Install to Inactive Slot.
d. Reboot and enjoy
-----------------------
PLEASE ADVISE IF THIS WORKS!

As the guy clearly mentioned, there's a boot.img and a debug_boot.img whenever i try to patch any of that and use fastboot to flash it I only get a bootloop
The bootloader is already unlocked and there's nothing else I can do to get this phone rooted
There's also no twrp currently supported for.it and that's pretty much it
I just needed help with this but it seems like this phone is very unknown and unsupported

MasDbs101 said:
As the guy clearly mentioned, there's a boot.img and a debug_boot.img whenever i try to patch any of that and use fastboot to flash it I only get a bootloop
The bootloader is already unlocked and there's nothing else I can do to get this phone rooted
There's also no twrp currently supported for.it and that's pretty much it
I just needed help with this but it seems like this phone is very unknown and unsupported
Click to expand...
Click to collapse
Have you explicitly tried
fastboot BOOT patched_boot.img
just BOOTING the patched boot image. just ignoring the the flash command for now.
This shouldn't cause a bootloop since it'll just revert back to the virgin boot.img
TWRP isn't needed for rooting.

Thank you for sharing this , I will try it later today and let you know what happens.

MasDbs101 said:
Thank you for sharing this , I will try it later today and let you know what happens.
Click to expand...
Click to collapse
Any luck?

stizarch said:
Any luck?
Click to expand...
Click to collapse
Bootloop

Finally, I successfully rooted! Procedure is the same as in the post 7, but before flashing patched boot you should flash empty vbmeta image:
fastboot flash vbmeta vbmeta_null.img
and then:
fastboot flash boot boot_magisk_patched_root.img
and reboot to system:
fastboot reboot
I attached empty vbmeta and patched boot.

knedlyk said:
Finally, I successfully rooted! Procedure is the same as in the post 7, but before flashing patched boot you should flash empty vbmeta image:
fastboot flash vbmeta vbmeta_null.img
and then:
fastboot flash boot boot_magisk_patched_root.img
and reboot to system:
fastboot reboot
I attached empty vbmeta and patched boot.
Click to expand...
Click to collapse
how did you get a null vbmeta file i need one for the ulefone armor 10 5g i wonder if its just empty it will work or something will try

zenoblank34 said:
how did you get a null vbmeta file i need one for the ulefone armor 10 5g i wonder if its just empty it will work or something will try
Click to expand...
Click to collapse
yes flashing vbmeta null over vbmeta on ulefone armor 10 5g worked as well i got root access

Armor8 said:
Hello to all,
i've been trying since 1 week now to root an Ulefone Armor 8, but it doesn't work. All drivers are installed. The OS installed on the device is Android 10, the build version is X70WSFFB.GQU.EEA.FHJ.Q0.TJAPA9VDYPTS.0703.V3.01. I have already contacted Ulefone and asked if there is another build version (for EU), but it is the only one currently available.
In the firmware there are two boot.img. One is called "boot.img" and the other is called "boot-debug-img". First I only patched the "boot.img" with Magisk and flashed the patched "magisk-patched.img" via ADB. After that the Armor 8 had a bootloop. The bootloop could be removed by flashing the original "boot.img" via ADB. The Armor started normally again.
After that I patched the "boot.img" and the "boot-debug.img" with Magisk and renamed them to "magisk-patched1.img" and "magisk-patched2.img". After that I flashed first the " magisk-patched1.img" and then the " magisk-patched2.img" via ADB. The Armor 8 then had a boot loop again. To get the bootloop away, the original "boot.img" was flashed back and Armor 8 is back in its factory default state.
How can it be rooted, what should I do differently? Could it be because there are two "boot" files in the firmware?
Sorry if my english is not perfect.
Thanks for your help and tips.
Greetings
Click to expand...
Click to collapse
Hello I tried but I fail ..
I install all drivers..
But when
Adb reboot bootloader .. rebooted..ok
Fastboot oem unlock ... Waiting for device...
So I cannot unlock the bootloader

have you tried
fastboot flashing oem
or
fastboot flash oem

zenoblank34 said:
have you tried
fastboot flashing oem
or
fastboot flash oem
Click to expand...
Click to collapse
Only work for me
adb reboot bootloader
fastboot -i 0x0E8D devices
fastboot -i 0x0E8D flashing unlock
fastboot -i 0x0E8D flash boot magisk_patched.img
fastboot -i 0x0E8D flash vbmeta vbmeta_null.img
fastboot -i 0x0E8D reboot
rebooting...

Thanks people, it worked for me.
Can you tell me how much time do you need to fully charge from 0 to 100% ?
And do you use charger from box?

PabloWalker13 said:
Only work for me
adb reboot bootloader
fastboot -i 0x0E8D devices
fastboot -i 0x0E8D flashing unlock
fastboot -i 0x0E8D flash boot magisk_patched.img
fastboot -i 0x0E8D flash vbmeta vbmeta_null.img
fastboot -i 0x0E8D reboot
rebooting...
Click to expand...
Click to collapse
What does it mean the code 0x0E8D?

[ 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

General [TWRP] Xiaomi 12

This TWRP works with Xiaomi 12
📌 [Shared] TWRP by skkk
⚡⚡A12/A13⚡⚡ ----------------------- BOOT VERSION Installation: Phone in fastboot mode Cmd: fastboot boot twrp.img or Power shell ./fastboot boot twrp.img then in Twrp go to Advanced -> flash current TWRP...
forum.xda-developers.com
Command to install:
1. boot your device in Fastboot mode
2. fastboot boot recovery_finename.img
This will temporary boot your device to TWRP
3. From TWRP go to Advanced and choose "Flash curent TWRP" - this will permanently install TWRP but will overwrite magisk scripts, so root will be lost.
4. Flash magisk from TWRP - this will fix root.

Thanks bro.
will this lost data or need to clear any caches after done installation TWRP?

you loose nothing and no caches to clear

geraldine said:
you loose nothing and no caches to clear
Click to expand...
Click to collapse
Well noted that.
I've tried and success!
Thanks again!

3.8.4
skkk/TWRP/A12/v3.8.4_A12 • AKR DL
dl.akr-developers.com

update 3.9
skkk/TWRP/A12/v3.9_A12 • AKR DL
dl.akr-developers.com

What does "boot" or "REC" mean? I always thought twrp is just a one file?

REC it's for direct flash the recovery with "fastboot flash recovery.img" (doesn't work for me)
BOOT it's for boot to the recovery "fastboot boot recovery.img" to flash permently go to advanced and "flash current twrp" (work great)

geraldine said:
update 3.9
skkk/TWRP/A12/v3.9_A12 • AKR DL
dl.akr-developers.com
Click to expand...
Click to collapse
Can I update from 3.8?
What is the changelog?

Yes, but you lose root. if there is.

double post, sorrry**

mmm, dont work for me, idk if im doing something wrong, when i put the command (fastboot boot recovery_name.img) it restarts, but the screen stays black and need the force the start.
I download this [BOOT]3.6.2_12-Mi12_v3.9_A12-cupid-skkk_632fca0d.img maybe im wrong with the version =/

darkevangelion said:
mmm, dont work for me, idk if im doing something wrong, when i put the command (fastboot boot recovery_name.img) it restarts, but the screen stays black and need the force the start.
I download this [BOOT]3.6.2_12-Mi12_v3.9_A12-cupid-skkk_632fca0d.img maybe im wrong with the version =/
Click to expand...
Click to collapse
There is a newer:
Downloading • AKR DL

immerzu2 said:
There is a newer:
Downloading • AKR DL
Click to expand...
Click to collapse
Thank you!! this version work, is it reccommended to make it permanent? i dont use root or magisk.

Hello. I have the latest TWRP installed on my Xiaomi 12. A friend of mine installed it. I would like to learn it, but the command "fasboot boot twrp.img" doesn't work for me. I don't know what I'm doing wrong, but the phone still won't boot into TWRP. I'm using ADB minimal and I renamed the downloaded file to twrp.img and put it in ADB minimal, then I used the command mentioned above, but still nothing happens, the phone won't enter TWRP. Once it enters TWRP, I use the command: "flash current twrp", I already know the next procedure. I welcome help. Thanks

Benoni1 said:
Hello. I have the latest TWRP installed on my Xiaomi 12. A friend of mine installed it. I would like to learn it, but the command "fasboot boot twrp.img" doesn't work for me. I don't know what I'm doing wrong, but the phone still won't boot into TWRP. I'm using ADB minimal and I renamed the downloaded file to twrp.img and put it in ADB minimal, then I used the command mentioned above, but still nothing happens, the phone won't enter TWRP. Once it enters TWRP, I use the command: "flash current twrp", I already know the next procedure. I welcome help. Thanks
Click to expand...
Click to collapse
" I would like to learn it, but the command "fasboot boot twrp.img" doesn't work for me"
Check with"fastboot devices"CMD or "./fastboot devices"Powershell before
the phone must be in fastboot mode.
CMD=fastboot boot recovery twrp.img
Powershell=./fastboot boot recovery twrp.img
Then use the twrp
go to Advanced > Flash Current TWRP
The Twrp .img must be in the same folder as the command.
Possibly post the screenshot of the result of the command

Flash TWRP-I still can't do it, I'm sending pictures

Benoni1 said:
Flash TWRP-I still can't do it, I'm sending pictures
Click to expand...
Click to collapse
Already said in the post above.
1/You wrote "fasboot" instead of fastboot.
2/Download SDK platform-tool extract the folder and put the twrp in it.
https://developer.android.com/studio/releases/platform-tools
3/ use the command from the folder where the twrp is.

NOSS8 said:
Already said in the post above.
1/You wrote "fasboot" instead of fastboot.
2/Download SDK platform-tool extract the folder and put the twrp in it.
https://developer.android.com/studio/releases/platform-tools
3/ use the command from the folder where the twrp is.
View attachment 5688077​
Click to expand...
Click to collapse
Hello, I already know it was successful. Thank you for your help. Best regards, Josef

fastboot flash recovery xxx.img is not correct.
the command is: fastboot flash recovery_ab xxx.img
A question: why the twrp version jumped from from 3.x directly to 5.x?