Database Develop

Flashed my boot loader, but cant finish up and root

So i looked at a bunch of threads but nothing was working out for me so i made a account. I have a ATT M7 running 4.4.2 and sense 6. I unlocked the boatloader, and i type in the commands to start the root process but it does nothing. At first it said cannot load, and somebody on here said that just means you've spelled it wrong. So then i noticed i had 2 different twrp files on my desktop. Deleted the old one and kept the newest one, after that, when i typed in the command, something else came up that i hadn't seen before
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, and if found,
recovery, tos
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
Click to expand...
Click to collapse
I have no idea what this means. My phones wiped bc of the boot loader but i have a back up, but i didn't want to wipe my phone for no reason.
If anybody has anything to contribute that'd be great. Im on mac os x 10.9 btw. Tried to root with PC also but it didn't work bc i didn't have drivers, installed some drivers but that didn't work either so i just gave up and went back to mac.
I did manually move the supersu file to the phone with the pc though

fastboot flash recovery twrp.img
Rename TWRP file to twrp.img put in pc adb folder

yatindroid said:
fastboot flash recovery twrp.img
Rename TWRP file to twrp.img put in pc adb folder
Click to expand...
Click to collapse
What do you mean put it in ADB folder? Thanks for the response though!!
I renamed it but I'm getting this "cannot load" message again. I read on here that all that means is that i spelled it wrong

stealth01 said:
What do you mean put it in ADB folder? Thanks for the response though!!
I renamed it but I'm getting this "cannot load" message again. I read on here that all that means is that i spelled it wrong
Click to expand...
Click to collapse
your recovery image must be in the same folder where you have adb.exe and fastboot.exe on your PC, otherwise, fastboot will not find the recovery image.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader

alray said:
your recovery image must be in the same folder where you have adb.exe and fastboot.exe on your PC, otherwise, fastboot will not find the recovery image.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Mac osx ?

yatindroid said:
Mac osx ?
Click to expand...
Click to collapse
you are right, my bad. same principle apply. recovery image must be in the same folder you have adb and fastboot (not adb.exe) and you may have to use ./ before each command
Code:
./fastboot flash recovery name_of_recovery.img
./fastboot erase cache
./fastboot reboot-bootloader

alray said:
you are right, my bad. same principle apply. recovery image must be in the same folder you have adb and fastboot (not adb.exe) and you may have to use ./ before each command
Code:
./fastboot flash recovery name_of_recovery.img
./fastboot erase cache
./fastboot reboot-bootloader
Click to expand...
Click to collapse
Yeah that helped a bit bc i had like 3 twrp image files, i have one now and its still telling me it cannot load.
so frustrating! I messed up though because when i was first rooting it i was following like 2 guides, should've followed one. Its not bricked right?

stealth01 said:
Yeah that helped a bit bc i had like 3 twrp image files, i have one now and its still telling me it cannot load.
so frustrating! I messed up though because when i was first rooting it i was following like 2 guides, should've followed one. Its not bricked right?
Click to expand...
Click to collapse
what recovery image are you using and please post the output of "fastboot getvar all" (not the imei and sn)

alray said:
what recovery image are you using and please post the output of "fastboot getvar all" (not the imei and sn)
Click to expand...
Click to collapse
the latest TWRP
openrecovery-twrp-2.7.1.1-m7.img
Click to expand...
Click to collapse
The guide i watched told me to go the twrp site and find the latest one and use that. My phone was on 4.4 and sense 6 before i unlocked the boot loader.
and how do i get that to show? Do i select something on my phone?

nvm got what you were talking about
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4274mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse

stealth01 said:
nvm got what you were talking about
Click to expand...
Click to collapse
I recommend you not use the latest twrp but to use ther version 2.6.3.3.
Now the screen you got (from your first post) is the help menu. It appear each time you enter an invalid command fastboot command.
so again make sure your recovery image (twrp 2.6.3.3) is in the same folder you have adb and fastboot on your mac.
with your phone in bootloader mode enter the following command:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
you might have to add ./ before each command (depending how you have install your fastboot/adb on your mac)
now if it fail again, please post a screenshot of your terminal window and post a screenshot of your adb/fastboot folder.

alray said:
I recommend you not use the latest twrp but to use ther version 2.6.3.3.
Now the screen you got (from your first post) is the help menu. It appear each time you enter an invalid command fastboot command.
so again make sure your recovery image (twrp 2.6.3.3) is in the same folder you have adb and fastboot on your mac.
with your phone in bootloader mode enter the following command:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
you might have to add ./ before each command (depending how you have install your fastboot/adb on your mac)
now if it fail again, please post a screenshot of your terminal window and post a screenshot of your adb/fastboot folder.
Click to expand...
Click to collapse
getting the same cannot load message. I even tried the older 2.6.3.2 version too
error: cannot load 'openrecovery-twrp-2.6.3.2-m7.img
Click to expand...
Click to collapse
error: cannot load 'openrecovery-twrp-2.6.3.3-m7.img
Click to expand...
Click to collapse

stealth01 said:
getting the same cannot load message. I even tried the older 2.6.3.2 version too
Click to expand...
Click to collapse
post the screenshot so we can see what you are doing wrong

{
"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"
}

alray said:
post the screenshot so we can see what you are doing wrong
Click to expand...
Click to collapse
my bad i was uploading them

i had like 3 android folders, but this is one that worked and would recognize the commands because this is the folder that installed my mac adb drivers. I downloaded like two other ones from tutorials but trashed them.

i also tried the ./ method, getting the same result

if anybody helps me out and it works I'll seriously donate $20. This has caused me a incredible amount of frustration and needs to get done

stealth01 said:
i had like 3 android folders, but this is one that worked and would recognize the commands because this is the folder that installed my mac adb drivers. I downloaded like two other ones from tutorials but trashed them.
Click to expand...
Click to collapse
have you changed directory (cd) in the terminal to the correct path where you have adb and fastboot? I see your adb, fastboot and recovery are in a folder named "android". you have censored a part of the terminal windows (probably the user name, so your name) so i can not see if your terminal is pointing the correct folder in your case "android". if this folder is on your dekstop then
Code:
cd Desktop/android [COLOR="Red"]or[/COLOR] cd /Users/<yourusername>/Desktop/android
fastboot flash recovery name_of_recovery
fastboot erase cache
fastboot reboot-bootloader
"can not load" error is because fastboot can't find the file
cause 1: file name miss-typed --->not your case
cause 2: file doesn't exist --->not your case
cause 3: not working from the correct path ---> might be your issue
cause 4: double file extension (more common on windows) i.e recovery.img.img (the second .img is hiden by the OS) --> might also be your issue, im not very familiar with mac so i dont know if the OS hide file extension for known file type like on windows
edit: looks like it also possible on a mac to have double file extension:
For one file
Select a file and choose File > Get Info or press Command (⌘)–I.
Click the triangle next to Name & Extension to expand the section and see the filename extension for the file.
To show or hide the filename extension, select or deselect “Hide extension.”
For all files
Choose Finder > Preferences, and then click Advanced.
Select or deselect “Show all filename extensions.”
Some filename extensions can’t be hidden. For example, images imported from a digital camera may continue to show the .jpg extension even after you deselect “Show all filename extensions.”
Click to expand...
Click to collapse

alray said:
have you changed directory (cd) in the terminal to the correct path where you have adb and fastboot? I see your adb, fastboot and recovery are in a folder named "android". you have censored a part of the terminal windows (probably the user name, so your name) so i can not see if your terminal is pointing the correct folder in your case "android". if this folder is on your dekstop then
Code:
cd Desktop/android [COLOR="Red"]or[/COLOR] cd /Users/<yourusername>/Desktop/android
fastboot flash recovery name_of_recovery
fastboot erase cache
fastboot reboot-bootloader
"can not load" error is because fastboot can't find the file
cause 1: file name miss-typed --->not your case
cause 2: file doesn't exist --->not your case
cause 3: not working from the correct path ---> might be your issue
cause 4: double file extension (more common on windows) i.e recovery.img.img (the second .img is hiden by the OS) --> might also be your issue, im not very familiar with mac so i dont know if the OS hide file extension for known file type like on windows
Click to expand...
Click to collapse
DUDE YOU FREAKING DID!!! I'm so happy finally!!
You'll be getting that $20 soon bro thank you so much!!!!

[ROM][11.0][OFFICIAL] crDroid v7.10 [Phoenix]

{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
Ask to get your bootloader unlocked first! - t.me/NokiaX7
First time installation:
First Time Install / Clean Flash
(All your data including the one in internal storage will be removed, so proceed with a caution! Or a backup )
MAKE SURE TO BE ON THE LATEST FIRMWARE/UPDATE BEFORE FLASHING
Also download vbmeta.img
Use the following command in fastboot to boot TWRP-
Code:
fastboot erase system
fastboot erase userdata
fastboot erase vendor
fastboot erase boot
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash boot twrp.img
*Now hold down the Vol+ button and Power button* while at the same time you enter this command-
fastboot reboot
*When the phone vibrates or androidone screen comes for 1-2 sec, leave the buttons*
After phone boots to TWRP, enter the password if encrypted.
Transfer boot.img to phone and flash it to both slots
Flash Magisk(optional)
Format Data
Reboot
Sources:
ROM: https://github.com/crdroidandroid
Kernel: Prebuilt
Download:
ROM Download
None, you tell
Visit official website @ crDroid.net
Nokia 8.1/X7 Community Telegram
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs

Changelog-
===== 17.08.2021 =====
- initial build
===== 30.08.2021 =====
- Official
- Notch cut-out fixed
- Added Google Camera by default(gapps required to open else, snap is present too)
- Fixed battery drain
- Modified tree for more stability
- Added fingerprint gestures

The FM Radio app is missing, can you include it in the next build?

Another request: the system/vendor/boot images are packed as a single file (payload.bin) in the zip, so I have to unpack them manually before fastboot flash. Can you just pack them as individual files in the zip?

leaxy86 said:
Another request: the system/vendor/boot images are packed as a single file (payload.bin) in the zip, so I have to unpack them manually before fastboot flash. Can you just pack them as individual files in the zip?
Click to expand...
Click to collapse
Great point, It would be great if @DS1884 can share system, boot & vendor separately instead of payload.bin as this needs payload dumper tool to extract rom which doesn't seems to be working most of the time in my case sometime only vendor & boot get extracted and vice versa.

C:\Users\rampu\Desktop\Nokia PNX\ADB-FIH>fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
-timeout <time> specify timeout. default time: 30s
im stuck at this part when i copy in paste. kep in mind vbmeta is in the dir of fastboot. any advice would be cool.

hashroot said:
Great point, It would be great if @DS1884 can share system, boot & vendor separately instead of payload.bin as this needs payload dumper tool to extract rom which doesn't seems to be working most of the time in my case sometime only vendor & boot get extracted and vice versa.
Click to expand...
Click to collapse
You can try this: https://github.com/ssut/payload-dumper-go/releases

Soniciso1 said:
C:\Users\rampu\Desktop\Nokia PNX\ADB-FIH>fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
-timeout <time> specify timeout. default time: 30s
im stuck at this part when i copy in paste. kep in mind vbmeta is in the dir of fastboot. any advice would be cool.
Click to expand...
Click to collapse
Does this work?
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

its strange. i flashed a stlck global rom then magically it al works. friggin wierd.
leaxy86 said:
Does this work?
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse

oh ad for the part where you do
fastboot flash boot_a boot.img
and
fastboot flash boot_b boot.img
i have to flash twrp or that other recovery then finish the process and skip the last step. if i dont it hangs at boot. after i flash magisk i cnn then flash stock boot and all works fine.

XT1965-3 Can't load Android system

Hello,
I have a Moto G 7 Plus (a XT1965-3 EU), which I softbricked when aborting an Android update by mistake (power button hold in bag while updating....)
I'm stuck on Android recovery with the message
Code:
Can't load Android system. Your data may be corrupt
. I have two options, Try again or Factory data reset (not an acceptable option).
What I tried so far:
- I tried this tutorial, but Motorola doesn't release the images, and sideloading this image (LAKE_RETAIL_9.0_PPWS29.98-111-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml), gives me this message :
Code:
footer is wrong
Signature verification failed
error: 21
- I tried to call the Motorola support, but they won't give me the OTA image, nor help me in a useful way.
- I wanted to install a custom recovery, but unlocking the oem would wipe everything, so no thanks.
I would rather get all the data than repairing the phone (I got it for free thanks to an Amazon Prime trial...), I have several priceless souvenirs in it, and of course I lost my backup drive when I moved away.
Thank you in advance for your help

NicolasBFR said:
Hello,
I have a Moto G 7 Plus (a XT1965-3 EU), which I softbricked when aborting an Android update by mistake (power button hold in bag while updating....)
I'm stuck on Android recovery with the message
Code:
Can't load Android system. Your data may be corrupt
. I have two options, Try again or Factory data reset (not an acceptable option).
What I tried so far:
- I tried this tutorial, but Motorola doesn't release the images, and
Click to expand...
Click to collapse
I don't know if these still work.
Update Tools
[TOOL][WIN] OTA Updates (Motorola)
[TOOL] Motorola OTA Link Generator Tool
NicolasBFR said:
sideloading this image (LAKE_RETAIL_9.0_PPWS29.98-111-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml), gives me this message :
Code:
footer is wrong
Signature verification failed
error: 21
Click to expand...
Click to collapse
That image is not an OTA, it's the full firmware and is not coded for installing with recovery, it's meant for fastboot mode.
You can try flashing with fastboot.exe
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com

sd_shadow said:
I don't know if these still work.
Update Tools
[TOOL][WIN] OTA Updates (Motorola)
[TOOL] Motorola OTA Link Generator Tool
Click to expand...
Click to collapse
Unfortunatly, both require ro.build.version.full to get the appropriate OTA image, and my device won't give it to me with fastboot getvar all . Any idea how I could find it ?
As for Fastboot flash, I would loose the data, which is not an option.

NicolasBFR said:
As for Fastboot flash, I would loose the data, which is not an option.
Click to expand...
Click to collapse
No, only if you use fastboot erase userdata

sd_shadow said:
No, only if you use fastboot erase userdata
Click to expand...
Click to collapse
So, I just have to do fastboot flash with all the .img and sparsechunk files (even though my bootloader is not unlocked and the device not rooted) ?
Why do all internet tutorials erase both cache and userdata ?
And what is the worse that could happen ?
I attached a screen of the archive content:
{
"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"
}

NicolasBFR said:
So, I just have to do fastboot flash with all the .img and sparsechunk files (even though my bootloader is not unlocked and the device not rooted) ?
Why do all internet tutorials erase both cache and userdata ?
And what is the worse that could happen ?
I attached a screen of the archive content:
View attachment 5421721
Click to expand...
Click to collapse
Flashing with a locked bootloader is tricky.
Your best option is using RSD Lite with an old Windows 7 or XP Machine
The servicefile.xml and the flashfile.xml contain the flash commands
the servicefile shouldn't have the userdata line, the flashfile does.
Use Notepad++ to remove the userdata line and save, then flash with RSD Lite.
If that is not an option you can try fastboot.exe
Use the servicefile.xml and the Online FlashFile Converter
run the commands one at a time, if you get an error stop.
and see my Troubleshooting

sd_shadow said:
If that is not an option you can try fastboot.exe
Use the servicefile.xml and the Online FlashFile Converter
run the commands one at a time, if you get an error stop.
and see my Troubleshooting
Click to expand...
Click to collapse
I had USB 3.0 ports so I had the "(bootloader) is-logical:partiti : not found" error.
if you want to know my script (from Online Flashfile converter), is
Bash:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
# fastboot erase carrier
# fastboot erase ddr
fastboot oem fb_mode_clear
echo English - Process concluded!
pause
fastboot reboot
exit
I have a second computer from 2005 with 2.0 USB, I am going to try again in few hours.
Also, all my computers are on Arch Linux (Manjaro) and I download fastboot with pacman,
fastboot --version returns me
Bash:
fastboot version 31.0.2-android-tools
Installed as /usr/bin/fastboot
.
Is my fastboot version ok ?

I am so stupid, I ran the commands above using my old computer, the same fastboot version and with a USB 2.0 port, but with once in a shell script. I don't even have the logs, and now the "Can't load android system" doesn't even appear anymore ! It's just a bootloop.
What should I do ?

Okay @sd_shadow , I used the linux mfastboot recommended by your guides, and this time it managed to flash everything... but I'm back to the bootloader error menu "Can't load Android system"...
Maybe I could flash TWRP recovery (or even just fastboot boot ?), then use it to retrieve userdata and then factory reset ?
EDIT: I tried fastboot boot TWRP.img but I got "permission denied". Maybe there is a custom ROM out there that don't need the userdata ?

General [TWRP] (Not works properly)[Camellia] [Camellian] [UNOFFICIAL] [BETA] TWRP 3.6.0_11 for Poco M3 Pro 5G & Redmi Note 10 5g

WARNING: THIS IS EXPERIMENTAL BETA FOR TEST
Prerequisites:
The bootloader must be unlocked.
Install ADB and Fastboot Drivers -->https://www.mediafire.com/file/7pal74b7e734u5d/15_Second_ADB_Installer_v1.5.6.zip/file
Download the TWRP Image for Poco M3 Pro 5G --> https://www.mediafire.com/file/1h3ogmhij694mby/Twrp_-3.6.0_11_port_poco_m3pro_5g_Camellia.img/file
Installing FastBoot drivers:
if you encountered no file are copied then disable your anti virus and retry in Linux just type 'apt install fastboot' 'dnf install fastboot' 'pacman -S fastboot' based on your current linux distro
Installing TWRP:
Reboot the phone to fastboot (Power + Vol Down)
Connect the phone to the computer using an USB cable (Preferred to use original cable that came with the phone)
Extract the fastboot files and open CMD/Terminal there.
Paste the twrp.img in the same folder.
Type' fastboot boot file_name.img' without the apostrophes.
The phone will reboot in TWRP after that go to Advanced > Flash Current TWRP.
Done!
All Feautures Works
Send Feedbacks Here Please
Developer : SpoliatorDRKBIN

Great! Is touch working on this?

great!!!!!

SalmanSH1 said:
WARNING: THIS IS EXPERIMENTAL BETA FOR TEST
Prerequisites:
The bootloader must be unlocked. Click here for a tutorial.
Install ADB and Fastboot Drivers from here (Select the latest) --> https://androidmtk.com/download-minimal-adb-and-fastboot-tool )
Install drivers for Camellian --> https://droidfilehost.com/download/download-xiaomi-usb-driver-for-windows (For Windows Only!)
Download the TWRP Image for Poco M3 Pro 5G --> https://www.mediafire.com/file/1h3ogmhij694mby/Twrp_-3.6.0_11_port_poco_m3pro_5g_Camellia.img/file
Installing TWRP:
Reboot the phone to fastboot (Power + Vol Down)
Connect the phone to the computer using an USB cable (Preferred to use original cable that came with the phone)
Extract the fastboot files and open CMD/Terminal there.
Paste the twrp.img in the same folder.
Type' fastboot boot file_name.img' without the apostrophes.
The phone will reboot in TWRP after that go to Advanced > Flash Current TWRP.
Done!
All Feautures Works
Send Feedbacks Here Please
Developer : SpoliatorDRKBIN
Click to expand...
Click to collapse
Did you own m3 pro ?
mtk device wont boot with this method according to:
fastboot boot command is bugged on Xiaomi MTK devices · Issue #2356 · MiCode/Xiaomi_Kernel_OpenSource
The best practice for installing TWRP seems to be to inject ramdisk after using fastboot boot twrp.img command. But when this command is broken on the firmware side, I have to make new TWRP build e...
github.com

up864 said:
Did you own m3 pro ?
mtk device wont boot with this method according to:
fastboot boot command is bugged on Xiaomi MTK devices · Issue #2356 · MiCode/Xiaomi_Kernel_OpenSource
The best practice for installing TWRP seems to be to inject ramdisk after using fastboot boot twrp.img command. But when this command is broken on the firmware side, I have to make new TWRP build e...
github.com
Click to expand...
Click to collapse
i confirm, dont boot. i thik he didnt test before post

shi-no_tenshi said:
Great! Is touch working on this?
Click to expand...
Click to collapse
yes touch works
up864 said:
Did you own m3 pro ?
mtk device wont boot with this method according to:
fastboot boot command is bugged on Xiaomi MTK devices · Issue #2356 · MiCode/Xiaomi_Kernel_OpenSource
The best practice for installing TWRP seems to be to inject ramdisk after using fastboot boot twrp.img command. But when this command is broken on the firmware side, I have to make new TWRP build e...
github.com
Click to expand...
Click to collapse
yes m3 Pro 5G
i'm not Developer

wetito said:
i confirm, dont boot. i thik he didnt test before post
Click to expand...
Click to collapse
do you tested ?
use xiaomi Fastboot tools ?

i edited 1st topic
i'll send Video of this Work

fastboot boot Twrp_-3.6.0_11_port_poco_m3pro_5g_Camellia.img
Sending 'boot.img' (38034 KB) OKAY [ 1.423s]
Booting FAILED (Status read failed (No such device))
fastboot: error: Command failed

fastboot boot Twrp_-3.6.0_11_Camellia.img
Sending 'boot.img' (38034 KB) OKAY [ 1.423s]
Booting FAILED (Status read failed (No such device))
fastboot: error: Command failed
Not Booting Redmi Note 10 5G....
Please Fix

use xiaomi fastboot tools

SalmanSH1 said:
use xiaomi fastboot tools
Click to expand...
Click to collapse
Sir Twrp Not Booting On Redmi Note 10 5G

emhashmi said:
fastboot boot Twrp_-3.6.0_11_Camellia.img
Sending 'boot.img' (38034 KB) OKAY [ 1.423s]
Booting FAILED (Status read failed (No such device))
fastboot: error: Command failed
Not Booting Redmi Note 10 5G....
Please Fix
Click to expand...
Click to collapse
https://www.mediafire.com/file/7pal74b7e734u5d/15_Second_ADB_Installer_v1.5.6.zip/file
Use This ADB fastboot installer

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot Twrp_-3.6.0_11_port_poco_m3pro_5g_Camellia.img
< waiting for any device >
downloading 'boot.img'...
OKAY [ 0.957s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 9.357s
{
"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"
}

emhashmi said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot Twrp_-3.6.0_11_port_poco_m3pro_5g_Camellia.img
< waiting for any device >
downloading 'boot.img'...
OKAY [ 0.957s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 9.357s
View attachment 5673465
Click to expand...
Click to collapse
change USB and first send:
fastboot reboot bootloader
then:
fastboot boot twrp.img

SalmanSH1 said:
WARNING: THIS IS EXPERIMENTAL BETA FOR TEST
Prerequisites:
The bootloader must be unlocked.
Install ADB and Fastboot Drivers -->https://www.mediafire.com/file/7pal74b7e734u5d/15_Second_ADB_Installer_v1.5.6.zip/file
Download the TWRP Image for Poco M3 Pro 5G --> https://www.mediafire.com/file/1h3ogmhij694mby/Twrp_-3.6.0_11_port_poco_m3pro_5g_Camellia.img/file
Installing FastBoot drivers:
if you encountered no file are copied then disable your anti virus and retry in Linux just type 'apt install fastboot' 'dnf install fastboot' 'pacman -S fastboot' based on your current linux distro
Installing TWRP:
Reboot the phone to fastboot (Power + Vol Down)
Connect the phone to the computer using an USB cable (Preferred to use original cable that came with the phone)
Extract the fastboot files and open CMD/Terminal there.
Paste the twrp.img in the same folder.
Type' fastboot boot file_name.img' without the apostrophes.
The phone will reboot in TWRP after that go to Advanced > Flash Current TWRP.
Done!
All Feautures Works
Send Feedbacks Here Please
Developer : SpoliatorDRKBIN
Click to expand...
Click to collapse
I got bootloop on MIUI 12.5.4 ID

This doesn't work
SalmanSH1 said:
change USB and first send:
fastboot reboot bootloader
then:
fastboot boot twrp.img
Click to expand...
Click to collapse
I tried USB 3 and USB 2

SalmanSH1 said:
change USB and first send:
fastboot reboot bootloader
then:
fastboot boot twrp.img
Click to expand...
Click to collapse
Already Change Usb And Change DATA Cable...But Doesn't work

SalmanSH1 said:
https://www.mediafire.com/file/7pal74b7e734u5d/15_Second_ADB_Installer_v1.5.6.zip/file
Use This ADB fastboot installer
Click to expand...
Click to collapse
i'm a linux user. my adb and fastboot driver are perfect

wetito said:
i'm a linux user. my adb and fastboot driver are perfect
Click to expand...
Click to collapse
I think he is trolling us. Or his phone is lucky one

How To Guide Fix MIUI logo stuck after patching boot.img with Magisk (And ROOT it successfully - MIUI13 A12)

I AM AWARE OF OTHER ROOT TUTORIALS HERE, THIS IS MORE DETAILED TUTORIAL THAT FIXES THE MIUI STUCK OR BOOTLOOP !!
I'm writing this post here because after months and few MIUI updates I finally fixed a problem that I wish somebody could help me with when I had it and that is: Camellian Stuck on MIUI logo (bootloop/won't boot) after patching boot.img with latest Magisk.
Steps:
Download fastboot version of your exact system version which u can check in your android settings; in my case that would be:
{
"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"
}
Download latest platform-tools from Google
Download Payload Dumper from GitHub and extract it anywhere
Extract payload.bin from fastboot ROM you just downloaded and put it in Payload Dumper folder
Open Payload Dumper folder and type CMD in Address Bar
In CMD type:
Code:
payload-dumper-go payload.bin
When it's finished use Magisk (in my case Magisk 555a54ec-alpha 25203 - Magisk Alpha Telegram) to patch boot.img that you extracted via Payload Dumper
Copy Magisk patched boot.img, vbmeta.img, vbmeta_system.img, vbmeta_vendor.img and paste it in platform-tools folder
Open CMD in platform-tools folder the same way you did with Payload Dumper and connect your phone via USB (ofc enable USB Debugging)
Type these adb / fastboot commands
Code:
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_system_a vbmeta_system.img
fastboot flash vbmeta_system_b vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_vendor_a vbmeta_vendor.img
fastboot flash vbmeta_vendor_b vbmeta_vendor.img
fastboot flash boot boot.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
If you're stuck on MIUI logo while rebooting type:
Code:
adb wait-for-device shell magisk --remove-modules
The phone will reboot with Magisk rooted.