Database Develop

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?

Verity mode is set to disabled - remove message

Hi, this is my firs post, I hope to be posting in the right place.
I recently unlocked the bootloader and did the root, and everything worked perfectly, however, when I started the device, the message "Verity mode is set to disabled" appears, and although not influencing usability is very annoying.
Can someone give me a hint how to remove this message?
I already tried some of commands via fastboot like:
fastboot oem lock
fastboot enable dm verity
fastboot oem enable_dm_verity
Thank you all for your help
{
"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"
}

Have the same problem is it possible to reactivate it?

same problem on moto X4! any news?

Im looking for some solution to this issue.

prognpunk said:
Im looking for some solution to this issue.
Click to expand...
Click to collapse
Have you tried:
https://forum.xda-developers.com/moto-z4/help/z4-boot-logo-animation-t4043957

kewlzter said:
Have you tried:
https://forum.xda-developers.com/moto-z4/help/z4-boot-logo-animation-t4043957
Click to expand...
Click to collapse
This will not work. The text is appearing on top of logo. If you change logo text will be appear on it too.

QkiZMR said:
This will not work. The text is appearing on top of logo. If you change logo text will be appear on it too.
Click to expand...
Click to collapse
Hmmm. I was talking about the last two replies.
The ones about boot signature. Maybe this tool and method could be adapted.

I read this thread that you mention but still text "Verity mode is set to disabled" will overlap bootpicture. Another thing is that MotoLogoEditor can edit only contents of logo partition and this "Verity..." text appears on bootpicture which is not in logo partition. Bootpicture is /system/media/bootanimation.zip. I think that there's no simple way to remove this text.

On my Moto G6 Plus the issue disappeared after flashing boot.img from Oreo, however, I cannot guarantee that it works on Moto Z3 Play.

daniel.smith said:
On my Moto G6 Plus the issue disappeared after flashing boot.img from Oreo, however, I cannot guarantee that it works on Moto Z3 Play.
Click to expand...
Click to collapse
You mentioned the wrong file. The right file is "bootloader.img" of oreo rom
Command: fastboot flash bootloader bootloader.img
Thank you. Work on my G6 Plus

jamesjunn said:
You mentioned the wrong file. The right file is "bootloader.img" of oreo rom
Command: fastboot flash bootloader bootloader.img
Thank you. Work on my G6 Plus
Click to expand...
Click to collapse
i have a Moto Z3 Play
i have flashed the "bootloader.img" file and it didn't remove de the message
i have flashed the "boot.img" file and it removed the message but i cannot boot anymore (i'm on lineageOS)
so i guess this trick only work with the official ROM

nononymous said:
i have a Moto Z3 Play
i have flashed the "bootloader.img" file and it didn't remove de the message
i have flashed the "boot.img" file and it removed the message but i cannot boot anymore (i'm on lineageOS)
so i guess this trick only work with the official ROM
Click to expand...
Click to collapse
You need to put the bootloader or boot file inside the rom folder, replace the previous files and flash the rom completely.

Stuck in fastboot

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.

Mi a2 stuck on twrp screen

Hello there
I think i did somethinh wrong while trying to install twrp. Now when it boots it stays stuck on twrp screen, i cant switch it off. If i try, it will boot again on twrp screen. But i can boot it on fastboot mode.
I tryed with adb commnds to reinstall twrp but it does not recocnize dhe device when the phone is in fastboot mode.
If i boot the phone on the stuck twrp screen it is recognized by adb but it does not executes any command.
Eventually i thought trying to clean flash the stock rom will fix everything and i can try again with a fresh start. But the mi flash gives error,; flashing is not allowed for critical partitions.
The bootloader is unlocked.
Your browser is not able to display this video.

Try flashing your original boot.img (that worked with your current ROM version) back to the device from Fastboot.

Andrologic said:
Try flashing your original boot.img (that worked with your current ROM version) back to the device from Fastboot.
Click to expand...
Click to collapse
Thnx for the suggestion. But as i said the phone does not respont to adb commands.

biqe said:
Thnx for the suggestion. But as i said the phone does not respont to adb commands.
Click to expand...
Click to collapse
Not adb. You need to be in bootloader mode with Fastboot access to be able to flash boot back. Power up the device in bootloader mode with the vol+power buttons and confirm that your device has Fastboot access (e.g 'fastboot devices' returns your device id). Flash your boot from there. If Fastboot access is impossible, it's a bigger issue but try that first...

Andrologic said:
Not adb. You need to be in bootloader mode with Fastboot access to be able to flash boot back. Power up the device in bootloader mode with the vol+power buttons and confirm that your device has Fastboot access (e.g 'fastboot devices' returns your device id). Flash your boot from there. If Fastboot access is impossible, it's a bigger issue but try that first...
Click to expand...
Click to collapse
When i try vol+power it boots on twrp and stays like that
{
"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. It loks like using adb was the problem. But using the platform tools i could execute comands and i fixed the issue. The phone is clean and i could flash the stock rom with mi flash.

biqe said:
Update. It loks like using adb was the problem. But using the platform tools i could execute comands and i fixed the issue. The phone is clean and i could flash the stock rom with mi flash.
Click to expand...
Click to collapse
Hello, i have the same problem. Did you use only mi flash to resolve the issue?

Mi A2 does not have /recovery partition, a recovery is a part of the /boot image, and thus TWRP is not to be "flashed" into /boot (or absent /recovery), but can be "patched" into /boot installing appropriate .ZIP file in a temporarily booted TWRP (tip: search Guides).
This "revelation" could be found in many threads / guides in this forum - search could help you.
As well as "revelations" answering your question:
AndroidOne devices do not need any MiFlash (except for testpoint unbricking, tip: search Guides), if bootloader and critical partitions are unlocked, just normal fastboot.exe from latest Android platform-tools (tip: search in Guides).