[Q] Broken Flashmode / Fastboot works fine - Sony Xperia X Compact Questions & Answers

Hello everyone,
I played around with my Xperia X Compact, backuped my TA partition, upgraded Android again, unlocked the bootloader and oem partition and then tried to flash a custom ROM. That ROM failed to start and it seems like I couldn't write to the oem partition. Now the real problem started. While I can still enter fastboot mode and flash partitions, I can't enter flashmode anymore. If I try, the light just flashes red, then green for a second and switches off again. It doesn't even show up on my PC in the brief period, that it's green.
I've since flashed android back via fastboot (flashed kernel, system, cache and userdata), but I'm out of ideas, how to restore flashmode or unlock the oem partition, so I can actually write to it. If I try to unlock the oem partition, it just tells me, that this is not needed, but I can't write to it.
Does anyone have any ideas? I tried to find a solution for the last few months now and I'll probably give up and just buy a new phone soon (as I don't like android and I can't even update it to 8).
Thank you in advance!

deepbluev7 said:
Hello everyone,
I played around with my Xperia X Compact, backuped my TA partition, upgraded Android again, unlocked the bootloader and oem partition and then tried to flash a custom ROM. That ROM failed to start and it seems like I couldn't write to the oem partition. Now the real problem started. While I can still enter fastboot mode and flash partitions, I can't enter flashmode anymore. If I try, the light just flashes red, then green for a second and switches off again. It doesn't even show up on my PC in the brief period, that it's green.
I've since flashed android back via fastboot (flashed kernel, system, cache and userdata), but I'm out of ideas, how to restore flashmode or unlock the oem partition, so I can actually write to it. If I try to unlock the oem partition, it just tells me, that this is not needed, but I can't write to it.
Does anyone have any ideas? I tried to find a solution for the last few months now and I'll probably give up and just buy a new phone soon (as I don't like android and I can't even update it to 8).
Thank you in advance!
Click to expand...
Click to collapse
Did you already try drivers install via Flashtool? Open drivers exe file in /flashtool/drivers, and check boxes for fastboot, flashmode, and Xc.

levone1 said:
Did you already try drivers install via Flashtool? Open drivers exe file in /flashtool/drivers, and check boxes for fastboot, flashmode, and Xc.
Click to expand...
Click to collapse
Thank you for your response.
I don't think it's a driver issue. I flashed via flashmode before on Linux and Windows, and in those cases the green light stayed on, until I switched the phone off. Now the green light goes off, before it can even connect to my computer, so it seems like the flashmode crashes on the phone. Nonetheless I tried the driver install, but that didn't change anything.
The phone only lights the green light for a second, before it goes off and then it starts looping red -> green -> off -> repeat.

Related

Nexus 4 Problem: Wont boot into system or recovery, but fastboot and able to flash?!!

Very weird behaviour:
1. Phone does not boot up at all - neither system nor recovery (tried 5.1 and 4.4.4 factory images and 2.8.3.0 TWRP as recovery).
2. Can start in fastboot mode and flash factory image but after flashing modem the device is "stuck" in QHSUSB_DLOAD mode.. when I restart into fastboot it continues to flash and finishes the flashing process apparently.
3. When the device is off and plugged in its recognized as "unkown device" or QHSUSB_DLOAD again - no signs of charging at all.
Phone got to me in "bricked" state - would not boot and was only showing red light when plugging in - after loading it for a while (it showed the battery with a lighning inside on screen during charge attempt, but no percentages at all) i flashed latest factory image but that did not help it seems.. =(
Tried "fastboot erase cache" as well...
Any ideas?
zroice said:
Very weird behaviour:
1. Phone does not boot up at all - neither system nor recovery (tried 5.1 and 4.4.4 factory images and 2.8.3.0 TWRP as recovery).
2. Can start in fastboot mode and flash factory image but after flashing modem the device is "stuck" in QHSUSB_DLOAD mode.. when I restart into fastboot it continues to flash and finishes the flashing process apparently.
3. When the device is off and plugged in its recognized as "unkown device" or QHSUSB_DLOAD again - no signs of charging at all.
Phone got to me in "bricked" state - would not boot and was only showing red light when plugging in - after loading it for a while (it showed the battery with a lighning inside on screen during charge attempt, but no percentages at all) i flashed latest factory image but that did not help it seems.. =(
Tried "fastboot erase cache" as well...
Any ideas?
Click to expand...
Click to collapse
u flashed stock doing fastboot -w update?
C4SCA said:
u flashed stock doing fastboot -w update?
Click to expand...
Click to collapse
downloaded the stock factory images (tried 4.4.4 and 5.1 so far) from google and used the "flash-all.bat". Should I do it manually instead?
What you mean "-w update" is that a parameter for the fastboot flash command?
zroice said:
downloaded the stock factory images (tried 4.4.4 and 5.1 so far) from google and used the "flash-all.bat". Should I do it manually instead?
What you mean "-w update" is that a parameter for the fastboot flash command?
Click to expand...
Click to collapse
He is asking if you wiped the device after flashing. You flashed the image using the flash-all.bat, which wipes the device. And you even erased the cache. So from the flashing point of view, it seems you did everything right. Do you have the wall charger to load the battery (for some hours)? I would try this. Besides, here is another thread, which seems to be related: http://forum.xda-developers.com/nexus-4/help/qhsusbdload-problem-t2253874
cheers
Had it charging for hours before flashing, so battery cant be the problem..
But when I now put the device on PC (or Charger) nothing seems to happen - not showing the charging symbols and PC recognizes the device as QHSUSB_DLOAD.
Fastboot mode is working, Boot to system and recovery show the google logo but thats it, not even a boot animation.
now its gettin recognized only as "unknown device" not even QHSUSB_DLOAD anymore.. weird
zroice said:
Had it charging for hours before flashing, so battery cant be the problem..
But when I now put the device on PC (or Charger) nothing seems to happen - not showing the charging symbols and PC recognizes the device as QHSUSB_DLOAD.
Fastboot mode is working, Boot to system and recovery show the google logo but thats it, not even a boot animation.
Click to expand...
Click to collapse
dont do fastboot erase cache. Do fastboot format cache.
reinstall the correct google usb drivers manually (http://forum.xda-developers.com/nexus-s/general/tutorial-n00bs-install-drivers-windows-t1901617)
try to flash 4.2.2 and see if it boots up using the flash all bat.
that QHSUSB_DLOAD mode i think its teh qualcomm recovery mode or something like that, there is a thread on xda about it.
Yea good idea gonna try and flash older firmware - although there was 5.0 or 5.1 on it when the phone got to me..
Starting to believe its a hardware issue or the bootloader is fked up somehow - the thing wasnt even rooted when it wouldnt start anymore ...
Are there any ready to use packages to flash bootloader again with qpst? Dont have much time for this thing anymore - so I cant assemble my own files - unless thats a quick process.. but from what ive seen its a bit difficult, right?
zroice said:
Yea good idea gonna try and flash older firmware - although there was 5.0 or 5.1 on it when the phone got to me..
Starting to believe its a hardware issue or the bootloader is fked up somehow - the thing wasnt even rooted when it wouldnt start anymore ...
Are there any ready to use packages to flash bootloader again with qpst? Dont have much time for this thing anymore - so I cant assemble my own files - unless thats a quick process.. but from what ive seen its a bit difficult, right?
Click to expand...
Click to collapse
no luck with 4.2.2 either - same behaviour.. flash is alright but then it wont boot or go into recovery.. argh
I had the same issue and this worked for me
https://productforums.google.com/forum/#!searchin/nexus/QHSUSB_DLOAD$20nexus$204/nexus/4Z5Sntc7u2c/HIyGuAVz8EQJ
halloga said:
I had the same issue and this worked for me
https://productforums.google.com/forum/#!searchin/nexus/QHSUSB_DLOAD$20nexus$204/nexus/4Z5Sntc7u2c/HIyGuAVz8EQJ
Click to expand...
Click to collapse
thanks man, tried that but no help. Phone isnt really stuck in the qhsusb_dload mode but it just won't boot neither the normal kernel nor the recovery system. All I can get this thing to boot is the fastboot mode and sometimes after flashing and rebooting from there the phone will be recognized as QHSUSB_DLOAD. When I plug it in while its off (either PC or wall charger) the Google Logo comes up, just as if its trying to boot, but no charging symbols.
In this state (google logo stuck) the pc does not recognize it at ALL - after a while the pc says "unknown device" has been attached but it has no hardware id or anything.
So the booting process is broken most likely. Question is if that is fixable with QPST or something else? Don't wanna invest any more time if its not likely to suceed though.. Already spent hours on this damn thing.. =)
zroice said:
thanks man, tried that but no help. Phone isnt really stuck in the qhsusb_dload mode but it just won't boot neither the normal kernel nor the recovery system. All I can get this thing to boot is the fastboot mode and sometimes after flashing and rebooting from there the phone will be recognized as QHSUSB_DLOAD. When I plug it in while its off (either PC or wall charger) the Google Logo comes up, just as if its trying to boot, but no charging symbols.
In this state (google logo stuck) the pc does not recognize it at ALL - after a while the pc says "unknown device" has been attached but it has no hardware id or anything.
So the booting process is broken most likely. Question is if that is fixable with QPST or something else? Don't wanna invest any more time if its not likely to suceed though.. Already spent hours on this damn thing.. =)
Click to expand...
Click to collapse
I know this situation man, I spent many hours too and finally solution came out that simple Hope you solve it soon
well i tried that - but i only get a "red" light when holding volume down and power while on wall charger.
This resets the QHSUSB_DLOAD mode, but still wont make the phone boot for me. Tried that combo several times - only "red" light no orange or smth.
When i do that combo when the phone is plugged in to the pc and its in qhsusb_dload mode the red light will flash instead of beeing on all the time.
So I think ill give up unless someone can point me to a good QPST guide to rewrite bootloader for the nexus 4...
Must be bootloader or hardware issue im quite sure..

I can' get it to boot properly. Help me please!

A friend of mine gave me this phone after unexpected self shutdown. The phone was in a boot loop. At this point where I am right now I think I tried everything I can. I have read various guides and tutorials how to bring this phone back to life and nothing works for me. I suppose that there is some damage on mainboard but till I losse this phone I want to be sure. So the situation looks like this. Since the bootloader in locked and there is no working OS I am not able to unlock the bootloader. (If I am wrong here tell me please because I can't find a solution "how to unlock bootloader without having working OS"). The only metode to flash this phone in this state is to use QFIL. Flashing through fastboot fails everytime - booloader locked -> no *.img flashing. So I have 4 various versions of stock ROM for this phone and after flashing via QFIL the phone doesn't boot. It end with 3 possible ways. 1'st way - clasic bootloop. 2'nd way - frozen on loading screen. 3'rd way - black screen with blue LED, USB diagnostics state, 9006 port opened, no chance to flash because of closed QD port 9008. After this I have to erase every single one of the partitions made through flashing. Then I am able again to flash with QFIL.
I have no idea where is the problem here or what am I doing wrong. I tested the internal memory with a partitioning program in search of bad sectors -> 100% OK. Filled the whole memory with zero's and then formated it. It didn't help. Are every of my stock ROMs broken or is this phone realy damaged? Dear XDA community help me please! I have no clue what can I still try.
Tried ZUI QPST image or CM one?
ankurpandeyvns said:
Tried ZUI QPST image or CM one?
Click to expand...
Click to collapse
CM through QFIL already tried. Doesn't boot. I've got .zip ROM images but without TWRP no chance to use it. I have got also an image in .qsb file but no idea how to push it into the phone. Will it work through fastboot to put the file into the phone and than flash through diagnostic mode ?
kotex said:
CM through QFIL already tried. Doesn't boot. I've got .zip ROM images but without TWRP no chance to use it. I have got also an image in .qsb file but no idea how to push it into the phone. Will it work through fastboot to put the file into the phone and than flash through diagnostic mode ?
Click to expand...
Click to collapse
I just recommend you downloading this https://drive.google.com/open?id=0B7zm16vLHfdBVi1lWlMwelBBdXc . It's ZUI 2.0.49 for qfil, hope it works for you.
kotex said:
CM through QFIL already tried. Doesn't boot. I've got .zip ROM images but without TWRP no chance to use it. I have got also an image in .qsb file but no idea how to push it into the phone. Will it work through fastboot to put the file into the phone and than flash through diagnostic mode ?
Click to expand...
Click to collapse
Download the CM QFIL image from my video. It should work.
ankurpandeyvns said:
Download the CM QFIL image from my video. It should work.
Click to expand...
Click to collapse
Already tried your copy. To be honest tried it many times in every way I could. The phone is now sitting for over 3h frozen on loading screen. It is never going to boot or tell me that this is normal... Ereased the whole internal memory by delting every existing partition and then flashed it via QFIL. Also tried to format the whole memory in ext4. Same result. Like I said the phone is laying right now for over 3h on the same CYANOGEN screen with some graphical artifacts.
Borja Viera said:
I just recommend you downloading this https://drive.google.com/open?id=0B7zm16vLHfdBVi1lWlMwelBBdXc . It's ZUI 2.0.49 for qfil, hope it works for you.
Click to expand...
Click to collapse
OMG This room booted normaly. Thank you some much my friend! You made my day. It is a step forward. However all connections aren't working. I can't find "OEM unlocking" under Developer Options. I want to unlock the Bootloader as soon as possible so I will be able to put TWRP recovery and then flash it with any available CustomROM
kotex said:
Already tried your copy. To be honest tried it many times in every way I could. The phone is now sitting for over 3h frozen on loading screen. It is never going to boot or tell me that this is normal... Ereased the whole internal memory by delting every existing partition and then flashed it via QFIL. Also tried to format the whole memory in ext4. Same result. Like I said the phone is laying right now for over 3h on the same CYANOGEN screen with some graphical artifacts.
Click to expand...
Click to collapse
What's the result after flashing ZUI 2.5.330 image?
ankurpandeyvns said:
What's the result after flashing ZUI 2.5.330 image?
Click to expand...
Click to collapse
Many hours frozen on black screen with blue led. 9008 QD port blocked. 9006 USB Diagnostics port opened. No chance to flash until all partitions are erased and the port is reset. Otherwise I need to try getting to the 9008 port by puting the USB cable while holding the "Vol Up" button and then flash it agin with QFIL.
kotex said:
Many hours frozen on black screen with blue led. 9008 QD port blocked. 9006 USB Diagnostics port opened. No chance to flash until all partitions are erased and the port is reset. Otherwise I need to try getting to the 9008 port by puting the USB cable while holding the "Vol Up" button and then flash it agin with QFIL.
Click to expand...
Click to collapse
Got successful in flashing?
ankurpandeyvns said:
Got successful in flashing?
Click to expand...
Click to collapse
Yes
Right now thanks to Borja Viera I used the working OS to make a "sdfuse" folder on the internal memory, put the .qsb image file into the folder and flash the phone through diagnostic mode. I have got right now android 5.1.1 on it and it booted normaly However the connections still aren;t working. I managed to enable "OEM unlocking" then got to the fastboot mode with a bit of help from AIO tool (because turning the phone with pressed "Vol Up" and "Vol Down" buttons at the same time makes the menu but no "go to bootloader" shortcut over there). Unlocked the bootloader manualy with minimal ADB. Then I wasn't able to put TWRP as the recovery because of some weird error comming every time I tried the command. So I flashed the phone once again back to CM 12.1 soft only to get other "the better one - with many options" bootloader. Tried flashig TWRP once again and voila! TWRP working!! Bootloader unlocked! In a while I will be downloading some CustomROM and turn this phone back to life... I hope so
[UPDATE]
Tried 5 different ROMs:
Two Cyanogen:
1'st - black screen blue led usb diagnostics state with port 9006 opened
2'nd - frozen on loading screen
Three CustomROMs:
1'st Official Lineage
2'nd Unofficial Lineage
3'rd AICP-12.1
All three are not booting. Phone resets itself on loading screen -> boot loop. Do you have any sugestion right now? In TWRP everything wiped and ROM installed on clean phone. Gapps installed too from Open Gapps website. Eveything done right with the instructions.
Is this phone really damaged?
kotex said:
Yes
Right now thanks to Borja Viera I used the working OS to make a "sdfuse" folder on the internal memory, put the .qsb image file into the folder and flash the phone through diagnostic mode. I have got right now android 5.1.1 on it and it booted normaly However the connections still aren;t working. I managed to enable "OEM unlocking" then got to the fastboot mode with a bit of help from AIO tool (because turning the phone with pressed "Vol Up" and "Vol Down" buttons at the same time makes the menu but no "go to bootloader" shortcut over there). Unlocked the bootloader manualy with minimal ADB. Then I wasn't able to put TWRP as the recovery because of some weird error comming every time I tried the command. So I flashed the phone once again back to CM 12.1 soft only to get other "the better one - with many options" bootloader. Tried flashig TWRP once again and voila! TWRP working!! Bootloader unlocked! In a while I will be downloading some CustomROM and turn this phone back to life... I hope so
[UPDATE]
Tried 5 different ROMs:
Two Cyanogen:
1'st - black screen blue led usb diagnostics state with port 9006 opened
2'nd - frozen on loading screen
Three CustomROMs:
1'st Official Lineage
2'nd Unofficial Lineage
3'rd AICP-12.1
All three are not booting. Phone resets itself on loading screen -> boot loop. Do you have any sugestion right now? In TWRP everything wiped and ROM installed on clean phone. Gapps installed too from Open Gapps website. Eveything done right with the instructions.
Is this phone really damaged?
Click to expand...
Click to collapse
If you're still in warranty, the best bet will be to get it replaced. Because it seems like a serious issue in the hardware.
kotex said:
Yes
Right now thanks to Borja Viera I used the working OS to make a "sdfuse" folder on the internal memory, put the .qsb image file into the folder and flash the phone through diagnostic mode. I have got right now android 5.1.1 on it and it booted normaly However the connections still aren;t working. I managed to enable "OEM unlocking" then got to the fastboot mode with a bit of help from AIO tool (because turning the phone with pressed "Vol Up" and "Vol Down" buttons at the same time makes the menu but no "go to bootloader" shortcut over there). Unlocked the bootloader manualy with minimal ADB. Then I wasn't able to put TWRP as the recovery because of some weird error comming every time I tried the command. So I flashed the phone once again back to CM 12.1 soft only to get other "the better one - with many options" bootloader. Tried flashig TWRP once again and voila! TWRP working!! Bootloader unlocked! In a while I will be downloading some CustomROM and turn this phone back to life... I hope so
[UPDATE]
Tried 5 different ROMs:
Two Cyanogen:
1'st - black screen blue led usb diagnostics state with port 9006 opened
2'nd - frozen on loading screen
Three CustomROMs:
1'st Official Lineage
2'nd Unofficial Lineage
3'rd AICP-12.1
All three are not booting. Phone resets itself on loading screen -> boot loop. Do you have any sugestion right now? In TWRP everything wiped and ROM installed on clean phone. Gapps installed too from Open Gapps website. Eveything done right with the instructions.
Is this phone really damaged?
Click to expand...
Click to collapse
Do you have any telegram account, we could make things faster if we communicate that way.
ankurpandeyvns said:
If you're still in warranty, the best bet will be to get it replaced. Because it seems like a serious issue in the hardware.
Click to expand...
Click to collapse
Asked my firend about it. The phone is like 1 month old. He was making some pictures and the phone suddenly died and got to boot loop. He bought it new on ebay. Shipped from China. He already made some research about the warranty before he gave it to me. He made some calls and emails to customer service here in Germany and they told him that he has to send the phone back to China. No warranty in Germany. It is not worth to send it back to China because of duty tax on the way to China. They send him this phone on some special shipping method to avoid this taxes and stay with profitable shipping price. But if you need to send it back they won;t help you at all. And the dispatch price is a no-go.
Since I have decent experience with electronics and flashing various smartphones he gave it to me with a though that I will be able to bring it back to life.
I already said when I started this topic that I suppose that this phone has some damage on the mainboard because of the weird behaviour. I just want to be sure about that and try everything I can before I tell him that he wasted his money by buying this phone.
I want to thank you for your support! If you have some ideas what could I still try I will gladly listen.
kotex said:
Asked my firend about it. The phone is like 1 month old. He was making some pictures and the phone suddenly died and got to boot loop. He bought it new on ebay. Shipped from China. He already made some research about the warranty before he gave it to me. He made some calls and emails to customer service here in Germany and they told him that he has to send the phone back to China. No warranty in Germany. It is not worth to send it back to China because of duty tax on the way to China. They send him this phone on some special shipping method to avoid this taxes and stay with profitable shipping price. But if you need to send it back they won;t help you at all. And the dispatch price is a no-go.
Since I have decent experience with electronics and flashing various smartphones he gave it to me with a though that I will be able to bring it back to life.
I already said when I started this topic that I suppose that this phone has some damage on the mainboard because of the weird behaviour. I just want to be sure about that and try everything I can before I tell him that he wasted his money by buying this phone.
I want to thank you for your support! If you have some ideas what could I still try I will gladly listen.
Click to expand...
Click to collapse
If you have telegram, drop a message @ankurpandeyvns

Huawei P9 Lite stuck on bootloop, can't enter recovery mode

Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken
There are few different versions of P9 Lite, look at the back of the phone to the bottom to see the numbers beside VSN and let us know.
1) Also when the phone is turned off plug in the usb to a computer or charging adapter
2) Hold down volume up & power
3) Let go of the power button when you feel the buzz while still holding the volume up button
4) Download latest version & recovery.
5) Go to Settings>Developer Options>USB Debugging On
5B) If you don't see Developer Options in settings, then go to Settings>About Phone>Build Number & ( tap the Build Number untill it unlocks)
6) Update us on the status, hope it works out.
GloryNation said:
There are few different versions of P9 Lite, look at the back of the phone to the bottom to see the numbers beside VSN and let us know.
1) Also when the phone is turned off plug in the usb to a computer or charging adapter
2) Hold down volume up & power
3) Let go of the power button when you feel the buzz while still holding the volume up button
4) Download latest version & recovery.
5) Go to Settings>Developer Options>USB Debugging On
5B) If you don't see Developer Options in settings, then go to Settings>About Phone>Build Number & ( tap the Build Number untill it unlocks)
6) Update us on the status, hope it works out.
Click to expand...
Click to collapse
tried to enter recovery, still not work. can't go to developer options because phone is stuck on logo, can't power off. couldn't find any solution that works anywhere, been searching for more than 6 hours, still no use. phone model is VNS-L21 forgot to mention earlier
What exactly were you doing before this happened and does your computer recognize your phone when plugged in at all.
Try holding volume up & down together & plug phone in when it reboots on you, & report back with what you see. If anything at all.
GloryNation said:
What exactly were you doing before this happened and does your computer recognize your phone when plugged in at all.
Try holding volume up & down together & plug phone in when it reboots on you, & report back with what you see. If anything at all.
Click to expand...
Click to collapse
I tried to install nougat update, computer recognizes it only in fastboot. holding volume buttons haven't changed anything still no progress. the thing is i had installed nougat a moth or so ago and it worked fine, then rolled back to marshmallow and now this. i'm pretty sure i tried to install correct package, because it was the same i had installed earlier
Did you download a adb tool on your computer that have the 'fastboot.exe' file? If so open that folder,
Have the mouse curser hover in that folder, hold down shift & right click the mouse
Open command prompt
Connect phone as is in fastboot mode
Type adb devices & press enter
Type adb continue & press enter
Hi,
I have the same issue as ellanyx.
my phone can only be stucked while booting or if I connect my phone to a computer, I'm able to boot it in fastboot.
as ellanyx, I didn't enable usb-debug nor OEM unlock option...
so when I'm in fastboot, I type the command "fastboot oem unlock xxxxxx" (hopefully the different data needed are the correct ones mentioned on the box of the phone) I get this error message:
C:\Users\Dieu\Downloads\SRKToolHuawei-STABLE-V1.3-20160619>fastboot oem unlock xxxxx
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
and off course the other options like "fastboot flash recovery recovery.img "... doesn't work.
I can't use the adb commands neither.
when I type the commande, as mentioned above, "adb devices" or "adb continue", nothing works.
So I'm a bit desesperate
do you have any solution for this kind of issue?
thanks
Dude, so the last firmware on your phone was MM or N? If it was MM you should put stock firmware appropriate for your model in dload folder on SD card and put volume+volume-power, and thats it. If you stack on N,....then I dont know because dload method doesnt work with N, or maybe works if you can find stock firmware with recovery for N.
Regards
Unfortunately I can't update with the 3 button update otherwise it would indeed solvemy problem.
pyromana said:
Unfortunately I can't update with the 3 button update otherwise it would indeed solvemy problem.
Click to expand...
Click to collapse
Probably you didnt have correct Oeminfo for MM if dload method didnt work....Try to conect phone with Toolkit and follow procedure for flashing oeminfo and custombin, after that flash stock recovrry and b161 via dload metod. You will find it on forum here.
Regards
the procedure from SRK toolkit?
would it be possible to provide it? because I can't unlock the OEM and I didn't tick the USB debug think.
Maybe problem with the ps not phone so u can not connect with adb
Try with different pc you must have flash oem with fast boot without enable adb from phone if u in fastboot
I can only boot my phone in fastboot (vol- + power) and not in recovery (vol+ + power).
also when using the SRK toolkit, the first screen tells me to be sure that the usb debugging is enable, which I haven't done...
if I'm not mistaken, fastboot is to use the fastboot command and recovery the adb commands
the connection with fastboot works on my computer, the link is made. however when I type the command to unlock the OEM, I get an error stating that the command is not allowed.
when I use the SRK toolkit, with the different questions, he tries to connect the phone with adb and waiting.... waiting...
is there a command to reboot in recovery but from fastboot? in the otherway around it exists but it doesn't seem that from fastboot to recovery it exists.
thanks.
Alexxxx1 said:
Dude, so the last firmware on your phone was MM or N? If it was MM you should put stock firmware appropriate for your model in dload folder on SD card and put volume+volume-power, and thats it. If you stack on N,....then I dont know because dload method doesnt work with N, or maybe works if you can find stock firmware with recovery for N.
Regards
Click to expand...
Click to collapse
dload method works on N. I downgraded my phone from unofficial N update back to official MM update using this method yesterday. You just have to enable OEM at developer options on settings.
It looks like people can't be bothered to read the 1st post properly before they reply.
HE CAN NOT BOOT TO ANDROID SO HE CAN NOT ENABLE OEM OR ACTIVATE USB DEBUGGING!!!!
What he CAN do, is go into eRecovery and Fastboot.
With that in mind, I would suggest using the dload method through fastboot.
Also, make sure it is Huawei SRK Tools 2.0 that is used, as it actually asks if you are in debug mode or fastboot.
Note that there is a few bugs in SRK 2.0:
The TWRP recovery file has the wrong filename in the package, so it WILL fail unless you name it correctly.
Also, when trying to root, do NOT use the "P9 Lite" method as that WILL fail too. Use the "P9/P9 Plus" method.
I am trying to set up a complete guide that can restore the phone when it is stuck in fastboot, however I apparently went a step too far...
ellanyx said:
Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken[/QUOTE
Do you have TWRP recovery ?
---------- Post added at 09:55 AM ---------- Previous post was at 09:50 AM ----------
ellanyx said:
Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken
Click to expand...
Click to collapse
Boot into fastboot mode and flash a custom recovery by meticulus. Link : meticulus.co.vu
Then whenyou get stuck hold power and vol down button for 2 minutes the phone will reboot and then when it says that your device has been unlocked and cant be trusted then only press vol up key ( dont press power button then). The u get into huawei recovery. From that u should power off the phone. Now get a custom rom by meticulus into your device sd card ( Cyanogenmod 13 is recommended ). Then insert sd card in a powered off phone. Now press vol up and power key and flash gapps and custom rom and you are good to go.
Click to expand...
Click to collapse
So, MY question:
I have tried 4 times to get Nougat installed, but every time I got the SMALL package (1.25gb) which means it is not complete.
I decided to try ONE more time, but think I have made a serious mistake.
I was on B161 and tried to downgrade to B160 without upgrading to Nougat first.
This has caused my phone to be stuck at boot with the message "Your device is booting now..."
I can NOT get into eRecovery or fastboot no matter what I do.
If I just leave the phone, then it discharge very fast, but as soon as I plug it in, it starts up and gets stuck at the same screen again.
Does anyone have ANY idea about how I can get out of this problem?
UPDATE:
I have managed to boot to fastboot while connected to my pc.
The phone is unlocked but FRP is LOCKED, which means I can't flash anything.
I read about using Miracle Loader to remove the FRP lock, but it can't "see" my phone. Maybe I am doing it wrong?
SnowmanDK said:
So, MY question:
I have tried 4 times to get Nougat installed, but every time I got the SMALL package (1.25gb) which means it is not complete.
I decided to try ONE more time, but think I have made a serious mistake.
I was on B161 and tried to downgrade to B160 without upgrading to Nougat first.
This has caused my phone to be stuck at boot with the message "Your device is booting now..."
I can NOT get into eRecovery or fastboot no matter what I do.
If I just leave the phone, then it discharge very fast, but as soon as I plug it in, it starts up and gets stuck at the same screen again.
Does anyone have ANY idea about how I can get out of this problem?
UPDATE:
I have managed to boot to fastboot while connected to my pc.
The phone is unlocked but FRP is LOCKED, which means I can't flash anything.
I read about using Miracle Loader to remove the FRP lock, but it can't "see" my phone. Maybe I am doing it wrong?
Click to expand...
Click to collapse
Try to relock and then unlock the bootloader again. And make sure oem unlocking is enabled in dev options
Arsaam said:
Try to relock and then unlock the bootloader again. And make sure oem unlocking is enabled in dev options
Click to expand...
Click to collapse
Please read my previous post again
I can NOT boot normally. And as FRP is locked, then I can't relock or unlock the bootloader.
SnowmanDK said:
Please read my previous post again
I can NOT boot normally. And as FRP is locked, then I can't relock or unlock the bootloader.
Click to expand...
Click to collapse
Go to fast boot mode and from their try to flash meticulus recovery.
You can also try the adb method as well.
Visit meticulus.co.vu

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.

How to unlock Moto C Plus bootloader

I bought a Motorola Moto C Plus a while ago so I can root it and play around with it. I tried to unlock the bootloader for a while on this phone but I just can't. Every guide I tried didn't work. From mfastboot to MTKClient.
mfastboot just gave "unknown command" when trying to get unlock data, and MTKClient couldn't detect a partition or something when trying to wipe.
Then I tried searching my serial number: ZW2224XFWW, but that gave no results. Not on Google nor on here. Can anybody help. I'm very new to the rooting scene.
EDIT: I have a Moto C Plus with 1GB RAM and 16GB internal storage
MTKClient works, download the live .iso file from https://github.com/bkerler/mtkclient
Boot from it, open a console and type:
pip3 install -r requirements.txt
First just follow the readme to unlock the bootloader and after that root with latest magisk. I just tested all that on a moto C, I don't have the exact model but it was the 8gb/1gb variant.
Something's going terribly wrong because now it hangs at 43.8% while flashing boot partition and i dont know why
(I'm scared...)
MarkPCExpert said:
Something's going terribly wrong because now it hangs at 43.8% while flashing boot partition and i dont know why
(I'm scared...)
Click to expand...
Click to collapse
After further investigation, this happens also at recovery and maybe also other partitions so now it is soft bricked
EDIT: it seems that the connection stops or something because after it fails flashing, i also cant do other operations. I NEED HELP!!!
EDIT 2: after trying the console instead of the gui, i discovered that it was never unlocked in the first place. It said "unknown seccfg partition header, aborting unlock"
You are going to know you have your bootloader unlocked if you see a white letters on black background message saying that the phone will boot in 5 seconds after turning it on. You can't flash anything with a locked bootlader.
THATS EXACTLY WHAT I'M GETTING!!! But still, i can't flash a single thing. and I dont know why. I tried to flash TWRP recovery to install a lineageos build but TWRP hangs at 88%. And the patched magisk thingy hung at 43.8%
Now the phone is kind of bricked.
EDIT: Maybe the hang is because i use USB 2 or the Live ISO on a not so good USB. I do use an upgraded Dell OptiPlex 3010 as my main machine. Or the hang is bcuz it failed to flash.
Reflash the original firmware and try again. If you did a backup just flash the original boot.bin
Welp. I am screwed. I forgot i was running a live USB so the entire backup is gone.
And the userdata was also empty for the most part.
Try this: https://www.motorola.com/us/rescue-and-smart-assistant/p
If that doesn't work see if you can find a stock firmware and flash with flash tool. https://androidfilehost.com/?fid=889964283620774903
I already tried that one, but when i plug it in, it doesnt do anything and I DONT KNOW WHY!
also im on vacation
UPDATE: im back from vacation and no replies, great...
BUT, ive chosen a mostly aosp based rom for the phone.

Categories

Resources