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.
Related
I was on February stock image with twrp and magisk and elemental X kernal installed prior and had everything functioning properly since the febuary update but just installed flux theme within substratum and when i applied overlay my screen went black with only status bar icons showing ...so i rebooted phone and for some reason it boots and hangs on the google loading page then boots to twrp ...unfortunatly i had password/fingerprint lock on so twrp wont decrypt , i tried using adb/fastboot to try and do a flash all bat but fastboot message says fastboot is not recongnized as an internal or external command , operable program or batch file ... i have the -w removed from the flash all bat , i'm wondering if it wont flash because adb setting isn't on in developer settings..... dont know what to do or how to fix :crying:
If anyone could help or offer advice it would be greatly appreciated
Mr. Blanco said:
I was on February stock image with twrp and magisk and elemental X kernal installed prior and had everything functioning properly since the febuary update but just installed flux theme within substratum and when i applied overlay my screen went black with only status bar icons showing ...so i rebooted phone and for some reason it boots and hangs on the google loading page then boots to twrp ...unfortunatly i had password/fingerprint lock on so twrp wont decrypt , i tried using adb/fastboot to try and do a flash all bat but fastboot message says fastboot is not recongnized as an internal or external command , operable program or batch file ... i have the -w removed from the flash all bat , i'm wondering if it wont flash because adb setting isn't on in developer settings..... dont know what to do or how to fix :crying:
If anyone could help or offer advice it would be greatly appreciated
Click to expand...
Click to collapse
Your likely going to have to do a clean flash of the factory image, and wipe it clean since you can't get into twrp to restore your backup. However, it also sounds like your device is not being recognized by adb/fastboot. When your in fastboot mode, and type fastboot devices, do you get your phone ID displayed?? Also, are your SDK/platform-tools up to date??
Badger50 said:
Your likely going to have to do a clean flash of the factory image, and wipe it clean since you can't get into twrp to restore your backup. However, it also sounds like your device is not being recognized by adb/fastboot. When your in fastboot mode, and type fastboot devices, do you get your phone ID displayed?? Also, are your SDK/platform-tools up to date??
Click to expand...
Click to collapse
I'm using sdk platform tools dec, 27.0.1 so i believe it is the most up to date version and when i fastboot devices i do get a serial number - fastboot showing , which is what kind of confused me , did the flash all bat and got that message as i posted before and the only thing i have changed in it was removing the -w ... so kind of scratching my head here why it's not working ... do you have any ideas what i might be able to do to fix
Mr. Blanco said:
I'm using sdk platform tools dec, 27.0.1 so i believe it is the most up to date version and when i fastboot devices i do get a serial number - fastboot showing , which is what kind of confused me , did the flash all bat and got that message as i posted before and the only thing i have changed in it was removing the -w ... so kind of scratching my head here why it's not working ... do you have any ideas what i might be able to do to fix
Click to expand...
Click to collapse
Are you typing the command, or double clicking the script??
Your definitely up to date on SDK BTW ?
Badger50 said:
Your likely going to have to do a clean flash of the factory image, and wipe it clean since you can't get into twrp to restore your backup. However, it also sounds like your device is not being recognized by adb/fastboot. When your in fastboot mode, and type fastboot devices, do you get your phone ID displayed?? Also, are your SDK/platform-tools up to date??
Click to expand...
Click to collapse
i'm really embarrassed ... i was using the flash all bat from with in the factory image and not the platform tools file .. i sincerely apologize for posting this thread , this was definitely a user error ....is there a way to delete this embarrassing thread ...lol
Mr. Blanco said:
i'm really embarrassed ... i was using the flash all bat from with in the factory image and not the platform tools file .. i sincerely apologize for posting this thread , this was definitely a user error ....is there a way to delete this embarrassing thread ...lol
Click to expand...
Click to collapse
Dude, there's nothing to be embarrassed about, most of us have been there, no big deal. However, I still don't think dirty flashing the factory image is going to fix it, hopefully it does, but essentially your not removing the files that's causing the ui to fail. But we shall see.
Badger50 said:
Dude, there's nothing to be embarrassed about, most of us have been there, no big deal. However, I still don't think dirty flashing the factory image is going to fix it, hopefully it does, but essentially your not removing the files that's causing the ui to fail. But we shall see.
Click to expand...
Click to collapse
well phone is back up and running completely stock now just about to flash twrp, and the flash kernal and magisk ...still not sure what caused this whole thing as i only installed flux substratum theme , phone was fine and fully functioning since last update ... and by the way thank you for reaching out to help me , i really appreciate it ....one thing that was strange though was when process what finished flashing , i got the corrupt device message warning before booting in to the os but everything seems fine so far
Mr. Blanco said:
well phone is back up and running completely stock now just about to flash twrp, and the flash kernal and magisk ...still not sure what caused this whole thing as i only installed flux substratum theme , phone was fine and fully functioning since last update ... and by the way thank you for reaching out to help me , i really appreciate it ....one thing that was strange though was when process what finished flashing , i got the corrupt device message warning before booting in to the os but everything seems fine so far
Click to expand...
Click to collapse
Glad your back up and running. Little FYI for you. Theme overlays can shut you down very quickly, as you now know. When twrp is working correctly, it's not as big deal, since you just go into twrp and flash the substratum rescue zip and all is well. So, going forward, if you want to theme, keep your lock screen security set to swipe or none until you are finished themeing. There is an adb way to push twrp to temporary cache so that you can use it. Here is the link if you want to learn how to do it ??
https://forum.xda-developers.com/pi...aimen-flash-kernel-1-00-t3702057/post75495348
Badger50 said:
Glad your back up and running. Little FYI for you. Theme overlays can shut you down very quickly, as you now know. When twrp is working correctly, it's not as big deal, since you just go into twrp and flash the substratum rescue zip and all is well. So, going forward, if you want to theme, keep your lock screen security set to swipe or none until you are finished themeing. There is an adb way to push twrp to temporary cache so that you can use it. Here is the link if you want to learn how to do it
https://forum.xda-developers.com/pi...aimen-flash-kernel-1-00-t3702057/post75495348
Click to expand...
Click to collapse
Yes i will using your advice when attempting to theme or make any other adjustments from now on ...just found out i removed the -w from the factory image and not the one in the platforms tools so once again i have lost all saved data and starting from scratch..... grrrrrrr .... lol and thank you for the link ! i'm figuring since i'm starting from scratch that maybe i could check out the DU rom that's out right now , just wondering if you have flashed and if so how do you like it so far
Mr. Blanco said:
Yes i will using your advice when attempting to theme or make any other adjustments from now on ...just found out i removed the -w from the factory image and not the one in the platforms tools so once again i have lost all saved data and starting from scratch..... grrrrrrr .... lol and thank you for the link ! i'm figuring since i'm starting from scratch that maybe i could check out the DU rom that's out right now , just wondering if you have flashed and if so how do you like it so far
Click to expand...
Click to collapse
Oh yeah! I'm running it, and it's really solid! Bout the only thing not working is the squeeze thingy, which I never use anyway, and some issues with wifi calling. Other than that, it's great! ??
Badger50 said:
Oh yeah! I'm running it, and it's really solid! Bout the only thing not working is the squeeze thingy, which I never use anyway, and some issues with wifi calling. Other than that, it's great!
Click to expand...
Click to collapse
That's awesome, glad to hear to that , and i can live with out squeeze and wifi calling i'm just about to give it a shot right now , wish me luck ..lol read your post on your/bajasur install instructions if it worked for you guys i'm hoping it will work for me ...... just to double check with you since you were able to get it up and running , is this the process ......
1. Be on February Security
2. Disable Security Pin in settings
3. Reboot to TWRP (Make backup if needed)
4. Factory Data Reset
5. Flash DU
6. Flash TWRP
7. Reboot ROM and set up without security
8. Reboot back to TWRP and flash latest Magisk
9. Reboot back to ROM and set up security
10. Done!
Mr. Blanco said:
That's awesome, glad to hear to that , and i can live with out squeeze and wifi calling i'm just about to give it a shot right now , wish me luck ..lol read your post on your/bajasur install instructions if it worked for you guys i'm hoping it will work for me ...... just to double check with you since you were able to get it up and running , is this the process ......
1. Be on February Security
2. Disable Security Pin in settings
3. Reboot to TWRP (Make backup if needed)
4. Factory Data Reset
5. Flash DU
6. Flash TWRP
7. Reboot ROM and set up without security
8. Reboot back to TWRP and flash latest Magisk
9. Reboot back to ROM and set up security
10. Done!
Click to expand...
Click to collapse
Yep, you got it. Justd don't wipe system in twrp! ?
Badger50 said:
Yep, you got it. Justd don't wipe system in twrp!
Click to expand...
Click to collapse
just booted into twrp and don't have touch functions , as i'm completly stock now , should i flash the flash kernal to get touch functions in twrp and then follow that process
Mr. Blanco said:
just booted into twrp and don't have touch functions , as i'm completly stock now , should i flash the flash kernal to get touch functions in twrp and then follow that process
Click to expand...
Click to collapse
Did you disable lock screen security first? Kinda hard to flash a kernel if you don't have touch functions. Unless you adb push it.
Badger50 said:
Did you disable lock screen security first? Kinda hard to flash a kernel if you don't have touch functions. Unless you adb push it.
Click to expand...
Click to collapse
Yes i disabled all security features ... lock screen / finger print but thinking i should have fastbooted twrp img and from with in the twrp img i should have flashed the Du rom zip and then the twrp zip ... is there a way to do the install with out touch functions like adb push ? never pushed anything to my device before and now wondering do i need to flash stock feb image again and then do the fastboot twrp img and from there flash the DU zip and then the permanent twrp zip ?
Mr. Blanco said:
Yes i disabled all security features ... lock screen / finger print but thinking i should have fastbooted twrp img and from with in the twrp img i should have flashed the Du rom zip and then the twrp zip ... is there a way to do the install with out touch functions like adb push ? never pushed anything to my device before and now wondering do i need to flash stock feb image again and then do the fastboot twrp img and from there flash the DU zip and then the permanent twrp zip ?
Click to expand...
Click to collapse
Try fastbooting the twrp.img first and see if you get it working fist :good:
Badger50 said:
Try fastbooting the twrp.img first and see if you get it working fist :good:
Click to expand...
Click to collapse
Boom shaka laka ...... i got it up and running i fastbooted the stock boot.img and the did the twrp.img thing and flashed the rom and twrp and everything is up and running now, so glad it all worked out and , going to attemp to flash magisk now ... do you know if the latest magisk works 15.4 or should i stick with 15.3 ? and by the way thank you for helping with this whole process , i'm really grateful , big time props to you for all your help !!!!
Mr. Blanco said:
Boom shaka laka ...... i got it up and running i fastbooted the stock boot.img and the did the twrp.img thing and flashed the rom and twrp and everything is up and running now, so glad it all worked out and , going to attemp to flash magisk now ... do you know if the latest magisk works 15.4 or should i stick with 15.3 ? and by the way thank you for helping with this whole process , i'm really grateful , big time props to you for all your help !!!!
Click to expand...
Click to collapse
Saaweeeeeeeeeeet! Good job man :good: Magisk 15.4 is working fine for me. And, your very welcome ??
Badger50 said:
Saaweeeeeeeeeeet! Good job man :good: Magisk 15.4 is working fine for me. And, your very welcome [/Q
i have a question , i got a message about a vendor image on my fist boot up , was just wondering if you did too and if thats just part of the package deal when using this rom
Click to expand...
Click to collapse
Mr. Blanco said:
Badger50 said:
Saaweeeeeeeeeeet! Good job man :good: Magisk 15.4 is working fine for me. And, your very welcome [/Q
i have a question , i got a message about a vendor image on my fist boot up , was just wondering if you did too and if thats just part of the package deal when using this rom
Click to expand...
Click to collapse
Some have reported the same on other AOSP roms. A possible fix, though not always successful, is to fastboot the vendor.img to both slots. The message is harmless, and won't cause any damage to your OS. It's just annoying at boot up is all ?
Click to expand...
Click to collapse
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?
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.
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
Hi! 2 days ago I just installed two updates (MIUI 12.5 or something, then MIUI 13 with Android 12) on my rooted POCO F3, I unrooted with magisk before every update, then when it requested to reboot, I installed back magisk. The updates were installed succesfuly and the phone was working properly until it shut down because of no battery. When I tried to turn it on the phone took like 5 minutes to get to the MIUI screen and then restarted directly in Recovery Mode. What can I do about it?
Also, can I flash it without losing data, I have photos and documents that I didn't back up?
Or can I just recover something from it?
Cosminxda said:
Hi! 2 days ago I just installed two updates (MIUI 12.5 or something, then MIUI 13 with Android 12) on my rooted POCO F3, I unrooted with magisk before every update, then when it requested to reboot, I installed back magisk. The updates were installed succesfuly and the phone was working properly until it shut down because of no battery. When I tried to turn it on the phone took like 5 minutes to get to the MIUI screen and then restarted directly in Recovery Mode. What can I do about it?
Also, can I flash it without losing data, I have photos and documents that I didn't back up?
Or can I just recover something from it?
Click to expand...
Click to collapse
Use twrp and check whether it can decrypt storage - A12 version by nebrassy
Rstment ^m^ said:
Use twrp and check whether it can decrypt storage - A12 version by nebrassy
Click to expand...
Click to collapse
I booted into twrp and it doesn't recognise the password that I use
Can I do something else?
Cosminxda said:
Can I do something else?
Click to expand...
Click to collapse
I have no idea... Try flashing stock boot image.
Download fastboot rom , unzip it. Open images folder and find boot.img
Fastboot flash boot_ab boot.img
If that doesn't work either try skkk twrp
Rstment ^m^ said:
I have no idea... Try flashing stock boot image.
Download fastboot rom , unzip it. Open images folder and find boot.img
Fastboot flash boot_ab boot.img
Click to expand...
Click to collapse
If I try this will my data get erased?
Rstment ^m^ said:
If that doesn't work either try skkk twrp
Click to expand...
Click to collapse
DUDE THANK YOU! I tried this and I got access to all my files, now I just want to know, is it possible to restore my phone or I just have to get file after file from it?
Cosminxda said:
DUDE THANK YOU! I tried this and I got access to all my files, now I just want to know, is it possible to restore my phone or I just have to get file after file from it?
Click to expand...
Click to collapse
I suggest flash original boot.img if you wanna try restoring phone... This only removes magisk. Tho if you have pc and you're gonna be downloading fastboot rom anyways might as well do a clean flash instead - flash_all.bat file
Especially since you used skkk twrp... It's sources don't exist , so run the files you pulled from it through antivirus of some sorts and flash phone with stock rom
How did it happen anyways? You deleted magisk via app, then flashed it via PC before phone booted from OTA?
you can flash latest rom from xiaomi using the mi flash tool without losing user data
Rstment ^m^ said:
I suggest flash original boot.img if you wanna try restoring phone... This only removes magisk. Tho if you have pc and you're gonna be downloading fastboot rom anyways might as well do a clean flash instead - flash_all.bat file
Especially since you used skkk twrp... It's sources don't exist , so run the files you pulled from it through antivirus of some sorts and flash phone with stock rom
How did it happen anyways? You deleted magisk via app, then flashed it via PC before phone booted from OTA?
Click to expand...
Click to collapse
I will try to do that. Is the command fastboot flash boot_ab boot.img?
So i searched for a fast method to upgrade my phone without losing root on youtube because I already didn't upgrade it from when I bought it. I did exactly what he did in the video twice, because I had 2 updates, this is the vid
After I did all of that, everything went well only for one day until my phone shut down because of programmed shut down and startup (I chose it for battery saving lol), yeah it shut down at 12am when I was awake, I tried starting it again when I found myself in a bootloop. And this is how it got stuck in a bootloop.
You need to do a data format..
Andreasgbrv2 said:
You need to do a data format..
Click to expand...
Click to collapse
Rstment ^m^ said:
I suggest flash original boot.img if you wanna try restoring phone... This only removes magisk. Tho if you have pc and you're gonna be downloading fastboot rom anyways might as well do a clean flash instead - flash_all.bat file
Especially since you used skkk twrp... It's sources don't exist , so run the files you pulled from it through antivirus of some sorts and flash phone with stock rom
How did it happen anyways? You deleted magisk via app, then flashed it via PC before phone booted from OTA?
Click to expand...
Click to collapse
Thank you again!!!! I booted boot.img and repaired my phone, the only problem is that the dialer app lost it's name (it's named com.google.something dialer) and it's icon, oh it also crashes
Andreasgbrv2 said:
You need to do a data format..
Click to expand...
Click to collapse
I don't think so, i recovered my phone for now
Thank you everyone for helping me, especially Rstment ^m^! I rooted my phone back again and everything works without any corrupted files!
Cosminxda said:
Thank you everyone for helping me, especially Rstment ^m^! I rooted my phone back again and everything works without any corrupted files!
Click to expand...
Click to collapse
Can you help me?