Database Info

TF300T 4.2 TWRP Error

Hi XDA,
I am a complete noob, and this is my first time posting, so bear with me.
Some time ago I rooted and unlocked my TF300 with SuperSu. Recently I wanted to upgrade to 4.4 kitkat. However, my Tablet was stuck at Andriod 4.1 because of the the unlock.
I went to manually update my TF via the Asus website. I installed the 10.6.1.8 using my TWRP 2.5, and Oem 4.1 OS. Installation worked just fine. After install, I booted up and I had 4.2 with everything working correctly.
Next step was to install TWRP 2.7.0.1. I reset my TF and went into RCK to see something went wrong when updating.
My TWRP will not load, and I get the Android on his back with the red triangle when I try to enter RCK.
Thanks in advance!!

I managed to install 10.6.1.27, but it did not change anything with my boot loader.
I downloaded motochopper, but that didn't seem to work, just told me my abt was out of date. SuperSu isn't working now either, "No Binary, There is a problem."
How do I install TWRP 2.7 with no boot loader? Please help.

TallMilk said:
I managed to install 10.6.1.27, but it did not change anything with my boot loader.
I downloaded motochopper, but that didn't seem to work, just told me my abt was out of date. SuperSu isn't working now either, "No Binary, There is a problem."
How do I install TWRP 2.7 with no boot loader? Please help.
Click to expand...
Click to collapse
Most people just install TWRP via fastboot like
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
You could try using other root methods, like Framaroot or Kingo. I think Kingo was reported to work on the latest stock version.

cmendonc2 said:
Most people just install TWRP via fastboot like
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
You could try using other root methods, like Framaroot or Kingo. I think Kingo was reported to work on the latest stock version.
Click to expand...
Click to collapse
I will look into that, but I am pretty sure I was already rooted, unless losing my boot loader means I am no longer rooted.
Another thing, I can't find a twrp.blob for 2.7, just a zip. I have one for 2.5, but that is useless because I already have 4.2. I also have not been able to find a working link to fastboot.
If anyone could give me a link to the fastboot or a link to a tutorial, that would be amazing. I have done my research, but all the lingo and different methods can be mind bending.
Thanks

TallMilk said:
I will look into that, but I am pretty sure I was already rooted, unless losing my boot loader means I am no longer rooted.
Another thing, I can't find a twrp.blob for 2.7, just a zip. I have one for 2.5, but that is useless because I already have 4.2. I also have not been able to find a working link to fastboot.
If anyone could give me a link to the fastboot or a link to a tutorial, that would be amazing. I have done my research, but all the lingo and different methods can be mind bending.
Thanks
Click to expand...
Click to collapse
You can get the img (which substitutes as a blob) from extracting it from the TWRP 2.7 zip file.
1) You will need ADB and fastboot for this: http://forum.xda-developers.com/showthread.php?p=42407269. I would suggest keeping the tablet at least at 50% battery.
2) Install Naked Drivers. This may be optional for you. If you can proceed to the next step without, you won't need it.
3) Enter fastboot by rebooting and holding down the power button. TF300 enters fastboot automatically since this is 4.2 BL.
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
fastboot devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery twrp.img -i 0x0b05
Blue bar on device will fill. Be patient.
5) Reboot the Device back into Android. This is an important step.
6.) Go back into TWRP and install what you want.

You are amazing. I will give it a try tonight and report back!

cmendonc2 said:
You can get the img (which substitutes as a blob) from extracting it from the TWRP 2.7 zip file.
1) You will need ADB and fastboot for this: http://forum.xda-developers.com/showthread.php?p=42407269. I would suggest keeping the tablet at least at 50% battery.
2) Install Naked Drivers. This may be optional for you. If you can proceed to the next step without, you won't need it.
3) Enter fastboot by rebooting and holding down the power button. TF300 enters fastboot automatically since this is 4.2 BL.
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
fastboot devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery twrp.img -i 0x0b05
Blue bar on device will fill. Be patient.
5) Reboot the Device back into Android. This is an important step.
6.) Go back into TWRP and install what you want.
Click to expand...
Click to collapse
Installed adb fastboot. However, my device does not automatically go into fastboot, I still have to hold down the volume key.
Once I am in fastboot usb (with the 3 icons), I fastboot successfully and get the serial number, then when I type the 'fastboot flash recovery twrp.img -i 0x0b05' command I get this error: cannot load 'twrp.img' : No error
I am attemping to use the 2.7.0.1 twrp from the 4.4.2 page. I have extracted the recovery.img (tried renaming to twrp and left it the same) and placed it in the root of both my external and internal sd.
I have now tried it with .zips .img .blob and I receive the same error everytime. Not sure what I am doing wrong now.

TallMilk said:
Installed adb fastboot. However, my device does not automatically go into fastboot, I still have to hold down the volume key.
Once I am in fastboot usb (with the 3 icons), I fastboot successfully and get the serial number, then when I type the 'fastboot flash recovery twrp.img -i 0x0b05' command I get this error: cannot load 'twrp.img' : No error
I am attemping to use the 2.7.0.1 twrp from the 4.4.2 page. I have extracted the recovery.img (tried renaming to twrp and left it the same) and placed it in the root of both my external and internal sd.
I have now tried it with .zips .img .blob and I receive the same error everytime. Not sure what I am doing wrong now.
Click to expand...
Click to collapse
Put the twrp.img into your ADB folder, where you installed it. Then run the next command.

cmendonc2 said:
Put the twrp.img into your ADB folder, where you installed it. Then run the next command.
Click to expand...
Click to collapse
Awesome! Worked like a charm. twrp 2.7.0.1 installed perfectly.
Then I tried to flash the cyanogenmod. Said it installed fine, but it just gets stuck on the loading screen...

I am trying to do exactly what TallMilk is doing...put Cyanogenmod on my tablet. It is my understanding that I have to unlock my bootloader though? Which I have tried doing a million different ways with the Asus Unlock tool which always gives me an error.
If I follow the instructions posted above I will be able to flash Cyanogenmod without unlocking my bootloader?

SilentSpartan said:
I am trying to do exactly what TallMilk is doing...put Cyanogenmod on my tablet. It is my understanding that I have to unlock my bootloader though? Which I have tried doing a million different ways with the Asus Unlock tool which always gives me an error.
If I follow the instructions posted above I will be able to flash Cyanogenmod without unlocking my bootloader?
Click to expand...
Click to collapse
Finally got it to work. I had to do a wipe first, read about old roms interfering with new installations.
SilentSpartan, I used SuperSU last year to root and unlock my tablet when it was still a 4.0 android to flash to 4.1. This recent update was from 2.5 TWRP on a rooted device running 4.2. When I installed 4.2, it blew away my TWRP, and I had to flash the new TWRP 2.7.0.1.
That flash from OEM fastboot to TWRP 2.7.0.1 is what I needed help with.

TallMilk said:
Finally got it to work. I had to do a wipe first, read about old roms interfering with new installations.
SilentSpartan, I used SuperSU last year to root and unlock my tablet when it was still a 4.0 android to flash to 4.1. This recent update was from 2.5 TWRP on a rooted device running 4.2. When I installed 4.2, it blew away my TWRP, and I had to flash the new TWRP 2.7.0.1.
That flash from OEM fastboot to TWRP 2.7.0.1 is what I needed help with.
Click to expand...
Click to collapse
Damn, so I'm screwed. Why does Asus have to such so much...? You can no longer unlock afaik.

SilentSpartan said:
I am trying to do exactly what TallMilk is doing...put Cyanogenmod on my tablet. It is my understanding that I have to unlock my bootloader though? Which I have tried doing a million different ways with the Asus Unlock tool which always gives me an error.
If I follow the instructions posted above I will be able to flash Cyanogenmod without unlocking my bootloader?
Click to expand...
Click to collapse
You're going to have to unlock no matter what. Did you try both v7 and v8 of the unlocker and calling Asus Support to tell them to put your serial number back into the database (get a manager)?

cmendonc2 said:
You're going to have to unlock no matter what. Did you try both v7 and v8 of the unlocker and calling Asus Support to tell them to put your serial number back into the database (get a manager)?
Click to expand...
Click to collapse
I've tried every firmware and unlock tool combination. Nothing works. I sent them an email a day ago. Depending on there response, maybe I'll try calling. I'm so fed up with this tablet, I'm about to throw it out my window. $400 POS. :good:

SilentSpartan said:
I've tried every firmware and unlock tool combination. Nothing works. I sent them an email a day ago. Depending on there response, maybe I'll try calling. I'm so fed up with this tablet, I'm about to throw it out my window. $400 POS. :good:
Click to expand...
Click to collapse
Did you ever get your tablet fixed? I am having some problems myself after a miserable m9 update.

(HELP ME ) Bricked

So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!

Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
Give the all required information like Brand, model number in your post first.

Huawei honor 5x kiwi L24, I can't really acces the phone so finding some information is impossible. My main issue is when I boot it's failing to verify the Boot.img , recovery.img and system.img . I don't exactly know what all information I can give you

Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html

-Hope- said:
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html
Click to expand...
Click to collapse
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.

Nixonkai417 said:
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.
Click to expand...
Click to collapse
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work

-Hope- said:
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work
Click to expand...
Click to collapse
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.

Nixonkai417 said:
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.
Click to expand...
Click to collapse
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?

-Hope- said:
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?
Click to expand...
Click to collapse
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.

Nixonkai417 said:
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.
Click to expand...
Click to collapse
As long as the bootloader says 'phone is unlocked' then its ok

-Hope- said:
As long as the bootloader says 'phone is unlocked' then its ok
Click to expand...
Click to collapse
I'm my case the bootloader has relocked, so in green it say phone status: locked.

Nixonkai417 said:
I'm my case the bootloader has relocked, so in green it say phone status: locked.
Click to expand...
Click to collapse
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?

-Hope- said:
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?
Click to expand...
Click to collapse
(REMOTE: command not allowed)

I have already sent an email to Huawei support, just waiting on a response to see if they can give me another unlock code. If I'm unable to unlock the boot loader again with the codes, what's my options for unlocling the boot loader without Huawei's help.

Root OOS 10.0.1

Hello, i was on android 10 open beta 2 with root
But while upgrading i ran into some complications and now i am on OOS 10.0.1 but dont have root
I tried to install twrp but after pushing through adb the screen says "fastboot mode" and stays there. And after typing fastboot reboot the phone reboots into home screen
I also tried to patch boot image of oos 10.0.1 but it enters into fastboot loop
Any way i can get root?

What happens when you're in fastboot and boot the twrp file?

Phantom Thief said:
What happens when you're in fastboot and boot the twrp file?
Click to expand...
Click to collapse
The whole screen turns black with the words "fastboot mode" in the center

ViperCDX said:
I tried to install twrp but after pushing through adb the screen says "fastboot mode" and stays there. And after typing fastboot reboot the phone reboots into home screen
Click to expand...
Click to collapse
Your description sounds a bit suspicious, like you aren't doing the right method. Or maybe you are not just using the right (precise) terminology. There is a lot of confusion by folks on how to boot/install TWRP properly on this device, so that is why I am pointing this out, and hope you can clarify more specifically so we can then help you.
You don't need to adb push the TWRP.img file to boot TWRP, and you don't "install" TWRP.img using fastboot either. You should be trying to fastboot boot twrp.img, with that img file on your computer.
You do need the Magisk zip on the phone (and adb push is one way); as well as the TWRP installer zip if you intend to install (not just boot) TWRP to the phone. The TWRP installer zip not completely necessary, if you want to just flash Magisk and achieve root (not have TWRP installed on the phone).
Also, are any error messages showing up on your command prompt on the computer, and if so what does it day exactly?
Might be best if you cut/paste your fastboot commands, or post a screenshot of your PC, so we can see exactly what commands you used, error messages, etc.

redpoint73 said:
Your description sounds a bit suspicious, like you aren't doing the right method. Or maybe you are not just using the right (precise) terminology. There is a lot of confusion by folks on how to boot/install TWRP properly on this device, so that is why I am pointing this out, and hope you can clarify more specifically so we can then help you.
You don't need to adb push the TWRP.img file to boot TWRP, and you don't "install" TWRP.img using fastboot either. You should be trying to fastboot boot twrp.img, with that img file on your computer.
You do need the Magisk zip on the phone (and adb push is one way); as well as the TWRP installer zip if you intend to install (not just boot) TWRP to the phone. The TWRP installer zip not completely necessary, if you want to just flash Magisk and achieve root (not have TWRP installed on the phone).
Also, are any error messages showing up on your command prompt on the computer, and if so what does it day exactly?
Might be best if you cut/paste your fastboot commands, or post a screenshot of your PC, so we can see exactly what commands you used, error messages, etc.
Click to expand...
Click to collapse
ok let me try to be as specific as possible.
First i put the "twrp-3.3.1-4-guacamole.img" file in the adb folder and "twrp-3.3.1-4-guacamole.zip" in the internal storage of my phone
Then i switched off my phone, pressed vol up and vol down and power button to enter fastboot mode
i connected my phone to my pc
opened cmd window in the adb folder
typed "fastboot devices" to check if connected
then "fastboot boot twrp-3.3.1-4-guacamole.img"
on pressing enter , i get the 2 ok messages on cmd window and at that point my phones screen goes completely black with "Fastboot mode" written in the center
And stays there that way
now if i type "fastboot reboot" the phone reboots to the home screen
Hope i made it a bit clear
Sorry cant post screenshots at this moment, i am on vacation and dont have my laptop with me

You're using the wrong twrp image. You have to use the one for android q. Unofficial build of twrp for android q is available on the development section. Get that image, fastboot boot twrp.img and then install magisk 20. You don't need to install the twrp zip. You can just boot the image from fastboot whenever you need a custom recovery.
If you absolutely want the recovery, then you can flash it (remember to get the zip for android q) from magisk and then do direct install of magisk then reboot.

kgs1992 said:
You're using the wrong twrp image. You have to use the one for android q. Unofficial build of twrp for android q is available on the development section. Get that image, fastboot boot twrp.img and then install magisk 20. You don't need to install the twrp zip. You can just boot the image from fastboot whenever you need a custom recovery.
If you absolutely want the recovery, then you can flash it (remember to get the zip for android q) from magisk and then do direct install of magisk then reboot.
Click to expand...
Click to collapse
Oh damn, didnt realise that, so silly of me
Will try the android q version and report back

ViperCDX said:
Oh damn, didnt realise that, so silly of me
Will try the android q version and report back
Click to expand...
Click to collapse
Good catch by the previous user, that you need to use an updated TWRP version.
Unofficial version -70 from the following thread is what you want (if you haven't found it already): https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322

redpoint73 said:
Good catch by the previous user, that you need to use an updated TWRP version.
Unofficial version -70 from the following thread is what you want (if you haven't found it already): https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Click to expand...
Click to collapse
Yeah i pushed the .70 version through fastboot then flashed the installer
And now i have twrp
However when i try to flash magisk zip through twrp, the phone enters into fastboot mode and does not enter home screen
I have to fastboot boot image to get out of it
I have tried magisk 20.1,20 and 19.4
Kindly help

Hello guys please help me if you know what is this? What can I do? it's bug in Android 10.0.1 or something wrong that show me every minute this error?Show me in every minute this Don't want communicate with E4:5F:8D:9C:06:1A.Wait your answer,thanks.

HELP :: I bricked my Mi MIX 2S installing a Magisk Module of another phone (K20pro)

Please mods, I dont know if this post is in the correct forum. I'm exhausted after being hours trying to solve this issue and here is 2am. Feel free to move the thread wherever you think it suits better.
I posted the same message here: https://forum.xda-developers.com/k2...9t-pro-one-t4093255/post83029067#post83029067
I think that maybe this Mi MIX 2S forum is more suitable for asking for some help. This is the original message:
Yes I did. I feel like an ashole... The module is not for the MI MIX 2S, but I thought (yes, I told you, I'm an ashole, that being Magisk, it could be universal. For all smartphones with Magisk)
Is my fault, I know. I come here to beg for your help.
I had my Xiamo Mi MIX 2S with the last Xiaomi EU rom with MIUI 12, rooted with Magisk. Everything worked flawlessly.
Then I say that fantastic module: Screen Overclock. I thought, fantastic! I could have a lower refresh rate and that way save some battery... I did... And now I'm stuck in Fastboot.
I installed the latest official room with MiFlash following this tutorial: https://c.mi.com/oc/miuidownload/detail?guide=2
I even downloaded the last room from there (Global) as it says is the latest.
The biggest outcome is to boot into the official recovery. I tried to install TWRP and it install (fastboot flash recovery twrp-3.3.1-0-polaris.img ---> version 3.4 doesn't work either) but after that, I can't reboot into recovery. It comes back to Fastboot again.
Trying to boot the recovery with fastboot boot twrp-3.3.1-0-polaris.img throws the following error:
PHP:
Sending 'boot.img' (42476 KB) OKAY [ 1.219s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: 00000050')
FAILED (remote: 'Failed to load/authenticate boot image: 00000050')
So I don't know what to do, and I do really need your help please.
I'll post this same message in the Mi MIX 2S board. Hopefully somebody who could imagine what went on, can give a helping hand.
Please help
Thank you all
Manu

So know is even worse.
For a reason I don't know, now I'm able to load adb sideload (pcsuite) but when entering in fastboot, inmediatly I can see a very small letters in the top left corner that say: "Press any key to shutdown"
Solved connecting the MI MIX 2S to a USB2 port rather than a USB3. Weird... At least I have again access to Fastboot

I dont think this have any solution. I managed to install via XiaomiADB sideload to the 99%
And at 99%... it stopped:
C:\Users\manu\Downloads\XiaomiADB>XiaomiADB.exe miui_MIMIX2SGlobal_V11.0.5.0.QDGMIXM_42f0653956_10.0.zip
* Miui sideload made by Francesco Tescari, updated 02 Feb 2018 *
* Checking device status *
* Getting recovery info *
* Creating file MD5 hash *
* Querying ota update server, attempt #0 *
Data partition format might not be necessary and will NOT be done automatically after installation.
If the device doesn't reboot or some apps crash after reboot, you need to manually format the device using "format-data" command!
* Starting sideload *
Sending file to the device... (~100%)
Checking file checksum...
Installing file on the device... (~99%)
* Sideload output: *
ERROR: Sideload error -> Unknown error during file installation
Installation FAILED!, press ENTER to exit
So I'll try to see tomorrow if you guys can help, but I don't see any option here...
Well, at least connecting it to a USB2 port seems that I Can, again, to fastboot without the small "Press any key to shutdown" message

So another question.
A guy in the other thread told me this:
kiran8631 said:
So, when I screwed my phone trying recoveries, I got stuck in FastBoot. no matter what I did, even Power + Vol Up got me to fastboot, and I had just wiped my OS, so I had nothing to boot into.
This happens when you wipe your SYSTEM and/or VENDOR partitions and choose reboot recovery, or flash an incompatible recovery.
After a lot of stressful minutes, scared half out of my mind. A guy named @Shivsom helped me.
Basically what he made me do was, Download his file vbmeta_dv_shivsom.img that is given below in attachments.
Then copy the twrp.img file and vbmeta_dv_shivsom.img file to my adb Folder.
Open the Command prompt in that folder, by clicking on the address bar of File Explorer and typing > cmd > then Enter
Type the instructions
Code:
fastboot flash vbmeta vbmeta_dv_shivsom.img
Then type, (Since my twrp image file was re-named to twrp.img, if you haven't done so, do it)
Code:
fastboot flash recovery twrp.img
Then press and hold Power and Volume Up till you feel the haptic feedback see the TWRP recovery
Click to expand...
Click to collapse
He attached a vbmeta.img. I've never heard of that before, by the way.
So I didn't flashed because I was afraid that this was for P20PRO too.
I downloaded this one too https://xiaomifirmware.com/download-link/?dlm-dp-dl=14341 which is also a vbmeta.img
So both files are 4.1kb. Comparing them with an online tool it turns out that the _dv_shivsom.img version is full of zeros, while the one in xiaomifirmware have data inside.
What should I do?

manudas said:
So another question.
A guy in the other thread told me this:
He attached a vbmeta.img. I've never heard of that before, by the way.
So I didn't flashed because I was afraid that this was for P20PRO too.
I downloaded this one too https://xiaomifirmware.com/download-link/?dlm-dp-dl=14341 which is also a vbmeta.img
So both files are 4.1kb. Comparing them with an online tool it turns out that the _dv_shivsom.img version is full of zeros, while the one in xiaomifirmware have data inside.
What should I do?
Click to expand...
Click to collapse
I had tried this my k20 pro when I was in same situation and it worked and also I think u should also try this it will work

kiran8631 said:
I had tried this my k20 pro when I was in same situation and it worked and also I think u should also try this it will work
Click to expand...
Click to collapse
Thank you
I did it, and unfortunately no more recovery, no more fastboot.
The led flashes a couple of times and nothing else. Absolutely broken. I'm not blaming you, you only tried to help
Time to save for another phone
Thank you guys anyway

Take it to service center

manudas said:
Thank you
I did it, and unfortunately no more recovery, no more fastboot.
The led flashes a couple of times and nothing else. Absolutely broken. I'm not blaming you, you only tried to help
Time to save for another phone
Thank you guys anyway
Click to expand...
Click to collapse
If you get fastboot working again I can give you mix2s vbmeta

cvamoose said:
If you get fastboot working again I can give you mix2s vbmeta
Click to expand...
Click to collapse
Thank you, but the only reaction of the phone when I press any combination of buttons is to blink the led a couple of times. So I don't think that now it could be sorted out. Anyway, why don't you attach it here so if anybody in the future needs it, don't download the wrong one?

Try to enter EDL mode. Then flash latest MIUI global fastboot ROM with miflash. It should working

reevdre said:
Try to enter EDL mode. Then flash latest MIUI global fastboot ROM with miflash. It should working
Click to expand...
Click to collapse
Even if he got into edl mode he cant flash anything unless he has an authorized account. Also to get into edl at his current state the back of phone must come off and certain spots need to be shorted.

reevdre said:
Try to enter EDL mode. Then flash latest MIUI global fastboot ROM with miflash. It should working
Click to expand...
Click to collapse
Hey, thank you for your answer.
As I cannot access either to the Recovery or the Fastboot, I dont know how to enter EDL to be honest... I tried the vol- + power and connecting the cable but windows didn't recognise anything
Any other way?

You have to press vol- and vol+ at once and connect USB cable.
If it doesn't work I believe that test points should work. To do that you need to remove back cover then short two test points that are below camera using for instance scissors with small ends (this may help https://www.youtube.com/watch?v=koj3cGnhic0) and having both points connected with each other connect USB cable.

manudas said:
Hey, thank you for your answer.
As I cannot access either to the Recovery or the Fastboot, I dont know how to enter EDL to be honest... I tried the vol- + power and connecting the cable but windows didn't recognise anything
Any other way?
Click to expand...
Click to collapse
If you access edl mode contact me with a private message

Alcatel TCL A502DL/A501DL root/custom recovery/custom roms?

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.