First of all, sorry for my bad english. My problem started when i deleted accidentally one partition of the tablet, trying to make an working twrp for it. Now I have no adb commands, no recovery, no fastboot,no logo,no display light. Nothing works. Just an expensive brick. PC only see something like "diagnosis 900E, instead of USB QDLoader 9008,so QFIL can do nothing to fix.I have changed driver,now can be seen QDLoader but QFIL gave me errors. I just bought another tablet, same model, for my son. I will try to pull out system, recovery, boot etc. But after that...? Any chance to make an bootable microSD card with those files? Any advice please?
Costi979 said:
First of all, sorry for my bad english. My problem started when i deleted accidentally one partition of the tablet, trying to make an working twrp for it. Now I have no adb commands, no recovery, no fastboot,no logo,no display light. Nothing works. Just an expensive brick. PC only see something like "diagnosis 900E, instead of USB QDLoader 9008,so QFIL can do nothing to fix.I have changed driver,now can be seen QDLoader but QFIL gave me errors. I just bought another tablet, same model, for my son. I will try to pull out system, recovery, boot etc. But after that...? Any chance to make an bootable microSD card with those files? Any advice please?
Click to expand...
Click to collapse
So use ZTE tool studio emmc tool to unbrick your android.
Follow guide of Androidbrick.com.
The tool posted on these site is actually a ZTE tool studio tool by name of Androidbrick tool.
Just Google and download it from torforum.org
Already tried,not working.I cannot swich phone in download mode
Costi979 said:
Already tried,not working.I cannot swich phone in download mode
Click to expand...
Click to collapse
These tool unbrick your android when no fastboot, no recovery, not booting by anyways. Just detects in 9008 port. I am sure it's better than Qfil.
That`s the problem with port detection
How does this happened ?
Hello Costi979,
Sorry for your tablet, I hope you will find a solution
I wanted to know if this happened when trying to install TWRP on this tab2 10-30 tablet, under Android 6.0.1, like explained in this thread : http://forum.xda-developers.com/android/development/recovery-lenovo-tab-a10-30f-l-twrp-3-0-t3442588 ? Can you confirm that it does work or not ?
Thanks for your explanations,
I hope you will success to recover your tablet,
Regards,
Sebastien
Barnabe02 said:
Hello Costi979,
Sorry for your tablet, I hope you will find a solution
I wanted to know if this happened when trying to install TWRP on this tab2 10-30 tablet, under Android 6.0.1, like explained in this thread : http://forum.xda-developers.com/android/development/recovery-lenovo-tab-a10-30f-l-twrp-3-0-t3442588 ? Can you confirm that it does work or not ?
Thanks for your explanations,
I hope you will success to recover your tablet,
Regards,
Sebastien
Click to expand...
Click to collapse
Sorry if u have issues to. My problem started when i erased via adb one partition . Twrp works fine
Related
Hi guys, after installing chainfire3d and reboot the device it win't start any more, it stop on teclast logo, rockchip flash tool don't recognize the device that in windows is seen as adb device..for some strange reason if i look at the device details it will be recognized as an htc?? I can start in recovery mode (the one with the little android ko with a red "!")
I really don't know what to do now.. someone with a brillant idea and some more experience than me can help in a flash with some other tool? or if exist an emergency flash from sd..
Thank you!!
Solved...
I'm sorry to have bothered you all.
It's strange.. but i changed the usb cable (that works perfect with my phone) and tablet was seen from the rockchip flasher..
Really sorry.
Thx.
Help
figus77 said:
Hi guys, after installing chainfire3d and reboot the device it win't start any more, it stop on teclast logo, rockchip flash tool don't recognize the device that in windows is seen as adb device..for some strange reason if i look at the device details it will be recognized as an htc?? I can start in recovery mode (the one with the little android ko with a red "!")
I really don't know what to do now.. someone with a brillant idea and some more experience than me can help in a flash with some other tool? or if exist an emergency flash from sd..
Thank you!!
Click to expand...
Click to collapse
Hello, how did you solve it? Please any help will do.
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
This may help. http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
At least there is more going on for Firefox Open over there.
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Defier525 said:
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Click to expand...
Click to collapse
Sorry! Eyes tight shut!
Are there any updates on this one?
I have bricked Open too, I'm attaching the PCB picture, if it is any help to maybe find UART or JTAG pins?
Can someone be really nice and please dump the bootloader from working ZTE Open in send it to me?
I've found some guy, who maybe can help me write bootloder with JTAG.
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
psywolf said:
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
Click to expand...
Click to collapse
Thanks for your time to help, but this does not work for me. I get an error, when I press flash button (printscreen under attachments).
I've tried to probe the pins with the multi-meter and found GND and V+ (picture under attachment)
Now it would be nice to have something like this -> http://www.grandideastudio.com/portfolio/jtagulator/
Defier525 said:
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
Click to expand...
Click to collapse
tpt files for the zte open
https://www.dropbox.com/sh/rnj3rja7gd54s98/_twgXEkMFH/P752D04_DEV_EU_20131212_v1.2.7z
Thank you for the link. But what tool is supposed to be used to flash the files? And is there a way I can use my backup as well? In this case: how can I transform it to TPT files?
Update: I tried flashing it by following the instructions of the link posted by psywolf, but unfortunately I am getting the same error as aversario. I tried also flashing just recovery, but it seems like no single partition is flashed successfully.
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
aversario said:
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
Click to expand...
Click to collapse
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
linr76 said:
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
Click to expand...
Click to collapse
Well, I don't know the partition names by heart, but as I remember the bootloader is one of the small partitions (so definitely not system or boot or userdata or recovery).
The way to get that small partitions would be installing CWM recovery first -> http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
then enter adb shell on computer
su # to get root privileges
then it should be something like explained here -> https://www.youtube.com/watch?v=j3GOzUURSgM&feature=player_detailpage#t=153
And thank you very much for your time
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Sent from my V3 using Tapatalk
linr76 said:
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Click to expand...
Click to collapse
OK, I get that. I'm sure there exists a way to do it without changing recovery also. I just can't figure it out because that's the only Firefox OS phone I've had.
try to reinstall
Hi, I bricked my ZTE Open (EU version) too. Had bought it from a German Ebay seller and tried to flash FirefoxOS 2.0 on my device. I don't have the CWM recovery installed, only the "Firefox OS System Recovery" Big mistake, I know . When I switch on the device, the Firefox OS logo appears, then disappeas after a few seconds, and so on, the perfect bootloop
I can't access the device via ADB or fastboot.
When I ty to install any downloaded zip (even from ZTE's homepage) from the SD card, I get following messages:
Code:
--Install /sdcard ...
Finding update package ...
Opening update package ...
Verifying update package ...
E: signature verification failed
Installation aborted.
So there is no valid signature.
Can you help me please? Thank you!
Heinz
Found a solution by myself!:victory:
I downloaded the update.zip file from firefox.ztems.com (Update package of Android GB for OPEN device) and installed it.
After that I could flash the CWM recovery. It seems to work...
Hi guys, i really hope you can help me, i m so deseperate...
After OTA Update my CATERPILLAR S30 bricked into bootloop, i can access to the stock recovery (wipe data/factory not fix it) and bootloader show me ; "DC CHECK"
I read that it could be my bootloader (emmc) wich it's corrupted...
The chipset is a Qualcomm Snapdragon MSM8909, of course USB debugging is disabled and i can't find any stock rom, backup for this phone....
Please HELP ME...i work hight in the mountain and if i cant communicate it will become....quite dangerous for me...
If someone has a backup (EU AREA), a stock rom or any solution for me ill be gratefull
Bye
Nobody can upload me OTA file (wich i ll .zip), boot.img, backup or any kind of solution please...?
AnY-One said:
Nobody can upload me OTA file (wich i ll .zip), boot.img, backup or any kind of solution please...?
Click to expand...
Click to collapse
What software version are you on?
Chuggers said:
What software version are you on?
Click to expand...
Click to collapse
Hello there and thanks helping me...
I'm AnY-One but i can't log in with; i dont know why...
I dont know what is my software version i only can say to you that the last update i tried to install came about 10-12/01 (EU France) and i bought this phone the 24/12 and i already did a first update.
So my phone stuck in bootloop (Qualcomm HS-USB QDLoader 9008 recognized) when i tried to install the 2nd update 10-12/01 so...
I have all qualcomm developpers tools with qualcomm flash utility and i can access to stock recovery...perhaps just a boot.img should work...
Pleassse help guys...
"and...as you can read; SORRY FOR MY ENGLISH"
---------- Post added at 05:32 PM ---------- Previous post was at 04:52 PM ----------
an update.zip that i can flash from recovery should be welcome
---------- Post added at 06:19 PM ---------- Previous post was at 05:32 PM ----------
Got it, i think software version (viewing in recovery mode) is LTE_D0201121.0_S30_0.017.01
Zi0nlive said:
-snip-
Click to expand...
Click to collapse
Is warranty not an option?
nagalun said:
Is warranty not an option?
Click to expand...
Click to collapse
it is but it takes time...and i like to fix my mistakes by my self...
Have you a solution for me? can you upload the OTA files or a backup rom .zip?
Zi0nlive said:
it is but it takes time...and i like to fix my mistakes by my self...
Have you a solution for me? can you upload the OTA files or a backup rom .zip?
Click to expand...
Click to collapse
You can access recovery?
Usually when you see "Qualcomm HS-USB QDLoader 9008" it is because the phone can't load the bootloader (bios), so I am a bit confused about the state of your phone.
You likely need more files than the OTA has.
nagalun said:
You can access recovery?
Usually when you see "Qualcomm HS-USB QDLoader 9008" it is because the phone can't load the bootloader (bios), so I am a bit confused about the state of your phone.
You likely need more files than the OTA has.
Click to expand...
Click to collapse
That's a good question ; yes i can access to QDloader HS-USB 9008 with qualcomm drivers ; I CAN ONLY acces to
recovery holding VOL+ then plugin in USB. Phone off then : POWER + VOL+ doesnt boot recovery.
Wipe Data/factory seems to work, adb sideload; device is regognized in adb shell but most of commands answer are: "FAILED (remote: unknown command)" when i choose reboot in bootloader it's the boot screen with 'DC CHECK MODE' left corner..
Is there someone reading me who has the same phone?
Is there someone able to upload me .img (system, boot ...) that i can flash with QPST Tools? Stock Firmware? Nandroid Backup?
Is there someone who can guide me to repair that phone stuck in bootscreen? I think the problem come from my stupidity fogetting to unroot (Kingoroot apk replaced by SuperSU) before OTA update.
How extract my proper firmware
Hello
How extract the om from the device
Help Me
Same problem...
I have the same problem too... Please help
sharing my experience in a similar quest
Hello ! You probably must have resolved the issue by now. Like you, I too had a similar issue ( Reliance Jio Lyf Wind4 - Haier L51)
In my nooby quest for a solution have made some progress. The learning is:
One needs : Mprg8909.hex, 8909_msimage.mbn, rawprogram0.xml, patch0,xml to recover.
If you can get hold of a phone similar to yours, you can dump all the partitions. That can then be used to get the required information to make your unique rawprogram0.xml. The process of dumping becomes very easy if the phone is root and you are running an insecure boot. Using basing Linux commands like fdisk,gparted,proc you can get and idea of your partition details. The dd command will help you dump the partitions.
Yes the tools to use is from the QPST suite or look for the stand alone emmcdl.exe
As your phone is showing the QUSB 9008 mode you need to be able to switch the phone to Emergency Download Mode after which you can use MIflash or similar tool to flash the ROm from the dumped images. Thats where the rawprogram0.xml comes in. It details partition information required to revive the phone.
Havent succeeded yet, but am feeling encouraged. Probably need to resolve syntax errors creating the rawprogram0.xml and figure out if just this much is enough to switch the phone to EDL.
After lurking here for months, this is my first post, therefore I request indulgence in case I have inadvertently erred
TooSour
AnY-One said:
Hi guys, i really hope you can help me, i m so deseperate...
After OTA Update my CATERPILLAR S30 bricked into bootloop, i can access to the stock recovery (wipe data/factory not fix it)
and bootloader show me ; "DC CHECK"
I read that it could be my bootloader (emmc) wich it's corrupted...
The chipset is a Qualcomm Snapdragon MSM8909, of course USB debugging is disabled and i can't find any stock rom, backup for this phone....
Please HELP ME...i work hight in the mountain and if i cant communicate it will become....quite dangerous for me...
If someone has a backup (EU AREA), a stock rom or any solution for me ill be gratefull
Bye
Click to expand...
Click to collapse
You will need:
Hi
I have a similar issue with a different phone (Reliance LYF LS 5014 - a.k.a. Haier HL-L51) Service centres will claim that the motherboard needs to be changed (and charge you an arm and a leg ;p) Even if you get the firmware image it wont help. Thats becuase if you are bricked and in the QLoader 9008 , you first have to get the phone in EDL (emergency download mode) only then can you use MI Flash et al to flash your ROM.
The route I am taking is as follows: got hold of a similar phone and dumped all the partitions using the dd command. Then getting hold of all partition information using gdisk/parted/df et al This is so that I can create a partition.xml. From this I could run a Python script ( PartitionTool.py) to get rawprogram0.xml, patch0.xml. Using emmcldl and partiton.xml I can create the 8909_msimage.mbn . Hopefully, armed with these and QPST /Miflash I should be able to revive my phone. I have read that one needs the mprg8909.hex to kick the phone into EDL but am not convinced that without it I will remain stuck. That file seems to be guarded like a state secret by phone manufacturers.
ALl this I have learnt the hard way over almost a fortnight. I confess that I do fall into the "noob" category and cant program/develop to save my life. Therefore it should be easy for anyone with the right amount of enthu
Cheers
Zi0nlive said:
Is there someone reading me who has the same phone?
Is there someone able to upload me .img (system, boot ...) that i can flash with QPST Tools? Stock Firmware? Nandroid Backup?
Is there someone who can guide me to repair that phone stuck in bootscreen? I think the problem come from my stupidity fogetting to unroot (Kingoroot apk replaced by SuperSU) before OTA update.
Click to expand...
Click to collapse
on continuing my quest for a solution
Havent given up yet.
Discovered two really useful utilities: emmcdl and fh_loader both work from the DOS command prompt and are useful to download images and partitions to the phone.
Managed to create a rawpartition0.xml which I think is for my phone ( LYF Wind 4 a.k.a Haier HL L51 and LS5014) For this I used a similar phone and after rooting it managed to extract start sector and size in kilobytes info for each of the partitions.
Also used EFS Professional to get a backup of emcc firmware.
Have successfully downloaded all the partitions but am failing at the bootloader (emmc firmware) part. Continuing my quest for a solution and will share whatever I figure.
Cheers
Vonageext4ts said:
Havent given up yet.
Discovered two really useful utilities: emmcdl and fh_loader both work from the DOS command prompt and are useful to download images and partitions to the phone.
Managed to create a rawpartition0.xml which I think is for my phone ( LYF Wind 4 a.k.a Haier HL L51 and LS5014) For this I used a similar phone and after rooting it managed to extract start sector and size in kilobytes info for each of the partitions.
Also used EFS Professional to get a backup of emcc firmware.
Have successfully downloaded all the partitions but am failing at the bootloader (emmc firmware) part. Continuing my quest for a solution and will share whatever I figure.
Cheers
Click to expand...
Click to collapse
1. Why can't you go to the Rjio service center and get it flashed? Just tell them it got screwed after an update.
2. How did you manage to root the phone? Mine is Flame1 which has same MSM8909 chipset.
I am very not happy with the stock ROM but I don't think anyone has come up with a custom ROM for this cheap chipset.
I have bricked my CAT S30 too. Is there someone who have a solution? Or can somehow make a ROM copy so I can somehow flash it to the phone? I made a lot of searching and can not figure out how to make the phone work again.
hello I need firmware for S30 because I lightened too much after the root and I deleted something I should not, is now locked in the home screen CAT, but I can get into fastboot and bootloader.
thank you guys
file for CAT S30
Hello
I purchased another CAT S30 which has just lit downloaded a system update and I extracted from the cache, now the load so you can work on it.
if you need other things tell me how can I copy them from working phone.
my I crashed after I canceled the DownloadProviderUi.apk files and perhaps I put not compatible. now I can only access the fastboot or DC CHECK mode.
I tried to flash the .zip program but by mistake, I tried to flash the update and installs it by error although it says it has been installed, and still does not start, remains in the white screen CAT
https://www.dropbox.com/s/trqfxvnp90qt8vn/__FUMO.zip?dl=0
Vonageext4ts said:
Havent given up yet.
Discovered two really useful utilities: emmcdl and fh_loader both work from the DOS command prompt and are useful to download images and partitions to the phone.
Managed to create a rawpartition0.xml which I think is for my phone ( LYF Wind 4 a.k.a Haier HL L51 and LS5014) For this I used a similar phone and after rooting it managed to extract start sector and size in kilobytes info for each of the partitions.
Also used EFS Professional to get a backup of emcc firmware.
Have successfully downloaded all the partitions but am failing at the bootloader (emmc firmware) part. Continuing my quest for a solution and will share whatever I figure.
Cheers
Click to expand...
Click to collapse
Hi.. i have a CAT S30 stuck in logo, how i can use your file? thanks
Hi got this same phone only two weeks ago, and broke it trying to root it, got stuck on Bootscreen, however I found an unofficial rom for the device, loaded into an SD card and applied via recovery and boom, its a working phone again.
If you still need help, let me know so I send you a link to the ROM.
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?
Hello !
As the title says I need a custom recovery for my phone.
I'm using the Archos 50d Helium and it is running Lollipop 5.1.
I also have uploaded the stock recovery.img here so that you could try to work with it.
Can someone try to make one for me ?
I'm really not familiar with compiling stuff on Android.
Thanks and have a good day ! :victory:
Ps: If you have any question don't hesitate & ask me I'll gladly answer !
Hi! My Archos 50d Helium have got brick after I flash TRWP recovery (maybe wrong version for my phone). Now it can't get into logo, recovery mode, fastboot mode. It can be realized via PC by Qualcomm HS-USB Diagnostics 9006 Drivers.
I found a method to fix it. I guess it bricked due to TWRP format wrong to SYS_BOOT partition on my device (my fault).
I need a SYS_BOOT.IMG to unbrick it.
PLS help me!