Hi. I need to send my phone for servicing due to battery issue. I tried to lock bootloader however I am having problems with Fastboot. I installed factory image for Marshmallow A2017GV1.0.0B11(SD rm_userdata)N rollback M that can be found here. I've used minimal_adb_fastboot_1.4.1_portable on windows 10. CMD running as administrator. The only Fastboot related command that return something is
Code:
fastboot devices
Commands like
Code:
fastboot flashing get_unlock_ability
fastboot flashing lock
gives me error "FAILED (remote: unknown command)"
Not sure what am I doing wrong. Is it wrong version of Fastboot that I use? The thing is I also tried that on Linux with Fastboot package and the same error occurred. I also tried different stock roms like B03 and B05 and the result was the same. I even installed ZTE_A2017GV1.2.0B04_Full_Stock_Reverter_by_tron1.zip but still no change. Not sure what am I doing wrong. Please help. Thanks
Related
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
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.
Hello. My phone is accessible only via fastboot and rescue mode.
this appears on screen
func NO: 5 (mcu image)
error no : 1(security verify failed!)
1 .Flashing ROM with this commands is not working, otherwise flashing them is successful
fastboot flash boot BOOT.IMG
fastboot flash recovery RECOVERY.IMG
fastboot flash system SYSTEM.IMG command. *
fastboot flash cust CUST.IMG
2. Recovery option is not accessible
3. EMUI also is not working
4.Phone is unlocked
5.but most of fastboot adb commands are not executable
for instance:
-------- adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error: unknown host service
-------C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem lock
...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
6. My IMEI is gone
7. I can't replace mcu.img parition(in order to fix mcu image error), which is obviously the problem, nor boot.img,recovery.img, system.img and cust.img
VERY IMPORTANT INFORMATION !!!
I am in this situation, because my stock ROM had issues with battery, I tried to root device with wrong tool. Than I f****d my stock firmware,not a big deal, easily fixable in various ways. I reinstall and everything was OK, except the fact my IMEI was corrupted. I start a program in one video (please search in youtube " How To Fix Huawei Invailed Imei By Huawei Imei Fixer Tool" ,because I am new user and don't have permission to upload external links) and than inadvertently press number 7 which wasn't my model number.This is the reason why my phone is bricked. I know..... I suck, but please help me. Is my situation fixable or I just have to throw my phone away. Also I have a desire to bring this phone for repair, but only if there is some sense.
Please help me. Thank you. :crying:
coilspring said:
Hello. My phone is accessible only via fastboot and rescue mode.
this appears on screen
func NO: 5 (mcu image)
error no : 1(security verify failed!)
1 .Flashing ROM with this commands is not working, otherwise flashing them is successful
fastboot flash boot BOOT.IMG
fastboot flash recovery RECOVERY.IMG
fastboot flash system SYSTEM.IMG command. *
fastboot flash cust CUST.IMG
2. Recovery option is not accessible
3. EMUI also is not working
4.Phone is unlocked
5.but most of fastboot adb commands are not executable
for instance:
-------- adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error: unknown host service
-------C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem lock
...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
6. My IMEI is gone
7. I can't replace mcu.img parition(in order to fix mcu image error), which is obviously the problem, nor boot.img,recovery.img, system.img and cust.img
VERY IMPORTANT INFORMATION !!!
I am in this situation, because my stock ROM had issues with battery, I tried to root device with wrong tool. Than I f****d my stock firmware,not a big deal, easily fixable in various ways. I reinstall and everything was OK, except the fact my IMEI was corrupted. I start a program in one video (please search in youtube " How To Fix Huawei Invailed Imei By Huawei Imei Fixer Tool" ,because I am new user and don't have permission to upload external links) and than inadvertently press number 7 which wasn't my model number.This is the reason why my phone is bricked. I know..... I suck, but please help me. Is my situation fixable or I just have to throw my phone away. Also I have a desire to bring this phone for repair, but only if there is some sense.
Please help me. Thank you. :crying:
Click to expand...
Click to collapse
Try here,it might work to fix your imei
Hi there I have the same problem with my p8lite and your proposed method didnt work for me. Please help
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
Hi All,
Trying to flash an A1 with the following rom images and both give the error of Mismatching image and device.
tissot_images_V9.5.9.0.ODHMIFA_20180316.0000.00_8.0_f8cd1b4e8e
tissot_images_V9.5.11.0.ODHMIFA_20180504.0000.00_8.0_1a04581058
The phone is currently a brick belonging to a friend of mine, and I would like to try and get it back up and running. Fastboot can see the device, as can MiFlash, but when running the command
Code:
Fastboot oem device-info
it throws an error stating
Code:
FAILED (Command write failed (Unknown Error))
Any ideas? The device will boot into fastboot but no further, and gives a warning about being unlocked when you try to boot. I'm not sure how to check if it is a re-branded Mi5x or not, as the box is a Global version A1 box with corresponding IMEI cods to a model MDG2. The phone does have the Android One laser etch on the back however.
By bricked I mean the phone will turn on, load the warning about an unlocked bootloader and then go to the Android One "bars" screen you see before the pretty android one loading screen. Here it just stops.
The drivers i'm using come from the MiFlash install, and I've tried doing a TWRP install with fastboot but still no joy. Fastboot can see the device, and talk with it, but nothing I seem to do has got the kit back working.
Anyone able to give some help or advice?
Further info on what ive tried here
http://en.miui.com/thread-3158263-1-1.html