Database Develop

Problem flashing stock moto 4.4.4 firmware

Sorry if this doesn't belong here, but I need to ask it....for those who flashed cm11 or cm12 on their moto x and then flashed back to stock for any reason using the stock sbf, has anyone seen a red text saying "sp space is not enough" after flashing the system IMG? Yesterday I flashed back to stock using fastboot commands and got that line in red text showing on my phone when flashing system and I'm a bit worried about it, here is a picture I took (sorry for the poor quality)
The phone booted up normally but this thing still worries me...
Thanks in advance for the help!
I forgot, my phone is a moto x GSM developer edition xt1053
{
"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"
}

When you were doing the fastboot commands did you make sure to use the mfastboot command for the system image rather than the normal fastboot?

coles427 said:
When you were doing the fastboot commands did you make sure to use the mfastboot command for the system image rather than the normal fastboot?
Click to expand...
Click to collapse
Yes, I'm a 100% sure, I flashed the same phone before with the same firmware and the same mfastboot file with no problem at all, and suddenly yesterday this red text appeared when trying to flash it again... Really weird

cammel said:
Yes, I'm a 100% sure, I flashed the same phone before with the same firmware and the same mfastboot file with no problem at all, and suddenly yesterday this red text appeared when trying to flash it again... Really weird
Click to expand...
Click to collapse
Hmm... Did you try the RSDlite restore method?

coles427 said:
Hmm... Did you try the RSDlite restore method?
Click to expand...
Click to collapse
Nope, never used rsdlite, and I can't use it cause the stock 4.4.4 firmware for my phone does not include an XML file inside it cause since it's the developer edition Motorola provides the firmware and they only include the firmware files and the mfastboot.exe to use with them, but not a XML file, which is also weird...

also have the same issue. I flashed back my moto x from CM12 and same message appear. by the way im using RSD lite. before i used to flash it many time using RSD lite and only lately I notice that message. thanks

ryuben2k said:
also have the same issue. I flashed back my moto x from CM12 and same message appear. by the way im using RSD lite. before i used to flash it many time using RSD lite and only lately I notice that message. thanks
Click to expand...
Click to collapse
I think it might be related with twrp, cause I never flashed any ROM on my phone, I only installed twrp to be able to root my phone and after that I got that red text every time I try to go back to stock 4.4.4 and trust me, I searched for days on the web and no one knows why this happens and what it means...
It would be awesome if a developer or a more advanced user can helps us find what's wrong with our phone and why this happened....

cammel said:
I think it might be related with twrp, cause I never flashed any ROM on my phone, I only installed twrp to be able to root my phone and after that I got that red text every time I try to go back to stock 4.4.4 and trust me, I searched for days on the web and no one knows why this happens and what it means...
It would be awesome if a developer or a more advanced user can helps us find what's wrong with our phone and why this happened....
Click to expand...
Click to collapse
Did you run the command fastboot erase userdata? Or did you run fastboot erase system before flashing the new system.img?

Travisdroidx2 said:
Did you run the command fastboot erase userdata? Or did you run fastboot erase system before flashing the new system.img?
Click to expand...
Click to collapse
I did run the command fastboot erase userdata, but the erase system command scares me, I have never seen anyone using that command on fastboot on the moto x tutorials or on any other phone's tutorial...
So...have you ever tried that command on the moto x? Cause I'm afraid that if I do that erase system thing and then get an error while flashing the stock system img, then I'm pretty much screwed....right?

Moto G 4G (uk model) Stuck on wallpaper

Hey Guys, i'm really struggling to find a solution to this as every time i try to google a solution it just comes up with a load of results trying to tell me how to change my wallpaper :/
So basically, overnight, my dad's Moto G 4G started to act strangly. It can still:
Boot up normally
Power Off normally
Vibrates when notifications come through
Rings, all be it temporarily when called and can be answered if connected to the car's bluetooth.
However, it will no longer display any of the UI (other than the Power Off dialogue) and the wallpaper. I can see that the phone isn't completely frozen as the wallpaper in use is a live wallpaper which you can interact with via touch.
When the phone is plugged into my laptop the phone is showing in 'my computer' but it shows no files, same situation in recovery and fastboot too.
I've tried wiping the cache from recovery but it's still the same.
There was one instance where the first time i plugged the phone into the laptop via usb it brought up the whole ui, icons, status bar and all, for like 2 seconds.
Now, back to nothing. Not sure what to do from here. I'm desperately trying not to factory reset it as my grandfather (my dad's dad) passed away recently and i'm pretty sure there are files on here which are now irreplaceable

jhaedee said:
Hey Guys, i'm really struggling to find a solution to this as every time i try to google a solution it just comes up with a load of results trying to tell me how to change my wallpaper :/
So basically, overnight, my dad's Moto G 4G started to act strangly. It can still:
Boot up normally
Power Off normally
Vibrates when notifications come through
Rings, all be it temporarily when called and can be answered if connected to the car's bluetooth.
However, it will no longer display any of the UI (other than the Power Off dialogue) and the wallpaper. I can see that the phone isn't completely frozen as the wallpaper in use is a live wallpaper which you can interact with via touch.
When the phone is plugged into my laptop the phone is showing in 'my computer' but it shows no files, same situation in recovery and fastboot too.
I've tried wiping the cache from recovery but it's still the same.
There was one instance where the first time i plugged the phone into the laptop via usb it brought up the whole ui, icons, status bar and all, for like 2 seconds.
Now, back to nothing. Not sure what to do from here. I'm desperately trying not to factory reset it as my grandfather (my dad's dad) passed away recently and i'm pretty sure there are files on here which are now irreplaceable
Click to expand...
Click to collapse
Ouch, looks like an emmc problem, some partitions may be corrupted.
1st be sure if the usb cable is ok, i have seen many cable going nuts and loosing data but still charging.
If the usb cable is dead you will need a working one anyway to try to recover the phone after you got your data.
Also try apps like airdroid works, you can save everything wirelessy from your pc.
When you have a working cable and still failed to save data you can try to flash a recovery that allow mounting partitions to your pc ( twrp ) whitout booting the os, since for what i understood your android installation got corrupted somewhere and is borked.
Wich model is that one ? should be an XT1072 right ? YOU MUST BE SURE or flashing the wrong stuffs can totaly BRICK your phone.
If it's an XT1072 i have uploaded for you the latest UK stock image to mega.nz so you can dl it quickly
https://mega.nz/#!fId0yD4a!LjyEIjRXse092l7j_JL0Ky324EK6SS4vK4kdqGcS9XY
You will need fastboot + mfastbbotv2 and here they are
https://mega.nz/#!bdEDBDiQ!3KlB6WfUxUep1QR7XSvwpuCuxWnktfCh7YBX020HqmY
Put everything in the same folder ( ex c:\phoner )
open a dos shell whit admin privileges and navigate to that folder, then use this commands and check after every commands if you get back the OK on flashing (you can copy-paste them into the shell)
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata <--- DON'T use this only if you wasn't able to recover your data whit the others methods
mfastboot.exe reboot
The phone should have rebooted, may take longer to boot don't panic, now the phone should be ok and if you didn't wiped the userdata it should be 100% the same as before whit the latest stock fw, my advice is to do a full factory restore to use it, so once you recovered your data do a factory reset from the android menu.
If the phone isn't a 1072 as supposed dl here the correct zip http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC
If you have more questions, especially on flashing twrp/stock just ask before doing anything that could turn the phone into a stone.

Thank you Dr. Nic for your incredibly informative response
Firstly, I was wrong initially, it is actually a XT1039 (first gen 4g) but this does appear to be listed on the file factory page you linked so I should be fine with the instructions.
What I do want to ask though is:
Is there anyway for me to boot twrp without installing it as a temporary basis? I'm sure I've done this before previously on my old moto x but it has been a while. I seem to recall you can type in a fast boot command and get it to boot to twrp. The phone is not rooted or bootloader unlocked (which i know will wipe the phone if I do it so that isn't really a permanent option yet)
Secondly, is there any way for me to find out which stock rom files I need without being able to access the os and looking in settings? I know it is a xt1039 but there are about 5 different, carrier based versions available and I don't want to flash the wrong one.
Thanks again for all your help
If this goes to plan you will have made my father's Christmas special

jhaedee said:
Thank you Dr. Nic for your incredibly informative response
Firstly, I was wrong initially, it is actually a XT1039 (first gen 4g) but this does appear to be listed on the file factory page you linked so I should be fine with the instructions.
What I do want to ask though is:
Is there anyway for me to boot twrp without installing it as a temporary basis? I'm sure I've done this before previously on my old moto x but it has been a while. I seem to recall you can type in a fast boot command and get it to boot to twrp. The phone is not rooted or bootloader unlocked (which i know will wipe the phone if I do it so that isn't really a permanent option yet)
Secondly, is there any way for me to find out which stock rom files I need without being able to access the os and looking in settings? I know it is a xt1039 but there are about 5 different, carrier based versions available and I don't want to flash the wrong one.
Thanks again for all your help
If this goes to plan you will have made my father's Christmas special
Click to expand...
Click to collapse
So 1 thing at time
Probably the others fw you saw was olders versions too or for others regions, i suggest to use the same as you have or the latest
You are completly unable to check your current os installed from phone infos ? have you checked everything on the box ? somewhere there must be some infos, maybe under a barcode sticker.
This should be your latest UK stock, XT1039 aka "peregrine", do you rember if you was on 4.4.4 or 5.1 ? you should flash the same version to improve the % of not loosing something.
Clean Stock 5.1 http://www.filefactory.com/file/dpx...RINE_RETGB_5.1_LPB23.13-17.3_cid7_CFC.xml.zip
So, the cable is ok ? are you able to issue commands whit fastboot ?
If yes unlock the bootloader to install a modded recovery, you will need that to copy your files, and if that fails last try is flashing stock whitout deleteing userdata, but the corruption could be both in /data and /system so after the recovery you will have to do a factory reset anyway.
To boot twrp you have to flash it, don't worry if you want the phone full stock again is the last step you have to do that to fix the corruptions happened, and it's no 100% success rate too since that could happened becouse the emmc is failing

Unbrick Xiaomi Mi A2 [jasemine]

Hello,
i have bought a new Xiaomi Mi A2 and thought it would be a really nice idea to flash magisk on it. First everything was alright. I unlocked my bootloader in fastboot with "fastboot oem unlock" and flashed twrp on the b partition. Unfortunately my device broke (don't know why... maybe the unofficial twrp with some bugs or...). So now i have a really big problem, because my twrp recovery is missing as well as the stock recovery. When i try to switch on the mobile i am stuck in bootloop (with the mi logo). Not even the bootloader warning is shown.
Fastboot mode is working but not really nice. Not even the mitu appears, no the display is black (or doesn't show anything.. The device's display is on).
My Mi A2 is recognized by the computer so I considered to flash the stock rom with fastboot.
I thought it would work, but in the mi flash programm i got the erorr: flash devcfg_a error.
Now i can't switch my mobile off, because when I'm holding the power button, it restarts and restarts and restarts...
I know i am stupid and maybe have done something wrong, but i would be soooo happy to get some help
Thank you so much!

Fastboot flashing unlock_critical
(It will wipe /data)
then flash with mi flash
But before doing that, try just flashing stock boot
Fastboot flash boot_a boot.img
Or boot_b if that's your active slot

Nebrassy said:
Fastboot flashing unlock_critical
(It will wipe /data)
then flash with mi flash
But before doing that, try just flashing stock boot
Fastboot flash boot_a boot.img
Or boot_b if that's your active slot
Click to expand...
Click to collapse
Thank you very much for your answer.
Unfortunately i have wiped everything in twrp before (when it worked) so there's nothing stored on the device.
When i type in critical unlock only a big list of commands appears which can be used.... ?

MardukPVP said:
Thank you very much for your answer.
Unfortunately i have wiped everything in twrp before (when it worked) so there's nothing stored on the device.
When i type in critical unlock only a big list of commands appears which can be used.... ?
Click to expand...
Click to collapse
what's the exact command you used?

Nebrassy said:
what's the exact command you used?
Click to expand...
Click to collapse
In minimal ADB and Fastboot I used: fastboot flashing unlock_critical
{
"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"
}

MardukPVP said:
In minimal ADB and Fastboot I used: fastboot flashing unlock_critical
Click to expand...
Click to collapse
Don't use minimal adb, use this https://developer.android.com/studio/releases/platform-tools

Okay, i've got no words. You saved my life. It worked. Thank you sooo much !!!

Not receiving updates
I need help i recently flashed fastboot rom on mi A2 Oct patch firmware.I can't receive any Ota Updates,How to get in phone on original state? With working online updates in settings PLEASE HELP!!:crying::crying:

jdivya524 said:
I need help i recently flashed fastboot rom on mi A2 Oct patch firmware.I can't receive any Ota Updates,How to get in phone on original state? With working online updates in settings PLEASE HELP!!:crying::crying:
Click to expand...
Click to collapse
So you have flashed this rom https://en.miui.com/download-353.html ?

Nebrassy said:
Fastboot flashing unlock_critical
(It will wipe /data)
then flash with mi flash
But before doing that, try just flashing stock boot
Fastboot flash boot_a boot.img
I promised I would create an account here just to thank you if your method worked!
After doing something dumb (I typed some wrong commands I think) my A2 got into the infinite reboot, never got out of the android logo, I tried everything and literally thought I lost my phone for good ;n;
I downloaded "jasmine_global_images_V10.0.2.0.PDIMIFJ_20181206.0000.00_9.0_02b8deeb6d.tar" and flashed that on miflash and watched my phone come back from the dead like frankestein or something. He's doing great and is in top shape, thanks to your advice! THANK YOU VERY MUCH! Hope you have a wonderful 2019!
Click to expand...
Click to collapse

MardukPVP said:
Okay, i've got no words. You saved my life. It worked. Thank you sooo much !!!
Click to expand...
Click to collapse
Hey Did Your smartphone works fine I mean did you get every Updates from Stock

error
Nebrassy said:
Fastboot flashing unlock_critical
(It will wipe /data)
then flash with mi flash
But before doing that, try just flashing stock boot
Fastboot flash boot_a boot.img
Or boot_b if that's your active slot
Click to expand...
Click to collapse
When i try it shows the error remote error flashing partition , how to solve that help please my email is [email protected] , replay there if possible thank you

[email protected] said:
When i try it shows the error remote error flashing partition , how to solve that help please my email is [email protected] , replay there if possible thank you
Click to expand...
Click to collapse
Try flashing through edl mode

I think I bricked my mi a2 please help me.
MardukPVP said:
Thank you very much for your answer.
Unfortunately i have wiped everything in twrp before (when it worked) so there's nothing stored on the device.
When i type in critical unlock only a big list of commands appears which can be used....
Click to expand...
Click to collapse
I have a mi a2 and it's stuck on Android logo screen. It has an unlocked bootloader and maybe it's rooted too. While I thought I rooted it.. It went into bootlooping.. Only fastboot and android logo can be accessed. I tried flashing it with stock rom but mi flash tool goes like 3500+ sec. Please tell how to fix this.

same issu
okay i hav the same problem, can't fix it
whenever i try to use any command in cmd during the device is in fastboot mode, my phone screen go to the black, and it says in a liitle, "press any key to shutdown"
is there any solution? it will me life saving.

anikapproe said:
...whenever i try to use any command in cmd during the device is in fastboot mode, my phone screen go to the black, and it says in a liitle, "press any key to shutdown" is there any solution?
Click to expand...
Click to collapse
I have the same issue in PC I'm writing this from (in USB3.1 Gen2 and Gen 1 ports, and even in USB 2.0 ports), but have no problems in 2 other PCs I currently have access to.
For non-universal solution with my current PC please see more info in my answer in neighbouring thread: https://forum.xda-developers.com/showpost.php?p=81693759&postcount=28.

[Guides]Downgrade from android 11 to 10

Part1:Unlock Bootlaoder
step1: download and install Rescue and Smart Assistant Tool
https://www.motorola.com/us/rescue-and-smart-assistant/p
step2: download and install USB drivers
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/88481/
step3: download Attachments"cmd-here.zip",unzip to Rescue and Smart Assistant fold
step4:Settings phone: System > Developer Options.
Enable OEM Unlocking and also enable USB Debugging,then switch off your device.
Put device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
Connect phone to PC with USB cable,then waiting PC automaticly install phone driver.
step5:go to Motorola unlock page,then complete thine page steps. Use "cmd-here"open CMD to type command
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
You will get unlock code in your mailbox finally.
step6:type fastboot oem unlock 'your code'
The process will wipe all the data off your phone and reboot.
Part2:TWRP for Motorola Moto Edge
step7:go to TWRP for Motorola Moto Edge page,choose and download .zip and .img.
https://twrp.me/motorola/motorolamotoedge.html
Please follow "Installation" steps to flash TWRP in this page.
Part3:download Official firmware
step8:Choose the correct android 10 firmware and download
https://mirrors.lolinet.com/firmware/moto/racer/official/
step9:Unzip the file,then step by step to execute these commands：
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash dsp dspso.bin
fastboot flash erase userdata (I get wrong feedback,but no problem)
fastboot flash erase ddr (I get wrong feedback,but no problem)
fastboot oem fb_mode_clear
step10:Reboot devices(If you get wrong feedback same to me,now you can run factry restore after devices reboot on the screen)
Enjoy! the downgrade procedure was successed!​

good afternoon friend !
I have been trying to unlock the bootloader and without success. is only giving this message!
"Your device does not qualify for bootloader unlocking."
what to do? already tried two sites, American and BR. Any solution? i want to go back android 10 .
Thank you very much in advance

_DuuhPro said:
good afternoon friend !
I have been trying to unlock the bootloader and without success. is only giving this message!
"Your device does not qualify for bootloader unlocking."
what to do? already tried two sites, American and BR. Any solution? i want to go back android 10 .
Thank you very much in advance
Click to expand...
Click to collapse
Which cid and channel does it have?
Code:
fastboot getvar cid
fastboot getvar ro.carrier

sd_shadow said:
Which cid and channel does it have?
Code:
fastboot getvar cid
fastboot getvar ro.carrier
Click to expand...
Click to collapse
good night coming home I will see this friend, tell me something please, the android 10 is much better battery / performance ratio?

sd_shadow said:
Which cid and channel does it have?
Code:
fastboot getvar cid
fastboot getvar ro.carrier
Click to expand...
Click to collapse
Here are the infos you asked for, if I could help I would be very grateful, thank you !!
0000000000000000#30303637343833373031006D6F746F726F6C0000#319265AB6EA044F1802F74495C19E6B6B859F4DB#714CAE65000000000000000000000000
cid: 0x0000
ro.carrier: unknown

sd_shadow said:
Which cid and channel does it have?
Code:
fastboot getvar cid
fastboot getvar ro.carrier
Click to expand...
Click to collapse
Hey brother ?

_DuuhPro said:
good afternoon friend !
I have been trying to unlock the bootloader and without success. is only giving this message!
"Your device does not qualify for bootloader unlocking."
what to do? already tried two sites, American and BR. Any solution? i want to go back android 10 .
Thank you very much in advance
Click to expand...
Click to collapse
check you already turn on OEM unlocking in Developer options

Vger20192019 said:
check you already turn on OEM unlocking in Developer options
Click to expand...
Click to collapse
Yes started !!!
{
"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"
}

Vger20192019 said:
check you already turn on OEM unlocking in Developer options
Click to expand...
Click to collapse
hey broo!! any tips to help me friend? i'm dying to go back android 10!!!
?

_DuuhPro said:
Here are the infos you asked for, if I could help I would be very grateful, thank you !!
0000000000000000#30303637343833373031006D6F746F726F6C0000#319265AB6EA044F1802F74495C19E6B6B859F4DB#714CAE65000000000000000000000000
cid: 0x0000
ro.carrier: unknown
Click to expand...
Click to collapse
The problem is your device is not providing the correct info, the first part should not be all zeros.
try reflashing firmware with LMSA.

sd_shadow said:
The problem is your device is not providing the correct info, the first part should not be all zeros.
try reflashing firmware with LMSA.
Click to expand...
Click to collapse
good night my friend , the software really had a pending att , I did it through the LMSA , but the same code still remained . what can we be doing?? to give up??
now it is up to date.
RPDS31.Q4U-39-26-14-3
October Security Patch

If Motorola unlock page show "Your device does not qualify for bootloader unlocking",that means you need give up.
By the way if you just downgrade to 10 with official ROM,you just do it！No need unlock phone（in my experience with downgrade huawei P10）

Vger20192019 said:
If Motorola unlock page show "Your device does not qualify for bootloader unlocking",that means you need give up.
By the way if you just downgrade to 10 with official ROM,you just do it！No need unlock phone（in my experience with downgrade huawei P10）
Click to expand...
Click to collapse
No Motorola devices cannot be downgraded from one android version to another.

sd_shadow said:
No Motorola devices cannot be downgraded from one android version to another.
Click to expand...
Click to collapse
You'll have to make my phone aware of this limitation.

Question Oneplus 10 Pro stuck in Bootloop

So I restarted my phone today and it just entered an infinite boot loop. Not sure what happened but that's all it's doing whenever I turn it on. I can enter the bootloader but other than that nothing is working. I noticed the bootloader and baseband are empty as well.
I wish this phone had an unbrick tool like the oneplus 7 devices but I don't know. I guess I may just have a brick until someone shakes.
{
"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"
}

biglo said:
So I restarted my phone today and it just entered an infinite boot loop. Not sure what happened but that's all it's doing whenever I turn it on. I can enter the bootloader but other than that nothing is working. I noticed the bootloader and baseband are empty as well.
I wish this phone had an unbrick tool like the oneplus 7 devices but I don't know. I guess I may just have a brick until someone shakes.
View attachment 5694575
Click to expand...
Click to collapse
Are you rooted? Can you get in recovery? What model number?

twinnfamous said:
Are you rooted? Can you get in recovery? What model number?
Click to expand...
Click to collapse
Was rooted, can get to recovery using the enhanced flash tool and model is 2210.

biglo said:
Was rooted, can get to recovery using the enhanced flash tool and model is 2210.
Click to expand...
Click to collapse
Have you tried flashing stock boot.img or factory resetting?

twinnfamous said:
Have you tried flashing stock boot.img or factory resetting?
Click to expand...
Click to collapse
Yes, I tried both options without success.

biglo said:
Yes, I tried both options without success.
Click to expand...
Click to collapse
That's not good usually one or the other fixes it. Only thing I can think of is flashing all images in fastboot. But try vendor_boot first

When this happened to me on my OP6 when I had it and when I couldn't recover it with MSM tools or boot.img, I decided it is motherboard failure.
But I would try fastboot ROM if I were you. If it doesn't help, I will send it to the service center.

You may have booted a patched yet not made it permanent so when you rebooted you lost it.
If that rings a bell then just boot a patched boot image. Not flash.. once you're booted and in the system just open magisk and click direct install..
Reboot and it should be permanent.
Beyond that you can go to recovery or fastboot to get back in business although you'll lose your data

My phone did this once when I accidentally changed A/B partition, try switching partition via fastboot
Do the following
fastboot getvar all
then you'll get somewhere the following
(bootloader) current-slot:A or B
then you should be able to do either
fastboot set_active other
or either
fastboot set_active a
fastboot set_active b

unsafe8989 said:
My phone did this once when I accidentally changed A/B partition, try switching partition via fastboot
Do the following
fastboot getvar all
then you'll get somewhere the following
(bootloader) current-slot:A or B
then you should be able to do either
fastboot set_active other
or either
fastboot set_active a
fastboot set_active b
Click to expand...
Click to collapse
I tried switching slots the other day, it gave me the same results.

hello did you found any solutions?

biglo said:
I tried switching slots the other day, it gave me the same results.
Click to expand...
Click to collapse
That means you have no boot img on it

try to flash a boot img to slot a and slot b

Is this still ongoing?? Lol that's insanity.
The reason you cannot boot is 100% your boot image.
So either boot or flash a boot image (stock or patched)
If you'd like to reflash your whole phone then click on vol up and then recovery.
If you're looking for a tool then grab fastboot enhance, whilst in fastboot use it to remove the cow files, search for them, once that's done, flash a payload.bin and this will reload your whole OS.
There are guides for everything I've mentioned above, just search.

dladz said:
Is this still ongoing?? Lol that's insanity.
The reason you cannot boot is 100% your boot image.
So either boot or flash a boot image (stock or patched)
If you'd like to reflash your whole phone then click on vol up and then recovery.
If you're looking for a tool then grab fastboot enhance, whilst in fastboot use it to remove the cow files, search for them, once that's done, flash a payload.bin and this will reload your whole OS.
There are guides for everything I've mentioned above, just search.
Click to expand...
Click to collapse
Hi,
I have the same problem. Never used the phone. Just to install Magisk and edit the payload.bin file. When I installed the new boot file via Fastboot it went wrong.
Tried everything but can't get the phone out of the loop. I don't have a recovery function!
You indicate that there are manuals for existing solutions everywhere. Do you have the links for me? Not very good at finding this.

*-MaCK-* said:
Hi,
I have the same problem. Never used the phone. Just to install Magisk and edit the payload.bin file. When I installed the new boot file via Fastboot it went wrong.
Tried everything but can't get the phone out of the loop. I don't have a recovery function!
You indicate that there are manuals for existing solutions everywhere. Do you have the links for me? Not very good at finding this.
Click to expand...
Click to collapse
Doesn't help that the forums went through a crap update that broke the sections.
That being said, you're looking for a guide so that's your key word.
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com
There's a good few of them, the screen shot is taken from the main OnePlus 10 pro forum section, I can see two. Mine and the 2215 one.
Also when you say 'installed' I hope you meant boot and not flash, booting is risk free.. Read my thread and it'll make sense.

I wish people would read more...cause it all here...just need to take the time and read alot of post...to find what they are looking for...lol