Red triangle during the installation of Android 5.1 (OTA) - Nexus 5 Q&A, Help & Troubleshooting

Hello everyone,
I have a Nexus 5 Stock without root with Android 5.0.1.
When I get the OTA Android 5.1, when it is unloaded, i restart the phone for installation but this crashes and shows the android with the belly open and the red triangle (and the word error in the robot).
This problem happened to me on other occasions, is the only solution that I was able to find was to manually flash the ROM. But I'd like you would install the ROM normally using 'OTA.
I hope you can solve my problem, thank you in advance

thejackal94 said:
Hello everyone,
I have a Nexus 5 Stock without root with Android 5.0.1.
When I get the OTA Android 5.1, when it is unloaded, i restart the phone for installation but this crashes and shows the android with the belly open and the red triangle (and the word error in the robot).
This problem happened to me on other occasions, is the only solution that I was able to find was to manually flash the ROM. But I'd like you would install the ROM normally using 'OTA.
I hope you can solve my problem, thank you in advance
Click to expand...
Click to collapse
Try to install ota again, and when you get that error screen press and hold power key then press and release volume_up key then you should some sort of text which will tell what caused the error and then you can release the power key.
What error you see?

thejackal94 said:
Hello everyone,
I have a Nexus 5 Stock without root with Android 5.0.1.
When I get the OTA Android 5.1, when it is unloaded, i restart the phone for installation but this crashes and shows the android with the belly open and the red triangle (and the word error in the robot).
This problem happened to me on other occasions, is the only solution that I was able to find was to manually flash the ROM. But I'd like you would install the ROM normally using 'OTA.
I hope you can solve my problem, thank you in advance
Click to expand...
Click to collapse
It doesn't sound like you do, but in the off chance that you have TWRP or ClockworkMod installed, these will cause an OTA to fail installing.

bitdomo said:
Try to install ota again, and when you get that error screen press and hold power key then press and release volume_up key then you should some sort of text which will tell what caused the error and then you can release the power key.
What error you see?
Click to expand...
Click to collapse
Ok i have tried, this is the message that appears:
E:Error in /cache/update.zip
(status 7)
Installation aborted.
Mounted /system

Visa Declined said:
It doesn't sound like you do, but in the off chance that you have TWRP or ClockworkMod installed, these will cause an OTA to fail installing.
Click to expand...
Click to collapse
My nexus is completely stock, I never installed TWRP, ClockworkMod.

thejackal94 said:
Ok i have tried, this is the message that appears:
E:Error in /cache/update.zip
(status 7)
Installation aborted.
Mounted /system
Click to expand...
Click to collapse
Maybe you have a bad download.
Wipe cache in the stock recovery. This will delete the downloaded OTA and will force the phone to download it again.

bitdomo said:
Maybe you have a bad download.
Wipe cache in the stock recovery. This will delete the downloaded OTA and will force the phone to download it again.
Click to expand...
Click to collapse
I tried to do the Wipe cache, but always same error (status 7)

thejackal94 said:
I tried to do the Wipe cache, but always same error (status 7)
Click to expand...
Click to collapse
Download google usb drivers
Extract it
Download ota
Rename ota to update.zip
Download 15 secs adb installer
Install it
Connect phone in bootloader mode.
Install drivers for bootloader mode in device manager using the the extracted google usb drivers.
Go to recovery mode.
Enable the recovery menu
Select apply update from ADB
In device manager install the drivers for the new Unknown (or nexus 5) device. You have to select the Let me pick from list of device drivers on my computer then select ADB Interface and then select anything which has ADB in its name.
Open CMD
cd to the directory which contains the update.zip
Use this command: adb sideload update.zip
If ADB sideload timed out on the phone then select apply update from ADB again​

bitdomo said:
Download google usb drivers
Extract it
Download ota
Rename ota to update.zip
Download 15 secs adb installer
Install it
Connect phone in bootloader mode.
Install drivers for bootloader mode in device manager using the the extracted google usb drivers.
Go to recovery mode.
Enable the recovery menu
Select apply update from ADB
In device manager install the drivers for the new Unknown (or nexus 5) device. You have to select the Let me pick from list of device drivers on my computer then select ADB Interface and then select anything which has ADB in its name.
Open CMD
cd to the directory which contains the update.zip
Use this command: adb sideload update.zip
If ADB sideload timed out on the phone then select apply update from ADB again​
Click to expand...
Click to collapse
I followed step by step the guide but again appears Status 7! I don't know what to do

thejackal94 said:
I followed step by step the guide but again appears Status 7! I don't know what to do
Click to expand...
Click to collapse
The next step would be doing a factory reset. If that not works then unlocking bootloader and flashing the latest stock rom in fastboot.

Related

Phone stuck on boot animation, won't sideload

I unrooted phone to update to Android 5.0.1
Wiped data & cache and tried to reboot but phone won't load past boot animation
I have tried everything I can find online. Phone appears in Device Manager as Android Device, but does not connect to PC when in command prompt.
adb devices shows no devices
when I start phone in fastboot, then recovery mode, I can select to install a file via ADB
when I choose this, and run adb devices in command prompt, it then shows a sideload device
but when I go to load a file, it gives me the same error every time:
E:footer is wrong
E:signature verification failed
Is there anything I can do? Please help! Thanks.
pds6 said:
I unrooted phone to update to Android 5.0.1
Wiped data & cache and tried to reboot but phone won't load past boot animation
I have tried everything I can find online. Phone appears in Device Manager as Android Device, but does not connect to PC when in command prompt.
adb devices shows no devices
when I start phone in fastboot, then recovery mode, I can select to install a file via ADB
when I choose this, and run adb devices in command prompt, it then shows a sideload device
but when I go to load a file, it gives me the same error every time:
E:footer is wrong
E:signature verification failed
Is there anything I can do? Please help! Thanks.
Click to expand...
Click to collapse
What recovery have you got and what file are you sideloading?
All you have to do is restart the phone in bootloader and make a fresh install of factory image via fastboot.
rootSU said:
What recovery have you got and what file are you sideloading?
Click to expand...
Click to collapse
I'm not sure unfortunately... Is that something I can find out from the Fastboot menu?
I was trying to sideload a factory image 5.0 or 5.0.1
pds6 said:
I'm not sure unfortunately... Is that something I can find out from the Fastboot menu?
I was trying to sideload a factory image 5.0 or 5.0.1
Click to expand...
Click to collapse
You can't sideload a factory image. You must use fastboot.
zagorteney said:
All you have to do is restart the phone in bootloader and make a fresh install of factory image via fastboot.
Click to expand...
Click to collapse
How can I make my Acer read Nexus 5 to install factory image via command prompt?
It comes up in Device Manager, driver seems to be installed fine, as Android Device but does not connect properly (no devices listed in "adb devices")
You use fastboot in bootloader if you want to use factory images.
Read the following 2 threads in general > sticky roll-up
- adb and fastboot
- flashing factory images / save your nexus
rootSU said:
You can't sideload a factory image. You must use fastboot.
Click to expand...
Click to collapse
Oh okay, my bad. Do I have any options to sideload anything, or is there a way to make phone connect for fastboot? Again, it's visible in Device Manager w/drivers, but not in command prompt. Thank you
will try above suggestions and report back
rootSU said:
You use fastboot in bootloader if you want to use factory images.
Read the following 2 threads in general > sticky roll-up
- adb and fastboot
- flashing factory images / save your nexus
Click to expand...
Click to collapse
After downloading the recommended Driver file from adb and fastboot thread, I unzip it to a folder and attempt to install in Device Manager. I get error saying "the hash for the file is not present in the specified file log..."
pds6 said:
After downloading the recommended Driver file from adb and fastboot thread, I unzip it to a folder and attempt to install in Device Manager. I get error saying "the hash for the file is not present in the specified file log..."
Click to expand...
Click to collapse
Win 7?
rootSU said:
Win 7?
Click to expand...
Click to collapse
8.1
pds6 said:
8.1
Click to expand...
Click to collapse
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
rootSU said:
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
Click to expand...
Click to collapse
Yes uninstalled drivers through Device Manager & did the restart through the settings as outlined there.
Will try to download google usb driver from here http://developer.android.com/sdk/win-usb.html#top
Edit: this driver installed correctly. Device now appears in device manager as Android Bootloader Interface (phone is at Fastboot screen)
rootSU said:
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
Click to expand...
Click to collapse
Wow thank you, your thread suggestion was exactly what I needed. I did not know the difference between ADB & Fastboot.
Silly mistake but one that I couldn't solve through several hours of internet searches yesterday. Thanks for your time and insight, have a great day
Nexus 5 fixed
pds6 said:
Wow thank you, your thread suggestion was exactly what I needed. I did not know the difference between ADB & Fastboot.
Silly mistake but one that I couldn't solve through several hours of internet searches yesterday. Thanks for your time and insight, have a great day
Nexus 5 fixed
Click to expand...
Click to collapse
No probs. Glad you're sorted.

Update to Lollipop 5.1 [No Root/No Wipe/No Flashing/No Custom Recovery NEEDED !!!]

Hi,
Its been a long time since I got my nexus5 and decided not to do anything with it (root/flashing). I waited for Lollipop 5.0 & 5.0.1 OTA to reach my device. BUT, I couldn't wait until Lollipop 5.1 hit OTA to my device. So I decided to ahead and get that.
I didn't want to Wipe all data OR Root OR Flash custom ROMS OR Unlock the Bootloader (which anyways wipe all data). So, I read & searched for a way to get 5.1 OTA files installed. voila !! I found a way (most of u guys will know this. But thought would be great to share with you. ) adb & Sideload
First I downloaded the drivers & the latest Android SDK (Android Studio)
Then, Downloaded the appropriate OTA Image file & move it into Platform-Tools Folder. (have to match with current Build Number LRX22C/LRX210)
Enabled USB Debugging
Connect the device to PC
Checked if adb is running OK (*The best place to open a command prompt is from within the Platform-Tools in the SDK. Open command prompt as Administrator”)
type : adb devices
Click to expand...
Click to collapse
You should get a serial number followed by “device.”
015d182f9a0aac28 device
Click to expand...
Click to collapse
Reboot to the Bootloader
adb reboot bootloader
Click to expand...
Click to collapse
Use Volume Down on your device to until you see “Recovery.”
Select it with the Power button.
Your device will boot to an Android logo with a exclamation mark.
To jump past this, press Volume Up and Power at the same time.
You will now be in stock recovery.
With Volume Down, highlight “apply update from ADB.” Press Power to choose it.
Back to your PC, type the following command:
adb sideload <filename of update.zip>
Click to expand...
Click to collapse
If your adb is working properly, you should see the file transfer to your device in adb.
Once that finishes, your device will begin to update.
Once it has finished, simply reboot and enjoy the update.
OTA Files
Android 5.1 LMY47D from Android 5.0.1 LRX22C
Android 5.1 LMY47D from Android 5.0 LRX21O
Source
Happy Sideloading
haarsh said:
Hi,
Its been a long time since I got my nexus5 and decided not to do anything with it (root/flashing). I waited for Lollipop 5.0 & 5.0.1 OTA to reach my device. BUT, I couldn't wait until Lollipop 5.1 hit OTA to my device. So I decided to ahead and get that.
I didn't want to Wipe all data OR Root OR Flash custom ROMS OR Unlock the Bootloader (which anyways wipe all data). So, I read & searched for a way to get 5.1 OTA files installed. voila !! I found a way (most of u guys will know this. But thought would be great to share with you. ) adb & Sideload
First I downloaded the drivers & the latest Android SDK (Android Studio)
Then, Downloaded the appropriate OTA Image file & move it into Platform-Tools Folder. (have to match with current Build Number LRX22C/LRX210)
Enabled USB Debugging
Connect the device to PC
Checked if adb is running OK (*The best place to open a command prompt is from within the Platform-Tools in the SDK. Open command prompt as Administrator”)
You should get a serial number followed by “device.”
Reboot to the Bootloader
Use Volume Down on your device to until you see “Recovery.”
Select it with the Power button.
Your device will boot to an Android logo with a exclamation mark.
To jump past this, press Volume Up and Power at the same time.
You will now be in stock recovery.
With Volume Down, highlight “apply update from ADB.” Press Power to choose it.
Back to your PC, type the following command:
If your adb is working properly, you should see the file transfer to your device in adb.
Once that finishes, your device will begin to update.
Once it has finished, simply reboot and enjoy the update.
OTA Files
Android 5.1 LMY47D from Android 5.0.1 LRX22C
Android 5.1 LMY47D from Android 5.0 LRX21O
Source
Happy Sideloading
Click to expand...
Click to collapse
Well.. yeah... this is how sideloading is done with stock recovery.
Thanks anyways
Im running Win 8.1 and my pc does not recognize the phone as soon as it enters recovery and I can therefore not sideload the file. . Any trick to get this to work would be greatly appreciated.
TommyTheGun said:
Im running Win 8.1 and my pc does not recognize the phone as soon as it enters recovery and I can therefore not sideload the file. . Any trick to get this to work would be greatly appreciated.
Click to expand...
Click to collapse
Hi, Pls look into this guide.
Hope it helps
Isn't the sideload option in stock recovery (long time since I have seen it).
Seems you could just download it to your phone, enter stock recovery and sideload from there.
wangdaning said:
Isn't the sideload option in stock recovery (long time since I have seen it).
Seems you could just download it to your phone, enter stock recovery and sideload from there.
Click to expand...
Click to collapse
Hi, there is no sideload option in stock recovery as it seems. Device need to be connected to a PC and after selecting the option "apply update via adb" in recovey only can push the update zip
Sent from my Nexus 5 using XDA Free mobile app
not working.. i have completely stock nexus 5. running on win7. i instaled drivers. usb debugging enabled. when phone is normal running state and type adb devices, device is recognized and device manager in windows show
Android Composite ADB Interface
Click to expand...
Click to collapse
when enter adb reboot bootloader, device reset to fastboot and in system device manager show
Android Bootloader Interface
Click to expand...
Click to collapse
if enter to recovery or type adb reboot recovery (instead of adb reboot bootloader), device reset to recovery mode. but in this moment its disconnected from win completely and device manager not show any android device. offcourse when enter adb devices, device not show and adb sideload then not work. any ideas?
glirpi said:
not working.. i have completely stock nexus 5. running on win7. i instaled drivers. usb debugging enabled. when phone is normal running state and type adb devices, device is recognized and device manager in windows show
when enter adb reboot bootloader, device reset to fastboot and in system device manager show
if enter to recovery or type adb reboot recovery (instead of adb reboot bootloader), device reset to recovery mode. but in this moment its disconnected from win completely and device manager not show any android device. offcourse when enter adb devices, device not show and adb sideload then not work. any ideas?
Click to expand...
Click to collapse
Long ago, I had the exact same issues in Win7.
Clockwork's universal drivers fixed it for me.
You can find the links in this post
http://forum.xda-developers.com/showpost.php?p=59420668&postcount=322
my fault. everything is OK.
the 10th step
To jump past this, press Volume Up and Power at the same time.
Click to expand...
Click to collapse
not that clear. properly it should be: press power, then press volume up, release volume up and then release power if i try it push in same time, nothing happened.
then if show recovery menu and select apply update from ADB, new device in device manager is show
thank you!
need LMY47I OTA file
can u post the OTA for LMY47i like the one you posted for LMY47D
vaasbtech said:
can u post the OTA for LMY47i like the one you posted for LMY47D
Click to expand...
Click to collapse
Hi, What is your Device's Model (nexus 5 / nexus 6 etc)
Hello, my nexus's model number is LRX22C,
But here (https://developers.google.com/android/nexus/images) I can not find 5.1 image file for LRX22C.
Also when I check for updates it says my device has already last android version, but I'm on 5.0.1
Cool story bro
Conixcit said:
Hello, my nexus's model number is LRX22C,
But here (https://developers.google.com/android/nexus/images) I can not find 5.1 image file for LRX22C.
Also when I check for updates it says my device has already last android version, but I'm on 5.0.1
Cool story bro
Click to expand...
Click to collapse
Hi, LRX22C is not the model no. Its the Build Number Do you have a nexus 5 or any other ?
Sent from my Nexus 5 using XDA Free mobile app
Sent from my Nexus 5 using XDA Free mobile app
I get message "You need to have ADB version 1.0.32 or newer to sideload this device".
Found v32 online, downloaded, unzipped, put OTA file in that folder, followed your guide and boom, I`m now on 5.1 !!!!! I was so fed up waiting for Google to push 5.1 on my Nexus 5, but now I have it.
Thank you so much for such an easy tutorial.
haarsh said:
Hi, What is your Device's Model (nexus 5 / nexus 6 etc)
Click to expand...
Click to collapse
Its nexus 5 plz do post me the link
vaasbtech said:
Its nexus 5 plz do post me the link
Click to expand...
Click to collapse
Click here
Source : https://developers.google.com/android/nexus/images
Sent from my Nexus 5 using XDA Free mobile app
Bro need the OTA update file which was around 200mb which you have posted on the start of the page.I have downloaded this file earlier itself but don't know which file to copy and paste in platform-tools.
Sent from my Nexus 5 using XDA Free mobile app
This made my job very easy..... Thanks..
haarsh said:
[*]Back to your PC, type the following command:
Click to expand...
Click to collapse
I get ERROR: DEVICE OFFLINE

(soft)bricked my device. Is there a fix?

Hi all,
I installed the TWRP recovery for my mate 7 - 09 version, with lollipop 5.1. But then I unknowingly wiped something I shouldn't have: I think it was the system folder. No backups were made
My phone keeps starting up to the huawei logo and then reboots\turns off. I can get into fastboot&rescue mode, but that's it. No recovery, no 3-button fix (as far as I know).
The second problem is that I cannot get my device to be recognised by my pc. adb devices doesn't give me any results.
I don't feel like I can install the drivers properly as well. Pherhaps thats the problem? How can I do this? I have a driversetup from a mate7 download, but double clicking it doesnt show any prompts.
Anyone who can help me in any way is more than welcome!
dekraan said:
Hi all,
I installed the TWRP recovery for my mate 7 - 09 version, with lollipop 5.1. But then I unknowingly wiped something I shouldn't have: I think it was the system folder. No backups were made
My phone keeps starting up to the huawei logo and then reboots\turns off. I can get into fastboot&rescue mode, but that's it. No recovery, no 3-button fix (as far as I know).
The second problem is that I cannot get my device to be recognised by my pc. adb devices doesn't give me any results.
I don't feel like I can install the drivers properly as well. Pherhaps thats the problem? How can I do this? I have a driversetup from a mate7 download, but double clicking it doesnt show any prompts.
Anyone who can help me in any way is more than welcome!
Click to expand...
Click to collapse
Hey Buddy, here's what you can try to do:
1.) Boot connect your phone to your computer.
2.) Next, boot your phone to fastboot.
3.) Next, open command prompt from the folder where your ADB files are stored.
4.)On CMD type:
fastboot devices
5.) If your device appears then you have 2 options now. You can either:
a.) Flash Stock recovery.img or
b.) Flash back TWRP
6.) If choosing option a.) you can then save stock firmware within dload folder on your external sd card then force upgrade via 3 btn method.
7.) If choosing option b.) you can boot to twrp then either sideload a custom rom or try to save on your external sd and flash
blitzkriegger said:
Hey Buddy, here's what you can try to do:
1.) Boot connect your phone to your computer.
2.) Next, boot your phone to fastboot.
3.) Next, open command prompt from the folder where your ADB files are stored.
4.)On CMD type:
fastboot devices
5.) If your device appears then you have 2 options now. You can either:
a.) Flash Stock recovery.img or
b.) Flash back TWRP
6.) If choosing option a.) you can then save stock firmware within dload folder on your external sd card then force upgrade via 3 btn method.
7.) If choosing option b.) you can boot to twrp then either sideload a custom rom or try to save on your external sd and flash
Click to expand...
Click to collapse
I'll give that a try, thank you. With step 1, you just mean: connect the phone through usb to the computer, right?
When I rooted the phone, I did so on my work laptop, so I am hoping I can get it recognised there, but lets see what happens at home.
EDIT:
Ok, i've typed in fastboot devices, and it gave me one line with a 16-digit code (numbers and letters) some white space and then the word fastboot. What does that mean?
That should meen it recognizes your phone in fastboot mode. Next step is to flash as stated in step 5 that in the instructions.
Sent from my HUAWEI MT7-L09 using Tapatalk
dekraan said:
I'll give that a try, thank you. With step 1, you just mean: connect the phone through usb to the computer, right?
When I rooted the phone, I did so on my work laptop, so I am hoping I can get it recognised there, but lets see what happens at home.
EDIT:
Ok, i've typed in fastboot devices, and it gave me one line with a 16-digit code (numbers and letters) some white space and then the word fastboot. What does that mean?
Click to expand...
Click to collapse
EDIT AGAIN:
Ok, this is what I did. I downloaded the well known mate7 package, extracted the b119 tools folder and I put the twrp_2.8.7.0_mate7_5.1.img file from this forum (the TWRP for 5.1) inside this folder.
Then, I open cmd inside the folder, and I typed: fastboot flash recovery twrp_2.8.7.0_mate7_5.1.img. This is what happens:
target reported max download size of 471859200 bytes
sending 'recovery'(12644 KB)...
OKAY [ 1.302s]
writing 'recovery'...
OKAY [ 0.455s]
finished. total time: 1.756s
Now, I finally managed to get back into TWRP! I've only got 2% battery though (but I see a + which I think means charging...EDIT: yes, it is on 3% now. Better leave it like this...).
It tells me this:
TWRP has detected an unmodified system partition.
TWRP can leave your system partition unmodified to make it easier for you to take official updates. TWRP will be unable to prevent the stock rom from replacing TWRP and will not offer to root your device. Installing zips or performing adb operations may still modify the system partition.
I decided to swipe, to allow modifications.
So, I've got twrp back! For lollipop. This probably means I have to flash the lollipop rom? I will download the update.zip file next and put it on my sd card (using my pc and a microsd adapter...)
Keep you posted!
Ok, this is not working.
I put update.zip on my sd-card, and tried to install it. This is what I get:
Installing 'sd-ext/update.zip'...
checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:unknown command [errno]
file_getprop: failed to stat
E: error executing updater binary in zup 'sd-ext/update.zip'
Error flashing zip 'sd-ext/update.zip'...
Updating partition details...
...done
EDIT:
I tried to sideload but on my pc I get:
error: protocol fault (no status)
And on my TWRP I get:
You need adb 1.0.32 or newer to sideload to this device.
EDIT:
Updated my adb to 1.0.32 for windows, and rebooted everything. Now i'm at 6% of sideload. Hoping this will work!
EDITn the PC everything seems to go ok, but on my phone it says: E:Zip signature verification failed:1
What should I try next?
dekraan said:
Ok, this is not working.
I put update.zip on my sd-card, and tried to install it. This is what I get:
Installing 'sd-ext/update.zip'...
checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:unknown command [errno]
file_getprop: failed to stat
E: error executing updater binary in zup 'sd-ext/update.zip'
Error flashing zip 'sd-ext/update.zip'...
Updating partition details...
...done
EDIT:
I tried to sideload but on my pc I get:
error: protocol fault (no status)
And on my TWRP I get:
You need adb 1.0.32 or newer to sideload to this device.
EDIT:
Updated my adb to 1.0.32 for windows, and rebooted everything. Now i'm at 6% of sideload. Hoping this will work!
EDITn the PC everything seems to go ok, but on my phone it says: E:Zip signature verification failed:1
What should I try next?
Click to expand...
Click to collapse
I don't advise you to flash lollipop firmware first. It's more prudent to go back to kitkat first as I believe Lollipop needs kitkat as base
1.) Put stock kitkat update.app on dload folder of your memory card. Also make sure you have the LO9 stock kitkat recovery.
2.) With your phone connected to pc, go to twrp and reboot to bootloader.
3.) Once on bootloader open cmd on your tools folder then fastboot flash the stock kitkat recovery.
4.) Once done, fastboot reboot then force upgrade to install stock firmware.
5.) Once you have stock kitkat follow the drill to reach lollipop
blitzkriegger said:
I don't advise you to flash lollipop firmware first. It's more prudent to go back to kitkat first as I believe Lollipop needs kitkat as base
1.) Put stock kitkat update.app on dload folder of your memory card. Also make sure you have the LO9 stock kitkat recovery.
2.) With your phone connected to pc, go to twrp and reboot to bootloader.
3.) Once on bootloader open cmd on your tools folder then fastboot flash the stock kitkat recovery.
4.) Once done, fastboot reboot then force upgrade to install stock firmware.
5.) Once you have stock kitkat follow the drill to reach lollipop
Click to expand...
Click to collapse
Hi, thank you for your advice. I have but one question remaining: what stock kitkat update should I use? And where can I find the right recovery that goes with it?
I've tried several recovery_stock.img I found, and it does take away TWRP, so it might have done the trick. Only problem is that I cannot force upgrade to install whats on my sd-card....The phone keeps turning on (after a long push) and after seeing the logo for a little while, it turns off (short vibration)... Is there another way?
dekraan said:
Hi, thank you for your advice. I have but one question remaining: what stock kitkat update should I use? And where can I find the right recovery that goes with it?
I've tried several recovery_stock.img I found, and it does take away TWRP, so it might have done the trick. Only problem is that I cannot force upgrade to install whats on my sd-card....The phone keeps turning on (after a long push) and after seeing the logo for a little while, it turns off (short vibration)... Is there another way?
Click to expand...
Click to collapse
You should flash B137SP03 firmware. You can also refer to this guide:
http://forum.xda-developers.com/mate-7/help/5-1-to-4-4-2-bootloop-t3132888
1.)Prepare the Stock B137SP03 firmware on your SD card
2.)Download the fastboot.zip guide and extract it to a separate folder.
3.) next connect your phone to your computer and go to fastboot mode.
4.) Flash the boot.img and recovery.img you find on that guide.
5.) Once done, do the force upgrade with the B137 firmware.
blitzkriegger said:
You should flash B137SP03 firmware. You can also refer to this guide:
http://forum.xda-developers.com/mate-7/help/5-1-to-4-4-2-bootloop-t3132888
1.)Prepare the Stock B137SP03 firmware on your SD card
2.)Download the fastboot.zip guide and extract it to a separate folder.
3.) next connect your phone to your computer and go to fastboot mode.
4.) Flash the boot.img and recovery.img you find on that guide.
5.) Once done, do the force upgrade with the B137 firmware.
Click to expand...
Click to collapse
I've followed the guide you are reffering to. And I flashed the boot and recovery, and managed to get the roll back force installed. But for the life of me, I cannot get my phone to force install the B137 zip. I just can't get into force install mode. Are there tips or tricks? I am holding power up and down, and then press power untill I feel a short vibration. But all it does it show me the huawei logo screen and then shuts down again.
Very frustrating!
EDIT:
ok, I noticed that when my sd-card is not inserted, the phone easily boots into the force install mode. It shows the logo for a couple of seconds, screen goes black and then the force install loads. So this is what I did: insert the sd card half way, press vol up and down, and power on. Then after the logo when the screen goes black, insert the sd-card all the way and when the phone goes to force install mode, it can find the update!
Now installing.... hope this helps someone else out there!
Worked! And I am up and running again! Thank you for saving my mate
I got my Mate bricked and i've been trying to figure out how to solve it. I tried lots of things from different guides, but just an hour ago I found this guide and it worked! I can't tell you how happy I am right now, thanks guys!
aleksik said:
I got my Mate bricked and i've been trying to figure out how to solve it. I tried lots of things from different guides, but just an hour ago I found this guide and it worked! I can't tell you how happy I am right now, thanks guys!
Click to expand...
Click to collapse
Glad to hear both of you guys have your mates up and running again. As long as a phone turns on and is not dead as a brick there's always hope it can be restored
Hi everyone, I have the same problem with my mate 7, i was messing with unlocking bootloader(which I succesfully have done), couldn't get my phone rooted so installed TWRP recovery for Lollipop(which was already installed when i bought the phone). Ended up with soft bricked phone(no OS, no recovery at all).
I tried different tutorials how to fix it, none of them worked(including that one unfortunatelly).
I have taken some pictures to show you what the problem is but cannot post them until reach 10 posts on forum
Basically, i can get into fastboot mode by holding volume down with power button. Windows and Hisuite don't recognise my device but in fastboot mode i can check devices connected. Typing "fastboot devices" i get "P6Q7M14A15008421 fastboot", which i guess is my device indeed.
After that i try flashing boot.img and recovery.img(which are reported OK). Then rebooting with 3 button(vol up and down, power) and Huawei logo screen appears for a bit and goes into white screen saying "rescue mode" and at the bottom: "Error Func NO: 10(FUNC_BOOT_RECOVERY) Error NO:2". Trying rebooting into recovery mode(vol up and power) it shows similar "recovery mode" screen but with different errors: "Error! Func NO:12(FUNC_LOAD_IOM3) Error NO:1".
That's it! It seems like i cannot flash my device successfully for some reason. What Windows version did you guys use?? I tried Win 8.0 and Win 10, maybe i should use older systems? Please help, i had my phone for a week only and broke it(
I can't help you much because I don't have enough knowledge about these kind of things.. I use Windows 7 and from my previous experiences I can say that working with Windows 8 can be frustrating. PS. I bricked my Mate 12hrs after buying it
muzammil84 said:
Hi everyone, I have the same problem with my mate 7, i was messing with unlocking bootloader(which I succesfully have done), couldn't get my phone rooted so installed TWRP recovery for Lollipop(which was already installed when i bought the phone). Ended up with soft bricked phone(no OS, no recovery at all).
I tried different tutorials how to fix it, none of them worked(including that one unfortunatelly).
I have taken some pictures to show you what the problem is but cannot post them until reach 10 posts on forum
Basically, i can get into fastboot mode by holding volume down with power button. Windows and Hisuite don't recognise my device but in fastboot mode i can check devices connected. Typing "fastboot devices" i get "P6Q7M14A15008421 fastboot", which i guess is my device indeed.
After that i try flashing boot.img and recovery.img(which are reported OK). Then rebooting with 3 button(vol up and down, power) and Huawei logo screen appears for a bit and goes into white screen saying "rescue mode" and at the bottom: "Error Func NO: 10(FUNC_BOOT_RECOVERY) Error NO:2". Trying rebooting into recovery mode(vol up and power) it shows similar "recovery mode" screen but with different errors: "Error! Func NO:12(FUNC_LOAD_IOM3) Error NO:1".
That's it! It seems like i cannot flash my device successfully for some reason. What Windows version did you guys use?? I tried Win 8.0 and Win 10, maybe i should use older systems? Please help, i had my phone for a week only and broke it(
Click to expand...
Click to collapse
Sounds like the wrong boot.img or recovery.img has been flashed. May I know what Mate 7 model you have and which Lollipop firmwre version your phone came last with?
Try to obtain boot.img and revoery.img for your lollipop version then flash that via fastboot
blitzkriegger said:
Sounds like the wrong boot.img -recovery.img has been flashed. May I know what Mate 7 model you have and which Lollipop firmwre version your phone came last with?
Try to obtain boot.img and revoery.img for your lollipop version then flash that via fastboot
Click to expand...
Click to collapse
My phone mt7-09l, european version 16gb. Came with lollipop 5.1 when I bought it but I think I have formatted it via twrp recovery so it shouldn't matter what boot and recovery version I am trying to flash, should it? I'll extract boot and recovery from b308 today andtry that, see if this works. If not, only thing I can try is using win7 and that's it really, no more possibilities
dekraan said:
I've followed the guide you are reffering to. And I flashed the boot and recovery, and managed to get the roll back force installed. But for the life of me, I cannot get my phone to force install the B137 zip. I just can't get into force install mode. Are there tips or tricks? I am holding power up and down, and then press power untill I feel a short vibration. But all it does it show me the huawei logo screen and then shuts down again.
Very frustrating!
EDIT:
ok, I noticed that when my sd-card is not inserted, the phone easily boots into the force install mode. It shows the logo for a couple of seconds, screen goes black and then the force install loads. So this is what I did: insert the sd card half way, press vol up and down, and power on. Then after the logo when the screen goes black, insert the sd-card all the way and when the phone goes to force install mode, it can find the update!
Now installing.... hope this helps someone else out there!
Click to expand...
Click to collapse
I'm stuck on this stage, no errors while flashing but no boot either. Shows logo then like a spark a bit of music and animation (1 sec maybe) and reboot, so on and on and on...
muzammil84 said:
My phone mt7-09l, european version 16gb. Came with lollipop 5.1 when I bought it but I think I have formatted it via twrp recovery so it shouldn't matter what boot and recovery version I am trying to flash, should it? I'll extract boot and recovery from b308 today andtry that, see if this works. If not, only thing I can try is using win7 and that's it really, no more possibilities
Click to expand...
Click to collapse
If you were on Lollipop when everything went sour, you should do what I did, thanks to advice from @blitzkriegger:
You should flash B137SP03 firmware. You can also refer to this guide:
http://forum.xda-developers.com/mate...tloop-t3132888
1.)Prepare the Stock B137SP03 firmware on your SD card
2.)Download the fastboot.zip guide and extract it to a separate folder.
3.) next connect your phone to your computer and go to fastboot mode.
4.) Flash the boot.img and recovery.img you find on that guide.
5.) Once done, do the force upgrade with the B137 firmware.
I used the full steps from the link in there: flashed the right boot and recovery through fastboot. Then I flashed the rollback zip from my sd-card, and then I flashed the B137 zip from my sd-card. I can't tell you more about it, obviously
brack11 said:
I'm stuck on this stage, no errors while flashing but no boot either. Shows logo then like a spark a bit of music and animation (1 sec maybe) and reboot, so on and on and on...
Click to expand...
Click to collapse
Been there, done that. Very frustrating! I've tried several things, none of which are probably the right way, but they worked for me. sometimes....
Can you get into stock recovery (vol+ and power)? What I tried several times was wipe cache, and then hold the powerbutton untill my phone turned off. That worked occasionally to get the device totally turned off. Then try to get to force update with your sd-card half way in, and flip it in totally when the logo dissapears and the screen is black. I also tried to shut down the constant starting up by going into fastboot/recovery mode and then holding power down. As long as it takes. Good luck! And hopefully someone can give you proper advice...

[Soft Brick] [Flash Stock] [Recovery] [ADB Driver] Yuphoria [Solution]

Soft Bricking ?
Phone starts and stuck on the Yu logo.
Hard Bricking?
Phone does not start even if the battery is full. Have to go to the service center.
[Note]
1.Make sure that you have 70-80% battery on your phone.
2.You need a PC and a USB cable to connect your phone to the PC.
3.Flashing the factory firmware will wipe all the data present in the internal memory. So, make a backup of that if you can.
[Required Downloads]
1.Download the flash tools.
2. Download the factory firmware (signed fastboot)
3. adb setup drivers.
4. Mirror for drivers manual install here.
5. You can use this tool performs various functions.
# [Install Adb Derives Manually]
1. First of all extract the downloaded file and save it in the computer.
2. Before installation you have to disable the "signature verification" in windows. In windowa 8 or 10 you can do it by going to advanced settings or you can google the way of disabling signature verification.
3. After that turn off the phone and connect it pressing vol up that it will boot in fastboot mode.
4. When you connect the phone go device manager and search for device connected showing error sign.
5. Now click on that device and check for deriver update.
6. Now select the deriver in computer not automatically and select all devices.
7. Now select "have disk"
8. Browse the folder where you had extracted the adb drivers.
9. Now select the drivers file and install.
10. Ignores the Warning and select "always allow"
11. When finished check the device again by connecting to computer in fastboot mode with usb.
# [Flash Factory Firmware]
Steps
1. Extract the flashtools zip in a new folder on the desktop.
2. Extract the factory firmware zip in the same folder and make sure that all of the flashtools files are also present.
3. Now, power off your phone. If you are stuck in a bootloop, then pull out the battery and reinsert it. (Do not switch on the phone.)
4. While pressing the Volume Up key, connect your phone to the PC with the help of a USB cable.
5. You should now see the fastboot logo on your device. If you did, leave the Volume Up key. (If you do not see the logo, retry the process.)
6. Now go to the folder where you extracted the flash tools and factory firmware and run the flash-all.bat by double clicking on it.
7. A command window will open and the flashing procedure will start. (Make sure that your device does not disconnect from your PC during the procedure.)
8. The command window will automatically close once the procedure is completed.
9. Disconnect your device and boot it up by pressing the Power button. The first boot might take around 5-10 minutes to complete.
Congrats!
# [Recovey Installation (Very Easy Method)]
Note
1. Phone must has unlocked bootloader.
2. It must be rooted.
Steps
1. Download the twrp.img file and place it into your phone storage.( you can choose any custom recovery)
2. Now download the app from playstore flashify
3. Now install it and open the app it will require permission for root access, allow the root access.
4. Now open the app and u can backup the current recovery.
5. Now select the "flash" menu and select the "recovry image" and choose the .img file from storage.
6. Then select yes for flashing warning and will says flashing recovery. After completion it will say flash completed.
7. Now select the option button on right top corner and select the reboot into recovery.
8. Now it will reboot into recovery.
Hit "Thanks" if found this thread helpful....​
Thanks for the solution...... it works well !!
Though my yuphoria was working perfectly fine, i wanted to factory reset my mobile for some reasons, which i was not able to do. Both soft and hard custom recovery options were not working (no recovery screen pop up, mobile boots and stuck at YU logo ), tried your solution and it worked.
Just one input for new users like me, where you have asked users to install adb drivers, i tried that part but on running the bat file, the device was not detected, hence had to add yuphoria device drivers from their official site, i am not able to paste the link here but file name is YUPHORIA_drivers-v1.0.zip, also USB debugging option needs to be turned on in developer option for this solution to work.
Rest all steps work exact as you explained.
Sahilsharma said:
Though my yuphoria was working perfectly fine, i wanted to factory reset my mobile for some reasons, which i was not able to do. Both soft and hard custom recovery options were not working (no recovery screen pop up, mobile boots and stuck at YU logo ), tried your solution and it worked.
Just one input for new users like me, where you have asked users to install adb drivers, i tried that part but on running the bat file, the device was not detected, hence had to add yuphoria device drivers from their official site, i am not able to paste the link here but file name is YUPHORIA_drivers-v1.0.zip, also USB debugging option needs to be turned on in developer option for this solution to work.
Rest all steps work exact as you explained.
Click to expand...
Click to collapse
Yup bro its difficult to set bootloader driver for yuphoria. But you can install it manually. But always remember to "disable driver signature verification" before installation and i will update the derivers link for manual installation if you message me the link.
will this work on unlocked bootloader
nickjones1007 said:
will this work on unlocked bootloader
Click to expand...
Click to collapse
"yup"... it will work. There is nothing to do with boot loader. It will flash the stock rom and boot-loader will get locked again. You have to unlock the boot-loader again if you want to flash custom rom again.
And i will get the official ota updates from YU as well ?
Sent from my YU5010 using Tapatalk
nickjones1007 said:
And i will get the official ota updates from YU as well ?
Sent from my YU5010 using Tapatalk
Click to expand...
Click to collapse
yep bro.. you will get the updates and i don't think you know that, there are no restrictions for unlocking/locking boot-loader of YU mobile. I mean the warranty not void if you unlock the boot-loader.
Thnx a lot bro and yeah i knw that ... Actually i'm gonna start installing roms so in case if it goes wrong i just a needed reliable method to get back on stock company's software ....
Thnx again bro
Sent from my YU5010 using Tapatalk
nickjones1007 said:
Thnx a lot bro and yeah i knw that ... Actually i'm gonna start installing roms so in case if it goes wrong i just a needed reliable method to get back on stock company's software ....
Thnx again bro
Sent from my YU5010 using Tapatalk
Click to expand...
Click to collapse
its reliable bro and worked for me when i screwed my phone. But note one thing that you should have installed the adb drivers properly on your computer. Anyway if u screwed up don't hesitate to discuss here.
When i start the flashall.bat the phone restarts and stuck back at the cyanogen logo..!
goudaniket said:
When i start the flashall.bat the phone restarts and stuck back at the cyanogen logo..!
Click to expand...
Click to collapse
Is driver properly installed? Or retry to download setup again if you have done right then
1. boot into bootloader
2. run bat file it will take some time. If all goes well then it will say about relocking of boot-loader.
3. seletct yes and restart.
4. you will see yu logo and it will take 10-15 minutes to load so stay calm! If it doesn't load then try again.
awesome... worked for me
maazkazi91 said:
awesome... worked for me
Click to expand...
Click to collapse
You can simply hit the thanks buttton bro
Can u remember me?
I can't root my YU 5010a
ankityu said:
I can't root my YU 5010a
Click to expand...
Click to collapse
I think you have issue with adb driver .. Is that resolved?
No man
...its still stuck in there..
ankityu said:
No man
...its still stuck in there..
Click to expand...
Click to collapse
Bro i hv updated the thread with steps to install adb drivers. Try it and then report if it works.
What is signed fastboot
ankityu said:
What is signed fastboot
Click to expand...
Click to collapse
Install it . these are the drivers.

please provide Step-by-step correct procedure to install cm 12.1 nightly on xperia l

hi folks!
from last three days onwards i have been trying to install cyanogenmod 12.1 on my xperia l.......but i got no look.......i used cyanogenmod nightly recovery and when i tried to update from sdcard(cm 12.1 nightly toashan),.........it came out with error installation error from dev/block/mmsd.1 /by-name/fotakernel.......incompatiable package....please provide step-by-step procedure for installing cyanogenmod 12.1 if possible screen shots please........
bharath94 said:
hi folks!
from last three days onwards i have been trying to install cyanogenmod 12.1 on my xperia l.......but i got no look.......i used cyanogenmod nightly recovery and when i tried to update from sdcard(cm 12.1 nightly toashan),.........it came out with error installation error from dev/block/mmsd.1 /by-name/fotakernel.......incompatiable package....please provide step-by-step procedure for installing cyanogenmod 12.1 if possible screen shots please........
Click to expand...
Click to collapse
You can flash nothing in CM recovery you need a new recovery.
If you're on stock ROM use this method
Download this file HERE.
Extract the the file in your computer and open the cmd in the folder by pressing shift+LMB and write the code:
Code:
fastboot flash boot boot.img
important:connect your phone to the computer in fastboot holding the vol+ and connect it.
Now you can press entre you have now CWM recovery .
Boot to recovery and flash CM12 then make a factory reset and boot to system .
If you're using a Lollipop ROM use this method
Just install this app here:
http://forum.xda-developers.com/xperia-l/development/app-recoveries-recovery-installer-t3187914
And give root then flash TWRP .
NOW you can install whatever you want:silly:
n78 shadow said:
You can flash nothing in CM recovery you need a new recovery.
If you're on stock ROM use this method
Download this file HERE.
Extract the the file in your computer and open the cmd in the folder by pressing shift+LMB and write the code:
Code:
fastboot flash boot boot.img
important:connect your phone to the computer in fastboot holding the vol+ and connect it.
Now you can press entre you have now CWM recovery .
Boot to recovery and flash CM12 then make a factory reset and boot to system .
If you're using a Lollipop ROM use this method
Just install this app here:
http://forum.xda-developers.com/xperia-l/development/app-recoveries-recovery-installer-t3187914
And give root then flash TWRP .
NOW you can install whatever you want:silly:
Click to expand...
Click to collapse
ok! but i cant understand "open the cmd in the folder by pressing shift+LMB"! i'm sorry. i'm a biginner! this question may seem so simple! but confusing for me
i can start cmd from the "run" in start button of win7. but it says, "fastboot" command seems meaningless!
I understand the mistake I made. booting started. and give this error:
FAILED <remote: command not allowed>
what is the problem?
PL.biologist said:
ok! but i cant understand "open the cmd in the folder by pressing shift+LMB"! i'm sorry. i'm a biginner! this question may seem so simple! but confusing for me
i can start cmd from the "run" in start button of win7. but it says, "fastboot" command seems meaningless!
I understand the mistake I made. booting started. and give this error:
FAILED <remote: command not allowed>
what is the problem?
Click to expand...
Click to collapse
Open the extracted folder and press shift + Right Mouse Button
Then chose "open a command window"
Edit: sorry for the mistake I wrote LMB it should be RMB
n78 shadow said:
Open the extracted folder and press shift + Right Mouse Button
Then chose "open a command window"
Edit: sorry for the mistake I wrote LMB it should be RMB
Click to expand...
Click to collapse
don't matter, I found it
what about the error????
FAILED <remote: command not allowed>
PL.biologist said:
don't matter, I found it
what about the error????
FAILED <remote: command not allowed>
Click to expand...
Click to collapse
Where did you get this error, while flashing?
Edit: if you have problems flashing via fastbooy there's easier method go here
http://forum.xda-developers.com/xperia-l/orig-development/cwm-recovery-installer-t2589320
And download the recovery installer on your computer and install CWM on your phone then you can flash CM12
Important make sure that your bootloader is unlocked
n78 shadow said:
Where did you get this error, while flashing?
Edit: if you have problems flashing via fastbooy there's easier method go here
http://forum.xda-developers.com/xperia-l/orig-development/cwm-recovery-installer-t2589320
And download the recovery installer on your computer and install CWM on your phone then you can flash CM12
Important make sure that your bootloader is unlocked
Click to expand...
Click to collapse
thanks so much. that worked.
after unlocking the bootloader, I used flashtool and flash in fastboot mode, without any error. but when phone rebooted went to cyanogenmod recovery menu! I choose to update via sd! and all thing were going OK. unfortunately, it failed! the error said that "this update is for c2105, c2104, taoshan, but your phone is." It seems it cant recognize my phone is c2105!
why this error ocured, and what should I do!
again thanks for your good solutions.
PL.biologist said:
thanks so much. that worked.
after unlocking the bootloader, I used flashtool and flash in fastboot mode, without any error. but when phone rebooted went to cyanogenmod recovery menu! I choose to update via sd! and all thing were going OK. unfortunately, it failed! the error said that "this update is for c2105, c2104, taoshan, but your phone is." It seems it cant recognize my phone is c2105!
why this error ocured, and what should I do!
again thanks for your good solutions.
Click to expand...
Click to collapse
this is a known bug of that buggy CM recovery... simply use one of the other available ones ( ONLY FLASH STUFF FOR OUR DEVICR )
Sent from my Xperia T using XDA Free mobile app

Categories

Resources