Files in gs3ezrecovery?? - Verizon Samsung Galaxy S III

A newbie, I rooted my phone and was trying to figure out EZRecovery. Ended up bricking the phone and installed a stock image using Odin, but that is a separate issue about which I may write a separate question.
After I installed the stock image, I noticed that there is a folder on the SDCard entitled gs3recovery and inside are 6 files named as follows: 2 (0 bytes), recovery_hyb_invisibleckv2 (5.44MB), recovery_rec_CWM6010 (5.41MB), recovery_rec_CWMT5849 (6.34MB), recovery_rec_stock (6.10MB), and recovery_rec_twrp220 (6.96MB). The latter 5 are all Disk Image Files.
When I was trying to use EZRecovery, I went looking for images in TRWP and CWM folders and didn't find any. Are these the images inside the gs3recovery folder or are they too small to be images?
Could these images be used if I rerooted?

What images are you trying to find? The images in that folder are when you open ezrecovery and use the drop down box to select a recovery to flash, those are the recoveries.
Sent from my SCH-I535 using xda app-developers app

Those are the recovery images that EZRecovery uses to flash a specific recovery onto your phone. There only usable if your rooted, so if you aren't its safe to delete that folder.

kintwofan said:
What images are you trying to find? The images in that folder are when you open ezrecovery and use the drop down box to select a recovery to flash, those are the recoveries.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thank you for your reply.
So let me confirm that you're saying these are images that I could recover using EZRecovery?
I thought that was probably the case, but I had expected the images to be a lot larger than 5-6MB.....like on Windows PC 7 where the image is more than 50% the size of the system drive.

Those are the recovery images. You could even use terminal to flash them using.the dd commands. The app does it for u
Sent from my SCH-I535 using xda premium

Thank you all for responding. Basically then, I have images I could restore but I will have to root to do so.
I won't go into the whole story, but I have to root anyway because I restored a stock image to the bricked phone while the bootloader was unlocked.
I am planning to go back to stock but I can't do that until the bootloader is locked and I have to root in order to do that.
Thanks again.

Related

build.prop update.zip

Is it possible to make an update.zip file that replaces the build.prop file, or any way to replace the build.prop file without doing a full restore?
I did it using adb commands.
Well I tried using adb shell to swap the file, but when I ran su I got "[1] + Stopped (signal) su"
So I guess I'm going to be forced to do a nadroid restore of my system
Just use root explorer to copy the file to /sd, then use astro to edit it, and root explorer it back to the original spot and reboot. You don't need to change file permissions or any thing. No computer needed.
Sent from my GT-I9000 using Tapatalk
Boot loop
Clienterror said:
Just use root explorer to copy the file to /sd, then use astro to edit it, and root explorer it back to the original spot and reboot. You don't need to change file permissions or any thing. No computer needed.
Click to expand...
Click to collapse
Hi Clienterror,
What if the system is not booting?
I had installed an application which changes resolution and now ended up with a boot loop.
I have searched for ways how to extract the build.prop and correct the error, but none appears to exist.
I was asking if it is possible to extract the current build.prop via the update.zip method so that the build.prop can be repaired...
I read that from the update.zip you can execute code, would it be possible to use a similar method for extracting files from the system folder?
Thanks
remuscat said:
Hi Clienterror,
What if the system is not booting?
I had installed an application which changes resolution and now ended up with a boot loop.
I have searched for ways how to extract the build.prop and correct the error, but none appears to exist.
I was asking if it is possible to extract the current build.prop via the update.zip method so that the build.prop can be repaired...
I read that from the update.zip you can execute code, would it be possible to use a similar method for extracting files from the system folder?
Thanks
Click to expand...
Click to collapse
You could just reflash your current ROM and it should replace it.
korockinout13 said:
You could just reflash your current ROM and it should replace it.
Click to expand...
Click to collapse
Hi korockinout13,
I have tried to refresh from a rom i got, but I am prompted an error with Nand version.
The android in question is not common (Subor, a chinese Android Tablet) and have not found any firmware for my particular model except for the one supplied by the supplier, which still does not install.
At this stage reflashing is not an option, so I am looking for something else...
Thanks for your time
P
remuscat said:
Hi Clienterror,
What if the system is not booting?
I had installed an application which changes resolution and now ended up with a boot loop.
I have searched for ways how to extract the build.prop and correct the error, but none appears to exist.
I was asking if it is possible to extract the current build.prop via the update.zip method so that the build.prop can be repaired...
I read that from the update.zip you can execute code, would it be possible to use a similar method for extracting files from the system folder?
Thanks
Click to expand...
Click to collapse
Actually there is a potential option... can you get into recovery? And does your recovery have a file manager? If so go into mounts and mount /system. Then use the file manager in recovery and you should be able to access build.prop. copy it to your SD and then you should be able to mount your SD to your computer through recovery.
Edit: when you mount /system make sure you mount the SD as well or you won't be able to copy to it while you're in the recovery file manager.
Sent from my SGH-I897 using xda app-developers app
Hi m1batt1,
The recovery does not have any file mount option
I have lost all hope of being able to get the system to boot.
Thanks the same.
remuscat said:
Hi m1batt1,
The recovery does not have any file mount option
I have lost all hope of being able to get the system to boot.
Thanks the same.
Click to expand...
Click to collapse
You might have to flash stock KK4 at this point and go from there.
What kernel do you have for it not to have a file mount? I believe even stock kernel has it Since you can get in download mode, I would flash a newer kernel if I were you (with Odin) to be able to mount in recovery.
remuscat said:
Hi korockinout13,
I have tried to refresh from a rom i got, but I am prompted an error with Nand version.
The android in question is not common (Subor, a chinese Android Tablet) and have not found any firmware for my particular model except for the one supplied by the supplier, which still does not install.
At this stage reflashing is not an option, so I am looking for something else...
Thanks for your time
Click to expand...
Click to collapse
BWolf56 said:
You might have to flash stock KK4 at this point and go from there.
What kernel do you have for it not to have a file mount? I believe even stock kernel has it Since you can get in download mode, I would flash a newer kernel if I were you (with Odin) to be able to mount in recovery.
Click to expand...
Click to collapse
From what I'm reading he doesn't even have a captivate. He's using some Chinese tablet.
Sent from my SGH-I897 using xda app-developers app

Custom recovery image not sticking

I Having a problem when everytime I go into fastboot mode and click on recovery the /!\ comes up and would have to take the battery out and reflash the custom recovery image thru adb. Then it will work but can someone help make the recovery image stick
Sent from my Nexus S using XDA App
mrnexus said:
I Having a problem when everytime I go into fastboot mode and click on recovery the /!\ comes up and would have to take the battery out and reflash the custom recovery image thru adb. Then it will work but can someone help make the recovery image stick
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
There is a .sh file that needs to be removed, totally forgot the location of it :/
/etc/install-recovery.sh needs to be deleted or renamed.
It's a "safety" feature in 3.3.1 and above to restore the stock recovery if it doesn't pass a check on boot each time.
This is pointed out in numerous threads...search a little for more details if you need them.
Ok thanks
Sent from my Nexus S using XDA App
It wont let me rename so I guess I going to delete it
Sent from my Nexus S using XDA App
mrnexus said:
It wont let me rename so I guess I going to delete it
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Are you mounting the /system partition as read/write?
Use root explorer or similar or issue the remount command from the command line before trying to rename it.
that's the trick just rename the image, and the CW recovery will stick
that's the way it's written in the step by step guide,
distortedloop said:
Are you mounting the /system partition as read/write?
Use root explorer or similar or issue the remount command from the command line before trying to rename it.
Click to expand...
Click to collapse
I am having problems renaming it as well. I'm not sure what you mean by "use root explorer or similar or issue the remount command from the command line before trying to rename it.
I have tried using Astro and Android Mate to rename the file and both will not let me.
EDIT: Nevermind, I used root explorer and was able to find "mount r/w" and rename it finally. Thanks.
godzigga said:
I am having problems renaming it as well. I'm not sure what you mean by "use root explorer or similar or issue the remount command from the command line before trying to rename it.
I have tried using Astro and Android Mate to rename the file and both will not let me.
Click to expand...
Click to collapse
Because those won't allow you to modify system files. Get Root Explorer, like he said, and use that.
AllGamer said:
that's the trick just rename the image, and the CW recovery will stick
that's the way it's written in the step by step guide,
Click to expand...
Click to collapse
weird, i don't remember renaming anything besides the clockwork image to recovery.img . Still able to boot into clock after each reboot.
vaust said:
weird, i don't remember renaming anything besides the clockwork image to recovery.img . Still able to boot into clock after each reboot.
Click to expand...
Click to collapse
Cause u probably used ADB to get it to stop reflashing the stock recovery. Using root explorer is the same thing only less technical.
Sent from my Nexus S using XDA App
sarge363 said:
Cause u probably used ADB to get it to stop reflashing the stock recovery. Using root explorer is the same thing only less technical.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
True, I used adb, spent like 2 hour trying to get the pc drivers to recognize the nexus. I used the PDAnet drivers eventually.
vaust said:
weird, i don't remember renaming anything besides the clockwork image to recovery.img . Still able to boot into clock after each reboot.
Click to expand...
Click to collapse
Are you on a custom ROM like CM or Bionix? They remove the script that rewrites stock recovery.
If you're on stock, what version of it are you on? 2.3.1 and higher have a file called /etc/install-recovery.sh on them, and if that's there it should be reflashing stock on every boot, whether you renamed the image you flashed to recovery or not...

help install amon ra

so i have a samsung galaxy s 4g that is rooted with superoneclick. right now i have clockworkmod recovery 3.2.0.0. i like amon ra much better. i had this on my G1.im trying to flash 2.2.1. i cant seem to get it to flash. in terminal emulator it doesnt recognize the command "flash_image" it is "not found". i have adb setup but when i try "adb root" i get a message "adbd cannot run as root in production builds" i cant seem to get into bootloader by holding down buttons or by using "quick boot" i tried rom manager, "flash alternate recovery" is greyed out. please help!
No amon ra or ROM manager for this phone.
Sent from my SGH-T959V using xda premium
jager555 said:
No amon ra or ROM manager for this phone.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Is the 3E stock recovery the only reason?
I don't understand why its not an option....
Was it built for this phone?
Sent from my SGH-T959V using xda premium
A bunch of things you need to know for galaxies vs aosp
1. I also came from a g1. I loved it.
2. AOSP, Sense, Motoblur.etc excluding Touchwiz(These types run on the basic file format. Install rom from a signed zip, start up using a bootloader spl, you must be familiar with hardspl. A boot.img, this is the kernel, and a zip with /system, and other stuff. Also a recovery.img(Amon Ra). And a modem.img
3. Those phones have a posibility for ADB Remount command and fastboot.
eg adb remount, or fastboot flash recovery.img
4. Touchwiz is Galaxy. They run on 2 bootloader binary files, a zImage as a kernel, and mainly the /system partition called factoryfs.rfs is stockly available on a computer flashable tar file which has the files. The tar files usually with files that include factoryfs.rfs, datafs.rfs, cache.rfs, param.lfs, boot.bin, sbl.bin, zImage and modem.bin.
5. Factoryfs = /system zip datafs = /data partition cache = /cache partition, param includes core files like splash image 1 for the g1, and boot and sbl are bootloader, zImage = boot.img with different coding, modem.bin = modem.img
6. zImage contains the recovery.img partition on GB and the /system partion has recovery in froyo roms.
7. Touchwiz has odd mounts, and flashing alternate recoveries has the potential to make your phone an expensive paper weight.
8. There is a feature kind of like boot loader and spl mode for g1(rainbow screen) called download mode. This is where you connect to the computer to flash the big tar files.
9. The smart devs have created a clockworkmod recovery, which has more functions then amon ra and allows you to flash zip files with sgs4g roms.
10. Boot animation cannot be changed unless you have a kernel supporting them. Instead of bootanimation.zip, they use 2 files called bootsamsung.qmg, and bootsamsungloop.qmg
11. DON"T FLASH ANYTHING NOT MADE FOR THIS PHONE, ESPECIALLY BOOTLOADERS AS THEY MAY MAKE YOUR PHONE UNUSABLE, THE REST USUALLY CAN BE RECOVERED.
so is there a way to backup/restore my galaxy s like i could my G1
1. the galaxy s 4g is not a G1
2. yes, you can back it up by going to "backup and restore" in CWM and then clicking "Backup". this will back everything up.
you can restore by choosing the same option in cwm, but "restore" once in the menu.
if you are on a rom that you want to keep, you can go to advanced restore in the backup/restore menu and restore only your data.
gdofwar has a tutorial out on how to backup/restore the phone. does this help?
when i go into ROM Manager and click "backup current rom" it takes me to the screen in the picture. there are no backup options. incase you cant see the pic. the options are:
reboot system now
reinstall packages
delete all user data
delete cache data.
lokeycmos said:
when i go into ROM Manager and click "backup current rom" it takes me to the screen in the picture. there are no backup options. incase you cant see the pic. the options are:
reboot system now
reinstall packages
delete all user data
delete cache data.
Click to expand...
Click to collapse
ROM manager does not work on this phone. You cant use ROM manager. ROM manager does not work.
Sent from my SGH-T959V using xda premium
Exodian said:
ROM manager does not work on this phone. You cant use ROM manager. ROM manager does not work.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
so what can i do?
Omfg
Sent from my SGH-T959V using xda premium
Dev section krylon 360 cwm final thread. Read it follow it.
Sent from my SGH-T959V using xda premium
Bali on Froyo. drhonk's GB kernels.
Sent from my SGH-T959V using xda premium
Cool THank you for the thread! i have the update.zip on my sd card. when i try to push the other file it says "failed to copy 'recovery' to '/system/bin/recovery': Read-only file system" how do i work through this? thank you much!
jager555 said:
Omfg
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
You read my mind with that post. LOL
htaak said:
You read my mind with that post. LOL
Click to expand...
Click to collapse
Im looking for help not criticism. im obvisously not on your level.
ok. look for the bali 3.3uv threads. odin this file using the instructions in the thread. this will give you the proper cwm and root.
lokeycmos said:
Im looking for help not criticism. im obvisously not on your level.
Click to expand...
Click to collapse
I hope you are above my level LOL.
It wasn't meant as criticism, Jager just happened to post exactly what I was thinking at the moment I was thinking it as I read through the thread, and it made me laugh. It was like a mini version of Monty Python's Dead Parrot Sketch.
I sincerely apologize if it came over that way. I am not here to argue with or upset anyone.
lokeycmos said:
Cool THank you for the thread! i have the update.zip on my sd card. when i try to push the other file it says "failed to copy 'recovery' to '/system/bin/recovery': Read-only file system" how do i work through this? thank you much!
Click to expand...
Click to collapse
Flash, not push. Unless you're rooted, the file system is set to read-only. If you are rooted, download root explorer or any other file system explorer, set to R/W, and push again.
To flash, boot to recovery and select the update.zip option (don't remember exact wording).
Sent from my SGH-T959V using xda premium
neocorteqz said:
Flash, not push. Unless you're rooted, the file system is set to read-only. If you are rooted, download root explorer or any other file system explorer, set to R/W, and push again.
To flash, boot to recovery and select the update.zip option (don't remember exact wording).
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
if you do it this way for the love of god dont forget to remont the system as r/o after you copy the recovery file to the system bin folder ....

[Q] how do you get boot image to flash it??

hi guys i know this is a stupid question and i can follow directions pretty well, but how or where do you get the boot image from to flash it.. i am trying to install jellybam and im getting that looping screen im pretty sure that i know i have to flash the boot image but i dont know how nor where to get it from
Its in the actual ROM zip. Download it to your desktop and double click the zip, you will see it there.
Also, I use the all in one tool to flash my boot.IMG and it works fine and its much less complicated. Go download the tool, then place the bootimg in the kernel folder of the all in one tool, then run the tool and select flash kernel option. Obv make sure your phone is connected to your laptop and USB debugging is enabled on your phone.
Hope that helps.
Sent from my One X using xda app-developers app
boot image
dalvarez0312 said:
Its in the actual ROM zip. Download it to your desktop and double click the zip, you will see it there.
Also, I use the all in one tool to flash my boot.IMG and it works fine and its much less complicated. Go download the tool, then place the bootimg in the kernel folder of the all in one tool, then run the tool and select flash kernel option. Obv make sure your phone is connected to your laptop and USB debugging is enabled on your phone.
Hope that helps.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
thank you but i still dont see the boot image is it in one of the folders?
It should in the parent directory (not in a folder). Be sure that your computer and/or unzip program is not setup to hide unknown file extensions or anything like that.
Use flashimagegui before you install the Rom
Sent from my HTC One XL using xda app-developers app

Image not found (jb).img

I have followed everything to a 't' and took the jb image 'renamed it' to (basically took out jb and kept 'recovery' and '.img') IS THAT CORRECT?
and when I ran the command for the image recovery it says image not found.
I even tried TWRP image and renamed... Same problem-
I know I posted some stupid stuff and I apologize - i have read a lot more into rooting and figured a lot out, but this is am @ a loss... Not sure what else to...
I plead for help
ganggreen777 said:
I have followed everything to a 't' and took the jb image 'renamed it' to (basically took out jb and kept 'recovery' and '.img') IS THAT CORRECT?
and when I ran the command for the image recovery it says image not found.
I even tried TWRP image and renamed... Same problem-
I know I posted some stupid stuff and I apologize - i have read a lot more into rooting and figured a lot out, but this is am @ a loss... Not sure what else to...
I plead for help
Click to expand...
Click to collapse
the image file needs to be in the same place that you are running fastboot from. for example i have C:/andriod abd where all my adb/fastboot drivers and .exe and such are and to flash a blob/img file i must put the file in that same folder because thats where fastboot looks for the blob/img.
ide bet money that this is your problem. and what fastboot command are you using? It would be helpful if you could be more descriptive of the steps you have tried
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
markymark567 said:
the image file needs to be in the same place that you are running fastboot from. for example i have C:/andriod abd where all my adb/fastboot drivers and .exe and such are and to flash a blob/img file i must put the file in that same folder because thats where fastboot looks for the blob/img.
ide bet money that this is your problem. and what fastboot command are you using? It would be helpful if you could be more descriptive of the steps you have tried
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
BTW-THANKYOU soo much for hekping
I will put more information up and pics to help-people see what I see and are doing
I actually made a file folder (I saw it on a YouTube video) and put all of the files needed for the recovery;for example
"rocovery1"=file folder (in c drive) and that folder includes the two(2) adb(.dll) files / the fastboot file (but my 'fastboot' file doesn't have an exe after it) does that matter-/and then of course the image file... ALL OF THAT IS IN A folder I named... should I have not done that? If not where would I find my adb files? Better yet how are they supposed to be listed?
Sent from my Galaxy Nexus using Tapatalk 2
ganggreen777 said:
BTW-THANKYOU soo much for hekping
I will put more information up and pics to help-people see what I see and are doing
I actually made a file folder (I saw it on a YouTube video) and put all of the files needed for the recovery;for example
"rocovery1"=file folder (in c drive) and that folder includes the two(2) adb(.dll) files / the fastboot file (but my 'fastboot' file doesn't have an exe after it) does that matter-/and then of course the image file... ALL OF THAT IS IN A folder I named... should I have not done that? If not where would I find my adb files? Better yet how are they supposed to be listed?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
FYI
Asus uses .blob NOT .img
Even if it's CWM or TWRP (either one would be '.blob') NOT '.img' - either one?
Sent from my Galaxy Nexus using Tapatalk 2
ganggreen777 said:
Even if it's CWM or TWRP (either one would be '.blob') NOT '.img' - either one?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Recovery is through fastboot, and fastboot for asus requires .blob. So yes, its blob irregardless.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
I AM ROOTED!
Sent from my Galaxy Nexus using Tapatalk 2

Categories

Resources