Database Info

[FIRMWARE][STOCK] DOOGEE NOVA Y100X | Android 5.0

It took me days trying to make Doogee send me these files. I managed to unbrick my device with this firmware.
So I decided to post it here so anyone can unbrick ther Y100X.
It must be used with SP Flash Tool, here is the link to the thread: Flash Tool
This is the firmware :laugh: (extract with 7zip): --files removed--
For me it worked with the Format All + Download option.
-The firmware is stock and provided by Doogee. I got nothing to do with the making of the files. I also do not get paid for providing these files. I just wanna help others. -

Link sharing is on now. Sorry for forgetting about this.

thanks for el firmware, now how to get the root ... xD. My smartphone is underway yet, cost me $ 70

Root can be achieved through kingroot. But it is an app I personally hate, so I used some KingRoot to SuperSU apps and they worked,so good luck!

Many thanks for the original Firmware :highfive:

I hope there will upgrade to 5.1 or a dream.

Hello
i got trouble with that Y100X, tried to root it with KingoRoot, then i want to replace Kinguser with SuperSu, after that it ended up in Bootloop (showing DooGee logo then reboots). SP Flash Tool won't start (also tried to find Phone with adb but it always reboot to fast and don't connect)
Any thing i can do?

nickless07 said:
Hello
i got trouble with that Y100X, tried to root it with KingoRoot, then i want to replace Kinguser with SuperSu, after that it ended up in Bootloop (showing DooGee logo then reboots). SP Flash Tool won't start (also tried to find Phone with adb but it always reboot to fast and don't connect)
Any thing i can do?
Click to expand...
Click to collapse
Excuse for machine translation.
Took the information from 4pda.ru on this phone.
I quote: "Yesterday did the same thing, got the same) to the office. Site doogee rocked tools for model valencia 2. Including VCOM driver and flasher. The drivers stood on XP vlёt. Ask insertion of a cap according to the instructions of the threads about Flash Tool. Read the instructions and firmware itself took less time than the jump firmware) So do not be scared) is Ruth will not put. How then do not need to.
Briefly: 1 swing tools here https___drive.google.com/file/d/0B-eEVUUoOlT4QzZwZE54LTVFWms/edit?pli=1
2 swing firmware from the link in the header of the topic and its extract 7zip archiver;
3 Turn off the phone, connect it to a computer, manually set VCOM driver from the archive with the tools, disconnect the phone;
4 launch Flash Tool, look for a file scatter in the folder where you unzipped firmware
5 remove the checkbox PRELOADER
6 click DOWNLOAD, connect the cable to the computer off the phone and wait for the flashing 100%
7 disconnect the phone from the computer, and run the long wait until the turn
8 all
I hope that helps
ps in reference to replace ___ :// - new users can not link

ariss77 said:
Excuse for machine translation.
Took the information from 4pda.ru on this phone.
I quote: "Yesterday did the same thing, got the same) to the office. Site doogee rocked tools for model valencia 2. Including VCOM driver and flasher. The drivers stood on XP vlёt. Ask insertion of a cap according to the instructions of the threads about Flash Tool. Read the instructions and firmware itself took less time than the jump firmware) So do not be scared) is Ruth will not put. How then do not need to.
Briefly: 1 swing tools here https___drive.google.com/file/d/0B-eEVUUoOlT4QzZwZE54LTVFWms/edit?pli=1
2 swing firmware from the link in the header of the topic and its extract 7zip archiver;
3 Turn off the phone, connect it to a computer, manually set VCOM driver from the archive with the tools, disconnect the phone;
4 launch Flash Tool, look for a file scatter in the folder where you unzipped firmware
5 remove the checkbox PRELOADER
6 click DOWNLOAD, connect the cable to the computer off the phone and wait for the flashing 100%
7 disconnect the phone from the computer, and run the long wait until the turn
8 all
I hope that helps
ps in reference to replace ___ :// - new users can not link
Click to expand...
Click to collapse
SP Flashtool don't find phone. All drivers installed. Phone goes in fastboot or stock revocery only.
I wish i could get adb shell :crying:
Is there any way to flash system partition in Fastboot or sideload?

thank you
Hi brother
Thank you very much for the ROM, it help me a lot.

nickless07 said:
SP Flashtool don't find phone. All drivers installed. Phone goes in fastboot or stock revocery only.
I wish i could get adb shell :crying:
Is there any way to flash system partition in Fastboot or sideload?
Click to expand...
Click to collapse
Try to flash without the battery, rather than simply turned off the phone.

You my friend are a saviour.
Tried rooting and bricked my phone, Kingroot wouldn't work so tried the Kingo apk which bricked it.
Back to square one now so will wait for a verified root
Thanks :good::good::good::good::good::good::good:

Hi can with this repair an bootlop on the doogee nova y 100x .when i turnt off the phone ??
Sent from my Valencia2_Y100pro using XDA Free mobile app

Got my mother in law a doogee y100x. Apparently Google plus won't install on it. Did anyone face this? Is there a workaround?

Hi.
I had the bootloop problem, and I've solved with this firmware. (Many thanks TheSpecialNoob)
In order to FlashTool detects the phone, needs to be power off, without enter in FlashTool mode.
Select a scatter file, choose "Format All + Download" and press Download.
Thats all.

Custom recovery Doogee Nova Y100X
By the way, someone has managed to stick a custom recovery??? like the CWM or TWRP. If so, could you explain how you did, or upload the recovery.img file for the FlashTool?.
Thank you

zagzag99 said:
Got my mother in law a doogee y100x. Apparently Google plus won't install on it. Did anyone face this? Is there a workaround?
Click to expand...
Click to collapse
It's a problem on all Y100X devices. Doogee must have messed something up in the build.prop I hope they release an official fix.

Carliv Touch Recovery v3.3 for Doogee Nova Y100X
fanjul said:
By the way, someone has managed to stick a custom recovery??? like the CWM or TWRP. If so, could you explain how you did, or upload the recovery.img file for the FlashTool?.
Thank you
Click to expand...
Click to collapse
I auto-answer.
I found a Russian website, which explain how to install a custom recovery (Carliv Touch Recovery v3.3). :good:
I leave the link to the page. http://4pda.ru/forum/index.php?s=&showtopic=669833&view=findpost&p=42555995
If someone is not able to install it , I can try to explain it.
Also I have kept all the necessary files.
Regards

greetings from Spain
Thanks for giving us the original ROM.
I followed your steps and selecting "Format All + Download" I deleted the imeis and as I have read on the internet, also the NVRAM.
As I can do to permanently leave imeis? every time I have restored the ROM to modify and not know if I deleted more things to do a "Format ALL"
Someone I can pass the "NVRAM.bin" to upload it to my phone? Any other suggestions?
[email protected]
Regards

Yeah, I have the same problem. After restoring the stock rom, I have lost NVRAM settings.
Someone who has not restored the phone to stock, can upload the file nva.bin phone.
Thank you

Solution to “custom binary blocked by fpr lock” for galaxy a5 2016 – SM-A510FD

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!

[Completed] LG L50 Hard Brick

Hi companions I turn to you because I have a problem with my LG L50 (d213c). I'm using google translator, I hope you understand my faults ...
what happens to my terminal is that this bricked (or at least for me) when I turn only displays the download mode ... so it when connected via USB to the PC. I tried to flash the KDZ by various programs and tools and these have the same problem ... at the time and is loading the firmware on the phone only advances up to 10% in the LG Support Tool after that asks me to connect the device because there were problems (?) and so ad infinitum. In the programs selected and the KDZ file is loaded ... to already be flashing process, just beginning says there was problem when this extracting the KDZ and ends the process right there ... download the KDZ in different PC lg-phone-firmware and even down from an earlier version from the same page but also corresponded to my region and operator, to rule that it was the file that were damaged, and yet still can not flash the terminal, add that I have the drivers installed.
*I hope someone can help me or guide to revive my LG, because imagine if it appears the download mode and recognizes the PC (at least until I try to flash xd) there must be way to save, thanks in advance any help.
Si consigo ayuda en español mucho mejor xD

xNeoooo said:
Hi companions I turn to you because I have a problem with my LG L50 (d213c). I'm using google translator, I hope you understand my faults ...
what happens to my terminal is that this bricked (or at least for me) when I turn only displays the download mode ... so it when connected via USB to the PC. I tried to flash the KDZ by various programs and tools and these have the same problem ... at the time and is loading the firmware on the phone only advances up to 10% in the LG Support Tool after that asks me to connect the device because there were problems (?) and so ad infinitum. In the programs selected and the KDZ file is loaded ... to already be flashing process, just beginning says there was problem when this extracting the KDZ and ends the process right there ... download the KDZ in different PC lg-phone-firmware and even down from an earlier version from the same page but also corresponded to my region and operator, to rule that it was the file that were damaged, and yet still can not flash the terminal, add that I have the drivers installed.
*I hope someone can help me or guide to revive my LG, because imagine if it appears the download mode and recognizes the PC (at least until I try to flash xd) there must be way to save, thanks in advance any help.
Si consigo ayuda en español mucho mejor xD
Click to expand...
Click to collapse
Hi,
Please try posting your query here Ask any Query Newbie Friendly with all relevant details, the experts there maybe able to assist you.
-Vatsal

[FIX] Orange State Bootloop on OUKITEL K6000 Plus - HOW TO FIX

Hello,
After unlocking the bootloader and installing TWRP on my OUKITEL K6000 Plus I was trying to install madOS, but unfortunately my phone went into Orange State bootloop. I could not enter fastboot anymore, and at some point even Recovery stopped to work. My phone was almost dead. I was looking for solutions but actually there was no clear guide how to revive a patient. I found that many people have similar issue so when I finally managed to resurrect my K6000 with original stock ROM I decided to share my solution.
Here's the fix:
1. Google for 'Techprolonged MediaTek MT65xx USB VCOM Drivers'. Using the guide you will find install MediaTek DA USB VCOM Port Drivers via Device Manager (step 5). Do this even if you already previously installed MediaTek USB VCOM Drivers. This is very important to install this DA version of drivers, otherwise you may have problems with uploading stock ROM via SP Flash Tool.
2. Install SP Flash Tool if you don't have it yet. You can find it easily with google.
3. Download original stock K6000 Plus ROM V6.0. You can find it easily on needrom website (NOTE: you have to create an account on needrom if you don't have it yet). Unpack it.
4. Launch SP Flash Tool, go to Options->Option... in Connection settings change USB speed to Full speed and Battery to with battery. Close Option window.
5. In SP Flash Tool go to Download tab, click on choose right next to Scatter-loading file field, navigate to the folder where you unpacked previously downloaded stock K6000 Plus ROM V6.0. Open MT6750_Android_scatter.txt file.
6. In open menu choose Download Only if it's not selected by default. All fields below should have tick enabled. I mean for 'preloader', for 'recovery', etc...
7. Unplug your phone from PC if it's connected. Shut down your phone by clicking and holding for approx 10 secs ALL THREE BUTTONS: VOL UP + VOL DOWN + POWER. If you do this properly, your phone should not self-boot into Orange State anymore.
8. In SP Flash Tool click Download icon (the one with green arrow), all the fields should become inactive.
9. Using one hand only click and hold at the same time VOL UP + POWER button.
10. Now, while you still hold these buttons, you have to connect your phone to PC (plug in micro USB cable into your phone). VERY IMPORTANT: If you have STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003) error after you connect it means you don't have DA version of MediaTek driver properly installed (step no. 1).
11. Your phone should start to flash up and you should see the progress in SP Flash Tool status bar. You can release VOL UP and POWER button now. The process may take long time, for me it was more than 1 hour. The longest part was flashing up the [system]. The good thing is you can observe the progress during whole process.
12. When flashing process is end you will see a small window with the information about completion. Now you can unplug your phone, and launch it with POWER button. You should still see the Orange State message but right after that your phone should boot up into normal mode with freshly uploaded original stock ROM. Congratulations!
Hopefully this will also fix your K6000 Plus and maybe even other models.
I'm really sorry I don't provide any direct links, but I haven't posted 10 posts yet and my XDA account is still limited.
Regards,
Slavedriver

Please help I have error 4032 (BROM ERROR S_FT_ENABLE_DRAM_FAIL)

1. Google for 'Techprolonged MediaTek MT65xx USB VCOM Drivers'. Using the guide you will find install MediaTek DA USB VCOM Port Drivers via Device Manager (step 5). Do this even if you already previously installed MediaTek USB VCOM Drivers. This is very important to install this DA version of drivers, otherwise you may have problems with uploading stock ROM via SP Flash Tool.
this should solve that

STATUS_BROM_CMD_SEND_DA_FAIL
persists even after installing correct drivers?
Solution: Choose
Download Agent as DA-PL in SP flash tools. And follow the same guide.

Thank you so much for this post, just saved an Oukitel K6000 Plus. Just finished process, rebooting normally for first use. It's been stressfull hours, what a relieve.

slavedriver83 said:
9. Using one hand only click and hold at the same time VOL UP + POWER button.
10. Now, while you still hold these buttons, you have to connect your phone to PC (plug in micro USB cable into your phone). VERY IMPORTANT: If
Click to expand...
Click to collapse
this helped me a lot with my ulefone armor 2, thanks

Fixed the orange state, thanks a lot for this guide.
Do you think I shall try again to upgrade to Android 8 anymore?

slavedriver83 said:
9. Using one hand only click and hold at the same time VOL UP + POWER button.
Click to expand...
Click to collapse
Thank you very much for the advice
I thought I put my phone in the trash when I read this.
But in point 9 I had to push only the VOL UP if I press the two buttons, the AP returns an error.

You saved mine as well, slavedriver!
And it is a Teclast Tpad A10S!
I had given it up.
Thanks a lot!

It works also on U20 plus. I had to select DA_SWSEC as Download Agent. Thank you so much!

Guide worked Perfectly for me.
My mobile was bricked in the same Bootloop. The guide worked perfectly for me. Thanks a lot for useful and detailed help.

I understand this thread is almost 1 year old. I tried this procedure and everything went well. The only problem the phone does not boot. It does turn on but nothing comes up. No boot menu no logo just a few flickering lights and a very dark background. Does anyone have any ideas?
OK6000 Plus

pvkid said:
I understand this thread is almost 1 year old. I tried this procedure and everything went well. The only problem the phone does not boot. It does turn on but nothing comes up. No boot menu no logo just a few flickering lights and a very dark background. Does anyone have any ideas?
OK6000 Plus
Click to expand...
Click to collapse
Tried this guide but SP shows the following messagge "STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060005) " (so it doesn't end with 3 but with 5)

Pyandroid said:
1. Google for 'Techprolonged MediaTek MT65xx USB VCOM Drivers'. Using the guide you will find install MediaTek DA USB VCOM Port Drivers via Device Manager (step 5). Do this even if you already previously installed MediaTek USB VCOM Drivers. This is very important to install this DA version of drivers, otherwise you may have problems with uploading stock ROM via SP Flash Tool.
this should solve that
Click to expand...
Click to collapse
Bro I got a different error just looks like:
ERROR STATUS_SEC_AUTH_FILE_NEEDED (0xc0030012)
Please help me out...I use "tecno spark 4 kc2"

slavedriver83 said:
Hello,
After unlocking the bootloader and installing TWRP on my OUKITEL K6000 Plus I was trying to install madOS, but unfortunately my phone went into Orange State bootloop. I could not enter fastboot anymore, and at some point even Recovery stopped to work. My phone was almost dead. I was looking for solutions but actually there was no clear guide how to revive a patient. I found that many people have similar issue so when I finally managed to resurrect my K6000 with original stock ROM I decided to share my solution.
Here's the fix:
1. Google for 'Techprolonged MediaTek MT65xx USB VCOM Drivers'. Using the guide you will find install MediaTek DA USB VCOM Port Drivers via Device Manager (step 5). Do this even if you already previously installed MediaTek USB VCOM Drivers. This is very important to install this DA version of drivers, otherwise you may have problems with uploading stock ROM via SP Flash Tool.
2. Install SP Flash Tool if you don't have it yet. You can find it easily with google.
3. Download original stock K6000 Plus ROM V6.0. You can find it easily on needrom website (NOTE: you have to create an account on needrom if you don't have it yet). Unpack it.
4. Launch SP Flash Tool, go to Options->Option... in Connection settings change USB speed to Full speed and Battery to with battery. Close Option window.
5. In SP Flash Tool go to Download tab, click on choose right next to Scatter-loading file field, navigate to the folder where you unpacked previously downloaded stock K6000 Plus ROM V6.0. Open MT6750_Android_scatter.txt file.
6. In open menu choose Download Only if it's not selected by default. All fields below should have tick enabled. I mean for 'preloader', for 'recovery', etc...
7. Unplug your phone from PC if it's connected. Shut down your phone by clicking and holding for approx 10 secs ALL THREE BUTTONS: VOL UP + VOL DOWN + POWER. If you do this properly, your phone should not self-boot into Orange State anymore.
8. In SP Flash Tool click Download icon (the one with green arrow), all the fields should become inactive.
9. Using one hand only click and hold at the same time VOL UP + POWER button.
10. Now, while you still hold these buttons, you have to connect your phone to PC (plug in micro USB cable into your phone). VERY IMPORTANT: If you have STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003) error after you connect it means you don't have DA version of MediaTek driver properly installed (step no. 1).
11. Your phone should start to flash up and you should see the progress in SP Flash Tool status bar. You can release VOL UP and POWER button now. The process may take long time, for me it was more than 1 hour. The longest part was flashing up the [system]. The good thing is you can observe the progress during whole process.
12. When flashing process is end you will see a small window with the information about completion. Now you can unplug your phone, and launch it with POWER button. You should still see the Orange State message but right after that your phone should boot up into normal mode with freshly uploaded original stock ROM. Congratulations!
Hopefully this will also fix your K6000 Plus and maybe even other models.
I'm really sorry I don't provide any direct links, but I haven't posted 10 posts yet and my XDA account is still limited.
Regards,
Slavedriver
Click to expand...
Click to collapse
Solution?
for:
ERROR STATUS_SEC_AUTH_FILE_NEEDED (0xc0030012)
"Tecno spark 4 kc2"

slavedriver83 said:
Hello,
After unlocking the bootloader and installing TWRP on my OUKITEL K6000 Plus I was trying to install madOS, but unfortunately my phone went into Orange State bootloop. I could not enter fastboot anymore, and at some point even Recovery stopped to work. My phone was almost dead. I was looking for solutions but actually there was no clear guide how to revive a patient. I found that many people have similar issue so when I finally managed to resurrect my K6000 with original stock ROM I decided to share my solution.
Here's the fix:
1. Google for 'Techprolonged MediaTek MT65xx USB VCOM Drivers'. Using the guide you will find install MediaTek DA USB VCOM Port Drivers via Device Manager (step 5). Do this even if you already previously installed MediaTek USB VCOM Drivers. This is very important to install this DA version of drivers, otherwise you may have problems with uploading stock ROM via SP Flash Tool.
2. Install SP Flash Tool if you don't have it yet. You can find it easily with google.
3. Download original stock K6000 Plus ROM V6.0. You can find it easily on needrom website (NOTE: you have to create an account on needrom if you don't have it yet). Unpack it.
4. Launch SP Flash Tool, go to Options->Option... in Connection settings change USB speed to Full speed and Battery to with battery. Close Option window.
5. In SP Flash Tool go to Download tab, click on choose right next to Scatter-loading file field, navigate to the folder where you unpacked previously downloaded stock K6000 Plus ROM V6.0. Open MT6750_Android_scatter.txt file.
6. In open menu choose Download Only if it's not selected by default. All fields below should have tick enabled. I mean for 'preloader', for 'recovery', etc...
7. Unplug your phone from PC if it's connected. Shut down your phone by clicking and holding for approx 10 secs ALL THREE BUTTONS: VOL UP + VOL DOWN + POWER. If you do this properly, your phone should not self-boot into Orange State anymore.
8. In SP Flash Tool click Download icon (the one with green arrow), all the fields should become inactive.
9. Using one hand only click and hold at the same time VOL UP + POWER button.
10. Now, while you still hold these buttons, you have to connect your phone to PC (plug in micro USB cable into your phone). VERY IMPORTANT: If you have STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003) error after you connect it means you don't have DA version of MediaTek driver properly installed (step no. 1).
11. Your phone should start to flash up and you should see the progress in SP Flash Tool status bar. You can release VOL UP and POWER button now. The process may take long time, for me it was more than 1 hour. The longest part was flashing up the [system]. The good thing is you can observe the progress during whole process.
12. When flashing process is end you will see a small window with the information about completion. Now you can unplug your phone, and launch it with POWER button. You should still see the Orange State message but right after that your phone should boot up into normal mode with freshly uploaded original stock ROM. Congratulations!
Hopefully this will also fix your K6000 Plus and maybe even other models.
I'm really sorry I don't provide any direct links, but I haven't posted 10 posts yet and my XDA account is still limited.
Regards,
Slavedriver
Click to expand...
Click to collapse
Hi, do I need my phone to be rooted to do this.
I unlocked bootloader in my gionee f205 from fastboot and now it is in orange state bootloop.
I haven't rooted my phone before doing it.

Need working stock ROM for my MTK Timmy M50!

Hello, I have a Timmy M50 with 3 factory malwares (detected with Dr.Web antivirus):
Android.Downloader.561.origin in /system/priv-app/MediaService/oat/arm/MediaService.odex
Android.Mobifun.14 in /system/priv-app/com.android.telephone/com.android.telephone.apk
Android.Mobifun.14 in /system/priv-app/com.android.telephone/arm/com.android.telephone.odex
It seems this phone is impossible to root. I unlocked the bootloader (there's an option in settings), then I tried the following software: Cydia Impactor, MTK Droid Tool, Root Genius (pc & apk), 360root, Baidu Root (v1.0 and v2.86), iRoot (1.8.9), Kingoroot (pc & apk), Kingroot (px & apk), OneClickRoot, SRSRoot. No success.
So I followed a guide to re-flash stock ROM. I used SP Flash Tool v5.1804 and rom Timmy_M50_MT6737M_R2_20170713_7.0.
I selected "download only" mode but it refused to dowload the firmware on the phone, the program told me to use "Format all + Download" mode because PMT was changed. So I went on with this.
Since then, my phone is unusable. Display turns on but shows a black screen, flash led flashes 3 times (error code?), the startup sound plays but nothing is shown on screen. After about ten seconds another sound is played (it seems an error sound).
So I downloaded and tried many other stock ROMS (Android 7 and 6), but none worked. I downloaded them from:
filesrom com - rom-timmy-m50-mt6737m (3 firmwares Android 7)
needrom com - download - timmy-m50 (14 firmwares Android 7)
needrom com - download - timmy-m50-6-0 (3 firmwares Android 6)
and some others found on the net.
Some roms show the same behavior already described (black screen), some others don't let the phone turn on.
Since they're all stock roms, I don't understand why they don't work on my Timmy M50.
I tried other flashing programs, but they don't detect my phone or throw some strange errors.
My Timmy M50 is dated 06/2017 on the back, so it shouldn't have a revised electronic (that maybe is present on most recent versions) but the original one.
I also tried a complete format, it makes no difference.
Any suggestion? Or any new firmware to try?
Please help me!
Thank you

Mismo problema
Presento el mismo problema , ayudaa

Idem. Any solutions?
Inviato dal mio LEX720 utilizzando Tapatalk