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

Cannot install .zip with CWM

I keep getting this error message:
Finding update package...
Opening update package...
Installing update...
Copying files...
E:Failure at line 2:
copy_dir package:system SYSTEM:
Installation aborted.
This happens with any .zip I try to install in CWM. I even flashed the new CWM through ROM manager and it still won't work. I've been trying to flash a new kernel with no success, but it also won't install themes or other roms. Any advice would help because I would love to flash DL30 later today if I can get this fixed (without having to use ODIN and flash to stock). I also tried clearing the cache and nothing changed still.
Thanks.

Did you install CWM correctly? (Flashed via ODIN 1st, then through ROM Manager?)
And you are sure you are in Clockwork Recovery (green screen)??
Finally, can you open the zip file through Root Explorer? You might just have a bad .zip file, although unlikely, if you say every .zip file you tried is failing.. but just double check..

Yes I know CW worked because I've installed several roms and kernels beforehand. The problem started after I installed the Blazed v2.2 kernel by sirgatez a few days ago. I noticed a slight lag on the lockscreen so i tried to install a different kernel but can't.

samething happened to me today. i reverted back to stock and re installed every thing. you have to use odin its not that hard at all to use. just open up odin, take out battery, hold down volume down, let odin recognise it, and flash wht ever you need.

Yeah I realized that was possible I was just hoping to avoid doing that because I just wanted to re-flash a kernel for now, and possible try out Froyo later. But if no one has another solution I'll probably just flash to DL09 through Odin and go straight to DL30 from that.

Installing ROM error, what am I doing wrong?

Hey,
I recently rooted my phone GS2 and wanted to install the CyanodenMod 7.1.0, but I keep getting an error every time I try install via Rom manager, Btw this is my first time doing this, I have read lots from sites and forums but just don't get what is going wrong, This is what I do:
- Download ROM Manager
- Click "Flash ClockworkMod Recovery" and it does that successfully
- Click "Download ROM" and select "CyanogenMod" it download fine and then click "Wipe Data and Cache" & "Wipe Dalvik Cache". I have also done the same thing but using the option from SD Card.
- My phone restarts and boots into the standard recovery and give this error:
"--Installing Package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted."
- Then I just click "reboot system now" since it didn't work and now I am stuck.
I sort of know the problem, it isn't booting into the Clockwork Recovery it's just booting to the standard recovery, but I have no idea how to make it open the Clockwork Recovery, please help or tell me what I am missing.
Thanks for reading.

Don't use Rom Manager, It is not compatible with our phones
You should still be able to enter Download mode
Visit the thread HERE and have a good read and you should be able to get your phone back in working order

Ugh, rom manager. I tend to avoid the apps for doing that kind of thing. I use Odin for Kernels and CWM (Home+Power+Volume Up method) for ROMs. The other ways tend to crash.

How do I do it via CWM? Can you do little step by step guide only rough if possible? Thank you.
Sent from my GT-I9100 using XDA App

Mark719 said:
How do I do it via CWM? Can you do little step by step guide only rough if possible?
Click to expand...
Click to collapse
If only this was already written somewhere, like a FAQ or wiki.

You can boot into recovery mode manually, and choose the zip file from sdcard and flash it straight away. You can also toggle the signature verification there if you get the same error.

1. Download Siyah kernel, open the .zip and copy the zImage file to your SDcard.
2. Install DarkyROM2 app via Android market
3. Choose Flash option in DarkyROM2 tool and select the zImage file copied to SDcard.
Once DarkyROM finishes doing its job you should have ClockWorkMod Recovery installed.
For CM7
1. Download CM7 manually from cyanogenmod.com site
2. Copy the downloaded zip to sdcard
3. Shut of your phone and power it on using volume up+home+power
4. Hold it till you get to a screen with lots of options in orange or blue color thats CWM
5. Do a factory data reset ( Will delete all apps/settings )
5. Select Install zip from sdcard > Choose zip from sdcard > select CM7 zip you copied
say ok.
6. Reboot your device, done .. you should boot into CM7.

[Q] Please help me, error while flashing

Hi guys, I hope you can help me.
I have just rooted + flashed my motorola defy plus for the first time (on any device for that matter)
I installed 2nd init, version 0.6.... or something.
Put a rom, kernel and google apps on my sd-card
Then I turned usb-debugging off and rebooted my phone.
Now I can get into bootmenu, and this is what I do:
1) go to recovery
2) select custom recovery
3) then it says: Clockworkmod Recovery v2.5.1.8
E: Can't open /tmp/recovery.log
4) I then select wipe data/factory reset
5) then it says this: Formatting DATA
Formatting CACHE
FORMATTING SDEXT
No app2sd partition found. Skipping format of /sd-ext
Formatting SDCARD:/.android_secure
Data wipe complete
E: Can't open /tmp/recovery.log
6) After that i select install zip from sdcard
7) then I select choose zip from sdcard
8) then I select the zip file containing the rom
9) And it says: Finding update package
Opening update package
Installing update
E: Can't make /tmp/update_binary
Installation aborted
Now I can't go any further and can't use my phone at all
I hope u guys can help me, and that I haven't F*ed up my phone

I have a quite similar problem.
On a defy+,rooted 2ndinit installed, backup-ed first, download the new quarx05/03 ICS, put the zip on sd, wipe data, reboot and start to install ics, but the message was
''Finding update package
Installing update
E: Can't make /tmp/update_binary
Installation aborted"
Thanks to the previously backup I can use may phone as usual.
What I have done wrong with de ICS installation?
Thanks
PS. Sorry for probable a dummie question:What we have to do with md5 zip near the CM9 Jordan.zip?

A little help please about the subject?
Thank you

ics
The entire process
ClockworkMode v2.5.1.8
Wipping data...
Formatting DATA...
Formatting CACHE...
Formatting SDEXT..
No app2sd partition found.Skipping format of /sd-ext.
Formatting SDCARD: /.android_secure...
Data wipe complete
E: Can't open /tmp/recovery.log...
Installing: SDCard:download/CM9-ICS-MR1-120305-jordan.zip
Finding update package
Opening update package
Installing update
E: Can't make /tmp/update_binary
Installation aborted
if try Wipe Dalvik Cache:
E: Can't mount /dev/block/mmcblk0p2
(No such file or directory)
I guess that this is a simple and many times occured error, since nobody has any answer....

Does you disabled the usb debugging before flashing?

Yes I do, but nothing change,
Thanks

if I'm not mistaken the last release of 2nd init is not compatible with defy. Try to check this on the development forum. I hope I have been of help.

I'd tried with both 1.0.7 latest and 0.6.1.
With latest, the phone is blocked.
Thanks

I had used this. Try with it
P.S. sorry for my bad english.

Tried, the same errors,
Thanks

I don't know. Sorry. By the time i had used that.

I think you need to go to stable recovery after you wipe your data from custom recovery
Sent from my MB525 using xda premium

I think you need to go to stable recovery after you wipe your data from custom recovery
What do you mean by "stable recovery"? You talk about version 0.6. of 2nd init or something else?
Can you show a step-by step procedure?
Thank you in advance.
However, which is the procedure to un-root a defy+ and to have it with the original, fresh system?

I had flash a new SBF, root with Unlockroot v2.3, anything else doesn't work, 2ndinit v2.0 stable, wipe data/cache/dalvik (same errors), try to install cm9-ics, the same error "Can't make /tmp/update_binary"
What the f.....?

cretu22 said:
I had flash a new SBF, root with Unlockroot v2.3, anything else doesn't work, 2ndinit v2.0 stable, wipe data/cache/dalvik (same errors), try to install cm9-ics, the same error "Can't make /tmp/update_binary"
What the f.....?
Click to expand...
Click to collapse
Hi, I have exactly the same problem.. Trying to find a solution but is quite difficult. First I thought it has something to do with the partitioning, as stated in THIS topic. But, in THIS topic, people say that partitioning the SD card is not necessary at all..

@Cretu22: Yes stable recovery is CWM 0.6
Don't install stable recovery! I too faced this issue when I flashed using stable recovery. In snd init install Latest recovery and then try flashing your ROM. That should work..

I did choose the stable version indeed 0.6.7.
Now i did uninstall it and installed the latest 1.0.7, but when I reboot my phone it won't get into the boot menu but just boots into android. Tried it several times, but only with 0.6.7 I seem to be able to get in the menu

fokkeh said:
I did choose the stable version indeed 0.6.7.
Now i did uninstall it and installed the latest 1.0.7, but when I reboot my phone it won't get into the boot menu but just boots into android. Tried it several times, but only with 0.6.7 I seem to be able to get in the menu
Click to expand...
Click to collapse
Okay!! I hope you were pressing the volume down button when the blue LED came?? Try doing this again all over.. I mean reinstall 2nd init and then latest recovery.. I remember doing this once(instal latest recovery after I installed stable recovery)..

pranks1989 said:
Okay!! I hope you were pressing the volume down button when the blue LED came?? Try doing this again all over.. I mean reinstall 2nd init and then latest recovery.. I remember doing this once(instal latest recovery after I installed stable recovery)..
Click to expand...
Click to collapse
Yes, its working Pressing the volume down button was not necessary with 0.6.7, that was what went wrong. Now the zips installed like a charm

i know the answer and is very simple
the problem is that you cannot create that specific folder.... because it already exist, cmp (connected music player) creates it, just delete it from SD and done!

[RESOLVED] How do I restore factory Rom (from Revolution HD 3.0.1 on TF101)?

I am running the Revolution HD rom, this is how I purchased my TF101 from a friend, and I want to restore the factory rom so I can get ICS and the update for the battery issue until mike gets it implemented into Revolution.
How can I do this?
Thanks!

-edit- nevermind, I didn't notice you were running revolution.

If you want to flash back to stock, go to the ASUS Support site and download the 9.2.1.11 firmware for your device.
Unzip it 1 time (there is a zip file within the zip) so it will still have a zip.
Put the file on a microSD or the internal /sdcard/ directory depending on your version of CWM and where it can read.
Boot to CWM.
Install zip.
Choose the zip you downloaded.
Now you will be back to stock unrooted with stock recovery.
Then you will need to check for updates and grab the latest update from ASUS OTA.
If you want to root again you will need to vipermod option 1 to get root access.

Ah, thank you Fred! I did exactly that and it failed but it was the zip within a zip that killed me!

The update is actually failing with the following error:
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
Any ideas?

gbatt said:
The update is actually failing with the following error:
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
Here's exactly what I did to go from Revolution HD 3.0.1 back to stock Asus ICS 9.2.1.11
1. Download the firmware from Asus website. The file name was US_epaduser9_2_1_11UpdateLauncher.zip. You unzip this. You get US_epad-user-9.2.1.11.zip. You put US_epad-user-9.2.1.11.zip on your microSD card.
2. Boot into CWM
3. Factory reset
4. Clear Cache
5. Clear dalvik cache
6. Mount & Storage - format /system
7. Mount & Storage - format /cache
8. Power off(from CWM menu, might be under advanced, I forgot)
9. Boot into CWM.
10. Install zip from sdcard. Choose US_epad-user-9.2.1.11.zip on your microSD.
11. Reboot after flashing is complete.
12. You should now be on Asus stock ICS with stock recovery.
13. I didn't add any of my google accounts during the initial setup because I wanted to do it after I do the 9.2.1.17 update.
14. Shut off and do a cold boot.
Worked perfectly fine for me.
What didn't work was, I was not getting the 9.2.1.17 update afterwards.
So I rooted using Vipermod, installed CWM, and manually flashed the update through CWM. I had to re-root after the update. Simply ran Vipermod again.
Been 2+ days, and it's super stable with great battery life. Not a single random reboot or crash.

gbatt said:
The update is actually failing with the following error:
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
You probably have a custom recovery that doesn't mount the staging partition. You can mount it manually through adb in recovery "mount /dev/block/mccblk0p4 /staging" or flash a repackaged stock rom. At this point, you will probably have a stock system, but not the boot.img, bootloader, or recovery. The blob will flash the those parts, including the recovery, so you will be unrooted with a stock recovery.
sent from my cyanogen(mod) vision

gee one said:
You probably have a custom recovery that doesn't mount the staging partition. You can mount it manually through adb in recovery "mount /dev/block/mccblk0p4 /staging" or flash a repackaged stock rom. At this point, you will probably have a stock system, but not the boot.img, bootloader, or recovery. The blob will flash the those parts, including the recovery, so you will be unrooted with a stock recovery.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Ya, its ClockworkMod Recovery v3.1.0.1.
I tried Horndroids steps above and its still the same error.
I'm sorry but how do I "mount manually through adb"?
Ive only ever used clockworkMod

gbatt said:
Ya, its ClockworkMod Recovery v3.1.0.1.
I tried Horndroids steps above and its still the same error.
I'm sorry but how do I "mount manually through adb"?
Ive only ever used clockworkMod
Click to expand...
Click to collapse
I am pretty sure my CWM Recovery was 3.1.0.1 too.
Try replacing your CWM with Rogue XM Recovery http://forum.xda-developers.com/showthread.php?t=1446019

Awesome! That worked great. Thanks Horndroid!