Related
Myself and apparently many others like the AOSP apps better than the sense apps. I find the interface for the AOSP messaging, calendar, browser, calculator, and dialer/contacts applications to be more attractive and in some cases more usable. I really liked Bugless Beast 0.4 since it featured these applications, but I have had a hard time with the bug that keeps disk drive from working, and there are various reports of some syncing and battery issues. The EVO-NonSense series has been great too, but I use HDMI out sometimes and like having some of the sense stuff installed. Big thanks to both BuglessPete and tjohnsonjr for their AOSP work.
(7/18/2010) I have attached some of the files I have been using, see descriptions at the bottom of the post.
So since it took a little digging for me to figure out how to do this (even though to advanced users this is easy) I thought it might come in handy for other new users. Additionally I'm hoping by posting this someone can help me figure out how to get the dialer/contacts stuff working, I have the others working fine.
I've done the below on DamageControl, and I think another (baked snack maybe, can't remember). I'll probably throw together an update.zip that can patch these in place later, but I'd rather get the dialer/contacts part figure out first.
Setup:
1. You will need a fully rooted (toast root part 2, NAND unlocked) phone, and adb up and running. There are several explanations for both parts, but the ones listed in the "useful threads" sticky are joeykrim's for adb and toast's part 1 and part 2 for root.
2. I have been using the apk's from BuglessPete's bugless beast 0.4 ROM. The thread for it is available here.
Once you unzip the file, you will find the needed apks in the /system/app folder.
Note: Please donate to pete, he doesn't even have an EVO yet and is doing some great work. Hopefully if he has a phone to work on he can get some of these small bugs squashed and keep the development for BB going.
3. Backup your phone. If you don't know how to reboot into recovery and restore from a nandroid backup, you do not want to do this yet, especially if you want to try help me figure out how to get the dialer running. The idea with the dialer is to try different things until something works. In all likelihood you will hit a point where things are FCing so much you can't do anything. You will almost certainly need to restore from a Nandroid backup at some point.
Important: More than likely anything I list here can't break a phone in a way that a nandroid restore won't fix, but I can not and will not be accountable for any problems with your phone.
Which files:
One nice thing about adding files this way is you can pick and choose what to use. If you like the stock messaging but want the AOSP calendar, you can do just that.
Calculator: Calculator.apk
Calendar: CalendarProvider.apk and Calendar.apk
Default "Navigator" application: CarDock.apk <- you can keep both
Internet: Browser.apk and HTMLViewer.apk <- doesn't show previews of each tab, but allows up to 8 instead of 4. There may be other functionality gained or lost, I dunno.
Clock: DeskClock.apk (can exist beside HTC clock, and can be installed without this procedure)
Messaging (SMS, Text): Mms.apk <- Many people have trouble with this one.
####### Not Working! See post #2 ########
# Phone: Phone.apk, ContactsProvider.apk, Contacts.apk
###################################
To install:
I think you can use adb to do this install with the files still on the computer, but I go ahead and throw all the needed apks onto my sdcard, typically in a folder. Also, if you need to be in the Android SDK's /tools directory to use adb (this depends on your configuration) do that. Connect your phone, and make sure it is in "Charge Only" so the sdcard stays mounted. To make sure adb sees the phone properly issue:
Code:
adb devices
and you should get a return listing the device ID. If so we will mount the /system partition as read-write:
Code:
adb remount
Log into the phones local shell:
Code:
adb shell
you are now on the phones command line and file system, not on your local machine. Now we can start installing files. I'll use Calculator in this example, and I have the apk in a folder on the sdcard called AOSP_apks:
Code:
install /sdcard/AOSP_apks/Calculator.apk /system/app
You can do a couple at a time, and you must do more than one at a time when installing a provider like CalendarProvider.apk and Calendar.apk.
Once you are done, exit the phone's shell, and reboot the phone:
Code:
exit
adb reboot
The change may show up immediately, but the phone and applications aren't designed to change these core functions on the fly, so make sure to reboot the phone. Once it reboots you will probably notice the AOSP icon has replaced the former, and you have the AOSP skin and/or functionality.
Post #2 will deal with progress so far on the dialer/contacts.
(added 7/17) Notes on different apks: The BB Launcher2.apk has his skin on the google search widget, or grab the apk from something else like DC for stock. Launcher.apk from BB is the one with the wide drawer and (I think) 9 screens.
Music.apk from DC is the modded music app from Cyanogen. It has some very nice UI tweaks.
Attached:
- Music.apk used in Cyanogenmod from DC
- Calendar, CalendarProvider, Browser and HTMLViewer from BB 0.4
- CarDock, Calculator, and MMS from AOSP EVO-NonSense
Contacts/Dialer Progress: I'm sure some of the more advanced developers know the answer to this, so ideally someone can fill me in. In the meantime I'll report my findings here, and if others can add feedback to the thread on what they have done, I'll update this post. Hopefully in the long run there will be a straightforward explanation for this I can add to the above post.
I have installed the three files listed above (ContactsProvider.apk, Contacts.apk, and Phone.apk) which seems to install the right bits, but I get FCs.
Later on I added Telephony.apk and FutureDialService.apk, which didn't improve anything. Finally I noticed that Bugless Beast didn't have HTCDialer.apk, so I removed that as well. I think this was the point things went from the dialer and contacts applications FCing to non-stop FCs that kept me from doing anything on the phone.
Attached are the three apps I'm sure are involved for the Contacts/Dialer, pulled from tjohnsonjr's AOSP EVO. More files may be needed, but I'm still trying to figure out which.
The Dialer/Contacts apk used to work, I believe on ROMs that are not based off the newest OTA. Since it worked for me, but stopped once I started using ROMs based of the newest OTA. Anyways great post.
I installed the files and I cant see them. They're in the folders but its like they're hidden from the OS.
I tried to do this before since I love BB but the wake bug in v4 was killing me. I always got install errors. Did you delete the Mms.apk first.. THEN install Mms.apk and reboot? Or did you just install over it? I got errors either way. Also it totally disabled texting on my phone even after reinstalling the HTC Mms.apk.
I had to clean cache/reset then reflash my Nand backup and even then my texting was still broken until I sent one to my wife and then magically I got the 10-15 test "texts" I had sent.
RikusHaven said:
The Dialer/Contacts apk used to work, I believe on ROMs that are not based off the newest OTA. Since it worked for me, but stopped once I started using ROMs based of the newest OTA. Anyways great post.
Click to expand...
Click to collapse
Thanks and thanks. This is interesting. Of course BB is based on the older ROM, so maybe that is why BB works but this doesn't. I'll have to grab an older ROM and try that. It may be an issue of grabbing a newer build of the dialer or something.
warmachine69 said:
I installed the files and I cant see them. They're in the folders but its like they're hidden from the OS.
Click to expand...
Click to collapse
Did it overwrite the existing files? Or do you totally not have whatever you installed, AOSP or sense? Which ROM and version?
MikeBrWade said:
I tried to do this before since I love BB but the wake bug in v4 was killing me. I always got install errors. Did you delete the Mms.apk first.. THEN install Mms.apk and reboot? Or did you just install over it? I got errors either way. Also it totally disabled texting on my phone even after reinstalling the HTC Mms.apk.
I had to clean cache/reset then reflash my Nand backup and even then my texting was still broken until I sent one to my wife and then magically I got the 10-15 test "texts" I had sent.
Click to expand...
Click to collapse
Were you able to successfully do the adb remount first? The way I did it just overwrote the existing Mms.apk.
Also what ROM and version are you running?
laydros said:
Thanks and thanks. This is interesting. Of course BB is based on the older ROM, so maybe that is why BB works but this doesn't. I'll have to grab an older ROM and try that. It may be an issue of grabbing a newer build of the dialer or something.
Did it overwrite the existing files? Or do you totally not have whatever you installed, AOSP or sense? Which ROM and version?
Were you able to successfully do the adb remount first? The way I did it just overwrote the existing Mms.apk.
Also what ROM and version are you running?
Click to expand...
Click to collapse
BBv3 and yes the remount worked.. I am currently in my 84th hour of a long battery duration test so I can't plug it in and try it right now since it will wipe my stats. However it would give some "parse" error and then fail to install. If I forced it by just cp'ing the apk and chmod'ing the exec permissions it would fail horribly.
84th hour of a battery duration test? details please?
MikeBrWade said:
BBv3 and yes the remount worked.. I am currently in my 84th hour of a long battery duration test so I can't plug it in and try it right now since it will wipe my stats. However it would give some "parse" error and then fail to install. If I forced it by just cp'ing the apk and chmod'ing the exec permissions it would fail horribly.
Click to expand...
Click to collapse
Was it something like
Code:
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
If so, I had the same error when I didn't have the /system partition fully mounted as read-write. Did you get any errors from the "adb remount" command?
davebu said:
84th hour of a battery duration test? details please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=7154719&postcount=993
This is my post talking about it.. I am on hour ~91 of the test.. still running with 8% battery left... BBv3 rocks!
laydros said:
Was it something like
Code:
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
If so, I had the same error when I didn't have the /system partition fully mounted as read-write. Did you get any errors from the "adb remount" command?
Click to expand...
Click to collapse
Hmmm maybe I did and didn't notice it.. I am down to 8% right now so by mid day my battery will probably die. I am hoping to make the 100Hr on one charge mark, after that I will try again and note any errors.
MikeBrWade said:
Hmmm maybe I did and didn't notice it.. I am down to 8% right now so by mid day my battery will probably die. I am hoping to make the 100Hr on one charge mark, after that I will try again and note any errors.
Click to expand...
Click to collapse
ok so I just redid your steps and I didn't get the error code this time (maybe my remount didn't work the last time I tried it). But now I get FC everytime I try and launch the text app. I installed over the Htc mms.apk =(
Anyone got an HTC Mms.apk handy they can post so I don't have to restore nand?
If you have the AOSP apps available, could you please post them all in .zip folder in the OP?
MikeBrWade said:
ok so I just redid your steps and I didn't get the error code this time (maybe my remount didn't work the last time I tried it). But now I get FC everytime I try and launch the text app. I installed over the Htc mms.apk =(
Anyone got an HTC Mms.apk handy they can post so I don't have to restore nand?
Click to expand...
Click to collapse
NVM I extracted it from an old nand backup. So, for me at least the Mms.apk from AOSP causes FCs and won't run at all . Put the HTC Mms.apk back and it works fine. =( Urgh any hints?
edited to add the HTC Mms.apk incase someone does what I did and kills it, so they dont' have to go through the process of trying to extract it.
MikeBrWade said:
NVM I extracted it from an old nand backup. So, for me at least the Mms.apk from AOSP causes FCs and won't. Put the HTC Mms.apk back and it works fine. =( Urgh any hints?
edited to add the HTC Mms.apk incase someone does what I did and kills it, so they dont' have to go through the process of trying to extract it.
Click to expand...
Click to collapse
The only issues I've had with the AOSP Mms.apk was the lack of actual mms functionality.
thanks for the apk so I could go back
I[E said:
The only issues I've had with the AOSP Mms.apk was the lack of actual mms functionality.
thanks for the apk so I could go back
Click to expand...
Click to collapse
Interesting that you say that, since I had some MMS texts in my cache. Wondering if when the AOSP version couldn't deal with them so it just FC'ed instead.
So I tried that, deleting ALL my texts so it wouldn't have some MMS collision or something. But that didn't work either, HTC Mms.apk works fine.. the AOSP.apk FC's. Could the OP or something with a working AOSP Mms.apk post it maybe it's my copy. Mine has an MD5 of : 441e3b8863bc3ab88ce6ad9bc1671f22
I have mms messages in my cache too. The AOSP apk shows them fine, just can't send new mms messages. Maybe your file is corrupt?
Sent from my PC36100 using XDA App
I going to upload all the AOSP apks that I include in my ROMs when I get home tonight.
Can you tell us how you got contacts.apk to work? I'm trying with FreshRom and I pulled the Contacts.apk from your Rom and it won't recognize the file when I push it using adbshell. The file is in the app folder but android ignores it.
I[E said:
I have mms messages in my cache too. The AOSP apk shows them fine, just can't send new mms messages. Maybe your file is corrupt?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Does does your md5 match mine?
I decided that I didnt like the default CircleBattery in the TPC v3 ROM, so I set out to change it to one i liked better. This would be it. I also hated that the vibrate icon on the status bar was always on. I made it go away. My phone is on vibrate in both the attached screenshots.
THIS HAS ONLY BEEN TESTED ON TPC v3
It may work on other ROMs, but FLASH AT YOUR OWN RISK.
At the very least, you should be on a deodexed ROM! Otherwise funky things WILL happen!
Removing the Vibrate icon SHOULD work on most ROMs, but i have never tried it and have no information telling me either way. The battery mod may work on most Rogers-based rom, but it will almost definitely mess with other things in ROM. I would not install recommend installing it on a different ROM.
How to install
Using flashable zips:
Code:
[LIST=1]
[*]Backup current rom, just in case
[*]Download the zip file you want to flash (attached below)
[*]Flash in CWM recovery
[*]clear dalvik cache
[*]reboot system, wait for long reboot (system is rebuilding dalvik cache, every boot afterwards will be back to normal speeds)
[/LIST]
With adb:
For the Battery Mod:
Code:
[LIST=1]
[*]Create a backup of your current Framework-res.apk
[LIST][*]either make a nandroid or "adb pull /system/framework/framework-res.apk"[/LIST]
[*]Download the attached framework-res.apk
[*]reboot your phone into recovery
[LIST][*]either in terminal enter "reboot recovery" or use "adb reboot recovery"
[*]this MAY not need to be done, but i have never tried it any other way. better safe than sorry[/LIST]
[*]on your phone in recovery, mount the system partition
[LIST][*]mounts and storage > mount /system[/LIST]
[*]on your pc, enter this command, replacing [DOWNLOAD PATH] with the path to where ever you downloaded the framework-res.apk
[LIST][*]adb push [DOWNLOAD PATH]/framework-res.apk /system/framework
[*]there is a space between the .apk and /system
[/LIST]
[*]Clear your dalvik cache and fix permissions
[LIST][*]advanced > clear dalvik cache
[*]advanced > fix permissions
[*]again, this may not need to be done, but i have never tested it without doing it[/LIST]
[*]reboot your phone
[LIST][*]this will take a long time, as your phone is rebuilding the dalvik cache.
[*]each boot after the first will be much faster[/LIST][/LIST]
For the No Vibrate icon
Code:
[LIST=1]
[*]Create a backup of your current SystemUI.apk
[LIST][*]either make a nandroid or "adb pull /system/app/SystemUI.apk"[/LIST]
[*]Download the attached SystemUI.apk
[*]reboot your phone into recovery
[LIST][*]either in terminal enter "reboot recovery" or use "adb reboot recovery"
[*]this MAY not need to be done, but i have never tried it any other way. better safe than sorry[/LIST]
[*]on your phone in recovery, mount the system partition
[LIST][*]mounts and storage > mount /system[/LIST]
[*]on your pc, enter this command, replacing [DOWNLOAD PATH] with the path to where ever you downloaded the SystemUI.apk
[LIST][*]adb push [DOWNLOAD PATH]/SystemUI.apk /system/app
[*]there is a space between the .apk and /system
[/LIST]
[*]Clear your dalvik cache and fix permissions
[LIST][*]advanced > clear dalvik cache
[*]advanced > fix permissions
[*]again, this may not need to be done, but i have never tested it without doing it[/LIST]
[*]reboot your phone
[LIST][*]this will take a long time, as your phone is rebuilding the dalvik cache.
[*]each boot after the first will be much faster[/LIST][/LIST]
These can both be done at the same time if you want to save time and use both. Steps 1, 2, and 5 should be done at the same time, and it doesnt matter which order.
Enjoy!
Great job, but a flashable zip would be so much easier.
True... Well I created flashable zips. only problem is I'm not sure if they work. I tested all of them, they all flash and my phone is still completely usable, so I dont think they are dangerous. But, since my phone already had these installed, I cant tell if they actually changed anything. If someone could test this, it would be quite awesome. Dont want to put it on the main post if it doesnt actually work.
Thanks,
I tested BatteryMod and NoVibrate.zip and it work like a charm,
Great job.
The battery was not exactly my taste then I changed it for this
Thanks for testing it! I'll put the zips on the main post now. What rom were you using? If this works on other roms, I'd like to let people know. That is a cool icon. I personally think any circle mod clashes with the touchwiz theme, which I actually like.
Thanks dude! this was my only gripe with TPCv3! I'll try the zip in the morning. Thanks!
Hey man how did you get the battery percentage to be off-centered like that within the battery icon? And did you use UOT?
Sent from my SAMSUNG-SGH-I727 using XDA App
I use TPCv3
and yes I used UOC to build the new battery.
plwalsh88 said:
Hey man how did you get the battery percentage to be off-centered like that within the battery icon? And did you use UOT?
Sent from my SAMSUNG-SGH-I727 using XDA App
Click to expand...
Click to collapse
well i manually edited the framework-res.apk file. did not use any software besides 7zip. the battery icons are just pictures, so the text isnt overlayed text, its just a .jpg with a number in it. i didnt actually make the battery icons, i took them from a galaxy s2 rom from somewhere.
Pseudonym117 said:
well i manually edited the framework-res.apk file. did not use any software besides 7zip. the battery icons are just pictures, so the text isnt overlayed text, its just a .jpg with a number in it. i didnt actually make the battery icons, i took them from a galaxy s2 rom from somewhere.
Click to expand...
Click to collapse
Ohhh interesting, thank you! Since I'm not running TPC, I wouldn't want to take your framework-res, but I guess I could use the battery images you used and swap them inside my framework-res. I've been wanting to learn how to decompile/recompile those apks, so I guess this would be good practice. I'd have to read up more about where the images go and all though. But that's doable right?
Sent from my SAMSUNG-SGH-I727 using XDA App
its definitely doable! really, all you need to do is open the framework-res from here in 7zip (not extract, just open) and copy all the files that include "stat_sys_battery" from "res/drawable-hdpi" and put them inside your framework-res (same folder, opened in 7zip). then you need to copy "stat_sys_battery.xml" and "stat_sys_battery_charge.xml" from the "res/drawable" into your framework-res.
if i didnt properly explain that, let me know. you definitely should make a backup of your rom before flashing a custom framework-res, just in case you break something.
Wow awesome! That doesn't sound bad at all. I will give it a shot for sure. And will definitely backup everything. I would then just adb push it back to /system/framework as you described in your OP right? That could also be done with root explorer right?
Sent from my SAMSUNG-SGH-I727 using XDA App
i would do it like i said in my original post. you may be able to do it with root explorer, but i wouldnt personally do it, as files are constantly being read from framework-res.apk. dont think it would work, like deleting a file in windows doesnt work when you have in open in another program. i could be wrong, but i think adb at the recovery menu would be much safer.
Yeah that makes perfect sense. I'll let you know how it goes when I finally find the time to do it. Thanks for your help!
zip worked as stated. TPCv3
thanks again
zip working on stock too, only power buttons are not in order..
norbarb said:
zip working on stock too, only power buttons are not in order..
Click to expand...
Click to collapse
full stock or deodexed stock? if it isnt deodexed, i am extremely surprised that it worked. what do you mean by the power buttons being out of order?
Pseudonym117 said:
full stock or deodexed stock? if it isnt deodexed, i am extremely surprised that it worked. what do you mean by the power buttons being out of order?
Click to expand...
Click to collapse
Full stock. When you press power to turn off phone you got Sound off where Power off should be also when Flight mode should be is Sound off. When you press volume buttons you got message something about Text settings, but icons are correct so you know what is for what...
norbarb said:
Full stock. When you press power to turn off phone you got Sound off where Power off should be also when Flight mode should be is Sound off. When you press volume buttons you got message something about Text settings, but icons are correct so you know what is for what...
Click to expand...
Click to collapse
very strange... it may do less things wrong if you were to have a deodexed rom (probably would still have somewhat funky behavior, but not as much). but if youre happy with how it works, by all mean keep it how it is.
floppy__ said:
Thanks,
I tested BatteryMod and NoVibrate.zip and it work like a charm,
Great job.
The battery was not exactly my taste then I changed it for this
Click to expand...
Click to collapse
Just an FYI to you or anyone else that might not be aware (since there are no pics for the Sky ICS ROM additional downloads). This is also available as one of the extra downloads in the Sky ICS ROM thread (post #2). Its the Digital Circle Battery mod.
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.
Are there any DSP managers that work with our Motoblur 2.2 ROM other than PowerAmp? PowerAmp is fine for playing stored music; I find myself listening to Pandora more often though. Even on the treble booster audio setting everything sounds muffled.
magicCrazyThing said:
Are there any DSP managers that work with our Motoblur 2.2 ROM other than PowerAmp? PowerAmp is fine for playing stored music; I find myself listening to Pandora more often though. Even on the treble booster audio setting everything sounds muffled.
Click to expand...
Click to collapse
Not positive, but you might be able to use AudioEffectSettings.apk from CM7. Its a Moto DSP app. I've never tried, but then again, I've ran a custom rom since the 4th hour of owning a Bravo. Push\paste it into /system/app and set the permissions to either 644 or whatever the other apps have in the gui of your filemanager.
Open a terminal\command prompt in the folder with the file and use this command
Linux Version
Code:
adb remount && adb push ./AudioEffectSettings.apk /system/app && adb shell chmod 0644 /system/app/AudioEffectSettings.apk && adb reboot
Windows Version
Code:
adb remount && adb push .\AudioEffectSettings.apk /system/app && adb shell chmod 0644 /system/app/AudioEffectSettings.apk && adb reboot
Note that the only difference is ./ to .\ between the two.
The only problem I can see is Android changed the DSP framework from 2.2(stock) to 2.3(CM7\MS2\MIUI). It won't cause bootloops or anything bad to happen, but it might not work.
If you're running stock you should switch to the BravoX rom -- its a stock deodexed rom for the Bravo and it runs much faster and smoother.
If you do try this let us know if it works.
I usually just use cm7, but due to some rather bothersome problems I've had lately I decide to just use BravoX for awhile. I just tend to be a bit of an audiofile.( That was the original reason for my switch to to CM7 actually.)
which is easier to use ADB under: Ubuntu or Windows? I run both on a dual boot. Also could you point me to a tutorial of adb? I always avoided it because of how complicated it seemed.
It depends on which system you're more comfortable using the command line on really; or use the most. I'd use the linux version myself, but linux is my only OS
Go here and you'll find all the instructions you'll need for either windows or linux install.
http://developer.android.com/sdk/index.html
Its a bit complicated but really worth it in the end to have adb installed -- once you get the hang of pushing files to your device you'll never mount your sdcard again. Adb is much safer anyways; less chances of file system corruption from multiple OS's mounting and unmounting the sdcard. It happened to me a lot when I dual booted 7 and Mint 12 -- every time windows would unmount it I'd have file corruption issues. Since I quit using windows I haven't had file corruption anymore.
If you need more help than what that site has, just search the forums here (there are tons of adb tutorials) then post here if you can't find what you're looking for.
//I'm an audiofile myself. The DSPManager not working on CM9\10 really grinds my gears -- its still required to be installed for 3rd party DSPManagers to function (PowerAmp, MortPlayer, etc). There's also a paid equalizer app on the market, but I've never used it at all. Not sure if it supports Froyo, but it does support Gingerbread and up.
If I don't post back anytime soon its because my PC is on the ass end of the next PA compile and it gets really slow on the java compile for the apk's.
I forgot that I already had it all setup in windows. Now I just have to look through some of the tutorials on here.
I actually already had it installed completely under Windows. I just need to learn the commands. I know it's adb push, but from their I'm learning.
opps, My computer didn't show my previous post. so now theirs two. sorry.
I just noticed that you already had the command there. it wont let adb remount run though it just keeps telling me "remount failed: operation not permitted." my phone has android debugging enabled. what would cause that?
okay, I have it all sorted out. It sent the AudioEffectSetting.apk over and so far no problems. It's allowing me to change the audio effects, and the stock music app is working. I don't think it sounds as muffled as it did. would this allow for me to use the CM7 Dsp manager app? would that be the best way to test?
magicCrazyThing said:
okay, I have it all sorted out. It sent the AudioEffectSetting.apk over and so far no problems. It's allowing me to change the audio effects, and the stock music app is working. I don't think it sounds as muffled as it did. would this allow for me to use the CM7 Dsp manager app? would that be the best way to test?
Click to expand...
Click to collapse
Glad that AudioEffects works. Good to know if you run the stock roms.
Just push DSP and try. Worst that'll happen is you'll have to remove it.
I think it relies on the library /system/lib/soundfx/libcyanogen-dsp.so, push it if DSPManager doesn't work.
The permissions are still 0644 for these files. Most libraries and apks are.
to remove
adb remount
adb shell
rm /system/app/DSPManager.apk && rm /system/lib/soundfx/libcyanogen-dsp.so
I've been having adb issues for a while now. Enabling tethering fixes it for me. What sucks is I can't use adb in the bootmenu or pull a logcat on boot.
Something here isn't happening right. Adb says the files are pushing fine. the DSP manager is not showing up anywhere though. as a test I ran the the push command by itself and then ran the second part separately. when It goes to run that second part to set the permission though it tells me that that directory does not exist. it's listing the files as the wrong sizes too. the DSP Manager is only 42Kb, and adb is pushing something that is 660Kb. It's doing that with all of them. the sizes are always listed wrong.
magicCrazyThing said:
Something here isn't happening right. Adb says the files are pushing fine. the DSP manager is not showing up anywhere though. as a test I ran the the push command by itself and then ran the second part separately. when It goes to run that second part to set the permission though it tells me that that directory does not exist. it's listing the files as the wrong sizes too. the DSP Manager is only 42Kb, and adb is pushing something that is 660Kb. It's doing that with all of them. the sizes are always listed wrong.
Click to expand...
Click to collapse
That's weird, the file sizes. How long ago did you set up adb? Its probably been updated since the last time you used it. On my system all I have to do it type "android" and it opens up the sdk to update it. I've never used the sdk under Windows so I'm not sure the proper command to update it (my adb on windows was in a root kit).
Just use a file manager to do it. I recommend Apoonet's MiFileExplorer (here on xda) or Yaffs Explorere by TPruvot (Epsylon3) on the market. I suggest Yaffs because it also shows you the linux chmod code when you change file permissions (useful feature if you're learning chmod).
Since its related I'll add that if you've ever added an app /system/app and it didn't work properly, it requires a lib to be added to /system/lib. You have to do it manually by opening up the apk and copying the lib over (use the arm7 lib if there are more than 1 of the same name). There is no lib in DSPManager but it relies on the one mentioned earlier.
Good Luck
I think what happened with the lib mentioned earlier is that there is no soundfx folder in system/lib/. I went looking for it last night with a file manager. there is one in there called DSP though. I would have justt pushed the audio lib there, but I didn't think the DSPmanager.apk would find it.
The DSPmanager from Cm6 will start up. it won't do anything though. do you know what libs it relies on?
I guess Froyo doesn't have that folder (just checked the SBF)
Here's the soundfx folder from a Defy GingerBread SBF -- non flashable zip.
Just make a soundfx folder in /system/lib and copy all the files to it; same permissions as always.
The dsp folder is codec related, not effects
Not sure what lib is required for CM6 (never used it)
I have everything in the folders now. CM7 DSPManager still won't show up. I went in and found it in Yaff's. When I try to install it through Yaff's it just tells my that there was a problem parsing the package. Also your link isn't showing; I have one of you CM7 Kang zips that I have been pulling files from though.
magicCrazyThing said:
I have everything in the folders now. CM7 DSPManager still won't show up. I went in and found it in Yaff's. When I try to install it through Yaff's it just tells my that there was a problem parsing the package. Also your link isn't showing; I have one of you CM7 Kang zips that I have been pulling files from though.
Click to expand...
Click to collapse
I guess I forgot to upload it. I was sleepy. Its up there now.
It won't install since its a system app. The only way to use it is to place it at /system/app with the correct permissions and reboot. If it doesn't show up it might just not work on Froyo.
Try this flashable zip. Make a nandroid before flashing it. I replaced a few audio libs, changed the DSPManager.apk sdk version to froyo. There's a chance this zip will either work or cause bootloops or do nothing at all. I can't test it since I'm on PA and I don't feel like SBFing back to Froyo, then flashing BravoX.
EDIT
Forgot to add -- if the zip flashes just fine, boots fine, and DSPManager opens but does nothing, add in libaudio.so from CM7 in the zip here to /system/lib and reflash it.
I got stuck on the Red M both times I tried. The first time I was on the BravoX recovery; the second time (after SBFing) I tried under 2nd-init. i'm beginning to wonder if this is possible. I guess I'll start burring my head in lots of forums and try again tomorrow.
You're awesome for all the support you've been giving me though. I get the feeling we're really close to getting this working.
magicCrazyThing said:
I got stuck on the Red M both times I tried. The first time I was on the BravoX recovery; the second time (after SBFing) I tried under 2nd-init. i'm beginning to wonder if this is possible. I guess I'll start burring my head in lots of forums and try again tomorrow.
You're awesome for all the support you've been giving me though. I get the feeling we're really close to getting this working.
Click to expand...
Click to collapse
try removing libeffects.so.
The fourms I found added in libaudiofilinger.so and libaudio.so if needed -- I forgot that our libaudio.so on CM7 is from stock froyo so its not necessary here.
I know that the 3rd Party DSP's on the Market use their own special libraries on Froyo\2.2 roms to give them GB style DSP's. Google upgraded the DSP framework from 2.2 to 2.3.
If you looking for Pure Music functionality and awesomeness then I highly recommend changing to CM7. GB roms have the best mods for audio effects, long press the volume for track changing. The fx folder is necessary (at least in some Miui Ports its was).
That said, I'll jump back to BravoX and see if I can't get it working on my phone. I like a challenge and doing something that benefits a native Bravo rom. Unlike everyone else here, I have a rooted SBF (made it myself) so its not very hard for me to do -- flash sbf, run market enabler, install 2nd-init, flash away . If I had remembered to backup my /data partition into the sbf I wouldn't even have to do that...just sbf and install 2nd-init.
Since you're on BravoX, have you ever tried the BlurLauncher3D Walter79 uses with MS2 Ginger? I'm about to use it with BravoX so I'll find out if it works or not.
---------- Post added at 09:56 AM ---------- Previous post was at 09:05 AM ----------
Back on BravoX. I need to tweak its init scripts to load the multitouch module and overclock module. Also, no tethering sucks.
---------- Post added at 10:40 AM ---------- Previous post was at 09:56 AM ----------
Managed to disable the tethering entitlement check.....only I'm forced to tether with 3g and not my home wifi like I do on CM7 -- that needs to be fixed, but at least I can post on the forums with my Keyboard again. I'm gonna keep messing around and see if I can't get it to use my home wifi instead of 3g.
Btw, to use thethering -- open build.prop and change ro.mot.entitlement_check=true to =false -- that's it. And I was changing smali code until I saw that prop string embedded in it.
Had to jump back to PA -- tethering was eating up my 3g bandwidth.
I started using the Droid 1 CM6 libs -- they don't cause bootloops or issues, but they don't make DSPManager work either. So far I've tried libaudio.so and libaudioflinger.so.
Wow, that was a lot of explanation.lol I haven't had time to try anything. you also tried the only thing I found anything on.
I haven't used tethering so far I never had a reason too. why do you have to use it?
Also, did you ever get blur launcher 3d to work on BravoX. I tried getting it to work with CM7 before, but all I ended up with the many times I tried was everything being deleted from my homescreens and the ROM would become extremely buggy.
magicCrazyThing said:
Wow, that was a lot of explanation.lol I haven't had time to try anything. you also tried the only thing I found anything on.
I haven't used tethering so far I never had a reason too. why do you have to use it?
Click to expand...
Click to collapse
My PC is farther from the router than my longest ethernet wire so I connect to WIFI on the Bravo and tether it. I can only do it on CM7\9\10\Miui. Moto roms have an entitlement check in them. I found the build.prop string to disable the check, but I'm still working on changing the default dhcp settings for tethering -- they're set to 192.168.43.XXX and I need it set to 192.168.0.XXX. I changed the dhcp range values in the smali code of services.jar but it didn't matter. I think there might be another smali file with dhcp ranges somewhere else. I don't want to change my routers dhcp range since all my WiFi devices are set to connect to a static IP (had to for the iPhones in the house -- the iPhone dhcp bug).
ROOT:
We've been discussing about this for about a month, and I think it's time to sum it all up and open a new cleaner thread.
First, how do you root the Alcatel Onetouch 997D?
This phone is quite new (less than 2 months in the market) and is one of the few phones which can't be rooted by the script developed by Bin4ry or the other well-known methods, such as Unlockroot or SuperOneClick, but it is not unrootable.
In order to root this phone, you must first boot it into Factory mode, a special menu, present in all Mediatek based phones, which can be used to test the various parts of the phone. You get to this menu by turning the phone on while pressing the volume down batton and power button at the same time, until it appears.
Once in factory mode menu, you can connect the phone to a pc, which, if the appropiate adb drivers are installed, will detect it. At this point, the phone can be rooted, by the use of an app called MTK Droid tools. I've succesfully tested versions 2.2.8 and 2.2.9.
After MTK Droid Tools finds the phone, you just have to press the "root" button. The phone will be rebooted two times, and after the second reboot, MTK Droid Tools achieves a temporary root which enables it to install Superuser, su and busybox, so the root is permanent.
During this process, MTK Droid Tools asks whether you want to make a backup. You'd better answer no, since this process is very buggy and fails on this phone, so it's a complete waste of time.
When "Task is complete" message appears, you can reboot the phone, but it won't work right away. Due to a problem not yet identified, it's mandatory to wipe data from recovery for the phone to work. Some people have reported the loss of Google Play Store, and others have lost a lot of apps. Anyway, a wipe solves the problem and the phone remains rooted.
MTK Droid Tools 2.2.8 can be found here: http://www.4shared.com/zip/NyHaro3-/MTKdroidTools.html
CWM Recovery:
We have a 99% working CWMR. I compiled it myself with the help of the dsixda kitchen and the MT6577 CWMR porting plugin developed by Bruno Martins.
I say it's 99% working because backup doesn't work 100%. Alcatel phones have a non standard partition called "custpack", which contains a lot of apps bundled with the phone and whose deletion prevents OTA updates from working, so it's not something one would like to remove. My knowledge of Android is not enough to try to dig inside CWMR source code, to see if I can modify the backup process and make it recognize the custpack partition, so I left it as is. Instead, I decided to develop a shell script which can make CWMR-compatible backups, which can at least be restored from it.
Everything else is fully functional. It's version 6.0.1.2.
To flash it, you need to root the phone, using the method explained above, and flash the recovery image using Mobileuncle Tools utility, which can be freely downloaded from Google Play Store. It's very important to download the latest version from Google Play, since previous versions lying around, and the version MTK Droid Tools installs during the root process can't flash a recovery on MT6577 processors.
To flash the recovery with Mobileuncle tools, you have to place it on the root of the external sd card and open Mobileuncle tools. After granting root permissions, if you haven't done yet, you choose "change recovery" and choose the corresponding .img file. Once the process is done, the phone will automatically reboot into the new recovery. It may fail, which you'll notice because the phone boots into the stock recovery, and you may need to do it again. I've noticed that, at least in mine, it works best if I do it while the phone is unplugged from the computer.
As I said abpove, everything, except backup, works well. Restore works, if you have the correct backup (more on this later).
My CWMR can be downloaded from my Mediafire account: http://www.mediafire.com/?v7wfjr6v1t7b0z5
NANDROID BACKUP:
After noticing the backup process in CWMR can't backup the Alcatel exclusive custpack partition, I began trying to solve this. I guess the best way to do it should be modifying the source code of CWMR to adapt the backup process, but, since that exceedes my current knowledge level, I tried differemt approaches. I downloaded the app Online Nandroid backup from Google Play, and learnt that a nandroid backup can be easily done using a shell script, given you have a rooted phone and a way to execute shell scripts. The good news is that it's done, and I have achieved my goal, and now have a working shell script, which creates backups that can later be restored from CWMR.
This script creates 7 files, like the standard CWMR backup process does. The files are:
1) boot.img
2) recovery.img
3) system.ext4.tar
4) cache.ext4.tar
5) data.ext4.tar
6) .android_secure.vfat.tar
7) nandroid.md5
Files 1, 2, 4, 5 and 6 are exactly what you now get if you use my CWMR port and perform a backup. The difference lies in file 3.
In a backup created from our current CWMR, this are the contents of the tar archives:
system.ext4.tar: files under /system, and all its subdirectories
cache.ext4.tar: files under /cache, and all its subdirectories
data.ext4.tar: files under /data, and all its subdirectories
.android_secure.vfat.tar: files under /sdcard/.android_secure
In a backup created by my script, it's slightly different:
system.ext4.tar: files under /system, and all its subdirectories, and also files under /custpack, and all it's subdirectories
cache.ext4.tar: files under /cache, and all its subdirectories
data.ext4.tar: files under /data, and all its subdirectories
.android_secure.vfat.tar: files under /sdcard/.android_secure
On both backups, boot.img and recovery.img are images compatible with Mediatek Flash Tool or Mobileuncle Tools (in the case recovery.img), and nandroid.md5 contains the md5 sum of every file, so the restore process can validate the integrity of them, to prevent you from ever restoring a corrupt archive.
In order to use my script, you need an app which can execute them. My preference (and the only one I have fully tested the script with) is GScript, which can be freely downloaded from Google Play Store.
There's also a paid version, but the only difference between them is that the paid version is updated more often than the free one.
How to install the script:
1) Download and install GScript, free or paid. You can use the apk file provided by me inside the attached zip.
2) Download the attached zip file with the scipt, if you haven't done so to install GScript.
3) Put the script on the external sd card, under a folder called "gscript". Use lowercase characters for the name and never change the name, as this would result in GScript not working or finding your scripts. The resulting structure should be:
/sdcard/gscript
|
------------> bin
Inside /sdcard/gscript you have the script itself, called "Alcatel_OT_997D_nandroid.sh" and inside /sdcard/gscript/bin, you have the busybox
binary, used by the script. Even if you have busybox already installed, don't delete this binary, since it's the only one the script will use, and
the only one it's been fully tested with.
4) Open GScript.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5) On the GScript main window, you can see a pair of sample scripts already included. You need to touch the menu button and then on "Add script".
6) Browse for the .sh file on /sdcard/gscript, and tick "Needs SU?" if it's not already ticked, since this script needs a rooted phone.
7) Once the new script is in the list of installed scripts, you only need to touch its name to launch it. The first time you do it, GScript will ask for root permissions. Allow it.
Once you open the script, it will run automatically, and will end around 5-10 min. later, depending on how loaded your phone is. In order to be able to see every message shown by the script, it's better to raise the screen timeout, to at least 10 minutes. After execution, the output window will auto close, unless you cancel auto closing by touching anywhere on the screen except, of course, the close button.
The backups are stored under the /sdcard/clockworkmod directory (the script will create it if its not already there), under which it will create a new subdirectory, with the date and time of the backup, just in the same format CWMR uses.
During the execution of the script, you may see two error messages, which are not really errors, but warnings you can ignore. These errors are:
1) Errors creating directories at startup. If the script has already been used, or you have tried the backup inside CWMR, sdcard/clockworkmod/backup already exists. The script will tell you that, but it will keep working.
2) Removing leading "/" from member names: tar utility removes "/" from the input parameters, just that.
3) XXXXXXXX: socket ignored, where XXXXXXXX is the name of a file. Sockets are temporary files Unix apps use to communicate with other apps. Since they are temporary, tar just ignores them, so you can also ignore the error message.
On mi phone, after I close the results window, GScript force closes, but this doesn't affect the execution of the script. As I've read somewhere, it
looks like this is a problem common to a lot of users.
DISCLAIMER:
This script is offered AS IS, with no warranty. It has been successfully tested on my own phone, and the generated backup was then perfectly restored from recovery with no issues, but I can't say it won't fail on other people's phones.
It's the first version, fully functional, but with some room for improvement. As it is right now, it's not error free, since it doesn't check if you have enough space left on the sdcard, or if you don't have any apps moved to the sd card. In fact, I have not tested it in such a situation, and I don't know what would happen if you backup your phone with no apps moved. On the other hand, it doesn't bakcup sd-ext, so if anyone has a second partition on the sdcard, to use Link2SD o a2sd, that partition won't be backed up, although data for apps linked to the second partition will. Anyway, even if it fails, you don't have to worry, since it won't change anything inside the phone. If you later restore a backup made with this script, you are doing it AT YOUR OWN RISK. I will not accept any responsibility for damage or data loss caused by the use of this script or restoration or any backup created with it.
Don't forget this script needs a rooted phone, and that performing some things on rooted phones is risky. If the worst case, you will always be able to recover the phone using Alcatel One Touch Upgrade on your pc.
Any comments or improvements are welcome, but if you change / improve anything, don't forget to share it with the community, so everyone can take advantage of it.
IMPORTANT:
This script is only suitable for the Alcatel OT-997D, and probably other phones by the same brand, if they have the "custpack" partition, exclusive to Alcatel. It won't work, unless code regarding the custpack partition is modified, in other phones, and I will not give support to users complaining the script doesn't work on their non Alcatel phones, or their Alcatel phones without s custpack partition.
FINAL NOTE:
Ok, that's it. Now, I'm going to have a rest, maybe until Alcatel release the long waited Jelly Bean update.
EDIT:
I had forgotten the "thanks" section:
Thanks to:
@dsixda, for the great kitchen
Bruno Martins (@bgcngm) for his valueable advice and his scripts to unpack/repack recovery of any MT657x based device
@yuweng, who developed the great kitchen plugin to port CWMR to any MT657x based device. and also pointed me in the right directory when I was trying to root the phone
@ameer1234567890, author of the great onandroid script. I haven't used your code, but it taught me I had to unmount and remount the sdcard on a different location to be able to backup .android_secure
Reserved
Reserved too
Any chance of working on a custom rom? i would love to get the standard google theme instead of the alcatel icons
maybe i try to get this done, changing the icons is'nt that hard normally
btw i'm still looking to cleanup this phone, you know the partitions pretty wel, where is the location of all the stock apps like chrome etc, i would love to make the phone as close to googles standard as i can get it
edit: you can always pm me, i don't want to ruin this topic
Hey jman10 thank you very much for your awesome tutorial.
But i still have to ask, if the restore works 100%, because of lack of gps signals i made a cwm backup of my current stock-rom(4.0.4) and tried, if the newest update(4.0.4-01001) still has problems with gps signals. Well actually it didn't get any better, so i decided to go back to the old version with the help of my backup.
CWM said there were no errors while restoring, so also thought it. But i get a few bugs using the old version, the stock camera-app gets force closes, even after reboots or a data wipe. The stock e-mail app shows weird artefacts on the email subjects, a very large 'x'. It seems, like a lot of system files are missing or sth.
Can you help me?
Thanks!
kassipopassi said:
Hey jman10 thank you very much for your awesome tutorial.
But i still have to ask, if the restore works 100%, because of lack of gps signals i made a cwm backup of my current stock-rom(4.0.4) and tried, if the newest update(4.0.4-01001) still has problems with gps signals. Well actually it didn't get any better, so i decided to go back to the old version with the help of my backup.
CWM said there were no errors while restoring, so also thought it. But i get a few bugs using the old version, the stock camera-app gets force closes, even after reboots or a data wipe. The stock e-mail app shows weird artefacts on the email subjects, a very large 'x'. It seems, like a lot of system files are missing or sth.
Can you help me?
Thanks!
Click to expand...
Click to collapse
If you use my script to backup your rom, restore from CWMR will work 100%. So, your way to go is to start from scratch. Download Alcatel Onetouch Upgrade to a pc, connect the phone and get the latest full version rom on their servers (which sometimes is not the latest one available). Then, connect via wifi and get the latest OTA update. After that, you can root the phone, flash CWMR and make a working backup. From that moment, you'll be able to restore whenever you want and not risk anything.
By the way, which problems are you having with the gps? Mine is working like a charm, even indoors. Where are you from and what kind of tests have you done with it?
Hey thanks for your quick answer, actually i did the whole process that way:
-root stock firmware 4.0.4
-installed cwm per mobileuncle tools
-created image per script
-updated with the help of one touch manager to 4.0.4-01001
-tried gps, didnt work
-rooted
-installed cwm per mobileuncle tools
and then i wanted to return to point 1, but as soon as i restored the backup, my camera doesnt work and i get random fc's of several apps. i would like to return to stock 4.0.4, because since the new update the system is more laggy
do you know a way? do you have a *.img of the old version?
my gps is really weird, i would say it works at 10%. in my home city i couldnt make it work, then i tried it randomly in 2 other cities and it worked instantly, but then i try it again at the same spot, where it worked a couple of hours earlier and it doesnt work anymore its really weird.
thanks man!
kassipopassi said:
Hey thanks for your quick answer, actually i did the whole process that way:
-root stock firmware 4.0.4
-installed cwm per mobileuncle tools
-created image per script
-updated with the help of one touch manager to 4.0.4-01001
-tried gps, didnt work
-rooted
-installed cwm per mobileuncle tools
and then i wanted to return to point 1, but as soon as i restored the backup, my camera doesnt work and i get random fc's of several apps. i would like to return to stock 4.0.4, because since the new update the system is more laggy
do you know a way? do you have a *.img of the old version?
my gps is really weird, i would say it works at 10%. in my home city i couldnt make it work, then i tried it randomly in 2 other cities and it worked instantly, but then i try it again at the same spot, where it worked a couple of hours earlier and it doesnt work anymore its really weird.
thanks man!
Click to expand...
Click to collapse
Did you do a factory reset after rooting? It's really important to do so, and the phone doesn't work if you don't.
Hey mate,
sure i did, i have no problems with root at all. My problem is to restore my cwm backup i did with the old firmware, because i really want it back badly. Do you have a image file of the "roll out" stock firmware?
Thanks in advance!
Hi,
it seems like I am missing something.
I installed the MTK-Tools 2.2.8, connected the phone but the phone is not recognized. I see there is missing some MT65xx AndroidPhone-Driver. Where can I get one?
The installation of the OneTouchManager does not help. Any ideas?
kassipopassi said:
Hey mate,
sure i did, i have no problems with root at all. My problem is to restore my cwm backup i did with the old firmware, because i really want it back badly. Do you have a image file of the "roll out" stock firmware?
Thanks in advance!
Click to expand...
Click to collapse
The system image I have is vastly modified by me, so it might not be suitable for you. If you did the backup using my script, it should work right away. Can you tell me what files (names, sizes, etc.) you have in your backup?
Roland_SGN said:
I installed the MTK-Tools 2.2.8, connected the phone but the phone is not recognized. I see there is missing some MT65xx AndroidPhone-Driver. Where can I get one?
Click to expand...
Click to collapse
There is a driver directory inside mtk tools zip. Let windows take that driver manually.
we now have kernel (and more) sources online from alcatel:
http://sourceforge.net/projects/alcatel/files/OT_997D_20121228.tar.xz/download
I'm downloading them...
fear_factory84 said:
we now have kernel (and more) sources online from alcatel:
http://sourceforge.net/projects/alcatel/files/OT_997D_20121228.tar.xz/download
I'm downloading them...
Click to expand...
Click to collapse
Now we just need a CM10 rom, then we're on!
Sent from my Packard Bell [email protected] v20 using Tapatalk
MadMav88 said:
Now we just need a CM10 rom, then we're on!
Sent from my Packard Bell [email protected] v20 using Tapatalk
Click to expand...
Click to collapse
You need also to implement dual sim support on it.. it's a huge work!!!
For now we can aim to fix those annoying bugs on stock rom (if we can) and get a 100% working recovery.
My bugs on latest stock rom:
- bluetooth freezes when bt headset is disconnected by lack of signal
- compass doesn't give good values at all
- need for speed most wanted sound is borked and is not 100% smooth like on other mtk 6577 devices.
In addition I would like to have:
- smaller system bar on the bottom
- search button and menu button always visible on system bar
- extended power menu with the option to have "extended desktop" (system bar hidden by killing it, and then restarted when reenabled)
These can be made by editing framework with smali and friends.
Prerequisite is a fully deodexed rom (and that is easier) and a lot of spare time!
Any news?
Sent from my ALCATEL ONE TOUCH 997D using xda app-developers app
fear_factory84 said:
You need also to implement dual sim support on it.. it's a huge work!!!
For now we can aim to fix those annoying bugs on stock rom (if we can) and get a 100% working recovery.
My bugs on latest stock rom:
- bluetooth freezes when bt headset is disconnected by lack of signal
- compass doesn't give good values at all
- need for speed most wanted sound is borked and is not 100% smooth like on other mtk 6577 devices.
In addition I would like to have:
- smaller system bar on the bottom
- search button and menu button always visible on system bar
- extended power menu with the option to have "extended desktop" (system bar hidden by killing it, and then restarted when reenabled)
These can be made by editing framework with smali and friends.
Prerequisite is a fully deodexed rom (and that is easier) and a lot of spare time!
Click to expand...
Click to collapse
About bugs:
- When I'm calling someone that is listed as favourite for a specific sim, the system asks which number I want to use.. I know about the configuration, I settled the first sim as principal (every call) and the second sim just for some contact. So, why is still asking which number is able to use for them? Is it a bug?
- The digital compass doesn't work well, or better, it's not working at all! The North it's not properly indicated, it follows the gravity verse..
Addictions:
- The status bar can be toggled by power menu or maybe by a sequence (example: vol - vol -)
Etc.
Sent from my Packard Bell [email protected] v20 using Tapatalk
MadMav88 said:
About bugs:
- When I'm calling someone that is listed as favourite for a specific sim, the system asks which number I want to use.. I know about the configuration, I settled the first sim as principal (every call) and the second sim just for some contact. So, why is still asking which number is able to use for them? Is it a bug?
Click to expand...
Click to collapse
It's the same on mine.
I tried to set one contact associated to 1st sim and an other to the 2nd sim, and I set the 1st sim for all call.
When I want to call:
-if I phone one contact without associated's sim, call goes direct by the 1st Sim.
-If I phone one contact with the 1st sim associated, call goes direct by the 1st Sim.
-If I phone one contact with the 2nd sim associated, the sim choice windows appear but it's written "suggested" on the 2nd sim.
So the call don't start automatically.
and I set no principal sim for call (every time you need to choose), I have the sugestion on the associated's Sim.
Many people complained about this contact sim preference bug.. I never used this function, so I can't tell.
To toggle status bar, the better working solution I've found is the Hide bar app (search it on xda).
Yesterday I was fighting with my phone that looses signal on the secondary sim when on charge. It may be a bug with my sim/operator combination when sim1 has 3g enabled.
Sim1 Wind Italy, 3g enabled on it, Sim2 Tim Italy no 3g (obviously), when I attach charger or usb cable, I loose Tim signal.
Swapping usim card slots does nothing.
If I enable 3g on Tim Italy, and no-3g on Wind Italy, it works flawlessy. Same if I disable totally 3g.
Anyone with similar issues?
I collected radio logcats and sent them to Alcatel Italia. Probably they will not reply at all, but I have tried...
Please do the same for other bugs! Maybe they'll hear us..
Converning CWM Backup: What about making the backup with online nandroid backup using an adapted partition layout like for those devices here?
That would be restorable by your cwm, too?