Related
So I got a cheap android tablet and I wanted to root it. I was successful so I decided to install TWRP. I searched for my specific model and found an image on a german forum. I downloaded and flashed it and it got stuck in a reboot loop. So I looked at the image and it was for the QV1030. I tried to get it into recovery but couldn't. Many sources told me to hold Vol Up and Lock, and I tried this and more. Nothing would make it enter recovery mode. Then I read about SP Flash Tool and found the stock rom for the tablet and decided I would try to flash that. It kept coming up with an error, and every source online told me to format the flash except for the bootloader and then I could flash it. So I did. Now it doesn't show anything on screen, and SP Flash Tool comes up with error 6045. But it does show up in device manager under com ports as, "MediaTek USB Port" so I think I can still do something about it. I don't have any backups. I don't know what I'm doing. I require assistance please.
So I reflashed the entire backup and it come up with no error. The logo comes up and it plays the chime. The logo does this little shimmer effect and once it gets to this screen, it shimmers indefinitely. If I plug it in, it begins installing a driver and then stops part way through.
drsinclair said:
So I reflashed the entire backup and it come up with no error. The logo comes up and it plays the chime. The logo does this little shimmer effect and once it gets to this screen, it shimmers indefinitely. If I plug it in, it begins installing a driver and then stops part way through.
Click to expand...
Click to collapse
I left it for about 5 minutes and it finished the driver. I thought it froze but I was wrong. It shows up now on device manager under Portable Devices as, "MTP USB Device". I tried to see if it was listed as a device by ADB. It is not. Lets just say I've already learned a thing or two about this stuff. Good thing I did it on an 80 dollar chinese tablet and not my HTC One M9
drsinclair said:
I left it for about 5 minutes and it finished the driver. I thought it froze but I was wrong. It shows up now on device manager under Portable Devices as, "MTP USB Device". I tried to see if it was listed as a device by ADB. It is not. Lets just say I've already learned a thing or two about this stuff. Good thing I did it on an 80 dollar chinese tablet and not my HTC One M9
Click to expand...
Click to collapse
I got it to work again mostly. So I realized that I wasn't flashing the whole backup. Some things didn't have a path and I had to set it manualy. Now it has CFW for some reason, but I reset it and it works now. The only thing is WiFi is not turning on. Any ideas about that?
drsinclair said:
I got it to work again mostly. So I realized that I wasn't flashing the whole backup. Some things didn't have a path and I had to set it manualy. Now it has CFW for some reason, but I reset it and it works now. The only thing is WiFi is not turning on. Any ideas about that?
Click to expand...
Click to collapse
I actually want to upgrade this from Android 4.2.2 to a more recent version. Do you guys have any ideas about that?
So I've come to the conclusion that while the device is no longer bricked, the current installation is written over the old one and things are conflicting. I know this because I looked through the cache and found filenames referring to apps I had installed before breaking it. So would the solution be to wipe the system partition and reflash the system.img so everything is fresh? Or does the problem lie elsewhere.
I formated the system partition, used SP Flasher to flash system.img and then did a factory reset. The issue has still not been solved. And now that I have done that, I don't have root access anymore. Framaroot says it was successful and I restart and check root explorer on ES File Explorer and it doesn't work.
I gained root access using a different method. However the WiFi still doesn't work. I think it may be that the mac address information was from the backup I flashed from the internet, and therefore doesn't match. I found a guide that tells me how to hex edit a file and put in my real mac address, but it's unavailable under wifi. I don't have the sticker on the back that says it either. How else can I find it?
Turns out the mac address can be anything. I used SN Write tool and an AB DB for my chipset and it still didn't solve the problem. I have no idea what to do. Can anyone help me?
I fixed the issue by grabbing a different backup from some russian website and flashing the system.img and secro.img to it. It now works fine 100%. Thanks
help - link
drsinclair said:
I fixed the issue by grabbing a different backup from some russian website and flashing the system.img and secro.img to it. It now works fine 100%. Thanks
Click to expand...
Click to collapse
Hey man! I have the same problems with my QV 830. Can you give me the link for system.img and secro.img, please?
Hello , Guys
Since you all probably know, Lenovo A7020a48 has Android 6.0 Marshmallow which cannot be rooted because of the following :
1 - We got a locked bootloader, we can't flash or boot into custom recoveries and sadly at the moment I couldn't find a way to unlock it.
2 - We don't even have a custom recovery made for that model yet, I tried different version of TWRP for A7020a40 ~ A7020a46 models and they all crashed upon booting to them.
3 - Kingroot and similiar apps can't root Android 6.0.
So the only way to root your phone would be to downgrade it to Android 5.1 Lolipop which is easy.
Here is download links for the stock roms :
A7020a48_LL_S125_160419_ROW.rar.7z
A7020a48_S259_160721_ROW.7z
When you finish downloading please don't forget that we are going to use the SP Flash Tool provided in the rom as only that version "SP_Flash_Tool_5.1552.00" worked for me with no errors however with latest versions i got problems.
Obviously you are going to install the USB drivers and CDC drivers located at the "DRV_Tools" folder in the rom you downloaded.
after installing the drivers correctly turn off your phone, open SP flash tool, and choose the scatter file located at : "\SW\target_bin\MT6755_Android_scatter.txt" and then choose "Download Mode" then wait for it to finish checking the files, then click on the download button on the top left corner.
Then connect your device and wait for it to detect the device .
Wait until the flashing is complete Then After the green circle appears, simply disconnect your phone and boot into system normally.
Note: You might see a black box in the bottom left corner saying "efuse flash done or similar stuff" don't worry about it" it won't appear again however if you got an error saying "DL image failed" then you did something wrong repeat the previous steps again and make sure you choose everything correct especially your rom.
Now to the last part, finish the first time setup screens by skipping most of them and DO NOT UPDATE YOUR SYSTEM AT ALL
if you got a notification to update, simply ignore it or press cancel, and open google chrome, download king root and wait for it to simply root you phone.
Congratulations that's the first part for rooting your phone.
Now to Fixing Your IMEI
Simply Enable USB debugging in options and enable OEM unlocking.
Then power off your phone.
Download this tool : MauiMETA_v9.1635.23.rar
Yes Again it has to be that specific versions, with other versions i couldn't connect to my device however with this version i could.
Extract it to a random location on your pc and MauiMeta.exe and click on options and enable "enable composite kernel usb (adb)" then click on reconnect.
Now you have to connect your device with usb and turn it on, don't worry MauiMeta will change the boot to META mode automatically after it starts booting leave it as it's and wait for the tool to connect to your phone.
***After it connects simply choose IMEI download and a new window should appear, first click on upload from flash button then click yes to retrieve the modem file from your phone, then simply type your IMEI ( Please note that changing your IMEI is illegal however you should only use this method to fix your IMEI not change it ! , you have been warned)
Note : IMEI numbers should be 15 numbers however with MauiMeta you should only type the first 14 number as the 15th number is only a checksum number and will be added automatically.
After typing the IMEIs and checking them simply click on download to flash.
After it says "flashing is successful" then close the window and click Disconnect, and your phone should turn off automatically and you should start it up again.
*** Note : If you have a corrupted NVRAM file on your phone then you are lucky since that rom comes with the modem db file as well to fix NVRAM issues, simply click "Change NVRAM database file" then click No to choose the file, The file exists in the ROM package you downloaded earlier in the following location : "SW\modemdb\MDDB_InfoCustomApp....etc.EDB" and continue the rest of the steps normally.
Please Note that I won't provide support for this, I have only created this tutorial to save time for other people and I'm not expert yet to fix all the problem you may face however after following these steps i managed to root my device and even fix the invalid imei errors i got.
Also if you found errors in my thread or mistakes Please let me know so i can fix them.
Good luck and Don't hard brick your phone XD
I get this error in SP FLASH TOOL 5.1552.00- STATUS_SEC_PL_VFY_FAIL (-10*****)
Any idea ?
Error coming?
i got the same error in SP FLASH TOOL 5.1552.00- (BROM ERROR : STATUS_SEC_PL_VFY_FAIL (-1073610746))
nishkarshxda said:
i got the same error in SP FLASH TOOL 5.1552.00- (BROM ERROR : STATUS_SEC_PL_VFY_FAIL (-1073610746))
Click to expand...
Click to collapse
Use This Version Of Flash tool enable usb and storage checksum hit download ( Use different usb port better use backside of CPU )
Sp-flash-tool-V5-1548
10000% Working
mobile not getting switched on after downgrading
Hi, I tried to flash my Lenovo vibe K5 note (a7020a48 4 GB RAM). It was done without any error but I couldn't switch on my mobile nor it was detected in my computer. Please help me
Bro i download and flashed successfully but phone cant turn on but i flashed again marshmallow phone will turn on...Why lollipop cant boot... Second link for rom is lollipop or not
Any proof?
Bro where did you get these two rooms from? Tell us the source. Otherwise, how will we know?
after flash mobile no on anybody can u help me to how to flash 5.0 in lenovo k5 note
It worked great thanks .......though minor glitches may occur such as not playing any sound and not supporting JIO sim card. These can be fixed by System Updating your phone to the latest version preferably through a sound wifi connection.
Hi again,
I have a friends T95Z and trying to fix it up. It won't connect on WiFi. When you go to network settings - WiFi is switched off. If you switch it on - it "pretends" to search for about 40 seconds - finds no AP nearby and switches "Off".
I have wrenched on a number of these T95Z. boxes and always seem to get them working.*
Hats off to Superceleron and his ROM -* His ROM really cleaned up the first couple of these I worked on. They had the LTM8830 chipset I think.
Then I worked on a couple newer T95Z's and that ROM didn't work. If I recall - same thing where you can try and turn the WiFi on but it just turns off. I think they turned out to have the 9377 chipset. Found a workable ROM for them and all is well.
Okay so here are some pics of the insides of this one:**https://imgur.com/a/Kd2M1Ta
I flashed a bunch of ROMs - Here is like a list of some of the file names etc:
Poison ROM - https://forum.xda-developers.com/an...mputers/amlogic/t95z-plus-poison-rom-t3751720
T95ZPLUS_q200_9377_customV3.2
atvXperience_v2F_s912
s912_atvXperience_v2FF
T95U PRO_S912_02012017_
v1016-EB-AGCF-LPDDR3-2G
Sorry that I didn't keep great notes on what I flashed but hey - once you start flashing - it is just so easy to try another one.*
Anyway - Several of the ROM's said they were for the AP6255 chipset and ALL of the ROM's do the same thing where the WiFi just won't turn on.*
Now I am not an expert on this - so I don't know:
Can you confirm - Is this a Sunvell?
Is the wifi chipset an AP6255?
What else should I try?* I wandered into a T95U ROM... should I wander further and look for Beelink or other manuf ROM's that show the AP6255?
Is there any other tool or APK that can be flashed after ROM install to query the hardware config or add chipset support?
Open to ideas.*
Thanks!
wantpizza said:
Hi again,
I have a friends T95Z and trying to fix it up. It won't connect on WiFi. When you go to network settings - WiFi is switched off. If you switch it on - it "pretends" to search for about 40 seconds - finds no AP nearby and switches "Off".
I have wrenched on a number of these T95Z. boxes and always seem to get them working.*
Hats off to Superceleron and his ROM -* His ROM really cleaned up the first couple of these I worked on. They had the LTM8830 chipset I think.
Then I worked on a couple newer T95Z's and that ROM didn't work. If I recall - same thing where you can try and turn the WiFi on but it just turns off. I think they turned out to have the 9377 chipset. Found a workable ROM for them and all is well.
Okay so here are some pics of the insides of this one:**https://imgur.com/a/Kd2M1Ta
I flashed a bunch of ROMs - Here is like a list of some of the file names etc:
Poison ROM - https://forum.xda-developers.com/an...mputers/amlogic/t95z-plus-poison-rom-t3751720
T95ZPLUS_q200_9377_customV3.2
atvXperience_v2F_s912
s912_atvXperience_v2FF
T95U PRO_S912_02012017_
v1016-EB-AGCF-LPDDR3-2G
Sorry that I didn't keep great notes on what I flashed but hey - once you start flashing - it is just so easy to try another one.*
Anyway - Several of the ROM's said they were for the AP6255 chipset and ALL of the ROM's do the same thing where the WiFi just won't turn on.*
Now I am not an expert on this - so I don't know:
Can you confirm - Is this a Sunvell?
Is the wifi chipset an AP6255?
What else should I try?* I wandered into a T95U ROM... should I wander further and look for Beelink or other manuf ROM's that show the AP6255?
Is there any other tool or APK that can be flashed after ROM install to query the hardware config or add chipset support?
Open to ideas.*
Thanks!
Click to expand...
Click to collapse
The problem is that flashing multiple ROM's can sometimes leave remnants behind and mess things up. Or, you flashed an incompatible ROM that hosed up the EEPROM. The first thing I'd suggest trying, is to go back to square one by flashing the proper stock ROM back on the device again using the USB Flash Tool and be sure to select "Force Erase All" when doing it. I've ran into the same problem on multiple occasions and flashing stock always seems to get me back up and running again.
If that doesn't work, then you'll probably need to crack it open and reset the EEPROM by shorting out the pins in order to get it into a state where it'll overwrite the incorrect code. To do that, make sure the USB Burning tool is running and the USB cable it plugged in so you know when it's been triggered. Then run a paperclip along the pins of the chip until it trips and shows back up in the tool. That will put it into programming mode so you can re-flash the ROM again completely.
Link to 2/16 STOCK FW: https://mega.nz/#F!YJ0nTC4Z!qBz6gmJCjwHn0HtlVe2apw
Link to 3/32 STOCK FW: https://goo.gl/RG92GR
Good luck!
Thanks for the reply.
I am downloading the 2G version now. I will try a force flash as suggested.
A couple of questions - when a ROM leaves remnants - what are the other symptoms? I thought that lots of problems appear when the flash is "dirty"?
Anyway - I will flash this version when Mega lets me finish the download.
If I have to move on to step two and short the eeprom - which chip in my pictures is that?
Thanks again!
AthieN said:
. . . .If that doesn't work, then you'll probably need to crack it open and reset the EEPROM by shorting out the pins in order to get it into a state where it'll overwrite the incorrect code. To do that, make sure the USB Burning tool is running and the USB cable it plugged in so you know when it's been triggered. Then run a paperclip along the pins of the chip until it trips and shows back up in the tool. That will put it into programming mode so you can re-flash the ROM again completely.
. . . .
Good luck!
Click to expand...
Click to collapse
....
Okay - well force flashed the referenced ROM and even another "Factory" ROM supposedly for the 6255 wifi chipset. No go.
They both still work it seems fine - but no wifi.
So any hints on reseting the EEPROM?
Thanks again,
wantpizza said:
....
Okay - well force flashed the referenced ROM and even another "Factory" ROM supposedly for the 6255 wifi chipset. No go.
They both still work it seems fine - but no wifi.
So any hints on reseting the EEPROM?
Thanks again,
Click to expand...
Click to collapse
Very strange. It almost sounds like your WiFi radio is malfunctioning. If that's the case, then there's really not much you'll be able to do to fix it unfortunately...
One thing you can do to verify, is to grab a file manager like FX, go into /system/etc/wifi and verify that the 6255 directory exists. If it does, then it's probably just the radio. You'll need to be rooted to do the above though. Also, grab a terminal emulator, 'su -' to root, and run a 'dmesg |grep eth' and 'dmesg |grep wifi' and see what it says. You might be able to figure some stuff out based on the output... Are you 100% sure you have the 6255 radio?
As for the EEPROM, it's pretty dangerous to do that, but if you really want to try, just do what I mentioned earlier. Crack open the device, plug it in to power and the USB, and then run a paperclip along the posts, shorting them out until the device resets and shows back up in the USB burning tool...
Okay - flashed just about as many variations I could find. I tried your trick of looking for a folder inside /system/etc/wifi and did confirm there is a directory labeled 6255 and it has some files in it. I will try to run a couple of grep commands too and post what I find. But I am starting to feel that the actual chip is faulty.
After further thought - I am not really wanting to do a dangerous step to reset an EEPROM when it might turn this from a device without wifi to a device that does nothing.
Still curious - looking at the pictures I posted to begin with - is anyone sure that the chipset is the AP6255? Does this chipset do both the cat5 and wifi networking? Or is there yet another chip that does the cat5 networking? (I know there are better words for this - just can't think of them right now)
Anyway - anyone have any other thoughts? I already explained to my friend that this one looks like a hardwire only device so I am putting it back together.
Thanks again,
You're beating a dead horse thinking some magic ROM you flash will fix it when it's clear the source of the problem is the common denominator of wifi being hosed on all of them. Especially since you said you installed roms that supported your AP6255 (as your board pic makes clear) wifi chip where everything else worked except the wifi.
You need to grep for the wifi network errors as AthieN spelled out how to do in his initial reply.
wantpizza said:
Hi again,
I have a friends T95Z and trying to fix it up. It won't connect on WiFi. When you go to network settings - WiFi is switched off. If you switch it on - it "pretends" to search for about 40 seconds - finds no AP nearby and switches "Off".
I have wrenched on a number of these T95Z. boxes and always seem to get them working.*
Hats off to Superceleron and his ROM -* His ROM really cleaned up the first couple of these I worked on. They had the LTM8830 chipset I think.
Then I worked on a couple newer T95Z's and that ROM didn't work. If I recall - same thing where you can try and turn the WiFi on but it just turns off. I think they turned out to have the 9377 chipset. Found a workable ROM for them and all is well.
Okay so here are some pics of the insides of this one:**https://imgur.com/a/Kd2M1Ta
I flashed a bunch of ROMs - Here is like a list of some of the file names etc:
Poison ROM - https://forum.xda-developers.com/an...mputers/amlogic/t95z-plus-poison-rom-t3751720
T95ZPLUS_q200_9377_customV3.2
atvXperience_v2F_s912
s912_atvXperience_v2FF
T95U PRO_S912_02012017_
v1016-EB-AGCF-LPDDR3-2G
Sorry that I didn't keep great notes on what I flashed but hey - once you start flashing - it is just so easy to try another one.*
Anyway - Several of the ROM's said they were for the AP6255 chipset and ALL of the ROM's do the same thing where the WiFi just won't turn on.*
Now I am not an expert on this - so I don't know:
Can you confirm - Is this a Sunvell?
Is the wifi chipset an AP6255?
What else should I try?* I wandered into a T95U ROM... should I wander further and look for Beelink or other manuf ROM's that show the AP6255?
Is there any other tool or APK that can be flashed after ROM install to query the hardware config or add chipset support?
Open to ideas.*
Thanks!
Click to expand...
Click to collapse
Thanks for the other hint on running the grep command.
I tried and tried to copy this a better way - but short of retyping word for word - a picture was the best I could do.
https://imgur.com/a/oZxojmU
I don't read many reports from a grep command but it is interesting - on one of the lines it reports that "No power on pin 2"
Not sure if it simply is that the chip wasn't soldered in correctly?
Anyway - that is the update. Any thoughts or things to try before I give up are appreciated.
Regards,
el80ne said:
You're beating a dead horse thinking some magic ROM you flash will fix it when it's clear the source of the problem is the common denominator of wifi being hosed on all of them. Especially since you said you installed roms that supported your AP6255 (as your board pic makes clear) wifi chip where everything else worked except the wifi.
You need to grep for the wifi network errors as AthieN spelled out how to do in his initial reply.
Click to expand...
Click to collapse
Sorry - didn't read this before my post but don't worry - I am with ya. I had a suspicion from the start. But - there is lots of "Wizardry" in these forums so worth a post.
Thanks everyone.
The good news is that it looks like your kernel isn't finding the right wifi driver on boot which is why it's shutting down. That means there actually might be a ROM version out there that supports your device. But maybe it just doesn't know where to look.
The name of your modular driver is for the AP6255 is dhd.ko.
Try loading it manually from command line as root.
# modprobe dhd
See if you can find dhd.ko in your filesystem somewhere under /lib/modules.
If you can't then try and find a rom that has your wifi driver module on it called dhd.ko.
Update: Just saw there's a more updated qualcomm driver called qca9377.ko so try to load that module or see if the file qca9377.ko exists under /lib/modules.
# modprobe qca9377
wantpizza said:
Thanks for the other hint on running the grep command.
I tried and tried to copy this a better way - but short of retyping word for word - a picture was the best I could do.
https://imgur.com/a/oZxojmU
I don't read many reports from a grep command but it is interesting - on one of the lines it reports that "No power on pin 2"
Not sure if it simply is that the chip wasn't soldered in correctly?
Anyway - that is the update. Any thoughts or things to try before I give up are appreciated.
Regards,
Click to expand...
Click to collapse
Okay - well good news bad news?
I tried to load each of those other drivers
Code:
# modprobe qca9377
modprobe: can't change directory to '/system/lib/modules': No such file or directory
# modprobe dhd
modprobe: can't change directory to '/system/lib/modules': No such file or directory
Now I need to find some other rom that has those drivers?
Or can I just find those files and place them in that file directory? Anywhere I can just get the driver?
Thanks again,
Okay - newest update
I searched and there was no folder named 'modules' in system/lib
So I created that folder and I copied dhd.ko into that folder. (I searched for the newer qca9377 but i couldn't find it)
Now if I type modprobe dhd in terminal as su I get
Code:
#modprobe dhd
modprobe: can't open 'modules.dep': No such file or directory
Oh and - newest wrinkle - somehow I installed something that pops a durex condom ad ontop of everything about every 45 seconds. What is the easy way to find the offending apk? I tried to long click so I could find the properties or something but nothing working. The only thing open is this terminal emulator??
Anyway- that is the latest.
Thanks again,
i have the same issue did you ever resolve?
me too, anyone resolve it?
hello all,
yesterday i decide to root my old phone, to see if i could get spoofing working on pokemon go.
flashed it manged it to get superSU , installed magisk, passed the safetycheck, and got spoofing working. but since the phone was full of old apps, i decide to do a factory reset, but looks like this ruined everything, so i went did all steps again, at 1 point i forget to enable oem option.
so i get the msg, custom binary blocked by frp, once i turn my phone on. after hours of searching i found the right firmware, and i could fix this problem.
but now, no matter what i do, if i press volume down, home, power i keep getting in download modus, instant of recovery modus.
i need to get in twrp to install magisk from there.
because if i try, it from the magisk app manager, like i did it the first time, it say say failed to load boot.img
personally i think that i have flashed some wrong roms or something, but i am really stuck now on what do to, is there something easy to uninstall everything i have done? or anyone can point me in a direction of what do now?
Samsung j510fn(2016)
Build: nmf26xj510fnxxu2brb1
thanks, and sorry for my bad english
Hi , if your device is not boot properly try to flash this 4 file firmware:
http://www.mediafire.com/file/h884u0o8dy9va0l/J510FNXXU2BQJ8_7.1.1_4File.zip
Before you do that :
- Make sure that your battery is full charged !
- Put your device into Download mode.
- Load those files properly inside Odin flash tool.
- Connect your device with usb 2.0 port and once Odin detects your device click on Start .
If that doesn't help you to with latest firmware for your region :
https://updato.com/firmware-archive-select-model?q=j510fn&exact=1&r=&v=Nougat(Android+7.1.1)&rpp=15
Good luck
Teddy Lo said:
Hi , if your device is not boot properly try to flash this 4 file firmware:
Before you do that :
- Make sure that your battery is full charged !
- Put your device into Download mode.
- Load those files properly inside Odin flash tool.
- Connect your device with usb 2.0 port and once Odin detects your device click on Start .
If that doesn't help you to with latest firmware for your region :
Good luck
Click to expand...
Click to collapse
Thx my friend it worked
have other question maybe you can help me also? i need to deodex my system, but i read everywhere that i need more then 25% free space on my /system folder. currently i have 0,1mb free of the 3gb. while my internal storage have 8gb free space, is there a easy way to make /system bigger so i can deodex it?
greetz
I don't know , but maybe this can help you:
https://www.samsungdeodex.com/2017/08/rom-deodex-samsung-j510fn.html?m=1
or
https://4pda.ru/forum/index.php?showtopic=925236&st=140
You must to know that phone modification can brick your device permanently !!! So think twice before you do anything.
Hello guys! I have a problem with one phone that i am trying to fix for someone and I feel sooo, sooo completely lost in all of this as I know almost nothing about this. The cell phone model that is in question is Alcatel One Touch Pop C3-4033x.
It seems to be using a Mediatek chipset and I was reading some of your advices here & there and tried using the program called SP FlashTools but it always resulted in error, in the end. It seems that something is wrong with this phones emmc flash memory. So, I tried transfering some files as a zip files to the SD-card and tried to apply update from it, but it said always: Installation aborted. And then, I have tried looking for a way to flash stock firmware of that specific Alcatel model on SD-card, but I just don't have any clue how to do it, if it is possible, even. Maybe I should just give up trying?
Oh, I almost forgot to write that the phone doesn't have the access to Android OS and USB debugging isn't turned on, because computer doesn't seem to list it and I don't know if there any button combinations that Alcatel uses for this model to get into that fastboot or adb mode, even though have installed mediatek drivers. It can only get into Android System Recovery 3e. That seems to be everything, I think, at least.
Oh guys, I am so, so, so sorry if I am bothering you with this. I just didn't know what or where else to ask this. Thank you sooo much!
Hi download those files:
Firmware:
https://www.mediafire.com/file/bpm4ibsbmr4q6nc/OT-4033X-Without_Mobilis_logo__BY_GSMSERVE.rar/file
SP Flash tool:
https://androidfilehost.com/?fid=11410963190603870440
Driver:
https://mega.nz/#!8VYkQCxD!fkhTrZwFFILDAglO1cR_8pIM4Cel52brZ7RB6QZoc6o
Once you downloaded all right driver open SP flash tool and add Scatter file
MT6572_Android_scatter.txt
Click on Download , connect your phone without battery and see if the process is going on if not try again with battery inside.
If you end up with error do the same thing but now first do Format then after is Finish do Download. Good luck ...
It still displays error :/
Teddy Lo said:
I have tried to do everything like you have said, but it still displays error when i press the Download button, and it displays that error after some seconds pass and also the same happens hen i try to use the Format function. This is the error it displays when i tried with the download button: BROM ERROR: S_DA_SDMMC_WRITE_FAILED (3149)
And this is the same error it displayed when i tried using the Format function: S_DA_SDMMC_WRITE_FAILED (3149)
i am so, so sorry for bothering with this.
Click to expand...
Click to collapse
Try with another version of SP Flash tool little bit newest .