Develop Bugs

[Q] TWRP

I updated the software on my DEB Nexus 7 from KOTH49H to KVT49L and now I can't install TWRP.
Are they in progress of making a new recovery img so that it works or should I revert back to KOT49H?

MColbath said:
I updated the software on my DEB Nexus 7 from KOTH49H to KVT49L and now I can't install TWRP.
Are they in progress of making a new recovery img so that it works or should I revert back to KOT49H?
Click to expand...
Click to collapse
Do you still have root? What was the error?

There is no error it flashes TWRP and then when I boot recovery it is still stock recovery. I am unrooted.
Sent from my VS980 4G using XDA Premium 4 mobile app

MColbath said:
There is no error it flashes TWRP and then when I boot recovery it is still stock recovery. I am unrooted.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you outline the exact steps you are doing to flash?

mdamaged said:
Can you outline the exact steps you are doing to flash?
Click to expand...
Click to collapse
I originally started out with PA 5.0 BETA but, then I reverted to stock to get the update. Full flash black to 4.4.2 KOT49H then I factory reset it once more to make sure everything is okay. After that I completed the setup Wizard and let all the apps update, after that was done I would reboot the tablet and then activate developer options. I flash using a batch I made that simply boots the tablet into bootloader then it uses the command fastboot flash recovery openrecovery-twrp-2.6.3.1-deb.img and reboots the device. Once it boots up I reboot into recovery and it shows the stock recovery instead of TWRP.

MColbath said:
I originally started out with PA 5.0 BETA but, then I reverted to stock to get the update. Full flash black to 4.4.2 KOT49H then I factory reset it once more to make sure everything is okay. After that I completed the setup Wizard and let all the apps update, after that was done I would reboot the tablet and then activate developer options. I flash using a batch I made that simply boots the tablet into bootloader then it uses the command fastboot flash recovery openrecovery-twrp-2.6.3.1-deb.img and reboots the device. Once it boots up I reboot into recovery and it shows the stock recovery instead of TWRP.
Click to expand...
Click to collapse
In the process of resetting back to factory, did it relock your bootloader? I ask only because some tools do this automatically. I had to ask.

mdamaged said:
In the process of resetting back to factory, did it relock you bootloader? I ask only because some tools do this automatically. I had to ask.
Click to expand...
Click to collapse
Nah, I did it manually to see if locking and re-unlocking it would allow TWRP to be flashed but, that didn't work.

MColbath said:
Nah, I did it manually to see if locking and re-unlocking it would allow TWRP to be flashed but, that didn't work.
Click to expand...
Click to collapse
Welp, can you BOOT into twrp...i.e. fastboot boot openrecovery-twrp-2.6.3.1-deb.img then you can root it (a suggestion to use goo was here, but forget that).
If you can boot into twrp using the above suggestion, you can at least root and get some stuff done while waiting for a fix or update or someone more knowledgeable than I to solve your issue.
The only thing I can think of is that the bootloader changed and we are back to where you started, waiting for them to update it for your bootloader.

mdamaged said:
Welp, can you BOOT into twrp...i.e. fastboot boot openrecovery-twrp-2.6.3.1-deb.img then you can root it and try using...goo manager (never used this myself heard some good, some bad things, about it YMMV etc etc).
Click to expand...
Click to collapse
No, well I can temporarily boot into TWRP using Wugfresh's kit but, that's the only way I can boot into TWRP. I'm not sure if that will work but, I will give it a shot.

MColbath said:
No, well I can temporarily boot into TWRP using Wugfresh's kit but, that's the only way I can boot into TWRP. I'm not sure if that will work but, I will give it a shot.
Click to expand...
Click to collapse
Don't bother with goo (they disabled downloads and it seems for good reason), see my edits in last post.

mdamaged said:
Don't bother with goo (they disabled downloads and it seems for good reason), see my edits in last post.
Click to expand...
Click to collapse
Okay seems good.

mdamaged said:
Don't bother with goo (they disabled downloads and it seems for good reason), see my edits in last post.
Click to expand...
Click to collapse
Worked well I was able to root, install BusyBox (latest), and install glitch kernel without bricking. Thanks for the help.

MColbath said:
Worked well I was able to root, install BusyBox (latest), and install glitch kernel without bricking. Thanks for the help.
Click to expand...
Click to collapse
No problem, thanks for the update.

mdamaged said:
No problem, thanks for the update.
Click to expand...
Click to collapse
I am browsing the root and it seems like they made a backup file that defaults it back to the original recovery. I am assuming this has something to do with Verizon because they patched a lot of stuff in the update or so it seems.

MColbath said:
I am browsing the root and it seems like they made a backup file that defaults it back to the original recovery. I am assuming this has something to do with Verizon because they patched a lot of stuff in the update or so it seems.
Click to expand...
Click to collapse
Hmm, as you probably know there is a file that is normally renamed in the process of installing recoveries to prevent that, my guess is they changed the name or location or added a new one (with a diff name) or did something with the permissions so it could not be renamed, and I'll bet if you boot into twrp and rename that file you'll be able to flash and boot into twrp, though I'd make sure the contents of that file ONLY do that one thing, and that renaming it won't cause it to boot loop.

mdamaged said:
Hmm, as you probably know there is a file that is normally renamed in the process of installing recoveries to prevent that, my guess is they changed the name or added a new one (with a diff name), and I'll bet if you boot into twrp and rename that file you'll be able to flash and boot into twrp, though I'd make sure the contents of that file ONLY do that one thing, and that renaming it won't cause it to boot loop.
Click to expand...
Click to collapse
Yeah there are new backup files all over the place in System partition.

MColbath said:
Yeah there are new backup files all over the place in System partition.
Click to expand...
Click to collapse
Stupid providers.

mdamaged said:
Stupid providers.
Click to expand...
Click to collapse
I'm checking the developer block section of recovery right now.
I'll upload the log for the recovery too. Hold on.

Here it is.

MColbath said:
Here it is.
Click to expand...
Click to collapse
Is there a file in /system named recovery-from-boot.p?

[MOD] Note 4 International Boot/Shutdown Animation

I've seen some ROMs using this boot animation and I must prefer it as opposed to the stock T-Mobile animations, so I decided to package these into a CWM/TWRP package so that you can use it regardless of what ROM you decide to use. I checked to see if this had been posted before, but wasn't able to find anything. While I tested it with the T-Mobile version (SM-N910T) it will work with any variant.
To apply the mod just flash your chosen zip file in either CWM or TWRP.
Standard: https://www.androidfilehost.com/?fid=95784891001609635
Standard w/ Boot Sound Disabled: https://www.androidfilehost.com/?fid=95784891001609633
Reset To Stock Animations: https://www.androidfilehost.com/?fid=95784891001609634
Enjoy!
P.S. I am fully aware that the stock animation is basically this with the absurdly bright T-Mobile screen at the end, that's why I don't like it!

Thanks for this I personally prefer this one

mike28 said:
Thanks for this I personally prefer this one
Click to expand...
Click to collapse
Do we have a link seeing this bootanimation? Thanks!

bigmase23 said:
Do we have a link seeing this bootanimation? Thanks!
Click to expand...
Click to collapse
No need, it is just the T-Mobile one without the absurdly bright T-Mobile screen. Its just the sparkly Samsung logo. Eventually I'll get around to getting the Lollipop boot animation installed.

bootloop if you put a kernel
i flash it on top of kk kernel and i get boot loops

Deezy88 said:
i flash it on top of kk kernel and i get boot loops
Click to expand...
Click to collapse
Then you did something wrong, I'm using it with FireKatN4 + KT-NOTE4 and it works great. This does not modify anything that would cause a bootloop. My spidey sense tells me that you didn't clear your Cache/Dalvik when you flashed the kernel like the instructions clearly tell you to do.

Thanks

Is this a flash able zip or do we replace the boot animation file ?

re: flashable
JaZart said:
Is this a flash able zip or do we replace the boot animation file ?
Click to expand...
Click to collapse
This is a flashable zip file, flash using twrp recovery.
Good luck!

Misterjunky said:
re: flashable
This is a flashable zip file, flash using twrp recovery.
Good luck!
Click to expand...
Click to collapse
I was able to change the boot animation without flashing.

That doesn't get rid of the annoying jingle

trying to flash twrp; it just hangs!

Hi all,
*I've unlocked bootloader
* Have tried fastboot boot TWRP.img, as well as tried flashing TWRP RC1 via the Skipsoft toolkit.
Every way I've tried the phone just sits at the TWRP boot screen and doesn't allow me to go any further..
Any help here would be truly appreciated!
Cheers,

I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.

dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
You're braver than me. I haven't had my Pixel XL long but this is the first phone I've ever owned where I am afraid to try and install a custom recovery and ROM. With the dual partitions and what I hear about TWRP still being buggy it just seems like Google didn't want people to run anything but pure Android on the Pixels.

dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....

mikefnz said:
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....
Click to expand...
Click to collapse
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.

mac796 said:
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.
Click to expand...
Click to collapse
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!

mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?

XtraArrow said:
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?
Click to expand...
Click to collapse
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!

mazubo said:
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!
Click to expand...
Click to collapse
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.

XtraArrow said:
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.
Click to expand...
Click to collapse
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..

mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1 zip
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again

mazubo said:
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..
Click to expand...
Click to collapse
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??

mac796 said:
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again
Click to expand...
Click to collapse
Hmm, maybe this is where I've gone wrong.. I thought the need to create a security pin/pattern was only if coming from a previously rooted state, or from a custom ROM. I will try this as well and report back.. thanks!

XtraArrow said:
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??
Click to expand...
Click to collapse
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..

mazubo said:
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..
Click to expand...
Click to collapse
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.

XtraArrow said:
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.
Click to expand...
Click to collapse
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!

mazubo said:
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!
Click to expand...
Click to collapse
I'm no expert but it's seems like a decent suggestion. Let us know how it goes.

@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!

Just wait. It will take little longer
Sent from my Pixel XL using Tapatalk

freddy0872 said:
@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!
Click to expand...
Click to collapse
Yes, I have tried fastboot to flash the TWRP img, as well as skipsofts toolkit. I guess I've been using the term "flash" for fastboot, as I haven't been able to use twrp yet.. I understand that you need to flash the TWRP img via pc and then flash the TWRP zip, then SuperSU or magisk, whatever your poison may be !

Pixel XL 8.1 Developer Preview Stock Recovery Image

Where can I find this, exactly? I looked through the 8.1 image, and while I found the boot.img file, there is no recovery file anywhere inside it.
Can anybody help me find this please?

MultiKoopa said:
Where can I find this, exactly? I looked through the 8.1 image, and while I found the boot.img file, there is no recovery file anywhere inside it.
Can anybody help me find this please?
Click to expand...
Click to collapse
Why exactly do you need this? It flashes fine without it

With A-B partitioned devices (inc. Pixel), recovery is part of boot

PresidentMcCain said:
With A-B partitioned devices (inc. Pixel), recovery is part of boot
Click to expand...
Click to collapse
this explains EVERYTHING
thanks
I needed it cause I made a dumbass mistake while switching to 8.1 and trying to root it

did you get it?
MultiKoopa said:
this explains EVERYTHING
thanks
I needed it cause I made a dumbass mistake while switching to 8.1 and trying to root it
Click to expand...
Click to collapse
did you get it?

HeZhiKui said:
did you get it?
Click to expand...
Click to collapse
Yeah I just flashed the boot image to both partitions, and the boot loop was fixed

MultiKoopa said:
Yeah I just flashed the boot image to both partitions, and the boot loop was fixed
Click to expand...
Click to collapse
my pixel xl is now stuck at the initial setting up staus after i unenrolled the 8.1 beta program due to always "Couldn't connect to internet" while the wi-fi is connected . and i post a thread(see the below) link for help, but no body reply me yet. Do you have any idea about my issue? sorry i would like to attched the pictures, but i dont know how to.
thanks.
https://forum.xda-developers.com/pixel-xl/help/setting-due-to-connect-to-internet-wi-t3701963

Boot image for Mate SE

Hello
Can some send me a TWRP backup of their Mate SE? I only need the boot image. Please just the boot partition. I don't have a good internet where I am at right now and I bricked. Thanks!

Sandman-007 said:
Hello
Can some send me a TWRP backup of their Mate SE? I only need the boot image. Please just the boot partition. I don't have a good internet where I am at right now and I bricked. Thanks!
Click to expand...
Click to collapse
Unlocked for a whole , what, 3 hours , and you brick already.
Sorry had to do that.
I don't have mate , but 7x the roms are supposedly basically the same. At least the 7x custom roms work on se.
I have boot image uploaded , along with the the rest of the partitions , as separate files. On Android file host. You can. Try to use that.
As far as mate back up I have found one, but it is whole backup.
https://androidfilehost.com/?w=files&flid=261152

mrmazak said:
Unlocked for a whole , what, 3 hours , and you brick already.
Sorry had to do that.
I don't have mate , but 7x the roms are supposedly basically the same. At least the 7x custom roms work on se.
I have boot image uploaded , along with the the rest of the partitions , as separate files. On Android file host. You can. Try to use that.
As far as mate back up I have found one, but it is whole backup.
https://androidfilehost.com/?w=files&flid=261152
Click to expand...
Click to collapse
LOL what can I say, I took one for the team!
Thanks, I actually found a boot.img for a 7x that I fastboot flashed but it didn't help. I am downloading a Full TWRP backup for the Mate SE that I found but my internet at my GFs is real slow so gonna take a couple hours. I'll update.
What Roms for 7x work on SE? Maybe I will just flash one of those? My phone wasn't on Oreo so I don't imagine an Oreo ROM working,
Oh and I bricked by flashing Magisk and no-verify 4.1. I knew I shouldve stayed away from Magisk and just flashed SuperSU

Sandman-007 said:
LOL what can I say, I took one for the team!
Thanks, I actually found a boot.img for a 7x that I fastboot flashed but it didn't help. I am downloading a Full TWRP backup for the Mate SE that I found but my internet at my GFs is real slow so gonna take a couple hours. I'll update.
What Roms for 7x work on SE? Maybe I will just flash one of those? My phone wasn't on Oreo so I don't imagine an Oreo ROM working,
Oh and I bricked by flashing Magisk and no-verify 4.1. I knew I shouldve stayed away from Magisk and just flashed SuperSU
Click to expand...
Click to collapse
I have it downloaded already and have put the images up as files.
***updating this in 5 minutes with link***

mrmazak said:
I have it downloaded already and have put the images up as files.
***updating this in 5 minutes with link***
Click to expand...
Click to collapse
Ok Thanks. So which Rom were u referring too because I only see one and it's Oreo based.

Sandman-007 said:
Ok Thanks. So which Rom were u referring too because I only see one and it's Oreo based.
Click to expand...
Click to collapse
I'm reading through the Mate thread again to see which ones. I think it was the manual Oreo update that worked, but have not found that claim yet.
here is link to folder, still uploading files , but boot is ready
https://www.androidfilehost.com/?w=files&flid=266003

mrmazak said:
I'm reading through the Mate thread again to see which ones. I think it was the manual Oreo update that worked, but have not found that claim yet.
here is link to folder, still uploading files , but boot is ready
https://www.androidfilehost.com/?w=files&flid=266003
Click to expand...
Click to collapse
Thanks downloading now. I do believe it was the manual Oreo. It works for the L31

Sandman-007 said:
Thanks downloading now. I do believe it was the manual Oreo. It works for the L31
Click to expand...
Click to collapse
found the post i remeber reading.
https://forum.xda-developers.com/showpost.php?p=76286950&postcount=159

mrmazak said:
I'm reading through the Mate thread again to see which ones. I think it was the manual Oreo update that worked, but have not found that claim yet.
here is link to folder, still uploading files , but boot is ready
https://www.androidfilehost.com/?w=files&flid=266003
Click to expand...
Click to collapse
Thank You! That worked! My phone boots. That funny because I tried 2 other boot.img for the 7x but they didn't work. Thanks!
Edit: Welp Spoke too soon. I boot but get a black screen once I hit home screen. Trying a Factory reset. I did one earlier but ehhh...

Sandman-007 said:
Thank You! That worked! My phone boots. That funny because I tried 2 other boot.img for the 7x but they didn't work. Thanks!
Edit: Welp Spoke too soon. I boot but get a black screen once I hit home screen.
Click to expand...
Click to collapse
that last boot is from mate backup.
try to go inside , to dark room to see if screen is really blank or just turned down real low.
the brightness on these seem to be able to go way too low.

mrmazak said:
that last boot is from mate backup.
try to go inside , to dark room to see if screen is really blank or just turned down real low.
the brightness on these seem to be able to go way too low.
Click to expand...
Click to collapse
I can see the nav bar and the power menu options. Launcher just wont start. I think I need to flash system image

Sandman-007 said:
I can see the nav bar and the power menu options. Launcher just wont start. I think I need to flash system image
Click to expand...
Click to collapse
well, lets review what you did , and maybe figure out what is "broke" maybe less drastic than system flash is needed.

mrmazak said:
well, lets review what you did , and maybe figure out what is "broke" maybe less drastic than system flash is needed.
Click to expand...
Click to collapse
Ok. SO after I unlocked my bootloader I flashes TWRP 3.1.1-0. I can't find 3.1.1-1 for the 7x even tho that is the one ppl say to use since it supports decrypt.
Then I flashed the latest Magisk and no-verity 4.1. When my system didn't boot I tried n-verity 6.0 then 5.1 as I thought I was using the wrong version but it didn't help.
I did try flashing the uninstaller for Magisk but it fails to flash. Can't find /Vender it says. Honestly I should've just flashed SuperSU.

Sandman-007 said:
Ok. SO after I unlocked my bootloader I flashes TWRP 3.1.1-0. I can't find 3.1.1-1 for the 7x even tho that is the one ppl say to use since it supports decrypt.
Then I flashed the latest Magisk and no-verity 4.1. When my system didn't boot I tried n-verity 6.0 then 5.1 as I thought I was using the wrong version but it didn't help.
I did try flashing the uninstaller for Magisk but it fails to flash. Can't find /Vender it says. Honestly I should've just flashed SuperSU.
Click to expand...
Click to collapse
Maybe need to flash vendor partition.
Still uploading that file. Is at 33%Done
It is 822 mb
Version I am putting up is from the b130 backup
Check back in file host folder in about 15-20 minutes. Or continue with the original full backup download. Done

mrmazak said:
Maybe need to flash vendor partition.
Still uploading that file. Is at 33%Done
It is 822 mb
Version I am putting up is from the b130 backup
Check back in file host folder in about 15-20 minutes. Or continue with the original full backup download. Done
Click to expand...
Click to collapse
Thank you. It'll be a few hours but I will get back to you!

mrmazak said:
Maybe need to flash vendor partition.
Still uploading that file. Is at 33%Done
It is 822 mb
Version I am putting up is from the b130 backup
Check back in file host folder in about 15-20 minutes. Or continue with the original full backup download. Done
Click to expand...
Click to collapse
Well I tried flashing Boot, System and Vender and I still have the blank screen. I even wiped system and Data then reflashed. I suspect the system.img is different for Mate SE and I am flashing 7x System.img

Sandman-007 said:
Well I tried flashing Boot, System and Vender and I still have the blank screen. I even wiped system and Data then reflashed. I suspect the system.img is different for Mate SE and I am flashing 7x System.img
Click to expand...
Click to collapse
The folder I shared is the mate se backup.

mrmazak said:
The folder I shared is the mate se backup.
Click to expand...
Click to collapse
Any suggestions then because I flashed all the files after a full wipe and I still get a Black Screen with nav bar showing and power options showing but no launcher

Sandman-007 said:
I can see the nav bar and the power menu options. Launcher just wont start. I think I need to flash system image
Click to expand...
Click to collapse
i bricked mine within a day, same reason: magisk + no-verify. Can't say for sure why, I installed magisk ok, no-verify had zip error, but installed anyway, then I wiped caches. result = no boot. Maybe I shouldn't have wiped?
I was able to recover using someone else's backup imgs and part of the process here:
https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
I used fastboot to flash the system and boot imgs and used twrp to flash the vendor img. I think that was the trick, just using fastboot to flash the vendor resulted in the black screen with nav controls only.

drunkle said:
i bricked mine within a day, same reason: magisk + no-verify. Can't say for sure why, I installed magisk ok, no-verify had zip error, but installed anyway, then I wiped caches. result = no boot. Maybe I shouldn't have wiped?
I was able to recover using someone else's backup imgs and part of the process here:
https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
I used fastboot to flash the system and boot imgs and used twrp to flash the vendor img. I think that was the trick, just using fastboot to flash the vendor resulted in the black screen with nav controls only.
Click to expand...
Click to collapse
OK I tried that. Selected the vender partition in TWRP and flashed vender img on top. Still black screen.