*******Solved thanks to Anteo*****I was rooted on Oreo MHA-L29C432 329(log) and I tried to unroot resulting on a bricked phone. Now I have only two bootload options(see screenshots) and erecovery. I cannot flash anything on bootload, I get errors on flashing twrp, boot image etc. Dload method also unsuccessful. Even with: "fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img" it says that flash is successful but twrp is not accessible or installed. Any help please.
Download and extract update.zip from your oreo firmware, from http://pro-teammt.ru/firmware-database/
Download Huawei Update Extractor.
Open Huawei Update Extractor. Click on the '..' button, open update.app that you extracted earlier.
Right click on RAMDISK, click in Extract Selected.
Flash ramdisk using fastboot flash ramdisk RAMDISK.img
You could extract KERNEL too and flash using fastboot flash kernel KERNEL.img
ante0 said:
Download and extract update.zip from your oreo firmware, from http://pro-teammt.ru/firmware-database/
Download Huawei Update Extractor.
Open Huawei Update Extractor. Click on the '..' button, open update.app that you extracted earlier.
Right click on RAMDISK, click in Extract Selected.
Flash ramdisk using fastboot flash ramdisk RAMDISK.img
You could extract KERNEL too and flash using fastboot flash kernel KERNEL.img
Click to expand...
Click to collapse
Thanks for the reply. Unfortunately when I load Update.app on the update extractor I get this error(see photo)
Edit: I unchecked some features on the settings of the extractor and now is extracting
jogefo said:
Thanks for the reply. Unfortunately when I load Update.app on the update extractor I get this error(see photo)
Click to expand...
Click to collapse
as expected... :/
I will download and extract it. Hold on.
Edit: To clarify, Huawei did something to erecovery_ramdisk (erecovery_ramdis) so the matching HEADER for it doesn't match,m so you have to extract using the splitupdate perl script (https://github.com/marcominetti/split_updata.pl though I'm using a pull request because it can filter what to extract https://github.com/smoser/split_updata.pl )
Here you go: https://mega.nz/#!1axXxSBD!bTpdnvUVoebD44up_dhOchHOGnVhPME4_eBNygV2mbI
Dear Anteo
It really worked your solution. You are a genius.
Thank you so much,
George
ante0 said:
as expected... :/
I will download and extract it. Hold on.
Edit: To clarify, Huawei did something to erecovery_ramdisk (erecovery_ramdis) so the matching HEADER for it doesn't match,m so you have to extract using the splitupdate perl script (https://github.com/marcominetti/split_updata.pl though I'm using a pull request because it can filter what to extract https://github.com/smoser/split_updata.pl )
Here you go: https://mega.nz/#!1axXxSBD!bTpdnvUVoebD44up_dhOchHOGnVhPME4_eBNygV2mbI
Click to expand...
Click to collapse
jogefo said:
Dear Anteo
It really worked your solution. You are a genius.
Thank you so much,
George
Click to expand...
Click to collapse
Thank you
please help sir.
ante0 said:
as expected... :/
I will download and extract it. Hold on.
Edit: To clarify, Huawei did something to erecovery_ramdisk (erecovery_ramdis) so the matching HEADER for it doesn't match,m so you have to extract using the splitupdate perl script (https://github.com/marcominetti/split_updata.pl though I'm using a pull request because it can filter what to extract https://github.com/smoser/split_updata.pl )
Here you go: https://mega.nz/#!1axXxSBD!bTpdnvUVoebD44up_dhOchHOGnVhPME4_eBNygV2mbI
Click to expand...
Click to collapse
i tried to root my mate 9 l29 c636 with 8.0.0.361 rom but it got in bootloops.
now error mode is showing only.
i find one thread with similar issues, which you helped.
please help, as i am unable to extract any image using update extractor.
my phone is showing error:- please update system again.
funct no 11 ( recovery image)
error no 2 (load failed)
please help sir
smsmasti said:
i tried to root my mate 9 l29 c636 with 8.0.0.361 rom but it got in bootloops.
now error mode is showing only.
i find one thread with similar issues, which you helped.
please help, as i am unable to extract any image using update extractor.
my phone is showing error:- please update system again.
funct no 11 ( recovery image)
error no 2 (load failed)
please help sir
Click to expand...
Click to collapse
Download and extract: https://mega.nz/#!ELYREZyZ!E1p-CZsjvMJQ5f1kphJIwKFvtFlOS3Z8Q5Cbs4Wy_Nw
Boot to fastboot & rescure, flash:
fastboot flash ramdisk RAMDISK.img
fastboot flash kernel KERNEL.img
fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img
now you should be able to use update guide again.
Edit: Currently you can only flash SuperSU2.82:
For encrypted phone: https://mega.nz/#!dPISSKab!RKomqYjYh9lB1WCkAZY97f2CJvrdLdsSA5U9fk4GeMY
For decrypted phone: https://mega.nz/#!MDoBVabL!_X47_o9jnUOMLMfIDx45jsOdGRhLffHUdyUElb6enho
ante0 said:
Download and extract: https://mega.nz/#!ELYREZyZ!E1p-CZsjvMJQ5f1kphJIwKFvtFlOS3Z8Q5Cbs4Wy_Nw
Boot to fastboot & rescure, flash:
fastboot flash ramdisk RAMDISK.img
fastboot flash kernel KERNEL.img
fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img
now you should be able to use update guide again.
Edit: Currently you can only flash SuperSU2.82:
For encrypted phone: https://mega.nz/#!dPISSKab!RKomqYjYh9lB1WCkAZY97f2CJvrdLdsSA5U9fk4GeMY
For decrypted phone: https://mega.nz/#!MDoBVabL!_X47_o9jnUOMLMfIDx45jsOdGRhLffHUdyUElb6enho
Click to expand...
Click to collapse
done ,as you said...
still same screen...
only chnage is that now i can see a android bootlogo screen...then goes to same error mode
smsmasti said:
done ,as you said...
still same screen...
only chnage is that now i can see a android bootlogo screen...then goes to same error mode
Click to expand...
Click to collapse
Same error?
ante0 said:
Same error?
Click to expand...
Click to collapse
yes
smsmasti said:
yes
Click to expand...
Click to collapse
here is the image...
when i am trying to extract image files using update extractor, its is saying..recvover_ramdis.img: invalid header crc- expected 17423 got 53274
smsmasti said:
yes
Click to expand...
Click to collapse
And fastboot didn't say Remote error or anything like that?
Try boot to recovery.
Ah, saw image now.
---------- Post added at 04:01 PM ---------- Previous post was at 03:53 PM ----------
smsmasti said:
when i am trying to extract image files using update extractor, its is saying..recvover_ramdis.img: invalid header crc- expected 17423 got 53274
Click to expand...
Click to collapse
That's because Huawei did something. It's erecovery.
Disable CRC in settings of Huawei update extractor
ante0 said:
And fastboot didn't say Remote error or anything like that?
Try boot to recovery.
Ah, saw image now.
---------- Post added at 04:01 PM ---------- Previous post was at 03:53 PM ----------
That's because Huawei did something. It's erecovery.
Disable CRC in settings of Huawei update extractor
Click to expand...
Click to collapse
can i flash system.img after extracting. will it help
smsmasti said:
can i flash system.img after extracting. will it help
Click to expand...
Click to collapse
Nope. Just RECOVERY_RAMDISK.img, RAMDISK.img and KERNEL.img.
eRecovey can't be flashed from fastboot
ante0 said:
Nope. Just RECOVERY_RAMDISK.img, RAMDISK.img and KERNEL.img.
eRecovey can't be flashed from fastboot
Click to expand...
Click to collapse
what can i do now
smsmasti said:
what can i do now
Click to expand...
Click to collapse
Could try flashing the other RECOVERY_VENDOR and RECOVERY_VBMETA. But it should work unless fastboot says something else.
Fastboot mode says FRP UNLOCK, right?
ante0 said:
Could try flashing the other RECOVERY_VENDOR and RECOVERY_VBMETA. But it should work unless fastboot says something else.
Fastboot mode says FRP UNLOCK, right?
Click to expand...
Click to collapse
yes frp and bootloader both unlock
smsmasti said:
yes frp and bootloader both unlock
Click to expand...
Click to collapse
Can you take a screenshot of command prompt after you've flashed the images?
Related
My device's rom is MT7-L09V100R001C00B133SP11, I tried to install B127 MT7-L09 West Europe rom but have error while installing the rom. The error is "huawei cust fail". I tried many roms (B120, B121, B126, B127) but no success and everytime the same error. But I can flash only its original rom MT7-L09V100R001C00B133SP11 without any problem. How to solve this problem? Help please.
Tried to flash after FLASHE of Rom, the Cust.img in flash mode?
fastboot flash cust cust.img
The Cust you can find here.
https://mega.co.nz/#!uQ4mFTjB!vcz0m0Ea4mUjkIQdQEgCtdnn3RkpxKK1sFDHbPSvWSA
Fooox1 said:
Tried to flash after FLASHE of Rom, the Cust.img in flash mode?
fastboot flash cust cust.img
The Cust you can find here.
https://mega.co.nz/#!uQ4mFTjB!vcz0m0Ea4mUjkIQdQEgCtdnn3RkpxKK1sFDHbPSvWSA
Click to expand...
Click to collapse
No problem flashing cust. When I put the rom dload and to install full rom it gives error. I could not flash any rom from dload except b133.
Then extract the desired Rome and boot.img, recovery.img, system.img and cust.img manual flash.
command:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
Then it should start and you can do that Rome again completely FLASHE.
Fooox1 said:
Then extract the desired Rome and boot.img, recovery.img, system.img and cust.img manual flash.
command:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
Then it should start and you can do that Rome again completely FLASHE.
Click to expand...
Click to collapse
I did everything you write. Everytime no success. I think there was a regional lock on our phones. I think I must flash more img files to unlock regional lock.
Of course, the boot loader mechanism to be open. More imgs can not flash itself. All other get error messages.
Open bootloader, flash Custom Rom would be an alternative.
Fooox1 said:
Of course, the boot loader mechanism to be open. More imgs can not flash itself. All other get error messages.
Open bootloader, flash Custom Rom would be an alternative.
Click to expand...
Click to collapse
My bootloader is unlocked. Which custom rom can I flash.
Try it so that is close to stock and deodexd.
http://forum.xda-developers.com/mate-7/orig-development/custom-rom-kangvip-rom-b122sp06v1-1-t3022436
Fooox1 said:
Try it so that is close to stock and deodexd.
http://forum.xda-developers.com/mate-7/orig-development/custom-rom-kangvip-rom-b122sp06v1-1-t3022436
Click to expand...
Click to collapse
But it says "In addition, you should the B127 MT7-L09 Western Europe or the B122SP06 installed, otherwise it will get to the bootloop." and my rom is not b127 or b126. My rom is b133. Will it bootloop.
b127 is the minimum requirement, you lie already higher. If so beware.
Fooox1 said:
b127 is the minimum requirement, you lie already higher. If so beware.
Click to expand...
Click to collapse
Can you explain step by step what will I do.
I'm in cust fail error drama like you, i have TL 10 international stuck in b119 original firmware but i got root with alternative method whitout unlock boot loader.
Cust fail appears even if i simply Hard reset my phone the root remains
No ROM upgrade via ota non ROM can be flashed via SD card method.
My questions:
Can i try to flash original firmware via fast boot without unlock boot loader first?
I unpacked update.app with extractor and got many file : cust boot recovery modem etc
Which One should i flash and in which order?
Thnks in advance forma help
Without unlocked bootloader you can not flash imgs. If you have unpack the zip you a dload folder that is on the SD and you can flash.
---------- Post added at 01:21 PM ---------- Previous post was at 01:17 PM ----------
isaekrem said:
Can you explain step by step what will I do.
Click to expand...
Click to collapse
You can read it in the manual.
- Flash KangVIP recovery
- Zip to the SD
- Factory reset in recovery
- Flash zip
Done.
Fooox1 said:
Without unlocked bootloader you can not flash imgs. If you have unpack the zip you a dload folder that is on the SD and you can flash.
---------- Post added at 01:21 PM ---------- Previous post was at 01:17 PM ----------
You can read it in the manual.
- Flash KangVIP recovery
- Zip to the SD
- Factory reset in recovery
- Flash zip
Done.
Click to expand...
Click to collapse
Thanks. Now I am on kangvip rom.
can someone upload they cust folder for me?
hey
after few topic here i last give up
my phone now like dead
only recovery mode with cmw or fastboot mode
yeah i have access to type command in adb mode
but i cant find my rom
i download like 20 stock rom from huawei site
and i try extract it but it now make exe file after extraxt
like post
EXTRA: Working With UPDATE.APP - Making it flashable for SP Flash Tool
Click to expand...
Click to collapse
pleaseeeee help me for unbrick my phone
it start with command
fastboot flash boot boot.img
Click to expand...
Click to collapse
im like now not sure what do this command exactly
all i know it for make the boot of phone start with cwm
but after i found same tools i know how to open fastboot mode
but now my phone only boot to fastboot mode
i try command
fastboot flash boot boot.img
Click to expand...
Click to collapse
with boot.img file i got from update.app i try to extraxt but it long boot and not do anything just huwaei logo
please same one help me with get corruct file to download and then extraxt it to get file txt to try flash it with SP Flash Tool
i try command
fastboot flash system system.img
Click to expand...
Click to collapse
with system.img file but it get error
and i try with dload folder and inside it file update.app
but i got error
what i do guys to solve my problem
waiting any help:crying:
1. find any rom for g6-u10
2. flash original recovery.img (via fastboot, so you will loose cwm)
3. copy update.app into dload folder on your SD card
4.power off phone
5. hold volume+ volume - simultaneously, then pres power for short time (until you see something is happening and when you see it started you can release volumes. then you will see flashing original process.
done.
thanks for reply , i waiting same help from few days and i hope try with me :crying:
osmera said:
1. find any rom for g6-u10
Click to expand...
Click to collapse
i did and download like 15 files firmware from huawei for g6 but i need orginal stock
osmera said:
2. flash original recovery.img (via fastboot, so you will loose cwm)
Click to expand...
Click to collapse
i cant extraxt update.app (file exe to convert files after extraxt not come with files extraxt from update.app)
osmera said:
3. copy update.app into dload folder on your SD card
Click to expand...
Click to collapse
i did this tow
but it show error
C:\adb>fastboot flash system system.img
sending 'system' (1020171 KB)... FAILED (remote: data length is too large)
finished. total time: -0.000s
Click to expand...
Click to collapse
osmera said:
4.power off phone
5. hold volume+ volume - simultaneously, then pres power for short time (until you see something is happening and when you see it started you can release volumes. then you will see flashing original process.
done.
Click to expand...
Click to collapse
i can change bot but i dont have rom zip with stable and cant sending system.img , can u give me zip rom or help me get system in phone
if i try same firm with command system
C:\adb> fastboot flash system system.img
sending 'system' (539684 KB)...
FAILED (remote: data too large)
finished. total time: 0.004s
Click to expand...
Click to collapse
thanks for nothing
i fix it with G6-U10 EMUI 3.0 to EMUI 2.0 Roll back.zip
c0derman said:
thanks for nothing
i fix it with G6-U10 EMUI 3.0 to EMUI 2.0 Roll back.zip
Click to expand...
Click to collapse
hi where can i download that file you mentioned? please i need help same issue with your phone. please please please please! i beg you:crying:
download from here
http://consumer.huawei.com/be/support/products/downloads/ascend-g6-be.htm
notice : file zip size 742mg this is file not any other files
c0derman said:
download from here
http://consumer.huawei.com/be/support/products/downloads/ascend-g6-be.htm
notice : file zip size 742mg this is file not any other files
Click to expand...
Click to collapse
How did you flash it? W/o unlocked bootloader ?
Hello everyone
I'm in a huge trouble, I flashed recovery partition using twrp on oreo firmware by mistake and now I can't enter to bootloader mode to reflash recovery using the extracted recovery.img from UPDATE.APP.
I already tried:
dload folder with UPDATE.APP and pressing volume down, volume up and power button
Press & hold power button and plug the USB cable
Neither of them work, and my phone is stucked in ERROR MODE saying:
Attention!
Plase update system again
Error!
Func NO: 11 (recovery image)
Error No: 2 (load failed!)
Please help, I do not what to do or at least enter to bootloader to reflash the custom recovery.
Hi, I have the same problem. Were you able to fix it?
plug in usb, hold power and vol down until you get to fastboot.
If you are on OREO now, make sure to extract recovery_ramdisk and recovery_kernel, and flash both in fastboot
fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img
fastboot flash recovery_kernel RECOVERY_KERNEL.img
If you can't find RECOVERY_RAMDISK you're using a nougat update.app.
ante0 said:
plug in usb, hold power and vol down until you get to fastboot.
If you are on OREO now, make sure to extract recovery_ramdisk and recovery_kernel, and flash both in fastboot
fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img
fastboot flash recovery_kernel RECOVERY_KERNEL.img
If you can't find RECOVERY_RAMDISK you're using a nougat update.app.
Click to expand...
Click to collapse
Hi,
I would like to know where to find RECOVERY_KERNEL.img, as there's no UPDATE.APP contains it.
I have the very same problem, but I managed to enter the fastboot though.
Another question, how to flash the erecovery partitions, it seems it has been blocked from access.
thanks.:good:
liuyujack said:
Hi,
I would like to know where to find RECOVERY_KERNEL.img, as there's no UPDATE.APP contains it.
I have the very same problem, but I managed to enter the fastboot though.
Another question, how to flash the erecovery partitions, it seems it has been blocked from access.
thanks.:good:
Click to expand...
Click to collapse
Woops. There's no recovery_kernel. There's ERECOVERY_KERNEL.
Recovery most likely uses regular KERNEL.
You can flash erecovery partitions in twrp, using dd.
ante0 said:
Woops. There's no recovery_kernel. There's ERECOVERY_KERNEL.
Recovery most likely uses regular KERNEL.
You can flash erecovery partitions in twrp, using dd.
Click to expand...
Click to collapse
Thanks for the explanation. however, to leave the error mode, I flashed recovery_ramdisk, ramdisk, kernel, and system, but it still stuck there the moment I leave the fastboot with the same error code.
Do you know why this is or have any solution?
Thanks.
liuyujack said:
Thanks for the explanation. however, to leave the error mode, I flashed recovery_ramdisk, ramdisk, kernel, and system, but it still stuck there the moment I leave the fastboot with the same error code.
Do you know why this is or have any solution?
Thanks.
Click to expand...
Click to collapse
Same error code as: Error!
Func NO: 11 (recovery image)
Error No: 2 (load failed!)
?
ante0 said:
Same error code as: Error!
Func NO: 11 (recovery image)
Error No: 2 (load failed!)
?
Click to expand...
Click to collapse
yes, exactly
ante0 said:
Same error code as: Error!
Func NO: 11 (recovery image)
Error No: 2 (load failed!)
?
Click to expand...
Click to collapse
liuyujack said:
yes, exactly
Click to expand...
Click to collapse
additional information:
fastboot oem lock-state info
...
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ 0.007s]
finished. total time: 0.007s
as: Error!
Func NO: 14 (no image found)
Error No: 2 (load failed!)
similar one here. Is there any solution?
liuyujack said:
yes, exactly
Click to expand...
Click to collapse
Hi !
Did you find a solution ?
I have the same errors, Desperately looking for a solution.... Did anyone get it figured out?
Thanks
I finally figured it out. Hopefully this will help somebody else. I ended up fixing it by using DC unlocker. That Basically got me to where I could boot into erecovery. It also allowed me to use ADB to flash TWRP. From there I just flashed the entire hwota8 package. I'm back up and running thankfully. Once again, I really appreciate you and people like you who help others on this forum.
seti007 said:
I finally figured it out. Hopefully this will help somebody else. I ended up fixing it by using DC unlocker. That Basically got me to where I could boot into erecovery. It also allowed me to use ADB to flash TWRP. From there I just flashed the entire hwota8 package. I'm back up and running thankfully. Once again, I really appreciate you and people like you who help others on this forum.
Click to expand...
Click to collapse
Could you do a guide for that?
Has anyone found a solution.? Im about ready to jump the gun on dc phoenix. But if someone found an alternative, it would really help.
-flash stock firmware with newflasher
-boot once. Install magisk manager app and patch stock boot image. (You can find it in Martinx3 stock recovery) than copy patched boot image to your computer.
-in fastboot:
* fastboot erase system
*fastboot flash userdata userdata.img
*fastboot flash system yoursystemfile.img
Optionally if you want to flash gapps
*fastboot flash boot twrp.img
*fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Flash gapps in twrp and than select install image and choose patched_boot.img and select boot partition
if not just do
*fastboot flash boot patched_boot.img
*fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
*reboot
(To install magisk you need to boot once and then do fastboot flash boot patched_boot.img again)
Twrp you can find here https://forum.xda-developers.com/xp...recovery-twrp-3-2-2-0-touch-recovery-t3821597
Userdata.img-https://drive.google.com/file/d/1Ni_lU5jY3oQ4GDbezJ83BOLKNbLvU4ue/view
How copy patched boot image on computer? Thanks!
Connect your phone to pc and just copy it like a normall file. You can find it in download folder.
alexsmel1 said:
How copy patched boot image on computer? Thanks!
Click to expand...
Click to collapse
lolnwl said:
Connect your phone to pc and just copy it like a normall file. You can find it in download folder.
Click to expand...
Click to collapse
PS C:\ADB> fastboot flash patched_boot.img
unknown partition 'patched_boot.img'
error: cannot determine image filename for 'patched_boot.img'
---------- Post added at 04:00 PM ---------- Previous post was at 03:59 PM ----------
alexsmel1 said:
How copy patched boot image on computer? Thanks!
Click to expand...
Click to collapse
lolnwl said:
Connect your phone to pc and just copy it like a normall file. You can find it in download folder.
Click to expand...
Click to collapse
PS C:\ADB> fastboot flash patched_boot.img
unknown partition 'patched_boot.img'
error: cannot determine image filename for 'patched_boot.img'
How do i fix this? Thank!
alexsmel1 said:
PS C:\ADB> fastboot flash patched_boot.img
unknown partition 'patched_boot.img'
error: cannot determine image filename for 'patched_boot.img'
---------- Post added at 04:00 PM ---------- Previous post was at 03:59 PM ----------
PS C:\ADB> fastboot flash patched_boot.img
unknown partition 'patched_boot.img'
error: cannot determine image filename for 'patched_boot.img'
How do i fix this? Thank!
Click to expand...
Click to collapse
It should be fastboot flash boot patched_boot.img.
lolnwl said:
Connect your phone to pc and just copy it like a normall file. You can find it in download folder.
Click to expand...
Click to collapse
Before the fastboot flash patched_boot.img command, I requested twrp of my stock firmware.
fastboot flash boot twrp-xz2.img
* fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
After that, it booted into recovery and installed the patched_boot.img and select boot partition.
After that, it was loaded into the system after the logo was loaded, it disappears and the black screen remains on, after that the reboot is permanent.
Help please solve the problem.
I took the boot.img file from the latest aosp firmware from MartinX3. Maybe I did something wrong?
alexsmel1 said:
Before the fastboot flash patched_boot.img command, I requested twrp of my stock firmware.
fastboot flash boot twrp-xz2.img
* fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
After that, it booted into recovery and installed the patched_boot.img and select boot partition.
After that, it was loaded into the system after the logo was loaded, it disappears and the black screen remains on, after that the reboot is permanent.
Help please solve the problem.
Click to expand...
Click to collapse
Do all the steps from the instructions and it will work
lolnwl said:
Do all the steps from the instructions and it will work
Click to expand...
Click to collapse
I took the boot.img file from the latest aosp firmware from MartinX3. Maybe I did something wrong?
---------- Post added at 04:22 PM ---------- Previous post was at 04:21 PM ----------
lolnwl said:
Do all the steps from the instructions and it will work
Click to expand...
Click to collapse
I took the boot.img file from the latest aosp firmware from MartinX3. Did I do this correctly or did I do something wrong?
---------- Post added at 04:22 PM ---------- Previous post was at 04:22 PM ----------
lolnwl said:
Do all the steps from the instructions and it will work
Click to expand...
Click to collapse
I took the boot.img file from the latest aosp firmware from MartinX3. Did I do this correctly or did I do something wrong?
---------- Post added at 04:22 PM ---------- Previous post was at 04:22 PM ----------
lolnwl said:
Do all the steps from the instructions and it will work
Click to expand...
Click to collapse
I took the boot.img file from the latest aosp firmware from MartinX3. Did I do this correctly or did I do something wrong?
alexsmel1 said:
I took the boot.img file from the latest aosp firmware from MartinX3. Maybe I did something wrong?
Click to expand...
Click to collapse
Get the boot.img from stock martinx3 recovery.
lolnwl said:
Get the boot.img from stock martinx3 recovery.
Click to expand...
Click to collapse
You will forgive me, but I don’t know where to boot.img file. I have firmware 52.0.A.3.84, in the stock_twrp_xz2_52.0.A.3.84 folder there are only such files twrp-xz2.img and vbmeta.img. I apologize for so many problems that have arisen because of me.
alexsmel1 said:
You will forgive me, but I don’t know where to boot.img file. I have firmware 52.0.A.3.84, in the stock_twrp_xz2_52.0.A.3.84 folder there are only such files twrp-xz2.img and vbmeta.img. I apologize for so many problems that have arisen because of me.
Click to expand...
Click to collapse
First of all you should update stock to the newest version to update all driver(52.0.A.3.202 is the newest with twrp support) and than unpack stock twrp and go to twrp-stock-installer and copy boot.img
lolnwl said:
First of all you should update stock to the newest version to update all driver(52.0.A.3.202 is the newest with twrp support) and than unpack stock twrp and go to twrp-stock-installer and copy boot.img
Click to expand...
Click to collapse
Thanks! Where you need to get userdata.img?
https://drive.google.com/file/d/1Ni_lU5jY3oQ4GDbezJ83BOLKNbLvU4ue/view?usp=sharing
lolnwl said:
https://drive.google.com/file/d/1Ni_lU5jY3oQ4GDbezJ83BOLKNbLvU4ue/view?usp=sharing
Click to expand...
Click to collapse
I really appreciate your work. I did everything according to the instructions:
fastboot erase system
fastboot flash userdata userdata.img
Fastboot flash system system.img (PixelExperienceP-arm-aonly)
fastboot flash boot patched_boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
After that, my phone goes into reboot after the appearance of the logo. I do not know what to do. Sorry for the problems that I delivered. Help please fix it.
alexsmel1 said:
I really appreciate your work. I did everything according to the instructions:
fastboot erase system
fastboot flash userdata userdata.img
Fastboot flash system system.img (PixelExperienceP-arm-aonly)
fastboot flash boot patched_boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
After that, my phone goes into reboot after the appearance of the logo. I do not know what to do. Sorry for the problems that I delivered. Help please fix it.
Click to expand...
Click to collapse
Our device is ab partition!!! A only gsi will not boot! Download ab version and give it a try
lolnwl said:
Our device is ab partition!!! A only gsi will not boot! Download ab version and give it a try
Click to expand...
Click to collapse
Thank you very much my friend !!!!!!!!!!! Thanks to you, I managed to do it finally. I am very happy for your help !!!!!!!!! Thank!!!!: о: о: о
alexsmel1 said:
Thank you very much my friend !!!!!!!!!!! Thanks to you, I managed to do it finally. I am very happy for your help !!!!!!!!! Thank!!!!: о: о: о
Click to expand...
Click to collapse
no problem
Nice that you want to give us a gsi guide.
And now my critics :silly:
Code:
1. You don't need to erase the system.
Flashing a partition does it too.
And we may have the erase bug in the bootloader, where executing the erase command on its own may take more than only 1 second.
Code:
2. You can flash the system.img in the twrp.
And of course wipe the userdata, too (userdata and internal storage due to encryption).
Code:
3. A styled guide with the XDA forum bbcode would be nice. :)
MartinX3 said:
Nice that you want to give us a gsi guide.
And now my critics :silly:
Code:
1. You don't need to erase the system.
Flashing a partition does it too.
And we may have the erase bug in the bootloader, where executing the erase command on its own may take more than only 1 second.
Code:
2. You can flash the system.img in the twrp.
And of course wipe the userdata, too (userdata and internal storage due to encryption).
Code:
3. A styled guide with the XDA forum bbcode would be nice. :)
Click to expand...
Click to collapse
Thanks for your reply. Its my first guide so it may not be the best.
I tried to flash system.img from twrp but after that flashlight did not work so I chosed fastboot for flashing
lolnwl said:
Thanks for your reply. Its my first guide so it may not be the best.
I tried to flash system.img from twrp but after that flashlight did not work so I chosed fastboot for flashing
Click to expand...
Click to collapse
Then the flash light start working?
Technically twrp should do the same
Someone plz help me I got stuck on fastboot mode while installing custom recovery and ROM
Phantom010 said:
Someone plz help me I got stuck on fastboot mode while installing custom recovery and ROM
Click to expand...
Click to collapse
Are you able to power off your device ?
Nameless Foe said:
Are you able to power off your device ?
Click to expand...
Click to collapse
Yes I can also install custom recovery but no ROM can boot up from custom recovery! If I keep device on fastboot mode it automatically turns off and turn on to fastboot mode.
Phantom010 said:
Yes I can also install custom recovery but no ROM can boot up from custom recovery! If I keep device on fastboot mode it automatically turns off and turn on to fastboot mode.
Click to expand...
Click to collapse
Are you able to extract the fast boot ROM onto your computer?
This includes :
boot.img
system.img
vendor.img
vbmeta.img
Nameless Foe said:
Are you able to extract the fast boot ROM onto your computer?
This includes :
boot.img
system.img
vendor.img
vbmeta.img
Click to expand...
Click to collapse
I have downloaded firmware of it but that file can not be extracted it was .ozip file
Phantom010 said:
I have downloaded firmware of it but that file can not be extracted it was .ozip file
Click to expand...
Click to collapse
Your gonna have to find a way to convert to a regular zip then extract those 4 .img files out of the zip
Nameless Foe said:
Your gonna have to find a way to convert to a regular zip then extract those 4 .img files out of the zip
Click to expand...
Click to collapse
name of the firmware is RMX1911EX_11_OTA_1610_all_qom4EBEvsckf.ozip it does not extract from pc.
Phantom010 said:
name of the firmware is RMX1911EX_11_OTA_1610_all_qom4EBEvsckf.ozip it does not extract from pc.
Click to expand...
Click to collapse
Ok. So is that the file you downloaded to your pc ?
Nameless Foe said:
Ok. So is that the file you downloaded to your pc ?
Click to expand...
Click to collapse
This is the firmware I have downloaded from official realme site it can't be extracted.
Phantom010 said:
This is the firmware I have downloaded from official realme site it can't be extracted.
Click to expand...
Click to collapse
Try to re-download it. Make sure you completely delete the current one from your pc.
Bare with me. I'm at work now. I won't be able to respond as fast
Nameless Foe said:
Try to re-download it. Make sure you completely delete the current one from your pc.
Bare with me. I'm at work now. I won't be able to respond as fast
Click to expand...
Click to collapse
If you can get those 4 files extracted to your pc, you will need to wipe your phone via fast boot, then flash all 4 of them files separately via fastboot and your phone should go back to normal.
Nameless Foe said:
If you can get those 4 files extracted to your pc, you will need to wipe your phone via fast boot, then flash all 4 of them files separately via fastboot and your phone should go back to normal.
Click to expand...
Click to collapse
ok replay when you are free thanks for giving your time man, one thing wipe mean from pc i have installed twrp also. i am confused about why custom rom does not boot up when i install it from twro it installs successfully after system reboot it goes directly to fastboot mode.
Phantom010 said:
ok replay when you are free thanks for giving your time man, one thing wipe mean from pc i have installed twrp also. i am confused about why custom rom does not boot up when i install it from twro it installs successfully after system reboot it goes directly to fastboot mode.
Click to expand...
Click to collapse
If your phone is bricked, which it seems that it is...
Your gonna have to flash the stock firmware if you want to be able to use the phone again
I'm not sure why the rom won't boot and goes back to fast boot mode we will continue once your able to flash the stock firmware
Phantom010 said:
Someone plz help me I got stuck on fastboot mode while installing custom recovery and ROM
Click to expand...
Click to collapse
Any luck ?
Nameless Foe said:
Any luck ?
Click to expand...
Click to collapse
Nameless Foe said:
Oh **** man I got the same problem from starting to end same
Click to expand...
Click to collapse
Nameless Foe said:
If your phone is bricked, which it seems that it is...
Your gonna have to flash the stock firmware if you want to be able to use the phone again
I'm not sure why the rom won't boot and goes back to fast boot mode we will continue once your able to flash the stock firmware
Click to expand...
Click to collapse
If only I managed to access recovery mode your method would have worked. I tried flashing stock ROM recovery and Orange fox recovery but it always bootloops to fastboot way sooner than I can finish all of my steps. Same case when I tried to erase boot it bootloops faster than the process to be finished.
Can you please suggest me any method to stop bootloops atleast in fastboot mode?
Nameless Foe said:
Any luck
Click to expand...
Click to collapse
Plz help i have realme 7pro and when i starts my phone it goes to fastboot mode and restarts again and again and comes to fastboot mode plz help i am tensed from last 3 days
NickOp said:
Plz help i have realme 7pro and when i starts my phone it goes to fastboot mode and restarts again and again and comes to fastboot mode plz help i am tensed from last 3 days
Click to expand...
Click to collapse
OK ik resetting my pc right now. It's gonna be some time before I can assist you somone else might before me
Nameless Foe said:
OK ik resetting my pc right now. It's gonna be some time before I can assist you somone else might before me
Click to expand...
Click to collapse
now plz help i cannot explain that how much frustrated i am
NickOp said:
now plz help i cannot explain that how much frustrated i am
Click to expand...
Click to collapse
have you done in extracting the *.img in the ofp file?
if yes then go to your cmd and type the command:
1. fastboot erase boot && fastboot erase dtbo && fastboot erase recovery && fastboot erase metadata && fastboot erase vbmeta && fastboot erase system && fastboot erase vendor && fastboot erase userdata && fastboot reboot-bootloader
the command was based from this thread : https://forum.xda-developers.com/t/realme-5-stuck-on-fastboot-mode.4096691/
then after issuing the previous command change the "erase" to "flash":
2. fastboot flash boot boot.img && fastboot flash dtbo dtbo.img &&...... (don't include the metadata group)
i just fixed mine today