Database Develop

P7-L10 does not support NFC / Downgrade from EMUI 3.0 to EMUI 2.3 - OVER ADB (CMD)

My phone P7 - L10 does not support NFC and can not install the ROM dload way.
It all happened on the phone Huawei Ascend P7 - L10 !
After the test pointless to go from B135 emui2.3 for L10 to B604 emui3.0 for L07 I was able to return mysterious way back to B135 emui2.3 with three buttons method .
But I have a problem, I have not in the system settings NFC and when I run the application NFC which is pre-installed , so my phone reports that this device does not support NFC .
Furthermore, I can not install any ROM using the method of three buttons , or with the help of local update ( dload rom version )
I can only install zip ROM version via TWRP .
I tried flashing many recevery.img through ADB , but without success.
Always when install dload ROM installation FAIL message will pop up .
Now I have a custom rom se7en rom and I still have not NFC !
Someone please help ?
Thank you

jkmaxfli said:
My phone P7 - L10 does not support NFC and can not install the ROM dload way.
It all happened on the phone Huawei Ascend P7 - L10 !
After the test pointless to go from B135 emui2.3 for L10 to B604 emui3.0 for L07 I was able to return mysterious way back to B135 emui2.3 with three buttons method .
But I have a problem, I have not in the system settings NFC and when I run the application NFC which is pre-installed , so my phone reports that this device does not support NFC .
Furthermore, I can not install any ROM using the method of three buttons , or with the help of local update ( dload rom version )
I can only install zip ROM version via TWRP .
I tried flashing many recevery.img through ADB , but without success.
Always when install dload ROM installation FAIL message will pop up .
Now I have a custom rom se7en rom and I still have not NFC !
Someone please help ?
Thank you
Click to expand...
Click to collapse
first you cant flash huwai firmewire with twrp you neeed stock recovery....
dl the firmware you want (e.g 135) and put the dload file on your sd-card
extract the recovery img (from the firmeware) with "huawei update extractor"
flash this recovery img
go in recovery and flash the file...it should be work

xynewageyx said:
first you cant flash huwai firmewire with twrp you neeed stock recovery....
dl the firmware you want (e.g 135) and put the dload file on your sd-card
extract the recovery img (from the firmeware) with "huawei update extractor"
flash this recovery img
go in recovery and flash the file...it should be work
Click to expand...
Click to collapse
Hi
Thank you for your response and help, but unfortunately this method also does not work.
When I perform everything I need , what you write , still pop up message when I install the update - FAIL .
This method I have tried as first aid .

jkmaxfli said:
Hi
Thank you for your response and help, but unfortunately this method also does not work.
When I perform everything I need , what you write , still pop up message when I install the update - FAIL .
This method I have tried as first aid .
Click to expand...
Click to collapse
http://forum.xda-developers.com/ascend-p7/help/huawei-p7-bootloop-t2904049
have you try this?

xynewageyx said:
http://forum.xda-developers.com/ascend-p7/help/huawei-p7-bootloop-t2904049
have you try this?
Click to expand...
Click to collapse
This method is perfect super, its done, NFC is back on ma device !!!
Thanks very much man.:good::good::good:
----------------------------------------------------------------------------------
How to install entire firmware manually with fastboot commands.
Extract with "Huawei Extractor" tool images also: RECOVERY, BOOT, SYSTEM, CUST, USERDATA and CACHE.
Use this commands in ADB (CMD) :
"fastboot flash recovery recovery.img"
"fastboot flash boot boot.img"
"fastboot flash system system.img"
"fastboot flash cust cust.img"
"fastboot flash userdata userdata.img"
"fastboot flash cache cache.img"
When you are finished with flashing of all images, use "fastboot reboot" command to restart your phone.

jkmaxfli said:
This method is perfect super, its done, NFC is back on ma device !!!
Thanks very much man.:good::good::good:
----------------------------------------------------------------------------------
How to install entire firmware manually with fastboot commands.
Extract with "Huawei Extractor" tool images also: RECOVERY, BOOT, SYSTEM, CUST, USERDATA and CACHE.
Use this commands in ADB (CMD) :
"fastboot flash recovery recovery.img"
"fastboot flash boot boot.img"
"fastboot flash system system.img"
"fastboot flash cust cust.img"
"fastboot flash userdata userdata.img"
"fastboot flash cache cache.img"
When you are finished with flashing of all images, use "fastboot reboot" command to restart your phone.
Click to expand...
Click to collapse
no problem bro

P7-L10
jkmaxfli said:
This method is perfect super, its done, NFC is back on ma device !!!
Thanks very much man.:good::good::good:
----------------------------------------------------------------------------------
How to install entire firmware manually with fastboot commands.
Extract with "Huawei Extractor" tool images also: RECOVERY, BOOT, SYSTEM, CUST, USERDATA and CACHE.
Use this commands in ADB (CMD) :
"fastboot flash recovery recovery.img"
"fastboot flash boot boot.img"
"fastboot flash system system.img"
"fastboot flash cust cust.img"
"fastboot flash userdata userdata.img"
"fastboot flash cache cache.img"
When you are finished with flashing of all images, use "fastboot reboot" command to restart your phone.
Click to expand...
Click to collapse
hi
I did all things but after that my phone just restart frequently, so please advice me in this regards .
my phone is P7L-10 Vodafone
many thanks .
---------- Post added at 01:53 PM ---------- Previous post was at 01:46 PM ----------
jkmaxfli said:
This method is perfect super, its done, NFC is back on ma device !!!
Thanks very much man.:good::good::good:
----------------------------------------------------------------------------------
How to install entire firmware manually with fastboot commands.
Extract with "Huawei Extractor" tool images also: RECOVERY, BOOT, SYSTEM, CUST, USERDATA and CACHE.
Use this commands in ADB (CMD) :
"fastboot flash recovery recovery.img"
"fastboot flash boot boot.img"
"fastboot flash system system.img"
"fastboot flash cust cust.img"
"fastboot flash userdata userdata.img"
"fastboot flash cache cache.img"
When you are finished with flashing of all images, use "fastboot reboot" command to restart your phone.
Click to expand...
Click to collapse
hi
I did all things but after that my phone just restart frequently, so please advice me in this regards .
is it related to hardware issue or not ?
my phone is P7L-10 Vodafone
many thanks .

[GUIDE] Update stock rooted/modified rom to last 6.0 Marshmallow w/o losing your data

Requirements:
you need to have a pc with adb working
a stock firmware on your device (any)
unlocked bootloader
a working backup just in case
Pro:
you will not lose your data / application
Cons:
you will lose all system modification (root, busybox, custom kernel...)
you'll take all the risk of operation (I've tested on my device)
Guide:
some file names changes depending on version so please complete the {version_here} placeholder with the file you download
* prepend "sudo" on command line if you are on a Linux machine
download last version for your device here (if you want to root download the zip file in the section below to speed up the operations)
extract
extract image-{device_here}-{version_here}.zip in the same folder (no subdir)
command line* (or reboot device with vol down pressed):
Code:
adb reboot bootloader
command line*:
Code:
cd {your_path_here}
command line*:
Code:
fastboot flash bootloader bootloader-{device_here}-{version_here}.img
command line*:
Code:
fastboot reboot-bootloader
command line*:
Code:
fastboot flash radio radio-{device_here}-{version_here}.img
command line*:
Code:
fastboot flash system system.img
command line*:
Code:
fastboot flash boot boot.img
ONLY IF YOU FOUND A VENDOR.IMG IN THE ZIP command line*:
Code:
fastboot flash vendor vendor.img
command line*:
Code:
fastboot flash cache cache.img
command line*:
Code:
fastboot reboot
Now you have the lastest stock image and all your data.
Change recovery (TWRP) and root:
Note that we haven't flash the stock recovery, but during every boot of an unmodified system there's a script that do that (supersu usually deactive this behavior during install).
If you had TWRP installed and the SuperSU zip on your device, at the end of the above procedure you can boot directly from bootloader to recovery and go directly to last step:
download: TWRP image (twrp-{version_here}-{device_here}.img) for your device
download: chainfire SuperSU 2.71 on your device
command line*:
Code:
fastboot flash recovery twrp-{version_here}-{device_here}.img
alternatively you can keep the original recovery and use TWRP one time with
Code:
fastboot boot twrp-{version_here}-{device_here}.img
boot in recovery and flash supersu zip

working fine for me, all correct, thanks

Just tried with flash_all.bat. I'm getting the message "Can not generate image". How can I solve this, please?

Thank you, works like a charm!

Same here, cant flash system

There's not flash-all.bat in my steps (that delete you data!), can't give help about it sorry

i've gone your way, but i tried also the flash-all.bat with the -w switch, didnt work.

Tnx mate. Helped a lot

Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?

Sp0KI said:
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Click to expand...
Click to collapse
I think that all who has flashed the developer preview got an broken filesystem or the partitions missmatch.
Before i used the preview the -w update flag worked well to rebuild the partitions, now it didnt work anymore, tried all factory images don to 4.4

c3k said:
Requirements:
you need to have a pc with adb working
a stock firmware on your device (any)
a working backup just in case
Click to expand...
Click to collapse
so if i have twrp, before i have to return stock 5.0.1??
or i flash directly 5.1 over twrp?
tnx

chikess said:
I think that all who has flashed the developer preview got an broken filesystem or the partitions missmatch.
Before i used the preview the -w update flag worked well to rebuild the partitions, now it didnt work anymore, tried all factory images don to 4.4
Click to expand...
Click to collapse
I didn't flash the preview.

Sp0KI said:
I didn't flash the preview.
Click to expand...
Click to collapse
Hmm ok, but u got the same problems. So, in this way we had to wait for a flashable zip or maybe ota.

@c3k why do you mention to flash twrp while in steps above stock recovery is not included to flash... ? Doesn't that mean that custom recovery (twrp) is still on device?

Doesn't this require an unlocked bootloader, and not necessarily root, or am I confused?

Sp0KI said:
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Click to expand...
Click to collapse
Are you using the latest version for the fastboot.exe file?

foosion said:
Doesn't this require an unlocked bootloader, and not necessarily root, or am I confused?
Click to expand...
Click to collapse
This requires an unlocked bootloader. But, there are users like us who have rooted the stock ROM.
This guide is meant for the users who has unlocked bootloader with rooted stock ROM.
This guide will also work for phones with unlocked bootloaders with STOCK ROM(rooted or un-rooted).
efrant said:
Are you using the latest version for the fastboot.exe file?
Click to expand...
Click to collapse
I had faced the same issue while flashing LRX22C. It got fixed by rebooting the phone and switching the cable to a different USB port. Might work for him too.
PS: I have flashed the images from Linux.

In my case I guess all the issues are from a previous attempt to flash OptiPop ROM. The flashing process it's a little tricky to understand (with that F2FS file system). I remember that after flashed OptiPop and the phone didn't boot, I tried to restore to stock ROM and it was a lot of errors until it worked fine again.

efrant said:
Are you using the latest version for the fastboot.exe file?
Click to expand...
Click to collapse
I'm using the newest Minimal ADB.
The strange thing is, that i can flash the LRX22C system.img and all other new lmy47d files but not the lmy47d system.img.
I guess i'll wait for the OTA update and hope it works then.
Tried rebooting and switching port and usb cabel..

You actually don't need to manually install supersu or root. Flash the 5.1 images and then (after the first full boot) flash twrp.
Once you boot into twrp and exit out of it, you will be promoted with a message that your phone is not rooted, and you're asked if you want to install supersu. It's built into twrp.

[Q] How to flash 5.1 image?

Current: Unlocked, Rooted, TWRP, Custom Rom 5.0.1, Custom Kernel, Encrypted
Goal: Unlocked, Rooted, TWRP, Factory 5.1.0, Custom Kernel, Decrypted
How do I go from my current state to my goal?
Would the following steps be correct and shortest?
1) Flash factory image - Flash All
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
2) Disable encryption - Flash kernel, disable + wipe
http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
3) Install Root - SuperSU
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
4) Install TWRP
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
5) Install Custom Kernel
Is step 2 in the correct order? Do I perform the install and disable to eliminate all traces of decryption?
Step 5, do I flash the kernel via TWRP or use the kernel's app from the Google Store?

Bump

I was Stock 5.01. except rooted and decrypted.
Copied SuperSU.zip to my Nexus 6.
had all the .img files extracted and in the same folder as my fastboot.exe from the Android SDK (make sure you are at the latest).
Boot to bootloader.
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
Using a decrypted flagged 5.1 boot.img
fastboot flash boot de-cryptedboot.img
fastboot flash system system.img
fastboot flash cache cache.img
I reflashed twrp as well...couldn't remember if I had left it on or had flash to stock recovery after rooting.
fastboot flash recovery twrp-2.8.5.0.img
When that finished flashing I used the volume keys to move to "boot recovery" and pressed power.
Team Win Recovery came up and I installed SuperSU.zip
Rebooted...done. 5.1, unencrypted, rooted and kept all my data.

Where did you get the decrypted boot img from?

From this thread.
http://forum.xda-developers.com/showthread.php?t=2946715

does the ota zip file contain all the .img files.............
it looks like it does, but there not all named in the normal fashion..........
can this be clarified.......
what files are what?

They are all there. Bootloader and the radio are in the main zip file and the rest are in the zip that is inside the main zip file. Extract both zip files.

tcrews said:
They are all there. Bootloader and the radio are in the main zip file and the rest are in the zip that is inside the main zip file. Extract both zip files.
Click to expand...
Click to collapse
after seeing this post I realize your talking about the factory image (tgz) and not the OTA zip.........
I have now downloaded the image but I am sure this post was referring to the 5.1 ota zip.......

While upgrading from 6.01-7.0 crashed at 83% Now Stuck at Google logo image w/Unlock

Any help appreciated here, I have been searching the forums all morning, but haven't found the same issue as mine (lots of stuck at google ?'s but none from failed upgrade) last night I decided to take the plunge and update my N6 from build 6.0.1 (MOB31H, Oct 2016) to 7.0.0 (NBD90Z, Oct 2016)
I typically use the WugFresh NRT to upgrade via factory image. Last night I decided to give the OTA images a try.
Everything was going smoothly until I bumped my keyboard tray and my phone became disconnected while still flashing. It was almost done too.....it was at the point of flashing the system image and was interrupted at 83% and it failed install.
I then attempted to recover from this by flashing entire factory image for 7.0 but it doesn't seem to want to mount my device. I then tried to go back and flash 6.01 to device using the softbrick/bootloop function from the NRT toolkit. It seemed to partially work as the size of the word google on the screen changed during boot went smaller (so I assume the boot.img was able to flash?) but I am still stuck at the google logo with the unlock at the bottom. Bright side is device is bootloader unlocked.
If I try the recover from bootloop function on the NRT it seems to have trouble sending files to phone (goes through all the process just doesn't take it looks like it sending files but before each at beginning it doesn't seem to connect to device.
I can access bootloader, and recovery. In recovery I tried to wipe/cache (wipes but doesn't help), tried factory reset (wipes but still stuck at Google), tried to mount system through selecting via recovery and it fails.
Not sure which image I should try to flash now to recover 6.01 or 7.0 or if I can even recover from this? Any suggestions are appreciated.
When I first got my phone I did create a backup using the NRT but that was on I think 5.0 or 5.01 and I no longer have twrp installed, should I try putting twrp on it and restoring that back up? It was a long time ago and I am not sure if it will cause radio or boot img issues...since I have upgraded so far past without making another backup with a newer version.
I have read that some others with similar issues that were told to use the N beta to get a clean flash.....only issue is there is no longer a N beta for Nexus 6......it now only shows 7.01 for 6p, 5x, and pixel.
Should I try flashing twrp and a ROM? And after see if I can get to load that way then go back and flash stock image?
Any help or suggestions are appreciated.

On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit

Dirty_Jerz said:
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Click to expand...
Click to collapse
just a silly question really , can this work on on a locked bootloader /not rooted device ?

touns_j said:
just a silly question really , can this work on on a locked bootloader /not rooted device ?
Click to expand...
Click to collapse
This requires you unlock your bootloader. You will be installing a custom recovery. Root is not needed though.

wavechapter said:
This requires you unlock your bootloader. You will be installing a custom recovery. Root is not needed though.
Click to expand...
Click to collapse
alright , i thought twrp could be replaced with stock recovery

Dirty_Jerz said:
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Click to expand...
Click to collapse
Thank You Dirty_Jerz! I really appreciate the help.
I am now back up and running on 7.0!

Black screen problem

Hi, I've just rooted my Huawei P8 lite 2017 and I saw that the root had erased all the google apps and the keyboard from my phone. So I tried to install open gapps from the TWRP recovery mode and when I turned on my phone, I had a black screen with only the three virtual buttons at the bottom. So I tried to do a factory reset from the recovery mode and it didn't changed anything. Then I tried in the eRocovery with "Download latest version and recovery" but it didn't work neither; it says "Getting package info failed".
Can you help me to solve this problem ?? :crying::crying:

Bad idea to flash gapps on a stock ROM, you might need to flash system again via fastboot. Do you know what Firmware you had?

No, I don't know, I can only acces to the TWRP recovery mode and to eRecovery and it doesn't connect to my computer because I can access to "Debugging USB". Can you help me ?

Download Official Firmware update and install it via TWRP, and Thats all! If you what i can send you root method, Best Regards

Ok but I can't find any official firmware for Huawei P8 Lite 2017. If you where to find it, can you send it to me pls??

RootingPro-18 said:
Download Official Firmware update and install it via TWRP, and Thats all! If you what i can send you root method, Best Regards
Click to expand...
Click to collapse
I don't think its possible to flash official update with TWRP on this phone.

MobileTechArena said:
I don't think its possible to flash official update with TWRP on this phone.
Click to expand...
Click to collapse
What is your Build number?

I don't know, as I said, I can't access to anything on my phone.

Halec said:
I don't know, as I said, I can't access to anything on my phone.
Click to expand...
Click to collapse
In Witch Region You Live? EU? ASV?

In EU, more precisely in France if it's useful.

Halec said:
In EU, more precisely in France if it's useful.
Click to expand...
Click to collapse
Can you boot to fastboot (hold volume down button and connect to pc)? You can try to flash B110 Firmware. Download Huawei update extractor, and Extract Boot.img, Recovery.img and System.img from the Update.APP.
Download ADB drivers, instal and then open install directory an paste earlier extracted Boot.img, Recovery.img and System.img
Flash those via fastboot:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
.

MobileTechArena said:
Can you boot to fastboot (hold volume down button and connect to pc)? You can try to flash B110 Firmware. Download Huawei update extractor, and Extract Boot.img, Recovery.img and System.img from the Update.APP.
Download ADB drivers, instal and then open install directory an paste earlier extracted Boot.img, Recovery.img and System.img
Flash those via fastboot:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
.
Click to expand...
Click to collapse
Ok, thank you, I'll try.

MobileTechArena said:
Can you boot to fastboot (hold volume down button and connect to pc)? You can try to flash B110 Firmware. Download Huawei update extractor, and Extract Boot.img, Recovery.img and System.img from the Update.APP.
Download ADB drivers, instal and then open install directory an paste earlier extracted Boot.img, Recovery.img and System.img
Flash those via fastboot:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
.
Click to expand...
Click to collapse
It didn't work. But after that, I went on the recovery mode and did a factory reset and it worked. Thank you very much for helping me.