Related
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
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...
OK, so after fighting with my Nexus S 4G for three hours trying to get it rooted (it took 15 - 30 minutes for my Hero and Evo Shift) I finally established root and wanted to install ClockworkMod. Of course I've come to learn that it's just not that simple, and I have to rename the default recovery, which require r/w permissions, and just more hoops to jump through.
Long story short, I rooted, set r/w access and renamed install-recovery.sh and used ROM Manager to install ClockworkMod. Reboot to recovery, and all seems well. Except that the next time I reboot, I'm back to the default recovery, my renamed install-recovery.sh.old is no where to be found and low and behold, install-recovery.sh is back.
Considering how easy this was with HTC devices... I'm starting to get a little pissed off.
Anyone have any idea why I can't maintain ClockworkMod?
Why don't you just use fastboot and flash the recovery image? It will be permanent if you do that... It takes about ten seconds.
Download the clockwork mod recovery and rename it to recovery.img then reboot your phone into the bootloader (hold volume up while you power on your phone). With the Android sdk installed and in your path, type fastboot flash recovery recovery.img and enjoy. If you want more specific help, you can pm me. I'll need to know what type of computer you have, Windows, Mac, or Linux in that case.
Sent from my Nexus S 4G using XDA Premium App
If you're sure you did the renaming properly and after that the file got restored back, I'd suggest you trying to trick the system by making a backup of the original install-recovery.sh and then instead of renaming it, just delete everything in that file so you still have the file named install-recovery.sh which will do noting to the recovery partition
radadev said:
Download the clockwork mod recovery and rename it to recovery.img then reboot your phone into the bootloader (hold volume up while you power on your phone). With the Android sdk installed and in your path, type fastboot flash recovery recovery.img and enjoy. If you want more specific help, you can pm me. I'll need to know what type of computer you have, Windows, Mac, or Linux in that case.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
OK... tried this. No go.
Reboot still shows the default and not clockwork.
The file I renamed on my i9020a to prevent stock recovery from being reinstalled was in the folder \etc and was called install-recovery.bak
Cheers
So you're saying that your NS is rooted but when you boot into recovery, default recovery replaces CWM right?
1) Download 'Root Explorer' and 'ROM Manager' from the Market (Skip this step if you already have done so)
2) Reboot
3) Open 'Root Explorer' and open 'etc' directory
4) On the top right hand corner, click the 'Mount R/W' button
5) On the same directory, find 'install-recovery.sh' and rename this file to a different name (e.g. install-recovery.sh.old)
6) Open 'ROM Manager' and click 'Flash ClockworkMod Recovery.'
7) Reboot
jungbum said:
So you're saying that your NS is rooted but when you boot into recovery, default recovery replaces CWM right?
1) Download 'Root Explorer' and 'ROM Manager' from the Market (Skip this step if you already have done so)
2) Reboot
3) Open 'Root Explorer' and open 'etc' directory
4) On the top right hand corner, click the 'Mount R/W' button
5) On the same directory, find 'install-recovery.sh' and rename this file to a different name (e.g. install-recovery.sh.old)
6) Open 'ROM Manager' and click 'Flash ClockworkMod Recovery.'
7) Reboot
Click to expand...
Click to collapse
This is the first thing I tried. No dice.
Sophos1 said:
The file I renamed on my i9020a to prevent stock recovery from being reinstalled was in the folder \etc and was called install-recovery.bak
Cheers
Click to expand...
Click to collapse
I don't see an "install-recovery.bak"
Stupid question, is your bootloader still unlocked?
wild1z said:
Stupid question, is your bootloader still unlocked?
Click to expand...
Click to collapse
Yep. Still unlocked. Super-user and root programs appear to work fine. Can pull apks and push them back. I really don't know why this isn't working for me. Just thought maybe I wasn't alone.
Shadodragon said:
Yep. Still unlocked. Super-user and root programs appear to work fine. Can pull apks and push them back. I really don't know why this isn't working for me. Just thought maybe I wasn't alone.
Click to expand...
Click to collapse
Have you tried to lock it back up and return to stock? I suspect you are using the latest clockwork mod too right? I feel your pain. My Hero was a PITA to root and it had all kinds of wanky problems one day and the next.. Blue skys.
wild1z said:
Have you tried to lock it back up and return to stock? I suspect you are using the latest clockwork mod too right? I feel your pain. My Hero was a PITA to root and it had all kinds of wanky problems one day and the next.. Blue skys.
Click to expand...
Click to collapse
See, the Hero was easy for me. The Nexus seems 10 times harder to do things to.
I have noticed this, I have an:
etc\install-recovery.sh
and
system\etc\install-recovery.sh
Do I need to rename both?
Shadodragon said:
See, the Hero was easy for me. The Nexus seems 10 times harder to do things to.
I have noticed this, I have an:
etc\install-recovery.sh
and
system\etc\install-recovery.sh
Do I need to rename both?
Click to expand...
Click to collapse
I can only tell you what I would do. I would try to get it back to stock and lock it up to start over.
Maybe JasonMahoney, AOSP and Lilduce will come on over and share this fun with us.
hello all,
first of all THANK YOU very much for this ROM - really appreciate it!!!
second of all:
I currently have a stock rom on my device - rooted.
As I understand I need to replace the stock recovery with that of krylon360(http://forum.xda-developers.com/show....php?t=1099374) and then follow the steps listed in the first post??
is the link in my post is the link to the final version of cwm for our devices??
Thank you very much for the help and sorry for the noobenst this is my first rom change
alon2 said:
hello all,
first of all THANK YOU very much for this ROM - really appreciate it!!!
second of all:
I currently have a stock rom on my device - rooted.
As I understand I need to replace the stock recovery with that of krylon360(http://forum.xda-developers.com/show....php?t=1099374) and then follow the steps listed in the first post??
is the link in my post is the link to the final version of cwm for our devices??
Thank you very much for the help and sorry for the noobenst this is my first rom change
Click to expand...
Click to collapse
your link wont load, just make sure you go to the thread that says CWM FINAL by krylon 360 and follow the steps and you will be fine
dsexton702 said:
your link wont load, just make sure you go to the thread that says CWM FINAL by krylon 360 and follow the steps and you will be fine
Click to expand...
Click to collapse
this is the link(as I see it in my broser)
what are the steps after I replaced the recovery?
is it as simple as following the steps in this thread?cause I saw people had problems...
Thank you very much for the help again
Just go to cyclopscomputers.com/gs4g
Sent from my SGH-T959V using XDA App
Use root explorer to copy/replace recovery.bin put update.zip on root of sd card, reboot into recovery.
Sent from my SGH-T959V using XDA Premium App
This is what I did and worked perfectly. But I allready had KD1 which I recomend you get. Download the recovery and update.zip and put both of them on the root of your sd card. Then get root explorer from the market. Open root explorer and go down to sdcard. In the sd card you are gonna find the recovery file you placed in there. Your long press it and its gomma say copy. Copy that and press back button and then your at the main page of root explorer again. Its gonna say paste and cancle at.the bottom but dont press anything yet. You go all the way down to system and go into it and then into /bin. In /bin your gonna press the mount r~w button at the top right which allows you to paste the file. You press paste at bottom left and its gonna ask if you want to overwrite say yes.(if it didnt ask you overwrite that either means the file you downloaded was renamed.or there was a (2) or (3) on it if you downloaded various times. Just take the ending out so its.just.recovery)
Now back out to homescreen of your phone.and if you have kd1 you can get into recovery from quickboot if not then turn off your phone and hold powerbutton and both volume keys while the phones turning on normally it will go to a bluish screen with an android.(recovery) here you click reinstall packages and your done
Sent from my SGH-T959V using XDA Premium App
sorry i have to do this... but i'm pretty sure theres more than enuff info to figure it out... noob or noobiest... didnt have to start a random thread
Moved to general.
rickyy00 said:
This is what I did and worked perfectly. But I allready had KD1 which I recomend you get. Download the recovery and update.zip and put both of them on the root of your sd card. Then get root explorer from the market. Open root explorer and go down to sdcard. In the sd card you are gonna find the recovery file you placed in there. Your long press it and its gomma say copy. Copy that and press back button and then your at the main page of root explorer again. Its gonna say paste and cancle at.the bottom but dont press anything yet. You go all the way down to system and go into it and then into /bin. In /bin your gonna press the mount r~w button at the top right which allows you to paste the file. You press paste at bottom left and its gonna ask if you want to overwrite say yes.(if it didnt ask you overwrite that either means the file you downloaded was renamed.or there was a (2) or (3) on it if you downloaded various times. Just take the ending out so its.just.recovery)
Now back out to homescreen of your phone.and if you have kd1 you can get into recovery from quickboot if not then turn off your phone and hold powerbutton and both volume keys while the phones turning on normally it will go to a bluish screen with an android.(recovery) here you click reinstall packages and your done
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Thank you very much for the detailed explanation.
I'll try that tomorrow at work cause at home I can't get windows 7 to recognize my device
To be honest u don't need a pc and can do the whole thing from your phone with the right apps and it works flawlessly haveing roottookit and supermanger also helpful in the process
Sent from my SGH-T959V
rose2jam said:
To be honest u don't need a pc and can do the whole thing from your phone with the right apps and it works flawlessly haveing roottookit and supermanger also helpful in the process
Sent from my SGH-T959V
Click to expand...
Click to collapse
how can I do it without a PC?
downloading now supermanger , didnt find roottookit
not working...
So I did as you said(didn't use my PC by downloading stright to the phone and using root explorer)
boot into recovery using quick boot app(exclamation mark screen with little green robot)
pressed the reinstall packages
it says:
-- Applying Multi CSC
-- Installing Multi CSC
-- Install from sdcard..(in yellow)
Finding update package(in yellow)
E:Can't mount /dev/block/mmcblk0p1(in red)
(No such file or directory)(in red)
E:Can't mount SDCARD:update.zip(in red)
Installation aborted(in red)
did I do something wrong?
alon2 said:
So I did as you said(didn't use my PC by downloading stright to the phone and using root explorer)
boot into recovery using quick boot app(exclamation mark screen with little green robot)
pressed the reinstall packages
it says:
-- Install from sdcard..(in yellow)
Finding update package(in yellow)
E:Can't mount /dev/block/mmcblk0p1(in red)
(No such file or directory)(in red)
E:Can't mount SDCARD:update.zip(in red)
Installation aborted(in red)
did I do something wrong?
Click to expand...
Click to collapse
Did you move the the update.zip to the correct directory?
yep moved it to /sdcard
Sent from my SGH-T959V using XDA App
Did u add the recovery file from downloaded to system .bin folder
Sent from my SGH-T959V
rose2jam said:
Did u add the recovery file from downloaded to system .bin folder
Sent from my SGH-T959V
Click to expand...
Click to collapse
yes I did just like the tutorial said to(overwrite the original)
/dev/block/mmcblk0p1 - really doesn't exist
E:Can't mount /dev/block/mmcblk0p1(in red)
(No such file or directory)(in red)
Click to expand...
Click to collapse
I really don't have that directory - should I have it?
issue solved by formatting the SDcard
so I formatted mt sdcard and the managed to get into CWM.
I hava another question:
now every time I want to go into CWM I should do the same procedure?
I mean put the update.zip in the root of the sdcard->go to recovery->reinstall apps?
Alon
That's what I do leaving the update there... btw its root toolbox helps geting into recovery without the three button push also with getting rid of bloat
Sent from my SGH-T959V
going to flash...few more questions
rose2jam said:
That's what I do leaving the update there... btw its root toolbox helps geting into recovery without the three button push also with getting rid of bloat
Sent from my SGH-T959V
Click to expand...
Click to collapse
Now that I have cwm I want to replace the kernel.
I want to take Bali v2.1 extended battery from whisky -
my questions are:
1) which kernel should I take:regular\UV(what's the difference anyway)
2) what about all my apps+data/contacts/sms...? will it erase them?what backup should I do?
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 ....