Database Users

Flashed TWRP as boot.img / Now it only goes to recovery HELP ME!!!

Hi people...
Everything was going so smoothly... bootloader unlock... root... some nice root apps... free paid games... and my p8 lite was just feeling so good... until... I flashed twrp with flashify under the name of boot.img... Am I stupid or what?! Now I can only get 2 scenarios... when i turn on the phone it goes directly to twrp. In twrp i get the option to go the bootloader screen... If I choose system it goes back to twrp... I can't get it to start. I downloaded the official tar.gz from emui site but I dont know how can I install it. PLEASE HELP... What should I do in this case?! I miss my baby...
Thanks in advance

You have to restore stock recovery in fastboot mode.

arviit said:
You have to restore stock recovery in fastboot mode.
Click to expand...
Click to collapse
How do I do that?! If I wanted to wipe my phone completely and re-install the OS would be better to do it using twrp or stock recovery?
Thank you very much

Sorry, i misunderstood. If you flashed twrp as boot.img, reflash stock boot in fastboot mode.

flash stock boot.img in fastboot mode
and then flash twrp as recovery
will be like this
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery TWRP.img
fastboot reboot
use the boot.img from stock rom and twrp image you downloaded

Oh no!
Now I made some serious **** to my baby... guess now i'll have to send it to huawei to fix it. I made a full wipe like if it was format c: in computers... everything is gone (i didnt had any personal data) it doesnt have OS even. But when I still had twrp i tried to flash boot.img and recovery.img and now when i start it goes directly to bootloader screen but saying "please update system again" and where it used to say phone unlocked it now says (in red letters):
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
I was able to get to eRecovery with usb connected but when i choose to download e install the new version it gives me the message "wifi starting failed".
It also does not get any instuction with fastboot. but hi suite starts when I connect it. Strange?!
What do you think? Should I send it to huawei? Or is it possible for me to make it work again?
Also tried UPDATE.APP function and all give me fail message.
I'm going crazy!!!! But I love to mess around with android... To me this is the android essence. Fortunately I have a lumia for when my baby doesnt work.loooool
Thank you all

I don't understand why you don't use fastboot. Everybody told you to use it. In our phone situation, without custom kernel or rom, twrp is for experimentation and you cannot mix things.

arviit said:
I don't understand why you don't use fastboot. Everybody told you to use it. In our phone situation, without custom kernel or rom, twrp is for experimentation and you cannot mix things.
Click to expand...
Click to collapse
Well, you warned me... but sometimes i do these kind of *****... So, in this situation you think it's better to send it or is there way to fix this.
By the way, when I enter huawei eRecovery and I get the option to download the firmware through wifi and it says wifi starting failed, is there any way to make this work? And to fastboot do we need to open cmd as administrator to make it work? Because if Hi suite detects the phone I should also be able to fastboot it right?
Thanks for your patience

Just use fastboot aand flash everything
Recovery
Boot
Systme
Cust

jabonloco said:
flash stock boot.img in fastboot mode
and then flash twrp as recovery
will be like this
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery TWRP.img
fastboot reboot
use the boot.img from stock rom and twrp image you downloaded
Click to expand...
Click to collapse
hello I have p8 lite unlocked and rooted, yesterday I wanted to install the TWRP 2.8.7. but I was wrong and I installed twrp for the p8 and not p8 lite.
When I go into recovery mode my phone locks that read huawey, I tried with fastboot command to delete the wrong recovery and install the right of the p8 lite but the result does not change, my phone locks that read huawey
i think The commands that you wrote and that I have quoted are also fine for my case, it's' true?
i have version firmware b133 which boot.img from stock rom?

Try to reflash stock boot.img too.

arviit said:
Try to reflash stock boot.img too.
Click to expand...
Click to collapse
but Ido the extraction of the boot.img from the update version b133?

Hi everyone!!
First of all, thanks to everybody who helped me with this situation.
I now am using my baby again as if it was new. I wiped him completely as i stated before and it was as easy as finding the right firmware (136a) and using the vol down + vol up + power button technique. I put the UPDATE.APP file inside a folder named dload in sdcard using other phone (with my p8 was impossible). After that rebooted the device, pressed those 3 buttons and the instalation started successfully.
I just cant explain how happy i was. I stayed 3 days without it.
After that I have been messing with fastboot so thanks to everyone who made me realize that i didnt need to do all of this, but well, A full wipe is always welcome.
Is there any custom kernel on the way for overclock my baby?

Please explain to me how do I put SOLVED in this thread as my problem is already solved...
Thanks

siul_lasc said:
Hi everyone!!
First of all, thanks to everybody who helped me with this situation.
I now am using my baby again as if it was new. I wiped him completely as i stated before and it was as easy as finding the right firmware (136a) and using the vol down + vol up + power button technique. I put the UPDATE.APP file inside a folder named dload in sdcard using other phone (with my p8 was impossible). After that rebooted the device, pressed those 3 buttons and the instalation started successfully.
I just cant explain how happy i was. I stayed 3 days without it.
After that I have been messing with fastboot so thanks to everyone who made me realize that i didnt need to do all of this, but well, A full wipe is always welcome.
Is there any custom kernel on the way for overclock my baby?
Click to expand...
Click to collapse
I also have same problem. Now i am going to try this. thank you very much.
---------- Post added at 02:22 PM ---------- Previous post was at 01:53 PM ----------
siul_lasc said:
Hi everyone!!
First of all, thanks to everybody who helped me with this situation.
I now am using my baby again as if it was new. I wiped him completely as i stated before and it was as easy as finding the right firmware (136a) and using the vol down + vol up + power button technique. I put the UPDATE.APP file inside a folder named dload in sdcard using other phone (with my p8 was impossible). After that rebooted the device, pressed those 3 buttons and the instalation started successfully.
I just cant explain how happy i was. I stayed 3 days without it.
After that I have been messing with fastboot so thanks to everyone who made me realize that i didnt need to do all of this, but well, A full wipe is always welcome.
Is there any custom kernel on the way for overclock my baby?
Click to expand...
Click to collapse
Yeah finally my phone is working now thanks to you I searched many treads and forums but i cant find a solution. But finally i got an easy solution Thank you again bro.. Good Luck !!!:good::good::good::good::good::good::good:

Just download your firmware version, use huawei extractor to extract boot.img,cust.img,recovery.img and system.img
After that,download mininal adb fastboot copy you files into fastboot folder , enter fastboot mode on your phone and from fastboot folder,open cmd and type these commands:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
After this your phone will boot normally. Once you've done this, copy update.app to your sdcard or internal and install it by local update. Once you've done all this,your phone is fine.

May I know how do you wipe your internal storage? and what if after wiping, im unable to get into recovery mode? does it mean phone is not usable anymore?

SOLUTION
Hello. I'm the bigest mess on androids but i know that flashing stock recovery can remove any TWRP/CWR. If its too powerfull flash stock boot and run fastboot -w.(fastboot -w erases all PERSONAL data)

Guys Help me in this
guys help me
http://forum.xda-developers.com/honor-7/help/stock-emui-recovery-image-lost-twrp-t3442021

thank you !!
VladHD said:
Just download your firmware version, use huawei extractor to extract boot.img,cust.img,recovery.img and system.img
After that,download mininal adb fastboot copy you files into fastboot folder , enter fastboot mode on your phone and from fastboot folder,open cmd and type these commands:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
After this your phone will boot normally. Once you've done this, copy update.app to your sdcard or internal and install it by local update. Once you've done all this,your phone is fine.
Click to expand...
Click to collapse
After days of searching the internet i couldnt find any working solution. then i tried the local update without flashing al those .img's. ( didnt work )
Now after flashing al those .img's my phone works again but its a whole different phone. Only problem is when i try to update him with the update.app file it won't go any further then 5%.
If you know why this happens let me know
Further i wanna thank you one last time .. thank you

Help with bootloop

Hi,
I did search, but I didn't find any solution to the issue. I got the Nexus 6P 64 GB.
I unlocked my bootloader using the 6p Multitool. Thereafter I used my normal method of fastboot (Minimal ADB) to flash the boot.img from this thread http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344.
After that I flashed TWRP. Basically I followed the instructions here: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928.
But my phone is not booting up.
It gives me this error:
Your device software cannot be checked for corruption. Please lock the bootloader."
But I tried that and it doesn't work. I tried from fastboot restoring to factory, but get the same message.
Please help me!

Did you check the enable oem unlocking in developer settings?
Sent from my Nexus 6P using Tapatalk

Yes. As I said, I achieved the unlock. Now I just can't get back into my phone or recovery or anything other than fastboot (where it says unlock)

isn't "Your device software cannot be checked for corruption. Please lock the bootloader." the new msg on boot when you are unlocked, and you have to wait ~10 secs before it startup ?

After that, I'm stuck on the Google screen. It just goes on and on. Left it for over 20 minutes at one point and it didn't get past it.
Edit: The multicolored animated google screen. The animation just keeps going and going.

Del.

Your issue might be due to the encryption of the phone. Take a look at this thread: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976
From this thread:
NOTE: Decrypting data is not supported yet. The Nexus 6P will normally attempt to encrypt the device automatically on first boot. To use TWRP as you normally would, you will have to format data and install a slightly modified boot image with forceencrypt disabled. My Nexus 6P should arrive tomorrow and I will start working on decrypt once I get my hands on it.
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

Read through that thread. Part of the issue is that I don't know which variant (MDA89D & MDB08K) I have, or how to find that out seeing as I can't boot into the phone.
If I have the variant I may be able to fix this through the unified toolkit (though I'm not sure of that)

Did you ever fix this?

Try flashing the factory image and starting from scratch. You must have messed up somewhere. Re-download the boot.img from Chainfire's thread, maybe that was corrupt or something.

1. Download the MDB08K factory image (it's not a variant, it's a Marshmallow update) and unzip it.
2. Download the MDB08K boot.zip from Chainfire's modified boot.img thread
3. Download latest SuperSU beta zip
Wipe phone in TWRP, to include format data.
In bootloader, fastboot flash MDB08K
fastboot flash modified boot.img (from zip)
In TWRP, ADB sideload SuperSU
Reboot and it should perform normally.

kibmikey1 said:
1. Download the MDB08K factory image (it's not a variant, it's a Marshmallow update) and unzip it.
2. Download the MDB08K boot.zip from Chainfire's modified boot.img thread
3. Download latest SuperSU beta zip
Wipe phone in TWRP, to include format data.
In bootloader, fastboot flash MDB08K
fastboot flash modified boot.img (from zip)
In TWRP, ADB sideload SuperSU
Reboot and it should perform normally.
Click to expand...
Click to collapse
Thank you for your reply, but I can't get into TWRP either!! Any way for me to restore to factory or do the repairs from in flashboot without the restore?

I ran into the same issue last night trying to install TWRP. I'm still not sure how to get around it but I did get my phone back. you should be able to get to the bootloader (hold the power button until phone turns off, then hold vol up+vol down+power) once there use ADB fastboot to go back to stock.
this link will walk you through what you need. follow step 7.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
here it is as well:
How To Flash The Factory Images (And Return To Stock)
Prerequisites: unlocked bootloader (section 1).
Download the appropriate factory images for your model here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-01.31.img
radio-angler-angler-01.29.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-01.31.img
cache.img
radio-angler-angler-01.29.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-01.31.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-m8994f-2.6.28.0.65.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash userdata C:\angler\images\userdata.img
fastboot flash vendor C:\angler\images\vendor.img

Thank you. I was eventually able to do tysonwald's suggestion. First I didn't know what my version was, so I couldn't.
At some point I was able to get into the phone with constant gapp errors, check it.
Now my phone is unlocked and rooted. But when I go to settings to security (and when I tried to set up my fingerprint) settings crashes. Any ideas?
There was still some issue. I wiped the phone with the above method again, did NOT set up twrp/root, and everything works. It was something about the custom boot image I guess. Any advice if I want to try to set it up again?

Problem solved. Needed to update to newer image before doing everything. Issue resolve from Heisenberg's thread. Thank you all!

I had the same damn issue last night. Thise bootleg instructions had me flashing build k boot.img on build D. Maybe i wasnt paying attention lol!

I have a very similar problem, I flashed the k boot img. and now I'm stuck in an endless bootloop any idea?

TeriusPR said:
I have a very similar problem, I flashed the k boot img. and now I'm stuck in an endless bootloop any idea?
Click to expand...
Click to collapse
Read thru this guide and follow the instructions to the T. http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

I had a similar issue just now where my phone got stuck at the TWRP logo. Selecting the reboot option in download mode refused to remove it. I had to follow step 10 to get my phone back to stock. I'm afraid to try this again now

Is there anyway to know which version do i need to download? i bought the phone already bricked and i am trying to bring it back to life

[Help Needed]P8 Lite brick?

So i recently bought a p8 lite and i rooted it. Later that day i factory reseted it and now it is not working properly (see the video)
Do you guys know what to do?
https: //www . youtube. com /watch?v=jRGSHvg39BA

finniebox said:
So i recently bought a p8 lite and i rooted it. Later that day i factory reseted it and now it is not working properly (see the video)
Do you guys know what to do?
https: //www . youtube. com /watch?v=jRGSHvg39BA
Click to expand...
Click to collapse
Try this
1. download your rom (update.app) extract with huawei extractor (boot, recovery,cust, system)
2 install adb drivers and img and put both into a folder
3 in the folder shift+left click open window cmd
4 power on your phone on bootloader (volume up+power) (your device should bootloader unlocked, if you not, sorry, i cant help).
5 in a window command write fastboot flash boot boot.img
fastboot flash recovery recovery.img
Fastboot flash cust cust.img
fastboot flash system system.img
fastboot reboot
your device reboot sucefully that's all , I hope and serve you
sorry for my poor english :V

creas1587 said:
Try this
1. download your rom (update.app) extract with huawei extractor (boot, recovery, system, )
2 install adb drivers and img and put both into a folder
3 in the folder shift+left click open window cmd
4 power on your phone on bootloader (volume up+power) (your device should bootloader unlocked, if you not, sorry, i cant help).
5 in a window command write fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
your device reboot sucefully that's all , I hope and serve you
sorry for my poor english :V
Click to expand...
Click to collapse
My build number is ALE-L21C432B183 and i cant find the rom for that anywhere, do you have one?

finniebox said:
My build number is ALE-L21C432B183 and i cant find the rom for that anywhere, do you have one?
Click to expand...
Click to collapse
Dah! Cualquier rom sirve, baja la b170, la open market

I fixed it

Wiped off everything,only TWRP left,what do?[Huawei P10 Lite]

I accidentally wiped off everything with TWRP.
I have no backups.
I'm really having trouble finding ANY rom for this phone,custom or stock.
I've only found firmware that can update my OS not install it completely.
Could anyone find the correct ROM for me?
Anything will do.
Please help!

If you have a second device, donwload Huawei firmware finder from Play store. Enter your model number and donwload a full package. Doesn't really matter which one. Then just flash it in TWRP without extracting.

Vinnipinni said:
If you have a second device, donwload Huawei firmware finder from Play store. Enter your model number and donwload a full package. Doesn't really matter which one. Then just flash it in TWRP without extracting.
Click to expand...
Click to collapse
Is there any way to know my exact phone model number without having access to the OS?
Using the pc version I have to enter some kind of G and F values,what should i put in there?
EDIT:I've narrowed it down to WAS-LX1 and WAS LX1A,any way of distinguishing between those?
EDIT 2 : I seem to fail to flash literally any ROM,I get a zip verification error if i try to check that,if not I just get:
Updater process edned with ERROR : 9,and E: unknown command [errno] before that

Justkill43 said:
Is there any way to know my exact phone model number without having access to the OS?
Using the pc version I have to enter some kind of G and F values,what should i put in there?
EDIT:I've narrowed it down to WAS-LX1 and WAS LX1A,any way of distinguishing between those?
Click to expand...
Click to collapse
Shouldn't your phone model number be beneath the battery?

Michael24884 said:
Shouldn't your phone model number be beneath the battery?
Click to expand...
Click to collapse
Well yeah,it should.
But this is one of those phones that can't really be opened with special tools that I don't really have,and even if i did have them I wouldn't mess with the phone's insides because it's one of those types of phone....

Update:It may have something to do with the roms i have downloaded,I've tried 3 of them and none of them had ANY .img files
No boot.img no recovery.img etc,what am I doing wrong?

Justkill43 said:
Update:It may have something to do with the roms i have downloaded,I've tried 3 of them and none of them had ANY .img files
No boot.img no recovery.img etc,what am I doing wrong?
Click to expand...
Click to collapse
Huawei uses some special archiving, there should be an UPDATE.APP inside the downloaded files. You need a tool called Huawei Update Extractor to get the .img files.

Vinnipinni said:
Huawei uses some special archiving, there should be an UPDATE.APP inside the downloaded files. You need a tool called Huawei Update Extractor to get the .img files.
Click to expand...
Click to collapse
Oh I see,and should I just get the .imgs out of the update.app and then flash the rom?
Because so far I can't flash any of them,I get these errors:
E: unknown command [errno]
And
Updater process ended with ERROR : 9

Justkill43 said:
Oh I see,and should I just get the .imgs out of the update.app and then flash the rom?
Because so far I can't flash any of them,I get these errors:
E: unknown command [errno]
And
Updater process ended with ERROR : 9
Click to expand...
Click to collapse
What did you type?
Ohh and where are you from?

Vinnipinni said:
What did you type?
Ohh and where are you from?
Click to expand...
Click to collapse
What did i type??
Serbia.

Justkill43 said:
What did i type??
Serbia.
Click to expand...
Click to collapse
Yeah, mean the fastboot command you used

Vinnipinni said:
Yeah, mean the fastboot command you used
Click to expand...
Click to collapse
Kinda confused now,as I don't think I've used any fastboot commands at all.

Justkill43 said:
Kinda confused now,as I don't think I've used any fastboot commands at all.
Click to expand...
Click to collapse
If you want to flash the .img files, you have to enter your Bootloader. Do this by booting TWRP and type adb reboot bootloader. Then, out the .img files into the adb/ fastboot folder and type
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cust cust.img
Instead of system.img you need to use the exact filename of the system.img file. I think you need to only use these three commands, but I'll have another look.
Edit: you could also replace your current recovery and then try to flash the update file with the stock recovery. Do this by typing fastboot flash recovery recovery.img

Vinnipinni said:
If you want to flash the .img files, you have to enter your Bootloader. Do this by booting TWRP and type adb reboot bootloader. Then, out the .img files into the adb/ fastboot folder and type
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cust cust.img
Instead of system.img you need to use the exact filename of the system.img file. I think you need to only use these three commands, but I'll have another look.
Edit: you could also replace your current recovery and then try to flash the update file with the stock recovery. Do this by typing fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Oh so I should just flash those 3 imgs instead of the whole zip?
Also there is no cust.img
I'll list all the imgs here so you can see what i should be able to flash:
-Boot
-Crc.img
-Curver.img
-DTS.img
-EFI.img
-FASTBOOT.img
-FW_HIFI.img
-FW_LPM3.img
-MODEM_FW.img
-PACKAGE_TYPE.img
-PRODUCT.img
-RECOVERY.img
-RECOVERY2.img
-SENSORHUNB.img
-SHA256RSA.img
-SYSTEM.img
-TEEOS.img
-TRUSTFIRMWARE.img
-VENDOR.img
-VERLIST.img
-XLOADER.img

Justkill43 said:
Oh so I should just flash those 3 imgs instead of the whole zip?
Also there is no cust.img
I'll list all the imgs here so you can see what i should be able to flash:
-Boot
-Crc.img
-Curver.img
-DTS.img
-EFI.img
-FASTBOOT.img
-FW_HIFI.img
-FW_LPM3.img
-MODEM_FW.img
-PACKAGE_TYPE.img
-PRODUCT.img
-RECOVERY.img
-RECOVERY2.img
-SENSORHUNB.img
-SHA256RSA.img
-SYSTEM.img
-TEEOS.img
-TRUSTFIRMWARE.img
-VENDOR.img
-VERLIST.img
-XLOADER.img
Click to expand...
Click to collapse
Yes! You can't flash most of it, it's not possible.
Flash Boot, Recovery, System and Vendor. Of that doesn't work, Put the UPDATE.APP into the dload folder on your SD and hold Power, Volume + and Volume -. That should force the flash of the update.
And if that still doesn't work, ask for a TWRP update on the P10 Forums. Then Restore everything except Data.

Vinnipinni said:
If you want to flash the .img files, you have to enter your Bootloader. Do this by booting TWRP and type adb reboot bootloader. Then, out the .img files into the adb/ fastboot folder and type
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cust cust.img
Instead of system.img you need to use the exact filename of the system.img file. I think you need to only use these three commands, but I'll have another look.
Edit: you could also replace your current recovery and then try to flash the update file with the stock recovery. Do this by typing fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Alright,I'm getting the hang of this.
But what did you mean with the exact filename of system.img?How do i find that out?

Justkill43 said:
Alright,I'm getting the hang of this.
But what did you mean with the exact filename of system.img?How do i find that out?
Click to expand...
Click to collapse
Just the name of the file. Don't know if it's sytsem.img or SYSTEM.IMG

Vinnipinni said:
Just the name of the file. Don't know if it's sytsem.img or SYSTEM.IMG
Click to expand...
Click to collapse
Got it,flashed system,recovery and boot
Trying to flash vendor I get an error when it's trying to write vendor:
FAILED (remote:Command not allowed)
Still stuck in a boot loop.
I'm gonna put the update.app in the sdcard.
I just create a dload folder in the sd card,put it in,wipe off everything I've flashed and do the 3 button thing,right?

Vinnipinni said:
Just the name of the file. Don't know if it's sytsem.img or SYSTEM.IMG
Click to expand...
Click to collapse
UPDATE: Failed the 3 button thing,maybe I got the wrong ROM,i'll try it with another one,I have a question though
My friend has the same phone as me(p10 lite) and when he goes to about phone and checks out the model number he only sees WAS-LX1
I'm pretty sure i have that same model number now but I can't find a ROM that's specifically WAS-LX1,it's always WAS-LX1 And something added on there like WAS-LX1C02,should I even worry about that?

Vinnipinni said:
Yes! You can't flash most of it, it's not possible.
Flash Boot, Recovery, System and Vendor. Of that doesn't work, Put the UPDATE.APP into the dload folder on your SD and hold Power, Volume + and Volume -. That should force the flash of the update.
And if that still doesn't work, ask for a TWRP update on the P10 Forums. Then Restore everything except Data.
Click to expand...
Click to collapse
After trying the first 2 methods I can't even boot into twrp anymore,I'm super screwed...

[UPDATE][OTA]Huawei y7 trt-lx1 updates

Hi, since i got several updates for my device i thought i'd upload them in case you didn't got it by now.
Pulled them out of logcat.
Security Patches : september 2017
These are for TRT-LX1 C432 B100
INSTALL : rename to update.zip and put in intSD and update through settings ( adb sideload ....)
UPDATES :
TRT-LX1C432B140 : https://androidfilehost.com/?fid=817906626617946360
TRT-LX1C432B150 : https://androidfilehost.com/?fid=817906626617946370
TRT-LX1C432B160 : https://androidfilehost.com/?fid=673791459329061119
TRT-LX1C432B171 : https://androidfilehost.com/?fid=673956719939820453
don't just HIT&RUN....there's a :good: button for some reason

Do you have a full stock ROM for this device (or full nandroid backup)? Do you have a working port of TWRP?
We are trying to get TWRP going on an almost identical device, the Ascend XT2.

aslezak said:
Do you have a full stock ROM for this device (or full nandroid backup)? Do you have a working port of TWRP?
We are trying to get TWRP going on an almost identical device, the Ascend XT2.
Click to expand...
Click to collapse
Not yet - going to try to fastboot boot on twrp i found somewhere and pull firmware - keeping you updated

raystef66, want to try these TWRPs that enigma2446 created using your update.zips ?
Please let us know if they work!
steps:
adb reboot bootloader
fastboot flash recovery <imagename>.img
fastboot reboot
adb reboot recovery
enigma2446 said:
Sorry guys I'm an idiot, the recovery files are in update.app that has to be extracted as well.
Here's a couple more
https://drive.google.com/file/d/1fTc2nyKKO0ELjh2-FGxk03HX7Aw4k2qf/view?usp=drivesdk
https://drive.google.com/file/d/1eAwEAqrVnhxPKD4U-TcqfI2ILr37arLz/view?usp=drivesdk
Click to expand...
Click to collapse
raystef66 said:
Not yet - going to try to fastboot boot on twrp i found somewhere and pull firmware - keeping you updated
Click to expand...
Click to collapse

aslezak said:
raystef66, want to try these TWRPs that enigma2446 created using your update.zips ?
Please let us know if they work!
steps:
adb reboot bootloader
fastboot flash recovery <imagename>.img
fastboot reboot
adb reboot recovery
Click to expand...
Click to collapse
Yeah, haven't got the time to create one out of the zips.
But i'll look into it and let you know.
Btw, i'll not flash but BOOT and see if it's booting. Much safer
EDIT : NOT WORKING
I'll try to make one soon

Could you try booting the stock recovery from the update (update.app / RECOVERY.img)? I extracted using the Huawei update extract tool.
I'm not sure if this phone has some type of lock on booting a recovery (without flashing) ...
If it's easier for you, I've uploaded the extracted RECOVERY.img here:
http://www.filedropper.com/recovery-img
​
raystef66 said:
Yeah, haven't got the time to create one out of the zips.
But i'll look into it and elt you know.
Btw, i'll not flash but BOOT and see if it's booting. Much safer
EDIT : NOT WORKING
I'll try to make one soon
Click to expand...
Click to collapse

aslezak said:
Could you try booting the stock recovery from the update (update.app / RECOVERY.img)? I extracted using the Huawei update extract tool.
I'm not sure if this phone has some type of lock on booting a recovery (without flashing) ...
If it's easier for you, I've uploaded the extracted RECOVERY.img here:
http://www.filedropper.com/recovery-img
​
Click to expand...
Click to collapse
I've had that file for a while but haven't the time to make a new twrp for it as i'm always working on my axon 7
Anyway thnx for the effort :good:
I'll test it today and update you.
EDIT : cant fastboot boot stockrecovery.img too - hangs on booting...
Seems to be a problem there. Let's look into that.

Hello friends this update serves the Huawei y7 trt lx3. Thank you

Sheesh .. does "adb reboot recovery" work either?
I flashed mine so I have no idea if that works. If it doesn't work for you, and you never flashed it, we should also try to adb reboot recovery2 & see if that also fails.
Thanks again for your help.
raystef66 said:
I've had that file for a while but haven't the time to make a new twrp for it as i'm always working on my axon 7
Anyway thnx for the effort :good:
I'll test it today and update you.
EDIT : cant fastboot boot stockrecovery.img too - hangs on booting...
Seems to be a problem there. Let's look into that.
Click to expand...
Click to collapse

aslezak said:
Sheesh .. does "fastboot reboot recovery" work either?
I flashed mine so I have no idea if that works. If it doesn't work for you, and you never flashed it, we should also try to fastboot reboot recovery2 & see if that also fails.
Thanks again for your help.
Click to expand...
Click to collapse
You're welcome.
As a matter of fact, as i look into my updates i logcatted from my phone (see OP), the recovery.img of 140 and 150 are the same size : 59032 (as yours).
But the latest 160, has a size of 62592. Check for yourself. Strange...
Anyway, i cannot fastboot boot stockrecovery like said, neither size 140 neither 160 . What works is adb reboot recovery as it is standard.
Btw, there is no such command as fastboot reboot recovery imo. Only fastboot reboot or fastboot boot recovery (either for twrp or your stockrecovery)
Also, what do you mean with : you flashed yours....what did you flash ? and why would you flash your stock recovery as you're on stock
Explain what you have done so far because it's unclear what you're doing.

I flashed various TWRPs of similar models as my recovery, including the two links I had posted in this discussion. I flashed them because "fastboot boot recovery.img" doesn't seem to work on our devices.
I still have the stock recovery in partition "erecovery" so I can adb reboot erecovery, but if I adb reboot recovery, I get the blue power light and black screen.
It's good to know that "adb reboot recovery" works for you. In the update packages, the erecovery.img and recovery.img are exactly the same file, so that's expected. It must be that the erecovery for the Y7 2017 is different than the erecovery for the Ascend XT2 H1711 :crying:
raystef66 said:
You're welcome.
As a matter of fact, as i look into my updates i logcatted from my phone (see OP), the recovery.img of 140 and 150 are the same size : 59032 (as yours).
But the latest 160, has a size of 62592. Check for yourself. Strange...
Anyway, i cannot fastboot boot stockrecovery like said, neither size 140 neither 160 . What works is adb reboot recovery as it is standard.
Btw, there is no such command as fastboot reboot recovery imo. Only fastboot reboot or fastboot boot recovery (either for twrp or your stockrecovery)
Also, what do you mean with : you flashed yours....what did you flash ? and why would you flash your stock recovery as you're on stock
Explain what you have done so far because it's unclear what you're doing.
Click to expand...
Click to collapse

aslezak said:
I flashed various TWRPs of similar models as my recovery, including the two links I had posted in this discussion. I flashed them because "fastboot boot recovery.img" doesn't seem to work on our devices.
I still have the stock recovery in partition "erecovery" so I can adb reboot erecovery, but if I adb reboot recovery, I get the blue power light and black screen.
It's good to know that "adb reboot recovery" works for you. In the update packages, the erecovery.img and recovery.img are exactly the same file, so that's expected. It must be that the erecovery for the Y7 2017 is different than the erecovery for the Ascend XT2 H1711 :crying:
Click to expand...
Click to collapse
ok i understand.
True, most likely they are different as you could expect.
Nevertheless we need a twrp

aslezak said:
I flashed various TWRPs of similar models as my recovery, including the two links I had posted in this discussion. I flashed them because "fastboot boot recovery.img" doesn't seem to work on our devices.
I still have the stock recovery in partition "erecovery" so I can adb reboot erecovery, but if I adb reboot recovery, I get the blue power light and black screen.
It's good to know that "adb reboot recovery" works for you. In the update packages, the erecovery.img and recovery.img are exactly the same file, so that's expected. It must be that the erecovery for the Y7 2017 is different than the erecovery for the Ascend XT2 H1711 :crying:
Click to expand...
Click to collapse
I'm in the same situation, I had a bootloader loop going for a minute there. Managed to get out. If anyone figures out the twrp situation it would be greatly appreciated.
I'm not going to wait time with all the one click root apps, considering the only computer available is an app and it seems everything is meant for PC at the moment.

Nice work guys... I'm still waiting for this device but learning in advance... Thanks
Enviado desde mi X5max_PRO mediante Tapatalk

I'm waiting for twrp can't gain super user. I thought the phone would be an easy root.

Slygot said:
I'm waiting for twrp can't gain super user. I thought the phone would be an easy root.
Click to expand...
Click to collapse
Here!
https://forum.xda-developers.com/general/general/twrp-recovery-root-t3734325

astusal said:
Here!
https://forum.xda-developers.com/general/general/twrp-recovery-root-t3734325
Click to expand...
Click to collapse
I managed to get there and the files are no longer available in the tread. Link brings me to a 410 Gone error.
---------- Post added at 12:17 PM ---------- Previous post was at 12:15 PM ----------
Slygot said:
I managed to get there and the files are no longer available in the tread. Link brings me to a 410 Gone error.
Click to expand...
Click to collapse
Nevermind I am an idiot. Found it.

Do you have the full rom?

ashd999 said:
Do you have the full rom?
Click to expand...
Click to collapse
https://forum.xda-developers.com/general/general/twrp-huawei-y7-trt-lx1-trt-lx3-t3738002

I would really love a TRT_LX2 u seemed to get most of them but not my build ive rooted the phone but would love a trwrp for my build..
Moonlighter