Hi,
Okay, I hope this method can help you, so you don’t have to go through the tedious process I went through to fix this fpr lock problem, I personally tried a lot of methods described in forums and finally was able to fix this problem, so I hope this works for you too and you don’t have to spend a lot of time looking for a solution to this problem.
I used this method on my galaxy a5 2016, but I think it will work on other Samsung phones as well if you download the right stock rom for it.
Warning: if you are a newbie, please read through this entire post once before attempting to try it out. It’ll only take a few minutes but at least you’ll know what you’re doing.
since i'm a new user i'm not allowed to post outside links so i'll put spaces between my links to be able to post them.
So I had the same problem as a lot of other guys, I had rooted my Galaxy A5 Sm-a510-fd through CF-Auto-Root, Everything was working fine, But Since I didn't know about OEM Unlocking & FRP Lock (Factory Reset Protection), I Logged Into my google account in my phone, and after restarting my phone after installing an app, my phone showed a red small text at the top left corner of my screen saying "custom binary blocked by fpr lock", now keep in mind I had enabled usb debugging and oem unlocking before but since I logged into my google account, apparently google had disabled the oem unlocking, hence this message.
Now I tried a few methods like a method where someone had said to go into download mode (Hold Volume down + Home + Power) and then pressing the volume down (cancel) instead of volume up (continue) and after the restart the phone for some reason wouldn't show this message again (weird), some had tried this in that forum with success but it didn’t work for me, so first try this see if it works for you, then I tried to flash a new stock rom but I got the same frp lock message in download mode as well, then I tried a few other method which didn’t work and I don’t even remember them (I’m a newbee, and I was confused by all the articles I had read and all the method I had tried so I don’t remember a lot of them, and a few of them may have worked but needed to remove the battery but in galaxy a5 battery isn’t removable), but the method which finally worked for me was this (It was posted in gsmhosting . com by zishhaider user):
1. Download (A510FXXU1AOL1 02.12.2015) from samsung-updates . com/device/?id=SM-A510F or from sammobile . com/firmwares website.
2. Remove .md5 at the end of stock rom you downloaded, extract the .tar file with 7zip to a folder, delete cm.bin and sboot.bin from this folder, open 7zip file manager from you installed program list in windows, navigate to the folder, choose all remaining files, click add, choose tar as archive format and and click ok to compress the files again into a tar format (a better method to re-pack these files into a tar ball is by using a software called unified android toolkit described at the end of this post).
3. Download and install the latest kies from Samsung (it will automatically install the latest usb drivers for your phone) and I recommend restarting your computer after installing kies.
4. Now go to download mode (Volume down + Home + Power >> Volume Up) , Download odin 3.10.7 or newer if available at the time of reading this post, right click on odin and run as administrator, now connect your phone to your computer with the usb cable preferably coming with your own phone, now if you have installed the drivers (from kies software) and if the cable is working and usb debugging is enabled, odin should detect your phone and show <ID:0/003> added in the message section (the number 3 isn't important, it depends on which usb port you use), now check the options tab to make sure only Auto Reboot and F. Reset Time are checked (by default these 2 are always checked, make sure Re-partition is unchecked). I recommend waiting a minute or two to make sure your phone and odin have recognized each other fully and usb drivers are fully installed.
5. Click on AP and browse to the location where you compressed the rom files and choose it, now to begin flashing this stock rom, just hit start.
6. When ODIN is done, you should see a box that will say reset or passed (depending on which version you have, you may see either or both.). At this point it is ok to remove your device.
ODIN has completed the flash, and by now, the device should be going through the reboot screen, if it works for you as it did for me you won't get the frp lock message again.
Any problems, try these few things: Update Drivers, and restart your PC; Different cables; Different USB ports.
Just a tip: If you are in download mode and you want to restart or turn off your phone for any reason and you have an unremovable battery like me, in download mode hold Volume down + Power for 10 to 20 seconds to restart your phone, now if you want to turn it off completely, after the restart hold Volume up + Home + Power to go to recovery and from there choose turn off.
-------------------------
After this process your phone should boot and the red little text saying “custom binary is locked by frp lock” should disappear. But since you flashed your phone after you removed cm.bin and sboot.bin your phone will be slow and you will aslo, still have to bypass the frp lock from google inside your phone, to do that I will give you a link to youtube from rootjunkey which explains it best how to bypass this frp lock inside the phone, or if you have the user and password of the google account you had previously logged in with to you phone, you can enter those and when asking to backup your previous apps choose "treat this phone as a new device" because you don’t want to install the apps just yet and you’ll have to flash your phone one more time with the complete stock (including cm.bin and sboot.bin). after entering your phone either by logging into your google account or bypassing the google acounot login screen, go to settings >> about >> software info and hit build number several times to enable developers options, then go to developers option and enable usb debugging and the damned oem unlock, and from now on before restarting or turning your phone off check to see the goddamned oem unlock box is on.
www . youtube . com/watch?v=JzywoFS_r9U
www . youtube . com/watch?v=DJ8_qbj1DPQ
Now after I did all these things I tried to flash the whole stock rom I had downloaded but I got the message “sw .rev binary check failed device 2 binary 1” and I think the reason I got this was beacase I had flashed many other recovery and roms before and I had screwed up my bootloader version and my phone didn’t recognize this rom as the right one for my phone, I downloaded a few more roms from my own country (Iran) and each time it either gave me this message or failed because it was stuck in flashing either hidden.img or sboot.bin or … . so what I did was a method I learned from someone in a forum (I don’t remember which forum), I’ll post a picture of that method and explain a little bit about the steps or modifications I made. And before using this method, download unified android toolkit, just google and download it, you’ll need it for this method.
link to the image:
s7.picofile . com/file/8250224492/Galaxy_S6_NAND_Write_Start_Fail_Fix.jpg
this software creates a folder in the root of your operating system drive (c Drive in my case) named Unified_Android_ToolKit, inside it you will find an input and an output folder, put the files you want to re-pack into tar files in the input folder, follow the instructions (99, 8, 1, 3) and your resulting files will be saved in output folder.
So the modifications I made to that method was:
The order I followed in flashing was as follows:
- AP: Boot/Recovery/System : these are the main system and recovery files and have the biggest size.
- CRC: Cashe/Hidden : This is some country code used for the region to flash the ROM against, XE is Europe, AU is Australia, and so on, this part can throw you off, its more then for tracking what region this is based of, in terms of localization and language support. And more importantly, for Kies to recognize the region and to determine if there's firmware update available. It is quite possible to have a CSC that can be limited to one country.
- CP: Modem
- BL: cm/sboot : Your bootloader
This is the order I followed and as you can see I chose all buttons and their corresponding files instead of choosing all of them with AP. Each one of these buttons re-writes the corresponding file into it’s previous partition in your phone.
Also I flashed boot.img first, restarted, flashed recovery.img, restarted, and so on, except for the cm.bin and sboot.bin which I repacked with unified android toolkit into one tar ball instead of 2 tar file, and flashed them together, to do this all you have to do is put these 2 together into the input folder and select 99, then 8, then 2, then yes.
finally I decided to try using Samsung smart switch (which I had tried but didn’t work before) to try to flash a stock rom once again to make sure everything is back to normal, but it still didn’t work and froze just like before, so I decided to use kies and it worked, even though smart switch is newer I believe kies is still better, so I recommend you use kies to update your firmware one more time using this Samsung tool, especially if the previous method still didn't fully work or if your baseband version or IMEI is unknown. To do that after enabling usb debugging, open kies, connect your phone to your computer, unlock your phone screen if it is locked and wait for kies to recognize your phone, if it said kies does not support your device or try smart switch just ignore it, it’s okay even if it doesn’t recognize your phone, just go to tools and choose firmware upgrade and initialization, now enter your model number (Upper-case), then serial number, both are on the box of your phone, sn is also behind your battery or at the back of your phone if your battery is unremovable, follow the instructions, at one point you’ll have to disconnect the cable, turn off your phone, go into download mode and conncet the cable again and then hit update to update the downloaded firmware. This time if everything goes right your phone may work even better and faster than before just like it did for me.
one last thing: I had screwd up my phone so badly that my baseband and IMEI was unknown and I couldn’t make any calls, and what’s worse I hadn’t backed up my efs folder, so I tried a few methods to solve this and finally decided to use kies, kies hadn’t worked before but this time it worked and restored everything to normal.
Now this time after i fixed my phone, I have backed up my efs folder, and my stock rom from clockworkmod recovery, and I have also set up a Microsoft/Samsung drive, google drive and dropbox account and installed some software to backup every contact, message, and app I have to the cloud in case sth like this happens again, I learned my lesson, I hope you do the same.
Developers, please correct any mistakes I may have made explaining this method, I am a newbie and these are what I learned in just 2 days of reading many forums and applying them to solve my own problem, so I may be wrong in some of these, so before people try this method out correct all the mistakes I may have made so people don’t brick their phones. Thank you
I hope this was helpful, thanks for reading, sign out.
quick question, when i try to flash the modified .tar rom a message appears saying: "custom binary(boot) blocked by frp lock"
but without i cant activate developer options and OEM unlock. i cant use my phone atm
edit: phone is a510f
After removing the 2 files from tar, I was able to flash OK.
But after flashing, my phone is stuck in bootloop - it shows Samsung Galaxy A5 and restarts, continuosly.
---------- Post added at 09:09 AM ---------- Previous post was at 09:08 AM ----------
After removing the 2 files from tar, I was able to flash OK.
But after flashing, my phone is stuck in bootloop - it shows Samsung Galaxy A5 and restarts, continuosly.
Thanks, this helped my friend he is a n00b
This does not work with 6.0.1
Just for anybody who has that version, dont waste your time downloading 5.1.1, it wont work if you already in 6.0.1
Why should oem unlocking automatically turned off
This actually applies to all Samsung phones...
But, use the right firmware and flash it using Odin.
Side note:
To activate Developer options, tap Build number 7 times on About phone settings. Then, open Developer options and activate OEM Unlock.
You should ready to go flashing everything. Happy flashing!
AlokAk said:
Why should oem unlocking automatically turned off
Click to expand...
Click to collapse
OEM Unlock is turned off by default for Factory Reset Protection (FRP) feature to work properly.
Sent from my ASUS_Z00AD using XDA Labs
Is there any way by which i turned on OEM UNLOCKING permanentaly..
I have also rooted my A5 2016 by cff auto root.it rooted But after restarting it shows custom binary blocked by Frp lock. I have submitted this phone to samsung care. They fix it.
Now my phone is okk .
But no root access. Now I am not dare to root it by cff auto root
Is there any other way to Root my Galaxy A5 2016 Marshmallow (6.0.1) that after rooting it works without any problemm, if anyone could help me please.
Thanks in Advance
Which country's firmware i download for my galaxy A5 2016 ( SM-A510FD ) INDIA region.
On Sammobile website there is no firmware for india region.
Please tellll
AlokAk said:
Which country's firmware i download for my galaxy A5 2016 ( SM-A510FD ) INDIA region.
On Sammobile website there is no firmware for india region.
Please tellll
Click to expand...
Click to collapse
You could try to find it on Updato.
Sent from my ASUS_Z00AD using XDA Labs
No firmware for India region infact it only shows four region in filter region section
samsung a5 2016 SM-A510FD firmware fail any [Q-call 9041634416 i help you better
orion7i7 said:
Hi,
Okay, I hope this method can help you.
Click to expand...
Click to collapse
tx You saved my phone life
It works also with other software not only old one
não da certo comigo
no meu galaxy a5 deu essa mensagem mas coloco no modo download mas ele não aparece no ODIN pois não reconhece o cel pelo pc e agora ???
Fwatech said:
no meu galaxy a5 deu essa mensagem mas coloco no modo download mas ele não aparece no ODIN pois não reconhece o cel pelo pc e agora ???
Click to expand...
Click to collapse
The same thing happened with my phone.
After this message "Custom recovery blocked by FRP lock", the boot does not go ahead and in the download mode is not recognized by the pc.
I can not solve this :crying:
danjercm said:
and in the download mode is not recognized by the pc.
Click to expand...
Click to collapse
1) Have you installed USB drivers?
2) Have you tried other cables?
3) Have you tried different OSes, Odin versions, etc...?
Sent from my Redmi 3 using XDA Labs
krasCGQ said:
1) Have you installed USB drivers?
2) Have you tried other cables?
3) Have you tried different OSes, Odin versions, etc...?
Sent from my Redmi 3 using XDA Labs
Click to expand...
Click to collapse
Hi
thanks for answering
1) Yes, I installed the most up-to-date version of the samsung driver (SAMSUNG_USB_Driver_for_Mobile_Phones_1.5.63.0)
2) Yes, I tried 5 different original cables
3) I tried with 6 different versions of Odin, on windows 7, 8.1 and 10.
so I researched google, the only alternative is to do a procedure called JTAG, but still had hope of being able to solve without having to open the device
If anyone has a suggestion, I'll appreciate it.
Thanks
Many thanks
Me and my A5 want to thank you a lot. You saved his life I don't have to use my Wiko View :silly: anymore
Not simple is write combination firmware to the phone, then enable usb debugging and then just write firmware that not erase user data and cache and use free sw or adb command(this work not depend on software in the phone) to unlock the phone.
Simple software is here and the manual.
http://www.hardreset.info/FRP-Unlocker/
Thank you so much dude! I've searched the internet for 2 days and then this post came by so I decided to read and do it because I had nothing to lose and hell yeah it worked! THANKS!
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?