Database Users

[RECOVERY] 3e Recovery Modded w/ No Verification

NOTE
This is took from untermensch's thread in the Vibrant forum so I take no credit for this (http://forum.xda-developers.com/showthread.php?t=833423)
I have noticed some of you are having issues after installing a new kernel or rom, when you boot into recovery you now have 3e, which does not allow unsigned zips to be flashed. With this version of 3e it has no-verification check, now allowing you to flash whatever you want.
This zip has
1) 3e recovery modified to disable signature checking
2) disables the forced wipe after installing any update.
Instructions
1)Download and extract the file below
2)Use a terminal emulator or ADB shell and type.. (or you can use Root Explorer or SGSTools to mount system RW)
Code:
mount -o rw,remount /dev/block/stl9 /system
3)Use a file manager like Root Explorer and copy the recovery file to /system/bin and replace the one there
4)Now, reboot and you should have a modded 3e recovery with no signature verification
You can either leave the modded 3e recovery or you can now flash CWM via Rom Manager
**Just like anything else, I am not responsible if this bricks your phone, this is fairly simple, follow the guide...Do at your own risk**

Old news, we have CWM now in pretty much everything.
Also you cannot just replace the recovery file... you have to replace the images in sbin or in the zImage its self, otherwise you get errors and cannot do anything.

designgears said:
Old news, we have CWM now in pretty much everything.
Also you cannot just replace the recovery file... you have to replace the images in sbin or in the zImage its self, otherwise you get errors and cannot do anything.
Click to expand...
Click to collapse
I done the exact method above and works fine for me...
Place extracted recovery file in /system/bin/ , reboot and flash cwm via rom manager, works perfectly fine...the reason I posted was, if you read Hardcores thread, and seen this in other threads, that after flashing his kernel, when they goto recovery they now have 3e (depending on which method when entering recovery)..alot of people have done it the way I posted with no issues...im not trying to argue with you, you by far know more then me, just posting what worked for me and some others

sounds like a good idea for the people that updated to Rogers froyo that has the 3e recovery. You could just flash a new kernel, but this is definately a good alternative.
Thanks
Sent from my SGH-I897 using XDA App

If you look at Darkyy's rom he has a script that does this.

Thanks, this works flawlessly on a Rogers Froyo Stock. Now I have CWM working and good to go. The only thing left would be to apply some kind of lagfix.

Tested and works with Rogers 2.2 Rom. Thanks

skorchir said:
Tested and works with Rogers 2.2 Rom. Thanks
Click to expand...
Click to collapse
I also have.
Thanks

Works great on Rogers 2.2. Thanks

I tested it on Galaxy S i9000m bell and it work A+
i do not have to flash cf-boot to make unsigned zip to be installed
thanks a lot for your hard work.
only thing is botton function become different then original 3e
but its working A+

I'm a little confused on how the Recovery works..... I have a I897 that I flashed Cognition 2.3b8 to with ROM Manager/CWM and when I chose "reboot into recovery" from ROM Manager from inside Cognition, it worked fine after reloading packages once. A few days ago, I flashed Perception 10.1 with the firebird kernel. After noticing the battery didn't last as long as it used to with Cognition, I did some research and found the SpeedMod kernel K12L. Before I flashed it, I did a backup from ROM Manager which rebooted into CWM with no problems and did the backup with no problem. I have since flashed K12M and K12N. Now I thought I would give Cog 3.0 a shot and wanted to back up my current config with Perception 10.1/SpeedMod K12N. From ROM Manager, I chose to backup, named my backup and the phone rebooted into 3e Recovery and gave the errors you listed above but I don't understand why? Is it because of the I9000 kernel which doesn't make sense since Firebird is a I9000 kernel. Was it from flashing SpeedMod? Also noticed, that only the volume up/down buttons worked, not the power button which is also the select key. Only way out was to 3 button reboot (or pull the battery) which rebooted into CWM and then initiated the ROM Manager backup.
Any ideas why? Also, if I was to ODIN flash JH6 back to the phone, would that restore the Stock 2e Recovery? Sorry for the long post, but I'm still trying to learn this stuff and think you guys are awesome. The captivate would be a crappy phone if it wasn't for you all.

I guess if I had read your second post a little closer I would have seen that flashing SpeedMod causes it. I used your fix in the OP and when I tell it to "Reboot into Recovery" from ROM Manager, it boots into what I assume is 3e (Goes by real quick) and shows something about MOVI and verification and then boots into CWM Recovery v2.5.1.2. If I 3 button boot into recovery, it boots into CWM v2.5.1.0 SpeedMod ULFK. Seems to work now but I'm still confused. Thanks again.

Using sgstools to change mount RW completes its task fine. When I try to copy the new file to /system/bin it does not allow it. The permissions do not change. I tried terminal emulator it doesnt work either. The files stay -r only. I have tried so many times to delete/rename/ or copy over. I just gave up. My system is 2.2 and rooted before you ask.

davidis57 said:
Using sgstools to change mount RW completes its task fine. When I try to copy the new file to /system/bin it does not allow it. The permissions do not change. I tried terminal emulator it doesnt work either. The files stay -r only. I have tried so many times to delete/rename/ or copy over. I just gave up. My system is 2.2 and rooted before you ask.
Click to expand...
Click to collapse
Use a terminal emulator or adb shell and type...
Code:
chmod 777 /system/bin/recovery
That should give r/w permission to the file, ...i just tested to verify it and it worked for me. also if you have Root Explorer you can just long press the file and select Permissions and check all the boxes.

Exact the same thing is happening to me! Beforehand I had flashed CF Root to get Superuser also at the same time when rooting. I Still can boot into recovery with 3BR and come into the speedmod ULFK settings. Speedmod introduces 3e and you need signed packages. You must have 2e for this I assume!? Can anyone tell me what goes wrong?

Im using the Speedmod kernel and it always pissed me off that everytime I wanted to flash somethng via CWM that I had to pull the battery and restart my phone for it to finish because of the 3e 'no signed packages'
I did the steps in the OP and I noticed that I didnt even have a recovery file in system/bin but I put it in there anyway. I rebooted and flashed a different modem just to check and sure enough, it worked. Now I dont have to worry about pulling my battery and having to reboot my phone everytime I want to flash something.
Thanks for this!

Well the file is moved now. I get reinstall packages in recovery and thats all does. I installed rom manager and have cwm on my sdcard. The phone does not go into cwm recovery. It doesnot give me options to apply install.zip. I have dxjpa and z4root running. This modded recovery does not work. Any ideas?

davidis57 said:
Well the file is moved now. I get reinstall packages in recovery and thats all does. I installed rom manager and have cwm on my sdcard. The phone does not go into cwm recovery. It doesnot give me options to apply install.zip. I have dxjpa and z4root running. This modded recovery does not work. Any ideas?
Click to expand...
Click to collapse
Once you install cwm and reboot back into 3e, select reinstall packages, it will install cwm and then load into it , if it doesn't then the file didn't copy over, make sure it replaces it ok, I've used this quite a few times and it works everytime, and everyone that has posted has not had an issue, so it does work
Sent from my SGH-I897 using XDA App

It did copy over in fact i deleted the old one and put the new one in its place. It never installs anything and seems to error but its so fast i cant read it.
Sent from my GT-I9000 using XDA App

davidis57 said:
It did copy over in fact i deleted the old one and put the new one in its place. It never installs anything and seems to error but its so fast i cant read it.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Try starting over, delete the recovery file and also delete the update.zip on the root of the sdcard, then copy the modded recovery over to /system/bin/ , then open rom manager and install cwm again, something could have happened with the update.zip, cause if you are able to get into 3e and select reinstall packages and it actually starts but errors out with the update.zip, then something could possibly be wrong with the update.zip .. it might restart after you select reinstall packages, but it should then load in to cwm, if it doesnt and boots back into android, then go into rom manager and select restart recovery and see if that works

SBKv2 and custom ROMs

So I just got a SBKv2,(C30). TF101 and wanted to try out Megatron. What's the safest way to do this without ending up with a brick?
Not new to flashing. Got several Android devices, Nook Color and Droidx on roms
Sent from my Transformer TF101 using Tapatalk 2

i think you may have 8.x.x.21 fw, if you havent updated asus fw yet. I have same device as well, and I used vipermod for rooting which is the first step in moving forward.
Only thing i really recommend is OTA rootkeeper once you root your device.

Already rooted (vipermod opt1) and got OTA rootkeeper installed.
Also installed recoveryinstaller lastnight, but then I chicken-out didn't go any further.
I guess I just need to be careful when flashing. Check MD5 matched on everything I downloaded to make sure I don't get stuck with a bad file.
Anymore tips guys before I start the flashing frenzy?

jdpdata said:
Already rooted (vipermod opt1) and got OTA rootkeeper installed.
Also installed recoveryinstaller lastnight, but then I chicken-out didn't go any further.
I guess I just need to be careful when flashing. Check MD5 matched on everything I downloaded to make sure I don't get stuck with a bad file.
Anymore tips guys before I start the flashing frenzy?
Click to expand...
Click to collapse
First is to go into CWM recovery and do a nandroid backup.
I suggest you stay with a recovery that read from external sd card.
If you used RecoveryInstaller it should have installed Roach's 3.2.0.1 which is good
or you can use Team Rouge recovery which read from both internal and external sd.
The newer recovery read from the internal storage only, which is ok just make sure you don't use a Superwipe script.
I highly recommend you set up ADB which come in handy also.
http://forum.xda-developers.com/showthread.php?t=1071584

baseballfanz said:
If you used RecoveryInstaller it should have installed Roach's 3.2.0.1 which is good
Click to expand...
Click to collapse
+1 to this, never had a problem with 3.2.0.1 and it reads ext-sd. I've just stuck with this version.

My TF101 is a C20 serial. This is what I did, I'll skip rooting the TF since you already did it (I did it the same way). Everything was with the TF attached to the dock:
-Installed gnufabio's Recovery Installer from this thread: http://forum.xda-developers.com/showthread.php?t=1346180
-Booted into recovery and installed rburrow's Rogue XM Recovery from this thread: http://forum.xda-developers.com/showthread.php?t=1446019
-Rebooted into recovery
-Followed "First time install instructions" on first post of ricardopvz's Megatron ROM (http://forum.xda-developers.com/showthread.php?t=1525148) which basically are:
-Go to mounts and storage, format data, cache and system
-Do a factory reset (wipe)
-Install Megatron ROM
-Install gapps
-Install custom kernel (I used guevor's test17c from it's own thread http://forum.xda-developers.com/showthread.php?t=1565519 but now I'm on test18e)
-Reboot into ROM
-Download and install Megatron Parts
-Have fun!
And I'm really having fun with it!

jdpdata said:
Already rooted (vipermod opt1) and got OTA rootkeeper installed.
Also installed recoveryinstaller lastnight, but then I chicken-out didn't go any further.
I guess I just need to be careful when flashing. Check MD5 matched on everything I downloaded to make sure I don't get stuck with a bad file.
Anymore tips guys before I start the flashing frenzy?
Click to expand...
Click to collapse
Lol, chicken. I never check MD5 but I don't advise following my lead
But yes, be careful and set up ADB before anything. It's best to set it up before you mess something up than after, like I did (hence why I said to not follow my lead ) but I was lucky and able to use nvflash to unbrick it (thank God b/c I wasn't sure which model I had)

[Q] Restore Defy to Factory settings after Root and 2nd Init and 2nd Init

How do I restore my Defy to factory settings without ANY of the things I set up on it?
I had rooted it using SuperOneClick Root and used the 2nd Init Installer to install the 2nd Init Boot Menu. I also have CWM installed by SuperOneClick Root or 2nd Init.
I want to redo everything on my device.
My device has Android BootMenu <v0.6.1> Is this part of the device originally or installed by 2nd Init?
Under it, it says DOKDO so I'm guessing its 3rd party.
The reason for this is that I'm unable to update to 2.2 because the file apparently cannot be found after downloading the update. I can't find it manually in /sdcard either. Also, CWN won't allow me to backup because it couldn't mount a certain file nor /sdcard
Should I try to format my SD CArd first?

j814wong said:
The reason for this is that I'm unable to update to 2.2 because the file apparently cannot be found after downloading the update. I can't find it manually in /sdcard either. Also, CWN won't allow me to backup because it couldn't mount a certain file nor /sdcard
Should I try to format my SD CArd first?
Click to expand...
Click to collapse
Have you look under the foder "Download" or "download"?
If that doesn't help, formating the sdcard seems like a good start to try solving this problem.
j814wong said:
How do I restore my Defy to factory settings without ANY of the things I set up on it?
Click to expand...
Click to collapse
Under Settings > Privacy you'll find the restore factory settings, but it won't unroot your phone nor uninstall Bootmenu.
As fas as I'm concerned, this could only be achieved with a full SBF, that is to say installing Motorola's firmware.
j814wong said:
How do I restore my Defy to factory settings without ANY of the things I set up on it?
I had rooted it using SuperOneClick Root and used the 2nd Init Installer to install the 2nd Init Boot Menu. I also have CWM installed by SuperOneClick Root or 2nd Init.
I want to redo everything on my device.
My device has Android BootMenu <v0.6.1> Is this part of the device originally or installed by 2nd Init?
Under it, it says DOKDO so I'm guessing its 3rd party.
The reason for this is that I'm unable to update to 2.2 because the file apparently cannot be found after downloading the update. I can't find it manually in /sdcard either. Also, CWN won't allow me to backup because it couldn't mount a certain file nor /sdcard
Should I try to format my SD CArd first?
Click to expand...
Click to collapse

So in regards to the SPF, if I use the same one one/version on my devvice already, eFuse won't change a thing right?

j814wong said:
So in regards to the SPF, if I use the same one one/version on my devvice already, eFuse won't change a thing right?
Click to expand...
Click to collapse
Right. eFuse only blows when you flash a "higher" sbf.
And you have to flash an sbf, because 2nd init lets you remove the custom recovery, but it doesn't remove the custom recovery entry in the boot menu.

Questions go in the Q&A section

Hi I have a similar problem as well. I upgraded to CM7 a while ago and wanted to try the CM9 by epsylon. I tried upgrading directly, but got stuck in bootloader so I reverted back to stock using RSDlite.
I've been trying to go to CM9 directly from stock using Suttaroom's guide [http://forum.xda-developers.com/showthread.php?t=1756234]
Everything is fine up until I install the 2nd init. When I install the 'latest version' the bootloader does not work and just boots normally (no blue light). I figured this is because I've upgraded using cm7 so maybe I've blown an eFuse or two.
So i installed the 2nd init version for 'stable CM-based ROMS' and this time the blue light came on and I was able to get into ClockworkMod Recovery. Once there however, it is unable to read the sdcard and gives me an error message saying
"E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (no such file or directory) E:can'tmount /sdcard"
Any idea about where to go? I'm guessing because my kernel is upgraded (I think) that I need to find a 2nd init that is compatible with it?

CWM-Rom manager not working on N7 JB 4.2.1

Is anyone else having loads of problems with clockwork mod and rom manager since updating to 4.2.1
For me RM doesnt do anything and I CWM keeps will not re-flash a backup unless its 4.2.1. Even though I copy n past to new directory where CWM keeps backups but will not reflash them. Also everytime after I use CWM it seems to delete itself and i have to reflash via the command line. Help welcome. Thx in advance....
Update: Not sure if its RM or CWM. Have just worked out CWM is deleting itself everytime after use. IT doesnt leave any other option once you try to re-boot device from CWM....

veroby said:
Is anyone else having loads of problems with clockwork mod and rom manager since updating to 4.2.1
For me RM doesnt do anything and I CWM keeps will not re-flash a backup unless its 4.2.1. Even though I copy n past to new directory where CWM keeps backups but will not reflash them. Also everytime after I use CWM it seems to delete itself and i have to reflash via the command line. Help welcome. Thx in advance....
Update: Not sure if its RM or CWM. Have just worked out CWM is deleting itself everytime after use. IT doesnt leave any other option once you try to re-boot device from CWM....
Click to expand...
Click to collapse
There's a file in /system that you should either rename or delete called: recovery-from-boot.p
That reloads the stock Android recovery at each reboot. Then once you have renamed/deleted it, reflash CWM Recovery again from the command line and it should stick now.
You're using the latest CWM Recovery correct? I don't use RM or CWMR at all (TWRP), so I may not be able to totally help out.

RMarkwald said:
There's a file in /system that you should either rename or delete called: recovery-from-boot.p
That reloads the stock Android recovery at each reboot. Then once you have renamed/deleted it, reflash CWM Recovery again from the command line and it should stick now.
You're using the latest CWM Recovery correct? I don't use RM or CWMR at all (TWRP), so I may not be able to totally help out.
Click to expand...
Click to collapse
Hey thx - I have always used them and found them to be easy tools in the past. Dont really want to change to TWRP but it seems all recommendations are leaning towards and its the way to go with 4.2.1. Thx again... I have to ask why that file exist in the first place. Just to catch donkeys like me out.....Also if you know and are still around. Is there a way to restore old backups from 4.1.1

veroby said:
Hey thx - I have always used them and found them to be easy tools in the past. Dont really want to change to TWRP but it seems all recommendations are leaning towards and its the way to go with 4.2.1. Thx again... I have to ask why that file exist in the first place. Just to catch donkeys like me out.....Also if you know and are still around. Is there a way to restore old backups from 4.1.1
Click to expand...
Click to collapse
I've had no issues flashing 4.1.1/4.1.2 ROMs to 4.2.1 and vice versa...but again I'm using TWRP Recovery.
The file is in the stock images from Google, and it's there to reload stock Android recovery at boot...other than that I'm not sure of the exact reasoning.
I know that Android 4.2 has multi-user support, and that has been the cause for many issues with 4.2 in general due to it creating a folder /sdcard/0...so flashing multiple 4.2 ROMs without the latest CWM Recovery version 6.0.1.9 would cause another folder created there at /sdcard/0/0...and so on. If you created another user, they would have their own folder at /sdcard/1...and so on.
I would make sure that you have the latest CWM Recovery flashed to your device, then put your backup in the correct folder. From what I remember when using RM and CWM, there's the folder for your backup and then one level up from that there's the blobs folder, you'll need BOTH of those in order to restore things, as the blobs folder is the backup.

[Q] nook color CM10.2 update problems CyanogenROM_Downloader/TWRP

Hi all. I have a Nook Color running CM 10.2 and am trying to upgrade it without success.
I have Superuser, CyanogenmodRom_Download, and TWRP downloaded.
Using CyanogenmodROM_Downloader configured to use TWRP I can successfully download a new Nightly. When I select Flash it takes me to Cyanboot. I select Internal eMMC Recovery and it brings up a notice saying that the Install Failed.
I tried using TWRP->Install->CyanogenROM_Downloader->cm-10.2-20131009-NIGHTLY-encore.zip. I'm not Wiping anything. Cyanboot into Internal eMMC recovery and the existing release instead of the update is installed.
Also, the only way I can tell which build is installed is with the CyanogenROM_Downloader. I looked around the web for something that would tell me where to look and didn't find anything. I also looked around /etc and didn't find anything obvious. Is there an easy way to tell what nightly build is installed?
I've been beating on this step for a couple of days now and looking around this site and the web and haven't found anything that helps although I'm sure it's out there somewhere. Any suggestions would be appreciated.
Thanks
Steve S.

Finding installed ROM
sjs_bebop said:
Hi all. I have a Nook Color running CM 10.2 and am trying to upgrade it without success.
I have Superuser, CyanogenmodRom_Download, and TWRP downloaded.
Using CyanogenmodROM_Downloader configured to use TWRP I can successfully download a new Nightly. When I select Flash it takes me to Cyanboot. I select Internal eMMC Recovery and it brings up a notice saying that the Install Failed.
I tried using TWRP->Install->CyanogenROM_Downloader->cm-10.2-20131009-NIGHTLY-encore.zip. I'm not Wiping anything. Cyanboot into Internal eMMC recovery and the existing release instead of the update is installed.
Also, the only way I can tell which build is installed is with the CyanogenROM_Downloader. I looked around the web for something that would tell me where to look and didn't find anything. I also looked around /etc and didn't find anything obvious. Is there an easy way to tell what nightly build is installed?
I've been beating on this step for a couple of days now and looking around this site and the web and haven't found anything that helps although I'm sure it's out there somewhere. Any suggestions would be appreciated.
Thanks
Steve S.
Click to expand...
Click to collapse
Go into system settings / about tablet (at bottom of settings)
About 3/4 down list you'll see the ROM installed. Also kernel info plus other info.
For updates ;
I go to this link and download directly.
http://download.cyanogenmod.org/?type=nightly&device=encore
Also I copy and paste the md5 sum into MD5 checker (free in play store), run the check.
Reboot into recovery using power button menu and install in TWRP there. I had too many problems using cm downloader, goo manager, etc.

nook color cm10.2 update problems
Thanks. That helps. I can determine the version now.
But I still can't get update to work. I downloaded from the location you gave using the browser and can see the file using TWRP and selecting install. This boots into the cyanoboot loader, there are two options enabled: 'Internal eMMC Normal' and 'Internal eMMC Recovery.' Normal seems to reboot -- which makes sense. Recovery re-installs the currently installed version. Also, using ADB I can see the new cm-nightly zip file in /storage/sdcard1/Download.
I don't see TWRP during the reboot. Should I??
I also don't get an option to select a new image to install. Should I?
I also tried copying the cm-nightly zip file to the /emmc directory and that doesn't seem to make any difference.

Sounds like a problem I had a while back
sjs_bebop said:
Thanks. That helps. I can determine the version now.
But I still can't get update to work. I downloaded from the location you gave using the browser and can see the file using TWRP and selecting install. This boots into the cyanoboot loader, there are two options enabled: 'Internal eMMC Normal' and 'Internal eMMC Recovery.' Normal seems to reboot -- which makes sense. Recovery re-installs the currently installed version. Also, using ADB I can see the new cm-nightly zip file in /storage/sdcard1/Download.
I don't see TWRP during the reboot. Should I??
I also don't get an option to select a new image to install. Should I?
I also tried copying the cm-nightly zip file to the /emmc directory and that doesn't seem to make any difference.
Click to expand...
Click to collapse
You may be having partition problems. I have had either lost the ability to install new nightlies or the ability to backup. Read the instructions through completely first. Get the info together and then start.
If you have a backup App like titanium backup, backup all files and data before anything else. Also if you can, do a backup in recovery before doing the following.
Check this link: http://forum.xda-developers.com/showthread.php?p=28457126#post28457126 by Leapinlar
I set up a 2Gb sd bootable card to run these from using the CWM recovery (If you need help check eyeballer's link below).
I put the partition repair files on it. Also the 1.4.3 Stock rom, the TWRP open recovery. zip 2.4.1.0 (http://forum.xda-developers.com/showpost.php?p=37554712&postcount=129), and the latest Rom you want to install and Gapps.
After following leapinlar's instructions including installing the 1.4.3 Stock rom (fixes other possible problems), then follow eyeballer's install for the Rom, Gapps and recovery here (http://forum.xda-developers.com/showthread.php?t=1030227&highlight=install+cm7+to+nook+color).
After booting and doing the initial CM setup return to recovery and VERY IMPORTANT ***restore only the data*** Not boot or system from your latest backup. This should get you back up and running. If you have a backup like Titanium restore "newer versions of apps" if you had to use an older recovery backup. Once you have everything set reboot into recovery and do another backup for safeties sake.
Including my wife's Nook I have four units and have needed to do this 4 or 5 times. Takes a little time but has always worked great. I keep the card available and update the Rom, Gapps or whatever else needs changing.
This link also contains a lot of helpful info. I have all these bookmarked on both my PC and Nook.
User Tips http://forum.xda-developers.com/showthread.php?p=25354258#post25354258