Hey guys,
Today I decided to flash TrickDroid 10.0.0. Everything went well, installed it and at the end of flashing appeared a blue screen saying "Please wait". Waited for about 8-10 minutes, than just clicked once a power button. It asked me do I really wanna quit Aroma installation, pressed No. Then something "magical" happened and it was saying that installation is finished, click to reboot. So I did. After this step my phone won't turn on in any ways, tried to connect to pc - still no signs, it even won't charging..
How can I bring it to life!? Or this is it?
Nelayme said:
Hey guys,
Today I decided to flash TrickDroid 10.0.0. Everything went well, installed it and at the end of flashing appeared a blue screen saying "Please wait". Waited for about 8-10 minutes, than just clicked once a power button. It asked me do I really wanna quit Aroma installation, pressed No. Then something "magical" happened and it was saying that installation is finished, click to reboot. So I did. After this step my phone won't turn on in any ways, tried to connect to pc - still no signs, it even won't charging..
How can I bring it to life!? Or this is it?
Click to expand...
Click to collapse
Hold Power and Volume down until it goes into the bootloader, from there go into recovery and try re-flashing.
AllAboutTheCore said:
Hold Power and Volume down until it goes into the bootloader, from there go into recovery and try re-flashing.
Click to expand...
Click to collapse
Tried this many times but still nothing happens. I think it's totally bricked
Put it under a light, a very strong light and longpress the power button, try this
Are you S-On or S-Off? If you're S-On it isn't possible for you to totally brick the phone as far as I'm aware ... Especially not from flashing a ROM.
AllAboutTheCore said:
Are you S-On or S-Off? If you're S-On it isn't possible for you to totally brick the phone as far as I'm aware ... Especially not from flashing a ROM.
Click to expand...
Click to collapse
I'm S-On. I was searching for a solution later today and I found JTAG Riff box (actually, the service which brings the phones back to life by using this tool). However they can't help me at all, cause my phone isn't listed in that repairable list (not sure why). And the other thing they said was that I need to change the mainboard, because there're no other ways how to fix this problem. And it's a job for htc, not for them.
Nelayme said:
I'm S-On. I was searching for a solution later today and I found JTAG Riff box (actually, the service which brings the phones back to life by using this tool). However they can't help me at all, cause my phone isn't listed in that repairable list (not sure why). And the other thing they said was that I need to change the mainboard, because there're no other ways how to fix this problem. And it's a job for htc, not for them.
Click to expand...
Click to collapse
if your phone is booting to recovery you can still fix it without replacing mainboard just download cyanogenmod once and try flashing it after wiping everything and see if phone boots up. if it does you can use another custom sense 5rom and if it doesnt htc is the way to go
You're not bricked at all, calm down. Aroma crashes all the time and you just didn't finish the rom installation. Go back into recovery, wipe everything and flash it again. To turn the phone off, plug it into your PC and type 'adb reboot' and then hold down power and volume down as it is rebooting.
Hi
Got an HTC for my son 2 weeks back. He used it for a day, but then got an update. After downloading the update, I restarted at the prompt and got a message that the download was corrupted. Switched off the phone and after sometime, restarted, but without the update. I then downloaded it again and got it running for him.
A week later and the phone just crashed and switched off! Charged it and switched it on, but it just crashes and boot loops. Since my son is now not with me, I instructed him to do a reset using hardware buttons (since it does not boot and thereby allow him to do a factory reset from within the phone. I told him to:
Turn off your phone.
With the phone turned off, press and hold the VOLUME DOWN button, and then briefly press the POWER button.
Wait for the screen with the three Android images to appear, and then release the VOLUME DOWN button.
Press VOLUME DOWN to select CLEAR STORAGE, and then press POWER.
Press VOLUME UP to start the factory reset.
Click to expand...
Click to collapse
According to him, this too does not seem to help and it is still crashing (boot loops).
Can someone please suggest something. Problem is that to claim warranty I need him to bring the phone back (as it is a regional warranty) and the earliest he can get it to me is in about 3 months!
Thanks for any help/ suggestions
Does the phone have an unlocked bootloader and custom ROM?
If so then he needs to re flash the rom using Mike's thread:
http://forum.xda-developers.com/showthread.php?t=2265618
http://forum.xda-developers.com/showthread.php?t=2265618
or a more user friendly method is hasoon2000's here:
http://forum.xda-developers.com/showthread.php?t=2183942
Can you please let me know how to check if the bootloader is locked?
It's brand new ... not rooted, nothing .... clean phone 2 weeks of which 1 week has not been used as it was not booting.
Paparasee said:
Can you please let me know how to check if the bootloader is locked?
It's brand new ... not rooted, nothing .... clean phone 2 weeks of which 1 week has not been used as it was not booting.
Click to expand...
Click to collapse
If it's new and clean, then the bootloader will be locked. You have to manually unlock it.
Try going to fastboot and then running "fastboot erase cache".
Though most likely, you may have to take it to a repair center for them to bring it back to stock, without you having to go through the hassle; Especially since it's only 2 weeks old.
Hello All,
Hoping someone will be able to assist me, though I'm starting to lose hope.
I have spent all day so far reading threads, and trying various suggestions and fixes, but nothing has really helped and I'm beginning to think the phone may just be kaput.
Initial issue was nothing out of the ordinary; woke up to find the phone was not responding so pulled the battery. After putting the battery back in, the phone would no longer turn on. Uh oh. Did the obvious, repull the battery, try again. Nothing. Connect to charger (nothing happens, no charging icon on screen). At this point I think the battery has died so I bought a new one. No change, phone still won't turn on and nothing happens when I plug it in to charge.
So now I connect it to my PC, and I get the installing hardware message trying to install the APX stuff which fails. After some research, I manage to get the APX drivers installed such that the phone is detected when I plug it in. More research, decide to try the AOI Toolkit to backup everything first. This works ok.
So now I try and enter recovery mode via Power key + Volume Down key. Nothing. Ok, change the recovery image then. Device is not detected via ADB method. NVFlash method instead then. The bootloader loads fine, the screen wakes up and shows the S/W Download... message. I figure this is a hopeful sign. I try all 3 (ics-cwm-5, ics-cwm-6, twrp-2.5). They all flash successfully. However, I can't enter recovery mode with any of them. Once I disconnect the phone, insert the battery and then hold down the Power + Volume Down buttons, nothing ever happens.
I've also tried the LG Update Tool and the Smartflash options, but the phone is never detected.
As a last resort I repartitioned. This also worked ok, but still no recovery mode.
tl;dr
Phone won't turn on, show as charging, or enter recovery mode. Works when connected as APX with AOI Toolkit.
Am I missing something? Doing something wrong? Any assistance is greatly appreciated. Thx.
Bump
Okay, I'm bumping this thread myself (mostly because I'm an idiot and this could happen to me, too), but to give you my two cents: Have you tried the Full Brick Repair tool? You flash it through NVFlash and apparently "it cures any brick". Try it and tell us how it went.
NoDze said:
Okay, I'm bumping this thread myself (mostly because I'm an idiot and this could happen to me, too), but to give you my two cents: Have you tried the Full Brick Repair tool? You flash it through NVFlash and apparently "it cures any brick". Try it and tell us how it went.
Click to expand...
Click to collapse
Thanks for the suggestion. The flash process itself completed without issue, but still nothing once the battery is inserted and the power button is pressed. I'm going to assume there is some sort of hardware issue at this point and consider the phone officially dead. Now, where's my hammer...?
xda_fanboy said:
Thanks for the suggestion. The flash process itself completed without issue, but still nothing once the battery is inserted and the power button is pressed. I'm going to assume there is some sort of hardware issue at this point and consider the phone officially dead. Now, where's my hammer...?
Click to expand...
Click to collapse
Don't give up yet. Try smartflash and flash stock, or whatever. Seriously. Just keep on trying. I had a Samsung Captivate a year back and something similar happened where I woke up one beautiful morning, tried to unlock my phone: no response. I thought I had an SOD, so I pulled the battery out, reinserted: bootloop. Entered recovery, can't flash anything, unable to mount system/data partitions. Turns out my internal memory/ROM got fried. Yay. But until then, I tried every possible option. Wow, this turned out to be a bit depressing. Just try more stuff. After you've tried everything, and I mean everything, declare the phone dead.
I think i have a similar problem. Just woke up to find my phone to be dead. Tried the usual methods, nothing. Best it could do was from time to time show me a battery sign with a red triangle and a whtie exclamation mark in it. Then sometimes i manage to get into the recovery mode, there i tried practically everything. Used restore, it shows that restore was a success, but when i reboot my phone i get into an endless circle of bootloader icon appearing and dissappearing,
EDIT: somehow from the countless attempt it fired up.
Make sure to have the right bootloader before nvflashing unbrick roms....
xda_fanboy said:
Hello All,
Hoping someone will be able to assist me, though I'm starting to lose hope.
I have spent all day so far reading threads, and trying various suggestions and fixes, but nothing has really helped and I'm beginning to think the phone may just be kaput.
Initial issue was nothing out of the ordinary; woke up to find the phone was not responding so pulled the battery. After putting the battery back in, the phone would no longer turn on. Uh oh. Did the obvious, repull the battery, try again. Nothing. Connect to charger (nothing happens, no charging icon on screen). At this point I think the battery has died so I bought a new one. No change, phone still won't turn on and nothing happens when I plug it in to charge.
So now I connect it to my PC, and I get the installing hardware message trying to install the APX stuff which fails. After some research, I manage to get the APX drivers installed such that the phone is detected when I plug it in. More research, decide to try the AOI Toolkit to backup everything first. This works ok.
So now I try and enter recovery mode via Power key + Volume Down key. Nothing. Ok, change the recovery image then. Device is not detected via ADB method. NVFlash method instead then. The bootloader loads fine, the screen wakes up and shows the S/W Download... message. I figure this is a hopeful sign. I try all 3 (ics-cwm-5, ics-cwm-6, twrp-2.5). They all flash successfully. However, I can't enter recovery mode with any of them. Once I disconnect the phone, insert the battery and then hold down the Power + Volume Down buttons, nothing ever happens.
I've also tried the LG Update Tool and the Smartflash options, but the phone is never detected.
As a last resort I repartitioned. This also worked ok, but still no recovery mode.
tl;dr
Phone won't turn on, show as charging, or enter recovery mode. Works when connected as APX with AOI Toolkit.
Am I missing something? Doing something wrong? Any assistance is greatly appreciated. Thx.
Click to expand...
Click to collapse
Try to flash a new recovery image in apx mode.
And edit the /dev/block/mmcblk0p3 partition your self.
seek=6144 count=75 bs=1 / boot-recovery
Thanks for the added input and encouragement folks.
Just reporting an update:
Having been unsuccessful more times than I could count, I decided to physically disassemble the phone (normally Engineering fix #2, but performed out of order on this occasion). I have zero idea why it should have made a difference, as all I did was take it apart and then put it back together, but the phone has groaned back to life.
Of course, then sausage-fingers here managed to tear the digitizer cable when doing the final reassambly... /facepalm
Anyhow, I have a replacement on order, so I'm hopeful that when I receive that in a few days I'm back to a fully functional Optimus 2x!!
Hi.
I've been searching for a solution on how to fix my phone for already almost a year now. I didn't even do anything to it, no custom recoveries or OS (wanted to get CM, but at the time it wasn't available on it, not sure if now is).
The problem - the phone is stuck in a bootloop with an empty battery. The battery wasn't empty at the beginning, but it died in the process of trying to make it work, since the only thing I can boot is "fastboot&rescue" mode, in which the phone doesn't charge - how sweet. Now, I've read just about every thread here on how to flash custom (and original) recoveries, all the DLOAD folder versions and everything, and somewhere in between all that I found that it's impossible to flash anything if the battery is low (or totally empty).
The question - how do I charge the battery if it doesn't boot in anything other than fastboot, and when I plug it in the wall it just loops and loops and loops, and doesn't even charge? It's also impossible to turn it off while it's plugged in the charger. WTF, Huawei, really?
Any help appreciated. Cheers,
Can you Boot into recovery through pressing power + volume+?
You may have to remove the back of your phone and buy a new battery. The disassambling process is pretty simple, but of course you will loose any guarantee..
l3Nni said:
Can you Boot into recovery through pressing power + volume+?
You may have to remove the back of your phone and buy a new battery. The disassambling process is pretty simple, but of course you will loose any guarantee..
Click to expand...
Click to collapse
No, can't boot into recovery, only fastboot. If I could, I guess I would've already fixed it, heh.
I actually got it to charge, at least that's what I think. There was a *.bat script somewhere here that was repeatedly doing these two things:
1) fastboot getvar battery-voltage
2) fastboot reboot-bootloader
So, I ran that (while the phone was plugged in my computer and running fastboot mode), and it began looping and looping and looping. Left it like that for the night. Now, in the morning, when I unplugged it and tried to do someting, the red "battery low" LED wasn't glowing/blinking anymore! Since "fastboot getvar battery-voltage" returned an error all the time (remote: command not allowed), I don't exactly know how much power I have in it, but I'll just leave it like that for a day or two now, and then try some of the methods I've already tried before. Got any new ones I could try?
I already removed the back and removed the battery - wanted to see if I can charge it externally, but has a very small connector to connect it to the mother board, and I can't just put it in any external charger - I actually didn't find any external chargers that can charge the battery of this phone, really strange.
About the warranty - don't even care anymore. Somehow I managed to get a small crack on the glass on the back of the phone just a few days after getting it. Screen is not damaged, just the back cover. And, you don't know Latvia, but this is how it goes here. I took it to a repair shop - the one I needed to take my device for warranty repair. However, in Latvia that means it's just an another small repair shop, which just happens to have a contract with the company who sold me the phone (mobile phone operator). So, they take my phone, say they'll do a diagnostic and get back to me. Three weeks pass, and they call me telling that the only thing they can do is replace the motherboard, which is gonna cost me about 250 euros. That, or nothing. I don't agree. That means, if I don't agree to their suggested method of repairing, I have to pay for the diagnostic (about 20 euros).
Well, good idea, looks like you will get your phone running..
To unbrick your device you need to flash a recovery that matches with the firmware you had been on. So, if you had a B1xx Rom running try flashing TWRP 2.8.1.0 and MyRom 1.2. After that flash the stock emui 2.3 recovery and B133 through dload. If you were on a B6xx Ron flash TWRP 2.8.7.0 and MyRom 3.3, then emui 3.0 Recovery and B621.
When you didn't try this way until now, do it. It should work if the device isn't hardbricked.. I wish you the best.
l3Nni said:
Well, good idea, looks like you will get your phone running..
To unbrick your device you need to flash a recovery that matches with the firmware you had been on. So, if you had a B1xx Rom running try flashing TWRP 2.8.1.0 and MyRom 1.2. After that flash the stock emui 2.3 recovery and B133 through dload. If you were on a B6xx Ron flash TWRP 2.8.7.0 and MyRom 3.3, then emui 3.0 Recovery and B621.
When you didn't try this way until now, do it. It should work if the device isn't hardbricked.. I wish you the best.
Click to expand...
Click to collapse
Just flashed TWRP 2.8.1.0, it's already getting better. Now when I tried turning it on in recovery mode, it's not just simply bootlooping all the time, but is stuck on the Huawei logo. At least I hope that's better If I try to turn it on normally it just bootloops again. Omg omg omg.
l3Nni said:
Well, good idea, looks like you will get your phone running..
To unbrick your device you need to flash a recovery that matches with the firmware you had been on. So, if you had a B1xx Rom running try flashing TWRP 2.8.1.0 and MyRom 1.2. After that flash the stock emui 2.3 recovery and B133 through dload. If you were on a B6xx Ron flash TWRP 2.8.7.0 and MyRom 3.3, then emui 3.0 Recovery and B621.
When you didn't try this way until now, do it. It should work if the device isn't hardbricked.. I wish you the best.
Click to expand...
Click to collapse
Well, tried everything again. Flashing all those recoveries, nothing, can't get a recovery. Put a dload folder with update.app in it, magic 3 button combo just gives me some more of that good old bootloop. Extracted everything from the update.app, flashed recovery, system and boot with fastboot - all showed success. I got the most excited when it got to flashing system - it was quite big and took quite long, and returned success, so I really hoped that really did something - but no. Downloaded P7 kernel. Tried "fastboot flash:raw boot P7_kernel" ("P7_kernel" is the name of the file). It created a boot image (544985088 bytes), sending 'boot' returned "OKAY [20.622s]", then "writing boot" returned "FAILED (remote: flash write failure)". Is this the thing that's really broken? The boot flash partition? If so - what can I do, if anything?
God I hate this phone. The best is that I only used it for 3 months, and I still have to pay for it for more than a year. It's been in this condition for 7-8 months already. FML.
edzjins said:
Well, tried everything again. Flashing all those recoveries, nothing, can't get a recovery. Put a dload folder with update.app in it, magic 3 button combo just gives me some more of that good old bootloop. Extracted everything from the update.app, flashed recovery, system and boot with fastboot - all showed success. I got the most excited when it got to flashing system - it was quite big and took quite long, and returned success, so I really hoped that really did something - but no. Downloaded P7 kernel. Tried "fastboot flash:raw boot P7_kernel" ("P7_kernel" is the name of the file). It created a boot image (544985088 bytes), sending 'boot' returned "OKAY [20.622s]", then "writing boot" returned "FAILED (remote: flash write failure)". Is this the thing that's really broken? The boot flash partition? If so - what can I do, if anything?
God I hate this phone. The best is that I only used it for 3 months, and I still have to pay for it for more than a year. It's been in this condition for 7-8 months already. FML.
Click to expand...
Click to collapse
Hi, is your bootloader unlocked??? I think you cant write the boot partition if tour p7 is not unlocked, hace you tried flashing stock recovery? Try the b135
SiulGKT said:
Hi, is your bootloader unlocked??? I think you cant write the boot partition if tour p7 is not unlocked, hace you tried flashing stock recovery? Try the b135
Click to expand...
Click to collapse
Hi. Yes, bootloader unlocked, 100% sure. Have tried flashing the stock recovery, no changes. Tried to find the b135 now - I actually failed to find a real, valid download link! All I found were some russian ****up sites, which downloaded some russian ****ing malware! WTF? I'm about to give up on this phone. Just destroy it with all my hate for it. **** this ****ing piece of **** to hell. There is no hope, and **** my life. Whatever.
Be patient. I'll give you link soon but give me answers for this questions.
What was yours last valid ROM ?
Dude you can't flash any recovery you want.... It's not simply working between different ROMs.
Second question. Do you unplaged usb cable before flashing ROM by force update (3 buttons) ?
PS
I am not sure but battery isn't charging even fastboot mode or if totally device is off ?
Sent from my HUAWEI P7-L10 using Tapatalk
Ziolek67 said:
Be patient. I'll give you link soon but give me answers for this questions.
What was yours last valid ROM ?
Dude you can't flash any recovery you want.... It's not simply working between different ROMs.
Second question. Do you unplaged usb cable before flashing ROM by force update (3 buttons) ?
PS
I am not sure but battery isn't charging even fastboot mode or if totally device is off ?
Sent from my HUAWEI P7-L10 using Tapatalk
Click to expand...
Click to collapse
My last valid ROM is the only one I ever had - EMUI, whichever was the latest about a year ago.
After flashing recovery in fastboot mode, I unplugged the cable and pressed the power button and helt it until it turned off. Waited for a minute to see if it doesn't turn on, to make sure it's completely off - just what the instructions say. Then I tried the force update with 3 buttons, cable unplugged. With stock ROM it was still bootlooping, no changes at all, but with TWRP 2.8.1.0 it got stuck at Huawei logo - but no bootloop. Just Huawei logo, nothing else.
Battery is not charging in fastboot mode because that's how it is on all phones. But it's also not charging when it's totally off, because when I plug it in the charger, it automatically tries to turn on, and starts bootlooping. It's impossible to charge it then. However, with the .bat script I guess I have solved the charging problem - at least the red LED doesn't light/flash anymore.
Emui 3.0 beta release was at the end of 2014, official B609 in January 2015. It's important what rom you have been on. Trying different ones is just a waste of time..
You may try to extract and flash Bxxx part for part (depends on what rom you were) and then TWRP 2.8.1.0/2.8.7.0.I have no other idea, unfortunately.
It's a stupid question, but did you, when trying to boot into recovery, press volume+ for a longer time?
edzjins said:
My last valid ROM is the only one I ever had - EMUI, whichever was the latest about a year ago.
After flashing recovery in fastboot mode, I unplugged the cable and pressed the power button and helt it until it turned off. Waited for a minute to see if it doesn't turn on, to make sure it's completely off - just what the instructions say. Then I tried the force update with 3 buttons, cable unplugged. With stock ROM it was still bootlooping, no changes at all, but with TWRP 2.8.1.0 it got stuck at Huawei logo - but no bootloop. Just Huawei logo, nothing else.
Battery is not charging in fastboot mode because that's how it is on all phones. But it's also not charging when it's totally off, because when I plug it in the charger, it automatically tries to turn on, and starts bootlooping. It's impossible to charge it then. However, with the .bat script I guess I have solved the charging problem - at least the red LED doesn't light/flash anymore.
Click to expand...
Click to collapse
Than you probably have EMUI 2.3 ROM version.
Try flashing B135 recovery from here.
Next try to install B135 ROM from this link.
l3Nni said:
Emui 3.0 beta release was at the end of 2014, official B609 in January 2015. It's important what rom you have been on. Trying different ones is just a waste of time..
You may try to extract and flash Bxxx part for part (depends on what rom you were) and then TWRP 2.8.1.0/2.8.7.0.I have no other idea, unfortunately.
It's a stupid question, but did you, when trying to boot into recovery, press volume+ for a longer time?
Click to expand...
Click to collapse
No, it broke down before EMUI 3 came out, then. I guess I had the ROM which was just before EMUI 3.
Usually when trying to boot into recovery I press the volume+, hold it for about 10 seconds, and then press and hold the power button until it starts turning on. Then I hold both of them for some time, then release the power button but keep the volume button pressed. I've tried doing it differently - holding both buttons for longer time, releasing both as soon as it starts turning on, nothing I've tried works.
edzjins said:
No, it broke down before EMUI 3 came out, then. I guess I had the ROM which was just before EMUI 3.
Usually when trying to boot into recovery I press the volume+, hold it for about 10 seconds, and then press and hold the power button until it starts turning on. Then I hold both of them for some time, then release the power button but keep the volume button pressed. I've tried doing it differently - holding both buttons for longer time, releasing both as soon as it starts turning on, nothing I've tried works.
Click to expand...
Click to collapse
B135 recovery
http://forum.xda-developers.com/ascend-p7/general/trying-to-update-rom-1-2-t3222485
I uploaded it couple days ago...
OK, I left it "charging" for 2 days straight, hoping maybe battery was too low to flash partitions or whatever. Just wanted to make sure the battery is charged enough. I can't check the voltage or the percentage, because "fastboot getvar battery-voltage" always says that it's forbidden, no permissions, whatever.
So, I left it to charge for 2 days, and now I tested all the things you guys have posted here. Carefully, one by one. Every fastboot flash command returned success, but in the end nothing changed. Doesn't matter which recovery and/or boot I flash, it's just stupidly bootlooping all the time. Nada.
Finally, you can buy a defect P7 (with a broken screen or anything like this) for pretty low money on eBay and change the motherboard.
But I could also understand it well if you just throw it out of the window.. You had really bad luck.
Probably i have the same problem..... You solve yours problem with this ?
Nop, didn't solve the bootloop. I managed to get a donor phone for 55eur though, which had a bent body and wasn't functioning well because of that, and the screen was a bit cracked too. So I did a motherboard swap. Worked perfectly, but the battery connector protecting case screw doesn't hold in anymore, so sometimes it just turns off because it loses connection, or something. I tried to fasten it with some duct tape, hoped it'd help, and put a hard case on it - got better, but still fails sometimes.
I try give it back on warranty, i hope thei repair it.
I am in the EXACT same boat as edzjins. I have wasted 4 days of my precocious life trying to flash stuff on a phone with a completely dead battery.
I just doesn't work, period!
The only possible fix is to buy a new battery, replace the old one, and after the new battery is installed, have all of the flashing software ready to go and fired up before the new battery dies, too!
Its a time game.
Just like edzjins, there was a brief period of time when I thought I could stop the bootloop via TWRP recovery, but was unable to and the battery completely died.
Be wary of trying to flash "EdXposed" framework with TWRP. Instead, flash it only through Magisk.
I have learned the hard way : (
Hi,
So I had a Problem that my huawei (Working Phone) soft bricked himself over night. It was on his charger over night and worked fine on this evening... on the next morning I want to check my calender and the phone was already on the huawei logo... I think ok it does a reboot and locked himself. Than I forced off the device with power + volume up. Reboot instant after that and still stucked so ok I am soft bricked now. After searching a bit on Google it sad delete your cache via recovery. Problem I can't enter recovery or eRecovery only fastboot is available. Going into fastboot try the hisuit from huawei with the result phone not supported. But after that try on the white fastboot screen stand's "entering recovery mode..." so i let it do his thing... After many hours I came back and there it was the emui recovery. I decided to only clear the cache and boot. Again soft lock on logo... After that I tried again fastboot -> hisuit that doesn't work that the phone says entering recovery mode... -> but nothing happened...
I came back after the next work day...
The screen was black and I can't boot it anymore (still lie on my desk since first soft brick so yeah I am 100% proof the display will work) I plugged it in in my pc and it says now USB SER typical driver not found error code from windows...
IT will react when I force it with power + volume up only with dc from pc and reconnect in USB SER
Anyone any ideas to fix this hard brick?
Model: SNE-LX1
FRP and Phone locked
Stock Rom on it !
And If it possible I will let it as stock as possible (as I said it's only a work phone!)
Thanks for all the help !
@Blade8895
F
Huawei phones just aren't what they used to be... Some time ago their unlock policy vanished into thin air, then came alligations of spying, a trade ban in the US, and I've even heard rumors about them trying to make phones brick themselves after installing custom software. ?
Sadly, I can only recommend to stay clear of their devices until this whole situation improves...
I actually have the same issue, my phone downloaded the latest update and I scheduled it to auto update at midnight,next morning when I woke up,was surprised coz my regular alarm (from phone) didnt woke me up,so I grab my phone and saw it was dead,but it was full charge, then it didnt open anymore,and I tried to do all the reset or hard recovery technics on the net but it still is bricked. If I plug it on a computer it only says usb ser.. I guess its how the company makes money by destroying their own system,so you'd buy a new one,coz you cant access your data or all your files from the old one,so you would buy a new huawei again,to retrieve your files.
USB SER is testpoint mode. Idk how, but you have closed the service mode contacts. In general, this is solvable, in the service it should not cost a lot of money.