Database Info

[Q] Stuck on Google logo. Unable to push image file to phone... Please help.

Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.

looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM

Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!

nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.

leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...

leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.

Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......

Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.

You need the drivers.

albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.

Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?

leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782

ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.

leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?

nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".

Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?

kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.

the same issue for me. is there any working solution for that?

I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147

GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing

[UNOFFICIAL][DECRYPTION WORKS] TWRP 3.3.1 for UMIDIGI F1 [20191103]

Introduction
This is an UNOFFICIAL TWRP port for UMIDIGI F1 that works properly with encrypted /data partition in official ROM. I am aware that the UMIDIGI F1 already has TWRP built for it, but none of them seem to have decryption working properly. In fact, every single TWRP, even official ones, for any MT6771 device, seem to have non-functional decryption support. Through some digging I managed to fix decryption at least for UMIDIGI F1, so here is my version of TWRP for the device.
Known Bugs
- Screen may flash on the password-input UI. Anything else is fine though.
This TWRP has been tested with official ROM and my LineageOS 17 port (https://forum.xda-developers.com/android/development/unofficial-lineageos-17-0-umidigi-f1-t3997827) and it works fine.
This is UNTESTED on the F1 Play. ONLY TESTED on regular F1.
Why Bother
Because security matters. Using a cheap device should not mean giving up security, and more importantly, privacy.
Instructions
1. Unlock bootloader
2. Enable ADB debugging in system
3. Execute "adb reboot bootloader" while having your phone connected to PC
4. Execute "fastboot flash recovery <your_downloaded_recovery>.img"
5. Reboot phone while holding Volume Up + Power buttons
Note: The official ROM may overwrite the recovery, so you may need to re-flash the recovery if this behavior isn't prevented either by TWRP or manually.
Downlaods & Sources
20191103: https://github.com/PeterCxy/android_device_umidigi_F1/releases/tag/20191103-twrp
- Fixed issues with Magisk and OpenGAPPS
20191102: https://github.com/PeterCxy/android_device_umidigi_F1/releases/tag/20191102-twrp
Device Tree: https://github.com/PeterCxy/android_device_umidigi_F1/tree/twrp-9.0
Modified TWRP (Required for decryption to work): https://github.com/PeterCxy/android_bootable_recovery

Updated to 20191103

I appreciate your sharing this. I have added "system_image emmc" to the fstab file, so I can flash and backup the system.img
This works good on my F1,
But I tried to make this decrypt work for my other phone with 6771(Bold N1), but couldn't find all same files added to recovery/root from stock firmware.

mrmazak said:
I appreciate your sharing this. I have added "system_image emmc" to the fstab file, so I can flash and backup the system.img
This works good on my F1,
But I tried to make this decrypt work for my other phone with 6771(Bold N1), but couldn't find all same files added to recovery/root from stock firmware.
Click to expand...
Click to collapse
Those files are extracted from vendor.img, but it can be different on different devices, e.g. keymaster version might be different. Also you will need to patch them using `patchelf` to make them use `/sbin/linker64` instead of `/system/bin/linker64`

hello
im willing to port your amazing twrp to our phone UMIDIGI F1 Play and i need permission to do it ???
thanks

Shadow Of Leaf said:
hello
im willing to port your amazing twrp to our phone UMIDIGI F1 Play and i need permission to do it ???
thanks
Click to expand...
Click to collapse
on other releases, no change was needed to boot on both. I would try as is first.
as long as you have working sp flash tool in case of issue.

mrmazak said:
on other releases, no change was needed to boot on both. I would try as is first.
as long as you have working sp flash tool in case of issue.
Click to expand...
Click to collapse
Cause i test it without changes , it reboot to system
I think because they have different kernels

I am unable to install twrp.
When I run the "fasthboot flash recovery" command, cmd aparace "waiting for de ice" and nothing happens on my phone ...
Am I doing something wrong?

no fastboot response
for some reason (most likely pilot error, lol) the phone doesn't show when I do "fastboot devices" - even though the F1's screen shows "fastboot mode" in very tiny letters on the bottom-left.
probably something stupid I'm doing wrong, will keep trying...

tarvoke said:
for some reason (most likely pilot error, lol) the phone doesn't show when I do "fastboot devices" - even though the F1's screen shows "fastboot mode" in very tiny letters on the bottom-left.
probably something stupid I'm doing wrong, will keep trying...
Click to expand...
Click to collapse
You can operate from adb/fastboot folder and device can stay on fastboot mode but if drivers were not properly installed then no connection with pc.
Try installing:
- https://androidmtk.com/download-15-seconds-adb-installer
- https://androidmtk.com/download-mtk-usb-all-drivers
- https://www.androidweblog.com/download-mediatek-usb-vcom-drivers/
Start the process from device on using adb commands to always allow access to the pc. I mean:
Code:
adb devices
and then if device is detected you will see a screen warning to "always allow...." then tap on yes; this suppress future conflicts, then
Code:
adb reboot bootloader
while on fastboot follow with
Code:
fastboot devices

SubwayChamp said:
You can operate from adb/fastboot folder and device can stay on fastboot mode but if drivers were not properly installed then no connection with pc.
Click to expand...
Click to collapse
thanks!
adb was already working (is how I made the thing reboot to bootloader, and yes I did tell it to permanently accept the computer I'm using.
this is on linux, so the drivers shouldn't be a problem... although SMH I never put USB IDs into the udev rules. which is interesting, because regular adb already worked fine without it - I have had phones in the past that some did, some did not, require the computer to know about vendor/hardware ID.
(and I know that the adb USB IDs are usually different than the ID for fastboot, as well.)
like I said, pilot error lol. but thank you again for the reply!

I have done the following:
Enabled Developer Options
Enabled USB Debugging
Enabled OEM Unlocking
Unlocked the bootloader with:
Code:
adb reboot bootloader
fastboot flashing unlock
Rebooted and Enabled USB Debugging again.
Then after downloading your recovery
Code:
adb reboot bootloader
fastboot boot ~/Downloads/recovery.img
But nothing happened.
I rebooted and thought I would try flashing
Code:
adb reboot bootloader
fastboot flash recovery ~/Downloads/recovery.img
It just paused on the boot screen saying "Your device has been unlocked and can't be trusted".
If I reboot then try to go direct to recovery:
Code:
adb reboot recovery
I end up with the broken android screen and "No command"
What am I missing?

opticyclic said:
I have done the following:
Enabled Developer Options
Enabled USB Debugging
Enabled OEM Unlocking
Unlocked the bootloader with:
Code:
adb reboot bootloader
fastboot flashing unlock
Rebooted and Enabled USB Debugging again.
Then after downloading your recovery
Code:
adb reboot bootloader
fastboot boot ~/Downloads/recovery.img
But nothing happened.
I rebooted and thought I would try flashing
Code:
adb reboot bootloader
fastboot flash recovery ~/Downloads/recovery.img
It just paused on the boot screen saying "Your device has been unlocked and can't be trusted".
If I reboot then try to go direct to recovery:
Code:
adb reboot recovery
I end up with the broken android screen and "No command"
What am I missing?
Click to expand...
Click to collapse
While in fastboot the first you should do is see if device is detected by pc with
Code:
fastboot devices
It looks like something is wrong with your path, I ever avoid path copying or moving the file/image to the adb/fastboot directory but anyway if you don´t want to do it you can copy the path from the bar where your recovery file is allocated, for example, if the file is in Downloads directory like it seems actually is, no matter what unit/drive you are in you can set an absolute value to avoid errors, look at this example: C:\Users\your_user\Downloads
If your device is detected then you can flash the recovery as you were trying to do it with
Code:
fastboot flash recovery recovery.img
and then you can reboot directly to it without need to reboot to system previously and this will prevent TWRP from being overwritten, with
Code:
fastboot boot recovery.img

hmm, so when I checked the udev rules, it already had one for MTK/mediatek - and the USB vendor is '08ed' in fastboot as well as in regular adb, so it wasn't a problem with udev/plugdev.
which I guess may mean the lunix generic android drivers for fastboot might be... "lacking" - I'll have to scrounge up a win7 laptop and try the recommended windows drivers.

SubwayChamp said:
...
It looks like something is wrong with your path, I ever avoid path copying or moving the file/image to the adb/fastboot directory but anyway if you don´t want to do it you can copy the path from the bar where your recovery file is allocated, for example, if the file is in Downloads directory like it seems actually is, no matter what unit/drive you are in you can set an absolute value to avoid errors, look at this example: C:\Users\your_user\Downloads
...
Click to expand...
Click to collapse
I don't think it was anything to do with the path as it output the file transfer size.
I think it was a combination of the following:
I wasn't pressing the right combinations of buttons after flashing.
i.e. holding VOL UP and pressing POWER on the screen saying "Your device has been unlocked and can't be trusted".
Rebooting might (?) have been reverting the recovery.
I was originally trying this on the firmware that was shipped 2019012414 but after flashing 2019090418 with SPFlashTool I had more success.
I also able to reboot to recovery directly after flashing with fastboot with the following:
Code:
fastboot oem reboot-recovery
Whichever was the key I can now reboot to recovery from adb too.
:good:

Your twrp eliminates fingerprint authentication.
I discovered something interesting, your twrp only works on my device, no other twrp works, but when I install it, I lose my fingerprint, it doesn't work at all.
Simply put, I must choose between the fingerprint or the root.

LyrielAlk said:
No other twrp works, but when I install it, I lose my fingerprint, it doesn't work at all.
Simply put, I must choose between the fingerprint or the root.
Click to expand...
Click to collapse
Try to clean flash last vendor build with spflash tool. First boot need stock recovery.
You don't need custom recovery to achieve root.
Maybe give a try to SNwriter (I never needed it though and can't help here).

Both of those twrp are not sticking. I have flashed with spoken flash tool v5 1944 win and I fastboot cmd with the same results.

Thanks
Gracias for this master ?

good
Shadow Of Leaf said:
hello
im willing to port your amazing twrp to our phone UMIDIGI F1 Play and i need permission to do it ???
thanks
Click to expand...
Click to collapse
good idea

Flash to stock firmware from T-Mobile

I am trying to flash to stock/global firmware from T-Mobiles. I have already unlocked the bootloader but I am confused on what to do next. Some people say all you need to do is flash the system and boot images. But when i try to flash the system it says unknown partition. If I try to flash everything it says Critical partitions can not be flashed and I dont know how to unlock them, fastboot flashing unlock_critical is an unknown command. Please help!

Try on adb using " adb reboot fastboot" reboot to fastbootd and flash system, vendor.

hendavi said:
Try on adb using " adb reboot fastboot" reboot to fastbootd and flash system, vendor.
Click to expand...
Click to collapse
Ive progressed a bit and decided to use MSM Download Tool. Although I cant seem to get into EDL mode. My phone is bricked so i cant use adb, and fastboot commands dont seem to be working. Ive tried button combinations but they just lead me either into recovery mode or fastboot mode.

In fastboot, type fastboot reboot fastboot see whether can boot into fastbootd or not.

yoboy44 said:
Ive progressed a bit and decided to use MSM Download Tool. Although I cant seem to get into EDL mode. My phone is bricked so i cant use adb, and fastboot commands dont seem to be working. Ive tried button combinations but they just lead me either into recovery mode or fastboot mode.
Click to expand...
Click to collapse
This is a very simple fix. You can boot into fastboot, do that again, and flash LineageOS Recovery while your there
Boot into recovery, choose advanced options, than enable ADB. Boom, now you can use ADB on your bricked phone.
.
The command you're looking for once there is "adb reboot edl"
Also a lot of the guides on how to convert to Global either use broken methods, or link to the wrong files. If I had a dollar eveytime someone messaged me about following a guide and ending in crash dump mode I'd have a lot of dollars. DM me if you wanna know how to get to global and you're struggling.

Question OnePlus 9 LE2110 256GB No OS No Recovery

As the title says, I have no OS and only have fastboot available.
I unlocked the bootloader and pushed TWRP 3.5.1_10-Nebrassy so that I could root with Magisk.
fastboot boot twrp.img
All went well to that point. Then I tried to flash TWRP.
fastboot flash recovery twrp.img
Then I had no OS. I tried to download the latest stock ROM, 11.2.9.9.LE25DA.
https://www.oneplus.in/support/softwareupgrade/details?code=PM1617074715494
I extracted the payload.bin and successfully flashed the files to fastboot.
https://www.droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/
Then I try to boot into fastbootd to install the other files.
fastboot reboot fastboot
Once in fastbootd, I have to choose a language from (I presume) Mandarin, Cantonese, and English. I choose English.
Then it says "fastbootd" across the top, but the cmd window is unresponsive, "< waiting for any device >"
I have to choose Advanced, or Exit.
I choose Advanced.
I have to choose "Reboot to fastboot," "Reboot to recovery," or "Ver 2.0"
I choose Reboot to fastboot because there is no recovery.
cmd is responsive, but I'm in fastboot, not fastbootd.
I try to flash the remaining files.
fastboot flash abl abl.img
I get the following message from the cmd window.
FAILED: <remote: 'Flashing is not allowed for Critical Partitions'>
fastboot error: error: Command failed
Obviously, because I'm not in fastbootd. Except I can't get a responsive cmd prompt in fastbootd.
I have also tried to flash TWRP again. It does not flash. I can push it over and it will boot up, but the touch screen is not responsive, so I have to hard reset to get back to fastboot.
fastboot boot twrp.img
So, at this point, all I have is fastboot and a bootloop.
Would someone please either direct me to a forum where this has been addressed (that I have obviously missed in my search), or please advise how to proceed? I would very much appreciate whatever guidance anyone can offer.

DoktorNo said:
As the title says, I have no OS and only have fastboot available.
I unlocked the bootloader and pushed TWRP 3.5.1_10-Nebrassy so that I could root with Magisk.
fastboot boot twrp.img
All went well to that point. Then I tried to flash TWRP.
fastboot flash recovery twrp.img
Then I had no OS. I tried to download the latest stock ROM, 11.2.9.9.LE25DA.
https://www.oneplus.in/support/softwareupgrade/details?code=PM1617074715494
I extracted the payload.bin and successfully flashed the files to fastboot.
https://www.droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/
Then I try to boot into fastbootd to install the other files.
fastboot reboot fastboot
Once in fastbootd, I have to choose a language from (I presume) Mandarin, Cantonese, and English. I choose English.
Then it says "fastbootd" across the top, but the cmd window is unresponsive, "< waiting for any device >"
I have to choose Advanced, or Exit.
I choose Advanced.
I have to choose "Reboot to fastboot," "Reboot to recovery," or "Ver 2.0"
I choose Reboot to fastboot because there is no recovery.
cmd is responsive, but I'm in fastboot, not fastbootd.
I try to flash the remaining files.
fastboot flash abl abl.img
I get the following message from the cmd window.
FAILED: <remote: 'Flashing is not allowed for Critical Partitions'>
fastboot error: error: Command failed
Obviously, because I'm not in fastbootd. Except I can't get a responsive cmd prompt in fastbootd.
I have also tried to flash TWRP again. It does not flash. I can push it over and it will boot up, but the touch screen is not responsive, so I have to hard reset to get back to fastboot.
fastboot boot twrp.img
So, at this point, all I have is fastboot and a bootloop.
Would someone please either direct me to a forum where this has been addressed (that I have obviously missed in my search), or please advise how to proceed? I would very much appreciate whatever guidance anyone can offer.
Click to expand...
Click to collapse
Try:
fastboot flashing unlock
then
fastboot flashing unlock_critical

Thank you for the reply.
The device is already unlocked, but I did as you suggested and tried both commands.
For both attempts I got the following message:
FAILED <remote : ' Device already : unlocked!'>
Fastboot: error: Command failed.

@DoktorNo you don't flash twrp that way anymore. You have to boot into twrp, then flash from inside twrp itelf.
So
fastboot boot twrp.img
Then once twrp starts up, go to the advanced tab, and flash the recovery.

mx597turbo said:
@DoktorNo you don't flash twrp that way anymore. You have to boot into twrp, then flash from inside twrp itelf.
So
fastboot boot twrp.img
Then once twrp starts up, go to the advanced tab, and flash the recovery.
Click to expand...
Click to collapse
Great suggestion, except when I boot into twrp, I cannot use the touch screen. So twrp will boot, but it is not responsive. Any thoughts on how to make that work? Then I'd be nearly set.

Does the msm tool not work for you? I have to use the one plus 9 pro in version to restore mine.. And you can try sideloading the ota

XxBigBuckxX said:
Does the msm tool not work for you? I have to use the one plus 9 pro in version to restore mine.. And you can try sideloading the ota
Click to expand...
Click to collapse
I haven't tried it. I'll give it a go when I'm home this evening and post my results.

DoktorNo said:
I haven't tried it. I'll give it a go when I'm home this evening and post my results.
Click to expand...
Click to collapse
Also, are you using the most updated version of twrp for the 9/9 pro? I'm sure you are, but just checking.

mx597turbo said:
Also, are you using the most updated version of twrp for the 9/9 pro? I'm sure you are, but just checking.
Click to expand...
Click to collapse
Great question and worth asking. I used twrp 3.5.1_lemonade-Nebrassy.
3.5.1-lemonadep-Nebrassy
Since there's no OS, there is no interface with the touchscreen, so I can't interact with it in that way. I can sideload twrp but then it's just an image on the screen.

There is a newer one TWRP-3.5.2-lemonadep-Nebrassy. If your unable to use twrp to flash or sideload MSM Tool is pretty simple. Use the original cable and put it EDL mode and run it.

DoktorNo said:
Great suggestion, except when I boot into twrp, I cannot use the touch screen. So twrp will boot, but it is not responsive. Any thoughts on how to make that work? Then I'd be nearly set.
Click to expand...
Click to collapse
Just a thought, as I am unable to test. What if you plugged a usb mouse into the phone using an A to C adapter? May be worth a try, but not sure if twrp has mouse support. I have an adapter somewhere - If I find it, I'll let know know if this works.

mx597turbo said:
Just a thought, as I am unable to test. What if you plugged a usb mouse into the phone using an A to C adapter? May be worth a try, but not sure if twrp has mouse support. I have an adapter somewhere - If I find it, I'll let know know if this works.
Click to expand...
Click to collapse
This works , mouse and keyboard

XxBigBuckxX said:
Does the msm tool not work for you? I have to use the one plus 9 pro in version to restore mine.. And you can try sideloading the ota
Click to expand...
Click to collapse
Msm will not download from the link you provided. GDrive scans the .exe and dll files before download and says there is a virus, so I am only able to download the other half of the files.

XxBigBuckxX said:
There is a newer one TWRP-3.5.2-lemonadep-Nebrassy. If your unable to use twrp to flash or sideload MSM Tool is pretty simple. Use the original cable and put it EDL mode and run it.
Click to expand...
Click to collapse
Got the new twrp. Still no touch screen.

mx597turbo said:
Just a thought, as I am unable to test. What if you plugged a usb mouse into the phone using an A to C adapter? May be worth a try, but not sure if twrp has mouse support. I have an adapter somewhere - If I find it, I'll let know know if this works.
Click to expand...
Click to collapse
I will have to buy an adapter.

Here , that was more of a guide. List of unbrick tools select your proper one from here. If you get errors try the One Plus 9 Pro IN version as that what worked with nothing else for a lot of people including me.

DoktorNo said:
Msm will not download from the link you provided. GDrive scans the .exe and dll files before download and says there is a virus, so I am only able to download the other half of the files.
Click to expand...
Click to collapse
Last thing you will need is the driver, here is the signed Microsoft version.
Power off the phone.
Plug in the USB cable your computer but do not connect the other end to the phone.
I Find it easier to have push start on msm tool at this point
Hold down Volume Up and Volume Down buttons for a few seconds, and plug in the cable while you are continuing to hold them. and it should connect and flash.

XxBigBuckxX said:
Here , that was more of a guide. List of unbrick tools select your proper one from here. If you get errors try the One Plus 9 Pro IN version as that what worked with nothing else for a lot of people including me.
Click to expand...
Click to collapse
Downloading now. I'll try this and report back. Thanks.

DoktorNo said:
Downloading now. I'll try this and report back. Thanks.
Click to expand...
Click to collapse
Okay and you might have to try it power cycle it a few times trying to get into edl mode especially if you do not already have working drivers. But windows update will pull working drivers as well if your not sure how to use a .cab file. There are guides everywhere even video if if you need. I've tested some weird things on the 7t pro McLaren and 9 pro and msm tool has always brought them back.

hj

Rooting Tecno LC8. or tecno power pro 2.

I recently got my hands on Tecno LC8 and am amazed by how good it is. Sadly its a bit hard to root BUT I have done necessary work for all of you.
### Instructions
1. Update to LC8-H6215ABCD-Q-GL-220402V350
2. connect to a laptop/pc with adb tools installed.
3. type in terminal adb reboot fastboot
4. When phone start in fastboot mode (It comes with a animation of usb cable with bluish glow)
5. Type in terminal
fastboot flash vbmeta_vendor vbmeta.img
fastboot flash vbmeta_system vbmeta.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
6. Install Magisk.apk from their release page https://github.com/topjohnwu/Magisk/releases/
7. Enjoy
Now time for cons
- This your whole system may or maynot be formatted. I invite for anyone to confirm it.
- SafetyNet works?????? Idk and can neither confirm it. again I invite for anyone to confirm it. This device is for very specific purpose
- TWRP? I can make it yes. But please just no I am providing with recovery image. If you wanna have a go at it go for it. It will be highly appreciated.
- You wanna go full AOSP on this device??
I already tried it. GSI project treble is comaptible with device "x64 ab partition img" But dual sim support is wonky. Flashlight won't work readily My advice is to extract the mediatek sim processor and replace it with GSI google sim processor and whole mediatek tree.
BUT if you have only one sim card go wild you can install GSI on nearly mediatek device with project treble support.
If you wanna install custom rom without TWRP.
Do this
[WARNING ROOT NEEDED]
fastboot delete-logical-partition product
fastboot flash system [your custom rom file location]
fastboot -w
fastboot reboot
Tecno LC8 support "x64ab partition" images.

Thanks YOU , About to follow your steps , I was direct here from https://www.hovatek.com/forum/thread-42975-post-232022.html#pid232022

Harfho said:
Thanks YOU , About to follow your steps , I was direct here from https://www.hovatek.com/forum/thread-42975-post-232022.html#pid232022
Click to expand...
Click to collapse
so the commad that works for me was
fastboot flash boot boot.img
fastboot flash boot.img does not work ,
error getting was
unknown partition 'boot.img'
fastboot: error: cannot determine image filename for 'boot.img'

Harfho said:
so the commad that works for me was
fastboot flash boot boot.img
fastboot flash boot.img does not work ,
error getting was
unknown partition 'boot.img'
fastboot: error: cannot determine image filename for 'boot.img'
Click to expand...
Click to collapse
Thanks for bringing it to my attention. command should be
fastboot flash boot boot.img
I will correct it asap

Carnalthot said:
Thanks for bringing it to my attention. command should be
fastboot flash boot boot.img
I will correct it asap
Click to expand...
Click to collapse
is there any way I can contact you I have more phone I needed to root, I just want you to explain HOWTO and what NOTO do
I have infinix S5Lite
infinix Hot 9
That I want to root also

Harfho said:
is there any way I can contact you I have more phone I needed to root, I just want you to explain HOWTO and what NOTO do
I have infinix S5Lite
infinix Hot 9
That I want to root also
Click to expand...
Click to collapse
I have no problem teaching you.
I do things thrifty. I preferrably use linux to root basically. BUT windows is also pretty good to root android you need platform tools and adb.
the sure fire way to root chinese phones is
1. Unlock bootloader
2. Open flashing privileges (FRP unlock, unlocking phones etc different company calls it differently)
3. Have an understanding of boot verifiers (vbmeta stands for verify boot metadata ) Nowadays phone verifies boot image by vbmeta_product vbmeta_vendor and vbmeta itself
You have to make all of them blank so nothing verifies your boot image on start up
I suggest downloading a firmware of your phone model to understand the partitions system of your phone model
4. Extract your boot image and vbmeta with mtkclient
5. Now patch your boot image. You can do it by hand or by magisk.
6. Flash every vbmeta with blank-vbmeta and boot with patched_boot
7. TWRP is optional DON'T do it if you have only one phone. Always have backup if you want to touch recovery partition
WHAT TO LOOK OUT FOR
1. update versions. Chinese Kernel update are very sensitive to version numbers. Don't flash v290 boot.img on v350 boot.img. It will brick instantanously.
2. Always learn how to flash your phone model. It saves a lot of headache.
3. Don't be afraid to ask for help.
4. Don't be afraid to throw your phone in anger. No no Seriously. To root a phone is to insist on ownership and if phone denies that it is totally reasonable to obliterate the said phone. I actually mean the last advice.

So can i use the
Carnalthot said:
I have no problem teaching you.
I do things thrifty. I preferrably use linux to root basically. BUT windows is also pretty good to root android you need platform tools and adb.
the sure fire way to root chinese phones is
1. Unlock bootloader
2. Open flashing privileges (FRP unlock, unlocking phones etc different company calls it differently)
3. Have an understanding of boot verifiers (vbmeta stands for verify boot metadata ) Nowadays phone verifies boot image by vbmeta_product vbmeta_vendor and vbmeta itself
You have to make all of them blank so nothing verifies your boot image on start up
I suggest downloading a firmware of your phone model to understand the partitions system of your phone model
4. Extract your boot image and vbmeta with mtkclient
5. Now patch your boot image. You can do it by hand or by magisk.
6. Flash every vbmeta with blank-vbmeta and boot with patched_boot
7. TWRP is optional DON'T do it if you have only one phone. Always have backup if you want to touch recovery partition
WHAT TO LOOK OUT FOR
1. update versions. Chinese Kernel update are very sensitive to version numbers. Don't flash v290 boot.img on v350 boot.img. It will brick instantanously.
2. Always learn how to flash your phone model. It saves a lot of headache.
3. Don't be afraid to ask for help.
4. Don't be afraid to throw your phone in anger. No no Seriously. To root a phone is to insist on ownership and if phone denies that it is totally reasonable to obliterate the said phone. I actually mean the last advice.
Click to expand...
Click to collapse
So i can use this vbmeta for other china phones ,
The hard things is getting boot.img
I’m on limited plan , to download heavy files just to get boot.img out of it is a concern for me.

Harfho said:
So can i use the
So i can use this vbmeta for other china phones ,
The hard things is getting boot.img
I’m on limited plan , to download heavy files just to get boot.img out of it is a concern for me.
Click to expand...
Click to collapse
Hmm you need to get boot.img from your own phone by using mtkclient application. Downloading firmware is to understand about the partition system of your phone. ALWAYS use your own phone boot.img

Carnalthot said:
Hmm you need to get boot.img from your own phone by using mtkclient application. Downloading firmware is to understand about the partition system of your phone. ALWAYS use your own phone boot.img
Click to expand...
Click to collapse
So i can use this vbmeta for other china phones?
and am stock on this on mtkclient
Power off the phone before connecting.
For brom mode, press and hold vol up, vol dwn, or all hw buttons and connect usb.
For preloader mode, don't press any hw button and connect usb.
If it is already connected and on, hold power for 10 seconds to reset.

Harfho said:
So i can use this vbmeta for other china phones?
and am stock on this on mtkclient
Power off the phone before connecting.
For brom mode, press and hold vol up, vol dwn, or all hw buttons and connect usb.
For preloader mode, don't press any hw button and connect usb.
If it is already connected and on, hold power for 10 seconds to reset.
Click to expand...
Click to collapse
Yes you can use vbmeta for other china phone it's blank vbmeta.
And you are right on money for Brom mode. Preloader mode is hit and trial method for Chinese phones

Carnalthot said:
Yes you can use vbmeta for other china phone it's blank vbmeta.
And you are right on money for Brom mode. Preloader mode is hit and trial method for Chinese phones
Click to expand...
Click to collapse
Sorry I don’t get this
“And you are right on money for Brom Mode.”

Harfho said:
Sorry I don’t get this
“And you are right on money for Brom Mode.”
Click to expand...
Click to collapse
To access Brom mode you need to either remove battery/power off phone then while holding volume up/down button connect the usb cable with pc. PC should be listening for any Brom connections when you connect the phone.

Carnalthot said:
To access Brom mode you need to either remove battery/power off phone then while holding volume up/down button connect the usb cable with pc. PC should be listening for any Brom connections when you connect the phone.
Click to expand...
Click to collapse
I Did that to no avail

Harfho said:
I Did that to no avail
Click to expand...
Click to collapse
Did you do frp unlock?

No, i have not

Do a frp unlock without it you cannot flash.
Actually to root your phone you don't need Brom mode

Carnalthot said:
Do a frp unlock without it you cannot flash.
Actually to root your phone you don't need Brom mode
Click to expand...
Click to collapse
Yes, wanted to get the boot.img of the phone first and patched it , so i can run all the commands at once.
oR without unlock bootloader I can’t get the boot.img with mtkclient?

Harfho said:
Yes, wanted to get the boot.img of the phone first and patched it , so i can run all the commands at once.
oR without unlock bootloader I can’t get the boot.img with mtkclient?
Click to expand...
Click to collapse
To get boot.img you need frp unlock.

Carnalthot said:
To get boot.img you need frp unlock.
Click to expand...
Click to collapse
Ok thanks, I will do that.
frp unlock also mean bootloader unlock?

Harfho said:
Ok thanks, I will do that.
frp unlock also mean bootloader unlock?
Click to expand...
Click to collapse
Nope