Database Info

[Q] flashing rom with Quick flash package

- Quick Flash Package: Radio_12.62.60.27_26.13.04.19_M - HTC 3.06.405.1
http://forum.xda-developers.com/showthread.php?t=877295&highlight=radio+thread
Trying to install the above for use with BinDroid. When Im bootloader mode and when its trying to write the radio it says it could't do it. What can I do?
I used the advanced hack toolkit, does this even do RADIO-OFF?
Thanks

mcvigo said:
- Quick Flash Package: Radio_12.62.60.27_26.13.04.19_M - HTC 3.06.405.1
http://forum.xda-developers.com/showthread.php?t=877295&highlight=radio+thread
Trying to install the above for use with BinDroid. When Im bootloader mode and when its trying to write the radio it says it could't do it. What can I do?
I used the advanced hack toolkit, does this even do RADIO-OFF?
Thanks
Click to expand...
Click to collapse
You must rename the downloaded file exactly "PD98IMG.zip". Once you do that, place on the root of your SD card (i.e. put it on the sd card). Once there, boot into bootloader and it should find the file and flash the radio. I cannot stress enough 2 things. You MUST name the file exactly "PD98IMG.zip" or it will not recognize the file. Also, if you have hide extension preference on, you may not need to add the .zip part to the end of the file. If you do add the .zip and it doesn't recognize in hboot, and you have named it exactly "PD98IMG.zip" then delete the .zip part and try again. Secondly, check the md5 number to be sure you didn't download a corrupt file. More times then not its fine but I cannot stress enough that only bad things can happen if you flash a corrupt radio. Lastly, search search search! there are numerous threads, especially in the dev section (1st thread) that details how to flash radios. Below I've added the link, while the radio that you're about to flash is on the DHD forum, the method to flash is still the same in the provided link below. If this has helped you, know where the thanks button is
FOLLOW THESE INSTRUCTIONS!
Edit: Uhm, not sure what you mean by does this do radio off? If you ran the hack kit and you have successfully installed Bindroid, you should be rooted with S-Off, enabling you to flash the radio with the above mentioned method..in bootloader it should say S-off, again though if you have flashed bindroid, you are rooted successfully I would think..

I did what you told me and its not working for some reason. What could this be? Says something like Wrong Image.

Tried flashing Radio with the toolkit too, it goes through the process but radio is the same.... So frustrating.

Stop. You can't just take any file and rename it to PD98IMG and it will magically work. There needs to be a script included to actually run it correctly. Now if you hold on for a while, I made a PD98IMG file for this radio a while ago for someone else. Let me look for it and I will post back.
The hack kit gives you S-OFF. That's all you need to flash a radio PD99IMG file. Also, please post if you have the Inspire or the DHD. Just curious.

thanks, I will wait. What I did was put the file in root, do a restart into bootloader, select hboot then started running saying wrong P98IMG.zip. Tried 3 different methods and no go. I have an inspire 4g from ATT and has the gingerbread stock radio on it. I want a new radio due to horrible battery life. I noticed that it gives me 3.9v instead of 4.2, is this a problem?

Before I post the file, please make sure you delete any other PD98IMG zip files that are on your sd card.

Yeah I know, also what method should I use with your file?

It seems it was the RADIO i was looking the problem. I put in this one,
Radio w/RCDATA: 12.59.60.26P_26.11.04.21_M
MD5 Sum: 57cccef401c372c6d421c986ee42e0fe and flashing worked perfectly. Guess Ill try this one for a while.

Boot into Hboot. You can do this by these methods. First go into your menu settings and it is usually under Power. Make sure the option for Fasboot is unchecked. After this power phone off. After phone is powered off, hold down the volume down key and keep pressing it. While still pressing volume down key press power buttonfor a second or two. You can let go of the volume button as soon as the white Hboot screen shows up. The phone will scan for files and find the PD98IMG file. It will then ask you if you want to update. Press the correct volume key to accept. DO NOT POWER OFF THE PHONE DURING THE UPDATE. It should take less than a minute. Once it is done, press power to reboot. After phone is running, make sure you delete PD98IMG file off of sd card. It will save you a headache if you ever need to go back into Hboot. Link is posted. Before you transfer to sd card, rename the file to exactly "PD98IMG", without the quotes. Just delete the underscore and the ending I added.
http://www.mediafire.com/?rysi497mkxmrh9g
---------- Post added at 10:58 PM ---------- Previous post was at 10:53 PM ----------
If you flash a radio file then make sure you flash the matching RIL file in recovery, not Hboot. In recovery options, go to mounts, mount system, then go back and select the RIL zip file to flash.

thanks alot, will try with the one you posted now. I was able to flash with another radio so it was that one specifically that was bad or w.e.

If you are going to use the ATT 421 radio you just posted, then flash the RIL file in recovery like I described. Flash the matching RIL file in recovery, not Hboot. In recovery options, go to mounts, mount system, then go back and select the RIL zip file to flash. I am posting the RIL for the radio you just listed and for the one I posted, which will end in 4.19.
I am also including a program created by ZikyHD. Install it on your phone. It is an easy way to check and see what radio and RIL you have installed.

ahhh! my apologies!! I thought he pulled the radio file from the same page I did (not the case) holy crap what a bonehead move by me! Wolf good man! I'm using BinDroid too and flashed the recommended radio recently and pulled the file from a different page...glad Wolf got you straightened out..I should have just posted the PD98IMG I had, glad wolf is on his game better then I am. Assumptions are really killing me lately!

It happens, but be careful when messing around with radio files because you can brick your phone if it messes up. To the OP, make sure you check the previous post made by me for additional information and downloads. Also let us know how it worked out. Test any new radio for at least a few days to a week. It needs to settle down. Remember, what works well for some people in their area may not work well for you, and vice versa.

Wolf_2 said:
It happens, but be careful when messing around with radio files because you can brick your phone if it messes up. To the OP, make sure you check the previous post made by me for additional information and downloads. Also let us know how it worked out. Test any new radio for at least a few days to a week. It needs to settle down. Remember, what works well for some people in their area may not work well for you, and vice versa.
Click to expand...
Click to collapse
I always take extreme caution when dealing with radios...and I cannot stress enough how important it is to delete the radio off the SD card..what nightmare that can become if you softbrick or something...not that I learned that the hard way or anything

I tried installing that app to check the RIL, doesn't phone says its not recognized.

mcvigo said:
I tried installing that app to check the RIL, doesn't phone says its not recognized.
Click to expand...
Click to collapse
well at the risk of making myself an ass again, I use terminal commands to check my ril..as far as I know it does work. If you want to take this route, download your favorite terminal app (I use terminal emulator). Open a command windown and type "su" and hit enter. First time it should prompt you to allow superuser permission. Allow it. then type: getprop "gsm.version.ril-impl" and hit enter. It will display the RIL file and hopefully the one you're expecting!

What phone do you have? That should work with most phones. It an Android program. If you are having trouble installing it then try a program like Easy Installer from the market. You can also run terminal commands on your phone or your computer to check the radio/RIL information.
In phone terminal, type the following after typing su and hitting enter:
getprop "gsm.version.ril-imp"
In command prompt, ADB, type the following after adb shell:
getprop "gsm.version.ril-impl"
Edit: Looks like I did not pay attention and refresh the screen. MMM answered the question. To the OP, what phone do you have and I am assuming the radio flash worked.

Thanks alot bro, with your file it was the only way I could this radio to install, tried alot of other methods and it would't work. Thanks alot again.

[TOOL] G2X Cleanup Batch *** WARNING *** WILL FORMAT INTERNAL SD

If you are going to flash and ICS ROM after this tool please make sure to first install a GB then ICS otherwise your SD card will not be accessible. I am trying to find a fix but it has been illusive. This statement will be removed once a fix has been found and OP updated.
Now with CWM Touch!
This method uses NVFLASH to recreate all partitions and formats them, thereby getting rid of the file allocation pointers and hence renders data inaccessible without effort.
Note: I have never seen a file come back to life or its data affect other files without effort on the users part or a temporary glitch once the partitions and pointers have been overwritten. Please post a reply with evidence if you have seen it.
Benefits:
The contents of the zip file can be used to super clean G2X before a new ROM flash. This tool recreates all the partitions in the phone so wipes the pointers to all files (everything). The method it employes has existed from before. The files here will stop short of pushing a ROM, so that you can push your favorite ROM.
Prerequisites:
G2X (Will not work on O2X due to different partition table)
Desire to have a clean install of your favorite ROM
Backup your data
*** WARNING ***​
This tool will wipe both phone internal memory and internal SD card. External SD card content is safe.
Don't say you haven't been warned!
What to do:
Download the attached Zip file.
Take out the battery (assuming you have backed up your data on external SD card, computer or elsewhere), connect the device via USB while holding VOL+ and VOL- together. Don't let go of the volume buttons until the device is recognized.
(I typically leave Device Manager open to see when it shows up in the list under "USB Controllers").
Launch flash.bat, sit back and wait until the process finishes (generally a good idea to open a command prompt, CD to the directory and then run the file).
Unplug, put battery in, reboot into CWM recovery (pushed by this tool) by holding VOL- first, then pressing and holding POWER).
Flash your favorite ROM.
Enjoy!
I made this package because I could not get the bluetooth to work with G2x GB 2.3.3 (and below). The issue was a disconnect problem where both the phone and headset would still think they were connected but in audio would not be routed for a call or media. After this procedure my phone has not had an issue for almost 3 weeks now. I have tried it with two ROMs and 3 different headsets without any issues.
I guess I will not toss this phone after all .
Putting it out there in the hope that it may help others solve some of their issues as well. I suspect bad data stays in places not touched by other methods.
Your comments are most welcome.
[Update]
Klathmon has made an newer version with CWM 5.0.2.8. RP by Klathmon can be found here:
http://forum.xda-developers.com/showpost.php?p=24768294&postcount=66
I have tested the windows version but linux one is untested. Use at your own risk.
[Update]
Now with CWM Touch!
Thanks to everyone who has contributed on this thread with a drive to positive change! You work/comments/suggestions are very much appreciated.
References:
http://forum.xda-developers.com/showthread.php?t=1248644. This link was the inspiration for the current work.
Link to CWM Touch development thread. I took the image posted there: http://rootzwiki.com/topic/22984-recovery-touch-enabled-cwm-5813/
[EDIT] The zip file should be fixed now. Darn work machine does something to the upload.

was just about to flash the new hellfire rom and saw this tool! will try it out and see how things go
edit: yeah corrupt zip on my end too.

The zip file seems to be corrupt. Could you re-upload plz

worked great on my end, no problems.

khanggle said:
worked great on my end, no problems.
Click to expand...
Click to collapse
The real test is how stable your ROM would stay with this method to wipe than any of the other methods.
I guess only time will tell .

wow this method really blaze hellfire much thanks to your( you) & (rom dev)

Ohh I like this. Thank you for sharing .
This thing is faster than nullifier, and I especially like how you don't need to be in CWM to use it. It just seems like doing it in "update mode" would allow better manipulation of the phone's internals.

so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)

dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
He states in OP that it doesn't write anything, therefor doesn't "nullify". It formats and partitions.

dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA

mansa_noob said:
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.

MWBehr said:
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.
Click to expand...
Click to collapse
Done. OP updated to reflect. Thanks for clarifying that. It was not my intention to state that this tool does anything any other does, or does not.
I think we are all trying to do the same thing... get rid of the issues when swapping ROMs like _____. I can't seem to think of a good analogy here .

thanks for clarifying the OP, that makes much more sense
and no i wasnt trying to say you were reinenting the wheel, just trying to understand what your tool is actually doing
and also i do understand that it would take effort to get data off any type of storage device once the partition has been erased. i deal with wiping hard drives in a data center all the time. we use a DOD wipe tool that writes 1s and 0s over a drive a minimum of three full times to eradicate the data
but with this tool doing it outside of CWM, it sounds like it may do a better job of it
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?

dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).

dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
I was thinking the same thing but seems easy enough .. add the cwm img to the dir and edit the .cfg file. Hopefully that should get the new CWM flashed

So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA

mansa_noob said:
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).
Click to expand...
Click to collapse
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
PL0X_Kleiner said:
So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
i think it would be pointless unless you are super paranoid

dodgefan67 said:
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
i think it would be pointless unless you are super paranoid
Click to expand...
Click to collapse
Nobody is twisting any arms here... Use it if you want to, don't if you don't want to.
I saw benefit so posted so that others may benefit as well.
Sent from my LG-P999 using XDA

Ok so question, why are you killing all the data on your internal SD card? Why not just the individual partitions that the phone uses? Your destroying data that don't need to be destroyed before flashing a rom...
Sent from my LG-P999 using xda premium

It does not have to be destroyed. I just haven't had a chance to test without recreating emmc yet.
Next step. Likely tomorrow. Would like to test before release.
Sent from my LG-P999 using XDA
[edit] BTW, I do want to restate that there is some data that needs to be destroyed which is not being taken care of by other methods. I don't believe it is in the emmc, but rather it resides in one of the other partitions. Most methods out there are only working in the /data, /system and /cache domain.
My original problem (bluetooth disconnect) which happens to be a problem for some in the community even now was only completely fixed by this method.

[GUIDE]How to load CM9 on GSIII

**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.

[ROM] Custom Stock Samsung Conquer 4G FC17 Rooted With Tweaks

Since people continue to only download part 1, even though I've explained fully that you MUST download BOTH parts before extracting, I have now added this at the beginning of the post, so hopefully people will actually follow the directions properly. DOWNLOAD BOTH PARTS BEFORE EXTRACTING, IT WILL NOT EXTRACT PROPERLY ONLY DOWNLOADING ONE PART!!!
This is a custom stock ROM for the Samsung Conquer 4G that has many advantages over a completely stock image. It was developed by me, Brien Johnson of XHPCreations aka brienj.
The link to the files for the ROM are at the very end of this post, but I recommend you read the FULL post while downloading the files.
- Your phone will be rooted.
- The complete FC17 update that shouldn't nag you to update to FE16. (may help to delete the FE16 update in the cache if you already had it pushed to your phone)
- Clockword Mod Recovery for making easy backups and restores.
- Completely Deodexed and ZipAligned for better performance or being able to hack further.
- All bloatware removed, i.e. SprintID
- Stock Launcher replaced by ADWLauncher. (the stock Launcher could not be deodexed, but ADWLauncher is much better and more robust)
- Debuggable.
- Custom power menu that includes, reboot, reboot into recovery, and reboot into download. (Currently the reboot into download does not work, will try to get it to work if possible in the future)
- Custom battery icons that show the actual percentage of battery power left.
- ICS Fonts for better appearance of text in phone's menus.
- Memory and network tweaks for best performance and battery savings.
- Support for running scripts on boot in init.d folder. I've included one script to help sdcard performance, feel free to add any more that you want.
- Support for standard bootanimation.zip files.
Along with these tweaks I will give instructions on improving the network performance further and changing the boot sound, as well as give links to useful programs and hacks that can be added on this phone.
I suggest only using this ROM if you have not successfully applied the FE16 OTA Update to your phone. If you have a stock FE16 phone, it MAY still work however. I can not guarantee this ROM will work for you, and I am not liable for any damage to your phone if you try to install this ...
Here are the instructions to install the custom stock ROM on a Samsung Conquer 4G with the FC17 update. It is installed in two parts, the first is if you do not already have Clockwork Mod Recovery installed, in which case follow the Odin instructions. If you have installed the CWMR already from my instructions here - http://forum.xda-developers.com/showthread.php?t=1610534 then go ahead and follow the CWMR instructions.
Odin installation instructions (Use if you do not have CWMR already installed):
To enter Download Mode on the phone, make sure the phone is turned off and plugged into the wall charging. You should also make sure the phone has a good charge on it. Then turn the phone on by pressing the volume down and camera button and holding them while pressing the power button for a few seconds.
Unzip all the files on your computer and follow these steps.
1) Enter download mode on the phone and plug it into your computer.
2) Open up the Odin program in Windows, run as administrator if on a version of Windows that has such a feature, such as Windows 7. Sorry, there is no Odin for Linux based systems that I know about.
3) Press the OPS button and select the SPH-D600_FC17_CWM_XHP1.ops file.
4) Press the PDA button and select the SPH-D600_FC17_CWM_XHP1.tar.md5 file.
5) Press the Start button, the images should install and the phone reboot.
Congrats, your phone now has my Custom FC17 ROM with a CWM Recovery.
CWMR installation instructions (Use if you have CWMR installed):
Unzip all the files on your computer and follow these steps.
1) Copy the clockworkmod folder and merge it with the folder already on your SD Card. If you do not already have that folder on the SD Card, you may not have CWMR already installed, or you've never made a backup before with it.
2) Boot into CWMR by holding the volume down button and the power button while pugged into the wall charger, or by using the adb command "reboot recovery".
3) Select the menu item "backup and restore".
4) Select the menu item "restore".
5) Select the restore named "SPH-D600_FC17_CWM_XHP1".
6) Select the menu item "reboot now".
Congrats, your phone now has my Custom FC17 ROM with a CWM Recovery.
Now that the phone has the custom ROM, here are some things you can add or do to further improve performance on the phone if you wish.
First of all I recommend installing AdFree, Terminal Emulator, Titanium Backup, and if you wish ScriptManager, which can all be found on the Google Play Store. I can help you find them if needed.
For better 3G follow these steps (enter commands into Terminal Emulator or use the adb shell):
Type this command: getprop ril.MSL
It should show your MSL. Write it down.
Open the dialer and dial ##3282##
Enter your MSL
Click on "Others"
Click on "Multimedia"
Change the settings as follows:
RTSP Proxy Address: 0.0.0.0
RTSP Proxy Port: 0
HTTPPD Proxy Address: 0.0.0.0
HTTPPD Proxy Port: 0
The stock settings are:
RTSP Proxy Address: rtsp.vog.sprintpcs.com
RTSP Proxy Port: 554
HTTPPD Proxy Address: pd.vog.sprintpcs.com
HTTPPD Proxy Port: 8085
Here is how to change the boot sound:
First of all get the "poweron.snd" file from the /system/etc/ folder. It is a raw sound file which can be opened in any audio editor, such as Cool Edit Pro.
Here are the settings to select when opening it up in Cool Edit Pro for example:
Sampling Rate: 441000
Channels: Stereo
Resolution: 16-bit
Data Formatted As: 16-bit Intel PCM
Offset Input Data By: 0
Now you can listen to the boot sound in the audio editor. You can change it to your liking and save it in the same format. Remember to keep it a RAW audio file with the settings above. Replace the "poweron.snd" file with your edited audio file, retaining the same filename.
To replace the boot animation, you can find the "bootanimation.zip" file in the /system/media/ folder. Replace it with a bootanimation file of your liking. I've included a custom bootanimation that was modified to match the custom boot logo I made. I made all of it from a popular bootanimation of which I can not remember where I found it. I am not taking any credit for the original bootanimation, I just modified it to say Samsung Conquer 4G at the top and to speed up and spin faster at the end. If anyone remembers the original creator, I will add a link to it.
A great cpu tuning program that works on the phone (although won't save settings on boot for some reason), is this - http://forum.xda-developers.com/showthread.php?t=1584508. From the screenshots below you can see that the phone will last almost 3 days without this program, although the other screenshot was using the program setting of PowerSave and after 20 1/2 hours it was still at 70%, but I also didn't use the phone, I just had it locked. However, when running in PowerSave mode, the phone will be very sluggish, so is only to use if you are just waiting for phone calls or just texting.
These are all the tweaks I have for now. I hope you enjoy the ROM.
I hate to bring this up, but if you like this ROM, please consider making a donation. I don't do this just for donations, I enjoy helping everyone out, but I was in a near fatal accident over two years ago and can no longer work. If you find yourself enjoying this ROM, please click on the Donate button under my name, I would really appreciate it. I can try to improve the ROM over time, but please remember that this ROM is strictly made for performance and battery life and to give you more control over your phone. I don't plan on doing any theming, and most people do ICS themes and such. Personally I hate the look of the ICS themes and the only thing I've taken from ICS, is the fonts, which I do like and look much better than the original. If you want some fancy theme, or mods like Beats Audio, I'd suggest looking for another ROM. If you want performance and longer battery life, I think you'll enjoy mine.
Take care and thank you for trying my ROM.
You must download BOTH of these files before you can extract them. After downloading them, put them both in the same folder, and open the part1.rar file up, and you can then extract the files properly. If you only download one of the two files, the files will be corrupted or not work:
Here is the link to the first file of the ROM - SPH-D600_FC17_CWM_XHP1.part1.rar
Here is the link to the second file of the ROM - SPH-D600_FC17_CWM_XHP1.part2.rar
I apologize for having to split it into two files, but I have a maximum of 200MB I can upload, as I don't have a premium account at MediaFire.

Dude, your awesome.
So glad to see this!
bring on the flock of desperate Conquer users.
This is John Smith from Ting forums by the way.
Good job man. Gonna download asap.

DiehlC said:
Dude, your awesome.
So glad to see this!
bring on the flock of desperate Conquer users.
This is John Smith from Ting forums by the way.
Good job man. Gonna download asap.
Click to expand...
Click to collapse
Cool. I hope it works great for you.
You were able to install my other one, so you have CWMR already, right? If so, I recommend just updating that way as it's of course much easier.

Thanks for your hard work, looks great...

brienj said:
Cool. I hope it works great for you.
You were able to install my other one, so you have CWMR already, right? If so, I recommend just updating that way as it's of course much easier.
Click to expand...
Click to collapse
Sure do, so yup thats my plan.
What do you think about "Mobile Odin" Would it also work for flashing this? for information sake atleast.

DiehlC said:
Sure do, so yup thats my plan.
What do you think about "Mobile Odin" Would it also work for flashing this? for information sake atleast.
Click to expand...
Click to collapse
It probably would. Perhaps it uses the flash_image binary to flash the images properly, but I don't know for sure. You'd have to make sure you give it the correct names of the mtd partitions though, or it would know the correct names for them, but that's if it uses the flash_image binary. You can always flash these yourself with the flash_image binary using the mtd table I listed. If you have CWMR though, I'd just do it that way.
It doesn't list our phone in the compatible phones, which leads me to believe it only knows the partition tables for the phones listed. Perhaps if you gave them our partition table, they could make it work though.

john9 said:
Thanks for your hard work, looks great...
Click to expand...
Click to collapse
You're welcome. Hard work is an understatement though. When I had my accident, my head was split wide open from being struck. As a result, I have serious brain damage, although I have retained most of the smarts I had before the accident, which helps. However, it takes me months to do something like this, whereas before it would have taken maybe a week or two at the most, heck, probably a couple of days to be honest. I can not concentrate, I have to do one thing at a time, and I always forget things, even something that happened a few minutes ago. This is why I can not even work, as I can not be in a competitive work environment. Heck, even posting a post will take me close to 5 or 10 minutes, from fixing all the transposed letters, double-printing of letters, grammar, etc. The first post of the thread took me about 3 hours to finish and completely type up. It may appear from my posts, that I am smart, which I don't want to brag, but I believe I am, but because of my TBI, it's not what it appears to be, as you only see the final result after all my editing. I used to hide my problem, but I am not ashamed to admit it any more.

Thanks man this is really fast. I did a test and left my phone locked and it started out at 64 than 2 hours later it was 61!! Really good battery life.
Sent from my SPH-D600 using xda premium

Came here from the Ting forums. I just had to remember my username I created way back when I still had an XV6800. Those were the days!
Anyway, I tried downloading part 2 a few times, and every time I extract the files, it tells me the md5 file is broken. Anyone else having this issue?

bradyarz said:
Came here from the Ting forums. I just had to remember my username I created way back when I still had an XV6800. Those were the days!
Anyway, I tried downloading part 2 a few times, and every time I extract the files, it tells me the md5 file is broken. Anyone else having this issue?
Click to expand...
Click to collapse
You have to have part 1 and part 2 in the same folder, then open part1. It is a two part rar file, so uses both files. By opening just the second file, it won't all be there. But both files contain the whole package, you just need to open part 1, as long as you have part 2 as well.
I had to split the rar file up because Mediafire only allows me to upload a maximum filesize of 200MB, since I don't have a premium account. I've updated this info right before the download links.
itzdarockz said:
Thanks man this is really fast. I did a test and left my phone locked and it started out at 64 than 2 hours later it was 61!! Really good battery life.
Sent from my SPH-D600 using xda premium
Click to expand...
Click to collapse
Well that's great to hear it works ok for you and yes, the battery life, even without the cpu tuner program is FAR better than original. At least it has been for me. I can run an intensive program with WiFi and the phone would still last close to 10 - 12 hours. That was the whole goal of my ROM, was for longer battery life, since it sucks when stock, and I think I succeeded at it.

brienj said:
You have to have part 1 and part 2 in the same folder, then open part1. It is a two part rar file, so uses both files. By opening just the second file, it won't all be there. But both files contain the whole package, you just need to open part 1, as long as you have part 2 as well.
I had to split the rar file up because Mediafire only allows me to upload a maximum filesize of 200MB, since I don't have a premium account. I've updated this info right before the download links.
Click to expand...
Click to collapse
Ok, thanks. I was just a little worried because part 1 extracted fine, and part 2 always gave me an error, giving me the part 2 md5 as a 0 byte file.
I've never rooted through android before, so I want to make sure I've got everything squared away before I begin.

brienj said:
You have to have part 1 and part 2 in the same folder, then open part1. It is a two part rar file, so uses both files. By opening just the second file, it won't all be there. But both files contain the whole package, you just need to open part 1, as long as you have part 2 as well.
I had to split the rar file up because Mediafire only allows me to upload a maximum filesize of 200MB, since I don't have a premium account. I've updated this info right before the download links.
Well that's great to hear it works ok for you and yes, the battery life, even without the cpu tuner program is FAR better than original. At least it has been for me. I can run an intensive program with WiFi and the phone would still last close to 10 - 12 hours. That was the whole goal of my ROM, was for longer battery life, since it sucks when stock, and I think I succeeded at it.
Click to expand...
Click to collapse
Good to hear you are no longer ashamed, plus theres no reason to be. Especially since you can whip up great stuff like this. among other things youve done.
I havent flashed it yet, as I am backing up a lot of stuff, and trying to backup all the linux stuff I installed via opkg package manager using "BotBrew", which is getting a bit complicated. Plus I have to make a nand too beforehand.
So I should be able to get to it soon. Im excited.
But by the way, now that you have the Partitioning table layout mapped out, I wonder what we could do to further expand our internal memory/storage? I wonder if we could double partition our SD cards like some others do on other devices? They basically just format their SD with FAT32 in the first (which will be the extended internal), and the next being Ext4 for SD card storage. Seems like we should be able to do the same like anyone else, especially since you got that nice bit of info through your troubles, on the partitioning.
What do you think on this position?
Take care Brien.

DiehlC said:
Good to hear you are no longer ashamed, plus theres no reason to be. Especially since you can whip up great stuff like this. among other things youve done.
I havent flashed it yet, as I am backing up a lot of stuff, and trying to backup all the linux stuff I installed via opkg package manager using "BotBrew", which is getting a bit complicated. Plus I have to make a nand too beforehand.
So I should be able to get to it soon. Im excited.
But by the way, now that you have the Partitioning table layout mapped out, I wonder what we could do to further expand our internal memory/storage? I wonder if we could double partition our SD cards like some others do on other devices? They basically just format their SD with FAT32 in the first (which will be the extended internal), and the next being Ext4 for SD card storage. Seems like we should be able to do the same like anyone else, especially since you got that nice bit of info through your troubles, on the partitioning.
What do you think on this position?
Take care Brien.
Click to expand...
Click to collapse
I am "new" to doing all of this type of work. I used to strictly do game hacking/modding, not stuff to cheat, but to make the games better and more fun. Late last year I started getting into the Android systems and seeing what I could do. I'm sure if I looked into this stuff I could figure something out eventually, but not sure how long it would really take me. This seems like something that is similar between all phones, so maybe you should see what can be done already. If it's a phone specific thing, then one of us will have to do the dirty work. I just don't know.

i got an md5 mismatch error when trying to do the restore

New2ThaDroid said:
i got an md5 mismatch error when trying to do the restore
Click to expand...
Click to collapse
I've had that happen before. Here is the solution, but I'd try recopying it to your sdcard another time to make sure it was copied correctly - http://forum.xda-developers.com/showthread.php?t=714114
Also, are you sure you downloaded BOTH of the rar files as I said in the OP, and it did not give you any errors when extracting the files?
Also, try renaming the name of the folder to only include alphanumeric symbols.

I got an error when extracting the files too. I extracted both the files to the same folder so I don't know what the problem is and I extracted the first part first and the the second. I don't know what it is

I got it to work and the Rom on my phone. Looks good! Good job. I would like to add some themes if anyone has some or knows how I could do it myself.
Sent from my SPH-D600 using xda premium

how long
brien how long does it take the your rom to install itself using odin approximately? i ask because it took me over 40 minutes to install it and its at time of this still going

I'm going to do some themeing using UOT Kitchen
Sent from my SPH-D600 using xda premium

New2ThaDroid said:
I'm going to do some themeing using UOT Kitchen
Sent from my SPH-D600 using xda premium
Click to expand...
Click to collapse
Sure, if that's what you want. Like I said in my original post, this ROM was made to be practical, not to be fancy. It does have the ICS fonts in it, which look a bit nicer though.

[DEV][RECOVERY]CWM Touch 6.0.2.7 for OT-995 [2013-01-09]

Should be working fine but it's thoroughly untested so expect errors at some point.
It's for cyanogenmod installations where /custpack is mounted to /system/app, if there is a request i'll make a version that mounts /custpack to /custpack but for now this is it.
I take no responsibility for what this will do to your phone, it's entirely possible that it will kill your phone and even cause a rift in the space time continuum which will kill us all.
Anyway, here it is, flashable via fastboot as usual, if it goes to stable i'll make an installer for it to install via CWM.
For those not comfortable with flashing via fastboot or who don't have access to a computer at this time, use flash_image via terminal, it should work fine.
Latest version:
cwm_touch_cocktail_6.0.2.7-testing-V2.img
MD5: feb35010a527de42c6c68d6987b939e1
Old versions (kept but not recommended):
cwm_touch_cocktail_6.0.2.7-testing.img
MD5: da314f6eb6429bc3530539d8a0e9e20a

Changelog:
2013-01-09
* Fixed buttons, you can now scroll, select and go back using the buttons.
* Fixed backup, /custpack is now linked to /system/app, this should also make it compatible with older roms. (Remember, this is still testing)
* Added mountpoint for /sd-ext to fix nandroid backups for A2SD/S2E/Links2SD installed apps.
* Fixed some glitches and updated kernel code.
2013-01-08
* initial release

Just flashed it to my mobile and thus far it looks promising. Currently I am not planning to change my rom yet so I haven't confirmed if it is able to flash a rom I only saw it boot.
A little thing I noticed though.
When CWM boots and you are in the main menu the menu fills around 80% of the screen. But when you go to another menu lets say flash something from SDCard it only fills up 50% of the screen and you have to scroll a lot to reach the bottom.
Also the buttons are not working at all?
When you press some of the buttons it starts doing weird stuff..
It seems like the volume buttons and the power button work currectly but the buttons at the bottom of the screen are weird.

Hylix said:
Just flashed it to my mobile and thus far it looks promising. Currently I am not planning to change my rom yet so I haven't confirmed if it is able to flash a rom I only saw it boot.
A little thing I noticed though.
When CWM boots and you are in the main menu the menu fills around 80% of the screen. But when you go to another menu lets say flash something from SDCard it only fills up 50% of the screen and you have to scroll a lot to reach the bottom.
Also the buttons are not working at all?
When you press some of the buttons it starts doing weird stuff..
It seems like the volume buttons and the power button work currectly but the buttons at the bottom of the screen are weird.
Click to expand...
Click to collapse
I had completely forgotten about the bottom buttons TBH, i'll fix that in a future version.
Regarding the screen space, it's not much i can do about that ATM but i'll keep it in mind when and if it gets to stable.

Awesome looking good so far

Really cool. Just point and I'll help test.

Downloading and testing.
With this we can backup and restore CM/PA/PAC roms right?

Mrwargod said:
Downloading and testing.
With this we can backup and restore CM/PA/PAC roms right?
Click to expand...
Click to collapse
If you mount /system/app in mounts and storage it should work just fine.
I'm probably going to write a script and put it in the place of the nandroid/nanddump/nandwrite files so /system/app is mounted before the backup/restore is written.
Just added some stuff to it, partitioning sdcard and support for sd-ext (and swap).
Should work well with an init.d script and s2e for those interested in larger storage for apps.
(simple script to mount /dev/mmcblk1p2 to /sd-ext would work)

tumaini418 said:
Really cool. Just point and I'll help test.
Click to expand...
Click to collapse
Would be great it you have the opportunity.

When i use key test section, its dont back main screen and i need unplug battery.
You did great job thanks a lot...

master' said:
When i use key test section, its dont back main screen and i need unplug battery.
You did great job thanks a lot...
Click to expand...
Click to collapse
You are welcome.

Jinxxed said:
If you mount /system/app in mounts and storage it should work just fine.
I'm probably going to write a script and put it in the place of the nandroid/nanddump/nandwrite files so /system/app is mounted before the backup/restore is written.
Just added some stuff to it, partitioning sdcard and support for sd-ext (and swap).
Should work well with an init.d script and s2e for those interested in larger storage for apps.
(simple script to mount /dev/mmcblk1p2 to /sd-ext would work)
Click to expand...
Click to collapse
Yes, having that automated would be great. If i could backup/restore/install zip's all in one CWM that would be awssome and render it definitivelly daily usable. And way easyer for me to test more roms without the concern in loosing my previous rom.

Mrwargod said:
Yes, having that automated would be great. If i could backup/restore/install zip's all in one CWM that would be awssome and render it definitivelly daily usable. And way easyer for me to test more roms without the concern in loosing my previous rom.
Click to expand...
Click to collapse
Should work fine now, to check if it is, analyze the content of your /sdcard/clockworkmod folder.

Already on it to try the latest version of PAC.
I'll feed you on how it went.
---------- Post added at 11:39 AM ---------- Previous post was at 11:18 AM ----------
The link is dead Jinxxed, or is it still uploading?

Mrwargod said:
Already on it to try the latest version of PAC.
I'll feed you on how it went.
---------- Post added at 11:39 AM ---------- Previous post was at 11:18 AM ----------
The link is dead Jinxxed, or is it still uploading?
Click to expand...
Click to collapse
I mistyped the link. :silly: It's fixed now.
Sorry about that.

Yeah, i had already figured out the correct link anyway.
Thanks, testing!

Wipe battery stats is missing in advanced menu.
Backup / Restore - Not working properly - Some of my apps got lost in restore, namedelly all the gapps, some launchers (holoHD), some file explorers (root file explorer), google account, . . .
Flash zip - ROM flashed ok but gapps didn't flashed, neither did an aditional mod.
But it's really looking really good. And the hardware buttons are fixed.
Keep up the good work.

Mrwargod said:
Wipe battery stats is missing in advanced menu.
Backup / Restore - Not working properly - Some of my apps got lost in restore, namedelly all the gapps, some launchers (holoHD), some file explorers (root file explorer), google account, . . .
Flash zip - ROM flashed ok but gapps didn't flashed, neither did an aditional mod.
But it's really looking really good. And the hardware buttons are fixed.
Keep up the good work.
Click to expand...
Click to collapse
Thank you.
It's a weird result since that means that the backup has problems with both /data and /system/app (i assume since google account and launchers not installed via CWM are stored on /data). It really should be all or nothing, one would think...
There is a problem with mounting /system/app for some reason, that's why gapps isn't installed properly, i'll look into it.
It should be easy enough to fix though, expect a new version within the next couple of days.

Will post the same post here as in Benetnath his PAC rom cause maybe it has something to do with CWM?
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Just ran against a problem with doing the PAC update.
All my gapps seem to be broken and some apps crash on start up.
I had the first PAC rom running and flashed the newest over it while clearing my cache (tried flashing the gapps after this but still didn't fix it)
After this I did a complete reset and flashed it and now it seems to work.
Don't know if its the ROM or if its the new touch CWM which is still in testing..
NOTE: It seems like other people succeeded in flashing the updated rom over the previous rom.
I am not the only one with this problem and it seems like there are other people who have the same problem with the other CWM so ignore this all

trying to flash image in terminal in phone. i keep getting "error scanning partitionsfailed with error: -1
??????????
anyone?
nevermind i went ahead and did it the way i know how.
2nd Edit: just did a backup and restore. Seems to have worked fine.
I couldn't mount usb though.
Great work man. Between you and Benetnath we should be cooking with gas soon.
Thanks jinxxed.