Database Users

Xoom Stuck on red M!

Please help!!! After I was able to unlock my xoom and went reboot just before the adb remount command it just stays on the red M screen. I am able to get Starting RSD Protocol and Starting fastboot protocol at the top left but that is it. Also I have been able to connect with rsd lite but I dont have the sbf file and can't find it on the web anywhere. Please help!
Thanks in Advance

mhobbs82 said:
Please help!!! After I was able to unlock my xoom and went reboot just before the adb remount command it just stays on the red M screen. I am able to get Starting RSD Protocol and Starting fastboot protocol at the top left but that is it. Also I have been able to connect with rsd lite but I dont have the sbf file and can't find it on the web anywhere. Please help!
Thanks in Advance
Click to expand...
Click to collapse
If you are able to boot into Fastboot Protocol, you probably dont need rsd lite. You should be able to flash all of the files in the command prompt. Try re-locking your Xoom to see if that get you out of the soft brick. If it does, you can then try to unlock it again.
You can re-lock your Xoom by typing the following in the command prompt (while booted into fastboot protocol):
Code:
fastboot oem lock
Once you do this, follow the instructions on your Xoom's screen.
If it works, your Xoom should restart back into factory state once it's finished flashing the files.

I got it to lock back now I have Failed image LNX 0x0002 at the top??

Reboot in fastboot mode (power + vol up, after ~2 secs keep pressing vol-down repeadetly, until Fastboot appears; confirm selection with vol-up) and flash stock via fastboot
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
You may re-unlock your XOOM after successful update, re-root it, etc.

After the first line of code all I get is (cannot load 'system.img'). I really appreciate the help that I have gotten so far!
I now have managed to get it into CWM recovery... I am going to flash the rest of the steps in the universal root method.

Thanks again! I ended up reflashing the rom from CWM recovery and now I am rooted and back running! !!!

Im glad you were able to fix it.

Xoom wifi rooted but OEM locked again without any img files copied
I unlocked using fastboot oem unlock. But was trying to copy CM zip file using adb push. But I was getting stuck at fastboot screen where it says "starting fasboot protocol support" and nothing happens.
So I wiped /data and /cache
it did not help.
so I locked back again (fastboot oem lock). Now I am stuck with the message
Failed to boot LNX 0x0004
starting RSD mode 2
OneWire: Charger is connected....
Battery charge level: 92% (last two lines are irrelevant anyway)
SO I assume now that I dont have any image it wont boot normal. And since its locked I am not even able to get into fastboor or recovery which were installed correctly before.
help pls.
_TB_TB_ said:
Reboot in fastboot mode (power + vol up, after ~2 secs keep pressing vol-down repeadetly, until Fastboot appears; confirm selection with vol-up) and flash stock via fastboot
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
You may re-unlock your XOOM after successful update, re-root it, etc.
Click to expand...
Click to collapse
---------- Post added at 06:19 PM ---------- Previous post was at 05:54 PM ----------
I ca run fastboot command. fastboot reboot command does reboot the device. But then it comes back to the screen like this:
--> Fastboot
Starting Fastboot protocol support.
with the Red M in middle.
So I cam not able to run adb but can run fastboot commands. Due to this I can not copy the CM and flash using recovery.
I am able to get to recovery screen too by pressing volume down while rebooting.
But when I try adb push to copy the CM zip, it says error: device not found
Pl help. How do I get the CM zip to the device and run it using recovery (using clockwork).
sashykanth said:
I unlocked using fastboot oem unlock. But was trying to copy CM zip file using adb push. But I was getting stuck at fastboot screen where it says "starting fasboot protocol support" and nothing happens.
So I wiped /data and /cache
it did not help.
so I locked back again (fastboot oem lock). Now I am stuck with the message
Failed to boot LNX 0x0004
starting RSD mode 2
OneWire: Charger is connected....
Battery charge level: 92% (last two lines are irrelevant anyway)
SO I assume now that I dont have any image it wont boot normal. And since its locked I am not even able to get into fastboor or recovery which were installed correctly before.
help pls.
Click to expand...
Click to collapse
---------- Post added at 07:13 PM ---------- Previous post was at 06:19 PM ----------
Problem was I was using the wrong recovery image. Did not realize latest one does not work with xoom. Thanks. found the xoom recovery version in this forum.
sashykanth said:
I unlocked using fastboot oem unlock. But was trying to copy CM zip file using adb push. But I was getting stuck at fastboot screen where it says "starting fasboot protocol support" and nothing happens.
So I wiped /data and /cache
it did not help.
so I locked back again (fastboot oem lock). Now I am stuck with the message
Failed to boot LNX 0x0004
starting RSD mode 2
OneWire: Charger is connected....
Battery charge level: 92% (last two lines are irrelevant anyway)
SO I assume now that I dont have any image it wont boot normal. And since its locked I am not even able to get into fastboor or recovery which were installed correctly before.
help pls.
---------- Post added at 06:19 PM ---------- Previous post was at 05:54 PM ----------
I ca run fastboot command. fastboot reboot command does reboot the device. But then it comes back to the screen like this:
--> Fastboot
Starting Fastboot protocol support.
with the Red M in middle.
So I cam not able to run adb but can run fastboot commands. Due to this I can not copy the CM and flash using recovery.
I am able to get to recovery screen too by pressing volume down while rebooting.
But when I try adb push to copy the CM zip, it says error: device not found
Pl help. How do I get the CM zip to the device and run it using recovery (using clockwork).
Click to expand...
Click to collapse

Q| secure boot

Hello,
Ive got a phone from a customer saying it wont boot up, also said he just OTAed, It only enter bootloader mod (stuck on black screen when trying yo enter recovery).
It also says Secure Boot - enable
and I cant flash anything of course , What can I do to boot it up ?

is his bootloader unlocked?
---------- Post added at 01:09 PM ---------- Previous post was at 01:08 PM ----------
try and use this https://developers.google.com/android/nexus/images
---------- Post added at 01:09 PM ---------- Previous post was at 01:09 PM ----------
try and use this https://developers.google.com/android/nexus/images

theyau said:
is his bootloader unlocked?
---------- Post added at 01:09 PM ---------- Previous post was at 01:08 PM ----------
try and use this https://developers.google.com/android/nexus/images
---------- Post added at 01:09 PM ---------- Previous post was at 01:09 PM ----------
try and use this https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Its always locked, if I unlock the bootloader its automatically re-locking after reboot

Bump
any one has any idea please ?

deadwolf666 said:
Hello,
Ive got a phone from a customer saying it wont boot up, also said he just OTAed, It only enter bootloader mod (stuck on black screen when trying yo enter recovery).
It also says Secure Boot - enable
and I cant flash anything of course , What can I do to boot it up ?
Click to expand...
Click to collapse
Secure boot is enabled on all Nexus 4's, and you cannot disable it. By the way, Secure boot has nothing to do with the lock state of the bootloader -- it has to do with the secure boot chain of the AQP8064 chipset.
Unlock the booloader using "fastboot oem unlock" and then flash the factory images. See here.

If simply flashing factory images, an unlock should not be necessary. Is customer wanting you to try and preserve data?

efrant said:
Secure boot is enabled on all Nexus 4's, and you cannot disable it. By the way, Secure boot has nothing to do with the lock state of the bootloader -- it has to do with the secure boot chain of the AQP8064 chipset.
Unlock the booloader using "fastboot oem unlock" and then flash the factory images. See here.
Click to expand...
Click to collapse
Thanks for the answer but the wierd problem is that after I unlock the bootloader and try to flash any thing I get":
sending 'bootloader' (2188 KB)... FAILED (command write failed (Unknown error))
Click to expand...
Click to collapse
and after I reboot it shows that the bootloader is locked

I managed to boot into twrp recovery but no screen by "fastboot boot recovery.img" and I get adb access.
ant thing I can do from here ?

deadwolf666 said:
I managed to boot into twrp recovery but no screen by "fastboot boot recovery.img"
Click to expand...
Click to collapse
You are seeing a black screen because you are not using the correct command. It should be: fastboot -c "lge.kcal=0|0|0|x" boot recovery.img

efrant said:
You are seeing a black screen because you are not using the correct command. It should be: fastboot -c "lge.kcal=0|0|0|x" boot recovery.img
Click to expand...
Click to collapse
Thank you it helped abit
now I tryed twrp and it asked me for decryd pass, and cant mount any partition.
cwm can sideload but wipe will give errors (cant mount) and after reboot the bootloader is locked againg and wont boot.
stock just reboots.
can it be HW ? or any other solution ?
btw where did you learend this switch and where can I read about it ? "lge.kcal=0|0|0|x"
Thanks again

deadwolf666 said:
Thank you it helped abit
now I tryed twrp and it asked me for decryd pass, and cant mount any partition.
cwm can sideload but wipe will give errors (cant mount) and after reboot the bootloader is locked againg and wont boot.
stock just reboots.
can it be HW ? or any other solution ?
btw where did you learend this switch and where can I read about it ? "lge.kcal=0|0|0|x"
Thanks again
Click to expand...
Click to collapse
Two options before we decide it's hardware.
Procedure #1:
1) Download the LATEST version of fastboot.exe from here and extract it to C:\android.
2) Download the latest factory image from Google's dev page and verify the checksum with what is posted on the website.
3) Extract all the images from all the .tgz, .tar, .zip files within and put the 6 image files in C:\android
4) Reboot your device into the bootloader and plug into your PC.
5) Open a command prompt in that same directory and type the following commands:
Code:
fastboot oem unlock
fastboot reboot-bootloader
fasltboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
Does that work? If so then continue with flashing the radio, boot, system and recovery images. If not, then go to procedure number 2:
Procedure #2
Follow the instructions in this thread.
deadwolf666 said:
btw where did you learend this switch and where can I read about it ? "lge.kcal=0|0|0|x"
Thanks again
Click to expand...
Click to collapse
Have a look here.

efrant said:
Two options before we decide it's hardware.
Procedure #1:
1) Download the LATEST version of fastboot.exe from here and extract it to C:\android.
2) Download the latest factory image from Google's dev page and verify the checksum with what is posted on the website.
3) Extract all the images from all the .tgz, .tar, .zip files within and put the 6 image files in C:\android
4) Reboot your device into the bootloader and plug into your PC.
5) Open a command prompt in that same directory and type the following commands:
Code:
fastboot oem unlock
fastboot reboot-bootloader
fasltboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
Does that work? If so then continue with flashing the radio, boot, system and recovery images. If not, then go to procedure number 2:
Procedure #2
Follow the instructions in this thread.
Have a look here.
Click to expand...
Click to collapse
Procedure #1 is not working I get FAILED command write failed unknown error
Procedure #2 I tryed a few times on different pc (also different OS) and never got the software to recognize the phone (any way Ill try again and update)
thanks for the link will read it soon ^^

Cant make the NPST recognize the phone ;\
while booting custom recovery I cant mount any partition and the bootloader remains locked after reboot.
Any thing else to try ?

Do you have the OTA problem? (LFW73W recovery)

Do you have the OTA problem? (LFW73W recovery)
Let's see the % of Nexus 9 errors.
Problem
There is one problem with a lots of Nexus 9 what failed to apply correctly the new OTA (LRX21Q).
The problem seems to be that the first Nexus 9 OTA (LRX21L) failed to update the Recovery partition of Nexus 9, maintained the old version (LFW73W).
The fix?
This OTA can't be applied! There are two solutions:
Waiting until Google releasing another OTA. OTA RELEASED LRX21R from LRX21L - http://android.clients.google.com/p...is-LRX21R-from-LRX21L-factory-recovery-ok.zip
Unlock the bootloader (Erasing all data) and apply the full LRX21Q Factory Image.
Other stuffs
How too Enter in the recovery mode?
Put your device into the bootloader menu by either the following command or by holding down the power button and the volume down button while your Nexus is turned off.
Now use the volume down button twice until you have scrolled to Recovery mode, and press the power button to select it. It will look like your Nexus is restarting itself but an image of an Android with a red exclamation mark over it will appear. Next hold down the power button and press the volume up button, and you will be in recovery mode.
See it here -> https://www.youtube.com/watch?v=DuuSTnbQSlM (from 2:10 until 4:31)
How too apply the new Factory Image
Unlock the bootloader (will erase all data)
Download the factory image. Extract the .tar.gz then extract the zip too. You will have a folder that has 5 .img filesnin it. Flash one at a time with fastboot.
PHP:
fastboot devices
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot flash radio <radio file name here>.img (If exists)
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash cache cache.img (erase cache; not needed)
fastboot flash userdata userdata.img (If exists, erase user data; not needed)
fastboot reboot

How check the recovery version ?

fblasot said:
How check the recovery version ?
Click to expand...
Click to collapse
Put your device into the bootloader menu by either the following command or by holding down the power button and the volume down button while your Nexus is turned off.
Now use the volume down button twice until you have scrolled to Recovery mode, and press the power button to select it. It will look like your Nexus is restarting itself but an image of an Android with a red exclamation mark over it will appear. Next hold down the power button and press the volume up button, and you will be in recovery mode.

i have the problem but im waiting for #2..

#3 solution. Download the factory image. Extract the .tar.gz then extract the zip too. You will have a folder that has 5 .img filesnin it. Flash one at a time with fastboot.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
Then :
fastboot reboot
This is what worked for me.

I'm having the exact problem.
Sent from my Nexus 9 using Tapatalk

Cuzz1369 said:
#3 solution. Download the factory image. Extract the .tar.gz then extract the zip too. You will have a folder that has 5 .img filesnin it. Flash one at a time with fastboot.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
Then :
fastboot reboot
This is what worked for me.
Click to expand...
Click to collapse
Don't work if you have the bootloader locked. So is the same was #1.

Cuzz1369 said:
#3 solution. Download the factory image. Extract the .tar.gz then extract the zip too. You will have a folder that has 5 .img filesnin it. Flash one at a time with fastboot.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
Then :
fastboot reboot
This is what worked for me.
Click to expand...
Click to collapse
Thx Cuzz1369, flashed (unlocked/relocked bootloader) like you mentioned works like a charm. Running LRX21Q now.
Don't forget to enable "OEM unlock" in developer options otherwise unlocking/locking bootloader doesn't work.
>sent from my lollipopped Nexus 9<

Cuzz1369 said:
#3 solution. Download the factory image. Extract the .tar.gz then extract the zip too. You will have a folder that has 5 .img filesnin it. Flash one at a time with fastboot.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
Then :
fastboot reboot
This is what worked for me.
Click to expand...
Click to collapse
Worked perfectly. Thanks!

marcomsousa said:
Don't work if you have the bootloader locked. So is the same was #1.
Click to expand...
Click to collapse
Obviously......... Sigh

Cuzz1369 said:
#3 solution. Download the factory image. Extract the .tar.gz then extract the zip too. You will have a folder that has 5 .img filesnin it. Flash one at a time with fastboot.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
Then :
fastboot reboot
This is what worked for me.
Click to expand...
Click to collapse
Thanks for sharing these steps and thanks to the TS for creating this thread.
Now, is there an idiots version to this? I have never manually updated / flashed any device before.
I understand I can just wait for the OTA, but now that I have a Nexus device I'd love to learn how to do this.
I have already downloaded and unzipped the LRX21Q Factory Image, installed Minimal ADB and Fastboot from here, and enabled OEM unlocking in the developer options. What should I do next?
Also, is my understanding correct in that my data will be erased and my device factory reset if I perform this manual update and that future OTA updates will still work if I choose not to manually update down the road?

I have a bit of a problem if i flash all the stock img files manually ( this is not my first nexus ) but after reboot i still get the recovery error ?

marcomsousa said:
Put your device into the bootloader menu by either the following command or by holding down the power button and the volume down button while your Nexus is turned off.
Now use the volume down button twice until you have scrolled to Recovery mode, and press the power button to select it. It will look like your Nexus is restarting itself but an image of an Android with a red exclamation mark over it will appear. Next hold down the power button and press the volume up button, and you will be in recovery mode.
Click to expand...
Click to collapse
Every time i try this part "Next hold down the power button and press the volume up button, and you will be in recovery mode." i bounce back to the bootloader menu ?

Hogyoku said:
Every time i try this part "Next hold down the power button and press the volume up button, and you will be in recovery mode." i bounce back to the bootloader menu ?
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=DuuSTnbQSlM
See from 2:10 until 4:31

marcomsousa said:
https://www.youtube.com/watch?v=DuuSTnbQSlM
See from 2:10 until 4:31
Click to expand...
Click to collapse
Thanks that did the trick !

livinginavacuum said:
Thanks for sharing these steps and thanks to the TS for creating this thread.
Now, is there an idiots version to this? I have never manually updated / flashed any device before.
I understand I can just wait for the OTA, but now that I have a Nexus device I'd love to learn how to do this.
I have already downloaded and unzipped the LRX21Q Factory Image, installed Minimal ADB and Fastboot from here, and enabled OEM unlocking in the developer options. What should I do next?
Also, is my understanding correct in that my data will be erased and my device factory reset if I perform this manual update and that future OTA updates will still work if I choose not to manually update down the road?
Click to expand...
Click to collapse
Go to the folder with fastboot and adb. Unzip everything in that folder.
Shift + right click in the folder and open command prompt.
Type "adb devices" to make sure your device shows up.
Then type in commands mentioned above

Also had this problem, and option #3 worked for me. Thanks!

No problem here, am on 21Q and the LFW73W recovery

I'm starting to think I'm the only person in the world who hasn't received the ota update. Am I?

Nope, I don't have it yet either.

Le Pro 3 URGENT HELP Soft brick?

Hello, I am in dire need of assistance. I'm not sure what I did, but I think i soft bricked my Le Pro 3 LEX727. I was attempting to install a custom rom, I wiped Delvik,system,cache,data then proceeded to flash lineage. When I rebooted it quickled flashed Le Eco bootup then crashed or went to a black screen. Same thing with recovery, quickly flashes "Le Eco Recovery" then goes black. I can boot into Fastboot and the device shows up there, but when I attempt to do "fastboot oem unlock-go" I get "FAILED (remote: oem unlock is not allowed)". Please help me, I really need to fix my phone.
Sincerely,
A grateful person who messed up their phone.

It goes into recovery mode? power button + volume up button. redo the procedure and leaves everything in the options selected .. or I hope you made a backup beforehand, there are various discussions on how to recover

If you can access fastboot, youre golden. Just flash a stock rom

trizex said:
If you can access fastboot, youre golden. Just flash a stock rom
Click to expand...
Click to collapse
Can you help me out with where to go from there, or direct me to a thread? When I attempt to unlock oem so i can flash twrp it says "oem unlock is not allowed"
thank you very much.

Gynlemon said:
It goes into recovery mode? power button + volume up button. redo the procedure and leaves everything in the options selected .. or I hope you made a backup beforehand, there are various discussions on how to recover
Click to expand...
Click to collapse
No, it can only boot into fastboot.

Yewsif said:
No, it can only boot into fastboot.
Click to expand...
Click to collapse
https://forum.xda-developers.com/le-pro3/how-to/guide-to-install-stock-rom-custom-t3486600

Gynlemon said:
https://forum.xda-developers.com/le-pro3/how-to/guide-to-install-stock-rom-custom-t3486600
Click to expand...
Click to collapse
Thank you, but as I cant get into the devices OS, I cannot enable usb debugging and oem unlock. Only thing I can access is the fastboot menu.

Have you tried flashing the aboot file? from this thread
fastboot flash aboot emmc_appsboot.mbn
then
reboot
then
Fastboot mode using power-off + volume down.
then
fastboot oem unlock-go
then you can boot or flash into TWRP or whatever recovery

Joms_US said:
Have you tried flashing the aboot file? from this thread
fastboot flash aboot emmc_appsboot.mbn
then
reboot
then
Fastboot mode using power-off + volume down.
then
fastboot oem unlock-go
then you can boot or flash into TWRP or whatever recovery
Click to expand...
Click to collapse
No, I have not. What do you mean the aboot file.

Yewsif said:
No, I have not. What do you mean the aboot file.
Click to expand...
Click to collapse
http://newandroidbook.com/Articles/aboot.html

Joms_US said:
http://newandroidbook.com/Articles/aboot.html
Click to expand...
Click to collapse
Thank you for your time and help, but I have no idea what to do with that link, I understand the adb commands I need to put in. Is there anyway you can sort of walk me through it with steps?
Thank you.

You prolly have more experience than me so I am just pointing to you what I did to unlock the bootloader which seems to be the problem? ^_^
https://forum.xda-developers.com/showpost.php?p=71116203&postcount=8
I gave the instructions and link there already but here is the direct link that contains the aboot file.
https://www.androidfilehost.com/?fid=313042859668275431

joms_us said:
you prolly have more experience than me so i am just pointing to you what i did to unlock the bootloader which seems to be the problem? ^_^
https://forum.xda-developers.com/showpost.php?p=71116203&postcount=8
i gave the instructions and link there already but here is the direct link that contains the aboot file.
https://www.androidfilehost.com/?fid=313042859668275431
Click to expand...
Click to collapse
thank you so much, flashing the aboot file worked and made my custom rom run perfectly! I love you.

Yewsif said:
thank you so much, flashing the aboot file worked and made my custom rom run perfectly! I love you.
Click to expand...
Click to collapse
Thanks would be enough.

Joms_US said:
Have you tried flashing the aboot file? from this thread
fastboot flash aboot emmc_appsboot.mbn
then
reboot
then
Fastboot mode using power-off + volume down.
then
fastboot oem unlock-go
then you can boot or flash into TWRP or whatever recovery
Click to expand...
Click to collapse
I royally messed up my custom ROM install, this got me to boot again. Thank you.

This should be a sticky, or a part of any installation method. Why? If you upgrade to the latest official firmware (e.g. 21s+), your bootloader will no longer be unlocked with the oem unlock-go method. You *have* to flash this bootloader first so you can then unlock it and do all the other steps.

kaivorth said:
I royally messed up my custom ROM install, this got me to boot again. Thank you.
Click to expand...
Click to collapse
Glad this thread helped you.

Joms_US said:
Have you tried flashing the aboot file? from this thread
fastboot flash aboot emmc_appsboot.mbn
then
reboot
then
Fastboot mode using power-off + volume down.
then
fastboot oem unlock-go
then you can boot or flash into TWRP or whatever recovery
Click to expand...
Click to collapse
This works ! Thank you

Joms_US said:
Have you tried flashing the aboot file? from this thread
fastboot flash aboot emmc_appsboot.mbn
then
reboot
then
Fastboot mode using power-off + volume down.
then
fastboot oem unlock-go
then you can boot or flash into TWRP or whatever recovery
Click to expand...
Click to collapse
great thanks for you. I finally unbrick X727 with same way.

Huawei p8 lite stuck in rescue mode

Hi i have the problem, yesterday i tried to root the phone. I unlocked bootloader succefully but after root i got bootloop so i tried to wipe the data and reinstall stock ROM. And i think this is where i messed something up. After this my telefon just go to rescue mode with errors Func NO: 10 boot image and Error NO: 2 load image. But when i try to go to the recovery i have Func NO : 11 recovery image. Help me i am very sad. :C

halk15 said:
Hi i have the problem, yesterday i tried to root the phone. I unlocked bootloader succefully but after root i got bootloop so i tried to wipe the data and reinstall stock ROM. And i think this is where i messed something up. After this my telefon just go to rescue mode with errors Func NO: 10 boot image and Error NO: 2 load image. But when i try to go to the recovery i have Func NO : 11 recovery image. Help me i am very sad. :C
Click to expand...
Click to collapse
Try flashing stock ROM using fastboot
use Huawei update extractor select boot ,system,cust,recovery ,extract them and flash them with fastboot like this
fastboot flash system system.img
fastboot flash boot boot.img etc....
just make sure that you place those img files in same folder as adb is.
---------- Post added at 06:50 PM ---------- Previous post was at 06:46 PM ----------
halk15 said:
Hi i have the problem, yesterday i tried to root the phone. I unlocked bootloader succefully but after root i got bootloop so i tried to wipe the data and reinstall stock ROM. And i think this is where i messed something up. After this my telefon just go to rescue mode with errors Func NO: 10 boot image and Error NO: 2 load image. But when i try to go to the recovery i have Func NO : 11 recovery image. Help me i am very sad. :C
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2277112 check this if you dont know how to setup fastboot

Nikola6511 said:
Try flashing stock ROM using fastboot
use Huawei update extractor select boot ,system,cust,recovery ,extract them and flash them with fastboot like this
fastboot flash system system.img
fastboot flash boot boot.img etc....
just make sure that you place those img files in same folder as adb is.
---------- Post added at 06:50 PM ---------- Previous post was at 06:46 PM ----------
https://forum.xda-developers.com/showthread.php?t=2277112 check this if you dont know how to setup fastboot
Click to expand...
Click to collapse
Well, if i only could go into fastboot mode. I have only rescue mode (no fastboot and rescue). ADB don't see the phone.

halk15 said:
Well, if i only could go into fastboot mode. I have only rescue mode (no fastboot and rescue). ADB don't see the phone.
Click to expand...
Click to collapse
Seems like your boot image is damaged but check this thread maybe it helps https://forum.xda-developers.com/p8lite/help/stuck-rescue-mode-screen-please-help-t3244872

usually you should always get into fastboot mode. Turn off your phone, connect it to PC, press power and volume down, after screen turns on release the PowerButton and keep holding VolumeDown, until you are in fastboot mode. Then use fastboot to flash a new boot, recovery and system

Hello all,
I have a similar problem on my old P8 lite phone, but I can enter into fastboot mode. No idea how it turned out like this... I bought a P20 lite and stoped using P8 lite for several months. Some days ago, tried to use the phona and it was unresponsive. Wiped data and some more options, and the phone got stuck on rescue mode.
I've read this and other threads and tried to use fastboot to flash stock ROM again. I downloaded update file, extracted boot.img, system.img, cust.img and recovery.img but when I try, to start flashing boot.img I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot BOOT.IMG
target reported max download size of 471859200 bytes
sending 'boot' (22688 KB)...
OKAY ( 0.588s)
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.592s
When I enter fastboot & rescue mode I get the messagem "PHONE Locked" (green letters). What can I do to recover the phone?
TIA for your help.