I have no idea what happened beside the battery completely drained and I was left hard bricked. I only have the blinking led. No mode beside EDL. Was rooted, stock rom android 11 and stock recovery. Phone had been stolen and possibly had someone trying to get in it. Appeared fine and in working order before it died though.
I have tried 3 different version blankflash files. I have been using sofiap. A few times (tried about 50x) they went all the way through to "fastboot reboot", but fastboot NEVER opens. Just same situation as before. May be an issue with singleimage.bin? Since blankflash doesn't seem to be effective, can I use another program (Qualcomm programs, Flash tools or other)? I have tried finding a solution, searched endlessly and have the same brick I had.
Please advise and help with the exact files, links, etc. The easiest way would be awesome. I would greatly appreciate any/all assistance.
Jaymi
jayleemcnabb81 said:
I have no idea what happened beside the battery completely drained and I was left hard bricked. I only have the blinking led. No mode beside EDL. Was rooted, stock rom android 11 and stock recovery. Phone had been stolen and possibly had someone trying to get in it. Appeared fine and in working order before it died though.
I have tried 3 different version blankflash files. I have been using sofiap. A few times (tried about 50x) they went all the way through to "fastboot reboot", but fastboot NEVER opens. Just same situation as before. May be an issue with singleimage.bin? Since blankflash doesn't seem to be effective, can I use another program (Qualcomm programs, Flash tools or other)? I have tried finding a solution, searched endlessly and have the same brick I had.
Please advise and help with the exact files, links, etc. The easiest way would be awesome. I would greatly appreciate any/all assistance.
Jaymi
Click to expand...
Click to collapse
Hard bricked mine too.
Metro G Stylus 2021.
acrinym said:
Hard bricked mine too.
Metro G Stylus 2021.
Click to expand...
Click to collapse
I Switched to Slot B and now it doesn't do anything except go into EDL.
Hey @sd_shadow, any idea what we could do to fix this mess? This is a phone I'm supposed to return.
I'm still stuck with a brick. Have been for months. Took it apart (why not it doesn't work anyway) and tried the points thing to put it in edl and still nothing. WE NEED ADVICE PRETTY PLEASE.
Thanks in advance,
Jaymi
acrinym said:
Hey @sd_shadow, any idea what we could do to fix this mess? This is a phone I'm supposed to return.
Click to expand...
Click to collapse
If it's a warranty return it shouldn't matter
Related
Hi guys, i am new to this forum and would like some help on restoring a bricked (don't know how bad) android tablet. It first got jammed on the start screen logo because of an app that i uninstalled the wrong way. I then tried to reboot it and that is where the problem started, so I decided to try flash a nexus or TWRP or a CWM image with amd with no avail but my phone was detected. CMD kept on displaying that the size of the images were too large, but the RAMDISK.img flashed. After this I also tried sideloading the nexus 5 image, since that's all I could find in the bootloader that actually worked. Unfortunately, as soon as i copied it showed 'aborted' therefore I rebooted it and the cycle began
The battery then drained and now I can't access recovery mode or fast boot (only the menu) which eventually goes off after a few seconds, and when I plug it in, it shows the critical battery sign then tries to boot, but doesn't charge and does this repeatedly. It doesn't display the boot image at all.
It is an Alps LC 007 Tab with some MTK kernel and a custom recovery and bootloader. Is there any hope of reviving my tablet? Please help????????
dothwolo said:
Hi guys, i am new to this forum and would like some help on restoring a bricked (don't know how bad) android tablet. It first got jammed on the start screen logo because of an app that i uninstalled the wrong way. I then tried to reboot it and that is where the problem started, so I decided to try flash a nexus or TWRP or a CWM image with amd with no avail but my phone was detected. CMD kept on displaying that the size of the images were too large, but the RAMDISK.img flashed. After this I also tried sideloading the nexus 5 image, since that's all I could find in the bootloader that actually worked. Unfortunately, as soon as i copied it showed 'aborted' therefore I rebooted it and the cycle began
The battery then drained and now I can't access recovery mode or fast boot (only the menu) which eventually goes off after a few seconds, and when I plug it in, it shows the critical battery sign then tries to boot, but doesn't charge and does this repeatedly. It doesn't display the boot image at all.
It is an Alps LC 007 Tab with some MTK kernel and a custom recovery and bootloader. Is there any hope of reviving my tablet? Please help????????
Click to expand...
Click to collapse
I can access preloader with windows SP Flash Tool but nothing else? Isn't there some kind of way to flash images with the flash tool?
Please help:crying:
dothwolo said:
I can access preloader with windows SP Flash Tool but nothing else? Isn't there some kind of way to flash images with the flash tool?
Please help:crying:
Click to expand...
Click to collapse
Seriously? I came to this forum with a mild situation and now I've completely bricked my mt65xx device doing things I didn't know how to do. It's been 3 days!
DAY 1
I try use adb to undo soft brick but the battery dies and I can't access the bootloader or fastboot or recovery but just the boot menu.
DAY 2
I try use the SPF tool with not much knowledge from the YouTube videos I watched and I end up formatting my device with only a backup of the system.img (which isn't even an image).
DAY 3
The device is completely unresponsive after trying over and over with a little bit more knowledge from research.
Now I'm wondering what would've happened if I got a response at least to catch my attention and stop me from doing things without knowledge of what I'm doing. I'm not forcing People to help but at least reply so that I stop. 108 views and no reply. Sorry if I sound a bit too grumpy but I am not happy. .......
dothwolo said:
Seriously? I came to this forum with a mild situation and now I've completely bricked my mt65xx device doing things I didn't know how to do. It's been 3 days!
DAY 1
I try use adb to undo soft brick but the battery dies and I can't access the bootloader or fastboot or recovery but just the boot menu.
DAY 2
I try use the SPF tool with not much knowledge from the YouTube videos I watched and I end up formatting my device with only a backup of the system.img (which isn't even an image).
DAY 3
The device is completely unresponsive after trying over and over with a little bit more knowledge from research.
Now I'm wondering what would've happened if I got a response at least to catch my attention and stop me from doing things without knowledge of what I'm doing. I'm not forcing People to help but at least reply so that I stop. 108 views and no reply. Sorry if I sound a bit too grumpy but I am not happy. .......
Click to expand...
Click to collapse
Sorry for the late response ... we are trying to help, but xda is not our fulltime job. We do it voluntarily ... next to our jobs and real lifes.
As there is nothing about your exact device on xda, here are some useful threads about similar devices:
[UTIL][WIN][MT65xx] MTK Droid Root & Tools | MediaTek Android Smartphone by rua1
[GUIDE] How to 'unbrick' your Mediatek MT65xx by yuweng
[TUT] [TOOL] MT65xx ROM Porting by yuweng
If nothing of the above helps in your case, please ask in the [Ask Any Question][Newbie Friendly] by dagger thread.
Keep in mind to provide as much information as possible to get best help and advices.
Hope that you will find a way to unbrick your device.
Problem: You have purchased a China Lenovo S856 smartphone and tried to flash ROW ('Rest of World') firmware to it for whatever reason. You now have a softbricked phone that won't boot past the Lenovo screen.
Solution: Download the following files, which are a little tutorial with pictures, as well as the correct China firmware for your s856 and the Flashing tool to use....https://drive.google.com/open?id=0B6knvSQRiKPzQTMtaXFXZEFNbHc https://drive.google.com/open?id=0B6knvSQRiKPzRTk4ZTB3c1VDdzA https://drive.google.com/open?id=0B6knvSQRiKPzWVA2UENuY1NYTkk
All the solutions I have seen so far were sketchy at best and very difficult to comprehend, let alone use to unbrick your phone. This is what worked for me, and my attempt to help anyone else with the above problem.
That is all, and good day to you.
Thanks for your help, but my problem looks very difficult now, because the system cannot recognize the phone and the phone refuse to boot on. What do you advice?
way2aware said:
Problem: You have purchased a China Lenovo S856 smartphone and tried to flash ROW ('Rest of World') firmware to it for whatever reason. You now have a softbricked phone that won't boot past the Lenovo screen.
Solution: Download the following files, which are a little tutorial with pictures, as well as the correct China firmware for your s856 and the Flashing tool to use....https://drive.google.com/open?id=0B6knvSQRiKPzQTMtaXFXZEFNbHc https://drive.google.com/open?id=0B6knvSQRiKPzRTk4ZTB3c1VDdzA https://drive.google.com/open?id=0B6knvSQRiKPzWVA2UENuY1NYTkk
All the solutions I have seen so far were sketchy at best and very difficult to comprehend, let alone use to unbrick your phone. This is what worked for me, and my attempt to help anyone else with the above problem.
That is all, and good day to you.
Click to expand...
Click to collapse
Prajiro said:
Thanks for your help, but my problem looks very difficult now, because the system cannot recognize the phone and the phone refuse to boot on. What do you advice?
Click to expand...
Click to collapse
Hello...
My system did not recognize my phone, either. Nor would it boot up... it was bricked. This tutorial is for people who are exactly in your situation. I would suggest downloading the files I have uploaded, and reading the tutorial.
way2aware said:
Hello...
My system did not recognize my phone, either. Nor would it boot up... it was bricked. This tutorial is for people who are exactly in your situation. I would suggest downloading the files I have uploaded, and reading the tutorial.
Click to expand...
Click to collapse
Finally got the process started,...but after 7s I got and error message Reached the end of the file.(0x80070026: Receiving hello packet)
Could it be my PC (win 10 32 bit) problem or what do you think?
This happened to me as well, the first and second time I tried the flash. There is a trick which worked for me... I pulled the battery out and put it back in and while holding the volume 'up' button, I plugged my phone into my computer usb port and let windows install the driver. It took a few seconds and then I clicked 'refresh' on the Miflash window, which I had left on. At this point the 'flash' button became available and I clicked on it. This time the flash was successful. Try it.
Hi guys its the 3rd time that i post here in the forum hopping to restore my "dead" Moto G3 XT1543 1GB RAM Snapdragon 410 (MSM8916).
Some days ago I've unlock my phone bootloader in order to install CM14.1 and i did it with success! but my sim card wasn't working, so, I tried to look for a solution. And I found a video on youtube that showed the supost fix for this issue, but i was wrong. I've flashed the file which broke my phone immediately and now my phone doesn't do ANYTHING!! Well, at least it shows on my computer as QDLoader 9008 but for now on I dont know what I have to do! I know that the easiest way to fix it is buying another motherboard, but I think that still hope for someone to find the way to fix it! Well, if the pc recognizes the processor so there's something to be done right?
I had searched all over the internet during this week, and I found some interesting possible ways to fix it, but im not a developer so I need help and opinions from other people.
1)The first way was to change the mode to 9006 aka diag mode though some files wich in theory allows you to acces eMMC partition and restore all the 29 inside partition and recover your phone. The problem is: I don't know how to change it to diag mode, but yea i have the needed files, and i don't have the tool to acces the eMMC of the phone and i dont have a backup of the partitions to write over the corrupted ones.
2)The second way was to use this tutorial *http://www.droidsavvy.com/unbrick-qualcomm-mobiles/* that i still havent tried since my phone isn't with me right now. So, in this supose way we can contact the phone through a tool called QFIL and try to "Inject" the bootloader or whatever, in the phone to foce him into a bootloop and so enabling the fastboot mode which allows you to install a rom later on. well the problem for this one is, i dont know if it works on your moto g3 but i gonna try. (if you try this option tell me and i gonna upload the needed files because the folder avaliable in the link contais files for the processor Snapdragon 610 and Moto G3 processor is a 410)
3) The third way is a Jtag repair in a authorized store, but i dont think Moto G3 have a jtag fix (im posting this possibility because i could be wrong)
4) In this way could be a updated Blank Flash actually used to hard unbrick the Moto G1 and I Guess the G2? But im not a developer and I dont know too much about programing, but i'm sure someone out there is a pro
5) Use the QPST which is kinda the same thing as use a eMMC tool? ( again im not a dev ) and from what i got, is used to config all your phone from scratch. would be good if there's a tuto out there
6) Sit and wait till Motorola release the MBM-CI 5.0 which from what i got is used like the Blank Flash or used to make a Blank Flash idk
AGAIN!!! IM NOT A DEV, THIS IS JUST SOME WAYS THAT I FOUND OUT THERE ON THE INTERNET WHICH COULD BE USED TO FIX YOUR BELOVED MOTO G3!! SO, I'M SHARING ALL MY RESEACH WITH YOU GUYS BECAUSE IS A SHAME HAVE TO DUMP MY DEVICE LIKE THAT OR HAVE TO EXPEND LIKE R$ 500 IN A NEW MOTHER BOARD WHICH IN DOLLAR ITS LIKE 1600 U$D (this is Brazil guys yea it's a horrible country T_T ) SO I HOPE THAT THIS POST HELPS SOMEBODY AND IF YOU GOT SOME INFO SHARE TO HELP US TRY TO FIX THE PHONE!
hey you got successful??? in unbricking your phone?
[email protected] said:
hey you got successful??? in unbricking your phone?
Click to expand...
Click to collapse
not yet, i send my phone to an authorized i hope they can fix it via programming box
IkkyShad said:
not yet, i send my phone to an authorized i hope they can fix it via programming box
Click to expand...
Click to collapse
Ohhkay
You'll need blankflash for this device, that's the only thing which will take it back to bootloader mode so you can flash a firmware. Blankflash is usually found in stock firmwares, however the chances are kinda low
siredux said:
You'll need blankflash for this device, that's the only thing which will take it back to bootloader mode so you can flash a firmware. Blankflash is usually found in stock firmwares, however the chances are kinda low
Click to expand...
Click to collapse
yeah i know, i tried everything in 3 weeks but with no success, unfortunately the moto g3 firmwares are kinda different from other firmwares
IkkyShad said:
yeah i know, i tried everything in 3 weeks but with no success, unfortunately the moto g3 firmwares are kinda different from other firmwares
Click to expand...
Click to collapse
Can we even try a firmware of Moto g 2 Nd gen ,to get into fastboot anyhow ? Bcoz Moto g 2nd gen is hardbirck recoverable
[email protected] said:
Can we even try a firmware of Moto g 2 Nd gen ,to get into fastboot anyhow ? Bcoz Moto g 2nd gen is hardbirck recoverable
Click to expand...
Click to collapse
yeah, you can try but the models are different and also the partitions inside the phone... try it out and if it works you can post here
No u can't try the Moto g2 firmware..... As Moto g2 is also waiting for MBM CI 5 file for lollipop and Motorola is not releasing those file needed for blankflash
Sorry to bump needlessly but has there been any progress in this regard?
Has anyone found a solution or blankflash files?
I managed to hardbrick my device while trying to resize the system and userdata partitions (stupid, I know)
Jaysin365 said:
Sorry to bump needlessly but has there been any progress in this regard?
Has anyone found a solution or blankflash files?
I managed to hardbrick my device while trying to resize the system and userdata partitions (stupid, I know)
Click to expand...
Click to collapse
No... And just like previous Moto devices, it is unlikely we will ever get the necessary files.
Same situation, any updates?
I'm currently facing the same situation with XT1543, it ran Marshmallow 6.0 stock (came with Lollipop) and suddenly it hard bricked (last time i checked there were no software updates and even if there were, the phone would not restart itself to update). I ran blankflash but the results were these:
greeting device for command mode
opening device: \\.\COM3
OKAY [ 0.001s]
greeting device for command mode
FAILED (blank-flash:greet-device:error reading packet)
Click to expand...
Click to collapse
I appreciate any help!
gibarsin said:
I'm currently facing the same situation with XT1543, it ran Marshmallow 6.0 stock (came with Lollipop) and suddenly it hard bricked (last time i checked there were no software updates and even if there were, the phone would not restart itself to update). I ran blankflash but the results were these:
I appreciate any help!
Click to expand...
Click to collapse
If you can't get to the bootloader, it's toast... we do not have the proper files to do a Qload reflash, and the chances of getting them are near zero.
Try the usual... drain the battery and hold Power+Vol Dn (normal method to access bootloader) or press and hold Power+Vol Dn for 15-30 seconds, if you can't get to the bootloader there is NO recovery method available. Sorry.
acejavelin said:
If you can't get to the bootloader, it's toast... we do not have the proper files to do a Qload reflash, and the chances of getting them are near zero.
Try the usual... drain the battery and hold Power+Vol Dn (normal method to access bootloader) or press and hold Power+Vol Dn for 15-30 seconds, if you can't get to the bootloader there is NO recovery method available. Sorry.
Click to expand...
Click to collapse
Thanks for the quick reply, I will post my results here whether it's successful or not.
acejavelin said:
If you can't get to the bootloader, it's toast... we do not have the proper files to do a Qload reflash, and the chances of getting them are near zero.
Try the usual... drain the battery and hold Power+Vol Dn (normal method to access bootloader) or press and hold Power+Vol Dn for 15-30 seconds, if you can't get to the bootloader there is NO recovery method available. Sorry.
Click to expand...
Click to collapse
+1 on this.
The only other thing I would do is take it apart and detach one wire from battery and short that lose wire to the other wire (short the phone, NOT the battery!) for 15 sec or so and reconnect wire to battery and put phone back together and try boot to bootloader (power plus vol-dn). If no go, at that point if it were worth it I would give it to ATT to fix, or toss it in the drawer for parts.
I too hard bricked my g3.
My PC detected it as Qualcomm 9008 mode
Plz help how to solve this
Durga teja said:
I too hard bricked my g3.
My PC detected it as Qualcomm 9008 mode
Plz help how to solve this
Click to expand...
Click to collapse
Tell us how you bricked it?
KrisM22 said:
Tell us how you bricked it?
Click to expand...
Click to collapse
Rooted and installed twrp nd framework on 5.0
Bro accidentally updated to 6.0 on WiFi
Blank screen. No bootloader.
LED blinkinh
Durga teja said:
Rooted and installed twrp nd framework on 5.0
Bro accidentally updated to 6.0 on WiFi
Blank screen. No bootloader.
LED blinkinh
Click to expand...
Click to collapse
beyond my knowledge. Hopefully someone will jump in.
Durga teja said:
Rooted and installed twrp nd framework on 5.0
Bro accidentally updated to 6.0 on WiFi
Blank screen. No bootloader.
LED blinkinh
Click to expand...
Click to collapse
If there is no bootloader and the only thing that can be seen on the computer is QdLoader mode, it's done... Send it to Moto for repair or send it to the recycler, there is no fix we can do.
Ok, i have a doogee x5 pro phone and i tried to root it by flashing twrp recovery using sp flash tools. While flashing i got the error "PMT Changed for the rom it must be download". So i did a small research on internet and i found out that i needed to format everything except bootloader. This succeded. So after that i tried to install the firmware with this succeding to. Unfortunately the time i tried to turn phone on it was dead. SP Flash Tools wont detect it anymore. Please help me cause the phone is not mine and its brand new! I can rate my self as moderate android user. :crying:
i think i have a bigger problem... I downloaded a stock rom for doogee max pro(cause i just realised it wasnt just pro it was max pro) and it didnt seem to be recognised again. Any help would be appreciated. I constantly keep trying to raise it from the deads. Thanks!
Ap0s said:
i think i have a bigger problem... I downloaded a stock rom for doogee max pro(cause i just realised it wasnt just pro it was max pro) and it didnt seem to be recognised again. Any help would be appreciated. I constantly keep trying to raise it from the deads. Thanks!
Click to expand...
Click to collapse
On mtk devices a preloader is independently installed, it should be almost impossible to destroy, I owned a x5 pro and had best success to flash it with sp flash by taking out the battery, press flash button and plug it in...
The second huge issue I see is when you used the specific flash tool format option you very, very likely killed the nvram partition which contained the imei, so you'll have to fix this too by generating a new one and using mtk engineer mode which is well described and to find on Google..
But let's go step by step. Check without battery, or if it's a non replaceable you'll need find the reset button..
i have tried before without battery and i tried just now but nothing. Its very weird it was detected before and now no in same and another machine. I am pretty confused and stressed. Hope i didnt do any physical damage.. :crying:. THANKS!
starting to get pretty stressed omg! and is there a difference between MT6737M and MT6737?
i came to the point im starting to lose my mind... tried everything i could, i have 5 days left to repair this phone and i dont wanna pay 85 euros for this. SP Flash Tools wont detect the phone. Tried almost 5 different scatter files,2 different PCs and different mtk drivers. Im losing my mind already
UPDATE: I almost fixed it! I had flashed wrong preloader so phone wasn't recognized by SP Flash Tool. I fixed preloaded with a little trick from here: link. After that i flashed stock rom downloaded from doogee.cc but phone will not boot resulting in a total black screen. When i hot Power + Vol Up it takes me to another screen:
Select Boot Mode:
Recovery
Bootloader
Normal
Doesn't matter which boot mode i choose i just get a total black screen which means i get nothing. Idk what is happening! Any further help would be appreciated! I constantly try to bring it back working with little success and small improvements.
Last UPDATE: FIXED my phone had no juice left inside so couldnt complete boot proccess. Now its all good running Btw someone must pin this META trick link i send on my previous post cause im sure more people out there have preloader issues!!! Thank you everyone!!
Sam Nakamura said:
On mtk devices a preloader is independently installed, it should be almost impossible to destroy, I owned a x5 pro and had best success to flash it with sp flash by taking out the battery, press flash button and plug it in...
The second huge issue I see is when you used the specific flash tool format option you very, very likely killed the nvram partition which contained the imei, so you'll have to fix this too by generating a new one and using mtk engineer mode which is well described and to find on Google..
But let's go step by step. Check without battery, or if it's a non replaceable you'll need find the reset button..
Click to expand...
Click to collapse
And yes i couldnt flash it with battery only with!
Hello everybody,
I have a bootloop issue with a Lenovo P11 Pro. It is stuck in a bootloop and keeps restarting 1 min after Lenovo logo.
I have tried anything from Hard Reset to Rescue Smart Assistant Flashing and Qfil Flashing. It flashes successful but Tablet still doesn't want to boot up.
Have any ideas? I bought it like that so don't know what the person before me did to it.
Tablet seems to charge.
Thanks in advance for all the ideas!
emybuse said:
Hello everybody,
I have a bootloop issue with a Lenovo P11 Pro. It is stuck in a bootloop and keeps restarting 1 min after Lenovo logo.
I have tried anything from Hard Reset to Rescue Smart Assistant Flashing and Qfil Flashing. It flashes successful but Tablet still doesn't want to boot up.
Have any ideas? I bought it like that so don't know what the person before me did to it.
Tablet seems to charge.
Thanks in advance for all the ideas!
Click to expand...
Click to collapse
I haven't had this situation, but what firmware have you tried flashing? Have you read the threads about the region codes, and how the firmware has to match them (in the latest firmwares) or the region code has to be changed. I would try flashing an international firmware, and if that doesn't work try a china firmware. There are only two regions I think, so one of those should work.
I could have got the wrong end of the stick with this as I've not been in this situation, so not very carefully read those threads yet, so just a suggestion!
mdurkin said:
I haven't had this situation, but what firmware have you tried flashing? Have you read the threads about the region codes, and how the firmware has to match them (in the latest firmwares) or the region code has to be changed. I would try flashing an international firmware, and if that doesn't work try a china firmware. There are only two regions I think, so one of those should work.
I could have got the wrong end of the stick with this as I've not been in this situation, so not very carefully read those threads yet, so just a suggestion!
Click to expand...
Click to collapse
Rescue and Smart Asistant does the job automaticaly and it flashed TB-J706L_S620103_211124_ROW. And with Qfil I tried the TB-J706L_S243005_210601_ROW.
emybuse said:
Rescue and Smart Asistant does the job automaticaly and it flashed TB-J706L_S620103_211124_ROW. And with Qfil I tried the TB-J706L_S243005_210601_ROW.
Click to expand...
Click to collapse
RSA did not succeed in my case.
$ fastboot set_active a did the trick for me!
Amatöhr said:
RSA did not succeed in my case.
$ fastboot set_active a did the trick for me!
Click to expand...
Click to collapse
Fail : not unlock, help me
I didn't think I had to, when I plug in the tablet it pops up with the name and everything.
Hi, I have the same issue with a Tab 11 pro gen 2. Could you let me know how to solve it? I can't even find the recovery, and tried all button combinations. I can only go to fastboot or meta modes.
im literally stuck on this ( fastboot ) screen... it boots straight to this screen. If i plug the device into my pc it says device not recognised and none of the drivers seem to work. I have tried everything to shut it down so i can try flash via EDL, but the power button just takes me back to fastboot again...
I'm having the same reboot issue 1 minute or less after fully booting. I have no idea how to fix it