Install Rom on Galaxy S4 internal memory - Galaxy S 4 Q&A, Help & Troubleshooting

Hi Guys
I'm so lost and I've been trying to figure this out for 2 days now on my own.
I've rooted my S4 i9505 and installed ClockWorkMod on it but I don't have an SD card and am trying to install a ROM from the internal memory. My question is now how do I put the ROM at "root access level" on my phone? I have a Mac and a PC so instructions for either would be appreciated. When I attach the device via USB, it connects as a media device in Windows but what folder do I put the rom into?
Any help hugely appreciated

I had this problem as well. I ended up just sending the via sideload. Download the Google SDK and install the software toolkit.Place your .zip file in the same place as the adb.exe. Navigate to that folder in command prompt and run these command after selecting sideload in CWM.
ADB USB
ADB SIDELOAD NAMEOFROM.ZIP
Sent from my GT-I9505G using Tapatalk 4 Beta

Thanks for the reply.
I managed to sort out the issues.
What I did was install this:
1) CWM Advanced PhilZ Touch - this gave more options and made everything easier
2) I then downloaded the ZIP Rom I wanted and created a new folder on the phone using "Android File Transfer"
3) I then booted the phone into recovery mode and installed the rom via the "internal SD card" option and selected the zip and it was done in about 2 minutes!
Easy peasy when you know how but took me ages to figure it out!

Related

[ANDROID] ClockworkMod Permanent Installation Fix! - Step by Step Instructions

I have figured out a way to permanently install ClockworkMod Recovey on your hybrid WebOS/CyanogenMod Touchpad. Like many of you, my ClockworkMod installation failed when I tried to install using ACMEInstaller while I also installed CyanogenMod.
I realize there is now a workaround to "inject" ClockworkMod into your TP using novacom however this requires you to utilize a computer everytime you want to boot ClockworkMod. Follow the instructions below to install ClockworkMod onto your TP permanently and free yourself from your PC!
1. Boot into WebOS
2. Mount TP to your computer and create a "cminstall" folder if it no longer exists after your CyanogenMod installation
3. Copy the "update-cwm_tenderloin-1012.zip" file into the "cminstall" directory, then unmount TP from computer
4. Download the "Internalz Pro" program using the "Preware" application in WebOS if you haven't already (Google is your friend if you get stuck here)
5. Open "Internalz Pro" and navigate to the "boot" menu (will most likely require you to tap the top-most icon of a folder with two dots next to it to get to the root of the TP - should be second folder down)
6. Tap on the file "uImage.ClockworkMod" and select "move"
7. Navigate to the "media/internal/" directory and click "select" to move file
8. Now tap on the file "update-uimage" and move the file to the same "internal" directory you did in step #7
9. Exit from "Internalz Pro" and reboot device while holding down the up volume key, which will take you in to WebOS Recovery (or select WebOS Recovery when you get to the moboot screen you may have previously installed) - you should now see a large USB icon and should be connected to your computer using a usb cable
10. Go to your command prompt in Windows and navigate to the menu where you have novacom installed - you should also have the ACMEInstaller binary file copied into this directory by now (If you don't know what I'm talking about, remember Google is your friend)
11. Type in "novacom boot mem:// < ACMEInstaller" in the command line and press enter
12. You should now see ClockworkMod recovery installing on your TP - Once it reboots into moboot select "boot ClockworkMod" and watch it boot into ClockworkMod!
13. After celebrating, boot back into WebOS, go into "Internalz Pro" and move the file "update-uimage" back into the "boot" directory - the "uImage.ClockworkMod" file that you put in the "Internal" directory is no longer needed since you reinstalled ClockworkMod properly
Essentially the boot directory was overloaded which caused for insufficient space when installing ClockworkMod. Now you should be able to boot into WebOS, CyanogenMod, WebOS, AND ClockworkMod Recovery without a computer. As always, I do not take responsibility for you bricking your TP or variability you may have... use this information if it is helpful but don't blame me if something goes wrong. I'm just trying to help out the community that has helped me for so long.
Let me know if this is helpful to you. Thanks!
dseelye
What!?
Hi!
firstly, thank you for making this guide, i know that alot of people like myself will appreciate it.
but i've run into a problem, see, now i don't have the option to boot into cyanogenmod anymore !
can i flash it in clockworkmod, or do i have to do it all over again?
a reply would be appreciated
you most likely copied the wrong file from the boot folder, as there was one for clockworkmod and one for cyanogen mod... look and see if you incorrectly copied the cyanogenmod "uImage.CyanogenMod" to your internal sd card to free up space. You will have to move this back to the boot folder and grab the other one.
Thank you VERY much!
and thanks for the INCREDIBLY quick reply!
EDIT: IT WORKED!!! YOU'RE THE MAN!!!!!
No problem... let me know if that solved your concern...thx
EDIT: Oh, just saw the edit of your post...great, glad that was it!
Just wondering... how permanent is permanent?
For instance, if I use "web doctor" to restore my touchpad, will the recovery be overwritten?
Yes, I just mean that you don't have to "inject" clockworkmod into your TP using your computer which was the workaround for the people who couldn't get it installed originally during the CyanogenMod installation. This just installs it properly but can be wiped with WebOS Doctor like anything else...
bigblueshock said:
Just wondering... how permanent is permanent?
For instance, if I use "web doctor" to restore my touchpad, will the recovery be overwritten?
Click to expand...
Click to collapse
Yeap... it will not delete a single bit of CM7, just gonna restore the original bootloaders, delete moboot and skip CWM /Android on boot...
Running again ACME with only moboot and CWM in the cminstall folder will restore them.
....After WebOS doctor... it will show CM7 as the last time you shut it down.
Sent from my GT-I9000 using XDA App
I followed directions exactly but I am not seeing the uImage.clockwork in the boot folder. Any suggestions? I see that file in the cminstall folder, do I just leave in there or should I copy directly to media\internal?
Sent from my SPH-D710 using xda premium
The "uImage.ClockworkMod" may not be in the boot directory I suppose if the previous install attempts didn't put it there so not sure why it isn't in yours. Essentially you are just trying to move some of the larger files out of that directory so you can install ClockworkMod properly as the space constraint of the partition size seems to be the issue. The other file I mentioned, "update-uimage", is actually the largest one I found and you may be able to do the ClockworkMod install properly by only removing that one temporarily. Let us know if you are able to resolve.
I've installed clockworkmod recovery with no errors on the first try, is it advisable that I need to use this method?
I was installing cwm for the first time. I didn't include it originally with the install of cyanogen mod, I guess that's why it wasn't in the boot folder. I placed both files in the media\internal directory and also inside the cminstall folder and ran the command and it worked fine. When I checked internalz pro to remove the files, the cminstall folder and uimage files were gone already. So it looks like I am good to go. cwm is working, I flashed gapps from it. Thanks for reply.
Now I just need to figure out how to make phone calls.
Sent from my SPH-D710 using xda premium
If you installed ClockworkMod completely the first time and it works, then you definitely don't need to do this as this thread was intended for those that tried to install it at the same time as when they installed CyanogenMod and ClockworkMod Recovery didn't install properly. These instructions are to outline how to get it installed correctly as just trying again using ACMEInstaller wasn't working for anyone due to the small size left in the boot directory.
hey thanks for the fix but after the fix i cant get into the market
Not sure why you can't access the market...no issues here. I would suggest reinstalling the gapps zip file and possible the market fix file that are out there now that you have clockworkmod working properly.
thanks for the help thats what i had to do
Hi, the "move" option isn't available, only "copy" "info" and "open"
The entire directory is "view-only"
Not sure why "move" isn't available for you... its been a while since I installed Preware and Internalz Pro so I must have gotten root access somehow and that's why it shows up for me and others. I'd suggest searching for how to obtain root access to WebOS to find your answer... possibly development mode if you haven't already done that but I thought that was required to get Preware installed in the first place.
Move command
dseelye said:
Not sure why "move" isn't available for you... its been a while since I installed Preware and Internalz Pro so I must have gotten root access somehow and that's why it shows up for me and others. I'd suggest searching for how to obtain root access to WebOS to find your answer... possibly development mode if you haven't already done that but I thought that was required to get Preware installed in the first place.
Click to expand...
Click to collapse
I have the same problem. Move/delete commands are available on the media/internals but on boot folder move is not available.
Thanks
Awesome man! Been struggling with this since two days. Thanks a lot for the fix and step by step instructions
---------- Post added at 09:07 AM ---------- Previous post was at 09:00 AM ----------
tmkhan said:
I have the same problem. Move/delete commands are available on the media/internals but on boot folder move is not available.
Click to expand...
Click to collapse
After Opening "Internalz Pro", Open "Preferences", scroll down to the bottom. You will see an option called "Master mode". Turn it on. You will get read/write access to the boot folder.

Can't write on internal SD card after root

After having rooted (with nexus 10 toolkit v1.3.0) my nexus 10 and flashed AOPK Nexus 10 (WIP) Task650 & Ktoonsez (1-4) rom, I'm unable to upload to, change or move any files or folders on my internal SD card. I installed Root Explorer and changed from Mount R/O to Mounted as r/w. Access is granted by Super SU. I also tried to change permission settings, unfortunatedly without any success. There appeared the following message:
"Warning
Permissions change was not successful. Please note that some file systems (e.g. SD card) do not allow permission changes."
Is there a possibility to change these permissions in order to be able to create and move files and folders on my SD card?
Thanks for taking your time to help me with my issue!
Anzirothu
1. Clear cache
2. Clear dalvik
3. Fix Permissions
forgot something ?
Thank you for your reply, Patrik!
1. done.
2. done.
3. Fix Permissions - How? With cwm? I did fix permissions with cwm recovery, but the problem persists...
Just so we are clear, when you say "upload to, change, or move" are you meaning you cannot copy a file from your computer to your Nexus 10? Or just that you cant arrange stuff through root explorer from within the tablet itself?
Neither copying from PC to Nexus nor arranging stuff through root exlorer from within the tablet itself. I can't even download an email attachment and put it to the SD card. The card seems to be locked.
I had that problem once but I dont remember what caused it or what exactly I did to fix. I think I just did a complete wipe by locking and unlocking the bootloader and then installing a new ROM again.
I think I did this too (unroot, lock bootloader, then root and unlock bootloader) and then installed the same rom again. I will try it this time with another rom.
Isn't there really no other solution to get access to my SD card again??
Thx for your help!
Are you using a toolkit to unlock and root? If so them maybe it is not doing something right and it messing up a permissions somewhere. It could also be a driver problem on your PC with being unable to copy a file to the tablet.
Thank you for your help!
I am using the nexus 10 toolkit V1.3.0. Right now I'm trying to intall twrp recovery with a fully wiped sd card. No easy task fot me being a noob...
In ClockWorkMod, make sure that /data is mounted
Then download the Android SDK: http://developer.android.com/sdk/index.html
I usually put all the files just in C:/android-sdk-windows
Once you have it all there open up the SDK Manager and download all the additional files needed. You probably only need to download "Android SDK Tools" and "Android SDK Platform-tools", but I always download the other files for whatever version of Android I am running, in our case Android 4.2. That way I have them if I need to do something else.
Once downloaded, open the Android-sdk-windows/platform-tools directory. copy:
adb.exe
adbWinApi.dll
adbWinUsbApi.dll
fastboot.exe
to your base C:/Android-SDK-Windows directory.
Now open command prompt from Start -> run
type: cd C:/Android-SDK-Windows
type: "adb devices" and it should list your tablet. It will actually say something with your devices serial number and then "Recovery" after it, showing your tablet is in recovery. If you dont see this then you either dont have your tablet mounted right from in the Recovery, ClockWorkMod is stupid, or you dont have working adb drivers.
Now copy the ROM you want to flash to C:/Android-SDK-Windows
Then type: "adb push blahblahblah.zip /data/media/0"
That should push the ROM to the root of your SD card. Give it time, it takes a while to push a ROM file. Once it is done, flash the ROM.
That *should* put it in the right spot where it looks like it is on your "internal storage" (what you see when navigating files within the ROM). If you dont see the ROM in clockworkMod then keep navigating back to the root of your internal storage and then open up "data", then "media", then "0" and you should see it. If you still cant find the ROM, push it again but just use "/data/media" as the location.
I just did all these steps myself to verify I remembered it all correct and I was able to successfully copy a ROM and find it on my tablet to flash by doing everything I just listed above. SO you should be good to go if you follow all those steps properly. I know it looks like a lot of work, but it really isnt and will go quite fast. Most of it is just the setup for getting ADB and Fastboot ready to use.
For a ROM to install, I would recommend to someone new like you either of these:
http://forum.xda-developers.com/showthread.php?t=2071082
^^^^^ That one is pretty close to the stock ROM with a few fixes and a couple extra features
or: http://forum.xda-developers.com/showthread.php?t=2071082
^^^^^ This one is pretty much CyanogenMod 10.1, but built by a different guy and not pulling every new thing from CM, just the "cherry picks" of features. It tends to be a bit more stable and less buggy than the real CM10.1 nightly's
And for a kernel you can flash and forget you will want to try this one:
http://forum.xda-developers.com/showthread.php?t=2098157
^^^^^ To flash that you will want to do a similar thing as how you pushed the ROM to your device. Only this time you will copy the kernels' "boot-r4.img" file into your android-adk-windows directory and use the command: "fastboot flash boot boot-r4.img"
While I enjoy the KTManta kernel more, it does require a bit of tweaking to get running perfect. Which is one of the things I like about it because of all the options to tweak. But for someone just learning this stuff that would be a bad thing, so Franco's kernel is much better than stock and doesnt require you to adjust anything once it is flashed to your tablet.

[Q] Desperate need some help, failure updating 4.4

my nexus 4 was rooted with 4.3 but then i decide to upgrade to 4.4
this is the video i am trying to follow, basically just wipe & install which i did most the time.
youtube title "NEXUS 4: HOW TO MANUALLY UPDATE TO ANDROID 4.4 KITKAT"
it has two files one is mako and one is gapp.
after i did all the wiping in cwm and try to install the mako file, it shows "no file context" or sth similar, and installation is abort (i think there is problem when i transfer the file), but then i continue to install the gapp file (what the hell was i thinking?)
so now i am stuck in the google start up loop, i can only access cwm recovery mode and don't have a valid rom to install in my sdcard.
i tried to adb push another rom to the sdcard with no success (my storage was already very low, any way to remove files in the storage at this point?)
the "mount & storage" also doesn't seem to let me mount the sdcard (but system shows up "unmount").
so now i don't know what to do.
if anything has any idea or suggestion please let us know.
i am quite desperate now with a dead phone and will try anything.
thanks for reading such a long thread.
Dude that vid is old and it installs pa or some other port just flash factory images from google
Sent from my F1 using xda app-developers app
try to sideload a zip with ADB in recovery. no need to copy to your internal storage.
also try to connect with adb shell, then you can delete some files manual with rm.
Frickelpit said:
try to sideload a zip with ADB in recovery. no need to copy to your internal storage.
also try to connect with adb shell, then you can delete some files manual with rm.
Click to expand...
Click to collapse
any step by step guide to do this?
i am still new to this thing even i install a few roms before.
i will google it now, but any additional info is much appreciate.
thanks
Frickelpit said:
try to sideload a zip with ADB in recovery. no need to copy to your internal storage.
also try to connect with adb shell, then you can delete some files manual with rm.
Click to expand...
Click to collapse
frustrated..
i can't seem to get my windows to recogize the device (when i type adb devices, it shows an empty list)
already try trouble shooting this for a long time with no result.
any idea?
telly0050 said:
frustrated..
i can't seem to get my windows to recogize the device (when i type adb devices, it shows an empty list)
already try trouble shooting this for a long time with no result.
any idea?
Click to expand...
Click to collapse
after tons of troubleshooting finally got it back to work.
it ends up the reason is i didn't update to the latest cwm at the very beginning.
and sideloading 4.4 didn't work because of that too, i have to install an old 4.2 to have it working.

Phone now has no OS!

Had LG G2 2 hours
Rooted, TWRP installed. Downloaded new ROM and copied to storage (whilst phone was running). Booted in to recovery wiped Rom (stupidly) then went to install new Rom which is not there. So I have no OS...
Unless it's in a weird directory I need to copy it across again however Mount under TWRP settings does not bring up windows explorer to allow me to copy it again (USB Drivers all installed I thought after root process). Had it got an SD card slot I could have burnt it to that in my PC and then put it in the phone.
Any ideas please
jamesbond_28_007 said:
Had LG G2 2 hours
Rooted, TWRP installed. Downloaded new ROM and copied to storage (whilst phone was running). Booted in to recovery wiped Rom (stupidly) then went to install new Rom which is not there. So I have no OS...
Unless it's in a weird directory I need to copy it across again however Mount under TWRP settings does not bring up windows explorer to allow me to copy it again (USB Drivers all installed I thought after root process). Had it got an SD card slot I could have burnt it to that in my PC and then put it in the phone.
Any ideas please
Click to expand...
Click to collapse
"adb sideload" -> please type into the searchbox. Would help you a little more but busy currently. however this will help you.
So you wiped your complete storage? lol.
Try to sideload your rom.
http://android-revolution-hd.blogspot.de/2013/12/ow-to-use-adb-sideload.html
ckyy said:
So you wiped your complete storage? lol.
Try to sideload your rom.
http://android-revolution-hd.blogspot.de/2013/12/ow-to-use-adb-sideload.html
Click to expand...
Click to collapse
Yes nightmare. And ADB doesnt look for the faint hearted either. is there no way of mounting in TWRP?
jamesbond_28_007 said:
Yes nightmare. And ADB doesnt look for the faint hearted either. is there no way of mounting in TWRP?
Click to expand...
Click to collapse
I wouldn't bother trying to get it to work. Sideloading is way faster.
http://forum.xda-developers.com/showthread.php?t=2588979
1. Download and install it. Put the rom inside ADB folder. Put twrp in sideload mode.
2. Open your adb folder and shift-right click. Select open command propt here.
3. This is what you type in your CMD -> adb sideload flash.zip (flash.zip is obviously replaced by your rom name).
ckyy said:
I wouldn't bother trying to get it to work. Sideloading is way faster.
http://forum.xda-developers.com/showthread.php?t=2588979
1. Download and install it. Put the rom inside ADB folder. Put twrp in sideload mode.
2. Open your adb folder and shift-right click. Select open command propt here.
3. This is what you type in your CMD -> adb sideload flash.zip (flash.zip is obviously replaced by your rom name).
Click to expand...
Click to collapse
Thanks. 'device not found'...
jamesbond_28_007 said:
Thanks. 'device not found'...
Click to expand...
Click to collapse
Have you installed all drivers?
Gesendet von meinem LG-D802 mit Tapatalk
jamesbond_28_007 said:
Thanks. 'device not found'...
Click to expand...
Click to collapse
Ok. Needed google universal ADB driver by Koush (as windows 8). So it reached 100% but phone back on LG flashscreen...
jamesbond_28_007 said:
Ok. Needed google universal ADB driver by Koush (as windows 8). So it reached 100% but phone back on LG flashscreen...
Click to expand...
Click to collapse
All good. Thanks for all the help and apologies for being such a muppet.

[Q] How to install a ROM on Micromax Canvas Juice A177 using ADB?

Hi Geeks
Yesterday I kinda soft-bricked(idk but i think that's what its called) my phone(Micromax Canvas Juice A177). I moved my /system/app/ folder to my sdcard and now my phone won't boot. The boot animation runs in a loop. i can access the power_button+volume_up menu. Another big problem is that i cannot use my External sdcard for recovery since i have swapped my sdcard1 with sdcard0. so when i open "apply update from sdcard" it opens my ORIGINALLY-sdcard0(which is now treated as sdcard1) which i cannot remove from my phone. so apply update from sdcard option is terminated.
i want to know if there is any way i can re-copy the /system/app/ folder to my device. i tried doing the same via adb but it always returns an error:closed.
then i thought i would install all those packages manually using adb sideload packagename.apk which would basically put them in the /system/app folder(if i'm not mistaken). but every time i try installing a package it sends the package till 100% but my phone shows "Installation Aborted".
Now i am downloading the stock ROM but i don't think I'll be able to install it using adb sideload.
i have never installed a ROM before.
please help me at least start my device!!!
Thanks

Categories

Resources