I recently updated my Poco M3, it updated correctly but after that, it doesn't turn on anymore, I searched about it and I found that it was a problem with the update. I managed to turn on my phone again by pressing 13 seconds the power button, after that, I received a new update so I thought the update fixed that but when the phone rebooted to install the new update it doesn't turn on anymore. I've tried to enter fast boot mode but doesnt't works.
I don't know what should I do, I've tried again to hold on the power button and I also tried to enter fast boot but as I said it doesn't work. Also when I plug my phone to charge it, nothing happens
I hope someone can help me, and sorry for my bad English.
you need to drain your battery first. same happen to my poco m3. after that you need to flash your firmware or else it will happen again after you reboot.
vinzikidz said:
you need to drain your battery first. same happen to my poco m3. after that you need to flash your firmware or else it will happen again after you reboot.
Click to expand...
Click to collapse
And how can I flash the firmware? I've tried using the Xiaomi Flash tool but it asks me for a Mi account that is valid for the process.
charecktowa said:
And how can I flash the firmware? I've tried using the Xiaomi Flash tool but it asks me for a Mi account that is valid for the process.
Click to expand...
Click to collapse
unlock bootloader. install twrp. flash firmware
charecktowa said:
I recently updated my Poco M3, it updated correctly but after that, it doesn't turn on anymore, I searched about it and I found that it was a problem with the update. I managed to turn on my phone again by pressing 13 seconds the power button, after that, I received a new update so I thought the update fixed that but when the phone rebooted to install the new update it doesn't turn on anymore. I've tried to enter fast boot mode but doesnt't works.
I don't know what should I do, I've tried again to hold on the power button and I also tried to enter fast boot but as I said it doesn't work. Also when I plug my phone to charge it, nothing happens
I hope someone can help me, and sorry for my bad English.
Click to expand...
Click to collapse
Drain out your battery and then just plug the charger then wait.
I had this happen to me 2 times now,it would take days if your phone fully charged like mine,it takes 5 days.
After that,
make sure to backup your phone,unlock your bootloader and then re-flash the stock rom with Mi-Flash or just use another rom to your liking.
The truth is I like the stock MIUI than any other rom but if this kind of problem keep happening,I rather just flash another rom.
Hopes this help fixing your phone,sorry for the rant there.
Biggest problem with this phone is , there's no way to force reset the phone. I literally tried everything from vol up + power and volume down + power and everything else Buying this phone is prolly one of the biggest regret of my life. And the youtuber xiaomi slaves didnt help. But my real question is.... Will flashing custom rom fix this problem?
yankee77 said:
Biggest problem with this phone is , there's no way to force reset the phone. I literally tried everything from vol up + power and volume down + power and everything else Buying this phone is prolly one of the biggest regret of my life. And the youtuber xiaomi slaves didnt help. But my real question is.... Will flashing custom rom fix this problem?
Click to expand...
Click to collapse
Same question...i have experienced deadboot in this poco m3 4 times already...the only option is to remove the battery and put it back again...then hold power button to turn it on...no fastboot...no recovery mode...i dont have a choice but to open it and remove the battery...now...my question is...What if i flashed a custom rom...will it fix deadboot issue on this phone?
charecktowa said:
I recently updated my Poco M3, it updated correctly but after that, it doesn't turn on anymore, I searched about it and I found that it was a problem with the update. I managed to turn on my phone again by pressing 13 seconds the power button, after that, I received a new update so I thought the update fixed that but when the phone rebooted to install the new update it doesn't turn on anymore. I've tried to enter fast boot mode but doesnt't works.
I don't know what should I do, I've tried again to hold on the power button and I also tried to enter fast boot but as I said it doesn't work. Also when I plug my phone to charge it, nothing happens
I hope someone can help me, and sorry for my bad English.
Click to expand...
Click to collapse
have you try test point?
Hopefully this doesnt happen to anyone.. saw this vid on youtube. Basically poco m3 doesnt turn on even when battery connectors removed.
yankee77 said:
yankee77 said:
Hopefully this doesnt happen to anyone.. saw this vid on youtube. Basically poco m3 doesnt turn on even when battery connectors removed.
Click to expand...
Click to collapse
It did happen to me and I did pull the battery connector even pull the display connector while doing it.I read a post on reddit about it,pull the battery and display connector and then try connect it back while pushing the power button,the guy said the phone did turned on but whenever he tried to restart,phone would not boot and he would repeat that unplug,plug,hold power thinggy .I did try the method but nothing happened.Plug in to pc would only detect it as in EDL mode,with a locked bootloader theres nothing I can really do as flashing it would only met with this and that error.Then I read someone on a forum said to just let the phone fully discharged and try to plug in charger and wait for the battery empty logo pop on screen then the phone would boot as normal.It did work for me but I gone through nearly 5 days as my phone was fully charged.Its been like 4-5 days now and eventhough I already downloaded the latest ota for miui global,Im still dreading to install it as Im afraid the same problem would occurs again.Maybe I should unlock my bootloader first so the next time my phone goes EDL mode again,things would get easier to do.Sorry if this rants of mine a bit too long.
Click to expand...
Click to collapse
i did a factory reset.... but the phone didnt turned back on. i did do the ota update three times prior to this one which failed three times. .. the first one prolly broke the recovery and fastboot mode ... im not sure what to do after this. since i cant go to recovery or fastboot mode. this is prolly the first time i experienced this. where the ota itself which is supposed to make the phone better broke the phone. it will prolly turn on after it got drained but im not sure how to update firmware without recovery or fastboot and yes this is a ****ty phone and company alright. i send my logs to xiaomi. and still no response from them.
tnx sa share boss malaking tulong
when i heat ( about 3 to 5 sec. or more with soldering iron and flux) camera power ic under ( Power Control IC PMI632-902 ) the phone boots up
HCBE AKD written on this ic
in some other m3 phones that text is different
it has 4*3 pin under lower left side of shield
phone boots up with this method one time
if you use flux phone will be good till 1 hour power off then problem comes back
i neeeeeed schematic diagram of this phone's motherboard...
in some cases when you unplug battery
then short circuit with power key
then plug pc usb till flashing screen
after that i connect battery with holding down power key and usb connected
phone powers on from edl mode to normal mode (in some cases lcd flashes in some other battery icon shows rapidly and gets off)
ow in cit mode #27-charger test some phones we have red text battery test fail insted blue text that ask reverse plug usb type c connection)
is there another test or somting else???
{
"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"
}
does the phone go to fastboot with adb
Any update on this?
I have this same problem
How can I drain the batter ?
vinzikidz said:
you need to drain your battery first. same happen to my poco m3. after that you need to flash your firmware or else it will happen again after you reboot.
Click to expand...
Click to collapse
after you reflashed, did you encounter the same problems again?
pidliget said:
does the phone go to fastboot with adb
Click to expand...
Click to collapse
no just edl mode
phone current in charge is about 100 mAmp
if you heat motherboard phone turns on get charge normally and every thing is ok till you get reboot or turn phone off
vinzikidz said:
you need to drain your battery first. same happen to my poco m3. after that you need to flash your firmware or else it will happen again after you reboot.
Click to expand...
Click to collapse
How do I drain the battery
ArcherXY said:
How do I drain the battery
Click to expand...
Click to collapse
Poco m3 drains battery by itself. General rule of the thumb
1-10% - 0 to 1 day
11-20% - 2 days
Basically 1 day is around 10% of battery
I think the motherboard is on but for some odd reason the display board and basically the whole thing doesnt turn on on. But it still is draining battery even when turned off. Removing the battery doesnt fix it. I tried several times
Related
Hello, i was trying to charge my nexus 4 couse it wouldn't turn on but after an hour it still didn't turn on.
So after trying a liitle wile to turn it on i held all three buttons (power, volume up & down) and now it says "Download Mode".
{
"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"
}
Never heard of this mode. Try connecting ur phone to pc and see if it gets detected. That would be nice to know.
gt-kingz said:
Never heard of this mode. Try connecting ur phone to pc and see if it gets detected. That would be nice to know.
Click to expand...
Click to collapse
srry just restarted (it don't appear on the computer, can check with lsusb on ubuntu but not now)
How to do it!
How to get into Download Mode
Boot into bootloader and hold all three buttons
It's LG's version of Samsung's Odin mode. However, there isn't a leak of the utility yet.
There is a long tutorial on how to use it in the Nexus 4 service manual floating around.
Basically it's worthless for us until that utility leaks.
El Daddy said:
It's LG's version of Samsung's Odin mode. However, there isn't a leak of the utility yet.
There is a long tutorial on how to use it in the Nexus 4 service manual floating around.
Basically it's worthless for us until that utility leaks.
Click to expand...
Click to collapse
I'm not entirely sure, but I think that "Download mode" interfaces with LGNPST. From my understanding, it's not publicly available, but...
Anyway, this is an interesting thread.
efrant said:
I'm not entirely sure, but I think that "Download mode" interfaces with LGNPST. From my understanding, it's not publicly available, but...
Anyway, this is an interesting thread.
Click to expand...
Click to collapse
Interesting indeed. So it looks like I'm wrong. Most of that stuff is way over my head though.
Sent from my Nexus 7 using xda premium
When I first rooted I flashed a bad recovery that deleted all my stuff and got into DL mode 3 times, I panicked. Somehow I managed to get back into boot loader and after that flashed stock boot.IMG and re-rooted...
Sent from my Nexus 4 using xda app-developers app
309041291a said:
When I first rooted I flashed a bad recovery that deleted all my stuff and got into DL mode 3 times, I panicked. Somehow I managed to get back into boot loader and after that flashed stock boot.IMG and re-rooted...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
i'm in the same situation and appropriate anybody's help to get me back into the right track.
So what happened with this? Mine just did the same while doing the rooting of my phone. I've been using MSKIP's tutorial amongst other youtube videos showing his option in depth. No idea what happened but now I'm stuck in this "brick" or "soft brick" mode like you guys were saying earlier. What is the solution? I don't see any other pages in this thread and I'm a total noob with this stuff.
**Edit**
Fixed mine, was waiting for a while like it said but I finally powered it one, did a factory reset, and re-did everything else that comes with the 1 CLICK FOR ALL button on mskip's toolkit. Everything is perfect now and I hacked it, whoo hoo!
easy fix... working..
Jbele said:
Hello, i was trying to charge my nexus 4 couse it wouldn't turn on but after an hour it still didn't turn on.
So after trying a liitle wile to turn it on i held all three buttons (power, volume up & down) and now it says "Download Mode".
Click to expand...
Click to collapse
this same problem happened to me today.. don't worry there is a fix...
1.Get into bootloader ( Press all three buttons at same time)
2.flash google factory image from fastboot. get factory images from here... https://developers.google.com/android/nexus/images ..
3.If you dont know how to flash use mskip's toolkit for nexus 4 and flash it... (best for new users like me) get mskip's toolkit from here... http://forum.xda-developers.com/showthread.php?t=1995688
ALL THANKS TO MSKIP'S TOOLKIT
if you have queries or want detailed information comment below
NICE FEELING WHEN YOU SEE DOWNLOAD MODE... WORTH EXPERIENCING THE MINI HEART ATTACK..
DON'T WORRY ITS NEARLY IMPOSSIBLE TO BRICK NEXUS 4..
:good::good::good: ALL THE BEST:good::good::good:
HOPE THIS WORKS
shengovind said:
this same problem happened to me today.. don't worry there is a fix...
1.Get into bootloader ( Press all three buttons at same time)
2.flash google factory image from fastboot. get factory images from here... https://developers.google.com/android/nexus/images ..
3.If you dont know how to flash use mskip's toolkit for nexus 4 and flash it... (best for new users like me) get mskip's toolkit from here... http://forum.xda-developers.com/showthread.php?t=1995688
ALL THANKS TO MSKIP'S TOOLKIT
if you have queries or want detailed information comment below
NICE FEELING WHEN YOU SEE DOWNLOAD MODE... WORTH EXPERIENCING THE MINI HEART ATTACK..
DON'T WORRY ITS NEARLY IMPOSSIBLE TO BRICK NEXUS 4..
:good::good::good: ALL THE BEST:good::good::good:
HOPE THIS WORKS
Click to expand...
Click to collapse
it happened to me now, when the battery was dead. when i connect the phone to a wall charger i got the download mode massage ,
when i'm pressing all 3 buttons the phone makes a vibe (like a boot vibe) and the the red light is flashing on/off
no bootloader.
what to do?
havlaz said:
it happened to me now, when the battery was dead. when i connect the phone to a wall charger i got the download mode massage ,
when i'm pressing all 3 buttons the phone makes a vibe (like a boot vibe) and the the red light is flashing on/off
no bootloader.
what to do?
Click to expand...
Click to collapse
You should try to get into the fastboot mode first, when the phone is off, Hold Power + Volume Download button. If you can get in the fastboot menu, then use instruction above to reflash your device.
If you can't, you might be able to recover your phone using Download Mode: http://forum.xda-developers.com/showthread.php?t=2347060
havlaz said:
it happened to me now, when the battery was dead. when i connect the phone to a wall charger i got the download mode massage ,
when i'm pressing all 3 buttons the phone makes a vibe (like a boot vibe) and the the red light is flashing on/off
no bootloader.
what to do?
Click to expand...
Click to collapse
Red light due to battery low..
All you have to do is charge the phone for about six hours on the wall charger..
Then try booting your phone ..
If there's only bootloader and phone isn't booting flash factory from fastboot..
Plug it to wall charger over night.. Then try to get to download mode..
Try this to get out of red light only if there is absolutely no other way..: http://forum.xda-developers.com/showthread.php?t=2250454
If there is no boot loader whatsoever even after trying for a hell lot of time, only download mode, then do this..
http://forum.xda-developers.com/showthread.php?t=2347060
sent from my Prevert nexus
psak said:
i'm in the same situation and appropriate anybody's help to get me back into the right track.
Click to expand...
Click to collapse
When you are in download mode, press and hold Vol Down and Power, that should bring up fastboot mode, which you can use to flash another recovery...
[email protected] said:
When you are in download mode, press and hold Vol Down and Power, that should bring up fastboot mode, which you can use to flash another recovery...
Click to expand...
Click to collapse
Try Pressing power button alone for 10 sec or so...
Should do the trick
Having the same problem. I was on purity rom(4.4.3), with default purity kernel. I flashed the Ak poseidon kernel, with Ukm. It booted fine , was on phone for about 4 minutes, and then I ran antutu benchmark. Before that I didn’t change anything via synapse app. Then when I ran test on antutu phone went off. Non of the buttons were responding. I plugged the phone into wall charger and pressed all 3 buttons. Then the download mode appeared. Left it like that on the charger , went to sleep. When I woke up the phone was turned off. Today I was flashing factory img ( 4.4.3. occam). Following the instructions http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312 [/URL]. Everything went ok no problem in the cmd , only the thing was , when I had to fastboot the booth loader, then the phone stuck in power on loop . ( reboots, then it says google, and reboots again) I was able to stop this by holding volume down, then it goes into bootloader. Finished flashing factory img, like it says on the tut. And the same thing happens. The phone won’t boot, And it is not responding when it is unplugged. Please help :/
---------- Post added at 03:28 PM ---------- Previous post was at 03:26 PM ----------
shengovind said:
Red light due to battery low..
All you have to do is charge the phone for about six hours on the wall charger..
Then try booting your phone ..
If there's only bootloader and phone isn't booting flash factory from fastboot..
Plug it to wall charger over night.. Then try to get to download mode..
Try this to get out of red light only if there is absolutely no other way..: http://forum.xda-developers.com/showthread.php?t=2250454
If there is no boot loader whatsoever even after trying for a hell lot of time, only download mode, then do this..
http://forum.xda-developers.com/showthread.php?t=2347060
sent from my Prevert nexus
Click to expand...
Click to collapse
I will try to reconnect the battery now, maby that will help----
Fixed it !
ripped.animal said:
Having the same problem. I was on purity rom(4.4.3), with default purity kernel. I flashed the Ak poseidon kernel, with Ukm. It booted fine , was on phone for about 4 minutes, and then I ran antutu benchmark. Before that I didn’t change anything via synapse app. Then when I ran test on antutu phone went off. Non of the buttons were responding. I plugged the phone into wall charger and pressed all 3 buttons. Then the download mode appeared. Left it like that on the charger , went to sleep. When I woke up the phone was turned off. Today I was flashing factory img ( 4.4.3. occam). Following the instructions http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312 [/URL]. Everything went ok no problem in the cmd , only the thing was , when I had to fastboot the booth loader, then the phone stuck in power on loop . ( reboots, then it says google, and reboots again) I was able to stop this by holding volume down, then it goes into bootloader. Finished flashing factory img, like it says on the tut. And the same thing happens. The phone won’t boot, And it is not responding when it is unplugged. Please help :/
---------- Post added at 03:28 PM ---------- Previous post was at 03:26 PM ----------
I will try to reconnect the battery now, maby that will help----
Click to expand...
Click to collapse
After reconnecting the battery, I managed to boot the device. But i got gazzlion errors, non of the apps were responding. I got the msg to delete the partion or my device will not function properly. Since I have already flashed the factory img I booted to stock recovery. And deleted all user data , (factory reset). Then the device booted normally. I have lost my recovery img but what the hell I don’t care now Flashed the CMW touch, and super user. Now everything works fine
Fix - Volume Up + Power
I had the same problem this morning and found an easier fix on Google product forums.
Push Volume Up + Power button until it works. Worked for me
<not able to paste link as I'm still a n00b user and this is among my first ten posts here. Ok, this is my FIRST post here>
I got the same thing too...
Hi guys, so I recently have this problem where I try to turn on my phone and he starts to boot and at the part where the boot animation comes it shows only a blue screen for like 10-15 secs and then turns off. That happend after I was trying to disassemble the phone(long story), anyway I didn't completely disassemble it just took out the screws and then gave up and put the screws back. The blue screen happens only when I get the battery out and back, if I try to boot the phone after the blue screen it just gets to bootloop. Guys, please, I need very fast help because the phone isn't mine(Yes I know im stupid). Anyway thanks for reading this.
{
"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"
}
xgamer231 said:
Hi guys, so I recently have this problem where I try to turn on my phone and he starts to boot and at the part where the boot animation comes it shows only a blue screen for like 10-15 secs and then turns off. That happend after I was trying to disassemble the phone(long story), anyway I didn't completely disassemble it just took out the screws and then gave up and put the screws back. The blue screen happens only when I get the battery out and back, if I try to boot the phone after the blue screen it just gets to bootloop. Guys, please, I need very fast help because the phone isn't mine(Yes I know im stupid). Anyway thanks for reading this.
Click to expand...
Click to collapse
Google un brick Samsung j5
infixremix said:
Google un brick Samsung j5
Click to expand...
Click to collapse
I have already flashed a stock firmware and still the blue screen.
xgamer231 said:
I have already flashed a stock firmware and still the blue screen.
Click to expand...
Click to collapse
Damn... Try using another ROM. If you can get to the part where the boot logo should be but appears blue screen you migh have a chance...
Get into download mode and flash TWRP trough Odin and one of the custom ROMs around. If it boots into TWRP succesfully and after that it succesfully boots into the ROM you just installed trough TWRP, than it was a software issue. If it doesn't boot and you get the same exact blue screen... It might be either a hardware error or an issue with the bootloader. I'm really saying that because it is one of the more sensitive and important parts of the firmware and the fact that your blue screen color is exactly the same as the download mode (bootloader) might link it to an issue with a bootloader.
@Henkate, I'm summoning you. Maybe you an help this fella as I think you know loads more things about the firmware
BTW: next time don't mess with hardware. Messing with software is easier and safer : )
Also... What were you trying to do by taking the poor guy appart? Replacing the screen maybe? Stuck SIM card?
Amarius1 said:
Damn... Try using another ROM. If you can get to the part where the boot logo should be but appears blue screen you migh have a chance...
Get into download mode and flash TWRP trough Odin and one of the custom ROMs around. If it boots into TWRP succesfully and after that it succesfully boots into the ROM you just installed trough TWRP, than it was a software issue. If it doesn't boot and you get the same exact blue screen... It might be either a hardware error or an issue with the bootloader. I'm really saying that because it is one of the more sensitive and important parts of the firmware and the fact that your blue screen color is exactly the same as the download mode (bootloader) might link it to an issue with a bootloader.
@Henkate, I'm summoning you. Maybe you an help this fella as I think you know loads more things about the firmware
BTW: next time don't mess with hardware. Messing with software is easier and safer : )
Also... What were you trying to do by taking the poor guy appart? Replacing the screen maybe? Stuck SIM card?
Click to expand...
Click to collapse
Well I'll try a custom rom when I get come, but now I will tell you the whole story how it went trough. So when I got this phone it was stuck in a bootloop(it boots up, freezes for 5-10 secs and restarts and so on), and I tried hard reset and putting stock firmware and still nothing. I got to a conclusion, because the phone was drowned in water few days ago, maybe the power button had a short circuit so I went disassembling it to try to dry more the motherboard, when I took of the screws I realized I can't get to the mobo because I needed to get first the display off and I didn't had the tools for that. Anyway I put the screws back and boom blue screen.
The blue color isn't exactly the same like in download mode, the camera I took the picture with is very bad. The blue color is a standard blue blue(like in rgb).
I don't believe it couls be a hardware failure, because I didn't touch anything drastic, one thing I did touch was the display cable under the little panel, I just plug it off.
Btw. Just to mention its the J500FN model.
I really apprechiate the help guys :S
xgamer231 said:
Well I'll try a custom rom when I get come, but now I will tell you the whole story how it went trough. So when I got this phone it was stuck in a bootloop(it boots up, freezes for 5-10 secs and restarts and so on), and I tried hard reset and putting stock firmware and still nothing. I got to a conclusion, because the phone was drowned in water few days ago, maybe the power button had a short circuit so I went disassembling it to try to dry more the motherboard, when I took of the screws I realized I can't get to the mobo because I needed to get first the display off and I didn't had the tools for that. Anyway I put the screws back and boom blue screen.
The blue color isn't exactly the same like in download mode, the camera I took the picture with is very bad. The blue color is a standard blue blue(like in rgb).
I don't believe it couls be a hardware failure, because I didn't touch anything drastic, one thing I did touch was the display cable under the little panel, I just plug it off.
Btw. Just to mention its the J500FN model.
I really apprechiate the help guys :S
Click to expand...
Click to collapse
This looks like hardware failure. I would check the cable for the display you removed is properly connected.
If it is then it may be you've damaged the delicate connector.
ashyx said:
This looks like hardware failure. I would check the cable for the display you removed is properly connected.
If it is then it may be you've damaged the delicate connector.
Click to expand...
Click to collapse
The cable is in place, I don't really believe its the cable because bl and recovery are fine(no graphical disorders).
Just tried to flash TWRP, and I got a auth fail(google says i need to autorize something in dev settings idrk), strange thing I don't get the bootloop anymore when I try to turn on the phone after the blue screen shuts off.
Here's a video:
https://www.youtube.com/watch?v=tWkqTg77rbg
xgamer231 said:
The cable is in place, I don't really believe its the cable because bl and recovery are fine(no graphical disorders).
Just tried to flash TWRP, and I got a auth fail(google says i need to autorize something in dev settings idrk), strange thing I don't get the bootloop anymore when I try to turn on the phone after the blue screen shuts off.
Here's a video:
Click to expand...
Click to collapse
Bro, why don't you go to service somewhere in your city, im sure they wouldn't take much money for that fix since i believe it is minor hardware failure, they have appropriate tools and will get the job done quickly. Don't mess with your phone further more. I know this is not the answer you exoected but this is what i would do since i would rather give up on 20$ and be safe.
xgamer231 said:
The cable is in place, I don't really believe its the cable because bl and recovery are fine(no graphical disorders).
Just tried to flash TWRP, and I got a auth fail(google says i need to autorize something in dev settings idrk), strange thing I don't get the bootloop anymore when I try to turn on the phone after the blue screen shuts off.
Here's a video:
Click to expand...
Click to collapse
But can you enter Recovery? If yes, you can transfer a rom zip file from your computer to phone as adb is working in TWRP. If after flashing the ROM you still get the blue screen... Than it definetelly isn't a software issue, but a hardware one, persisting no matter what you do to the software.
Amarius1 said:
Damn... Try using another ROM. If you can get to the part where the boot logo should be but appears blue screen you migh have a chance...
Get into download mode and flash TWRP trough Odin and one of the custom ROMs around. If it boots into TWRP succesfully and after that it succesfully boots into the ROM you just installed trough TWRP, than it was a software issue. If it doesn't boot and you get the same exact blue screen... It might be either a hardware error or an issue with the bootloader. I'm really saying that because it is one of the more sensitive and important parts of the firmware and the fact that your blue screen color is exactly the same as the download mode (bootloader) might link it to an issue with a bootloader.
@Henkate, I'm summoning you. Maybe you an help this fella as I think you know loads more things about the firmware
BTW: next time don't mess with hardware. Messing with software is easier and safer : )
Also... What were you trying to do by taking the poor guy appart? Replacing the screen maybe? Stuck SIM card?
Click to expand...
Click to collapse
Amarius1 said:
But can you enter Recovery? If yes, you can transfer a rom zip file from your computer to phone as adb is working in TWRP. If after flashing the ROM you still get the blue screen... Than it definetelly isn't a software issue, but a hardware one, persisting no matter what you do to the software.
Click to expand...
Click to collapse
Yea, but I don't have TWRP installed because odin gives me some auth fail. I don't really know to give up or continue with this.
xgamer231 said:
Yea, but I don't have TWRP installed because odin gives me some auth fail. I don't really know to give up or continue with this.
Click to expand...
Click to collapse
It's possible you have damaged the emmc. The bootloader resides on a different part of memory to the rest of the firmware.
However, can you actually boot to stock recovery?
ashyx said:
It's possible you have damaged the emmc. The bootloader resides on a different part of memory to the rest of the firmware.
However, can you actually boot to stock recovery?
Click to expand...
Click to collapse
Yes, everything exept the bot sequence is fine.
Have you tried factory reset in recovery?
It looks for GPU failure, not a software.
Anyway, it happened after disassembly, before as I suppose everything was working so dissamblessing was the most probably cause of this.
As a mate mentioned, go to a service center, they should agree with my opinion. Unfortunately mainboard switch would fix it.
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
xgamer231 said:
Yea, but I don't have TWRP installed because odin gives me some auth fail. I don't really know to give up or continue with this.
Click to expand...
Click to collapse
Right what I suggest you do is re install stock from Odin then download NICK VERSES twrp install that and then install a ROM either RR or cm 13 if that doesn't work take it to a store
infixremix said:
Right what I suggest you do is re install stock from Odin then download NICK VERSES twrp install that and then install a ROM either RR or cm 13 if that doesn't work take it to a store
Click to expand...
Click to collapse
He cant flash anything custom as he can't enable OEM unlock.
ashyx said:
He cant flash anything custom as he can't enable OEM unlock.
Click to expand...
Click to collapse
Ffs take it to a shop then
---------- Post added at 01:50 AM ---------- Previous post was at 01:39 AM ----------
xgamer231 said:
I have already flashed a stock firmware and still the blue screen.
Click to expand...
Click to collapse
http://www.any-data-recovery.com/an...e-blue-screen-of-death-on-samsung-galaxy.html it seems to be a software issue
Okay looks like we're out of solutions, I'll take the phone back to his owner and explain the situation.
Thank you all guys, I really apprechiate the help
Same problem
Got the same problem with my friends device 3 days ago
What should i do i haven't try anything yet but thinking to re assembly it
Hello, i know this threat is very old, but recently i sufer the same problem (Yes i dissambled the phone). My problem was worst because eventually my phone wasn't booting at all. So heres what i do:
1. I took the battery out.
2. I plug in the charger until the phone gets a bit hot.
3. Then (with the charger still plugged) i put the battery back.
4. After that i get the charging screen, so i press the power on button and the phone booting on normally.
Note: While i was doing that process the phone was without the back part (i mean the part where the speaker is) and i reassembled the phone while it was on.
I Hope this help someone!!!!
Had been rooted my phone before, didn't like it because I couldn't use my banking apps. Back to official firmware via Kies, been using for few months... no problem until yesterday. I charged my phone up to 92%, I unplugged and unlocked my phone, it restarted itself then never come back live again.
I used Smart Switch for another stock firmware flashing with no luck. The software skipped downloading from 85% to 100% immediately, it was ok installing system update on Smart Switch but when the phone completed and restarted, on the screen it shown "erasing" and "installing system up to 32%", it won't get pass above 32% except a blue dead android with loading icon, it freezes every time.
Full Album here, so you might get some ideas of what's going on...
http://imgur.com/a/Ad6dV
{
"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 went to Samsung store yesterday, however once they see knox has been tripped, they refused to fix my phone unless I pay for a new motherboard which will cost me £220. :crying:
I have been trying to flash any official firmware using both Smart Switch, Samsung Kies and Odin, Android 6.0 or 7.0 and every tools lead to blue led black screen or boot looping. I have tried at least 10 times of each methods, even ADB mode, but ADB won't offer much choices except 'adb sideload' commands but it verify each package. So I cannot install TWRP recovery and so on... Odin won't install TWRP recovery as well, it failed every time.
It is sad to see this phone die on me. I have never dropped this phone and it has 0 scratch on it... still looks brand new! If anyone of you could help me out getting this baby alive, I could pay you little money.
Thanks for your time!
lovetv said:
Had been rooted my phone before, didn't like it because I couldn't use my banking apps. Back to official firmware via Kies, been using for few months... no problem until yesterday. I charged my phone up to 92%, I unplugged and unlocked my phone, it restarted itself then never come back live again.
I used Smart Switch for another stock firmware flashing with no luck. The software skipped downloading from 85% to 100% immediately, it was ok installing system update on Smart Switch but when the phone completed and restarted, on the screen it shown "erasing" and "installing system up to 32%", it won't get pass above 32% except a blue dead android with loading icon, it freezes every time.
Full Album here, so you might get some ideas of what's going on...
http://imgur.com/a/Ad6dV
I went to Samsung store yesterday, however once they see knox has been tripped, they refused to fix my phone unless I pay for a new motherboard which will cost me £220. :crying:
I have been trying to flash any official firmware using both Smart Switch, Samsung Kies and Odin, Android 6.0 or 7.0 and every tools lead to blue led black screen or boot looping. I have tried at least 10 times of each methods, even ADB mode, but ADB won't offer much choices except 'adb sideload' commands but it verify each package. So I cannot install TWRP recovery and so on... Odin won't install TWRP recovery as well, it failed every time.
It is sad to see this phone die on me. I have never dropped this phone and it has 0 scratch on it... still looks brand new! If anyone of you could help me out getting this baby alive, I could pay you little money.
Thanks for your time!
Click to expand...
Click to collapse
Take a look here https://forum.xda-developers.com/s7-edge/help/s7-edge-bug-t3331878/page12
post #114
mrsmtt said:
Take a look here https://forum.xda-developers.com/s7-edge/help/s7-edge-bug-t3331878/page12
post #114
Click to expand...
Click to collapse
I've tried this solution more than 10 times with no luck
Have you tried flashing the boot.img recovery.img ect separately? I had this kind of thing on a different Samsung and i fixed it by flashing each one separate.
Clarkiieh said:
Have you tried flashing the boot.img recovery.img ect separately? I had this kind of thing on a different Samsung and i fixed it by flashing each one separate.
Click to expand...
Click to collapse
That's good idea, which option should I use in Odin? Should be AP option right?
The files should work with their own options I'm not too sure which ones work with which, and there is a set order to flash in as well which I'm not sure about either.
---------- Post added at 03:47 PM ---------- Previous post was at 03:38 PM ----------
They all have their own button I think pal
What about fastboot flash?
I finally revived my phone!!! I'm so happy right now
I'll provide these solutions if anyone has the same issue like me. What I did altogether was:
1.0) Remove devices from your Google accounts (I had 2), wait for 48 hours to cool down? Although not sure if this option caused the bootloop, might be useful for someone...
1.1) Downloading the oldest firmware from https://www.sammobile.com flash it using Odin 3.11.1
1.2) Upload BL, AP, CP and CSC files, but I uploaded the correct Pit file too! WARNING: Be sure you know what you doing before trying to mess with this! Otherwise don't try pit file! Leave the options by default! Unless you ran out of choices!!! but I've ticked auto reboot, re-partition, f.reset time, nano erase all and bootloader update for my case. Then start to flash of course.
2.0) Phone were still crashing upon system update... I waited out the battery to drain up. Until next day... Tips: If there's no led light, try to sense it with your face if there's any temperature
2.1) Plugged in ur phone and see if there's the battery charging icon. If there is, you're in luck.
2.2) Charge until 100%, turn it on. Hopefully you can boot up now but I couldn't...
3.0) My phone was still in boot looping (Samsung Logo), I had to turn on recovery mode and wipe + format system then mount /system for whatever reason... then restart using the recovery mode...
3.1) At this time, I finally past through the boot loop which I'll be in the Google sign in screen!
4.0) Phone was in the oldest firmware, of course I will update the official firmware automatically, however the first update didn't make it, and stucked on Samsung logo again!
4.1) All I did was wait a little bit about (25mins) and reset again... somehow it fixed the issue and boot back in.
4.2) Then system update every single firmware up to the latest, boom! I'm on the latest firmware again and everything is up and running!
5.0) Extra tips: Make sure you have up to 60% battery life before turning on recovery mode, but I had to charge up to 100% for my case.
5.1) Remove FRP lock (google accounts, remove devices) might help?
5.2) On recovery mode, wipe cache and format system again might help too!
Good luck guys, I was about to give up trying after 20 flashes (Smart Switch, Kies, and Odin with different pc too!) and had to wait for battery to drain everytime if it stucks! Which annoys me but I made it!!
Glad you got it sorted ?
I would recommend Batman ROM if your willing to flash again.
Same happen to my Phone many times!
Solution!
After a few Reboots your Phone will stuck with screen of or may a blue led on (pulsing) or without any reaction (black screen, all led off) !
Now you have to wait until your battery will be empty compl. Can be up to 18 hours and more! depend how much your Mobile was loaded! or until Led light is off! is your phone still warm? Than it is still draining!You have to wait untill it is complet off and getting cool. Or, if u can, get it in the download mode, with sreen on it will be decharged faster! but mostly your phone will stay death.
After all that, Phone is cold and no Led is illuminated, plug your Phone to usb charging! Wait a little time until you can see the normal charging screen and orange Led is illuminated! (if charging screen will not upper, you have to wait longer!for decharging battery)
let it charge untill it is complet full! Dont touch! Wait at leasst 8 hours and more with charger still connected ! Best is overnight.
after this usely your phone will start normaly , without loosing any data!
Thats what helped me many times!
All my tries with bootloader, software brought nothing, just lots of waisted time and lost Data! you not need to del your phone at google!
Try this, it will work
Vollidiot said:
Same happen to my Phone many times!
Solution!
After a few Reboots your Phone will stuck with screen of or may a blue led on (pulsing) or without any reaction (black screen, all led off) !
Now you have to wait until your battery will be empty compl. Can be up to 18 hours and more! depend how much your Mobile was loaded! or until Led light is off! is your phone still warm? Than it is still draining!You have to wait untill it is complet off and getting cool. Or, if u can, get it in the download mode, with sreen on it will be decharged faster! but mostly your phone will stay death.
After all that, Phone is cold and no Led is illuminated, plug your Phone to usb charging! Wait a little time until you can see the normal charging screen and orange Led is illuminated! (if charging screen will not upper, you have to wait longer!for decharging battery)
let it charge untill it is complet full! Dont touch! Wait at leasst 8 hours and more with charger still connected ! Best is overnight.
after this usely your phone will start normaly , without loosing any data!
Thats what helped me many times!
All my tries with bootloader, software brought nothing, just lots of waisted time and lost Data! you not need to del your phone at google!
Try this, it will work
Click to expand...
Click to collapse
My phone turned out to be a faulty motherboard, went to Samsung support centre and they repaired for me within 3 working days. Now I got a sort of a new phone, it has 0 scratch since I bought it last year Feb, so it's like a new phone to me :laugh::good:
But yeah, motherboard was acting weird, was lasting a week then breaks again... finally motherboard was dead, so I could repair it without seeing the knox being triggered. Phew
Hi guys, wondering if you could help me here.
1) I recently upgraded my M3 to Nougat by mistake and tried to use the "C100B009" full rom to downgrade to MM using "Power + Vol up + Vol down".
2) I was stuck in eRecovery after the update and I realized i missed out the rollback package. So i downloaded and extracted the contents of rollback package to "dload" folder and ran the update again. But it seems afterwards, the tablet was stuck on ""Your device is booting now", and the Power + Vol up + Vol down doesn't work anymore.
3) I managed to get into fastboot and bootloader was locked. So i issued the unlock command based on keys i had saved earlier. The command said it worked and it would reboot and wipe the phone.
4) After the reboot, it seems i'm again stuck in "Your device is booting now". I can't shut down the tablet as it would just reboot, vibrate twice and show the same message again. Eventually, it flat of battery.
5) I also don't seem to be able to go into fastboot anymore. Holding Vol down and plugging into computer still gets me the "Your device is booting now" message. Also, the tablet can't hold a charge. It will blink red. Seem to charge a little after a while, then power itself into "Your device is booting now" message, drain flat, and repeat the cycle again.
Anyone could give any advice on this or would i have to bring down to a service centre for replacement..... :crying:
If you had read here other threads you will be able to solve at least a big part of your problem.
I just had similar situation this weekend while trying updates. I let it die, then tried to boot by plugging into good AC adapter (not PC USB). It showed booting for a while. Eventually it just came up. I had done that dead battery, then little bit of charge multiple times. Good luck.
nostep said:
I just had similar situation this weekend while trying updates. I let it die, then tried to boot by plugging into good AC adapter (not PC USB). It showed booting for a while. Eventually it just came up. I had done that dead battery, then little bit of charge multiple times. Good luck.
Click to expand...
Click to collapse
Hmm, when you said it just came up, did you mean the tablet booted up normally? Or you meant you could go into fastboot after your staggered charging? Because i tried charging with AC adapter before, but the tablet turns itself on after a while, and then just runs itself flat again with the "Your device is booting now" message. I can't seem to trigger fastboot mode off it.
I had previously loaded half of c128b350 and needed to load the second half via twrp. I loaded the wrong twrp (4.1) and it was stuck trying to boot it. I cannot get into fastboot without OS working. Anyway after 10 hours it finally booted the half finished b350 and I managed to get the rest from there.
@fallen_13 do you solve this problems? I've got exactly problem as you
---------- Post added at 11:21 PM ---------- Previous post was at 11:21 PM ----------
[/COLOR @fallen_13 do you solve this problems? I've got exactly problem as you
romeo_coi said:
@fallen_13 do you solve this problems? I've got exactly problem as you
---------- Post added at 11:21 PM ---------- Previous post was at 11:21 PM ----------
[/COLOR @fallen_13 do you solve this problems? I've got exactly problem as you
Click to expand...
Click to collapse
I tried my luck and sent it into service centre. Been a month and still waiting for replacement since they didn't have stock.
fallen_13 said:
I tried my luck and sent it into service centre. Been a month and still waiting for replacement since they didn't have stock.
Click to expand...
Click to collapse
Just messed up with this sh!t 3 days ago
I've tried several ways I can search on xda, 4pda and google.... but still no luck.
The dead battery trick then "Volume (-) + USB plug in to pc" seem to be useless.
According to the confirmation of member MuHuCTP23 in 4pda thread below, there is only one user was able to boot tablet to bootloader after did a "fastboot oem unlock" when in rollback process, What a lucky guy! And him doesn't know how he managed to got device into bootloader.
http://4pda.ru/forum/index.php?showtopic=780572&st=2020#entry64535878
Now I'm reading from this post:
https://forum.xda-developers.com/huawei-p9lite/help/huawei-p9-lite-vns-l31-fastboot-adb-t3590158
And other threads about the "totally bricked Huawei android phone" becasue of "flashing rollback wrong ways".
Some users confirmed the trick "3 button in cold boot": press and hold power button untill device powers off then release power button, quickly press and hold Vol (-) button and connect the usb cable (which is already attached to pc) right before or exactly when device vibrates will able to take device into bootloader mode. But it's really matter about timing when connect the usb cable to device.
So I tried this way and it actually did something difference:
When connect usb cable at "wrong time", device starts with 3 options screen instead of the no option screen. It's a little bit confuse here, there're two bootloop screens:
1- The device shows: Your device is unlock... and under this device is trying to boot direct to recovery.
2- The device shows: Your device is unlock... and there're 3 options choice as normal, but whatever we choice it'll be stucked as well as before :silly:
And when I can connect usb to device at the "right time", it doesn't startup in bootloop but the screen with red bolt alert then again it starts again in bootloop. I think it was tried to boot itself to bootloader mode but due to the low battery it only shows the red bolt alert. This thing is very weird because AFAIK even if You totally drained the battery the bootloader will always show up.
....
After 3 days continous try and try, now I'm thinking about give it up and send it to the store, my tablet is being covered under 30 days return policy. The main problem here is I bought this tab from Japan but I'm living in Vietnam, so Idk if foreign customers will be treated the same way as domestic customers or not. I email to the support and waiting for the reply .
@romeo_coi
I believe you and i went through the same steps. I spent about 3 months researching the subject before giving in and sending to service centre. My guess is that after the unsuccessful rollback, when we unlock the bootloader, the process will erase data from the tablet. But maybe some partition information had changed, so after the erase completes, the tablet becomes hard bricked instead.
Anyway, i wish you luck on the return to Japan. One thing you can try before sending back is to drain the battery fully by taping down the power button. Once that happens, you will no longer see the red bolt alert. Then you can just report as an unable to power on issue.
fallen_13 said:
@romeo_coi
I believe you and i went through the same steps. I spent about 3 months researching the subject before giving in and sending to service centre. My guess is that after the unsuccessful rollback, when we unlock the bootloader, the process will erase data from the tablet. But maybe some partition information had changed, so after the erase completes, the tablet becomes hard bricked instead.
Anyway, i wish you luck on the return to Japan. One thing you can try before sending back is to drain the battery fully by taping down the power button. Once that happens, you will no longer see the red bolt alert. Then you can just report as an unable to power on issue.
Click to expand...
Click to collapse
-I don't think after re-unlock bootloader in rollback processing, it cannot erase data because mine was stucked right after device restart without successfully boot into erase data step. May be it caused due to wrong patritions flashing then some functions not working correctly as it should. And may be with some special tools, Huawei engineers can re-write the partritions and save the device.
-And about drained the battery before contacting the supplier, I think it will no help because they can easily plug a charger into device and found that we're messed arround with system modification. So I explained to them exactly how the deivce is but in another way: after received and used device in some days for testing, then I perform a factory reset to clean it up for my own settings but the device stuck at boot screen.... Hope they accepted and return another tab for me. If not, then I have luxury paperweight
-In this case, it may be weird and hard to believe but trust me, I'm working for a large chain store system in Vietnam (smartphone cate. of course) and people in my country sometimes did something they don't even f**king know what is it. I've seen some devices with the unlocking bootloder processing hasn't done completely by previous user, and the next users are f*cked already because they will never be noticed untill they do something such as update system, unlock bootloader again.. or even just perform a factory reset. Once these processing done (luckily) completely, devices will come back to the original state and safe for use. But in some cases, these processing taking errors then devices will be bricked. I think it's the most reasonable explanation why there're more and more OEMs accepted to covered "devices with software modifications" in warranty policy.
Below is the warranty policy of the Motorola X Pure 2015 for example:
{
"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"
}
Hi there,
I was in Japan and bought BTV-W09 on 11/29 and just returned back to Canada. (Mediapad M3 is not officially available in Canada.)
And right away I upgraded to Nougat but don't like it, so down graded back to 6.0 through 2 UPDATE.APPs via dload folder method.
I found that after the down grade,the fingerprint sensor/home button not working at all.
So I tried to repeat the process of installing UPDATE.APP again. And ended up exactly the same situation as you guys.
Booting stuck at "Huawei MediaPad" + "Powered by Android" screen. Even with proper charger hooked up, the battery drains and never charge enough to do anything.
I can not force shut down, can't go into recovery or nothing. But I managed to get into some sort of recover screen. ( Press Power till the screen gets blank, then plug USB while pressing Vol-. But the recovery requires HiSuite. Since my PC is Linux and I run Win7 via VirtualBox, without sufficient battery power I can't even utilize this method.
If you guys still trying to unbrick/restore, at least you can try go into that mode by pressing Vol- immediately after pressing Power and plug in USB.
I will leave it a while to see weather the battery charges, then use some native Windows PC and HiSuite and see what happens.
If everything fails, then I have to send back to Huawei Japan for repair or use it as a paper weight!
Please let me know the current status of yours.
x52-curcuma said:
Hi there,
I was in Japan and bought BTV-W09 on 11/29 and just returned back to Canada. (Mediapad M3 is not officially available in Canada.)
And right away I upgraded to Nougat but don't like it, so down graded back to 6.0 through 2 UPDATE.APPs via dload folder method.
I found that after the down grade,the fingerprint sensor/home button not working at all.
So I tried to repeat the process of installing UPDATE.APP again. And ended up exactly the same situation as you guys.
Booting stuck at "Huawei MediaPad" + "Powered by Android" screen. Even with proper charger hooked up, the battery drains and never charge enough to do anything.
I can not force shut down, can't go into recovery or nothing. But I managed to get into some sort of recover screen. ( Press Power till the screen gets blank, then plug USB while pressing Vol-. But the recovery requires HiSuite. Since my PC is Linux and I run Win7 via VirtualBox, without sufficient battery power I can't even utilize this method.
If you guys still trying to unbrick/restore, at least you can try go into that mode by pressing Vol- immediately after pressing Power and plug in USB.
I will leave it a while to see weather the battery charges, then use some native Windows PC and HiSuite and see what happens.
If everything fails, then I have to send back to Huawei Japan for repair or use it as a paper weight!
Please let me know the current status of yours.
Click to expand...
Click to collapse
Can try power + vol up for ~3 seconds, it shuts down, then let go (timing, if you keep holding it'll go back to the loop) and it should boot to this recovery screen with 2 options, restore factory and shutdown (not fastboot or twrp). Least that's what mine does W09.
piloki said:
Can try power + vol up for ~3 seconds, it shuts down, then let go (timing, if you keep holding it'll go back to the loop) and it should boot to this recovery screen with 2 options, restore factory and shutdown (not fastboot or twrp). Least that's what mine does W09.
Click to expand...
Click to collapse
Didn't work for me. It does not charge enough. Auto shut down after about 5 min. stuck at boot then shut down for 3~4 min. of charging, and repeating forever. Just before finishing this charging, press Vol up + USB plug-in takes me into Fastboot & Rescue mode. Seems like it is missing eRecovery. Anyways, it doesn't connect to HiSuite running on native Win7 as it does not give me the required non-debugging mode connection.
Later I will try flash eRecovery image via fastboot. Most likely it will not work though without USB-Debugging on.
Okay, fastboot does not work. I can send BOOT.img, RECOVERY.img etc to W09, but can not write them into it due to lack of debugging. When getting into fastboot & rescue mode it also shows the link for rescue detail, bu the site is non-existing.
Most of the instructions EMUI/Huawei provide are useless anyway.
My remaining options are getting very little now.
I guess there is no solution to this. HiSuite's System Recovery allows you to connect W09 without debugging, but the function supports only Mediapad T2. M3 is more than a year old model but Huawei can not support it is unbelievable!
So, I gave up.
x52-curcuma said:
I guess there is no solution to this. HiSuite's System Recovery allows you to connect W09 without debugging, but the function supports only Mediapad T2. M3 is more than a year old model but Huawei can not support it is unbelievable!
So, I gave up.
Click to expand...
Click to collapse
Ah sorry to hear. You try the sd card method?
piloki said:
Ah sorry to hear. You try the sd card method?
Click to expand...
Click to collapse
Yes, I have tried that as well. Nothing works. The worst part is, aside from poor Huawei support, the battery will not charge more than a few minutes worth.
Hello guys, i am the newest member of your commuity.
Recently i bought a leeco le pro 3 elite (x722). Now it has a problem. I was taking a snapshot of the screen in the morning and in notification are it kept showing saving screenshot (phone continued to work just ok, i an 4g video call through messenger, surfing the web, playing some games all day). Even after trying to close forcibly the notification about the save it wouldn't dissapear. In the evening i tried to do a restart and the phone shutted down and now can't turn it on. Only i can get is this when i plug it in computer:
{
"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"
}
If i put it to charge , the phone is getting charged i think, because it's starting to gain a little bit temperature (normal, like everytime when was charging) , but no blinking light or anything else. i tried a lot of combination to start up: Vol up+ power, vol down+ power, all three pressed, power button for 3 minutes, power + vol down for 2 minutes etc...
I don't get nothing not a vibration or even a blink - 0 reaction.
Can you give me an advice how to bring it back to life?
tudorm91 said:
Hello guys, i am the newest member of your commuity.
Recently i bought a leeco le pro 3 elite (x722). Now it has a problem. I was taking a snapshot of the screen in the morning and in notification are it kept showing saving screenshot (phone continued to work just ok, i an 4g video call through messenger, surfing the web, playing some games all day). Even after trying to close forcibly the notification about the save it wouldn't dissapear. In the evening i tried to do a restart and the phone shutted down and now can't turn it on. Only i can get is this when i plug it in computer:
If i put it to charge , the phone is getting charged i think, because it's starting to gain a little bit temperature (normal, like everytime when was charging) , but no blinking light or anything else. i tried a lot of combination to start up: Vol up+ power, vol down+ power, all three pressed, power button for 3 minutes, power + vol down for 2 minutes etc...
I don't get nothing not a vibration or even a blink - 0 reaction.
Can you give me an advice how to bring it back to life?
Click to expand...
Click to collapse
Need more information.
Sorry to hear about this issue.
Does it have stock software or did you attempt to install a custom Rom?
Can you boot into Recovery? (Stock or TWRP)
Can you boot to fastboot mode?
If it has stock and you just bought it, you need to immediately return it for a exchange, it sounds like its bricked. Hopefully you can get to recovery or fastboot. There is no fix for a bricked X722. If the bootloader is unlocked and you can get to fastboot there is hope.
Answering the questions above will help determine whether or not there is any solution for your X722
tsongming said:
Need more information.
Sorry to hear about this issue.
Does it have stock software or did you attempt to install a custom Rom?
Can you boot into Recovery? (Stock or TWRP)
Can you boot to fastboot mode?
If it has stock and you just bought it, you need to immediately return it for a exchange, it sounds like its bricked. Hopefully you can get to recovery or fastboot. There is no fix for a bricked X722. If the bootloader is unlocked and you can get to fastboot there is hope.
Answering the questions above will help determine whether or not there is any solution for your X722
Click to expand...
Click to collapse
no i never tried to unlock or to see status of bootloader.
i can't get anything on the screen and on computer i only get de Qualcomm qLoader driver (status). no matter what buttons i try combine when trying to power on the device i get nothing not a light or a vibration. Even the led on the upper side isn't lightning up, even if if put it to charge.
tudorm91 said:
no i never tried to unlock or to see status of bootloader.
i can't get anything on the screen and on computer i only get de Qualcomm qLoader driver (status). no matter what buttons i try combine when trying to power on the device i get nothing not a light or a vibration. Even the led on the upper side isn't lightning up, even if if put it to charge.
Click to expand...
Click to collapse
Does it have stock software?
Did you attempt installing a custom ROM, or manually update stock EUI?
If it still has the stock software and you never flashed custom software nor tried to install 5.8.26s, incorrectly then Your battery is probably dead. Possibly caused by a faulty USB C cable. You can order a battery for about $20.
Have you tried charging with another cable?
On the other hand if you attempted flashing software without unlocking the bootloader, the phone is hard bricked and there is no resolution at this moment.
Sent from my LEX727 using XDA Labs
tsongming said:
Does it have stock software?
Did you attempt installing a custom ROM, or manually update stock EUI?
If it still has the stock software and you never flashed custom software nor tried to install 5.8.26s, incorrectly then Your battery is probably dead. Possibly caused by a faulty USB C cable. You can order a battery for about $20.
Have you tried charging with another cable?
On the other hand if you attempted flashing software without unlocking the bootloader, the phone is hard bricked and there is no resolution at this moment.
Sent from my LEX727 using XDA Labs
Click to expand...
Click to collapse
No i didn't try to update or to install custom roms or enter some special mods. i just used the phone to make 4g call and some small games. I didn't even tried to put some hacked games or soft.
My phone was on a repairing center so they tried another cable, but i still get only this status Qloader 8006.
tudorm91 said:
No i didn't try to update or to install custom roms or enter some special mods. i just used the phone to make 4g call and some small games. I didn't even tried to put some hacked games or soft.
My phone was on a repairing center so they tried another cable, but i still get only this status Qloader 8006.
Click to expand...
Click to collapse
Since the battery is obviously working, somehow you phone is bricked. Maybe a shop rom was installed by the vendor?
You need to file a claim for a warranty exchange from whoever you bought the phone from., we do not have the needed Qfil software for the Leeco X722, and there is no way to repair without it. However in a worst case scenario, you can replace the motherboard.