Undo ClockworkMod Recovery

[Phalanx7621]

How did you unlock the bootloader?? This has not been done yet with any dev.

Please explain more. Thank you.


.

Well there are three magic stones that lie on the southern shore of the mystical land of Asgard, if we find them and bring them back, the Warlock who requires them will in exchange unlock our bootloaders! Who will join me?!

Sent from my MB860 using Tapatalk

 

[Smajll]

hi, I'd like to continue with this thread, I did the same thing like rmkilc. I'm using an European Atrix and it's running 2.3.4 official, it's rooted and I flashed the CWR. Now I found out that I have to flash pudding for BL unlocking. I'm not going to do this so how can I get back to stock recovery?

 

[CSharpHeaven]

Recovery and Bootloader are explaind in an easy manner...

The primary purpose of Android Recoery program is to apply updates, run programs, wipe cache, format partitions, and reset a device. The default Android Recovery programs are limited in functionality than the custom recovery programs.

Why Android Recovery program is needed? All functionalities listed in above cannot be done while Linux and Android are online or running. Therefore, the Android Recovery runs in its own environment so the changes can be applied to the Linux and Android while not running.

Since Android Recovery can be used for making all sort of changes many manufactures lock the bootloader to limit the functionality of the Android Recovery program. Apart from giving the basic version of the program (Recovery) this version of the recovery program can only flash signed images or zip files. A signed image or zip file contains a special key that the only manufacturer can generate it and that is why the default Android Recovery programs with locked bootloader is useless to the users and developers.

The main purpose of locking the bootloader is to prevent the Android Recovery program to be replaced, by flashing it in fastboot mode, with one that does not limited by signed image and zip files only. This is why the first thing one need to do is to unlock the bootloader.

If your device already uses a custom recovery that means the device's bootloader was previously unlocked. Flashing a .sbf file using RSDLite for instance not only relocks the bootloader but also replaces the Recovery Program back to the default.

I hope the above explanation helps understanding both the recovery and bootloader.

 

[Smajll]

Recovery and Bootloader are explaind in an easy manner...

The primary purpose of Android Recoery program is to apply updates, run programs, wipe cache, format partitions, and reset a device. The default Android Recovery programs are limited in functionality than the custom recovery programs.

Why Android Recovery program is needed? All functionalities listed in above cannot be done while Linux and Android are online or running. Therefore, the Android Recovery runs in its own environment so the changes can be applied to the Linux and Android while not running.
.......

as far as I understand, my bootloader is locked that means that the recovery is still stock? basically I could now unroot the phone and it would be like a new one?

 

[CSharpHeaven]

as far as I understand, my bootloader is locked that means that the recovery is still stock? basically I could now unroot the phone and it would be like a new one?

Not having your phone in hand I cannot be 100% sure but I have unlocked the bootloader of my phone a couple of days ago. Now when I boot my phone on the top left corner of the screen 'unlocked' message is displayed. If you don't see the message then that means your phone currently is locked and would have the 'default' Android Recovery. If a phone was previously unlocked and locked again then one of the appropriate .sbf files must be flashed. This is important that the .sbf version to be either the same version or higher than the previous one that was being used. This process will install the default Android recovery too.

Unrooting will put the phone back to its default security privilege profile.

Please remember, Motorola is logging certain activities in their recent phones now that can be easily traced. The warranty is the case behind this. No one more than Motorola thinks their phones are so precious which we know they are not anymore.

 

[Smajll]

ok, thank you for your help. The bl is locked and I un-rooted my phone

 

[jiggykilla]

Recovery and Bootloader are explaind in an easy manner...

The primary purpose of Android Recoery program is to apply updates, run programs, wipe cache, format partitions, and reset a device. The default Android Recovery programs are limited in functionality than the custom recovery programs.

Why Android Recovery program is needed? All functionalities listed in above cannot be done while Linux and Android are online or running. Therefore, the Android Recovery runs in its own environment so the changes can be applied to the Linux and Android while not running.

Since Android Recovery can be used for making all sort of changes many manufactures lock the bootloader to limit the functionality of the Android Recovery program. Apart from giving the basic version of the program (Recovery) this version of the recovery program can only flash signed images or zip files. A signed image or zip file contains a special key that the only manufacturer can generate it and that is why the default Android Recovery programs with locked bootloader is useless to the users and developers.

The main purpose of locking the bootloader is to prevent the Android Recovery program to be replaced, by flashing it in fastboot mode, with one that does not limited by signed image and zip files only. This is why the first thing one need to do is to unlock the bootloader.

If your device already uses a custom recovery that means the device's bootloader was previously unlocked. Flashing a .sbf file using RSDLite for instance not only relocks the bootloader but also replaces the Recovery Program back to the default.

I hope the above explanation helps understanding both the recovery and bootloader.

Thanks for clearing that up! I have some understanding how it works but this has cleared it up for me!

Spilled from my Atrix4g utilizing Tapatalk

 

[konker]

I think the storage encryption also depends on the Android Recovery??

Recovery and Bootloader are explaind in an easy manner...

The primary purpose of Android Recoery program is to apply updates, run programs, wipe cache, format partitions, and reset a device. The default Android Recovery programs are limited in functionality than the custom recovery programs.

Why Android Recovery program is needed? All functionalities listed in above cannot be done while Linux and Android are online or running. Therefore, the Android Recovery runs in its own environment so the changes can be applied to the Linux and Android while not running.

Since Android Recovery can be used for making all sort of changes many manufactures lock the bootloader to limit the functionality of the Android Recovery program. Apart from giving the basic version of the program (Recovery) this version of the recovery program can only flash signed images or zip files. A signed image or zip file contains a special key that the only manufacturer can generate it and that is why the default Android Recovery programs with locked bootloader is useless to the users and developers.

The main purpose of locking the bootloader is to prevent the Android Recovery program to be replaced, by flashing it in fastboot mode, with one that does not limited by signed image and zip files only. This is why the first thing one need to do is to unlock the bootloader.

If your device already uses a custom recovery that means the device's bootloader was previously unlocked. Flashing a .sbf file using RSDLite for instance not only relocks the bootloader but also replaces the Recovery Program back to the default.

I hope the above explanation helps understanding both the recovery and bootloader.

CSharpHeaven,

Thanks for this explanation.
I understand what you are saying.
However, I'm trying to deal with an AT&T Motorola Atrix 4G with unlocked bootloader & CWM Recovery.
I cannot enable the Device data encryption on the stock Fruit Cake 4.5.141 ROM on this phone as CWM will halt with an error message at the bottom: E:Invalid command argument
I suspect that the stock Android Recovery is needed for the Device data encryption to work.
Do you know how I can restore the stock recovery?
I tried to flash the stock 4.5.141 SBF using RSDLite but it will fail with the sec_exception: febe, 35, 35
I don't understand what this error message means & don't know how to proceed.
Please advise me what I should do next.
Thanks!

Konker

 

[ravilov]

CSharpHeaven,

Thanks for this explanation.
I understand what you are saying.
However, I'm trying to deal with an AT&T Motorola Atrix 4G with unlocked bootloader & CWM Recovery.
I cannot enable the Device data encryption on the stock Fruit Cake 4.5.141 ROM on this phone as CWM will halt with an error message at the bottom: E:Invalid command argument
I suspect that the stock Android Recovery is needed for the Device data encryption to work.
Do you know how I can restore the stock recovery?
I tried to flash the stock 4.5.141 SBF using RSDLite but it will fail with the sec_exception: febe, 35, 35
I don't understand what this error message means & don't know how to proceed.
Please advise me what I should do next.
Thanks!

Konker

Next time you attempt this, try pulling out the file /cache/recovery/command right after it reports this error. You can use adb for that. Then post the content here (it's a normal text file), maybe someone can shed some light as to what command seems to be the issue.

 

[konker]

Next time you attempt this, try pulling out the file /cache/recovery/command right after it reports this error. You can use adb for that. Then post the content here (it's a normal text file), maybe someone can shed some light as to what command seems to be the issue.

ravilov,

Thanks for your quick input.
By the time I flash the SBF using RSDLite, the whole phone would have been wiped, system, cache, boot etc...
You mean I could still use ADB to access that said file?
What mode should the phone be in?
Thanks!

Konker

Update:
I finally figured out that the sec_exception: febe, 35, 35 error meant that the SBF was not intended for the device. That led me to suspect that the system board is not an original AT&T US board. I gave an Asian stock SBF a try & viola! The phone was successfully restored to factory stock ROM with stock bootloader & the Unlocked words removed from the boot screen. Device encryption is also working without any issues.

 

[ravilov]

No... nevermind.
If you've flashed the SBF, there's nothing to do anymore. No ADB or anything.