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:
Related
Hello all.
I wanted flash my phone with CM recovery, but when am writing the command:
cd\
cd "Program Files\Droid Expolrer\SDK\tools"
fastboot flash recovery recovery.img
my PC just freezes nothing happens.
When I connected my phone with PC the first time in Fastboot Mode I had to install the drivers and I did, take a look:
{
"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"
}
So I thought that I have my connection during flashing, but I found something weird just today.
There is a screen with connected phone:
device not found, but in the end it restarts my phone - WEIRD
There is a screen without phone:
that is normal
So what is the problem my PC doesn't see my phone when am typing:
fastboot flash recovery recovery.img
but next time when am typing fastboot reboot or erase data/cache it sees my phone correctly and it does finalize my commands...
wtf
when you want to check that.. if phone is connected to fastboot(not adb shell):
Code:
#fastboot devices
and when fastboot device connected, appears something that:
Code:
???? Fastboot
You can follow my log below:
And am sure that my ROM is supporting Recovery
ZduneX25 said:
You can follow my log below:
And am sure that my ROM is supporting Recovery
Click to expand...
Click to collapse
okay... ..
this is your device there:
Code:
? fastboot
got it workin on sister's computer ?
try this command too (ps. put recovery.img to android-sdk/tools folder):
# fastboot boot recovery.img
it just boots up recovery, but actually it's not installing recovery to phone
She will back home this Sunday.
Am making the video for you Uploading in progress - not so fast. Gonna share in about 1 hour.
I hope I can upload 68mb files on youtube wish me luck
Here you go:
http://www.youtube.com/watch?v=YfqHF8Wog9M
ZduneX25 said:
Here you go:
http://www.youtube.com/watch?v=YfqHF8Wog9M
Click to expand...
Click to collapse
woot
that's a big problem with usb or something.
have you tried with diffirent usb ports?
when computer keeps restarting, i think that theres some conflict with usb-adb drivers...u can try to reinstall both....usb drivers and phone drivers
It is restarting only with this command:
#fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Any other command works perfect...
I was doing wipe via fastboot:
#fastboot erase userdata
#fastboot erase cache
Click to expand...
Click to collapse
and it has been working.
I've done root via adb either w/o problems.
ZduneX25 said:
It is restarting only with this command:
Any other command works perfect...
I was doing wipe via fastboot:
and it has been working.
I've done root via adb either w/o problems.
Click to expand...
Click to collapse
try to replace with my fastboot.exe (maybe your fastboot.exe file is corrupted)
Very same file, nothing has changed.
ZduneX25 said:
Very same file, nothing has changed.
Click to expand...
Click to collapse
sorry can't help then...u can try via adb shell again...maybe you got some luck and get it workin.
Guess what buddy, am tired of this and mad :/ I will try to figure it out on my Sis's PC.
ZduneX25 said:
Guess what buddy, am tired of this and mad :/ I will try to figure it out on my Sis's PC.
Click to expand...
Click to collapse
ok, let me know then.
Guess what just happened bro. I found nice pack for recovery and for users without sdk. And I tried on PC in my dad's office. And it works
__________
Written with Tapatalk on GT540
Finally
Good for you ! But I'm still confused by one question, how can your PC restart after fastboot flash command :S (okay... mine cmd freezes on fastboot flash...but yours restarts) ?
My PC does what he wants. I have recovery wow, but after a couple restarts I can't turn on my PC now hehe.
__________
Written with Tapatalk on GT540
maybe fresh windows installition helps !?
I won't try I will leave it for the night. Should work tomorrow morning. Like a said, this is very strange computer.
__________
Written with Tapatalk on GT540
ZduneX25 said:
I won't try I will leave it for the night. Should work tomorrow morning. Like a said, this is very strange computer.
__________
Written with Tapatalk on GT540
Click to expand...
Click to collapse
yeah, but i'm worked on computers about 6-7 years... and this "error" what u have is very strange.. i'm telling that u have some big problem with usb or some conflict there.. i'll hope that it is only problem with ur computer...
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..
So in preparation for the kitkat update, I did the following steps:
unrooted within superuser app
flash stock recovery
flash stock boot.img
flash stock system.img
Once I rebooted I downloaded the OTA and tried to install. Now, after that, I wasnt really sure what happened on the phone, as I passed the time by watching a youtube video on my computer. However, I looked back down, and it was inside the bootloader, giving a partition failure of some sort. And when I tried to flash anything, it gave a remote failure error. It won't boot into anything, and it says the device is locked. Can't do mfastboot oem get_unlock_data either, literally nothing but fastboot reboot works
do i have a $650 paper weight on my hands?
{
"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"
}
Fixed it! See the post at the very bottom of this page for the solution!
i would use RSD lite to get back to the latest 4.2.2
mj0528 said:
i would use RSD lite to get back to the latest 4.2.2
Click to expand...
Click to collapse
it won't boot at all
Well fastboot starts at least. If you try to reload stock firmware (4.2.2) using rsdlite(not fastboot from a command line) which error do you get?
Steve-x said:
Well fastboot starts at least. If you try to reload stock firmware (4.2.2) using rsdlite(not fastboot from a command line) which error do you get?
Click to expand...
Click to collapse
My device isn't showing up under rsdlite 6.1.4 at all
Sadly then I'm leaning towards it being a pretty looking brick. I've had many flash failures while experimenting with my XT1058s but I have never tried any custom recoveries so they were always recoverable with fastboot and rsdlite.
Hopefully someone else has some suggestions for you to try.
I flashed system.img, recovery.img, and boot.img from the original sbf file. not from the first OTA. and then the phone seems to have locked itself
alex94kumar said:
I flashed system.img, recovery.img, and boot.img from the original sbf file. not from the first OTA. and then the phone seems to have locked itself
Click to expand...
Click to collapse
Had you taken the first OTA already? If you had done that, you should have flashed these files from the new SBF file....
So, when you are in fastboot mode, your device is no longer getting recognized from fasboot command line? What does fastboot devices show?
tejaskary said:
Had you taken the first OTA already? If you had done that, you should have flashed these files from the new SBF file....
So, when you are in fastboot mode, your device is no longer getting recognized?
Click to expand...
Click to collapse
Ah. there's my problem. I flashed the files from the factory moto X.
And the device is recognized in fastboot, I can send it commands, it's just that none of them except fastboot reboot actually work
alex94kumar said:
Ah. there's my problem. I flashed the files from the factory moto X.
And the device is recognized in fastboot, I can send it commands, it's just that none of them except fastboot reboot actually work
Click to expand...
Click to collapse
Can you try these commands and see if anything changes?
fastboot oem fb_mode_clear
fastboot reboot-bootloader
After that can you try any of the fastboot flash commands using the new SBF file?
It worked!!! Oh my god thank you so much! You are a life saver!!
delete
alex94kumar said:
It worked!!! Oh my god thank you so much! You are a life saver!!
Click to expand...
Click to collapse
Glad it worked for you !! Enjoy with 4.4...
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.
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!