Op5 not detected by pc- stuck at powered by android. - OnePlus 5 Questions & Answers

Hi all,
need help for my op5, been reading from the net but cant find solution.
currently it stuck at powered by android. i have tried using unbrick step, but not working because the phone will turn on when plug in the cable to connect pc
https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
It stuck after factory reset through twrp.
-already unlock bootloader.
- cannot go in recovery.
- cannot bootloader.
- adb not detect device.
thanks,any suggestion n help anyone?

sidqara said:
Hi all,
need help for my op5, been reading from the net but cant find solution.
currently it stuck at powered by android. i have tried using unbrick step, but not working because the phone will turn on when plug in the cable to connect pc
https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
It stuck after factory reset through twrp.
-already unlock bootloader.
- cannot go in recovery.
- cannot bootloader.
- adb not detect device.
thanks,any suggestion n help anyone?
Click to expand...
Click to collapse
You followed step 4 and 5 of the unbrick guide already?
Why you are in this situation? What's happening before and what is your rom, bootloader status?

You followed step 4 and 5 of the unbrick guide already?
4. yes done, im using w10 64bit
5. when connect phone to pc, it boot up to powered by android.
Why you are in this situation? What's happening before and what is your rom, bootloader status?
unlock bootloader rooted with custom rom, then change to oos.
got few error-android not working, so im gonna do clean flash again. go to twrp, factory reset. then its happen.
:silly:

sidqara said:
You followed step 4 and 5 of the unbrick guide already?
4. yes done, im using w10 64bit
5. when connect phone to pc, it boot up to powered by android.
Why you are in this situation? What's happening before and what is your rom, bootloader status?
unlock bootloader rooted with custom rom, then change to oos.
got few error-android not working, so im gonna do clean flash again. go to twrp, factory reset. then its happen.
:silly:
Click to expand...
Click to collapse
And you really pressed the volume up button and then connect it to the PC?
When coming from a custom rom it's highly recommended to wipe system, data, cache and format internal storage too.

strongst said:
And you really pressed the volume up button and then connect it to the PC?
When coming from a custom rom it's highly recommended to wipe system, data, cache and format internal storage too.
Click to expand...
Click to collapse
yup, i'm positive im pressing the volume button, been tried with 2 different laptop, same.
and previously i have succeed unbrick my friend op3, and no issue at all. as i can remember the phone will not turn on rite? when connect to PC.

Update.
succeed, problem solved.
disassemble battery, phone until it wont turn on when connect to pc, lucky it work.
then unbrick using unbrick tools. next plan to change screen n fingerprint scanner.
im happy , bought op5 for a cheap price.

Related

[Q] Rooting Problem

Hello guys!
I wanted to root my Nexus 4 today, and started to do all the steps. I downloaded all the drivers and setupped them.
Then I unlocked the phone by using this command on the correct folder in cmd "adb reboot bootloader".
It was succesfull. Then I did this step by writing this on cmd "fastboot oem unlock". I was succesfull too n there
was no problem. Then I setupped twrp recovery mode v2.6.0.0. But I didn't send the files of SuperSU to the phone. I tried to reboot my phone while it was connected to my pc with usb,the google icon appeared first, then the X icon of nexus appeared. After this, a screen showed up on my pc which says "the drivers are being setupped" but then it showed that it couldnt setup the drivers. Phone stucked here and cannot be started. There is only the X image of nexus but I cant start the phone. I can use recovery mode and bootloader only. So now can u please tell me what I did wrong and what should I do now to start my phone.
By the way I also tried to backup but it failed too.
Thanks, and waiting for your valuable answers.
Have you tried a factory reset from recovery?
Sent from my Nexus 4 using Tapatalk 2
ChrisHRocks said:
Have you tried a factory reset from recovery?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the answer. But if I factory reset, I will not be able to setup any roms cuz I cant connect to my phone from my pc with usb.
So if I factory reset, will I have to setup any roms to my phone ? Also I cant connect to my phone from my pc in recovery mode.
I did a factory reset. And my phone is working now. Thanks for everything. Çükünü yiyim abiii
I would recommend starting everything fresh. Follow this guide to revert to stock, then follow the root steps also in the same post.
Edit: Oops, posted too late. Glad you have it sorted out

Another bootloop problem

hey guys today i was rooting my nexus player.
everything was smooth until SuperSU didn not show up.
after restarting my NP i got stock in boot loop.
I tried to use adb to access my device but ran into an issue
when i use: adb devices - it shows me empty list of devices.
i think its because i can not detect it because its not actually boot in the rom it self.
does anyone know how to fix this?
things i tied:
updating drivers
using adb devices
unplugging power cord and pluging back in
using different usb cables
-- I downloaded SkipSoft tool not really sure how to use it yet or what i exactly need from it.
did anyone use it?
any help would be very appreciated
thank you.
UPDATE:
i managed to get into a stock recovery mode
fastboot is offline.
I think its because the USB debugging is not enabled. is there a way to avoid this?
Did you solve your issue? I also have bootloop and can't access fastboot.
if you saved your old stick rom you should be able to reset it. i think you have to hold power button. this willl allow you to get into settings and pick what file to boot from. sorry it was a while ago when i did this. but if you haven't saved your stick boot than you might be out of options.
eried1 said:
Did you solve your issue? I also have bootloop and can't access fastboot.
Click to expand...
Click to collapse
TotalONE said:
if you saved your old stick rom you should be able to reset it. i think you have to hold power button. this willl allow you to get into settings and pick what file to boot from. sorry it was a while ago when i did this. but if you haven't saved your stick boot than you might be out of options.
Click to expand...
Click to collapse
Tried it and it didn't work. Resetting will just wipe user settings. I believe this to be system related.

[GUIDE]ROOT/TWRP/MULTIROM/Cm13/RR on Locked Bootloader + Hardbrick Recovery

DO NOT FLASH HYDROGEN ROMS ON HELIUM, OR YOU GONNA HAVE A HARDBRICK.
IN CASE YOU HAVE ONE, HERE IS THE SOLUTION.
This was tested with Xiaomi Mi Max 128GB helium and localized rom from xiaomi eu.
I am not responsible for bricked devices or anything else. So at your own risk:
1. Install official MiPhone drivers
2. Download and install MiFash beta.
3. Download and unpack TWRP for miflash: 32gb or 64-128gb thanks @Abdess76.
4. Download ROM for your device, I recommend to try this one. You can install RR/CM Rom as well.
5. Run MiFlash with admin rights.
6. Turn off the phone, plug the cable to PC and halfway to the phone.
7. At the same time press Volume + and Volume - and plug in the cable.
8. Refresh MiFlash phone should show up. (If it didn't then make sure you did it right and u got drivers)
9. Navigate to your unpacked TWRP and flash it.
10. Now, boot ur phone with volume up. It's a bit slow. If it's stuck on miui logo, just release button and wait.
From here start to pay more attention:
11. TWRP can ask for password, press cancel and allow modifications by moving slider.
If you just need ROOT and your current rom, skip to the step 16. Also there is a recovery from boot in system folder. If you won't remove it, recovery may be replaced with stock one after reboot. Keep it that way if you want OTAs.
12. Format data.
13. Enable MTP and put modified zip in your phone.
14. Go to mounts and unmount system **
15. Flash your rom.
16. Flash latest supersu.
17. Reboot the phone.
In case u got NO OS message, then it means that u probably ignored step 15.
Also first boot may take like 15-20 minutes, since eu rom is deodexed.
Just to be sure, after installation mount system partition and navigate to the /system folder using TWRP's file manager and make sure it's not empty.
* In my case system didn't install because script could mount system partition since it was already mounted.
P.S. In order to update, you need to install OTA for offical rom via TWRP. Then without rebooting flash SuperSU, and finally using TWRP's file manager navigate to system folder and delete file named recovery from boot. Doing so will keep root and recovery.
Thank you so much for the guide! I will try it tonite
Waiting for boot loader is just too long..
WOW!!!! Just, wow..... I can not believe it but it worked like a charm. It took me forever to figure out my issue with the drivers, but after solving that I followed you step-by-step. And, lo and behold, it WORKED! Note for other users, Twrp took about a minute or two to finally boot up and it took me personally about 15-20 minutes before MIUI 8 finally booted. Just wait it out and you should have the amazing results that Doom Slayer has so graciously provided you
THANK YOU!!!!
I just done following your guide and it works!!
For rooting, I tried 2 times before it works. I believe you missed out a step to mount back system before flashing supersu.
So in the future, how do we dirty flash? Start from step 13?
How about clean flash? Start from step 12?
Thank you once again for this great guide!!
You saved me a lot of time waiting for Bootloader approval.
flywithme said:
I just done following your guide and it works!!
For rooting, I tried 2 times before it works. I believe you missed out a step to mount back system before flashing supersu.
So in the future, how do we dirty flash? Start from step 13?
How about clean flash? Start from step 12?
Thank you once again for this great guide!!
You saved me a lot of time waiting for Bootloader approval.
Click to expand...
Click to collapse
Yeah, dirty flash is you keep your data and format system and caches .
Clean flash is u format data as well.
The thing is that u have root, and ur phone is also secured. It's linked to ur Mi account, while it's locked. It's better to keep that way
Theoretically If you will ignore steps from 12 to 16. (Maybe u can ignore data formatting too)
Then you can get a ROOT and TWRP on your current rom.
And also theoretically while on miui 8 rom ,u can try to unlock bootloader without waiting.
Try this manual.
I have followed these steps and bricked my phone, spent the last 24h trying to recover it no luck.
I got an error while in the process of flashing the rom at step 16, then tried again and phone went black, stopped responding.
It's not detected using adb or fast boot, it appears in device manager as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB Diagnostics 900E", I have tried to flash again TWRP or the official ROM, it says success every time but the phone is still dead.
Could it be due to locked boot loader ?
agreusar said:
I have followed these steps and bricked my phone, spent the last 24h trying to recover it no luck.
I got an error while in the process of flashing the rom at step 16, then tried again and phone went black, stopped responding.
It's not detected using adb or fast boot, it appears in device manager as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB Diagnostics 900E", I have tried to flash again TWRP or the official ROM, it says success every time but the phone is still dead.
Could it be due to locked boot loader ?
Click to expand...
Click to collapse
Open it up and remove battery for a few minutes, then try again from step 6...
agreusar said:
I have followed these steps and bricked my phone, spent the last 24h trying to recover it no luck.
I got an error while in the process of flashing the rom at step 16, then tried again and phone went black, stopped responding.
It's not detected using adb or fast boot, it appears in device manager as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB Diagnostics 900E", I have tried to flash again TWRP or the official ROM, it says success every time but the phone is still dead.
Could it be due to locked boot loader ?
Click to expand...
Click to collapse
Which rom did u flash, give the link please.
Are u sure it's for your version? It can be a broken file as well.
Does the device connects when u hold both volume buttons?
It's called emergency download mode, u can istall rom with miflasher.
There is a testpoint method also.
All u need is a pic from this post on http://4pda.ru/forum/index.php?showtopic=749580&st=700#entry51154086
U need to disconect battery, connect testpoint to battery and flash ur device with miflash.
After that let it charge, since this in your state phone consumes battery.
thanks for you answer, I flashed the MiMAXPRO EU ROM xiaomi.eu_multi_MIMAXPro_6.8.4_v8-6.0.zip (sorry as a new user not allowed to post a link yet)
When I hold both volume buttons the screen is still black but MI Flasher works with COM10, after flashing a ROM or TWRP again MIFlash says "success" but the phone is still dead and won't start up even after holding power button for a long time.
I'm happy to open the phone and try the method on the russian forum, I will try tomorrow hope it will start up
agreusar said:
thanks for you answer, I flashed the MiMAXPRO EU ROM xiaomi.eu_multi_MIMAXPro_6.8.4_v8-6.0.zip (sorry as a new user not allowed to post a link yet)
When I hold both volume buttons the screen is still black but MI Flasher works with COM10, after flashing a ROM or TWRP again MIFlash says "success" but the phone is still dead and won't start up even after holding power button for a long time.
I'm happy to open the phone and try the method on the russian forum, I will try tomorrow hope it will start up
Click to expand...
Click to collapse
Don't worry about your phone, the testpoint method will work for sure.
But in order to prevent this kind of situations ,we need to determine the reason how did it happen and you need to help me with that one by answering following questions:
1) You have mentioned that you had an error 1st time.
I also had error which was cache related, and it's OK because that partition was just formatted. You tried to flash again... but did you unmount your system partition for second time?
2) What's the capacity of your internal storage?
3) Did you use internal or external storage? If external then I need the model and the file system that have been used on that storage.
Doom Slayer said:
Don't worry about your phone, the testpoint method will work for sure.
But in order to prevent this kind of situations ,we need to determine the reason how did it happen and you need to help me with that one by answering following questions:
1) You have mentioned that you had an error 1st time.
I also had error which was cache related, and it's OK because that partition was just formatted. You tried to flash again... but did you unmount your system partition for second time?
2) What's the capacity of your internal storage?
3) Did you use internal or external storage? If external then I need the model and the file system that have been used on that storage.
Click to expand...
Click to collapse
Hello,
I managed to recover the phone, I installed a fresh windows 7 on another PC with only MI Flash Beta installed, device appeared as "Qualcomm HS-USB QDLoader 9008" as usual and I flashed the china ROM. Not sure why it wouldn't start previously after flashing, maybe issue with drivers.
1) unfortunately I don;t remember the syntax of the error, it was after a few seconds of flashing but the process seemed interrupted, I even googled it but my browser history has been purged.
2) 64GB (Helium)
3)I used internal storage, copied the zip on the phone using MTP.
Might try to go through the process again this weekend.
agreusar said:
Hello,
I managed to recover the phone, I installed a fresh windows 7 on another PC with only MI Flash Beta installed, device appeared as "Qualcomm HS-USB QDLoader 9008" as usual and I flashed the china ROM. Not sure why it wouldn't start previously after flashing, maybe issue with drivers.
1) unfortunately I don;t remember the syntax of the error, it was after a few seconds of flashing but the process seemed interrupted, I even googled it but my browser history has been purged.
2) 64GB (Helium)
3)I used internal storage, copied the zip on the phone using MTP.
Might try to go through the process again this weekend.
Click to expand...
Click to collapse
Well, I guess system was mounted and it gived u the error,but formatted it.
hi to all of you. I am very interested by this thread. Here is the story. I received my brand new mi max helium this week but it was the chinese rom. I am in France and my country did not appear in the settings. So I wanted to flash a global rom. I plugged it to my pc in recovery mode and a window appeared said that there is an update. I clicked ok and after a while I got stuck in the mi logo bootloop.
Then from then I tried everything possible from several solutions here, but nothing worked. What I got is the mi logo without bootloop, but nothing more.
I get the message that the bootloader is locked, but I can't get it unlock if it is in this state.
What I can reach is the recovery mode and the fastboot mode. But nothing else worked, flash or anything.
That is why I am interested to flash a recovery, in order to flash a clean rom, etc..
I did what you, Doom Slayer, explains, but I could not get a twrp flash. It ends with "receiving hello packet" in mi flash, and every thing stopped.
If I cannnot install any recovery, I cannot flash a rom.
So please if you have any suggestion, it would be helpful. Thanks a lot.
alain belay said:
hi to all of you. I am very interested by this thread. Here is the story. I received my brand new mi max helium this week but it was the chinese rom. I am in France and my country did not appear in the settings. So I wanted to flash a global rom. I plugged it to my pc in recovery mode and a window appeared said that there is an update. I clicked ok and after a while I got stuck in the mi logo bootloop.
Then from then I tried everything possible from several solutions here, but nothing worked. What I got is the mi logo without bootloop, but nothing more.
I get the message that the bootloader is locked, but I can't get it unlock if it is in this state.
What I can reach is the recovery mode and the fastboot mode. But nothing else worked, flash or anything.
That is why I am interested to flash a recovery, in order to flash a clean rom, etc..
I did what you, Doom Slayer, explains, but I could not get a twrp flash. It ends with "receiving hello packet" in mi flash, and every thing stopped.
If I cannnot install any recovery, I cannot flash a rom.
So please if you have any suggestion, it would be helpful. Thanks a lot.
Click to expand...
Click to collapse
Did you disable drivers signature?
Also some people have a better luck on windows 7, u can try a virtual machine.
If you can enter EDL mode, then you should be fine.
Unless Chinese already disabled it in a new update.
I would blame drivers. Make sure u got them correctly.
Updated tutorial.
Uploaded TWRP for helium, so you don't need to edit updater script anymore, since script will get correct model.
Now you can try to get root on your current rom and unlock bootloader without Xiaomi's confirmation.
People having helium with unlocked bootloader may also have problems installing roms from xiaomi eu, if they have TWRP from hydrogen.
You may update using my recovery.img from archive using fastboot, or TWRP(will also work for locked bootloader).
Doom Slayer said:
Did you disable drivers signature?
Also some people have a better luck on windows 7, u can try a virtual machine.
If you can enter EDL mode, then you should be fine.
Unless Chinese already disabled it in a new update.
I would blame drivers. Make sure u got them correctly.
Click to expand...
Click to collapse
hi Doom. Thank you for reply. But what do you mean by " disable drivers signature". I did not do anything but install the drivers and when I am on what I think is EDL mode(screen isi black) the driver is recognized as Qualcomm HS-USB QDLoader 9008(COM20).
Anyway, I will give another try and let you know. Thank you again.
---------- Post added at 09:14 AM ---------- Previous post was at 08:22 AM ----------
I followed your guide and I could get the twrp installed. So I tried to install rom(following your link). It said rebooting in 5 seconds, and then nothing. The screen is black, no power anymore, no logo, no vibes, and no life at all.
I cannot get any more reaction from it. I plugged it to my pc, but nothing is connected. I was so happy with twrp working... Any idea?...
one more information I don't know if it can help, when I flashed first, I tried the "xiaomi.eu_multi_MIMAXPro_6.8.4_v8-6.0" and a message said "failed. This rom is for helium and this is hydrogen phone". Which is strange because mine is helium(4GB/128GB).
Then I tried with the "xiaomi.eu_multi_MIMAX_V7.5.6.0.MBCCNDE_v7-6.0" rom, and everything got ok, last message "success. The phone will reboot in 5 seconds", and from then, dead all over...
alain belay said:
one more information I don't know if it can help, when I flashed first, I tried the "xiaomi.eu_multi_MIMAXPro_6.8.4_v8-6.0" and a message said "failed. This rom is for helium and this is hydrogen phone". Which is strange because mine is helium(4GB/128GB).
Then I tried with the "xiaomi.eu_multi_MIMAX_V7.5.6.0.MBCCNDE_v7-6.0" rom, and everything got ok, last message "success. The phone will reboot in 5 seconds", and from then, dead all over...
Click to expand...
Click to collapse
Looks like you installed hydrogen TWRP and that caused all your problems.
I've been very careful to install the helium twrp from this thread...

VNS-L21 Stucked at Device is booting now.No access to ADB,Recovery,FastBoot,erecovery

Hello everyone! I have read almost a hundred threads and discussions about unbricking P9 Lite and none of them was my case. I have unlocked my bootloader and i can tell that by seeing the warning from huawei which says my device is not safe.
Okay, but the case is phone is stucked at Device is booting now and i dont have nothing to pick from because people can choose wrether to press power and continue to boot or hold volume up to go to recovery. But i can`t get anywhere because the phone just go straight to Device is booting now. I can`t get to fastboot, adb, erecovery, recovery or any kind of option instead of seeing Huawei logo when powering up and Device is booting now right after it. No sound from laptop when i connect usb and holding Volume down + Power. Nothing.
Any help would be really appreciated.
have you tried turning the phone on WHILE pressing those keys? volume up + power for recovery, or power down + power for fastboot?
SALVO9 said:
have you tried turning the phone on WHILE pressing those keys? volume up + power for recovery, or power down + power for fastboot?
Click to expand...
Click to collapse
yes, multiple times. that was the first thing to try. Anything else u could think of? :good:
What have you done?
So why is it bricked?
Schlengge said:
What have you done?
So why is it bricked?
Click to expand...
Click to collapse
Well, i updated to Nougat B336. It went all fine but it was slow. So i decided to downgrade to MM using oem-info after that flashing middle package and then MM. But in order to install these with Revolution Recovery you have to change data partition to f2fs than back to ext4 and then format data in order to be able to mount data. And then phone got bricked without any idea why. And then i tried numerous firmwares, extracting update packages flashing boot,cust and system. None of them made it. I had access to fastboot, recovery and emui recovery but recovies from huawei did nothing but to stop at 5% with package errors. Even ones from Huawei official website made exactly for VNS-L21 Dual Sim. The last thing i decided was to flash TWRP Meticulus because i thought partitioning will be better than Revolution but when i flash it i lost every access to this phone. No fastboot, adb, recovery, erecovery even dload\update.app on SD Card doesnt work. :good:
Drained battery in order to somehow make it to fastboot. No success. Even then when holding Vol+ + Vol- and Power i got to No battery symbol. When holding down Vol- + Power i got to Huawei logo and then straight to Device is booting now. If i just leave it as it is it goes to logo than Device is booting now... and nothing happens of course. Huawei got one of the worst support pages after Lenovo maybe. They are just useless
goretsov said:
Drained battery in order to somehow make it to fastboot. No success. Even then when holding Vol+ + Vol- and Power i got to No battery symbol. When holding down Vol- + Power i got to Huawei logo and then straight to Device is booting now. If i just leave it as it is it goes to logo than Device is booting now... and nothing happens of course. Huawei got one of the worst support pages after Lenovo maybe. They are just useless
Click to expand...
Click to collapse
When you connect the phone to the pc HiSuite launches?
Chisetdel31260 said:
When you connect the phone to the pc HiSuite launches?
Click to expand...
Click to collapse
Well, previously i always got in fastboot when i`m connected to HiSuite and click on Restore device (Not supported model for restore! Blaaa) but now i can`t connect even when i`m there. Can someone send me only the usb drivers for the VNS-L21 because i don`t have trust to this HiSuite thing? :highfive:
C`mon guys give us some ideas. I disassembled this little beast take off battery put usb in my laptop and then boom same thing. Huawei logo straight to Device is booting now...
You have to install hisuite because it needs the right drivers to run. Moreover it is a good indicator to know if there is a link between them.
Chisetdel31260 said:
You have to install hisuite because it needs the right drivers to run. Moreover it is a good indicator to know if there is a link between them.
Click to expand...
Click to collapse
Yes, i do know it and yes i do have it installed. This was the first thing i did when i bought this phone. I reinstalled it and it does not make any change. But i think there`s something not exactly right with the connection between the app and the phone because there`s no sound when plugging the phone. That`s a pretty solid clue that something is not right.
goretsov said:
Well, i updated to Nougat B336. It went all fine but it was slow. So i decided to downgrade to MM using oem-info after that flashing middle package and then MM. But in order to install these with Revolution Recovery you have to change data partition to f2fs than back to ext4 and then format data in order to be able to mount data. And then phone got bricked without any idea why. And then i tried numerous firmwares, extracting update packages flashing boot,cust and system. None of them made it. I had access to fastboot, recovery and emui recovery but recovies from huawei did nothing but to stop at 5% with package errors. Even ones from Huawei official website made exactly for VNS-L21 Dual Sim. The last thing i decided was to flash TWRP Meticulus because i thought partitioning will be better than Revolution but when i flash it i lost every access to this phone. No fastboot, adb, recovery, erecovery even dload\update.app on SD Card doesnt work. :good:
Click to expand...
Click to collapse
you could've flashed oeminfo in revolution recovery and then use the update.app of mm, no need to format the data partition.
have you tried booting to fastboot while connected with usb? and if you check device manager while connected, can you find your device in there?
mjz2cool said:
you could've flashed oeminfo in revolution recovery and then use the update.app of mm, no need to format the data partition.
have you tried booting to fastboot while connected with usb? and if you check device manager while connected, can you find your device in there?
Click to expand...
Click to collapse
Yes, i tried it as i said in the previous replies, no i can`t see it in device manager because Windows doesn`t recognise it when i plugged it to the usb ports. I say doesn`t recognise because there is no sound when the phone is being connected and i hold whichever combinations there are for VNS-L21. Thank you for your suggestion if you have any ideas i will appreciate them :highfive:
goretsov said:
Yes, i tried it as i said in the previous replies, no i can`t see it in device manager because Windows doesn`t recognise it when i plugged it to the usb ports. I say doesn`t recognise because there is no sound when the phone is being connected and i hold whichever combinations there are for VNS-L21. Thank you for your suggestion if you have any ideas i will appreciate them :highfive:
Click to expand...
Click to collapse
As i said i`ve read a lot of posts and comments of random users of P9 Lite and all of them doesn`t work for me. We need something out of the box, because i think this is not something you see every day. And it will be usefull to everyone who owns P9 Lite. :good:
goretsov said:
Yes, i tried it as i said in the previous replies, no i can`t see it in device manager because Windows doesn`t recognise it when i plugged it to the usb ports. I say doesn`t recognise because there is no sound when the phone is being connected and i hold whichever combinations there are for VNS-L21. Thank you for your suggestion if you have any ideas i will appreciate them :highfive:
Click to expand...
Click to collapse
did you check device manager itself? no sound playing doesn't mean the device isn't showing up in device manager, it is possible it shows up but isn't recognized. if device manager doesn't list it i haven't said anything
Used another pc
Chisetdel31260 said:
Used another pc
Click to expand...
Click to collapse
I`ll try another PC thank you for that advice. Well last time i checked device manager and nothing showed up even after scaning for changes nothing shows up. Interesting part is even without battery when usb is plugged in there`s no connection between PC and phone.
Can be battery and empty.
Connect it to a wall socket for 2 hours.
Chisetdel31260 said:
Can be battery and empty.
Connect it to a wall socket for 2 hours.
Click to expand...
Click to collapse
Nope i tried it. Doesn`t work. Another pc doesn`t recognize it too. Same thing. Can`t get into anything just logo and then Device is booting now. I`m starting to lose hope.
goretsov said:
Nope i tried it. Doesn`t work. Another pc doesn`t recognize it too. Same thing. Can`t get into anything just logo and then Device is booting now. I`m starting to lose hope.
Click to expand...
Click to collapse
I hope not to say stupidity.
So it makes see huawei logo. So it boots.
I think you deleted something at system.img.
So you have to take your time and make it go to fastboot and install recoverynougatb9, flash system.img b336, make it start again.

Stuck in rescue mode after tried flashing stock firmware

Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㄰㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㄰㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.

Categories

Resources