Database Develop

[Unlocked Only][Release]CWM Recovery Mod for Atrix 4G 2011-06-30 updated again!

thread outdated ! please user romracer's http://forum.xda-developers.com/showthread.php?t=1204500
Hi ALL,
This is the recovery.img build for Unlocked AT&T Atrix 4G.
You can flash this direct to the recovery partition for a unlocked device, no more AC charger!
Thanks Koush and other devs who are working on the original cwm recovery.
enjoy porting CM7!
this is under developmet ,please use at your own risk! but every release will be tested first.if you like my work. buy me a beer
have fun.
Updated:GMT+8:00 06-30 11:20am
filename: recovery-en-goapk-0630-1029.zip
add backup and restore pds( backup tested,restore didnt test.)
add Internal SD card Support (nandroid and choose zip from internal sdcard)
should add a restart adb server int the menu in next version.
Latest Download:
View attachment recovery-en-goapk-0630-1029.zip
{
"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 Remove install_recovery.sh located in your /system/etc/ ,so that the recovery will not be overwrite to stock one.
GMT+8:00 2011-06-25-22:25 Update again:
Important Update!recovery-en-goapk-0625-2034.zip
fix wipe format and backup restore
latest: View attachment recovery-en-goapk-0625-2034.zip
GMT+8:00 2011-06-25 03:38 Update:
fix format data and cache
please update to latest build.
another fixed!
please update.
and every other thing should work as it should。
how to install:
Windows:
unzip recovery-en-goapk.zip to D:\
open a CMD in windows.
fastboot flash recovery D:\recovery-en-goapk.img
Linux:
unzip recovery-en-goapk.zip to you home
mot-fastboot flash recovery ~/recovery-en-goapk.img
mot-fastboot reboot
pics：
Downloads:
2011-06-24-16:10 GMT +8:00
View attachment recovery-en-goapk.zip
2011-06-25 03:38 GMT +8:00
View attachment recovery-en-goapk-0313.zip
HERE IS THE　EASY　GUIDE：thanks Paschalis !
I had the prev version of CWM, and i wanted to update to the latest, using moto-fastboot instead of fastboot..
It's very easy.. So i wrote a little guide.. Dont blame me.. Its for new guys like me!
Btw will any future update of CWM, have adb enabled?
eg If we messed up with framework or anything else can cause a soft-brick, then recover using backup files..
Step-by-Step
How to install on Windows with moto-fastboot
1) With Root-Explorer go to: /system/etc/ and remove: "install_recovery.sh" file
2) Download moto-fastboot.rar, and latest recovery recovery-en-goapk-0630-1029.zip
3) Extract contents of moto-fastboot.rar in C:\Windows,
and content of recovery-en-goapk-0630-1029.zip in C (for example).
4) Get your Atrix in FastBoot:
................................ a) Turn it off
................................ b) While turning it on, press VolumeDown key
................................ c) Press VolumeUp key
................................ d) Connect your Atrix to your PC using usb data cable
5) Open a cmd (Command Prompt)
6) Enter following cmd commands:
............. a) cd C:\
............. b) moto-fastboot flash recovery C:\recovery-en-goapk-0630-1029.img
............. c) moto-fastboot reboot
7) Thank Paschalis for this guide!
Click to expand...
Click to collapse
original post on http://bbs.goapk.com/thread-2874929-1-1.html
please include this info when you post this on other forums.

Holy freakin Hell!!! Thanks!!! Good to hear from ya!!!! Its like xmas around here in june!! LOL

Great to see this so soon. I cannot wait for a fully functional version! Glad to see you still lurking around here tenfar, thankyou for this, as well as koush and all the others (if any) involved in making this happen!

How To: Get into CWM Recovery
Using ADB:
- adb reboot recovery​
Using buttons:
- Hold down power, downward volume buttons until you see "Fastboot"
- Use downward volume button to click multiple times until you see Android Recovery
- Then, press the upward volume button​

Thanks! Tenfar excited to put it to good use!

omg today is going nuts! only if i could get gingerbread lol

Any chance for the source? Or at least say how you got it working?

could i unlock simlock my phone with flashing ur file?

lechicuong said:
could i unlock simlock my phone with flashing ur file?
Click to expand...
Click to collapse
No... 10char

i flashed this recovery via fastboot but any idea how to get in to recovery?

Not working for me.. keep getting "Failed to process command flash :recovery error (0x180002)....?

Daniel_GB said:
i flashed this recovery via fastboot but any idea how to get in to recovery?
Click to expand...
Click to collapse
hold vol down while powering on. press vol down to scroll the choices and vol up to select android recovery

rickriego said:
Not working for me.. keep getting "Failed to process command flash :recovery error (0x180002)....?
Click to expand...
Click to collapse
Don't shoot me if i'm wrong, but are you SURE you unlocked the bootloader?
I unlocked mine, but screwed a lot up, so i had to SBF flash... tried to run this and got the same error.... forgot to RE-unlock. Mine is rooted too (had to re-root), but idk if that is significant
hope this helps! =)

lol...positive..

Just to let you know I flashed the 1.8.3 sbf after unlocking and then tried to flash this and met with failure.
I then ran the unlock sbf again (only) and it flashed successfully. Perhaps flashing a previous sbf does "re lock" (at least partially) the phone?

rickriego said:
Not working for me.. keep getting "Failed to process command flash :recovery error (0x180002)....?
Click to expand...
Click to collapse
reflash the pudding sbf. I'm guessing you have flashed a different sbf since you unlocked
edit: NM slow typer lol

Bakano said:
Don't shoot me if i'm wrong, but are you SURE you unlocked the bootloader?
I unlocked mine, but screwed a lot up, so i had to SBF flash... tried to run this and got the same error.... forgot to RE-unlock. Mine is rooted too (had to re-root), but idk if that is significant
hope this helps! =)
Click to expand...
Click to collapse
i thought i read that we should still be unlocked after sbf flash..and i did flash back to 1.83..and rooted btw..
EDIT: just came up with "BATTERY TOO LOW TO FLASH"..maybe thats the issue..

rickriego said:
i thought i read that we should still be unlocked after sbf flash..and i did flash back to 1.83..and rooted btw..
EDIT: just came up with "BATTERY TOO LOW TO FLASH"..maybe thats the issue..
Click to expand...
Click to collapse
No I did the same thing and got the same error. you gotta reflash the unlock sbf to fix it. everyone is right.

You can enter recovery mode with "adb reboot recovery" too!

jruweaver said:
reflash the pudding sbf. I'm guessing you have flashed a different sbf since you unlocked
edit: NM slow typer lol
Click to expand...
Click to collapse
yep...flashed to 1.83 like you. i'm gonna charge up and try the steps u took..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:

[Q&A] TWRP for A11_CHL and A11_UL 32-bit only

Q&A for TWRP for A11_CHL and A11_UL 32-bit only
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for TWRP for A11_CHL and A11_UL 32-bit only. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

I think I have ROOT now, installed Su via Recovery. Awesome, thanks!:laugh:

I Can't Seem To Download The Recovery
I can't seem to download the recovery. can anyone help me with that? all im getting is the androidfiles logo.

I think i may have messed up here. I was in that crowd that got there recovery messed up with the 816 recovery. So my bootloader got relocked (before the custom recovery today) actually its been relocked for a while with tampered above it. Does that mean I'm screwed for getting TWRP on this thing. It still boots (thankfully) but it when I try to flash it says "remote signature verify fail". I'm guessing thats because its relocked. What do I do if there is anything i can do. I'm also doing this on a mac.

Reflash your UNLOCK_BIN.
Then Reboot phone.
Then flash custom recovery IMG
Then let Custom recovery install SU or have an SU.ZIP on your SD card to install.
Then install busybox, again best from a zip done inside recovery.
Need files posted let me know..
---------- Post added at 07:12 AM ---------- Previous post was at 06:54 AM ----------
Files for 510_Desire:
h**ps://***.mediafire.com/?mhjc61kyba1kmcz
Hope that helps..

Doesn't part of the unlock process require the stock recovery?

Unlocking phone only requires access to FASTBOOT, if you haven't damaged that, then you should be OK. Try flashing your unlock_code.bin again and see what happens.. heck you already flashed a recovery that wasn't for this device, so why be scared now
Put HTC Desire 510 into FASTBOOT mode:
Hold POWER + VOL Down to boot into HBOOT
Use VOL button to move to FASTBOOT and PRESS Power to select.
On your computer:
Open a command prompt (CMD.EXE), navigate to your FASTBOOT folder, with TWRP_2.8.1.0_A11.IMG (RENAMED to recovery.img) in the same directory-- connect your phone via USB, and type the following:
fastboot flash recovery recovery.img
Once it's flashed I can confirm you get SU installed, and can get busybox installed. Apps2SD works as well, so far. When I used HTC's Unlocker bin file, it demolished my stock recovery. It would not boot into recovery for anything. And this flashed flawlessly.

mixelpixx said:
Unlocking phone only requires access to FASTBOOT, if you haven't damaged that, then you should be OK. Try flashing your unlock_code.bin again and see what happens.. heck you already flashed a recovery that wasn't for this device, so why be scared now
Put HTC Desire 510 into FASTBOOT mode:
Hold POWER + VOL Down to boot into HBOOT
Use VOL button to move to FASTBOOT and PRESS Power to select.
On your computer:
Open a command prompt (CMD.EXE), navigate to your FASTBOOT folder, with TWRP_2.8.1.0_A11.IMG (RENAMED to recovery.img) in the same directory-- connect your phone via USB, and type the following:
fastboot flash recovery recovery.img
Once it's flashed I can confirm you get SU installed, and can get busybox installed. Apps2SD works as well, so far. When I used HTC's Unlocker bin file, it demolished my stock recovery. It would not boot into recovery for anything. And this flashed flawlessly.
Click to expand...
Click to collapse
Not working. when i get to the unlock token screen in fastboot it wants to enter recovery. That's what makes me think it needs stock recovery to wipe the device to unlock it. That's where it freezes. It says "Entering Recovery... and at the bottom it say this build is for development purposes only" overlaying the fastboot unlock screen. if i press a button the screen gets all static. and Restarts in fastboot still locked. if i restart it without it plugged in, it boots up normally.

Did you try using the original unlock_code.bin they sent you? You shouldn't need a new token and go through all of that... I believe FASTBOOT is a separate entity from recovery, so it's function shouldn't be affected.

mixelpixx said:
Did you try using the original unlock_code.bin they sent you? You shouldn't need a new token and go through all of that... I believe FASTBOOT is a separate entity from recovery, so it's function shouldn't be affected.
Click to expand...
Click to collapse
1. My bootloader got relocked while having the 816 recovery from the how to that used to be in the 510 forum.
{
"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"
}
2. I put in the command like I did before, I still had the unlock file from HTCDev
3. After selecting yes and confirming I get this screen. and its froze there.
4. If i hit the power button on that screen it just vibrates, if i hit a volume key, i get static and then it reboots normally and its still locked.

mixelpixx said:
Unlocking phone only requires access to FASTBOOT, if you haven't damaged that, then you should be OK. Try flashing your unlock_code.bin again and see what happens.. heck you already flashed a recovery that wasn't for this device, so why be scared now
Put HTC Desire 510 into FASTBOOT mode:
Hold POWER + VOL Down to boot into HBOOT
Use VOL button to move to FASTBOOT and PRESS Power to select.
On your computer:
Open a command prompt (CMD.EXE), navigate to your FASTBOOT folder, with TWRP_2.8.1.0_A11.IMG (RENAMED to recovery.img) in the same directory-- connect your phone via USB, and type the following:
fastboot flash recovery recovery.img
Once it's flashed I can confirm you get SU installed, and can get busybox installed. Apps2SD works as well, so far. When I used HTC's Unlocker bin file, it demolished my stock recovery. It would not boot into recovery for anything. And this flashed flawlessly.
Click to expand...
Click to collapse
when you change the recovery.img , try dragging the recovery.img to cmd.exe. so it would go like this, fastboot flash recovery ( drag the recovery img. you just made) and you are good to go. dont forget to check your work when you are done pushing the recovery.

smiley45 said:
when you change the recovery.img , try dragging the recovery.img to cmd.exe. so it would go like this, fastboot flash recovery ( drag the recovery img. you just made) and you are good to go. dont forget to check your work when you are done pushing the recovery.
Click to expand...
Click to collapse
Thanks for the suggestion guys but its not going to work for me. I can't even get my bootloader unlocked. This has been the most frustrating, P.O.S. letdown of an Android I have ever purchased. I just want throw this phone.
I spend months waiting for root and recovery for this phone thinking it was 64 bit. I find a write up claiming that the 816 recovery works with the 510. Take it back to best buy when i find out that its not 64 bit. They try to wipe which subsequently relocks it. Now i can't even root when a working root arises.

Tethering ?
Does the kernel and Rom have to be created before I can tether the phone ? I ask this because I know that for my wifes S3 I found a zip to install with recovery that let me tether the phone. It's probably a stupid question to ask but the reason I won't activate my Desire is because we use it for the kids to watch movies and such. I know that her ROM is the original one rooted and with custom recovery but just the zip for tethering it. I'd appreciate any input in this area. Thank you.

Elithefly said:
Does the kernel and Rom have to be created before I can tether the phone ? I ask this because I know that for my wifes S3 I found a zip to install with recovery that let me tether the phone. It's probably a stupid question to ask but the reason I won't activate my Desire is because we use it for the kids to watch movies and such. I know that her ROM is the original one rooted and with custom recovery but just the zip for tethering it. I'd appreciate any input in this area. Thank you.
Click to expand...
Click to collapse
You can tether in Settings > More > Mobile network sharing. No root even required.

dipspit said:
You can tether in Settings > More > Mobile network sharing. No root even required.
Click to expand...
Click to collapse
Yeah, I got that but I don't have that plan with my carrier and don't really have too. My other phone is running Pac 4.4.4 or CROM depending on which one I have installed. That was the kind of situation I was looking for. Built in or a zip I could install .

I can make a zip to unlock tethering natively for cricket users.

Having trouble with the partitioning
Thanks a lot for the recovery image. I've got the phone rooted, and I'm in the process of partitioning my SD card so I can move apps over (this is also my first rodeo).
I used the partitioning tool in the recovery, but regardless of the size I tell it, I get the message saying it won't work because the swap and ext combined size is bigger than the card. It's a 16G card, and I'm setting swap to 0, and I've tried everywhere from 512 to 1024 for the ext size (based on a friend's recommendation).
Am I doing something wrong? I got my 510 from Virgin Mobile in the US.
Thanks for the help!
-jason

It's a bug in twrp. I use mini partitioning tool and stick my sd card in a reader.
Also you need to be s-off for this to work. Your links 2sd or your apps2sd will fail until s-off for this device is found.

any news on recovery for 64bit version?

HTC Desire 510
Anyone know if there is a recovery for 64 bit yet?

Installation by MIUI Flash Tool is going on forever

Hello, my phone is stuck in Fastboot mode (rebooting does not work, it will always boot into fastboot mode) so I just followed this guide to flash a new ROM: https://c.mi.com/oc/miuidownload/detail?guide=2
But I am wondering, why the installation is still going on after over 10min. - What is wrong?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

After trying it again:

It is just stuck forever and I do not know why, I do not get out of fast boot mode and I really do not know what to do now.
Like doesn't the "status" say something what is wrong here? I cannot identefy it, but has anyone enough experience with it and maybe experienced my issue already?

Try flash non-official rom via recovery (twrp). After successful flash, launch system. Then, try flash latest stable via fastboot (do not use FLASH-AND-LOCK, use it only after successfully flashing like flash, check if everything is ok and then flash it again and lock).

I cannot enter recovery, I am stuck in a Fast boot loop. The phone won't let me get into recovery mode.

So flash TWRP in fastboot mode.
And you could try to flash another ROM because "echo Missmatching image and device"

The name of your directory path should not include any space. Replace the spaces with underscores, dashes or just remove them.
From your screenshot, you selected clean all and lock. Try unlocking the bootloader again.
Sent from my MI 9 using Tapatalk

Thanks, but the thing is I fixed all those things already as my last picture shows: https://img.xda-cdn.com/5kNbM-6ZvzA8Jvc_Fc-qUwGIG-Q=/https://i.imgur.com/ZOhtier.png
@Tomcar do you mean 'fastboot flash recovery name.img' ? That does not work, it still boots me into fastboot mode everytime I try to get into recovery mode.

Shure, because you are locked again

I fixed the problem. I just downloaded a newer version of Mi Flash and now I have the newest version installed. So the plan is to install a new custom rom now.
Why is wipe system not recommended to do?
And do I have to "wipe internal storage"?

I really do not understand.. Now as I sad above I have the newest version installed and the phone is unlocked too!
When I go into fastboot mode and do "fastboot flash recovery twrp.img" it works, but when I boot into recovery mode with volume UP and power button the old recovery is still there.
What am I missing out here?

hallohallo222 said:
I really do not understand.. Now as I sad above I have the newest version installed and the phone is unlocked too!
When I go into fastboot mode and do "fastboot flash recovery twrp.img" it works, but when I boot into recovery mode with volume UP and power button the old recovery is still there.
What am I missing out here?
Click to expand...
Click to collapse
Try after "fastboot flash recovery twrp.img"
"fastboot boot recovery twrp.img"
Once you do this, the recovery should stay permanently there.
Dont know why, but this was working for me.
(I hate this phone, too many strange things with it)

On my Mi 9, what I did to make TWRP stick was to press vol up + power right after flashing the recovery, to boot into TWRP.
Sent from my MI 9 using Tapatalk

sangbuana said:
On my Mi 9, what I did to make TWRP stick was to press vol up + power right after flashing the recovery, to boot into TWRP.
Sent from my MI 9 using Tapatalk
Click to expand...
Click to collapse
You my friend are a genius, thanks for the help. That worked!
abocksberger said:
Try after "fastboot flash recovery twrp.img"
"fastboot boot recovery twrp.img"
Once you do this, the recovery should stay permanently there.
Dont know why, but this was working for me.
(I hate this phone, too many strange things with it)
Click to expand...
Click to collapse
Thanks, this did not work somehow the boot command did not get recognized: "C:\Mini ADB and Fastboot>fastboot boot recovery twrp.img
fastboot: error: cannot load 'recovery': No such file or directory"

I was facing the same issue. I stopped the flashing. Copied manually the recovery.img file that came with the flash tool, and flashed the original recovery manually, cause i had it on a customer recovery. Then i tried again, it showed a more meaningful error, basically the path of the folder we're flashing can't have spaces. moved the folder under C: and tried again.. all worked!!

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