This is my first time asking for help directly here, I always find the answers in the other threads solved, but this time I can not find an answer.
I have a alcatel one touch 5020t evolve its a MTK6575 (t-mobile but is used in el salvador), I used to MTKDroidTools to install CWM Revocovery, I did back up with the same program but apparently did not because i look and i cant find anything in the back up folder, only left some files called:
ALCATEL-ONE-TOUCH-5020T_130818__boot_patched_140129-175612.img
ALCATEL-ONE-TOUCH-5020T_130818__recovery_140129-175612.img
in the folder called recovery.
Now the phone on, the startup screen and then turns off, I can enter a menu by pressing on + vol +, where it says enter recovery mode or normal mode, before they tried to install cwm I could go in and delete everything from there, now I get the menu of recovery mode and normal mode but since does not enter recovery mode, got it turns off, like when entering the normal mode.
I tried to flash with sp flash tool but I get an authentication error that is on the img
The pc recognizes my phone, makes the sound when you connect something, now if we go to Device Manager, a device called first appears:
MTK USB Port
After that is disconnected and then a new one appears called :
Media Tek Preloader USB VCOM Port
But there ir a problem, then this becomes a repetitive one disconnects and connects the other, but only when I connect the phone without battery only stays in:
MTK USB Port.
Help what can i do to revive my phone ???????????????
you found any solution i have the same problem ?
:/
harold99 said:
you found any solution i have the same problem ?
Click to expand...
Click to collapse
Sorry, but i could not solve yet, nobody helps me
So were you able to flash cwm to the device? there are several threads requesting a custom recovery for this device and either way could you upload those first two .img files I may be able to use them to try to recover my device
*** Okay so the problem is that the boot loader on this device is locked and for the time being a custom recovery is not possible. I still have access to the recovery on my device so if I could find a way to build an update file from the source code or an official firmware update I could fix mine. Yours may be too far gone. sorry.
any luck with a solution? How close to one have you got to...
ipeedalil said:
*** Okay so the problem is that the boot loader on this device is locked and for the time being a custom recovery is not possible.
Click to expand...
Click to collapse
A friendly warning: Don't just mess around with the Bootloader, that's one delicate piece of software, try to find how to unlock it first, then we can talk of changing the recovery. For rooting purposes I can attest that you can safely root it using the OneClickRoot solutions around the net. I used some chinese root and it worked like a charm.
Soft Bricked 5020T
carlitox2301 said:
This is my first time asking for help directly here, I always find the answers in the other threads solved, but this time I can not find an answer.
I have a alcatel one touch 5020t evolve its a MTK6575 (t-mobile but is used in el salvador), I used to MTKDroidTools to install CWM Revocovery, I did back up with the same program but apparently did not because i look and i cant find anything in the back up folder, only left some files called:
ALCATEL-ONE-TOUCH-5020T_130818__boot_patched_140129-175612.img
ALCATEL-ONE-TOUCH-5020T_130818__recovery_140129-175612.img
in the folder called recovery.
Now the phone on, the startup screen and then turns off, I can enter a menu by pressing on + vol +, where it says enter recovery mode or normal mode, before they tried to install cwm I could go in and delete everything from there, now I get the menu of recovery mode and normal mode but since does not enter recovery mode, got it turns off, like when entering the normal mode.
I tried to flash with sp flash tool but I get an authentication error that is on the img
The pc recognizes my phone, makes the sound when you connect something, now if we go to Device Manager, a device called first appears:
MTK USB Port
After that is disconnected and then a new one appears called :
Media Tek Preloader USB VCOM Port
But there ir a problem, then this becomes a repetitive one disconnects and connects the other, but only when I connect the phone without battery only stays in:
MTK USB Port.
Help what can i do to revive my phone ???????????????
Click to expand...
Click to collapse
I have had a OT-5020T with all the same symptoms as you describe. After much research and diagnosis here is what I have learned and know to be true.
You have soft bricked your phone. For this phone it results in the boot loop you described. At present a Custom Recovery that works is not available for this phone and any attempt to flash an existing one results in a soft brick. There are apps that will flash a Custom Recovery while the phone is one but once you reboot ... !!! Bricked!! This is because ...
a) the memory mapping for this phone is different that other OT-5020 models, so the Custom Recovery placement and indexing is wrong when flashed, causing the boot-loop, and inability for Custom Recovery to load,
and ,
b) the bootloader is locked for the 5020T (different story for other OT 5020 models), and no one has found a way around it yet. Trying to flash back stock firmware for the OT-5020T requires it to be unlocked.
One Touch Update 2.8.0 doesn't seem to want to work one the phone has been altered in this way. SPtools won't work because you need an accurate OT-5020T scatter file (memory map) ,and certification file (bootloader unlocker) to flash any image. In addition to all this the phone doesn't maintain a steady usb connection long enough to allow use of android tools adb and fastboot commands although it does can stay connected in a different mode.
What I have used to restore my phones firmware is a package from Furious Gold that allows the phone to be flashed to factory firmware. I have used it successfully, so I can confirm that the phone wasn't a permanent brick.
Alcatel 5020t T-Mobile plis help flshe file
please am in need of alcatel 5020w firmware, please if someone is having it or having that same phone and want to read the firmware for me my email is [email protected]
thanks
Hey
I have a nexus 5 which was rooted and lineageOS was already installed (don't remeber which one, i didn(o do the installation).
I wanted to upgrade to lineageOS17.
I had issues when i wanted to install opengapps. I found some messages on the forum to resize the file system.
Then I had other issues and i did different stuffs with my phone.
In the end, I think my phone is totally dead : evrything is erased and I can't have access to the TWRP interface to install an ne rom or to wipe the phone memory
When I turn on my phone, i am in the bootloader mode.
I choose recovery in orderto get to the TWRP interface but it doesn't work. the phones just turned off.
When i plub my phone to the computer i cant' have access to its storage disc.
I still can root the phone with "CF-Auto-Root-hammerhead-hammerhead-nexus5".
but then I can't do anyhting else.
Is any help possible? or should I just dump my phone?
anavatat said:
Hey
I have a nexus 5 which was rooted and lineageOS was already installed (don't remeber which one, i didn(o do the installation).
I wanted to upgrade to lineageOS17.
I had issues when i wanted to install opengapps. I found some messages on the forum to resize the file system.
Then I had other issues and i did different stuffs with my phone.
In the end, I think my phone is totally dead : evrything is erased and I can't have access to the TWRP interface to install an ne rom or to wipe the phone memory
When I turn on my phone, i am in the bootloader mode.
I choose recovery in orderto get to the TWRP interface but it doesn't work. the phones just turned off.
When i plub my phone to the computer i cant' have access to its storage disc.
I still can root the phone with "CF-Auto-Root-hammerhead-hammerhead-nexus5".
but then I can't do anyhting else.
Is any help possible? or should I just dump my phone?
Click to expand...
Click to collapse
I would try to flash the last factory image via fastboot.
Hi everyone, I have a VIvo Y81i (1812). and i forget it's screen lock password.
Issued in format via software that i never enabled it's adb ever nor it's attached to any computer before.So it's only detecting in computers as MTP device only none other than that. Not as Ports and LTP device.
What i have tried so far:
Tried to format with recovery mode which still asked for password to unlock before format.
Miracle tool to format phone but after setup it keep saying the port be occupied even when i tried virtual port software.
FRP by pass tool which need port number of device it's not gonna work because my phone never detect after installed lots of adb,Vcom drivers.
Now i need to unlock my phone but over the week of trying and googling i end up here to get some help from XDA forums.
Please guys help me out in this issue.
Thanks
Hi all, I have an Alcatel Joy Tab that's all of a sudden decided to keep looping this error.
Error only pops up outside of the lock screen: on the lock screen, I'm able to swipe down the notifications bar and enter settings from there. Additionally, UI seems to be functional in the Camera app as well.
I've already factory reset once, and it was back to normal for a little while, but then it came back again. Any suggestions?
Specs:
Alcatel Joy Tab 1
Model 9027W
Android 8.1.0
Baseband version MT6739
Kernel Version 4.4.95
Most times the sole reason behind the issue “Android System UI Has Stopped” is the improper installation of the OS update or the corrupted one.
Hence do a clear re-flash of Stock ROM.
jwoegerbauer said:
Most times the sole reason behind the issue “Android System UI Has Stopped” is the improper installation of the OS update or the corrupted one.
Hence do a clear re-flash of Stock ROM.
Click to expand...
Click to collapse
Thanks for the reply, I've been looking for a stock ROM since I first had the issue. However I haven't been able to have any luck finding one. Do you have any suggestions on where to look? If I ultimately still can't find one am I SOL?
I've heard that you can just return to stock by using Alcatel's official Mobile Upgrade tool here but it keeps giving me a message saying that the version I'm using is the most updated version.
Software Drivers - Alcatel
Software Drivers
www.alcatelmobile.com
I would like to know more about this too. Same issue with poster. Any custom roms or anything out there for this?
No custom ROMs. There is one out there that is unlocked. But, I've lost the post about it. Used it to carrier unlock mine. Haven't had the time to see if it unlocked more.
This issue happens to me. Going into settings and removing the screen lock solves it (but obviously no screen lock). Formatting data allows you to use a screen lock for a while, until the issue decides to pop up again. Usually though it followed doing something like installing xposed framework or something advanced like that. But other times it seemed it may have been a result of booting my custom TWRP image. It's built from a generated device tree so it's not perfect yet.
Edit to add: I modified my fstab and removed the metadata encryption entry for userdata. I haven't seen the issue appear since. Encryption is now gone, but this thing is pretty weak as it is and I don't generally keep data that needs encrypting on it.
Edit: "SystemUI has stopped working" is solved with the latest firmware. If you can't get latest firmware (The alcatel mobile upgrade tool kept telling me I was on the latest or it would just crash) Do a google search for MTK Sugar Tool. Versions after 2018 will force the latest updates to the device over usb
Now for a better bit of info I have:
Bootloader unlock and proper Magisk root is possible on this device. In order to get to fastboot to unlock bl:
1. If you have basic experience with python, you can use this script to boot to fastboot:
MTK Bootseq: enter alternative boot modes in MediaTek-based smartphones
MTK Bootseq: enter alternative boot modes in MediaTek-based smartphones - mtk-bootseq.py
gist.github.com
2. RISKY: If you are inexperienced, need to unlock bl, and have good AV software (This is how I did it the first time, but be warned: while my up-to-date installation of Kaspersky found nothing today (10-31-21), Virustotal.com showed that around 18 databases flag this program for trojan like behavior):
Search google for "MTK Boot Mode Selector Tool by mvirus team". There are several links available all over shady blogs and such. This tool does work and is a simple exe, requiring only that proper alcatel USB drivers and fastboot drivers are installed; However, it's sketchy as hell and I suggest you read up on python and just use the first option.
I AM NOT RESPONSIBLE FOR DAMAGE CAUSED BY POTENTIAL VIRUSES IF YOU USE THE SECOND METHOD
Use either method (but you should really learn how to run python scripts and identify the path or name of serial ports in linux or windows (respectively) and use the first method) to get to fastboot and bl unlock like normal.
In windows it's just a matter of rebooting your tablet while holding volume down and watching in device manager for the correct COM port number to enter as a parameter of the command. (I.E. COM7.) Once you have the port number, you send it to the script as a command.
I.E.:
Code:
python mtk-bootseq.py FASTBOOT COM7
To get the port number in windows:
My tablet rebooted three times and reconnected while holding the volume down key. Each time it reconnected, a new entry in the device manager named "Ports (COM & LPT)" appears. This will disappear as soon as it disconnects, which seems to be after something like 3 seconds, so you have to be actively watching. If you expand "Ports (COM & LPT), after the first two boots, "MTK USB Port (COM*)" will appear, with * being a number (I.E. COM7.) On the third boot, "Preloader USB VCom Port (COM*)" will appear. This is the COM port number you are after. It will likely be different than the port number of the first two, which were identical for me.
I may make a full tutorial on both the linux and windows python methods soon (though it's pretty simple if you have basic experience with python,) but it doesn't seem like demand for bootloader unlock on this device is very high. (I have put a lot of work into this post already, however.)
cheger32 said:
This issue happens to me. Going into settings and removing the screen lock solves it (but obviously no screen lock). Formatting data allows you to use a screen lock for a while, until the issue decides to pop up again. Usually though it followed doing something like installing xposed framework or something advanced like that. But other times it seemed it may have been a result of booting my custom TWRP image. It's built from a generated device tree so it's not perfect yet.
Edit to add: I modified my fstab and removed the metadata encryption entry for userdata. I haven't seen the issue appear since. Encryption is now gone, but this thing is pretty weak as it is and I don't generally keep data that needs encrypting on it.
Now for a better bit of info I have:
Bootloader unlock and proper Magisk root is possible on this device. In order to get to fastboot to unlock bl:
1. If you have basic experience with python, you can use this script to boot to fastboot:
MTK Bootseq: enter alternative boot modes in MediaTek-based smartphones
MTK Bootseq: enter alternative boot modes in MediaTek-based smartphones - mtk-bootseq.py
gist.github.com
2. RISKY: If you are inexperienced, need to unlock bl, and have good AV software (This is how I did it the first time, but be warned: while my up-to-date installation of Kaspersky found nothing today (10-31-21), Virustotal.com showed that around 18 databases flag this program for trojan like behavior):
Search google for "MTK Boot Mode Selector Tool by mvirus team". There are several links available all over shady blogs and such. This tool does work and is a simple exe, requiring only that proper alcatel USB drivers and fastboot drivers are installed; However, it's sketchy as hell and I suggest you read up on python and just use the first option.
I AM NOT RESPONSIBLE FOR DAMAGE CAUSED BY POTENTIAL VIRUSES IF YOU USE THE SECOND METHOD
Use either method (but you should really learn how to run python scripts and identify the path or name of serial ports in linux or windows (respectively) and use the first method) to get to fastboot and bl unlock like normal.
In windows it's just a matter of rebooting your tablet while holding volume down and watching in device manager for the correct COM port number to enter as a parameter of the command. (I.E. COM7.) Once you have the port number, you send it to the script as a command.
I.E.:
Code:
python mtk-bootseq.py FASTBOOT COM7
To get the port number in windows:
My tablet rebooted three times and reconnected while holding the volume down key. Each time it reconnected, a new entry in the device manager named "Ports (COM & LPT)" appears. This will disappear as soon as it disconnects, which seems to be after something like 3 seconds, so you have to be actively watching. If you expand "Ports (COM & LPT), after the first two boots, "MTK USB Port (COM*)" will appear, with * being a number (I.E. COM7.) On the third boot, "Preloader USB VCom Port (COM*)" will appear. This is the COM port number you are after. It will likely be different than the port number of the first two, which were identical for me.
I may make a full tutorial on both the linux and windows python methods soon (though it's pretty simple if you have basic experience with python,) but it doesn't seem like demand for bootloader unlock on this device is very high. (I have put a lot of work into this post already, however.)
Click to expand...
Click to collapse
Bootloader Unlock failed. Is there any solution?
Azukegi said:
Bootloader Unlock failed. Is there any solution?
Click to expand...
Click to collapse
Did you enable OEM unlock in developer settings first?
cheger32 said:
Did you enable OEM unlock in developer settings first?
Click to expand...
Click to collapse
I eventually got it, but there's a patch for this device preventing any root and on top of that there's no custom recovery for this device :/
Azukegi said:
I eventually got it, but there's a patch for this device preventing any root and on top of that there's no custom recovery for this device :/
Click to expand...
Click to collapse
Really? I built TWRP for it, I can send it to you if you want to try it. What block is there for installing root? Originally I used a temp root to get the boot image (There should be a few exploits currently available in the latest Android release for this tablet, at least enough to dd the boot partition) and then patched it with magisk, then once I found the MTK bootseq script I flashed it with fastboot. Didn't need TWRP at all. If we have the same firmware version I could also just send my currently patched boot image.
cheger32 said:
Really? I built TWRP for it, I can send it to you if you want to try it. What block is there for installing root? Originally I used a temp root to get the boot image (There should be a few exploits currently available in the latest Android release for this tablet, at least enough to dd the boot partition) and then patched it with magisk, then once I found the MTK bootseq script I flashed it with fastboot. Didn't need TWRP at all. If we have the same firmware version I could also just send my currently patched boot image.
Click to expand...
Click to collapse
Dude no way, I would love to get that TWRP from you if possible
Azukegi said:
Dude no way, I would love to get that TWRP from you if possible
Click to expand...
Click to collapse
TWRP 3.6.1 for Alcatel 3T 8 (Maybe also generic Joytab 1?)
I built this last night, seems to work well. Let me know if there are any issues. This will be my last post in this thread as I've gotten off topic. I'll create a new thread with a guide if I find the time.
This is built from a twrp compatible device tree generated from a recovery image with a few modifcations and corrections. The kernel was built from sources released by alcatel (it took me nearly a year and some legal threats to get them to release it to me.)
just flash that to recovery in fastboot mode:
Code:
fastboot flash recovery <img filename>
Be sure to make a backup of your original if possible.
I just remembered that there's a bypass method and a useful utility in existence (located here: http://www.mediafire.com/file/qtmkilaimympapf/mtk_bypass_rev4.7z/file) for enabling the use of spflashtool to make backups and even flash images without fastboot with this device. Sorry, I'm still dusting the cobwebs off of this project.
EDIT: 23 builds later and I fixed /data decryption. As I said this will be my last post here but in case I never make a formal thread, here is a fully working twrp.
Edit again: I realized adb push and sideload wasn't working so I fixed it. Here's the latest build
I've got a 3T that I use rarely and it seems if I leave it for a while I get the same lock screen issue. I've discovered mention of a T-Mobile update that might resolve this:
Does anyone know where I can get this build and if I can force it on to my 3T. My carrier has no updates available.
Android 8.1.0
Build number: 1AWKUMK0May 14, 2021Resolves issue preventing device unlockAvailable May 14, 2021
Devices that meet the update requirements can be upgraded to the current software version.
So, I'm having the same problem. Just bought the joy tablet on Amazon. Yesterday it was working fine, then this morning got this error. I can't unlock the screen. If I use the pulldown menu I can click on one thing before the error pops up and the screen goes black then back to lock. I can't do anything on the tablet at all. Since I just bought it, should I just return it?
mnpeaches78 said:
So, I'm having the same problem. Just bought the joy tablet on Amazon. Yesterday it was working fine, then this morning got this error. I can't unlock the screen. If I use the pulldown menu I can click on one thing before the error pops up and the screen goes black then back to lock. I can't do anything on the tablet at all. Since I just bought it, should I just return it?
Click to expand...
Click to collapse
If it's too late to return it you can put it in recovery mode and try to restore it that way if that doesn't work then you can reflash it with SUGAR MTK SP
mnpeaches78 said:
So, I'm having the same problem. Just bought the joy tablet on Amazon. Yesterday it was working fine, then this morning got this error. I can't unlock the screen. If I use the pulldown menu I can click on one thing before the error pops up and the screen goes black then back to lock. I can't do anything on the tablet at all. Since I just bought it, should I just return it?
Click to expand...
Click to collapse
You can try SUGAR MTK SP
Hi, I was trying to revert back to realme UI stock from Pixel Experience ROM on my Realme 5i device(RMX 2030 EX). So, first I tried to install stock recovery through Orange fox. But after installing the recovery, my phone got bricked and now it's not even being detected by the pc nor I can access fastboot mode. As PC is not detecting my phone, I can't use Realme Flash tool or cmd to change my recovery. What can I do? Please if you know, give me a fix. I would be so grateful to you. Thanks for your time.
Here are some methods that might work for you.
How to Access an Android Phone with a Broken Screen
Dealing with a broken screen on your Android phone is a hassle. Although phone screens are pretty tough, one nasty drop can shatter them completely. Given that most people have a lot of irreplaceable content on their phones, it is
www.alphr.com
@Aranya Kishor Das
My POV: If on Android device side neither adbd ( requires USB Debugging got enabled ) nor fastbootd ( requires OEM unlock got enabled ) is accessible although the device's matching OEM USB driver got installed on Windows computer, then it's recommended to take phone to authorized service center and let them try to fix it.