Hello, my first post on RN8PRO Section, but I am on this forum since I bought this device five months ago. Rough times!
But now we have some custom ROMs, and I want to test some on this beast. Bootloader already unlocked. Now I have some files here (linux):
- twrp.img (AgentFabulous)
- lk.img
- preload.img
- vendor.img (begonian, 871MB)
What I need to be sure, is the correct order of flashing everything. Do I:
Code:
fastboot flash recovery twrp.img
fastboot flash preloader preloader_begonia.bin
fastboot flash lk lk.img
fastboot flash lk2 lk.img
fastboot flash vendor vendor.img
fastboot reboot
Press volume UP + power until Recovery, then flash ROM???
Is this all? Am I forgetting something?
P.S: SP Flash Tools and Global Stock Android 9 ROM already download, just in case
Thanks in advance
Preloader should be the first just in case and then lk, and to enter to fastboot or recovery vol up + pwr, and then choose one
Related
Hello Everyone,
My Pixel XL is going in bootloop after working for sometime. I have to factory reset it via recovery to get it working again. I am attching log which i got via ADB when it boot up. Can somebody help me with that?
No root no unlocked bootloader.
rkravi85 said:
Hello Everyone,
My Pixel XL is going in bootloop after working for sometime. I have to factory reset it via recovery to get it working again. I am attching log which i got via ADB when it boot up. Can somebody help me with that?
No root no unlocked bootloader.
Click to expand...
Click to collapse
No log
Sorry My Bad @Homeboy76
Have you tried these steps below?
If you have modified a little the stock android (hosts file, root, kernel, etc.), you may experience a fail in OTA update;
If you have a bootloop/soft brick/not sure of the state of your android system;
This WILL NOT delete your data and apps. This will remove your custom kernel/root/hosts/recovery through (which is a good thing because it will be clean then).
1) Download your system image for Marlin (Pixel XL) on google website.
download the latest version
2) Unzip the file marlin-nde63v-factory-______.zip
3) Unzip inside the new directory (marlin-nde63v) the image-marlin-_____.zip
Execute fastboot commands (assuming the bin is on your PATH)
Code:
fastboot reboot-bootloader
fastboot flash radio radio-marlin-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
to add TWRP;
fastboot boot /path/to/twrp.img
then In TWRP, install twrp.zip for permanent twrp. Goodluck!
friends, how are you?
It's the following .. I have a serious problem with my Moto G5.
When he went to do the update for Oreo he gave a problem ... Of which I can not leave.
It starts in fastboot mode or attempts to initialize Android but stops on screen (M) as picture.
The bootloader is locked, I tried to unlock by cmd and put the key sent by the motorola, signaled as if it worked and continues as (oem_locked).
I do not have root, my bootloader is locked, and I can not access recovery despite entering fastboot mode.
I tried installing several roms by adb, but I could not succeed with any (Always giving FAILED REMOTE).
Yesterday until it managed to enter the initial configuration of the android (where it places the wifi) but then restarted and never again.
I've tried everything a little bit, and I could not succeed with anything.
Help me, please, I do not know what else to do!
Thank you
:confuso:
You have a few options
The first is just wipe the phone and see if it boots
You can do this by putting the phone in bootloader mode (as per your screenshot) by holding Vol down & power button
Then in cmd/terminal window where you have fastboot on your pc type
fastboot erase userdata
Note this will delete everything on internal storage!
Then select the boot normally from bootloader menu
Another option is to flash the entire firmware via fastboot
You will need firmware which is the same or newer than what you currently have
You don't need an unlocked bootloader to flash stock firmware via fastboot
Note fastboot is different from adb - adb won't work in fastboot mode!
.....
My friend, I made the process using the rom of https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244 except that excluding the (fastboot flash partition gpt.bin and
fastboot flash bootloader bootloader.img).
Similarly, the screen continues with the motorola logo, does not advance to android, recovery when I select and tighten the power, stay on the motorola screen and back to the fastboot.
The result of the process is this in the image
TheFixItMan said:
You have a few options
The first is just wipe the phone and see if it boots
You can do this by putting the phone in bootloader mode (as per your screenshot) by holding Vol down & power button
Then in cmd/terminal window where you have fastboot on your pc type
fastboot erase userdata
Note this will delete everything on internal storage!
Then select the boot normally from bootloader menu
Another option is to flash the entire firmware via fastboot
You will need firmware which is the same or newer than what you currently have
You don't need an unlocked bootloader to flash stock firmware via fastboot
Note fastboot is different from adb - adb won't work in fastboot mode!
Click to expand...
Click to collapse
sonmota said:
My friend, I made the process using the rom of https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244 except that excluding the (fastboot flash partition gpt.bin and
fastboot flash bootloader bootloader.img).
Similarly, the screen continues with the motorola logo, does not advance to android, recovery when I select and tighten the power, stay on the motorola screen and back to the fastboot.
The result of the process is this in the image
Click to expand...
Click to collapse
You need to flash the ENTIRE stock firmware and it MUST be the same or newer than the version already on the phone
Plus you missed sparsechunk0
You got pre-flash validation errors as you are either using the wrong firmware or haven't flash the entire firmware from start to finish
Note if you flash wrong firmware you could potentially hard brick your device
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
....
I'm from Brazil and from what I've been observing the ROM would be with the same bases as this one from the link.
I refined the process using the command lines you posted and "FAILED REMOTE" is repeated in some lines.
Would not it be some case of partitioning the corrupted system?
Follow the pictures below.
TheFixItMan said:
You need to flash the ENTIRE stock firmware and it MUST be the same or newer than the version already on the phone
Plus you missed sparsechunk0
You got pre-flash validation errors as you are either using the wrong firmware or haven't flash the entire firmware from start to finish
Note if you flash wrong firmware you could potentially hard brick your device
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
sonmota said:
I'm from Brazil and from what I've been observing the ROM would be with the same bases as this one from the link.
I refined the process using the command lines you posted and "FAILED REMOTE" is repeated in some lines.
Would not it be some case of partitioning the corrupted system?
Follow the pictures below.
Click to expand...
Click to collapse
Gpt failed because the firmware you are trying to flash is older than what is currently on your phone
Gpt is needed to repartition your phone and must be flashed along with the bootloader
You will need to download firmware which is equal to or newer than what is already on your phone
I saw there was an October update in the ROM. I will try here in the community this ROM and try to blink and bring the result here ..
friend .. I followed the rom .. I did the whole process (without FAILED) but when it starts up it gets frozen in the Motorola logo.
Any tips on what it might be?
TheFixItMan said:
Gpt failed because the firmware you are trying to flash is older than what is currently on your phone
Gpt is needed to repartition your phone and must be flashed along with the bootloader
You will need to download firmware which is equal to or newer than what is already on your phone
Click to expand...
Click to collapse
sonmota said:
friend .. I followed the rom .. I did the whole process (without FAILED) but when it starts up it gets frozen in the Motorola logo.
Any tips on what it might be?
Click to expand...
Click to collapse
As long as everything flashed correctly and the entire firmware had no errors I'd go into stock recovery and perform a factory reset
Hold Vol down & power button
At bootloader menu use volume keys to navigate to recovery and press power button to select
At the Android screen with no command push and hold power button then with power button held then press Vol up
You are now in recovery mode
Use Vol keys with goto wipe data/factory reset & power button to select
If the rom doesn't boot after that chances are you didn't flash the firmware correctly or there was an error in flashing it due to the wrong firmware used
I can not get into recovery. Would not it be a problem with the motherboard?
TheFixItMan said:
As long as everything flashed correctly and the entire firmware had no errors I'd go into stock recovery and perform a factory reset
Hold Vol down & power button
At bootloader menu use volume keys to navigate to recovery and press power button to select
At the Android screen with no command push and hold power button then with power button held then press Vol up
You are now in recovery mode
Use Vol keys with goto wipe data/factory reset & power button to select
If the rom doesn't boot after that chances are you didn't flash the firmware correctly or there was an error in flashing it due to the wrong firmware used
Click to expand...
Click to collapse
sonmota said:
I can not get into recovery. Would not it be a problem with the motherboard?
Click to expand...
Click to collapse
Could well be
As long as gpt flashed successfully without giving a downgrade warning which will call it to fail then the recovery part of the firmware should flash and you should have access to recovery mode via entering recovery from bootloader then holding power button and volume up at the picture of the android screen
It could be a motherboard issue but since you have no problem getting into bootloader it's more likely a firmware issue/user error
Trying to flash Lineage 17.1 or TWRP on Cubot Quest Lite ends in Orange-State-Bootloop
After flashing Lineage 17.1 i get a Bootloop at orange state.
Restoring original System and generating TWRP with the hovatek tool and flashing only TWRP produced also a bootloop
Tried [Hovatek]_Mediatek_Auto_TWRP_Recovery_Porter_V1.7a_by_Team_Hovatek.7z
Tried also [Hovatek]_Spreadtrum_(SPD)_Auto_TWRP_Recovery_Porter_V1.4_by_Team_Hovatek.7z
Flashing is done from Linux PC with following commands:
1. Try Lineage System without a Rocovery:
fastboot flashing unlock (volume key up for confirmation)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img <-- vbmeta.img from Cubot Stock rom
fastboot flash boot boot.img
fastboot flash system lineage-17.1-20210321-UNOFFICIAL-treble_arm64_avS.img
fastboot reboot
I tried also lineage-17.1-20210321-UNOFFICIAL-treble_a64_avS.img
2. Try Only TWRP Recovery with Stock Rom System unchanged
generate recovery with Hovatek Recovery Porter, then
restore original System with SP-Flash-Tool, then
fastboot flashing unlock (volume key up for confirmation)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash recovery recovery.img
fastboot reboot
Then try to enter Recovery by pressing Volume-UP+Power-Key
I was successfull with a Cubot Kingkong Mini with the same approach. Both phones from cubot have the same CPU, RAM, Camera
Mediatek MT6761 Helio A22, 64bit
Any ideas to get Lineage or TWRP running?
Hi, I have the same phone and find android 9 very painful.....do you think I can install android 6 ?
Hi andro-try, have you solved yet problem reported (TWRP) ?
Hi,
I unlocked my Note 8 Pro, flashing twrp-3.7.0_9-0-begonia.img with Fastboot successfully , but by reboot no twrp-startscreen/menu starts. Instead on loop of Redmi-Logo with unlocked-Symbol for 5 seconds, than reboot. several keykombinations (volume-Up+OnOff-key) does not start twrp... what is wrong? (I tried several older twrp-versions.)
I read https://forum.xda-developers.com/t/guide-info-psa-redmi-note-8-pro-megathread-cfw.4056527 and used follwing commands:
fastboot flash preloader preloader_begonia.bin
fastboot flash lk lk.img
fastboot flash lk2 lk.img
now my phone is absolutely bricked. only blacksreen. fastboot does not start, fastboot-command does not find any device.
edu.mc said:
I read https://forum.xda-developers.com/t/guide-info-psa-redmi-note-8-pro-megathread-cfw.4056527 and used follwing commands:
fastboot flash preloader preloader_begonia.bin
fastboot flash lk lk.img
fastboot flash lk2 lk.img
now my phone is absolutely bricked. only blacksreen. fastboot does not start, fastboot-command does not find any device.
Click to expand...
Click to collapse
It brick because you did something stupid. Follow this to recover your phone:
edu.mc said:
Hi,
I unlocked my Note 8 Pro, flashing twrp-3.7.0_9-0-begonia.img with Fastboot successfully , but by reboot no twrp-startscreen/menu starts. Instead on loop of Redmi-Logo with unlocked-Symbol for 5 seconds, than reboot. several keykombinations (volume-Up+OnOff-key) does not start twrp... what is wrong? (I tried several older twrp-versions.)
Click to expand...
Click to collapse
And _9 is Android 9. So you need to downgrade to Miui Android 9 to use that "Official" one. Or use unofficial twrp for Miui 12.0.x or Miui 12.5.x
-
!!!!!!!!!!!!!!!!!!!!!!!!!WE ARE NOT RESPONSIBLE FOR ANYTHING THAT MIGHT HAPPEN TO YOUR DEVICE TRYING TO INSTALL THIS ROM!!!!!!!!!!!!!!!!!!!!!!
This ROM has been tested for about a week on two capri devices one from India and other from South America
Loads of thanks to @Electimon for his trees and all his help fixing issues we faced in bringing this ROM
Kernel Source: https://github.com/moto-common/android_kernel_motorola_msm-4.19
Manifest: https://github.com/moto-common/local_manifests
Not working:
FM Radio
Dual Sim (Will look into this soon) - Looked into it. This is being flaky once enabled. Will need more time to fix this.
5Ghz Wifi - not stable, keeps disconnecting, use 2.4Ghz
Telegram group: https://t.me/motobengalchat
Flashing instructions:
Code:
Make sure you are on latest of your stock Android 11, Booted and the rom is working.
Download zip and extract it and run the following commands
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot -w
fastboot reboot fastboot
fastboot flash system system.img
# In case the above command fails saying parititon size is not enough then try to resize it with below command
fastboot resize-logical-partition system_a 1073741824 #(run this only if the above command fails and if you are on slot_a else change it to system_b)
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
To flash gapps, follow instructions below
Flashing gapps:
On the phone screen you should be seeing a menu, press volume down to goto Enter recovery and press power button to choose it
Here you will see a different menu, press power down to navigate to apply update and press power button to choose it and press power button again to choose Apply from ADB
Now on the command line enter below command
Code:
adb sideload MindTheGapps-13.0.0-arm64-20230408_162909.zip
In case you have missed flashing gapps and booted into ROM, make sure you reset device in recovery before flashing gapps
...