Hi,
had a rooted 2213 OP10 Pro.
Tried to update it to the latest C26 update locally. after it extracted, just rebooted without permission and I lost root.
opened magisk and there no option to inactive slot after ota.
booted into fastboot and flashed magisk patched boot. when it booted, opened magisk and there an option to write to inactive slot. did it.
after that, the phone is in qualcoom crash dump mode.
Can I recover it somehow ? what should i don next ?
please any advice, this is my work phone.
Lior84 said:
Hi,
had a rooted 2213 OP10 Pro.
Tried to update it to the latest C26 update locally. after it extracted, just rebooted without permission and I lost root.
opened magisk and there no option to inactive slot after ota.
booted into fastboot and flashed magisk patched boot. when it booted, opened magisk and there an option to write to inactive slot. did it.
after that, the phone is in qualcoom crash dump mode.
Can I recover it somehow ? what should i don next ?
please any advice, this is my work phone.
Click to expand...
Click to collapse
Can you go into bootloader mode?
TheNewHEROBRINE said:
Can you go into bootloader mode?
Click to expand...
Click to collapse
yes
{
"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 is probably the cause of the issue. Magisk switched your active slot to the previous one which becomes unbootable after the update completes successfully. You should be able to switch back to your working slot by doing fastboot --set-active=other, although I'm not 100% sure this is right solution I think it's a reasonable one. I'm always a bit scared suggesting solutions to people who have a recent OnePlus phone since they can't unbrick it if they end up in a hard brick.
TheNewHEROBRINE said:
View attachment 5847335
This is probably the cause of the issue. Magisk switched your active slot to the previous one which becomes unbootable after the update completes successfully. You should be able to switch back to your working slot by doing fastboot --set-active=other, although I'm not 100% sure this is right solution I think it's a reasonable one. I'm always a bit scared suggesting solutions to people who have a recent OnePlus phone since they can't unbrick it if they end up in a hard brick.
Click to expand...
Click to collapse
did't understood the command that you suggested.
did copy paste to it and it says unrecognized option
Lior84 said:
did't understood the command that you suggested.
did copy paste to it and it says unrecognized option
Click to expand...
Click to collapse
Is your phone in bootloader mode and recognized by fastboot? Can you send a screenshot of the command + error?
TheNewHEROBRINE said:
Is your phone in bootloader mode and recognized by fastboot? Can you send a screenshot of the command + error?
Click to expand...
Click to collapse
ok, opened updated platofrm tools and did what you said...
it's worked !!!
now is the only problem that I have no root
How I bring it back ? my version is NE2213_11_c.26
Lior84 said:
ok, opened updated platofrm tools and did what you said...
it's worked !!!
now is the only problem that I have no root
Click to expand...
Click to collapse
Boot the Magisk patched boot.img (don't flash it!). Then go into Magisk and do a direct install (DON'T do install to inactive slot). Then reboot and check if root is still there.
TheNewHEROBRINE said:
Boot the Magisk patched boot.img (don't flash it!). Then go into Magisk and do a direct install (DON'T do install to inactive slot). Then reboot and check if root is still there.
Click to expand...
Click to collapse
where to get it ? or how to make it ?
Lior84 said:
booted into fastboot and flashed magisk patched boot.
Click to expand...
Click to collapse
You can use the one you already have, you just need to do fastboot boot magisk_patched.img (or whatever it's called) instead of fastboot flash.
TheNewHEROBRINE said:
You can use the one you already have, you just need to do fastboot boot magisk_patched.img (or whatever it's called) instead of fastboot flash.
Click to expand...
Click to collapse
i did this. it sending it and succeeded. then says boot failed ( remote unrecognized command)
Lior84 said:
i did this. it sending it and succeeded. then says boot failed ( remote unrecognized command)
Click to expand...
Click to collapse
Are you sure you're in bootloader mode and not fastbootd?
Lior84 said:
i did this. it sending it and succeeded. then says boot failed ( remote unrecognized command)
Click to expand...
Click to collapse
adb reboot fastboot reboots you to fastbootd, not bootloader mode! You need to do adb reboot bootloader.
TheNewHEROBRINE said:
adb reboot fastboot reboots you to fastbootd, not bootloader mode! You need to do adb reboot bootloader.
Click to expand...
Click to collapse
OK, finally everything worked. I'm a little bit rusty (my first android was HTC desire back in 2010).
Thank you very much, You really saved me a lot of time and frustration !!! I already started to think how to get all the data back.
I really appreciate your help !!!
THank you again.
Lior
You're welcome!
Related
Hi,
I downloaded CWM unofficial 6.0.32 from this forum, but I'm new and I have no idea what to do with it. I did successfully root my phone that's all I've done to it.
Thanks!
You use fastboot commands. There's a tutorial skeevy just made in general.
Sent from my PACMAN MATRIX HD MAXX
I'm sorry, but I'm getting stuck
1: I installed the sdk replaced the files with the updated ones provided.
2:checked adb devices from command promt and It sees my device.
3: ran adb and it successfully starts
4: I then rebooted phone into fastboot Power+Volume down and adb reports device not found.
5: pull hair out.
I'd appreciate a sort of idiots guide because I'm getting no where fast and I've read and read, but they don't explain much that's the problem.
Do you have the lastest motorola usb driver installed?
hungrymr2 said:
Do you have the lastest motorola usb driver installed?
Click to expand...
Click to collapse
Yes, Sir
Rick1488 said:
I'm sorry, but I'm getting stuck
1: I installed the sdk replaced the files with the updated ones provided.
2:checked adb devices from command promt and It sees my device.
3: ran adb and it successfully starts
4: I then rebooted phone into fastboot Power+Volume down and adb reports device not found.
5: pull hair out.
I'd appreciate a sort of idiots guide because I'm getting no where fast and I've read and read, but they don't explain much that's the problem.
Click to expand...
Click to collapse
1. :good:
2. :good:
3 :good:
4 You're in fastboot mode....adb won't recognize your phone....that's normal...
5
use the command "fastboot flash recovery cwm.img" from inside the folder with cwm.img. Or move the fastboot executable and the recovery image to C:\ and do it from there...Win can crap out when/if there are too many characters in the path...
Also, right click the fastboot executable and set it to run as admin. Might have to disable UAC as well....don't ask me how, I don't know...google it.
//I'm cereal, ya had to rename the SBF because in the home directory the path + sbf name would be too many characters for Win to work with and the flash would fail....
No idea, but here's what I did to install cwm. download safestrap apk, boot to safestrap recovery, hit fix permission, go back to cmd prompt, fastboot flash it,
edit: try enabling "usb developer/debugging mode" before booting it into fastboot?
skeevydude said:
1. :good:
2. :good:
3 :good:
4 You're in fastboot mode....adb won't recognize your phone....that's normal...
5
use the command "fastboot flash recovery cwm.img" from inside the folder with cwm.img. Or move the fastboot executable and the recovery image to C:\ and do it from there...Win can crap out when/if there are too many characters in the path...
Also, right click the fastboot executable and set it to run as admin. Might have to disable UAC as well....don't ask me how, I don't know...google it.
//I'm cereal, ya had to rename the SBF because in the home directory the path + sbf name would be too many characters for Win to work with and the flash would fail....
Click to expand...
Click to collapse
Ok your directions were very helpful and I thought good things were coming my way, but when entering the flash command I get preflash validation failed. <failed> remote failure.
{
"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"
}
Update: now the phone boots to fastboot with flash failure on the bottom. What the hell did I do wrong?
Update2: ok got her back to life back to the original problem.
Rick1488 said:
Ok your directions were very helpful and I thought good things were coming my way, but when entering the flash command I get preflash validation failed. <failed> remote failure.
Update: now the phone boots to fastboot with flash failure on the bottom. What the hell did I do wrong?
Update2: ok got her back to life back to the original problem.
Click to expand...
Click to collapse
You might have a picky motherboard. Some front-side ubs ports won't work for some odd reason for some users. Use a usb port on the back of your pc.
Out of curiousity, did you try flashing a fastboot with rsd before you started doing this? And if yes, did it finish completely?
Also attached is a zip to flash CWM from SSR (maybe...SSR might block the command) and a fastboot modified to only flash CWM. Both are untested but worth a shot.
EDIT: Any one of you windows users care to chime in? Ya'll know I don't run it. I'm kinda runnin outta ideas here....gettin down to the just use linux reply...
unlocked bootloader
I saw that you rooted but did you unlock the boot loader?
frog1982 said:
I saw that you rooted but did you unlock the boot loader?
Click to expand...
Click to collapse
You're right...can't believe I missed that...never once is that mentioned...,
frog1982 said:
I saw that you rooted but did you unlock the boot loader?
Click to expand...
Click to collapse
Um, I kinda forgot that part.. my fault. I just unlocked the bootloader and I'm gonna give it another try.
UPDATE: Success!
I'm sorry guys thanks for all your help.
:victory::victory:
hi
my problem is
I tried to downgrade my phone
android 6 to 5
My phone was incomplete downgrade
And now when turned off and turned on
Stuck on the
{
"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"
}
Please tell me what is the alternative
No option is not enabled
no recovery
no Emergency Updates
only fastboot mod
the fastboot mode is worked
rezaghaedamini said:
the fastboot mode is worked
Click to expand...
Click to collapse
Take it to Huawei customer service center. I lost one of my phones coz it had the same problem. Tried everything but couldn't revive it.
Took it to a shop to repair and he messed it up.
Connect to pc or laptop and open command prompt to adb folder and type fastboot devices if devices detected then we proceed http://forum.xda-developers.com/general/general/guide-flash-variant-version-firmware-t3506404.
Krish93 said:
Connect to pc or laptop and open command prompt to adb folder and type fastboot devices if devices detected then we proceed http://forum.xda-developers.com/general/general/guide-flash-variant-version-firmware-t3506404.
Click to expand...
Click to collapse
My bad, should have asked him to do this first. Mine was error 3 and wasn't revivable.
This error is different. Thanks for the help.
You need to unlock your device.
https://www.gizdev.com/install-twrp-3-0-root-honor-4x-emui-4-0/
1-unlock your device
2-run bootloader
3-install twrp
4-extract the honor firmware
http://forum.xda-developers.com/honor-4x/how-to/roll-to-emui-cm13-honor-4x-che1-l04-t3507998
5-follow the instructions as above link.
Krish93 said:
Connect to pc or laptop and open command prompt to adb folder and type fastboot devices if devices detected then we proceed http://forum.xda-developers.com/general/general/guide-flash-variant-version-firmware-t3506404.
Click to expand...
Click to collapse
i did
My phone did not change
dopserver said:
You need to unlock your device.
https://www.gizdev.com/install-twrp-3-0-root-honor-4x-emui-4-0/
1-unlock your device
2-run bootloader
3-install twrp
4-extract the honor firmware
http://forum.xda-developers.com/honor-4x/how-to/roll-to-emui-cm13-honor-4x-che1-l04-t3507998
5-follow the instructions as above link.
Click to expand...
Click to collapse
my phone is unlocked
and All these things did
Did not alter
rezaghaedamini said:
my phone is unlocked
and All these things did
Did not alter
Click to expand...
Click to collapse
Connect your phone to PC and keep device manager opened and see if device manager registers your phone.
Report back please...
muradulislam said:
Connect your phone to PC and keep device manager opened and see if device manager registers your phone.
Report back please...
Click to expand...
Click to collapse
MY English is not good please tell me What do you mean
device manager to phone
or to pc
rezaghaedamini said:
MY English is not good please tell me What do you mean
device manager to phone
or to pc
Click to expand...
Click to collapse
Keep your PC device manager open and connect your phone to PC, does it register as a new device...
not big deal ,
Do The following
Install Fastboot files .
Download TWRP .
Connect Ur Device with Fastboot ,
Flash Ur TWRP Throw Fastboot .
Boot To TWRP
FLASH STOCK img Files One By one
This Step Not Recommended but also :
Throw Fast-boot Flash UR Stock .img files .
Romiui said:
not big deal ,
Do The following
Install Fastboot files .
Download TWRP .
Connect Ur Device with Fastboot ,
Flash Ur TWRP Throw Fastboot .
Boot To TWRP
FLASH STOCK img Files One By one
This Step Not Recommended but also :
Throw Fast-boot Flash UR Stock .img files .
Click to expand...
Click to collapse
tnk not work
rezaghaedamini said:
tnk not work
Click to expand...
Click to collapse
it should otherwise there is an wrong step u did ! .
rezaghaedamini said:
tnk not work
Click to expand...
Click to collapse
If your PC does not make a sound when you connect your phone to it then you have to first install drivers.
I am sure that is the case here, your PC is not recognizing your phone.
muradulislam said:
If your PC does not make a sound when you connect your phone to it then you have to first install drivers.
I am sure that is the case here, your PC is not recognizing your phone.
Click to expand...
Click to collapse
I have installed drivers
And when I connect the phone to the sound system
Only through the Fast Boot
rezaghaedamini said:
I have installed drivers
And when I connect the phone to the sound system
Only through the Fast Boot
Click to expand...
Click to collapse
So fastboot is working... Do you have an unlocked bootloader?
Fastboot screen is simple or with red error message?
muradulislam said:
So fastboot is working... Do you have an unlocked bootloader?
Fastboot screen is simple or with red error message?
Click to expand...
Click to collapse
yes i am bootloader unlocked
Both options
Red and simple
i can Write files via Fast Boot
and write android 4 5 6
5 file
boot
system
recovery
cust
userdata
and not work
and write twrp recovery
and not work
rezaghaedamini said:
yes i am bootloader unlocked
Both options
Red and simple
i can Write files via Fast Boot
and write android 4 5 6
5 file
boot
system
recovery
cust
userdata
and not work
and write twrp recovery
and not work
Click to expand...
Click to collapse
Make a dload folder in SD card And copy update.app of the latest firmware to it.
Then, flash only recovery and boot of the latest firmware for your phone. (Extracted from update.app which you copied to SD)
After flashing above image files, type
Fastboot reboot
Quickly disconnect from pc and press and hold power + vol up + vol down until screen turns on. Let go of power but keep other two pressed for five, six sec more.
Lemme know how it works.
if stock wont work then try custom rom , install custom recovery and install custom rom .
Yes, it is my own fault. I rooted yesterday, and installed a kernel today. All was fine until I tried to update to to the November update, never got that far.
I made sure to use the correct factory image for Magisk.
In adb i typed fastboot recovery, and my is now stuck on the google splash screen.
I can boot to fastboot, with the power button, and down arrow, and that's it.
fastboot devices, in adb does return the serial number.
I am unable to get beyond that. I know I'm softbricked.
Any suggestions would be appreciated.
Seems like you should be able to side load factory image
After about 20 tries, I was finally able to boot to recovery. I'm going to factory reset, and redo. Thanks for the help, though.
mimart7 said:
After about 20 tries, I was finally able to boot to recovery. I'm going to factory reset, and redo. Thanks for the help, though.
Click to expand...
Click to collapse
https://forum.xda-developers.com/pi...-10-q-root-t3996969/post80774791#post80774791
Here is an update:
When I run adb devices, the serial number is not returned.
When I run fast devices, the serial number is returned.
I have extracted all the files from the zip, for the image, there is no boot.sig, recovery.img, system.sig, or vendor sig.
{
"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"
}
View attachment 4873031
mimart7 said:
Here is an update:
When I run adb devices, the serial number is not returned.
When I run fast devices, the serial number is returned.
I have extracted all the files from the zip, for the image, there is no boot.sig, recovery.img, system.sig, or vendor sig.
Click to expand...
Click to collapse
In adb mode in the OS, try typing..adb kill-server...
Then allow your device to always communicate with your pc, your having a driver issue. Your readout for your factory image is correct. There is no recovery anymore, it's tied in with the boot.img
mimart7 said:
Here is an update:
When I run adb devices, the serial number is not returned.
When I run fast devices, the serial number is returned.
I have extracted all the files from the zip, for the image, there is no boot.sig, recovery.img, system.sig, or vendor sig.
Click to expand...
Click to collapse
@mimart7
If you booted fastboot mode, fastboot devices is all that is needed to insure your phone is communicating with your computer.
Are you using the latest SDK platform-tools 29.0.5?
If yes, is the Platform-tools, and the extracted factory image files in this folder C:\Platform-tools\New folder?
I've got it working, thanks to all.
mimart7 said:
I've got it working, thanks to all.
Click to expand...
Click to collapse
How did you git it working if you dont mind coming to talk to me please.
https://discord.gg/XnMeYF6
DemonicMurderer said:
How did you git it working if you dont mind coming to talk to me please.
https://discord.gg/XnMeYF6
Click to expand...
Click to collapse
Did you have:
USB Debugging enabled?
Do you have Platform Tools?
https://developer.android.com/studio/releases/platform-tools
When in fastboot, and your phone is attached to your computer, and you type fastboot devices in adb, do you get your the serial number of your phone?
I'm in this situation and yes I have the lastest platform-tools. I do get the serial number back when I type fastboot devices. My folder location is C:\Platform-tools
Caselka said:
I'm in this situation and yes I have the lastest platform-tools. I do get the serial number back when I type fastboot devices. My folder location is C:\Platform-tools
Click to expand...
Click to collapse
What situation? SDK Platform-tools r29.0.6?
What are you trying to do?
Homeboy76 said:
What situation? SDK Platform-tools r29.0.6?
What are you trying to do?
Click to expand...
Click to collapse
Yup SDK r29.0.6.
I was soft-bricked and stuck in a boot loop.
I managed to get to recovery mode but only by flashing all the files then holding the power button & volume up button.
Once in recovery, I tried a million things to figure out how to get it back to a clean slate.
After hundreds of tries, I managed to sideload flame OTA.
The phone's bootloader is now unlocked.
Now going to focus on what I did wrong originally when trying to get Magisk on the Pixel 4 :laugh:
Caselka said:
Yup SDK r29.0.6.
I was soft-bricked and stuck in a boot loop.
I managed to get to recovery mode but only by flashing all the files then holding the power button & volume up button.
Once in recovery, I tried a million things to figure out how to get it back to a clean slate.
After hundreds of tries, I managed to sideload flame OTA.
The phone's bootloader is now unlocked.
Now going to focus on what I did wrong originally when trying to get Magisk on the Pixel 4 :laugh:
Click to expand...
Click to collapse
Search the pixel 4 thread.
Homeboy76 said:
Search the pixel 4 thread.
Click to expand...
Click to collapse
All done. Managed to successfully complete it
stuck in fastboot
Caselka said:
All done. Managed to successfully complete it
Click to expand...
Click to collapse
hi im also stuck in fastboot but no serial coming up under fastboot devices. was doing a flash-all.bat when it stopped halfway through and has been stuck ever since. cant go into recovery or anything. Any help would be appreciated.
Hello
My phone damage
It comes to my that massege
the current image (boot/recovery) have been destoyed and can not boot.
please flash the correct image or contact customer service to fix it.
see pics
{
"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"
}
How I can fix it
I can't do any things , only restert and open thats list when i choose recovery mode it will come window error
You still have twrp/fastboot?
natedogg20050 said:
You still have twrp/fastboot?
Click to expand...
Click to collapse
now my phone only work 2 windows
If I select recovery mode it will restart again
Now I can't connect to bootloader
Does the far recovery mode work for you? If yes, then there is an opportunity!
Have you tried this instruction? If you enter recovery mode, then it will help 100%, try everything according to this instruction.[/QUOTE]
https://forum.xda-developers.com/re...ock-fastboot-flashable-images-realme-t4003107
Now this window not working with me
and also If i connect my phone on my computer not working with fastboot
C:\Users\M7mmd\Desktop\realme\platform-tools>fastboot --disable-verity --disable
-verification flash vbmeta vbmeta.img
< waiting for any device >
hey guy, don’t bother with your head after flashing the official firmware and that’s all.
avoid brick. otherwise I had a hard brick for such a situation, I had to turn in the service one and they did it to me, remember our brick will not brick in any way until there is no way out.
Gayrat1999 said:
hey guy, don’t bother with your head after flashing the official firmware and that’s all.
avoid brick. otherwise I had a hard brick for such a situation, I had to turn in the service one and they did it to me, remember our brick will not brick in any way until there is no way out.
Click to expand...
Click to collapse
I didn't understand what your meaning
Now , There is solve for this problem ?
does the recovery mode work for you at least ?? You can simply download and flash this firmware and that’s it. Версия 07 https://forum.xda-developers.com/re...ock-fastboot-flashable-images-realme-t4003107
when I choose ( Recovery mode ) the device restart again
aa .. almost forgot one more moment! But does it go into fastboot mode, does fastboot work, or does it still reboot?
Gayrat1999 said:
aa .. almost forgot one more moment! But does it go into fastboot mode, does fastboot work, or does it still reboot?
Click to expand...
Click to collapse
When I choose recovery mode Automatically reboot my phone
And When I connect my phone on computer not working Fastboot
then forgive me for your device in a brick, take it to an authorized service center.
Gayrat1999 said:
then forgive me for your device in a brick, take it to an authorized service center.
Click to expand...
Click to collapse
Now the problem is service center still not open on my country
Is there way to install Rom on my phone ?
This will help
https://youtu.be/4wsa81bG6II
rkmadotra said:
https://youtu.be/4wsa81bG6II
Click to expand...
Click to collapse
Hello
I'm to trying change my version cn to global
But some problems happened
now I installing last update for software global by trwp (Recovery) successful but when I restart my phone again go back to trwp window
And also I install cn version can't install with me and again my phone restart
I want it to work , I don't care if CN version or what over
Anybody have all the fills img
Recovery
Boot
System
Vbmata
Vonder
??
bumtab said:
Hello
I'm to trying change my version cn to global
But some problems happened
now I installing last update for software global by trwp (Recovery) successful but when I restart my phone again go back to trwp window
And also I install cn version can't install with me and again my phone restart
I want it to work , I don't care if CN version or what over
Click to expand...
Click to collapse
Did you format internal storage with twrp ?
rkmadotra said:
Did you format internal storage with twrp ?
Click to expand...
Click to collapse
I have a same problem,after i erase all data with yes from twrp,my phone only restar in OS without any posibility to go into fastboot.
"PS C:\adb> adb devices
List of devices attached
ce8bf9af recovery
they find phone,but when I try to flash over adb just folowing message:
PS C:\adb> fastboot flash vbmeta vbmeta.img
< waiting for device >"
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