FingerPrint and themes not working - Honor 7X Questions & Answers

I was on nougat on my L21_hw_eu before i tried to upgrade manualy to oreo. i tried the twrp and terminal method and my phone started upgading. It failed at 72% saying "update verification failed". I lost my stock rom and bricked my phone.
Then i manualy flashed different Update.app images and was able to unbrick my phone .
I tried lineage OS and stock oreo.
Problems are:
1: I cant factory reset my phone using stock recovery it fails at 24%
2: FingerPrint Sensor won't work except for gestures (in Stock oreo. works in LineageOs)
3: Themes dont work
4: Flash light don't work
4: CAMERA is not responding. in both roms
in lineageOs everything works perfectly except Camera.
Please provide me details for what am i doing wrong..

iu.khan53 said:
I was on nougat on my L21_hw_eu before i tried to upgrade manualy to oreo. i tried the twrp and terminal method and my phone started upgading. It failed at 72% saying "update verification failed". I lost my stock rom and bricked my phone.
Then i manualy flashed different Update.app images and was able to unbrick my phone .
I tried lineage OS and stock oreo.
Problems are:
1: I cant factory reset my phone using stock recovery it fails at 24%
2: FingerPrint Sensor won't work except for gestures (in Stock oreo. works in LineageOs)
3: Themes dont work
4: Flash light don't work
4: CAMERA is not responding. in both roms
in lineageOs everything works perfectly except Camera.
Please provide me details for what am i doing wrong..
Click to expand...
Click to collapse
If you only have extracted images flashed from update.app, then you do not have the full rom installed.
You should run either hurupdater of HWOTA again to get full emui8 installed.

mrmazak said:
If you only have extracted images flashed from update.app, then you do not have the full rom installed.
You should run either hurupdater of HWOTA again to get full emui8 installed.
Click to expand...
Click to collapse
I suspected that too...
Now my TWRP hangs at initial screen. i m using p20lite.img twrp
other TWRP works but they dont have adb enabled
is there a way i could flash through fastboot?

iu.khan53 said:
I suspected that too...
Now my TWRP hangs at initial screen. i m using p20lite.img twrp
other TWRP works but they dont have adb enabled
is there a way i could flash through fastboot?
Click to expand...
Click to collapse
no,
dont adb though.

mrmazak said:
no,
dont adb though.
Click to expand...
Click to collapse
HuRUpdater keeps loading on initial screen and
HWota Fails after installing no check recovery.
screenshot attached..

iu.khan53 said:
HuRUpdater keeps loading on initial screen and
HWota Fails after installing no check recovery.
screenshot attached..
Click to expand...
Click to collapse
Is that v3.1 . I pulled that version because of error 2 messages.
Check the guide and download again. File name should be. ...
NVM, I just put the download link here.
https://www.androidfilehost.com/?fid=746163614322268008

mrmazak said:
Is that v3.1 . I pulled that version because of error 2 messages.
Check the guide and download again. File name should be. ...
NVM, I just put the download link here.
https://www.androidfilehost.com/?fid=746163614322268008
Click to expand...
Click to collapse
Hwota was successful with the newer version but after rebooting update failed at 0%

iu.khan53 said:
Hwota was successful with the newer version but after rebooting update failed at 0%
Click to expand...
Click to collapse
Please screenshot the twrp screen before reboot.

mrmazak said:
Please screenshot the twrp screen before reboot.
Click to expand...
Click to collapse
i flashed different images from UPDATE.APP manually through fastboot and twrp.. I was succesfull and fingerprint was working but camera was still not working so i stupidity flashed DTS.IMG, ODM.img, and ERECOVERY_KERNEL.img through twrp and when i rebooted. there was completely black screen and nothing was working. fastboot only recognizes device and i m able to send commands . i wanted to flash other dts,odm and ERECOVERY_KERNEL.img through fastboot but it says "remote command not allowed". there is absolutely no life in phone. i think it is hard bricked. is there a way to get device back?? or else i m completely F****D.

iu.khan53 said:
i flashed different images from UPDATE.APP manually through fastboot and twrp.. I was succesfull and fingerprint was working but camera was still not working so i stupidity flashed DTS.IMG, ODM.img, and ERECOVERY_KERNEL.img through twrp and when i rebooted. there was completely black screen and nothing was working. fastboot only recognizes device and i m able to send commands . i wanted to flash other dts,odm and ERECOVERY_KERNEL.img through fastboot but it says "remote command not allowed". there is absolutely no life in phone. i think it is hard bricked. is there a way to get device back?? or else i m completely F****D.
Click to expand...
Click to collapse
You are well past anything I. Have dealt with.

mrmazak said:
You are well past anything I. Have dealt with.
Click to expand...
Click to collapse
well i will try to repair it with sigma device. I heard it can flash anything on to device through fastboot. I will try that otherwise i have to give it to huawei service centre and pray they accept to repair it.

iu.khan53 said:
well i will try to repair it with sigma device. I heard it can flash anything on to device through fastboot. I will try that otherwise i have to give it to huawei service centre and pray they accept to repair it.
Click to expand...
Click to collapse
can not explain it, but I have seen that camra not working problem, and the blank black screenfixed by flashing the vendor partiton. The bad part about that is, i do not think it flashes with fastboot.

mrmazak said:
can not explain it, but I have seen that camra not working problem, and the blank black screenfixed by flashing the vendor partiton. The bad part about that is, i do not think it flashes with fastboot.
Click to expand...
Click to collapse
i took the phone to local repair shop they flashed naugat on it and were unsuccesfull(naugat cant be flashed on oreo) but i am again at fastboot with situation similar to this thread.
https://forum.xda-developers.com/mate-9/help/please-help-bootloop-error-func-14-1-t3724685

iu.khan53 said:
i took the phone to local repair shop they flashed naugat on it and were unsuccesfull(naugat cant be flashed on oreo) but i am again at fastboot with situation similar to this thread.
https://forum.xda-developers.com/mate-9/help/please-help-bootloop-error-func-14-1-t3724685
Click to expand...
Click to collapse
As far as I know (which is not that far). You need three images to be correct for recovery to load on oreo based device.
1. recovery_ramdisk.img
2. kernel.img
3. recovery_vbmeta
try to flash those in fastboot first. and see if they complete without error.
then if they do flash, try to boot into recovery. (try with stock first-- can try TWRP after if this works)

mrmazak said:
As far as I know (which is not that far). You need three images to be correct for recovery to load on oreo based device.
1. recovery_ramdisk.img
2. kernel.img
3. recovery_vbmeta
try to flash those in fastboot first. and see if they complete without error.
then if they do flash, try to boot into recovery. (try with stock first-- can try TWRP after if this works)
Click to expand...
Click to collapse
i cant flash ramdisk images. ithink i m on naugat now because i am able to flash succesfully recovery.img and boot.img in recovery and boot partitions. but cant flash ramdisk and kernel.
and what is iom3 image. error do i need to flash something for that?
and also hifi image error when upgrading through dload method

iu.khan53 said:
i cant flash ramdisk images. ithink i m on naugat now because i am able to flash succesfully recovery.img and boot.img in recovery and boot partitions. but cant flash ramdisk and kernel.
and what is iom3 image. error do i need to flash something for that?
and also hifi image error when upgrading through dload method
Click to expand...
Click to collapse
oh, well let me get together some nougat suggestions

mrmazak said:
oh, well let me get together some nougat suggestions
Click to expand...
Click to collapse
i have sent phone to the service center. waiting for their response now. They told me if they were unable to repair the phone then i will get a new one. lets hope for the best.

iu.khan53 said:
i have sent phone to the service center. waiting for their response now. They told me if they were unable to repair the phone then i will get a new one. lets hope for the best.
Click to expand...
Click to collapse
That sounds good

mrmazak said:
That sounds good
Click to expand...
Click to collapse
Received call today they were unable to repair it. They said they will get me a new one as soon as new stock arrives.

mrmazak said:
That sounds good
Click to expand...
Click to collapse
Recieved new phone today. Works like a charm. but again stuck on naugat. i will wait for official upgrade this time
Edit:
Got upgrade to oreo today. Love the new UI.

Related

Honor 7X Oreo Stock Recovery

Hi, I manually updated my honor 7x (BND AL10 INDIAN) to EMUI 8 following the other post in this forum and after that I went on to flash TWRP recovery again from another post "complete_twrp_ramdisk.img" so that I could take full Nand backups and what not. But Here's the problem, When I try to flash the stock recovery back "BND_RECOVERY_NOcheck" which I flashed during upgrading to EMUI 8, it says "size of image is large than target device"
I tried this using boot fastboot command "fastboot flash recovery_ramdisk recovery.img" and also using the TWRP. It doesn't work either way. So I'm basically stuck with TWRP. The reason I want stock recovery is because
1. I can install OTA UPDATES on EMUI 8 (I actually got one)
2. I may want to just be on complete stock like locked bootloader, sock recovery etc...
Could any one help?? Maybe I need the right stock recovery file ?
BTW It's my first post ever so please go easy if I did any mistakes.
Could you share your twrp? Thanks!
Thetpcguy said:
Hi, I manually updated my honor 7x (BND AL10 INDIAN) to EMUI 8 following the other post in this forum and after that I went on to flash TWRP recovery again from another post "complete_twrp_ramdisk.img" so that I could take full Nand backups and what not. But Here's the problem, When I try to flash the stock recovery back "BND_RECOVERY_NOcheck" which I flashed during upgrading to EMUI 8, it says "size of image is large than target device"
I tried this using boot fastboot command "fastboot flash recovery_ramdisk recovery.img" and also using the TWRP. It doesn't work either way. So I'm basically stuck with TWRP. The reason I want stock recovery is because
1. I can install OTA UPDATES on EMUI 8 (I actually got one)
2. I may want to just be on complete stock like locked bootloader, sock recovery etc...
Could any one help?? Maybe I need the right stock recovery file ?
BTW It's my first post ever so please go easy if I did any mistakes.
Click to expand...
Click to collapse
"BND_RECOVERY_NOcheck" is nouget stock recovery.
Oreo update replaces all the partitions, including the recovery that you flashed in order to install the update.
The stock recovery can be extracted from "update.app" , the one inside the oreo "updateL22.zip"
holds said:
Could you share your twrp? Thanks!
Click to expand...
Click to collapse
It's here https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500
mrmazak said:
"BND_RECOVERY_NOcheck" is nouget stock recovery.
Oreo update replaces all the partitions, including the recovery that you flashed in order to install the update.
The stock recovery can be extracted from "update.app" , the one inside the oreo "updateL22.zip"
Click to expand...
Click to collapse
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Thetpcguy said:
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Click to expand...
Click to collapse
you should already have the update.zip.
use same one you "manualy" installed.
winrar did not work for me but 7-zip did.
there is also rom extractor built into "multi-tool" and stand alone extractor around here some where.
I found it here
the name is just like the twrp you flashed and just like the partition that you flashed. (recovery_ramdisk.img)
Thetpcguy said:
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Click to expand...
Click to collapse
Hi, so I figured Huawei update extractor app is the way to do it but I have a Mac and there doesn't seem to be a Mac version? is there a way to do it on android or Mac?
mrmazak said:
you should already have the update.zip.
use same one you "manualy" installed.
winrar did not work for me but 7-zip did.
there is also rom extractor built into "multi-tool" and stand alone extractor around here some where.
I found it here
the name is just like the twrp you flashed and just like the partition that you flashed. (recovery_ramdisk.img)
Click to expand...
Click to collapse
Hi, Thanks for all your replies. After doing a bit of search, I managed to get it extracted on my android using zarchiver app and I copied the recovery_ramdisk.img from that BNDL22.ZIP and when I tried flashing it using the fastboot command "fastboot flash recovery_ramdisk recovery.img" It went ok and It got installed but when I tried to boot into recovery, I got this screen "ERROR MODE" ATTENTION ETC.. I don't know where I'm going wrong?
Thetpcguy said:
Hi, Thanks for all your replies. After doing a bit of search, I managed to get it extracted on my android using zarchiver app and I copied the recovery_ramdisk.img from that BNDL22.ZIP and when I tried flashing it using the fastboot command "fastboot flash recovery_ramdisk recovery.img" It went ok and It got installed but when I tried to boot into recovery, I got this screen "ERROR MODE" ATTENTION ETC.. I don't know where I'm going wrong?
Click to expand...
Click to collapse
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
mrmazak said:
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
Click to expand...
Click to collapse
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
i am wipeiing my data it always show faild plss help my device is dead
Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
Which perticular file should i flash for stock recovery please. There are 4-5 files. Pl help. I am on RR and want to flash system.img to go back to oreo beta. But i think i do not have stock recovery as i had tried to flash twrp. Pl help
Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
Hey bro thefe are too many files there will it flash through fastboot or twrp and how to flash one by one pls help me
Hello all,
thanks for all the info in this thread.
I bricked my Honox 7x (BND-LC21) by trying to go Oreo.
The installation went halfway through, but now I can't complete (missing info howto flash bootloader / kernel) and I also can't go back as the partition layout has already changed to oreo style.
Steps done so far:
- unlocked boot loader
- installed twrp
- extract system image and recovery image from oreo update zip
getting the phone in fastboot mode i can successfully run
fastboot flash recovery_ramdisk recovery_ramdisk.img (i can also flash old recoveries this way, but none of them will successfully boot into recovery mode)
fastboot flash system system.img
either way, the system will not boot afterwards.
how do I manually flash bootloader / kernel on the oreo partition layout?
erecovery and hisuite won't recover my phone either...
Any hints appreciated
Aibiman
mrmazak said:
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
Click to expand...
Click to collapse
Can I flash just the stock recovery to my phone and if so is it the recover_ramdis.img, or do I need to flash them all. I'm on mostly stock bnd-l24. Unlocked bootloader TWRP and magisk for root. There's a new update and i wanted to flash stock recovery so I could update.
kingd421 said:
Can I flash just the stock recovery to my phone and if so is it the recover_ramdis.img, or do I need to flash them all. I'm on mostly stock bnd-l24. Unlocked bootloader TWRP and magisk for root. There's a new update and i wanted to flash stock recovery so I could update.
Click to expand...
Click to collapse
Yes that is the recovery.
But if you have root, update not going to work
mrmazak said:
Yes that is the recovery.
But if you have root, update not going to work
Click to expand...
Click to collapse
Will uninstalling magisk fix that or does the boot image have to be reflashed. Thank you for the quick response
kingd421 said:
Will uninstalling magisk fix that or does the boot image have to be reflashed. Thank you for the quick response
Click to expand...
Click to collapse
From magisk manager app should be a restore images option
mrmazak said:
From magisk manager app should be a restore images option
Click to expand...
Click to collapse
Sounds good. I appreciate it.
aibiman said:
Hello all,
thanks for all the info in this thread.
I bricked my Honox 7x (BND-LC21) by trying to go Oreo.
The installation went halfway through, but now I can't complete (missing info howto flash bootloader / kernel) and I also can't go back as the partition layout has already changed to oreo style.
Steps done so far:
- unlocked boot loader
- installed twrp
- extract system image and recovery image from oreo update zip
getting the phone in fastboot mode i can successfully run
fastboot flash recovery_ramdisk recovery_ramdisk.img (i can also flash old recoveries this way, but none of them will successfully boot into recovery mode)
fastboot flash system system.img
either way, the system will not boot afterwards.
how do I manually flash bootloader / kernel on the oreo partition layout?
erecovery and hisuite won't recover my phone either...
Any hints appreciated
Aibiman
Click to expand...
Click to collapse
can you in to TWRP?

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.

I tried to unroot my Honor 7X and failed

Hi,
So this morning I decided to root my phone (BND-L21)
I did it! But I realise I couldn't use Snapchat since being rooted didn't allow me. After going through various methods, I gave up and was left with the only guaranteed method, which was to unroot my phone.
I got stuck in a bootloop after pressing the unroot button in SuperSU.
I can access TWRP mode, Recovery mode, and the Rescue mode or something.
The Recovery mode which used wifi to reset my phone by installing a fresh rom had failed..
The rescue mode i have no idea what to do with (neither do I have any idea about ADB to help me out here)
In TWRP mode, i wiped everything and formatted data, hoping something would happen because nothing else did.
Everything I tried to do, I would just end up back in the booting screen with "Your device is.....booting...."
On my PC, it recognises my honor 7x in RECOVERY if I type in adb devices.
I'm believe I'm almost at a critical stage of turning my phone into a brick.
I tried downloading stock rom and installing it from TWRP mode but it came up with "UPDATER PROCESS ENDED WITH ERROR: 9"
Please help. I can't afford another one, nor do I have a backup phone. It says I have no current ROM if I intend to reboot my phone.
pausethegame said:
Hi,
So this morning I decided to root my phone (BND-L21)
I did it! But I realise I couldn't use Snapchat since being rooted didn't allow me. After going through various methods, I gave up and was left with the only guaranteed method, which was to unroot my phone.
I got stuck in a bootloop after pressing the unroot button in SuperSU.
I can access TWRP mode, Recovery mode, and the Rescue mode or something.
The Recovery mode which used wifi to reset my phone by installing a fresh rom had failed..
The rescue mode i have no idea what to do with (neither do I have any idea about ADB to help me out here)
In TWRP mode, i wiped everything and formatted data, hoping something would happen because nothing else did.
Everything I tried to do, I would just end up back in the booting screen with "Your device is.....booting...."
On my PC, it recognises my honor 7x in RECOVERY if I type in adb devices.
I'm believe I'm almost at a critical stage of turning my phone into a brick.
I tried downloading stock rom and installing it from TWRP mode but it came up with "UPDATER PROCESS ENDED WITH ERROR: 9"
Please help. I can't afford another one, nor do I have a backup phone. It says I have no current ROM if I intend to reboot my phone.
Click to expand...
Click to collapse
formating in twrp was not a good idea. These huawei phones have "other" files that system needs stored on /data. The stock recovery skips these files when doing a reset, twrp does not.
you should probably flash fullOTA to get back to working stock now.
try to follow this guide.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
mrmazak said:
formating in twrp was not a good idea. These huawei phones have "other" files that system needs stored on /data. The stock recovery skips these files when doing a reset, twrp does not.
you should probably flash fullOTA to get back to working stock now.
try to follow this guide.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
Click to expand...
Click to collapse
Um, the situation changed quite drastically.
I can't access TWRP anymore and when I plugged my phone in to my computer it detects it as a disk drive...
Can I still flash stock rom using sd card or anything else?
(Also, i sent it to a repair shop today and they'll get back to me tomorrow.)
pausethegame said:
Um, the situation changed quite drastically.
I can't access TWRP anymore and when I plugged my phone in to my computer it detects it as a disk drive...
Can I still flash stock rom using sd card or anything else?
(Also, i sent it to a repair shop today and they'll get back to me tomorrow.)
Click to expand...
Click to collapse
You asked in pm for details on hwota
I already give you link here for that .
mrmazak said:
You asked in pm for details on hwota
I already give you link here for that .
Click to expand...
Click to collapse
Oh ok. Will this method work even if I don't have any OS installed on my phone?
Also, are the 3 files you mentioned in your post refer to the ones within the filelist of Firmware Finder?
pausethegame said:
Oh ok. Will this method work even if I don't have any OS installed on my phone?
Also, are the 3 files you mentioned in your post refer to the ones within the filelist of Firmware Finder?
Click to expand...
Click to collapse
yes(should) and yes.
mrmazak said:
yes(should) and yes.
Click to expand...
Click to collapse
Ok. Do I extract the 3 update zips into the HWOTA folder or do I just copy the 3 update zips?
Thanks so much!!
pausethegame said:
Ok. Do I extract the 3 update zips into the HWOTA folder or do I just copy the 3 update zips?
Thanks so much!!
Click to expand...
Click to collapse
copy.

Can't flash twrp on note 5 AI MIUI Global 9.5 | Stable 9.5.5.0(OEIMIFA)

I was buy this phone a few days ago with ubl already. I think that was great because i don't need to unlock the bootloader by myself. Since this my first xiaomi phone, unlocking the bootloader may gave me headache. But when i tried to flash twrp, i face a problem that adb said "FAILED (remote: Requested download size is more than max allowed)". At the same time, in fastboot screen shown "press anykey to shutdown". Is somebody here know what must i do? I was spend at least six days looking for solution on internet.. but, still no luck. Hope someone here will help. Any suggestions will so appreciated.
-Sorry for my bad English
Additional info:
On me, isn't driver or port or my windows 10 problem like some people saying since i can run any fastboot commands (flashing twrp too) with another xiaomi phone.
Check this thread
https://forum.xda-developers.com/re...uide-fix-locking-bootloader-fake-ubl-t3833631
deathbearer said:
Check this thread
https://forum.xda-developers.com/re...uide-fix-locking-bootloader-fake-ubl-t3833631
Click to expand...
Click to collapse
Sorry for late replying.. Actually, i though fake UBL is not the problem since my device can bind mi account. I do research for 2 weeks and find nothing can solved this problem
Kratos-mgc said:
Sorry for late replying.. Actually, i though fake UBL is not the problem since my device can bind mi account. I do research for 2 weeks and find nothing can solved this problem
Click to expand...
Click to collapse
Get this zip : https://files.orangefox.website/OrangeFox-Stable/whyred/
Extract it.. find recovery.img and put it in your fastboot folder, run 'fastboot boot recovery.img'.. now, after going to recovery the device will show up as storage in Windows, and put the orange fox zip in internel memory and flash it with booted recovery....
DKWxda said:
Get this zip : https://files.orangefox.website/OrangeFox-Stable/whyred/
Extract it.. find recovery.img and put it in your fastboot folder, run 'fastboot boot recovery.img'.. now, after going to recovery the device will show up as storage in Windows, and put the orange fox zip in internel memory and flash it with booted recovery....
Click to expand...
Click to collapse
Thanks.. Downloading file right now. I thought i've done that before with older version of OrangeFox without luck. Have try with Official TWRP and RedWolf too with same result. But, will try with latest version like you said :highfive:
Kratos-mgc said:
Thanks.. Downloading file right now. I thought i've done that before with older version of OrangeFox without luck. Have try with Official TWRP and RedWolf too with same result. But, will try with latest version like you said :highfive:
Click to expand...
Click to collapse
Np .. post here what happened..
DKWxda said:
Np .. post here what happened..
Click to expand...
Click to collapse
Sure
DKWxda said:
Np .. post here what happened..
Click to expand...
Click to collapse
Same as before.. fail either. What should i gonna do now?
Actually, my phone already had twrp installed with custom rom too after 2 weeks use time. I can't find solution for my problem so i do unusually step (or you can say frustrating step). Do test point things and flash rom like usual. But, before i replace stock recovery with twrp and rename it like stock one. After that, just start flashing and when it finish, boot to recovery directly and flash magisk plus no verity. Then i got twrp and root.. But, still can't flash anything from fastboot, even flashing with miflash. Just curious what exactly the problem is. I know can repeat the same step just in case i got problem to boot and somehow can't boot to twrp too. But, you know.. that takes lot of time to do
I don't know if ur problem is solved by now, i think you should flash latest dev firmware, that might be the key, have you ever done that after the problem? You should use twrp to do that tho.. and pls take note, every firmware is not supported by everry recovery, but i trust orange fox, and don't try to downgrade firmware too, check always if the cutom rom support the firmware you gonna flash and also check ARB value...
Edit: what does this mean
replace stock recovery with twrp and rename it like stock one

A70 vbmeta error after magisk update 20.0

Hello everyone,
after many hours of research I couldn't find anyone with the same problem or any solution for this.
Recently (yesterday) magisk brought out a new update 20.0 and I got a notification so I opened magisk manager and clicked on update magisk auto (recommended). After it updated successfuly, a reboot button appeared on right bottom corner and I clicked it. After it turned off and on it went directly to download mode and of top of the screen there was this error:
"partition vbmeta
Reason vbmeta: Error verifying vbmeta image:
0_0_INDIVLDVMT_EDRHS_IMTHSGAUEMSAC"
Screenshots:
https://prnt.sc/pigzsh
https://prnt.sc/pih0ax
And after like 3-5 times I hardreset (VOL DOWN + POWER) then immediately press VOL UP + POWER to come into magisk root mode again, the device boot but I have no root anymore. And there is no auto update choice anymore at magisk. I tried also patching the official firmware again and flash it but didn't work, I'm still not rooted and I get always many times to download mode with this error if I reboot the device.
Did anything go wrong during magisk auto update?
If yes, why it said "update success"?
Do I have to update magisk? I used the auto update method the first time and I am deep in trouble.
What should I do to fix this and getting rooted again?
If possible without losing my files/wipe data.
My device: Galaxy A70 (SM-A705FN/DS)
Android 9
Thanks in advance
HH
Hello !
Dont worry, same here. Just install the unofficial twrp from step 4 (flashing vbmeta)
https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
Now your phone will be able to boot to twrp then to system
Follow step 5 for root.
I do that and my phone boot again and magisk updated.
You will lose nothing, easy and fast
Good luck !
PS : dont know Why we have this problem. But this solution work for me.
Vmbeta Image
Hello, could you please post the original stock vmbeta image, i can't get out of that screen in the screenshots without flashing it and i am very stressed.
Please help me?
xeedes said:
Hello, could you please post the original stock vmbeta image, i can't get out of that screen in the screenshots without flashing it and i am very stressed.
Please help me?
Click to expand...
Click to collapse
hello xeedes, what screen you have ?
the same as "partition vbmeta
Reason vbmeta: Error verifying vbmeta image:
0_0_INDIVLDVMT_EDRHS_IMTHSGAUEMSAC" ???
try twrp maybe ?
flash with odin.
what have you done to get screw to that screen ?
ps : i think this screen mean you have try to modify partition system with stock vbmeta. stock vbmeta does not allow modifications. maybe... i dont know exactly ^^
Ial69 said:
hello xeedes, what screen you have ?
the same as "partition vbmeta
Reason vbmeta: Error verifying vbmeta image:
0_0_INDIVLDVMT_EDRHS_IMTHSGAUEMSAC" ???
try twrp maybe ?
flash with odin.
what have you done to get screw to that screen ?
ps : i think this screen mean you have try to modify partition system with stock vbmeta. stock vbmeta does not allow modifications. maybe... i dont know exactly ^^
Click to expand...
Click to collapse
I tried to relock the bootloader when flashing a modified vbmeta, now its stuck and will only continue if i flash the stock vbmeta i assume. yes its the exact same screen and message and this phone won't let me flash anything :/ nor exit the screen with any key commands, just flashes a70 and immediately goes back to the said screen
xeedes said:
I tried to relock the bootloader when flashing a modified vbmeta, now its stuck and will only continue if i flash the stock vbmeta i assume. yes its the exact same screen and message and this phone won't let me flash anything :/ nor exit the screen with any key commands, just flashes a70 and immediately goes back to the said screen
Click to expand...
Click to collapse
I think you need custom recovery if you're stuck on this screen.
its a good news your phone boot in download mode and is detected by odin.
dont relock bootloader. (maybe... if you know what you do forget that ^^)
if you want stock vbmeta try to download all the stock rom from samfirm.
then flash all the stock rom ( if possible, verify the requirements)
hope this help.
ps : cant post link to samfirm because the forum lock me to post external link....(because im a new user)
and you need to have unlock your bootloader to flash, bad things can happens with a lock bootloader. like brick.
Ial69 said:
I think you need custom recovery if you're stuck on this screen.
its a good news your phone boot in download mode and is detected by odin.
dont relock bootloader. (maybe... if you know what you do forget that ^^)
if you want stock vbmeta try to download all the stock rom from samfirm.
then flash all the stock rom ( if possible, verify the requirements)
hope this help.
Click to expand...
Click to collapse
hey, thank you for the reply, i've tried flashing the stock rom but nothing happens. downloading it from samfirm though. im going to sleep. thank you for the help
its really that hard guys, no one can root this device without having vbmeta and magisk problems,
it has been 6 months since this phone released
emadhussein said:
its really that hard guys, no one can root this device without having vbmeta and magisk problems,
it has been 6 months since this phone released
Click to expand...
Click to collapse
never got problems like that , as long as you follow tutorial it's fine , a blank vbmeta image have to be flashed in order to bypass boot verifications like theses , it's not that hard...
I've attempted to flash the stock rom but when i do, i get this.
https://ibb.co/mqhCKfc
Any thoughts?
xeedes said:
I've attempted to flash the stock rom but when i do, i get this.
https://ibb.co/mqhCKfc
Any thoughts?
Click to expand...
Click to collapse
Reboot phone and pc. Then retry to flash TWRP. The phone will boot fine.
this work for me.
I root this phone with magisk at first time. no problem...
follow tuto.
for magisk :
https://forum.xda-developers.com/galaxy-a70/how-to/to-root-magisk-odin-t3930099
for TWRP :
https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
i have vbmeta error too, bypass with TWRP. cant help you more than that, sorry....
BK said:
never got problems like that , as long as you follow tutorial it's fine , a blank vbmeta image have to be flashed in order to bypass boot verifications like theses , it's not that hard...
Click to expand...
Click to collapse
Everything was fine till magisk got update v20
I got vbmeta error in the download mood , even tho i flashed vbmeta file , any idea how to fix
emadhussein said:
Everything was fine till magisk got update v20
I got vbmeta error in the download mood , even tho i flashed vbmeta file , any idea how to fix
Click to expand...
Click to collapse
to update magisk you have to patch a recovery.img with magisk then install it with TWRP/odin.
just like the first time you get root with magsik ?
Ial69 said:
to update magisk you have to patch a recovery.img with magisk then install it with TWRP/odin.
just like the first time you get root with magsik ?
Click to expand...
Click to collapse
yes i did that, but i end up with vbmeta error , i flashed vbmeta but still
emadhussein said:
yes i did that, but i end up with vbmeta error , i flashed vbmeta but still
Click to expand...
Click to collapse
sorry, do you have try to install twrp ? he cause the vbmeta error ?
what odin says ?
Do you have reboot phone and pc before each try ?
need to uncheck autoreboot in odin too, like even.
Thanks for every answer, I didn't try flashing TWRP but I will try when I go home. Seems like it fix the problem for alot of people. Thanks guys I will tell you if it worked for me or not.
emadhussein said:
yes i did that, but i end up with vbmeta error , i flashed vbmeta but still
Click to expand...
Click to collapse
Better try flash twrp since it works for many.
Read all answers in this thread.
HornyHugo said:
Thanks for every answer, I didn't try flashing TWRP but I will try when I go home. Seems like it fix the problem for alot of people. Thanks guys I will tell you if it worked for me or not.
Better try flash twrp since it works for many.
Read all answers in this thread.
Click to expand...
Click to collapse
this is what i say from the beginning.
Ial69 said:
Hello !
Dont worry, same here. Just install the unofficial twrp from step 4 (flashing vbmeta)
https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
Now your phone will be able to boot to twrp then to system
Follow step 5 for root.
I do that and my phone boot again and magisk updated.
You will lose nothing, easy and fast
Good luck !
PS : dont know Why we have this problem. But this solution work for me.
Click to expand...
Click to collapse
But step 4 says after flashing vbmeta.tar you need to go to recovery mode and wipe data. And this will make me lose all data. Do I need to flash vbmeta if I flash twrp?
HornyHugo said:
But step 4 says after flashing vbmeta.tar you need to go to recovery mode and wipe data. And this will make me lose all data. Do I need to flash vbmeta if I flash twrp?
Click to expand...
Click to collapse
If you already unlocked your bootloader, start with step 3.
If you are already rooted, start with step 4.
4 - Time to flash recovery. Download (link is at the end of this post) the latest version as zip and extract it. You should end up with one single file named recovery.img. Pack it as tar with 7zip or any other compression tool you prefer. This packed tar file should only contain recovery.img and nothing else, also make sure the name is still recovery.img, otherwise Odin will refuse to flash it. In Odin put the tar file in AP and simply hit start. Congrats you now have TWRP installed!
You begin from step 4. step 4 no need to wipe.
wipe is for step 3.
you are already unlock and rooted your phone if you have tried to update magisk and get stuck on vbmeta error.
ps : just do step 4. flashing recovery. then step 5 for root access ^^
good luck !
xeedes said:
I've attempted to flash the stock rom but when i do, i get this.
https://ibb.co/mqhCKfc
Any thoughts?
Click to expand...
Click to collapse
just connect your device to computer with cable and boot it with volume buttons

Categories

Resources