Related
hello I am currently in need of of some serious help right now I have a one plus 7 pro tmobile variant and I switched it into international with twrp and all that after that I started messing with the twrp settings and the phone wouldent boot up but would stay in fastboot mode luckily I could just switch to different slot I was on a now im on b but now I tried to remove twrp and tried to get the phone back to normal I think both slots are messed up both slot a and b wont boot the phone and the phone just keeps rebooting itself into fastboot mode I cant go into recovery and I cant go into anything but fastboot mode I locked the bootloader to see if it will do anything now its still in fastboot mode and I cant flash anything because the phone wont unlock its bootloader now I don't know what to do pls help it would be greatly appreciated
@AshAe
Being on slot B to leave fastboot mode try
Code:
fastboot devices
fastboot --set-active=a
to boot device to (normal) Android OS kept in slot A: wait for response OKAY before re-starting phone !!!
BTW:
TWRP once installed can never get uninstalled, unless you re-flash Stock ROM.
jwoegerbauer said:
@AshAe
Being on slot B to leave fastboot mode try
Code:
fastboot devices
fastboot --set-active=a
to boot device to (normal) Android OS kept in slot A: wait for response OKAY before re-starting phone !!!
BTW:
TWRP once installed can never get uninstalled, unless you re-flash Stock ROM.
Click to expand...
Click to collapse
slot a dosent work either
AshAe said:
slot a dosent work either
Click to expand...
Click to collapse
Because fastboot obviously is working, what means you can enter device's bootloader, run
Code:
fastboot devices
fastboot boot twrp.img
to get access to TWRP: from there re-flash phone with its Stock ROM
Note: It's NO GOOD IDEA to install TWRP on Android with A/B-ed partition system.
1. bootloader is unlocked and confirmed
2. im running on a Realme Q latest Stock Rom RMX1971_11_C.08
3 ADB and USB debuging are properly setup.
4. I have tried the following recoveries, none working.
-recovery-TWRP-3.3.2B-0227-REALME_Q-CN-wzsx150.img
-OrangeFox-HOMEMADE-RMX1971.img
-OrangeFox-R11.0_0-Stable-RMX1971.img
-twrp-RMX1971-20191121.img
ABD always confirm to push the recovery file succesfully but everytime I boot in recovery, I get the Realme UI recovery.
What I'm I doing wrong ?????
jungl1st said:
1. bootloader is unlocked and confirmed
2. im running on a Realme Q latest Stock Rom RMX1971_11_C.08
3 ADB and USB debuging are properly setup.
4. I have tried the following recoveries, none working.
-recovery-TWRP-3.3.2B-0227-REALME_Q-CN-wzsx150.img
-OrangeFox-HOMEMADE-RMX1971.img
-OrangeFox-R11.0_0-Stable-RMX1971.img
-twrp-RMX1971-20191121.img
ABD always confirm to push the recovery file succesfully but everytime I boot in recovery, I get the Realme UI recovery.
What I'm I doing wrong ?????
Click to expand...
Click to collapse
Ah yes. I've ran into similar issues last time I tried to revert from Pixel Experience Android 11 to stock RMQ firmware. I noticed if you start sending the recovery with fastboot flash recovery twrp.img, the fastboot cmd waits for device, you enter fastboot mode and then connect to the PC via usb 2.0 port the recovery will be successfully flashed BUT only that one file, whatever you want to flash next time for example vbmeta or system, vendor.img you'll have to repeat the cycle. Disconnect the usb cable, enter the flashing command to fastboot cmd on PC, boot back again to fastboot mode on your phone then connect the usb cable. This solved the issue for me.
greenys' said:
Ah yes. I've ran into similar issues last time I tried to revert from Pixel Experience Android 11 to stock RMQ firmware. I noticed if you start sending the recovery with fastboot flash recovery twrp.img, the fastboot cmd waits for device, you enter fastboot mode and then connect to the PC via usb 2.0 port the recovery will be successfully flashed BUT only that one file, whatever you want to flash next time for example vbmeta or system, vendor.img you'll have to repeat the cycle. Disconnect the usb cable, enter the flashing command to fastboot cmd on PC, boot back again to fastboot mode on your phone then connect the usb cable. This solved the issue for me.
Click to expand...
Click to collapse
Thank you very much for the tip ! I shall give it a try as soon as I'm back home , since I'm on holiday now and don't have the device !
jungl1st said:
Thank you very much for the tip ! I shall give it a try as soon as I'm back home , since I'm on holiday now and don't have the device !
Click to expand...
Click to collapse
It's worth a try for sure. Yesterday it took me more than 6 hours to set up a working RUI after Pixel Experience. One of these issues was that I couldn't flash custom recovery and vbmeta. I Always keep a modified vbmeta and twrp.img on my external SD card once I successfully managed to boot up into twrp after fastboot flash. Remember, keeping custom recovery installed should be your number one priority for you can pretty much solve anything with it.
greenys' said:
It's worth a try for sure. Yesterday it took me more than 6 hours to set up a working RUI after Pixel Experience. One of these issues was that I couldn't flash custom recovery and vbmeta. I Always keep a modified vbmeta and twrp.img on my external SD card once I successfully managed to boot up into twrp after fastboot flash. Remember, keeping custom recovery installed should be your number one priority for you can pretty much solve anything with it.
Click to expand...
Click to collapse
indeeed, custom recovery is the turning point to recover almost anything ! given the point that one manages to install it in the first place
greenys' said:
It's worth a try for sure. Yesterday it took me more than 6 hours to set up a working RUI after Pixel Experience. One of these issues was that I couldn't flash custom recovery and vbmeta. I Always keep a modified vbmeta and twrp.img on my external SD card once I successfully managed to boot up into twrp after fastboot flash. Remember, keeping custom recovery installed should be your number one priority for you can pretty much solve anything with it.
Click to expand...
Click to collapse
Hi, I actually managed to flash the recovery, how ever it seem not to properly overwrite the original recovery.
I mean, i can flash and boot in to TWRP, only once at a time, once I exit TWRP and reboot into recovery, I land into the Realme recovery again !!!!! dont know whats wrong
Is there any way to get root/custom recovery/custom roms on the A502DL or A501DL? If so, how?
lehmancurtis said:
Use the boot mode tool from here for the a501dl. It definitely is unlockable! You can grab the TWRP.img I compiled for the a501dl from this link.
Click to expand...
Click to collapse
Bump. I found some information, but unfortunately the instructions are not very clear. I assume lehmancurtis means to go to fastboot with the boot mode tool, and then flash the TWRP.img with adb. However, I am not sure if this is the right way to do things and I do not have adb drivers for the A501DL or A502DL.
lmgnsa said:
Bump. I found some information, but unfortunately the instructions are not very clear. I assume lehmancurtis means to go to fastboot with the boot mode tool, and then flash the TWRP.img with adb. However, I am not sure if this is the right way to do things and I do not have adb drivers for the A501DL or A502DL.
Click to expand...
Click to collapse
adb and fastboot include a generic Google driver and the VCOM driver installer for mtk includes what you'll need. Once in fastboot...
Code:
fastboot oem unlock-go
Follow the instructions on your device to unlock the bootloader. Then boot to system and reboot to fastboot with bootmode tool. Once in fastboot...
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot oem reboot-recovery
Then it should boot to TWRP. Be sure to format data f2fs to remove encryption so you can mount data.
And you will need to install Magisk from recovery to have root and keep. OEM recovery from replacing TWRP.
lehmancurtis said:
adb and fastboot include a generic Google driver and the VCOM driver installer for mtk includes what you'll need. Once in fastboot...
Code:
fastboot oem unlock-go
Follow the instructions on your device to unlock the bootloader. Then boot to system and reboot to fastboot with bootmode tool. Once in fastboot...
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot own reboot-recovery
Then it should boot to TWRP. Be sure to format data f2fs to remove encryption so you can mount data.
And you will need to install Magisk from recovery to have root and keep. OEM recovery from replacing TWRP.
Click to expand...
Click to collapse
Just to confirm:
To prevent the OEM recovery from replacing TWRP, I have to flash Magisk.
If I flashed a gsi, would this problem still be present?
edit: if I wanted to flash a gsi, would I be able to flash "A" only roms, "AB" only roms, or A/AB roms?
edit2: @lehmancurtis plz help me
@lehmancurtis : How do you get the a502dl into fastboot mode? I have tried everything that I can think of, and nothing works! Thank you for all of your help, m8!
fliproc said:
@lehmancurtis : How do you get the a502dl into fastboot mode? I have tried everything that I can think of, and nothing works! Thank you for all of your help, m8!
Click to expand...
Click to collapse
Use a tool that controls bootmode. Mtk-mode-selector
lehmancurtis said:
Use a tool that controls bootmode. Mtk-mode-selector
Click to expand...
Click to collapse
Please help, it says "waiting port" forever
Thanks for the reply! I tried this tool, along with adb commands, etc., and I just can't even get fastboot. This would be an AWESOME phone, if not for this dumb crap!! The phone I had before this one is a Z717VL, and it sucks as well. They are both Tracfone phones that were given to me by my wife. I think I'll just get a Galaxy S8 or so and just root it instead. All other phones that I had on Verizon in the past have been super easy... just a One-Click-Root. Thanks everyone for your time and help!
lehmancurtis said:
adb and fastboot include a generic Google driver and the VCOM driver installer for mtk includes what you'll need. Once in fastboot...
Code:
fastboot oem unlock-go
Follow the instructions on your device to unlock the bootloader. Then boot to system and reboot to fastboot with bootmode tool. Once in fastboot...
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot own reboot-recovery
Then it should boot to TWRP. Be sure to format data f2fs to remove encryption so you can mount data.
And you will need to install Magisk from recovery to have root and keep. OEM recovery from replacing TWRP.
Click to expand...
Click to collapse
lehmancurtis said:
Use a tool that controls bootmode. Mtk-mode-selector
Click to expand...
Click to collapse
Are you sure the method you thought of works? The bootmode tool you linked cannot get the A501DL to fastboot mode, it just says "waiting port" forever.
@lehmancurtis I feel like you might be lying about whether or not your method works, as the boot mode tool does not work. @lmgnsa did it work for you?
I got it to work by loading the boot mode tool, selecting fastboot, and plugging the phone in when it is turned off while holding volume down.
Then you can unlock the bootloader.
williamhancock328` said:
I got it to work by loading the boot mode tool, selecting fastboot, and plugging the phone in when it is turned off while holding volume down.
Then you can unlock the bootloader.
Click to expand...
Click to collapse
I cannot get to fastboot even if I follow these steps... @williamhancock328` @lehmancurtis
It still says "waiting port" forever.
Make sure to install the MTK VCOM drivers first, the android drivers from google or samsung will not work!
Mediatek USB VCOM Drivers (all MTK devices).zip | by www.foldertips.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I was able to bootloader unlock my Alcatel 3T 8, even being on tmobile using the boot selector tool
mickeybeats said:
Make sure to install the MTK VCOM drivers first, the android drivers from google or samsung will not work!
Mediatek USB VCOM Drivers (all MTK devices).zip | by www.foldertips.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I was able to bootloader unlock my Alcatel 3T 8, even being on tmobile using the boot selector tool
Click to expand...
Click to collapse
I have already installed the MTK VCOM drivers multiple times, I don't know why it still doesn't work.
T
lmgnsa said:
Just to confirm:
To prevent the OEM recovery from replacing TWRP, I have to flash Magisk.
If I flashed a gsi, would this problem still be present?
edit: if I wanted to flash a gsi, would I be able to flash "A" only roms, "AB" only roms, or A/AB roms?
edit2: @lehmancurtis plz help me
Click to expand...
Click to collapse
lmgnsa said:
To keep recovery from being replace several files need to be disable (various approaches are effective i.e. removed, replace, or renamed). Magisk usually handles this task, but sometimes there are exceptions. But, you need to address that before flashing gsi's for multiple reason and none are fun to deal with. Yes, this is A only and does not use A/B update method (at least not entirely as a few partitions are making use of the A/B partition labels). I've not been doing much with this particular device since mine was cracked and the usb port messed up when I got it, so nature took its course before I was able to achieve a fully stable custom setup.
Click to expand...
Click to collapse
sj78 said:
I cannot get to fastboot even if I follow these steps... @williamhancock328` @lehmancurtis
It still says "waiting port" forever.
Click to expand...
Click to collapse
It sometime takes a few tries to get the phone and tool to do what its supposed to, but if you get the waiting message start over until the program reboots the device. It will work, it's just not a perfect process.
lmgnsa said:
Just to confirm:
To prevent the OEM recovery from replacing TWRP, I have to flash Magisk.
If I flashed a gsi, would this problem still be present?
edit: if I wanted to flash a gsi, would I be able to flash "A" only roms, "AB" only roms, or A/AB roms?
edit2: @lehmancurtis plz help me
Click to expand...
Click to collapse
You need to modify a few files. It's almost just like the 5059 devices and you can look up the 5041c thread to see what needs edited. Use the fstab.mt6739 from the 5041c.
Here's the tool. I think some of the links to it got messed up. Make sure you turn on developer options and check that oem unlock is ticked as well as adb usb options. Once in fastboot, issue the following
Code:
fastboot oem unlock-go
Follow the instructions on the device. Then boot into system and complete setup so that you can turn on developer options again since your device was just reset. Boot to fastboot once again and issue these.
Code:
fastboot flash recovery ./recovery.img
Code:
fastboot oem reboot-recovery
That should be the custom recovery you just installed. It will be replace on reboot if steps are not taken. I was in the process of working this issue when my beat up a501dl succumbed to its varied and multiple impact injuries. If I can find the time to repair it I will finish where I left off, but in the mean time I will help as much as I can.
Regular drivers are built into the phone but you may need vcom drivers. I'm going to attempt to repair mine enough to reset and flash again. I'll probably have to nav my screen via commands, but I will attempt to capture the process and show you.
I've got a A501DL, I enabled usb debugging and oem unlock, seems like the A501DL in fastboot does not talk with the pc, i've installed so many driver things its crazy butat fastboot when typing fastboot reboot bootloader, it reboots the phone but it skips fastboot and turns on to my home screen, I used volume up and power, I get in fast boot butthe device isnt being detected by windows 10 64 bit. Also in fast boot there is only
reboot system now
wipe data/factory reset
wipe cache partition
power off
im going nut that fastboot isnt working with this device.
Hey guys, I need help flashing my Google pixel 2. It was off for a couple of months and now when I am trying to start it, its not booting without putting it on charge and even then it only shows the battery icon then the google icon and restarts (So a bootloop). But when I press and hold the power button and volume down key, it goes in the fastboot mode ( the one where all device information is shown with an Android Logo) (Pic att).
If I select Download mode, it just shows operation denied and if I select recovery mode then it goes to bootloop again. Also as far as I remember when I last used the phone, the usb debugging was turned off so please suggest what to do from here.
If you have USB debugging disabled with OEM unlocking off there's not much you can do. That's why I usually suggest if you're going to relock your bootloader keep oem unlocking enabled so you can flash the factory image if you run into problems. this has saved me a few times.
try downloading the platform tools and usb driver and running the unlock command, what message do you get? The first command you want to run is ADB devices to make sure that your device appears in the list and the command prompt. second command to run is fastboot reboot bootloader , If your phone restarts back into bootloader then you know you have the driver and fastboot /ADB installed and working properly. then go to the Android developer page and find the proper unlock fast boot command I think there's a different one for the Pixel 2.
Alekos said:
If you have USB debugging disabled with OEM unlocking off there's not much you can do. That's why I usually suggest if you're going to relock your bootloader keep oem unlocking enabled so you can flash the factory image if you run into problems. this has saved me a few times.
try downloading the platform tools and usb driver and running the unlock command, what message do you get? The first command you want to run is ADB devices to make sure that your device appears in the list and the command prompt. second command to run is fastboot reboot bootloader , If your phone restarts back into bootloader then you know you have the driver and fastboot /ADB installed and working properly. then go to the Android developer page and find the proper unlock fast boot command I think there's a different one for the Pixel 2.
Click to expand...
Click to collapse
Hey thanks for the update man. I know I should have kept atleast oem unlocking enabled. My fault.
Now I followed your instructions and the phone only shows under fastboot devices. But when I run ADB devices it comes as blank under list of devices attached. I still tried the fastboot reboot bootloader command but the phone just restarts with the battery charging icon flashing on screen and then going back into the fastboot mode. (pic of which I attached in the original post).
Any other ideas would be appreciated, else ill just take it to a service centre.
mayankggrwl said:
Hey thanks for the update man. I know I should have nlocking enabled. My fault.
Now I followed your instructions and the phone only shows under fastboot devices. But when I run ADB devices it comes as blank under list of devices attached. I still tried the fastboot reboot bootloader command but the phone just restarts with the battery charging icon flashing on screen and then going back into the fastboot mode. (pic of which I attached in the original post).
Any other ideas would be appreciated, else ill just take it to a service centre.
Click to expand...
Click to collapse
Mine shows blank also when running the devices command.
If you can run commands like "fastboot reboot bootloader" or "fastboot reboot recovery" etc and the device restarts, then platform-tools and driver is installed. I mean make sure you have the latest versions of both or else there's no point on going any further. An older version platform-tools will cause a bunch off issues so update that for sure.
what happens when you run any of these commands when your in the bootlaoder menu (where it says Fastboot and device state: locked) (after you've updated platform-tools, check the version by typing the command " fastboot --version" - 31.0.3 is the latest version)
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot oem unlock
If you can unlock your device, you can flash recovery/bootloader image and go from there. But it doesn't look good.
Alekos said:
Mine shows blank also when running the devices command.
If you can run commands like "fastboot reboot bootloader" or "fastboot reboot recovery" etc and the device restarts, then platform-tools and driver is installed. I mean make sure you have the latest versions of both or else there's no point on going any further. An older version platform-tools will cause a bunch off issues so update that for sure.
what happens when you run any of these commands when your in the bootlaoder menu (where it says Fastboot and device state: locked) (after you've updated platform-tools, check the version by typing the command " fastboot --version" - 31.0.3 is the latest version)
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot oem unlock
If you can unlock your device, you can flash recovery/bootloader image and go from there. But it doesn't look good.
Click to expand...
Click to collapse
Hey man, Thanks for the update.
Unfortunately none of these commands are working and yes I have the latest platform tools and drivers installed. Attaching image of the same.
mayankggrwl said:
Hey man, Thanks for the update.
Unfortunately none of these commands are working and yes I have the latest platform tools and drivers installed. Attaching image of the same.
Click to expand...
Click to collapse
yeah, it means the oem unlocking option is disabled in developer options. damn.
can you try logging into recover menu at all so you can update both boot slots A/B with the ota using adb update option in the recovery menu.
What about running a few fastboot commands to delete userdata and even switch boot slots. that Fastboot screen will show what slot you are booted in (either a or b). try switching slots and booting then?
fastboot --set-active=a (if you are in Slot-B)
fastboot --set-active=b (if you are in Slot-A)
After swithing slots, hit restart device and as soon as you see the Google Logo, hold volume down. If you can boot into Android, enable oem unlocking as soon as you can, don't even connect to wifi or whatever. Or try accessing Recovery mode after switching slots. Main goal is to try to access recovery to update ota and/or access Android to enable oem unlocking.
have you looked on xda for other fastboot commands to try? There's a few Unbrick posts on the Pixel subs - worth a try?
edit-- sorry, I deleted some of my comment by mistake, had to rewrite it/
Alekos said:
yeah, it means the oem unlocking option is disabled in developer options. damn.
can you try logging into recover menu at all so you can update both boot slots A/B with the ota using adb update option in the recovery menu.
What about running a few fastboot commands to delete userdata and even switch boot slots. that Fastboot screen will show what slot you are booted in (either a or b). try switching slots and booting then?
fastboot --set-active=a (if you are in Slot-B)
fastboot --set-active=b (if you are in Slot-A)
After swithing slots, hit restart device and as soon as you see the Google Logo, hold volume down. If you can boot into Android, enable oem unlocking as soon as you can, don't even connect to wifi or whatever. Or try accessing Recovery mode after switching slots. Main goal is to try to access recovery to update ota and/or access Android to enable oem unlocking.
have you looked on xda for other fastboot commands to try? There's a few Unbrick posts on the Pixel subs - worth a try?
edit-- sorry, I deleted some of my comment by mistake, had to rewrite it/
Click to expand...
Click to collapse
Okay so I tried switching slots. Currently active slot is A but it again shows error that slot chage is not allowed in locked state. Well was worth a try.
I tried almost everything to get into recovery menu as per my knowledge but cant. It just restarts back into the fastboot state or goes into bootloop.
I did a bit of searching before creating this thread but didnt found anything. Ill try again and see if someone has something similar.
mayankggrwl said:
Okay so I tried switching slots. Currently active slot is A but it again shows error that slot chage is not allowed in locked state. Well was worth a try.
I tried almost everything to get into recovery menu as per my knowledge but cant. It just restarts back into the fastboot state or goes into bootloop.
I did a bit of searching before creating this thread but didnt found anything. Ill try again and see if someone has something similar.
Click to expand...
Click to collapse
this thread is interesting:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
specifically this comment:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
download the full factory image (not ota) and extract it, and move the radio and bootloader images into platform tools folder and try flashing? But don't think you can.
Also, maybe try installing Skipsoft and see what commands you can execute from there? https://skipsoft.net/download/unified-android-toolkit-v1-7-2/
it supports the Pixel 2.
Not sure how the op in that thread above fixed his Pixel 2 with Skipsoft tool. His Device state said Locked in his screenshot on his post.
Also try draining the battery and see if it will boot into Recovery Mode at all. And check the other Pixel threads (like Pixel 3 XL) there's a few unbrick posts there also.
edit--try these commands
fastboot erase system
fastboot erase data
fastboot erase cache
Alekos said:
this thread is interesting:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
specifically this comment:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
download the full factory image (not ota) and extract it, and move the radio and bootloader images into platform tools folder and try flashing? But don't think you can.
Also, maybe try installing Skipsoft and see what commands you can execute from there? https://skipsoft.net/download/unified-android-toolkit-v1-7-2/
it supports the Pixel 2.
Not sure how those users in the thread flashed the bootloader image since I didn't think you could if the device state is locked, but worth a try.
Also try draining the battery and see if it will boot into Recovery Mode at all. And check the other Pixel threads (like Pixel 3 XL) there's a few unbrick posts there also.
Click to expand...
Click to collapse
Okay great !! Thanks for these. Ill go through that thread and will see if any of the listed methods work. Will also try that software. In a rush so will try these later on and then ill update you.
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