Database Users

[Q] problems with CWM recovery

Hello everyone. I've been reading about CM7 and find this:
http://forum.xda-developers.com/showthread.php?t=1257574&highlight=cm7+no+nightly
So i started to do the step by step and i'm stucked in the 3rd step "current rom backup" when i see" android recovery" and press volume up It says " failed to boot 2 starting rsd", and nothing happens. I've to take the battery Out and everything runs normal.
Any ideas?
Sorry about my english thanks!

Hi, probably you CWM or Kernel is corrupted, try to install it again e probably you´ll get successful...

soadcma said:
Hi, probably you CWM or Kernel is corrupted, try to install it again e probably you´ll get successful...
Click to expand...
Click to collapse
i'd unistall cwm from aplications, but it still the same.
cwm was flashed, is there a way to unflash it?

I would use fastboot and reinstall romracers recovery

If you flash CWM recovery you need to unlock your bootloader.
I had the same problem, unlocking it fixed it.

Since this gets asked every other day, here is a more complete explanation.
A locked bootlloader verifies that the recovery partition is correctly signed by Moto.
The CWM does not have this signature. So when you flashed that, the bootloader tosses the error that recovery will not load.
Either:
Follow instructions elsewhere to unlock your bootloader
or
Flash back to a stock recovery.
This same thing could happen if you flash a ROM that changes the kernel, boot partition or partition table (to a non moto signed one) to a device with a locked bootloader. That is why some ROMs require an unlocked bootloader and some do not. The system partition is not signed, so much can be safely changed w/o unlocking. A recovery or kernel can not use custom versions w/o unlocking.
Here is a more detailed explanation:
http://forum.xda-developers.com/showthread.php?t=1262266

pienne said:
If you flash CWM recovery you need to unlock your bootloader.
I had the same problem, unlocking it fixed it.
Click to expand...
Click to collapse
Thanks for answer, i will unlock the bootloader

exwannabe said:
Since this gets asked every other day, here is a more complete explanation.
A locked bootlloader verifies that the recovery partition is correctly signed by Moto.
The CWM does not have this signature. So when you flashed that, the bootloader tosses the error that recovery will not load.
Either:
Follow instructions elsewhere to unlock your bootloader
or
Flash back to a stock recovery.
This same thing could happen if you flash a ROM that changes the kernel, boot partition or partition table (to a non moto signed one) to a device with a locked bootloader. That is why some ROMs require an unlocked bootloader and some do not. The system partition is not signed, so much can be safely changed w/o unlocking. A recovery or kernel can not use custom versions w/o unlocking.
Here is a more detailed explanation:
http://forum.xda-developers.com/showthread.php?t=1262266
Click to expand...
Click to collapse
Thanks for answer, i'm Out Of town, so when i came back i will do It and I will ley you know.
Thanks!

In need of Help (Root) won't boot

Hello,
So, I got my Nexus 10 today. Super nice tablet. I wanted to root it and unlock the bootloader - unlocking the bootloader went fine, and I managed to flash CWM recovery. However, I forgot the enable USB Debugging under developer tools before I started all this..
My question now, how do I get this thing to boot again? And what is the smartest move now to root it?
Thanks!

What method did you use?

I keep linking these same posts lately. lol
http://forum.xda-developers.com/showpost.php?p=37019359&postcount=10
http://forum.xda-developers.com/showpost.php?p=37020134&postcount=3

If you're stuck in a boot loop after unlocking the bootloader, you may have to perform a factory reset from recovery. I had to do this to get mine booting again after I unlocked it. After the reset, everything worked great.
Of course, this is also assuming you unlocked your bootloader using fastboot , and not a toolkit. Solution might be the same though either way. May be worth a shot.

I also borked the original ROM after unlocking it, before I even flashed a custom recovery using the nexus toolkit (http://forum.xda-developers.com/showthread.php?t=2015467)
However, it is quite easy to reflash the software (you will loose the data though) through the same toolkit. After that I was able to flash TWRP recovery and CM10.1

Thank you all for your help! Got it working using the linux toolkit and perform a factory reset

[Q] Nexus 10 back to modified stock?

N10, rooted (supersu), unlocked bootloader, TWRP Touch recovery v2.6.3.1, Omnirom 4.4.2, Franco Kernel R16, ART.
I been flashing a lot, tried many roms... Now looking to go back to stock, but still want to use TWRP, and FK. I'm torn between using xposed (for AppOps and other cherrypicked mods) and Dalvik, or no xposed and ART...
My Question is, what is the best way to get back to stock 4.4.2 KOT49H, while keeping root and custom recovery. Do I need to sideload the factory image, re-root, and re-install custom recovery? Ideally I'm looking for a zip I can just flash along with supersu while keeping the custom recovery. I've looked for a zip file for pure aosp, but all I am finding is the sideload files from google's git, or "pure" AOSP roms with mods....
Also, I feel silly asking this because it seems pretty basic and I probably should already know at this point... The bootloader needs to stay unlocked once a custom recovery is installed, or should I be re-locking? I have been leaving it unlocked, for fear of bricking (aware bricking is not a huge deal with Nexus) but as I understand it, there are security concerns leaving the BL unlocked. Or am I way off base here?
TIA

Not much for security concerns, at least not for me. I personally always keep bootloader unlocked
As for keeping things similar but going back to stock +rooted, I would do this
Download factory image (just Google search: android factory image and grab appropriate one)
Unpack all on pc
Then boot to recovery, make a nandroid and then move all wanted files to PC (next steps involve some data loss)
Boot to bootloader
fastboot erase system -w
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
Now boot to recovery and should have an option to flash su, if not sideload a su.zip here
Now reboot, you will be stock kernel and ROM, and will be rooted and have same recovery as before
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app

Stock 5.0.1, Rooted, Bootloader Unlocked, TWRP Recovery - 5.0.2 will not install

I apologise if this is not the correct forum so someone please correct me if necessary thanks.
I have a Google Nexus 10 with the Stock 5.0.1 ROM, an unlocked bootloader, and a custom TWRP Recovery.
My Nexus has just automatically downloaded the 5.0.2 update but when I tap on INSTALL it simply boots into TWRP Recovery. If I try to manually install from there I get the "failed" message?
I think this may be because my bootloader is unlocked but before I lock it I need to ask some questions. I have a Samsung Galaxy S3 GT-I9300 (Intl) which I have been rooting and switching custom ROMs with for a couple of years so I am familiar with rooting and flashing recovery and ROM images so will hopefully understand any replies so here goes:
1 Will automatic update resume if I lock my bootloader again?
2 If I do lock my bootloader will anything happen, that is, will anything get erased/restored?
3 If I laterUNlock my bootloader will anything happen, that is, will anything get erased/restored?
4 In summary I'm thinking I can lock my bootloader to allow the automatic install of update 5.0.2 and then simply unlock the bootloader again if I need to?
I would appreciate any comments/advice. Thanks

matrixmainframe said:
I apologise if this is not the correct forum so someone please correct me if necessary thanks.
I have a Google Nexus 10 with the Stock 5.0.1 ROM, an unlocked bootloader, and a custom TWRP Recovery.
My Nexus has just automatically downloaded the 5.0.2 update but when I tap on INSTALL it simply boots into TWRP Recovery. If I try to manually install from there I get the "failed" message?
I think this may be because my bootloader is unlocked but before I lock it I need to ask some questions. I have a Samsung Galaxy S3 GT-I9300 (Intl) which I have been rooting and switching custom ROMs with for a couple of years so I am familiar with rooting and flashing recovery and ROM images so will hopefully understand any replies so here goes:
1 Will automatic update resume if I lock my bootloader again?
2 If I do lock my bootloader will anything happen, that is, will anything get erased/restored?
3 If I laterUNlock my bootloader will anything happen, that is, will anything get erased/restored?
4 In summary I'm thinking I can lock my bootloader to allow the automatic install of update 5.0.2 and then simply unlock the bootloader again if I need to?
I would appreciate any comments/advice. Thanks
Click to expand...
Click to collapse
It's because you've got a custom recovery. Download the 5.0.2 factory image and flash it with wugs toolkit and set it to no wipe mode. I did it and it works fine.
Sent from my Nexus 5 using XDA Free mobile app

matrixmainframe said:
I apologise if this is not the correct forum so someone please correct me if necessary thanks.
I have a Google Nexus 10 with the Stock 5.0.1 ROM, an unlocked bootloader, and a custom TWRP Recovery.
My Nexus has just automatically downloaded the 5.0.2 update but when I tap on INSTALL it simply boots into TWRP Recovery. If I try to manually install from there I get the "failed" message?
I think this may be because my bootloader is unlocked but before I lock it I need to ask some questions. I have a Samsung Galaxy S3 GT-I9300 (Intl) which I have been rooting and switching custom ROMs with for a couple of years so I am familiar with rooting and flashing recovery and ROM images so will hopefully understand any replies so here goes:
1 Will automatic update resume if I lock my bootloader again?
2 If I do lock my bootloader will anything happen, that is, will anything get erased/restored?
3 If I laterUNlock my bootloader will anything happen, that is, will anything get erased/restored?
4 In summary I'm thinking I can lock my bootloader to allow the automatic install of update 5.0.2 and then simply unlock the bootloader again if I need to?
I would appreciate any comments/advice. Thanks
Click to expand...
Click to collapse
Let's do HARD reinstall. Make sure to backup the data you wanna keep as it will be erased in the process.
Download the official google factory images.
Read the instructions( really easy)
Install trhought adb
You can boot into 5.0.2
Bingo!

Bricked device?

Hi everyone,
While trying to upgrade my device to stock Android 7.1.1, I've forgotten to flash the boot image. All the other components have been correctly flashed (system, bootloader, radio, etc.), but I was not careful enough and I forgot to flash the boot image. The problem is I've decided to relock my bootloader (silly me) right afterwards and now the device is in a bootloop (as the current boot image comes from the custom ROM that was installed previously). Naturally, I cannot unlock my bootloader again as it says "OEM unlock is not allowed". Am I screwed? Any ideas on how to unlock my bootloader? After many years of flashing, this is the first time I'm in a real trouble. Thanks for your help!

Yup u may at a lose if the Bootloader is locked then I don't think u can flash anything that's why it's recommended not to Relock the Bootloader bc if you phone doesn't boot for some reason then there's nothing u can do but to RMA it if u still have warranty. If not then sell as parts
Sent from my Pixel XL using Tapatalk

Thanks for your input! I will have it RMA'ed, so it's not a huge deal, but I was wondering whether there was a way of troubleshooting this. But I guess that's not possible. Cheers!

[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work