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
Related
Hello,
I managed to brick my new Feiteng H7100 phone, i flashed wrong rom to it and got a greenish screen when trying to start the phone.
So i formatted the phone in SPFT tool "Format whole flash" and from then it stopped responding, i cant start the phone anymore, and the charging indicator wont light up when charging.
When connecting the phone to try and reflash it the computer recognizes that i have connected the phone to the computer, but flashing doesnt work.
It is the S7180 with 1GB ram.
I hope there is a solution to it and it can be fixed, iam not sure if this can be called had brick or soft brick.
Was very close to throw it out of the window yesterday, but then thought i can give it a chance
Thanks
Have you found a solution to the problem? I have a similar problem. Dead after flash ROM
please help me
Thanks
Mine is dead also
jemmars said:
Have you found a solution to the problem? I have a similar problem. Dead after flash ROM
please help me
Thanks
Click to expand...
Click to collapse
Same mine is completely dead after I flash it - Its not recognized by the originally drivers in windows 7. Showing up as an Unknown Device.
if it is showing up as an device, it isn`t bricked. you need to get the right firmware and flash it again. force install the drivers for the unknown device or take the drivers for Rom you flashed. (e.g. flashed wrong preloader from ZTE to a Star device, need to install ZTE drivers)
While I don't know the specifics of the Feiteng H7100, I've "bricked" many an android phone and tablet. Fortunately it's usually easy to fix.
1) Reboot the device into CWM Recovery Mode (usually by holding power and volume buttons at the same time)
2) Plug it into your computer & run "adb devices" - if you device comes up as a Recovery device, then you're probably home free
3) Run an "adb push newly_downloaded_cyanogenmod_rom.zip /sdcard/" - the data location (/sdcard/ in this example) might vary depending on your device
4) Wipe Cache
5) Install Zip from sdcard and choose your new_rom.zip
Previously, I've talked about how I bricked my G920T by using an apk to try to root my phone.
Then I tried to do a factory reset with the stock recovery but it wouldn't even go into the stock recovery. So I flashed TWRP and wiped the whole phone including the system partition.
Then I tried to flash a stock 6.0.1 firmware to the phone but doing so did not improve the situation as my phone still won't boot. Even worse, when I power my phone, all I see is the blue LED indicator, no Samsung logo, nothing.
Then I tried to flash a custom ROM like XtreStoLite but that didn't fix anything either.
When I use TWRP or the stock recovery, the error "failed to mount /efs (invalid argument)" comes up on the log. I tried using the ADB method to fix it but my phone would not get recognized by ADB probably because USB debugging isn't on by default.
I cannot shut down the phone without having it charged to a power source then holding down PWR+DOWN VOLUME+HOME until the screen shuts off.
When I enter download mode, I don't see the warning screen, I enter the download mode directly.
It will warm you when you enter download. Or use TWRP and reboot into Download.Once in download flash the ROM using Odin. Get the latest one from SamFirm.
P.S. Next time root using CF Auto Root
yasteellutch said:
It will warm you when you enter download. Or use TWRP and reboot into Download.Once in download flash the ROM using Odin. Get the latest one from SamFirm.
P.S. Next time root using CF Auto Root
Click to expand...
Click to collapse
It doesn't warn me when I enter download mode, that's one of the problems.
I tried flashing the official ROM using ODIN, it still won't boot because of the efs error.
1) Download the latest SmartSwitch
2) Click on more -> Emergency software recovery and initialization
3) Go into Device initialization, enter your model name, search for it and proceed as advised by the assistant
That should fix everything, otherwise:
1) Download the latest official firmware for your model, the 4-File (or 3-File) Version
2) Use latest ODIN, check repartition in options
3) Select all the files and flash it
If EFS or DRK is corrupted, flashing roms, custom or not won`t help, it can be fixed via repair box maybe (Octoplus/Z3X)
Try to flash CF auto root for your model, if it still won`t boot, then find someone with a box to try to help you remotely or not.
But Smart Switch emergency initialization with phone sn would be the first thing I would try.
Orginator said:
1) Download the latest SmartSwitch
2) Click on more -> Emergency software recovery and initialization
3) Go into Device initialization, enter your model name, search for it and proceed as advised by the assistant
That should fix everything, otherwise:
1) Download the latest official firmware for your model, the 4-File (or 3-File) Version
2) Use latest ODIN, check repartition in options
3) Select all the files and flash it
Click to expand...
Click to collapse
Which mode should I be in when using SmartSwitch? No devices are shown when I have it plugged in during the bootup, and is so too in download mode but shows a not supported message.
brenner650 said:
If EFS or DRK is corrupted, flashing roms, custom or not won`t help, it can be fixed via repair box maybe (Octoplus/Z3X)
Try to flash CF auto root for your model, if it still won`t boot, then find someone with a box to try to help you remotely or not.
But Smart Switch emergency initialization with phone sn would be the first thing I would try.
Click to expand...
Click to collapse
How can someone with a box help me remotely?
zheyizhu said:
Which mode should I be in when using SmartSwitch? No devices are shown when I have it plugged in during the bootup, and is so too in download mode but shows a not supported message.
Click to expand...
Click to collapse
Download mode offcourse. Nevermind the not supported message.
Follow instructions from link below, I made it for such occasions:
http://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
zheyizhu said:
How can someone with a box help me remotely?
Click to expand...
Click to collapse
Well if you know someone who have a box, it doesn`t have to be remotely.
If not, it is possible to fix it remotely, with help of usb hub (FlexiHub or similar), tunneling (TeamViewer or similar) and box software (you connect phone to your computer, the other guy connects box to his computer, both of you are connected through a gateway to a wonderfull thing called internet, and everybody is happy ) .
Same as on site, just with few more things in between the phone, and the box.
brenner650 said:
Download mode offcourse. Nevermind the not supported message.
Follow instructions from link below, I made it for such occasions:
http://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
Well if you know someone who have a box, it doesn`t have to be remotely.
If not, it is possible to fix it remotely, with help of usb hub (FlexiHub or similar), tunneling (TeamViewer or similar) and box software (you connect phone to your computer, the other guy connects box to his computer, both of you are connected through a gateway to a wonderfull thing called internet, and everybody is happy ) .
Same as on site, just with few more things in between the phone, and the box.
Click to expand...
Click to collapse
The S/N sticker on the back of the phone is long gone, is there any other way I can find it besides from going into settings because I can't do that?
EDIT: I am able to borrow a friend's serial and got the firmware installed.
The Samsung boot logo is back now, however, the device still won't boot. The efs error is still there but the download mode warning sign came back.
EDIT #2: Okay, I flashed TWRP now and ADB is working once again. Can I utilize this to fix the efs error?
This thread is about how to recover the MTK Android phone, if it has gone Bricked (soft/hard/dead/etc)
THIS IS FOR INFORMATION ONLY.
Q. How Phone gets Bricked?
Ans : Basically, phone get bricked during the installation of Android OS (flashing).
Reason/why it happens
- If flashing is interrupted by low battery or loose cable connection during flashing.
- Using wrong firmware or a custom ROM (unstable) to flash your phone.
Result:
* Phone will not boot even after holding the power key and it will not accept charging. (Hard Brick / Dead Brick)
* Boot-Loop
* Restart loop
* No Recovery (In this situation, Hard Reset will not work)
Q. - Why Phone becomes dead (MTK Android Phone) ?
Ans : While installing Custom ROM or Stock firmware (unstable), Preloader (.bin) file becomes corrupted.
PRELOADER - It is the file in MTK android phone which helps to boot the phone.
Tools & Software Required:
SP Flash tool
Android Stock ROM
MTK USB Driver
PC / Laptop
Dead MTK Phone
USB cable.
NOTE: SP Flash tool has 3 Dropdown, Its meaning & How to use:
MOTA SIU : while choosing this function before clicking on Download, only boot, recovery and Android will be updated.
Format All + Download : while choosing this function before clicking on Download, it first erases the old Firmware then install new firmware. (Recommended when MTK phone stuck at logo & hard reset fails)
Firmware Upgrade: while choosing this function before clicking on Download, its update the Android version. (Recommended when installing a higher or lower version of Android manually)
Steps to Fix/Unbrick Dead Android (MTK) Phone
1- Install MTK driver.
2- Download the tool.
3- Unzip it and double click on Flash_tool.exe.
4- It will launch the tool.
5- Download Android stock ROM, unzip it.
6- Click on Scatter-Loading and assign the path of file (Select Firmware i.e. {.txt extension}).
7- Click on Download.
8- Switch off Mobile and connect it to PC using USB cable by pressing Volume down as boot key.
9- Flashing starts and when completed, Download OK will appear.
Also check Here for more Understanding, Special Thanks to @yuweng
Please let me know if anything is wrong here, so that I can make correction and help other member for better understanding.
Also hit THANKS button if you find this as useful info.
If you found this post helpful then don’t forget to share this post with other Android users so that they could get their dead phones working in few easy steps without paying few dollars on it.
Reserved
Nice Guide, Can you please list MTK devices ????
421rahman said:
Nice Guide, Can you please list MTK devices ????
Click to expand...
Click to collapse
OK, Will be adding attachments later, Thanks
Salman
--
Thanks @Salman Al-Badgail for this use full info.
Deena Khanam said:
Thanks @Salman Al-Badgail for this use full info.
Click to expand...
Click to collapse
welcome & Thanks
@jamsubzero check this guide
@jamsubzero I saw your post and thread regarding Dead Bricked
Hey guys.
I own a lenovo A328. For the past couple of months my phone, gets poping up "com.google.etc.etc has stopped".
I tried doing a factory reset, but no luck. Then I learn that I can flash it using SPflash tool with the stock firmware.
And luckily, I did it, my phone back to normal. But then, a few couple of weeks, it started to pop up the same error messages again until I can't do anything on my phone, and unitl it boot loops. So, I reflash again with the same firmware (stock).. and it works again. And same thing keeps repeating and repeating;
until I thought I can try to change the options in sp flash tool..
Instead of "Download only", I choose, "Firmware upgrade".... the flashing finished successfully.
BUT when I press the power button to turn it on, nothing happens, and when I charge it, I cant see the charging screen (or it's not actually charging). I'm sure that it is charging before the flashing, and the power button is working.
When I connect it to the computer, i hear a "connected" sound, then "disconnected", and repeating.
i also tried to reflash it, both the "DL only" and "Firmware upgrade", even the "Format all + ...."
and it flashed successfully (meaning, computer still recognized it), but still not turning on.
Please help me. please.
Click to expand...
Click to collapse
NEVER DOWNLOAD ROM NOT MEANT FOR YOUR PHONE. IT WILL BRICK IT !
What you did is you flashed wrong firmware to your device and the result you in Dead Brick, However there is still solution for your problem. Please Please Please do a proper search first and download correct firmware and other necessary files for your device. Please check firmware number ok.
You can Flash it again but you need to open phone and try, Check here for better understanding.
GUIDE : HERE. Or else please go to any mobile shop and ask them to flash. Dont tell the original reason that you tried to flash or etc. Tell them that it stop suddenly and for now I am unable to access it. They charge you about 5-15 USD based on your country, for me they had charged 10U$D me for lenovo A3500-HV dead flashing. Hope this help you.
i got no scatter file in stock rom pls help!
Aller retour si flash tool
Hard bricked Lenovo a7000
**Hi I got problem on yesterday I was install ing new Rom but suddenly my Lenovo a7000 hard brick
It is not responding any point .even charging .and charging light also .it's dead
But it when I connet to my pc it's connecting sound conning from pc ....My phone is dead plaease help
Salman Al-Badgail said:
This thread is about how to recover the MTK Android phone, if it has gone Bricked (soft/hard/dead/etc)
THIS IS FOR INFORMATION ONLY.
Q. How Phone gets Bricked?
Ans : Basically, phone get bricked during the installation of Android OS (flashing).
Reason/why it happens
- If flashing is interrupted by low battery or loose cable connection during flashing.
- Using wrong firmware or a custom ROM (unstable) to flash your phone.
Result:
* Phone will not boot even after holding the power key and it will not accept charging. (Hard Brick / Dead Brick)
* Boot-Loop
* Restart loop
* No Recovery (In this situation, Hard Reset will not work)
Q. - Why Phone becomes dead (MTK Android Phone) ?
Ans : While installing Custom ROM or Stock firmware (unstable), Preloader (.bin) file becomes corrupted.
PRELOADER - It is the file in MTK android phone which helps to boot the phone.
Tools & Software Required:
SP Flash tool
Android Stock ROM
MTK USB Driver
PC / Laptop
Dead MTK Phone
USB cable.
NOTE: SP Flash tool has 3 Dropdown, Its meaning & How to use:
MOTA SIU : while choosing this function before clicking on Download, only boot, recovery and Android will be updated.
Format All + Download : while choosing this function before clicking on Download, it first erases the old Firmware then install new firmware. (Recommended when MTK phone stuck at logo & hard reset fails)
Firmware Upgrade: while choosing this function before clicking on Download, its update the Android version. (Recommended when installing a higher or lower version of Android manually)
Steps to Fix/Unbrick Dead Android (MTK) Phone
1- Install MTK driver.
2- Download the tool.
3- Unzip it and double click on Flash_tool.exe.
4- It will launch the tool.
5- Download Android stock ROM, unzip it.
6- Click on Scatter-Loading and assign the path of file (Select Firmware i.e. {.txt extension}).
7- Click on Download.
8- Switch off Mobile and connect it to PC using USB cable by pressing Volume down as boot key.
9- Flashing starts and when completed, Download OK will appear.
Also check Here for more Understanding, Special Thanks [email protected]
Please let me know if anything is wrong here, so that I can make correction and help other member for better understanding.
Also hit THANKS button if you find this as useful info.
If you found this post helpful then don’t forget to share this post with other Android users so that they could get their dead phones working in few easy steps without paying few dollars on it.
Click to expand...
Click to collapse
S
Sir please help me out
I have Micromax a120 device. Few days back it got bricked it stuck on bootloop and not working even after factory reset moreover my pc is not recognizing mobile and display message as device descriptor request failed. I have installed all drivers
---------- Post added at 07:47 PM ---------- Previous post was at 07:47 PM ----------
Salman Al-Badgail said:
Reserved
Click to expand...
Click to collapse
Sir please help me out
I have Micromax a120 device. Few days back it got bricked it stuck on bootloop and not working even after factory reset moreover my pc is not recognizing mobile and display message as device descriptor request failed. I have installed all drivers
im having mt8127 mtk device it is not flashing iam having corrupted preloader i tried to flash the preloader it is not flashing , can any body knows to fix it??
How can a phone that's bricked be switched off? Am a bit confused.
Salman Al-Badgail said:
This thread is about how to recover the MTK Android phone, if it has gone Bricked (soft/hard/dead/etc)
THIS IS FOR INFORMATION ONLY.
Q. How Phone gets Bricked?
Ans : Basically, phone get bricked during the installation of Android OS (flashing).
Reason/why it happens
- If flashing is interrupted by low battery or loose cable connection during flashing.
- Using wrong firmware or a custom ROM (unstable) to flash your phone.
Result:
* Phone will not boot even after holding the power key and it will not accept charging. (Hard Brick / Dead Brick)
* Boot-Loop
* Restart loop
* No Recovery (In this situation, Hard Reset will not work)
Q. - Why Phone becomes dead (MTK Android Phone) ?
Ans : While installing Custom ROM or Stock firmware (unstable), Preloader (.bin) file becomes corrupted.
PRELOADER - It is the file in MTK android phone which helps to boot the phone.
Tools & Software Required:
SP Flash tool
Android Stock ROM
MTK USB Driver
PC / Laptop
Dead MTK Phone
USB cable.
NOTE: SP Flash tool has 3 Dropdown, Its meaning & How to use:
MOTA SIU : while choosing this function before clicking on Download, only boot, recovery and Android will be updated.
Format All + Download : while choosing this function before clicking on Download, it first erases the old Firmware then install new firmware. (Recommended when MTK phone stuck at logo & hard reset fails)
Firmware Upgrade: while choosing this function before clicking on Download, its update the Android version. (Recommended when installing a higher or lower version of Android manually)
Steps to Fix/Unbrick Dead Android (MTK) Phone
1- Install MTK driver.
2- Download the tool.
3- Unzip it and double click on Flash_tool.exe.
4- It will launch the tool.
5- Download Android stock ROM, unzip it.
6- Click on Scatter-Loading and assign the path of file (Select Firmware i.e. {.txt extension}).
7- Click on Download.
8- Switch off Mobile and connect it to PC using USB cable by pressing Volume down as boot key.
9- Flashing starts and when completed, Download OK will appear.
Also check Here for more Understanding, Special Thanks to @yuweng
Please let me know if anything is wrong here, so that I can make correction and help other member for better understanding.
Also hit THANKS button if you find this as useful info.
If you found this post helpful then don’t forget to share this post with other Android users so that they could get their dead phones working in few easy steps without paying few dollars on it.
Click to expand...
Click to collapse
i am trying to flash vivo s7 and the cable shake and since then the phone is dead, have flashed it several time, it complete but it refuse to on
I need help please
Basically I was flashing updates for my CUBOT Nova and everything was going fine and I tried out this custom recovery which wouldn't mount any partition so it didn't really suit me. And I did this a dozen of times with other recoveries and if anything happened I had the firmware in SP tools ready to be flashed and if I could save going to it I just used the fastboot to flash it, and so I decided to completly stop and just put my phone back to normal and because I done it before I formatted the whole flash, (and FYI every 2 times I plugged in the phone powered off my computer always searched for drivers in the windows update but it failed and so everything still worked) but after I formatted it and plugged it out and in to download the firmware, my computer successfully installed the drivers and at this moment I was like shoot so I tried to download and it didnt recognise my phone and so I uninstalled the driver my computer installed and see if it worked and it kept installing it again, so I decided to uninstall every mtk driver I had and rebooted, when I installed every single driver again it tried to download drivers from the windows update but it failed and on the sp flash tools it goes to 100% on the Downloading DA (so the red bar) and stays like that for a while and I get notifications that I have a unrecognisable usb device and after a while it gives me randomly 2 errors 0xC0050005 and 0XC0060001 and I know someone is going to tell me I dont have the right firmware or that it's not the right ones but it isn't I got from the official Cubot website and I got an early versions from firmwarefiles I think and none of them work, now I just have a phone without anything on it and I cant flash anything on it until I just hope someone would walk me through what to do I would appreciate so much I'm sorry I wrote so much as I had to explain in max detail as I could what happened!
netcrafy said:
How can a phone that's bricked be switched off? Am a bit confused.
Click to expand...
Click to collapse
i wanted to say the same thing, also i tried enter EDL for 2 days DD (helio G80) LMFAO
Hi there
I would like to know if you can help me in repairing my device.
So i wanted to do an upgrade on the tablet and i messed it up.
I was on CMW recovery at first and then i did a format on cache system and data. but when i wanted to flash the rom CM14.1 it fail and the devices restarted.
the screen goes on but i can see faint lines on the screen.
I did make a back up of the rom and tried to flash it back but it didnt work.
I used all the roms and it still didnt work. I tried many SP flash tool and formating and still not working. every single rom has been flash and all are green but the phone does not want to boot. i have youtube and followed the instructions and every single step i can think of but u have a gut feeling i am mssing something.
I cannot write SN on the fone as it will not work. i have uninstalled all the drivers re-install all the drivers did all the instruction that you have provided but still it will work.
the tablet does still detect on the PC and it does work. so basically it is in a bootloop but its not powering up. Some suggested using MRT TOOLS or MIRACLES but i have a problem with that as it always have a virus attached it to and when i download it the pc removes it. so i dont know where i can get a good crack tool.
i really need your help if you can.
Hello Guys
i closed SP tool while flashing
my phone : infinix hot 10s
i cant power on it and cant join fastboot and cant join bootloader
When i connect phone by orginial usb
computer said (USB not recoginzed)
i installed all drivers but now phone is dead and he was rooted so i cant going to warranty
how i fix it?
Hi,
so with this Tutorial i was able to unlock the bootloader of the Blackview tab 8.
but i just could not find any way to flash magisk.
- "fastboot boot patched_img.img" and "fastboot flash boot patched_img.img" gave me "fastboot: error: Couldn't parse partition size '0x'"
- "fastboot flash:raw boot boot.img" was able to flash the patched_boot.img (a twrp i tried to port as well), but then i was stuck at blackview logo (SOFTBRICK)
- SPD Research Tool R24.0.0003 was able to flash patched_boot.img, but same stuck at logo (SOFTBRICK)
The only way i was able to unbrick it, involved opening back cover and disconnecting the battery and reconnecting it again.
then put research tool to download mode and flash stock img
I'm hoping for some advices, what i could try to get magisk flashed
- Tab8 Firmware (DK_SC9863A_P30_5G_10.0_Tab8_EEA_20201022_V1.0)
- SPD Research Tool R24 (there are 2 other tools but afaik research tool is the only one, where i can choose which partitions to flash)
best regards
Oxo
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
nr0000000 said:
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
Click to expand...
Click to collapse
I did it like described in the tutorial i linked. did you use linux? maybe in a VM or so, to use the .sh script. AFAIK it doesnt work with windows
also dont forget to activate "OEM unlocking" in dev options
StormChaser1337 said:
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
Click to expand...
Click to collapse
i dont know about test point actually. you can open it pretty easily and just disconnect battery. then connect again, use sdp tool and start the flash process, then press vol- and hold it while pluging in usb cable. thats what i do, if im stuck and cant do anything else.
regarding button combination, i'm not sure. usually i use adb reboot bootloader.
Also for the Blackview Tab 8 you need to extract keys from your vbmeta.img and sign it differently, also every other .img you wanna flash, like patched magisk boot.img. i successfully rooted mine some time ago, but i flashed some magisk modules and something went wrong and i ended up bootlooping. now im trying to root again.
somehow i cant flash the vbmeta.img. i dont remember if i did anything different last time.
all the stuff i did to get it rooted, i have taken from that hovatek forum.
edit: uploaded Stock Rom Images and stuff like for example a magsik patched boot image, which got repacked with android image kitchen then signed and repacked again with avbtool here
PS: dont have time to invest to this atm, also i just read that there was a update sometime this year which i didnt get, so maybe that changed some stuff.
I was considering buying this Blackview tablet and before I ordered it I got in touch with the Blackview home people in Hong Kong. They were extremely UNHELPFUL AND EVEN RUDE (not unusual for the chinese). As far as I am concerned this mob does not deserve to be supported and having a product that is so difficult to do any tinkering with precludes it from my list for sure. It is so time for consumers to DEMAND that any product that does not give explicit instructions as to unlocking and flashing is not supported. Why is it not possible in this day and age for this to happen. OK I know why but you get my meaning.
I have an Alcatel Onetouch Pixi 3 (10) Wifi 8079 tablet with an MT8127. I tried flashing a twrp recovery following Kirito’s guide but I had a glitching screen in a bootloop instead, so I tried flashing another twrp providedby the same user (was named twrp-new) and instead of the glitchy screen this time I’d see the twrp logo and then it would auto reboot after giving several unable to mount data errors. I was not able to do anything in twrp.
I then formatted the whole device except the bootloader. I realize that I should now be flashing a ROM (I have all the required stock ROM files including the scatter file) but SP Flash Tool won’t recognize my device (on three different OSes: Win7, Win8.1, a Linux distro). I also tried out Mobile Upgrade S but it too won’t see my device.
The device’s battery is soldered with three wires to the motherboard, so I can’t easily plug it out. Why do you think that my laptop won’t detect the device? Could it be that the tablet is running all the time (so it’s not off) and the battery lasts long because the device isn’t performing any operations?
As for drivers, when I used SP Flash Tool to flash the new twrp, I didn’t install any drivers myself on Windows 7. Now that it didn’t recognize my device, I installed all kinds of drivers on both Win 7 and 8.1 like MediaTek VCOM USB and Preloader drivers but I stll couldn’t get it to work. I get no feedback from my device no matter what I do (power button, volume up and down buttons).
Do not say that it is hard bricked because all I did was formatting the device except the bootloader.
tesiz22 said:
I have an Alcatel Onetouch Pixi 3 (10) Wifi 8079 tablet with an MT8127. I tried flashing a twrp recovery following Kirito’s guide but I had a glitching screen in a bootloop instead, so I tried flashing another twrp providedby the same user (was named twrp-new) and instead of the glitchy screen this time I’d see the twrp logo and then it would auto reboot after giving several unable to mount data errors. I was not able to do anything in twrp.
I then formatted the whole device except the bootloader. I realize that I should now be flashing a ROM (I have all the required stock ROM files including the scatter file) but SP Flash Tool won’t recognize my device (on three different OSes: Win7, Win8.1, a Linux distro). I also tried out Mobile Upgrade S but it too won’t see my device.
The device’s battery is soldered with three wires to the motherboard, so I can’t easily plug it out. Why do you think that my laptop won’t detect the device? Could it be that the tablet is running all the time (so it’s not off) and the battery lasts long because the device isn’t performing any operations?
As for drivers, when I used SP Flash Tool to flash the new twrp, I didn’t install any drivers myself on Windows 7. Now that it didn’t recognize my device, I installed all kinds of drivers on both Win 7 and 8.1 like MediaTek VCOM USB and Preloader drivers but I stll couldn’t get it to work. I get no feedback from my device no matter what I do (power button, volume up and down buttons).
Do not say that it is hard bricked because all I did was formatting the device except the bootloader.
Click to expand...
Click to collapse
Did you ever get this resolved? I have this same exact problem just with a different device
ayetab said:
Did you ever get this resolved? I have this same exact problem just with a different device
Click to expand...
Click to collapse
I have got it all resolved. My device is running fine with Magisk. I recommend that you take a look at my post history.
tesiz22 said:
I have got it all resolved. My device is running fine with Magisk. I recommend that you take a look at my post history.
Click to expand...
Click to collapse
How do I see your post history? I have a Blu view 3 and pc recognizes it cause I hear the ding sound I'm stuck in fastboot mode cause dm-verity failed I need to flash stock eom but flash tool just sits there nothing happens.
Kireej said:
How do I see your post history? I have a Blu view 3 and pc recognizes it cause I hear the ding sound I'm stuck in fastboot mode cause dm-verity failed I need to flash stock eom but flash tool just sits there nothing happens.
Click to expand...
Click to collapse
I don't know what a Blu view 3 is, but you can click my name to open my profile and hit "postings" to see my post history.