Auto zip installer? - Samsung Epic 4G Touch

Is there a file manager that when selecting, say a .zip file, will automatically boot you into recovery, auto install &/or update & then boot you back into your phone?
I mean not that manually booting into recovery, searching & selecting your file, let it do its thing & then selecting the option to reboot system, is all that hard, I'm just trying to find a process that simplifies all that.
***Update: Okay I installed ROM Manager and when selecting one of my zip files in ES Explorer, I was able to select the file and do as needed. So I guess that answers my question. Unless someone has an another alternative that doesn't require ROM Manager***

I personally wouldn't use rom manager. It has been known to cause bricks with this phone. Especially the fake flash of the touch recovery. It doesn't play well with this phone because if our recovery being baked into the kernels.
sent from my BAD A$$ Epic touch

patrao_n said:
I personally wouldn't use rom manager. It has been known to cause bricks with this phone. Especially the fake flash of the touch recovery. It doesn't play well with this phone because if our recovery being baked into the kernels.
Click to expand...
Click to collapse
Thanks, I did notice that when attempting to install a zipped app via the ES File Explorer/Rom Manager method it did boot into recovery & did in fact say installing, but as soon as the phone rebooted I could not locate the supposed installed app. I had to do it again, which defeats the purpose of being an "faster/easier" method.

Related

ClockwordMod, ROM Manager and Recovery

So i'm having a few issues with ClockwordMod and/or ROM Manager
from within ROM Manager when I hit flash clockworkmod it'll download and give me confirmation of success, but I can't seem to launch it - is it supposed to automatically launch after I enter recovery mode? Was it supposed to change any menu entries after I hit volume up+power?
I ended up downloading clockwordmod as update.zip and running it from sdcard:update.zip
Additionally, Reboot into Recovery from ROM manager doesn't do anything. It asks if i'm sure, I say yes, then nothing happens. QuickBoot however has no problems rebooting straight into the recovery menu though, and I can also do it from ADB. Am I missing something obvious?
sparksalot said:
So i'm having a few issues with ClockwordMod and/or ROM Manager
from within ROM Manager when I hit flash clockworkmod it'll download and give me confirmation of success, but I can't seem to launch it - is it supposed to automatically launch after I enter recovery mode? Was it supposed to change any menu entries after I hit volume up+power?
I ended up downloading clockwordmod as update.zip and running it from sdcard:update.zip
Additionally, Reboot into Recovery from ROM manager doesn't do anything. It asks if i'm sure, I say yes, then nothing happens. QuickBoot however has no problems rebooting straight into the recovery menu though, and I can also do it from ADB. Am I missing something obvious?
Click to expand...
Click to collapse
Flashing clockworkmod as an update.zip will do no changes to your current recovery.
If you want to replace your current phone's recovery with clockworkmod simply search for unrevoked on these forums.
I have the same problem, it is a bug with ROM manager, you have to give the app superuser permissions before clicking any of the options, so if you were to do this then on your first install of the app click on flash recovery (even if you have it), it will ask for superuser permissions, grant them it and the app will then work fine.
ahh it'd be good if it told you that
next I went into it and went to install superuser but of course you need to have superuser to do that :|
But i'm there now, thanks for your help

[MOD] JMG recovery with sig check disabled.

Someone PM'ed me about this and I finely got around to doing it. I do not have
a Galaxy Tab and when I try to test it on my Vibrant I cannot navigate the menu
buttons are not mapped correctly.
I am fairly certain that it will work, just cant test to make sure. If it turns out
that it works anyone is welcome to use it and can even use my install script
which can be found here.
http://forum.xda-developers.com/showthread.php?t=833423
if it does work you will not have to flash a modified kernel to use Clockwork.
just rename JMG_recovery to recovery and replace bin/recovery in the script
directory.
The attached file is not flashable!!!
it contains a modified JMG recovery an IDA disassembler database
file and a text file with the patch offsets and the patch data. and
is intended for testing and development purposes only.
Thank you!
Well, I tried that, or let me first explain to you what I tried.
I copied the supplied 'recovery' file, replacing the existing /system/bin/recovery .
Then I flashed RomManager's recovery. As this JMG is a EURO-based rom, and Rommanager does not support EURO ROM option for ClockWorkMod, I choosed Tmobile (which my tab is). Maybe this was the mistake.....???
Then I rebooted into recovery and it still shows Samsung Recovery 3e.
I was not sure what to do with the code you supplied and the installation process you offered - but the description was clear to only replace the recovery file, and that is what I did.
Did I miss something?
Thanks for your help anyway - let me know and I can test for you, anytime.
Hope I am not making a total fool of myself. I realized that you did not say anything about ClockWorkMod, but all the other recovery-image-replacements offer access to CWM so I assume this would to. I guess I was wrong.
bert269 said:
Well, I tried that, or let me first explain to you what I tried.
I copied the supplied 'recovery' file, replacing the existing /system/bin/recovery .
Then I flashed RomManager's recovery. As this JMG is a EURO-based rom, and Rommanager does not support EURO ROM option for ClockWorkMod, I choosed Tmobile (which my tab is). Maybe this was the mistake.....???
Then I rebooted into recovery and it still shows Samsung Recovery 3e.
I was not sure what to do with the code you supplied and the installation process you offered - but the description was clear to only replace the recovery file, and that is what I did.
Did I miss something?
Thanks for your help anyway - let me know and I can test for you, anytime.
Hope I am not making a total fool of myself. I realized that you did not say anything about ClockWorkMod, but all the other recovery-image-replacements offer access to CWM so I assume this would to. I guess I was wrong.
Click to expand...
Click to collapse
once you are in the Samsung's recovery select reinstall packages if clockwork
works like on the Vibrant then the device will appear to reboot back into the
Samsung recovery if you get this far then the posted file works, if you select
reinstall packages again then clockwork should launch assuming you have
busybox installed and every thing else works like it does on the Vibrant.
untermensch said:
once you are in the Samsung's recovery select reinstall packages if clockwork
works like on the Vibrant then the device will appear to reboot back into the
Samsung recovery if you get this far then the posted file works, if you select
reinstall packages again then clockwork should launch assuming you have
busybox installed and every thing else works like it does on the Vibrant.
Click to expand...
Click to collapse
When i select 'reinstall packages' nothing happens, it does not reboot back into Samsung recovery.
Where will Clockwork recovery come from, from the recovery file that I copied into /system/bin ?
It does not seem to work for me
untermensch said:
once you are in the Samsung's recovery select reinstall packages if clockwork
works like on the Vibrant then the device will appear to reboot back into the
Samsung recovery if you get this far then the posted file works, if you select
reinstall packages again then clockwork should launch assuming you have
busybox installed and every thing else works like it does on the Vibrant.
Click to expand...
Click to collapse
When i select 'reinstall packages' nothing happens, it does not reboot back into Samsung recovery.
Where will Clockwork recovery come from, from the recovery file that I copied into /system/bin ?
Thank you for sharing.
I guess it works.
I was not unable to flash GT-P1000-CSC-MULTI-OXXJK2 ## before, it would say "signature check failed".
I replaced the recovery in the bin folder and ran the script.
Now i am able to use above CSC file.
a1jatt said:
Thank you for sharing.
I guess it works.
I was not unable to flash GT-P1000-CSC-MULTI-OXXJK2 ## before, it would say "signature check failed".
I replaced the recovery in the bin folder and ran the script.
Now i am able to use above CSC file.
Click to expand...
Click to collapse
Thank You!
The code for the signature check is the same for all the Samsung devices I have
looked at, just the offsets are different. So once I find it I can do the mod in my
sleep.
I also just did an md5 check on the JMG and JME recovery and they are the same
so I bet this will work on most of the firmware versions out there.
bert269 said:
When i select 'reinstall packages' nothing happens, it does not reboot back into Samsung recovery.
Where will Clockwork recovery come from, from the recovery file that I copied into /system/bin ?
Click to expand...
Click to collapse
the recovery I asked to be tested is the Samsung recovery, when you select
reinstall packages Samsung's recovery looks for a file on the SD card called
update.zip. When/if that file is found recovery then loads a public key file from
/res/keys which is in the kernel ram file system, this is why you need to flash a
modified kernel to use Clockwork because someone has to change the key to
the same one used to sign Clockwork. once the public key is loaded Samsung's
recovery check's the signature of update.zip. if the private key used to sign the
package does not match the public key loaded from /res/keys you get the
"signature check failed" message.
Clockwork recovery is the update.zip on the SD card.
the modification I made to Samsung's recovery disables signature checking and
will allow you to install unsigned packages.
i need this file cause everytime installing CSC always failed verification signature failed
but i don't understand how to use this file
can you give me explain tut details?
i don't have recovery clockwerk
my system recovery (3e)
Very nice ! Thanks for sharing the hex-edit offsets !
Extra instructions:
http://forum.xda-developers.com/showthread.php?p=11289885#post11289885
still problem with signature
root, copy/overwrite "recovery" /system/bin
then run script
then installing CSC
but still failed
what wrong?
very2 tired work with this
I'm actually using this patched 3e recovery in my custom initramfs now
(At this stage, I'm not interested in ClockWorkMod 3.0 recovery for my self-built kernel...I tried it a few times, but didn't find it useful)
3e bricked my tab lastnight, had to return it to tmo and play it off as a battery defect.
i only tried because clockworkmod gets me stuck at the last adb command step

[Q] Problem upgrading ClockworkMod.

I dowloaded ROM Manager from the market and used the Flash ClockworkMod Recovery option to upgrade to the latest verion of CWM.
From the ROM Manager application it says the current verion is 3.0.0.8 but when I reboot into recovery the phone still says v2.5.1.2. Am I doing something wrong?
Thanks
EKhatch1 said:
I dowloaded ROM Manager from the market and used the Flash ClockworkMod Recovery option to upgrade to the latest verion of CWM.
From the ROM Manager application it says the current verion is 3.0.0.8 but when I reboot into recovery the phone still says v2.5.1.2. Am I doing something wrong?
Thanks
Click to expand...
Click to collapse
in ROM manager hit Menu >> Settings and check the box for Erase Recovery. This will erase your current recovery before flashing the new one to give you a clean flash.
Then just hit Flash ClockworkMod Recovery. It should attempt to flash it again.
Okay I did that and it didn't work so I cleared the download cache from the menu setting and tried again. It appeard to work but when I reboot into recovery my phone still says it is on v.2.5.1.2
Maybe this is a sign I should just leave my phone alone for a while. lol
Just manually flash it. ROM Manager was doing that to me too. I hate using ROM Manager... lol. I flash stuff manually myself because then I know is going on.
http://dougpiston.com/?page_id=85
For AMOLED: use 3.0.0.7 (some have reported problems with 3.0.0.8 on AMOLED).
For SLCD: use 3.0.0.8
Rename the zip you download to "PB31IMG" (without quotes) and put it on the root of your SD card. Boot to HBoot and flash the update when prompted (by pressing Vol Up).
Don't forget to delete the zip after it successfully updates. To add onto CarngeX, the zip should be named: PB31IMG.zip
Okay thanks. I had never even tried ROM Manager for anything else. I always load ROM's manually but I thought it would be way more complicated to update than you showed me. It's all good now. Thanks again.
SlimSnoopOS said:
Don't forget to delete the zip after it successfully updates. To add onto CarngeX, the zip should be named: PB31IMG.zip
Click to expand...
Click to collapse
Reason I just said "name it to PB31IMG" is because a lot of times people have file extensions hidden, and they end up naming it to "PB31IMG.zip.zip" and it causes more problems lol.
EKhatch1 said:
Okay thanks. I had never even tried ROM Manager for anything else. I always load ROM's manually but I thought it would be way more complicated to update than you showed me. It's all good now. Thanks again.
Click to expand...
Click to collapse
Glad you got it running.
carngeX said:
Just manually flash it. ROM Manager was doing that to me too. I hate using ROM Manager... lol. I flash stuff manually myself because then I know is going on.
For AMOLED: use 3.0.0.7 (some have reported problems with 3.0.0.8 on AMOLED).
For SLCD: use 3.0.0.8
Rename the zip you download to "PB31IMG" (without quotes) and put it on the root of your SD card. Boot to HBoot and flash the update when prompted (by pressing Vol Up).
Click to expand...
Click to collapse
I'm just curious, I've updated my cwm to 3.0.0.7 already through rom manager, but I had previous tried doing it like this through recovery using a .zip. When it prompts for the update, is it just passive? Like you enter hboot and then wait until it asks if you want to upgrade?
soft pillowcase said:
I'm just curious, I've updated my cwm to 3.0.0.7 already through rom manager, but I had previous tried doing it like this through recovery using a .zip. When it prompts for the update, is it just passive? Like you enter hboot and then wait until it asks if you want to upgrade?
Click to expand...
Click to collapse
When you boot to HBoot, it should check for a PB31IMG.zip file on your card. If it finds one, it'll ask if you would like to update or not.
carngeX said:
When you boot to HBoot, it should check for a PB31IMG.zip file on your card. If it finds one, it'll ask if you would like to update or not.
Click to expand...
Click to collapse
I guess I didn't package it right since I would see it scan for it (quickly, so I couldn't see what it was saying exactly), but it didn't offer me any option to update afterwards. Thanks.
Then it's probably not named correctly (needs to be exactly PB31IMG.zip, check for hidden extensions), or your SD card isn't formatted to fat32.
k_nivesout said:
Then it's probably not named correctly (needs to be exactly PB31IMG.zip, check for hidden extensions), or your SD card isn't formatted to fat32.
Click to expand...
Click to collapse
Thanks, I think it's the formatting issue; I'll try again soon.

[Q] Repair platform.xml?

Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Any suggestions on how I can get access back to my device so I can repair/replace the platform.xml file and restore functionality to my phone?
Thank you very much!
Deozaan said:
Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Click to expand...
Click to collapse
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery
enryea123 said:
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery
Click to expand...
Click to collapse
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).
Deozaan said:
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).
Click to expand...
Click to collapse
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.
enryea123 said:
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.
Click to expand...
Click to collapse
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.
Deozaan said:
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.
Click to expand...
Click to collapse
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
having a backup of the sdcard is always a good idea :good:, i have 2 backups of mysdcard on 2 different hard drives of my computer and the pictures i take with the camera are automatically uploaded on my dropbox .
enryea123 said:
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
Click to expand...
Click to collapse
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.
Deozaan said:
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.
Click to expand...
Click to collapse
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip
enryea123 said:
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip
Click to expand...
Click to collapse
I was in CWM Recovery. I was using the zip file that I extracted from the link you gave me for Google's stock ROMs (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!
enryea123 said:
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip
Click to expand...
Click to collapse
Try this one
Deozaan said:
I was in CWM Recovery. I was using the zip file that I extracted from here the link you gave me (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!
Click to expand...
Click to collapse
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.
enryea123 said:
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.
Click to expand...
Click to collapse
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.
I got it working again. The ROM you gave me failed signature verification in CWM Recovery, but I told it to install anyway and it worked. Thank you.
The problem I was having with Gmail not syncing was that I used Titanium Backup to restore my data, but because all the data from my "SD card" got erased, Titanium Backup itself lots its settings, so my Device ID was different. I guess Gmail relies on the device ID for syncing.
Thank you so much for your help! I learned a lot from the experience.
Glad i helped you. well this is one of the reasons why i don't restore data with titanium (especially system data).
and by the way:
Deozaan said:
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.
Click to expand...
Click to collapse
To fully reset and install a clean rom using fastboot you have to extract the bootloader-blabla.img and radio-blabla.img files from the tar.gz archive and then extract the 4 .img files inside the zip (that is inside the tar.gz) and flash this 6 .img files connetting your phone in bootloader mode to your computer and using fastboot in terminal (in fact this procedure reinstall the recovery too).

[Q] cant install root file from internal storage?

Hey guys im trying to root my device so i can install some lightweight custom roms. Ive been following this guide i found online
http://androidcritics.com/how-to-root-and-install-clockworkmod-recovery-on-galaxy-s3-i747/
I basically did this
Installing Clockwork Recovery Mod
Find the recovery image file which is clockworkmod.tar
On your Samsung Galaxy S3 I747, press and hold down the volume down, power, and home buttons
Once your at the warning screen, press volume up to accept
Launch the Odin program from your computer
In Odin, find the PDA tab and click it
Find the clockworkmod.tar.md5 file in the unzipped recovery image file
Press start to begin flashing the recovery mod
BE PATIENT! and wait until your device reboots
Once your device has fully rebooted, you can start installing root
It loaded on the phone fine. I then did this
Installing Root
Transfer the root.zip file onto your phone from your computer
Make sure you connect your s3 to your computer and find the root zip file and put it in your downloads folder.
Enter clockwork recover mod by holding down the volume up, power, and home buttons
Navigate by using the volume buttons to Install Zip > Choose Zip from Internal SD card > Navigate to the downloads folder> Select
Be Patient! and wait until your device is finished
Once the process is finished, you can select Reboot
Once your device has rebooted, launch the Google Play Store app
Search “SuperuserSU” and select the first app that shows in the search results
Install this app
Once it has finished installing, your done!
The only problem is I cant navigate to the option "install zip from internal sd card" I simply dont have though's options here is what I have when hold volume up reset and home
"reboot system now
apply update from ADB
apply update from external storage (which i dont have)
wipe data/factory reset
wipe cache partition
apply update from cache
When i hit apply update from ADB it says "now send the package you want to apply to the device with "adb sideload <filename>"...
Im wondering if the original flash didnt go thru? Why dont I have the options that I should?
Any help would mean the world trying to get this puppy up asap!
regards,
Eddy
eddyg519 said:
Hey guys im trying to root my device so i can install some lightweight custom roms. Ive been following this guide i found online
http://androidcritics.com/how-to-root-and-install-clockworkmod-recovery-on-galaxy-s3-i747/
I basically did this
Installing Clockwork Recovery Mod
Find the recovery image file which is clockworkmod.tar
On your Samsung Galaxy S3 I747, press and hold down the volume down, power, and home buttons
Once your at the warning screen, press volume up to accept
Launch the Odin program from your computer
In Odin, find the PDA tab and click it
Find the clockworkmod.tar.md5 file in the unzipped recovery image file
Press start to begin flashing the recovery mod
BE PATIENT! and wait until your device reboots
Once your device has fully rebooted, you can start installing root
It loaded on the phone fine. I then did this
Installing Root
Transfer the root.zip file onto your phone from your computer
Make sure you connect your s3 to your computer and find the root zip file and put it in your downloads folder.
Enter clockwork recover mod by holding down the volume up, power, and home buttons
Navigate by using the volume buttons to Install Zip > Choose Zip from Internal SD card > Navigate to the downloads folder> Select
Be Patient! and wait until your device is finished
Once the process is finished, you can select Reboot
Once your device has rebooted, launch the Google Play Store app
Search “SuperuserSU” and select the first app that shows in the search results
Install this app
Once it has finished installing, your done!
The only problem is I cant navigate to the option "install zip from internal sd card" I simply dont have though's options here is what I have when hold volume up reset and home
"reboot system now
apply update from ADB
apply update from external storage (which i dont have)
wipe data/factory reset
wipe cache partition
apply update from cache
When i hit apply update from ADB it says "now send the package you want to apply to the device with "adb sideload <filename>"...
Im wondering if the original flash didnt go thru? Why dont I have the options that I should?
Any help would mean the world trying to get this puppy up asap!
regards,
Eddy
Click to expand...
Click to collapse
Sounds like the root method you are using is just way to complicated. Follow this one here http://forum.xda-developers.com/showthread.php?t=1739426 it has prerooted firmwares that you just install with odin and you are done (cwm included). Just make sure you grab the right firmware for your carrier.
If I have helped you out, slap that thanks button.
aeppacher said:
Sounds like the root method you are using is just way to complicated. Follow this one here http://forum.xda-developers.com/showthread.php?t=1739426 it has prerooted firmwares that you just install with odin and you are done (cwm included). Just make sure you grab the right firmware for your carrier.
If I have helped you out, slap that thanks button.
Click to expand...
Click to collapse
Beauty I think its flashing the rogers rom to my phone from there Im good to load other roms using this odin tool? (or is it rom manager?)
also what is this clockwork mod ? I might as well go into play store and get both rom manager and clockwork?
- eddy
So After I flashed the new rom to my phone i left it plugged in and it restarted. Android loader popped on and now it says android is upgrading... starting apps. Its been like this for over a half an hour... what do i do??? helpppp dont really want to reset it but it is bricked? or do i have to reload ?
update:
held the restart button down it restarted bit is still stuck on starting apps.
update two:
held vol down home and reset tried to reload the rogers rom onto the phone and now it stops at samsung load screen. Do i have to reload the carrier that came with the phone? I cant quite remember what the original carrier was.
UPDATE THREE:
I as able to boot back into the phone but...nothing changed? i ended up wiping the phones data in settings because its too full as it is. I downloaded root checker and it said access was denied ? That makes its not rooted after all... I followed the directions seems that they didnt take? Any clues?
eddy
eddyg519 said:
So After I flashed the new rom to my phone i left it plugged in and it restarted. Android loader popped on and now it says android is upgrading... starting apps. Its been like this for over a half an hour... what do i do??? helpppp dont really want to reset it but it is bricked? or do i have to reload ?
update:
held the restart button down it restarted bit is still stuck on starting apps.
update two:
held vol down home and reset tried to reload the rogers rom onto the phone and now it stops at samsung load screen. Do i have to reload the carrier that came with the phone? I cant quite remember what the original carrier was.
UPDATE THREE:
I as able to boot back into the phone but...nothing changed? i ended up wiping the phones data in settings because its too full as it is. I downloaded root checker and it said access was denied ? That makes its not rooted after all... I followed the directions seems that they didnt take? Any clues?
eddy
Click to expand...
Click to collapse
Okay buddy looks like you need to learn some basic android 101
You are definitely not ready to root or do anything til you learn this stuff...
Okay, so first is recoveries. Basically recoveries are a bit of software that let's you flash ROMs, kernels, and whatever else to your phone. When you hold volume up and power when your phone is off, you boot to recovery. Now basically recoveries are necessary because when you are flashing a new ROM it essentially deletes the android system from your phone first so this is a way of your phone still working between flashes.
Clockworkmod is a custom recovery with a lot of features meant for flashing ROMs. There are competitors such as TWRP (team win recovery project) but clockworkmod is a great starter. Use videos or tutorials on how to use it before you flash your first ROM. I can not stress how often you need to read read and read some more.
Okay so rooting your phone. Basically there is a "root" directory of your phone. Its where all the system files are stored and it let's you do a lot of stuff, but it also means you can screw a lot of stuff up to (like really screw it up). On default you are locked out of here by the maker of your phone for various reasons. Rooting means that someone found an exploit to gain access to this folder. Usually what you then do is you find a way to inject superuser (a little app that gives root access to other apps later on). You use Odin in this case to install a stock Samsung rom (with superuser already put in the root directory of that modified ROM its installing) essentially this means you have root. Root allows you to install recoveries like clockworkmod (which you need to flash ROMs later.
Okay so that was my quick run through. At your point you need to go to YouTube and Google how to root the sgs3 and hopefully they should have one for your specific carrier. The process should be the same minus the files you flash. Essentially you should be looking for stock ROM (for your specific device) with superuser or supersu already installed. Then you should be finding a way to install clockworkmod once you have root. (You may be able to find a file or tutorial that does this in one go). I cannot emphasise enough about reading. You wouldn't be here had you read first and in the flashing business, if you don't want a sgs3 paper weight you should read first.
Oh and ROMmanager from the marketplace installs clockworkmod for you (ONCE YOU HAVE ROOT) its simple. Just download it from the play story. Click flash recovery. It will load a bit and your done. Then you can reboot into it. ROM manager (the paid version is unnecessary) it just adds extra features you don't yet need. Look at it once you have flashed your first few ROMs.
Best of luck. Let me know and slap that thanks button. I wrote this on my phone.
READ READ READ
eddyg519 said:
Hey guys im trying to root my device so i can install some lightweight custom roms. Ive been following this guide i found online
http://androidcritics.com/how-to-root-and-install-clockworkmod-recovery-on-galaxy-s3-i747/
I basically did this
Installing Clockwork Recovery Mod
Find the recovery image file which is clockworkmod.tar
On your Samsung Galaxy S3 I747, press and hold down the volume down, power, and home buttons
Once your at the warning screen, press volume up to accept
Launch the Odin program from your computer
In Odin, find the PDA tab and click it
Find the clockworkmod.tar.md5 file in the unzipped recovery image file
Press start to begin flashing the recovery mod
BE PATIENT! and wait until your device reboots
Once your device has fully rebooted, you can start installing root
It loaded on the phone fine. I then did this
Installing Root
Transfer the root.zip file onto your phone from your computer
Make sure you connect your s3 to your computer and find the root zip file and put it in your downloads folder.
Enter clockwork recover mod by holding down the volume up, power, and home buttons
Navigate by using the volume buttons to Install Zip > Choose Zip from Internal SD card > Navigate to the downloads folder> Select
Be Patient! and wait until your device is finished
Once the process is finished, you can select Reboot
Once your device has rebooted, launch the Google Play Store app
Search “SuperuserSU” and select the first app that shows in the search results
Install this app
Once it has finished installing, your done!
The only problem is I cant navigate to the option "install zip from internal sd card" I simply dont have though's options here is what I have when hold volume up reset and home
"reboot system now
apply update from ADB
apply update from external storage (which i dont have)
wipe data/factory reset
wipe cache partition
apply update from cache
When i hit apply update from ADB it says "now send the package you want to apply to the device with "adb sideload <filename>"...
Im wondering if the original flash didnt go thru? Why dont I have the options that I should?
Any help would mean the world trying to get this puppy up asap!
regards,
Eddy
Click to expand...
Click to collapse
Hi eddy,
It sounds like you didn't get CWM to stick after your flash with ODIN. You need to uncheck the reboot option in odin and then after the flash is done pull the battery and go directly into CWM loader by booting with the volume up + power + home button method. This will give you cwm rather than the stock loader you seem to be trying to use. You're almost there!
sxorpyon said:
Hi eddy,
It sounds like you didn't get CWM to stick after your flash with ODIN. You need to uncheck the reboot option in odin and then after the flash is done pull the battery and go directly into CWM loader by booting with the volume up + power + home button method. This will give you cwm rather than the stock loader you seem to be trying to use. You're almost there!
Click to expand...
Click to collapse
He also said root wasn't sticking. He needs that before he can cwm to stick
aeppacher said:
He also said root wasn't sticking. He needs that before he can cwm to stick
Click to expand...
Click to collapse
I think he can't install the superuser.zip from cwm after boot because he's allowing the stock rom to overwrite his cwm flash ... he's gotta pull his battery after the odin flash to get root in. That's what worked for me. once he's got root he can use rom manager to upgrade to cwm 6.x
sxorpyon said:
I think he can't install the superuser.zip from cwm after boot because he's allowing the stock rom to overwrite his cwm flash ... he's gotta pull his battery after the odin flash to get root in. That's what worked for me. once he's got root he can use rom manager to upgrade to cwm 6.x
Click to expand...
Click to collapse
He shouldn't need cwm to install. If flashes a firmware with root already injected he can then just use rom manager to install clockworkmod for the first time since rom manager just needs root which he will have. You can root and keep the stock recovery on at the same time
I think his biggest issue is root not sticking. Til he does that cwm wont install

Categories

Resources