Database Users

Android 6.0.1 and any camera (stock included) fail.

I haven't done a factory reset yet but I would love to avoid it if possible.
I went to take a picture of the wife's newly decorated Christmas tree and the stock camera fails to fully start. It behaves as if it can not use the hardware. When I look at the back there is a small red light/laser that refuses to go out unless the phone is rebooted.
I've rebooted the phone a few times and tried Manual Camera and a couple others .. same behavior.
The phone is running 6.0.1 and is rooted.
Anyone seeing this and have any ideas?

Are you using the stock kernel

I am having the same problem. I flashed with the factory image and the camera won't work in any apps. Stock camera, Snapchat, Instagram, etc. Flashlight had not been working from the Quick Settings tiles, but it did work after wiping cache and dalvik in TWRP.
I saw someone mention on reddit that it can be an issue with using NRT to flash (I didn't use it) and something about vendor.img. I reflashed vendor.img and it didn't change anything.

SuperSmashedBro said:
Are you using the stock kernel
Click to expand...
Click to collapse
Yep. With the exception of being rooted and using a few utils like root explorer and recently ... nothing special. I did just notice Google Play Services *****ed and said there was an error but it wasn't specific about the error. I did bounce the cache for Google Play Services after seeing that.
Nothing odd about this phone ... it's been top notch for the last month.

fury683 said:
I am having the same problem. I flashed with the factory image and the camera won't work in any apps. Stock camera, Snapchat, Instagram, etc. Flashlight had not been working from the Quick Settings tiles, but it did work after wiping cache and dalvik in TWRP.
I saw someone mention on reddit that it can be an issue with using NRT to flash (I didn't use it) and something about vendor.img. I reflashed vendor.img and it didn't change anything.
Click to expand...
Click to collapse
I wonder if it's the vendor.img that caused this. Hmm.. I wonder if the vendor.img from 6.0 would sort it. hmm.

aergern said:
I wonder if it's the vendor.img that caused this. Hmm.. I wonder if the vendor.img from 6.0 would sort it. hmm.
Click to expand...
Click to collapse
I am trying a reflash of the factory image again. Will try out the camera upon first boot before proceeding with TWRP/root/Xposed. It's optimizing my apps right now, I'll let you know in a minute.
---------- Post added at 08:49 PM ---------- Previous post was at 08:45 PM ----------
Full reflash (without wiping userdata) with factory image seems to have worked... Now to try proceeding one step at a time with TWRP/root/Xposed to see if it breaks again.

fury683 said:
I am trying a reflash of the factory image again. Will try out the camera upon first boot before proceeding with TWRP/root/Xposed. It's optimizing my apps right now, I'll let you know in a minute.
Click to expand...
Click to collapse
Yeah, I tried flashing the 6.0 vendor.img and Manual Camera started and I got visual but it froze. I did get a complaint that something was wrong with my system. So I'm trying the 6.0.1 vendor.img. Let me know what you find.

I had this issue on 6.0 when I was trying to do systemless root. I was given boot.img options that were modified (L, M and N) L didn't allow root, N borked the camera, M worked. I would think it's the boot.img

aergern said:
Yeah, I tried flashing the 6.0 vendor.img and Manual Camera started and I got visual but it froze. I did get a complaint that something was wrong with my system. So I'm trying the 6.0.1 vendor.img. Let me know what you find.
Click to expand...
Click to collapse
No dice. Reflashing the 6.0.1 vendor.img did squat. I'll wait.

darkamikaze said:
I had this issue on 6.0 when I was trying to do systemless root. I was given boot.img options that were modified (L, M and N) L didn't allow root, N borked the camera, M worked. I would think it's the boot.img
Click to expand...
Click to collapse
So reflashing the system.img and waiting for Chainfire to make a new boot image could be the solution. That kinda sucks but it could be the only solution.

darkamikaze said:
I had this issue on 6.0 when I was trying to do systemless root. I was given boot.img options that were modified (L, M and N) L didn't allow root, N borked the camera, M worked. I would think it's the boot.img
Click to expand...
Click to collapse
I am using the "traditional" root method and used the angler-mdb08k-boot.zip by Chainfire, which is what I have used before.

fury683 said:
I am using the "traditional" root method and used the angler-mdb08k-boot.zip by Chainfire, which is what I have used before.
Click to expand...
Click to collapse
Same here. Using the same root method each time with my Nexus 6 was never an issue.
Damn. hmm.

Using a 6.0 boot.img or kernel will break the camera on 6.0.1. You can use the new supersu 2.61 on the new 6.0.1 update and root works fine and so does the camera

edd247 said:
Using a 6.0 boot.img or kernel will break the camera on 6.0.1. You can use the new supersu 2.61 on the new 6.0.1 update and root works fine and so does the camera
Click to expand...
Click to collapse
Oh. So just flash supersu 2.61 instead of using the boot.img and supersu 2.5x method. Good. I'll give that a whirl.

I just used the 2.61 systemless root and it appears to be working OK. I just flashed Xposed and am rebooting (optimizing apps for the 3rd time tonight...). Process is pretty painless.
Flash factory image (my batch file was modified to NOT wipe userdata (-w removed))
Flash TWRP
Install SuperSU 2.61 from TWRP --- DO NOT INSTALL ROOT FROM TWRP IF/WHEN IT ASKS
---------- Post added at 09:31 PM ---------- Previous post was at 09:19 PM ----------
Xposed installed and it all seems to work OK.

fury683 said:
I just used the 2.61 systemless root and it appears to be working OK. I just flashed Xposed and am rebooting (optimizing apps for the 3rd time tonight...). Process is pretty painless.
Flash factory image (my batch file was modified to NOT wipe userdata (-w removed))
Flash TWRP
Install SuperSU 2.61 from TWRP --- DO NOT INSTALL ROOT FROM TWRP IF/WHEN IT ASKS
---------- Post added at 09:31 PM ---------- Previous post was at 09:19 PM ----------
Xposed installed and it all seems to work OK.
Click to expand...
Click to collapse
I just erased and reflashed each partition except userdata so it's doing it's thing. Once it's back up then I'll just use 2.61 and be done with it.
Thanks. Just hope I don't have to look at the boot animation much longer ...

Anyone try the modified MMB29N boot.img thats on the Unlock/Root/Flash Guide to see if it breaks the camera while rooting traditionally?

fury683 said:
I just used the 2.61 systemless root and it appears to be working OK. I just flashed Xposed and am rebooting (optimizing apps for the 3rd time tonight...). Process is pretty painless.
Flash factory image (my batch file was modified to NOT wipe userdata (-w removed))
Flash TWRP
Install SuperSU 2.61 from TWRP --- DO NOT INSTALL ROOT FROM TWRP IF/WHEN IT ASKS
---------- Post added at 09:31 PM ---------- Previous post was at 09:19 PM ----------
Xposed installed and it all seems to work OK.
Click to expand...
Click to collapse
I did this ...
fastboot erase system
fastboot erase cache
fastboot erase boot
fastboot erase vendor
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot reboot
Seems to be stuck at the bootloader animation ... so far .. 20 minutes? I shouldn't have to wipe userdata .. right?

captainwahid said:
Anyone try the modified MMB29N boot.img thats on the Unlock/Root/Flash Guide to see if it breaks the camera while rooting traditionally?
Click to expand...
Click to collapse
I used the only Angler boot.img in the list and it worked to root but the camera was screwed.

this one? http://forum.xda-developers.com/showpost.php?p=64004628&postcount=1195

nougat backup

can somebody post a twrp nougat backup for me ? im googlelooped from ota file i flashed on twrp from 6.01. i tried an old backup, 3 different images, n preview then sideloaded ota, wiped everything i can think of. flashed 6.0 6.01 roms, did images img by img used tool kit. i once did boot up but had wrong vendor and never got that far again. tried new twrp and old twrp. stuck until 7.0 images come

rbouza1 said:
can somebody post a twrp nougat backup for me ? im googlelooped from ota file i flashed on twrp from 6.01. i tried an old backup, 3 different images, n preview then sideloaded ota, wiped everything i can think of. flashed 6.0 6.01 roms, did images img by img used tool kit. i once did boot up but had wrong vendor and never got that far again. tried new twrp and old twrp. stuck until 7.0 images come
Click to expand...
Click to collapse
I'm uploading a backup of system, boot, and vendor to mega app. When done I'll post link to it.
---------- Post added at 06:05 PM ---------- Previous post was at 06:02 PM ----------
Just curious, are you using twrp 3.0.2-1 or 3.0.2-0?
https://mega.nz/#F!Zdx3hALS

Fe Mike said:
I'm uploading a backup of system, boot, and vendor to mega app. When done I'll post link to it.
---------- Post added at 06:05 PM ---------- Previous post was at 06:02 PM ----------
Just curious, are you using twrp 3.0.2-1 or 3.0.2-0.
Click to expand...
Click to collapse
was using the 3.0.2-1 but getting farther with previous. its boots to the circles almost

Fe Mike said:
I'm uploading a backup of system, boot, and vendor to mega app. When done I'll post link to it.
---------- Post added at 06:05 PM ---------- Previous post was at 06:02 PM ----------
Just curious, are you using twrp 3.0.2-1 or 3.0.2-0.
Click to expand...
Click to collapse
thank you, ill let you know if it works

Fe Mike said:
I'm uploading a backup of system, boot, and vendor to mega app. When done I'll post link to it.
---------- Post added at 06:05 PM ---------- Previous post was at 06:02 PM ----------
Just curious, are you using twrp 3.0.2-1 or 3.0.2-0?
https://mega.nz/#F!Zdx3hALS
Click to expand...
Click to collapse
needs decryption key

ok, I sent a pm with two links and I clicked on the first link and it took me straight to download. Ignore the second one cause link is broken. Sorry about that.

Fe Mike said:
ok, I sent a pm with two links and I clicked on the first link and it took me straight to download. Ignore the second one cause link is broken. Sorry about that.
Click to expand...
Click to collapse
thanks i recovered it but stuck on google

rbouza1 said:
thanks i recovered it but stuck on google
Click to expand...
Click to collapse
So even after restoring that backup your still stuck on Google splash screen?
I doubled checked my upload looks like its missing boot.emmc.wIn file. take the boot file from this post, and flash it through twrp. Make sure you select img file or twrp won't see it. It is the boot for that backup.
http://forum.xda-developers.com/nexus-6p/general/grab-flashable-7-0-official-ota-t3445543

Fe Mike said:
So even after restoring that backup your still stuck on Google splash screen?
I doubled checked my upload looks like its missing boot.emmc.wIn file. take the boot file from this post, and flash it through twrp. Make sure you select img file or twrp won't see it. It is the boot for that backup.
http://forum.xda-developers.com/nexus-6p/general/grab-flashable-7-0-official-ota-t3445543
Click to expand...
Click to collapse
no go thanks for trying

Sorry man. That blows, hopefully google will release that factory image soon.

Got stuck trying to root, just want to return to stock/factory settings.

I'm new so please forgive me and my ignorance through all of this. I had a great root experience with my old LG G3, so when I got my Axon 7 (A2017U) I thought I'd try to root it too. I tried to follow DrakenFX's guide (http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204) but I bit off more than I could chew. I got to the point where I had TWRP up, but this is where I think things started to fall apart. I was confused by the instructions and in a haste I continued anyway. In TWRP I went to Wipe>Format Data typed in yes like TWRP said and boom, I had no idea what happened. Rebooting only got a screen that said "Type in your password" but my passcode I had on the phone before it bricked didn't work. So by now I start panicking a bit. I thought I made a mistake earlier so I went back and tried to reinstall TWRP by putting the phone into EDL. The phone got stuck that way for a while, but I now I have it in TWRP. Right now, I just want to get back to safe stock android.
I'm 200% sure I messed with something I wasn't supposed to and I believe that is the system image(?)which Draken also linked (http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53). I'm downloading it as I type. I'm going to do my best to leave my phone just like it is right now, in TWRP, and wait for more advice on this before I do anything else.. What I'm curious about is where did I go wrong and what do I need to do to get my phone working again, preferably without returning it? Thank you for any advice you have to offer.
Update: It's worth noting I didn't know to enable OEM Unlocking when I was in stock android. Dumb move I know. I'm new here.

What software version are u on?

xiong77 said:
What software version are u on?
Click to expand...
Click to collapse
As far as I know I (was) on Android 6.0 A2017U B29. TWRP version 3.0.2-0

Get DrakenFX b29 mergeboot stack and b29 stock system and flash it then u should be OK. I did this too.

xiong77 said:
Get DrakenFX b29 mergeboot stack and b29 stock system and flash it then u should be OK. I did this too.
Click to expand...
Click to collapse
I tried, but the downloads take extremely long and are unreliable for me. I was downloading the stock system file at around 14 kbps and it eventually failed. Any other suggestions?

Wipe cache dalvik data and system reboot, ignore error message and reboot
---------- Post added at 06:54 AM ---------- Previous post was at 06:53 AM ----------
Try through ur computer
---------- Post added at 06:57 AM ---------- Previous post was at 06:54 AM ----------
Try go back to twrp and wipe like the op said

xiong77 said:
Wipe cache dalvik data and system reboot, ignore error message and reboot
---------- Post added at 06:54 AM ---------- Previous post was at 06:53 AM ----------
Try through ur computer
---------- Post added at 06:57 AM ---------- Previous post was at 06:54 AM ----------
Try go back to twrp and wipe like the op said
Click to expand...
Click to collapse
I've done the wipes multiple times. It's mostly the downloads I'm having trouble with. How and where do you get them? The links I found were dead or had a slow speed.

video_dewd said:
I've done the wipes multiple times. It's mostly the downloads I'm having trouble with. How and where do you get them? The links I found were dead or had a slow speed.
Click to expand...
Click to collapse
Did you save the recovery backup? If you did then use the axon7root.exe to flash the stock recovery. Then download the stock B20 from ZTE.

tabletalker7 said:
Did you save the recovery backup? If you did then use the axon7root.exe to flash the stock recovery. Then download the stock B20 from ZTE.
Click to expand...
Click to collapse
I've been able to find some recovery images that I found on other threads. The thing is, when I try to flash them on TWRP, I get an error about "/dev/block/sde14" being read-only.

video_dewd said:
I've been able to find some recovery images that I found on other threads. The thing is, when I try to flash them on TWRP, I get an error about "/dev/block/sde14" being read-only.
Click to expand...
Click to collapse
no no no no ..................... put phone in EDL mode. Copy the stock image into the folder with the axon7root.exe file you used to flash TWRP. Make sure the stock file is named recovery.img (or whatever the TWRP file is named in that folder, it has been a long time since I did this). Then use the axon7root.exe program the exact same way you did before. It will flash the stock recovery. Then in stock recovery you can flash the B20 from ZTE

tabletalker7 said:
no no no no ..................... put phone in EDL mode. Copy the stock image into the folder with the axon7root.exe file you used to flash TWRP. Make sure the stock file is named recovery.img (or whatever the TWRP file is named in that folder, it has been a long time since I did this). Then use the axon7root.exe program the exact same way you did before. It will flash the stock recovery. Then in stock recovery you can flash the B20 from ZTE
Click to expand...
Click to collapse
Ok, I will try this.
Update: I got the stock recovery back, but now I'm lost as to how to flash the stock b20 from zte. Thank you for all your help so far though.

video_dewd said:
Ok, I will try this.
Click to expand...
Click to collapse
got stock recovery working?

tabletalker7 said:
got stock recovery working?
Click to expand...
Click to collapse
Yes, I'm in the process of getting the update from sdcard feature working.
Update: Trying to use the update.zip file or unpacking it into the sdcard hasn't worked. Trying to use adb sideload returns "Cannot read 'update.zip'"

video_dewd said:
Yes, I'm in the process of getting the update from sdcard feature working.
Click to expand...
Click to collapse
ok - download it from zte. Put it on your SD card. In recovery select update from SD card. Be warned it will work but it is slow. Also note that while I will not say the bootloader unlock doesn't work on B29, I can say it worked flawlessly on B20. If you want unlocked I recommend doing so on B20.

tabletalker7 said:
ok - download it from zte. Put it on your SD card. In recovery select update from SD card. Be warned it will work but it is slow. Also note that while I will not say the bootloader unlock doesn't work on B29, I can say it worked flawlessly on B20. If you want unlocked I recommend doing so on B20.
Click to expand...
Click to collapse
I have the zip but it says, "Sorry,you can't sdcard upgrade".

video_dewd said:
I have the zip but it says, "Sorry,you can't sdcard upgrade".
Click to expand...
Click to collapse
try using adb sideload
---------- Post added at 07:48 AM ---------- Previous post was at 07:45 AM ----------
also people reportd sucess on the z-communities by placing the B20 on the internal sd card (phone storage)

tabletalker7 said:
try using adb sideload
---------- Post added at 07:48 AM ---------- Previous post was at 07:45 AM ----------
also people reportd sucess on the z-communities by placing the B20 on the internal sd card (phone storage)
Click to expand...
Click to collapse
I tried that. It won't accept the zip file and it's unclear which file to sideload. Would you happen to know? This is what files are in the unpacked zip. https://gyazo.com/c7546c3ed0dcb0972653eaeba42fcb40

video_dewd said:
I tried that. It won't accept the zip file and it's unclear which file to sideload. Would you happen to know? This is what files are in the unpacked zip. https://gyazo.com/c7546c3ed0dcb0972653eaeba42fcb40
Click to expand...
Click to collapse
Maybe - I'd have to download it to find out. If you can't get stock recovery to take it this post http://forum.xda-developers.com/showpost.php?p=69434328&postcount=17 gives you instructions on what lines to remove from the updater-script to make it flash in TWRP (I didn't have a problem making the stock B20 go in stock recovery, but I was unlocked at the time). You could reflash TWRP and try that.
Or just try this in TWRP http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2

tabletalker7 said:
Maybe - I'd have to download it to find out. If you can't get stock recovery to take it this post http://forum.xda-developers.com/showpost.php?p=69434328&postcount=17 gives you instructions on what lines to remove from the updater-script to make it flash in TWRP (I didn't have a problem making the stock B20 go in stock recovery, but I was unlocked at the time). You could reflash TWRP and try that.
Or just try this in TWRP http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Click to expand...
Click to collapse
I'm going to try the first option. The second option's link take horrendously long to download.
Update: Trying to flash from TWRP results in error "Could not find 'META-INF/com/google/android/update-binary' which makes no sense since update binary is exactly where it should be.
Further Update: It seems that the problem might have been that when I compressed "update.zip" to fix "updater-script" it changed to file path by adding the title of the folder "update" to the beginning. I think that messed with the path giving the the meta-inf error.

video_dewd said:
I'm going to try the first option. The second option's link take horrendously long to download.
Update: Trying to flash from TWRP results in error "Could not find 'META-INF/com/google/android/update-binary' which makes no sense since update binary is exactly where it should be.
Click to expand...
Click to collapse
OK. How did you do that?
---------- Post added at 10:09 AM ---------- Previous post was at 09:54 AM ----------
Just suck it up and download the 2 b29 files. If it is that slow pick a different mirror

[GUIDE]FULL ROOT Nougat Mate 8 (PHH'S SUPERUSER with TWRP 3.1.0-0)

[GUIDE]FULL ROOT IN NOUGAT MATE 8 (PHH SUPERUSER with TWRP 3.1.0-0)​
I created this thread so user can try other alternative root instead of SuperSU. This is full root with decrypted data partition in TWRP without formatting your data partition.
REQUIREMENTS
Unlocked Bootloader
Working and running Nougat (Stock firmware)
TWRP 3.1.0-0 (Nougat) Here (Credit to @surdu_petru & @OldDroid for making it possible to mate 8 & @franzyroy for not giving up hope :good: )
phh's SuperUser Here (config : noverify)
Must in untouched Stock boot
BEFORE PROCEED
BACKUP BACKUP BACKUP your data.
Copy superuser_noverify.zip into mSDCard
STEPS
1. Unlock Bootloader
2. Flash twrp-3.1.0-next-v3.img via ADB
3. Reboot to TWRP (It will take about 30 seconds or less to enter TWRP)
4. Install superuser_noverify.zip
5. Reboot to system
6. Go to playstore and Install phh's SuperUser app
Have fun!!
Cheers

Big Big Thnx To This Method Very very Thnx dexz To This Full Root Owner Of mate 8 Congratulations All
---------- Post added at 10:25 PM ---------- Previous post was at 10:22 PM ----------
dexz Which Rom used c185b560 or c432560 or c636b563 And thnx

misho_20063 said:
Big Big Thnx To This Method Very very Thnx dexz To This Full Root Owner Of mate 8 Congratulations All
---------- Post added at 10:25 PM ---------- Previous post was at 10:22 PM ----------
dexz Which Rom used c185b560 or c432560 or c636b563 And thnx
Click to expand...
Click to collapse
I have tested C636B521/B563, C432B560, AL10C00B577 & TL00C17B575 (in stock firmware). Rest of the region I think should be working.

From the reality of your experience Of this All Rom C636B521/B563, C432B560, AL10C00B577 & TL00C17B575 Which Is Best ?????? And Which Rom Used Now In Phone Use

Interesting.... I gonna perhaps test your method. Because mine works but not for all (like me unfortunalely contrary to what I thought).
---------- Post added 11-03-2017 at 00:26 ---------- Previous post was 10-03-2017 at 23:58 ----------
@dexz
Did you see that? It could help us for the root.
Edit:
I tried but it doesn't work for me with Nougat

misho_20063 said:
From the reality of your experience Of this All Rom C636B521/B563, C432B560, AL10C00B577 & TL00C17B575 Which Is Best ?????? And Which Rom Used Now In Phone Use
Click to expand...
Click to collapse
Currently I'm using C636B563 that's my original region but I personally prefer AL10 because of battery performance slightly better
franzyroy said:
Interesting.... I gonna perhaps test your method. Because mine works but not for all (like me unfortunalely contrary to what I thought).
---------- Post added 11-03-2017 at 00:26 ---------- Previous post was 10-03-2017 at 23:58 ----------
@dexz
Did you see that? It could help us for the root.
Edit:
I tried but it doesn't work for me with Nougat
Click to expand...
Click to collapse
Nice. I will try the link later.

Getting bootloop after rebooting... any idea?
Installation of files was succesfull, no errors in twrp.

Leo_83 said:
Getting bootloop after rebooting... any idea?
Installation of files was succesfull, no errors in twrp.
Click to expand...
Click to collapse
did u format your data before hand?
Sent from my Mate 9 using XDA Labs

eddmecha said:
did u format your data before hand?
Sent from my Mate 9 using XDA Labs
Click to expand...
Click to collapse
Yes followed the steps one by one...
Edit: One thing worth mentioning is that I used the update_data.zip from the russian link, when I orignally installed Nougat this was the only file that worked for me.
Edit2: Redid the steps but used the update_data-zip posted by Sillanwali in his thread to update to nougat C432B560 but I get "Error: 7....."

After the step 4, I preconize to reboot the recovery. It's advised after a "Format data".

Leo_83 said:
Yes followed the steps one by one...
Edit: One thing worth mentioning is that I used the update_data.zip from the russian link, when I orignally installed Nougat this was the only file that worked for me.
Edit2: Redid the steps but used the update_data-zip posted by Sillanwali in his thread to update to nougat C432B560 but I get "Error: 7....."
Click to expand...
Click to collapse
Make sure you are running unmodified stock firmware. As method above only patch boot img and push superuser files. Do not install decrypted boot img. It need untouched stock boot .
Once you completed the steps and reboot to system. It will normally bootloop twice then you will stuck at huawei logo about 3-5mins.

franzyroy said:
After the step 4, I preconize to reboot the recovery. It's advised after a "Format data".
Click to expand...
Click to collapse
It's optional step but normally most of my experiments I don't even need to "reboot to recovery" but I will add it as optional step in OP.

dexz said:
Make sure you are running unmodified stock firmware. As method above only patch boot img and push superuser files. Do not install decrypted boot img. It need untouched stock boot .
Once you completed the steps and reboot to system. It will normally bootloop twice then you will stuck at huawei logo about 3-5mins.
Click to expand...
Click to collapse
It's just not working for me. I was on stock firmware, only unlocked bootloader, I did not install decrypted boot.img.
I left the phone for roughly about 15 min (one Fifa game) in screen, it doesn't get past Huawei logo and I haven't seen it reboot.
Edit: What about the update_full_hw.zip is that not needed after formating data?
Edit2: Tried again but these time rebooting into recovery after formating data as suggested by @franzyroy but it didn't make a difference still bootloop

Leo_83 said:
It's just not working for me. I was on stock firmware, only unlocked bootloader, I did not install decrypted boot.img.
I left the phone for roughly about 15 min (one Fifa game) in screen, it doesn't get past Huawei logo and I haven't seen it reboot.
Edit: What about the update_full_hw.zip is that not needed after formating data?
Click to expand...
Click to collapse
Yes. That's the file we need to install (update_data_*.zip) at step no. 6
Leo_83 said:
Edit2: Tried again but these time rebooting into recovery after formating data as suggested by @franzyroy but it didn't make a difference still bootloop
Click to expand...
Click to collapse
Yes. Doesn't make any difference. That's why I skipped reboot to recovery after format data

dexz said:
Yes. That's the file we need to install (update_data_*.zip) at step no. 6
Click to expand...
Click to collapse
Aha thought it was just the update.zip file my bad *Hides in shame*

Leo_83 said:
Aha thought it was just the update.zip file my bad *Hides in shame*
Click to expand...
Click to collapse
so u actually flash update.zip instead of update_data_hw.zip?
Sent from my Mate 9 using XDA Labs

I setup All Method And Now My Phone Full Rooted 100% And All App With Root Working Well Very Very Thnx Man dexz Congratualtion Of All Owner Mate 8 Final The Root Is Full

misho_20063 said:
I setup All Method And Now My Phone Full Rooted 100% And All App With Root Working Well Very Very Thnx Man dexz Congratualtion Of All Owner Mate 8 Final The Root Is Full
Click to expand...
Click to collapse
I'm glad you got it full root.

Leo_83 said:
Aha thought it was just the update.zip file my bad *Hides in shame*
Click to expand...
Click to collapse
:laugh:

eddmecha said:
so u actually flash update.zip instead of update_data_hw.zip?
Sent from my Mate 9 using XDA Labs
Click to expand...
Click to collapse
Indeed I did lul
dexz said:
:laugh:
Click to expand...
Click to collapse
Working like a charm!! Thanks dexz!

twrp restoring to stock

I have a pro 3 x727 and I tried returning to stock but twrp keep saying no partition selected help

Here is a picture
It's not giving a option to select partition

island maan said:
Here is a picture
It's not giving a option to select partition
Click to expand...
Click to collapse
Look like you have no back up to restore
Sent from my SM-A730F using xda premium

mchlbenner said:
Look like you have no back up to restore
Click to expand...
Click to collapse
Yes I do

Consider using another version of TWRP.
1. Copy the backup file to your computer
2. Flash a lower version of TWRP.
3. Import the TWRP backup file to your phone.
4. Flash the backup.
---------- Post added at 01:03 AM ---------- Previous post was at 01:01 AM ----------
millkyway4 said:
Consider using another version of TWRP.
1. Copy the backup file to your computer
2. Flash a lower version of TWRP.
3. Import the TWRP backup file to your phone.
4. Flash the backup.
Click to expand...
Click to collapse
Also your backup files look a little weird, which backup version did you use?

millkyway4 said:
Consider using another version of TWRP.
1. Copy the backup file to your computer
2. Flash a lower version of TWRP.
3. Import the TWRP backup file to your phone.
4. Flash the backup.
---------- Post added at 01:03 AM ---------- Previous post was at 01:01 AM ----------
Also your backup files look a little weird, which backup version did you use?
Click to expand...
Click to collapse
Eui 5.9.021s

island maan said:
Eui 5.9.021s
Click to expand...
Click to collapse
Ditch everything, use a qfl file and hold your device power plus volume + and - then your phone should vibrate. connect it to your computer and using flash one flash the qfl file. Your phone should boot up with a developer preview of eui. then reinstall twrp and retry the previous instructions.