Develop Bugs

[Q] Bricked my nexus - Fastboot still almost working

I Think my device is lost. It´s locked in boot of my Gummynex rom.
I´m not allowed to flash anything else, it´s like my filesystem is broken.
I have attached som screenshots of the error´s i get in galaxy nexus toolkit 5.6
{
"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 Have also tryed with Odin, but i cant seem to get odin to connect with the phone in fastboot.
If i try to go into recoverymode i get the android man lying on his back with and Red triangle inside.
Hope someone have any idea of what i should try next.

on the phone itself, can you get to bootloader?

Tomcat27 said:
I Think my device is lost. It´s locked in boot of my Gummynex rom.
I´m not allowed to flash anything else, it´s like my filesystem is broken.
I have attached som screenshots of the error´s i get in galaxy nexus toolkit 5.6
I Have also tryed with Odin, but i cant seem to get odin to connect with the phone in fastboot.
If i try to go into recoverymode i get the android man lying on his back with and Red triangle inside.
Hope someone have any idea of what i should try next.
Click to expand...
Click to collapse
Try using fastboot commands to flash the stock img files instead of the toolkit.

jhernand1102 said:
Try using fastboot commands to flash the stock img files instead of the toolkit.
Click to expand...
Click to collapse
But when i download the files from Google´s homepage there is only 1 file.
Shouldn´t it be enough ?
It´s the yakju-imm76d-factory-c6e807a1.tar file for my phone.

Tomcat27 said:
But when i download the files from Google´s homepage there is only 1 file.
Shouldn´t it be enough ?
It´s the yakju-imm76d-factory-c6e807a1.tar file for my phone.
Click to expand...
Click to collapse
extract the files.

But when i extract the files with winrar, i still only get 1 file ?

Tomcat27 said:
But when i extract the files with winrar, i still only get 1 file ?
Click to expand...
Click to collapse
Extract it again.
Sent from my Galaxy Nexus using xda premium

I´ve extracted the files again. now i have 6 img files.
boot
bootloader
radio
recovery
system
userdata
Flashed all the files to the phone, each time i get an error like before, but i can see in the fast boot screen that baseband versions ect. changes.
But unfortunatly the phone still won´t boot.
I have locked it again, and will take it to the store for repair if someone don´t have some good ideas
Thank you in advance

unlock the bootloader ( fastboot oem unlock )
5) Open up Command Prompt or Terminal, navigate to the folder you've extracted it all too and enter the following commands waiting for each to finish
Windows
fastboot-windows flash bootloader bootloader-maguro-primekk15.img
fastboot-windows reboot-bootloader
fastboot-windows flash radio radio-maguro-i9250xxkk6.img
fastboot-windows reboot-bootloader
fastboot-windows -w update image-yakju-icl53f.zip
Linux
./fastboot-linux flash bootloader bootloader-maguro-primekk15.img
./fastboot-linux reboot-bootloader
./fastboot-linux flash radio radio-maguro-i9250xxkk6.img
./fastboot-linux reboot-bootloader
./fastboot-linux -w update image-yakju-icl53f.zip
OSX
./fastboot-mac flash bootloader bootloader-maguro-primekk15.img
./fastboot-mac reboot-bootloader
./fastboot-mac flash radio radio-maguro-i9250xxkk6.img
./fastboot-mac reboot-bootloader
./fastboot-mac -w update image-yakju-icl53f.zip
6) The last step is to lock the bootloader. Restart the phone into the bootloader
7) Open CMD in the location of Superboot and type:
fastboot-windows oem lock

Help Needed
Guys,
I need any help possible although I fear I may be beyond recovery. Basically my Galaxy Nexus is bricked, I had been running 4.0.4 (IMM76D) on it. The phone is rooted and unlocked.
When switching the phone on, all I get is Google and the unlocked keypad. Will not progress further. I can boot into fastboot mode, and sometimes into recovery however although I have files showing on the SD, when I choose them I get a message declaring the path empty.
My main issue is that the handset is not recognised by my computer (running windows 7 and also since yesterday a dual boot of Ubuntu). This results in my Nexus toolkit and the AdamOutler tool being of no use as they do not recognize the device.
Any help/advice will be greatly appreciated as I'm at my wits end

[Q] screen non-resposive after rom install

Please help me.. I just unlocked and installed a custom rom on my phone but after the installation the screen has been unresposive..
I tried to reinstall the rom since i forgot to flash the boot image on the first try but still the can't use the screen..

A little more info would be helpful... Which rom? which kernel? What is your hboot?
also post the result of fastboot getvar version-main

vin4yak said:
A little more info would be helpful... Which rom? which kernel? What is your hboot?
also post the result of fastboot getvar version-main
Click to expand...
Click to collapse
I first installed the nocturnal xi40 rom but forgot to flash the boot image and kernel.. awhile ago i tried to install the bindroid xtc rom + kernel but still nothing changed. My phone just boots up to home screen which is still unresposive and at times my music player automatically plays. :crying:

mikenirochiell said:
I first installed the nocturnal xi40 rom but forgot to flash the boot image and kernel.. awhile ago i tried to install the bindroid xtc rom + kernel but still nothing changed. My phone just boots up to home screen which is still unresposive and at times my music player automatically plays. :crying:
Click to expand...
Click to collapse
Don't get tense, this can be sorted out easily m8 if there's not hardware issue here...
Post the result of the following:
Code:
fastboot getvar version-main
fastboot oem readcid

vin4yak said:
Don't get tense, this can be sorted out easily m8 if there's not hardware issue here...
Post the result of the following:
Code:
fastboot getvar version-main
fastboot oem readcid
Click to expand...
Click to collapse
How can I do this?

mikenirochiell said:
How can I do this?
Click to expand...
Click to collapse
Can you pls guide me to this? I dont know how to use the code.

mikenirochiell said:
Can you pls guide me to this? I dont know how to use the code.
Click to expand...
Click to collapse
Use Fastboot.
Link:
http://www.mediafire.com/download/q2540u4g3v6qqd7/Fastboot.zip
Instructions:
1. Put the phone in bootloader (turn your phone off, and hold power + vol. down) then enter fastboot, and make sure it shows:" FASTBOOT USB "
2. Open a terminal windows, change the current location to the fastboot files, for an example: C:/Fastboot. So you need to type cd C:/fastboot (see image below)
3. Run the fastboot commands :good:
{
"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 did the codes followed the image you posted.. What's next?

wich recovery are you useing,,,also wich radio are you on

mikenirochiell said:
I did the codes followed the image you posted.. What's next?
Click to expand...
Click to collapse
I rebooted my phone but still no changes..still unresposive screen..

after you unlocked your bootloader wich recovery did you flash

hellothere74 said:
wich recovery are you useing,,,also wich radio are you on
Click to expand...
Click to collapse
cwm recovery v6.0.2.7
How can I know which radio I'm on??
Still nothing after reboot..

use the link wich fietspompje just given to you and follow what he has sed it will tell you on the black screen

hellothere74 said:
wich recovery are you useing,,,also wich radio are you on
Click to expand...
Click to collapse
I rebooted my phone but still no changes..still unresposive screen..

mikenirochiell said:
I rebooted my phone but still no changes..still unresposive screen..
Click to expand...
Click to collapse
i need to no what it says on the black screen

hellothere74 said:
i need to no what it says on the black screen
Click to expand...
Click to collapse
its the same as the image you posted..
I don't know what's next after that so iI rebooted.

mikenirochiell said:
its the same as the image you posted..
I don't know what's next after that so iI rebooted.
Click to expand...
Click to collapse
We want your device's version-main and cid!! Please copy paste all the text you can see from your cmd window over here! or we won't be able to help you...

vin4yak said:
We want your device's version-main and cid!! Please copy paste all the text you can see from your cmd window over here! or we won't be able to help you...
Click to expand...
Click to collapse
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\MykRo>cd C:/Fastboot
C:\Fastboot>fastboot getvar version-main
version-main: 3.19.709.2
finished. total time: -0.000s
C:\Fastboot>fastboot oem readcid
... INFODEBUG: cid: HTC__621
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Fastboot>

download this and flash it http://d-h.st/CNx
1 go to fastboot flash that recovery,,
2 reflash boot img
3 reflash rom

mikenirochiell said:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\MykRo>cd C:/Fastboot
C:\Fastboot>fastboot getvar version-main
version-main: 3.19.709.2
finished. total time: -0.000s
C:\Fastboot>fastboot oem readcid
... INFODEBUG: cid: HTC__621
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Fastboot>
Click to expand...
Click to collapse
Arrrghh! Taiwan device?!
There's no nandroid which matches your version-main, you can try to restore this backup : http://d-h.st/K7O
if you have officially received the JB update, it should work...
If you want to flash a custom rom, ICS roms won't work on your device because of the updated touch driver... Go to android development / original android development section and choose a JB rom!
also use this recovery, it is the only recovery which has a fully touch interface and works flawlessly: https://www.dropbox.com/s/p35p0tqf41jbj8b/recovery.img

Htc m9 corruted bootloader blue screen,Please HELP

When I enter in RUU mode (download mode) blue screen comes.
Before this I locked my bootloader to flash ota firmware,but it stuck on htc screen, then I relocked my bootloader but it gives me error.
Please help what to do?

are you soff?

blue screen error
plz some one help..
htc m9 asia tw
s-on
firmware update to 5.1 sudden mobile reset and now when it on after gives blue blank screen just....
just bootloader screen come while pressing vol + and vol - and power button. bt no recovery no download mode no RUU mode while going to download mode blue screen error plz someone help. what to do.

You can flash the stock files in the bootloader screen. Fastboot commands work. Just extract the ruu and flash the partitions individually.

philicibine said:
You can flash the stock files in the bootloader screen. Fastboot commands work. Just extract the ruu and flash the partitions individually.
Click to expand...
Click to collapse
fastboot command in bootloader screen gives error FAILED (remote: cannot flash this partition in s-on state)
please someone help to solve this problem.
{
"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"
}
This screen comes every time and reset htc logo and then same blue screen

Maybe try fastboot boot recovery.img and see if that works??

philicibine said:
Maybe try fastboot boot recovery.img and see if that works??
Click to expand...
Click to collapse
FAILED (remote: Not allow when s-on)

mnhs1010 said:
When I enter in RUU mode (download mode) blue screen comes.
Before this I locked my bootloader to flash ota firmware,but it stuck on htc screen, then I relocked my bootloader but it gives me error.
Please help what to do?
Click to expand...
Click to collapse
Is your error solved or are you still stuck with the blue screen as I am also the effected

LineArc said:
Is your error solved or are you still stuck with the blue screen as I am also the effected
Click to expand...
Click to collapse
Still same problem dear blue screen...

mnhs1010 said:
Still same problem dear blue screen...
Click to expand...
Click to collapse
Maybe u should take a look here their potential is to recover ur device with some fund ....better than going to HTC and screwing up alot of money

sa3d12 said:
Maybe u should take a look here their potential is to recover ur device with some fund ....better than going to HTC and screwing up alot of money
Click to expand...
Click to collapse
did your problem solved >>>>>

mnhs1010 said:
did your problem solved >>>>>
Click to expand...
Click to collapse
U mean you solved your problem or you are asking me? ..
Anyway i dont have problems with my device

hello my English is bad but i have solved this problem.
you need Minimal ADB and Fastboot
you need Firmware of your phone. (try with 3.35)
unzip your firmware zip in the minimal ADB and fastboot folder
open fastboot cmd
start your smartphone in bootloader
copy all files .img with fastboot
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash adsp adsp.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sdi sdi.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
fastboot reboot
Click to expand...
Click to collapse
done your blue screen is off and all acces to your download mode, Ruu.
need to reinstall recovery, and firmware again

I think you only need to flash the hosd

VashSV said:
hello my English is bad but i have solved this problem.
you need Minimal ADB and Fastboot
you need Firmware of your phone. (try with 3.35)
unzip your firmware zip in the minimal ADB and fastboot folder
open fastboot cmd
start your smartphone in bootloader
copy all files .img with fastboot
done your blue screen is off and all acces to your download mode, Ruu.
need to reinstall recovery, and firmware again
Click to expand...
Click to collapse
Thanks a lot! You have been avoided a heart attack hehe!

You my friend are a star... I thought my HTC M9 was a brick for sure.
Just to add people, remember do not try and copy through ADB installer (As I did to begin with)... It will not detect your phone... Use the Fastboot application within CMD.
VashSV said:
hello my English is bad but i have solved this problem.
you need Minimal ADB and Fastboot
you need Firmware of your phone. (try with 3.35)
unzip your firmware zip in the minimal ADB and fastboot folder
open fastboot cmd
start your smartphone in bootloader
copy all files .img with fastboot
done your blue screen is off and all acces to your download mode, Ruu.
need to reinstall recovery, and firmware again
Click to expand...
Click to collapse

VashSV said:
hello my English is bad but i have solved this problem.
you need Minimal ADB and Fastboot
you need Firmware of your phone. (try with 3.35)
unzip your firmware zip in the minimal ADB and fastboot folder
open fastboot cmd
start your smartphone in bootloader
copy all files .img with fastboot
done your blue screen is off and all acces to your download mode, Ruu.
need to reinstall recovery, and firmware again
Click to expand...
Click to collapse
does anyone have for m9 verizon ?

@VashSV, I already pressed thanks button but want to write and say thanks to you. You save my phone. Happy new year 2017

Many many many thanks to you!!! I what in this blue screen loop, thanks to your commande list I managed to write .img by .img, you are the boss.

Exact same problem
philicibine said:
You can flash the stock files in the bootloader screen. Fastboot commands work. Just extract the ruu and flash the partitions individually.
Click to expand...
Click to collapse
Hello, a bit late but I have the exact same problem with my HTC one M9, can you please help me? I am s-off, unlocked and my phone is T-MOB010 with N7 corrupted firmware :/ pleaseeee

the system has been destroyed

Plz help me what can i do? i dont flash properly my system has been destroyed. i did evething for solved this problem . now i have no option to solve this problem . now what can i do? any one Help me?
i am attached some photos
my image file : ginkgo_in_global_images_V11.0.3.0.PCOINXM
{
"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"
}
_20200214.0000.00_9.0_in_8e42c719e

Flash vbmeta file or try to move files to root directory.

shovan.cc said:
Plz help me what can i do? i dont flash properly my system has been destroyed. i did evething for solved this problem . now i have no option to solve this problem . now what can i do? any one Help me?
i am attached some photos
my image file : ginkgo_in_global_images_V11.0.3.0.PCOINXM
_20200214.0000.00_9.0_in_8e42c719e
Click to expand...
Click to collapse
in fastboot rom there must be a file vbmeta.img....
download latest platform tools first.
extract the plaform tools zip...copy vbmeta.img in this folder,open cmd in this folder path and flash vbmeta with phone in fastboot mode by this command
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after this flash recovery.

if you solve the problem, here the vbmeta: https://mega.nz/#!bUwliDDS!PNCWo68avE9GsyK4JeJgV1zoVIiejh0-gIs1X6MCEPk

Mi Flash should be able to restore your phone to 100% stock, including boot and vbmeta - it could be that the directory is too long. Try placing the fastboot file in your root folder (C:/) and direct Mi Flash Tool towards that.
System has been destroyed should only really show up when you try flashing a ROM without a dummy vbmeta.img

Thx.
CommieColin said:
Mi Flash should be able to restore your phone to 100% stock, including boot and vbmeta - it could be that the directory is too long. Try placing the fastboot file in your root folder (C:/) and direct Mi Flash Tool towards that.
System has been destroyed should only really show up when you try flashing a ROM without a dummy vbmeta.img
Click to expand...
Click to collapse
Thanks For Your Suggestion.. & i Am done This flash Properly.

thank you
the_weird_aquarian said:
in fastboot rom there must be a file vbmeta.img....
download latest platform tools first.
extract the plaform tools zip...copy vbmeta.img in this folder,open cmd in this folder path and flash vbmeta with phone in fastboot mode by this command
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after this flash recovery.
Click to expand...
Click to collapse
thank you you saved me

the_weird_aquarian said:
in fastboot rom there must be a file vbmeta.img....
download latest platform tools first.
extract the plaform tools zip...copy vbmeta.img in this folder,open cmd in this folder path and flash vbmeta with phone in fastboot mode by this command
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after this flash recovery.
Click to expand...
Click to collapse
I am trying my best to perform this action and i cant

Janelas said:
I am trying my best to perform this action and i cant
Click to expand...
Click to collapse
All commands worked but stil stuck on fastboot

Janelas said:
All commands worked but stil stuck on fastboot
Click to expand...
Click to collapse
sorry for the late reply...after vbmeta is successful, did you flash recovery.img?? if after flashing recovery it doesn't enter recovery mode, press vol up + power button then check.

How To Guide RMX3363 : unlock bootloader + root + install LOS recovery & custom ROM

Because really, a Realme GT ME is a killer with an AOSP ROM...
- - - - - - - - WARRANTY VOID IF YOU DO THAT - - - - - - - -​
(Use original charger cable to connect phone to PC)
Download : ADB/fastboot, Deep Test apk, Magisk apk/zip 25.2, LOS (Lineage OS) recovery, custom ROM zip and GAPPS zip (if needed by your custom ROM)
Update phone by OTA for Android 12 RUI3 Export (french network for me)
Check options in developer menu (USB debugging/OEM unlock)
Install and launch the Deep Test apk
Restart phone into fastboot mode (power + volume down)
Type CMD on PC : fastboot devices (phone must be detected)
Type CMD : fastboot flashing unlock
Unlock bootloader on phone
Restart phone
Download firmware RMX3363export_11_C.08_2022062322020000.ofp
Extract boot.img, vendor_boot.img, vbmeta.img and vbmeta_vendor.img with ofp_qc_decrypt.py (Github Python3 script)
Install and launch Magisk apk
Copy extracted boot.img and vendor_boot.img on phone
Patch files with Magisk
Copy patched files on PC
Restart phone into fastboot mode
Choose "Recovery mode" and wipe data
Restart phone into fastboot mode
Type CMD on PC : fastboot devices (phone must be detected)
Type CMD : fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Type CMD : fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
Type CMD : fastboot --set-slot=all flash boot patched-boot.img
Type CMD : fastboot --set-slot=all flash vendor_boot patched-vendor_boot.img
Restart phone (rooted)
Restart phone into fastboot mode
Type CMD on PC : fastboot devices (phone must be detected)
Type CMD : fastboot --set-slot=all flash boot LOS-recovery_boot.img
Type CMD : fastboot --set-slot=all flash vendor_boot LOS-recovery_vendor_boot.img
Type CMD : fastboot reboot recovery
Format DATA (factory reset) into LOS recovery
Launch ADB sideload into LOS recovery (and note active slot)
Type CMD on PC : adb devices (phone must be detected)
Type CMD : adb sideload <custom ROM>.zip
Relaunch ADB sideload into LOS recovery
Type CMD : adb sideload <GAPPS>.zip
Restart phone into fastboot mode
Type CMD on PC : fastboot devices (phone must be detected)
Type CMD : fastboot --set-active=<x> (a or b, depend of active slot at step 31)
Type CMD : fastboot reboot recovery
Launch ADB sideload into LOS recovery
Type CMD on PC : adb devices (phone must be detected)
Type CMD : adb sideload <custom ROM>.zip
Relaunch ADB sideload into LOS recovery
Type CMD : adb sideload <GAPPS>.zip
Restart phone
Welcome to your custom ROM !
(Perhaps you'll have, like me, to apply Magisk.zip in recovery mode to be definitively rooted)

After tested official ElixirOS and unofficial LineageOS, I prefer the second. So for me :
- lineageos-19.1-20220823-unofficial
- NikGapps-full-arm64-12-20220904-signed
- AGC8.4.300_V9.2_fix2
{
"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"
}
Animated notification's background (with LSPosed module) :

Where can I get a supported Depth Test app? Because I have tried all the depth test apps but they don't work..

Bungaza said:
Where can I get a supported Depth Test app? Because I have tried all the depth test apps but they don't work..
Click to expand...
Click to collapse
I'm sorry. This one works for mine :
https://androidfilehost.com/?fid=14655340768118457493

Hello,
Thanks for your simple guide, it worked for me!

enonaw said:
I'm sorry. This one works for mine :
https://androidfilehost.com/?fid=14655340768118457493
Click to expand...
Click to collapse
Not work

Bungaza said:
Not work
Click to expand...
Click to collapse
Do you have C08 export firmware ?

enonaw said:
Do you have C08 export firmware ?
Click to expand...
Click to collapse
I don't have

Amazing guide!

Bungaza said:
I don't have
Click to expand...
Click to collapse
Ok, so I'm sorry, I can't help you because this guide is for C08_Export...

enonaw said:
Ok, so I'm sorry, I can't help you because this guide is for C08_Export...
Click to expand...
Click to collapse
You're talking about C08 Export while my device doesn't support deep test apk. Unless you're talking about how to get into fastboot mode. I was able to get the export C08 firmware through a google search.

You should add in the guide the fact that if you are going to use Magisk on the custom rom you need to patch the boot.img and the vendor_boot.img of the specific rom extracted using payload-dumper-go tool

Bungaza said:
You're talking about C08 Export while my device doesn't support deep test apk. Unless you're talking about how to get into fastboot mode. I was able to get the export C08 firmware through a google search.
Click to expand...
Click to collapse
Hmmm... Ok. But this guide is for C08_export OTA updated smartphone (step 2). So, if you can't do step 2 before the step 4 (deep test), I can't help you.

leoufort said:
You should add in the guide the fact that if you are going to use Magisk on the custom rom you need to patch the boot.img and the vendor_boot.img of the specific rom extracted using payload-dumper-go tool
Click to expand...
Click to collapse
No. Look at "(Perhaps you'll have, like me, to apply Magisk.zip in recovery mode to be definitively rooted)" after the last step. I only did this to be able to use Magisk on custom ROM.

hi enonaw
i download RMX3363export_11_C.08_2022062322020000.ofp but unable to extract ofp file.
can u share here boot.img, vendor_boot.img, vbmeta.img and vbmeta_vendor.img from your pc.
Thnks in advance

ATuthura said:
hi enonaw
i download RMX3363export_11_C.08_2022062322020000.ofp but unable to extract ofp file.
can u share here boot.img, vendor_boot.img, vbmeta.img and vbmeta_vendor.img from your pc.
Thnks in advance
Click to expand...
Click to collapse
Hi, It's not a good idea to share stock img, because files can be altered when upload/download. Why are you unable to extract ofp file ? Did you use ofp_qc_decrypt.py (it works on both linux and windows) ?
ofp_qc_decrypt.py

enonaw said:
Hi, It's not a good idea to share stock img, because files can be altered when upload/download. Why are you unable to extract ofp file ? Did you use ofp_qc_decrypt.py (it works on both linux and windows) ?
ofp_qc_decrypt.py
Click to expand...
Click to collapse
i already tried, i cant. can u help me remotely via team viewer

ATuthura said:
i already tried, i cant. can u help me remotely via team viewer
Click to expand...
Click to collapse
See attached files, that's an archive of patched files by Magisk (password : rmx3363).
But verify the hash of your download before apply
And don't forget that I'm not responsible for what you do.

i am unbale toextract file

dear sir, just try
i face this issue
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
392a6bdd fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot --disable-verity --disa
ble-verification flash vbmeta vbmeta.img
target reported max download size of 805306368 bytes
sending 'vbmeta' (8 KB)...
OKAY [ 0.002s]
writing 'vbmeta'...
OKAY [ 0.009s]
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot --disable-verity --disa
ble-verification flash vbmeta_vendor vbmeta_vendor.img
target reported max download size of 805306368 bytes
sending 'vbmeta_vendor' (4 KB)...
OKAY [ 0.002s]
writing 'vbmeta_vendor'...
OKAY [ 0.009s]
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot --set-slot=all flash bo
ot patched-boot.img
fastboot: unknown option -- set-slot=all
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot --set-slot=all flash ve
ndor_boot patched-vendor_boot.img
fastboot: unknown option -- set-slot=all
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse