Hello guys this is my first time posting in here, the thing is, I hardbricked my Moto G4 and I can't make it work, it reboots each 5-6 seconds endlessly... any help or advice? I'm beyond desperate :/
Thank you in advance.
Here's a video to show you guys:
https:// youtu.be/_v5FErFl4rk
Ps: In the video, the phone is (usb) plugged to my laptop
Ps1: Already replaced the battery and nothing happened :/
Ps2: I know this section it's about g4plus, but I didn't receive so much help
Ps4: I followed the thread about recover a hardbrick phone, but can't run the commands just because the phone reboots itself each 5 seconds so, the process can't be completed.
letitrrain said:
Hello guys this is my first time posting in here, the thing is, I hardbricked my Moto G4 and I can't make it work, it reboots each 5-6 seconds endlessly... any help or advice? I'm beyond desperate :/
Thank you in advance.
Here's a video to show you guys:
https:// youtu.be/_v5FErFl4rk
Ps: In the video, the phone is (usb) plugged to my laptop
Ps1: Already replaced the battery and nothing happened :/
Ps2: I know this section it's about g4plus, but I didn't receive so much help
Ps4: I followed the thread about recover a hardbrick phone, but can't run the commands just because the phone reboots itself each 5 seconds so, the process can't be completed.
Click to expand...
Click to collapse
It's rebooting like you have kept power key and vol- key pressed. It may be hardware failure..
But tell us,
What happens if USB is not plugged ?
____Mdd said:
It's rebooting like you have kept power key and vol- key pressed. It may be hardware failure..
But tell us,
What happens if USB is not plugged ?
Click to expand...
Click to collapse
The same thing, the phone reboot by itself each 6 seconds, plugged or not :/
letitrrain said:
The same thing, the phone reboot by itself each 6 seconds, plugged or not :/
Click to expand...
Click to collapse
For a test, flash any partition of more than 100MB,
Keep written command, when it comes to bootloader, enter command.
It will be FAILED, but i want to see what other error command prompt reflects. Post those lines..
If power and vol- keys are pressed, it will reflect "too many links" line somewhere.. just check for it.
---------- Post added at 07:43 AM ---------- Previous post was at 07:39 AM ----------
I forgot to ask, how this happened ?
After flashing any ROM / firmware or before?
Sorry about the lack of reply to your other thread, I'll reply to you here.
As I recall, the battery on your device was a possible culprit - can you confirm that the connection being made to the motherboard is okay and not damaged? Might be a damaged or loose contact, which may be causing the reboots.
In your other thread, https://forum.xda-developers.com/mo...inite-loop-t3742393/post75398422#post75398422 we were trying to flash a stock ROM, but you were seeing failed (invalid argument). Can you try to reflash the GPT and bootloader and see what response you get? I'm concerned though that because your device keeps rebooting, a firmware flash may not be a good idea (partial firmware flashes are another source of bricked devices).
If that doesn't work, we may have to consider that this is a hardware fault resolvable only by a service centre.
____Mdd said:
For a test, flash any partition of more than 100MB,
Keep written command, when it comes to bootloader, enter command.
It will be FAILED, but i want to see what other error command prompt reflects. Post those lines..
If power and vol- keys are pressed, it will reflect "too many links" line somewhere.. just check for it.
---------- Post added at 07:43 AM ---------- Previous post was at 07:39 AM ----------
I forgot to ask, how this happened ?
After flashing any ROM / firmware or before?
Click to expand...
Click to collapse
Yes, reflects "too many links" when a file/partition is bigger than 100mb
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
9jarom said:
put the phone into fastboot mode leave it for like 10 minutes, if it does not reboot then its software error, if it does otherwise then PCB [battery/power ic]
Click to expand...
Click to collapse
It keeps rebooting itself each 5-6 seconds (its usb/plugged to my laptop)
echo92 said:
Sorry about the lack of reply to your other thread, I'll reply to you here.
As I recall, the battery on your device was a possible culprit - can you confirm that the connection being made to the motherboard is okay and not damaged? Might be a damaged or loose contact, which may be causing the reboots.
In your other thread, https://forum.xda-developers.com/mo...inite-loop-t3742393/post75398422#post75398422 we were trying to flash a stock ROM, but you were seeing failed (invalid argument). Can you try to reflash the GPT and bootloader and see what response you get? I'm concerned though that because your device keeps rebooting, a firmware flash may not be a good idea (partial firmware flashes are another source of bricked devices).
If that doesn't work, we may have to consider that this is a hardware fault resolvable only by a service centre.
Click to expand...
Click to collapse
I already made a battery replacement and nothing's happened, some people says it's a battery thing, other firmware issues and others says it's a stick-button problem which it works well.
letitrrain said:
Yes, reflects "too many links" when a file/partition is bigger than 100mb
It keeps rebooting itself each 5-6 seconds (its usb/plugged to my laptop)
I already made a battery replacement and nothing's happened, some people says it's a battery thing, other firmware issues and others says it's a stick-button problem which it works well.
Click to expand...
Click to collapse
Thanks for the info:
1)So you've replaced the battery, but the reboots still occur, is that correct? Do you know if you (or whoever replaced the battery) checked the battery contacts on the motherboard, check they're not damaged? I'm concerned that a damaged connector may be causing the reboots, which would require a motherboard replacement.
2)Can you confirm this reboot and 'data transfer failure' keeps happening if you change to another USB port (on your computer, not in a USB hub) and that you're using the original Motorola USB cable to flash and power your device? Or if you don't have the original USB cable, that you're using a high quality data+power USB cable?
3)I'll let ____Mdd verify this, but the 'data transfer failure (too many links) is possibly due to the volume and power keys pressed in?
I have faced that once,
i was experimenting and my bootloader hanged, so i restarted by pressing Power and Vol-, this show me that lines in cmd screen..
That's why i can say your device have hardware problem, something is keeping power/vol keys pressed.
(Searching on XDA show me that line also appears if there is Driver or other connection problem) but here possibilities are more of keys pressed, definitely hardware failure...
But still, you haven't answered how / when this happened ?
You tried to disassemble device ?
While flashing anything ??
echo92 said:
Thanks for the info:
1)So you've replaced the battery, but the reboots still occur, is that correct? Do you know if you (or whoever replaced the battery) checked the battery contacts on the motherboard, check they're not damaged? I'm concerned that a damaged connector may be causing the reboots, which would require a motherboard replacement.
2)Can you confirm this reboot and 'data transfer failure' keeps happening if you change to another USB port (on your computer, not in a USB hub) and that you're using the original Motorola USB cable to flash and power your device? Or if you don't have the original USB cable, that you're using a high quality data+power USB cable?
3)I'll let ____Mdd verify this, but the 'data transfer failure (too many links) is possibly due to the volume and power keys pressed in?
Click to expand...
Click to collapse
1) It was connected and everything was working "well", maybe it's not a battery issue :/
2) it's the original motorola usb, I tried with the original one and a cheap one and happens the same
3) I don't press any key because it reboot itself and leads automatically to the fastboot screen each 5 seconds.
Thank you for your reply, it means a lot to me
letitrrain said:
1) It was connected and everything was working "well", maybe it's not a battery issue :/
2) it's the original motorola usb, I tried with the original one and a cheap one and happens the same
3) I don't press any key because it reboot itself and leads automatically to the fastboot screen each 5 seconds.
Thank you for your reply, it means a lot to me
Click to expand...
Click to collapse
Hmm, I'd try pressing each of the volume and power buttons whilst your device is off, checking that you feel a click when you push them and they retract properly.
Else, it's starting to look like a motherboard issue, hence why I was asking if the battery connector was possibly damaged or loosened at any point (from the teardown videos, it seems like a 2 pin plug). If you're in fastboot, you're at the base level of firmware that is accessible by us, so your system, recovery, kernel and other software shouldn't have loaded in at this point (bit like the BIOS or UEFI). The only other thing I can suggest would be to re-flash just the bootloader and GPT, but without a stable device, flashing either of them and getting interrupted would lead to a hard brick. I do not know if the hard brick would be fixable with this blankflash: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
What do you mean by 'working well' in your above post?
Related
Hi, I was trying to update my LG G2 D800 to Lollipop using this guide:
http://webtrickz.com/how-to-update-lg-g2-to-official-lollipop-os/
However, after the device rebooted, it went to the LG logo screen, displayed this message in the top left corner, and went to an indefinite black screen.
boot certification error
secure booting error
cause: boot certification verify
Holding down the power button for about 15 seconds turns the device off, but sometimes it turns itself back on and does it again. Turning it off, then quickly holding volume down and power button, releasing on logo, then holding again brings it to a "Factory Data Reset" screen, however, doing a reset does nothing and puts me immediately back to the same problem.
Holding volume up and plugging it into my PC does the same thing, and when plugged in, windows recognizes about 20 "unformatted drives", and shows it as QHSUB_BULK in device manager, under other devices.
Before this, I was running stock 4.4.2, D80020y, rooted with towelroot. I had attempted to create a TWRP recovery, and it said it succeeded, however it was unable to boot to recovery.
I was going to try to fix it using this thread: http://forum.xda-developers.com/showthread.php?t=2582142
However, I am unable to find an img for D80020y.
I have access to a Win 8..1 desktop, and I can run whatever OS necessary in a VM.
Does anyone know where to find one? Or, can anyone provide me with one? Or, is there another way to fix this?
I'm just worried that my device is totally gone at this point, and considering I bought it used, I have no warranty, nor a phone to replace it, currently.
Thanks so much to anyone who can help me!
First off, why didn't you just do an OTA update to Lollipop (via settings/about phone) instead of trying to manually do it? It's a lot easier and you could of avoided all of this...
Anyways, I am not sure what exactly happened (maybe it was a bad flash or maybe you screwed up somewhere), but it looks like you've gotten yourself in a real mess.
Did you triple check that you followed the article step by step? Did other people state in the comments about any problems they faced when using the method?
I have tried that method you linked before, and I used Ubuntu, which is best for that method. However, it did not work for me. I remember going on and on with that and ultimately just flat out replaced my logic board when I had a bricked G2.
And I can totally relate to to the twenty unformatted drives, I have been in same exact situation with the endless windows popups when I plug in my phone, but I never really figured out the issue. I remember before I was stuck in fast boot mode, and after awhile I couldn't even get to fast boot.
Can you get into recovery? Is the phone still alive? If so, you can use this to get back to stock http://forum.xda-developers.com/showthread.php?t=2432476
Hope this helps a bit, I have never been in your situation but if you want a real, simple solution to this: I would purchase and replace your logic board (phone's motherboard). It is a definite fix. If you are not comfortable with that, then I would advise to go ahead and do some research about this. Unfortunately, I have no idea where you can get that img (I do not have a D800, but rather a VS980), but I am sure with some Google searches you can find it.
I have bricked a couple phones in the past, and we all learn from our mistakes!
Best of luck!
fischer12345 said:
*snip*
Click to expand...
Click to collapse
I couldn't do an OTA update, as it's an AT&T phone, unlocked, and was running on TMobile. (Sorry, could've sword I specified that)
I was very careful that I followed all the steps of that article, to the period, but, again, Murphy's Law. I'm not sure what could have gone wrong.
And currently, I've tried every button combination I know and every one I could find from searching, and the only thing I can get into is the hard reset mode, but I cannot actually do a hard reset (just reboots with the same issue).
I've been unable to find specific d80020y img files after quite a bit of searching, but I will continue, and I've also contacted LG support in the event that by some act of god they can provide me with the files or another fix.
Jtpetch said:
I couldn't do an OTA update, as it's an AT&T phone, unlocked, and was running on TMobile. (Sorry, could've sword I specified that)
I was very careful that I followed all the steps of that article, to the period, but, again, Murphy's Law. I'm not sure what could have gone wrong.
And currently, I've tried every button combination I know and every one I could find from searching, and the only thing I can get into is the hard reset mode, but I cannot actually do a hard reset (just reboots with the same issue).
I've been unable to find specific d80020y img files after quite a bit of searching, but I will continue, and I've also contacted LG support in the event that by some act of god they can provide me with the files or another fix.
Click to expand...
Click to collapse
Gotcha. I haven't ran into the issue you have been describing at all before, but I just wanted to try to understand this situation a little better, I wish I could tell you what exactly happened.
As far as your problem, here's what I would do. The phone is still alive correct? Contact LG and send that bad boy in. Tell them you used it for a couple of months and all of a sudden it does not work anymore. I think that would be your best bet. However, do not tell them you modified it or whatever you tried to do with it.
Be aware if you do send it in to LG, make sure you have not tried to open up the phone and screw around with it internally. They will not fix it if that is the case. Also, it can be quite pricey depending on your current condition.
Oh, and LG will not provide you with those files, they are there to help you with any kind of phone issue, but not these kinds of issues.
This my friend is the best advice I can give you! Again, another option would be replacing the logic board, but that is ONLY a last resort.
BTW, you didn't hard brick it so that's a plus
I've not got a warranty, nor do I have the funds currently to have it repaired. That would be my last option.
Also, I'm not sure if this is helpful or relevant, but when I plugged it in to my PC just now, and it "recognized" the whole bunch of drives, I clicked through each one to see if it actually accessed anything. The "drive" it labeled "G:" had a single "image" folder in it, containing a bunch of .b00, .b01, .b02, etc files, and some .mdt files. (See picture)
Is this relevant at all? Could this help me?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Jtpetch said:
I've not got a warranty, nor do I have the funds currently to have it repaired. That would be my last option.
Also, I'm not sure if this is helpful or relevant, but when I plugged it in to my PC just now, and it "recognized" the whole bunch of drives, I clicked through each one to see if it actually accessed anything. The "drive" it labeled "G:" had a single "image" folder in it, containing a bunch of .b00, .b01, .b02, etc files, and some .mdt files. (See picture)
Is this relevant at all? Could this help me?
Click to expand...
Click to collapse
can you enter download mode? pressisng VOL UP and then plug your phone and keep button press. does it goes to usb icon with curved arrows?
No download mode for me. Trying to boot to it just brings me the same error, and black screen.
Jtpetch said:
No download mode for me. Trying to boot to it just brings me the same error, and black screen.
Click to expand...
Click to collapse
in device manager whats it says mine said QHSUSB _BULK
i know there are 2 different errors 9006- and 9008 i think.. have you try skr tools? it has the required files. for unbrick read thread. maybe you can use it.. try my link in signature and go to tools and check skr tools. its a 700 mb download as it has most variants needed files laf/boot ect those files you need.
raptorddd said:
in device manager whats it says mine said QHSUSB _BULK
i know there are 2 different errors 9006- and 9008 i think.. have you try skr tools? it has the required files. for unbrick read thread. maybe you can use it.. try my link in signature and go to tools and check skr tools. its a 700 mb download as it has most variants needed files laf/boot ect those files you need.
Click to expand...
Click to collapse
It says the same, QHSUSB_BULK. I've not tried skr tools (never heard of it before now). I'll try that out tomorrow, thank you.
Jtpetch said:
It says the same, QHSUSB_BULK. I've not tried skr tools (never heard of it before now). I'll try that out tomorrow, thank you.
Click to expand...
Click to collapse
do the QHUSB_BULK Fix when u try it (its in 4)
anyway i got my g2 in a much heavier brick,
i have a third party lab that can possibly fix my g2...
its not that expensive....
so I just need to hope they can fix it
Jtpetch said:
It says the same, QHSUSB_BULK. I've not tried skr tools (never heard of it before now). I'll try that out tomorrow, thank you.
Click to expand...
Click to collapse
this happened to me had HQSUSB_BULK showed many drives . but i could enter download mode and flashed KDZ all i had to do was change port 5 to 41.
are you sure you try download mode.? pres VOL UP keep presssing. then plug usb cable . if it shows the usb icon and a bar metter then you can KDZ
raptorddd said:
this happened to me had HQSUSB_BULK showed many drives . but i could enter download mode and flashed KDZ all i had to do was change port 5 to 41.
are you sure you try download mode.? pres VOL UP keep presssing. then plug usb cable . if it shows the usb icon and a bar metter then you can KDZ
Click to expand...
Click to collapse
Yes, I am sure. I just tried it again, though, to confirm. Held volume up, plugged in USB, and it went to the LG logo screen, showed the same error text in the top left, and went to a black screen.
I am downloading the SRKtool right now, and will try as soon as i have it.
Alrighty, so, progress (?).
I did the procedure with SRKtool, and at the end it told me to unplug it from USB and restart it, So i did that, and it went to the download mode screen, then it gave an error (Regrettably, it went too quick for me to read it), and now it's on the LG logo and has been for maybe 5 minutes, and the notification light is flashing multicolor.
EDIT: YES! I turned it off, since it wasn't doing anything, and i am able to get into download mode! Miracle!
So, is there anything else i need to to, or can i just flash Lollipop to it now, with download mode?
Jtpetch said:
Alrighty, so, progress (?).
I did the procedure with SRKtool, and at the end it told me to unplug it from USB and restart it, So i did that, and it went to the download mode screen, then it gave an error (Regrettably, it went too quick for me to read it), and now it's on the LG logo and has been for maybe 5 minutes, and the notification light is flashing multicolor.
EDIT: YES! I turned it off, since it wasn't doing anything, and i am able to get into download mode! Miracle!
So, is there anything else i need to to, or can i just flash Lollipop to it now, with download mode?
Click to expand...
Click to collapse
am not sure but there isnta kdz for lollipop right? you may need to go to KK KDZ
ooo you have d800 same as me. you need to download this and use the kitkat
Download Installer - KitKat 4.4.2 D80020c
http://forum.xda-developers.com/showthread.php?t=2663369 do that and once you in KITKAT ill tell you
if you need helps just ask
Ah, ok, will do. And thanks so much for all the help!
Jtpetch said:
Ah, ok, will do. And thanks so much for all the help!
Click to expand...
Click to collapse
no problem just hit thanks it i helped, once you in KK ill tell you how to go from there.
Wow, it flashed and everything without a hitch. I'm in KK now, and everything seems all good. So how would I go about upgrading to lollipop?
Thought I'd post back to share the conclusion.
Everything's working perfectly now, I flashed Lollipop through the flash tool, worked perfectly, and now I'm rooted, got a proper TWRP recovery set up, Xposed installed, and everything is good. Seems to run smoother on Lollipop too, and I was skeptical about the battery life, but it seems great
Jtpetch said:
Thought I'd post back to share the conclusion.
Everything's working perfectly now, I flashed Lollipop through the flash tool, worked perfectly, and now I'm rooted, got a proper TWRP recovery set up, Xposed installed, and everything is good. Seems to run smoother on Lollipop too, and I was skeptical about the battery life, but it seems great
Click to expand...
Click to collapse
am glad you liked it, just pass the knowledge when someone is in the same shoes as you were..
i have the same problem as you please help
Jtpetch said:
Alrighty, so, progress (?).
I did the procedure with SRKtool, and at the end it told me to unplug it from USB and restart it, So i did that, and it went to the download mode screen, then it gave an error (Regrettably, it went too quick for me to read it), and now it's on the LG logo and has been for maybe 5 minutes, and the notification light is flashing multicolor.
EDIT: YES! I turned it off, since it wasn't doing anything, and i am able to get into download mode! Miracle!
please guide me through what you did to get back to download
Click to expand...
Click to collapse
Hi Everyone
This is Guide how to repair your phone who was dead
My phone doesn't worked for 3 days so i get small trick and successfully repaired from dead
My phone was 5 times not worked like dead,Screen not Works ...only LED works,when i connect to pc usb device not recognized and nothing....
Explanation about my Problem:
IN MY CASE!
and the worst In my case Power button and Volume Buttons doesn't working so i open the BACK COVER eject the cable from volume button and insert small cable in slots to cover the pins like pressing volume up and down and finally connected to pc with usb
So we are starting the GUIDE:
1.First you need the drivers so you can get from this https://drive.google.com/folderview?id=0B1T7tp6tJ_3kX3p6SUxWb2NfWTQ&usp=sharing
2.After you installed the Drivers go to. Download mode if not goes try this... Press Volume UP and Volume DOWN and connect to usb to your pc
3.Go to device Manager to view the Port ,so the port can be "Android HS-USB QDLoader 9008 (COM3)"
4.Download the Panasonic Firmware Eluga and Extract (don't worry this is the same like idol 3 only name changed)https://docs.google.com/uc?id=0B01OmzpKE6vAVDhaSFN2aVFzaVU
5. After Extract you wil find EB-90S55EWLv1009.exe so run as administrator wait to load data
6.select 6045 and in the list down you can find your phone
7.and press the button "download"
8.So process starting ..indetifying your device you will get informations about imei..rooted or no .....
9.so automatically started to flashing the firmware (my it's go to 45 % and then i get error)
10.Don't worry press the button Reboot Device
11.and your device will reboot and you will view 'the screen powered by android and then panasonic so i get message Encrypted device just click the button "reset" and automatically device will be reseted and when wil finish with reset automatically reboots and wait to first boot you will get welcome screen set up and finished.....
12.So device successfully repaired from dead
If you want to go to CM or Stock for Idol 3
-i will write guide to unlock bootloader and flash TWRP recovery
-You must have Minimal Adb and Fastboot
-type "adb reboot-bootloader" to reboot into bootloader. The device should reboot to the screen showing " .powered by android". This is bootloader mode.
-Then type "fastboot -i 0x1bbb devices" should show some numbers and "fastboot" after the numbers
-Type "fastboot -i 0x1bbb oem device-info" shows device info including bootloader status (e.g. locked).
-Type "fastboot -i 0x1bbb oem unlock" to unlock the bootloader; after this you should get, for device info,
-Type "fastboot -i 0x1bbb oem device-info" and you should see "Device unlocked: true"
-You successfully unlocked the bootloader one step more to flash the recovery
-Download the TWRP RECOVERY FROM THIS LINK:
https://www.androidfilehost.com/?fid=24421527759881858
-Then copy from when you downlaod and paste the recovery in C:\Program Files\Minimal ADB and Fastboot
-Press Shift in the directory and click Right on mouse and open command promt here
-Type fastboot -i 0x1bbb flash recovery twrp-3.0.0-1.img or fastboot -i 0x1bbb boot twrp-3.0.0-1.img (if you want to test before installation)
-so successfully installed recovery and flash CM Or whatever you want
[/SIZE][/COLOR][/B]
Sorry for Grammatical Errors!
This guide will repair from dead....
in my case , buttons also doesn't work , how did you opened the back cover?
xZrender said:
in my case , buttons also doesn't work , how did you opened the back cover?
Click to expand...
Click to collapse
here's video how you can open
https://www.youtube.com/watch?v=FrFE8FdTXrY
Alek Dev said:
Hi Everyone
IN MY CASE!
and the worst In my case Power button and Volume Buttons doesn't working so i open the BACK COVER eject the cable from volume button and insert small cable in slots to cover the pins like pressing volume up and down and finally connected to pc with usb
Click to expand...
Click to collapse
i opened back cover , but how did you press the volume button , it doesnt work for me , i ont know what to do ;/
xZrender said:
i opened back cover , but how did you press the volume button , it doesnt work for me , i ont know what to do ;/
Click to expand...
Click to collapse
Eject cable from motherboatd....insert small cable in slots to cover the pins like pressing volume up and down and finally connected to pc with usb
problem with idol 3 4.7 6039K
Hi there,
I don't know if this is the correct section, I hope so, otherwise I really appreciate you can drive me to the appropriate one, it's new for me this forum!
I have an idol 3 4.7, where I have installed kingroot and after I took out (I didn´t reset the phone, Just unistall the app),
yesterday i received the update system message, I imagine for the marshmallow update, so I say Yes, install it.
But the phone entered in bootloop. I only have the initial screen with the options as Reboot system, adb and so on.
I tried to wipe but nothing. So now my phone stucked. I tried with an assistance center in Quito but they could't
My questions are:
may I use this system for 6039K?
Or does anybody hear about a solution in this case?
Should I open and take out the battery?
Please, any suggestion will be really welcome in order to make the phone work again.
P.
nipozzano said:
Hi there,
I don't know if this is the correct section, I hope so, otherwise I really appreciate you can drive me to the appropriate one, it's new for me this forum!
I have an idol 3 4.7, where I have installed kingroot and after I took out (I didn´t reset the phone, Just unistall the app),
yesterday i received the update system message, I imagine for the marshmallow update, so I say Yes, install it.
But the phone entered in bootloop. I only have the initial screen with the options as Reboot system, adb and so on.
I tried to wipe but nothing. So now my phone stucked. I tried with an assistance center in Quito but they could't
My questions are:
may I use this system for 6039K?
Or does anybody hear about a solution in this case?
Should I open and take out the battery?
Please, any suggestion will be really welcome in order to make the phone work again.
P.
Click to expand...
Click to collapse
Hello
This Guide only works with Idol 3 5.5
but i will explain how to restore your device
Can you try with Mobile upgrade Q to restore,if doesn't work
Use this guide from wiemar ,it should help to you because it's for your model
http://forum.xda-developers.com/showpost.php?p=63709274&postcount=113
If you any questions ask me
Hi ! I follow the guide up to the section 9, unfortunately, in the Panasonic Firmware Eluga and Extract after pressing download it stops after 2% and I have got the error message "load nprg error error code 5002". Does someone know how to fix that ?
Thanks !
Error
I get: "Master Clear: FAIL Flash Status: [COM3->PC[3]] COM3->PC[3] failed to erase misc (Error code = 40016) " :crying:
Now I get the same error that matcail... did you solved it ???
Good tutorial but it does not help me. My phone keeps on rebooting.
Schumi_wk said:
Good tutorial but it does not help me. My phone keeps on rebooting.
Click to expand...
Click to collapse
Tell me info About your phone? Model,Country,ROM...../?
All is standard, no root, no twrp and the latest software from alcatel, the model is 6045Y. But all of a sudden my phone decided to random reboot and it didn't stop
So i looked to unbrick it and came with a couple of options, first i tried to sideload software but that didn't work, than i tried it with Mobile upgrade from alcatel and that didn't work.
Than i saw this thread and tried it twice but after Panasonic and the sound it starts to reboot again. Now i'm trying again with Mobile upgrade.
All that is changed is the recovery interface it looks now like it is from MM.
Schumi_wk said:
All is standard, no root, no twrp and the latest software from alcatel, the model is 6045Y. But all of a sudden my phone decided to random reboot and it didn't stop
So i looked to unbrick it and came with a couple of options, first i tried to sideload software but that didn't work, than i tried it with Mobile upgrade from alcatel and that didn't work.
Than i saw this thread and tried it twice but after Panasonic and the sound it starts to reboot again. Now i'm trying again with Mobile upgrade.
All that is changed is the recovery interface it looks now like it is from MM.
Click to expand...
Click to collapse
More Looks like Hardware Problem Try again with Mobile q if not works...Send to warranty repair.....
Alek, thank you for this great guide. It saved my 6045k model.
I was messing around with AlekOS 3.0, had issues with lock screen and experimented with modems. I managed to permanently disable secondary sim slot (was using famewolf's modem backups). I forgot to copy modem.img backup to my PC! Also tried bunch of TWRP backups with no luck. My last hope was Mobile Upgrade Q and reverting back tu 5.0.2. Unfortunately with no success (only one sim slot is recognized again).
Finally I found this thread, followed the guide and I can confirm that it did solve sim issue. The setup finished with no errors that you mentioned. It got stuck at 45%, but after a while (10min) it completed successfully.
Cheers!
I'm in the same situation as you,but my problem is that Panasonic Eluga doesn't recognice my devide,drivers are correctly installed,I checked everything but nothing:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I´ve tried everything to downgrade my device (Mobile Q doesn't work) but nothing :crying:
peito said:
I'm in the same situation as you,but my problem is that Panasonic Eluga doesn't recognice my devide,drivers are correctly installed,I checked everything but nothing:
I´ve tried everything to downgrade my device (Mobile Q doesn't work) but nothing :crying:
Click to expand...
Click to collapse
You must do something Wrong...Press Pwr button and Volume up and down and thern connect to PC and then you will get RED SCREEN....Press Volume Up until you get Black screen and then press Download and if you get again same Send me Pm with Teamviewer ID AND PASS and i will try to help you
eXoSaX said:
Alek, thank you for this great guide. It saved my 6045k model.
I was messing around with AlekOS 3.0, had issues with lock screen and experimented with modems. I managed to permanently disable secondary sim slot (was using famewolf's modem backups). I forgot to copy modem.img backup to my PC! Also tried bunch of TWRP backups with no luck. My last hope was Mobile Upgrade Q and reverting back tu 5.0.2. Unfortunately with no success (only one sim slot is recognized again).
Finally I found this thread, followed the guide and I can confirm that it did solve sim issue. The setup finished with no errors that you mentioned. It got stuck at 45%, but after a while (10min) it completed successfully.
Cheers!
Click to expand...
Click to collapse
Alek Dev said:
You must do something Wrong...Press Pwr button and Volume up and down and thern connect to PC and then you will get RED SCREEN....Press Volume Up until you get Black screen and then press Download and if you get again same Send me Pm with Teamviewer ID AND PASS and i will try to help you
Click to expand...
Click to collapse
That is exactly what I'm doing,entering in Download mode and then download in the Panasonic software,but nothing,the program cannot read my phone,I'm really tired of trying this,I will stuck in your Alek rom (btw,no matter how many times I flash your modem,I cannot get the lock screen ).Ty anyway Alek and keep it up!!!!
Was on alek 3.0 before bootloop appear after a strange warning on android about battery, now got bootloop, no twrp access etc
try ur solution but after 45% and error, reboot and no screen about panasonic only bootloop
11.and your device will reboot and you will view 'the screen powered by android and then panasonic so i get message Encrypted device just click the button "reset" and automatically device will be reseted and when wil finish with reset automatically reboots and wait to first boot you will get welcome screen set up and finished.....
Click to expand...
Click to collapse
already tried SUGAR+QCT_SP+v10.5.1(4pda source) and mobile upgrade q 5.0.9, both finished without error after 100% but still bootloop
i think it s total broke with motherboard pb or battery
thorfr said:
Was on alek 3.0 before bootloop appear after a strange warning on android about battery, now got bootloop, no twrp access etc
try ur solution but after 45% and error, reboot and no screen about panasonic only bootloop
already tried SUGAR+QCT_SP+v10.5.1(4pda source) and mobile upgrade q 5.0.9, both finished without error after 100% but still bootloop
i think it s total broke with motherboard pb or battery
Click to expand...
Click to collapse
Looks Like Problem With Motherboard and Battery ..you can try again with Panasonic Firmware Tool and if this not help Send it to Warranty Repair
ok i m gonna send it to warr:crying:antly
retry mobil q upgrage wo success bootloop again
i have a problem with my moto g4 plus / moto g4 i was trying to unlock bootloader and trying to install twrp in my phone but i didnt succefully install twrp or unlock bootloader now i only show blank screen .. i cant entered in fast-boot or recovery mood when i press volum + or power button its show boot mood options when i select any option its just goes blank and nothing happend.. when i press volume down + power button its not responding and nothing happen ... when i connect with pc/laptop it conneting and reconneting and in device manager it only show mediatek android usb com something like this ...... please help me
Can you tell us the procedure you were following to unlock your bootloader and try to flash TWRP?
When you press volume down and power key, do you see the normal fastboot screen (not sure what you mean by boot mode options)? Do you see text like AP Fastboot Mode (secure), a green Android like this image? https://i.ytimg.com/vi/Ei3vCdq3jn0/maxresdefault.jpg
Sounds like you may have to try a cache wipe or factory reset, or a stock ROM re-flash. Can you tell us what stock ROM you had on your device before attempting to unlock your bootloader?
EDIT - wait, you're seeing Mediatek Android USB...? Can we see a screen shot of the Device Manager for your device please?
i try multi procedures but at end i try fastboot oem unlock and after this i start my phone its not starting and only moto logo appears after this i try to flash twrp by fastboot flash recovey twrp.img and when i install i start in recovery mode its stuck on recovery screen and after some time rebbot and stuck in boot loop
MZaib74 said:
i try multi procedures but at end i try fastboot oem unlock and after this i start my phone its not starting and only moto logo appears after this i try to flash twrp by fastboot flash recovey twrp.img and when i install i start in recovery mode its stuck on recovery screen and after some time rebbot and stuck in boot loop
Click to expand...
Click to collapse
Hmm, that's very odd - so you requested the unlock key from Motorola, booted your device to the bootloader, entered the key with 'fastboot OEM unlock <the unlock key>', did your device then erase itself and then reboot? Similar to what is described in this guide: https://forum.xda-developers.com/showpost.php?p=67031801&postcount=2
Also, did your bootloader look like this : https://i.ytimg.com/vi/Ei3vCdq3jn0/maxresdefault.jpg or like this : https://i2.wp.com/blogthetech.com/w...Fastboot-Mode-on-MTK.jpg?resize=819,369&ssl=1
What concerns me is that you mentioned your device is presenting itself to your computer as a Mediatek device (rather than Motorola or Qualcomm). Can you confirm this with a screenshot of your Device Manager and confirm you do have a Moto G4/G4 Plus?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
echo92 said:
Hmm, that's very odd - so you requested the unlock key from Motorola, booted your device to the bootloader, entered the key with 'fastboot OEM unlock <the unlock key>', did your device then erase itself and then reboot? Similar to what is described in this guide: https://forum.xda-developers.com/showpost.php?p=67031801&postcount=2
Also, did your bootloader look like this : https://i.ytimg.com/vi/Ei3vCdq3jn0/maxresdefault.jpg or like this : https://i2.wp.com/blogthetech.com/w...Fastboot-Mode-on-MTK.jpg?resize=819,369&ssl=1
What concerns me is that you mentioned your device is presenting itself to your computer as a Mediatek device (rather than Motorola or Qualcomm). Can you confirm this with a screenshot of your Device Manager and confirm you do have a Moto G4/G4 Plus?
Click to expand...
Click to collapse
MZaib74 said:
Click to expand...
Click to collapse
That image isn't showing up, you have to upload the image to XDA or another image host, we can't see into your C:\ drive...
i dont know how to upload image here
echo92 said:
That image isn't showing up, you have to upload the image to XDA or another image host, we can't see into your C:\ drive...
Click to expand...
Click to collapse
and its not like which is shown in links sent by you ... its have only three options recovery mood fastboot mood and normal mood when i select any of these my phone screen goes blank and nothoing hapend
MZaib74 said:
i dont know how to upload image here
Click to expand...
Click to collapse
MZaib74 said:
i dont know how to upload image here
Click to expand...
Click to collapse
Upload the image to https://imgbb.com or tiny pic http://tinypic.com then once uploaded, there should be a shareable link which you can paste here.
If you have Google drive or Microsoft one drive, then you could upload to there and share the file link.
---------- Post added at 09:39 PM ---------- Previous post was at 09:36 PM ----------
MZaib74 said:
and its not like which is shown in links sent by you ... its have only three options recovery mood fastboot mood and normal mood when i select any of these my phone screen goes blank and nothoing hapend
Click to expand...
Click to collapse
So your bootloader screen looks more like this? https://blog.hovatek.com/bpyeki/uploads/2015/01/MTK_Phone_entering_boot_mode.jpg
Where did you buy the phone from?
echo92 said:
Upload the image to https://imgbb.com or tiny pic http://tinypic.com then once uploaded, there should be a shareable link which you can paste here.
If you have Google drive or Microsoft one drive, then you could upload to there and share the file link.
---------- Post added at 09:39 PM ---------- Previous post was at 09:36 PM ----------
So your bootloader screen looks more like this? https://blog.hovatek.com/bpyeki/uploads/2015/01/MTK_Phone_entering_boot_mode.jpg
Where did you buy the phone from?
Click to expand...
Click to collapse
yes exectly this i buy from local market in Pakistan second hand not box packed
MZaib74 said:
yes exectly this i buy from local market in Pakistan second hand not box packed
Click to expand...
Click to collapse
MZaib74 said:
yes exectly this i buy from local market in Pakistan second hand not box packed
Click to expand...
Click to collapse
Ah, that's a boot screen from a phone with MediaTek processors. This matches with you mentioning that the Device Manager on Windows is detecting a MediaTek USB connection (the MediaTek preloader USB vcom). I see it's the same as what you uploaded.
The big problem here is that genuine Moto G4/G4 Plus devices come with Qualcomm Snapdragon 617 CPUs, not MediaTek, and don't present themselves as MediaTek devices to a computer. Unless you've been mistakenly sold a Moto E4/E4 Plus (which have MediaTek CPUs in them), on the available evidence thus far, I'm concerned you may have bought a fake clone G4/G4 Plus.
It could be that someone has somehow flashed MediaTek firmware onto a Moto G4/Plus, but I'm not sure if that is even possible, as the Snapdragon bootloader would likely block such a firmware flash. A boot screen from a genuine Moto G4 that is not modified was shown here: https://i.ytimg.com/vi/Ei3vCdq3jn0/maxresdefault.jpg You'd normally get to this by powering off, then hold the power and volume down keys together.
I don't have any experience repairing such devices, and the guides here only will help you with Snapdragon/genuine Moto G4 devices. All I can do is point to guides like this https://www.engineerthink.com/blog/...ediatekmtk-android-phone/?PageSpeed=noscript' and hope you can find some firmware for this particular device. I hope that posting here https://forum.xda-developers.com/android/help might get you some assistance as well.
EDIT - What happens if you select normal mode, does your device boot?
Otherwise, I hope you can get your money back.
By the way thanks alot for helping me
is chaning of mother board will help me or not ??
i forget to tell you one thing my phone not showing in pc permanently its detected and flash for 1 sec and disappers from device manager and doing this process continusly
MZaib74 said:
is chaning of mother board will help me or not ??
Click to expand...
Click to collapse
Changing the motherboard, if there are spare motherboards that will fit your device, will be expensive, and may cost more than what you paid for the device. Are you hoping to try putting in a Moto G4 motherboard? Also, we don't know if the other components in the device are genuine or possible fakes as well, so you may have a genuine motherboard but low quality parts (e.g. the camera) that will impair your experience.
I'd try selecting normal mode in that boot list, see if you can get it booting again. Or perhaps try a factory reset from recovery, if you're willing to do so (as this will wipe your data).
Apologies about this - the evidence you've presented matches up unfortunately. I hope that you can get a refund from the seller for selling a non-genuine device if you so choose.
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
MZaib74 said:
i forget to tell you one thing my phone not showing in pc permanently its detected and flash for 1 sec and disappers from device manager and doing this process continusly
Click to expand...
Click to collapse
Hmm, can you check if the USB cable is plugged in fully and securely, and in a fully working USB port on your computer? Does it keep happening if you keep the device still, or get worse if you move the device around whilst still plugged in?
i try nothing happend when i connect another phone work fine
i dont know what to do know i think its better to leave it
So I downloaded the Android 7.1.1 and installed it via the update tool on the phone. I have not rooted, nor was I running a custom rom.
Everything went fine, until I looked over and noticed the phone was turned off. I figured it was part of the process, but after leaving it, nothing happened. I now can not power the phone on(It won't even vibrate to indicate it is trying)
The LED is also not turning on when I plug it in.
Any ideas?
viper98 said:
So I downloaded the Android 7.1.1 and installed it via the update tool on the phone. I have not rooted, nor was I running a custom rom.
Everything went fine, until I looked over and noticed the phone was turned off. I figured it was part of the process, but after leaving it, nothing happened. I now can not power the phone on(It won't even vibrate to indicate it is trying)
The LED is also not turning on when I plug it in.
Any ideas?
Click to expand...
Click to collapse
Couple of questions:
1. Where did you download Nougat 7.1.1 from?
2. Did you get any message when you unzip the file?
3. Did you notice anything unusual during update before you realised the phone didn't turn on?
Try if you can get into recovery by holding Power and Volume Up. If you can, try updating from there. That is, copy the update zip to the external sdcard, find Apply update from external sdcard, press the Power button. Let it finish then Reboot.
Good luck
priority1 said:
Couple of questions:
1. Where did you download Nougat 7.1.1 from?
2. Did you get any message when you unzip the file?
3. Did you notice anything unusual during update before you realised the phone didn't turn on?
Try if you can get into recovery by holding Power and Volume Up. If you can, try updating from there. That is, copy the update zip to the external sdcard, find Apply update from external sdcard, press the Power button. Let it finish then Reboot.
Good luck
Click to expand...
Click to collapse
I found it online, based on the link it looks like it is from ZTE's russia page.
This could be why it happened?
I got no messages at all. I just selected to install from an SD card in the settings menu, and it started everything.
As best as I can tell, it went out while the little android guy was on screen.
Can't get to recover, phone won't power on at all. Tried holding the power button for 45 seconds and that also did nothing.
viper98 said:
I found it online, based on the link it looks like it is from ZTE's russia page.
This could be why it happened?
I got no messages at all. I just selected to install from an SD card in the settings menu, and it started everything.
As best as I can tell, it went out while the little android guy was on screen.
Can't get to recover, phone won't power on at all. Tried holding the power button for 45 seconds and that also did nothing.
Click to expand...
Click to collapse
I downloaded from ZTE Russian site as well and updated fine. Nothing wrong with the software.
As you can't even boot into recovery, I'm afraid your phone is permanently bricked. I'm at my wits end. Maybe someone else has a better idea.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also have a bricked Axon 7 mini, what we need is to figure out where the Test-Point is located. I have tried to find it without success.
@ viper98,,
In you case, you can send your phone to repair center. This issue might not be fixed by flash or TWRP.
Thanks!
http://4pda.ru/pages/go/?u=https://...ye9SnceAq6QQRTGdMO9DSeNx6dN4/view?usp=sharing
nten2 said:
http://4pda.ru/pages/go/?u=https://...ye9SnceAq6QQRTGdMO9DSeNx6dN4/view?usp=sharing
Click to expand...
Click to collapse
Thank you! Axon 7 Mini is back from the dead!
reticuli said:
Thank you! Axon 7 Mini is back from the dead!
Click to expand...
Click to collapse
hi. could you please let me know exactly how you did this?
mine is totally dead, no buttons work, not detected by pc in any way.
made a deepflash cable....nothing
only a tiny dash at the corner of the screen, blinking when connected to pc.
if I open the phone and shortcircuit the test point would I get the COM port detected?
this is all I need, but I thought what you did was the same as the deepflash cable does?
PLEASE!!!! I killed it trying to roll back to android 6 after upgrading to 7 loosing my imei,.
now I don't care about imei, just bring it back to life. but to be honest I think mine is gone forever.....
did you remove the battery to make sure the phone was not in charging mode? please....how did you do it?
Thanks in advance
EDL-MODE Test-Point method
1. Open up your phone and disconnect the battery
2. Circuit test-point
3. Use deepflash cable and push button
4. Connect the battery
5. Push button on deepflash cable or change to regular usb cable when you see HS-USB Diagnostics 9008 in device manager. Flash edl recovery image with miflash.
Only Deepflash Cable method without opening phone
1. Use deepflash cable and push button
2. Press power key
3. Look for HS-USB Diagnostics 9008 in device manager.
With the right deepflash it's the same as using test-point. It was not that easy to open the phone. This one from ebay is the only deepflash cable that worked for me, tried my own homemade without success. https://www.ebay.com/itm/2-in1-Deep...140594?hash=item3af2795332:g:8kgAAOSw-QZZyfgH
reticuli said:
EDL-MODE Test-Point method
1. Open up your phone and disconnect the battery
2. Circuit test-point
3. Use deepflash cable and push button
4. Connect the battery
5. Push button on deepflash cable or change to regular usb cable when you see HS-USB Diagnostics 9008 in device manager. Flash edl recovery image with miflash.
Only Deepflash Cable method without opening phone
1. Use deepflash cable and push button
2. Press power key
3. Look for HS-USB Diagnostics 9008 in device manager.
With the right deepflash it's the same as using test-point. It was not that easy to open the phone. This one from ebay is the only deepflash cable that worked for me, tried my own homemade without success. https://www.ebay.com/itm/2-in1-Deep...140594?hash=item3af2795332:g:8kgAAOSw-QZZyfgH
Click to expand...
Click to collapse
cool. thanks mate, I'll be ordering the cable tonight will post you back in a couple of days........
you help was truly appreciated....
reticuli said:
EDL-MODE Test-Point method
1. Open up your phone and disconnect the battery
2. Circuit test-point
3. Use deepflash cable and push button
4. Connect the battery
5. Push button on deepflash cable or change to regular usb cable when you see HS-USB Diagnostics 9008 in device manager. Flash edl recovery image with miflash.
Only Deepflash Cable method without opening phone
1. Use deepflash cable and push button
2. Press power key
3. Look for HS-USB Diagnostics 9008 in device manager.
With the right deepflash it's the same as using test-point. It was not that easy to open the phone. This one from ebay is the only deepflash cable that worked for me, tried my own homemade without success. https://www.ebay.com/itm/2-in1-Deep...140594?hash=item3af2795332:g:8kgAAOSw-QZZyfgH
Click to expand...
Click to collapse
After 2 months I also recovered mine from its "deep afterlife".
The above procedure was quite straightforward, actually all you need is patience, skills to open the phone to begin with, perseverance, but most of all...... faith!
To be honest I'm not sure how, but after the test point nothing happened, and I left my phone plugged in, battery disconnected, and left it alone for a while to finally hear the windows driver sound.......at the end it worked. Thanks a lot.
demenicis said:
After 2 months I also recovered mine from its "deep afterlife".
The above procedure was quite straightforward, actually all you need is patience, skills to open the phone to begin with, perseverance, but most of all...... faith!
To be honest I'm not sure how, but after the test point nothing happened, and I left my phone plugged in, battery disconnected, and left it alone for a while to finally hear the windows driver sound.......at the end it worked. Thanks a lot.
Click to expand...
Click to collapse
Yeah it is no fun to open up the phone. Happy to hear that you revived the phone from the dead.
Before anything, let me state that there is no official Xiaomi tech support centers in my country, nor any offhand tech support houses that deal with Xiaomi devices. I don't know where to proceed here, and I haven't found any solutions online, so any help would be greatly welcomed.
So, my phone suffered some kind of freezing and after forcing reset it entered EDL mode (doesn't turn on, doesn't enter into fastboot, LED blinking in rapid intervals, PC recognizes it as Qualcomm HS 9008, the usual.)
EDIT: The issue is now different. I'll attach an error log below.
Basically, it stays on "ping target via firehose" before throwing this abomination of an error chain:
[12:43:50 AM]:9 COM9 83.4960975s [12:43:50 AM COM9]:System.Exception: [12:43:50 AM COM9]:error:The write timed out.
at XiaoMiFlash.code.Utility.Log.w(String deviceName, String msg, Boolean throwEx) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\Log.cs:line 102
at XiaoMiFlash.code.Utility.Comm.WritePort(Byte[] send, Int32 offSet, Int32 count) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\Comm.cs:line 232
at XiaoMiFlash.code.Utility.Comm.SendCommand(String command, Boolean checkAck) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\Comm.cs:line 260
at XiaoMiFlash.code.bl.SerialPortDevice.ping() in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\bl\SerialPortDevice.cs:line 751
at XiaoMiFlash.code.bl.SerialPortDevice.flash() in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\bl\SerialPortDevice.cs:line 65 at XiaoMiFlash.code.Utility.Log.w(String deviceName, String msg, Boolean throwEx) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\Log.cs:line 102
at XiaoMiFlash.code.Utility.Comm.WritePort(Byte[] send, Int32 offSet, Int32 count) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\Comm.cs:line 232
at XiaoMiFlash.code.Utility.Comm.SendCommand(String command, Boolean checkAck) in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\Comm.cs:line 260
at XiaoMiFlash.code.bl.SerialPortDevice.ping() in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\bl\SerialPortDevice.cs:line 751
at XiaoMiFlash.code.bl.SerialPortDevice.flash() in D:\Workspace\MiFlash\XiaoMiFlash\XiaoMiFlash\code\bl\SerialPortDevice.cs:line 65
Click to expand...
Click to collapse
The cable works fine, and other cables yield the same results. Using different ports or another computer doesn't help either.
Again, I'd be immensely grateful for any kind of help you could provide here.
Cheers!
Use a different USB port it worked out for me.
daveve said:
Use a different USB port it worked out for me.
Click to expand...
Click to collapse
Tried this, also switching cables and trying to do it on a different computer. No luck.
Update: managed to get past the whole hello packet thing, but I'm hitting another barrier now.
Miflash displays "ping target via firehose" for several seconds until it displays "the write timed out" followed by a long as heck description of the error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You tried cosmicdan's low level backup & restore?
.:Addicted:. said:
You tried cosmicdan's low level backup & restore?
Click to expand...
Click to collapse
I took a look at it, but what I understood from it is that you need to kick into fastboot and run some commands, which I can't since I cannot access fastboot mode
Edit: added an error log to the OP
KurisuSama said:
I took a look at it, but what I understood from it is that you need to kick into fastboot and run some commands, which I can't since I cannot access fastboot mode
Edit: added an error log to the OP
Click to expand...
Click to collapse
Nop. Those fastboot commands are only to enter edl mode. But you are already in edl mode.
Try with that tool.
And did it worked out for you? I am getting a null message when restoring backup with low level app from @CosmicDan
.:Addicted:. said:
Nop. Those fastboot commands are only to enter edl mode. But you are already in edl mode.
Try with that tool.
Click to expand...
Click to collapse
daveve said:
And did it worked out for you? I am getting a null message when restoring backup with low level app from @CosmicDan
Click to expand...
Click to collapse
Just tried cosmicdan's tool, it didn't work
I also tried flashing on QFIL again and it doesn't work either
You should probably tell us how you got to this point. That could help us decide if its broken on a hardware level or not. Usually QFIL will get you out if you do it right. But, in special cases, it wont.
tytydraco said:
You should probably tell us how you got to this point. That could help us decide if its broken on a hardware level or not. Usually QFIL will get you out if you do it right. But, in special cases, it wont.
Click to expand...
Click to collapse
In my case Miflash and qfil are flashing both successful but phone don't go on after flash. Led blinks white when I put him in the charger but don't charge. BTW I am using the test point method because my phone don't go in fastboot.
tytydraco said:
You should probably tell us how you got to this point. That could help us decide if its broken on a hardware level or not. Usually QFIL will get you out if you do it right. But, in special cases, it wont.
Click to expand...
Click to collapse
I left the phone next to me for 30 minutes while browsing the web, picked it up, saw that it was frozen and hard reset it by holding the power button. Then it got like this.
daveve said:
And did it worked out for you? I am getting a null message when restoring backup with low level app from @CosmicDan
Click to expand...
Click to collapse
Can you please give me the app link?
Rakibboss said:
Can you please give me the app link?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a1/how-to/tool-low-level-backup-restore-unbrick-t3790307
KurisuSama said:
I left the phone next to me for 30 minutes while browsing the web, picked it up, saw that it was frozen and hard reset it by holding the power button. Then it got like this.
Click to expand...
Click to collapse
I've had my phone a few times act in the same manner, but I had flashed Custom Roms, so maybe a bug in the Rom, but the point is, when I did things in the usual manner, just pressing for the normal amount of time it typically takes to power it on, go to fastboot, recovery etc., nothing worked, which sounds a bit like you.
SO, I was really in a panic thinking my phone was dead, but then I just held the buttons down for as long as it took and the phone rebooted.
So if you didn't try, hold down the buttons for up to 1 minute and see what happens, just play back and forth and hold them for a long time.
I can't tell you why, but sometimes it just gets bloody stuck and takes a lot of back and forth trying to get it to boot.
Try in this order and see;
1. Hold down power button down for 1 min
2. Hold buttons down for fastboot for 1 min
3. Hold buttons down for recovery 1 min
When I did it in this order, it eventually booted into recovery for me.
good luck
DoR3M3 said:
I've had my phone a few times act in the same manner, but I had flashed Custom Roms, so maybe a bug in the Rom, but the point is, when I did things in the usual manner, just pressing for the normal amount of time it typically takes to power it on, go to fastboot, recovery etc., nothing worked, which sounds a bit like you.
SO, I was really in a panic thinking my phone was dead, but then I just held the buttons down for as long as it took and the phone rebooted.
So if you didn't try, hold down the buttons for up to 1 minute and see what happens, just play back and forth and hold them for a long time.
I can't tell you why, but sometimes it just gets bloody stuck and takes a lot of back and forth trying to get it to boot.
Try in this order and see;
1. Hold down power button down for 1 min
2. Hold buttons down for fastboot for 1 min
3. Hold buttons down for recovery 1 min
When I did it in this order, it eventually booted into recovery for me.
good luck
Click to expand...
Click to collapse
Tried this a few times in the order you described, and a few more switching up the steps, but had no luck.
KurisuSama said:
Tried this a few times in the order you described, and a few more switching up the steps, but had no luck.
Click to expand...
Click to collapse
Maybe someone has some other ideas...
daveve said:
In my case Miflash and qfil are flashing both successful but phone don't go on after flash. Led blinks white when I put him in the charger but don't charge. BTW I am using the test point method because my phone don't go in fastboot.
Click to expand...
Click to collapse
After flashing in qdloader mode connect your device to pc and see if it recognize somthing or not
If port 900E detected tell me to guide you
But if doesnt found any device i think you didnt connect battery cable
emprazol said:
After flashing in qdloader mode connect your device to pc and see if it recognize somthing or not
If port 900E detected tell me to guide you
But if doesnt found any device i think you didnt connect battery cable
Click to expand...
Click to collapse
Battery cable is in after flash but for me it doesn't do anything after words. The phone don't get detected by pc only a white led keeps blinking. It doesn't matter which button combination I use phone don't boot up. Strange thing is after flash the phone got recognize by charger and gives a white blinking led.
Hold the power button for a second then relase the power key and try to going into fastboot mode and then flash with Mi Tools