Related
So I was running cynogenmod on my nexus 7 2012, and now that lollipop is out, I wanted to do a complete restore of my device and install stock. I first tried a few one click methods, but none of those worked, so I tried using the android sdk to install it through the command prompt. After a long struggle, I gave up and tried to turn my device back on, but it says "booting failed" in the upper right corner, and it doesnt get past the google screen. I can get to fastboot no problem, but I cant get into my recovery(which I am guessing got wiped). When I tried to reinstall stock again, every method i tried got stuck on trying to flash the bootloader. Is my device permanently bricked? If its not how can I fix it? thanks
See this. The Lollipop LRX21P factory image also has a borked bootloader file.
Replace the file "bootloader-grouper-4.23.img" with a valid version from the JWR66V, KRT16O, or KRT16S factory images and try again.
(actually, if you already have the 4.23 bootloader there is no need to flash the bootloader; you could edit the "flash-all.bat" file and remove the bootloader flash and reboot-bootloader lines).
Consider yourself lucky you still can get to fastboot.
bftb0 said:
See this. The Lollipop LRX21P factory image also has a borked bootloader file.
Replace the file "bootloader-grouper-4.23.img" with a valid version from the JWR66V, KRT16O, or KRT16S factory images and try again.
(actually, if you already have the 4.23 bootloader there is no need to flash the bootloader; you could edit the "flash-all.bat" file and remove the bootloader flash and reboot-bootloader lines).
Consider yourself lucky you still can get to fastboot.
Click to expand...
Click to collapse
Yea in fastboot it says that the bootloader version is 4.23. Ill try flashing it without the bootloader and see if that works
ok so I tried running the flash-all.bat, and it says archive does not contain boot.sig, and archive.sig. Then, it continues flashing, but after it gets to sending boot, I get an error that says FAILED(data transfer failure (unknown error)). then When I try to do something on the nexus it is frozen, and I have to hold power and volume down to get back into fastboot. Am I missing the boot and archive files?
ok so I reinstalled the android sdk and then flashed the image and it worked. There must have been some files missing or something. Thanks for your help!
Hi,
I did search, but I didn't find any solution to the issue. I got the Nexus 6P 64 GB.
I unlocked my bootloader using the 6p Multitool. Thereafter I used my normal method of fastboot (Minimal ADB) to flash the boot.img from this thread http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344.
After that I flashed TWRP. Basically I followed the instructions here: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928.
But my phone is not booting up.
It gives me this error:
Your device software cannot be checked for corruption. Please lock the bootloader."
But I tried that and it doesn't work. I tried from fastboot restoring to factory, but get the same message.
Please help me!
Did you check the enable oem unlocking in developer settings?
Sent from my Nexus 6P using Tapatalk
Yes. As I said, I achieved the unlock. Now I just can't get back into my phone or recovery or anything other than fastboot (where it says unlock)
isn't "Your device software cannot be checked for corruption. Please lock the bootloader." the new msg on boot when you are unlocked, and you have to wait ~10 secs before it startup ?
After that, I'm stuck on the Google screen. It just goes on and on. Left it for over 20 minutes at one point and it didn't get past it.
Edit: The multicolored animated google screen. The animation just keeps going and going.
Del.
Your issue might be due to the encryption of the phone. Take a look at this thread: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976
From this thread:
NOTE: Decrypting data is not supported yet. The Nexus 6P will normally attempt to encrypt the device automatically on first boot. To use TWRP as you normally would, you will have to format data and install a slightly modified boot image with forceencrypt disabled. My Nexus 6P should arrive tomorrow and I will start working on decrypt once I get my hands on it.
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Read through that thread. Part of the issue is that I don't know which variant (MDA89D & MDB08K) I have, or how to find that out seeing as I can't boot into the phone.
If I have the variant I may be able to fix this through the unified toolkit (though I'm not sure of that)
Did you ever fix this?
Try flashing the factory image and starting from scratch. You must have messed up somewhere. Re-download the boot.img from Chainfire's thread, maybe that was corrupt or something.
1. Download the MDB08K factory image (it's not a variant, it's a Marshmallow update) and unzip it.
2. Download the MDB08K boot.zip from Chainfire's modified boot.img thread
3. Download latest SuperSU beta zip
Wipe phone in TWRP, to include format data.
In bootloader, fastboot flash MDB08K
fastboot flash modified boot.img (from zip)
In TWRP, ADB sideload SuperSU
Reboot and it should perform normally.
kibmikey1 said:
1. Download the MDB08K factory image (it's not a variant, it's a Marshmallow update) and unzip it.
2. Download the MDB08K boot.zip from Chainfire's modified boot.img thread
3. Download latest SuperSU beta zip
Wipe phone in TWRP, to include format data.
In bootloader, fastboot flash MDB08K
fastboot flash modified boot.img (from zip)
In TWRP, ADB sideload SuperSU
Reboot and it should perform normally.
Click to expand...
Click to collapse
Thank you for your reply, but I can't get into TWRP either!! Any way for me to restore to factory or do the repairs from in flashboot without the restore?
I ran into the same issue last night trying to install TWRP. I'm still not sure how to get around it but I did get my phone back. you should be able to get to the bootloader (hold the power button until phone turns off, then hold vol up+vol down+power) once there use ADB fastboot to go back to stock.
this link will walk you through what you need. follow step 7.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
here it is as well:
How To Flash The Factory Images (And Return To Stock)
Prerequisites: unlocked bootloader (section 1).
Download the appropriate factory images for your model here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-01.31.img
radio-angler-angler-01.29.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-01.31.img
cache.img
radio-angler-angler-01.29.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-01.31.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-m8994f-2.6.28.0.65.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash userdata C:\angler\images\userdata.img
fastboot flash vendor C:\angler\images\vendor.img
Thank you. I was eventually able to do tysonwald's suggestion. First I didn't know what my version was, so I couldn't.
At some point I was able to get into the phone with constant gapp errors, check it.
Now my phone is unlocked and rooted. But when I go to settings to security (and when I tried to set up my fingerprint) settings crashes. Any ideas?
There was still some issue. I wiped the phone with the above method again, did NOT set up twrp/root, and everything works. It was something about the custom boot image I guess. Any advice if I want to try to set it up again?
Problem solved. Needed to update to newer image before doing everything. Issue resolve from Heisenberg's thread. Thank you all!
I had the same damn issue last night. Thise bootleg instructions had me flashing build k boot.img on build D. Maybe i wasnt paying attention lol!
I have a very similar problem, I flashed the k boot img. and now I'm stuck in an endless bootloop any idea?
TeriusPR said:
I have a very similar problem, I flashed the k boot img. and now I'm stuck in an endless bootloop any idea?
Click to expand...
Click to collapse
Read thru this guide and follow the instructions to the T. http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I had a similar issue just now where my phone got stuck at the TWRP logo. Selecting the reboot option in download mode refused to remove it. I had to follow step 10 to get my phone back to stock. I'm afraid to try this again now
Is there anyway to know which version do i need to download? i bought the phone already bricked and i am trying to bring it back to life
Hi guys massive android noobie here!
I really hope you guys can help me cause I am desperate!
This is what happened: I tried to manually update my phone B200 to B313. I had no luck with the update.zip so I tried the update.app (superstupid). As you guys might know, this resulted in a bootloop.
I downloaded Huawei firmware extractor and adb. I have two problems on top of a not working phone:
1: when i try to extract my firmware i just get a system.img, no boot.img or the other one you need
2: i managed to unlock my bootloader, but whenever i use adb devices it stays empty, fastboot reboot works though... weird
How do I get my lovely device working again?
Kind regards,
Jurgen
Flash B200 again with 3 button method, should work
Extract zip files and copy update.app on SD card, in dload folder
lejur said:
Hi guys massive android noobie here!
I really hope you guys can help me cause I am desperate!
This is what happened: I tried to manually update my phone B200 to B313. I had no luck with the update.zip so I tried the update.app (superstupid). As you guys might know, this resulted in a bootloop.
I downloaded Huawei firmware extractor and adb. I have two problems on top of a not working phone:
1: when i try to extract my firmware i just get a system.img, no boot.img or the other one you need
2: i managed to unlock my bootloader, but whenever i use adb devices it stays empty, fastboot reboot works though... weird
How do I get my lovely device working again?
Kind regards,
Jurgen
Click to expand...
Click to collapse
I tried to do something similar, although I screwed it up even further. Prior to attempting this entire process, I was using GRA-L09 build B171. After attempting to install B317 from B171, I got stuck in a bootloop between the Huawei logo and TWRP. I realized that my mistake was probably because I had TWRP instead of the stock ROM. Therefore, I downloaded the B170 full firmware and extracted the B170 files. I tried to use fastboot to flash boot.img system.img and recovery.img according to bihsik's guide, but fastboot could never recognize my device. So I decided to be "smart" and transfer Boot.img and recovery.img from the B170 firmware to my dload folder on my external sd card on the phone and install them directly from TWRP.
This screwed everything up, and now I'm stuck in Rescue Mode with "Error! Func NO : 11 (recovery image) Error NO : 2 (load failed!)"
I've searched google and XDA forums and have tried the methods here and here but without any luck.
Is there a way to fix my phone?
You can Easily Fix your Device , Just follow the Steps Carefully
Follow this link to fix your Mobile:
This Tutorial is easy to follow. Fix your device and Return to your OFFICIAL STOCK ROM
https://youtu.be/4AkSuE20_08
Links are included in video Description .
Cheers...!
I bricked my mobile few months ago and I fixed my mobile using this video , hope it will help you guys too.
---------- Post added at 12:28 PM ---------- Previous post was at 12:25 PM ----------
vudawatta said:
I tried to do something similar, although I screwed it up even further. Prior to attempting this entire process, I was using GRA-L09 build B171. After attempting to install B317 from B171, I got stuck in a bootloop between the Huawei logo and TWRP. I realized that my mistake was probably because I had TWRP instead of the stock ROM. Therefore, I downloaded the B170 full firmware and extracted the B170 files. I tried to use fastboot to flash boot.img system.img and recovery.img according to bihsik's guide, but fastboot could never recognize my device. So I decided to be "smart" and transfer Boot.img and recovery.img from the B170 firmware to my dload folder on my external sd card on the phone and install them directly from TWRP.
This screwed everything up, and now I'm stuck in Rescue Mode with "Error! Func NO : 11 (recovery image) Error NO : 2 (load failed!)"
I've searched google and XDA forums and have tried the methods here and here but without any luck.
Is there a way to fix my phone?
Click to expand...
Click to collapse
Just be Care full in choosing the Firmware , if your firmware doesn't match , then the 3 Button method will stop at 5%.
Good day everyone!
My fellow housemate managed to soft-brick his device and now im trying to think of a fix.
The device used to have Android 7.0 installed (EMUI 5.0). Then he installed TWRP + some custom 6.0 based rom, which resulted in a soft brick.
What i've tried so far:
1. Tried multiple update.app packages (C432B170 and C432B130 SHOULD be the ones i need, since the device is european). Update always fails with message "Incompatibility with current version. Please download the correct package".
2. Extracted BOOT.img, RECOVERY.img, SYSTEM.img and CUST.img and tried flashing them with fastboot. SYSTEM.img fails with message FAILED (remote: sparse flash write failure), CUST.img fails with some error connected with partitions.
3. Tried the downgrade package from Nougat to Marshmallow. Update.app still doesnt work with the same error as mentioned earlier, however, SYSTEM.img flashed via fastboot this time, but with no success, system still only boots in eRecovery and fastboot modes.
4. Tried installing multiple TWRP recoveries, none of them seem to work. Device just wont boot in recovery mode.
Any ideas?
Best regards,
Vlad
shxtov said:
Good day everyone!
My fellow housemate managed to soft-brick his device and now im trying to think of a fix.
The device used to have Android 7.0 installed (EMUI 5.0). Then he installed TWRP + some custom 6.0 based rom, which resulted in a soft brick.
What i've tried so far:
1. Tried multiple update.app packages (C432B170 and C432B130 SHOULD be the ones i need, since the device is european). Update always fails with message "Incompatibility with current version. Please download the correct package".
2. Extracted BOOT.img, RECOVERY.img, SYSTEM.img and CUST.img and tried flashing them with fastboot. SYSTEM.img fails with message FAILED (remote: sparse flash write failure), CUST.img fails with some error connected with partitions.
3. Tried the downgrade package from Nougat to Marshmallow. Update.app still doesnt work with the same error as mentioned earlier, however, SYSTEM.img flashed via fastboot this time, but with no success, system still only boots in eRecovery and fastboot modes.
4. Tried installing multiple TWRP recoveries, none of them seem to work. Device just wont boot in recovery mode.
Any ideas?
Best regards,
Vlad
Click to expand...
Click to collapse
I had the exact same problem! And I found a fix. Boot into the dload method of updating ( make sure it will give you an error, so don't have an SD card in ) then when it fails reboot. And as soon as it starts rebooting hold volume up, then it should take you to the stock recovery, then just wipe and it should be working! All the best
vdp1nnab said:
I had the exact same problem! And I found a fix. Boot into the dload method of updating ( make sure it will give you an error, so don't have an SD card in ) then when it fails reboot. And as soon as it starts rebooting hold volume up, then it should take you to the stock recovery, then just wipe and it should be working! All the best
Click to expand...
Click to collapse
Booted into Huawei eRecovery and it doesnt give me an option to wipe anything, just "download latest version and recovery" via Wi-Fi, which, unfortunately, fails.
shxtov said:
Booted into Huawei eRecovery and it doesnt give me an option to wipe anything, just "download latest version and recovery" via Wi-Fi, which, unfortunately, fails.
Click to expand...
Click to collapse
Okay. Try again. This time go into e recovery, then reboot and the second you touch that reboot button you hold volume up. Also one question. Can u boot into fastboot and ADB recognises your device ?
vdp1nnab said:
Okay. Try again. This time go into e recovery, then reboot and the second you touch that reboot button you hold volume up. Also one question. Can u boot into fastboot and ADB recognises your device ?
Click to expand...
Click to collapse
Nope, can't get into recovery, at all. Just keeps rebooting.
Yes, i can get into fastboot mode and fastboot recognizes the device.
shxtov said:
Nope, can't get into recovery, at all. Just keeps rebooting.
Yes, i can get into fastboot mode and fastboot recognizes the device.
Click to expand...
Click to collapse
Okay that helps a huge load. What you need to do is flash the nougat ROM again. You need to put the rom files into the root of ADB install location (program files/ Minimal ADB and Fastboot) in zip format. If I'm not mistaken you have update.zip and vnsXXX_Full_data (or something similar).
Then flash the firmware using this command once your connected in fastboot. I'm not sure the command. But I did some googling and can't find a solid answer. I remember doing it but I don't remember the command line.
Hi all,
I grabbed the latest factory build from here <https://developers.google.com/android/images#angler> and the latest TWRP recovery from here <https://dl.twrp.me/angler/>
I then proceeded to boot into recovery, formatted my entire system (including userdata), flashed the latest recovery, copied over the 8.0.0 build and the latest GAAPS, and then attempted to flash the factory image.
Unfortunately, this is where I've now gotten stuck. TWRP replies with my flash command with "invalid zip file format" and refuses to install.
I've attempted to go back to an old recovery and re-install build N4F26J, which also gets "invalid zip file format".
I also have a full TWRP backup from build N4F26J with 3 variations: Boot-System-Data, Boot-System-SysImage-Data, and Boot-System-SysImage-Vendor-Data-Cache-Recovery, but all 3 of them result in a frozen boot animation.
tl;dr: Anyone have an idea of what I can do to get a working factory image back onto my phone? Currently am stuck with a bootlooping backup image and a zip error warning when installing a new image (regardless of image version).
Thanks in advance!
Tiffiter said:
Hi all,
I grabbed the latest factory build from here <https://developers.google.com/android/images#angler> and the latest TWRP recovery from here <https://dl.twrp.me/angler/>
I then proceeded to boot into recovery, formatted my entire system (including userdata), flashed the latest recovery, copied over the 8.0.0 build and the latest GAAPS, and then attempted to flash the factory image.
Unfortunately, this is where I've now gotten stuck. TWRP replies with my flash command with "invalid zip file format" and refuses to install.
I've attempted to go back to an old recovery and re-install build N4F26J, which also gets "invalid zip file format".
I also have a full TWRP backup from build N4F26J with 3 variations: Boot-System-Data, Boot-System-SysImage-Data, and Boot-System-SysImage-Vendor-Data-Cache-Recovery, but all 3 of them result in a frozen boot animation.
tl;dr: Anyone have an idea of what I can do to get a working factory image back onto my phone? Currently am stuck with a bootlooping backup image and a zip error warning when installing a new image (regardless of image version).
Thanks in advance!
Click to expand...
Click to collapse
You don't flash a factory image in TWRP. Unzip the file and flash the individual images: boot, system, and vendor. Try that method or use ADB sideload to install the full OTA image. Full OTA images can be downloaded from the same site.
Sent from my Nexus 5X using Tapatalk
I'm assuming you have ADB / fastboot in place (if not, google it): unzip your factory image to a given folder. Navigate to this folder using prompt / terminal. Turn on your phone with vol down pressed and leave it at that screen. Plug it onto your computer and type fastboot devices - you should see a line with a bunch of numbers. If Windows, run flash-all.bat. If Mac / Linux, run flash-all.sh. Your phone should get back to life in a few, sit back and relax.
Tiffiter said:
Hi all,
I grabbed the latest factory build from here <https://developers.google.com/android/images#angler> and the latest TWRP recovery from here <https://dl.twrp.me/angler/>
I then proceeded to boot into recovery, formatted my entire system (including userdata), flashed the latest recovery, copied over the 8.0.0 build and the latest GAAPS, and then attempted to flash the factory image.
Unfortunately, this is where I've now gotten stuck. TWRP replies with my flash command with "invalid zip file format" and refuses to install.
I've attempted to go back to an old recovery and re-install build N4F26J, which also gets "invalid zip file format".
I also have a full TWRP backup from build N4F26J with 3 variations: Boot-System-Data, Boot-System-SysImage-Data, and Boot-System-SysImage-Vendor-Data-Cache-Recovery, but all 3 of them result in a frozen boot animation.
tl;dr: Anyone have an idea of what I can do to get a working factory image back onto my phone? Currently am stuck with a bootlooping backup image and a zip error warning when installing a new image (regardless of image version).
Thanks in advance!
Click to expand...
Click to collapse
As already mentioned, you can't flash factory images via TWRP.
Get ADB and use the flash-all.bat that comes with the factory image to clean install your OS.
Just go to bootloader mode and run the file.
Bear in mind it will WIPE all your device.
wizardwiz said:
As already mentioned, you can't flash factory images via TWRP.
Get ADB and use the flash-all.bat that comes with the factory image to clean install your OS.
Just go to bootloader mode and run the file.
Bear in mind it will WIPE all your device.
Click to expand...
Click to collapse
Actually that's partially incorrect. You have to flash bootloader and radio via fastboot. You can flash boot, system and vendor with TWRP (choosing img option) and, provided you root before booting, you can preserve the custom recovery.
ultyrunner said:
Actually that's partially incorrect. You have to flash bootloader and radio via fastboot. You can flash boot, system and vendor with TWRP (choosing img option) and, provided you root before booting, you can preserve the custom recovery.
Click to expand...
Click to collapse
Flashing factory images using flash-all.bat (or .sh) will flash ALL OS including modem, bootloader and everything else.
He can't use this method if his bootloader is locked.
I wasn't talking about using a manual fastboot option to flash an indevidual image.
wizardwiz said:
Flashing factory images using flash-all.bat (or .sh) will flash ALL OS including modem, bootloader and everything else.
He can't use this method if his bootloader is locked. I wasn't talking about using a manual fastboot option to flash an indevidual image.
Click to expand...
Click to collapse
In his original post he doesn't say anything about having a locked BL. As well, if he's stuck the way he is then perhaps you should have given him better information. It'd give him far more control if you directed him to the unlock/root/flash guide, which gives him more options (and more control via flashing individual partitions via fastboot) at https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928.
ultyrunner said:
In his original post he doesn't say anything about having a locked BL. As well, if he's stuck the way he is then perhaps you should have given him better information. It'd give him far more control if you directed him to the unlock/root/flash guide, which gives him more options (and more control via flashing individual partitions via fastboot) at https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928.
Click to expand...
Click to collapse
We're not in a contest, buddy. Just trying to help that guy.
He can simply choose the best option for him to get his device up and running.
If he is familiar with fastboot image flashing then by all do means he can use your method.
He is stuck with no OS installed and using flash-all.bat file is the easiest way to get his device boot properly.
wizardwiz said:
We're not in a contest, buddy. Just trying to help that guy.
He can simply choose the best option for him to get his device up and running.
If he is familiar with fastboot image flashing then by all do means he can use your method.
He is stuck with no OS installed and using flash-all.bat file is the easiest way to get his device boot properly.
Click to expand...
Click to collapse
No we're not in competition. My point was you gave him one option with the least control and not remotely the best option to get his device up and running, particularly making an assumption he has a locked bootloader, when you never asked. If he is able to use a command line to run a flash command, then pointing him to the guide is the best bet. If something goes wrong with flash-all scripts then he's probably going to be really lost.