Question HELP - Realmeflash.exe "cannot find central directory" - Realme GT Master Edition

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

Related

Help! Sensors turned off!

Hello everyone. I was with Android 7 on my ZS570KL and returned to 6 for a tutorial found on the internet and worked, but all the sensors of the device were disabled (screen rotation, gyroscope, approximation, fingerprint [only registers up to 93% and gives error], and all the others). How do I reactivate? I came back to Android 7, formatted the device several times, and nothing solves!
What tutorial and why?
No information = no 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"
}
I do not remember where I found the tutorial and the files, but the process is this:
1. Download http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZS570KL/UL-Z016-WW-4.12.40.1698-user.zip
2. Download https://mega.nz/#!tp9DSQ4b!3wdDLsh3BBtPju8G74xlDjLJ9QywFaoLs1T11mMt3QQ
3. Unzip FlashTools64_20161125.zip
4. Unzip UL-Z016-WW-4.12.40.1698-user.zip and move out files under firmware-update to FlashTools folder
5. Put downgrade.bat, boot.img, recovery.img to FlashTools folder
6. Reboot phone to bootloader and click downgrade.bat
The reason was to swap the conventional root SU through the Magisk. I tried to reinstall 7 just by replacing the original recovery available here in XDA, but the process was not going to restart, so I followed that one to try to return and reinstall everything. It worked, I got back to 6, but I did not know everything. It looks like a computer without the drivers installed.
I'd downgrade again, if it was me, this time I'd install a stock Rom (MM) from ASUS. Then test everything again. If everything is good to go then I'd root and upgrade.
Changing the OS in the middle doesn't help if you have a problem.
Especially if it just builds upon the foundations of the previous OS...
Did you flash a complete N rom or do an update?
The ROMs I try are exactly those of the Asus site. I tried the downgrade again to version 4.12.40.1698 and realized something when I flash in recovery mode. The following error messages appear:
Unmount of /firmware failed: no such volume
Mount: failed to mount /dev/block/bootdevice/by-name/mdtp at /firmware: No such file or directory
Unmount of /firmware failed, no such volume
What is it? How to solve?
I need the original kernel and recovery of the latest firmware released, can anyone make it available?
AndreSantoro84 said:
I need the original kernel and recovery of the latest firmware released, can anyone make it available?
Click to expand...
Click to collapse
These recovery images are from nenebear59, thanks to him !
Z016-WW-5.14.44.2212_recovery :
For 2.15GHz CPU
For 2.4GHz CPU
Thank you very much! Now I need the "persist.img" file, of the same rom, can you make it available? I thank you!
I downloaded the source code kernel from the Asus site, and the compressed file has a sensor folder. I downloaded the kernel zip file to my memory card and tried to install via recovery, however the following message appears: E: footer is wrong / E: signature verification failed. How do I get install by recovery or via flash in cmd?
I followed this tutorial (https://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061) and managed to recover the fingerprint reader, but the others are still turned off. I really need the correct file! Somebody help me, please!
I got it! I used the persist.img of the global rom of the Xiaomi Mi Mix and the sensors came back! Apparently it's a universal file that caters to any device. You can close the topic!
Hi.. i intend to downgrade my asus Zenfone 3 Deluxe to lollipop, can you upload files needed to repair issues please?
thank you!
equinoks said:
Hi.. i intend to downgrade my asus Zenfone 3 Deluxe to lollipop, can you upload files needed to repair issues please?
thank you!
Click to expand...
Click to collapse
Really??
Ryder. said:
Really??
Click to expand...
Click to collapse
sorry from nougat to marshmallow
There isn't android lollipop for the asus zenfone 3 series. They came out with marshmallow.
AndreSantoro84 said:
I got it! I used the persist.img of the global rom of the Xiaomi Mi Mix and the sensors came back! Apparently it's a universal file that caters to any device. You can close the topic!
Click to expand...
Click to collapse
HELLO! I'm having a similar issue. 5 times my Zs570kl end up stuck in Asus logo boot screen after being charging all night (with alarming overheating) . I had to wipe the device with factory reset every time to get it working again. Last time, when finally booted up, all sensor were off, and I couldn't make them work no matter how much I try factory reseting again. I think i could try to install the persist.img file you mention, could you help me to find it? Thanks so much in advance for your help.
Asus Z016D (ZS570KL) 2.15 SKU WW_user_5.15.44.2562 build
equinoks said:
Hi.. i intend to downgrade my asus Zenfone 3 Deluxe to lollipop, can you upload files needed to repair issues please?
thank you!
Click to expand...
Click to collapse
Come on. To downgrade, you need to download the official rom from the Asus website (version WW-4.12.40.1698 - do not forget to check if your device is 2.15 or 2.4 ghz). Downloaded, need to put the rom inside a micro sd card (can not be internal storage, need to be in sd). In addition, it must be with the original recovery (the version is indifferent), if it is in TWRP it will not work. Once you have done this, you will have access to recovery mode, go to the "install zip from sd card" option, locate the zip file of the rom and install it, and just wait. Having problems, report here.
cazadormoron said:
HELLO! I'm having a similar issue. 5 times my Zs570kl end up stuck in Asus logo boot screen after being charging all night (with alarming overheating) . I had to wipe the device with factory reset every time to get it working again. Last time, when finally booted up, all sensor were off, and I couldn't make them work no matter how much I try factory reseting again. I think i could try to install the persist.img file you mention, could you help me to find it? Thanks so much in advance for your help.
Asus Z016D (ZS570KL) 2.15 SKU WW_user_5.15.44.2562 build
Click to expand...
Click to collapse
Hello! To reinstall the sensors is very simple (both work to find out the way, but then it gets simple hahaha). Download the adb files (it is available here in the forum, and inside the folder put the persist.img that I will make available here.) Access the fastboot mode on the device, connect to the computer, and open the command prompt inside the folder. Open the CMD, type the following command line: fastboot flash persist persist.img and press enter. The file will be rewritten and after that the sensors will be reconfigured. Restart the device. Having problems, report here.
Solved!
AndreSantoro84 said:
Hello! To reinstall the sensors is very simple (both work to find out the way, but then it gets simple hahaha). Download the adb files (it is available here in the forum, and inside the folder put the persist.img that I will make available here.) Access the fastboot mode on the device, connect to the computer, and open the command prompt inside the folder. Open the CMD, type the following command line: fastboot flash persist persist.img and press enter. The file will be rewritten and after that the sensors will be reconfigured. Restart the device. Having problems, report here.
Click to expand...
Click to collapse
THANK YOU ANDRE!!! I'm really really happy to tell you that everything worked PERFECTLY. I wasn't sure if I need to unlock the bootloader and flash root first, so I tried to do it. I've been able to unlock the bootloader, but for some reason, when I flash the bootroot.img following the instructions from this post - https://forum.xda-developers.com/ze...v-liftoff-zs570klpro-official-unlock-t3557276 -, I get the asus logo boot loop. Anyway, without the root I flash the persist file and, as you said, all the sensors were reconfigured.
Again, muito muito obrigado!!!
cazadormoron said:
THANK YOU ANDRE!!! I'm really really happy to tell you that everything worked PERFECTLY. I wasn't sure if I need to unlock the bootloader and flash root first, so I tried to do it. I've been able to unlock the bootloader, but for some reason, when I flash the bootroot.img following the instructions from this post - https://forum.xda-developers.com/ze...v-liftoff-zs570klpro-official-unlock-t3557276 -, I get the asus logo boot loop. Anyway, without the root I flash the persist file and, as you said, all the sensors were reconfigured.
Again, muito muito obrigado!!!
Click to expand...
Click to collapse
If you want to root, flash the twrp and then supersu zip from twrp

[GUIDE]Unbrick honor6X. (No boot. No fastboot. No Recovery. No bootloader code)

NOTE:
this method is only for Honor6X and GR5-2017 Devices.
I am not responsable for any other damage:
**losing serial number,imei, or any other problem.**
this one will force to unlock bootloader code and FRP,and all your data will be erased.
it will help you to debrand to other regions easily.
************************************************************
you need at first this files:
-HL2BLNTMBD001051*
-HONOROEMINFO
-DRIVER HANDSET*
-IMAGE DOWNLOADER*
----------------------
1-Preparing files:
-exrtract all files below?
-then install driver :
{
"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"
}
-once installed open IDT and follow the steps :
-then browse in folder HL2BLNTMBD001051 and select :
----------------------
2-In the side of the phone :
-you have to open your phone to work on the motherboard :
-you need an object to touch the testpoints of the motherboard (Everything who's metallic can serve you)
-make sur that you press testpoints, then hold and put usb cable in the same time:
-[if phone turn on, turn it off and make sur that you contact between testpoints]
-you will see in the computer Your device is detected as(Huawei USB COM1.0)
if not, reinstall driver and reboot the computer.
----------------------
3-Runnig the work :
-now click on (play) button in IDT. [ you will see that the progression has started].
-once progression finished,go to the next step(4)
-if it fail..don't panic.
just flash SYSTEM.img manually with fastboot (system.img he is in fastbootimage folder).
----------------------
4-finishing:
-now your phone start working as factory mode,
reboot fastboot and flash any oeminfo file given or of your choice.
-once again done.
the last thing to do is update your firmware with eRecovery or by dload method (launching software upgrade app)
----------------------
Done :good: say thanks?
player615 said:
NOTE:
this method is only for Honor6X and GR5-2017 Devices.
I am not responsable for any other damage:
**losing serial number.or any other problem.**
this one will force to unlock bootloader code and FRP,and all your data will be erased.
it will help you to debrand to other regions easily.
************************************************************
you need at first this files:
-HL2BLNTMBD001051*
-HONOROEMINFO
-DRIVER HANDSET*
-IMAGE DOWNLOADER*
----------------------
1-Preparing files:
-exrtract all Zipped files below.
-then install driver :
-once installed open IDT and follow the steps :
-then browse in folder HL2BLNTMBD001051 and select :
----------------------
2-In the side of the phone :
-you have to open your phone to work on the motherboard :
-you need an object to touch the testpoints of the motherboard (Everything who's metallic can serve you)
-make sur that you press testpoints, then hold and put usb cable in the same time:
-[if phone turn on, turn it off and make sur that you contact between testpoints]
-you will see in the computer Your device is detected as(Huawei USB COM1.0) if not, reinstall driver and reboot the computer.
----------------------
3-Runnig the work :
-now click on (play)button in IDT.[ you will see that the progression has started].
-once progression finished,go to the next step(4)
-if it fail..don't panic.just flash SYSTEM.img manually with fastboot(system.img he is in fastbootimage folder)
----------------------
4-finishing:
-now your phone start working as factory mode, reboot fastboot and flash any oeminfo file given or of your choice.
-once again done.the last thing to do is update your firmware with eRecovery or by dload method (launching software upgrade app)
----------------------
Done :good:
Click to expand...
Click to collapse
Excellent guide. It will help a lot if people who are no longer under warranty (majority of us) and Don't mind Opening their phones. Great work. ???
Mannan Qamar said:
Excellent guide. It will help a lot if people who are no longer under warranty (majority of us) and Don't mind Opening their phones. Great work.
Click to expand...
Click to collapse
Thank you bro,?
player615 said:
NOTE:
this method is only for Honor6X and GR5-2017 Devices.
I am not responsable for any other damage:
**losing serial number.or any other problem.**
this one will force to unlock bootloader code and FRP,and all your data will be erased.
it will help you to debrand to other regions easily.
************************************************************
you need at first this files:
-HL2BLNTMBD001051*
-HONOROEMINFO
-DRIVER HANDSET*
-IMAGE DOWNLOADER*
----------------------
1-Preparing files:
-exrtract all Zipped files below.
-then install driver :
-once installed open IDT and follow the steps :
-then browse in folder HL2BLNTMBD001051 and select :
----------------------
2-In the side of the phone :
-you have to open your phone to work on the motherboard :
-you need an object to touch the testpoints of the motherboard (Everything who's metallic can serve you)
-make sur that you press testpoints, then hold and put usb cable in the same time:
-[if phone turn on, turn it off and make sur that you contact between testpoints]
-you will see in the computer Your device is detected as(Huawei USB COM1.0) if not, reinstall driver and reboot the computer.
----------------------
3-Runnig the work :
-now click on (play)button in IDT.[ you will see that the progression has started].
-once progression finished,go to the next step(4)
-if it fail..don't panic.just flash SYSTEM.img manually with fastboot(system.img he is in fastbootimage folder)
----------------------
4-finishing:
-now your phone start working as factory mode, reboot fastboot and flash any oeminfo file given or of your choice.
-once again done.the last thing to do is update your firmware with eRecovery or by dload method (launching software upgrade app)
----------------------
Done :good:
Click to expand...
Click to collapse
Thanks brother
Diego Intriago said:
Thanks brother
Click to expand...
Click to collapse
You are welcome?
WOW
thanks lot dear you give new life of my phone that was dead over a year. its really works
:fingers-crossed::fingers-crossed::fingers-crossed:
​
mirzafaisal said:
thanks lot dear you give new life of my phone that was dead over a year. its really works
:fingers-crossed::fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Your welcome?
Thank you very muchhhhh. I wait 14 month to fix this. I love youu.
It will unlock bootloader?
Mohit0033 said:
It will unlock bootloader?
Click to expand...
Click to collapse
yes
i need you help
Hi, I do the steps but when it reboots, it goes into fastboot mode or downloaded in step 3, what can I do? How do I install system manually?
thanks phone back to work again
BUT HOW TO WRITE OEMINFO FROM FASTBOOT
iguana22 said:
Hi, I do the steps but when it reboots, it goes into fastboot mode or downloaded in step 3, what can I do? How do I install system manually?
Click to expand...
Click to collapse
Flash it with fastboot i puted in guide the location of this partition..
ahwak said:
thanks phone back to work again
BUT HOW TO WRITE OEMINFO FROM FASTBOOT
Click to expand...
Click to collapse
Like others commands recovery or boot... Just change the name of partition that you want to flash
Fastboot flash oeminfo ....
player615 said:
Flash it with fastboot i puted in guide the location of this partition..
Click to expand...
Click to collapse
if I flash the system that is in the folder fasbootimage with adb it says it completes but it re-enters dowload mode when it restarts my cell phone is an honor 6x bln l21 what can I do?
iguana22 said:
if I flash the system that is in the folder fasbootimage with adb it says it completes but it re-enters dowload mode when it restarts my cell phone is an honor 6x bln l21 what can I do?
Click to expand...
Click to collapse
Repeat flash steps then flash system and do factory reset
player615 said:
Repeat flash steps then flash system and do factory reset
Click to expand...
Click to collapse
hello I did all the steps again and at the end factory reset and it stays again in fastboot can I install the app from the edl mode?
iguana22 said:
hello I did all the steps again and at the end factory reset and it stays again in fastboot can I install the app from the edl mode?
Click to expand...
Click to collapse
If you can boot erecovery just update with Otg or use sdcard, system partition don't needed at all...
player615 said:
If you can boot erecovery just update with Otg or use sdcard, system partition don't needed at all...
Click to expand...
Click to collapse
I can not enter the Erecovery mode Just enter the recovery mode with the USB cable connected to the PC and the button upwards will restart continuously maybe that's why? and arrives at 5 the update by sd when I press the 3 buttons and fail
player615 said:
If you can boot erecovery just update with Otg or use sdcard, system partition don't needed at all...
Click to expand...
Click to collapse
could install the twrp and then install some rom or custom rom? which one could I use?

How To Guide Nokia G20 boot.img flashing!

Please be aware that this could damage your phone & I'm not responsible for this. So only do this if you really feel comfortable with it & you know about the risks!
This file is only for Nokia G20 TA-1365 and should not be used for any other device.
Download this file to manually Flash partition or partitions using fastboot Command.
For more detailed tutotial on how to flash this file you can read this tutorial here by senior member fipsib at XDA!
Let's say you want to flash boot.img partition so in CMD you will enter.
"fastboot flash boot boot.img" without quotes.
I have extracted OTA stock rom for my Nokia G20 and have all the files in the screenshot below. If you want all the files shown in the screenshot below I have uploaded them to Google Drive for faster and safer downloads rather than using any other file sharing service.
I have compressed all the files in a zip format and here is the Google Drive link for all the files shown below. Please request the access to the file so that I can grant access to you. I have done this to prevent Google setting an limit to download and avoid any unnecessary downloads.
{
"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 have to unlock bootloader to flash boot.img if you have to can you tell how????
Don't know said:
Do you have to unlock bootloader to flash boot.img if you have to can you tell how????
Click to expand...
Click to collapse
Thankyou buddy but actually this post is a guide.
mvikrant97 said:
Please be aware that this could damage your phone & I'm not responsible for this. So only do this if you really feel comfortable with it & you know about the risks!
This file is only for Nokia G20 TA-1365 and should not be used for any other device.
Download this file to manually Flash partition or partitions using fastboot Command.
For more detailed tutotial on how to flash this file you can read this tutorial here by senior member fipsib at XDA!
Let's say you want to flash boot.img partition so in CMD you will enter.
"fastboot flash boot boot.img" without quotes.
I have extracted OTA stock rom for my Nokia G20 and have all the files in the screenshot below. If you want all the files shown in the screenshot below I have uploaded them to Google Drive for faster and safer downloads rather than using any other file sharing service.
I have compressed all the files in a zip format and here is the Google Drive link for all the files shown below. Please request the access to the file so that I can grant access to you. I have done this to prevent Google setting an limit to download and avoid any unnecessary downloads.
View attachment 5450449
Click to expand...
Click to collapse
Please share download link.I need to unbrick my Nokia G20 that was bricked.I have no firmware
Download this OTA ROM and flash using Apply update from SD CARD in recovery menu.
Use external SD card.
I don't know whether this will work.
ROM link
Don't know said:
Do you have to unlock bootloader to flash boot.img if you have to can you tell how????
Click to expand...
Click to collapse
Yes need to unlock bootloader.
mvikrant97 said:
Download this OTA ROM and flash using Apply update from SD CARD in recovery menu.
Use external SD card.
I don't know whether this will work.
ROM link
Click to expand...
Click to collapse
Hi thanks for the link. But my phone is bricked, can't enter recovery or fastboot mode. So the only solution here is a read firmware or scatter file.
mvikrant97 said:
Please be aware that this could damage your phone & I'm not responsible for this. So only do this if you really feel comfortable with it & you know about the risks!
This file is only for Nokia G20 TA-1365 and should not be used for any other device.
Download this file to manually Flash partition or partitions using fastboot Command.
For more detailed tutotial on how to flash this file you can read this tutorial here by senior member fipsib at XDA!
Let's say you want to flash boot.img partition so in CMD you will enter.
"fastboot flash boot boot.img" without quotes.
I have extracted OTA stock rom for my Nokia G20 and have all the files in the screenshot below. If you want all the files shown in the screenshot below I have uploaded them to Google Drive for faster and safer downloads rather than using any other file sharing service.
I have compressed all the files in a zip format and here is the Google Drive link for all the files shown below. Please request the access to the file so that I can grant access to you. I have done this to prevent Google setting an limit to download and avoid any unnecessary downloads.
View attachment 5450449
Click to expand...
Click to collapse
Kindly grant access to [email protected] need to unbrick my device
I would like to ask how do I extract the boot.img file from the phone? I can access the internals through the adb shell. I would love to learn the strategies used to extract the firmware from android devices that do not make them available. Thanks!!
karangejo said:
I would like to ask how do I extract the boot.img file from the phone? I can access the internals through the adb shell. I would love to learn the strategies used to extract the firmware from android devices that do not make them available. Thanks!!
Click to expand...
Click to collapse
Simply... You can't without root.
To get root (permanent root) you must unlock your bootloader........
Please, read this post to understand what i'm talking about https://forum.xda-developers.com/t/nokia-g21-development.4424031/
I think that today there's no way to unlock G10/G20/G21 bootloader. Then, no root or custom recovery can be build.
Maybe, @mvikrant97 can share with us some info (PM).
I unlocked my g20 TA-1343 by taking a hundred tiny screws out , shorting the test point, and using MTK Client 1.6
hyperlink of the link i pastedhttps://github.com/bkerler/mtkclient
I only took it apart because the other option was send it back to HMD
But I don't know how to flash the bin files with magisk or whatever as they're not valid images. but the thing is basically root if i felt like learning.
jdberkzk said:
I unlocked my g20 TA-1343 by taking a hundred tiny screws out , shorting the test point, and using MTK Client 1.6
hyperlink of the link i pastedhttps://github.com/bkerler/mtkclient
I only took it apart because the other option was send it back to HMD
But I don't know how to flash the bin files with magisk or whatever as they're not valid images. but the thing is basically root if i felt like learning.
Click to expand...
Click to collapse
Do you mean the bootloader unlock?
mvikrant97 said:
Do you mean the bootloader unlock?
Click to expand...
Click to collapse
Yes I unlocked the bootloader with mtk client but i have the G20 ta-1343 and. I didn't have a stom rom for it.. and I bricked it trying to root it and corrupt the gpt it looks like, now I cant get it to load in mtk client anymore. I haven't errased the rest of the phone but it is in a/b format so i dont know if i should flash it? I was stuck in boot loop
jdberkzk said:
Yes I unlocked the bootloader with mtk client but i have the G20 ta-1343 and. I didn't have a stom rom for it.. and I bricked it trying to root it and corrupt the gpt it looks like, now I cant get it to load in mtk client anymore. I haven't errased the rest of the phone but it is in a/b format so i dont know if i should flash it? I was stuck in boot loop
Click to expand...
Click to collapse
mvikrant97 said:
Do you mean the bootloader unlock?
Click to expand...
Click to collapse
I got bootloader unlocked but when i flashed magisk i got stuck on the android one screen and then now it's back to the no OS boot loop and
Error on reading data: MMC error (0xc0040030)
in mtkclient. i cant get to fastboot anymore.
I du
mvikrant97 said:
Do you mean the bootloader unlock
Click to expand...
Click to collapse
I dumped everything from my phone to my computer except userdata super otp and flashinfo i think.
the bins would flash the same as images except I can't get them to flash. should I try another firmware or?

Lg G8 AT&T boot_b.bin lost, fastboot loop

hello my name is petrus and i have a lg g8 LMG820M ATT with unlocked bootloader, i installed a custom rom ArrowOS 12.1 that worked perfectly, however i went to root with qfil and accidentally ended up replacing boot_b.bin by boot_a.bin , now the phone is stuck on fast boot screen
it already starts directly in fastboot and the text "ACTICE A/B slot - _a" no longer appears on the fastboot screen, there was no backup of boot_b.bin so I don't know how to solve it
Is there anything I can do to get it back? Or did he become a piece of garbage?
{
"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"
}
vini14zimm said:
hello my name is petrus and i have a lg g8 LMG820M ATT with unlocked bootloader, i installed a custom rom ArrowOS 12.1 that worked perfectly, however i went to root with qfil and accidentally ended up replacing boot_b.bin by boot_a.bin , now the phone is stuck on fast boot screen
it already starts directly in fastboot and the text "ACTICE A/B slot - _a" no longer appears on the fastboot screen, there was no backup of boot_b.bin so I don't know how to solve it
Is there anything I can do to get it back? Or did he become a piece of garbage?
View attachment 5656703
Click to expand...
Click to collapse
No, not a piece of garbage lol. Given the tools available for the G8; qfil, the programmers firehose, engineering abl, it's almost impossible to brick the device.
So, lesson learned; always make a backup. It sounds like you copied the boot partition for the slot that had at&t rom on it, to the slot that had ArrowOS on it? If so, sounds like just finding a copy of the ArrowOS boot partition should work?
Which version are you running? Someone may have that boot partition available.
AsItLies said:
No, not a piece of garbage lol. Given the tools available for the G8; qfil, the programmers firehose, engineering abl, it's almost impossible to brick the device.
So, lesson learned; always make a backup. It sounds like you copied the boot partition for the slot that had at&t rom on it, to the slot that had ArrowOS on it? If so, sounds like just finding a copy of the ArrowOS boot partition should work?
Which version are you running? Someone may have that boot partition available.
Click to expand...
Click to collapse
yes that was exactly it, i understand i will never do anything without backup, i was using Arrow-v12.1-alphalm-UNOFFICIAL-20220627
so if someone has lg g8 and is using Arrow v12.1 alpham send boot_b.bin and I copy it using QFIL will my device boot again?
vini14zimm said:
yes that was exactly it, i understand i will never do anything without backup, i was using Arrow-v12.1-alphalm-UNOFFICIAL-20220627
so if someone has lg g8 and is using Arrow v12.1 alpham send boot_b.bin and I copy it using QFIL will my device boot again?
Click to expand...
Click to collapse
Well, if all that's changed is the boot partition it should boot again. But I checked on tele group and no one responded with it.
You may have to download the rom and see if you can extract the boot partition from it.
II have the same problem, were you able to solve it?
i need help
yonaikymatos said:
II have the same problem, were you able to solve it?
Click to expand...
Click to collapse
I'm trying to extract this boot_b.bin from the room that AsItLies said, but I'm not going to lie I don't have much knowledge of how to do this so I still haven't been able to extract this file
It's very difficult to extract one without knowing how to do it but I'm still trying
vini14zimm said:
I'm trying to extract this boot_b.bin from the room that AsItLies said, but I'm not going to lie I don't have much knowledge of how to do this so I still haven't been able to extract this file
It's very difficult to extract one without knowing how to do it but I'm still trying
Click to expand...
Click to collapse
Okay, think this is what you need. BUT!! I'm not 100% it is... SO! first thing you do is back up the boot image from the slot you want to replace it with this one. That way, if it doesn't work, you can just reflash the one you backed up and you're none the worse.
Second: IF, when flashing this image to the boot partition (loading it in qfil speak), you get a warning message about 'over flow of data' (or something to that effect), immediately stop, do not continue, as that's an indication it will not only not work but make your situation worse. Good luck
sorry, xda not allowing me to attach, follow this gdrive link for file.
vini14zimm said:
I'm trying to extract this boot_b.bin from the room that AsItLies said, but I'm not going to lie I don't have much knowledge of how to do this so I still haven't been able to extract this file
It's very difficult to extract one without knowing how to do it but I'm still trying
Click to expand...
Click to collapse
I already solved it I'm going to attach the boot_b .bin
https://drive.google.com/file/d/1DANvrF-iklHQxr3bIOixv9orD376oG8U/view
the file is boot-a Android 11 Canadienc.bin
flash using qfil on a boot_b
AsItLies said:
Okay, think this is what you need. BUT!! I'm not 100% it is... SO! first thing you do is back up the boot image from the slot you want to replace it with this one. That way, if it doesn't work, you can just reflash the one you backed up and you're none the worse.
Second: IF, when flashing this image to the boot partition (loading it in qfil speak), you get a warning message about 'over flow of data' (or something to that effect), immediately stop, do not continue, as that's an indication it will not only not work but make your situation worse. Good luck
sorry, xda not allowing me to attach, follow this gdrive link for file.
Click to expand...
Click to collapse
I put arrowOS-boot.img in place of boot_b.bin using Qfil but I'm still at the fast boot screen, is there anything else I can do?
yonaikymatos said:
I already solved it I'm going to attach the boot_b .bin
https://drive.google.com/file/d/1DANvrF-iklHQxr3bIOixv9orD376oG8U/view
the file is boot-a Android 11 Canadienc.bin
flash using qfil on a boot_b
Click to expand...
Click to collapse
for some reason it's not being possible to put your boot-a Android 11 Canadienc.bin in place of my boot_b.bin , when I try to get this message Send image fail:Firehose Fail:FHLoader Failrocess fail , it doesn't seem like a good sign
vini14zimm said:
for some reason it's not being possible to put your boot-a Android 11 Canadienc.bin in place of my boot_b.bin , when I try to get this message Send image fail:Firehose Fail:FHLoader Failrocess fail , it doesn't seem like a good sign
View attachment 5659247
Click to expand...
Click to collapse
Don't use a usb 3.0 port when using qfil. You have to use a usb 2.0 port. Qfil is old software and was not designed for the higher speeds.
This is important whether making a backup of a partition of flashing a partition, either way with 3.x ports the image can get corrupted.
AsItLies said:
Don't use a usb 3.0 port when using qfil. You have to use a usb 2.0 port. Qfil is old software and was not designed for the higher speeds.
This is important whether making a backup of a partition of flashing a partition, either way with 3.x ports the image can get corrupted.
Click to expand...
Click to collapse
I put it in a usb 2.0 port and it was the same, this file does not seem to be compatible
Is there anything else I can do to save the device?
vini14zimm said:
I put it in a usb 2.0 port and it was the same, this file does not seem to be compatible
Is there anything else I can do to save the device?
View attachment 5664851
Click to expand...
Click to collapse
I'd suggest joining the tele group for that rom and asking there if anyone can give you the version of the boot partition you need.
AsItLies said:
I'd suggest joining the tele group for that rom and asking there if anyone can give you the version of the boot partition you need.
Click to expand...
Click to collapse
kinda had the same problem lol on 2023... anyways tried to fix it the way of netmsm, deleting all partitions, hard bricked i could say, kinda worked, but as far as i could do, it went to fastboot loop, to LG Bootlloooping lol, any recommendations

Question Red Warning and UnWorking Lockscreen. 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"
}
Hello, dear owners of this beautiful device.
After an unsuccessful attempt to get root, such a warning appeared, plus the ability to lock the screen disappeared. As a result, I didn't get root either and problems arose)
Could you show the instructions how to fix everything step by step and get root? Thanks)
Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...
redmgicUSER8 said:
Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...
Click to expand...
Click to collapse
did anything happen?
Stusick said:
Did anything happen?
Click to expand...
Click to collapse
Nothing yet... I'm trying to contact the support team. They can only do so much remotely
i have this error also what should i do?
the phone not boot up
the red warning are stuck
yakir150 said:
i have this error also what should i do?
the phone not boot up
the red warning are stuck
Click to expand...
Click to collapse
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
okay i try it and still no luck the same problem
yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.
[email protected] said:
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.
Click to expand...
Click to collapse
my phone is eu and using 4.18
can i use 3.19?
it's ok?
yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
For QFIL, use Flat Build and in the configuration use ufs. Good luck!
yakir150 said:
my phone is eu and using 4.18
can i use 3.19?
it's ok?
Click to expand...
Click to collapse
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.
[email protected] said:
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.
Click to expand...
Click to collapse
okay i will try and let you know
thank you very much
yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
If QFIL does not work, you need to do side load the rom multiple times again then it might work!
turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"
izsdeaman said:
turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"
Click to expand...
Click to collapse
The command on PC shows "Too many arguments." The Termux one works. Thanks!
[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
Tahnk you very very very much.

Categories

Resources