I messed up.
Flashed LineageOS 14.1,
Forgot to flash gaaps,
Afterward, for some reason could not enter TWRP and in 'Developers Options ' there was no option to OEM Unlock so I could not do 'fastboot flash recovery recovery.img' to regain TWRP.
tried to use the 'dload' method to return to stock 6.0.
message said uptade successful.
The phone now does not boot, does not enter erecovery, does not enter the updater (Power Button+Vol. Up+Vol. Down)
Only thing it does is enter fastboot (it says PHONE Unlocked and FRP Lock).
Can you help me?
Edit 1 : In fastboot mode only commands with fastboot work, no adb.
Because it is a Huawei the command 'fastboot oem unlock' does not work.
Edit 2 :Tried to 'fastboot flash system sistem.img' to flash the system.img from the update.app of stock android, unfortunately with the phone OEM Locked there is very little I can do with fastboot.
If anyone can direct me to a fastboot friendly update.zip that has the android-info.txt that seems to be required for for flashing I would apreciate it. (I have read that you can flash google-signed update.zip's while having OEM Lock)
Edit 3 : Looking through XDA I have found user with a similar issue to mine that have been able to enter recovery update after either letting the batery run dry or using fastboot to erase/format userdata and cache, the result for me is again 'FAILED (remote: Command not allowed)'.
Will be sending the P9 to Huawei and see what they can do with this.
Edit 4 : Huawei replaced the board and the battery (apparently it died during the trip to the repair center) they accepted the warranty despite the fact the phone was stuck on the warning screen that said the phone was unlocked.
Related
PROBLEM SOLVED! I used another pc, my usb ports were the problem! I recently got my Nexus 7 (2012), wi-fi only , I unlocked it's bootloader, installer TWRP recovery, and rooted it. For all these operations i used the N7 toolkit , because back then, I was a noob. The rooted tablet (4.2.2) worked Perfectly! But, after about 3 months, it's "volume down" button stopped working. I rebooted it, but it went in bootloader, instead of normal system. So I just select "Start" and it was in Safe Mode! OK, my "volume down" didn't work in Safe Mode (and bootloader mode) neither! And every time I reboot it, it goes to bootloader! I thought that it was a software problem confused , so I began flashing a new ROM. I didn't want to use the toolkit because everyone says that it's bad . I downloaded AndroidSDK, I re-downloaded the ADB and Fastboot drivers, and I downloaded the newer version of the bootloader (4.23, .img) . Tablet was already in bootloader and I connected it to the PC. In platform-tools folder I ran the "fastboot devices" command, and It was able to see it . So I copied the bootloader img to the same folder, and I ran "fastboot flash bootloader bootloader-grouper-4.23.img" . Then I rebooted it into bootloader again. IT WORKED! But, it didn't solve the "volume down" problem. My rooted 4.2.2 and TWRP were still on the system. Everytime I power off the tablet, and then hold the "Power" button, it goes into bootloader. It was that button issue causing that. Then I decided to take it to the service (same place where I bought iw the unloct) , but I couldn't because if they saked bootloader, non-stock recovery and the root, the wouldn't accept the warranty . I decided to download the latest 4.3 stock android, and stock recovery, flash them, and lock the bootloader. I downloaded 4.3 stock from google's official site, (nakasi-jwr66y) and I used the flash-all.bat command that came with it.
.bat command looks like this:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jwr66y.zip
echo Press any key to exit...
pause >nul
exit
I ran it. It successfully did the oem unlock (it was already unlocked) , all the erase commands, and flash bootloader command. But it was stuck on
"fastboot -w update image-nakasi-jwr66y.zip" . It stays steady for about 30secs , and than it says
"sending 'system' (x-kb)"
After some time it just says Data transfer failure(too manly links) ...
I tried the same process billion more times, but same error :/
I tried
-Re-downloading and installing the drivers
-Changing the usb ports, and microUSB cables,
-Restarting the pc (of course)
-Re-downloading the nakasi-jwr66y
-Downloading the twrp recovery (it successfully flashes it)
-Re-downloading the whole SDK
But it DOESN'T WORK? What should I do? Is the volume-down issue hardware or software ?
Sorry for my bad English :////////
P.S. What is the difference between "fastboot flashall" and "fastboot update" ?
Help! "Your device is corrupt. It can't be trusted and may not work properly." (Red)
Hello,
just recently i rooted my Nexus 6p device and unlocked the bootloader, i noticed however, after rooting the device i received an error on boot up stating "Your device software can't be checked for corruption. Please lock the bootloader." (Orange), but after researching on the internet many people said that was normal due to the boot loader being unlocked...
however my concern for today is i have flashed back to the factory images of marshmallow, and am now experiencing an error on boot up that Your device is corrupt. It can't be trusted and may not work properly." i followed the exact step-by-step guide on how to unroot and lock the boot loader on the link below however am still experiencing the issue, please help it will be ever so much appreciated.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
(the error that i am receiving after flashing stock image)
https://lh3.googleusercontent.com/iGv9RPFbDSLec-4-cvsQNOh46pt5RhEvPy7EKKZXmbtjJ16P7d5EXOJHCIsR=w300
I've had that as well with mine before. The way I fixed mine was a somewhat tedious process but it did work for me. Start by downloading one of the angler images from Google, then with 7zip, decompress the .tgz which gives you a .tar. Once more will get you a folder named xxxxxx-angler. (I think it was that way but not 100% sure since I'm not at my laptop at the moment). With your phone (unlocked) in bootloader/fastboot mode, run flash-all.bat. this gets you back to a fully stock system but still has the corruption flag tripped. Run stock recovery and do a factory reset and the corruption warning should be gone and back to the "normal" screen saying please lock the bootloader.
bb1981 said:
I've had that as well with mine before. The way I fixed mine was a somewhat tedious process but it did work for me. Start by downloading one of the angler images from Google, then with 7zip, decompress the .tgz which gives you a .tar. Once more will get you a folder named xxxxxx-angler. (I think it was that way but not 100% sure since I'm not at my laptop at the moment). With your phone (unlocked) in bootloader/fastboot mode, run flash-all.bat. this gets you back to a fully stock system but still has the corruption flag tripped. Run stock recovery and do a factory reset and the corruption warning should be gone and back to the "normal" screen saying please lock the bootloader.
Click to expand...
Click to collapse
thank you but i have already done all that, the problem is that i have flashed the angler image from google and did a factory reset,however, i am selling the phone soon and the warning message is still there even though the boot loader is locked and am not rooted
Moddy98 said:
thank you but i have already done all that, the problem is that i have flashed the angler image from google and did a factory reset,however, i am selling the phone soon and the warning message is still there even though the boot loader is locked and am not rooted
Click to expand...
Click to collapse
Try doing this process manually, if you're selling it. I would infer the data doesn't matter on the device.
Depending on which OS you are on. Focus your command prompt with fast boot installed to your directory containing the stock files (unzip the image zip)
Now do the following process manually. Step by step
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash vendor vendor.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot flash cache cache.img
Now, if you still get the red warning. Repeat the process and add :
fastboot format userdata
DO NOT FLASH THE USERDATA IMAGE
If this does not work, I have other suggestions.
same prob in orange..plz help bro
TnT_ said:
Try doing this process manually, if you're selling it. I would infer the data doesn't matter on the device.
Depending on which OS you are on. Focus your command prompt with fast boot installed to your directory containing the stock files (unzip the image zip)
Now do the following process manually. Step by step
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash vendor vendor.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot flash cache cache.img
Now, if you still get the red warning. Repeat the process and add :
fastboot format userdata
DO NOT FLASH THE USERDATA IMAGE
If this does not work, I have other suggestions.
Click to expand...
Click to collapse
I flashed my nexus 5x with marshmallow from nougat...but at the end i didn't lock the oem bootloader...so now i am repeatedly getting an error message "your device software can't be checked for corruption.Please lock the bootloader nexus"(orange color)..i had downgraded my nexus to marshmallow because i was having a bootloader stuck up loop problem...
And to do any of the steps I have to switch on the usb debugging mode right ??? But the problem is this message is constantly coming and i am unable to do anything for the past 2 days
vigy321 said:
I flashed my nexus 5x with marshmallow from nougat...but at the end i didn't lock the oem bootloader...so now i am repeatedly getting an error message "your device software can't be checked for corruption.Please lock the bootloader nexus"(orange color)..i had downgraded my nexus to marshmallow because i was having a bootloader stuck up loop problem...
And to do any of the steps I have to switch on the usb debugging mode right ??? But the problem is this message is constantly coming and i am unable to do anything for the past 2 days
Click to expand...
Click to collapse
To flash back to stock, you have to boot into bootloader and using fastboot to flash factory image.
But hey, you're in the Nexus 6P forum, try following this guide in the Nexus 5X forum:
https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I just went through this. Just unlock your bootloader with the Nexus toolkit and it'll go away that's all i did
Sent from my Nexus 6P using Tapatalk
---------- Post added at 06:45 PM ---------- Previous post was at 06:42 PM ----------
Moddy98 said:
Hello,
just recently i rooted my Nexus 6p device and unlocked the bootloader, i noticed however, after rooting the device i received an error on boot up stating "Your device software can't be checked for corruption. Please lock the bootloader." (Orange), but after researching on the internet many people said that was normal due to the boot loader being unlocked...
however my concern for today is i have flashed back to the factory images of marshmallow, and am now experiencing an error on boot up that Your device is corrupt. It can't be trusted and may not work properly." i followed the exact step-by-step guide on how to unroot and lock the boot loader on the link below however am still experiencing the issue, please help it will be ever so much appreciated.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
(the error that i am receiving after flashing stock image)
https://lh3.googleusercontent.com/iGv9RPFbDSLec-4-cvsQNOh46pt5RhEvPy7EKKZXmbtjJ16P7d5EXOJHCIsR=w300
Click to expand...
Click to collapse
It happened to me just last week. Just unlock your bootloader with the Nexus toolkit and it'll go away. That's all i did and it went away i got it the same way you did and that's all I did
Sent from my Nexus 6P using Tapatalk
what i messed up?
i have installed custom official cynogen14.1 rom and twrp recovery. everything was working fine.
but i messed up with bootloader. I have locked oem from fastboot mode without enabling option for oem unlocking in developer settings.
Now as my phone have custom rom and twrp installed it went into bootloop and only shows zuk logo and again restart.
What i diid till now?
i have opened backcover so that i can turn of bootloop and phone by disconecting battery.
I can enter into fastboot mode by pressing vol.+ and vol- buttons sumultaneously and connecting usb cable.
But i cannot unlock bootloader as it says unlocking bootloader not allowed. I have tried device specific commads like "fastboot -i 0x2b4c oem unlock" and "fastboot -i 0x2b4c oem unlock-go" but nothing works.
i have stock recovery image but cannot flash while bootloader is locked.
i can enter into adb sideload by following method:
by loading stock recovery by typing "fastboot boot recovery.img" (this does not work with twrp as it says signature varification failed)
and then selecting apply update >> selecting apply fron adb
this much i can do does anyone knows how to recover from such a state.
please help me or my phone will be a waste.
is there any way to install stock recovery i think phone will boot properly if i managed to install stock recovery.
To summarize, I have a Moto G5 Plus, with locked bootloader and I decided to update a ROM STOCK and made a simple mistake by forgetting the OEM unlock option in advance in the configuration menu. An error occurred on the way and tried to return to the stock. Now, when the phone boots up, it enters the boot loader (which is locked) and displays a startup error message that states that you must use the Software Repair Wizard.
trying to enter the recovery gives a code:
AP Fastboot Flash Mode [Secure]
Fastboot Reason: UTAG "bootmode" configured as fastboot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
Is there a known solution or force a recovery to work?
Thanks to all
Hello;
I found the solution, download the latest firmware from your cell phone, download it just unzip the zip and look for the files: gpt.bin and bootloader.img, those 2 ctrl + c and files go to the folder where they downloaded ADB tools and paste the files there , then execute the steps to open command window here and execute the following:
fastboot flash partitiongpt.bin
fastboot bootloader bootloader.img
fastboot reboot-bootloader
and it is ready to install the downloaded rom.
Gracias a AndresBRS https://www.clangsm.com/forum/index.php?showtopic=466891
Same problem with moto g5s plus xt1804
After flashing it shows failed to start ..failed to boot recovery and when I am trying to unlock bootloader it shows unlock data unavailable
beyondsunshine92 said:
After flashing it shows failed to start ..failed to boot recovery and when I am trying to unlock bootloader it shows unlock data unavailable
Click to expand...
Click to collapse
Install lenovo moto smart assistant in pc and go for rescue and flash the whole firmware.if your device is not supported then flash manually.
Moto smart assistant shows device not supported however I tried many fastboot stock roms but every time I get error invalid signed image. .ph stuck in fastboot
beyondsunshine92 said:
Moto smart assistant shows device not supported however I tried many fastboot stock roms but every time I get error invalid signed image. .ph stuck in fastboot
Click to expand...
Click to collapse
Download the firmware from here and then flash.
https://mirrors.lolinet.com/firmware/moto/potter/official/
riyan65 said:
Download the firmware from here and then flash.
@beyondsunshine92: Did you tried this? Is it working? I am also having the same issue. Please help guys
Click to expand...
Click to collapse
Hello. I have a lg v20 H990N. I flashed TWRP by dirty santa method and wanted to go back to stock. As per the instructions on the link https://forum.xda-developers.com/v20...-h990-t3624296, I used method 1a for going back to stock. I ran the code as mentioned in the method while using my backed up "abootbackup.img" but I accidently ran the code twice.
Code:
dd if=abootbackup.img of=/dev/block/bootdevice/by-name/aboot
sync
sleep 30
sync
After booting to bootloader. this is what I see written on the boot loader screen.
___________________________________
Welcome to fastboot mode for bootloader unlock:
*Quick Guidnance
1) Read Device Id
fastboot oem device-id
2) Write unlock key
fastboot flash unlock unlock.bin
3) Check boiotloader is unlocked
Fastboot getvar unlocked
*How to exit fastboot mide
USe "Fastboot reboot' command if fastboot is available
________________________________________
This is the meassage that pops up in fastboot. I can use fastboot but can't use "fastboot flash recovery twrp-3.0.2-1-h990.img" as it exits with error that remote: device is locked. I can't flash kdz with lg Up as Lg up says " there is no haadset connected". TWRP recovery is also not boot neither is the nougat rom that was installed. More \over my device is shown as "Kedacom USB device " in device manager in fastboot mode. Not in Com ports.
It apperas that my bootloader has locked somehow after flashing abootbackup and I can't unlock it as h990N is not supported by LG to unlock bootloader. screenshot attached.
Please help!!!
Yeah flashing the stock bootloader relocks most v20 variants, (the dirty santa bootloader can't truely unlock them, it just ignores the lock)
I'm not sure what you expected? Your link is broken, but it sounds like you reflashed stock firmware and then the stock bootloader and expected to be in a different situation than a fresh unrooted device?
You should be able to boot normally to Android or boot I to download mode and reroot from scratch.
.