Hello guys,
I've recently got my hands on a not-working P20 Lite, which was stuck on boot with the well-known "your device has failed verification and may not work properly" error message. Since I got stuck on a HUAWEI logo when trying to enter the recovery, ended up in a bootloop trying to enter the download mode, the only way to get the phone working was fastboot. And since I am writing this post, yeah, y'all guessing correctly, it has not been successful. (Error message 'Command not allowed')
After giving up on it and leaving it stuck on the HUAWEI logo for a while, I have noticed that it has turned off. After turning on the device, it shows a green screen with 2, red and blue squares (see attached image), still not being able to boot in recovery mode, however fastboot still somehow manages to fire up.
Any suggestions? Is this phone dead (which I honestly believe), or is there something that would possibly be able to change its state?
Thanks!
EnterPaulini said:
your device has failed verification and may not work properly"
Click to expand...
Click to collapse
EnterPaulini said:
it shows a green screen with 2, red and blue squares
Click to expand...
Click to collapse
Wrong region (oeminfo).
EnterPaulini said:
Is this phone dead?
Click to expand...
Click to collapse
No, not dead yet
Need more information about your phone . Install on your PC "Minimal ADB and fastboot" tool .
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
fastboot oem battery_present_check
and post the results please.
(First try to charge the phone).
(bootloader) :ANE-LX1 9.1.0.372(C432E7R1P7)
(bootloader) ANE-LX1
vendorcountry: hw/eu
(bootloader) :ANE-LX1-CUST 9.1.0.7(C432)
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
(bootloader) 3426mv
Thanks!
Okay, try this way out...
1. in fastboot mode run command
fastboot erase userdata
and try restart the device.
2. download and use a Service ROM
https://androidhost.ru/2AVi
with an sd/card or an USB-OTG flashdrive in dload mode. Unpack .zip archive , find dload file in "Software" folder, and simply transfer it to the SD card, without unpacking it! (instruction can be found in ReleaseDoc folder).
Turn off your phone and flash FW using three button combo .(Power+Vol.Up+VolDown).
-Alf- said:
Okay, try this way out...
Click to expand...
Click to collapse
Still hanging in there! Entering the dload mode does not work, I always land on the same green screen and it shuts down.
EDIT:
Back to the "Your device has failed verification and may not work properly" screen. It actually shows the HUAWEI logo again and shows that the device is charging, when turned off. Trying to enter the dload mode results in a bootloop.
EDIT2:
After few times of trying to enter the dload mode I am stuck with the green screen again. From what I have observed, the green screen does not come up when I am connected with the USB cable. When not, everything except fastboot leads to the green screen with a small LED diode blinking red (not so familiar with this phone, no idea what's this for, it's located on the notch). On the other hand, everything except fastboot with cable connected leads to a bootloop. But at least I can see the HUAWEI logo, eh?
Paid service
But if it's a hardware problem (e.g. dead memory), it won't help you.
-Alf- said:
Paid service
But if it's a hardware problem (e.g. dead memory), it won't help you.
Click to expand...
Click to collapse
And if I tried this solution @kikson112 suggested? Doing something with that test point, could this end up working?
I can't help you, that's Greek to me... I have never used this method, nor dc-phoenix (thank goodness).
This happened to my ANE-LX1 a while ago, bootloader never unlocked and device was fully stock...
Device was still under warranty and huawei repaired it for free
Probably a hardware issue
Hey! I have the same problem now. From todays morning it has been stuck on the loading Huawei logo. I haven't got any messages about that warning, you have got, but I have tried to enter the recovery mode and sometimes, it just flashes that green screen with the two squares. Now I think is without power. Have you somehow started the phone?
AmaliaRepova said:
Hey! I have the same problem now. From todays morning it has been stuck on the loading Huawei logo. I haven't got any messages about that warning, you have got, but I have tried to enter the recovery mode and sometimes, it just flashes that green screen with the two squares. Now I think is without power. Have you somehow started the phone?
Click to expand...
Click to collapse
Hello,
some related links:
https://forum.xda-developers.com/t/...-blue-red-flag-fastboot.4339931/post-85697163
Related
Hello xperia community.
I am facing a problem with unlocking the boot loader of my ZU and fastboot. On my mac, I downloaded the art bundle and unzipped it. In the unzipped folder, i headed to sdk>platform-tools and then I dragged the fastboot app into my terminal. Now I was in fast boot. So I typed:
Last login: Sat Nov 15 11:16:44 on ttys000
Adrians-MacBook-Air-2:~ adrian$ /Users/adrian/Downloads/adt-bundle-mac-x86_64-20140702/sdk/platform-tools/fastboot fastboot devices
< waiting for device >
ERROR: Unable to create a plug-in (e00002be)
and then I tried it with sudo
Last login: Sat Nov 15 11:08:24 on ttys000
Adrians-MacBook-Air-2:~ adrian$ /Users/adrian/Downloads/adt-bundle-mac-x86_64-20140702/sdk/platform-tools/fastboot sudo fastboot devices
< waiting for device >
ERROR: Unable to create a plug-in (e00002be)
still the same error
I also noticed that I dont get a purple light with my volume up, Androxydes Flashtool always recognizes my phone in Flash Mode?
------
Please Help
------
*edit: tried it with restart, unplug etc. , still nothing... / in service menue, footlocker unlock is allowed
Okay, so you've tried the most basic thing like holding VOL UP when you connect your Ultra to your Mac? Does the LED turn blue? If yes, you're in fastboot mode.
Skip the whole Mac thing and borrow a Windows computer and use that instead. Stuff will work better there.
It didnt turn blue up and down key both green for just a sec and then no light
cippus said:
It didnt turn blue up and down key both green for just a sec and then no light
Click to expand...
Click to collapse
I don't know a thing about mac os but this may be worth a look.
http://forum.xda-developers.com/showthread.php?t=2564453
Here is another one that you can try also.
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
So I basically just need my fastboot back...
I think my access to THW fastboot is broken.
Is there a way, the bootloader or the thing which controls the fb, to reset it?
cippus said:
So I basically just need my fastboot back...
I think my access to THW fastboot is broken.
Is there a way, the bootloader or the thing which controls the fb, to reset it?
Click to expand...
Click to collapse
You say you need your fastboot "back" but has it ever worked before? Did you try either of the methods to install adb and fastboot that I linked?
Yeah i tried it with the Sony tutorial.... It didnt work
Hi
I used my Xiaomi Redmi Note 3, 3GB RAM, 32GB new phone first day yesterday.
When I went to sleep it was 92% charged and when I woke up it was stuck on the Xiaomi loading screen. I let it on that screen for about 3 hours before I restarted it.
It's unable to boot into normal mode, and when I try to get into recovery mode it just shows a screen to connect a cable.
When I connect the cable to the computer it shows that the cable is connected but nothing happens after this.
If I boot the phone in fastboot and use Mi PC Suite to try to flash it, it just tells me to reboot in normal mode and try again.
If I hold all 3 buttons I have managed to get into some test mode, but from there I can't do anything.
How can I reset or get into my phone again? Is this normal behaviour after just one day use?
Johanna12221 said:
Hi
I used my Xiaomi Redmi Note 3, 3GB RAM, 32GB new phone first day yesterday.
When I went to sleep it was 92% charged and when I woke up it was stuck on the Xiaomi loading screen. I let it on that screen for about 3 hours before I restarted it.
It's unable to boot into normal mode, and when I try to get into recovery mode it just shows a screen to connect a cable.
When I connect the cable to the computer it shows that the cable is connected but nothing happens after this.
If I boot the phone in fastboot and use Mi PC Suite to try to flash it, it just tells me to reboot in normal mode and try again.
If I hold all 3 buttons I have managed to get into some test mode, but from there I can't do anything.
How can I reset or get into my phone again? Is this normal behaviour after just one day use?
Click to expand...
Click to collapse
Flash aboot it will ok..
Hi and thanks for your reply!
By running fastboot getvar product I found out that I have the "special edition" model, kate.
I have now downloaded this:
kate_global_images_6.9.8_20160805.0000.29_6.0_global_042c784ac4
After unpacking and trying to flash I get this:
Code:
fastboot flash tz C:\kate\kate\images\tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (637 KB)...
OKAY [ 0.023s]
writing 'tz'...
FAILED [B](remote: Critical partition flashing is not allowed)[/B]
finished. total time: 0.032s
"Flash tz error"
Johanna12221 said:
Hi and thanks for your reply!
By running fastboot getvar product I found out that I have the "special edition" model, kate.
I have now downloaded this:
kate_global_images_6.9.8_20160805.0000.29_6.0_global_042c784ac4
After unpacking and trying to flash I get this:
Code:
fastboot flash tz C:\kate\kate\images\tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (637 KB)...
OKAY [ 0.023s]
writing 'tz'...
FAILED [B](remote: Critical partition flashing is not allowed)[/B]
finished. total time: 0.032s
"Flash tz error"
Click to expand...
Click to collapse
By looks of it, you have a locked bootloader and hence, are unable to flash fastboot files. The only way for you to make your device usable again is to somehow boot into the 'edl' mode and use MiFlash to falsh the fastboot ROM from there.
Hi! Thanks for your reply.
I didn't do anything to the bootloader, so yeah it should be locked.
I will contact the store I bought it from and try to get it returned.
So sad to have made this purchase. I hope I can find another phone, perhaps one that is not as cheap as this.
Hi again!
I have kept trying to solve this issue further. I'm able to get into edl mode using the modified fastboot that I found here on the forums with "fastboot reboot-edl".
I managed to run MiFlash 2016.04.01 (important, newer version didn't work!)
But it still seems to be stuck in just an endless Android loading screen. Anything else I can try?
Johanna12221 said:
Hi again!
I have kept trying to solve this issue further. I'm able to get into edl mode using the modified fastboot that I found here on the forums with "fastboot reboot-edl".
I managed to run MiFlash 2016.04.01 (important, newer version didn't work!)
But it still seems to be stuck in just an endless Android loading screen. Anything else I can try?
Click to expand...
Click to collapse
I can help you. Talk me in PM.
Hi!
Thanks for offering your help, andersonaragao.
I finally got it to work by doing a "Flash all" of the MIUI 8 package.
So the steps so solve was just this easy:
Boot in fastboot (Volume down + power)
Make sure you have kenzo or kate (fastboot getvar product)
Get correct fastboot rom, depending on kenzo/kate: (http://en.miui.com/a-234.html)
Boot in edl (Fastboot_edl-v2: fastboot reboot-edl)
MiFlash 2016.04.01 (Flash all)
When i was updating the twrp i managed to hard brick my phone, it just shows the 1+ logo and "powered by android" when turned on. if i hold the power button and volume up it shows the cyanogenmod logo and "fastboot mod" and stays there. If i hold power button and volume down it just shows the 1+ logo without the "powered by android".
i followed this guide https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
completed all the steps but the installed program cant recognise my phone when i plug it in.
When its in fastboot mode logo i can see it in device manager under portable devices listed as "ONE E1001" (it has a yellow ! triangle next to it)
When i try to turn the recovery (powerbutton+volume down) where it shows just the 1+ logo with no "powered by android" i can see it in the device manager under android phone as "Android Bootloader Interface"
When i just turn it on where it does display "powered by android" i can see it same as in fastboot mode, as "ONE E1001" under portable devices, (a yellow ! triangle appears after some time too)
i tried a similar guide here: https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
did everything, i have like 5 driver now from all the guides, i think all of them work, i just cant manage to get the programs to realize when the phone is pluged in. Is it possible that something is still wrong with the drivers?
pls help );
PlsHelpMeee said:
When i was updating the twrp i managed to hard brick my phone, it just shows the 1+ logo and "powered by android" when turned on. if i hold the power button and volume up it shows the cyanogenmod logo and "fastboot mod" and stays there. If i hold power button and volume down it just shows the 1+ logo without the "powered by android".
i followed this guide https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Click to expand...
Click to collapse
You're talking about Cyanogenmod logo. What was on your phone before? What did you do exactly?
Are you sure you know how to use Fastboot?
"fastboot oem device-info" output?
And then explain precisely at what step you have error.
Kéno40 said:
You're talking about Cyanogenmod logo. What was on your phone before? What did you do exactly?
Are you sure you know how to use Fastboot?
"fastboot oem device-info" output?
And then explain precisely at what step you have error.
Click to expand...
Click to collapse
i had CM12 before i tried to upgrade, i managed to go through the entire first guide now, the CM logo isn't appearing anymore, now its the 1+ logo and below it "fastboot mode" the drivers were a problem after all
now im stuck at the new recovery that is installed and cant install the ROM from it, even my old one that i had before all of this (CM12) that i have on my sd card.
OK, so you flash something incompatible.
After CM13 or so, the bootloader have to be upgraded and then you have to use a version compatible with it.
First look with fastboot command I give if BL still unlocked.
Do you know how to use fastboot commands?
Kéno40 said:
OK, so you flash something incompatible.
After CM13 or so, the bootloader have to be upgraded and then you have to use a version compatible with it.
First look with fastboot command I give if BL still unlocked.
Do you know how to use fastboot commands?
Click to expand...
Click to collapse
kind of, "fastboot oem device-info" output is
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.010s]
finished. total time: 0.011s
if i could install the twrp from here i could install the ROM too i think, is there a guide to do so while stuck like this?
"fastboot oem unlock" gives me
FAILED (remote: oem unlock is disabled)
finished. total time: 0.009s
i cant use adb commands, in the command prompt my computer doesent even see the device when i type "adb devices", i think its because oem, debuging, isnt turned on but i cant turn it on if i cant install a ROM and check it "on" in the settings of the androis OS.
all i can use are fastboot comands since my computer can see it as a fastboot device while not as a adb device. i have a bricked phone with a locked bootloader i think.
BL is locked so only solution is mega unbrick guide.
I never tried but oos 3.1.4 won't flash either...
Kéno40 said:
BL is locked so only solution is mega unbrick guide.
I never tried but oos 3.1.4 won't flash either...
Click to expand...
Click to collapse
i did the mega unbricked guide, this one ==> https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
i have the recovery dom the guide installed but it cant install any ROMs or the twrp, im trying to install them over fastboot but it also cant be done because my device is locked and i cant flash anything remotely. I also cant use adb for some reason because the command prompt cant see my phone under "adb devices". is there anything i can install with that recovery? i just stuck, spent so much time and still nothing :crying:
i think adb devices dont show because usb debugging is not turned on, i dont know how it can be turned on without and actual operating system on the phone..
THis guide push you back with OnePlus recovery and OOS.
That's not what you have?
You did something wrong...
At which step does it stop?
A few day ago, one of the file ws missing. Do you have it all?
---------- Post added at 10:43 PM ---------- Previous post was at 10:43 PM ----------
THis guide push you back with OnePlus recovery and OOS.
That's not what you have?
You did something wrong...
At which step does it stop?
A few day ago, one of the file ws missing. Do you have it all?
Kéno40 said:
THis guide push you back with OnePlus recovery and OOS.
That's not what you have?
You did something wrong...
At which step does it stop?
A few day ago, one of the file ws missing. Do you have it all?
---------- Post added at 10:43 PM ---------- Previous post was at 10:43 PM ----------
THis guide push you back with OnePlus recovery and OOS.
That's not what you have?
You did something wrong...
At which step does it stop?
A few day ago, one of the file ws missing. Do you have it all?
Click to expand...
Click to collapse
i did all the steps, all of them work, when the program finished downloading/instaling things on my phone it turned on my phone and it was tuck at the 1+ logo again. when i held the power button+volume down it went to the custom recovery that was installed from the program from the guide. that recovery cant do anything i tried to install a new ROM even the twrp but it always says it failed.
i thought the guide was suposed to install a operating system too but it didnt. now i only have the OnePlus recovery (from the guide) and nothing else. When i try to just turn on the phone (just the power button) its stuck in the 1+ logo. power button+volume up gets the 1+ logo and "fastboot mode" below it
the original recovery tool link doesent work so i downloaded the mini version he posted in the comments, this one ==> https://www.androidfilehost.com/?fid=24269982087019810
maby the OS didnt come with it???
PlsHelpMeee said:
i did all the steps, all of them work, when the program finished downloading/instaling things on my phone it turned on my phone and it was tuck at the 1+ logo again. when i held the power button+volume down it went to the custom recovery that was installed from the program from the guide. that recovery cant do anything i tried to install a new ROM even the twrp but it always says it failed.
i thought the guide was suposed to install a operating system too but it didnt. now i only have the OnePlus recovery (from the guide) and nothing else. When i try to just turn on the phone (just the power button) its stuck in the 1+ logo. power button+volume up gets the 1+ logo and "fastboot mode" below it
the original recovery tool link doesent work so i downloaded the mini version he posted in the comments, this one ==> https://www.androidfilehost.com/?fid=24269982087019810
maby the OS didnt come with it???
Click to expand...
Click to collapse
You have to use the other. This mini tool is from dec 2015.
At last you should have OnePlus recovery + OOS.
Can you retry on an older computer (easier on win 7).
See if it works. At the end, try to fahs the OOS 3.1.4 zip from here :
http://downloads.oneplus.net/oneplus-x/oneplus_x_oxygenos_3.1.4/
Kéno40 said:
You have to use the other. This mini tool is from dec 2015.
At last you should have OnePlus recovery + OOS.
Can you retry on an older computer (easier on win 7).
See if it works. At the end, try to fahs the OOS 3.1.4 zip from here :
http://downloads.oneplus.net/oneplus-x/oneplus_x_oxygenos_3.1.4/
Click to expand...
Click to collapse
I downloaded the oxygen OS form the link, i managed to install it with the 1+ recovery. Everything is working now, thank you for everything!!
Cool if you have done it !
Now unlock bootloader, flash new TWRP and you're good to go to flash all recents customs roms.
My top 3 : Candy 7 // Sultan's LOS // OmniROM
PlsHelpMeee said:
I downloaded the oxygen OS form the link, i managed to install it with the 1+ recovery. Everything is working now, thank you for everything!!
Click to expand...
Click to collapse
Hi, thank you for the information, you made my day! I confirm only the official rom can be flashed. Then I could unlock oem / bootloader and install lineageos on my oneplus x.
Hello everyone,
I ran into this problem while trying to solve another.
The current state of my phone (h850):
On booting, I receive this message: "Your device is corrupt. It cannot be trusted and will not boot."
Fastboot is still accessible.
Download mode is not: holding the volume up button and connecting a USB cable presents me with the above message.
I can still access the "Factory data reset" dialog, but after selecting "Yes" twice it takes me to the above message.
[edit]:
fastboot getvar unlocked
unlocked: no
I tried unlocking the phone again using fastboot flash unlock:
Code:
fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.040s]
writing 'unlock'...
(bootloader) Error!!
(bootloader) Bootloader Unlock key write fail
FAILED (remote failure)
finished. total time: 0.080s
... so that sucks.
Any way to recover from this?
How the hell did I get here?
I had TWRP and LineageOS 14.1 installed. Lineage released a new update which I tried to install from the OTA-Update list. After rebooting, I ended up in TWRP, which did... nothing. So I tried rebooting, only to end up in TWRP again; there appeared to be no escape. Finally, I came across an answer on reddit (I'm not allowed to post outside links... it's on the LineageOS subreddit, post ID is 61nxs6):
for g5 the command are these:
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/fota
Click to expand...
Click to collapse
I tried those, and that's how I got here.
Try reflashing twrp.img in fast boot (see Autoprime's AIO post for instructions) then try booting into twrp - then at least you can wipe and flash a new stock/custom rom!
Best of luck!
megatron_lives said:
Try reflashing twrp.img in fast boot (see Autoprime's AIO post for instructions) then try booting into twrp - then at least you can wipe and flash a new stock/custom rom!
Best of luck!
Click to expand...
Click to collapse
Thanks for the reply!
Reflashing TWRP doesn't work as the device is somehow locked again:
Code:
fastboot flash recovery twrp-3.1.1-0-h850.img
target reported max download size of 536870912 bytes
sending 'recovery' (19076 KB)...
OKAY [ 0.471s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.490s
Unlocking fails as mentioned in my fist post.
did you try flashing stock kdz file with lgup? if it boots you can later try unlocking.
ozkaya said:
did you try flashing stock kdz file with lgup? if it boots you can later try unlocking.
Click to expand...
Click to collapse
It's my understanding that LGUP requires "download mode" to be active (which I cannot access, see first post). In any event, any mode that I can still reach (error message, factory reset, fastboot) does not cause the device to be visible to LGUP, even using Uppercut.
gqo said:
It's my understanding that LGUP requires "download mode" to be active (which I cannot access, see first post). In any event, any mode that I can still reach (error message, factory reset, fastboot) does not cause the device to be visible to LGUP, even using Uppercut.
Click to expand...
Click to collapse
good point. how about if you try fastboot flash recovery twrp.img or if it fails flash stockrecovery.img?
---------- Post added at 06:11 PM ---------- Previous post was at 06:08 PM ----------
gqo said:
It's my understanding that LGUP requires "download mode" to be active (which I cannot access, see first post). In any event, any mode that I can still reach (error message, factory reset, fastboot) does not cause the device to be visible to LGUP, even using Uppercut.
Click to expand...
Click to collapse
if flashing recoveries fail, try fastboot flash bootloader stockbootloader.img (you can find these images from stock zip format in the forum)
Thanks everyone for the help! Just to be thorough, I tried entering download mode for what felt like the 42nd time, and whaddaya know, it worked! So I'm currently in the process of returning to the point I was on before I tried that ill-fated update of LineageOS. Thanks again everyone!
gqo said:
Thanks everyone for the help! Just to be thorough, I tried entering download mode for what felt like the 42nd time, and whaddaya know, it worked! So I'm currently in the process of returning to the point I was on before I tried that ill-fated update of LineageOS. Thanks again everyone!
Click to expand...
Click to collapse
what exactly have you done? i have the same problem
trinity_user said:
what exactly have you done? i have the same problem
Click to expand...
Click to collapse
To enter download mode:
Turned phone off by removing the battery
Reinserted the battery without the USB cable plugged in
Pressed volume up and kept it pressed
Reinserted the USB cable while still keeping volume up button pressed
(As I mentioned, this didn't work the first few times around and I don't know why. Apparently, persistence paid off.)
To reflash the stock ROM:
Google-searched for this phrase: lg firmware h850
Note: I'm not yet allowed to post links. Your results may vary. There was a result at a domain which includes the words "lg" and "firmwares". That one I chose. Hope that's vague enough.
Also note that there are other sources of this image, I'm sure I've seen something here on the forums.
Downloaded the image H85020i_00_OPEN_EU_OP_0628.kdz (I had trouble with an image version that was less than 20i (10c I believe). Again, your mileage may vary.)
Booted into Windows because (sigh) LGUP, which is used to flash the above image onto the device, is only available for Windows
Acquired UPPERCUT along with the correct version of LGUP and the latest drivers
Started UPPERCUT which in turn started LGUP
Note: this will only work with your device connected and in download mode.
Selected the image mentioned above (click the File path column of the BIN file row if I remember correctly), selected upgrade, started and waited
Had a cup of tea to calm me down after a day's work of messing with my phone
After the phone rebooted, I reset it to factory settings
(you may run into an issue here with a password that you're supposed to enter, don't remember what I did there but as far as I understand it entering it wrong enough times will factory reset your phone as well)
[Optional stuff from here on out I guess]
Unlocked the phone again (fastboot flash unlock unlock.bin)
Flashed TWRP again
Installed LineageOS again
Hope that helps, good luck with your phone!
gqo said:
To enter download mode:
Turned phone off by removing the battery
Reinserted the battery without the USB cable plugged in
Pressed volume up and kept it pressed
Reinserted the USB cable while still keeping volume up button pressed
(As I mentioned, this didn't work the first few times around and I don't know why. Apparently, persistence paid off.)
To reflash the stock ROM:
Google-searched for this phrase: lg firmware h850
Note: I'm not yet allowed to post links. Your results may vary. There was a result at a domain which includes the words "lg" and "firmwares". That one I chose. Hope that's vague enough.
Also note that there are other sources of this image, I'm sure I've seen something here on the forums.
Downloaded the image H85020i_00_OPEN_EU_OP_0628.kdz (I had trouble with an image version that was less than 20i (10c I believe). Again, your mileage may vary.)
Booted into Windows because (sigh) LGUP, which is used to flash the above image onto the device, is only available for Windows
Acquired UPPERCUT along with the correct version of LGUP and the latest drivers
Started UPPERCUT which in turn started LGUP
Note: this will only work with your device connected and in download mode.
Selected the image mentioned above (click the File path column of the BIN file row if I remember correctly), selected upgrade, started and waited
Had a cup of tea to calm me down after a day's work of messing with my phone
After the phone rebooted, I reset it to factory settings
(you may run into an issue here with a password that you're supposed to enter, don't remember what I did there but as far as I understand it entering it wrong enough times will factory reset your phone as well)
[Optional stuff from here on out I guess]
Unlocked the phone again (fastboot flash unlock unlock.bin)
Flashed TWRP again
Installed LineageOS again
Hope that helps, good luck with your phone!
Click to expand...
Click to collapse
did u lost ur imei?
Zer0_rulz said:
did u lost ur imei?
Click to expand...
Click to collapse
Not sure what you mean. If you're wondering whether I lost that piece of information: no, it's printed on a sticker on the back of my phone. In general there's usually a sticker with your phone's IMEI somewhere on the packaging or, like in my case, on the device itself.
gqo said:
Hello everyone,
I ran into this problem while trying to solve another.
The current state of my phone (h850):
On booting, I receive this message: "Your device is corrupt. It cannot be trusted and will not boot."
Fastboot is still accessible.
Download mode is not: holding the volume up button and connecting a USB cable presents me with the above message.
I can still access the "Factory data reset" dialog, but after selecting "Yes" twice it takes me to the above message.
[edit]:
fastboot getvar unlocked
unlocked: no
I tried unlocking the phone again using fastboot flash unlock:
Code:
fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.040s]
writing 'unlock'...
(bootloader) Error!!
(bootloader) Bootloader Unlock key write fail
FAILED (remote failure)
finished. total time: 0.080s
... so that sucks.
Any way to recover from this?
How the hell did I get here?
I had TWRP and LineageOS 14.1 installed. Lineage released a new update which I tried to install from the OTA-Update list. After rebooting, I ended up in TWRP, which did... nothing. So I tried rebooting, only to end up in TWRP again; there appeared to be no escape. Finally, I came across an answer on reddit (I'm not allowed to post outside links... it's on the LineageOS subreddit, post ID is 61nxs6):
I tried those, and that's how I got here.
Click to expand...
Click to collapse
Wow... It's uncanny how close this is to the my own situation, except that in my case it's a G6 (US997).
gqo said:
To enter download mode:
Turned phone off by removing the battery
Reinserted the battery without the USB cable plugged in
Pressed volume up and kept it pressed
Reinserted the USB cable while still keeping volume up button pressed
(As I mentioned, this didn't work the first few times around and I don't know why. Apparently, persistence paid off.)
To reflash the stock ROM:
Google-searched for this phrase: lg firmware h850
Note: I'm not yet allowed to post links. Your results may vary. There was a result at a domain which includes the words "lg" and "firmwares". That one I chose. Hope that's vague enough.
Also note that there are other sources of this image, I'm sure I've seen something here on the forums.
Downloaded the image H85020i_00_OPEN_EU_OP_0628.kdz (I had trouble with an image version that was less than 20i (10c I believe). Again, your mileage may vary.)
Booted into Windows because (sigh) LGUP, which is used to flash the above image onto the device, is only available for Windows
Acquired UPPERCUT along with the correct version of LGUP and the latest drivers
Started UPPERCUT which in turn started LGUP
Note: this will only work with your device connected and in download mode.
Selected the image mentioned above (click the File path column of the BIN file row if I remember correctly), selected upgrade, started and waited
Had a cup of tea to calm me down after a day's work of messing with my phone
After the phone rebooted, I reset it to factory settings
(you may run into an issue here with a password that you're supposed to enter, don't remember what I did there but as far as I understand it entering it wrong enough times will factory reset your phone as well)
[Optional stuff from here on out I guess]
Unlocked the phone again (fastboot flash unlock unlock.bin)
Flashed TWRP again
Installed LineageOS again
Hope that helps, good luck with your phone!
Click to expand...
Click to collapse
Again I did the same, bar the tea, but unfortunately my tale does not end quite so happily... Not yet at least. I can "upgrade" with literally no problems using LGUP and one of the few G6 KDZs available, but when it's time reboot my phone always boots into the fastboot for bootloader unlock mode. I can use fastboot commands but my bootloader relocked at some point and I'm still not able to unlock it again. No matter what I do my phone always boots to fastboot... Except when I do the recovery key combination and press "Yes" twice, in this case there's a brief "erasing" animation and then I'm back to fastboot.
I realize I'm using a different device, but would anyone happen to have any thoughts on this? This is my first time using a non-Nexus LG and I must admit I'm struggling a bit to get out of this mess. The recovery and fastboot modes also look quite bare to me, but I might just be using the wrong.
Cheers!
gqo said:
To enter download mode:
Turned phone off by removing the battery
Reinserted the battery without the USB cable plugged in
Pressed volume up and kept it pressed
Reinserted the USB cable while still keeping volume up button pressed
(As I mentioned, this didn't work the first few times around and I don't know why. Apparently, persistence paid off.)
To reflash the stock ROM:
Google-searched for this phrase: lg firmware h850
Note: I'm not yet allowed to post links. Your results may vary. There was a result at a domain which includes the words "lg" and "firmwares". That one I chose. Hope that's vague enough.
Also note that there are other sources of this image, I'm sure I've seen something here on the forums.
Downloaded the image H85020i_00_OPEN_EU_OP_0628.kdz (I had trouble with an image version that was less than 20i (10c I believe). Again, your mileage may vary.)
Booted into Windows because (sigh) LGUP, which is used to flash the above image onto the device, is only available for Windows
Acquired UPPERCUT along with the correct version of LGUP and the latest drivers
Started UPPERCUT which in turn started LGUP
Note: this will only work with your device connected and in download mode.
Selected the image mentioned above (click the File path column of the BIN file row if I remember correctly), selected upgrade, started and waited
Had a cup of tea to calm me down after a day's work of messing with my phone
After the phone rebooted, I reset it to factory settings
(you may run into an issue here with a password that you're supposed to enter, don't remember what I did there but as far as I understand it entering it wrong enough times will factory reset your phone as well)
[Optional stuff from here on out I guess]
Unlocked the phone again (fastboot flash unlock unlock.bin)
Flashed TWRP again
Installed LineageOS again
Hope that helps, good luck with your phone!
Click to expand...
Click to collapse
Thank you for your detailed guide, but it didnt work for me yet. I tried maybe 100 times. Everytime the same Message "Your device is corrupted".
You are a life saver
Thank you for detailed tutorial.
My H850, which I managed to almost dead brick, like yours (of course from the same source - reddit ) after few minutes with uppercut + lgup ressurected with all the files and apps inside
So, after that I'm running through factory reset now and trying to unlock once again.
Thank you
Have the same problem but......
gqo said:
Hello everyone,
I ran into this problem while trying to solve another.
The current state of my phone (h850):
On booting, I receive this message: "Your device is corrupt. It cannot be trusted and will not boot."
Fastboot is still accessible.
Download mode is not: holding the volume up button and connecting a USB cable presents me with the above message.
I can still access the "Factory data reset" dialog, but after selecting "Yes" twice it takes me to the above message.
[edit]:
fastboot getvar unlocked
unlocked: no
I tried unlocking the phone again using fastboot flash unlock:
Code:
fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.040s]
writing 'unlock'...
(bootloader) Error!!
(bootloader) Bootloader Unlock key write fail
FAILED (remote failure)
finished. total time: 0.080s
... so that sucks.
Any way to recover from this?
How the hell did I get here?
I had TWRP and LineageOS 14.1 installed. Lineage released a new update which I tried to install from the OTA-Update list. After rebooting, I ended up in TWRP, which did... nothing. So I tried rebooting, only to end up in TWRP again; there appeared to be no escape. Finally, I came across an answer on reddit (I'm not allowed to post outside links... it's on the LineageOS subreddit, post ID is 61nxs6):
I tried those, and that's how I got here.
Click to expand...
Click to collapse
i have the same problem but i can still use the phone, how can i delete this error?
the boot loader it s not working.......PLEASE HEEEELP
gqo said:
To enter download mode:
Turned phone off by removing the battery
Reinserted the battery without the USB cable plugged in
Pressed volume up and kept it pressed
Reinserted the USB cable while still keeping volume up button pressed
(As I mentioned, this didn't work the first few times around and I don't know why. Apparently, persistence paid off.)
To reflash the stock ROM:
Google-searched for this phrase: lg firmware h850
Note: I'm not yet allowed to post links. Your results may vary. There was a result at a domain which includes the words "lg" and "firmwares". That one I chose. Hope that's vague enough.
Also note that there are other sources of this image, I'm sure I've seen something here on the forums.
Downloaded the image H85020i_00_OPEN_EU_OP_0628.kdz (I had trouble with an image version that was less than 20i (10c I believe). Again, your mileage may vary.)
Booted into Windows because (sigh) LGUP, which is used to flash the above image onto the device, is only available for Windows
Acquired UPPERCUT along with the correct version of LGUP and the latest drivers
Started UPPERCUT which in turn started LGUP
Note: this will only work with your device connected and in download mode.
Selected the image mentioned above (click the File path column of the BIN file row if I remember correctly), selected upgrade, started and waited
Had a cup of tea to calm me down after a day's work of messing with my phone
After the phone rebooted, I reset it to factory settings
(you may run into an issue here with a password that you're supposed to enter, don't remember what I did there but as far as I understand it entering it wrong enough times will factory reset your phone as well)
[Optional stuff from here on out I guess]
Unlocked the phone again (fastboot flash unlock unlock.bin)
Flashed TWRP again
Installed LineageOS again
Hope that helps, good luck with your phone!
Click to expand...
Click to collapse
I tried this, but my pc (and so LGUP) doesn't recognize my lg g5 (drivers are installed)... I don't know what to do.. please help me!!!
Use uppercut
Hello. I have the same problem. I was on LOS 15.1, then i deviced to go back on stock. I relocked the bootloader and i have this messege. When i go to download mode, lgup recognize the phone, but after 10 seconds the phone reboot and go to that screen again. Any suggestions?
volen said:
You are a life saver
Thank you for detailed tutorial.
My H850, which I managed to almost dead brick, like yours (of course from the same source - reddit ) after few minutes with uppercut + lgup ressurected with all the files and apps inside
So, after that I'm running through factory reset now and trying to unlock once again.
Thank you
Click to expand...
Click to collapse
I've got this problem also, thanks to those lines put into 'terminal'.
I can get into download mode easily, however by the time I then open Uppercut and try doing anything the phone reboots itself back into the 'corrupt' screen and keeps looping on that.
mgolder said:
I've got this problem also, thanks to those lines put into 'terminal'.
I can get into download mode easily, however by the time I then open Uppercut and try doing anything the phone reboots itself back into the 'corrupt' screen and keeps looping on that.
Click to expand...
Click to collapse
Maybe unlock.bin is corrupted, try ask LG to resend the file.
Still very new to the community, so please bear with me if I miss something or make any mistakes.
Trying to flash havocOS
I flashed an unofficial version of twrp (for X657, made sure to disable verity on both vbmeta and vbmeta_system), then attempted to boot into twrp, with no luck (it just ended up booting into fastboot for some reason).
I then tried to boot into fastbootd, completely forgetting i had twrp still installed, to flash havoc from there (this is where i think i messed up, i remember reading somewhere that twrp prevents this)
Now my phone is stuck looping on the infinix logo
Tried the SP Flash Tool, but kept getting this error. Which I'm guessing is because the phone keeps restarting (mainly because "Disconnected!" shows up in the console between two instances of the same error).
Any advice?
UnequalB said:
Still very new to the community, so please bear with me if I miss something or make any mistakes.
Trying to flash havocOS
I flashed an unofficial version of twrp (for X657, made sure to disable verity on both vbmeta and vbmeta_system), then attempted to boot into twrp, with no luck (it just ended up booting into fastboot for some reason).
Click to expand...
Click to collapse
Probably you haven´t to flash vbmeta to boot to TWRP but just when you are ready to boot to system.
UnequalB said:
I then tried to boot into fastbootd, completely forgetting i had twrp still installed, to flash havoc from there (this is where i think i messed up, i remember reading somewhere that twrp prevents this)
Click to expand...
Click to collapse
You can flash the TWRP image through fastboot and then boot to it through commands.
UnequalB said:
Now my phone is stuck looping on the infinix logo
Tried the SP Flash Tool, but kept getting this error. Which I'm guessing is because the phone keeps restarting (mainly because "Disconnected!" shows up in the console between two instances of the same error).
Any advice?
Click to expand...
Click to collapse
This is the list of errors from SP Flash tool https://forum.hovatek.com/thread-439.html
Anyway, you have a tool specific for your device https://forum.hovatek.com/thread-9224.html
I guess this thread must be moved to Android General Questions.
SubwayChamp said:
Probably you haven´t to flash vbmeta to boot to TWRP but just when you are ready to boot to system.
You can flash the TWRP image through fastboot and then boot to it through commands.
Click to expand...
Click to collapse
I meant twrp prevents booting to fastbootd, it was after trying to boot into fastbootd using "fastboot reboot fastboot" that the bootloop started, right now I can't seem to get past the boot logo.
SubwayChamp said:
This is the list of errors from SP Flash tool https://forum.hovatek.com/thread-439.html
Click to expand...
Click to collapse
Weirdly enough the error i got was not listed here..
SubwayChamp said:
Anyway, you have a tool specific for your device https://forum.hovatek.com/thread-9224.html
I guess this thread must be moved to Android General Questions.
Click to expand...
Click to collapse
This method doesn't work either since the phone won't stay off for more than 7 seconds.
I'm not stuck in a bootloop as in the phone powers on, then gets stuck, or powers off again
The phone continuously powers on and off and nothing I do (apart from disconnecting the battery) stops it, even then, once the battery is back in it begins looping again...
UnequalB said:
I meant twrp prevents booting to fastbootd, it was after trying to boot into fastbootd using "fastboot reboot fastboot" that the bootloop started, right now I can't seem to get past the boot logo.
Click to expand...
Click to collapse
You don't need to reboot to fastbootd, and you can't apply ADB commands either, because your device doesn't allow it due to random reboots and due to USB debugging is disabled right now.
UnequalB said:
Weirdly enough the error i got was not listed here..
This method doesn't work either since the phone won't stay off for more than 7 seconds.
Click to expand...
Click to collapse
Not true, this is the whole idea of this kind of tools either through SP Flash tool or Infinix tool you just have to GET device can be detected, this tiny portion of time will be enough for the tools can start its job, once the tool started the device get attached without a way to get out of it. To achieve this, prepare ALL that you need for tool to work even press flash/download, connect device with PC and apply the right combination key,
Prepare device manager on Windows and check which status of connection it is passing through to better understand which mode is lacking of.
UnequalB said:
I'm not stuck in a bootloop as in the phone powers on, then gets stuck, or powers off again
The phone continuously powers on and off and nothing I do (apart from disconnecting the battery) stops it, even then, once the battery is back in it begins looping again...
Click to expand...
Click to collapse
You are not saying till now which model your device is, assuming that the bootloader is unlocked.
SubwayChamp said:
You don't need to reboot to fastbootd, and you can't apply ADB commands either, because your device doesn't allow it due to random reboots and due to USB debugging is disabled right now.
Not true, this is the whole idea of this kind of tools either through SP Flash tool or Infinix tool you just have to GET device can be detected, this tiny portion of time will be enough for the tools can start its job, once the tool started the device get attached without a way to get out of it. To achieve this, prepare ALL that you need for tool to work even press flash/download, connect device with PC and apply the right combination key,
Prepare device manager on Windows and check which status of connection it is passing through to better understand which mode is lacking of.
You are not saying till now which model your device is, assuming that the bootloader is unlocked.
Click to expand...
Click to collapse
I tried again and that error seems to just be an issue with the linux version, it detected the phone fine and started writing to "super" on windows, but my laptop died, and now the phone isn't showing up on SP Flash, neither would it turn on at all.. but the charging indicator light comes on when I plug it in.
UnequalB said:
I tried again and that error seems to just be an issue with the linux version, it detected the phone fine and started writing to "super" on windows, but my laptop died, and now the phone isn't showing up on SP Flash, neither would it turn on at all.. but the charging indicator light comes on when I plug it in.
Click to expand...
Click to collapse
Well, if you interrupted the process, that's not good at all. The only you can do is keeping trying it, if your motherboard was not damaged.
hi guys i am DELTIERO from the Philippines did you allready solve the problem?
If not yet done message me on my facebook page https://www.facebook.com/del.villalobos.1/
and i will help you im here veltech san carlos negross occidental phil
Help please! I flashed a gapps zip file using flashify on my infinix smart 5 x657 (Running on lineageos gsi android 12) then the phone just went off. and it not turning on. but it shows the charging indicator light when i connect it to power.
I've tried disconnecting the battery still nothing
what possible solution is there for this?