[SOLVED] Poco X3 NFC - Bootloop after Wiping & Flashing Custom ROM - Xiaomi Poco X3 NFC Questions & Answers

Hello, today I wiped Dalvik / ART Cache, Cache and Data because I wanted to install Custom ROM.
Maybe I also accidentally wiped Internal Storage or System. Then I flashed the Custom ROM. Now after the Custom ROM flashes again, the boot animation will hang and then the phone will restart shortly. I don't know how to solve this situation. I tried to flash the MIUI using the Xiaomi Mi Flash Tool, install the ROM through Fastboot, but nothing worked.
Please anyone know what to do with this? Thank you

DrakMC said:
Hello, today I wiped Dalvik / ART Cache, Cache and Data because I wanted to install Custom ROM.
Maybe I also accidentally wiped Internal Storage or System. Then I flashed the Custom ROM. Now after the Custom ROM flashes again, the boot animation will hang and then the phone will restart shortly. I don't know how to solve this situation. I tried to flash the MIUI using the Xiaomi Mi Flash Tool, install the ROM through Fastboot, but nothing worked.
Please anyone know what to do with this? Thank you
Click to expand...
Click to collapse
You didn't explain your Problem quite well. Does it reboot to fastboot or does it reboot to system? (aka a Bootloop). if it reboots to system, here's what to do:
Boot into a custom recovery (twrp/Orangefox) and flash the required recovery MIUI ROM mentioned in your custom ROM's thread instructions.
Flash the custom ROM/Gapps, followed by Formatting /data using the Advanced Options in the wipe menu.
Reboot.
If you can't find the format option (which is mandatory before a new boot of a custom ROM), you can use this command while in fastboot mode:
Code:
fastboot erase userdata
Formatting /data is required for Encrypted devices to reset the encryption key and avoid a Bootloop. Please refer to this thread for more Custom ROM flashing instructions. If all else fails, you could EDL flash your device through MI flash tool/Command line, this process costs money (you need an Authorized Xiaomi Account) to complete.

Thank you very much for your help!
Slim K said:
Does it reboot to fastboot or does it reboot to system? (aka a Bootloop).
Click to expand...
Click to collapse
It depends when. When the MIUI flashes through the Mi Flash Tool, the Poco logo is displayed and the phone restarts and the Poco logo is displayed again. All the time.
So I followed your instructions.
I would like to flash ArrowOS, but nowhere do they write what version of MIUI I need. That's why I flashed this version of MIUI through Mi Flash Tool: https://xiaomifirmwareupdater.com/miui/surya/stable/V12.0.8.0.QJGMIXM/
After I flashed MIUI using Mi Flash Tool and then I booted into TWRP and installed the downloaded ArrowOS. After installation, I went to the Wipe section and deleted the Data. Then I restarted the phone to System. The Poco logo was displayed and after a while the phone booted into TWRP. So I don't know where the problem is. (Before ArrowOS flashed, the cell phone tried to boot into the system, the Poco logo was still displayed, and then the phone restarted.)

DrakMC said:
Thank you very much for your help!
It depends when. When the MIUI flashes through the Mi Flash Tool, the Poco logo is displayed and the phone restarts and the Poco logo is displayed again. All the time.
So I followed your instructions.
I would like to flash ArrowOS, but nowhere do they write what version of MIUI I need. That's why I flashed this version of MIUI through Mi Flash Tool: https://xiaomifirmwareupdater.com/miui/surya/stable/V12.0.8.0.QJGMIXM/
After I flashed MIUI using Mi Flash Tool and then I booted into TWRP and installed the downloaded ArrowOS. After installation, I went to the Wipe section and deleted the Data. Then I restarted the phone to System. The Poco logo was displayed and after a while the phone booted into TWRP. So I don't know where the problem is. (Before ArrowOS flashed, the cell phone tried to boot into the system, the Poco logo was still displayed, and then the phone restarted.)
Click to expand...
Click to collapse
Again, when I say FORMAT, I meant formatting by typing ”yes".
Also, you haven't looked at the ArrowOS thread close enough, see:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It says latest R firmware, basically V12.0.7.0.RJGEUXM. Another point I mentioned is the fact that a recovery MIUI is flashable through TWRP/Orangefox and not Fastboot/Mi flash tool, It comes in a .zip archive.
Regarding returning to stock, have you tried booting into stock recovery after fastboot flash and factory resetting? That could work.

Okay, I downloaded this ROM: https://xiaomifirmwareupdater.com/miui/surya/stable beta/V12.0.7.0.RJGEUXM/
I tried it to install it in TWRP and I got error 1:
I'm using TWRP 3.5.2_10-1-surya.

DrakMC said:
Okay, I downloaded this ROM: https://xiaomifirmwareupdater.com/miui/surya/stable beta/V12.0.7.0.RJGEUXM/
I tried it to install it in TWRP and I got error 1:
View attachment 5307411
I'm using TWRP 3.5.2_10-1-surya.
Click to expand...
Click to collapse
Error 1 just means a mismatch between the underlying stock and the newly flashed ROM, just ignore it and flash ArrowOS, Format data and reboot. If it still doesn't work, then return to stock through fastboot. (I never encountered so many problems as you did)

I followed your instructions. When I turn on smartphone, the Poco logo is displayed, then the ArrowOS animation will appear and freezes. After a while, the mobile phone restarts and this is repeated over and over again. (If I flash MIUI using the Mi Flash Tool, I also have a bootloop.)

I finally fixed the bootloop!
It was enough to take persist.img and flash it in TWRP before flashing MIUI via Mi Flash Tool.
Thank you very much everyone for your help!

just logged to thank u, mine was bricked too since an unsuccessful downgrade try, and I forgot to disable lock option in MiFlash, so I needed to wait 1 week to unlock bootloader again. I've tried everything, but ur post have saved me. ty very much for ur help, this tip can help a lot of ppl in the future. have a great weekend!

sevachcomunist4 said:
just logged to thank u, mine was bricked too since an unsuccessful downgrade try, and I forgot to disable lock option in MiFlash, so I needed to wait 1 week to unlock bootloader again. I've tried everything, but ur post have saved me. ty very much for ur help, this tip can help a lot of ppl in the future. have a great weekend!
Click to expand...
Click to collapse
You're welcome! I'm glad I could help someone! It took me about 40+ hours to resolve this issue before trying all possible methods.

DrakMC said:
I finally fixed the bootloop!
It was enough to take persist.img and flash it in TWRP before flashing MIUI via Mi Flash Tool.
Thank you very much everyone for your help!
Click to expand...
Click to collapse
please give me link

DrakMC said:
I finally fixed the bootloop!
It was enough to take persist.img and flash it in TWRP before flashing MIUI via Mi Flash Tool.
Thank you very much everyone for your help!
Click to expand...
Click to collapse
You literally saved my life bro. Why??? Flashed 30 times from fastboot and nothing. Just did what you said and phone booted smooth like a charm.

DP FH said:
You literally saved my life bro. Why??? Flashed 30 times from fastboot and nothing. Just did what you said and phone booted smooth like a charm.
Click to expand...
Click to collapse
You are welcome. I'm glad I could help someone.
I was whole week without the phone until I've fixed it. It took me over 40 hours to fix the issue.

Related

Please help, I'm stuck.

Hi everyone, I'm at a loss at what to do here.
I've attempted to unlock my phone which I've done successfully,flash the twrp image, and install the twrp zip but now because I'm running into issues, I just want to return to stock, I'm stuck in between. I thought if I flashed stock img from google and started over it would fix everything - but when I do flash stock img I get "not enough storage" and i cannot proceed. I've searched up and down this forum for an answer but to no avail. I'd appreciate the help
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have you updated your adb and fastboot? I've heard of a lot of problems cause by people's "minimal" setups being outdated. Also, there's a good chance you can get back to working simply by flashing the stock boot.img out of the system image you've already downloaded.
I think I have updated everything properly. At least, I think so.
When I try to flash just the system.img it hangs here;
OK, update. I was able to get NFM26Q to load up but it says my internal storage is corrupt upon booting and it doesn't recognize my SIM card (on Verizon). Should I flash a different factory image file? Or try something else? Thanks for any help.
iainaaldrich said:
Hi everyone, I'm at a loss at what to do here.
I've attempted to unlock my phone which I've done successfully,flash the twrp image, and install the twrp zip but now because I'm running into issues, I just want to return to stock, I'm stuck in between. I thought if I flashed stock img from google and started over it would fix everything - but when I do flash stock img I get "not enough storage" and i cannot proceed. I've searched up and down this forum for an answer but to no avail. I'd appreciate the help
Click to expand...
Click to collapse
I thought I saw that re-locking a Verizon bootloader would cause possible instability and would not be supported. I'm not sure if you're still under warranty but you might want to look into a replacement if you can't get it figured out. If you successfully relocked it then you should be ok under service.
I think at this point you might want to try a factory/reset in the stock recovery menu and see if Q loads up. Without seeing where you are and what you've done it's hard to diagnose.
bobby janow said:
I thought I saw that re-locking a Verizon bootloader would cause possible instability and would not be supported. I'm not sure if you're still under warranty but you might want to look into a replacement if you can't get it figured out. If you successfully relocked it then you should be ok under service.
I think at this point you might want to try a factory/reset in the stock recovery menu and see if Q loads up. Without seeing where you are and what you've done it's hard to diagnose.
Click to expand...
Click to collapse
First thing I did was unlock the phone, second thing I did was flash the IMG for twrp, booted into twrp and flashed the zip. I couldn't get past twrp, if I restarted the phone, it would just get stuck at twrp. So, I had no OS to boot into somehow and so at this point, I flashed the stock 7.1 file from Google and now it boots into the OS with no twrp, or bootloader, but the OS boots with an error message saying the internal storage is corrupt. I can use the phone but I have no data connection, camera fails to load, etc etc. So it's pretty useless. I made the mistake of thinking it would just be as easy as a Nexus, which clearly, it's not. I think I got everything I did there. I'm just trying to figure out how to get it back to stock, like right out if the box. My mistake surely, I'm just hoping someone can explain the necessary steps to get back to point A. Thanks for your help.
Maybe I need to lock the bootloader lock this phone again then flash stock IMG from Google for the OS?
I'm at a complete loss. I've tried almost everything I've read on XDA, and elsewhere.
iainaaldrich said:
First thing I did was unlock the phone, second thing I did was flash the IMG for twrp, booted into twrp and flashed the zip. I couldn't get past twrp, if I restarted the phone, it would just get stuck at twrp. So, I had no OS to boot into somehow and so at this point, I flashed the stock 7.1 file from Google and now it boots into the OS with no twrp, or bootloader, but the OS boots with an error message saying the internal storage is corrupt. I can use the phone but I have no data connection, camera fails to load, etc etc. So it's pretty useless. I made the mistake of thinking it would just be as easy as a Nexus, which clearly, it's not. I think I got everything I did there. I'm just trying to figure out how to get it back to stock, like right out if the box. My mistake surely, I'm just hoping someone can explain the necessary steps to get back to point A. Thanks for your help.
Click to expand...
Click to collapse
First, if you haven't already done so, update your adb/fastboot setup to the latest version. I see you're using minimal adb. The latest version is 1.4.1. You can get it here. From the looks of your first screenshot I'd guess you need to update. Whatever the case, run the flashall batch file again. I don't know how long you let it sit at flashing system but I've flashed mine a couple times and it hangs on system for what seems forever. It looks like it's not doing a thing but if you wait long enough, eventually it jumps to life and continues. Give it time. How long? I don't really know. Guessing mine hung there for at least 5 minutes, maybe more.
iainaaldrich said:
Maybe I need to lock the bootloader lock this phone again then flash stock IMG from Google for the OS?
I'm at a complete loss. I've tried almost everything I've read on XDA, and elsewhere.
Click to expand...
Click to collapse
Is your bootloader unlocked at this point? Have you tried a factory/reset from the stock recovery menu if you are not. If you are you can look for instructions on how to flash a factory image manually, which includes all the necessary files such as recovery, radio, bl, vendor etc. Just don't flash 7.1.1 yet. Get the phone working first on 7.1 (X) version preferably.
robocuff said:
First, if you haven't already done so, update your adb/fastboot setup to the latest version. I see you're using minimal adb. The latest version is 1.4.1. You can get it here. From the looks of your first screenshot I'd guess you need to update. Whatever the case, run the flashall batch file again. I don't know how long you let it sit at flashing system but I've flashed mine a couple times and it hangs on system for what seems forever. It looks like it's not doing a thing but if you wait long enough, eventually it jumps to life and continues. Give it time. How long? I don't really know. Guessing mine hung there for at least 5 minutes, maybe more.
Click to expand...
Click to collapse
Thanks, I'll try this again. The last time I tried, it just froze. But good point.
bobby janow said:
Is your bootloader unlocked at this point? Have you tried a factory/reset from the stock recovery menu if you are not. If you are you can look for instructions on how to flash a factory image manually, which includes all the necessary files such as recovery, radio, bl, vendor etc. Just don't flash 7.1.1 yet. Get the phone working first on 7.1 (X) version preferably.
Click to expand...
Click to collapse
When I boot up it has the unlocked logo, but if I try to boot into recovery I simply get "no command" with an exclamation point above the Android logo. So I'm not able to do a factory/reset from the recovery menu. I'll try refreshing everything again but I kept getting "not enough storage" or a similar error message.
iainaaldrich said:
When I boot up it has the unlocked logo, but if I try to boot into recovery I simply get "no command" with an exclamation point above the Android logo. So I'm not able to do a factory/reset from the recovery menu. I'll try refreshing everything again but I kept getting "not enough storage" or a similar error message.
Click to expand...
Click to collapse
In recovery with the no command logo, hold down the power key and hit the vol up key. That will get you into recovery where you can do those things. Use the vol keys to go up and down in the menu. Google stock recovery in android 7.1 for screenshots and more detailed instructions if you need.
I was able to get everything back up and running by following method 2 here - manually flashing using minimal adb: http://www.theandroidsoul.com/flash-firmware-factory-image-google-pixel/ and using the verizon 7.1 image from google's site, then updated to 7.1.1 on an unlocked bootloader, everything is working fine, however I am having one issue - seems as though the system flashed twice? I should have a lot more storage than this:
Is there a way to completely wipe everything and manually reflash the stock image?
Anybody know what I can do to wipe everything and start fresh? My bootloader is already unlocked. Thank you!
iainaaldrich said:
Maybe I need to lock the bootloader lock this phone again then flash stock IMG from Google for the OS?
I'm at a complete loss. I've tried almost everything I've read on XDA, and elsewhere.
Click to expand...
Click to collapse
Do not relock your bootloader. Ever.
Get your fastboot up to date, and use the flash all script that comes with the factory image.
Sent from my Pixel XL using XDA Labs
TonikJDK said:
Do not relock your bootloader. Ever.
Get your fastboot up to date, and use the flash all script that comes with the factory image.
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
Yeah, I'm not going to. I got it working by flashing it manually, the flash all script didn't work. How do I erase everything? Because for some reason now, my system image takes up almost all of my internal storage. It's as if, I have multiple system images on the same device...or something....
iainaaldrich said:
Yeah, I'm not going to. I got it working by flashing it manually, the flash all script didn't work. How do I erase everything? Because for some reason now, my system image takes up almost all of my internal storage. It's as if, I have multiple system images on the same device...or something....
Click to expand...
Click to collapse
Is this a 128 or 32? 128 often misreports space after flash. Have to factory reset to get it back.
Sent from my Pixel XL using XDA Labs
TonikJDK said:
Is this a 128 or 32? 128 often misreports space after flash. Have to factory reset to get it back.
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
No, 32. It's reporting correctly, but I don't get why it's taking up so much space.
iainaaldrich said:
No, 32. It's reporting correctly, but I don't get why it's taking up so much space.
Click to expand...
Click to collapse
How much does storage say system is using?
Sent from my Pixel XL using XDA Labs

[TOOL] Huawei Multi-Tool v8 by Team MT

Huawei Multi-Tool by Team MT​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download Link:
Project downloads
Description:
The application is based on working with fastboot and adb modes of Huawei and Honor smartphones. Allows you to perform many actions with any device on the processor Kirin and Qualcomm. If you are new to Huawei devices, the utility will help open the bootloader, put TWRP, get root and so on without knowing the command line. For the advanced — it’s an affordable and powerful utility instead of the command line. The utility of the utility grows every day.
The utility’s functionality is divided into BASIC and ADVANCED. Basic have all supported devices. Advanced, only those whose full support is claimed.
Advanced is marked in orange color below.
Capabilities:
Auto-update to the current version (updates itself).
Change the language of the utility (RU / EN / CN).
Installing Custom Recovery / eRecovery (TWRP).
Assistant for installing custom SuperSu (Root).
Reboot to Recovery | eRecovery | Fastboot & Rescue mode.
Custom firmware BOOT.img.
Flashing the images of boot, cust, recovery, system, userdata.
Unlock / Lock bootloader (with saving key locally and to the Team MT cloud )
Unbrick.
Installing All Drivers for Huawei Devices.
Install Huawei HiSuite.
Installing Huawei Update Extractor.
Installing DC Unlocker.
Installing DC Phoenix.
Enabling hidden / disabled EMUI functions without Root.
Installing TWRP.
Installing TWRP from the online database.
SuperSu Installation.
SuperSu Installation from the online database.
Installing the recovery.img, recovery2.img and boot.img run from the online database.
Install any* firmware (RUFI).
Operating system:
Windows 7 SP1 / 8.1 / 10 (Windows XP not available)
Linux / MAC OS — through virtual mashine.
Requirements: Install when requesting .NET 4.6.1
UI Languages: RU/EN/CN
Project Website: http://pro-teammt.ru/huawei-multi-tool
Support: Support chat in Telegram with us and community (RUS/ENG)
News: TeamMT News channel (RUS)
Tutorials: TeamMT YOUTUBE channel (RUS)
Developer: inside!out / Team MT /
XDA:DevDB Information
[TOOL] Huawei Multi-Tool v8 by Team MT, Tool/Utility for the Honor 8
Contributors
inside!out, greatslon, virusplus, redhaos (4pda), wolfhound88 (4pda), vovan1982 (4pda)
Version Information
Status: Beta
Beta Release Date: 2017-12-08
Created 2017-01-21
Last Updated 2019-11-27
There is change log link
Oline database change log​
Reserved
Good tool Thank you, just keep the translation going...
I don't find a download link from your website? Also original Multi-tool download link is missing? https://forum.xda-developers.com/honor-7/general/honor-7-multi-tool-t3281176
Are the Chinese versions *7.1.1x* "release" versions or "beta" versions and also: Do they include other languages, like English (to pick one out of a hat) ;?
I realize there'd be radio problems, etc, but am thinking of ways around it if each version includes all language capabilities.
Thanks.
Great tool, good job team
Where is download link?? The link just takes me to a empty XDA site...
HonorCasper said:
Where is download link?? The link just takes me to a empty XDA site...
Click to expand...
Click to collapse
UP!
I join the previous speaker. No working link.
HonorCasper: Check this thread also. It is some working link, but no the newest version.
what are these hidden functions you're talking about?
last version :
http://4pda.ru/pages/go/?u=http://hwmt.ru/blds/Huawei_Multi-Tool_by_Team_MT_v6.exe&e=51396624
but don't have the recovery of nougat honor 8, but in extras you can flash manually
Hi there! Yesterday i flashed B360 to my FRD-L09, and while trying to get twrp and root working things went south. Eventually I've wiped the data partition, performed a factory reset and flashed a b360 data package from one of the forum threads via twrp. This resulted in an non-fully functional system (couldn't use security tab in settings, updater wasn't even there, themes didn't work correctly etc.) I've tried to use the unbrick feature of the multitool to revert to B131, but it resulted in the system not booting at all. I've tried relocking the bootloader to be able to use the stock eRecovery or hisuite, but instead I've got the phone hanging on the blue screen with honor logo. I can restart it, but it won't respond to fastboot or recovery key combination. Is it a brick?
sysak said:
Hi there! Yesterday i flashed B360 to my FRD-L09, and while trying to get twrp and root working things went south. Eventually I've wiped the data partition, performed a factory reset and flashed a b360 data package from one of the forum threads via twrp. This resulted in an non-fully functional system (couldn't use security tab in settings, updater wasn't even there, themes didn't work correctly etc.) I've tried to use the unbrick feature of the multitool to revert to B131, but it resulted in the system not booting at all. I've tried relocking the bootloader to be able to use the stock eRecovery or hisuite, but instead I've got the phone hanging on the blue screen with honor logo. I can restart it, but it won't respond to fastboot or recovery key combination. Is it a brick?
Click to expand...
Click to collapse
Were you ever able to get into fastboot or recovery?
DanDroidOS said:
Were you ever able to get into fastboot or recovery?
Click to expand...
Click to collapse
Yes. First i lost recovery when i flashed the stock recovery with the mt-tool. I lost fastboot when i relocked the bootloader.
EDIT: Once the battery drained overnight, I was able to put it in fastboot. I've noticed that when i use the unbrick functionality the writing of 'cust' fails. Any way to force a full reflash of update.app? HiSuite says my device is unsupported and mt-tool doesn't seem to do the trick, unless the problem is in the software i'm trying to flash (L09C432B131).
sysak said:
Yes. First i lost recovery when i flashed the stock recovery with the mt-tool. I lost fastboot when i relocked the bootloader.
EDIT: Once the battery drained overnight, I was able to put it in fastboot. I've noticed that when i use the unbrick functionality the writing of 'cust' fails. Any way to force a full reflash of update.app? HiSuite says my device is unsupported and mt-tool doesn't seem to do the trick, unless the problem is in the software i'm trying to flash (L09C432B131).
Click to expand...
Click to collapse
I would try to flash TWRP in fastboot and use CM just so you can have a semi-working phone until you figure out the problem. Wish I could be of more help, but I'm a noob with the Honor. Hope you get it figured out, good luck.
DanDroidOS said:
I would try to flash TWRP in fastboot and use CM just so you can have a semi-working phone until you figure out the problem. Wish I could be of more help, but I'm a noob with the Honor. Hope you get it figured out, good luck.
Click to expand...
Click to collapse
Thanks for your help. Actually this was what I tried to do after fastboot started to work again. Unfortunately it's stuck on "patching system image unconditionally" and i can't wipe or format most partitions. It's something to do with f2fs vs ext 4 i think. Maybe I'll try various unoficial twrp releases. Anyway, I'm optimistic that I'll figure it out. At least it's not a brick. BTW, wiping entire internal storage is not a good idea with honor 8, am i right?
sysak said:
Thanks for your help. Actually this was what I tried to do after fastboot started to work again. Unfortunately it's stuck on "patching system image unconditionally" and i can't wipe or format most partitions. It's something to do with f2fs vs ext 4 i think. Maybe I'll try various unoficial twrp releases. Anyway, I'm optimistic that I'll figure it out. At least it's not a brick. BTW, wiping entire internal storage is not a good idea with honor 8, am i right?
Click to expand...
Click to collapse
The purpose of formatting the /data partition (and in turn internal storage) is merely to remove the /data partition encryption. I would suggest trying the Rollback package that Huawei offers to see if that does anything.
Guys, links and project repaired. Development in process. Translating too
inside!out said:
Guys, links and project repaired. Development in process. Translating too
Click to expand...
Click to collapse
If you need help for translating it in german i could help
xontec said:
If you need help for translating it in german i could help
Click to expand...
Click to collapse
Only English. And it's so hard

[cofface] [3.1.1-0]Twrp recovery for Huawei Nova2

Hi guys,
I made the TWRP from TeamWin official sources for Huawei Nova2 . You can download the img and flash it from fastboot.
Bootloader unlocked required!
Installation:
Unlock bootloader (skip if you have already unlocked it)
Reboot into fastboot mode
Flash using
Code:
HTML:
fastboot flash recovery cofface_pic_al00_recovery_en.img
Reboot
Download:
AndroidFileHost
Bugs:
When device is encrypted you can't see the files into recovery
Let me know if there are others
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc:fingers-crossed:
PAYPAL DONATION LINK
email:[email protected]
Unfortunately It is not working!
After flashing your file there is still the Huawei EMUI Bootloader and no TWRP. Bootloader was unlocked before. Fastboot was working fine.
Any idea?
Problem with Google GAPPS
Hi,
Thank you for your tuto and your ROM
I have bought my nova 2 in china.
Do you know how to install GAPPS. I have tried different version (stock, pico,.. ) but it's no use.
Do you know if I have to change the region first ?
Is it ok with your ROM ?
Regards
Perfect
Perfect, thank you!
Not working
Hello,
TWRP ist not working for me, I still have the EMUI bootloader after flash and reboot.
Boot into TWRP Recovery ("fastboot boot cofface_pic_al00_recovery_en.img") is aborted with:
"FAILED (remote: Command not allowed)"
Is there anything I've done wrong?
Thx!
dr.luther.1517 said:
Perfect, thank you!
Click to expand...
Click to collapse
did it work with your Nova 2?
i have got a demo device ( from germany ). Can some one upload his OEM info for a normal device ?
And yeah... it works
Success
Works very well, Thanks !
But ... while playing with it I lost the stock ROM for my Huawei Nova 2.
Since there is no download source available, could anybody share a stock ROM backup so I could restore using Twrp ?
Thanks !
My Nova 2 (PIC-LX9C432) automatically encrypts the disk after the first run, and then TWRP is unable to read /data partition nor do nandroid backups as a result. Can someone guide on how to disable encryption or get TWRP to decrypt data.
I read elsewhere that newer versions of TWRP are able to decrypt if you set a password / screen lock.
WARNING!!!! DO NOT FLASH THIS RECOVERY
Ideally cofface should remove this thread as flashing this recovery causes harm and no good. This TWRP port does not detect nor decrypt encryption on the 'data' partition and hence you will not be able to root your device nor take a nandroid backup.
What's worse, you will loose your recovery partition and will not be able to flash any other stock Nova 2 firmware updates.
If you have not yet flashed recovery and have the stock, please do a backup of your stock recovery and upload for the benefit of those who have lost it because of this recovery. See this thread...
https://forum.xda-developers.com/nova-2/help/help-restore-stock-recovery-t3741034
jusma said:
WARNING!!!! DO NOT FLASH THIS RECOVERY
Ideally cofface should remove this thread as flashing this recovery causes harm and no good. This TWRP port does not detect nor decrypt encryption on the 'data' partition and hence you will not be able to root your device nor take a nandroid backup.
What's worse, you will loose your recovery partition and will not be able to flash any other stock Nova 2 firmware updates.
If you have not yet flashed recovery and have the stock, please do a backup of your stock recovery and upload for the benefit of those who have lost it because of this recovery. See this thread...
https://forum.xda-developers.com/nova-2/help/help-restore-stock-recovery-t3741034
Click to expand...
Click to collapse
Perhaps you could get some tips from nova (1) thread there we had the same problems. But so long we have a working twrp with backup possibility.
Hi, i used this Twrp, but did not notice the error mesaje when i "create" a back up for all my data, then when deleting some things, i went off the road and ended deleting the complete operative system, and know i dont seem to be able to find a room for my phone is a huawei p10selfie(in my country) or huawei nova 2 plus (in the rest of the world) model BAC-L03, sry if i dont use the correct words, since english is not my native lenguaje
I was installing this twrp in Nova 2i and it get bricked ...I can only open TWRP which is just usless i can't flash anything from TWRP coz TWRP is not able to mount anything .Bootloader won't start and even my pc can't detect my phone. Any hope ?
iamramanlmc said:
I was installing this twrp in Nova 2i and it get bricked ...I can only open TWRP which is just usless i can't flash anything from TWRP coz TWRP is not able to mount anything .Bootloader won't start and even my pc can't detect my phone. Any hope ?
Click to expand...
Click to collapse
Nova 2i is Mate 10 Lite! https://forum.xda-developers.com/ma...e--roms-kernels-recoveries--other-development
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[RECOVERY][UNOFFICIAL]TWRP Recovery Project 3.5.2 Micromax IN 1 (E6746)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
*/Your warranty is now void.
We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or recoverys, kernels.
You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers./*
Click to expand...
Click to collapse
FLASH GUIDE
1. Unlocked your bootloader
2. Download twrp-3.5.2-e6746.img
3. Run this Following commands
1. adb reboot bootloader
2. fastboot --disable--verification flash vbmeta vbmeta.img
3. fastboot flash recovery twrp-3.5.2-e6746.img
4. fastboot reboot recovery
Click to expand...
Click to collapse
DOWNLOAD
Device Tree
Working
• Decryption
• fastbootd
• MTP & ADB
Bugs
• spam me in support group
• Tell me
Support group
• here
Credits
• TEAM WIN FOR TWRP
• @ZanGhoul in TG
• and @uknowndevice in TG
where is vbmeta.img
I am trying to backup stock recovery using
fastboot boot <recoveryname>.img
says ok but boots to stock recovery not TWRP.
sieger007 said:
where is vbmeta.img
I am trying to backup stock recovery using
fastboot boot <recoveryname>.img
says ok but boots to stock recovery not TWRP.
Click to expand...
Click to collapse
Much better fastboot flash twrp.img, but if you backup stock recovery, just try to pull it via adb
ok I dont have root. How can I backup recovery and other partitons without root
sieger007 said:
ok I dont have root. How can I backup recovery and other partitons without root
Click to expand...
Click to collapse
Try, reboot to recovery mode if, pc read your device adb pull /dev/block/by-name/recovery
mastersenpai05 said:
Try, reboot to recovery mode if, pc read your device adb pull /dev/block/by-name/recovery
Click to expand...
Click to collapse
that is the problem
fastboot boot recovery does not boot to TWRP & I dont have root - I am stuck
if I could temporarily install any custom recovery - problem is solved - Nandroid backup and adb pull. Problem is it keeps going back to stock recovery & i dont want to flash TWRP unless I back up stock recovery. Any thoughts ?
sieger007 said:
if I could temporarily install any custom recovery - problem is solved - Nandroid backup and adb pull. Problem is it keeps going back to stock recovery & i dont want to flash TWRP unless I back up stock recovery. Any thoughts ?
Click to expand...
Click to collapse
Yeah, stock rom issue need to root sir, but I will fix it sir.
sieger007 said:
if I could temporarily install any custom recovery - problem is solved - Nandroid backup and adb pull. Problem is it keeps going back to stock recovery & i dont want to flash TWRP unless I back up stock recovery. Any thoughts ?
Click to expand...
Click to collapse
Not in stock firmware sir? The stoc recovery.img?
mastersenpai05 said:
Not in stock firmware sir? The stoc recovery.img?
Click to expand...
Click to collapse
I meant I tried .... fastboot boot <thisTWRPfile>.img after running vmeta and it will still boot into stock recovery. If I boot in stock recovery - adb shell will not run cos stock recovery does not support it. Problem is there isnt so far stock firmware available , so if I mess up and no backup - I have to run to service center and more $
sieger007 said:
I meant I tried .... fastboot boot <thisTWRPfile>.img after running vmeta and it will still boot into stock recovery. If I boot in stock recovery - adb shell will not run cos stock recovery does not support it. Problem is there isnt so far stock firmware available , so if I mess up and no backup - I have to run to service center and more $
Click to expand...
Click to collapse
MICROMAX IN 1 E6746 http://mtk-p.micromaxinfo.com/product/E6746/Software/India/MMX_E6746_SW_V10.0._HW_V1.0_20210416.zip
mastersenpai05 said:
MICROMAX IN 1 E6746 http://mtk-p.micromaxinfo.com/product/E6746/Software/India/MMX_E6746_SW_V10.0._HW_V1.0_20210416.zip
Click to expand...
Click to collapse
thanks i will check it out. Just wanted to check if this TWRP support USB OTG.Want to transfer Nandroid backup to FLash Drive
sieger007 said:
thanks i will check it out. Just wanted to check if this TWRP support USB OTG.Want to transfer Nandroid backup to FLash Drive
Click to expand...
Click to collapse
Yes sir, I want to know that too. Not yet try but try to check then tell me
TWRP installed fine . OTG works. Now the other 3 letter problem .....OTA.
I got notification that update is available. It wont install via TWRP.
How do I install OTA. wrt THis guide .... this phone does not seem to fit ( this isn't A/B phone type A phone ) . WHat do I do ? restore stock recovery and boot and then restore TWRP and boot.patch.img ? Any clue ?
sieger007 said:
TWRP installed fine . OTG works. Now the other 3 letter problem .....OTA.
I got notification that update is available. It wont install via TWRP.
How do I install OTA. wrt THis guide .... this phone does not seem to fit ( this isn't A/B phone type A phone ) . WHat do I do ? restore stock recovery and boot and then restore TWRP and boot.patch.img ? Any clue ?
Click to expand...
Click to collapse
I don't think so if possible to use twrp in ota update, but you can use twrp for flashing recovery rom ( stock recovery rom)
mastersenpai05 said:
I don't think so if possible to use twrp in ota update, but you can use twrp for flashing recovery rom ( stock recovery rom)
Click to expand...
Click to collapse
I don't know what are the exact criteria for successful OTA update from a vague idea I think it check whether there is original boot and recovery image otherwise says no
in that case would flashing this DM verify no encrypt module remove this checking and after installing this we should be able to to install periodic OTA updates
or as a long-term procedure every time I have to install OTA I have to restore original boot and recovery or should I just restore recovery
as follow up - I could install OTA by restoring stock r'y . There isn't a need to restore boot. You can keep it this way or else if TWRP is restored the same proc ought to repeat before the next OTA.
I am attaching stock boot and recoveries here in case they could be of use.
Boot-recovery--mmx1
sieger007 said:
as follow up - I could install OTA by restoring stock r'y . There isn't a need to restore boot. You can keep it this way or else if TWRP is restored the same proc ought to repeat before the next OTA.
I am attaching stock boot and recoveries here in case they could be of use.
Boot-recovery--mmx1
Click to expand...
Click to collapse
Nice thank you so much! You can also join in micromax in 1 group in telegram
Update : it never worked. I thought it did but that update notice sprung and it wanted to do it all over again. I restored stock recovery. No Luck OTA's keep failing. I then restored stock Boot after removing magisk . Still got veriification error. My BL is unlocked. What does it take to get my OTA zip file working.... do I flash dm verify force encrypt . Why does it refuse. Should BL be locked as well anyone have luck push OTA update after rooting IN 1
Do you have kernel source code

screen not registering inputs after update to LineageOS 19.1

So I performed the upgrade from LineageOS 18.1 to LineageOS 19.1 via the following links: https://wiki.lineageos.org/devices/instantnoodle/fw_update & https://wiki.lineageos.org/devices/instantnoodle/install
All seemed well with no problems, but now when I boot up the device (instantnoodle) It starts up normally but then the screen does not register inputs.
So I can't get past the pin for my SIM or the startup screen you get when first startup LineageOS 19.1
What I have done is go back to recovery and did a Factory reset and format all data.
But this did not make things better..
Does anyone have an idea if there is a work around for this problem?
baseballbatboy26 said:
So I performed the upgrade from LineageOS 18.1 to LineageOS 19.1 via the following links: https://wiki.lineageos.org/devices/instantnoodle/fw_update & https://wiki.lineageos.org/devices/instantnoodle/install
All seemed well with no problems, but now when I boot up the device (instantnoodle) It starts up normally but then the screen does not register inputs.
So I can't get past the pin for my SIM or the startup screen you get when first startup LineageOS 19.1
What I have done is go back to recovery and did a Factory reset and format all data.
But this did not make things better..
Does anyone have an idea if there is a work around for this problem?
Click to expand...
Click to collapse
SOLVED. Used the newest OTA Update
my oneplus 8t screen not respond to touch after installing lineageOS 19 today
meowXda said:
my oneplus 8t screen not respond to touch after installing lineageOS 19 today
Click to expand...
Click to collapse
Which method of flashing did you utilize before installing the ROM, e.g., fastboot, TWRP, OrangeFox, etc?
rodken said:
Which method of flashing did you utilize before installing the ROM, e.g., fastboot, TWRP, OrangeFox, etc?
Click to expand...
Click to collapse
I followed the steps provided by the lineage os official website.
meowXda said:
I followed the steps provided by the lineage os official website.
Click to expand...
Click to collapse
Boot into TWRP instead of LOS Recovery
-- Factory Reset, then Format data / factory reset
-- Reflash ROM
You can always revert to a previous build to test for firmware issues.
rodken said:
Boot into TWRP instead of LOS Recovery
-- Factory Reset, then Format data / factory reset
-- Reflash ROM
You can always revert to a previous build to test for firmware issues.
Click to expand...
Click to collapse
I'm unable to turn off my phone now, because touchscreen doesn't work, only the physical buttons work
rodken said:
Boot into TWRP instead of LOS Recovery
-- Factory Reset, then Format data / factory reset
-- Reflash ROM
You can always revert to a previous build to test for firmware issues.
Click to expand...
Click to collapse
Do you have any instructions article or vlog about this
I wanted to get rid of the oxygen os because there was too many bugs..
meowXda said:
I wanted to get rid of the oxygen os because there was too many bugs..
Click to expand...
Click to collapse
Only the physical buttons work on your device which makes your device a candidate for a complete restore via MSM.
Code:
Boot into TWRP
type: fastboot boot twrp.img
rodken said:
Only the physical buttons work on your device which makes your device a candidate for a complete restore via MSM.
Code:
Boot into TWRP
type: fastboot boot twrp.img
Click to expand...
Click to collapse
Is it a bricked phone right?
meowXda said:
Is it a bricked phone right?
Click to expand...
Click to collapse
What does MSM stands for?
meowXda said:
my oneplus 8t screen not respond to touch after installing lineageOS 19 today
Click to expand...
Click to collapse
I would have to assume that you meant Lineage OS 19.1 for Kebab?
meowXda said:
What does MSM stands for?
Click to expand...
Click to collapse
If you are not familiar with the MSM Tool
-- Refer to this guide.
meowXda said:
Is it a bricked phone right?
Click to expand...
Click to collapse
Your device is not bricked
-- Hard bricked devices will show few or no signs of life. A hard bricked device does not power on or show any vendor logo
-- A "soft bricked" device may show signs of life, but fails to boot or may display an error screen
-- Soft bricked devices can usually be fixed
rodken said:
Your device is not bricked
-- Hard bricked devices will show few or no signs of life. A hard bricked device does not power on or show any vendor logo
-- A "soft bricked" device may show signs of life, but fails to boot or may display an error screen
-- Soft bricked devices can usually be fixed
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rodken said:
Your device is not bricked
-- Hard bricked devices will show few or no signs of life. A hard bricked device does not power on or show any vendor logo
-- A "soft bricked" device may show signs of life, but fails to boot or may display an error screen
-- Soft bricked devices can usually be fixed
Click to expand...
Click to collapse
Can I flash my device with other rom such as PE without going back to oxygen os.
meowXda said:
Can I flash my device with other rom such as PE without going back to oxygen os.
Click to expand...
Click to collapse
If you are thinking about immediately flashing another Custom ROM without rectifying your current issue, you might be in for a rude awakening.
-- Usually, you can flash another Custom ROM by performing a complete factory reset.
-- In your case, start fresh and somewhat new from OOS
-- Remember not to flash a Custom ROM on top of another Custom ROM without clearing the cobwebs.
-- Read, proof-read and read a third time the installation instructions from the developer of each ROM.
OCD Moment: I find myself factory resetting three times between flashing different Custom ROMs
rodken said:
If you are thinking about immediately flashing another Custom ROM without rectifying your current issue, you might be in for a rude awakening.
-- Usually, you can flash another Custom ROM by performing a complete factory reset.
-- In your case, start fresh and somewhat new from OOS
-- Remember not to flash a Custom ROM on top of another Custom ROM without clearing the cobwebs.
-- Read, proof-read and read a third time the installation instructions from the developer of each ROM.
OCD Moment: I find myself factory resetting three times between flashing different Custom ROMs
Click to expand...
Click to collapse
I found that my touchscreen won't work even in the recovery mode(lineage os 19 recovery mode)
rodken said:
If you are thinking about immediately flashing another Custom ROM without rectifying your current issue, you might be in for a rude awakening.
-- Usually, you can flash another Custom ROM by performing a complete factory reset.
-- In your case, start fresh and somewhat new from OOS
-- Remember not to flash a Custom ROM on top of another Custom ROM without clearing the cobwebs.
-- Read, proof-read and read a third time the installation instructions from the developer of each ROM.
OCD Moment: I find myself factory resetting three times between flashing different Custom ROMs
Click to expand...
Click to collapse
I don't if it's the problem with lineageos or my phone itself

Categories

Resources