[POLL] Dead EMMC - Nexus 5 Q&A, Help & Troubleshooting

Hello.
I'm trying to centralize all the EMMC issues in order to see if there's a common link. Feel free to post some details as well after you answer the poll.

There are 2 different common links
1) faulty emmc
2) idiots

rootSU said:
There are 2 different common links
1) faulty emmc
2) idiots
Click to expand...
Click to collapse
I'm trying to see if there's for example a given toolkit that would corrupt your emmc - could help the noobs who brick their phone after using who know what toolkit. We all know that no matter how many times we warn people , some will still use rootkits and AIO toolkits - best we can do is keep them away from the really damaging ones.

You'll never narrow it down.

rootSU said:
You'll never narrow it down.
Click to expand...
Click to collapse
In the last week we had 4 bricked EMMCs . Out of those there's
- unknown (http://forum.xda-developers.com/google-nexus-5/help/bootloop-nexus-5-problem-persist-t2962356 )
- Toolkit/Rootkit http://forum.xda-developers.com/goo...ed-nexus-5-t2522020/post51345473#post51345473
-Possible rootkit , TWRP 2.6.4.3 http://forum.xda-developers.com/google-nexus-5/help/nexus-5-32gb-mobile-internal-memory-t2969559
- unknown , http://forum.xda-developers.com/google-nexus-5/help/accidentally-bricked-nexus-t2967493
I'm pretty sure if we collect more data - maybe some logs and logcats as well we might be able to find out if there's a specific chain of events that will brick them , bad quality emmcs or just abuse .
Also , I want to see if the 16gb version is less prone to it than the 32gb. From what I dug in the forums it does seem so - though it might be only my subjective impression since I didn't centralize any data yet.

My point is, even if a user was using a toolkit at the time of nand failure, there is no way on earth you van categorically say that the failure was caused by the toolkit. Yes, people shouldn't use toolkits as they don't know what they're doing, but also let's not also attribute faulty hardware, stupid people or just bad luck to toolkits too.
I'm sorry, but this thread won't help anyone.

My problem with emmc brick started when lg sent me back the phone that is still broken.
Before this, my device was only in bootloop at the google logo.

nexus 5 emmc chip problem
I baught a new nexus 5 after upgrading to lollipop Automatically its gone dead but when i downgrade to kit kat mobile was on but not upgrading to lollipop and imei was unknown ,baseband unknown and storage was corrupt and nothing is working only wifi is working
I show this to software guys but they are saying that the emmc chip Is not working is their any solution for it
Need help please

Flash stock cache image

rootSU said:
Flash stock cache image
Click to expand...
Click to collapse
How ? Im a newbie i really don't know about this please guide me

faizanfarooq86 said:
How ? Im a newbie i really don't know about this please guide me
Click to expand...
Click to collapse
Take a look at his signature.

faizanfarooq86 said:
How ? Im a newbie i really don't know about this please guide me
Click to expand...
Click to collapse
Using fastboot. All guides and info threads are in general

faizanfarooq86 said:
How ? Im a newbie i really don't know about this please guide me
Click to expand...
Click to collapse
Download the factory image and extract it. In there is a zip, extract it too. in there you'll find the cache image
fastboot flash cache cache.img
See rootSU's sticky in the general forum and look for how to return to stock, flash a factory image
Sent from my Nexus 9 using XDA Free mobile app

i think that i had a nand faulty in the beginning but the phone show juste lg logo and bootloop and he can enter to recovery and download mode it was on 4.4.2 but i didn't know and i flashed a lollipop image with toolkit and the phone was dead totally no recovery no download not charging and not booting at all , juste QHSUSB_Bulk or modem driver and usb composite device , i tried lg flash tool , lgnpst , qpst , diagbord and nothing was working juste unknown device or unknown mode ,
someone tell me that is a nand faulty but i don't know how to fix that
sorry for my english , i am from Algeria and there is no LG service

sahouli31 said:
i think that i had a nand faulty in the beginning but the phone show juste lg logo and bootloop and he can enter to recovery and download mode it was on 4.4.2 but i didn't know and i flashed a lollipop image with toolkit and the phone was dead totally no recovery no download not charging and not booting at all , juste QHSUSB_Bulk or modem driver and usb composite device , i tried lg flash tool , lgnpst , qpst , diagbord and nothing was working juste unknown device or unknown mode ,
someone tell me that is a nand faulty but i don't know how to fix that
sorry for my english , i am from Algeria and there is no LG service
Click to expand...
Click to collapse
I think that's a different issue.. I know @bitdomo wanted to test something on nexus 5 in that state

rootSU said:
I think that's a different issue.. I know @bitdomo wanted to test something on nexus 5 in that state
Click to expand...
Click to collapse
i know but it's missing for long , i am waiting for him for so long , i hope so he will be fine

jd1639 said:
Download the factory image and extract it. In there is a zip, extract it too. in there you'll find the cache image
fastboot flash cache cache.img
See rootSU's sticky in the general forum and look for how to return to stock, flash a factory image
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
But for this i think i need to put my phone on fastboot but their is no fastboot in my device now what Should i do only 4 options are coming on pressing volume down + power
Start, restart bootloader, recovery mode and power off
Is their any guy who can help me in step by step guidance

faizanfarooq86 said:
But for this i think i need to put my phone on fastboot but their is no fastboot in my device now what Should i do only 4 options are coming on pressing volume down + power
Start, restart bootloader, recovery mode and power off
Is their any guy who can help me in step by step guidance
Click to expand...
Click to collapse
Fastboot is done from the bootloader itself, it is not a menu option. Step by step guides are in general > sticky roll-up

im really stuck in the start of adb and fastboot is their any guy to whom should i show my nexus 5 imei gone. storage corrupt and baseband null even camera is also not working.
i live in pakistan please prefer a guy who can resolve my problem

is there any way to recover emmc fault?

Related

Nexus S i9020 Pit file

Hi all
Just recover the phone from dead boot, now it able to go into download mode. I just want to flash back to stock, going to do that with odin but it need the pit file. i've search the web, forum for the pit file but unable to locate one, if anyone have it or know where to dl please let me know
thanks
tdx3000 said:
Hi all
Just recover the phone from dead boot, now it able to go into download mode. I just want to flash back to stock, going to do that with odin but it need the pit file. i've search the web, forum for the pit file but unable to locate one, if anyone have it or know where to dl please let me know
thanks
Click to expand...
Click to collapse
If you can get into fastboot then don't use Odin. Assuming you have fastboot working use these
https://developers.google.com/android/nexus/images
http://forum.xda-developers.com/showthread.php?t=1785672&highlight=clean+install+4+1+1
http://forum.xda-developers.com/showthread.php?t=1572307&highlight=clean+install
the phone only go into download mode
Hi
could you please tell me how u were able to recover from dead boot...using which method & how were u able to go from download
thanks
tdx3000 said:
Hi all
Just recover the phone from dead boot, now it able to go into download mode. I just want to flash back to stock, going to do that with odin but it need the pit file. i've search the web, forum for the pit file but unable to locate one, if anyone have it or know where to dl please let me know
thanks
Click to expand...
Click to collapse
IndianKarmas said:
Hi
could you please tell me how u were able to recover from dead boot...using which method & how were u able to go from download
thanks
Click to expand...
Click to collapse
Just use any tool which is capable of repairing dead boot like Riff-box, Ort jtag and others
For me i use Riff-box to repair dead boots
Br
Msajum
I guess his phone bricked when he took the battery out when booting. And, when he uses Resurrector, he chosse galaxy s option, but not the Nexus S, then, the phone goes to download mode witch one always give the pit partition error.
Nobody (i guess) really know why this bug happens, but in the most of cases, it's about emmc, if you have an old phone, you can try, maybe...
How difficult is the hardware mod...I have zero experience with soldering but rather than having a dead brick would take chances ...tried taking phone to few phone guys in Toronto who had no clues...so thinking of trying hardware mod myself...would appreciate any guidance
samcortez said:
I guess his phone bricked when he took the battery out when booting. And, when he uses Resurrector, he chosse galaxy s option, but not the Nexus S, then, the phone goes to download mode witch one always give the pit partition error.
Nobody (i guess) really know why this bug happens, but in the most of cases, it's about emmc, if you have an old phone, you can try, maybe...
Click to expand...
Click to collapse
IndianKarmas said:
How difficult is the hardware mod...I have zero experience with soldering but rather than having a dead brick would take chances ...tried taking phone to few phone guys in Toronto who had no clues...so thinking of trying hardware mod myself...would appreciate any guidance
Click to expand...
Click to collapse
Don't do it then. You will destroy your phone completely.
Just look out for someone (in real-life) that can do it for you.
nexus s
samcortez said:
I guess his phone bricked when he took the battery out when booting. And, when he uses Resurrector, he chosse galaxy s option, but not the Nexus S, then, the phone goes to download mode witch one always give the pit partition error.
Nobody (i guess) really know why this bug happens, but in the most of cases, it's about emmc, if you have an old phone, you can try, maybe...
Click to expand...
Click to collapse
Hi
i have the same problem my nexus s shows download mode only when used galaxy s resurrector .
no output when nexus s resurrector.
plz help me
I didn't get any result. Now, what I know is that it might be a issue on EMMC chip. Thats all.

[Q] my note 10 is stuck in booting

Hey guys,
Ok here is the story I got a gt-n8000 , but an edition that got 1gb of ram , dont know how !! any ways this the issue my note is stuck in booting displaying samsung galaxy note 10.1, i can go into odin mode tried to flash it with JB but it display the same thing, tried 4.0.4 also no difference, tried to push the CWM image successful however holding the power button and volume up, dosen't get it to show up.
-the tablet dosen't switch off , if you pressed the power button what happen is its reboot thats it, I have waited for the battery to drain and then one I put it on the charger it load the booting and get stuck aka the usual
People plzzz help, thanks in advance
Umm OK
Put your tablet in download mode
And tell me what is the product name
If its empty I am sorry to inform you that this is a motherboard problem.
Sent from my GT-N8000 using xda premium
its says:
PRODUCT NAME: GT-N8000
ozmosis60 said:
I got a gt-n8000 , but an edition that got 1gb of ram ... i can go into odin mode tried to flash it with JB
Click to expand...
Click to collapse
hannarecord said:
Put your tablet in download mode and tell me what is the product name. If it's empty I am sorry to inform you that this is a motherboard problem
Click to expand...
Click to collapse
Nah, I think the problem is worse than that- apparently there was a pre-release version of the GT-N8000 with only 1GB of RAM, and the owner also bricked it 'cause the internals were different.
yes I probably have that version, however nothing fails in the process of flashing and nothing hardware wise look bricked, so its just a software problem any advice ??
ozmosis60 said:
yes I probably have that version, however nothing fails in the process of flashing and nothing hardware wise look bricked, so its just a software problem any advice ?
Click to expand...
Click to collapse
Problem is, there doesn't appear to be any publicallly-available builds for that hardware.
I heard that build N8000XXALE2 "baseband N8000XXLE2" might work, do you know where I can find it ??
Try Sammobile.com.
You will need to join to download stock firmwares...
tried there didn't find a thing, any one who knows another firmware that might work ??
any one any advice ??
You are looking for firmware for a device that technically doesn't exist; I don't expect that you'll find any applicable firmware anywhere.
Sorry.

[Q] N 8000 stuck on bootloop

My Tablet was in the charger and it was turned off when i tried to power it , i found it was stuck in a boot loop
i tried to flash a stock ROM using using Odin 3.10 but still nothing changed,
i cant access the recovery mode using the power and volume up key,
but can access the download mode . please help me
Thank you
Got same problem
Ayman87 said:
My Tablet was in the charger and it was turned off when i tried to power it , i found it was stuck in a boot loop
i tried to flash a stock ROM using using Odin 3.10 but still nothing changed,
i cant access the recovery mode using the power and volume up key,
but can access the download mode . please help me
Thank you
Click to expand...
Click to collapse
I got same boot loop problem a week ago after installing a game. I couldn't get into recovery mode but I do have download mode. I have tried flash stock ROM multiple times and it always failed. Today, I brought my device to samsung service center. But guess what, even them couldn't help resolve the issue!!!
I hope someone here are able to help.
wiien said:
I got same boot loop problem a week ago after installing a game. I couldn't get into recovery mode but I do have download mode. I have tried flash stock ROM multiple times and it always failed. Today, I brought my device to samsung service center. But guess what, even them couldn't help resolve the issue!!!
I hope someone here are able to help.
Click to expand...
Click to collapse
Could they even identify the problem ?
Can you access Bootloader? And any custom recovery?
SuperMan(Alex) said:
Can you access Bootloader? And any custom recovery?
Click to expand...
Click to collapse
No i did n`t try , can u please refer to me a link , or explain to me what should i do exactly ?
Ayman87 said:
No i did n`t try , can u please refer to me a link , or explain to me what should i do exactly ?
Click to expand...
Click to collapse
and i cant use " USB Debugging"
http://forum.xda-developers.com/showthread.php?t=2102677
i tried this custom recovery but still looping
same here . i suggest trying different stock firmwares , if i get the fix for this problem i will tell u here
ameer3adel said:
same here . i suggest trying different stock firmwares , if i get the fix for this problem i will tell u here
Click to expand...
Click to collapse
Thank you
Ayman87 said:
Could they even identify the problem ?
Click to expand...
Click to collapse
Well, they said it hit the IC memory (cost around $200). so expensive :crying:
I've tried stock kitkat but still no luck
Ugh guys I'm having the same issues my tablet won't go pass Samsung Galaxy note 10.1 splash screen and can't stay on twrp recovery with out rebooting again. I tried to reflash twrp tar and stock firmware but it always fails and then my PC would say my USB driver or port is unrecognizable or malfunction so I bought another USB charging wire and tried it today and still get the same issues I hope someone can help me and us out asap!!
same here
Hi guys!
same here! my note was charging and I've found it stucked in samsung logo without any reason. I've tried to install almost every version available of stock rom also from different country but no way. I can install also custom recovery but unfortunately I don't have any custom rom to try to install in my sd card. At the current time I really thinking to move to new note 10.1 2014...I'm afraid is some kinda hardware malfunctions. Any update from you guys with same issue?
Andrea
afarnedi said:
Hi guys!
same here! my note was charging and I've found it stucked in samsung logo without any reason. I've tried to install almost every version available of stock rom also from different country but no way. I can install also custom recovery but unfortunately I don't have any custom rom to try to install in my sd card. At the current time I really thinking to move to new note 10.1 2014...I'm afraid is some kinda hardware malfunctions. Any update from you guys with same issue?
Andrea
Click to expand...
Click to collapse
Wow now I'm really start to think it is a Samsung and hardware issue I think these tablets weren't made to be usable for more than 2 years smh is anyone else with this issue running lollipop roms? Jc
The same here, My friend just conntect me, that SAMSUNG does not want to cover charges, due to bootloader says SYSTEM STATUS: custom.
And he never did anything with his tablet.
He got angry and Samsung check the hardware and they find that some chip is broken. But still don't want to fix it due to custom issue.

SoftBricked Mate 7 Please Help

Hi,
I have root my phone. disabled some unnecessary apps, but i decided to factory reset, but when i open the phone top and bottom buttons were gone, no notifications. Now I cant do anything. How can i restore the whole OS back?
I have bring the stock recovery back but now i stuck!
now i cannot enter to bootlader
Trying with adb but it says not authorized. Authorize notify cant appear on screen i think its because huawei home not work properly.
And I cant even install anything from google play or local apk.
I think its bricked please help...
http://forum.xda-developers.com/showthread.php?t=3075332
did you try this?
Sent from my HUAWEI MT7-TL10
Easy Computer said:
http://forum.xda-developers.com/showthread.php?t=3075332
did you try this?
Sent from my HUAWEI MT7-TL10
Click to expand...
Click to collapse
Hi,
I have tried almost every steps except latest version update, because there is no latest version on Huawei Turkish website, latest one shows B133 but mine was B137, so it gives an error while starting the update from dload folder.
Hisuite doesnt recognize the phone.
Now I am downloading Huawei MT7-L09 CEE&Nordic European Channel V100R001C00B137SP03 Android 4.4.2 EMUI 3.0 This is not Turkish version but i hope I can install it with 3 button update procedure...
No luck...
It gave me "software install failed" error...
Now im scared to factory reset my phone... I hope you get to find a solution bro.
EzerchE said:
No luck...
It gave me "software install failed" error...
Click to expand...
Click to collapse
Easy Computer said:
Now im scared to factory reset my phone... I hope you get to find a solution bro.
Click to expand...
Click to collapse
Hi, i find a solution,
actually i find a way to enter fastboot mode without inside of android os.
connect mate 7 to pc, while its connected press 3 buttons and hold,
it will open in recovery mode adb,
then command: fastboot bootloader
you are in fastboot.
But now i bricked it so bad mistakenly.
Its enters looped rescue mode but it doesnt connects to fastboot.
But i have find a solution for it too.
While its in bricked rescue mode press and hold Volume down + power buttons,
it will enters to fastboot mode.
Now i am trying to flash files to repair rescue mode but i still didnt find how to repair it...
If you are in fadtboot mode you should be able to flash the stock recovery (the correct one!!!) via adb command. Then try 3buttons procedure. Please be carefull with the sd card, since most of them don't work in 3b mode. Try several btand of SD.
i hope you get it to work again. good luck bro :good:
EzerchE said:
Hi, i find a solution,
actually i find a way to enter fastboot mode without inside of android os.
connect mate 7 to pc, while its connected press 3 buttons and hold,
it will open in recovery mode adb,
then command: fastboot bootloader
you are in fastboot.
But now i bricked it so bad mistakenly.
Its enters looped rescue mode but it doesnt connects to fastboot.
But i have find a solution for it too.
While its in bricked rescue mode press and hold Volume down + power buttons,
it will enters to fastboot mode.
Now i am trying to flash files to repair rescue mode but i still didnt find how to repair it...
Click to expand...
Click to collapse
tuddu said:
If you are in fadtboot mode you should be able to flash the stock recovery (the correct one!!!) via adb command. Then try 3buttons procedure. Please be carefull with the sd card, since most of them don't work in 3b mode. Try several btand of SD.
Click to expand...
Click to collapse
Hi,
I flashed stock: boot.img, recovery.img, custom.img, system.img and cache.img inside from fastboot mode but no luck...
It gives this error immediately after reboot:
Error!
Func NO: 12 (FUNC_LOAD_IOM3)
Error NO: 1
And can't enter 3 buttons upgrade procedure
I think some system files are missing and it doesnt boot or enter to recovery mode...
Its so sad there is not so much users and professional support about Mate 7. I find the ways to enter bootlader without entering the OS by myself.
But its so easy to brick the phone so all users be very careful when flashing recovery and wiping the phone. As for as i know there is no way to fix my problem even by Huawei technical services. (A guy from another forum, sent his bricked Mate7, they returned the money to him he tolds..)
I could'nt repair the phone so I returned it to seller, thanks for the seller's return policy 14 day no rules accepts return. So I sent my device to seller and returned my money back. I dont know which device should I get.
Good luck all.
EzerchE said:
Its so sad there is not so much users and professional support about Mate 7. I find the ways to enter bootlader without entering the OS by myself.
But its so easy to brick the phone so all users be very careful when flashing recovery and wiping the phone. As for as i know there is no way to fix my problem even by Huawei technical services. (A guy from another forum, sent his bricked Mate7, they returned the money to him he tolds..)
I could'nt repair the phone so I returned it to seller, thanks for the seller's return policy 14 day no rules accepts return. So I sent my device to seller and returned my money back. I dont know which device should I get.
Good luck all.
Click to expand...
Click to collapse
Hi Ezerche. I'm so sorry your phone got bricked and you couldn't repair... I don't know how to root and I couldn't help you. What did you do wrong? I saw on this forum other users who had successfully rooted mate 7.
Now I think I will never root this phone, my 30 days return policy has expired. SO there was no way to repair your phone?
I found your problem on an chinese forum: https://translate.google.ro/transla....vmall.com/thread-3432260-1-1.html&edit-text=
and in italian forum : https://translate.google.ro/transla...mate-7-rescue-mode.html#post344249&edit-text=
You got lucky because you got your money back. What did you told them what happend with the phone? You told them the truth or something else?
If you can live without root you can get another mate 7.
alexre123 said:
Hi Ezerche. I'm so sorry your phone got bricked and you couldn't repair... I don't know how to root and I couldn't help you. What did you do wrong? I saw on this forum other users who had successfully rooted mate 7.
Now I think I will never root this phone, my 30 days return policy has expired. SO there was no way to repair your phone?
I found your problem on an chinese forum: https://translate.google.ro/transla....vmall.com/thread-3432260-1-1.html&edit-text=
and in italian forum : https://translate.google.ro/transla...mate-7-rescue-mode.html#post344249&edit-text=
You got lucky because you got your money back. What did you told them what happend with the phone? You told them the truth or something else?
If you can live without root you can get another mate 7.
Click to expand...
Click to collapse
Hi Alex,
I have rooted my phone, problem happened while i am wiping the boot, system and cust from CWM Recovery before the install new rom. I think its deleted something about sensors (on chinese forum they talking about iom3 error is related with sensors)
So phone didnt boot again.
I returned it to seller without any excuse. I just said I didnt satisfied with the phone. And they accept return and paid the money back in same day.

There's any hope for hard bricked Moto G3? (no fastboot, Qdloader 9008)

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.

Categories

Resources