My chinese phone Galaxy GT-N9000 clone Mtk6572 was brick, i try almost every tutorial and rom from many forum but still i can't bring my phone back to life ... please there anyone can help me? :crying: :crying: :crying: :crying:
Korean Clone Version Note 3
ijal7785 said:
My chinese phone Galaxy GT-N9000 clone Mtk6572 was brick, i try almost every tutorial and rom from many forum but still i can't bring my phone back to life ... please there anyone can help me? :crying: :crying: :crying: :crying:
Click to expand...
Click to collapse
- Mine is N9000 Note 3 Korean Clone Version MTK6572, and i'm wondering if theres a way to root it. i know there's a lot of android professionals here, and i hope we can find some answers.
- Version 4.3 jellybean
- Baseband Version: MTK6572 MAUI.11AMD.WW1150.SP. V23
- Kernel 2.6.35.7 [email protected] #4
- Software Version: JSS15J.N900ZSUBMI5
- Hardware Version: 1.1.0
Base on CPU Identifier:
- Spreadtrum SC6820a 1000 Mhz
- (fingerprint Brand for Fake Samsung Market)
- SMDK4X12
- Mali-300
Answer
ijal7785 said:
My chinese phone Galaxy GT-N9000 clone Mtk6572 was brick, i try almost every tutorial and rom from many forum but still i can't bring my phone back to life ... please there anyone can help me? :crying: :crying: :crying: :crying:
Click to expand...
Click to collapse
There is no support for chinese devices anywhere.
The tutorials are made only for the original device.
Did you back up the stock rom in the first place?
This problem would have been solved if you had a backup of your stock rom.
Now you have no other go than to contact the manufacturer for getting the phone fixed.
Trying other roms will not help you in restoring.
ijal7785 said:
My chinese phone Galaxy GT-N9000 clone Mtk6572 was brick, i try almost every tutorial and rom from many forum but still i can't bring my phone back to life ... please there anyone can help me? :crying: :crying: :crying: :crying:
Click to expand...
Click to collapse
try this >
- install ABD Drivers MTK65xx on your pc
- install SP Flash Tools
- download a custom ROM from needrom BUT only for your model N9000, other ROM will be useless
now extract the new ROM and let the window open after extraction
- open SP Flash Tools and load the scatter img file ( is in the extracted folder, navigate to that folder and load the scatter text img file )
- turn your phone off, wait until it vibrates to be sure is off
- press Download button on SP Flash Tools and after 1 sec connect your phone to PC
you'll the Flashing process Start, wait until is finish, it may take more than 10 min in some cases... you'll see a green circle after the process is done
- disconnect your phone and Power On, Voilaa
NovelCaidy said:
- Mine is N9000 Note 3 Korean Clone Version MTK6572, and i'm wondering if theres a way to root it. i know there's a lot of android professionals here, and i hope we can find some answers.
Click to expand...
Click to collapse
use Shuame or Framaroot, if u need help, i'm here...
Guys anybody got a rom for thje same phone...I have it too and its bricked..nothing is working
Ahh!!
Today I faced Same Problem With Same Model But Lots Of Effort Finally I Have Done .
My Working ROM : https://drive.google.com/uc?id=0B35LZs4cp74ZYlRYUnhpejUyZFE
Regards,
filip_pine said:
try this >
- install ABD Drivers MTK65xx on your pc
- install SP Flash Tools
- download a custom ROM from needrom BUT only for your model N9000, other ROM will be useless
now extract the new ROM and let the window open after extraction
- open SP Flash Tools and load the scatter img file ( is in the extracted folder, navigate to that folder and load the scatter text img file )
- turn your phone off, wait until it vibrates to be sure is off
- press Download button on SP Flash Tools and after 1 sec connect your phone to PC
you'll the Flashing process Start, wait until is finish, it may take more than 10 min in some cases... you'll see a green circle after the process is done
- disconnect your phone and Power On, Voilaa
use Shuame or Framaroot, if u need help, i'm here...
Click to expand...
Click to collapse
Hi, thanks for your help, but the phone is still bricked.
When i try to switch power on, nothing happen :crying:
If i push volume button, up or down i can see appear and disappear on device manager the ALCATEL SINGLE RNDIS SINGLE INTERFACE #5 but never MT65xx Preloader driver. :crying:
Seems to be not full dead but i don't know what else i can do.
If you have an advice for us with bricked phone...will be much appreciated.
Very thank you for any help kind. :crying:
D4N13L0N3 said:
Hi, thanks for your help, but the phone is still bricked.
When i try to switch power on, nothing happen :crying:
If i push volume button, up or down i can see appear and disappear on device manager the ALCATEL SINGLE RNDIS SINGLE INTERFACE #5 but never MT65xx Preloader driver. :crying:
Seems to be not full dead but i don't know what else i can do.
If you have an advice for us with bricked phone...will be much appreciated.
Very thank you for any help kind. :crying:
Click to expand...
Click to collapse
you need to install proper driver in order for the PC to recognize the phone, ussualy the Preloader USB VCOM Driver does the job, sometime it takes much more effort, and ADB Drivers need to be installed...
- Proper way to install Preloader USB VCOM Driver -
Connect your phone to PC and wait for the New hardware Found wizzard to appear
Choose i will install the driver by myself, then navigate to the folder location were you have the .ini driver file...
- If the method above dont work, then connect your phone to PC, wait for the New hardware found to appear...
Then right click on My PC and go to the Device Manager
Here you should have a yellow Mark and a phone name or something like this
Right click and choose update driver
Now choose the folder where you have extract the .ini driver file ....
Restart your PC
Open SP FlashTools and be sure that u have the proper ROM for your Phone, otherwise you´ll face DRAM FAIL Error
try this ROM that the guy posted above...
https://drive.google.com/uc?id=0B35LZs4cp74ZYlRYUnhpejUyZFE
filip_pine said:
you need to install proper driver in order for the PC to recognize the phone, ussualy the Preloader USB VCOM Driver does the job, sometime it takes much more effort, and ADB Drivers need to be installed...
- Proper way to install Preloader USB VCOM Driver -
Connect your phone to PC and wait for the New hardware Found wizzard to appear
Choose i will install the driver by myself, then navigate to the folder location were you have the .ini driver file...
- If the method above dont work, then connect your phone to PC, wait for the New hardware found to appear...
Then right click on My PC and go to the Device Manager
Here you should have a yellow Mark and a phone name or something like this
Right click and choose update driver
Now choose the folder where you have extract the .ini driver file ....
Restart your PC
Open SP FlashTools and be sure that u have the proper ROM for your Phone, otherwise you´ll face DRAM FAIL Error
try this ROM that the guy posted above...
Click to expand...
Click to collapse
Thanks, i tried your guide, but with that ROM finaly appear 100% in red color, probably because this phone have MTK6582 and not 6572.
If i use a rom for 6582 at the end of process i can see the DRAM FAIL error
I use this link from XDA for that ROMs:
androidxda.com/download-hdc-stock-rom-models
Any other advice ????
Thanks
D4N13L0N3 said:
Thanks, i tried your guide, but with that ROM finaly appear 100% in red color, probably because this phone have MTK6582 and not 6572.
If i use a rom for 6582 at the end of process i can see the DRAM FAIL error
I use this link from XDA for that ROMs:
androidxda.com/download-hdc-stock-rom-models
Any other advice ????
Thanks
Click to expand...
Click to collapse
ok, take your battery out and tell me the exact model...
filip_pine said:
ok, take your battery out and tell me the exact model...
Click to expand...
Click to collapse
Model: SM-N9000
SSN : N9000GSMH
Made in Korea by Samsung
filip_pine said:
ok, take your battery out and tell me the exact model...
Click to expand...
Click to collapse
This is model:
D4N13L0N3 said:
This is model:
Click to expand...
Click to collapse
try this ROM´s... maybe one of them will make your phone alive ...
http://www.needrom.com/mobile/11-hdc-n9000-note-3/
http://www.needrom.com/mobile/hdc-note-3-mt6582-sm-n9006/
http://www.needrom.com/mobile/hdc-galaxy-note-3-mtk6582-1gb-4gb-2014-kernel/
filip_pine said:
try this ROM´s... maybe one of them will make your phone alive ...
Click to expand...
Click to collapse
Thanks.
I will try, then i tell you if i can use like a paper block
filip_pine said:
try this ROM´s... maybe one of them will make your phone alive ...
Click to expand...
Click to collapse
Nothing, or i mistake all and fail, or i miss some important step.
In attached the errors :
D4N13L0N3 said:
Nothing, or i mistake all and fail, or i miss some important step.
In attached the errors :
Click to expand...
Click to collapse
did u get this error on all the 3 ROM´s ? (((
is there any chance that u can contact your seller from where did you bought the phone ? ask him for the Original ROM...
filip_pine said:
did u get this error on all the 3 ROM´s ? (((
is there any chance that u can contact your seller from where did you bought the phone ? ask him for the Original ROM...
Click to expand...
Click to collapse
No, not all, but everyone go on 100% with red line and not green circle.
I don't understand what error i made.
I think one thing, but the AGENT is right MTK_AllOne_DA.bin or i need to use the one in FIRMWARE folder ??
The files are :
lk.bin
logo.bin
preloader_lcsh82_wet_jb5.bin
What do you thing about it ???
Hi Filip,
i tried to delete USB drivers with USB Deview, after that, i re-charge a new one driver of device and then charge the ROM, this is the result :
The second image appear after about 15 minutes of time out.
D4N13L0N3 said:
Hi Filip,
i tried to delete USB drivers with USB Deview, after that, i re-charge a new one driver of device and then charge the ROM, this is the result :
The second image appear after about 15 minutes of time out.
Click to expand...
Click to collapse
ok, it seems that the problems are not the driver, sience you manage to get the phone recognized by pc... the problem seems to be SP Flash Tool...
my advice would be : reinstall again the windows, install again the USB Preloader VCOM Driver ( the correct way ) and install latest version of SP Flash Tool....
Then try to install again one of the 3 ROM´s that i give you... maybe you have luck buddy, i dont know...
is the only way you could get back your phone.... as you know, these phones are clones and is very hard to find compatible ROM´s and replacements parts....
I was having the ghost touches on my SM-N900 Note 3 Clone and the only solution was to change the digitizer, but : i can´t change it, sience i dont find anywhere Note 3 Clone digitizer replacements... only solution was to put the phone in a box and dont use it... ((
filip_pine said:
my advice would be : reinstall again the windows, install again the USB Preloader VCOM Driver ( the correct way ) and install latest version of SP Flash Tool....
Click to expand...
Click to collapse
I tried on my laptop with new OS installed and no antivirus installed, but the problem is the same.
I tried this tools : SP_Flash_Tool_v5.1352.01
and this : SP Flash Tool v3.1332.0.187
and the tools inside the ROM folder, but nothing. :crying:
Could you link me please the USB Preloader VCOM Driver ( for win7 64bit ), i guess the problem is that i used the bad one
Very thank you again for your help. :good:
Related
Hi
I have MobileUncle Tooll (granted SuperUser) and ROM Manager (granted SuperUser) installed on my Goophone I5 MTK6577 BUT I still CANNOT bypass Android Recovery 3E to install the goo.zip ROM - how do you bypass the 3E please???
ANYONE?
goophone v88 i5 from dhgate seller name shenzhen
Hey my phone is goophone i5 v88 i5 I brought from dhgate seller nane is shenzhen iam also trying to bypass cwm recovery but no sucess when flashing thrpugh mut and the reebooting to recovery blank display I think the processor is mt6577 dual core ram is 512 mb and screen resolution is 480*854 but with a yweaked stock kernel the system show fake hardware like 2gb ram higher screen resolution and so more but the phone rxactly looks and feels like iphpne 5 and about the software running on this phone I thing it is tje bugg free and coolest full ios6 themed rom
cj27282 said:
Hi
I have MobileUncle Tooll (granted SuperUser) and ROM Manager (granted SuperUser) installed on my Goophone I5 MTK6577 BUT I still CANNOT bypass Android Recovery 3E to install the goo.zip ROM - how do you bypass the 3E please???
Click to expand...
Click to collapse
Same here....unable to enter recovery mode after flashing CWM ...phone works but it "skips'" the recoverymode...factory mode works but yee...some solution for this would be nice......atleast i can still use the phone...altho with the stock rom witch is crap cause i cant back it up for flashing the phone...
cj27282 said:
Hi
I have MobileUncle Tooll (granted SuperUser) and ROM Manager (granted SuperUser) installed on my Goophone I5 MTK6577 BUT I still CANNOT bypass Android Recovery 3E to install the goo.zip ROM - how do you bypass the 3E please???
Click to expand...
Click to collapse
Any progress?
cj27282 said:
Hi
I have MobileUncle Tooll (granted SuperUser) and ROM Manager (granted SuperUser) installed on my Goophone I5 MTK6577 BUT I still CANNOT bypass Android Recovery 3E to install the goo.zip ROM - how do you bypass the 3E please???
Click to expand...
Click to collapse
Ok so problem solved.... unfortunately it will delete everything on your phone....i simply flashed the phone using SP-Flashtool and a rom from here => http://pan.baidu.com/share/link?shareid=324294&uk=540296524#dir/path=/Rom/Goophone I5 Rom supplyed by Zap ...
its the version v18 ... theres a v22 also you can download from http://pan.baidu.com/share/link?shareid=412131&uk=3022339290 but i havent tryed it yet so i dont know how well it works....
can you see what version your stock rom is? ... i think mine was 27 but im not 100% and i have been looking for a later version stock rom but i havent found any yet.....so yee.... the rom i installed now semes to be pretty much the same although it gave me lower antutu scores than the first one i had...dunno how mush that has to do with the software.... but userwise i havent noticed any major differance more than the charging animation thats different when the phone is switched of..and yes the system recovery 3e is in english
now ofcourse these roms are for the Fastcardtech Goophone I5 N2 micro simcard!!!
all is done at your own risk!!
also you HAVE TO INSTALL the mtk6577 VCOM driver in order to be able to use the sp.flastool correctly.....anything else might **** up your phone.... theres a good tutorial here http://forum.xda-developers.com/showthread.php?t=2206421
good luck and please post what stock version you have running now!! and if the phone is running fine otherwise maybe you want to reconsider flashing it since the versions i posted for download are v18 and v22....would love to get my hands on the newest stock rom...(did try to just flash the recovery image from the v18 but it bricked my phone)
jinishpv said:
Hey my phone is goophone i5 v88 i5 I brought from dhgate seller nane is shenzhen iam also trying to bypass cwm recovery but no sucess when flashing thrpugh mut and the reebooting to recovery blank display I think the processor is mt6577 dual core ram is 512 mb and screen resolution is 480*854 but with a yweaked stock kernel the system show fake hardware like 2gb ram higher screen resolution and so more but the phone rxactly looks and feels like iphpne 5 and about the software running on this phone I thing it is tje bugg free and coolest full ios6 themed rom
Click to expand...
Click to collapse
Hello,
About that phone, i buyed that phone, from the same seller, yesterday.
It is fake?Its not the actual goophone i5s that we see on their website?
Thanks!
i have the goophone i5 mt6577 with bee on the back cover
i can have the original recovery image recovery E3?
i wanto to turn back to original factory rom but my older backup don't recognize from colonelzap's cmw recovery
thank you
luponero76 said:
i have the goophone i5 mt6577 with bee on the back cover
i can have the original recovery image recovery E3?
i wanto to turn back to original factory rom but my older backup don't recognize from colonelzap's cmw recovery
thank you
Click to expand...
Click to collapse
did you flash the colonelzap recovery with flashtool??
if your colonelzap cwm works then you should back up your rom with cwm...
(I have not tryed it my self but i think it should work)
download this rom
http://pan.baidu.com/share/link?shareid=412128&uk=3022339290
uncompress and youl find a file called RECOVERY.IMG.....
now open your flashtool (i use sp-flashtool) and load the scatterfile "MT6577_Android_scatter_emmc.txt"
the flash tool is gonna show you a list with all the files that where in the zip..
uncheck all of them so the only one that is checkes is the RECOVERY.IMG ....and then you flash and TADA.....you should have your old S3 recovery back
if it all goes to **** you can just flash the complete rom and it will work.. .....atleast if you have the gooptone i5 n2/lte mtk6577
dont use mobile uncle for these files...that screwed up my phone....they need to be flashed to the phone!!
AND... this is the international v18 rom... dont know what version you have right now....but if you manage to make a back up rom of your phone PLEASE SHARE!!! .... ive been looking for the later international rom....and if you have the backup you can allways upgrade from the v18....so
GOOD LUCK!! ...keep us posted! ...and if you need more flashingdeetales you can just google or ask
CWM Goophone i5 N2 black screen
Hi , I have similar issue like this ...
I have Goophone i5 N2 from aliexpres.com
It's come with original ROM and with Root, unfortunately it has lot of bugs . So I would like to install custom ROM from Colonelzap.blogspot
I spent more then 2 days with trying to flash Clock work recovery mode . So I'll be able to flash new ROM. But there I'm stuck
I red several tutorial for instalation , I did go trough threads here on forum , etc but still without any success .
1, I tried to use MobileUncle MTK for set recovery image with image from colonel zap blog
2, I tried to use (maybe 10 different version of) SP Flash Tool and still got 2 issue (4050 or 8038) during flashing
I used recovery image from Greg's Mobile gadgets
And result is still same , When I try to load to recovery mode , I still got black screen only .. And I have to restart mobile again , then it start up normally ...
I'm starting to be little bit desperate
I'll really appreciate any help or advice
PS: because forum rules , I can't add any links to sources which I used .. But I'll response very fast for any questions. Thanks
Dude!! u gotta make sure u have the MTK Vcom drivers installed on your computer......when u got that its easy peasy..... make sure your phone us turbned of and DISSCONNECTED from the coputer... now in SPflashtool you load the rom that u wanna flash and you press the transfer button....when thats done the computer is gonna start looking for the phone.....this is the moment you connect your phone to the computer....otherwise it wont work...windows will start looking for som other crap driver to use with your phone.......
if u wanna get ur phone to work well you should go to the talkingmobi blog and download the stock rom and flash that one....then when thats done flash the CMW and throu that u put in the manuxo rom!!......thats more or less what ive done...altho i made my own rom...but its more or less the same as manuxos just with less chinese crap...but that u can do your self when u got the phone set up...easyest way i think is with "root app remover" that u can get for free from the app store...or "Playstore" to be precise... good luck!!
ja.viper said:
Hi , I have similar issue like this ...
I have Goophone i5 N2 from aliexpres.com
It's come with original ROM and with Root, unfortunately it has lot of bugs . So I would like to install custom ROM from Colonelzap.blogspot
I spent more then 2 days with trying to flash Clock work recovery mode . So I'll be able to flash new ROM. But there I'm stuck
I red several tutorial for instalation , I did go trough threads here on forum , etc but still without any success .
1, I tried to use MobileUncle MTK for set recovery image with image from colonel zap blog
2, I tried to use (maybe 10 different version of) SP Flash Tool and still got 2 issue (4050 or 8038) during flashing
I used recovery image from Greg's Mobile gadgets
And result is still same , When I try to load to recovery mode , I still got black screen only .. And I have to restart mobile again , then it start up normally ...
I'm starting to be little bit desperate
I'll really appreciate any help or advice
PS: because forum rules , I can't add any links to sources which I used .. But I'll response very fast for any questions. Thanks
Click to expand...
Click to collapse
virre62 said:
Dude!! u gotta make sure u have the MTK Vcom drivers installed on your computer......when u got that its easy peasy..... make sure your phone us turbned of and DISSCONNECTED from the coputer... now in SPflashtool you load the rom that u wanna flash and you press the transfer button....when thats done the computer is gonna start looking for the phone.....this is the moment you connect your phone to the computer....otherwise it wont work...windows will start looking for som other crap driver to use with your phone.......
if u wanna get ur phone to work well you should go to the talkingmobi blog and download the stock rom and flash that one....then when thats done flash the CMW and throu that u put in the manuxo rom!!......thats more or less what ive done...altho i made my own rom...but its more or less the same as manuxos just with less chinese crap...but that u can do your self when u got the phone set up...easyest way i think is with "root app remover" that u can get for free from the app store...or "Playstore" to be precise... good luck!!
Click to expand...
Click to collapse
Hi ,
I did this , several times . I installed correct Vcom driver, and update to last version . And I did follow steps for SP Flash tools. And i can see for aprox 2 sec , load driver for Vcom for Mediatek and So I think , that this part I made correctly.
When I tried load scattle file in to SP flash tool , and then run download and after that I connect switch off phone via cable .
SP FT find mobile via Vcom , and start upload and I see red progress bar on 100 and then after couple seconds I got error message :
1 , sometimes : BROM ERROR: S_FT_NEED_DOWNLOAD_ALL_FAIL (4050) ...
2, or : SP Flash Tool error 8038
ohh yee... ive had that aswell when i flashed the ladies n9589.....thats either due to a bad rom...maybe some error when you downloaded it OR ande most probably an incompatible version of SPFlashtool.... sometimes you have to try diffrent versions to get it to work on your specific phone... if u got the goophone i5 n2/LTE then you should try "SP_Flash_Tool_v3.1224.01"...
Thats the one i use for flashing my goophone and it works just fine.....and when you flash the CWM you should first boot up the phone with the latest rom you flashed b4 cause if you flash on an unbooted rom it wil most probably brick your phone so u gotta do the complete romflash from scratch....remember most costum roms are basically like "CWMbackups" that people do on their modifyed roms and spread....so with spflashtool you allways need to start with a propper rom with scatterfile....but ye....try running annother version of spflashtool... like the one i wrote in top...works for me ...and u can find it on goolgle
ja.viper said:
Hi ,
I did this , several times . I installed correct Vcom driver, and update to last version . And I did follow steps for SP Flash tools. And i can see for aprox 2 sec , load driver for Vcom for Mediatek and So I think , that this part I made correctly.
When I tried load scattle file in to SP flash tool , and then run download and after that I connect switch off phone via cable .
SP FT find mobile via Vcom , and start upload and I see red progress bar on 100 and then after couple seconds I got error message :
1 , sometimes : BROM ERROR: S_FT_NEED_DOWNLOAD_ALL_FAIL (4050) ...
2, or : SP Flash Tool error 8038
Click to expand...
Click to collapse
virre62 said:
ohh yee... ive had that aswell when i flashed the ladies n9589.....thats either due to a bad rom...maybe some error when you downloaded it OR ande most probably an incompatible version of SPFlashtool.... sometimes you have to try diffrent versions to get it to work on your specific phone... if u got the goophone i5 n2/LTE then you should try "SP_Flash_Tool_v3.1224.01"...
Thats the one i use for flashing my goophone and it works just fine.....and when you flash the CWM you should first boot up the phone with the latest rom you flashed b4 cause if you flash on an unbooted rom it wil most probably brick your phone so u gotta do the complete romflash from scratch....remember most costum roms are basically like "CWMbackups" that people do on their modifyed roms and spread....so with spflashtool you allways need to start with a propper rom with scatterfile....but ye....try running annother version of spflashtool... like the one i wrote in top...works for me ...and u can find it on goolgle
Click to expand...
Click to collapse
I used your suggested version of SP_Flash_Tool_v3.1224.01 and I used 2 different recovery.img , but in both tries i got same error as you can see on image
So i tried to upload new rom .
And it's look like a made a brick from this ... Now it doesn't respond at all ... SP flash tool doesn't recognize mobile at all
I can't connect now to the SP flash tool , it's just dont recognize phone , I can see only in device manager , which see 2 cards
and when I connect phone I can see for a moment USB Vcom port driver in list and for 1 second I can see that it write
Code:
Device is work properly
and then is change to image
Code:
Currently, this hardware device is not connected to the computer. (Code 45)
To fix this problem, reconnect this hardware device to the computer.
Do you have the ADB drivers installed on your computer? .... might be there where your problem is.....or annother conflicting driver on your computer....google the forums for ADB driver MTK Vcom driver install.... as i get it the computer wont know how to talk linux without the ADB pack.......i think its included in some vcom driver packs but i do believe i had to install that separatly the first time.....check that out...cause it should work.....if now try it with annother computer...could be some crap driver on your computer messing it up...i had an emulator at one point messing my spflashtool up....
ja.viper said:
So i tried to upload new rom .
And it's look like a made a brick from this ... Now it doesn't respond at all ... SP flash tool doesn't recognize mobile at all
I can't connect now to the SP flash tool , it's just dont recognize phone , I can see only in device manager , which see 2 cards
and when I connect phone I can see for a moment USB Vcom port driver in list and for 1 second I can see that it write
Code:
Device is work properly
and then is change to image
Code:
Currently, this hardware device is not connected to the computer. (Code 45)
To fix this problem, reconnect this hardware device to the computer.
Click to expand...
Click to collapse
stock ROM goophone-i5-0428-f-yzs.zip
virre62 said:
Do you have the ADB drivers installed on your computer? .... might be there where your problem is.....or annother conflicting driver on your computer....google the forums for ADB driver MTK Vcom driver install.... as i get it the computer wont know how to talk linux without the ADB pack.......i think its included in some vcom driver packs but i do believe i had to install that separatly the first time.....check that out...cause it should work.....if now try it with annother computer...could be some crap driver on your computer messing it up...i had an emulator at one point messing my spflashtool up....
Click to expand...
Click to collapse
So , I don't think so that problem is the driver, because SP flash tool works fine when I try to update firmware , it's finish all task , but then the mobile doesn't start . I think that I don't have correct ROM . I tried 3 different ROM and mobile still not start up . Still just blink screen and that's all . And then I have to some how switch off . Then I'm able to do update again trough SP flash Tool , but I need correct one ROM.
I tried to find stock ROM Goophone-i5-0428-f-yzs.zip , but I found it only on some crazy Chinese site 400GB.com (file/19858713) and I was unable to download it .:silly:
are you sure its a goophone you have?
Also..... your phone NEEDS to be charged with ATLEAST 60% or it will fail....flashing really drains the battery and ive had flashings fail just cause of low battery......but yee.... if its not a real goophone it wont work either way.... or if its annother model....you need to have the correct rom for the right phone or it will fail 99,5% of the times..
dont think i can do much more for u.....running out of ideas......it should work with that assuming your hardware is good.
ja.viper said:
So , I don't think so that problem is the driver, because SP flash tool works fine when I try to update firmware , it's finish all task , but then the mobile doesn't start . I think that I don't have correct ROM . I tried 3 different ROM and mobile still not start up . Still just blink screen and that's all . And then I have to some how switch off . Then I'm able to do update again trough SP flash Tool , but I need correct one ROM.
I tried to find stock ROM Goophone-i5-0428-f-yzs.zip , but I found it only on some crazy Chinese site 400GB.com (file/19858713) and I was unable to download it .:silly:
Click to expand...
Click to collapse
stock ROM goophone-i5-0428-f-yzs.zip
virre62 said:
are you sure its a goophone you have?
Also..... your phone NEEDS to be charged with ATLEAST 60% or it will fail....flashing really drains the battery and ive had flashings fail just cause of low battery......but yee.... if its not a real goophone it wont work either way.... or if its annother model....you need to have the correct rom for the right phone or it will fail 99,5% of the times..
dont think i can do much more for u.....running out of ideas......it should work with that assuming your hardware is good.
Click to expand...
Click to collapse
I saw some fake goophone on net , but it was with dual core CPU MTK 6587 etc ...
When I download SU and some other app like CPU Z ,etc I checked and I didn't see any suspicions information . So I hope that it is real Goophone i5 N2 ...
When I finished update firmware I saw in SP Flash tool that it's show some device info , so I'll add tomorrow another screen from this app.And try to verify if it's original goophone i5 N2 .
But this info about at least 60% of batter is important! Because it was charged about 50 % when I run update!
But process of flashing finished without any errors and in the end I saw Green circle , SO I was thinking that It's was finished successfully .....
Important question is . What should be done after updating new Firmware ?
I just tried to Start up the mobile .Should I do anything else ?
well if you get the green circle then its most probably that your out of battery......leave the phone charging for some hours... flash it and when your doen unplug it from the computer and just start it and wait cause the first boot up usually takes time,.....maybe up to 2-10 min depending on what rom u flashed......if you dont have enough battery to complete first boot you might run in to problems.....and if you wanna test your hardware you press the volume + and power and you get in to the factory hardware test menu just if u wanna make sure that ur phone is ok
ja.viper said:
I saw some fake goophone on net , but it was with dual core CPU MTK 6587 etc ...
When I download SU and some other app like CPU Z ,etc I checked and I didn't see any suspicions information . So I hope that it is real Goophone i5 N2 ...
When I finished update firmware I saw in SP Flash tool that it's show some device info , so I'll add tomorrow another screen from this app.And try to verify if it's original goophone i5 N2 .
But this info about at least 60% of batter is important! Because it was charged about 50 % when I run update!
But process of flashing finished without any errors and in the end I saw Green circle , SO I was thinking that It's was finished successfully .....
Important question is . What should be done after updating new Firmware ?
I just tried to Start up the mobile .Should I do anything else ?
Click to expand...
Click to collapse
I have just received my Iocean X7 Elite and was about to install a new rom. I had successfully rooted the device and then was trying to flash
the recovery with SP Flash Tool.
After the recovery flashed my phone refuses to turn on I believe its somehow bricked but have no idea how this could have happened. I did
format flash i only downloaded the recovery to the device.
In Device Manager when i plug the phone it it either shows up as 'DA USB VCOM Port' or 'MTK USB Port'.
When I try to use SP Tool to flash the stock Rom back onto the device I get an error saying 'BROM ERROR : S_FT_ENABLE_DRAM_FAIL(4032)'
I have no idea what to do next can someone help me.
I have tried what this thread suggests:
bump
same as u..but differ phone model.(N9589)
had a few upgrd...til the recent brick it.
Tried a few version of flash tool and still the same
Joshafc said:
I have just received my Iocean X7 Elite and was about to install a new rom. I had successfully rooted the device and then was trying to flash
the recovery with SP Flash Tool.
After the recovery flashed my phone refuses to turn on I believe its somehow bricked but have no idea how this could have happened. I did
format flash i only downloaded the recovery to the device.
In Device Manager when i plug the phone it it either shows up as 'DA USB VCOM Port' or 'MTK USB Port'.
When I try to use SP Tool to flash the stock Rom back onto the device I get an error saying 'BROM ERROR : S_FT_ENABLE_DRAM_FAIL(4032)'
I have no idea what to do next can someone help me.
I have tried what this thread suggests:
Click to expand...
Click to collapse
Same problem here - tried to install stock firmware and got this error...
these are common problems when flashing MT65xx based phones,
ie : error 4008, 4xxx, 5xxx whatever those codes mean, no explanation after extensive search on google.
once I managed to flash this one phone successfully, but I don't know exactly what I did.
as long as I recall, I tried to delete the whole flashtool folders, re-extract them, let the phone cool down a bit
and oh, try to press volume up, or down button (varies on devices) while connecting to USB, once the flashing progress bar starts, release the button.
In the flashtool option, at the OPTIONS-->DA DOWNLOAD ALL-->, check WITHOUT BATTERY.
and in the option, DA DOWNLOAD ALL--> SPEED, check DO NOT SWITCH SPEED.
try flashing your phone without battery inserted, it works many times for me.
NOTE : BEWARE, flashing your MTK65xx based phone, sometimes this tool tried to REMOVE YOUR PHONE's IMEI information, so take caution !
I haven't managed how to prevent IMEI removal when flashing those phones, because I'm not a developer.
Hope this helps.
tukulll said:
these are common problems when flashing MT65xx based phones,
ie : error 4008, 4xxx, 5xxx whatever those codes mean, no explanation after extensive search on google.
once I managed to flash this one phone successfully, but I don't know exactly what I did.
as long as I recall, I tried to delete the whole flashtool folders, re-extract them, let the phone cool down a bit
and oh, try to press volume up, or down button (varies on devices) while connecting to USB, once the flashing progress bar starts, release the button.
In the flashtool option, at the OPTIONS-->DA DOWNLOAD ALL-->, check WITHOUT BATTERY.
and in the option, DA DOWNLOAD ALL--> SPEED, check DO NOT SWITCH SPEED.
try flashing your phone without battery inserted, it works many times for me.
NOTE : BEWARE, flashing your MTK65xx based phone, sometimes this tool tried to REMOVE YOUR PHONE's IMEI information, so take caution !
I haven't managed how to prevent IMEI removal when flashing those phones, because I'm not a developer.
Hope this helps.
Click to expand...
Click to collapse
Thank you for your reply, but this doesn't help... ;(
Anyone?
I think I figured out that the error above means you are trying to flash an incorrect ROM. Make sure you are using the right one and also make sure you're using the latest version of sp flash tool.
Once I downloaded a later version of the flash tool it began installing the ROM but then a different error appeared.
So I formatted the nand with the sp flash tool.
Then I flashed the stock ROM again and it worked
Formatting it seemed to make the errors go away even though its advised not to do so.
Sent from my iOCEAN X7 using xda app-developers app
vessk0 said:
Anyone?
Click to expand...
Click to collapse
I fixed this error by completely removing and reinstalling other drivers for mtk vcom loader
anyone heard Iocean will recall all of the x7 elite's? i've had a mail today they should do it, but i don't know if it's true or not.
Schumi_wk said:
anyone heard Iocean will recall all of the x7 elite's? i've had a mail today they should do it, but i don't know if it's true or not.
Click to expand...
Click to collapse
I haven't heard about that. Maybe its a fake email. Did it say what the fault was?
Joshafc said:
I think I figured out that the error above means you are trying to flash an incorrect ROM. Make sure you are using the right one and also make sure you're using the latest version of sp flash tool.
Once I downloaded a later version of the flash tool it began installing the ROM but then a different error appeared.
So I formatted the nand with the sp flash tool.
Then I flashed the stock ROM again and it worked
Formatting it seemed to make the errors go away even though its advised not to do so.
Sent from my iOCEAN X7 using xda app-developers app
Click to expand...
Click to collapse
How to format the nand with sp flash tool, I use the latest version?
And can you point me to good original stock ROM?
Thank you!
lolet said:
I fixed this error by completely removing and reinstalling other drivers for mtk vcom loader
Click to expand...
Click to collapse
I tried reinstalling drivers, also tried other drivers, but this doesn't help...
I've had the same problem with the following installation Sp Tools
SP_Flash_Tool_exe_v3.1316.0.150
Rom: MP_mt89_v9_iocean_ousheng_jb2_20130520-184014_zhongyeqing_PC
http://d-h.st/ESX
Iocean X7 Youth
I don't have the same problem but i flashed the latest version of official rom for iOcean x7 Youth : 03 july 2013 : and wtf no more internal sdcard only the rom stockage. So i can't download anything, i can't use camera .
On the official website, I read that before flashing the 20 may 2013 rom one and the 03 July 2013 one, your baseband version have to be 23/04 or higher( you have to flash the 23/04 official rom first). This is only avalaible for the YOUTH version.
So tomorrow i will try what i said below to see if i have internal sd card again.
noob question::: since the iocean x7 young and turbo are the same phones...only different clock rates...will flashing the firmware for turbo on iocean x7 young work??assuming that the mtk6589T and mtk6589 are the same chipset only different clock rates??
Micromax A116 (Cant flash Rom)Brick Problem Solved
tukulll said:
these are common problems when flashing MT65xx based phones,
ie : error 4008, 4xxx, 5xxx whatever those codes mean, no explanation after extensive search on google.
once I managed to flash this one phone successfully, but I don't know exactly what I did.
as long as I recall, I tried to delete the whole flashtool folders, re-extract them, let the phone cool down a bit
and oh, try to press volume up, or down button (varies on devices) while connecting to USB, once the flashing progress bar starts, release the button.
In the flashtool option, at the OPTIONS-->DA DOWNLOAD ALL-->, check WITHOUT BATTERY.
and in the option, DA DOWNLOAD ALL--> SPEED, check DO NOT SWITCH SPEED.
try flashing your phone without battery inserted, it works many times for me.
NOTE : BEWARE, flashing your MTK65xx based phone, sometimes this tool tried to REMOVE YOUR PHONE's IMEI information, so take caution !
I haven't managed how to prevent IMEI removal when flashing those phones, because I'm not a developer.
Hope this helps.
Click to expand...
Click to collapse
Thanks a lot. My Micromax a116 was brick. Now its alive.
Here I am with the same problem in a N920e... AND IT'S NOT MINE! :crying:
I'll have to pay it to the owner if I can't solve this:
DaniPhii said:
Here I am with the same problem in a N920e... AND IT'S NOT MINE! :crying:
I'll have to pay it to the owner if I can't solve this:
View attachment 2243401
Click to expand...
Click to collapse
Clearly: Wrong driver. I had also this error. SPflash tool did not readback. I did not flash anything! I fixed this by showing the nonpresent devices in devicemanagement (google for show nonpresent devices for explanation)
Go to com ports, and delete all mediatek drivers except preloader driver. Now start over. It can help if you choose the same usb port where you had success last time.
SP flash tool shows in the statusbar which driver it is using.
mistraller said:
Clearly: Wrong driver. I had also this error. SPflash tool did not readback. I did not flash anything! I fixed this by showing the nonpresent devices in devicemanagement (google for show nonpresent devices for explanation)
Go to com ports, and delete all mediatek drivers except preloader driver. Now start over. It can help if you choose the same usb port where you had success last time.
Click to expand...
Click to collapse
Yes, you got it
SP Flash Tool couldn't find my phone, but now it works
It's exactly a windoze driver problem.
Going to devicemanagement, in LAN-Devices I a had an Alcatel device,
chosing driver by hand and use the mtk usb driver, now Flashtool finds the phone
Thanks a lotttttttt....
shiv.kbh said:
Thanks a lot. My Micromax a116 was brick. Now its alive.
Click to expand...
Click to collapse
Thanks a lot man i unbricked my bolt a58 with this...thanks thanks...
Hello guys I got a x920 and was working good until it started doing something similar like Samsung Galaxy S3 Sudden Death.
The phone would randomly get a screen freeze, and the half bottom of the screen got distorted like green and pink lines, then slowly, the pixels were turning to black until the whole screen gets black, but the backlight would remain on.
I had to pull the battery out, and sometimes the phone would work again instantly, some other times, it wouldn't turn on, only after some time, and after a lot of battery pulls.
But last time I got this sudden death, the phone never came back.
I had the stock rom and only root.
My model version is: e2001v21_v89_zlh_hd
Most people with this phone have the e2001_v89_zlh_hd, and most roms on needrom.com are for e2001_v89_zlh_hd, there are a lot of roms for e2001v21_v89_zlh_hd though but I tried everything and I got DRAM Failed.
I use windows 8
SP flash tool v3.1304.0.119, v3.1308.0.125, v3.1316.0.150
And several other roms for both versions.
There is a solution from a French guy about the DRAM failed problem here, but I got the S5 rom downloaded as he stated, and can't get pass the first red bar on SP flash tool.
Do you have any idea what is going on with the 2 versions of the phone? People say that they read on chinese forum that v2.1 (e2001v21_v89_zlh_hd) has got different EMMC. So I guess roms from the e2001_v89_zlh_hd wont work.
I would like to know if you guys have any working rom for my e2001v21_v89_zlh_hd because I really need the phone at the moment. I must get it back to life.
ps (Is windows 8 suitable for flashing? I have installed mtk drviers normally through a weird process enabling manual driver installation through the advanced startup thingy on Windows 8, otherwise it wouldn't let me install the drivers.)
Voliminal_8 said:
Hello guys I got a x920 and was working good until it started doing something similar like Samsung Galaxy S3 Sudden Death.
ps (Is windows 8 suitable for flashing? I have installed mtk drviers normally through a weird process enabling manual driver installation through the advanced startup thingy on Windows 8, otherwise it wouldn't let me install the drivers.)
Click to expand...
Click to collapse
ok, there is no difference for using window 8 , xp, win 7, as long as u have installed the driver correctly.
as u said u can see the red bar, that mean yr driver was installed correctly.
all u need is the right preloader.bin
as i can understand from my past experiance, i think that the later batch of the phone, the manufacturer might use different DRAM or they might have changed the coding of the ram. that is why we see quite often there is complaint of DRAM fail when u try to flash the official rom for the phone. Not for newer model of the phone ( yr phone has two/three batches).
so may be u could ask the http://www.needrom.com/mobile/star-tengda-x920/ - smartdigi to create a preloader.bin from their phone for u , then u replace the preloader.bin in yr rom and flash it.
smartdigi is a team from Greece, and so am I, so yes, I just sent a message.
I hope I'll find a solution.
Voliminal_8 said:
smartdigi is a team from Greece, and so am I, so yes, I just sent a message.
I hope I'll find a solution.
Click to expand...
Click to collapse
i had read tru the needrom wed regarding thier rom, i saw there is a instruction to pass tru the "DRAM fail."
had u tried that before.
they also had rom that match with yr version.
Yes, I downloaded the rom, and still got DRAM failed.
Is there any way to install smartdigi rom through sp flash tool and not sd card?
here's the link http://www.needrom.com/mobile/star-tengda-x920
Yes, I downloaded the rom, and still got DRAM failed.
Is there any way to install smartdigi rom through sp flash tool and not sd card?
here's the link http://www.needrom.com/mobile/star-tengda-x920
Voliminal_8 said:
Yes, I downloaded the rom, and still got DRAM failed.
Is there any way to install smartdigi rom through sp flash tool and not sd card?
here's the link http://www.needrom.com/mobile/star-tengda-x920
Click to expand...
Click to collapse
ok, i just want to know if the procedure as they decribe will work, as i cannot test it, as i don.'t have the phone.
did u manage to get the preloder from them.
if u get the preloader from smartdigi , u stilll get the "DRAM fail" , then i think , may be their phone is an older batch,
for me, if u can read back from from the SP flash tool, (version 3.1316, (i justy learn that there is v3.1328 available)), then definitely u can flash yr phone with this preloader.bin
note
since u can't even go to recovery, then there is no way u can flash the rom with card flash rom from smartdigi, the only way to recover yr phone is tru cable flash rom that mean, u have to pass tru the "DRAM fail"
Well, I found the problem, the drivers installed are MTK USB Port, and not Preloader VCOM drivers.
I use windows 8 x64, I restarted with bypassing the signature thing.
The problem is, when I try to manually select the vcom driver, after the installation it shows up as MTK USB Port, and not as a vcom port.
Any solution?
Voliminal_8 said:
Well, I found the problem, the drivers installed are MTK USB Port, and not Preloader VCOM drivers.
I use windows 8 x64, I restarted with bypassing the signature thing.
The problem is, when I try to manually select the vcom driver, after the installation it shows up as MTK USB Port, and not as a vcom port.
Any solution?
Click to expand...
Click to collapse
no, it does not matter if it is preloader port or vcom port, actually they don,t make difference if u flash the rom.
that mean yr computer is talking to the phone correctly.
now the most important part is the "preloader.bin" file in yr rom must match the dram in yr phone.
that is why u hve to ask who has yr exactly same model of yr phone to create a preloader.bin.
or just try to download the preloader.bin as many as u can.
if u have a friend who has the phone same as as yours, then i can help to create from his phone, or u can create the preloader.bin from his phone
edit,
try to download the latest sp flas tool v3.1324 or v3.1328 ,flash the rom with it.
I tried several roms, with different preloader.bin files, non seems to work.
I tried with all sp flash tool versions, all 3.13904.0.119, 3.1308.0.125, 3.1316.0.150, 3.1328.0.183
Some versions of SP, are not showing up all the files gathered from the scatter file. Some other do.
Well, a smartdigi member, told me to use windows 7, because the mediatek drivers have gone as fas as windows 7 x64.
Voliminal_8 said:
I tried several roms, with different preloader.bin files, non seems to work.
I tried with all sp flash tool versions, all 3.13904.0.119, 3.1308.0.125, 3.1316.0.150, 3.1328.0.183
Some versions of SP, are not showing up all the files gathered from the scatter file. Some other do.
Well, a smartdigi member, told me to use windows 7, because the mediatek drivers have gone as fas as windows 7 x64.
Click to expand...
Click to collapse
ya, u could try with win7.
for me i can flash with win8 also.
i use win 7 at home, win8 at office, no problem.
u could try with win7, i think most likely , u will get the same result.
i had brick my s7589, i unbrick it with the right preloader. after that i tried with the preloader.bin that was originally came with the rom.
this time , it can pass tru the "dram fail", get the purple color, then yellow, then finish with green color. then i try to swith on the phone, but, no response from the phoe. it was bricked again.
then i flash back with the right preloader.bin, the phone back to life again.
did u manage to get preloader.bin from smartdigi?
for me, it is the best solution to unbrick the phone. may be there is some other ways that i don't know
stevenma61 said:
ya, u could try with win7.
for me i can flash with win8 also.
i use win 7 at home, win8 at office, no problem.
u could try with win7, i think most likely , u will get the same result.
i had brick my s7589, i unbrick it with the right preloader. after that i tried with the preloader.bin that was originally came with the rom.
this time , it can pass tru the "dram fail", get the purple color, then yellow, then finish with green color. then i try to swith on the phone, but, no response from the phoe. it was bricked again.
then i flash back with the right preloader.bin, the phone back to life again.
did u manage to get preloader.bin from smartdigi?
for me, it is the best solution to unbrick the phone. may be there is some other ways that i don't know
Click to expand...
Click to collapse
Well... installed windows 7 in another partition.
It was like I never did it, exactly the same result. Everything behaved the same.
I don't know... maybe I have crappy mtk drivers, or I'm doing something wrong while installing them.
Let me describe the steps, and if I'm somewhere wrong you can tell me.
Well, after a clean windows 7 install, I connect the phone to the pc (with or without battery,I think I tried both, didn't see something change) it gets to "other devices" as an "unknown device". right click to update driver software, select the folder with vcom drivers.
It gets recognized as a mtk usb port.
Try to flash like that, same results.
Then I go to update driver again, but this time I click "let me pick from a list of device drivers on my computer." I uncheck show compatible hardware, then I choose MTK Preloader USB VCOM Port.
the device now shows up to the device manager as "MTK Preloader USB VCOM Port".
Try to flash, everything is the same...
I read somewhere, that the normal installation of vcom drivers is kinda different, that it get's shown up as "MTK Preloader USB VCOM Port" right away, and I read that when you install the vcom driver correctly, it connect and disconnects the device every 3 seconds.
Well.. I didn't manage to get the preloader.bin yet, I'll ask for it, but why the official rom on needrom.com preloader.bin is not working with my phone? And why would smatdigi preloader.bin would work for me?
I tried roms that are for e2001v21_v89_zlh_hd but even their preloader wouldn't work for me.
first of all, stop playing with those preloaders. random flashing will brick your motherboard of your computer too, if you flash a wrong BIOS file. clear? okay. the DRAM error occurs if the Rom is mismatching the "signature" of your device. so, before trying to flash it, take another one, in this case, the right one. ( for example: my device (n9770) got few cameras, few board revisions, ddr or ddr2 Ram and so on, only one Rom or a mix of different files will work)so flashing a wrong firmware causes more "damage" or "errors". have you backed up your firmware before rooting?
you need to find a full backup of your device ( most likely a Rom directly from your vendor) including ALL needed partitions for flashtool. ROM's of new devices are hard to find, even for n9770 (mt6577) there are ROM versions from 06-2012 till now. so, if you got a "newer" device, you need to get the correct firmware and flashtool should flash without problems. also, your drivers are working perfectly, otherwise flashtool won't show the red bar wich is checking the device.you may need to check if the "second" driver is installed correctly, because the device will switch from preloader mode to "flash mode". maybe the driver for the preloader is installed correctly, but it can't switch to flash mode.
Chrizzly92 said:
first of all, stop playing with those preloaders. random flashing will brick your motherboard of your computer too, if you flash a wrong BIOS file. clear?
Click to expand...
Click to collapse
Clear bro, but I never really managed to do a flash. Just never. I only get dram failed.
Chrizzly92 said:
okay. the DRAM error occurs if the Rom is mismatching the "signature" of your device. so, before trying to flash it, take another one, in this case, the right one. ( for example: my device (n9770) got few cameras, few board revisions, ddr or ddr2 Ram and so on, only one Rom or a mix of different files will work)so flashing a wrong firmware causes more "damage" or "errors". have you backed up your firmware before rooting?
Click to expand...
Click to collapse
I don't think I did any more harm, since nothing really fot flashed.
Not I don't have a backup :/
Chrizzly92 said:
you need to find a full backup of your device ( most likely a Rom directly from your vendor) including ALL needed partitions for flashtool.
Click to expand...
Click to collapse
I bought it from focalprice, even if they send me any rom, it will be one of the officials found in needrom.com ... So I don't think they'll handle it.
Chrizzly92 said:
also, your drivers are working perfectly, otherwise flashtool won't show the red bar wich is checking the device.you may need to check if the "second" driver is installed correctly, because the device will switch from preloader mode to "flash mode". maybe the driver for the preloader is installed correctly, but it can't switch to flash mode.
Click to expand...
Click to collapse
How can I check that the second drivers is installed correctly?
just open your device manager and check, if the device gets recognized correctly. start a flash and check, if there are any devices gets loaded while trying to flash. if so, install the correct driver. there are some issues with that sometimes.
if this won't work, try using MTD tool. flasing through there should work always, but it got some issues with vcom drivers. you need to assign every vcom port to the mtk device. explaining of this is retty hard since english isn't my motherlanguage, so its best to check google or xda for that.
also, can you start your device into recovery, or is it really "dead"? no bootlogo, nothing?
No the device is hard bricked, no recovery at all. Not anything. :/
I can't use MtkDroidTool, it doesn't detect my device.
hmn, i would suggest its a hardware failure. never saw a device "dying" without flashing before.
btw: i meant SPMultiPortFlashDownloadProject tool, this is a more advanced variant of sp flash tool. just google for it and put a log in here, so i (we) can check whats the matter.
Chrizzly92 said:
hmn, i would suggest its a hardware failure. never saw a device "dying" without flashing before.
btw: i meant SPMultiPortFlashDownloadProject tool, this is a more advanced variant of sp flash tool. just google for it and put a log in here, so i (we) can check whats the matter.
Click to expand...
Click to collapse
I already have this tool and used it with the same results.
Which log do you need? It has 3 but 2 of them are really long, cant fit them in one post.
Voliminal_8 said:
I already have this tool and used it with the same results.
Which log do you need? It has 3 but 2 of them are really long, cant fit them in one post.
Click to expand...
Click to collapse
did u manage to get the preloader from smartdxxx............. ???????
it just takes 5 minutes (the most) to create the preloader from the phone.
take up the battery from the phone, run sp flash tool, connect the phone to computer, 5 sec, the rom_0 is read
put back battery, on the phone, connect the phone to computer, run mtk droik tool, 30 secs later, the preloader is created.
china phones
stevenma61 said:
did u manage to get the preloader from smartdxxx............. ???????
it just takes 5 minutes (the most) to create the preloader from the phone.
take up the battery from the phone, run sp flash tool, connect the phone to computer, 5 sec, the rom_0 is read
put back battery, on the phone, connect the phone to computer, run mtk droik tool, 30 secs later, the preloader is created.
Click to expand...
Click to collapse
been to a lot off repair phones shop and all stead screen x920 done buy a SquareTrade 2 yr warranty £30.99 ins on phones
Hi, I was trying to use Flash tool and Don't know what happend but My Phone is completely DEAD right now even power button is also not working no screen is there (just blank phone).
I am having UMI X2 2GB rom, 32 gb internal memory, 1.5 GHZ (MT6589T) Model.
I tried to use SP Flash tool to recover my phone. Firstly I tried to format the phone, After that I tried to run the correct scatter file for MT6589 (from one of the ROM Posted under UMI-X2).
Drivers for the SP Flash tool is loaded correctly (into my Windows 8 Pc). I was previosly getting error as follow : SP FLASH TOOL ERROR: (8200)
[Platform Error] The load and target are inconsistent!
Now, after searching a lot I found that its something wrong with SP Flash tool version.
So I downloaded SP Flash Tool V3.1304.O.sn119 version. After that I am trying to "Download" the rom (with the correct scatter file for my ROM). but its only showing me RED Bar (with 100%) and after that it does nothing. Its neither showing me any error nor its continuing the process.
I am in serious problem here. Please help me out.
Thanks in advance!
- Umang
umang_nine said:
Now, after searching a lot I found that its something wrong with SP Flash tool version.
So I downloaded SP Flash Tool V3.1304.O.sn119 version. After that I am trying to "Download" the rom (with the correct scatter file for my ROM). but its only showing me RED Bar (with 100%) and after that it does nothing. Its neither showing me any error nor its continuing the process.
I am in serious problem here. Please help me out.
Click to expand...
Click to collapse
Try this version of :
SP Flash Tool
October Official Rom
USB Drivers (if needed)
Works for me.
Necro thread...
I have the same issue.
A couple of days ago the phone just started turning off / locking up when off, and having great difficulty tuning on... i.e. pulling out the battery for a minute or a few times.
Now the phone won't turn on at all. They only sign of life is the charging animation when you plug it in.
Prior to all this, there appeared a window in Chinese with some options. my GF (who's phone it is) just pressed something, no idea what. But she said something about 'drawing on the screen'??? sound like something locked up and the previous frame wasn't deleted from the frame buffer before redrawing the new one... I have no idea.
Anyway, I tried going into recovery to see if there was anything I could do there, unfortunately everything was in Chinese, so not much help. for some reason now, the recovery isn't even working.
Now I can connect to the phone via SPflash, but I get the above response: '[Platform Error] The load and target are inconsistent!'
Some other ROMs I tried give me this response:
'The load to be downloaded is for MT6589;
The target platform is MT6582_S00'
Which is quite suspicious.
Any ideas?
Thanks
hisense HS-U980 bricked....
hi,i have the smartphone hisense hs-u980 with mt6589 or mt6589t, i dont understand.... so, i briched with sp.flash tool and now is ompletly dead,,, can i have ur help-sipport please?
thank u very much
Hs-u980 complete dead/bricked
carretto76 said:
hi,i have the smartphone hisense hs-u980 with mt6589 or mt6589t, i dont understand.... so, i briched with sp.flash tool and now is ompletly dead,,, can i have ur help-sipport please?
thank u very much
Click to expand...
Click to collapse
i have ur same phone and i have ur same problem,my pkone is dead later flash any wrong miui rom from cwm recovery and now is dead,i dont have any idea where is original firmware for sp.flash tool or other how piranha box,please,anyone can please me??? THANK U for read!!!!
I have the same Problem. So frustrating men. If anyone finds a solucion please email me [email protected] ...
SP FLASH TOOL ERROR: (8200)
As i connect my phone it disconnects after 2 seconds..
Please give me a site to download scatter file for my micromax a 310
Apparently sometimes it's not the best idea to use the flashing software that the manufacturer of your phone released.
I have a Wiko Lenny(technically a MediaTek MT6572) that has(or had - now it's dead) the habit of simply rebooting into a bootloop every few months. Fixing that was simple; just start SP Flash Tool, format everything then flash the stock ROM back. Last time I did that was around 4 months ago, and since then I have upgraded to Windows 10, and as such, lost the tools I had installed.
Yesterday it went into a bootloop again. I didn't remember exactly what tools I used, so I assumed they were the tools that Wiko supplied a while back with the V10 ROM. Well, they weren't. I still thought I'd give them a try. I mean, it's from the manufacturer's site, so they must work even better that the ones I was using.
I was wrong. The tool flashed the ROM "successfully", but the only thing it actually succeeded to do is corrupt the preloader. For those who don't know, corrupting the preloader basically means the phone won't even power on(not boot, actually power on), won't charge, and the PC won't detect anything if you connect the phone. Practically, it's the hardest brick a phone can get.
The fastest way to fix that is by either using a JTAG connection to flash everything manually, or by entering something called the Mediatek META mode(don't quote me on this one, though - I never heard of it before). JTAG - well I don't have the tools or expertise necessary to do that(although I'd love to learn how to do it - if anyone can point me to a well-written guide or two about that, please do!), and I simply can't get the phone to enter the META mode.
Is JTAG the only way to do it? Is META mode just a myth? Is there a way to save my phone, or should I just say "RIP" and buy a new one(I have the money for a Samsung Galaxy A3, the new one, but I was planning to buy a new computer with that money - is it worth it?)?
TL;DR (It's not that long but anyway...):
I have a Wiko Lenny(Mediatek MT6572) with a corrupted preloader after I flashed it with Wiko's tool. Can I repair it or should I just buy a new phone?
Link to the culprit that killed my phone(AKA Wiko V10 ROM): https://docs.google.com/uc?id=0BzeAvoIC2yhHMTZESUU1Y3hUM0E
Come on people, let's fix this little guy.
EDIT: Please, just tell me what your ideas are... A tip, a crazy idea, some details about MTK devices that could help, anything is appreciated.
Please...
Looks like I'm getting the 10 posts just by begging people to say something... :crying:
I have an MTK phone and its always going wrong and not booting/turning on because I mess with it and break it
I'm sure I flash the backup I made in mtktools with spflash, and plug the phone in with no battery attached, I also have to use windows 7 on a dual boot as windows 10 never played ball properly. You also need the mtk VCOM driver installed, not just adb and normal drivers. If you have all these, and have tried them, then that is the end of my knowledge sadly. Only other thing is going to needrom and seeing if they have a full rom/backup with partition tables/preloader etc.
Also, had to try a few versions of sptools as certain versions didnt work, forget which one I have and which didnt work. And also had to use a samsung USB lead as the stock one didnt work, or the other way round. I just remember it was a ball-ache but did eventually work. Am not on that pc so cant be more helpful, sorry....
robneymcplum said:
I have an MTK phone and its always going wrong and not booting/turning on because I mess with it and break it
I'm sure I flash the backup I made in mtktools with spflash, and plug the phone in with no battery attached, I also have to use windows 7 on a dual boot as windows 10 never played ball properly. You also need the mtk VCOM driver installed, not just adb and normal drivers. If you have all these, and have tried them, then that is the end of my knowledge sadly. Only other thing is going to needrom and seeing if they have a full rom/backup with partition tables/preloader etc.
Also, had to try a few versions of sptools as certain versions didnt work, forget which one I have and which didnt work. And also had to use a samsung USB lead as the stock one didnt work, or the other way round. I just remember it was a ball-ache but did eventually work. Am not on that pc so cant be more helpful, sorry....
Click to expand...
Click to collapse
Thanks for replying. I'm not sure if I have the VCOM drivers, but I'll check. Luckily I also have a Win7 PC besides this one, so I'll try it there too.
You need to repair preloader. Contact me !
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
Please do a nice thing, and tell me how to repair it here. Maybe there will be people in the exact same situation...
Can't fix MIne too !
DragonSky87 said:
Please do a nice thing, and tell me how to repair it here. Maybe there will be people in the exact same situation...
Click to expand...
Click to collapse
I also got an android phone that is INTEX AQUA I5 hd , i was flashing my phone and unfortunatly my pc got off while flashing . And my preloader got currepted .
When i tries to flash my phone it connects to pc as Mediatek Viacom port , but after 3-4 sec it connects as a usb port .
I continuously gots connceted and dissconnected .
and my Sp flash tool shoes error " S_DA_SDMMC_READ_FAILED(3153) "
Can anybody help me with it ? please help me as soon as possible.
You need to flash preloader by Testpoint,after that flash rom.
Dont remember exactly the testpoint but you can try
DragonSky87 said:
Apparently sometimes it's not the best idea to use the flashing software that the manufacturer of your phone released.
I have a Wiko Lenny(technically a MediaTek MT6572) that has(or had - now it's dead) the habit of simply rebooting into a bootloop every few months. Fixing that was simple; just start SP Flash Tool, format everything then flash the stock ROM back. Last time I did that was around 4 months ago, and since then I have upgraded to Windows 10, and as such, lost the tools I had installed.
Yesterday it went into a bootloop again. I didn't remember exactly what tools I used, so I assumed they were the tools that Wiko supplied a while back with the V10 ROM. Well, they weren't. I still thought I'd give them a try. I mean, it's from the manufacturer's site, so they must work even better that the ones I was using.
I was wrong. The tool flashed the ROM "successfully", but the only thing it actually succeeded to do is corrupt the preloader. For those who don't know, corrupting the preloader basically means the phone won't even power on(not boot, actually power on), won't charge, and the PC won't detect anything if you connect the phone. Practically, it's the hardest brick a phone can get.
The fastest way to fix that is by either using a JTAG connection to flash everything manually, or by entering something called the Mediatek META mode(don't quote me on this one, though - I never heard of it before). JTAG - well I don't have the tools or expertise necessary to do that(although I'd love to learn how to do it - if anyone can point me to a well-written guide or two about that, please do!), and I simply can't get the phone to enter the META mode.
Is JTAG the only way to do it? Is META mode just a myth? Is there a way to save my phone, or should I just say "RIP" and buy a new one(I have the money for a Samsung Galaxy A3, the new one, but I was planning to buy a new computer with that money - is it worth it?)?
TL;DR (It's not that long but anyway...):
I have a Wiko Lenny(Mediatek MT6572) with a corrupted preloader after I flashed it with Wiko's tool. Can I repair it or should I just buy a new phone?
Link to the culprit that killed my phone(AKA Wiko V10 ROM): https://docs.google.com/uc?id=0BzeAvoIC2yhHMTZESUU1Y3hUM0E
Click to expand...
Click to collapse
Repair your own device
Soft Brick: Soft brick is the state of android device which occur due to some software problems like boot loops or phone freezing at some point during boot. This only occurs if some software problem occurred in the device mainly during OS upgrade or ROM flashing. If your device is in such state then you are luck there are 99% chances that you can recover your beloved device without needing any professional help or spending hundred of dollars.
Hard Brick Hard brick is the state of android device that occurs when your device won’t boot at all i.e. no boot loop,no recovery and also not charging. This occurs due to trying to flashed firmwere not made for your device or flashed incorrectly. This is more difficult to resolve and often require professional help
in MTK Android there is many Partitions in your phone. like Preloader, Recovery, Bootimg etc….. if somehow Preloader get Corrupted then you phone will not able to DETECT WITH PC !!! in other words you will have phone with BOOT DEAD.
How Preloader get corrupted ?
There could be few reasons but main reason could be that someone or you Flash your complete phone (include Preloader) with wrong files or with wrong ver. Also there could be reason someone Delete Preloader or you Deleted.
How could i know my phone have preloader dead ?
Preloader can be dead if some one Flash it wrong and after flash your mobile will not detect with pc any more. for confirm
1.sp flash tools does not detect your phone anymore and also the computer does not as there is a pop sound when usb is connected to device
2.open device manager
take battery out from phone
insert usb
insert battery
and check is computer detecting any device
If it’s not detect then you have phone which Preloader is dead AKA Boot Dead
How can i repair it ?
requirement
1.screwdriver (by which you can open the screw from handset)
2.bricked device
3.a usb cable
4.a copper wire( for sold test points)
5.a pc with sp flash tool,mtk drivers and stock firmwere for your mobile
now you have to disassemble your phone and take pcb out. check there should be some Golden points. check these points there should be written on them Rx,Tx,GND,Vcc,Vcharge etc… check there should be written “COLO” or “KOLO” or“KCOLO” you have to Sold that point with GND After Sold Attach usb now your phone will detect with USB !! and now ready to Flash.
In some phones “COLO” or “KOLO” or “KCOLO” not written for those type of phones you have to test all points one by one Short Golden point with GND and attach usb cable which point short with gnd can able to detect your phone by pc isForce Preloader Mode Test Point !! Keep in mind Don’t Short Vcc,Vcharge or any other pin which have 4.x Volts also i had tested “Colo” or “Kolo” or “KCOLO” don’t have any kind of volts.
need help
gsm-decode said:
You need to repair preloader. Contact me ![/QUOTE
i have samsung clone A9 MT6580 After reflash phon,e is dead by sptool..i thinkl preloader is damaged..i dont have back up..but ditecting VCOM BUT Always "Sft Enable Dram_Fail (4032)" in format or fullfash in all tools
Click to expand...
Click to collapse
help me i corrupted my pre loader
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
hi sir I try to flash a stock rom downloaded from internet
its a vivo v5 android mobile phone
I tried to flash but I got a few alerts
the selected model does not support model verification
and
if I tried it gives me a brom error
now my phone condition is hard bricked and responding to flash tool
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
HI sir how can I contact you
Hi I also have the same problem - when I flashed the stock rom of my LG K7 X-210 (MT6580__lge__LG-X210__m13g__5.1__ALPS.L1.MP6.V2.19_ARIMA6580.WE.L_P42) with the SP Flash tool when I was in a bootloop, I accidentally forgot to uncheck the preloader option. I flashed it to my phone and from that point onwards it didn't want to start up any more, nor would it react if I tried charging it. So conclusion: the preloader is corrupt...
However, I read online that MTK devices (mine is MT6580) have a 'meta' mode which allows your device to still connect to SP Flash tool even if it is hardbricked (in my case by pressing the volume up button, and then simultaneously plugging it in the computer). It is then recognized as MTK Com port something in device manager.
Luckily I have the same phone (but it's not mine) and I was wondering if it was possible to make a full rom dump from that device and restore it on mine? (a method that is safe for the other device as well)
i have a proble on my new phone since i flash preloader my touch is not working anymore, any solutions ?
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
I need to repair preloader of My Nokia G20.
hello this is very simple.
i solved this problem.
i wrte english very small.
flash atarken yanlış attığın preloader dosyası ile başlat.cihazı bilgisayara bağla.format bittikten hemen sonra doğru preloader dosyasını klasörün içine yapıştır.ama çok hızlı olmalısın.yani uyumsuz preloader dosyası ile cihaza yükleme yaparken tam format esnasında uyumlu olan preloader dosyasını hızlıca yapıştır.
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
Hello, is it too late to write?