Related
I always get an error saying E:/ cannot open file /cache/update.zip (bad), no matter what ROM it is. theres not even an update.zip anywhere on my phone or sd card, and i cant manage to get to this so called /cache. please help.
Mrblackroot said:
I always get an error saying E:/ cannot open file /cache/update.zip (bad), no matter what ROM it is. theres not even an update.zip anywhere on my phone or sd card, and i cant manage to get to this so called /cache. please help.
Click to expand...
Click to collapse
Since this isn't development related, you should post it in the general board.
You didn't install clockwork correctly, or you didn't follow all of the directions when you did install it. Did you follow the instructions and press "flash clockworkmod recovery", which downloads the latest version and puts the update file on your phone?
i did, i have the latest recovery version. and i uninstalled and then reinstalled it before trying again.
Wrong section and you have to use the option that says choose zip from sdcard not the one that says install update.zip
Sent from my GT-I9000 using XDA App
Mrblackroot said:
I always get an error saying E:/ cannot open file /cache/update.zip (bad), no matter what ROM it is. theres not even an update.zip anywhere on my phone or sd card, and i cant manage to get to this so called /cache. please help.
Click to expand...
Click to collapse
If there is no update.zip then in Rom Manager you need to select the first option that reads Flash ClockworkMod Recovery. That will bring up a screen asking which phone. If you are installing an i9000 rom choose i9000. If not choose the Captivate. That will install an update.zip on your sd card
Then select install rom from sd card and it will probably take you to stock recovery so select install packages (or whatever the 2nd choice is). That will get you into CWM. Install whatever rom from there
First off, this is the right section, as this thread is *somewhat* development related.
I had a similar problem a while back, and never did figure out exactly what was causing it. Might have been because I often just use the Clockwork update.zip (bootstrapped from stock recovery) to flash ROMs without always "installing" it from Android itself. Though, even when I got that error, I could still flash new ROMs without problems.
Either way, flash to stock w/ oneclick, then do a master clear, fixes the problem right up.
If there is no update.zip then in Rom Manager you need to select the first option that reads Flash ClockworkMod Recovery. That will bring up a screen asking which phone. If you are installing an i9000 rom choose i9000. If not choose the Captivate. That will install an update.zip on your sd card
Then select install rom from sd card and it will probably take you to stock recovery so select install packages (or whatever the 2nd choice is). That will get you into CWM. Install whatever rom from there
Click to expand...
Click to collapse
Thanks a lot, this worked. is there anyway i can just move this thread to the general forum, or would that require a moderator?
Shammyh said:
First off, this is the right section, as this thread is *somewhat* development related.
I had a similar problem a while back, and never did figure out exactly what was causing it. Might have been because I often just use the Clockwork update.zip (bootstrapped from stock recovery) to flash ROMs without always "installing" it from Android itself. Though, even when I got that error, I could still flash new ROMs without problems.
Either way, flash to stock w/ oneclick, then do a master clear, fixes the problem right up.
Click to expand...
Click to collapse
Mmmm.. last time I checked the development forums was for developers to start topics on things they have developed or are working on... not for Q & A. There's another board for that..
I get this error all the time.
Open ROM Manager, hit Menu, hit Clear Download Cache.
Then hit Flash Clockwork Mod Recovery, choose Captivate, and let it go. Then hit Reboot Into Recovery and it should work fine. You may have to select Reinstall Packages if you end up in the stock 2e recovery.
I'm so confused with all the lingo, root, kernel, s-off, ruu.
It just seems so overwelming. I don't think I want custom roms, all I want is att stuff removed, and faster data speeds.
And I'd like a way to return to stock in case I need to return the phone.
What phone are you coming from?
Read, as much as you can Google is your friend. Also if your having problems with goldcard checkout the unlockr. Setting up sdk isn't all that bad. This is coming from a renewed rookie with HTC phones because I've been away from adb for two years since I got rid of my dream and magic.
Coming from an iPhone. Don't understand anything about adb, sdk, terminal, etc.
Haven't tried making the gold card yet, ordered an sdcard but it hasn't come in yet.
harlenm said:
Coming from an iPhone. Don't understand anything about adb, sdk, terminal, etc.
Haven't tried making the gold card yet, ordered an sdcard but it hasn't come in yet.
Click to expand...
Click to collapse
Just use the card that came with the phone for goldcard. Use the goldcard helper tool from the market, get the mcc 2 number from the tool, go to the link provided, insert the mcc 2 number into the box on the page where it asks for it, get the file that was emailed to you, download the hack kit in the stickied thread of development, after installing Android sdk, unzip the hack kit using 7zip and only 7zip into the tools folder located in the Android folder. From that point you are ready to create a goldcard. That's where the sticky thread is your friend.
I know it sounds like a lot and in the end once you read up and understand how to use adb you'll understand its not that bad. Remember i am a rookie as well with most of this and would be glad to help as you progress
I think creating the gold card seems like the easy step, found a program that will do it and upload it to phone without needing the sdk.
My concern is all the other stuff, different kernels, different radios, etc. Downgrading the radio loses sound, so then you have to upgrade it again, but then the sound isn't as good, etc.
Then someone posted the stock kernel, compared to a telus kernel, what's the difference, and why put one over the other?
harlenm said:
I think creating the gold card seems like the easy step, found a program that will do it and upload it to phone without needing the sdk.
My concern is all the other stuff, different kernels, different radios, etc. Downgrading the radio loses sound, so then you have to upgrade it again, but then the sound isn't as good, etc.
Then someone posted the stock kernel, compared to a telus kernel, what's the difference, and why put one over the other?
Click to expand...
Click to collapse
The program doesn't work you need mcc2 number. The sound problem is a correlation of combining the dhd time with our kernel.
harlenm said:
Coming from an iPhone. Don't understand anything about adb, sdk, terminal, etc.
Haven't tried making the gold card yet, ordered an sdcard but it hasn't come in yet.
Click to expand...
Click to collapse
This will help with adb.Once you start tinkering you will figure it out quickly. As far as reading all the sound issues its really personal preference. You have to do these thing on your device and see if you have the same issue. Alot of the times you will find it that it comes down to different strokes for different folks. I myself have none of the issues that others have other than a weak external speaker. Reading is a great tool but dont get overwhelmed with the information your taking in because a good chunk will not pertain to you and your device. Just stick with the core information and what the op stated
The sound issue is the only thing that is not 100%, which will be fixed soon enough. We will get our own source soon enough, but for the time being dhd roms will do fine with either the stock or TELUS kernel. Personally the TELUS is better for fast data speeds.
harlenm said:
Coming from an iPhone. Don't understand anything about adb, sdk, terminal, etc.
Haven't tried making the gold card yet, ordered an sdcard but it hasn't come in yet.
Click to expand...
Click to collapse
Just my two cents and I hope you don't take offense to this, but you picked the wrong phone to jump into rooting and customizing since it's a new phone and the forums aren't yet up to speed on info. I would first read up in the Rodgers Magic 32A forum on how gold cards work, recovery, fastboot, adb, and custom roms work - these phones are broadly used and have been around for a while too.
I've read the instructions in the hack kit, and I still dont' get it.
I need to download the sdk, found that at http://developer.android.com/sdk/index.html
It says Terminal on the phone, so I need to download a terminal app from the market?
The commands look simple enough if I can figure out how to do them.
Edit, also need to download HTC sync?
read the guide Ive listed on how to install adb on the sdk and you will be fine.
harlenm said:
I've read the instructions in the hack kit, and I still dont' get it.
I need to download the sdk, found that at http://developer.android.com/sdk/index.html
It says Terminal on the phone, so I need to download a terminal app from the market?
The commands look simple enough if I can figure out how to do them.
Edit, also need to download HTC sync?
Click to expand...
Click to collapse
After the downgrade, terminal gets installed with the Rom. Always remember to enable debugging and charge only. The terminal part is the hardest. Also after receiving temproot exit out so you can go back into your sdk folder. All the hackerize commands are done from the kit location.
Well, I can't do this at work, was planning on trying, but the sdcard reader in my printer here doesn't work, so I'll have to try it with my laptop at home. Just wasted time downloading all the packages.
Still seems very cumbersome and confusing.
harlenm said:
Well, I can't do this at work, was planning on trying, but the sdcard reader in my printer here doesn't work, so I'll have to try it with my laptop at home. Just wasted time downloading all the packages.
Still seems very cumbersome and confusing.
Click to expand...
Click to collapse
You don't even need the SD reader. Just leave it the phone.
davwman said:
You don't even need the SD reader. Just leave it the phone.
Click to expand...
Click to collapse
Oh.
Now, once I get this done, how do you flash the new ROM?
harlenm said:
Oh.
Now, once I get this done, how do you flash the new ROM?
Click to expand...
Click to collapse
Once you have root, you can install ROM manager from the market. Run ROM manager, scroll to the bottom and tap on "All ClockworkMod Recoveries" and select 2.5.1.3 or 2.5.1.4. DO NOT INSTALL 3.0.0.5, it is NOT compatible with Froyo ROMs.
Once you tap one of those versions, it will automatically download and install ClockworkMod Recovery. Load the ROM you want to install onto your SD card, and in ROM manager, hit "reboot into recovery".
When you get to recovery, go to Backup/Restore and make a backup of your current ROM. Then do a data/cache wipe (factory restore) and then go to Install ZIP from SD Card and select your new ROM. Flash and you're on your merry way
harlenm said:
Oh.
Now, once I get this done, how do you flash the new ROM?
Click to expand...
Click to collapse
Read the included readme file in the kit its part of step two. The kit is designed so all you need to do is follow the instructions and input a few commands and it pretty much does everything for you minus pushing the power button to get into hboot. The second hackerize command is the actual downgraded Rom.
r34p3rex said:
Once you have root, you can install ROM manager from the market. Run ROM manager, scroll to the bottom and tap on "All ClockworkMod Recoveries" and select 2.5.1.3 or 2.5.1.4. DO NOT INSTALL 3.0.0.5, it is NOT compatible with Froyo ROMs.
Once you tap one of those versions, it will automatically download and install ClockworkMod Recovery. Load the ROM you want to install onto your SD card, and in ROM manager, hit "reboot into recovery".
When you get to recovery, go to Backup/Restore and make a backup of your current ROM. Then do a data/cache wipe (factory restore) and then go to Install ZIP from SD Card and select your new ROM. Flash and you're on your merry way
Click to expand...
Click to collapse
Thanks, gonna read up more and then go for it.
I just downloaded Rom manager and it says i need clockwork recover installed. So i select it.
It gives me 4 choices.
1. Google nexus S
2. Google nexus S 4G
3. Samsung epic 4G
4. Samsung Galaxy S i9000
I have a Samsung Galaxy Captivate i896 (Rogers).
Which one do i select?
Im guessing the i9000 but i will await a reply!
Thanks.
Satstalker said:
I just downloaded Rom manager and it says i need clockwork recover installed. So i select it.
It gives me 4 choices.
1. Google nexus S
2. Google nexus S 4G
3. Samsung epic 4G
4. Samsung Galaxy S i9000
I have a Samsung Galaxy Captivate i896 (Rogers).
Which one do i select?
Im guessing the i9000 but i will await a reply!
Thanks.
Click to expand...
Click to collapse
You'll need option 5: None of the above.
Seriously, though, Rom Manager doesn't work that well for the Captivate. You'll be in much better shape if you do the things that Rom Manager normally handles by yourself.
jmtheiss said:
You'll need option 5: None of the above.
Seriously, though, Rom Manager doesn't work that well for the Captivate. You'll be in much better shape if you do the things that Rom Manager normally handles by yourself.
Click to expand...
Click to collapse
Really!!! Damn. I just bought Rom manager premium and was going to flash CyanogenMod on my phone and i found a video using rom manager and it seems a lot easier to do with it.
Im wondering if its because i changed the stock kernel so i could root the phone! I put the mtcareys-kernel on following a user post.
I bet that's why i does not recognize the phone.
Sorry to hear you spent the money, but maybe it's not entirely bad - Rom Manager works on a lot of other devices, and you can (I believe) transfer the program between devices.
Rom Manager might not recognize your device if the build.prop file was edited. That could be why it's showing the I9000 option.
As far as flashing CyanogenMod, it's fairly straightforward:
1. Flash a kernel that will let you use CWM Recovery (Corn Kernel should have it - Boog's kernel does too, and if you need Froyo, look for speedmod).
2. Once in Recovery, flash the CM update.zip (you may have to do this twice. If so, reboot to recovery again, and flash again).
That should get you to CyanogenMod.
jmtheiss said:
Sorry to hear you spent the money, but maybe it's not entirely bad - Rom Manager works on a lot of other devices, and you can (I believe) transfer the program between devices.
Rom Manager might not recognize your device if the build.prop file was edited. That could be why it's showing the I9000 option.
As far as flashing CyanogenMod, it's fairly straightforward:
1. Flash a kernel that will let you use CWM Recovery (Corn Kernel should have it - Boog's kernel does too, and if you need Froyo, look for speedmod).
2. Once in Recovery, flash the CM update.zip (you may have to do this twice. If so, reboot to recovery again, and flash again).
That should get you to CyanogenMod.
Click to expand...
Click to collapse
Clockwork mod recover. Is that the blue writing that comes up when you press and hold volume up and down and then power? If so then yes i do have that. I used that to root the phone with the corn kernel. Little green guy with a yellow corn a boot up!
I did down load the latest stable version of CM. (update-cm-7.1.0-Captivate-signed)
It says to Place the CyanogenMod update.zip file on the root of the internal memory. But then it says Select Install zip from sdcard.
Also where is the update.zip file? And does it go on the root of the sd card or the root of the internal memory!
I'm following the guide here. http://wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Full_Update_Guide#Before_you_do_anything_.E2.80.94_Make_a_backup
The actual name of the file you downloaded isn't that important. You can leave it with whatever it comes as. The "update.zip" they're referring to is the CM build you downloaded.
What you'll need to do is to copy the .zip file onto your phone Internal SD (the 13 GB partition) at a place you can find it easily. Once you've done that, reboot into CWM recovery (the menu with about 7-9 options, including "install zip from sdcard". It may have blue writing, depending on which build it is. If it only has 4 options, you don't have CWM recovery, but stock recovery.).
Once you're there, select the install zip from sdcard option, and navigate to where you put that zip file. Choose to install it and let it run.
If you're confused about whether you're putting an item on the internal sd card or not, you can connect your phone (including doing the "connect usb storage" dialog) and see what the drive sizes are. Once you know for sure which is your internal SD (13 GB), and which is your external SD (GB based on your card size), you can then re-label them in Windows (e.g. Internal SD and External SD). Those labels will usually stick pretty well.
oops
i was going thru my file manager to get rid of some old downloads and files and i deleted update.zip. i am now pretty sure it was for rom manager or cwm and remember seeing somewhere that it is supposed to stay on the phone.
how to fix this? download new rom manager?
I have noticed lately that when i want to reboot to recovery from rom manager to flash something it just reboots the phone.
bradddo said:
i was going thru my file manager to get rid of some old downloads and files and i deleted update.zip. i am now pretty sure it was for rom manager or cwm and remember seeing somewhere that it is supposed to stay on the phone.
how to fix this? download new rom manager?
I have noticed lately that when i want to reboot to recovery from rom manager to flash something it just reboots the phone.
Click to expand...
Click to collapse
1. Don't worry about the .zip
2. Don't use ROM manager for this device
Sent from my SGH-I777 using xda premium
That s what I was hoping. I don't know what I have actually used this for , I just thought I needed it. I Normally boot to recovery and flash from there. Can I delete it, or is there a purpose for it?
Sent from my SGH-I897 using xda app-developers app
The update.zip contained cwm and was used during the eclair 2.1 days. Now days to get access to cwm we have custom kernels and we can use the extended power button menu of dev roms, button combo, apps, etc. to boot into recovery...so yep, don't worry about keepin it, unless u plan on goin back to eclair.
Sent from my SGH-I897 using xda premium
**this was a very early guide and most of the files and methods referenced in it are long outdated, sounds crazy I know as the phone has barely been out, but i recommend finding more recent guides at this point. I wanted to leave this up for archival reasons though. As of 7-22 I am running dhackers CM10 build with great results. Just don't forget to set max cpu clock back down to 1500 mhz if you don't want it over locked out of the box **
As per the usual disclaimer....at your own risk, be aware of IMEI loss issues and whatnot...basically cover your own butt.....and enjoy.....
7-15 2:46pm **As of right now voice and SMS are not working on my phone while other people report they are working fine. While you can still play around and see just how amazingly fast CM is on this phone, YMMV. If it doesn't work you need to know how to go back to stock before trying this.
7-29 this guide is very old, it pre-dates kexec and is only here for historical purposes
For clarification: The question was asked if one is supposed to follow the original Team Epic Kexec kernel instructions or these steps and the answer is two fold. If your goal is to install the UNOFFICIAL CM9 built by Invisiblek (which is the purpose of this thread), then you follow the steps in THIS THREAD ONLY. There are a couple steps and a couple files linked to in the original Kexec page that will not allow you to install CM9. That page was made for those wanting to try out their Kexec Proof of Concept KERNEL, not install a ROM of any kind.
This thread makes some assumptions, such as you already have a working install of the Android SDK and ADB, you already have the drivers installed, you are using the original USB cable that came with your phone, you know how to move around DOS to get to the directory where you downloaded the files, etc.......those lower level tasks are for another thread.
To Try Our Proof-of-Concept Kernel <<<The base of these instructions was the Team Epic Kexec Kernel page seen at this link, Many Thanks to them
Thanks to Invisiblek for clarifying and helping me get steps just right.
The following is an adaptation of the CM Kexec kernel proof of concept with the changes in files and steps necessary to load the latest CM9 work in progress. Be advised I take no credit at all. This is the work of Team Epic and Invisiblek. I just put this together for myself and for others who would like to try it with one caveat. DATA doesn't work! Voice and SMS only....and maybe 1xRtt data.....so you will be relying on WiFi for data! You've been warned!
Also, I highly suggest you use a free MD5 Hash checking utility to verify the integrity of the files you are downloading. That is why the MD5 hash is provided, so you can be sure you didn't get the wrong file or a corrupt download that could cause a BRICK!
If you don't follow the directions carefully you can end up with a brick! Ask questions after reading the OP if you still aren't sure. I probably won't know the right answer for sure. You may have to wait on someone with more experience in this to answer your question.
DO NOT ACCEPT AN OTA UPDATE WHILE RUNNING THIS SETUP
1. Download the recovery.img (MD5: f1c01ad20e02751a73188f173eb412ca), which combines our source-based kernel with our previously released CWM v4.
2. Flash the recovery.img following these instructions, that is:
Code:
adb push recovery.img /sdcard/
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 bs=256k
sync
3. Reboot into recovery (using volume up, home power buttons), wipe data, install one of invisibleks CM9 roms>click here for all of his CM9 roms< which do not have boot.img integrated, then continue with the steps below:
4. Download these additional files:
(required download)boot.img (MD5: db058f4b15df0fa1b9ee04a5c17cf103), which is invisibleks custom boot.img
It would be good at this point to read ahead and determine where you will be loading the next file. Keep in mind if you are in stock recovery and choose to wipe data, this will wipe the internal memory.
if you plan to load onto internal memory download this file boot_emmc_boot_img.zip (MD5: 84a3f98c194f6dedc583dbc75ccc34c2)
or
if you plan to load onto sdcard (ext) memory download this file boot_sdcard_boot_img.zip (MD5: 88904d7e69d455ff88756b4d1ad79aac), which are applied in recovery to kexec (boot) the custom boot.img.
5. Place boot.img either on the internal SD card (the /sdcard/ folder), or on the external SD card (the /mnt/extSdCard/ folder).
The boot.img kernel boots directly out of one of these folders, it will not (and should not) be flashed to the device.
6. If you're using the internal SD card, place boot_emmc_boot_img.zip in /sdcard/ as well. If you're using the external SD card, place boot_sdcard_boot_img.zip in /mnt/extSdCard/.
7. Reboot into recovery.
8. If using the internal SD card, select "Install zip from sd card" and then "choose zip from internal sdcard", then "boot_emmc_boot_img.zip". Alternatively, if using the external SD card, select "choose zip from sdcard", then "boot_sdcard_boot_img.zip".
At this point, the device should reboot "in the middle" of applying the update, temporarily booting boot.img. If the update "completes" and returns to the CWM menu, kexec has failed or the wrong recovery was loaded in the beginning. Please check the locations of boot.img, and boot_emmc_boot_img.zip or boot_sdcard_boot_img.zip and verify recovery.img file used was the correct one, verify using an MD5 hash checker.
9. Once booted, the custom kernel can be confirmed by checking "Kernel version" in "Settings", "About device". It should report:
3.0.8-gdefeb6f
[email protected] #1
SMP PREEMPT Sun Jul 8 04:27:58 EDT
2012
10. To reboot into the stock kernel, select "Restart" from the Power menu, which will actually reboot into CWM recovery. Press the Power button to select "reboot system now" and leave recovery.
11. You cannot simply power on your phone with this setup! In order to power on your phone you will have to hold volume up, home and power to boot into recovery and load the zip file you chose at step 4 where you chose either internal or external memory, so either "boot_emmc_boot_img.zip" or "boot_sdcard_boot_img.zip". If you do accidentally boot up by just hitting power, no big deal, it will give you all sorts of force closes, simply pull battery and boot back up using the Vol up, Home, power method.
If anyone would like to suggest further clarification, please do. To get the stock Google apps such as Play Store get the package HERE and install in recovery
Alternatively a more condensed version of this install procedure has been posted by nbsdx and can be found HERE.
7-15 2:46pm **As of right now voice and SMS are not working on my phone while others are working fine. While you can still play around and see just how amazingly fast CM is on this phone, YMMV. If it doesn't work you need to know how to go back to stock before trying this.
If you want to return to bone stock, simply go to THIS THREAD to get STOCK ROM IMAGE and then put your phone into Odin Download mode by following THIS THREAD and be sure to flash it using the PDA button. It will take a while, probably 20 minutes or so, it will take forever to boot up the first time but you will be on bone stock like new.
Very informative. Would read again.
Sent from my Transformer Prime TF201
dual boot
Being that we have to use kexec anyhow, it would be nice (especially with the state of current cm9 rom) if we could fully dual boot so as to keep stock system and data for stock kernel.
Like here,
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html
I just installed successfully using the instructions in the OP so I can confirm it works correctly. Holy crap it's fast.
Anybody want to put up a video of how well it runs for us that aren't brave enough to put it on our own phones?
Sent from my SCH-I535 using xda premium
dakalter said:
Anybody want to put up a video of how well it runs for us that aren't brave enough to put it on our own phones?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I'll leave that part to someone who doesn't sound like a retarded redneck on video.
silasrye said:
I tried to install the vzw cm9 (with with invisiblek's boot.img put back into the zip) via this method exactly.
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html
fake cwr works, and everything went fine, but when i try to flash boot_cm9.zip i stay in cwr.
I am using the cwr from this post
http://forum.xda-developers.com/showthread.php?t=1773514
I had started with the twrp from that post, but it didn't recognize my internal sdcard.
So, I don't see why this shouldn't be a doable thing. But something probably needs to be redirected somewhere.
The good news is, I boot into my normal rom without problem.
Click to expand...
Click to collapse
If you follow the steps in this thread, including using these links for your files, it will work without a problem.
I can't comment on why other guides on other sites using other files don't work.....and not really sure how it applies to this thread. Lets try to keep it on topic. If you have issues with the dual booting instructions, you might start a new thread to address that or jump in irc.freednode.net/verizons3 and graciously ask the people for help
When you flash the the CM9 rom built by Invisiblek it will come back out to CWR menu. At that point in the process I realized I hadn't copied the boot.img file into the root of my sd card, so i left it on the CWR menu, popped out the sdcard, copied the boot.img file over (already had the boot_sdcard_boot.img file on the root of sdcard), and popped the sdcard back in, chose advanced->reboot recovery, then followed the steps in this guide, worked perfectly.
silasrye said:
I tried to install the vzw cm9 (with with invisiblek's boot.img put back into the zip) via this method exactly.
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html
fake cwr works, and everything went fine, but when i try to flash boot_cm9.zip i stay in cwr.
I am using the cwr from this post
http://forum.xda-developers.com/showthread.php?t=1773514
I had started with the twrp from that post, but it didn't recognize my internal sdcard.
So, I don't see why this shouldn't be a doable thing. But something probably needs to be redirected somewhere.
The good news is, I boot into my normal rom without problem.
Click to expand...
Click to collapse
You need to add one line to Invisiblek's updater-script that "flashes" the boot.img to the bootloader partition in the multi boot folder. Check out the sprint cm9 install for the line to add.
I have tested dual booting to work perfectly.
is the data not working due to the ril??
suzook said:
is the data not working due to the ril??
Click to expand...
Click to collapse
yes, will update OP once we have working 3G/4G data
as of right now my voice and SMS isn't working while others is.....trying to figure it out
I flashed back to stock, simply because I need to have voice and SMS working. I could deal without 3G/4G data for a little bit and use WiFi, but no SMS/Voice was a deal breaker on my phone. I have to be easily gotten in touch with for work and such. It was fun while it lasted.
Will these same instructions work for the CM10 build that is in the server list?
17akota said:
Will these same instructions work for the CM10 build that is in the server list?
Click to expand...
Click to collapse
No. Different files used, probably a different step or two also. I plan to edit this once CM10 builds are ready for public consumption. These instructions also don't include the automated kexec scripting work done recently that allows your device to cold boot into CM9.
Sent from my SCH-I535 using xda premium
neyenlives said:
No. Different files used, probably a different step or two also. I plan to edit this once CM10 builds are ready for public consumption. These instructions also don't include the automated kexec scripting work done recently that allows your device to cold boot into CM9.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I figured that.
Could you point me in the direction of the new Kexec? I read about it somewhere and would like to try it out.
17akota said:
I figured that.
Could you point me in the direction of the new Kexec? I read about it somewhere and would like to try it out.
Click to expand...
Click to collapse
irc.freenode.net #verizons3
Sent from my SCH-I535 using xda premium
i came from a thunderbolt, and know how different a RIL can be from phone to phone, so i ask this quite seriously...
How different is the RIL from the Gnex to the SGIII?
seang said:
i came from a thunderbolt, and know how different a RIL can be from phone to phone, so i ask this quite seriously...
How different is the RIL from the Gnex to the SGIII?
Click to expand...
Click to collapse
Completely different processors.
Is there anyway to get the TouchWiz Camera on CM9? I really like that camera app.
I tried just putting it in /system/app and changing the permissions to rw-r--r-- and rebooting and nothing
Then i tried just installing it like a normal apk and it failed.
I would love CM9 if i could just get the stock camera app too work.
BTW im using DHacker29's CM9 and its amazing. So much easier to install.
17akota said:
Is there anyway to get the TouchWiz Camera on CM9? I really like that camera app.
I tried just putting it in /system/app and changing the permissions to rw-r--r-- and rebooting and nothing
Then i tried just installing it like a normal apk and it failed.
I would love CM9 if i could just get the stock camera app too work.
BTW im using DHacker29's CM9 and its amazing. So much easier to install.
Click to expand...
Click to collapse
It probably requires touchwiz frame work. It will take significantly more work than just dropping in an apk
Sent from my SCH-I535 using xda premium
DHacker's CM10 is awesome!! I've been running it all day and Jelly Bean is really smooth on the S3.
http://www.droidhive.com/forums/index.php?/files/category/26-sgs3/
Check it out guys.
My phone is rooted (With Super One Click) and when tap the "boot into recovery" option in Rom Manager it just send me to the stock recovery (with Blue text and what not). I have flashed Rom Manager with my Sidekick 4g before I tried to boot into recover. Please, someone help me. The answer is probably right in my face, but my noobish eyes just cant see it. :crying:
Please don't bash me this is my first post. I made sure there wasnt any post like this before i started a new tread.
Don't use ROM Manager with Sidekick 4G as CWM doesn't work the same way. When you reboot you always go into Samsung recovery from where you gotta reinstall packages to 'fake flash' the CWM recovery. If it says permission denied, the recovery file wasn't pushed to /system properly. You gotta reinstall every single time .. till of course you install a custom ROM. I think most come with voodoo CWM which replaces stock recovery, allowing you to go into CWM directly when you go to Recovery.
Firstly you need root, which I'm assuming you already have. Then you have to move a custom recovery to your phone's /system to allow you to install unsigned packages. You can do this using root explorer (paid app, but its the most simple and easy way of doing it) or you can do it using other similar apps that give you R/W (read and write) access. You also need to have a custom recovery file, the update.zip which when you hit reinstall packages (given you pushed the custom recovery file to the phone's system) would bring up clockworkmod recovery.
Read the noob guide here -> link. Its REALLY good and gives you a step by step of how to root / get custom recovery and install custom ROM.
Go here -> link. For more in depth information about getting a custom recovery. And here -> link. for Krylon's recovery files (links on his thread aren't all working).
Edit: Looks like the links on Krylon's page aren't working .. if someone can give an alternative it would be great!
I'm thinking about ODIN my device and start over but this time following one of the guides provided. I got cwm working but now I get a long script of code with a error that saids that it can't mount this and stuff like that. Ill try to post a image to give you a little better look at my problem. And for some reason the cmw logo isn't coming up behind the orange text.
Sent from my SGH-T839 using xda app-developers app
Those guided really helped me out I spent ages reading up different things so when I finally went and did it, I didn't face any problems!
Important notes:
1. Root, obviously I personally didn't use the latest edition of SuperOneClick (at the time) on the website, but the file the dev posted on his XDA Thread.
2. Don't use ROM Manager or any other 'one click' kind of recovery for this phone. You need to download a custom recovery file and update file (links above, thanks Krylon) and go into CWM Recovery through the official Samsung Recovery through reinstalling the custom update file. This is the only way to access Orange CWM. Most custom ROMs come with the Red Voodoo CWM which is permanent in the sense that when you go into recovery, you should go into CWM (Red), instead of having to go through Samsung.
3. Orange CWM (and some say Red CWM as well) has some mounting issues. Always remember to check your mounts such that System, Data (well just to be safe, all of the items in the list) always say UNMOUNT. Basically when its mounted, means CWM has access to the partition. It says UNMOUNT because it is MOUNTED. I know thats a bit confusing, but think of it like this - there is a light switch that says ON so when you press it, turns the lights on but then the writing changes to OFF because you need to push the switch to turn it off. Erm .. hope that helps?! Lol.
4. Basically if your partitions are showing up as MOUNT, means you need to MOUNT them. Otherwise whatever changes you did won't apply! Instead of getting confused like I did, just make sure the screen says UNMOUNT SYSTEM and so forth for the rest of the items on the list.
5. Before installing a custom ROM, I always wiped x 3, before and after. Means after checking mounts, wipe data / dalvik, etc. 3 times. So for me, after checking mounts I would go to wipe date - yes - done 1; wipe data - yes - done 2; wipe data - yes - done 3. Followed by wipe dalvik and whatever else you want to wipe. Then I'd check mounts again (they usually get unmounted after a wipe .. well for me they always have anyway) before installing the ROM. Oh, sometimes I installed the ROM twice. Then I'd check mounts, wipe x 3, check mounts again before finally rebooting and letting it stand still for around 20 minutes or so. I don't really know if there is a logic or if doing it so many times makes a difference but I know some other people have done this and (other than wasting time) it doesn't really do any harm (someone correct me if I'm wrong) so why the hell not? I think the basic reasoning behind double / triple wiping and installing is to make sure that the changes are properly written as sometimes the system still retains old data.
6. Some people have SD card partitioning issues apparent. I can't remember why everyone went around partitioning in the first place (it must have been for some important reason, completely slipped my mind right now .. I personally did it to link my apps / data to SD card and save internal memory / space) but I personally used Gparted to partition my card on a computer (rather than CWM on the phone as I've heard people have issues with this) and never had a problem.
But I think thats it. I know there is a lot of information but its really worth having a look at the guide and other posts on that thread as that and the ROM thread (I personally use GOV 3.2) really had me prepare for any possible issue beforehand so I started off in a position where I could avoid them.
WTF_IsA_Android said:
I'm thinking about ODIN my device and start over but this time following one of the guides provided. I got cwm working but now I get a long script of code with a error that saids that it can't mount this and stuff like that. Ill try to post a image to give you a little better look at my problem. And for some reason the cmw logo isn't coming up behind the orange text.
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
can someone update the sidekick 4g stuff everything is either dead or does not lead anywhere to download any of the required files, thanks.