Related
So I was an idiot, I've resigned myself to this fact because I've clearly done something wrong.
TWRP installed, rooted and booted.
Then I tried to flash a new ROM from here using TWRP and well... that's where things went tits up. Something in TWRP said in red about not being able to mount something. The loading screen was stuck and then it just bootlooped over and over again. I downloaded a stock ROM, wiped system and tried to flash but now it's stuck on the "your device is shifty" screen and I'm totally out of ideas...
Please refrain from pointing out what a moron I've been.
Thanks in advance to anyone who can save this wretched soul.
do you have access to bootloader with fastboot?
seeing a lot of threads like this around here. Don't want to offend you or anybody else but just that someone has said it: First thing you do after flashing TWRP is a backup :angel:
hope you get your things sorted though. Can your please provide a more detailed list of things you did? How did you try to flash the stock rom you downloaded? dload forced update? flashed in twrp? etc.
lomunet said:
do you have access to bootloader with fastboot?
Click to expand...
Click to collapse
I can still get in to bootloader and fastboot mode no problem.
seeing a lot of threads like this around here. Don't want to offend you or anybody else but just that someone has said it: First thing you do after flashing TWRP is a backup
hope you get your things sorted though. Can your please provide a more detailed list of things you did? How did you try to flash the stock rom you downloaded? dload forced update? flashed in twrp? etc.
Click to expand...
Click to collapse
Yeah I realised I should have done that the second things started going wrong, I got cocky. And I tried to flash the stock with TWRP; downloaded it to my laptop, put it on the SD card and then in to the phone. Every process that the installation or wipe or any of the other actions performed by TWRP is followed by a line saying "Failed to mount '/ data' (Invalid argument)". I tried to follow the forced update of the stock but I couldn't seem to get that to work either ( this method stechguide.com/marshmallow-stock-rom-for-huawei-p9 ). After all that I can't think if there's anything else.
zandercook1 said:
I can still get in to bootloader and fastboot mode no problem.
Yeah I realised I should have done that the second things started going wrong, I got cocky. And I tried to flash the stock with TWRP; downloaded it to my laptop, put it on the SD card and then in to the phone. Every process that the installation or wipe or any of the other actions performed by TWRP is followed by a line saying "Failed to mount '/ data' (Invalid argument)". I tried to follow the forced update of the stock but I couldn't seem to get that to work either ( this method stechguide.com/marshmallow-stock-rom-for-huawei-p9 ). After all that I can't think if there's anything else.
Click to expand...
Click to collapse
Ok, so a few things:
-The failed to mount /data message probably means that you have an old version of TWRP, check the thread again and make sure you use at least RC3 (newest one afaik).
-Original stock Huawei roms are not suitable for TWRP, to flash a stock rom you need a stock recovery which you can flash back the same way you flashed twrp (using fastboot, or SRK tools). Once you have stock recovery, you can force the update by putting the update file in a folder on your sdcard (internal or external) called "dload". Then you turn off the phone and start it by holding volume up, volume down and power.
-Alternatively you could use a custom rom, which you can find in the dev thread. Custom roms can and should be flashed in TWRP.
Try relocking botloader and installing stock rom with this tool
http://forum.xda-developers.com/p9/development/tool-srk-tool-huawei-bootloader-root-t3374068
clouds5 said:
Ok, so a few things:
-The failed to mount /data message probably means that you have an old version of TWRP, check the thread again and make sure you use at least RC3 (newest one afaik).
-Original stock Huawei roms are not suitable for TWRP, to flash a stock rom you need a stock recovery which you can flash back the same way you flashed twrp (using fastboot, or SRK tools). Once you have stock recovery, you can force the update by putting the update file in a folder on your sdcard (internal or external) called "dload". Then you turn off the phone and start it by holding volume up, volume down and power.
-Alternatively you could use a custom rom, which you can find in the dev thread. Custom roms can and should be flashed in TWRP.
Click to expand...
Click to collapse
I keep pressing the up/down + power buttons but it keeps going to TWRP, as for the out of date version I have 3.0.0-0 but as lomunet suggested I'm downloading the srk tool. That's what I originally used to install TWRP in the first place. For the stock ROM to boot do I need to do anything to the file when it's downloaded (ie zipped or unzipped)? Nosing around a few other threads I noticed they mention something about making a file in the root of the file, and I hope you'll pardon my ignorance, but I have no idea how to do that. As for the custom ROM, I'll try that again when srk tools has finished downloading and I've reinstalled TWRP.
lomunet said:
Try relocking botloader and installing stock rom with this tool
http://forum.xda-developers.com/p9/development/tool-srk-tool-huawei-bootloader-root-t3374068
Click to expand...
Click to collapse
And I'd just like to thank you two for your patience!
Edit:
Ok so, I installed the latest TWRP (3.0.2-eva-modaco-rc3) and that went off without a hitch. Using the SRK tools that lomunet suggested I tried to sideload the stock ROM but the error message of " cannot read 'sideload\ROM.zip' " keeps popping up. I'm downloading a custom ROM (forum.xda-developers.com/p9/development/rom-huawei-p9-fromfuture-newworld-t3390820) as I type to see if that works flashing it through TWRP.
zandercook1 said:
I keep pressing the up/down + power buttons but it keeps going to TWRP, as for the out of date version I have 3.0.0-0 but as lomunet suggested I'm downloading the srk tool. That's what I originally used to install TWRP in the first place. For the stock ROM to boot do I need to do anything to the file when it's downloaded (ie zipped or unzipped)? Nosing around a few other threads I noticed they mention something about making a file in the root of the file, and I hope you'll pardon my ignorance, but I have no idea how to do that. As for the custom ROM, I'll try that again when srk tools has finished downloading and I've reinstalled TWRP.
And I'd just like to thank you two for your patience!
Edit:
Ok so, I installed the latest TWRP (3.0.2-eva-modaco-rc3) and that went off without a hitch. Using the SRK tools that lomunet suggested I tried to sideload the stock ROM but the error message of " cannot read 'sideload\ROM.zip' " keeps popping up. I'm downloading a custom ROM (forum.xda-developers.com/p9/development/rom-huawei-p9-fromfuture-newworld-t3390820) as I type to see if that works flashing it through TWRP.
Click to expand...
Click to collapse
if twrp works the rom must be work without problems...
zandercook1 said:
I keep pressing the up/down + power buttons but it keeps going to TWRP
Click to expand...
Click to collapse
clouds5 said:
Original stock Huawei roms are not suitable for TWRP, to flash a stock rom you need a stock recovery
Click to expand...
Click to collapse
you really need to flash stock recovery first to flash stock firmware. It won't work as long as you have TWRP installed you can use SRK tools to flash stock recovery.
If you are always stuck, jus download "DC Phoenix"(i don't know if i'm authorized to post the name ?), it's a paid app but it's worked for me. Just boot to fastboot mode, and flash your firmware with the app
clouds5 said:
you really need to flash stock recovery first to flash stock firmware. It won't work as long as you have TWRP installed you can use SRK tools to flash stock recovery.
Click to expand...
Click to collapse
Ahhhh right right right. So I need to remove TWRP first, then use SRK tools to flash the stock recovery?
... so, how do I remove TWRP?
zandercook1 said:
Ahhhh right right right. So I need to remove TWRP first, then use SRK tools to flash the stock recovery?
... so, how do I remove TWRP?
Click to expand...
Click to collapse
Installing stock recovery will remove TWRP.
You're all heroes.
zandercook1 said:
You're all heroes.
Click to expand...
Click to collapse
You are a batman yourself.
THIS APPLIES ONLY TO THE A2017U VARIANT, DO NOT USE THIS FILE ON OTHER VERSIONS
Disclaimer - don't blame me if something goes wrong
As title says, this is a full stock unmodified B20 TWRP system image. It kan be used in addition to stock boot and recovery images to restore the US A7 to conditions which will be like stock and allow to flash upcoming OTA. This was tested by @jkuczera here http://forum.xda-developers.com/showthread.php?t=3459107
Link to system image
https://cloud.swehes.com/index.php/s/31V7GgihohBCdfy
If you are BL unlocked, you will need to lock it before flashing old recovery and boot (this may not be necessary to get MR2 to flash, depending on what it checks, but the phone might not boot, unknown). This will make your phone verify boot, recovery and /system again, so flash TWRP from tenfar's thread to be able boot after relocking since his is signed
To restore, unzip the file above to TWRP folder on the SD Card, then in TWRP under mount points unmount /system and put check mark on mount system as read-only. The read-only part is important so that TWRP does not modify the /system apon exit. You can then restore boot, recovery and system image.
Another partition, fastboot, was altered if you applied B20_boot, but so far no OTA has check it so it should be fine as is. Chance is it will be just overwritten by next OTA, but in case that changes, info will be added. This step is more risky since it involves using dd command and has to be applied carefully.
EDIT: looks like @Unjustified Dev posted new build that will flash fastboot image http://forum.xda-developers.com/showpost.php?p=68677272&postcount=133
You should then boot to stock recovery and factory wipe
In case you did not dump your boot and recovery, they can be found in @rczrider's post here
http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
Thanks to @swehes for providing the space on his cloud for this file, @rczrider for rest of the files and @jkuczera for trying this all out
So you need TWRP for this, but will this overwrite the TWRP recovery and make it truly stock?
imp3r10 said:
So you need TWRP for this, but will this overwrite the TWRP recovery and make it truly stock?
Click to expand...
Click to collapse
Indeed and before rebooting , you MUST Wipe Data + Internal Storage, cuz you are flashing new boot and system and will get in conflicts if there no wipe.
Just for clarity sake these are the steps I need to take to get back to B20 from B20_Boot?
1. fastboot oem lock
2. put system image from OP's post AND stock_boot_backup.img AND stock_recovery_backup.img from rczrider's post into TWRP folder.
3. in TWRP unmount /system and check mark on mount system as read only.
4. Flash boot, recovery, and system image.
5. Wipe Data and Internal Storage.
6. Profit?
runderekrun said:
Just for clarity sake these are the steps I need to take to get back to B20 from B20_Boot?
1. fastboot oem lock
2. put system image from OP's post AND stock_boot_backup.img AND stock_recovery_backup.img from rczrider's post into TWRP folder.
3. in TWRP unmount /system and check mark on mount system as read only.
4. Flash boot, recovery, and system image.
5. Wipe Data and Internal Storage.
6. Profit?
Click to expand...
Click to collapse
Pretty much. I would reboot to stock recovery after and factory wipe from there. you might wan't to flash fastboot from B20 OTA for extra profit but seems like it's a moot point so far if you have seen the Unjustified Devs trick for BL unlock via TWRP
peramikic said:
Pretty much. I would reboot to stock recovery after and factory wipe from there. you might wan't to flash fastboot from B20 OTA for extra profit but seems like it's a moot point so far if you have seen the Unjustified Devs trick for BL unlock via TWRP
Click to expand...
Click to collapse
Thanks.
I'm having to do a warranty replacement on my device so i'll probably want to do the fastboot flash. Any idea where to get a fastboot image?
runderekrun said:
I'm having to do a warranty replacement on my device so i'll probably want to do the fastboot flash. Any idea where to get a fastboot image?
Click to expand...
Click to collapse
Step 6 to pull your own: http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Or you can download the one I pulled from my device (it can be found in the Mega folder linked in the OP): http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
And as option 3 it's inside the B18toB20 OTA file floating somewhere around here
Alright I tried this and something went wrong.
First thing I did was copy all the files where they needed to be. Then I booted into fastboot and did a "fastboot oem lock".
Then my device would do nothing. I would boot up to the ZTE logo then go black a second later. I tried to force into recovery by selecting recovery in fastboot but same thing, ZTE logo then blackness.
I got it back by getting into fastboot and performing a "fastboot oem unlock" again. All it did was wipe data.
What did I do wrong? I thought I am supposed to lock bootloader first before I restore system and flash recover and boot????
runderekrun said:
Alright I tried this and something went wrong.
First thing I did was copy all the files where they needed to be. Then I booted into fastboot and did a "fastboot oem lock".
Then my device would do nothing. I would boot up to the ZTE logo then go black a second later. I tried to force into recovery by selecting recovery in fastboot but same thing, ZTE logo then blackness.
I got it back by getting into fastboot and performing a "fastboot oem unlock" again. All it did was wipe data.
What did I do wrong? I thought I am supposed to lock bootloader first before I restore system and flash recover and boot????
Click to expand...
Click to collapse
Ok so if you modified boot, system or recovery in anyway then after BL lock it will not boot since it will fail secure boot, so you need to load the signed TWRP from tenfar's thread via EDL after locking. That will let you run TWRP with locked BL. Although ig you just want stock for upcoming OTA, then you might be good staying unlocked. If for return, then you should lock it
peramikic said:
Ok so if you modified boot, system or recovery in anyway then after BL lock it will not boot since it will fail secure boot, so you need to load the signed TWRP from tenfar's thread via EDL after locking. That will let you run TWRP with locked BL. Although ig you just want stock for upcoming OTA, then you might be good staying unlocked. If for return, then you should lock it
Click to expand...
Click to collapse
I apologize if I am fundamentaly not understanding this but wouldn't it be easier to flash system, boot, recovery, and fastboot back to stock via my current twrp THEN relock bootloader?
runderekrun said:
I apologize if I am fundamentaly not understanding this but wouldn't it be easier to flash system, boot, recovery, and fastboot back to stock via my current twrp THEN relock bootloader?
Click to expand...
Click to collapse
Yeah, now that we know fastboot will work even on stock boot that will work as well. The only thing you won't be able to do is flash back the B20 fastboot image that way, but enough to pass OTA most likely. The long way you can revert the fastboot image as well. I only wanted to post the image to begin with, but then wrote out instruction as they rolled around in my head. This will change soon anyways so a proper write-up will happen, just not by me, Documentation was never my forte
My BL is unlocked from ZTE right now, If I want to get CM for future but also want upcoming update from ZTE? What are the exact steps that I need to follow to get future OTA but also keep the BL unlocked for future CM? Please help as I'm confused with all these instructions.
peramikic said:
THIS APPLIES ONLY TO THE A2017U VARIANT, DO NOT USE THIS FILE ON OTHER VERSIONS
Disclaimer - don't blame me if something goes wrong
As title says, this is a full stock unmodified B20 TWRP system image. It kan be used in addition to stock boot and recovery images to restore the US A7 to conditions which will be like stock and allow to flash upcoming OTA. This was tested by @jkuczera here http://forum.xda-developers.com/showthread.php?t=3459107
Link to system image
https://cloud.swehes.com/index.php/s/31V7GgihohBCdfy
If you are BL unlocked, you will need to lock it before flashing old recovery and boot (this may not be necessary to get MR2 to flash, depending on what it checks, but the phone might not boot, unknown). This will make your phone verify boot, recovery and /system again, so flash TWRP from tenfar's thread to be able boot after relocking since his is signed
To restore, unzip the file above to TWRP folder on the SD Card, then in TWRP under mount points unmount /system and put check mark on mount system as read-only. The read-only part is important so that TWRP does not modify the /system apon exit. You can then restore boot, recovery and system image.
Another partition, fastboot, was altered if you applied B20_boot, but so far no OTA has check it so it should be fine as is. Chance is it will be just overwritten by next OTA, but in case that changes, info will be added. This step is more risky since it involves using dd command and has to be applied carefully.
EDIT: looks like @Unjustified Dev posted new build that will flash fastboot image http://forum.xda-developers.com/showpost.php?p=68677272&postcount=133
You should then boot to stock recovery and factory wipe
In case you did not dump your boot and recovery, they can be found in @rczrider's post here
http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
Thanks to @swehes for providing the space on his cloud for this file, @rczrider for rest of the files and @jkuczera for trying this all out
Click to expand...
Click to collapse
Can someone please explain exactly how to do this. I have an unofficial twrp on my phone and the bootloader is unlocked but after i tried to flash super su it got stuck on bootloop so I wiped every thing and I also accidentally wiped my os too. So now I don't have an os and I want to go back to stock. Can someone please explain step by step on how to fix this? I just got the phone.
seby1234 said:
Can someone please explain exactly how to do this. I have an unofficial twrp on my phone and the bootloader is unlocked but after i tried to flash super su it got stuck on bootloop so I wiped every thing and I also accidentally wiped my os too. So now I don't have an os and I want to go back to stock. Can someone please explain step by step on how to fix this? I just got the phone.
Click to expand...
Click to collapse
All right I'm no expert either but I'll try to make this as straightforward as possible.
1) Format your SD card as exFAT. This is important as otherwise you will not be able to transfer the system image to your SD card since it is 6GB. To do this you can just plug it in to your PC, right click, Format and then select exFAT from the dropdown.
2) Download tenfar's tool for B20, rczrider's boot and recovery backup, and the system image backup from the link in the OP.
3) Create a new folder in /external_sd/TWRP/BACKUPS/serial_number/.Move the stock_boot_backup and stock_recovery backup into the folder.
4) Using a program such as 7zip, extract the 6GB system image file and move it to the same folder.
6) Go to into fastboot mode. Before you do anything you have to relock the bootloader otherwise the system will be modified and you want to be 100? stock. Execute 'fastboot oem lock'. You should then boot to a black screen.
7) Unzip tenfar's tool. Go to the unzipped folder, then hold down shift+right click and select 'Open command window here'. Execute 'axon7root.exe -p [COMPORT #] -r. To figure out your com port #, go to Device Manager, then go to down to where it says "Qualcomm Loader..." and your com port number is the number at the end. So for example if your com port number is 5, you should execute axon7root.exe -p 5 -r. Allow the program to do its thing.
5) Boot into TWRP. Do not swipe to allow modifications. Once in TWRP, go to "Install", "Install Image" at the bottom right hand corner, and then navigate to the stock_recovery_backup in the folder that you moved it to to. Select it and then choose the Recovery partition to flash it to. Do the same thing for stock_boot_backup.
6) Once you have flashed boot and recovery, go to the main menu, then "Restore" and then Restore the system image backup.
7) Go to wipe and then slide to factory reset. Finally, reboot system.
Hope that helps! If you have any questions, feel free to ask me.
rczrider's stock boot and recovery thread
http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818/page7
tenfar's tool thread: http://forum.xda-developers.com/axo...xon-7-root-bootloader-unlokced-t3441204/page1
Has anyone who requested the bootloader unlock from ZTE (and mistakenly installed it) returned to stock and been able to get OTA's? I followed this guide and seemed to have returned to stock fine but the only OTA I can get now is the bootloader unlock OTA. I've downloaded and discarded it several times but that is the only one I can get. Anyone know of a way to bypass this OTA and get the new MR2 that was just released? I want to get OTA's until the custom roms start flowing.
Thanks!
shifuharris said:
Has anyone who requested the bootloader unlock from ZTE (and mistakenly installed it) returned to stock and been able to get OTA's? I followed this guide and seemed to have returned to stock fine but the only OTA I can get now is the bootloader unlock OTA. I've downloaded and discarded it several times but that is the only one I can get. Anyone know of a way to bypass this OTA and get the new MR2 that was just released? I want to get OTA's until the custom roms start flowing.
Thanks!
Click to expand...
Click to collapse
From what I can tell, once you apply for official bootloader unlock, your IMEI is placed on a list that will not get any future OTA updates set to it.
However, the OTA for B20 to B27 has been uploaded here: https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ
Try flashing that via stock recovery.
Quick question for anyone who might know.
The Link to system image which is : https://cloud.swehes.com/index.php/s/31V7GgihohBCdfy has the following;
1. system_image.emmc.win
2. system_image.emmc.win.md5
Am I suppose to rename system_image.emmc.win to system_image.emmc.img and load?
it's not as clear that's why I ask but I ended up downloading rczrider system.img and reflashed via TWRP since I was a bit confused.
Thanks!
***************
I simply just went into TWRP backed up by boot so it would create a directory that contains the info I needed copied the system_image.emmc.win and system_image.emmc.win.md5 and restored.
xtermmin said:
From what I can tell, once you apply for official bootloader unlock, your IMEI is placed on a list that will not get any future OTA updates set to it.
However, the OTA for B20 to B27 has been uploaded here: https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ
Try flashing that via stock recovery.
Click to expand...
Click to collapse
I suspected as much. I downloaded the update and tried to flash it via the stock recovery using the update for ADB option but it fails saying that the package is not a ks package. Booooo. I really wanted this MR becasue they addressed the weak cell signal which I think contributes significantly to my battery drain. Not sure if there are any alternatives to get the update installed. Not very a happy about the ceased OTA's due to the bootloader unlock. Thinking the new Nexus (or whatever they are going to call them) is looking pretty good at the moment.
shifuharris said:
I suspected as much. I downloaded the update and tried to flash it via the stock recovery using the update for ADB option but it fails saying that the package is not a ks package. Booooo. I really wanted this MR becasue they addressed the weak cell signal which I think contributes significantly to my battery drain. Not sure if there are any alternatives to get the update installed. Not very a happy about the ceased OTA's due to the bootloader unlock. Thinking the new Nexus (or whatever they are going to call them) is looking pretty good at the moment.
Click to expand...
Click to collapse
Try the microSD card method instead.
First, make sure OEM Unlocking is checked in developer settings, rename the OTA to "update.zip", put on microSD, boot into stock recovery, and choose update from microSD.
I apologize first of all if this has been posted. I can't find a thread on it.
I recently bought a SM-T813NZKEXAR 9.7". I flashed TWRP via ODIN. I had placed SU internally. When I booted into TWRP it could not see the zip file. had 0mb. I had read to wipe date first.
Now, I can't boot into the system. When I do it reverts back to TWRP. Do I have to flash a system image? Trying to get out of the boot loop. Any help would be appreciated. Thanks
Note: TWRP would not allow me to mount the "Data
Edit: I installed TWRP again via Odin and let me reboot.. Now have to figure how to mount data. When I try to install SU, no files are listed
Your data partition is still encrypted, but you don't have the key anymore. In the past there was a patch to disable mandatory encryption, but I believe there is a newer method now.
You are NOT bricked.
jshamlet said:
Your data partition is still encrypted, but you don't have the key anymore. In the past there was a patch to disable mandatory encryption, but I believe there is a newer method now.
You are NOT bricked.
Click to expand...
Click to collapse
Thanks, good to know. Now I just have to try and find the method.. Any direction out there would be great
There is a sticky thread in the dev forum with all the info you need https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627
[Stock Rom] Huawei (Prague) PRA-xxxC432B182
For restoring/ rescue your device.P8 Lite 2017 - PRA-LX1, LX2, LX3, LA-1
P9 Lite 2017
Nova Lite
Honor 8 Youth
Created and tested on this device:
Huawei P8 lite 2017 [PRAGUE]
Model number: PRA-LX1
Build number: PRA-LX1C432B182
free device
The PRA is extrem sensitiv.
Any unconsidered, unofficial intervention, don't forgive it.
Hundreds of users have already "bricked" their device.
The response to the dealers is enormous.
To restore your devices,
I'll provide a complete rom.
It is 100% functional and rooted with SuperSu.
It is to be applied to the device via TWRP restoring.
But it is also suitable for this purpose without an OTA update,
to get the current firmware.
Be sure to read the following instructions carefully.
You're doing it at your own risk!
Rom installation:
In the download folder:
2017-12-30-PRAstockB182root (zip)
there are 26 backup files compressed as Zip files.
After downloading, unpack all files individually into this directory. Then delete all zip's. Now copy the whole directory to your TWRP backup folder. Where your other backups are.
Now flash the stock recovery and perform a factoryreset.
Now flash TWRP and make a wipe of the data and system partitions in TWRP.
Then restore my backup and reboot.
The firmware and the kernel are already rooted.
If necessary, you can install Busybox.
If the device does not boot, the bootloader must be unlocked again with the Huawei unlockcode.
It is a little bit more work for you to unpack everything individually, but this way a faultless installation is possible.
I have tested the up- and download, unpacking and restoring several times. It works perfectly. The rom is bug free.
Now create a new TWRP backup
and remove all older backups from the TWRP backup folder, otherwise they could cause problems later.
Save it to another folder or to
USB-/Stick, or HD.
I would now like to make a few comments on the end of the year:
I've had the P8 lite 2017 for a year.
The first rooting was developed by me.
The SuperSu and the first rooted kernel,
enabled the developers
@Tecalote and KangVip.
TWRP was provided by the LineageOS team. Again and again I have added fresh rootings and roms.
Nevertheless, increased Bricks are not missing.
It took an enormous amount of time to find
help the users. Unfortunately, this didn't work out for everyone.
My recommendation:
Now set up your device completely. Then create a complete backup with the ingenious Huawei Backup App. Now you take the recovery back.
"fastboot flash recovery recovery. img"
Removes TWRP from your brain for the time being.
Your device is now perfect and the firmware is original. You also have root and the OTA update authorization. When OREO comes, you just wait until I announce the new rooting."
I wish you all the best for 2018.
WARNING !
If all this has worked on my device, it does not mean that it goes with everyone else. Follow exactly the instructions to prevent damage. The execution is your risk.
Never make a factory reset in TWRP. Brick !!! Wipes only in stock recovery.
NOTE: Despite careful preparation I can not guarantee that through the implementation of this Guidance does not create damage to the device or operating system, and therefore assume no liability for ensuing damage and malfunction of hardware and software! If you are still unsure, follow these steps: Only perform the procedure if any mentioned conditions (model number, Android version, etc.) apply to you or your device. Read the instructions carefully and completely, check unfamiliar terminology by google or xda. Downloaded files check for viruses. A backup of important settings and data make. The instructions do not perform, if you do not know what you're doing.
Thank you very much: @Tecalote, KangVip,Chainfire, Stephen (Stericson), Jmz Software, LinageOs team, JRummy, as well as.
Huawei Technologies Co., Ltd.
Update 2017-12-31:
I removed the part "dual recovery".
The support on xda is finished.
Only here:
https://www.android-hilfe.de/forum/huawei-p8-lite-2017.2980/
I couldn't restore my phone. I followed all of your instructions and after restoring, when I reboot, the phone goes only in TWRP (no volume keys pressed). Any ideas on what I can do?
In any case thank you for the thread, it's good to have a well described procedure for these things
Restore your last backup and repeat the procedure.
Try this one first:
Root again with the SU (B182) from the download.
Tip for life: try not to trust random nerds on forums, offering "ROMs" and what they call "tutorials". Stick to the outlet which sold you the phone, and deal with them and/or the manufacturer, and you can't go far wrong.
afit5 said:
I couldn't restore my phone. I followed all of your instructions and after restoring, when I reboot, the phone goes only in TWRP (no volume keys pressed). Any ideas on what I can do?
In any case thank you for the thread, it's good to have a well described procedure for these things
Click to expand...
Click to collapse
I had the same situation. It's a bit tricky and you must really know, what you are doing
I rebooted to bootloader an repeated the oem unlock -> this caused a factory reset!!
I am on dual recovery and so I rebooted to twrp, repeated the restore with the b182 stock rom and could reboot to the system
mbwf said:
Tip for life: try not to trust random nerds on forums, offering "ROMs" and what they call "tutorials". Stick to the outlet which sold you the phone, and deal with them and/or the manufacturer, and you can't go far wrong.
Click to expand...
Click to collapse
100% useless post. This does not help anyone.
ChinHon tries to help others and i would trust him more than you...
KuGeSch said:
I had the same situation. It's a bit tricky and you must really know, what you are doing
I rebooted to bootloader an repeated the oem unlock -> this caused a factory reset!!
I am on dual recovery and so I rebooted to twrp, repeated the restore with the b182 stock rom and could reboot to the system
Click to expand...
Click to collapse
UPDATE: I solved in another way, which is: booted to fastboot mode, restored the stock recoveries (recovery1 to recovery1, erecovery to recovery2), then the phone booted normally as it should have had. At that point I could reflash twrp to recovery1, but that is optional.
I think the phone tried to boot but having the wrong recovery in recovery2 slot caused problems (just a random hypothesis). Hope this helps
afit5 said:
UPDATE: I solved in another way, which is: booted to fastboot mode, restored the stock recoveries (recovery1 to recovery1, erecovery to recovery2), then the phone booted normally as it should have had. At that point I could reflash twrp to recovery1, but that is optional.
I think the phone tried to boot but having the wrong recovery in recovery2 slot caused problems (just a random hypothesis). Hope this helps
Click to expand...
Click to collapse
What you call erecocery is this the stock erecovery or is it prague311.img from ChinHon? If it is the stock erecovery, where can I find it for download?
Thanks a lot!
KuGeSch said:
What you call erecocery is this the stock erecovery or is it prague311.img from ChinHon? If it is the stock erecovery, where can I find it for download?
Thanks a lot!
Click to expand...
Click to collapse
-prague311.img is TWRP
-recovery.img is the stock recovery on recovery partition 1
-recovery2.img is the stock eRecovery on recovery partition 2
https://www.mediafire.com/file/r33el93w5wyqwde/recovery2.img
ChinHon said:
-prague311.img is TWRP
-recovery.img is the stock recovery on recovery partition 1
-recovery2.img is the stock eRecovery on recovery partition 2
https://www.mediafire.com/file/r33el93w5wyqwde/recovery2.img
Click to expand...
Click to collapse
Thanks a lot! You are doing a great job!
Hello!
I want to follow this guide, it should be fine for my Dual SIM Variant, right?
I have a problem with one file, that is 'version.emmc.win.md5.zip' that can't be downloaded from MEGA. Can someone please provide a working link for that file?
Also a doubt: when all the files will be ready my idea is to restore your TWRP backup, flash stock recovery then lock bootloader, to make it as near to stock as possible: will this work? I have another TWRP backup that is running on my phone, but if I lock the bootloader it won't start, if I unlock the bootloader there no problems at all.
Thanks for your interesting topic!
SnoopyDog said:
100% useless post. This does not help anyone.
ChinHon tries to help others and i would trust him more than you...
Click to expand...
Click to collapse
Very good. Keep smiling.
baffo92 said:
Hello!
I want to follow this guide, it should be fine for my Dual SIM Variant, right?
I have a problem with one file, that is 'version.emmc.win.md5.zip' that can't be downloaded from MEGA. Can someone please provide a working link for that file?
Also a doubt: when all the files will be ready my idea is to restore your TWRP backup, flash stock recovery then lock bootloader, to make it as near to stock as possible: will this work? I have another TWRP backup that is running on my phone, but if I lock the bootloader it won't start, if I unlock the bootloader there no problems at all.
Thanks for your interesting topic!
Click to expand...
Click to collapse
Here's the link.
https://mega.nz/#!4sd3DI6Z!BOfI0teLD_m3aLUROhiMVZuePySmp329RXZpjsH3AM0
Please tell me why you want to take the rom. What's happening?
ChinHon said:
Here's the link.
https://mega.nz/#!4sd3DI6Z!BOfI0teLD_m3aLUROhiMVZuePySmp329RXZpjsH3AM0
Please tell me why you want to take the rom. What's happening?
Click to expand...
Click to collapse
The link works perfectly. Thanks!
I can now give this stock ROM a try!
EDIT 1: I'm trying to install the ROM but I have a problem with TWRP: I launch the command 'fastboot flash recovery prague311.img' then boot to TWRP, but the touchsceen of the phone is unresponsive and I can't do anything to make it work. Have you got any suggestion?
EDIT 2: I made some mistakes here and there, but the TWRP booted and now I have the phone on your ROM Version! I'm trying to clean everything and do a clean install if I can...
EDIT 3: I've done a full phone clean by using the 'Factory Reset' option in 'Settings'... now the phone boots, but:
1. NFC/GPS are not working, they are blinking
2. FM Radio is not working (it says com.huawei.... and has an Android icon instead of the original icon)
baffo92 said:
The link works perfectly. Thanks!
I can now give this stock ROM a try!
EDIT 1: I'm trying to install the ROM but I have a problem with TWRP: I launch the command 'fastboot flash recovery prague311.img' then boot to TWRP, but the touchsceen of the phone is unresponsive and I can't do anything to make it work. Have you got any suggestion?
EDIT 2: I made some mistakes here and there, but the TWRP booted and now I have the phone on your ROM Version! I'm trying to clean everything and do a clean install if I can...
Click to expand...
Click to collapse
To get the rom completely clean you do the following:
Go to my root thread section: Threadupdate: 2018-01-02 and work through the instructions. Then you have a perfect clean stock rom.
ChinHon said:
To get the rom completely clean you do the following:
Go to my root thread section: Threadupdate: 2018-01-02 and work through the instructions. Then you have a perfect clean stock rom.
Click to expand...
Click to collapse
Your support is very helpful, thanks!
I have problems on the steps to reproduce, even after reading your guide :')
This is what I do:
1. Wipe Data/Factory Reset + Wipe cache with stock recovery
2. Flash TWRP
3. Open TWRP, clean data, system and also cache + dalvik
4. Reboot the phone to a fully working with B182, in English with Dual SIM fully recognised
5. What I have to do from now on to have a fully stock experience (remove custom Kernel, reflash stock recovery and erecover, re-lock bootloader and fully ready to Oreo)?
Can you please guide me?
Thanks and sorry for my problems, but I work with Nexus devices thare a bit more 'elastic' in flashing
The kernel is stock. You just have to flash the eRecovery and recovery. That's all.
ChinHon said:
The kernel is stock. You just have to flash the eRecovery and recovery. That's all.
Click to expand...
Click to collapse
Ok, thanks!
This is what I did before, but I can't do a factory reset due to the problems described (Radio FM not working, NFC not working).
I can't also relock the bootloader, because the phone will boot to erecovery (recovery2) and won't let me reach the boot of the ROM. Have you got any suggestion?
If leave it as it is now (unlocked bootloader with stock recovery1 and recovery2) will Oreo arrive without any problems?
Your support is awesome, thanks
If you now take my UPDATE.APP via dload the problems should be gone.
ChinHon said:
If you now take my UPDATE.APP via dload the problems should be gone.
Click to expand...
Click to collapse
Sounds good!
If I flash the stock recovery, then update officially with an UPDATE.APP from SD Card everything should be ok.
Where can I find your UPDATE.APP? I didn't find it in your MEGA Folder
Thanks, again, for your incredible support!
Situation:
I tried rooting my phone. I extracted the boot.img with payloaddumper from the latest android 11 Zenfone 8 image from the Asus website (the same version I have on my phone). I patched that image file with Magisk. Flashed that file to my phone with fastboot which succeeded. But after rebooting this is the message I get:
"Your device is corrupted and cannot be trusted and will not boot" and than a link to g.co/ABH
There is no option to "press power to continue" as seen on other screenshots of this problem on YouTube. So I am stuck. I cannot enter recovery. It tries to boot a few times but than stays at the "start" screen while booting.
What I tried to fix this:
Internet states that I have to disable DM check with: adb reboot "dm-verity enforcing". But ADB does not see my device. Fastboot does! So I tried flashing back the original/unpatched boot.img but the result stays the same.
Question:
What can I do to fix this? Also flash Vendor_boot.img? At this moment I rather not do too much but wait for advice/tips in this forum.
And a few "stupid" questions:
- When trying to root the method described here in this forum..... does the bootloader have to be unlocked? My is not.
- IF the bootloader has to be open.... I know I have to use an Asus tool.... but is there a way to do it with ADB/Fastboot?
- When it is necessary to flash my whole device.... is there a way to save my data? (for example flash trwp first and back up data to a thumbdrive)
Any help much appreciated!
>>does the bootloader have to be unlocked
Yes
>>but is there a way to do it with ADB/Fastboot?
No. Only to relock. Or at least I haven't seen such method.
>>When it is necessary to flash my whole device
What do you mean?
>>is there a way to save my data?
If you have root and mean apps data - Swift backup. For me it is failed to restore only few apps (banking + Signal messenger) all other apps are ok.
dron39 said:
>>does the bootloader have to be unlocked
Yes
Click to expand...
Click to collapse
Ok.... bummer..... the device was not unlocked....... So NOT being unlocked did not prevent the flashing I guess. And a locked bootloader is preventing disabling the DM check?
dron39 said:
>>When it is necessary to flash my whole device
What do you mean?
Click to expand...
Click to collapse
If undoing my flash/error (= no unlocked bootloader) is not possible. I have to do a complete reflash I guess. So that would wipe all data. I was wondering if I could flash only parts of the system so some partitions would be spared (so I could save some data..... or install TWRP and maybe save some data)
dron39 said:
>>is there a way to save my data?
If you have root and mean apps data - Swift backup. For me it is failed to restore only few apps (banking + Signal messenger) all other apps are ok.
Click to expand...
Click to collapse
Root was the goal. But that did not happen yet because of the locked bootloader as I understand it now. So no root = no backup/saving data?
If I download the last OTA update my phone recieved, extract boot.img from it and flash that to my phone with fastboot will that restore my phone to a bootable state? If not,what will?