Database Develop

stuck at fastboot

Hey i am stuck in fastboot (going for a week now) and i kinda think it's dead i did that full wipe script and now it won't boot into anything i can do bootloader (my bro told me it can be flashed by there but i don't even know also i can't get into hboot due to the camera button being stubborn) so might as well ask here since he's at my cousins house for now and also how can i flash zip files? like the kind that aren't .img? just for details every time i try to flash via fastboot it either says unknown partition or cannot load blah.img maybe it's something i did wrong? i got adb/fastboot setup with the sdk and stuff but that's as far as i can get .
also i can't use adb (should be obvious by now).

can you access recovery mode? holding home+power?

I can try but don't guarantee success in doing so because of something i did in fastboot by mistake in trying to fix it ( ) unless there's a way of re flashing ra's rom or something there's no way i can get recovery to work again.
edit why don't they have those windows to phone flasher just like the hd2's have them that way i would have had it fixed by now .

Probably you should read a bit in this post.
If you are in fastboot, you can do almost everything with your phone.
1.
Code:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
and your phone is clean.
2.
Code:
fastboot flash recovery <recovery.img>
and you have a working recovery.
3. you can decide how to continue ...

whenever i try to flash it(at last step at the instructions at top), it keeps saying error: cannot load 'Recovery.img' file ,weird , i am using ra's recovery has recovery.img , don't know why it's not letting me flash it
edit even has the original name it won't load

you need to have it in the same directory from where you are calling the fastboot command, i.e.
you are on c:\ -> recovery.img must be located on c:\
otherwise you need to give the full path to your recovery.img, i.e.
Code:
fastboot flash recovery c:\recovery.img

AndDiSa said:
you need to have it in the same directory from where you are calling the fastboot command, i.e.
you are on c:\ -> recovery.img must be located on c:\
otherwise you need to give the full path to your recovery.img, i.e.
Code:
fastboot flash recovery c:\recovery.img
Click to expand...
Click to collapse
Because a button is not good enough here you go
{
"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"
}
for showing me the way also i'v been like this since last week reason i didn't ask in the first place is because i thought it was already answered already and i searched but couldn't find the right answer
but thanks to a guru like you i fixed it .
Edit - testing phone , seems to be doing something at the g1 screen.
Edit 2 - i think it might be ... bricked , hold on.
Edit 3 - got it into recovery lets see from here.
**** it tomorrow i get a new phone anyways time to put this demon to sleep
ok i am not going anywhere can't get lift off .

i have amonra recovery in a zip file if you can flash it via fastboot?

I can try that but if i can get into fast boot (is it the little balltracker thingy and the power button? if so i think my fastboot is broken because it just shows a blue light with no signal of the screen on )
What i have try'ed is that wipe script ohsaka-super-wipe <- and i am trying to get SenseLX v3.1 to run but all my attempts just lead me back to the recovery screen for some weird reason
also don't know if this info will help at all but i got a 16gb sdcard and getting another one soon just hope it's better class
Hold on let me see something
also i flashed my hboot alot of times so maybe it's something with that.

well it's hboot mode but different... hboot is used to flash .img files.. fastboot is the same but diff button to power on and as long as you have fastboot drivers installed you can flash zip files via fastboot, power on device by holding back+power
here's a guide to install adb/fastboot driver on windows vista/7 if thats what you have...
http://forum.xda-developers.com/showthread.php?t=1124916
EDIT: o wait so you do have recovery? you said after trying to install rom it brings you back to recovery?
what radio/spl do you have? you need 2708/2825 & 0013d
here is guide to install radio and spl
http://forum.xda-developers.com/showthread.php?t=1098899

ldrifta said:
well it's hboot mode but different... hboot is used to flash .img files.. fastboot is the same but diff button to power on and as long as you have fastboot drivers installed you can flash zip files via fastboot, power on device by holding back+power
here's a guide to install adb/fastboot driver on windows vista/7 if thats what you have...
http://forum.xda-developers.com/showthread.php?t=1124916
EDIT: o wait so you do have recovery? you said after trying to install rom it brings you back to recovery?
what radio/spl do you have? you need 2708/2825 &1. 0013d
here is guide to install radio and spl
http://forum.xda-developers.com/showthread.php?t=1098899
Click to expand...
Click to collapse
yep i have it, also following guide gonna report back in a few minutes
Edit - i got both hboot0013d-signed.zip and radio-2_22_27_08-signed.zip in my sdcard meaning i might have flashed them already so i don't see why it should be taking me to recovery
edit 2 bad hboot / E:missing bitmap Progress_empty/fill code -1 2x didn't wanna risk the real brick so i didn't install it.
Edit 3 E: - blah blah blah failure at line 3
well its' back to the drawing board for me..
and well fastboot don't work (camera button + power button don't do anything)
Now would'ya look at that it started working to an htc screen doing something alright
it hates me i swear.

lol when you get to the hboot or fastboot screen what does your device say? can you find out what radio and spl you have?

ldrifta said:
lol when you get to the hboot or fastboot screen what does your device say? can you find out what radio and spl you have?
Click to expand...
Click to collapse
Fuucucuc my luck was supposed to get a new phone today
also
NO i can't find out what radio/spl i have i can flash but it will give me a E:/hboot error

well you find out by powering on device in hboot mode, holding camera+power or even try back+power

Dream100 PVT 32b
HSPL.10.95.3000
CPLD - 4
Radio -2.22.28.25
thank you for the info since the camera button was be stubborn
i see i didn't have hboot maybe that's why it's was giving me errors'
----
got it back to default
-----
goddam my luck sucks almost had another one in the hook today (samsung captivate)

Phone Bricked after JB update

Hi, i installed the last JB OTA update yesterday, and it worked great, but then i would install lum's roms, and i did it wrong. Since i can't boot, it shows the Motorola logo for about 30 sec, then i got blackscreen. All i can do is boot in motorola's recovery (not safestrap), or AP Flashboot.
Is there a way to restore my phone ?
Sorry for my poor english and thanks for your help.

Lightofdark said:
Hi, i installed the last JB OTA update yesterday, and it worked great, but then i would install lum's roms, and i did it wrong. Since i can't boot, it shows the Motorola logo for about 30 sec, then i got blackscreen. All i can do is boot in motorola's recovery (not safestrap), or AP Flashboot.
Is there a way to restore my phone ?
Sorry for my poor english and thanks for your help.
Click to expand...
Click to collapse
What exactly did you do? Did you flash Lum_UK's ROM over top of your stock ROM? And you can't you still get in to safestrap recovery? If that's the case you may be hosed until JB fastboot files come out. You could try to reflash the JB OTA in stock recovery. I have a feeling it will fail since your stock system has been modified but worth a shot.

kwyrt said:
What exactly did you do? Did you flash Lum_UK's ROM over top of your stock ROM? And you can't you still get in to safestrap recovery? If that's the case you may be hosed until JB fastboot files come out. You could try to reflash the JB OTA in stock recovery. I have a feeling it will fail since your stock system has been modified but worth a shot.
Click to expand...
Click to collapse
I replaced the system folder on my phone by the one of lum's rom with file manager into safestrap recovery (not smart i know). And I already try to reflash the update in the recovery but it didn't work. I'll have to wait untile JB fastboot files comes out and use my old Xperia mini pro
EDIT : Ok, i can update my phone to JB with recovery, but then the phone boots on AP flashboot automaticaly and says "flash failure"

You deleted the stock ROM and copied over the files from my ROM by hand?
That's not going to work as it will also delete safestrap recovery as you have found out.
The JB OTA update won't install as it is a patch that only applies to the stock ICS ROM.
Attempting to downgrade to the ICS fastboot files will perma-brick your phone. Some partitions are safe to flash, some can only be upgraded. Fortunately the system partition is flashable without that nasty issue!
However I've had a look at how Droid4utility actually flashes them and it seems it is possible to flash just the system partition in fastboot using:
moto-fastboot flash system.img
I have dumped the system partition from my phone and am currently uploading it. It will take an hour to upload and I'm out for the afternoon. Edit: It's here: http://d-h.st/oXt
You'll need Fastboot and the Motorola USB drivers
Install the USB drivers.
Decompress the system.img file you downloaded. Put it in the same directory as moto-fastboot.exe.
Ensure the battery in your phone has lots of charge.
Boot the phone into fastboot by holding down both volume buttons and pressing the power button.
Choose fastboot by pressing the vol down button until fastboot is highlighted, then press vol up.
Connect your USB cable.
Run moto-fastboot flash system.img
Run moto-fastboot reboot
Note: I have not tried this on my own phone, and I hope I never have to. It should work in theory.

when ever i have used moto-fastboot, i had to use 'moto-fastboot.exe' to get it to work
Sent from my Clear using xda premium
---------- Post added at 11:33 AM ---------- Previous post was at 10:38 AM ----------
not sure what exactly what you will need to flash for jellybean to unbrick
download
update.zip for your device and system version
moto-fastboot.exe mediafire
instructions
1. Enter android recovery and do a wipe data/factory and cache
2) Then reboot device to fastboot mode.(make sure to have all motorola drivers installed on your PC)
3) move the update Zip and the MOTO-FASTBOOT to a folder (ex. c:/Root)
4. unzip files
5) Open the CMD, and enter the these commands.
cd/
cd c:root
moto-fastboot.exe flash system system.img
moto-fastboot.exe reboot
also try renaming patch/boot.img.p to boot.img
moto-fastboot.exe boot boot.img
moto-fastboot.exe reboot
do not let battery die, phone requires software to charge battery,
if battery dies you will need a
TBH’s Motorola Programing Cable

The jellybean fast boot files are not available yet, but from the description of the fault it would seem that only the system partition is bricked.
Easiest way to tell is if the phone still charges. If it does then the boot.img is fine and you should leave it well alone. Just flash my system.img and you should be good to go.
If the phone doesn't charge then switch it off and wait for the jellybean fast boot to turn up, do not switch it on again until it does.
Please let us know how you got on.

Lum_UK said:
The jellybean fast boot files are not available yet, but from the description of the fault it would seem that only the system partition is bricked.
Easiest way to tell is if the phone still charges. If it does then the boot.img is fine and you should leave it well alone. Just flash my system.img and you should be good to go.
If the phone doesn't charge then switch it off and wait for the jellybean fast boot to turn up, do not switch it on again until it does.
Please let us know how you got on.
Click to expand...
Click to collapse
How can i know if the phone does charge or not ?

turn off phone connect to wall charger, if you get battery charging screen your good
if not it's not charging
if phone will not turn off, hold volume down and power for 15-20 secs

sd_shadow said:
turn off phone connect to wall charger, if you get battery charging screen your good
if not it's not charging
if phone will not turn off, hold volume down and power for 15-20 secs
Click to expand...
Click to collapse
when i plug the cable it automacialy boot in AP fastboot, it doesn't seems good

what does it say in ap fastboot.?
AP Fastboot Flaash Mode (S)
0A.74....

Well annoyingly, that file I was trying to upload for you... Windows 8 decided to go into sleep mode before it had finished uploading, starting again.
I'm also happy to try and dump any other partitions that may help, if someone can tell me how to do it.

sd_shadow said:
what does it say in ap fastboot.?
AP Fastboot Flaash Mode (S)
0A.74....
Click to expand...
Click to collapse
AP Fastboot Flash Mode (S) (Flash Failure)
0A.77

does android recovery have, this phone has been rooted code
qe 1/1
Click to expand...
Click to collapse
if not, you could try taking to verizon store, and tell them the new update bricked your phone
they will likely have to send it to get repaired, don't know if any verizon stores flash phones anymore
{
"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"
}

Well the system image is finally uploaded if you want to try it
http://d-h.st/oXt

sd_shadow said:
does android recovery have, this phone has been rooted code
if not, you could try taking to verizon store, and tell them the new update bricked your phone
they will likely have to send it to get repaired, don't know if any verizon stores flash phones anymore
Click to expand...
Click to collapse
Thanks for your advice, but I live in France, and there is no Verizon store here.

Your options now are:
1) Try flashing the System.img I uploaded, it might work, it might not
2) Wait until a full fastboot image comes out and then flash that.

Lum_UK said:
Your options now are:
1) Try flashing the System.img I uploaded, it might work, it might not
2) Wait until a full fastboot image comes out and then flash that.
Click to expand...
Click to collapse
Well, i flashed the system.img (thanks a lot for the update btw), and now the phone boots on AP Fastboot with "(boot failure), with at the botom of the screen i've got these line :
"Invalid CG OTV (CG:system): Invalid SP Data
Invalid CG HAB (CG:system, status: 0X0056)
Invalid CG OTV (CG:system)"

Lightofdark said:
Well, i flashed the system.img (thanks a lot for the update btw), and now the phone boots on AP Fastboot with "(boot failure), and a the botom of the screen i've got these line :
"Invalid CG OTV (CG:system): Invalid SP Data
Invalid CG HAB (CG:system, status: 0X0056)
Invalid CG OTV (CG:system)"
Click to expand...
Click to collapse
Well it was worth a try. Now you'll just have to turn it off and hope the fastboot files show up soon

ok, so I'll wait. Anyway, thanks a lot for your help and your time.

Hello,
I was lead here because I'm having a similar problem... though not nearly as bad as the OP, it would seem. I managed to brick my system partition by trying to restore a nandroid of a working JB system partition in safestrap to stock slot to resolve some other errors in the install precipitated by a bad restore from Titanium.
Good news is that safestrap still works, and I can boot to any other slot... just not stock. When trying to boot stock, after the safestrap screen, I just get a black screen... it makes the *droid* sound, but screen stays black and nothing happens. No logo or OS appears.
I'm wondering if it might be worth a try to flash your system.img, or if I should leave it alone and run on safestrap until fastboots show up (which is hopefully soon)?
Thanks!

How to flash CWM Unoffical???

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:

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?

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