Database Develop

recovery 3e modified to work like recovery 2e - Updated 01/23/2011

there are a number of problems with the recovery in the just leaked
Froyo ROM.
1. signature checking
2. passing API version 3 to the updater binary
3. forced wipe after installing an update.zip
the attached zip has a 3e recovery modified to disable signature checking
report API version 2 for backwards compatibility with clockwork mod recovery
and disable the forced wipe after installing any update.
I don't know of any reason to run this version over 2e but it
might be useful to someone.
Installing:
1. turn on USB debugging
2. plug into computer
3. run script and follow on screen prompts.
UPDATED 01/23/2011
fixed path error when space in user name
UPDATED 01/22/2011
compressed the rageagainstthecage resource to prevent anti-virus detection
new anti-virus report
http://virscan.org/report/8e83f338fd7b8631c6b0bc0679efbd29.html
the /system file system is full on the newer ROM's
use the attached update.zip to root then install clockwork

Nice
Sent from my SGH-T959 using XDA App

ummmm... what attached zip?

kuhan said:
ummmm... what attached zip?
Click to expand...
Click to collapse
forgot to upload it.

kuhan said:
ummmm... what attached zip?
Click to expand...
Click to collapse
The one attached to the message(?)

fearmonkey said:
The one attached to the message(?)
Click to expand...
Click to collapse
yeah, he attached it after that post lol

how do you use this?
ok i wil bite. how do you use/flash this it cw is not accesible?

rename to update.zip i assume...... i mean thats how u flash everythign thats zip file if u cant get into clockwork.....

you cant flash this you will have to put the files on the internal sdcard
then use root explorer or adb to move the files into place, recovery goes to
/system/bin and the keys to /efs, update.zip is the clockwork recovery and
stays on the sdcard.
when you boot into recovery and choose re-install packages clockwork will
be able to do its thing.
I do like the sig verification but it's a PITA and may disable it, this is a temp
fix until I can finish hacking on recovery there is very little clues as to where
the functions are so it may be a few days.
forgot to mention to you also have to remount /system rw
mount -o rw,remount /dev/block/stl9 /system

Be-ware. Doing so on the ODIN 2E version will break Recovery all together.
Fine to replace on the Stock 2.2 ..
Ps.
Another Awesome Job untermensch

Not to sound like a total noob, but what benefit does this have over the current 2e recovery?

option94 said:
Not to sound like a total noob, but what benefit does this have over the current 2e recovery?
Click to expand...
Click to collapse
I haven't tried just replacing 3e with 2e, I doubt there is any advantage to
3e, to us anyway. but it is always worth while to find ways around these
things.
EDIT:
just replacing 3e with 2e did not work cant find the update.zip

Im suprised more people havent commented. I downloaded the first Stock version of JK2 and i tether so redownloading is not really what i wanted to do...plus i have a Mac so Id have to borrow my buddys pc again...anyway
This workedvgreat! For thise who might need it:
Place all files on the root of SD internal memory card
Copy keys file to /efs
Copy recovery file to /system/bin/ (backup old on first)
Leave all other files on SD internal
Reboot into stock recovery and select Reinstall Packages
itll do its thing and reboot into stock recovery again. From there youre set...just select reinstall packages each time.
Youre a life saver...thank you sir!

TJD319 said:
Im suprised more people havent commented. I downloaded the first Stock version of JK2 and i tether so redownloading is not really what i wanted to do...plus i have a Mac so Id have to borrow my buddys pc again...anyway
This workedvgreat! For thise who might need it:
Place all files on the root of SD internal memory card
Copy keys file to /efs
Copy recovery file to /system/bin/ (backup old on first)
Leave all other files on SD internal
Reboot into stock recovery and select Reinstall Packages
itll do its thing and reboot into stock recovery again. From there youre set...just select reinstall packages each time.
Youre a life saver...thank you sir!
Click to expand...
Click to collapse
thanks...
just updated the first post with a new version.
whats new
Code:
dissables forced post install wipe, dissables signature checking, and reports
API version 2 for backwards compatability with clockwork mod recovery.

Thanks man i rreally appreciate this like i said before. Working perfect snd no issues. Loving being able to CWM again ha. Anyway thank you again sir keep it up!

TJD319 said:
Im suprised more people havent commented. I downloaded the first Stock version of JK2 and i tether so redownloading is not really what i wanted to do...plus i have a Mac so Id have to borrow my buddys pc again...anyway
This workedvgreat! For thise who might need it:
Place all files on the root of SD internal memory card
Copy keys file to /efs
Copy recovery file to /system/bin/ (backup old on first)
Leave all other files on SD internal
Reboot into stock recovery and select Reinstall Packages
itll do its thing and reboot into stock recovery again. From there youre set...just select reinstall packages each time.
Youre a life saver...thank you sir!
Click to expand...
Click to collapse
Thanks untermensch for your work and thanks to the TJD319 for the clear step by step instructions.

Getting can't mount partition after I select a zip file to flash. I can get to cwr fine and it sees the sdcard (internal) fine since I can navigate and select the file I want. The error comes when I try flash. All the files in the zip are in the root of the sd internal, except for recovery and keys that are in the directory /system/bin and /efs respectively. Any advice?

untermensch said:
thanks...
just updated the first post with a new version.
whats new
Code:
dissables forced post install wipe, dissables signature checking, and reports
API version 2 for backwards compatability with clockwork mod recovery.
Click to expand...
Click to collapse
I personally want to say Thanks for Working on this... I Honestly like this version better than the 2e due to being able to wipe the SD-card now..
Thanks for everything.

eugene373 said:
I personally want to say Thanks for Working on this... I Honestly like this version better than the 2e due to being able to wipe the SD-card now..
Thanks for everything.
Click to expand...
Click to collapse
Thanks for the support Eugene....
updated the no sig check version again, too fix the issue that even though the key
is never used, recovery still looked for the existence of the file and would error out if not found.

untermensch said:
Thanks for the support Eugene....
updated the no sig check version again, too fix the issue that even though the key
is never used, recovery still looked for the existence of the file and would error out if not found.
Click to expand...
Click to collapse
Yo man i really appreciate your work. Froyos been great to me Stock 2.2 and this is perfect man. Working flawlessly for me and Im just happy to be able to nandroid.

[HOWTO] get root back after ota update!

this is how i did it anyways. i had to flash the boot.img and update via stock recovery to get the ota to flash. but then no root!
so heres how i got it back:
download the superboot/paulobrien method (http://forum.xda-developers.com/showthread.php?t=882333).
boot phone to fastboot.
Code:
fastboot boot boot.superboot.img
let phone boot, open terminal, su, just to check.
reboot phone.
rooted and ota'd now!

I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
The method I used was:
1. Boot into fastboot.
2.
Code:
fastboot flash recovery recovery-clockwork-3.0.0.0-crespo.img
3. Reboot from fastboot directly into recovery (not doing so will cause android to replace CWR).
4. Mount USB, copy su-2.3.6.1-ef-signed.zip to the /sdcard via windows/linux
5. Mount /system
6. Install update from zip (browse to were you put su-2.3.6.1-ef-signed.zip).
7. Install it, and reboot.
8. open root explorer, and rename /etc/install-recovery.sh to install-recovery.sh.old
9. open ROM Manager, reflash CWR.
now you are all done, rooted, w/ CWR

I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).

Luxferro said:
I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
Click to expand...
Click to collapse
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.

distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
im using stock recovery.

I'm rooted on 2.3.1 but I lose clockwork recovery when I reboot an gota reflash it using rom manager. Anyone having this problem

k0mpresd said:
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.
Click to expand...
Click to collapse
Sure it is. But on Android bootup, a script is running somewhere to replace it with stock recovery. They did this on Droid_1 after the first or second update (that's my only other android phone... so my android experience is limited).
edit: I just found the script. It's /etc/install-recovery.sh .... just renamed my to install-recovery.sh.old. gonna reflash CWR and test it now.
edit2: yep, works great now. CWR, and retained my 2.3.1 boot.img

So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone

chris6278 said:
So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone
Click to expand...
Click to collapse
No, it's a safety mechanism so you can't lose recovery... It has nothing to do with clockworkmod. Someone can make a root script or app that disables it easily. Or people can just do it themselves manually.
edit: actually, all that needs to be done is add some code to the update script inside su-2.3.6.1-ef-signed.zip so when it installs the update, it renames install-recovery.sh

distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks

If u dont mind can u please provide the instructions on how to do it manually. Id really appreciate it. Sorry im a noob lol

Where in root explorer do i need to rename

Where in root explorer do i rename it

plmiller0905 said:
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks
Click to expand...
Click to collapse
chmod needs to be done at a # prompt.

chris6278 said:
Where in root explorer do i rename it
Click to expand...
Click to collapse
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...

Is it just me or does adb remount no longer work?
If I use the old koush rootboot.img it works, but no wifi, if I use the stock boot.img, I get no wifi but am able to remount.

I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes

chris6278 said:
I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes
Click to expand...
Click to collapse
do you have root explorer? if not, it's just a file explorer that has root access. by default when you open it you are at /
you need to scroll down to /etc
go in that folder and find the install-recovery.sh
look up top for the button to turn it from read-only to read-write, click it
go back to the file long press it, and then choose rename.

Luxferro said:
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...
Click to expand...
Click to collapse
Thanks..I already rerooted but thanks anways

I got root explorer an followed ur directions an now everything works great. Thanx for ur help an sorry for being a pain lol

How to install OTA files?

On sammobile these days a few OTA files are available, one like this. Can anybody help how to use this .zip file. The contents of the file are,
1. debug_info (1KB)
2. delta.hidden (856KB)
3. delta.modem (1KB)
4. delta.platform (78396KB)
5. delta.Sbl (1280KB
6. delta.ua (241KB)
7. delta.zImage (4855KB)
FYI these files are not Recovery or CWM flashables.
Above file is an update of firmware to N7000DDLR8 from the previous firmware DDLR6 for indian GalaxyNote. As one can see it includes the firmware files, so be assured that it can be installed. But How???

yogeshmishra23 said:
On sammobile these days a few OTA files are available, one like this. Can anybody help how to use this .zip file. The contents of the file are,
1. debug_info (1KB)
2. delta.hidden (856KB)
3. delta.modem (1KB)
4. delta.platform (78396KB)
5. delta.Sbl (1280KB
6. delta.ua (241KB)
7. delta.zImage (4855KB)
FYI these files are not Recovery or CWM flashables.
Above file is an update of firmware to N7000DDLR8 from the previous firmware DDLR6 for indian GalaxyNote. As one can see it includes the firmware files, so be assured that it can be installed. But How???
Click to expand...
Click to collapse
normal recovery --> install update.zip?

DMax99 said:
normal recovery --> install update.zip?
Click to expand...
Click to collapse
As mentioned in OP, this file is not updated by Recovery. It returns error with both the Recovery and CWM.

yogeshmishra23 said:
As mentioned in OP, this file is not updated by Recovery. It returns error with both the Recovery and CWM.
Click to expand...
Click to collapse
you can try to rename the file to update.zip and then choose update from recovery. Dont know if this will help but its worth a try.

It gives a signature verification error not sure just renaming it to update.zip would fix it!

jaskiratsingh said:
you can try to rename the file to update.zip and then choose update from recovery. Dont know if this will help but its worth a try.
Click to expand...
Click to collapse
Tried all these before posting. No luck
!
tommy_vercetti said:
It gives a signature verification error not sure just renaming it to update.zip would fix it!
Click to expand...
Click to collapse
That is true for Recovery and CWM shows Installation Aborted message.
Sent from my GT-N7000 using xda premium

Instruction available at this link on sammobile.
http://www.sammobile.com/2012/08/25...999-android-4-1-1-jelly-bean-test-ota-update/
But already tried, stock recovery gives signature verification error.
Sent from my GT-N7000 using xda premium

You should be on complete stock ROM
non rooted and on unsafe kernel then may it work, and thats is the point to be concern. This work with unsafe kernel as well update also contains unsafe kernel, so anything lead to messing your device, that will be risky to wipe anything. and in this situation you have to first flash safe kernel.
Mobile odin pro added support for flashing OTA files, but unfortunately didn't recognise OTA files which available for india. (this fuction in mobile odin is still on experiments)

struggling to get the same working , but in vain ...

Please tell me i download the bin file from the following site. how i install this
http://www.sammobile.com/firmware/?page=3&model=GT-P7510&pcode=0&os=1&type=3#firmware

i dont think any has been able to get the OTA downloaded from sammobile to work.
what r u trying to download.. which firmware?

yasirshafiq said:
Please tell me i download the bin file from the following site. how i install this
http://www.sammobile.com/firmware/?page=3&model=GT-P7510&pcode=0&os=1&type=3#firmware
Click to expand...
Click to collapse
using this method:
All Credits to tracid
1. Copy all files from the archive to /cache/fota/ or /data/fota if you have bigger ota
/cache folder is only 192 MB
use root explorer
2. from adb shell:
su
chmod -R 0777 /cache (optional)
echo -n "--install_fota" > /cache/recovery/command
exit
adb reboot recovery

doc.. i tried that last time with the DDLR9 update and i was stuck in boot loop.

Really I didn't tried yet, it was said by tracid somewhere.
Sent from my GT-N7100 using xda premium

Isn't mobile odin able to flash ota updates?
Sent from my Galaxy Note running ICS

no.. it doesnot recognize it as a valid update.zip

Hey doc where have you been lately sir??? Busy with note 2??? Plz dnt leave our note1 and haven't seen you in the jelly been thread as well which has been so active for the last few days sir...
Sent from my GT-N7000 using xda app-developers app

Yeah busy with note2 forum but still keeping eyes here too.
Sent from my GT-N7100 using xda premium

any answer here ? philiz touch recovery dosnt work well

hello ppls
when i install mods on the recovery like "fly on mod" or "PurePerfomance X"
the recovery give me error status 7 any help please ?

iSpammer said:
hello ppls
when i install mods on the recovery like "fly on mod" or "PurePerfomance X"
the recovery give me error status 7 any help please ?
Click to expand...
Click to collapse
I've been given this link, it did not work for me but nevertheless, it's worth a try
http://forum.xda-developers.com/showthread.php?t=2302599

peter-k said:
I've been given this link, it did not work for me but nevertheless, it's worth a try
http://forum.xda-developers.com/showthread.php?t=2302599
Click to expand...
Click to collapse
nothing work :s
while flashng the mod it say
Fixing permissions
set_perm : some changes failed
E: Error in /storage/sdcard0/bluetooth/signed_fly-on_mod__v4.0-beta6.zip
(Status 7)
installation aborted
press any key to continue

iSpammer said:
nothing work :s
while flashng the mod it say
Fixing permissions
set_perm : some changes failed
E: Error in /storage/sdcard0/bluetooth/signed_fly-on_mod__v4.0-beta6.zip
(Status 7)
installation aborted
press any key to continue
Click to expand...
Click to collapse
I don't think it would be a problem with the updater-script, but on the other hand, you could try changing recoveries. Honestly, I wouldn't think this is the problem; I've flashed just about everything using different recoveries, and the only time I've had problems is with what @peter-k posted.
Then again, it's not like you're flashing a ROM or replacing system files, so you could always copy the files manually with Root Explorer and correct permission.
Also, since your problem is at a permission level, you might just have to fix permission (Root Explorer).
Open a terminal emulator (or ADB) and type:
Code:
su
Fly-On
That should tell you if it's installed or not, regardless of the error you got in recovery.

Maybe you'd want to try with the RC1, instead of the Beta version. I just flashed it and got no errors (CWM 6.0.5.0), although both updater scripts are identical except for the "delete("/system/etc/init.d/03kill_media_server");" line.
What ROM are you on?

Antiga Prime said:
Maybe you'd want to try with the RC1, instead of the Beta version. I just flashed it and got no errors (CWM 6.0.5.0), although both updater scripts are identical except for the "delete("/system/etc/init.d/03kill_media_server");" line.
What ROM are you on?
Click to expand...
Click to collapse
thanks i will try it now
i am on stock rom 4.3 locked bootloader , i am using an app called "Universal int.d" for int.d script support
edit : dosnt work also
even when downloading and installing the cwm v8 for locked bootloader i get the same error :/

iSpammer said:
thanks i will try it now
i am on stock rom 4.3 locked bootloader , i am using an app called "Universal int.d" for int.d script support
edit : dosnt work also
even when downloading and installing the cwm v8 for locked bootloader i get the same error :/
Click to expand...
Click to collapse
Well then don't flash it, copy the files manually and set permissions manually, there aren't that many files.
Files in /system/etc/rngd and /data/Fly-On should be assigned to user/group: root/shell, permissions: rwxrwxrwx.
Every other file should have user/group set to: root/root, and same permissions as before.

Antiga Prime said:
Well then don't flash it, copy the files manually and set permissions manually, there aren't that many files.
Files in /system/etc/rngd and /data/Fly-On should be assigned to user/group: root/shell, permissions: rwxrwxrwx.
Every other file should have user/group set to: root/root, and same permissions as before.
Click to expand...
Click to collapse
thanks you

[TOOL] Zenfone 2 boot repack

I see here and there requests about re-packing boot.img for ZF2.
Here are tools i'm using to re-pack my images for ZF2. This is for Linux. Just unpack attached archive to some directory. Put boot.img (or recovery.img renamed to boot.img) to the same directory and run extract_boot. Everything will be unpacked to boot sub-directory. Then you can modify boot/ramdisk directory as much as you want. When you finish, run make_boot and you will get boot.img ready to flash to ZF2.
Note1:
Generated boot.img set SELinux mode to permissive. This is better mode for modified boot/ROM. It will solve most problems you may encounter on custom ROMs.
Note2:
You HAVE to have unlocked bootloder in order to be able to boot the boot.img.
Note3:
Do not flash modified droidboot.img to ZF2! If somehow your bootloader will re-lock, you won't be able to boot anywhere if all three bootable partitions (boot.img, recovery.img, droidboot.img) will be modified. So, you will get bricked ZF2.

sorg said:
I see here and there requests about re-packing boot.img for ZF2.
Here are tools i'm using to re-pack my images for ZF2. This is for Linux. Just unpack attached archive to some directory. Put boot.img (or recovery.img renamed to boot.img) to the same directory and run extract_boot. Everything will be unpacked to boot sub-directory. Then you can modify boot/ramdisk directory as much as you want. When you finish, run make_boot and you will get boot.img ready to flash to ZF2.
Note1:
Generated boot.img set SELinux mode to permissive. This is better mode for modified boot/ROM. It will solve most problems you may encounter on custom ROMs.
Note2:
You HAVE to have unlocked bootloder in order to be able to boot the boot.img.
Note3:
Do not flash modified droidboot.img to ZF2! If somehow your bootloader will re-lock, you won't be able to boot anywhere if all three bootable partitions (boot.img, recovery.img, droidboot.img) will be modified. So, you will get bricked ZF2.
Click to expand...
Click to collapse
nice..thank you @sorg.. eventho I dont know on how to develop custom kernel..
can only wait for developers to release their custom kernel tester..

<deleted>

Great tool.
+1

Btw can you create same program for Windows?

can i use this to my asus ze500cl?

themonyo666 said:
can i use this to my asus ze500cl?
Click to expand...
Click to collapse
Maybe yes.
Try it.

Any love for windows?

S#@DY said:
Any love for windows?
Click to expand...
Click to collapse

mr_gourav2000 said:
Click to expand...
Click to collapse
Irrelevant reply, but I've got it. Thanks to @cieffe54

S#@DY said:
Irrelevant reply, but I've got it. Thanks to @cieffe54
Click to expand...
Click to collapse
Please share with us.

mr_gourav2000 said:
Please share with us.
Click to expand...
Click to collapse
Check your pm

S#@DY said:
Check your pm
Click to expand...
Click to collapse
Wow