Related
can someone tell me how to uninstall clockworkmod
trapharder4844 said:
can someone tell me how to uninstall clockworkmod
Click to expand...
Click to collapse
The Clockwork Recovery?
yes the recovery i dnt like i want the regular recovery back
trapharder4844 said:
yes the recovery i dnt like i want the regular recovery back
Click to expand...
Click to collapse
Just reflash the regular recovery back
trapharder4844 said:
yes the recovery i dnt like i want the regular recovery back
Click to expand...
Click to collapse
Ok you can follow these instructions
http://forum.xda-developers.com/showthread.php?t=705026
OR the method I perfer:
put the new recovery you want on the sdcard and name it recovery.img
also put flash_image on the sd card..
here is a link to flash_image
http://cybermetricsystems.net/android/flash_image.zip
Here is the cool EVO recovery by Amon_RA <--for easyness be sure to rename it to recovery.img
recovery-RA-evo-v1.7.0.1.img
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
reboot recovery
rjmjr69 said:
Just reflash the regular recovery back
Click to expand...
Click to collapse
where is the regular recovery
trapharder4844 said:
where is the regular recovery
Click to expand...
Click to collapse
Use the one I posted. It was made for the EVO.
apristel said:
Ok you can follow these instructions
http://forum.xda-developers.com/showthread.php?t=705026
OR the method I perfer:
put the new recovery you want on the sdcard and name it recovery.img
also put flash_image on the sd card..
here is a link to flash_image
http://cybermetricsystems.net/android/flash_image.zip
Here is the cool EVO recovery by Amon_RA <--for easyness be sure to rename it to recovery.img
recovery-RA-evo-v1.7.0.1.img
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
reboot recovery
Click to expand...
Click to collapse
so i really need to do step two of toast root process over again
trapharder4844 said:
so i really need to do step two of toast root process over again
Click to expand...
Click to collapse
No just do the code in the box i provided. I never said to do that root part 2 over!
apristel said:
No just do the code in the box i provided. I never said to do that root part 2 over!
Click to expand...
Click to collapse
thanks i did it work like a charm
trapharder4844 said:
thanks i did it work like a charm
Click to expand...
Click to collapse
Thats what we are here for!
Glad to help.
How do you use the code in the box?
daddysal said:
How do you use the code in the box?
Click to expand...
Click to collapse
through your command prompt
daddysal said:
How do you use the code in the box?
Click to expand...
Click to collapse
You need the android SDK..
then you goto the tools folder within the download and use adb shell.
apristel said:
You need the android SDK..
then you goto the tools folder within the download and use adb shell.
Click to expand...
Click to collapse
Is android sdk in the market?
daddysal said:
Is android sdk in the market?
Click to expand...
Click to collapse
Android SDK is - if explained by simple means - a tool on the computer that gives it's user the ability to "customise" , "code" , "1337ise" his Android ( 1337 in videogaming usually refers to elite players ) and it is used in the making of All ROMs ( Operating system would give a close meaning ) that you see on the internet like the Cyanogen one , etc... If you are looking for Android SDK you will find it on
http://developer.android.com/sdk/index.html
Anyone happen to have an updated flash_image link?
ExcaliburXVII said:
Anyone happen to have an updated flash_image link?
Click to expand...
Click to collapse
Check amonRAs thread. Its there.
Sent from my PC36100 using XDA Premium App
Here
http://db.tt/tAQqfgQ
Not sure if you jave to rename it pc36img or if you need to use terminal. Its been a long time, I forget. Bit this is what you need. Try the pc36.img method thru hboot first cuz I thing this zip is for that.
Sent from my PC36100 using XDA Premium App
Does anyone have a new flash image?
Full release post is here and I'll update at xda soon.
http://androidforums.com/lg-optimus...ry-optimus-one-p500-thunderg.html#post1896517
I got all the bugs worked out thanks alahkel & fughy for testing and of course Amon-Ra for original source.
New link version 2.2.1 Version 2.2.1
New version 3.06 Version 3.06
Thanks to you for the whole great work you've done!
We really appreciate that.
really GREAT WORK !!!!
Please, i need some info, how use adb on P500.
Absolute AWESOME!!!
Thanks!
Thanks !
works like a charm. I have installed your custom recovery. Backed up everything with nandroid, tried KeruROM, flashed back my original branded ROM from nandroid backup.
Everything works. I'm not going to try flash back my original recovery mtd, there is no reason to do it, but have a dd backup just in case. I don't know if it is safe to tamper with recovery mtd, cause I'm not sure if it is re-flashed after every system shutdown. I don't think so, cause I haven't found recovery.img in /system.
I have two questions regarding flashing custom recovery. I haven't used this command:
Code:
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
cause, i didn't found this script on my phone. Is it ok?
Second question: Is it mandatory to copy flash_image to /system/bin with this command?
Code:
cat /sdcard/flash_image > /system/bin/flash_image
Can't we use /data/local/tmp directory and running flash_image from there as we used in the process of rooting the phone? This way we don't have to remount /system in rw and do not have to modify it.
Now I'm going to explore ROM modding ;-)
Vintersorg said:
Thanks !
works like a charm. I have installed your custom recovery. Backed up everything with nandroid, tried KeruROM, flashed back my original branded ROM from nandroid backup.
Everything works. I'm not going to try flash back my original recovery mtd, there is no reason to do it, but have a dd backup just in case. I don't know if it is safe to tamper with recovery mtd, cause I'm not sure if it is re-flashed after every system shutdown. I don't think so, cause I haven't found recovery.img in /system.
I have two questions regarding flashing custom recovery. I haven't used this command:
Code:
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
cause, i didn't found this script on my phone. Is it ok?
Second question: Is it mandatory to copy flash_image to /system/bin with this command?
Code:
cat /sdcard/flash_image > /system/bin/flash_image
Can't we use /data/local/tmp directory and running flash_image from there as we used in the process of rooting the phone? This way we don't have to remount /system in rw and do not have to modify it.
Now I'm going to explore ROM modding ;-)
Click to expand...
Click to collapse
Flash_image doesn't have to be there but for simplicity I put it there so it would be in ATH. The install-recovery.sh is an evil script that will rewrite a recovery on boot with stock recovery(that only is there on some phones after an official ota update) so rom markers please remove it if it exists.
Any chance the p509 optimus t is similar enough for this to work? I'm willing to be the guinea pig if it should work.
Joeseph Mother said:
Any chance the p509 optimus t is similar enough for this to work? I'm willing to be the guinea pig if it should work.
Click to expand...
Click to collapse
Its close enough it has a very good chance of working but will take a guinea pig to verify. Kernel should be close enough to try. Only differences I saw in the ramdisk of p500 & p509 was model number and lang of en GB and en Us repectively. I had a bad/corrupt dump to work off of on the p509/T. I could use a good dump source with a md5sum to verify its not corrupted in uploading/downloading.
make sure you do this 1st to backup your stock recovery
from terminal or adb shell
Code:
dd if=/dev/mtd/mtd2 of=/sdcard/recovery-dump-T.img bs=4096
please upload that dump for me with a md5 too and I'll work on an official.
Can it be done without root? As normal user?
Thanks of all to drellisdee
I want to advertise that the custon recovery file is no more available at Media fire link that suggest us.
Waiting that the file will be restored is there someone that can upload it???
Thank's of all!!!
Are you just wanting kernel & recovery dumps, because I think I've already changed most other things on my system
Installs, starts off saying E:Bad boot message "
Button layout is correct.
Usb mounting works.
Wipe appears to have worked.
Backup fails with Error:Run 'nandroid-mobile.sh' via adb!
I was looking for just the custom recovery (recovery-RA-GNM-thunderg-1.1.0.img.zip). Now it's available again!!!!
I think that i 've to apply it anyway.
Then if you say that some new rom and kernel are incoming it could be great!!!!
I hope to learn the necessary to help in development ... in this time i accept your works...
Joeseph Mother said:
Installs, starts off saying E:Bad boot message "
Button layout is correct.
Usb mounting works.
Wipe appears to have worked.
Backup fails with Error:Run 'nandroid-mobile.sh' via adb!
Click to expand...
Click to collapse
You get that error on nandroid if battery is below 30%
Joeseph Mother said:
Are you just wanting kernel & recovery dumps, because I think I've already changed most other things on my system
Click to expand...
Click to collapse
yes I only need the recovery one.
ruigui said:
Can it be done without root? As normal user?
Click to expand...
Click to collapse
It was last post on previous page... Can these backups be done as normal user, or must it be as root?
ruigui said:
It was last post on previous page... Can these backups be done as normal user, or must it be as root?
Click to expand...
Click to collapse
Recovery menu?
Only with root settings....
drellisdee said:
You get that error on nandroid if battery is below 30%
Click to expand...
Click to collapse
I wish it was that easy, battery was 90%.
Stock T recovery:
http://www.mediafire.com/?01bleb4njbf1ccy
md5: b18bd6e79c7b962739816a2f1d4bdacf
personalweb said:
Recovery menu?
Only with root settings....
Click to expand...
Click to collapse
You didn't understand. If i am working on a terminal emulator, must the following command be done as root or can it be done as normal user?
dd if=/dev/mtd/mtd2 of=/sdcard/recovery-dump-T.img bs=4096
Click to expand...
Click to collapse
Can any one help me out in converting .img files (system.img, userdata.img generate uring AOSP ROM build) into files (e.g. factoryfs.rfs,data.rtf etc) flash-able by ODIN?
abhijeet.pathak said:
Can any one help me out in converting .img files (system.img, userdata.img generate uring AOSP ROM build) into files (e.g. factoryfs.rfs,data.rtf etc) flash-able by ODIN?
Click to expand...
Click to collapse
No need to convert... Just do this.
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
dd if=/dev/block/stl6 of=/sdcard/factoryfs.rfs
dd if=/dev/block/stl7 of=/sdcard/datafs.rfs
dd if=/dev/block/stl8 of=/sdcard/cache.rfs
exit
exit
The Dark Lestat said:
No need to convert... Just do this.
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
dd if=/dev/block/stl6 of=/sdcard/factoryfs.rfs
dd if=/dev/block/stl7 of=/sdcard/datafs.rfs
dd if=/dev/block/stl8 of=/sdcard/cache.rfs
exit
exit
Click to expand...
Click to collapse
I have already tried that but my problem is that I am not extracting factoryfs.rfs from phone.
I have compiled froyo from AOSP an got system.img file as a result.
I tried renaming system.img to factoryfs.rfs, but ODIN is saying "Invalid image" in after selecting the file.
abhijeet.pathak said:
I have already tried that but my problem is that I am not extracting factoryfs.rfs from phone.
I have compiled froyo from AOSP an got system.img file as a result.
I tried renaming system.img to factoryfs.rfs, but ODIN is saying "Invalid image" in after selecting the file.
Click to expand...
Click to collapse
We do not have a custom recovery, so flashing the files is impossible.
With a custom recovery, we could've flashed the .img files directly.
The Dark Lestat said:
We do not have a custom recovery, so flashing the files is impossible.
With a custom recovery, we could've flashed the .img files directly.
Click to expand...
Click to collapse
I also extracted contents of system.img and repackaged it as update.zip.
But after selecting "apply sdcard:update.zip", it gives error like:
unable to mount /dev/block/mmblk something... an then
unable to mount SDCARD;update.zip
Installation aborted.
abhijeet.pathak said:
I also extracted contents of system.img and repackaged it as update.zip.
But after selecting "apply sdcard:update.zip", it gives error like:
unable to mount /dev/block/mmblk something... an then
unable to mount SDCARD;update.zip
Installation aborted.
Click to expand...
Click to collapse
As I've already said, we cannot flash it because we don't have a custom recovery.
By default, FroYo recovery flashing is dead.
The Dark Lestat said:
As I've already said, we cannot flash it because we don't have a custom recovery.
By default, FroYo recovery flashing is dead.
Click to expand...
Click to collapse
Then in this case, what can be done if I just want to package the files from system.img into factoryfs.rfs and flash them using ODIN?
abhijeet.pathak said:
Then in this case, what can be done if I just want to package the files from system.img into factoryfs.rfs and flash them using ODIN?
Click to expand...
Click to collapse
I think converting them will corrupt them. As of right now, I do not know of a way.
abhijeet.pathak said:
Then in this case, what can be done if I just want to package the files from system.img into factoryfs.rfs and flash them using ODIN?
Click to expand...
Click to collapse
A possible workaround is to mount a rfs image in magic iso and replace the files with yours
Then flash and it'll work
Another way is use update.bat method like lestat
cdesai said:
A possible workaround is to mount a rfs image in magic iso and replace the files with yours
Then flash and it'll work
Another way is use update.bat method like lestat
But the first one is best
Click to expand...
Click to collapse
The first one corrupts the system.
Sent from my ACID Lestatious 2.0 BUILD 1.7 Galaxy 3 FROYO
The Dark Lestat said:
The first one corrupts the system.
Sent from my ACID Lestatious 2.0 BUILD 1.7 Galaxy 3 FROYO
Click to expand...
Click to collapse
Sorry didn't know that
So any other workaround?
cdesai said:
Sorry didn't know that
So any other workaround?
Click to expand...
Click to collapse
Nope. Using adb to replace the lib files kills the connection.
So, the only way is to flash.
Sent from my ACID Lestatious 2.0 BUILD 1.7 Galaxy 3 FROYO
The Dark Lestat said:
Nope. Using adb to replace the lib files kills the connection.
So, the only way is to flash.
Sent from my ACID Lestatious 2.0 BUILD 1.7 Galaxy 3 FROYO
Click to expand...
Click to collapse
Lib files can be copied to sdcard then remove earlier lib files through terminal emulator via command
"rm -r /system/lib/*.ko"
Copy new files via same method
"cp /sdcard/*.ko /system/lib/"
I think it is possible way.
ROM- Apocalypse 1.0 Beta
Base- XXJPM
Kernel- Apocalypse (Apollo)
Boot Animation- Rudolf
Theme- Arun Verma (Me)
Kernel Scripts- Motafoca
Lock Screen- Kyrillos
forum.samdroid.net/f28/howto-extract-files-samsung-rfs-1693/
You can mount same base rfs file change all files you want or if you need delete all files add files you need and umount you may use root explorer to change files or any other method you find convenient. Remember One thing you'll have to mount rw to make changes.
Edit another link maybe helpful
forum.xda-developers.com/showthread.php?t=751827&page=2
Sent from my GT-I5800 using Tapatalk
arunmcops said:
Lib files can be copied to sdcard then remove earlier lib files through terminal emulator via command
"rm -r /system/lib/*.ko"
Copy new files via same method
"cp /sdcard/*.ko /system/lib/"
I think it is possible way.
ROM- Apocalypse 1.0 Beta
Base- XXJPM
Kernel- Apocalypse (Apollo)
Boot Animation- Rudolf
Theme- Arun Verma (Me)
Kernel Scripts- Motafoca
Lock Screen- Kyrillos
Click to expand...
Click to collapse
That doesn't matter. It still kills ADB.
Maybe someone can edit Heimdall source to add i5800 support and try to flash img from there
we have update.zip now, so that can work
The Dark Lestat said:
No need to convert... Just do this.
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
dd if=/dev/block/stl6 of=/sdcard/factoryfs.rfs
dd if=/dev/block/stl7 of=/sdcard/datafs.rfs
dd if=/dev/block/stl8 of=/sdcard/cache.rfs
exit
exit
Click to expand...
Click to collapse
Hey where to do this.
guyzz plssss say how to read or extract d rfs file plesss
its vvery urgent..... pless guyzz
any software plsss give d link pls
plsss
Chill man
Use magiciso and/or linux disk reader
Btw abhijeet, what about it now- u can flash via cwm or update.zip
Koushik Dutta, creator of ROM Manager, ClockworkMod Recovery today posted on Google+ his new automated Recovery Builder.
All you need is a stock recovery image and press build to port ClockworkMod Recovery to virtually any device.
Builder Link: http://builder.clockworkmod.com/
google+ Link: https://plus.google.com/u/0/103583939320326217147/posts
Ooooooh
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Check the links... pretty interesting though.
I wonder if we can fix the "new recovery" with this. I'm too lazy to try it..
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php
someone do it
BaconStep said:
someone do it
Click to expand...
Click to collapse
yeah some one do it! please...
Normal cwm works fine on sgs3 !!!
Thx!!!
EDIT: ops wrong thread, but very nice tool
Where would I be able to find a recovery image?
Pull it from a stock recovery tarball.
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php
unsupported page size = 16384
I have a rooted PROSCAN plt7035-pl tablet that i've extracted a recovery.img from and uploaded to the recovery builder. The build failed with unsupported page size = 16384. Is there something I can do to fix the pagesize and make it complete the build?
recovery builder console output(shortened):
----- Making recovery filesystem ------
----- Making recovery filesystem ------
mkdir -p /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery
mkdir -p /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root
mkdir -p /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/etc
mkdir -p /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/tmp
Copying baseline ramdisk...
Copying baseline ramdisk...
cp -R /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/root /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery
rm /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/init*.rc
Modifying ramdisk contents...
Modifying ramdisk contents...
cp -f bootable/recovery/etc/init.rc /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/init.rc
cp -f /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/obj/EXECUTABLES/recovery_intermediates/recovery /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/sbin/
rm -f /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/init.*.rc
mkdir -p /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/system/bin
cp -rf bootable/recovery/res /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/
cp -f device/unknown/rk29sdk/recovery.fstab /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/etc/recovery.fstab
cp /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/obj/PACKAGING/ota_keys_intermediates/keys /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/res/keys
cat /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/root/default.prop /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/system/build.prop \
> /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/default.prop
> /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/default.prop
Modifying default.prop
Modifying default.prop
sed -i 's/ro.build.date.utc=.*/ro.build.date.utc=0/g' /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root/default.prop
----- Made recovery filesystem --------/Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root
----- Made recovery filesystem --------/Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root
----- Making uncompressed recovery ramdisk ------
----- Making uncompressed recovery ramdisk ------
/Volumes/Data/hudson/workspace/android/jellybean/out/host/darwin-x86/bin/mkbootfs /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root > /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/ramdisk-recovery.cpio
/Volumes/Data/hudson/workspace/android/jellybean/out/host/darwin-x86/bin/mkbootfs /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery/root > /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/ramdisk-recovery.cpio
----- Making recovery ramdisk ------
----- Making recovery ramdisk ------
/Volumes/Data/hudson/workspace/android/jellybean/out/host/darwin-x86/bin/minigzip < /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/ramdisk-recovery.cpio > /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/ramdisk-recovery.img
/Volumes/Data/hudson/workspace/android/jellybean/out/host/darwin-x86/bin/minigzip < /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/ramdisk-recovery.cpio > /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/ramdisk-recovery.img
----- Making recovery image ------
----- Making recovery image ------
/Volumes/Data/hudson/workspace/android/jellybean/out/host/darwin-x86/bin/mkbootimg --kernel /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/kernel --ramdisk /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/ramdisk-recovery.img --base 0x60400000 --pagesize 16384 --output /Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery.img
error: unsupported page size 16384
make: *** [/Volumes/Data/hudson/workspace/android/jellybean/out/target/product/rk29sdk/recovery.img] Error 255
build error!
Build failed.
Build step 'Execute shell' marked build as failure
Archiving artifacts
Finished: FAILURE
Help us localize this page
Page generated: Dec 29, 2012 7:06:51 PMREST APIJenkins ver. 1.489
Click to expand...
Click to collapse
T.L.Hingan said:
I have a rooted PROSCAN plt7035-pl tablet that i've extracted a recovery.img from and uploaded to the recovery builder. The build failed with unsupported page size = 16384. Is there something I can do to fix the pagesize and make it complete the build?
recovery builder console output(shortened):
Click to expand...
Click to collapse
Glad you could extract the recovery image because I failed when I tried it with the PLT-7035B.:crying:
does look interesting, and I see the potential, but not for our device. Especially when u can just Odin twrp.
mindmajick said:
I wonder if we can fix the "new recovery" with this. I'm too lazy to try it..
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php
Click to expand...
Click to collapse
what new recovery are you talking about? > the leak?
and whats the problem with the new recovery? >
vincom said:
what new recovery are you talking about? > the leak?
and whats the problem with the new recovery? >
Click to expand...
Click to collapse
You quoted an 8 month old post
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
You quoted an 8 month old post
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
lol, seen the date for last few posts, didnt notice majics post date
stupid xda app..stupid page 2...
vincom said:
lol, seen the date for last few posts, didnt notice majics post date
Click to expand...
Click to collapse
icenight89 said:
stupid xda app..stupid page 2...
Click to expand...
Click to collapse
Hahaha, pwned
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
how to use output files of koushik recovery builder
Hello!
Tried using Koushik Recovery Builder but how to use the output files?
I got the following files:
android_device_samsung_espressowifi.zip
inputrecovery.img
recovery.img
manifest.xml
Thanks in advance!
its says
Syncing...
Build was aborted
Aborted by Koushik Dutta
Archiving artifacts
Finished: ABORTED
why was it aborted? im using a a111.
hi
I have this file downloaded...
Code:
-rw-rw-r-- 1 root root 11956224 Nov 14 09:42 openrecovery-twrp-2.6.3.2-hammerhead.img
766b2361daf816eb168df37c55edb709 openrecovery-twrp-2.6.3.2-hammerhead.img
The md5 matches the one on goo.im...
Can I install this "safely" from a Android terminal emulator with the following commands...
Code:
#> su -
#> dd if=./openrecovery-twrp-2.6.3.2-hammerhead.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
and then would booting into recovery mode, would start TWRP ?
NOTE: THIS IS A QUESTION... ?
I wish goomanager has option of installing downloaded file... the site is giving 403 Forbidden...
ANYONE ???
Flash the img with fastboot. That's the safest way imo.
Sent using xda-developers app
yep i would flash using fastboot. permissions and stuff might get whacked if not done that way. Not sure just guessing.
Chromium_ said:
Flash the img with fastboot. That's the safest way imo.
Sent using xda-developers app
Click to expand...
Click to collapse
If i knew how to do that, I'd totally do it. lol
My Goo.im app ain't dl'ing twrp.
TheDudeAbides said:
If i knew how to do that, I'd totally do it. lol
My Goo.im app ain't dl'ing twrp.
Click to expand...
Click to collapse
Fastboot flash recovery nameofrecoveryfile.img
Not difficult at all
Sent from my Nexus 5
TheDudeAbides said:
If i knew how to do that, I'd totally do it. lol
My Goo.im app ain't dl'ing twrp.
Click to expand...
Click to collapse
If you go to goo.im it shows that the file has been downloaded over 12071 times!!!
Code:
openrecovery-twrp-2.6.3.2-hammerhead.img
766b2361daf816eb168df37c55edb709
Size: 11.4 MB
MD5: 766b2361daf816eb168df37c55edb709
Link: http://www.goo.im/devs/OpenRecovery/hammerhead//openrecovery-twrp-2.6.3.2-hammerhead.img
Short Link:
(view file changelog)
2013-11-05 14:14:08 PST 12071
Yet every-time I try I get a 403-Forbidden...
My main issue is my Windows is dozing, and am on RedHat most of the time... My ubuntu desktop is in storage so I cant get to
any sort of fastboot...
anyways... I just managed to install the adt on my LMDE (LinuxMintDebianEdition) and am now playing with
udev files... and reading about how to get fastboot working..!
I felt dd was fairly native... and would not cause any permission problems...
anyways.. I will flash the image with fastboot, and then dump the recovery device with dd and check the md5sum..
if it matches, I will try to erase and load it again with dd and see if this method can work..
G
UPDATE
THE dd METHOD WILL NOT WORK
I got fastboot working, loaded the twrp image and rebooted to recovery and it works...
next I dumped the "/dev/block/platform/msm_sdcc.1/by-name/recovery" and checked its md5sum
and it does not match the twrp recovery... so I bet it will not work...
JUST USE fastboot...
MOD: We can close this thread... its answered (by myself)
Click to expand...
Click to collapse