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:

[RESOLVED]Did I just brick my phone? Any help at all is appreciated

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...

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.

G5s Plus does not start the system, help me

Hello, I've been having this problem for about 2 days, well I'll summarize what happened to save mine and your time.
One day I was working with my g5s plus normally (using pixel experience 9.0), the other day I blocked the phone screen normally, but after that it turned off by itself and it is no longer booting the system...
interestingly it normally goes into bootloader and recovery mode, but whenever I try to install a rom, either custom or stock, it always has the same behavior, I install the rom and start the system, it loads up to the motorola logo and it turns off, it's not like a bootloop, it just loads up to the motorola logo and simply turns off.
I've tried many ways to recover, nothing worked, I tried to pass the rom through rsd lite, through motorola manager and of course through adb, I even tried to install a custom rom through twrp, but that always happens.
recently I was passing his latest rom through fastboot adb, when I noticed that during the process two errors appeared in the terminal, does anyone have any idea what it could be? I will leave the images linked here.
1. at the beginning of the rom installation it displays this highlighted message
{
"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. almost at the end of the installation it displays this same message...

I have been there
Flashing wrong stock firmware caused gpt error.
Best way to do that is this.
Install this to your pc and connect your device in fastboot mode.
Sometimes flashing second time with this tool helps.
If it doesn't help, flash firmware of your model firmware (written on back of your phone like XT****) then with rescue flash assistant tool try again to recover in fastboot mode.
If you want to automate and lazy to write use my flash.bat
Finally you achieved to boot the device but no imei or no 4G
1) Unlock oem lock
2) Flash Validus rom
3) Lock oem flash necessary files (You can use my oemlock.bat )
4) Back to stock with rescue and flash assistant.
By the way when rescue and smart assistant finished downloading your model's stock firmware, find where is it and copy it safe place

lynxrz said:
I have been there
Flashing wrong stock firmware caused gpt error.
Best way to do that is this.
Install this to your pc and connect your device in fastboot mode.
Sometimes flashing second time with this tool helps.
If it doesn't help, flash firmware of your model firmware (written on back of your phone like XT****) then with rescue flash assistant tool try again to recover in fastboot mode.
If you want to automate and lazy to write use my flash.bat
Finally you achieved to boot the device but no imei or no 4G
1) Unlock oem lock
2) Flash Validus rom
3) Lock oem flash necessary files (You can use my oemlock.bat )
4) Back to stock with rescue and flash assistant.
By the way when rescue and smart assistant finished downloading your model's stock firmware, find where is it and copy it safe place
Click to expand...
Click to collapse
Hello I've tried in all ways, I tried to restore the soft through RSDLite, from the lenovo software even by the ADB itself, but I wasn't successful, I think the problem is not hardware either.

ocod said:
Hello I've tried in all ways, I tried to restore the soft through RSDLite, from the lenovo software even by the ADB itself, but I wasn't successful, I think the problem is not hardware either.
Click to expand...
Click to collapse
First step:
Try to find gpt compatible firmware and flash it with fastboot.
Not Adb, not Rsdlite, not lenovo rescue asistant only with fastboot!
You will not get 'permission denied' error while flashing correct gpt partition table. If you find this firmware keep it, it could be correct firmware to go next step.
Examine my flash.bat file and don't flash all of them just these
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
I found it my compatible gpt firmware with downloading 30 GB+ stock firmware files then tried to flash every one of them in fastboot mode. Don't give up. I found the solution about a week. I'll check this post daily and try to help you step by step.

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