Need help from you guys!!
when I turn on my phone, it sits at the boot screen with the logo of lg and 5s after it shuts down.
early on the screen, has two messages?
BOOT ERROR IMAGE SIGNATURE
and another saying it will turn off to save battery.
my phone was recognized by the computer screen after that began to appear, the device is no longer recognized ...
Anyone know how to proceed?
just reflash a kdz and it'll work again
laufersteppenwolf said:
just reflash a kdz and it'll work again
Click to expand...
Click to collapse
I already tried that, but my phone is no longer recognized by the computer ...
before this screen appears, was recognized normally after this screen appeared, the phone is no longer recognized.
Flavio Costa said:
I already tried that, but my phone is no longer recognized by the computer ...
before this screen appears, was recognized normally after this screen appeared, the phone is no longer recognized.
Click to expand...
Click to collapse
Phone not recognized when in on state, or in download, recovery mode also? Which flash software you use?
hpnxfox said:
Phone isn't recognized by pc if phone is in SW download mode?
Click to expand...
Click to collapse
I can put it on the screen of S / W Upgrade, however, the phone is not recognized by the computer
Flavio Costa said:
I can put it on the screen of S / W Upgrade, however, the phone is not recognized by the computer
Click to expand...
Click to collapse
Stock rom? Stock recovery or custom? Which rom? Did you try to reset from recovery, and clear cache partition, reboot Pc ? And then try again?
hpnxfox said:
Stock rom? Stock recovery or custom? Which rom? Did you try to reset from recovery, and clear cache partition, reboot Pc ? And then try again?
Click to expand...
Click to collapse
I put the 20A and was functioning normally.
seem to lack any file on the device. in linux with the command lsusb, the device looks like this:
Bus 001 Device 007: ID 1004:6000 LG Electronics, Inc. KU330/KU990/VX4400/VX6000
Flavio Costa said:
I put the 20A and was functioning normally.
seem to lack any file on the device. in linux with the command lsusb, the device looks like this:
Bus 001 Device 007: ID 1004:6000 LG Electronics, Inc. KU330/KU990/VX4400/VX6000
Click to expand...
Click to collapse
Ahhh..sorry i am not so familiar with linux..using win from 3.1.X version till now win 7 64bit, but obviously your pc caught something on usb..maybe to try install, reinstall drivers...linux is not my territory..
hpnxfox said:
Ahhh..sorry i am not so familiar with linux..using win from 3.1.X version till now win 7 64bit, but obviously your pc caught something on usb..maybe to try install, reinstall drivers...linux is not my territory..
Click to expand...
Click to collapse
thanks for the help.
I do not think I can make it work by S / W UPGRADE because adb should be disabled.
honestly, do not know what to do ... more
Flavio Costa said:
I put the 20A and was functioning normally.
seem to lack any file on the device. in linux with the command lsusb, the device looks like this:
Bus 001 Device 007: ID 1004:6000 LG Electronics, Inc. KU330/KU990/VX4400/VX6000
Click to expand...
Click to collapse
hmmm, the device gets recognized, so it's still alife but what "KU330/KU990/VX4400/VX6000" should mean.... no idea... in what mode did you connect it? your (win) pc should recognize it too.
tried to pull the battery, put it back in and connect the device with vol - pressed? does it show any sign, whatsoever?
laufersteppenwolf said:
hmmm, the device gets recognized, so it's still alife but what "KU330/KU990/VX4400/VX6000" should mean.... no idea... in what mode did you connect it? your (win) pc should recognize it too.
tried to pull the battery, put it back in and connect the device with vol - pressed? does it show any sign, whatsoever?
Click to expand...
Click to collapse
when I turn on the machine, he gets 5s on the boot screen with the logo of lg and 2 error messages:
BOOT: ERROR SIGNATURE IMAGE
and another saying it will turn off to save battery.
I can enter the screen of S / W Upgrade, but I can not do anything beyond that.
Flavio Costa said:
when I turn on the machine, he gets 5s on the boot screen with the logo of lg and 2 error messages:
BOOT: ERROR SIGNATURE IMAGE
and another saying it will turn off to save battery.
I can enter the screen of S / W Upgrade, but I can not do anything beyond that.
Click to expand...
Click to collapse
have you followed the tut step by step? disabled the modem?
laufersteppenwolf said:
have you followed the tut step by step? disabled the modem?
Click to expand...
Click to collapse
I think he have a linux base computer..
" in linux with the command lsusb, the device looks like this:
Bus 001 Device 007: ID 1004:6000 LG Electronics, Inc. KU330/KU990/VX4400/VX6000"
laufersteppenwolf said:
have you followed the tut step by step? disabled the modem?
Click to expand...
Click to collapse
yes, it was working very well.
when I follow this tutorial: http://forum.xda-developers.com/showthread.php?t=2180138
I connect with Vol - and gave this error message ... I removed the battery, waited a bit, put again and the device usually called today, I had to restart the phone and started giving this error straight.
hpnxfox said:
I think he got a linux base computer..
" in linux with the command lsusb, the device looks like this:
Bus 001 Device 007: ID 1004:6000 LG Electronics, Inc. KU330/KU990/VX4400/VX6000"
Click to expand...
Click to collapse
this doesn't mean that he hasn't got a win computer i, for example, have got a (dual-booted) win/mint lappy and a xubuntu lappy for building roms etc.
---------- Post added at 11:31 PM ---------- Previous post was at 11:28 PM ----------
Flavio Costa said:
yes, it was working very well.
when I follow this tutorial: http://forum.xda-developers.com/showthread.php?t=2180138
I connect with Vol - and gave this error message ... I removed the battery, waited a bit, put again and the device usually called today, I had to restart the phone and started giving this error straight.
Click to expand...
Click to collapse
hmm, if i recall right, there is a "emergency restore" mode for, well, yeah , emergency restores but i don't know how to get there...
a tergra (3) device is nearly unbrickable...
hpnxfox said:
I think he have a linux base computer..
" in linux with the command lsusb, the device looks like this:
Bus 001 Device 007: ID 1004:6000 LG Electronics, Inc. KU330/KU990/VX4400/VX6000"
Click to expand...
Click to collapse
I use another machine with windows 7, only upgrades, updates to the mobile ... as the windows does not recognize anything apparatus was tested on linux and apparently the linux recognizes it, but not as P880 but these models back in the lsusb command.
How about LGMobile tool support (official tool), under customer support menu chose "recovery phone", i use this several times, and for me worked only if i get out battery, hold volume down and plugin to pc in the same time , and after phone recognition i put battery back and fallow instructions
laufersteppenwolf said:
this doesn't mean that he hasn't got a win computer i, for example, have got a (dual-booted) win/mint lappy and a xubuntu lappy for building roms etc.
---------- Post added at 11:31 PM ---------- Previous post was at 11:28 PM ----------
hmm, if i recall right, there is a "emergency restore" mode for, well, yeah , emergency restores but i don't know how to get there...
a tergra (3) device is nearly unbrickable...
Click to expand...
Click to collapse
it is thought that the lg tools in options, has the emergency recovery, it downloads a version of android, unpacks and starts to do the installation, however, not out 4%, my fear is the battery dies ...
Flavio Costa said:
I use another machine with windows 7, only upgrades, updates to the mobile ... as the windows does not recognize anything apparatus was tested on linux and apparently the linux recognizes it, but not as P880 but these models back in the lsusb command.
Click to expand...
Click to collapse
i guess you've rebooted your pc already?
any chance of accessing another computer?
---------- Post added at 11:40 PM ---------- Previous post was at 11:38 PM ----------
hpnxfox said:
How about LGMobile tool support (official tool), under customer support menu chose "recovery phone", i use this several times, and for me worked only if i get out battery, hold volume down and plugin to pc in the same time , and after phone recognition i put battery back..
Click to expand...
Click to collapse
i need to keep the battery always plugged in while connecting... (crazy screen if not )
Flavio Costa said:
it is thought that the lg tools in options, has the emergency recovery, it downloads a version of android, unpacks and starts to do the installation, however, not out 4%, my fear is the battery dies ...
Click to expand...
Click to collapse
and plugging it into the charger? does the offline-changing work?
EDIT: APX mode! that's what i meant with "emergency recovery-mode"
laufersteppenwolf said:
i guess you've rebooted your pc already?
any chance of accessing another computer?
---------- Post added at 11:40 PM ---------- Previous post was at 11:38 PM ----------
i need to keep the battery always plugged in while connecting... (crazy screen if not )
and plugging it into the charger? does the offline-changing work?
EDIT: APX mode! that's what i meant with "emergency recovery-mode"
Click to expand...
Click to collapse
when I put it to charge the same error message and stays in loop, connects, and disconnects with the error 5s
As I am new to the forum, I have to wait a while to respond ...
Related
I installed a recovery app from play store and flashed recovery from it. it asked to restart phone to boot loader. when i restarted it the screen gone black.
now when i pluged in the device usb and connect it with pc it gives the hardware detection sound and install driver.
Please help what should i do.
kakapagal said:
I installed a recovery app from play store and flashed recovery from it. it asked to restart phone to boot loader. when i restarted it the screen gone black.
now when i pluged in the device usb and connect it with pc it gives the hardware detection sound and install driver.
Please help what should i do.
Click to expand...
Click to collapse
give the link of what you installed form the play store
also need more info about your phone ''fastboot getvar all''
Possibly hard brick
sent from my mobile device
HELP
alray said:
give the link of what you installed form the play store
also need more info about your phone ''fastboot getvar all''
Click to expand...
Click to collapse
i installed Acer Recovery Installer from play store and from this app flashed recovery named Stock USA...... recovery(Do not remember the complete name)
MY device is HTC ONE
CCID is HTC__001
ANDROID VERSION KITKAT 4.4 M7 Europe
Befor flashing there was TWRP custome recovery installed.
someone on the other forum told me that i lost boot loader of my device
i am total noob in this matter. the above mentioned info is all i know so far.
Help
SaHiLzZ said:
Possibly hard brick
sent from my mobile device
Click to expand...
Click to collapse
then what is the solution for hard brick. any help?
kakapagal said:
then what is the solution for hard brick. any help?
Click to expand...
Click to collapse
Can you get into bootloader? Is fastboot working?
Marc199 said:
Can you get into bootloader? Is fastboot working?
Click to expand...
Click to collapse
no cannot boot into boot-loader or in fastboot mood.
it stays black screen but my pc detect hardware when i attche usb cable with my device
kakapagal said:
no cannot boot into boot-loader or in fastboot mood.
it stays black screen but my pc detect hardware when i attche usb cable with my device
Click to expand...
Click to collapse
What does it say in device manager?
So you tried holding power + volume down for more than 15 seconds?
Marc199 said:
What does it say in device manager?
So you tried holding power + volume down for more than 15 seconds?
Click to expand...
Click to collapse
yes i tried this but still screen stays black screen.
i did this with usb attached also. during this process PC gave pluged out and then pluged in sounds
So you have installed an app not intended for your device (for Acer tablets) and you then flashed a recovery for acer a500 tablet in your htc one! :victory::victory::victory:
If you cant access bootloader or send fastboot commands, then you converted your 700$ phone into a 700$ paper weight!
Connect your phone to computer and try this command:
fastboot devices
It should output your device s/n
Sent from my HTC One using xda app-developers app
kakapagal said:
yes i tried this but still screen stays black screen.
i did this with usb attached also. during this process PC gave pluged out and then pluged in sounds
Click to expand...
Click to collapse
Ok. Plug it in and tell me how the device manager recognizes the phone!
alray said:
So you have installed an app not intended for your device (for Acer tablets) and you then flashed a recovery for acer a500 tablet in your htc one! :thumbdown::thumbdown::thumbdown:
If you cant access bootloader or send fastboot commands, then you converted your 700$ phone into a 700$ paper weight! :what:
Connect your phone to computer and try this command:
fastboot devices
It should output your device s/n
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
i used this command . it says no device found and my pc end up searching driver QHUSB-DLOAD(not installed)
Marc199 said:
Ok. Plug it in and tell me how the device manager recognizes the phone!
Click to expand...
Click to collapse
htc manager does not recognize but my pc keep searching a driver named QHUSB-DLOAD(still not installed)
kakapagal said:
htc manager does not recognize but my pc keep searching a driver named QHUSB-DLOAD(still not installed)
Click to expand...
Click to collapse
really bad. Short story: QHUSB-DLOAD = Hard brick
nothing can be done except sending your phone to htc for repair/replacement
kakapagal said:
htc manager does not recognize but my pc keep searching a driver named QHUSB-DLOAD(still not installed)
Click to expand...
Click to collapse
I'm sorry to say this, but this is a hard brick and there is nothing you can do but to get a new device.
Marc199 said:
I'm sorry to say this, but this is a hard brick and there is nothing you can do but to get a new device.
Click to expand...
Click to collapse
i found this on a website will this method work?
Download and install Ubuntu (version 12.04); or create a live CD; or use the WUBI installer to install Ubuntu.
Boot your computer to Ubuntu (do not use a virtual machine).
When the desktop appears, click the Ubuntu icon, and type terminal in the text box that appears.
Open firefox and download the file in the link at the bottom of the page, allow it to save to the default location.
Switch to the terminal window.
Connect the phone via USB.
Type the following commands (note: linux is case sensitive):
cd Downloads
unzip PblClear.zip (download link is available on the website)
chmod 755 PblClear
sudo modprobe qcserial
sudo ./PblClear
The phone should now exit QHSUSB_DLOAD mode. If the phone reboots to android or if the charging LED lights you have been successful.
kakapagal said:
i found this on a website will this method work?
Download and install Ubuntu (version 12.04); or create a live CD; or use the WUBI installer to install Ubuntu.
Boot your computer to Ubuntu (do not use a virtual machine).
When the desktop appears, click the Ubuntu icon, and type terminal in the text box that appears.
Open firefox and download the file in the link at the bottom of the page, allow it to save to the default location.
Switch to the terminal window.
Connect the phone via USB.
Type the following commands (note: linux is case sensitive):
cd Downloads
unzip PblClear.zip (download link is available on the website)
chmod 755 PblClear
sudo modprobe qcserial
sudo ./PblClear
The phone should now exit QHSUSB_DLOAD mode. If the phone reboots to android or if the charging LED lights you have been successful.
Click to expand...
Click to collapse
Can you give us a link for that?
But this is probably for another device and won't work on the One.
Marc199 said:
Can you give us a link for that?
But this is probably for another device and won't work on the One.
Click to expand...
Click to collapse
here is the link
http://unlimited.io/qhsusbdload.htm
kakapagal said:
here is the link
http://unlimited.io/qhsusbdload.htm
Click to expand...
Click to collapse
The One is not supported. But since you have nothing to loose, you could try it.
Marc199 said:
The One is not supported. But since you have nothing to loose, you could try it.
Click to expand...
Click to collapse
someone repaired my device with j tag method but no sim in working. it asks for IMSI Code
I've rooted and flashed ROMs on three previous android phones but I still consider myself something of a noob.
I have a SM-N910T that I've had for a couple of months. I was trying to flash TWRP for the first time. Windows detected the phone (as it always has in the past) and Odin detected the phone. Halfway through the download the process failed and Odin threw up an error message.
Now I get 'Firmware upgrade encountered an issue' with a straight boot. I can boot into download mode on the phone but neither Windows, Odin, or Kies can detect the phone as far as I can tell. There don't appear to be any 'unknown devices' in Device Manager. I've tried different usb ports, different cables, and tried both my laptop and desktop (both are 64-bit windows 8.1) with multiple reboots.
I'm assuming from this point that the phone is hard bricked, but I wanted to see if anyone more knowledgeable had any ideas or input.
Well this is interesting. I can't guarantee this will work, but lets try . . .
1st. Pull the battery from your phone
2nd. Disconnect all usbs from your computer and reboot it
3rd. Once your computer turns back on - open kies 3, click Tools, and then click Reinstall Device Driver. Once finished, close out of kies
4th. Manually boot phone into download mode (Vol down + Home)
5th. Open ODIN and connect phone up to computer
Let me know if the device shows in ODIN before doing anything.
Thanks for taking the time to look at my problem 147aaron.
I followed your steps carefully and ODIN still doesn't see the phone.
halfsmart said:
Thanks for taking the time to look at my problem 147aaron.
I followed your steps carefully and ODIN still doesn't see the phone.
Click to expand...
Click to collapse
Does windows make that noise that something has been connected when you hook it up? If not, it sounds like you are going to have to have it sent in for repair.
I have now also tried installing Heimdall on my Ubuntu laptop and it also fails to detect the phone:
ERROR: Failed to detect compatible download-mode device.
147aaron said:
Does windows make that noise that something has been connected when you hook it up? If not, it sounds like you are going to have to have it sent in for repair.
Click to expand...
Click to collapse
No, it does not (it did before the failed flash). I figured as much, thanks for trying to help.
I'm guessing that the 'premium handset protection' insurance won't cover this?
halfsmart said:
I have now also tried installing Heimdall on my Ubuntu laptop and it also fails to detect the phone:
ERROR: Failed to detect compatible download-mode device.
Click to expand...
Click to collapse
Just checking, did you run as Sudo? Or have you set udev permissions. I always forget this the first time when flashing a phone via linux.
First check that your phone is inserted to a USB2.0 port.
Secondly turn the phone completely off for a few seconds, then manually boot into download. Don't let it boot into download mode by just pressing power!
Finally after plugging it in type dmesg in the terminal, it should show your phone connecting as an USB device.
If not post the output of dmesg > dmesg.log
inconceeeivable said:
Just checking, did you run as Sudo? Or have you set udev permissions. I always forget this the first time when flashing a phone via linux.
Click to expand...
Click to collapse
Good catch. However, running as sudo I still get the same error.
halfsmart said:
Good catch. However, running as sudo I still get the same error.
Click to expand...
Click to collapse
Shoot. Sorry man.
Seems like you have a bad phone.
sfjuocekr said:
First check that your phone is inserted to a USB2.0 port.
Secondly turn the phone completely off for a few seconds, then manually boot into download. Don't let it boot into download mode by just pressing power!
Finally after plugging it in type dmesg in the terminal, it should show your phone connecting as an USB device.
If not post the output of dmesg > dmesg.log
Click to expand...
Click to collapse
Unless I reading it wrong (I'm a command-line noob as well) all USB events took place within the first couple of seconds after booting the laptop. I plugged in the phone probably a minute or so after I got to the desktop, so I don't think it's registering. [EDIT: I typed sudo dmesg | grep -i usb and scanned down the time codes on the list]
Here's the dmesg.log:
Just going to throw this out there but have your checked that reactivation lock is unchecked
fcpelayo said:
Just going to throw this out there but have your checked that reactivation lock is unchecked
Click to expand...
Click to collapse
I'm certain that I never enabled anything like that, and on the downloading screen it says 'REACTIVATION LOCK(KK): OFF'
according to a quick google reactivation lock is only available on Verizon and US Cellular models..
I was talking about the one under settings and security. But if this isn't the problem then sorry idk.
fcpelayo said:
I was talking about the one under settings and security. But if this isn't the problem then sorry idk.
Click to expand...
Click to collapse
I think we're talking about the same thing. Either way, thanks for taking the time, I appreciate it.
i used kingo root in PC to root the phone , then after when i reboot the phone, it was stuck with the logo fore ever..
then i unlocked the boot loader and then flashes it with kitkat stock firmware..
then downloaded the lollipop update in the phone , after installing it the phone didn't booted ..
i cant boot it manually, cant go to fast boot mode ..
it is just dead...
what can i do ..plz help.
not showing qhslk bulk when connected to pc but shows ----unknown usb device(device descriptor request failed)
Oh I think its hardbricked dude,because if bootloader is unlocked then we shouldn't do any official updates...
---------- Post added at 10:53 AM ---------- Previous post was at 10:51 AM ----------
Still u can try to charge it or connect it to pc and goto device manager in pc and see that if it showing qhslk bulk or not,...
Divesh ahuja said:
Oh I think its hardbricked dude,because if bootloader is unlocked then we shouldn't do any official updates...
---------- Post added at 10:53 AM ---------- Previous post was at 10:51 AM ----------
Still u can try to charge it or connect it to pc and goto device manager in pc and see that if it showing qhslk bulk or not,...
Click to expand...
Click to collapse
nope..... not showing ......
Then what is it showing in pc??
Divesh ahuja said:
Then what is it showing in pc??
Click to expand...
Click to collapse
it shows ..
unknown usb device(device descriptor request failed)
i tried the blank flash but during the blank flash error occurs ..
cant install the specified driver for the blank flash..
Then its hardbricked bro,replace motherboard or sell it its body parts who needs or in the market
Just a few general ideas - probably won't help but you never know:
Leave it charging for several hours and then see if you can access fastboot
Try a different PC (including one that you've never plugged your phone into before, one with a different Windows version, etc.) to see if you can get it to recognise the phone as qhslk bulk
Try plugging the device into your PC using a different USB cable to see if you can get it to recognise the phone as qhslk bulk
Have a look around the web on guides for restoring a hard-bricked Moto G 2014 (specific model, type, etc.). This probably won't work but anything is worth a try. You could try following these on different PCs, with different USB cables, etc.
I think this problem was caused by trying to downgrade your phone to KitKat
Hope you get it working
Tried rooting moto xt1060 5.1 with the locked boot loader method, and then got stuck at the black screen from running python. Computer still recognizes it as a QCUSB (COM4) or something similar to that, but screen doesn't turn on at all. Tried every button combo, usb port, how-to's, but I'm a newbie with this. Any help would be appreciated. Thanks.
Its hardbrick, run root file inside that package, but first read and install every drivers mention on that post.
Salik Iqbal said:
Its hardbrick, run root file inside that package, but first read and install every drivers mention on that post.
Click to expand...
Click to collapse
which package?
motoexuser said:
which package?
Click to expand...
Click to collapse
The one you tried too root?
Salik Iqbal said:
The one you tried too root?
Click to expand...
Click to collapse
i tried it. no errors, but phone screen is still black. i am gonna charge the phone over night and try again.
also i get this error every time i try to run RSD lite "phone failed to switch to fast boot"
other info if it helps:
- phone is always recognized as "Qualcomm HS-USB QDLoader 9008 (COM5)"
- computer makes connecting and disconnecting sound when button combinations are held
motoexuser said:
i tried it. no errors, but phone screen is still black. i am gonna charge the phone over night and try again.
also i get this error every time i try to run RSD lite "phone failed to switch to fast boot"
other info if it helps:
- phone is always recognized as "Qualcomm HS-USB QDLoader 9008 (COM5)"
- computer makes connecting and disconnecting sound when button combinations are held
Click to expand...
Click to collapse
Well you need some extra help now.. will send you a package on monday.
Salik Iqbal said:
Well you need some extra help now.. will send you a package on monday.
Click to expand...
Click to collapse
thanks
Hi. I decided to flash my Honor 3c with Cyanogenmod 12.1. My problem is that i need TWRP (now I have CWM) but i can't flash it to my device. I try to do it by SP Flash Tool, but after i connect my turned off device, I get this error:
BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (0x7D4)
[H/W] Fail to download DA to baseband chip's internal SRAM!
[HINT]: 1. There's an cable communication problem between FlashTool and BootROM. 2. Target might be shutdown unexpectedly or target lost power supply.
[ACTION] 1. Try again. 2. Proceed H/W checking in download cable and target side com port. 3. Monitor if power-drop occured in target side.
Click to expand...
Click to collapse
Where is the problem? I've tried with 2 different cables and 2 different computers
Ceranzuo said:
Hi. I decided to flash my Honor 3c with Cyanogenmod 12.1. My problem is that i need TWRP (now I have CWM) but i can't flash it to my device. I try to do it by SP Flash Tool, but after i connect my turned off device, I get this error:
BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (0x7D4)
[H/W] Fail to download DA to baseband chip's internal SRAM!
[HINT]: 1. There's an cable communication problem between FlashTool and BootROM. 2. Target might be shutdown unexpectedly or target lost power supply.
[ACTION] 1. Try again. 2. Proceed H/W checking in download cable and target side com port. 3. Monitor if power-drop occured in target side.
Where is the problem? I've tried with 2 different cables and 2 different computers
Click to expand...
Click to collapse
Is your phone in bootloader mode? Hold Vol down+power to enter fastboot mode and then connect your phone to PC.
If you are already doing that or the problem still persists and have an unlocked bootloader(which I am sure you have), try to flash twrp manually.
muradulislam said:
Is your phone in bootloader mode? Hold Vol down+power to enter fastboot mode and then connect your phone to PC.
Click to expand...
Click to collapse
When I do it, my phone just turns on normally.
How can I check if I have unlocked bootloader? I have unlocked it about 1 year ago, but I did full wipe yesterday.
Ceranzuo said:
When I do it, my phone just turns on normally.
How can I check if I have unlocked bootloader? I have unlocked it about 1 year ago, but I did full wipe yesterday.
Click to expand...
Click to collapse
Vol down+power should boot into fastboot. Turn off the phone, hold both until honor logo shows up, let go of power but hold vol down for about 5 sec more.
If still the same, Turn off your phone, connect USB cable to phone, hold Vol down and connect the cable to computer. It should boot into bootloader now.
If it can not boot into bootloader still, the last is to try adb but that is a bit lengthy.
In bootloader mode, it will be written on phone screen in red whether phone is locked, unlocked or relocked.
Wipe does not effect bootloader status so it's still unlocked imo.
muradulislam said:
If still the same, Turn off your phone, connect USB cable to phone, hold Vol down and connect the cable to computer. It should boot into bootloader now.
Click to expand...
Click to collapse
After this, I got this text on my screen:
FASTBOOT&RESCUE MODE
Please connect usb cable to your computer and open hisuite
Click to expand...
Click to collapse
Ceranzuo said:
After this, I got this text on my screen:
FASTBOOT&RESCUE MODE
Please connect usb cable to your computer and open hisuite
Click to expand...
Click to collapse
It did not say anything about phone unlocked in red?
muradulislam said:
It did not say anything about phone unlocked in red?
Click to expand...
Click to collapse
Nope. Maybe I was wrong and I have never unlocked it? I don't remember, but I did something when I was upgrading my phone to Android 4.4.2
Ceranzuo said:
Nope. Maybe I was wrong and I have never unlocked it? I don't remember, but I did something when I was upgrading my phone to Android 4.4.2
Click to expand...
Click to collapse
At least it should say, phone locked. Saying nothing is a phenomenon i never heard before but I usually go for newer versions. May be that's the case.
Anyways use adb to fire this command
Fastboot OEM device-info
To be sure if its locked or not.
To setup adb, download and install latest Android SDK, run the program and only download platform-tools.
Your phone is international variant and it came with locked bootloader, I am sure sp tools unlocked it coz otherwise CWM could not be flashed.
Right click platform-tools folder and select run command prompt window here and type the above command
If the bootloader is unlocked (it will tell you if it is), copy the twrp image to platform-tools folder and rename it to twrp.img and fire this command
Fastboot flash recovery twrp.img
And try to reboot into recovery after disconnecting from pc and simultaneously holding power+ Vol up.
edit: nevermind, i forghot about something...
muradulislam said:
If the bootloader is unlocked (it will tell you if it is), copy the twrp image to platform-tools folder and rename it to twrp.img and fire this command
Fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Should I do this when my phone is switched off?
Ceranzuo said:
Should I do this when my phone is connected to pc or not? Switched off?
Click to expand...
Click to collapse
When your phone is connected to your pc in fastboot mode.
Lemme know how did it go, will reply back in the morning. Hope everything works fine for you.
Sent from my PLK-L01 using XDA Labs
muradulislam said:
When your phone is connected to your pc in fastboot mode.
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
Ok, after I typed this command, there appeared this message in window:
<waiting for any device>
Click to expand...
Click to collapse
after this I reboot into recovery mode, but there is still CWM, not TWRP
Ceranzuo said:
Ok, after I typed this command, there appeared this message in window:
<waiting for any device>
after this I reboot into recovery mode, but there is still CWM, not TWRP
Click to expand...
Click to collapse
You dont have your phone drivers installed. Google Huawei USB drivers and install them or use hisuite to install drivers for your phone.
After driver installation, do the same process again.
My bad. I assumed you would have drivers already installed
Sent from my PLK-L01 using XDA Labs
muradulislam said:
You dont have your phone drivers installed. Google Huawei USB drivers and install them or use hisuite to install drivers for your phone.
After driver installation, do the same process again.
My bad. I assumed you would have drivers already installed
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
I have already installed many drivers from different sites. I will try with hisuite
Ceranzuo said:
I have already installed many drivers from different sites. I will try with hisuite
Click to expand...
Click to collapse
Hisuite is the best option. Even if that does not work (there is a chance of that), Google Kouch's universal drivers and install those.
May have to manually install dribers if nothing works.
Lemme know how did it go. Will get back to you in the morning if nobody else came along (but someone surely will before that).
Have a nice day/night depending on your time zone
Sent from my PLK-L01 using XDA Labs
---------- Post added at 07:41 PM ---------- Previous post was at 07:31 PM ----------
Lemme get my teacher for you
@DigiGoon
Sent from my PLK-L01 using XDA Labs
I installed Hisuite and connected my phone. Windows have downloaded drivers automatically. And still the same...
But I forgot to tell you that when I connecting my switched off phone, my pc says "USB Device Not Recognized" (or something like that, I dont have english version of windows). Everything is ok when my phone is switched on...
This phone is cursed. I try to give up and stay on my current ROM, so I installed Nova Launcher, but setting it as default doesn't work :/
Thanks for trying to help me anyway.
Ceranzuo said:
I installed Hisuite and connected my phone. Windows have downloaded drivers automatically. And still the same...
But I forgot to tell you that when I connecting my switched off phone, my pc says "USB Device Not Recognized" (or something like that, I dont have english version of windows). Everything is ok when my phone is switched on...
This phone is cursed. I try to give up and stay on my current ROM, so I installed Nova Launcher, but setting it as default doesn't work :/
Thanks for trying to help me anyway.
Click to expand...
Click to collapse
I was awake just for your post. I think I got the problem. You need fastboot drivers imo but I would have to read a bit before I can suggest how to go about it.
Am busy tomorrow but will try to get back to you in the evening (GMT+5 time zone).
Can never be 100% sure but still I am confident, your problem has a solution. Just bear with me a day or two
Sent from my PLK-L01 using XDA Labs
Ceranzuo said:
I installed Hisuite and connected my phone. Windows have downloaded drivers automatically. And still the same...
But I forgot to tell you that when I connecting my switched off phone, my pc says "USB Device Not Recognized" (or something like that, I dont have english version of windows). Everything is ok when my phone is switched on...
This phone is cursed. I try to give up and stay on my current ROM, so I installed Nova Launcher, but setting it as default doesn't work :/
Thanks for trying to help me anyway.
Click to expand...
Click to collapse
Boot into recovery mode, no matter on which recovery are you on, and execute this command:
Code:
adb devices
And see the output, if it says something like:
Code:
**some_number** recovery
then it means there is no problem in the detection of your device by PC, if it does not, then check if the micro USB socket in the device is in good condition.
And I must ask: Are you able to do any operations on device via PC after connecting it?
DigiGoon said:
Boot into recovery mode, no matter on which recovery are you on, and execute this command:
Code:
adb devices
And see the output, if it says something like:
Code:
**some_number** recovery
then it means there is no problem in the detection of your device by PC, if it does not, then check if the micro USB socket in the device is in good condition.
Click to expand...
Click to collapse
I did it and it says some number and recovery
DigiGoon said:
And I must ask: Are you able to do any operations on device via PC after connecting it?
Click to expand...
Click to collapse
In "usb storage media" or something like that? Yes, I do.
Ceranzuo said:
I did it and it says some number and recovery
Click to expand...
Click to collapse
Okay, then it means that there is no problem in the connection. You are using SP Flash tool in which mode?
Sent from my PLK-L01 using Tapatalk