Develop Bugs

My phone system deleted

Hi guys
Well I guess I ruined my phone , I rooted my honor 7x BND-L21 a couple weeks ago and it worked after I rooted it everything was fine and normal till I was stupid enough and went into the super su app and I saw the full uninstall super su so I was even more stupid to press it and thinking that I’m gonna be free from the root and I won’t have to be afraid that it getting wrecked which I did it with my own hands after I pressed the uninstall super su the phone went black and won’t reboot anymore so I linked the phone to my laptop and went into my internal storage I didn’t find anything but the TWRP file which means there are no more system or systems files what so ever that’s my sad story I hope that any one of you can help me and make a backup to there phone like mine and take the time to help me install it because I don’t know anything about these stuff and I’ll be great full for you guys for the rest of my life
Again My phone is a : honor 7x BND-L21

ayadmanhal said:
Hi guys
Well I guess I ruined my phone , I rooted my honor 7x BND-L21 a couple weeks ago and it worked after I rooted it everything was fine and normal till I was stupid enough and went into the super su app and I saw the full uninstall super su so I was even more stupid to press it and thinking that I’m gonna be free from the root and I won’t have to be afraid that it getting wrecked which I did it with my own hands after I pressed the uninstall super su the phone went black and won’t reboot anymore so I linked the phone to my laptop and went into my internal storage I didn’t find anything but the TWRP file which means there are no more system or systems files what so ever that’s my sad story I hope that any one of you can help me and make a backup to there phone like mine and take the time to help me install it because I don’t know anything about these stuff and I’ll be great full for you guys for the rest of my life
Again My phone is a : honor 7x BND-L21
Click to expand...
Click to collapse
There is , at this time, no suggestion for you to fix.
Because, you do not tell enough of what you were doing, or did.
I mean. First superSU does not work on updated device(Oreo) . So must be nougat, but you did not say.
Next , removeing superSU , from inside of it's settings, will not erase system.
Your description of connecting to PC with USB and not able to see any system files. Well you cannot see Android system files in this way anyhow. Add to that USB (mtp) does not wokif there is no system I place to run the adb/mtp service.
Well if you mean you uninstalled root/superSU , then tried to restart, and that made the black screen, well this is different completely to what you asked. And this makes sense.
If this is what you need. You just need boot.img, if you were in fact on nougat. Or ramdisk.img, and/or kernel.kmg if it was Oreo.
For l21, I do not have these.

mrmazak said:
There is , at this time, no suggestion for you to fix.
Because, you do not tell enough of what you were doing, or did.
I mean. First superSU does not work on updated device(Oreo) . So must be nougat, but you did not say.
Next , removeing superSU , from inside of it's settings, will not erase system.
Your description of connecting to PC with USB and not able to see any system files. Well you cannot see Android system files in this way anyhow. Add to that USB (mtp) does not wokif there is no system I place to run the adb/mtp service.
Well if you mean you uninstalled root/superSU , then tried to restart, and that made the black screen, well this is different completely to what you asked. And this makes sense.
If this is what you need. You just need boot.img, if you were in fact on nougat. Or ramdisk.img, and/or kernel.kmg if it was Oreo.
For l21, I do not have these.
Click to expand...
Click to collapse
bro .
i was playing a game in my phone and the game shot me out and i see the system apps deleted in the menu of apps
i trie restart phone when idid my phone stuck wont open the system but its redirect me to twrp recovery
when the twrp opened i connect my phone with usb to pc
and i see nothing in internal storage only the twrp files !
im find all backup files (IMGs) system.img and cus.img etc..
but idk how to install it
My android version is 7..0 nougat 5.1 emui
and sry for my bad english ..
{
"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"
}

ayadmanhal said:
bro .
i was playing a game in my phone and the game shot me out and i see the system apps deleted in the menu of apps
i trie restart phone when idid my phone stuck wont open the system but its redirect me to twrp recovery
when the twrp opened i connect my phone with usb to pc
and i see nothing in internal storage only the twrp files !
im find all backup files (IMGs) system.img and cus.img etc..
but idk how to install it
My android version is 7..0 nougat 5.1 emui
and sry for my bad english ..
Click to expand...
Click to collapse
If you have all the needed files, just do this:
1. Boot into TWRP
2. Flash vendor.img, recovery_ramdis.img (Or something similar to that), and system.img
3. Flash them ^^^^ to the required partitions (Partition names to flash to should be self explanatory)
4. Do a factory reset
5. Reboot
Report back please if this works!

I have the exact same problem as OP. When I go into TWRP and mount an img or zip, there is always an error message saying
"Unable to find partition for path '/system' ". /system also doesn't show up anywhere else. . .
I tried your suggestion too but to no avail.
I don't know what to do anymore.
Edit: Now I can’t even get into TWRP after trying these 5 steps. All it shows me is the bootloader screen but with error messages.
“Please update the system again”
And at the bottom of the screen something about the boot.img

dutyyaknow said:
I have the exact same problem as OP. When I go into TWRP and mount an img or zip, there is always an error message saying
"Unable to find partition for path '/system' ". /system also doesn't show up anywhere else. . .
I tried your suggestion too but to no avail.
I don't know what to do anymore.
Edit: Now I can’t even get into TWRP after trying these 5 steps. All it shows me is the bootloader screen but with error messages.
“Please update the system again”
And at the bottom of the screen something about the boot.img
Click to expand...
Click to collapse
If you're talking about my suggestion, then please quote me next time.
Also, are you sure you have the right twrp installed?
When in bootloader mode, connect your device to adb. Does you device get recognized when you type "fastboot devices" ???

crayonicle said:
If you're talking about my suggestion, then please quote me next time.
Also, are you sure you have the right twrp installed?
When in bootloader mode, connect your device to adb. Does you device get recognized when you type "fastboot devices" ???
Click to expand...
Click to collapse
Thank you for helping out.
Yes, I tried your suggestion and I used version 3.1.1.0 of TWRP.
Unfortunately it looks like my device is not getting recognized in adb anymore. All I get is either the screen where it says "booting your device now" forever or the white ERROR MODE screen with "Attention! Please update system again.
There are two error messages at the bottom of the screen :
Func NO : 10 (boot image)
Error NO : 2 (load failed)
Now, how do I save myself out of this? It looks like I can't do anything. . .
Edit: correction, it does get recognized in adb in fastboot mode. Can I just flash your suggested TWRP from there?
Edit2: tried to flash the complete_twrp_ramdisk.img in fastboot mode with fastboot flash recovery command. Then I rebooted but instead of TWRP it still shows ERROR MODE

crayonicle said:
If you have all the needed files, just do this:
1. Boot into TWRP
2. Flash vendor.img, recovery_ramdis.img (Or something similar to that), and system.img
3. Flash them ^^^^ to the required partitions (Partition names to flash to should be self explanatory)
4. Do a factory reset
5. Reboot
Report back please if this works!
Click to expand...
Click to collapse
i did everything but nothing changed
ihave installed all IMGs
nothing happened and my phone still empty !
i trying to flash [OpenKirin's RROS ] room
it says succes but when im reboot still rebooting into recovery mode {twrp} 3.1.1.0
and my storage still empty
idk what i have to do
im think we have nothing to do !?

dutyyaknow said:
I have the exact same problem as OP. When I go into TWRP and mount an img or zip, there is always an error message saying
"Unable to find partition for path '/system' ". /system also doesn't show up anywhere else. . .
I tried your suggestion too but to no avail.
I don't know what to do anymore.
Edit: Now I can’t even get into TWRP after trying these 5 steps. All it shows me is the bootloader screen but with error messages.
“Please update the system again”
And at the bottom of the screen something about the boot.img
Click to expand...
Click to collapse
i think we loose our devices <\3

crayonicle said:
If you're talking about my suggestion, then please quote me next time.
Also, are you sure you have the right twrp installed?
When in bootloader mode, connect your device to adb. Does you device get recognized when you type "fastboot devices" ???
Click to expand...
Click to collapse
ayadmanhal said:
i think we loose our devices <\3
Click to expand...
Click to collapse
There has to be a way to fix it from fastboot mode.
If everything fails, we can still try to send it to a Huawei Center to get fixed. Just don't tell them that you rooted or unlocked your device. I heard that they will then switch out the motherboard for a new one.

dutyyaknow said:
There has to be a way to fix it from fastboot mode.
If everything fails, we can still try to send it to a Huawei Center to get fixed. Just don't tell them that you rooted or unlocked your device. I heard that they will then switch out the motherboard for a new one.
Click to expand...
Click to collapse
we cant go to huawei center bcz the phone unlocked and rooted
so the phone has no Guarantee and they will see the boot when says the device is not trusted <\3

After reflashing my old TWRP from fastboot, I can now access TWRP again and /system partition is showing up too. The ERROR MODE screen still shows up when I boot the phone with VOL + and POWER but when I press VOL + - and POWER I load into TWRP

dutyyaknow said:
After reflashing my old TWRP from fastboot, I can now access TWRP again and /system partition is showing up too. The ERROR MODE screen still shows up when I boot the phone with VOL + and POWER but when I press VOL + - and POWER I load into TWRP
Click to expand...
Click to collapse
my device only auto booting for twrp nothing more

up

no help :\

ayadmanhal said:
no help :\
Click to expand...
Click to collapse
Do you have ADB support on TWRP mode?
If so just use dd command to flash stock boot.img.
Try it by fastboot if you can.
You need to flash stock boot.img because rooting patches boot image and you tried to unroot but were unable to reboot that would replace the patched boot with the stock one.
If i undetstood the issue correctly...
If not, please enlight me...
Enviado do meu Le 2 através do Tapatalk

RSGI said:
Do you have ADB support on TWRP mode?
If so just use dd command to flash stock boot.img.
Try it by fastboot if you can.
You need to flash stock boot.img because rooting patches boot image and you tried to unroot but were unable to reboot that would replace the patched boot with the stock one.
If i undetstood the issue correctly...
If not, please enlight me...
Enviado do meu Le 2 através do Tapatalk
Click to expand...
Click to collapse
i trie much of boot.img files but no change
i tried everything but the phone still wont read the system files

dutyyaknow said:
Thank you for helping out.
Yes, I tried your suggestion and I used version 3.1.1.0 of TWRP.
Unfortunately it looks like my device is not getting recognized in adb anymore. All I get is either the screen where it says "booting your device now" forever or the white ERROR MODE screen with "Attention! Please update system again.
There are two error messages at the bottom of the screen :
Func NO : 10 (boot image)
Error NO : 2 (load failed)
Now, how do I save myself out of this? It looks like I can't do anything. . .
Edit: correction, it does get recognized in adb in fastboot mode. Can I just flash your suggested TWRP from there?
Edit2: tried to flash the complete_twrp_ramdisk.img in fastboot mode with fastboot flash recovery command. Then I rebooted but instead of TWRP it still shows ERROR MODE
Click to expand...
Click to collapse
Have you re-flash with Huawei Multi Tool, but first you must have file update.zip and extract update.app from http://pro-teammt.ru/firmware-database/?firmware_model=BND&firmware_page=0
---------- Post added at 06:48 AM ---------- Previous post was at 06:41 AM ----------
ayadmanhal said:
i trie much of boot.img files but no change
i tried everything but the phone still wont read the system files
Click to expand...
Click to collapse
you on Nougat? have try to upgrade to Oreo from this thread,
https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
there's maybe can fix your system file

[TWRP] TWRP/No-Verity Kernel for Moto E5 (Nora)(XT1944-2/-4)

Hi guys, today I'm going to explain you, how to use TWRP and also how to disable forced encryption
Very Important!!!!
Works for all ROMs included stock ROM
Take a backup of boot partition with TWRP in case of something goes wrong
Pre-requisites
1.- Unlocked Bootloader
2.- PC, drivers installed and plattform tools folder: https://www.dropbox.com/s/c3c8rev5e40gy5b/platform-tools-latest-windows.zip?dl=0
3.- TWRP for Moto E5 Play by @CodyF86 : https://androidfilehost.com/?fid=3700668719832239867
4. No verity kernel by @MotoJunkie01 (Only for XT1944-2 or XT1944-4!!!!) : https://drive.google.com/file/d/1NcyuFRgvvRiS5MT5Jxl3uS3XHCnULBMc/view
5. fstab.qcom by CodyF86 also: https://androidfilehost.com/?fid=674106145207491856
Procedure
1.- While you have downloaded all necessary files, go to platform tools folder, and put there TWRP image
2.- Reboot your phone onto fastboot/bootloader, then open cmd and boot into TWRP with this code: fastboot boot twrp_james.img (don't try to flash it because it won't work, and you will need to do that in order to use TWRP, all the time!!!)
3.- While you are in TWRP, go to bakcup and select everything, put the backup into SD Card to prevent some accidents. (The time that it will take depends on how much things you have on your phone)
4.- When backup it's done reboot to bootloader and flash the no-verity kernel
5.- Reboot system
6.- Then use some root explorer, this one is free and very useful https://forum.xda-developers.com/showthread.php?t=1523691
7.- Copy downloaded fstab.qcom and go to vendor/etc, the replace the file with the new one and reboot
8.- Boot again into TWRP, and swipe for factory reset, then format data (Remember that you'll lost your data
9.- Reboot the device, and wait.
This method is easier than the other and works fine, if you go to settings/security you'll see that device is encrypted but if you open that option, you'll notice that encryption is gone.*
Thanks to @MotoJunkie01 for the kernel
Thanks to @CodyF86 for TWRP and fstab.qcom

Nice guide @Fersho. Clear, informative, comprehensive and easy to follow.

MotoJunkie01 said:
Nice guide @Fersho. Clear, informative, comprehensive and easy to follow.
Click to expand...
Click to collapse
Thanks to you for helping with the kernel, I'm very thankful with you

Fersho said:
Thanks to you for helping with the kernel, I'm very thankful with you
Click to expand...
Click to collapse
No problem. I'm glad you posted a guide with the kernel and supporting files to help others. That's what it's all about.

MotoJunkie01 said:
No problem. I'm glad you posted a guide with the kernel and supporting files to help others. That's what it's all about.
Click to expand...
Click to collapse
Then now I'm going to share how to install RR and Pie GSI and also the way to fix lag on both Oreo/Pie

where can we get the verity kernel for moto e5 1944-3

Will the no verity kernel work for XT1944-5?

Mahendra11 said:
Will the no verity kernel work for XT1944-5?
Click to expand...
Click to collapse
Maybe, try by your own risk, make a backup of boot partition because is the one that you'll need in case of something goes wrong

Thread updated, I've noticed that the previous method didn't work at all, and also I discovered that stock rom works fine without encryption, then if stock is decrypted, other roms won't be encrypted anymore

No verity kernel link is down pls re-upload it bro

Fersho said:
Thread updated, I've noticed that the previous method didn't work at all, and also I discovered that stock rom works fine without encryption, then if stock is decrypted, other roms won't be encrypted anymore
Click to expand...
Click to collapse
Re upload please

borksek said:
Re upload please
Click to expand...
Click to collapse
Sorry but I only have stock for XT1944-4 the other stock roms are lost, if somebody had downloaded the others then he could upload them

Fersho said:
Sorry but I only have stock for XT1944-4 the other stock roms are lost, if somebody had downloaded the others then he could upload them
Click to expand...
Click to collapse
Please I have the XT1944-4 could send me the file no Verity Kernel

Do you have a non-verity kernel for XT1944-3? please (single sim variant)

no-verity undownloadable
Fersho said:
Hi guys, today I'm going to explain you, how to use TWRP and also how to disable forced encryption
Very Important!!!!
Works for all ROMs included stock ROM
Take a backup of boot partition with TWRP in case of something goes wrong
Pre-requisites
1.- Unlocked Bootloader
2.- PC, drivers installed and plattform tools folder: https://www.dropbox.com/s/c3c8rev5e40gy5b/platform-tools-latest-windows.zip?dl=0
3.- TWRP for Moto E5 Play by @CodyF86 : https://androidfilehost.com/?fid=3700668719832239867
4. No verity kernel by @MotoJunkie01 (Only for XT1944-2 or XT1944-4!!!!) : https://drive.google.com/file/d/1NcyuFRgvvRiS5MT5Jxl3uS3XHCnULBMc/view
5. fstab.qcom by CodyF86 also: https://androidfilehost.com/?fid=674106145207491856
Procedure
1.- While you have downloaded all necessary files, go to platform tools folder, and put there TWRP image
2.- Reboot your phone onto fastboot/bootloader, then open cmd and boot into TWRP with this code: fastboot boot twrp_james.img (don't try to flash it because it won't work, and you will need to do that in order to use TWRP, all the time!!!)
3.- While you are in TWRP, go to bakcup and select everything, put the backup into SD Card to prevent some accidents. (The time that it will take depends on how much things you have on your phone)
4.- When backup it's done reboot to bootloader and flash the no-verity kernel
5.- Reboot system
6.- Then use some root explorer, this one is free and very useful https://forum.xda-developers.com/showthread.php?t=1523691
7.- Copy downloaded fstab.qcom and go to vendor/etc, the replace the file with the new one and reboot
8.- Boot again into TWRP, and swipe for factory reset, then format data (Remember that you'll lost your data
9.- Reboot the device, and wait.
This method is easier than the other and works fine, if you go to settings/security you'll see that device is encrypted but if you open that option, you'll notice that encryption is gone.*
Thanks to @MotoJunkie01 for the kernel
Thanks to @CodyF86 for TWRP and fstab.qcom
Click to expand...
Click to collapse
hello first congratulations for this tutorial and your work, but there is a small problem with the famous no-verity ^^ it is impossible to download would it be possible to have new links? thank you in advance!!

Hi there. I tried a thousand times now ... no succeed. Everytime I try to boot to twrp_james.img the screen is not accessable anymore. No interaction possible.
Switching device off -> switching device on .... even the "swipe to unlock" doesn't work. I use Motorola Moto E5 Nora XT1944-2.
Any ideas?!

honk0504 said:
Hi there. I tried a thousand times now ... no succeed. Everytime I try to boot to twrp_james.img the screen is not accessable anymore. No interaction possible.
Switching device off -> switching device on .... even the "swipe to unlock" doesn't work. I use Motorola Moto E5 Nora XT1944-2.
Any ideas?!
Click to expand...
Click to collapse
I have the same problem, I tried everything.
I'm unable to use TWRP (james).
after "fastboot boot twrp_james.img"
TWRP comes up with the Mount/dycrypt your data screen, a mouse pointer is visible in the middle. No user interaction is possible twrp doesn't seem to respond to touch screen user input.
Also the "No verity kernel by @MotoJunkie01 (Only for XT1944-2 or XT1944-4!!!!) : https://drive.google.com/file/d/1Ncy...XHCnULBMc/view" link is dead. Can someone reupload this files.
Does anybody have a fix for this problem? I'm using the Moto E5 XT1944-2.

honk0504 said:
Hi there. I tried a thousand times now ... no succeed. Everytime I try to boot to twrp_james.img the screen is not accessable anymore. No interaction possible.
Switching device off -> switching device on .... even the "swipe to unlock" doesn't work. I use Motorola Moto E5 Nora XT1944-2.
Any ideas?!
Click to expand...
Click to collapse
I found a solution to use twrp on the Moto E5 Nora XT1944-2:
Use a micro usb to usb adapter (OTG adapter) and connect a mouse to you phone, now you can use twrp using the mouse.
{
"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"
}

Here is my no-verity kernel for xt1944-3 succesfully working
please OP add this to the thread!
https://www.mediafire.com/file/u52pxc21arlktn4/patched_boot.img/file

Can I install the No-Verity-opt-Encrypt zip instead of installing the kernel?

[GUIDE/TIP]Failed fastboot flashing of stock ROM

I was on stock ROM (12.0.8.0 QJSEUXM) and noticed that v12.0.9.0 is out for some time already, but not offered by system to be installed. In the past with my previous phones when I wanted to "force" the update, I simply downloaded fastboot ROM, flashed it and re-rooted the phone. In a matter of few minutes I had up-to-date and working phone again. Today I tried the same with Mi 10T lite and it failed miserably.
Observed issues:
1. flashing script (flash_all_except_storage.bat) comes with CRCLIST and SPARECRCLIST commands which are either not understood by phone (fastbootd), or fail verification (fastboot)
2. after modification of script and removal of beforementioned lines, flashing completes, however phone stays in bootloop showing just Mi logo
3. using different PC, USB port, USB cable, fastboot version, fastbootd/fastboot mode, driver version, Mi flash,.. result always in the same non-functional phone
4. after booting to TWRP (fastboot boot twrp.img), internal data gets decrypted correctly, but TWRP reports issue mounting /odm
5. flashing different ROM version results in the very same issue
Fix:
1. Flash stock ROM (in my case 12.0.8.0)
2. If you receive an CRC error, remove 2 lines from flashing script containing words CRCLIST and SPARECRCLIST and re-run it again
3. Download recovery ROM (12.0.9.0) and put it to internal SD (you can do it in advance or through TWRP when the phone is already "soft-bricked")
4. Flash recovery ROM from TWRP & reboot to functional system
I noticed that fastboot ROM uses super.img, which for some reason isn't flashed properly. Recovery ROM flashes /system, /vendor and /odm partitions directly, which overcomes this limitation. If anyone knows why it happens and especially how to use fastboot ROM directly with no extra steps, please share it.

_mysiak_ said:
I was on stock ROM (12.0.8.0 QJSEUXM) and noticed that v12.0.9.0 is out for some time already, but not offered by system to be installed. In the past with my previous phones when I wanted to "force" the update, I simply downloaded fastboot ROM, flashed it and re-rooted the phone. In a matter of few minutes I had up-to-date and working phone again. Today I tried the same with Mi 10T lite and it failed miserably.
Observed issues:
1. flashing script (flash_all_except_storage.bat) comes with CRCLIST and SPARECRCLIST commands which are either not understood by phone (fastbootd), or fail verification (fastboot)
2. after modification of script and removal of beforementioned lines, flashing completes, however phone stays in bootloop showing just Mi logo
3. using different PC, USB port, USB cable, fastboot version, fastbootd/fastboot mode, driver version, Mi flash,.. result always in the same non-functional phone
4. after booting to TWRP (fastboot boot twrp.img), internal data gets decrypted correctly, but TWRP reports issue mounting /odm
5. flashing different ROM version results in the very same issue
Fix:
1. Flash stock ROM (in my case 12.0.8.0)
2. Download recovery ROM (12.0.9.0) and put it to internal SD (you can do it in advance or through TWRP when the phone is already "soft-bricked")
3. Flash recovery ROM from TWRP & reboot to functional system
I noticed that fastboot ROM uses super.img, which for some reason isn't flashed properly. Recovery ROM flashes /system, /vendor and /odm partitions directly, which overcomes this limitation. If anyone knows why it happens and especially how to use fastboot ROM directly with no extra steps, please share it.
Click to expand...
Click to collapse
I tried to flash firmware rom with mi flash tool, but there error too, maybe i am errorman
i will try one more time, keep your fingers to me

NeverMind._. said:
I tried to flash firmware rom with mi flash tool, but there error too, maybe i am errorman
Click to expand...
Click to collapse
What error? You might need to modify your flashing script and remove lines mentioning CRCLIST and SPARECRCLIST.

_mysiak_ said:
What error? You might need to modify your flashing script and remove lines mentioning CRCLIST and SPARECRCLIST.
Click to expand...
Click to collapse
I will do it on my notebook, if it will show error i will show you it, btw thx for helping me

wtf, i flashd with mi flash tool, after 6 minutes, it shows error, phone is showing redmi lol
btw it works, but now i have redmi 10t lite
{
"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"
}

try this program QPST_2.7.496

i need help. After a failed attempt of flash. My phone stuck on fast boot screen not found in MI flash too. i installed adb again still not appear in mi flash tool. I can enter recovery mode but still not appear in mi flash tool. I only have stock recovery

kammgl said:
i need help. After a failed attempt of flash. My phone stuck on fast boot screen not found in MI flash too. i installed adb again still not appear in mi flash tool. I can enter recovery mode but still not appear in mi flash tool. I only have stock recovery
Click to expand...
Click to collapse
For flashing you need to be in fastboot mode. If your phone is not detected correctly, most probably you have incorrect drivers installed (ADB instead of fastboot). Check from command line "fastboot devices" - you should see your phone connected. If it's missing, check your drivers in Windows device manager.

Can you attach picture , of how many lines did you remove? I have 4 lines with spare and crc

tze_vitamin said:
Can you attach picture , of how many lines did you remove? I have 4 lines with spare and crc
Click to expand...
Click to collapse
Might be easier for you to show the lines.. I removed only 2 lines, but maybe there are more with more recent ROMs.

_mysiak_ said:
Might be easier for you to show the lines.. I removed only 2 lines, but maybe there are more with more recent ROMs.
Click to expand...
Click to collapse
I remove 4 lines but still have the same issue. I reopen MI flash tools, upload ROM again,and still showing the same error, I will upload pics later

I was using my phone normally, I left it charging and when I looked at it again, it would restart non-stop. It's a Xiaomi Mi 10T Lite, I held the power button, but it didn't turn on, it just came back to the bootloader screen, I didn't try to format it as I was trying to recover my files.
So I thought about unlocking the bootloader to get access to my files, I used Mi Unlock Tool, but it doesn't work. I still have access to my account phone number and email address. But I couldn't unlock by this method.
Please I need your help. Thank you

Question Xiaomi K40 Became A Brick

Hi peeps, my Xiaomi K40 now became a brick because it can't be installed any ROM, I've tried using TWRP and also mi flash tool but nothing helps.
When using TWRP I've tried two methods:
1/ adb sideload
2/ Install from a zip file which is pushed to device using adb push command(because now the device doesn't have any OS)
But in both cases it shown:
Failed to mount '/system_root' (Block device required)
Failed to mount '/system_ext' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
Click to expand...
Click to collapse
I've also tried to wipe all data using Advance Wipe option to repair the partition but no hope.
Any one has solution for this case? thanks in advance!

Flash your device in EDL mode.
Please refer to the post below on how to bypass edl mode authentication.
[GUIDE] How to bypass authentication and flash in EDL with NO auth for FREE!​
Thanks to VD171 for his post.

I think your device is having a Snapdragon Chipset. Sorry but you may try to search on google for contact to person who has authorised edl account to flash a Snapdragon based phone.

Learn more about it in this video

reborn2020 said:
Hi peeps, my Xiaomi K40 now became a brick because it can't be installed any ROM, I've tried using TWRP and also mi flash tool but nothing helps.
When using TWRP I've tried two methods:
1/ adb sideload
2/ Install from a zip file which is pushed to device using adb push command(because now the device doesn't have any OS)
But in both cases it shown:
I've also tried to wipe all data using Advance Wipe option to repair the partition but no hope.
Any one has solution for this case? thanks in advance!
Click to expand...
Click to collapse
do you still have your fastboot mode on your phone?

mvikrant97 said:
Learn more about it in this video
Click to expand...
Click to collapse
Mi flash didn't recognized my phone.
khazzey said:
do you still have your fastboot mode on your phone?
Click to expand...
Click to collapse
Yes I do.

no bypass for STUCKDRAGON devices for EDL Mode so sad the phone became literally bricked

reborn2020 said:
Mi flash didn't recognized my phone.
Yes I do.
Click to expand...
Click to collapse
listen to me, first if you are on windows 10 you should disable driver signature enforcement on your pc search it on google after disabling you should restart your pc, next step is to install xiaomi flash tool latest (02262021) version after installing the software open it, at the right upper of the software you will see drivers click it and click install after installing, reboot your phone into fastboot mode using volume down and power button, connect your phone to pc and click refresh on xiaomi flash tool if you're phone is detected please come back here let me know

khazzey said:
listen to me, first if you are on windows 10 you should disable driver signature enforcement on your pc search it on google after disabling you should restart your pc, next step is to install xiaomi flash tool latest (02262021) version after installing the software open it, at the right upper of the software you will see drivers click it and click install after installing, reboot your phone into fastboot mode using volume down and power button, connect your phone to pc and click refresh on xiaomi flash tool if you're phone is detected please come back here let me know
Click to expand...
Click to collapse
I did this before but no hope, I don't know if the problem is I'm using a macbook and run windows 10 via bootcamp, I don't have an actual windows computer.
P.S, I upload the latest status.
{
"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"
}

last week I was in a similar situation like yours just twrp and all partition screwed up.
well what saved me was to put dot os 5.2 on a USB c pen drive and then simply installing it from trwp (choosing USB pen as source) after literally 5-10 minutes phones came back to life.
let me know if it works for you.
also if twrp throws any error during installation just ignore them for me after flash completed phone booted just fine

ale82to said:
last week I was in a similar situation like yours just twrp and all partition screwed up.
well what saved me was to put dot os 5.2 on a USB c pen drive and then simply installing it from trwp (choosing USB pen as source) after literally 5-10 minutes phones came back to life.
let me know if it works for you.
also if twrp throws any error during installation just ignore them for me after flash completed phone booted just fine
Click to expand...
Click to collapse
I put a miui rom in a usb type c then connect into my phone, then boot into TWRP, and in Install option, I didn't see any option likes "USB pen"

reborn2020 said:
I put a miui rom in a usb type c then connect into my phone, then boot into TWRP, and in Install option, I didn't see any option likes "USB pen"
Click to expand...
Click to collapse
I said USB pen to make sure you choose it from TWRP install I think the righ name is external storage or something similar anyway it seems you are doing things the right way I am quite sure u ll bring phone back to life.
I think muiu room is just fine, should it fails try crDroid or dot os (do not try arrow or lineage)

Bruh I have a very simple solution I guess it might help you
Well first update to latest official twrp custom recovey for your device then
Navigate to Wipe
advance Wipe
Select data and choose Repair or Change File System
Press Repair File System to see if this fixes the issue. If not, continue.
Press Change File System, choose Ext2, and swipe to confirm.
now switch back to Ext4 and swipe to confirm.
i hope this might help you BTW then flash your first custom rom using a sd card or usb if succeeded then flash every stuff as usual

Anurag3100 said:
Bruh I have a very simple solution I guess it might help you
Well first update to latest official twrp custom recovey for your device then
Navigate to Wipe
advance Wipe
Select data and choose Repair or Change File System
Press Repair File System to see if this fixes the issue. If not, continue.
Press Change File System, choose Ext2, and swipe to confirm.
now switch back to Ext4 and swipe to confirm.
i hope this might help you BTW then flash your first custom rom using a sd card or usb if succeeded then flash every stuff as usual
Click to expand...
Click to collapse
Thanks, I've tried this before, unfortunately still can't solve my problem. Finally I decided to bring my phone to a technician.

Try fastboot erase userdata in cmd after taking your device to fastboot mode
Kinda check different twrp I think your twrp is having any problems plz flash your twrp once again
I hope this will surely work for you my friend.

reborn2020 said:
Thanks, I've tried this before, unfortunately still can't solve my problem. Finally I decided to bring my phone to a ttechnic
Click to expand...
Click to collapse
Bro try different formats then change to Ext4 well try this twrp https://dl.twrp.me/alioth/twrp-3.6.0_11-0-alioth.img.html umm i hope this will help you out completely.

if you still have your fastboot mode (turn off then hold power + vol. down), you should check your pc driver if adb and fastboot driver installed properly, then try flashing stock rom (dont relock your bootloader), I think what cause the brick is encrypted storage that get accessed by twrp, even if you decrypt it using password, you can still brick the phone by manually mount some partition in twrp

Thank you all of your help, peeps. Finally I solved my problem by the help of a technician. Because only technician has access to Xiaomi internal tools, these are "Hardware-Level" which could help in these cases.

He
reborn2020 said:
Thank you all of your help, peeps. Finally I solved my problem by the help of a technician. Because only technician has access to Xiaomi internal tools, these are "Hardware-Level" which could help in these cases.
Click to expand...
Click to collapse
Hello, glad you solved your issue, but can you please explain briefly how hardware was bricked since you were already able to reach fastboot & twrp? Since it's known that when you can boot to fastboot, it's a softbrick

Alipk52 said:
He
Hello, glad you solved your issue, but can you please explain briefly how hardware was bricked since you were already able to reach fastboot & twrp? Since it's known that when you can boot to fastboot, it's a softbrick
Click to expand...
Click to collapse
I can boot to fastboot but I can't do anything with fastboot becuase I wiped out anything on my phone include "firmware" maybe, I don't know, sorry but this's not my major so I can't explain.

Question HELP - Realmeflash.exe "cannot find central directory"

Hello everyone !
I am French and my English is very bad so I will use Google translation to communicate with you!
This is what is happening.
Without doing it on purpose, I flashed the original boot with the unofficial TWRP one!
Since then, I can no longer use my phone and I no longer enter the RUI3 interface.
I used Realmeflash.exe to reinstall the firmware and it gives me an error message "cannot find central directory".
{
"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"
}
Do you know how to solve this problem?
Thank you for your help !

I had the same problem you gotta get the MCT OFP extractor tool and QFIL, you extract everything with the MCT tool and then use QFIL to flash but the super.img is broken up into multiple files which I Have no clue how to merge so I'm stuck for now but if I get it working I'll be sure to tell you

kamubendi said:
I had the same problem you gotta get the MCT OFP extractor tool and QFIL, you extract everything with the MCT tool and then use QFIL to flash but the super.img is broken up into multiple files which I Have no clue how to merge so I'm stuck for now but if I get it working I'll be sure to tell you
Click to expand...
Click to collapse
Thank you very much friend

@kamubendi
I posted the problem on this page too !
https://c.realme.com/in/post-details/1525231625514856448
If it can help for the future

I share the extraction of the firmware : RMX3363GDPR_12_C.06_2022042721590000
https://drive.google.com/drive/folders/1QpeyOBuavwC3gq25jfKnNaXqmVBMAwt-?usp=sharing

use this flash tool. put the ofp file in same folder run exe & select region start flash https://github.com/italorecife/OppoRealme-OFP-Flash

urstrulynaveen said:
use this flash tool. put the ofp file in same folder run exe & select region start flash https://github.com/italorecife/OppoRealme-OFP-Flash
Click to expand...
Click to collapse
I already tried !
According to Google the .exe is infected with a virus, but I used it anyway, because I know it can be a false positive.
During use, the flash does a lot of "Success" but also "Failed", because of data protection on certain files!
Arrived at "service.img", the flash stops and nothing advances!

I recently unbricked my GT ME using this flash tool only. Realme flash tool doesn't support AB partition & dynamic partition table. It is the only working tool to flash through fastboot. After flashing completion change slot
fastboot getvar current-slot
fastboot --set-active=a or b
fastboot reboot

urstrulynaveen said:
I recently unbricked my GT ME using this flash tool only. Realme flash tool doesn't support AB partition & dynamic partition table. It is the only working tool to flash through fastboot. After flashing completion change slot
fastboot getvar current-slot
fastboot --set-active=a or b
fastboot reboot
Click to expand...
Click to collapse
I choose slot A to do the flashing and then I have to activate slot B ?

Yup after flashing success

urstrulynaveen said:
Yup after flashing success
Click to expand...
Click to collapse
Hi, I got my phone back from this scam repairman!
He damaged my phone even more than I left him!
Could you send me a screenshot of your c:\adb\dir please!
I no longer have recovery mode and the repairman told me a lot of things that I supposedly did during the flashing to get rid of his bull****!!
Thank you.

@urstrulynaveen Otherwise I tried what you told me and I got this!

ToutanVrac said:
@urstrulynaveen Otherwise I tried what you told me and I got this!
View attachment 5618219
Click to expand...
Click to collapse
Ur already in slot a change it to b. Firmware may flashed in slot b

urstrulynaveen said:
Ur already in slot a change it to b. Firmware may flashed in slot b
Click to expand...
Click to collapse
I already did, I have this command line that appears instead !
When I launch the program for slot A, it's very random when it blocks !
On the image, it's xb1_config_a which bug !
And when I close the window, it gives me success before it disappears !
In general, I have 50% success and 50% failed !
The furthest file that gave me the bug is the "super" file !
Apparently it is cut into 5 parts with the OFP extractor.

ToutanVrac said:
I already did, I have this command line that appears instead !
View attachment 5618873
When I launch the program for slot A, it's very random when it blocks !
On the image, it's xb1_config_a which bug !
And when I close the window, it gives me success before it disappears !
View attachment 5618879
In general, I have 50% success and 50% failed !
The furthest file that gave me the bug is the "super" file !
Apparently it is cut into 5 parts with the OFP extractor.
Click to expand...
Click to collapse
Every partition flashes in both slots except super partition. Super partition only flashes in inactive slot, that's why u need to change the slot. Super partition flashing takes around 25 to 30 minutes you need to be patient. & After flashing check slot and change it

urstrulynaveen
Thank you very much for helping me, it motivates me not to give up !
Did you receive a lot of failed during flashing ?

@urstrulynaveen
Problem solved...everything works! !
I'm in the interface and everything seems fine at the moment.
The flashing problem was what you said for the "super" file, but the main problem was above all the fact that I wasn't using a USB port on the motherboard !
Were you able to root the phone ?

ToutanVrac said:
@urstrulynaveen
Problem solved...everything works! !
I'm in the interface and everything seems fine at the moment.
The flashing problem was what you said for the "super" file, but the main problem was above all the fact that I wasn't using a USB port on the motherboard !
Were you able to root the phone ?
Click to expand...
Click to collapse
Can you explain to me how to do it with pictures and writing and I will be very thankful to you

nighetspy said:
Can you explain to me how to do it with pictures and writing and I will be very thankful to you
Click to expand...
Click to collapse
It's very easy !
1. You download the latest firmware
2. You put your phone in fastboot mode
3. You connect your phone with the original cable to an available port on your motherboard
4. You open the "OppoRealme-OFP-Flash_1.0.exe"
5. You choose the "most logical" options
The files will install one by one and you may get a lot of errors!
Leave it, the program will continue and at some point there will be a "super" file which will take a long time to install (30 minutes), you wait and then you will see your phone restart as if it were brand new !

ToutanVrac said:
It's very easy !
1. You download the latest firmware
2. You put your phone in fastboot mode
3. You connect your phone with the original cable to an available port on your motherboard
4. You open the "OppoRealme-OFP-Flash_1.0.exe"
5. You choose the "most logical" options
The files will install one by one and you may get a lot of errors!
Leave it, the program will continue and at some point there will be a "super" file which will take a long time to install (30 minutes), you wait and then you will see your phone restart as if it were brand new !
Click to expand...
Click to collapse
Finally, after two weeks of trouble, the problem was solved, thank you very much