Conditon :
Can't boot up into anything (Fastboot, recovery)
No Mi Logo
No Vibration
*Phone goes into EDL WITHOUT having to touch the pins on the mobo*
So, my phone was working like 3 days ago, until today it just went to "Red Light Blinking and Nothing Else", So i searched around the internet and basically on YT i got videos like "Heating up the Power IC Fixes this" but i really didn't wanted to try it so i went again and thought maybe i need to flash the Phone so i downloaded the "Global Stock Rom" so i then took the back cover off of my phone and plugged it the USB Cable and i saw "QualComm HS-USB QLoader 9008" which is right i guess and tried to flash it via MiFlash Tool. And indeed i got error BUT in sequence.
1st one was "cannot recieve hello packet"
which i solved by reconnecting my phone
Then
2nd "Object reference not set to an instance of an object"
I only got this ONCE, searched around again and found out that it's something with WRONG ROM type. So i redownloaded the ROM and got the third error.
3rd "init:storage fail" Which i again searched around and found this could be related to "EMMC Fail" which i have no idea how it went there.
So please if anyone have any info or can lend me some help then please let me know as soon as you can.
Thanks in advance.
(I also have a Note 4 (mido) in the same condition (Red Light Blinking and Nothing Else, it DOEN"T EVEN go in EDL mode)
PRemBh0i said:
Conditon :
Can't boot up into anything (Fastboot, recovery)
No Mi Logo
No Vibration
*Phone goes into EDL WITHOUT having to touch the pins on the mobo*
So, my phone was working like 3 days ago, until today it just went to "Red Light Blinking and Nothing Else", So i searched around the internet and basically on YT i got videos like "Heating up the Power IC Fixes this" but i really didn't wanted to try it so i went again and thought maybe i need to flash the Phone so i downloaded the "Global Stock Rom" so i then took the back cover off of my phone and plugged it the USB Cable and i saw "QualComm HS-USB QLoader 9008" which is right i guess and tried to flash it via MiFlash Tool. And indeed i got error BUT in sequence.
1st one was "cannot recieve hello packet"
which i solved by reconnecting my phone
Then
2nd "Object reference not set to an instance of an object"
I only got this ONCE, searched around again and found out that it's something with WRONG ROM type. So i redownloaded the ROM and got the third error.
3rd "init:storage fail" Which i again searched around and found this could be related to "EMMC Fail" which i have no idea how it went there.
So please if anyone have any info or can lend me some help then please let me know as soon as you can.
Thanks in advance.
(I also have a Note 4 (mido) in the same condition (Red Light Blinking and Nothing Else, it DOEN"T EVEN go in EDL mode)
Click to expand...
Click to collapse
So u cant successfully flash rom using edl mode??
What windows pc u r using 32bit or 64 bit ?
Black_Stark said:
So u cant successfully flash rom using edl mode??
What windows pc u r using 32bit or 64 bit ?
Click to expand...
Click to collapse
I have a 64 Bit Windows 10 with drivers installed, it just get stuck on "init Storage : Fail" after 7 seconds.
I have attached a .log.
PRemBh0i said:
I have a 64 Bit Windows 10 with drivers installed, it just get stuck on "init Storage : Fail" after 7 seconds.
I have attached a .log.
Click to expand...
Click to collapse
Try window driver signature disabled.
Try with diffrent usb ports.
Redownload fastboot rom. Extract it and try.
If still getting storage error then Emmc is dead. Repair it or buy new phone.
Black_Stark said:
Try window driver signature disabled.
Try with diffrent usb ports.
Redownload fastboot rom. Extract it and try.
If still getting storage error then EmmC is dead. Repair it or buy new phone.
Click to expand...
Click to collapse
I've tried a different port and re-downloaded the ROM, but i haven't tried to "Disable Driver Enforcement" yet, But if the EMMC is dead then how do i deal with it? And how does it dies? I was using it like 3 days ago with no problem and suddenly it's just gone.
PRemBh0i said:
I've tried a different port and re-downloaded the ROM, but i haven't tried to "Disable Driver Enforcement" yet, But if the EMMC is dead then how do i deal with it? And how does it dies? I was using it like 3 days ago with no problem and suddenly it's just gone.
Click to expand...
Click to collapse
Its phone . not human body which comes with 80 yrs warranty.
If u r gamer then its faster. It has limited write cycles. Disk can go corrupt and dead. How old u r using phone?
Black_Stark said:
Its phone . not human body which comes with 80 yrs warranty.
If u r gamer then its faster. It has limited write cycles. Disk can go corrupt and dead. How old u r using phone?
Click to expand...
Click to collapse
Okay i understand nothing lasts forever but still there could've been some signs that it might be die some time ,i also have a Moto E (1st Gen) it even has gone through water submersion but still works just as fine but recently it's batter died to i decided to lay it in his grave, but alas it's gone, So i just needed to know if you could let me know What can i do to fix the EmmC? Like any tutorials or something? I also have a Note 4 with the same problem as this. Or maybe i'll just never buy a Mi phone again
But still thanks for your time.
PRemBh0i said:
Okay i understand nothing lasts forever but still there could've been some signs that it might be die some time ,i also have a Moto E (1st Gen) it even has gone through water submersion but still works just as fine but recently it's batter died to i decided to lay it in his grave, but alas it's gone, So i just needed to know if you could let me know What can i do to fix the EmmC? Like any tutorials or something? I also have a Note 4 with the same problem as this. Or maybe i'll just never buy a Mi phone again
But still thanks for your time.
Click to expand...
Click to collapse
Its not harddisk which will give u alert or noisy sound before it dies. Its Sd. Thats the demerits of solid drive.
Emmc means embedded multi media card or disk. Its cant be repaired. It can be replaced in service center. May be.
But better buy new phone.
Nothing wrong in buying xiaomi phone.
Most problems happen when u stay on miui and keep doing OTA update for entire life which creates lots of bugs and issues.
U must do factory reset once in a six months. Or flash fastboot rom clean all flash using computer is best to keep phone healthy. Its not true that stock rom is always best. Sometimes its bloated and hogs ur phone like hell like miui.
So installing Custom debloated roms are best here to keep rom smooth running and increasing phones health.
Only upgrading using OTA is not good. Userdata and internal sd must be wiped after few months to clear bugs.
Related
Ok, this is as much a heads up to other P780 users as a desperate shoutout for help... I don't think I've seen anybody else with this problem so far, so here goes.
I purchased a P780 in december 2013, loved every bit of it and it worked flawlessly until about 1 month 1/2 ago. The phone was still brand new, but all of a sudden, it decided it will not charge unless I shut it down.
Basically:
- Phone powered ON, no charge, and not recognized when plugged into a computer => nothing happens. The funny thing is if I use the USB OTG cable, it will actually see and read USB flash drives...
- Phone powered OFF, will charge although the screen won't show anything, only the red led will let you know that it is charging. Also, it won't charge past 88%, meaning when I turn it off and charge it, the maximum battery % is 88% even if I let it charge for 2 days...
The phone has been like that for more than a month now... I considered sending it back for repair or exchange, given it's still under warranty but I am afraid to do so, since I would have to send it back to china and the seller who I bought it from won't help.
Ok, so what do you guys suggest I do? Do you think it's hardware related or software related? I am not sure it is hardware since it will actually charge albeit when powered off, and it will see USB flashdrives when using the USB OTG cable...
PS: I am running multinlingual S125 (Chinese P780).
The easiest solution is: Do a factory reset, if not working; Flash another ROM. Still not working? Sent back to service center, probably is hardware issue then.
Well that was my first reaction, when I first noticed it about 1 month 1/2 ago: I directly factory reseted it, which did nothing. I then proceeded to reflash the ROM (Multinlingual S125, Chinese base), which also did nothing. By the way, flashing was a bit of an ordeal since the tel would not be recognized when plugged into a computer. What I did was press Power + Volume Up, after launching flashtool and clicking on download or firmware upgrade. Only then would the computer recognize that something is being plugged in and start the flashing process. May be that info could help other people...
I proceeded to changing base to ROW P780 (using satanduck's ROW S123) a few days ago, in a last desperate attempt that it would change something, but alas... Really though, sending the phone back to China for repair scares the living f**k out of me, I don't even know how to proceed or where to begin...
Same here, i have charging problem with my p780. It wont charge with powered on, and only able to charge when switch it off. Been doing resets and flashes many time since then but nothing can fix my charging issue. Asked several times in local p780 forum including kaskus, also give no solution. I:ve read many complain bout lenovo SC in my country, make me think twice to take my phone there.
Sent from my Lenovo P780 using xda app-developers app
Same here
I have same problem. It's nice to know that phone will be recognized in recovery mode... so I can flash it.. since I have managed to damage its rom, so it wont boot. All in hope to solve this no-charging problem..
Still have same problem, even worse..
I have checked, unforunatly, my PC doesn't register my phone as any device when it's in recovery mode. With that said, I can't flash new rom, or recovery. Now I'm stuck with rom that doesn't boot, TWRP recovery that is incompatible with this phone (so I can't flash another rom), USB connection that makes phone unrecognizible by PC so I can't flash rom/recovery with flashtool..
I have gone to official Lenovo service here in Serbia, but since I have KIT (for China market) version of phone, there is nothing they could do to help. Pretty lame..
dario.alispahic said:
I have checked, unforunatly, my PC doesn't register my phone as any device when it's in recovery mode. With that said, I can't flash new rom, or recovery. Now I'm stuck with rom that doesn't boot, TWRP recovery that is incompatible with this phone (so I can't flash another rom), USB connection that makes phone unrecognizible by PC so I can't flash rom/recovery with flashtool..
I have gone to official Lenovo service here in Serbia, but since I have KIT (for China market) version of phone, there is nothing they could do to help. Pretty lame..
Click to expand...
Click to collapse
Try reinstall drivers for phone. Or try use another PC with different OS (win7 or winxp). Before your phone was recognized on your PC? Did you have installed drivers for phone before?
lenovo P780 Life 07 said:
Try reinstall drivers for phone. Or try use another PC with different OS (win7 or winxp). Before your phone was recognized on your PC? Did you have installed drivers for phone before?
Click to expand...
Click to collapse
I have read almost all topics regarding p780, and have found this post:
http://forum.xda-developers.com/showpost.php?p=52665841&postcount=16
That saved me... I have newer version of P780 that uses newer Preloader.img. That's why I couldn't flash anything. Now I still have that no charging while powered on problem, but at least I have 90% functional phone..
Leaked battery.
If anybody care to know why P780 has this problem. Driven by little madness I opened the device using mini screwdriver. Found lots off white crust on the right lower corner. I can conclude that mine has battery leaking problem which caused it loss 1/3 of its potential. A replacement need to be done by lenovo center.
Kevin Ismail said:
If anybody care to know why P780 has this problem. Driven by little madness I opened the device using mini screwdriver. Found lots off white crust on the right lower corner. I can conclude that mine has battery leaking problem which caused it loss 1/3 of its potential. A replacement need to be done by lenovo center.
Click to expand...
Click to collapse
Thanks for your info. I will check my phone in the morning. :thumbup:
Sent from my SMT TAB 704DC using XDA Free mobile app
I'm just wondering if you can completely Hard Brick a LG G2 to a point, where there is no revive possible.
I can purchase a cheap LG G2 international version, but the seller says that he broke it during flashing a Kernel.
Can you for example revive a phone,that had a Kernel from completely different phone flashed?
Any insight would be greatly appreciated.
Sent from my C6503 using Tapatalk 2
If it's true he only flashed a new kernel then u can restore it. If he messed with the partitions then.... No. If he used a broken usb cable and fried it....
Well ask to try the phone before u by it. Also check if it's stolen
Alright, I gathered some more information from the seller.
He tried updating TWRP, but he followed wrong instructions from some website.
He can´t enter Recovery or Download Mode on the Phone.
The Display is active, but only Backlight.
When he connects the Phone to his Computer, it shows multiple Mass Storages, but the LG Software doesn´t recognize it.
Is this a common problem, that is easy to fix, or should I rather wait for another Deal to come up.
p.s. I asked him for a receipt, and he says that he has one.
E-I-K-E said:
Alright, I gathered some more information from the seller.
He tried updating TWRP, but he followed wrong instructions from some website.
He can´t enter Recovery or Download Mode on the Phone.
The Display is active, but only Backlight.
When he connects the Phone to his Computer, it shows multiple Mass Storages, but the LG Software doesn´t recognize it.
Is this a common problem, that is easy to fix, or should I rather wait for another Deal to come up.
p.s. I asked him for a receipt, and he says that he has one.
Click to expand...
Click to collapse
If the guy was updating through TWRP, he probably have some knowledge on the matter, and the chances that he bricked it for good is high.
When I messed up my G2 a few times, being able to enter in download mode was the hint that the phone was revivable, if him really can't enter the download mode, then it is probably a bigger problem.
But the question is, by buying this possible lemon, how much will you be saving compared to buying a brand new?
If it's showing up like that, if you have a Linux machine you may be able to use dd to flash factory images to the partitions. There is a guide to it somewhere on here. But even if you were successful in flashing those, it really depends on how badly he screwed it up. In particular I really hope he didn't damage or wipe his efs. Or at least has it backed up.
Honestly, I'd point him to the right guides and have him fix it. If he screwed up his efs, or messed the partitions up, or fried something, it's dead and not coming back. If all he did was flash a kernel in twrp and it was actually from this phone and it was just a bad download or flash or something, then you'd probably be okay, but if that were the case you'd get a secure boot error and still be able to enter download mode. Personally, I would not buy a phone that won't boot, especially if the seller isn't even sure what's wrong with it.
Sent from my LG-G2 using Tapatalk
sounds recoverable, if there is a backlight and mass storage comes up that's good, you can dd partitions with linux
no backlight + no recognizable usb device at all = bricked
still, buy at your own risk
It is.. i just did by flashing a broken rom.. sent it to the repair center and they replaced the motherboard
Right, I asked him if the Device shows as qhsusb_bulk in device Manager, and it does.
The only thing that worries me, is that there is no Boot Logo, most of the people in the Linux Fix Thread atleast get a LG Logo and not just Backlight.
I´m really unsure what to do, I can save like 150€ by buying the broken G2, but well . . . I dont know if I can fix it.
Another problem is, that I have not a single clue on how to operate Linux/Ubuntu, and the only real fix requires either of those
E-I-K-E said:
Right, I asked him if the Device shows as qhsusb_bulk in device Manager, and it does.
The only thing that worries me, is that there is no Boot Logo, most of the people in the Linux Fix Thread atleast get a LG Logo and not just Backlight.
I´m really unsure what to do, I can save like 150€ by buying the broken G2, but well . . . I dont know if I can fix it.
Another problem is, that I have not a single clue on how to operate Linux/Ubuntu, and the only real fix requires either of those
Click to expand...
Click to collapse
Just look up a guide on how to install an Ubuntu virtual machine. You should be able to connect your G2 to that virtual if you let it capture the USB port. If you can get it cheap, buy it and try to negotiate so you might have a chance on selling it for higher later on if you can't fix it. To me though, it sounds quite fixable, I would go for it.
E-I-K-E said:
The only thing that worries me, is that there is no Boot Logo, most of the people in the Linux Fix Thread atleast get a LG Logo and not just Backlight.
Click to expand...
Click to collapse
this doesn't really matter, when I was trying to mess with the bootloader and corrupted it a few times I've never had the LG logo, as long as it comes up as storage you can DD it - the only time its a true brick is with no backlight and no usb device
if theres no boot logo you probably need to DD the aboot in
dr87 said:
this doesn't really matter, when I was trying to mess with the bootloader and corrupted it a few times I've never had the LG logo, as long as it comes up as storage you can DD it - the only time its a true brick is with no backlight and no usb device
if theres no boot logo you probably need to DD the aboot in
Click to expand...
Click to collapse
This.. If you have bulk mode, you can fix it!
kewkie said:
It is.. i just did by flashing a broken rom.. sent it to the repair center and they replaced the motherboard
Click to expand...
Click to collapse
That's actually just killing a fly with a sledgehammer. 99.9999% sure you got a softbrick.
Sent from my Moto G using XDA Premium 4 mobile app
Savoca said:
That's actually just killing a fly with a sledgehammer. 99.9999% sure you got a softbrick.
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Tried 3 different laptops
1x windows 8.1 (with ubuntu)
1x window 7 x64
1x windows 7 x86
Reinstalled all drivers, tried everything, but i couldnt get any usb connection.
- Factory reset? Freeze
- Normal boot? Stuck at bootlogo
- Download mode? Stucking at the loading screen
E-I-K-E said:
Alright, I gathered some more information from the seller.
He tried updating TWRP, but he followed wrong instructions from some website.
He can´t enter Recovery or Download Mode on the Phone.
The Display is active, but only Backlight.
Click to expand...
Click to collapse
I had that problem when updating TWRP too. You have to be careful because these recoveries are only made for specific firmware versions. I cant remember how I fixed the issue after only being able to get a backlight on and no image, but I did fix it and my phone works fine. I do think you will need the TWRP files already on the phone to fix though, so you can somehow manage to flash back. They will need to be on the phone since you can push anything via ADB
E-I-K-E said:
Right, I asked him if the Device shows as qhsusb_bulk in device Manager, and it does.
The only thing that worries me, is that there is no Boot Logo, most of the people in the Linux Fix Thread atleast get a LG Logo and not just Backlight.
I´m really unsure what to do, I can save like 150€ by buying the broken G2, but well . . . I dont know if I can fix it.
Another problem is, that I have not a single clue on how to operate Linux/Ubuntu, and the only real fix requires either of those
Click to expand...
Click to collapse
i've been in this bricked situation when i was trying the 4.4.2 update manually...completely bricked, could not get into download mode too...so gave it to the service centre which at first said the main board will have to be changed when recovering through software upgrade failed...next day i got the phone back as they managed to flash the software back on it...
does not end here...i tried to flash optimus g pro 2 rom through twrp and same thing happened again...but was lucky this time as i could enter download mode and flashed kdz to recover...
E-I-K-E said:
I'm just wondering if you can completely Hard Brick a LG G2 to a point, where there is no revive possible.
I can purchase a cheap LG G2 international version, but the seller says that he broke it during flashing a Kernel.
Can you for example revive a phone,that had a Kernel from completely different phone flashed?
Any insight would be greatly appreciated.
Sent from my C6503 using Tapatalk 2
Click to expand...
Click to collapse
And yes i truly believe that our device can be hard bricked like i did mine today.
I tried to compile a custom bootloader for G2 using Qualcom's sources and fraction of LK. But in doing so i left my phone in a quasi-state where it will not connect as a usb device coz it does not pass the bootloader (Although bootloader is working as it should). .
So the only two option remain here for me is
1. To send phone back to LG service center where they'll do idk what.
2. To use JTAG or short the ic (Wonder if it could be done ) i.e manually open the phone and boot into the primary bootloader(Qcom legacy BL).
See that's how you can hard brick ur phone the right way
fizzy177 said:
And yes i truly believe that our device can be hard bricked like i did mine today.
I tried to compile a custom bootloader for G2 using Qualcom's sources and fraction of LK. But in doing so i left my phone in a quasi-state where it will not connect as a usb device coz it does not pass the bootloader (Although bootloader is working as it should). .
So the only two option remain here for me is
1. To send phone back to LG service center where they'll do idk what.
2. To use JTAG or short the ic (Wonder if it could be done ) i.e manually open the phone and boot into the primary bootloader(Qcom legacy BL).
See that's how you can hard brick ur phone the right way
Click to expand...
Click to collapse
Your LK build wouldn't have matched the sbl1, anything other than LG's signed aboot wouldn't work.. /:
Sent from my Nexus 5 using XDA Premium 4 mobile app
Savoca said:
Your LK build wouldn't have matched the sbl1, anything other than LG's signed aboot wouldn't work.. /:
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
But it did work coz our bootloader enfoces the signature check not in the sbl.(Our Primary boot loader)
i'm sure of it because it tries to go to download option but freezes at initial stage.
had it been the case my device would've been detected as qucom_bulk device or so..
---------- Post added at 09:03 AM ---------- Previous post was at 08:58 AM ----------
kewkie said:
Tried 3 different laptops
1x windows 8.1 (with ubuntu)
1x window 7 x64
1x windows 7 x86
Reinstalled all drivers, tried everything, but i couldnt get any usb connection.
- Factory reset? Freeze
- Normal boot? Stuck at bootlogo
- Download mode? Stucking at the loading screen
Click to expand...
Click to collapse
You my dear friend are a victim of a curroupt bootloader seqence(NOT THE CoRRUPT BOOTLOADER) i.e
Your phone would start something like
1- EFI initialization ok
2-Primary Boot Load -ok
3-Vendor Boot Load -ok
4- Error unable to find proper boot sequence- system halted
So ur best options are the one that i've stated just above this thread.
My case. I root and flash custom recovery then apply OTA = medium brick. Download mode was not functioning, only recovery. To make matter worse, I flashed KK stock rom through ADB in recovery = super brick. Then I went to LG service center with poker face asked for reparation. They asked (confirm) whether your phone is rooted or not (they had already know though) and I just said like It is my sister's phone. Then they they open the phone and maybe directly format the sd card with some stuff. My phone is restored again afterward. In my opinion, software modification can always be repaired unless you fry your phone through overclock or overvolt.
ramabg said:
My case. I root and flash custom recovery then apply OTA = medium brick. Download mode was not functioning, only recovery. To make matter worse, I flashed KK stock rom through ADB in recovery = super brick. Then I went to LG service center with poker face asked for reparation. They asked (confirm) whether your phone is rooted or not (they had already know though) and I just said like It is my sister's phone. Then they they open the phone and maybe directly format the sd card with some stuff. My phone is restored again afterward. In my opinion, software modification can always be repaired unless you fry your phone through overclock or overvolt.
Click to expand...
Click to collapse
It's not a brick if it was restored... meh.
The phone notified me there is a system update so I went ahead. Unfortunately, towards the end, it gave me an error message. I remember seeing the big Android robot lying flat on its back.
Now, the phone is completely dead. When I connect it to my computer I can hear the "new hardware connected" sound then immediately the disconnecting sound. This goes on and on for ever.
I tried using the tools provided on Leagoo's site, but they're useless as the computer is not able to recognize the phone.
Is there a hard reset key combination?
Thanks.
Eddie
silentmonolith said:
The phone notified me there is a system update so I went ahead. Unfortunately, towards the end, it gave me an error message. I remember seeing the big Android robot lying flat on its back.
Now, the phone is completely dead. When I connect it to my computer I can hear the "new hardware connected" sound then immediately the disconnecting sound. This goes on and on for ever.
I tried using the tools provided on Leagoo's site, but they're useless as the computer is not able to recognize the phone.
Is there a hard reset key combination?
Thanks.
Eddie
Click to expand...
Click to collapse
I've here 4 brick-phone (friends have updated with the same result!).
leagoo support didn't answer to my polite email of support.
Anyone can give us a sugestion to recover it!?
j045 said:
I've here 4 brick-phone (friends have updated with the same result!).
leagoo support didn't answer to my polite email of support.
Anyone can give us a sugestion to recover it!?
Click to expand...
Click to collapse
In the end, I was able to finally recover it. I just kept trying and trying: while the phone was connected to the computer, I removed the battery, then I put it back in; as well I was disconnecting it from the computer, then plug it back - I did this several times until the software on the computer was able to recognize it.
Even so, when I managed to reflash it, around 60%-70%, I got a message that it failed; so I tried again - it failed around 80% then I tried one more time and it was successful. Now the phone is working fine.
So my advice to you is to keep trying - leave the software on and click on the "download firmware" or whatever it was called, meanwhile keep unplugging the phone (and play with the battery as well).
Good luck! (you will need it)
Same problem, but leagoo responded with driver, firmware, flash tool, instructions and a video.
But nothing changed, so i have to retry.
Thanks for your post.
Edit:
I was thinking that was a hardware problem with micro usb connector!
ItalianWolf said:
Same problem, but leagoo responded with driver, firmware, flash tool, instructions and a video.
But nothing changed, so i have to retry.
Thanks for your post.
Edit:
I was thinking that was a hardware problem with micro usb connector!
Click to expand...
Click to collapse
i did it! just tried a lot of times, but firmware from leagoo doesn't work, display shows only "stipes".
I found another firmware (don't remember where) and then all things went good.
Now the phone notified me there is a system update, i have to do it?
Hi everyone,
a friend sent me an almost new Redmi Note 2 (I think 2 months old) that he bought while he was living in China, that recently "just stopped working"
Since he's not living there anymore, warranty's not an option and since he was "tired of dealing with it" he sent it to me.
So... when it arrived here, I noticed that it was completely discharged. If you plug it in, the red light goes on, but only stays on for like 5 minutes.
No matter what you do, it won't turn on.
I tried letting it charge overnight, only to find out that it was completely discharged again the next morning. As in... I checked the battery with a voltmeter and it was completely dead again.
I've since gotten a replacement battery, but even with that, it won't turn on.
When I connect it to the computer (with, or without battery) it shows up as "USB Serial Device" and shortly after as "PreLoader USB VCOM Port", but the problem is that it immediately disconnects again, a second later, so I can't actually use SP Flash Tool to do anything with it.
Any idea what's wrong with it, or do you think it's borked beyond repair?
I'm well versed with electronics (electronic engineer) so I could try to open it up, but with these things it's really hard to find any obvious defective parts (let alone replace most of them) so I thought I should ask for your opinion first.
Thanks!
Maybe the USB port is broken or the cable... But well I don't know... (Can't compete with an electronic engineer - I am still a student
But I am interested in your solution if you solved it somehow
BROM 4001 error
Hi! I'm glad to have found you.
I have the same problem. I have tried to flash using SP flash tools but get a BROM 4001 error.
I can't post the url but I have a thread on miui dot com - "[Q & A] Redmi Note 2 bricked"
angahith said:
When I connect it to the computer (with, or without battery) it shows up as "USB Serial Device" and shortly after as "PreLoader USB VCOM Port", but the problem is that it immediately disconnects again, a second later, so I can't actually use SP Flash Tool to do anything with it.
Click to expand...
Click to collapse
This is normal.
You should press Download on SP Flash Tool before connecting the device.
---------- Post added at 12:15 ---------- Previous post was at 12:12 ----------
hp1337 said:
I have tried to flash using SP flash tools but get a BROM 4001 error.
Click to expand...
Click to collapse
Here you can find a list of SP Flash Tool error codes.
Thanks for helping. I checked the list of error codes and got
(4001) S_FT_DA_NO_RESPONSE
Скрыть содержимое
Solution: Change the USB-port and transfer the SP Flash Tool to the root of drive C: \
There is also a version that the download agent containing no information on the CPU / flash.
Solution: upgrade proshivalschika.
The problem could be hardware, such as the failed flash memory.
Click to expand...
Click to collapse
I moved SP flash tool and associated files to C:/ and tried a couple of USB ports but got the same result. It has the red bar at 100% and waits for 24-26 seconds before giving the same error code.
Heyo, sorry, I totally forgot about the phone for a good while and just remembered it again.
Okay so... I installed the drivers again and it shows the right ones, but I think I sort of found the issue.
It only ever gets recognized as MTK USB Port and not as MediaTek DA USB VCOM Port.
Unless all the guides are wrong, I need to press Volume+ after plugging it in, to start it in the other mode, but that only worked once when I was trying stuff out without SP Flash tool open and i accidentally unplugged it again. Now it just never goes into the DA mode again.
Hello guys!
I'm kinda freakin' out here.
Here's the story:
I bought this amazing Redmi 3 Pro from China, and after waiting for 33 days, it arrived. I knew that it's important change the ROM that came with the device, so... I changed it. I'm from Brazil, so I needed a ROM with Portuguese-BR language and at least, stable. When I was going to change the ROM, my device just turn off and never turned on again.
OBS: The drivers are installed. It recognizes as "Qualcomm HS-USB QDLoader 9008", so I think that it's on EDL Mode.
OBS2: I tested flash on: Win7(x64) and Win10(x64). Neither worked.
OBS3: Every time, I get the error "Reached End of File.(0x80070026: Receiving Hello Packet.)
OBS4: I downloaded several ROMs, several versions of MiFlash (including the Beta version) and nothing passed from the error above.
OBS5: The device doesn't turn on, doesn't light on the LED, doesn't vibrate etc.
I believe that the problem resides on the missing two files: MPRG8936.mbn and 8936_msimage.mbn.. If anyone have those files, please, share here.
Thank's for those who can help! ^^
Brow1998 said:
Hello guys!
I'm kinda freakin' out here.
Here's the story:
I bought this amazing Redmi 3 Pro from China, and after waiting for 33 days, it arrived. I knew that it's important change the ROM that came with the device, so... I changed it. I'm from Brazil, so I needed a ROM with Portuguese-BR language and at least, stable. When I was going to change the ROM, my device just turn off and never turned on again.
OBS: The drivers are installed. It recognizes as "Qualcomm HS-USB QDLoader 9008", so I think that it's on EDL Mode.
OBS2: I tested flash on: Win7(x64) and Win10(x64). Neither worked.
OBS3: Every time, I get the error "Reached End of File.(0x80070026: Receiving Hello Packet.)
OBS4: I downloaded several ROMs, several versions of MiFlash (including the Beta version) and nothing passed from the error above.
OBS5: The device doesn't turn on, doesn't light on the LED, doesn't vibrate etc.
I believe that the problem resides on the missing two files: MPRG8936.mbn and 8936_msimage.mbn.. If anyone have those files, please, share here.
Thank's for those who can help! ^^
Click to expand...
Click to collapse
don't panic.. just try this method.. your phone will be back!!
http://en.miui.com/forum.php?mod=viewthread&tid=283484&page=9#pid5645253
Didn't worked
saikatmitra71 said:
don't panic.. just try this method.. your phone will be back!!
Click to expand...
Click to collapse
Heey, didn't worked. .-.
it will be solved with the method which explained on this thread
en.miui.com/thread-283484-5-1.html
Hey @Brow1998
Try this : HERE
Section How to Unbrick the Redmi3
Scenario B (Hardbrick)
adblocker said:
Hey @Brow1998
Try this : forum.xda-developers.com/redmi-3/development/redmi-3-pro-spacex-rom-t3406919
Section How to Unbrick the Redmi3
Scenario B (Hardbrick)
Click to expand...
Click to collapse
Well.. I believe that my phone's battery is dead.. How can I charge it externally? Cuz the charger isn't charging properly. Tried several chargers, but the light of low battery doesn't turn on in a couple days.
Brow1998 said:
Well.. I believe that my phone's battery is dead.. How can I charge it externally? Cuz the charger isn't charging properly. Tried several chargers, but the light of low battery doesn't turn on in a couple days.
Click to expand...
Click to collapse
You need to plug the battery to other redmi 3 and charge it
or charge it directly with 1A 3.9V (risk of damage)
adblocker said:
You need to plug the battery to other redmi 3 and charge it
or charge it directly with 1A 3.9V (risk of damage)
Click to expand...
Click to collapse
Well.. I live in Brazil, and I don't know anyone who have this device, so that's not an option. Any other sugestions to charge it?
Brow1998 said:
Well.. I live in Brazil, and I don't know anyone who have this device, so that's not an option. Any other sugestions to charge it?
Click to expand...
Click to collapse
you do not need to charge the phone before flashing. i had the same problem. connect your phone to computer and after some minutes (may be up to 20 minutes) in device manager you will the phone as..... qdloader.... 9008 and every thing is ready to flash according the instructions.
rekh said:
you do not need to charge the phone before flashing. i had the same problem. connect your phone to computer and after some minutes (may be up to 20 minutes) in device manager you will the phone as..... qdloader.... 9008 and every thing is ready to flash according the instructions.
Click to expand...
Click to collapse
The computer recognizes the device exactly like this "Qualcomm HS-USB QDLoader 9008 (COM20)"
When i'm going to flash, an error appears, "Reached End of File.(0x80070026: Receiving Hello Packet.)".
Using the MiFlash Beta, the error says "Coudn't communicate with port COM20"
I wanna play pokémon go :c
Brow1998 said:
The computer recognizes the device exactly like this "Qualcomm HS-USB QDLoader 9008 (COM20)"
When i'm going to flash, an error appears, "Reached End of File.(0x80070026: Receiving Hello Packet.)".
Using the MiFlash Beta, the error says "Coudn't communicate with port COM20"
I wanna play pokémon go :c
Click to expand...
Click to collapse
why dont you do what I said ! ?
try it
someone like you did it and he saved his phone!
adblocker said:
why dont you do what I said ! ?
try it
someone like you did it and he saved his phone!
Click to expand...
Click to collapse
If you're talking about the solution through the guide for Redmi 3, I just did it and nothing worked. On MiFlash 2015.10.28.0 appeared the error "0x800700aa" Something like "Current Resource current being used" and when I click on refresh and try it again, the same old error appears: "0x80070026: Receiving Hello Packet"
On MiFlash Beta, the error "Can not read from port COM4" still appears.
Just updating.
Using this method, it worked: http://en.miui.com/forum.php?mod=viewthread&tid=283484&page=5#pid5510469
I was making some mistakes, but doing it properly totaly works!
Thank you all!
Brow1998 said:
Heey, didn't worked. .-.
Click to expand...
Click to collapse
same with my problem yesterday , my redmi3 deadbrick, but i can repair it, sorry for my english , follow that tutorial link