Related
i cant go to system , recovery or download mode , when i power on my device have a error certificate verification fail with lg logo for few seconds and then black screen , . what should i do ,
janukpalm said:
i cant go to system , recovery or download mode , when i power on my device have a error certificate verification fail with lg logo for few seconds and then black screen , . what should i do ,
Click to expand...
Click to collapse
Are you sure you cannot get into download mode? Hole power til you see the LG logo twice, then release so it powes off completely... Then hold only Volume up and plug the phone into your computer while holding it.
janukpalm said:
i cant go to system , recovery or download mode , when i power on my device have a error certificate verification fail with lg logo for few seconds and then black screen , . what should i do ,
Click to expand...
Click to collapse
What did you do or think you did to cause this? I would be easier to help if we knew what you were doing when this happened.
janukpalm said:
i cant go to system , recovery or download mode , when i power on my device have a error certificate verification fail with lg logo for few seconds and then black screen , . what should i do ,
Click to expand...
Click to collapse
I had the same problem. Spent nearly 10 hours trying to figure it all out but never made any progress. I sent it to LG though and they are working on fixing it up right now.
whoamanwtf said:
Are you sure you cannot get into download mode? Hole power til you see the LG logo twice, then release so it powes off completely... Then hold only Volume up and plug the phone into your computer while holding it.
Click to expand...
Click to collapse
YEs , i tried that too , but still cant go to download mode . it will show up the same screen and black screen , ,
mazer4455 said:
I had the same problem. Spent nearly 10 hours trying to figure it all out but never made any progress. I sent it to LG though and they are working on fixing it up right now.
Click to expand...
Click to collapse
so what do you think what should i do . can i send it to lg to fix it , ?
Jimi Mack said:
What did you do or think you did to cause this? I would be easier to help if we knew what you were doing when this happened.
Click to expand...
Click to collapse
i got an update after i installed it it didnt boot to system , went to recovery and after i restart it this happened . .
try plugging it in and use the LG software...I never done it myself but if you search i think there is a way you can fix it using LG software.
janukpalm said:
i cant go to system , recovery or download mode , when i power on my device have a error certificate verification fail with lg logo for few seconds and then black screen , . what should i do ,
Click to expand...
Click to collapse
I am not sure if you this will help 100% but what I did was installed the recovery in my phone then I updated my phone. Which made my phone go in recovery and if I restarted it gets stuck in recovery. I wasn't able to get in download mode as well.
If you can get in "recovery" then you can use this fix
to get in recovery hold the vol- and power button until your phone vibrate and you are in recovery.
then execute these commands through adb shell
http://forum.xda-developers.com/showthread.php?t=2451696
Edit--- after executing the commands flash the stock rom--- using LG flashing kit. Search the xda and you will be able to find a thread that details how to do it. yes you will be able to get in download mode, i got there in 2 tries.
aatish said:
I am not sure if you this will help 100% but what I did was installed the recovery in my phone then I updated my phone. Which made my phone go in recovery and if I restarted it gets stuck in recovery. I wasn't able to get in download mode as well.
If you can get in "recovery" then you can use this fix
to get in recovery hold the vol- and power button until your phone vibrate and you are in recovery.
then execute these commands through adb shell
http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
Thats also not working bro , anyway thanks for reply . i cant go to download model or system , stucked with black screen ,
janukpalm said:
Thats also not working bro , anyway thanks for reply . i cant go to download model or system , stucked with black screen ,
Click to expand...
Click to collapse
okay i am just saying but have you tried all keys combination to turn on your phone?
vol down and power
vol up + down and power
have you tried hard reset?
http://lgviet.com/forum/threads/moi-thu-ve-lg-g2-root-recovery-kdz-rom.4367/
read this forum
.... i wasn't able to get in recovery easily ... i had to keep trying until my phone vibrates and bang i am there... it never worked for the first time...
aatish said:
okay i am just saying but have you tried all keys combination to turn on your phone?
vol down and power
vol up + down and power
have you tried hard reset?
http://lgviet.com/forum/threads/moi-thu-ve-lg-g2-root-recovery-kdz-rom.4367/
read this forum
.... i wasn't able to get in recovery easily ... i had to keep trying until my phone vibrates and bang i am there... it never worked for the first time...
Click to expand...
Click to collapse
yeah , i tried everything since last night , and it wont vibrate either . did you also had the same black screen thing .
janukpalm said:
yeah , i tried everything since last night , and it wont vibrate either . did you also had the same black screen thing .
Click to expand...
Click to collapse
What kind of update caused this? You mentioned you got an update and then it was stuck dead.
Rooted/Custom Rom?
I was about to root my device and came to look at some instructions, this thread scared me...
hydeah said:
What kind of update caused this? You mentioned you got an update and then it was stuck dead.
Rooted/Custom Rom?
I was about to root my device and came to look at some instructions, this thread scared me...
Click to expand...
Click to collapse
NEVER UPDATE YOUR OTA AFTER INSTALLING RECOVERY!
read this!
http://lgviet.com/forum/threads/mot-so-van-de-can-luu-y-khi-su-dung-up-rom-cho-g2-can-phai-doc.4443/
---------- Post added at 12:43 PM ---------- Previous post was at 12:41 PM ----------
janukpalm said:
yeah , i tried everything since last night , and it wont vibrate either . did you also had the same black screen thing .
Click to expand...
Click to collapse
My phone got stuck in boot loop, keep restarting in loop but I was able to get in recovery.
I am wondering what you did? recall the steps... then maybe someone can help.
aatish said:
NEVER UPDATE YOUR OTA AFTER INSTALLING RECOVERY!
read this!
http://lgviet.com/forum/threads/mot-so-van-de-can-luu-y-khi-su-dung-up-rom-cho-g2-can-phai-doc.4443/
---------- Post added at 12:43 PM ---------- Previous post was at 12:41 PM ----------
My phone got stuck in boot loop, keep restarting in loop but I was able to get in recovery.
I am wondering what you did? recall the steps... then maybe someone can help.
Click to expand...
Click to collapse
yeah , thanks bro , my problem is also the same , but i guess im not lucky as u are , for now
janukpalm said:
yeah , thanks bro , my problem is also the same , but i guess im not lucky as u are , for now
Click to expand...
Click to collapse
I had korean phone and I was able to take out the battery and then plug it back in. Then tried turning on my phone while holding three buttons it showed me a korean menu, I dont' exactly remember but one of those option took me to recovery.
try holding all three button in boot.
aatish said:
NEVER UPDATE YOUR OTA AFTER INSTALLING RECOVERY!
read this!
http://lgviet.com/forum/threads/mot-so-van-de-can-luu-y-khi-su-dung-up-rom-cho-g2-can-phai-doc.4443/
---------- Post added at 12:43 PM ---------- Previous post was at 12:41 PM ----------
.
Click to expand...
Click to collapse
Sorry, can't read the link, but by recovery, you mean TWRP, right?
So basically, after rooting we can still do an OTA update, and it's still safe, right? But once we installed TWRP, we should not do any kind of OTA updates?
For TWRP, is this method good enough:
http://www.youtube.com/watch?v=nTJI9ThY0mk
To Root, I will use this method:
http://www.youtube.com/watch?v=Y45SXPRb31o#t=149
Sorry if I am steering topic off-course but I just wanted to make sure others don't do the same mistakes and end up in same situation.
Your suggestion of not doing OTA update is really valuable, so I wanted to build on that.
hydeah said:
Sorry, can't read the link, but by recovery, you mean TWRP, right?
So basically, after rooting we can still do an OTA update, and it's still safe, right? But once we installed TWRP, we should not do any kind of OTA updates?
For TWRP, is this method good enough:
http://www.youtube.com/watch?v=nTJI9ThY0mk
To Root, I will use this method:
http://www.youtube.com/watch?v=Y45SXPRb31o#t=149
Sorry if I am steering topic off-course but I just wanted to make sure others don't do the same mistakes and end up in same situation.
Your suggestion of not doing OTA update is really valuable, so I wanted to build on that.
Click to expand...
Click to collapse
The easiest and the way that really worked for me was to root it using "Vroot" http://www.mgyun.com/
but you should check which phone you have and which OTA version you have. As far as I know 11g and 11c for korean variant can only have cwm i am not sure if that is true for other phones as well. But be sure to check it. TWRP only works for 10x versions (where x is any alphabets) still dig deeper, I might be wrong.
But you should never update your phone after recovery.
and backup your IMEI number ... the thread i posted earlier try using google translate and download the apk to backup your IMEI by Hoang.
aatish said:
The easiest and the way that really worked for me was to root it using "Vroot" http://www.mgyun.com/
but you should check which phone you have and which OTA version you have. As far as I know 11g and 11c for korean variant can only have cwm i am not sure if that is true for other phones as well. But be sure to check it. TWRP only works for 10x versions (where x is any alphabets) still dig deeper, I might be wrong.
But you should never update your phone after recovery.
and backup your IMEI number ... the thread i posted earlier try using google translate and download the apk to backup your IMEI by Hoang.
Click to expand...
Click to collapse
I have the AT&T version. D800, Software Version D80010d.
First Thai, now Chinese? You are killing me. I don't use Chrome so they don't get translated automatically.
hydeah said:
I have the AT&T version. D800, Software Version D80010d.
First Thai, now Chinese? You are killing me. I don't use Chrome so they don't get translated automatically.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2434453
you will get vroot
The reason I'm making this thread is because I was trying to root my Honor 8 and things just didn't work out in TWRP. Rebooted my phone and I realized I had bricked it since it would not boot after 10 minutes. Solutions seem to be scattered throughout different threads so here's guide for when you're stuck in a boot loop or you bricked your Honor 8.
What you'll need:
1. The firmware currently you are on. @Coolyou posted a guide for a firmware finder. Here is the post.
2. SD Card
What to do:
Step 1.
Download the correct firmware. It will be a .zip file.
Step 2.
Create a folder called dload in the root of your SD card, not your internal storage. Copy the .zip file the folder and unzip it or unzip it else where and copy the content into the dload folder
Step 3.
Power off Honor 8 (if possible, sometimes it'll auto boot up when forced shutdown)
Step 4.
Make sure your device is not plugged into a computer as it will load into something else.
Hold Vol+ & Vol- & Power. It will being to install the firmware from the dload folder if done correctly. If it instantly fails that means you downloaded the incorrect firmware the device is already one.
You're done! However, if your device does not go past the startup logo within 3 minutes proceed to step 5.
Step 5 is probably necessary as everytime I've bricked my device, I've had to do the next step.
Step 5.
Power off. Hold power and Vol+. Once in Recovery mode (not eRecovery), clear cache and format your device. Once done, reboot.
Ta-da, you're device is now back to normal.
Unfortunately, I cant seem to get to the part where it detects my dload folder and installs from the UPDATE.APP file. My phone keeps auto restarting whenever I try to turn off, and since bootloader is locked, I cant flash any images. Every time I hold down Vol+, Vol-, and power button the phone just vibrates twice and goes to the blue honor boot logo. I have successfully managed to get to the Fastboot menu by holding down Vol- and power button, but this menu is useless as bootloader is locked. Is there anything I can do?
Let go off the power button after the first vibration. Also make sure your phone is not plugged to a pc. With pc connected it boots into eRecovery instead of recovery. Good luck!
Edit:Also the guide does not make it 100% specific but the dload folder on the sd card needs to have the update.app file right inside it. If the structure is sd\dload\folder\update.app it also won't work.
Rakeen70210 said:
Unfortunately, I cant seem to get to the part where it detects my dload folder and installs from the UPDATE.APP file. My phone keeps auto restarting whenever I try to turn off, and since bootloader is locked, I cant flash any images. Every time I hold down Vol+, Vol-, and power button the phone just vibrates twice and goes to the blue honor boot logo. I have successfully managed to get to the Fastboot menu by holding down Vol- and power button, but this menu is useless as bootloader is locked. Is there anything I can do?
Click to expand...
Click to collapse
i have same problem!
i can't reboot in download mode: it vibrates twice and reboot in blue screen always, even leaving power button after first vibration.
How can i fix this?
please help..!
alec_trikki said:
i have same problem!
i can't reboot in download mode: it vibrates twice and reboot in blue screen always, even leaving power button after first vibration.
How can i fix this?
please help..!
Click to expand...
Click to collapse
i have same problem, you can fix this? help me please
Add me to the list, two soft bricked Honor 8's. Once I made the jump to Nougat and installed the Nougat version of TWRP 3.0.1-1, I started having issues. So, I tried to downgrade to FRD-L04C567B150 from FRD-L04C567B320 and had big problems installing B150. Always getting unable to load /data Has to be something to do with the new data structure of Nougat I have a copy of the full stock rom of B150 and B162 and have wiped the phone. I am trying to dload full B150 from SDcard but will fail immediately and says Wrong Version. I can get to fastboot and ADB. I also tried custom ROMs but that wont work because they need the basic Nougat structure to work from. I don't have a clue how to proceed seeing that I can't even wipe the phone and install a Full stock ROM B150 or B162??
Any help would be extremely appreciated.
thekubiaks said:
Add me to the list, two soft bricked Honor 8's. Once I made the jump to Nougat and installed the Nougat version of TWRP 3.0.1-1, I started having issues. So, I tried to downgrade to FRD-L04C567B150 from FRD-L04C567B320 and had big problems installing B150. Always getting unable to load /data Has to be something to do with the new data structure of Nougat I have a copy of the full stock rom of B150 and B162 and have wiped the phone. I am trying to dload full B150 from SDcard but will fail immediately and says Wrong Version. I can get to fastboot and ADB. I also tried custom ROMs but that wont work because they need the basic Nougat structure to work from. I don't have a clue how to proceed seeing that I can't even wipe the phone and install a Full stock ROM B150 or B162??
Any help would be extremely appreciated.
Click to expand...
Click to collapse
UPDATE : It freaking worked!!! After an entire weekend of hair pulling and going way deep into Nougat and MM trying to find the cause, it was a simple Full ROM B162 that I dloaded and three fingered from the SD card (of course it has to be the exact ROM for your phone such as FRD-L04C567B###). WOW, two phones are back. I'll stay at FRD-L04C567B162 and like it.
Lesson Learned: When you try to do an eRecovery and the Honor 8 starts downloading new firmware from the internet it creates a new folder on the sd card called something like HwOC. In that folder is stored the new firmware that erecover plans to use on the recovery. IF this HwOC folder is present and you try to do a Full ROM three finger install with the B150 or B162 firmware in the dload folder, the recovery will stop and say something like invalid version. To fix, remove the HwOC folder so that only dload is present, now do the three finger start and the firmware will install without error. Worked twice for me.
Hi, my device is still not booting up after installing the matching dload firmware on my device from the honor 8 website (FRD-L09).
Is there still anything I can do to maybe get this fixed?
I created a nandroid backup of all partitions that I were able to back up, but even rolling back all partitions did not make it boot again.
Sadly, I am not able to get the device into e.g. fastboot mode anymore because it is not booting anymore and therefore cant get an adb shell on it.
I can still enter recovery mode, but when trying to boot it just stays at the blue screen with the white "honor" text after the short boot animation with the 3d text
Hi,
my phone keeps entering eRecovery and my PC does not recognize it so please how can I access it to install files. I think I have installed a wrong boot.img and recovery.img version of firmware.
Please I need help.
Thanks
Lorog said:
Hi,
my phone keeps entering eRecovery and my PC does not recognize it so please how can I access it to install files. I think I have installed a wrong boot.img and recovery.img version of firmware.
Please I need help.
Thanks
Click to expand...
Click to collapse
Same here on a Note 8 did you find a solution?
thekubiaks said:
UPDATE : It freaking worked!!! After an entire weekend of hair pulling and going way deep into Nougat and MM trying to find the cause, it was a simple Full ROM B162 that I dloaded and three fingered from the SD card (of course it has to be the exact ROM for your phone such as FRD-L04C567B###). WOW, two phones are back. I'll stay at FRD-L04C567B162 and like it.
Lesson Learned: When you try to do an eRecovery and the Honor 8 starts downloading new firmware from the internet it creates a new folder on the sd card called something like HwOC. In that folder is stored the new firmware that erecover plans to use on the recovery. IF this HwOC folder is present and you try to do a Full ROM three finger install with the B150 or B162 firmware in the dload folder, the recovery will stop and say something like invalid version. To fix, remove the HwOC folder so that only dload is present, now do the three finger start and the firmware will install without error. Worked twice for me.
Click to expand...
Click to collapse
Do you have the link for the b162 full firmware?
edit:
also what recovery did you have installed when you did this?
nickp22127 said:
Do you have the link for the b162 full firmware?
edit:
also what recovery did you have installed when you did this?
Click to expand...
Click to collapse
Its erecovery
tiagoesbastos said:
i have same problem, you can fix this? help me please
Click to expand...
Click to collapse
i have the same pblm...how did u both managed to boot it then??
---------- Post added at 11:46 AM ---------- Previous post was at 11:45 AM ----------
alec_trikki said:
i have same problem!
i can't reboot in download mode: it vibrates twice and reboot in blue screen always, even leaving power button after first vibration.
How can i fix this?
please help..!
Click to expand...
Click to collapse
tiagoesbastos said:
i have same problem, you can fix this? help me please
Click to expand...
Click to collapse
i have the same pblm...can u tell how did u managed to solve it???
oops, wrong thread
abbassbhai said:
i have the same pblm...how did u both managed to boot it then??
---------- Post added at 11:46 AM ---------- Previous post was at 11:45 AM ----------
i have the same pblm...can u tell how did u managed to solve it???
Click to expand...
Click to collapse
Do you find a solution? I have the same problem!
Rakeen70210 said:
Unfortunately, I cant seem to get to the part where it detects my dload folder and installs from the UPDATE.APP file. My phone keeps auto restarting whenever I try to turn off, and since bootloader is locked, I cant flash any images. Every time I hold down Vol+, Vol-, and power button the phone just vibrates twice and goes to the blue honor boot logo. I have successfully managed to get to the Fastboot menu by holding down Vol- and power button, but this menu is useless as bootloader is locked. Is there anything I can do?
Click to expand...
Click to collapse
Did you find a solution? I have the same problem!
Rakeen70210 said:
Unfortunately, I cant seem to get to the part where it detects my dload folder and installs from the UPDATE.APP file. My phone keeps auto restarting whenever I try to turn off, and since bootloader is locked, I cant flash any images. Every time I hold down Vol+, Vol-, and power button the phone just vibrates twice and goes to the blue honor boot logo. I have successfully managed to get to the Fastboot menu by holding down Vol- and power button, but this menu is useless as bootloader is locked. Is there anything I can do?
Click to expand...
Click to collapse
Hi, I have the exact same problem. Have you managed to fix it?
Same problems as other people above, couldn't load any recovery. Anyone can help us out?
Rakeen70210 said:
Unfortunately, I cant seem to get to the part where it detects my dload folder and installs from the UPDATE.APP file. My phone keeps auto restarting whenever I try to turn off, and since bootloader is locked, I cant flash any images. Every time I hold down Vol+, Vol-, and power button the phone just vibrates twice and goes to the blue honor boot logo. I have successfully managed to get to the Fastboot menu by holding down Vol- and power button, but this menu is useless as bootloader is locked. Is there anything I can do?
Click to expand...
Click to collapse
Hi even I have the same problem with Honor 8 Pro.. Did you get any solution??
Hi even I have the same problem with Honor 8 Did you get any solution??
Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!
Liebaart said:
Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!
Click to expand...
Click to collapse
With fastboot method, unlock bootloader again. Flash recovery. Boot into recovery. Wipe system and boot. Flash stock boot IMG and recovery IMG. Power off. Use dload. Now you are in bootloop. When booting press vol up 3 seconds, on e-recovery press shutdown. Press and hold power and vol up. Go to stock recovery, do factory reset.
Sent from my NEM-L21 using Tapatalk
Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.
Liebaart said:
Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.
Click to expand...
Click to collapse
Power off, vol up+ power can you go to recovery?
Sent from my NEM-L21 using Tapatalk
Liebaart said:
Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.
Click to expand...
Click to collapse
Post here IMEI+SN and i try to get you bootloader unlock code.
Thanks! I sent you a PM.
Anonda said:
Power off, vol up+ power can you go to recovery?
Click to expand...
Click to collapse
No, I can only get into fastboot when connected to a pc.
OK. gtdaniel was so kind to provide me with an unlock code. THANKS!
But, I don't seem te be able to use it...
I can put the phone in bootloader when connected to a pc. When I type "fastboot devices" I do get the correct serial number. But when I type "fastboot oem unlock 343...338" I get a FAILED (remote: command not allowed).
It seems this is because I never could allow OEM unlocking from the Android settings menu. But since my phone is bricked, I can not enter into that menu!
Does anybody know how to solve this??
Liebaart said:
OK. gtdaniel was so kind to provide me with an unlock code. THANKS!
But, I don't seem te be able to use it...
I can put the phone in bootloader when connected to a pc. When I type "fastboot devices" I do get the correct serial number. But when I type "fastboot oem unlock 343...338" I get a FAILED (remote: command not allowed).
It seems this is because I never could allow OEM unlocking from the Android settings menu. But since my phone is bricked, I can not enter into that menu!
Does anybody know how to solve this??
Click to expand...
Click to collapse
u can try with
VNS-L21-L22-L31 Toolkit or
SRKToolHuawei-Lod-Chong-V2.0-20161002
But i dont know is that good idea to listen to me anymore
Thanks, but the Toolkit says it can't find the device.
Liebaart said:
Thanks, but the Toolkit says it can't find the device.
Click to expand...
Click to collapse
at command line when u write adb devices u got your phone ?
Maybe is dump question but did you install adb android driver ?
I'm pretty sure that someone wrote in thread that you don't need to have this oem permission in android if you are in fastboot
dragon218 said:
at command line when u write adb devices u got your phone ?
Maybe is dump question but did you install adb android driver ?
I'm pretty sure that someone wrote in thread that you don't need to have this oem permission in android if you are in fastboot
Click to expand...
Click to collapse
OEM permission need for fastboot/unlock bootloader.
Sent from my NEM-L21 using Tapatalk
Anonda said:
OEM permission need for fastboot/unlock bootloader.
Click to expand...
Click to collapse
Yes, that's what I read too. Since I can't change that permission anymore while I can't start Android, I can't unlock. Dammit.
Is DC Unlocker my only option then? It seems their software can do it.
I'm afraid I've got some pretty bad news. Last week the same thing happened to me after I was THAT stupid to actually try and flash the rollback package for the second time. My phone got bricked just like yours, and NOTHING worked to fix it. I tried completely everything I could find on the net and XDA, and in the very end I was forced to bring it in for warranty repairs. Even they COULD NOT fix it and the phone ended up with the entire logicboard changed with a completely new one. I was lucky that it all was done under warranty. Will never do anything as stupid as that!
Really hope you find a fix somehow, but if not, the repair service is your only solution, because otherwise the phone is as good as dead.
markositoo said:
I'm afraid I've got some pretty bad news. Last week the same thing happened to me after I was THAT stupid to actually try and flash the rollback package for the second time. My phone got bricked just like yours, and NOTHING worked to fix it. I tried completely everything I could find on the net and XDA, and in the very end I was forced to bring it in for warranty repairs. Even they COULD NOT fix it and the phone ended up with the entire logicboard changed with a completely new one. I was lucky that it all was done under warranty. Will never do anything as stupid as that!
Really hope you find a fix somehow, but if not, the repair service is your only solution, because otherwise the phone is as good as dead.
Click to expand...
Click to collapse
my phone is also reedy to send to service. I have a lot of phone with android but no rom make so many damage to my phone, like this fc** rollback. finger cross, because huawei service in my country without warranty,takes for new motherboard 175 $ . I bought phone for 233 $ with 3 gb ram..... This will be harsh and pay(in)ful lesson for me.
dragon218 said:
my phone is also reedy to send to service. I have a lot of phone with android but no rom make so many damage to my phone, like this fc** rollback. finger cross, because huawei service in my country without warranty,takes for new motherboard 175 $ . I bought phone for 233 $ with 3 gb ram..... This will be harsh and pay(in)ful lesson for me.
Click to expand...
Click to collapse
Uhh, I am sorry to hear that. But yes, I had the same harsh lesson. They will be forced to changed the motherboard too, cause even they won't be able to re-flash the whole system. Though, what I did to have the warranty not declined, is I brought the phone to the service and said that - "The phone received and OTA update through the updater, I didn't look much into it and just went with it, pressed on update and everything seemed well. It worked until the moment where it installed and restarted, and now the phone is stuck on Huawei logo and you can't possibly do anything with it, not even turn it off." - and that's it. They will have to repair it under warranty because there is no proof left that you had rooted it or done any other installations not authorized by Huawei.
Best of luck!
Liebaart said:
Yes, that's what I read too. Since I can't change that permission anymore while I can't start Android, I can't unlock. Dammit.
Is DC Unlocker my only option then? It seems their software can do it.
Click to expand...
Click to collapse
I know that i read somewhere how to manage to this oem lock. I was 50 % right.
https://forum.dc-unlocker.com/forum...61751-huawei-mate-9-mha-l29-erase-frp-problem
Some user got the same problem that you have and flash boot.
But truly if u don't have "your device has been unlock" only bootloop on huawei logo, is more simple to send it back to warranty and play dump.
I have now "your device is unlock" and i pray for miracle.
Liebaart said:
Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!
Click to expand...
Click to collapse
I am exactly in the same situation with the difference that I don't have Fasboot! How do you get to Fastboot? Mine hangs on the screen that says the phone is unlocked and the device is booting... Vol+/Vol- and Power doesn't boot into Fastboot and my minimal ADB doesn't recognize the phone in the stages that it hangs...
---------- Post added 16th April 2017 at 12:04 AM ---------- Previous post was 15th April 2017 at 11:52 PM ----------
I have the same situation. I tried everything, Three button method, letting the battery run out completely, Vol+ and Power, Vol- and Power, connected to PC, not connected to PC. Every time I disconnect the charger, and reconnect it starts from 0. I read some other people here have the same problem. Send it to warranty and explain your rollback process unlocked the bootloader somehow (I mean the phone does do a lot of sh*ty sh*t, so this shouldn't seem very odd as well!!!) and hope that you get a repair/replacement and after that sell it on ebay hoping some stupid people like us in the first place will buy it and spend your money on a phone more reliable!
I managed to access the fastboot using the 3 button method in cold boot. Hold the Power key until the screen goes off and then release and hold down the Vol- key and immideately connect the usb cable to PC right before it vibrates or exactly when it vibrates (it's a matter of timing), and bingo you are in fastboot and you can flash system.img, recovery.img, cust.img, cache.img and boot.img from there, but this is not how I revived my phone. I used the 3 button method again when the phone was charged for like half an hour or so and the did the same cold boot trick and I could boot into the force upgrade environment (strangely this still didn't work whitout connecting the usb cable to PC), but it somehow didn't want to read the UPDATE.APP that I had in dload folder on my SD card and wanted to have it from my PC (I just felt it nad there was no indication of it ) so then I installed the DC Phoenix tool and payed 15 euros to be able to inject the complete UPDATE.APP to my bricked phone and the installation went well to 99% and failed, but I rebooted the phone and I could boot normally. Just to make sure I did a factory reset afterwards. Hope this helps.
Cannot get into Bootloader
Hey there!
Essentially as stupid as I am i flashed the Rollback Image at Android 6.0 too, because i wanted to get rid of C900. So now my phone is stuck in the Startup screen too. As mentioned here, I wanted to unlock bootloader again; The Button combination does not work, and if I want to start in bootloader via ADB, it just says "waiting for device"
i am really desperate and i don't know what i should do now
Thanks for the help
EDIT: Somehow managed to got it into Bootloader. At the moment i am unlocking it. Where do i get TWRP and the needed things? Please help, i'm just some noob who doesn't know how it's done
EDIT2: Solved, got Stock Recovery Re-installed, Flashed with the Force Update Method the Main Package of the Rollback (so not the temp rollback data), and worked. But Still C900 and no Google sign-in possible. Someone know how to solve?
I bricked my P8Lite when flashing the original firmware from withing TWRP.
Now I can neither boot into System, Recovery nor Fastboot. I tried all Power / Volume button combinations.
The screen stays black, the LED is flashing red, then two times green and then red again.
I disconnected the battery and reconnected it, still no progress.
Can anyone help me?
p8liteuser said:
I bricked my P8Lite when flashing the original firmware from withing TWRP.
Now I can neither boot into System, Recovery nor Fastboot. I tried all Power / Volume button combinations.
The screen stays black, the LED is flashing red, then two times green and then red again.
I disconnected the battery and reconnected it, still no progress.
Can anyone help me?
Click to expand...
Click to collapse
What version of original firmware were you using? What wipe did you make?
XTutorials said:
What version of original firmware were you using? What wipe did you make?
Click to expand...
Click to collapse
I extracted the Huawei Firmware for P8Lite (the correct one, I checked that) with Huawei Update Extractor and then installed from within TWRP.
After that I wiped TWRP asked me to wipe the cache and I did so.
p8liteuser said:
I extracted the Huawei Firmware for P8Lite (the correct one, I checked that) with Huawei Update Extractor and then installed from within TWRP.
After that I wiped TWRP asked me to wipe the cache and I did so.
Click to expand...
Click to collapse
Why did you extract the update.app from the update.zip!?!?
Of course it is bricked. I'm pretty sure you didn't edit updater-script to symlink the files not write the update.app.
I've seen this kind of brick 2-3 months ago on general or help section, search and maybe you will find something helpful.
somewhere I had the similar issue. Try this once:
Shut down your mobile
Connect your mobile (while it's turned off) to laptop while pressing the vol down key
This should boot you into fastboot mode
amageek nope, wont help. had that same kind of brick. Need to buy a new phone. Even Huawei Care cant fix it .
p8tgames said:
amageek nope, wont help. had that same kind of brick. Need to buy a new phone. Even Huawei Care cant fix it .
Click to expand...
Click to collapse
That sucks man.. Anyways, congrats on your new phone
amageek said:
That sucks man.. Anyways, congrats on your new phone
Click to expand...
Click to collapse
It isnt that bad. I take that whole thing with houmor
But, if you got that thing you can plug into the eMMC chip, you can recover it. (Dont know what its called)
As the title says. My k20 is boot looping with a black screen. The LG logo no longer shows.
I had Lineage 15.1 loaded, and thought I wound make a twrp backup using Travis' Red Wolf 64bit recovery. (Greetings, fellow Hoosier)
But, that wasn't enough for me. After the backup, I wanted to try the Nethunter Kernel. I was softbricked, so I recovered the boot partition and all was fine. But, silly me figured if nethunter didnt work for me then to try out FuseBox. After flashing that, the phone rebooted into a black screen, no logo. So, now way of knowing what stage of first boot it is in.
After some fiddling, I can get it into download mode, still black screen, I only know it's in download mode because LG Up(With Uppercut) suddenly detects it. At first, it only stayed in DL mode for for a few seconds then rebooted. Durng one of those "few seconds" boots, I manage to quickly start the LG Up Upgrade process, halting the reboot. I tried flashing MP26010j and 26010k. The flashes complete successfully then reboot, but.... still a black screen and continually reboots after about 15-30 seconds..
Tips, suggestions, ritual sacrifices?
If not for the boot looping I would think that a video driver isn't loading.
alternatively, anyone know of a comparable or close enough phone under $80 usd?
Had the same problem with bricked black screen.
i fixed mine by flashing a kdz with lgup tool
Connect it to windows make sure it doesnt keep disconnecting hold vol and power buttons different ways till is stable
flashed it like 4 times till the lg logo poped up and booted up factory mode now im back to lineage/wolf revovery. Dont give up yet
I do appreciate the motivation. I just went through the process another 10 times with the 26010j kdz, and 10 with the 26011k kdz. No luck.
radrnatn said:
Had the same problem with bricked black screen.
i fixed mine by flashing a kdz with lgup tool
Connect it to windows make sure it doesnt keep disconnecting hold vol and power buttons different ways till is stable
flashed it like 4 times till the lg logo poped up and booted up factory mode now im back to lineage/wolf revovery. Dont give up yet
Click to expand...
Click to collapse
bigbpc said:
I do appreciate the motivation. I just went through the process another 10 times with the 26010j kdz, and 10 with the 26011k kdz. No luck.
Click to expand...
Click to collapse
did you try with this and turn off real time protection https://mega.nz/#!5oxH3TwA!v7hRj5DRELer6j92X2I8zQMLxznofw37eYwZ8P_q-BM
and this kdz MP26010v_00_1214
also after i flashed it i kept playing around with removing the baterry and having different buttons pressed till the lg boot logo came on
I have the same problem, have you found a solution yet?
I have the same problem, have you found a solution yet?
I flash the stock rom m26010x and nothing
Unfortunately, no. I'm moving on and just counting it as a loss. I hope you have better luck.
EdesHD said:
I have the same problem, have you found a solution yet?
I flash the stock rom m26010x and nothing
Click to expand...
Click to collapse
bigbpc said:
alternatively, anyone know of a comparable or close enough phone under $80 usd?
Click to expand...
Click to collapse
Hey, calm down, just relax. Follow this link and you'll do just fine[dot]
lgk20[dot]com/lg-k20-plus-mp260-stock-rom-download-firmware-update-tutorial
EDIT:
Verified working 100%.
---------- Post added at 11:43 PM ---------- Previous post was at 11:32 PM ----------
THEN follow this link and onwards ya go!!
https://forum.xda-developers.com/lg...ecoveryroot-twrp-3-2-1-0-lg-k20-plus-t3727936