Related
Hello to all community,
strange things happened here... I use a Star H920+ phone. I had some problems with Bluetooth and Wifi, so i decided to flash rom again. I downloaded the rom from needrom dot com. (As new user, i cannot post the full url yet)
I used Smart Flash Tools to do the job. Firstly i had some difficulties getting some errors. After some search, i used MtkDroidTools and i got the right sizes for memory and write them at scatter file. The procedure went well and i got a green circle at Flash Tool.
And that's it...
After that, i get the absolute Black. But... the strange thing is that the Windows detects the phone. I tried every combination to get into recovery mode, but nothing. Only black screen.
I tried Flash Tools again to flash it with the same or an older rom, but after the some seconds, the application is not responding and Windows says that the Smart Flash Tools application has stopped responding and must be closed.
MtkDroidTools doesn't recognized the phone now.
But, as i have it connected with the pc, the sound of plug and unplug a device is heared all the time. ( Maybe it is rebooting continuously )
I hope that the hoping thing is that Windows detects the phone, but i cannot do anything more...
Do you have any idea to propose me ?
Thank you very much,
Periklis
Perarg said:
Hello to all community,
strange things happened here... I use a Star H920+ phone. I had some problems with Bluetooth and Wifi, so i decided to flash rom again. I downloaded the rom from needrom dot com. (As new user, i cannot post the full url yet)
I used Smart Flash Tools to do the job. Firstly i had some difficulties getting some errors. After some search, i used MtkDroidTools and i got the right sizes for memory and write them at scatter file. The procedure went well and i got a green circle at Flash Tool.
And that's it...
After that, i get the absolute Black. But... the strange thing is that the Windows detects the phone. I tried every combination to get into recovery mode, but nothing. Only black screen.
I tried Flash Tools again to flash it with the same or an older rom, but after the some seconds, the application is not responding and Windows says that the Smart Flash Tools application has stopped responding and must be closed.
MtkDroidTools doesn't recognized the phone now.
But, as i have it connected with the pc, the sound of plug and unplug a device is heared all the time. ( Maybe it is rebooting continuously )
I hope that the hoping thing is that Windows detects the phone, but i cannot do anything more...
Do you have any idea to propose me ?
Thank you very much,
Periklis
Click to expand...
Click to collapse
I have the same problem patrida !!! Have you found out a sollution yet ?
Use SP_Flash_Tool_v3.1344.0.212
And select Firmware -> upgrade
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
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?
Hi,
I bricked my phone, a SHARP Aquos C10.
After unlocking the bootloader I was able to install several rom. The last one was LineageOS 18.
I bricked the phone when I tried to replace LineageOS Recovery with TWRP by dint of trying.
The phone is not completely blocked. It gets stuck for a long time on the "battery" logo which replaced the "Sharp" logo when the unlocked it. After several minutes, it vibrates and restarts.
I can restart it by long pressing the OFF button, I can't turn it off, I can't put it in recovery mode.
I can just put it in download mode but unfortunately it is no longer recognized by the PC.
So, bricked or not bricked.
Thank you for your help.
Nobody can help me ?
Hallo,
if you still can go to the download mode, maybe not all hope is lost. Your phone might not have
a hard brick, but only a soft brick. Everything should be fine as long the download mode isn't bricked too.
I had a similar problem once with a tablet after flashing it.
You need to install the USB-Drivers for your device on your PC and then reconnect it.
This might sound ridicolous if you already have installed them, but sometimes
a deinstallation of the USB-drivers and reinstallation of the drivers might help.
I found the following site for the drivers:
"https://gsmusbdriver.com/sharp-aquos-c10".
If you prefer an official source, you can use: "http://www.sharpusa.com/Home/CustomerSupport/SharpCareCenter/MobileSupport/ADBDriver.aspx"
However both sources seem to look reliable for me, even if I can't test it, without having a SHARP device.
If you are not sure, you might compare it with other tutorials and look for reviews.
Installing the drivers can't lead to harm to your device until you don't connect it.
Things can't really get worse if you install the drivers. The only thing that could happen is, that either the PC will say that it recognizes the device or that no device can be recognized, so it's worth a try. Please report me, if it worked for you and you are able to flash again. I hope this will help.
With kind regards
dontdropme
Hello,
Thank you very much for your help.
Yes, I installed the USB drivers. I unlocked the phone for you I installed another rom.
I reinstalled the drivers following your links. Unfortunately that does not change anything. The phone is not recognized. No sound comes out of the computer when I connect the USB cable.
I tried on 2 computers, 1 on Windows 10 and in Windows 10 / Xubuntu dualboot.
When the battery is empty and I try to turn it on, a red battery will light up and flash. As I charge it, the battery changes color to green.
I don't have download mode if the cable is not plugged into the computer or the charger.
:/
Hallo,
the download mode is supposed to be only able to get started if you connect the device to the computer or another device, this is not strange. You need to go to the download mode and try to flash the stock firmware for you device. Try it at first without a device recognition of your PC and find out, if you need to do a hard reset before, to regain factory settings. I have listed, in color, a short number of things you could do now. If this still doesn't work only the SHARP team or a specialized company might help.
What you could do, is to ask the SHARP support for a source for the USB drivers and how to do a hard reset to regain the factory settings. I don't know which flashing tool you use for you device.
Normally if your device is not recognized by plugging it in to the PC-USB-Port the flashing tool shouldn't recognize it either, but it might be just an error of Windows, and the flashing tool is not allways depentent to the USB-drivers, but relies only on the question if you can go to the download mode, so you could give it a try to flash even in this case. Start the flashing software and look what will happen.
You said, that you have successfully flashed until now, which means that the flashing tool supports you device. If you can't flash now anymore, you might also not make a backup, which would be important, because the only things you could try now, is to find the stock firmware and flashing it.
If you haven't installed any important data on your system after flashing LineageOS or if you already made backups of your applications in a cloud or another drive you need not to care. It is possible that you will need to do a hard reset before. You can find on hardreset.info, in the section "All devices", how to do it or ask the SHARP support. If you fear you have still important data on your phone a backup is normally recommended.
Because flashing a ROM not only wipes your data, but removes the guarantee, the result is: Restoring the phone to a usable device by any helping team of SHARP's customer care service in you city, even if you have any service buildings, might be expensive in this case. To go around high prices you would need too look around also for other data restoring companies or specialists, if nothing works.
But at first, if you are able to do it; I would recommend to do a hard reset of your device, which should restore it to factory setting, which should make the drivers work.
Even if they don't work, ask SHARP for actualized USB-drivers. Try flashing also with and without working USB drivers, and find SHARP's stock firmware for you device first, which is a "must do", if you want to have access to the original recovery mode again. Flash this stock firmware after you have done a hard reset. After flashing the stock firmware you should be able to go to the custom recovery mode again, if not, only a specialized company or a help team of SHARP's customer service might help.
Hello,
The adb and fastboot commands wait for the device to connect.
SHARP support is not responding.
Hello, did you try "https://getsupport.sharpusa.com/Contact-Us/Product-Support"?
Because of the actual situation with the Virus, they might need longer to answer, so you need to be patient. As I see you already tried to connect your device after the use of CMD.exe. Installing the drivers with CMD and checking the Windows Hardware Manager if the Installation worked correctly is one way to do a driver install. I am sorry if this didn't work for you. If it does not, only a specailized soft- and hardware team can help, which could get expansive, but maybe not as much as buying a new device, so I hope for you Sharp will answer and give a correct Installation guide and that it will fit to solve your problem. I wish you good luck and that you don't need any other company than Sharp to help. I know that nobody is amused if all help and waiting does not help, after bricking bis device, but unfortunately I can't do more for you. I wish you success and keep your device in a safe place just for the case.
Hi everyone. As I said on a former post, I have an Alcatel 1t 7 tablet; I need its stock recovery image, but even stock firmware is getting impossible to find. I mean, apparently there are firmware for that reference of tablet, but what happens, is that there are several models that share the same physical appearance, but have different hardware, so, they have different firmware, and by that reason, their firmware don't work for my tablet. Anyway...
The fact is, looking that its original firmware is not available on the internet, at least publicly; I'm trying to reflash my tablet by using alcatel's tool called "Alcatel Mobile Upgrade", a tool that I don't guess, would be unknown for many of you. So as I said, I'm trying to reflash it with it (and in the process, restore stock recovery, I hope). So I installed MTK drivers, installed the version recommended for this tablet, followed program's instructions, but when I reach step 2 of 4, the program warns me saying this: "Read terminal information failed. Unplug device, remove the device battery and plug it again - Repeat step 2 and try again".
The issue is, that its battery is internal, not removable; even, is soldered to the board. And I must add, that at first, when I bought this tablet and began to "experiment" with it, I was using SP flash tool, and it was giving me almost the same warning that Alcatel mobile upgrade, but later I discovered what that was a fail of the used sp flash tool version. On a webpage, someone recommended a specific version of sp flash tool to fix that issue; I mean, that I could download firmware to the device without having to "unplug battery"; and It worked.
So first ¿How can upgrade my tablet by using that program?¿What am I doing wrong?¿ Which device must appear under device manager, to it can work?¿mtk usb port, Mediatek DA usb VCOM, Android preloader, or which one? And second, ¿Could be this problem, due to alcatel's mobile upgrade version?
let battery drain to make sure device is powered off. you only have preloader mode for a second - within this time pick up in device manager and install preloader drivers.
if drivers installed correctly, first start flashing, then connect phone. flash tool will keep device in preloader mode for the flashing time period
aIecxs said:
let battery drain to make sure device is powered off. you only have preloader mode for a second - within this time pick up in device manager and install preloader drivers.
if drivers installed correctly, first start flashing, then connect phone. flash tool will keep device in preloader mode for the flashing time period
Click to expand...
Click to collapse
Thank you for replying. Definitely using Alcatel mobile upgrade is not an option, at least to me. I mean, I couldn't make it work in any way. "Fortunately", after an exhaustive search, I could find a post on internet, that recommended for a similar issue, to use Sugar MTK; the publisher shared this program and its credentials, for can use it . So I downloaded and used it, and I could restore my original stock. Now my issue is to port it to TWRP, but now I'm gonna to write a new post about it.
link me to the sugarmtk