Hi, I was trying to flash a global rom on my renoir and it got some error on twrp. I just tried to reboot and starts all again and now I'm just stucked at a black screen (there's no interface to go to fastboot or recovery mode), when i try to connect it on my pc it sounds like a connected but i can't flash or do anything. I saw some people saying that I need like an "authorized account" to get it backs to life (and it's paid)... there's other way?
No other way in my opinion. Had to do the same a few months ago.
A few weeks ago I was in them same situation. I've contacted a telegram account, transfer $32 through PayPal, and someone accessed my notebook and revive my phone.
Hi,
The same problem.
Any idea????
@jimmy69 said:
Hi,
The same problem.
Any idea????
Click to expand...
Click to collapse
read 1 post up..no other solution
Related
Ok, so like I was flashing my phone to Cyanogen mod 9 (using CWM port 0.6) and it went wrong. My phone is now bricked. When I try to boot it up now I get the phone to computer warning thingy message
I can get it into download mode and emergency download mode, but Odin either comes up with "FAIL."
I have tried every single thing on the web, NOTHING works (One click unbrick etc, etc, etc). Please help!
One thing that might help is One Click Unbrick, even after i've installed all of the software, reinstalled the drivers, won't recognise my phone!
Is there anything left that I could try???
P.S. On all the other similar threads, the things they suggest don't work
Mad_Guy said:
Ok, so like I was flashing my phone to Cyanogen mod 9 (using CWM port 0.6) and it went wrong. My phone is now bricked. When I try to boot it up now I get the phone to computer warning thingy message
I can get it into download mode and emergency download mode, but Odin either comes up with "FAIL."
I have tried every single thing on the web, NOTHING works (One click unbrick etc, etc, etc). Please help!
One thing that might help is One Click Unbrick, even after i've installed all of the software, reinstalled the drivers, won't recognise my phone!
Is there anything left that I could try???
P.S. On all the other similar threads, the things they suggest don't work
Click to expand...
Click to collapse
One click unbrick wont work on the galaxy 5 (i think ) and the best way to unbrick your phone is to use a JTAG or simply give it to samsung for repairs... Trying something which is not supported may worsen the situation ..
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 Folks
I just bought my girlfriend a Redmi Note 3 SE (Kate) quick back story, she received it turned it on added a pin to it got called away, when she got back to it she couldn't remember the pin, bad news is she hadn't yet turned on Developer Mode or USB Debugging.
Original SW - MIUI 7.5 android 6.0.1, at least that's what the Ali product page says (Sorry it seems I can't post a link to the actual product)
This began last Friday, since then she has tried the following:-
Installed MI Suite and registered a gmail account - so far "device not recognised"
Applied for an Unlock code.
Unlocked the boot loader which seems to have been successful.
Flashed two different (stock) ROM's which completed successfully but both stuck while booting the phone.
One was:-
"kate_global_images_6.12.29_20161228.0000.00_6.0_global" not sure what the other was.
On trying a different ROM today she's now getting the following error:-
"Can't Flash in miflash. Not enough storage is available to process this command"
Tried different versions of the Flash tool including the Beta version but still getting the same error on each of them.
Ticked the "Clear Data" box in the Mi Flash tool but that doesn't help.
A bit stuck on what to try from here and any help would be greatly appreciated if you need any more info please let me know.
I had the same bootloop problem with the stock firmware and miflash and driver was a pain to get sorted out.
What versions of miflash have you tried and which firmware did you download from xiaomi?
theoneofgod said:
I had the same bootloop problem with the stock firmware and miflash and driver was a pain to get sorted out.
What versions of miflash have you tried and which firmware did you download from xiaomi?
Click to expand...
Click to collapse
Hi thanks for the reply, unfortunately I need to wait for an answer on that as she's not around at the moment, but from what I can gather she has tried miuiflash 1, 2 and beta and i know she tried this which I'm assuming is a firmware - kate_global_images_6.12.29_20161228.0000.00_6.0_global (if it's not please let me know what we should be using) *edit, mind you that's one of the files that got stuck showing the out of space error.
I also forgot to mention the PC is a win 10 64bit..
Soon as I can get you a better answer on the above I'll post it.
I would have them try this version http://bigota.d.miui.com/V8.1.1.0.M...DI_20161202.0000.00_6.0_global_ac46ea44bd.tgz it's the latest fastboot ROM.
Make sure when you install miflash you are running in test mode so the drivers install properly and accept any prompts about driver signatures. That is important. I believe MiFLash_v20160401 worked for me. Also you know when you're in EDL when the front LED flashes red now and then.
theoneofgod said:
I would have them try this version http://bigota.d.miui.com/V8.1.1.0.M...DI_20161202.0000.00_6.0_global_ac46ea44bd.tgz it's the latest fastboot ROM.
Make sure when you install miflash you are running in test mode so the drivers install properly and accept any prompts about driver signatures. That is important. I believe MiFLash_v20160401 worked for me. Also you know when you're in EDL when the front LED flashes red now and then.
Click to expand...
Click to collapse
Ah so it wasn't a firmware, alright I've passed this on as soon as I hear back I'll post here, many thanks.
I just checked the link for the 8.1.1.0 Firmware but it gives a 404 error on the page, I'll look on their site for an alternative, but if you do know of an alternative please let me know.
**edit Never mind a right click and copy link location got it.
So the issue looks to be solved, so firstly many thanks "theoneofgod" for your input.
Unfortunately due to a rather dodgy internet connection I haven't managed to get further into it, but here is what I received:-
"I used the same Kate and used miflash beta version.. i did the same as i did on first attempt.. after succesfully flashing it, i turned it on (result:same stuck on booting)
i switch it back to fastboot mode.
flash it.
result error.
i then press power on for about 5 seconds or till the mi logo appeared.
unplugged the USB cable and plugged it in again.
then phone booted.
and
When miflash beta version recognized my phone as just a device not com port. i flashed it. (it was just flashing endlessly)
So i tried to refresh the page, it then showed my device with an id as com10 (I have a feeling this might be the important part)
i flashed that too, and then it worked didn't get that error " no storage" anymore.
I'm not sure though if that helped
Basically I'm saying that i was flashing 1 device with two different id.
So I'm thinking simply the device refresh actually did the trick, anyway it looks to be solved, that was 3 days of no fun, and that whole thing about hey submit an application for a bootloader unlock and then wait 2 or 3 weeks and we might even refuse it lol.
Thanks again for your help "theoneofgod" thanks meter pressed.
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.
Stupid excuse, but I was under the influence and decided to flash PE on my phone and messed the A/B slot choice, so got stuck in fastboot and it didn't boot into recovery anymore no matter how much I erased and flashed it to any of both slots. More stupid decisions kept coming, and I erased EVERYTHING, system, vendor, modem, etc... pushed recovery via fastboot again but now it won't even go to fastboot, screen shows nothing, and Windows detects the device as Qualcomm HS-USB QDLoader 9008. Did some research and apparently phone is in Qualcomm Emergency Download Mode. Found this https://forum.hovatek.com/thread-19721.html and apparently it's possible to extract mmcblk0.img file from a similar device. Does anybody know if this will work ? Also MiFlash keeps showing " cannot receive hello packet " and then times out in like 19 seconds and device is unresponsive to everything and anything... Help please :')
freeze1994 said:
Stupid excuse, but I was under the influence and decided to flash PE on my phone and messed the A/B slot choice, so got stuck in fastboot and it didn't boot into recovery anymore no matter how much I erased and flashed it to any of both slots. More stupid decisions kept coming, and I erased EVERYTHING, system, vendor, modem, etc... pushed recovery via fastboot again but now it won't even go to fastboot, screen shows nothing, and Windows detects the device as Qualcomm HS-USB QDLoader 9008. Did some research and apparently phone is in Qualcomm Emergency Download Mode. Found this and apparently it's possible to extract mmcblk0.img file from a similar device. Does anybody know if this will work ? Also MiFlash keeps showing " cannot receive hello packet " and then times out in like 19 seconds and device is unresponsive to everything and anything... Help please :')
Click to expand...
Click to collapse
Maybe you will need do the EDL mode with an authorized account, and reflash system.
X7REME13 said:
Maybe you will need do the EDL mode with an authorized account, and reflash system.
Click to expand...
Click to collapse
Saw that around quite often but have no idea how to get said " authorized account " and from my understanding phone is in Qualcomm Emergency DL mode...
freeze1994 said:
Saw that around quite often but have no idea how to get said " authorized account " and from my understanding phone is in Qualcomm Emergency DL mode...
Click to expand...
Click to collapse
Visit a service center or use some online service. EDL stands for Emergeny DownLoad mode..
freeze1994 said:
Saw that around quite often but have no idea how to get said " authorized account " and from my understanding phone is in Qualcomm Emergency DL mode...
Click to expand...
Click to collapse
You are going to have to look for any user who has such an account. I know of some that have them, but I don't know if they are trustworthy (it remains in you).
- @Android_Servis on Telegram
- +7 967 777 15 98 Telegram and (I guees Whatsapp to)
- +880 1771989858 Whatsapp only
Write to them, hopefully they can solve your problem.
If you solve it, let me know with whom and how you did it...
I have an A3 with SoftBrick and I also need to solve it.
Apparently it's quite hard to get an authorized account to be able to flash in EDL mode indeed, trying to authorize mine, guess all that I can do is wait or go to s-unlock.com, reports of it working all around, really appreciate the help guys...
_mysiak_ said:
Visit a service center or use some online service. EDL stands for Emergeny DownLoad mode..
Click to expand...
Click to collapse
Appreciate the tip but I hate that EDL is locked and kinda want to go headstrong against it and get this done without paying a dime, phone is my property after I bought it, I don't see why any part of it should be locked and inaccessible to me as its owner ... just hate the way this has been handled by Xiaomi, feels greedy and wrong to me... Really appreciate the heads-up though, maybe it'll code to that eventually
freeze1994 said:
Appreciate the tip but I hate that EDL is locked and kinda want to go headstrong against it and get this done without paying a dime, phone is my property after I bought it, I don't see why any part of it should be locked and inaccessible to me as its owner ... just hate the way this has been handled by Xiaomi, feels greedy and wrong to me... Really appreciate the heads-up though, maybe it'll code to that eventually
Click to expand...
Click to collapse
Well, we are lucky that we can unlock the bootloader without any hassle, unlike many other Android phones out there. Xiaomi "locked" EDL mode probably because of some sellers, who bought cheaper phones (be it MIUI or Android One), swapped the ROM and re-sold them at higher price. Ordinary folks do not need to use EDL, if service center needs to use it, it will be free of charge. If someone's willing to unlock the bootloader and mess up with the phone, he should face the consequences if something goes wrong. It's not manufacturer's fault. Personally I'm glad that Xiaomi did not take the route of Nokia or Huawei, where you can't unlock the bootloader at all (at least not without a paid service).
- download and register MI FLASH PRO https://miflashpro.com/
- download Fastboot ROM https://xiaomifirmwareupdater.com/miui/laurel/
- download (Mi A3) prog_firehose_ddr_unbrick.elf https://www.leakite.com/xiaomi-programmer-firehose-files/
- check device manager - ports: qualcomm hs-usb qdloader 9008 (com3) - device is in EDL mode
- replace ROM/images/prog_firehose_ddr.elf with downloaded prog_firehose_ddr_unbrick.elf - fix for "Your Account is Unauthorized for this operation"
- open Mi Flash Pro/Mi Flash
- select path to ROM (can not have any space)
- select clean all
- select flash
if you are getting "cannot receive hello packet" or "cannot read from port com" it's probably EDL timeout or driver issue.
- unplug usb from phone, push power button for 40 sec, plug usb back to phone, refresh and flash
just pushing power button and waiting for disconnect/reconnect wasn't working..
just unplug/plug usb wasn't working..