**UPDATE**SuperG1-Computer 9/8/09 4:03am - G1 Android Development

Here is basic program for your windows computer that just does basic stuff.
It can reboot your phone to wherever you want like recovery, bootloader.
It will wipe your ext2/3 from recovery if you choose and it will repair your ext2/3.
This is still beta, so far everything that is on the app works. But when I say beta I mean I still to implement alot more features so just use it and then tell me what you guys want. I am working on implementing switchrom into it.
This is just about 3 hours of work so you will see alot more in the future.
Screenshots Below!
*(For those of you wondering it is writen in a mix of C++,vb.net,python,and MS-DOS)*
Twitter: http://twitter.com/kickfliprock13
** Oh I forgot to mention you need to have adb set up for this to work if you don't have it set up than it wont work. So if you want to set up just go here: http://punk-in.com/driver_vista.html
changelog:
9/8/09: Added a link to tell you how to install usb drivers for your phone
Added links to our twitter's and plurk's
Fixed a few small bugs
Sped it up a little

doesn't work. tried all your buttons. only one that said anything that made sense was the connect button saying that it was successfully connected. used them both with mounted and unmounted.

adb needed
you must have adb copied to system32 or have the path set up, sorry I forgot to mention that. and then when you plug your phone in click connect and then when it says that it has successfully connected than use the other commands. but everything uses adb so you need it!

Instead You can Add the ADB files into the program & provide a "Install Necessary Files" Button Which will copy the ADB & Fastboot files into the system32 folder of the User From the Inside Of the Program & its UI
Lastly Good Work...

fantasic! works like a charm.
no criticisms as such, but maybe the layout could be improved a bit (i appreciate you did in 3 hours )
anyway, very handy little program!

This sounds like an awesome project. i will play with it and let you know what i find.
Keep it up!

If any of you guys want to help out with it just send me a pm and I will send you myC++ folder. I took an entire C++ course in like 3 days so my brain is kinda forgetting some of the simpler stuff!

Nice work, it'll be a great tool to use. Keeping my eye on this project, I can only imagine all the modifications that'll be made for it.

Wipe is a basic deletion of ext3
What command are you using for fixing ext3?

Wipe is a basic deletion of ext3
What command are you using for fixing ext3?

I am using the repair filesystem command that cyanogen put into his recovery image

Related

[TOOL] ADB Gui - Also flashes radios [08/01/11]

For all you guys constantly flashing kernels,
I have made a little app to make sure that all command are typed in correctly & to make it a little easier.
You can find it here.
http://minooch.com
Let me know if you think I can make any improvements.
I've only tested it with my N1, but there is no reason why it wouldn't work on other android phones - its just using adb & fastboot. Having said that, it will obviously need the AndroidSDK installed (well partly) & the only other requirement is .NET 2.0 or up.
I finally got around to posting the new version - Version 1.0.1 - The main feature that has been added is synchronise. For example, you can select a folder full of music on your PC & it will copy all the music to your phone (if it's not already on there), & if there is music on your phone thats not on your pc that will copy over as well.
26/05/10 - Small change - Version 1.0.2 - ADB location is now saved in registry
17/08/10 - Version 1.0.3 - Added flash radio (via fastboot) - It will reboot into the bootloader, flash the radio & then reboot the phone
30/08/10 - Version 1.0.4 - Added a donate link
25/11/10 - Version 1.1 - It now has the option to verify the MD5 before flashing a radio
08/01/11 - Version 1.2 - Language can now be changed - Language.lang has the values of all labels, buttons & comboboxes
Known Bugs: (wth synchronise)
If a folder has a space in its name, it's contents won't sync properly (currently working on a solution)
If you delete a file/folder on your phone/pc (not both) it will be copied back next time you sync (not sure how to fix)
The destination folder must exist already (/sdcard/music or where ever you choose), but obviously not the folders what will synced they will be created
Cheers,
Minooch
Feel free to donate
Nice work. Looks like it will make things easier for inexperienced users...which I am not sure is a good or bad thing.
Also, you might want to add "adb reboot recovery". I know I use it fairly often.
(make it "adb wait-for-device reboot recovery". This way, if your phone is bootlooping due to you having not installed bcm4329, you can access recovery for adb push options to fix the bootloop)
rcxquake said:
Nice work. Looks like it will make things easier for inexperienced users...which I am not sure is a good or bad thing.
Also, you might want to add "adb reboot recovery". I know I use it fairly often.
(make it "adb wait-for-device reboot recovery". This way, if your phone is bootlooping due to you having not installed bcm4329, you can access recovery for adb push options to fix the bootloop)
Click to expand...
Click to collapse
didn't know that command will add it now. - edit: Done
Cheers,
Minooch
I'm happy with ADB so not going to be using this (don't mean that the way it sounds!) but just thought if the user is pushing the .ko over adb, will they need and "adb remount" option as well?
yep you will need to remount - but that is automatic.
Using my tool, it takes less steps & is faster
great tool! thumbs up!
Great tool. Any chance for a Wipe Cache/Dalvik Cache option? A lot of times this will fix a bootloop when flashing different kernels on top of eachother. I understand it's in the recovery but this could speed up the process even more.
mikroN1 said:
Great tool. Any chance for a Wipe Cache/Dalvik Cache option? A lot of times this will fix a bootloop when flashing different kernels on top of eachother. I understand it's in the recovery but this could speed up the process even more.
Click to expand...
Click to collapse
Thanks,
Will have a look into it.
looks like a nice tool.. gonna give it a try
good work man
Hey man I'd have to say that I'm getting used to the command line that I nearly forgot there's something in the world called GUI It's really a great tool for lazy guys like me (even I've written a simple shell script). Good job!
Thread hasn't been bumped in awhile. You still working on this Minooch? I was wondering if you could have it save your ADB location? Maybe have it save settings to an .ini file.
MikroN1,
I will add that later today when I get home from work.
Cheers.
Can you please kindly provide the manual instruction, as I'm not the professional user, even I don't know much the ADB command codes, so please instruct the functions of the buttons.
mikroN1 said:
Thread hasn't been bumped in awhile. You still working on this Minooch? I was wondering if you could have it save your ADB location? Maybe have it save settings to an .ini file.
Click to expand...
Click to collapse
mikroN1,
It nows saves the ADB location to registry
devil126 said:
Can you please kindly provide the manual instruction, as I'm not the professional user, even I don't know much the ADB command codes, so please instruct the functions of the buttons.
Click to expand...
Click to collapse
I'm a little confussed by what you want. Are you wanting a manual for ADB GUI or how to use ADB?
This is very good. Downloading now.
New Version - 1.0.3
Added flashing radio via fastboot
It will reboot into the bootloader, flash the radio & then reboot the phone
using ADB sync for sqlite DB
Hi,
I am fairly new to Android / ADB and i have found ADB as a great tool.
My requirement is to sync a sqlite DATABASE (from my PC and on device), i am not sure how should i go ahead with this, gave couple of tries but not able to get anything
Can anyone please suggest me possible ways to fix up this issue. If this is not possible please give me any alternate (i believe this is possible).
Any help in this regard would be highly appreciated.
Thanks in advance.
BTT
asinghma said:
Hi,
I am fairly new to Android / ADB and i have found ADB as a great tool.
My requirement is to sync a sqlite DATABASE (from my PC and on device), i am not sure how should i go ahead with this, gave couple of tries but not able to get anything
Can anyone please suggest me possible ways to fix up this issue. If this is not possible please give me any alternate (i believe this is possible).
Any help in this regard would be highly appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Bringing this thread to top.
Can anyone provide the source for ADB sync (prob from ADB_GUI tool)
Thanks,
Think you should add a donate button somewhere in your app too!
Vulpix said:
Think you should add a donate button somewhere in your app too!
Click to expand...
Click to collapse
Done Feel free to be the first to donate
Oh, If you would like me to add any features, let me know

[DEV] PSFreedom(PSJailbreak) Android Port

I think all of you PS3 owners here already know about the Jailbreak tool that allows you too execute unsigned code on the PS3. That opens the console for a lot of homebrew possibilities(mplayer port maybe?). The source code for the exploit leaked and a dev called KaKaRoTo managed to get it to be executed from a N900. Yesterday KaKaRoTo released his souce code and today someone already ported it to the Palm Pre. This quick port was possible because the N900 and Palm Pre both share the same USB controller(mUSB) which happens to be the controller used by the Droid/Milestone.
Here is some info from KaKaRoTo's blog:
Q: How hard is it to port it to a new device ?
A: Well, I’ve just separated my code from the N900 specific stuff, so it’s quite easy, there are mainly two functions to write, one to get and one to set the USB address.. two other functions that only return some static result depending on the configuration of the controller (the name of the endpoints, and whether the controller supports high speed or full speed mode).
Read the README file provided with PSFreedom, and check the psfreedom_machine.c file for specifics on what to implement.
Q: How can I port it to a new device.
A: Well, first, you need to figure out what controller your device uses, in the case of the N900, it’s ‘musb’..
Then go to the driver code for that controller (probably in drivers/usb/gadget) and look for ‘SET_ADDRESS’. In the case of musb, it was in drivers/usb/musb/musb_gadget_ep0.c. In there it was setting the address to the USB device, so just copy that code into the psfreedom_machine.c to allow setting the address, and add a similar function to be able to retreive the address.
Then add a function to return 0 or 1 depending on whether the controller supports HIGH, FULL or LOW speed mode (go to usb_gadget_register_driver for your controller, and in the first lines, it should validate the speed argument, it will tell you which ones are acceptable), set LOW speed mode to return TRUE only if FULL speed isn’t available .
Finally, add a function to return the endpoint names.. it will usually be something like ‘epXin’ and ‘epXout’ (where X is the endpoint number), or “epXin-bulk”, etc.. look at how the driver initializes its endpoints or grep for “->name” in the file to find where it sets it…
That should be enough!
Ok this is it for now with the FAQ. Next time, I’ll tell you all about my experience, what problems I encountered and how I fixed them, maybe it will help others!
Click to expand...
Click to collapse
http://kakaroto.homelinux.net/
Some people over the HTC Desire boards are already working on a port but Desire's controller is a different one(MSM72K) so they might take some time and it will be of no use for us
http://forum.xda-developers.com/showthread.php?t=772795
So, any dev here willing to give it a try?
according to zzg in the desire forum, this is what you need to do. no source changes.
Well you don't really need any changes to get it compiled against Droid's kernel, a quick and dirty way by looking at psfreedom's make file:
make -C /path/to/droid/kernel/source M=/path/to/psfreedom/source ARCH=arm CROSS_COMPILE=/path/to/android_ndk/tree/build/prebuilt/linux-x86/arm-eabi-4.4.0/bin/arm-eabi- EXTRA_CFLAGS=-DENABLE_MUSB_CONTROLLER modules
Click to expand...
Click to collapse
You can get the source from motorola.
Has anyone been successful with the exploit?
On the wiki it shows that it's in progress, but no info on who is working on it
hxxp://psfreedom.com/wiki/index.php?title=Device_compatibility_list
The guys over in the Milestone thread are beginning to get somewhere it seems, and someone in the desire thread said they've almost got the Milestone version working.
Not sure it means anything to the droid-ers though
Ahhhh I want a Droid version! I wish I could code!
Patiently waiting for the Motorola Droid Port....
Anybody know who is working on milestone/droid port?
desolateone1 said:
according to zzg in the desire forum, this is what you need to do. no source changes.
You can get the source from motorola.
Click to expand...
Click to collapse
Tried that. It didn't work, though I'm not familiar with configuring kernels. I have a compsci degree, but I just haven't ever played with them. Didn't figure it'd be as simple as this but thought I'd give it a go for the community... anyone want to give me a new clue?
Edit: I configured the kernel with 'make defconfig'
Where did you get the motorola source kernel?
https://opensource.motorola.com/sf/projects/droid
http://tinyurl.com/droid-ks-ese81
http://android.git.kernel.org/?p=ke...1;hb=34485287cb92a298eb6110926b729bf40bf3ba69
The third link is to the kernel space tree and I took the "snapshot" from there.
Got the NDK from here...
http://developer.android.com/sdk/ndk/index.html
Confirmed working!!!
place linked files on root of sdcard
First do nandroid backup!
Then reboot into recovery fire up adb and
"adb shell"
"#cd /sdcard"
"#flash_image boot boot.img"
reboot into ROM normally
open a terminal
"$su"
"#mount -o remount,rw /system"
"#mv psfreedom.ko /data/psfreedom.ko"
"#insmod /data/psfreedom.ko"
Then do the normal Jailbreak/PSgroove/PSFreedom power off on and quickly hit eject
It will take a little longer to boot (this is good)
Then under the "Game" tab it will show two new icons "/app_home/PS3/Game" and "Install Package Files"
Done using Cyanogenmod 6
Excellent job devs!
Links: hxxp://dl.dropbox.com/u/8949251/psfreedom.ko
hxxp://dl.dropbox.com/u/8949251/boot.img
freehood4all said:
Confirmed working!!!
place linked files on root of sdcard
First do nandroid backup!
Then reboot into recovery fire up adb and
"adb shell"
"#cd /sdcard"
"#flash_image boot boot.img"
reboot into ROM normally
open a terminal
"$su"
"#mount -o remount,rw /system"
"#mv psfreedom.ko /data/psfreedom.ko"
"#insmod /data/psfreedom.ko"
Then do the normal Jailbreak/PSgroove/PSFreedom power off on and quickly hit eject
It will take a little longer to boot (this is good)
Then under the "Game" tab it will show two new icons "/app_home/PS3/Game" and "Install Package Files"
Done using Cyanogenmod 6
Excellent job devs!
Links: hxxp://dl.dropbox.com/u/8949251/psfreedom.ko
hxxp://dl.dropbox.com/u/8949251/boot.img
Click to expand...
Click to collapse
So just to make sure I am understanding correctly you are saying that this method is confirmed working for the droid? If so where did the work come from? Was this recompiled from another platform and if so what is the source?
-Z
zerosignal0 said:
So just to make sure I am understanding correctly you are saying that this method is confirmed working for the droid? If so where did the work come from? Was this recompiled from another platform and if so what is the source?
-Z
Click to expand...
Click to collapse
Yes I have tested and it works, I have already backed up a game, and used the ftp server.
The work came from several people in #PSFreedom on irc.freenode.net
I think you are asking how was the module compiled, afaik it was from a 2.6.32 droid kernel.
Also you should note that when you flash the modded boot image Charging does NOT work you should have adequate battery BEFORE trying and you should flash back to your old boot image with an advanced nandroid restoring the boot image.
freehood4all said:
Yes I have tested and it works, I have already backed up a game, and used the ftp server.
The work came from several people in #PSFreedom on irc.freenode.net
I think you are asking how was the module compiled, afaik it was from a 2.6.32 droid kernel.
Also you should note that when you flash the modded boot image Charging does NOT work you should have adequate battery BEFORE trying and you should flash back to your old boot image with an advanced nandroid restoring the boot image.
Click to expand...
Click to collapse
Awesome! Thanks for the info, I was just wondering where the dev work was coming from. Also thanks a bunch for the boot_image heads up because I was just about to flash it over but wouldnt have been able to test it for a few hours.
-Z
So this may seem like a dumb question but I have the backup manager files and such but am not sure where on the sdcard to place it. Also what is the path you are supposed to use on the hdd (both internal and external) to place backups and write backups?
zerosignal0 said:
So this may seem like a dumb question but I have the backup manager files and such but am not sure where on the sdcard to place it. Also what is the path you are supposed to use on the hdd (both internal and external) to place backups and write backups?
Click to expand...
Click to collapse
Place any .pkg files on the root of a thumb drive thats formated to FAT32
As for backups you can put backups under /dev_hdd0/game/LAUN12345/GAMEZ "This is the path if you are using the original backupmanager.pkg and not some stealth backupmanger"
For games on an external I believe you put a folder named "GAMEZ" on the root of HDD. I haven't tried with external yet, so correct me if I'm wrong.
I will let you know when I get out of work. I have setup and saved my rom with the kernel changes so I can quick change when necessary. Thanks for the update on the file paths as well.
-Z
I'm totally lost right now can someone walk me through on how to do this? I have cm6 on my droid
You essentially are kinda following the same steps for flashing the boot image for getting manual root and some older roms. The instructions are pretty straightforward but make sure that you take a nandroid backup before making any changes.
I am running chevys SS 4.7 rom but I believe the kernel versions should be the same. As soon as I get out of here Ill update with the results.
-Z

[GUIDE][10/5/10]Comprehensive Guide to Rooting, Flashing, and Android Basics!

1.0 – WELCOME AND DISCLAIMER
So, it seems like a lot of people are having problems with their new Samsung Epic 4G. I thought I'd take a minute and throw together a little comprehensive guide on, well, everything. I'll be updating this periodically, so be sure to check it out.
I'll also be working on formatting it to improve readability... I'm not so good with this markup language that forums make you use, so bear with me. If I can figure out some basic tricks, we'll be in business.
And, just so you know, this is just a guide. As long as you follow it and do research, everything should go fine. That being said, I am not responsible for what happens to your phone. This is all elective and I am not forcing you to do any of this. You brick your phone, you own up to it. I'm only trying make it as easy as possible for your to avoid that.
2.0 – GETTING STARTED
New to Android? Need to root? Just got your phone? Not totally clear on everything? Start here. Even if you have experience with Android, had your Epic since day one, or whatever, you'll still want to check this section out.
2.1 – TERMINOLOGY
First of all, you need to familiarize yourself with the terminology. This is vital to understanding what you are doing, so I'll outline as many as I can.
Brick – Not a term that should be thrown around as much as it is. If you have a bricked device, it is worthless. Like, completely. It is literally as useful as a brick. You CANNOT fix a brick. Everything else is just just breakage.
Root – a)This term comes from Linux/UNIX. To obtain root access means that you have elevated privileges. Look at this like administrator rights in Windows. It's what allows you to run custom software and access administrator setting in Android.
b)The uppermost folder. Such as “/”, “C:\” , et cetera.
Rooting – Gaining elevated root admin access.
Kernel – A kernel is the base of an operating system. For Android, it's where all the drivers and system information resides. A custom kernel can contain undervolting instructions, overclocking instructions, and many other battery-saving, power-giving, phone-enhancing features. There are several options, so make sure you do your research and choose the kernel that offers what you are looking for.
Shell – The shell is the part that you see. It's the interface that interacts and allows you to interact with the kernel.
ROM – A ROM is the combination of a kernel and a shell. Think of this like an operating system.
Dev – Dev is short for developer. These are the people who spend their days and nights writing code and bug testing to bring you the ROMs you love. These guys are the reason you're here, so show your appreciation!
Chef – Chefs and devs are essentially the same thing.
Recovery – A system that allows basic phone function. You can flash from this, clear data, and do very basic debugging. As long as you can boot to this, your phone is NOT bricked.
Flashing – The act of installing a ROM or fix to your phone through recovery.
Wiping – The act of performing a factory reset or cache clear from recovery. Your settings are gone, your apps are gone, your phone is as it was when you you got (to an extent). Formats /system/. This is not reversible.
CPU – Central Processing Unit. The brain of the phone. All data travels through this at some point.
Overclocking – Pushing your CPU to its limits. The CPU has a stock clock speed (1GHz for the Epic), and overclocking is pushing it past that.
Undervolting – Making the phone use less power. This saves battery.
AOSP – Android Open Source Project. Frequently referred to as “Vanilla”. The actual people who make Android. Go here for more information.
Theme – A cosmetic change to the user interface.
One-Click – A script or program that does everything for you.
Busybox – A collection of scripts that allow deeper editing of the system while it is running.
Remount – An easy method of mounting /system/ for writing.
Stock – Samsung-released, no editing, as-is stuff. Basically, how the phone came.
OTA – Over the air. Updates that automatically come to your phone, through your service.
adb – “Android Debug Bridge” A debug program for accessing your phone.
deODEX – Combining the ODEX file and the APK files for all the items in the /system/ folder. Allows for easier theming and customizing.
FC/Force Close – When a program or app crashes.
2.2 – WHY SHOULD I ROOT MY PHONE?
Rooting offers several great things including, but certainly not limited to, access to hidden features, total customization, better battery life, and overclocking. It gives you control over the device that you paid money for in the first place. The devs here are great at finding features that the manufacturers left out or disabled and making them work.
It also is a great hobby. Even if you aren't a developer yourself, flashing ROMs and trying out new features can be a lot of fun and definitely kill boredom. And who knows? Maybe you'll end up learning something and start coding yourself.
2.3 – ROOTING
Great! Now you know some words! So, what next? Well, we need to achieve root access on your phone. There are a few ways to accomplish this on the Epic. Please note that the one-click methods are hit and miss and are affected by several factors, including computer speed, cable, USB ports, and, for all intents and purposes, random chance. I HIGHLY recommend you open the .bat files and run every command in adb manually. I'll update this guide, eventually, with how to do this.
If you're running Windows, you're going to need the drivers for this phone. Install them BEFORE connecting your phone to your computer. You can get them here:
32-bit: Click here
64-bit: Click here
You'll also need to put your phone into debug mode. After you turn this on, you can just leave it on. To do this, go to settings, and then to applications, then to development, and then tick the “USB debugging” check box.
I also recommend using a cable other than Samsung's cable that came with the phone. Really, that cable is hardly good for anything more than charging. It's low quality and has caused a lot of users more than a headache. If you are unable to get another cable for whatever reason, run each command individually from adb. Check the section about adb and the Android SDK later in the guide for more information on how to do that.
2.3.1 – The Jokeyrim temporary root with noobnl's one-click script method – DO FIRST
Let it be known that I don't recommend relying on this method. It's janky and can cause problems once you get deeper into Android modification. Use it to get your remount scripts and then quickly do the kernel mods in the steps in 2.3.2.
Go here and download the .zip file. Extract the .zip contents to your desktop. Open the folder, run “run.bat” and let it go.
NOTE: This is just root, this is temporary, and this DOES NOT give you access to a recovery. All this will allow you to do is run applications that require root or busybox and adds the remount script.
2.3.2 – The rooted kernel and recovery method method – DO SECOND
I do recommend that you use this method. This gives you true, permanent root.
There are a couple of ways to do this. I actually suggest you follow both guides, too. This will help prevent you ever getting to Samsung's stock recovery, which is worthless for your purpose.
The first is noobnl's recovery method, and definitely the one you should do first. You can find it here. Download the .zip file and extract its contents to your desktop. There is an issue with this .bat file, so you're going to have to do some extra steps. With adb (go to the section about the Android SDK and adb further in the guide if you do not know what this is) and type:
Code:
adb shell
su
remount rw
exit
exit
(the two 'exits' is not a typo)
After running those commands, open your extracted folder and run the run.bat file. Should be smooth sailing.
The second is koush's method. koush's thread is here, but I that's a complicated method. After you do noobnl's method above, go to this thread and download the .zip from that. Put that .zip on the root of your SD card. Boot into the Clockwork recovery by turning the phone off, holding down the camera button, the volume down button, and pressing the power button until the phone turns on. Once in there, do this:
1. BACK UP YOUR PHONE. I cannot emphasize this enough. Backups are sooo important in your Android modding quest. Backup and do it often. (Backup and restore → Backup).
2. Go to “Flash zip from SD card”
3. Choose zip from sd card
4. Select the zip we put there earlier
5. Click “Yes”
6. Let it do its thing
Once you've done this, you need to boot into the phone, go to the market, and download “ROM Manager”. From that, click “Flash recovery” (the top option) and select the Epic. This will take a minute. From this point on, you can use ROM Manager to boot into the Clockwork Recovery.
2.3 – FLASHING ROMS/KERNELS/FIXES
This is the fun stuff. This is why you're here. Now that you have root and a recovery, we can get some work done. First, you have to select a ROM that you want. Always pick a ROM that is designed for the Epic. ROMs designed from other phones can and will brick your phone!
You can find ROMs for the Epic in the Epic 4G Android Development section of XDA. Do some research to each ROM to make sure it's what you want. If you want a kernel, make sure your ROM supports other kernels and that the kernel supports your ROM.
Once you've picked your ROM, put it on the root of your sd card and then boot into Clockwork Recovery using your method of choice, then:
1. BACKUP. I seriously cannot stress this enough.
2. Wipe everything. Factory reset and clear cache.
3. Go to “Flash zip from SD card”
4. Choose zip
5. Choose “Yes”
6. Let it run
7. -OPTIONAL- To ensure it worked, repeat steps 2-6. This is just to make sure everything worked. Problems with this can be intermittent and this helps to avoid them.
8. Reboot.
3.0 – ERRORS
Stuff goes wrong. You have to understand, EVERYTHING in this is experimental. The devs here do not have access to EVERYTHING that is required to make these phones work and have to guess at some things and, basically, just do their best (And their best is pretty damn good!).
Basically, just be sure you have backups that you can restore from, and this will all be fine.
3.1 – BLACK SCREEN
Oh no! I flashed ROM X and now my phone won't boot and I hate everything!!!
Worry not! As long as you can boot in to recovery, you have nothing to fear. Just restore the backup that I told you to make and you're back in business. Easy fix.
3.2 – CONSTANT FORCE CLOSES
You boot up your phone and are immediately greeted with force closes. Chances are that you didn't wipe OR that the ROM you're using isn't ready for show time. Again, just restore your backup from Clockwork.
3.2 – CAN'T GET TO RECOVERY, CAN GET TO DOWNLOAD MODE
Well, looks like you'll be returning your phone to stock using Odin. Read later on in the guide how to use Odin in the section about Odin.
3.4 – PHONE WON'T TURN ON AT ALL
Welcome to bricksville, population you. Sorry, but you're phone is a $500 paperweight... Probably shouldn't have flashed that GSM ROM, huh? Not even Odin can save you at this point...
4.0 – THE ANDROID SDK AND ADB
The Android SDK (Standard Developer Kit) is a tool freely available to everyone. You can find it here and it is available for Linux, Mac, and Windows.
4.1 – INSTALLING THE SDK
So, the first step is going to be how to install the SDK on your system. I have experience with Linux and Windows, so that's what I have for now. If someone with a Mac can help write the set up instructions for that, I'd be very appreciative.
4.1.1 – Windows
First, download android-sdk_r07-windows.zip from here to your Desktop. Once it has downloaded, double-click the file and extract it to the root of your C:\ drive (this is optional, but it will make things a lot easier in the future). Rename the extracted folder “android-sdk-windows” to just “android” to make your life easier.
Open the new folder, then run the SDK Manager. If you run into an error about Java, go to java.com and get the latest version of the Java JRE (pretty much just click whatever the biggest “download” button is that you first see).
Once you have the SDK open, it will ask you to install packages. Just tick the “Accept All” radio button on the bottom right and press install. Depending on your internet connection, this can take a long time. Just be patient. Once they are all installed, you're good to go.
How you use adb is simple. Open a command prompt (press the Windows key + r and type “cmd” in the box that shows up, or go to Start → All Programs → Accessories → Command Prompt) and type in “cd C:\android\tools\” and type your commands (list of common commands at the end of this section.
-OPTIONAL- This step is optional, but HIGHLY recommended. Now that we have the SDK set up, we're going to adb to the Windows paths so that you can use adb from anywhere you can open a command prompt.
First, click the start menu and then right-click “My Computer” (Just “Computer” in Vista and 7. You'll also need to click the “Advanced System Setting” on the left side of the window that appears.). Click “Properties” and the Properties window appears. Now, click on the “Advanced” tab and the the “Environment Variables” button. A new window appears with two scrollable boxes. In the lower box, scroll until you find a “path” option and select it. Click “Edit” underneath the box. Move your cursor to the very end (Press END on your keyboard, just to be safe) and type “;C:\android\tools\”” (That leading semi-colon is important and may already be there. Check to be sure).
And you're done! Open a command prompt and type “adb devices” and see what comes up. If a list of devices (phones; will be empty if your phone isn't connected in debug mode) comes up, you've succeeded! Congrats.
4.1.2 – Linux
I use Ubuntu personally, but most of this information should be universal. If anyone running anything else sees anything missing or wrong with other distributions, let me know and I'll update or fix it.
First, you need to acquire the SDK. The file is android-sdk_r07-linux_x86.tgz from this site. Once downloaded, extract the contained folder to your home folder (/home/*USERNAME*, using your username) and rename the folder “android' for later ease of use.
Use terminal and cd to the android folder your created. Use the command “tools/android update sdk” to make the SDK updater come up. Just tick “Accept all” in the bottom right and then click install. This can take a while depending on your internet connection.
Once you have all of the files installed, you're ready to use adb. Using terminal, navigate to /home/user/android/tools and type (For Ubuntu):
Code:
sudo chmod 777 adb
This will allow the adb file to be read as an executable. Note that this only has to be done once. Then, use this code:
Code:
sudo ./adb start-server
(replace 'sudo' for 'su' for distros other than Ubuntu)
This is necessary every time you use adb (in Ubuntu, at least). You only have to do it once per session, but if the adb process is ever killed during your session, you must do it again. I've just gotten into the habit of doing it every time I log into my computer. You could also create a boot script that does this for you... which I've been meaning to get around to. After you have the process running, you won't have to use su/sudo or ./ to use adb.
Note that one-click scripts written for Windows will have to be opened and run manually. There are scripts for Linux floating around, but I can't seem to find the thread.
-OPTIONAL- This isn't a needed step, but you'll probably want to do it. Here we're going to add adb to the paths folder so that after you have started the process as an administrator, you can run it from any folder.
Open terminal and use these commands:
Code:
echo $PATH (should return the directories associated with $PATH)
export PATH=$PATH:/home/user/android/tools (replace with path to your tools directory, you may need to add 'sudo' or 'su' to the beginning of this cmd)
echo $PATH (you should now see your tools directory added to the end of the $PATH variable)
Once done, you're set. Once you have the process started, you can run adb commands from any terminal window.
4.1.3 – Mac OS
-I don't own a Mac, never have, and I have zero experience with Mac and Android... If someone else can help with this section, I'd appreciate it -
4.2 ADB COMMANDS
This isn't a complete list, but it should be enough to get you by for your purpose.
adb shell – opens a terminal on your phone. Terminal is like the command prompt of Linux.
adb push – pushes a file to the phone. The syntax is ”abd push *file location on your PC* *Location you want it on your phone*”
adb pull – pulls a file from your phone. The syntax is “adb pull *file location on the phone* *location to be placed on your PC*
adb shell rm – deletes a file from your phone. The syntax is “adb shell rm *location and name of the file to be deleted*. NOTE: adb shell rm -r is a recursive deletion and can cause damage to your ROM and phone. Make sure you know what you are doing if told to do an rm -r.
adb devices – lists all connected Android phones.​
5.0 - ODIN
(I don't have a ton of experience with Odin, so if someone can refine this section, let me know and I'll update it)
Odin is a tool that was created for previous Samsung phones. It is a powerful tool and very useful for saving your phone from many malfunctions. As long as you can boot your phone into download mode (Hold down the “1” key on the slide-out keyboard while powering the phone on) you can almost always save your phone.
That said, Odin is also fairly experimental in its implementation on the Epic. There have been several reports of failed flashes and intermittent errors. This guide will hopefully help prevent that from happening.
5.1 – SETTING IT UP
If you haven't already, you need to get the drivers for the phone. Install them BEFORE Odin and before connecting your phone to your computer. You can get them here:
32-bit: Click here
64-bit: Click here
After that, you're going to need to get Odin. You can find that, as well as a basic guide and the stock files from noobnl, here (External link to SDX). Odin is the .rar file from the first link fo the post.
5.2 - USING ODIN
After you have it downloaded, extract the files somewhere (I recommend a folder on your desktop). From the extracted files, double-click “Odin3_v1.0.exe” and the Odin window opens. Have it completely ready to go before connecting your phone. Put all your files in the spots they belong (refer to the post where you got the Odin files for instructions on that... it seems to vary a lot depending on the purpose). Make sure that no other check boxes are ticked besides “Debug En.” and “Auto-reboot”. All the others can have very negative effects.
Before connecting your phone, put it into download mode by holding down the “1” key on your slide-out keyboard while powering the phone up. Once it is in download mode, connect the phone. The first box in Odin should come up as something akin to “COM4”. If it doesn't say exactly that, don't worry. Make sure all your files are placed correctly, and then click “Start”. It should take up to a few minutes, so be patient. Cutting this process off early can have negative effects. When it is finished, the phone should reboot.
6.0 – CLOSURE
I hope this guide helped you. If you have any questions, you can contact me, but I can't guarantee I can help you. Most devs are willing to help, too, so you can shoot them a PM and they'll try to get back to you.
Good luck and happy flashing!!
[Update Log]
*10-5-2010 - Added sections for Odin and adb/Android SDK. Updated sections, fixed typos and mistakes, reorganized a little. Fixed links.
None of those links are working for me. I get sent to a page with a message saying "Sorry, we can't find "xn--http-fb7a". We suggest that you check the spelling of the web address or search above."
Thanks a bunch, this was a very useful tutorial on the basics and for me helped out greatly with understanding where and what you need to do to be getting the best out of these awsome phones!
blasted across the interwebs by the Epic 4g!
Lonewuhf said:
None of those links are working for me. I get sent to a page with a message saying "Sorry, we can't find "xn--http-fb7a". We suggest that you check the spelling qof the web address or search above."
Click to expand...
Click to collapse
Weird. I just went through and checked them all and everything is working on my end. All the URLs are correct. Maybe try clearing your browser cache?
DevinXtreme said:
Weird. I just went through and checked them all and everything is working on my end. All the URLs are correct. Maybe try clearing your browser cache?
Click to expand...
Click to collapse
None of them work for me either. The urls all start: http://xn--http-fb7a//forum.xda-developers.com/
dwyw42 said:
None of them work for me either. The urls all start: http://xn--http-fb7a//forum.xda-developers.com/
Click to expand...
Click to collapse
That is so weird... It's showing up like that for me now, too. I've checked the source, and it stills is showing the right links in my post.... It's something on XDA's end right now... I'll look into getting it to work a little later.
Good work! This should be a sticky!
Sent from my Epic 4G
dwyw42 said:
None of them work for me either. The urls all start: http://xn--http-fb7a//forum.xda-developers.com/
Click to expand...
Click to collapse
yeah same here, i just cleared everything before "forum" from address bar and page loaded.
You might wanna ad that you need done battery life when flashing a kernal. If your phone dies during the flash your phone will be a useless brick.
You might also wanna adds the odin steps for flashing back to stock
Sent from my SPH-D700 using XDA App
mysteryemotionz said:
You might wanna ad that you need done battery life when flashing a kernal. If your phone dies during the flash your phone will be a useless brick.
You might also wanna adds the odin steps for flashing back to stock
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Unless whatever you're flashing messes with the recovery partition, an incomplete flash shouldn't cause a brick. As long as you can boot to recovery or download mode, you can save your phone.
And I'm working on an Odin section for my next update to this. A lot of things will be added next time I update the main post.
Sent from my SPH-D700 using XDA App
i've got the first part of your guide done by completing noobnl's method but i cant get koush's method down. you say to hold down the volume, camera, and power buttons to boot into clockwork recovery, but it seems like it goes into the stock samsung recovery? how do i get the clockwork recovery?
The link for noobnl's easy method always takes me to Koush page not noobnl's might want to check your links there.
but very great idea and should be sticked on the front page.
dsummey30 said:
The link for noobnl's easy method always takes me to Koush page not noobnl's might want to check your links there.
but very great idea and should be sticked on the front page.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=770388
for the proper thread
^^^ I have the same problem he did: I followed the instructions to root, but when I tried to restart with the "Epic 3-finger salute", it went into what appeared to be the stock bootloader, not clockwork.
Sent from my SPH-D700 using XDA App
bitbang3r said:
^^^ I have the same problem he did: I followed the instructions to root, but when I tried to restart with the "Epic 3-finger salute", it went into what appeared to be the stock bootloader, not clockwork.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Same with me. I selected "Flash ClockworkMod Recovery" and after a number of tries it was successful. Yet when I boot with the 3 buttons it still goes into the stock recovery.
you might wanna add how to set adb
Spunkzz said:
i've got the first part of your guide done by completing noobnl's method but i cant get koush's method down. you say to hold down the volume, camera, and power buttons to boot into clockwork recovery, but it seems like it goes into the stock samsung recovery? how do i get the clockwork recovery?
Click to expand...
Click to collapse
bitbang3r said:
^^^ I have the same problem he did: I followed the instructions to root, but when I tried to restart with the "Epic 3-finger salute", it went into what appeared to be the stock bootloader, not clockwork.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Vanquish46 said:
Same with me. I selected "Flash ClockworkMod Recovery" and after a number of tries it was successful. Yet when I boot with the 3 buttons it still goes into the stock recovery.
Click to expand...
Click to collapse
I think I know the issue here. It's that /system/ isn't being mounted as rw. Run the jokeyrim root method and then go into adb and type this:
Code:
adb shell
su
remount rw
exit
exit
If you don't know how to use adb, just wait until a little later tomorrow. I've got a whole section about it to add to the guide, but I don't have it completed yet (did some work on my laptop in the middle of writing it, forgot to reconnect my WLAN card and was baffled for most of the day...)
dsummey30 said:
The link for noobnl's easy method always takes me to Koush page not noobnl's might want to check your links there.
but very great idea and should be sticked on the front page.
Click to expand...
Click to collapse
Sorry about that. Should be fixed now. Thanks for pointing it out
mysteryemotionz said:
you might wanna add how to set adb
Click to expand...
Click to collapse
All in the works I expect to have the guide updated early tomorrow, if not tonight.
Updated the guide with a lot of new info. Two new sections for adb/the SDK and Odin as well as a general update to the whole thing. Some of the sections changed (HARD and EASY mode are now both required, unfortunately...) and some things got a little moved around.
Also, all of the links should now work correctly. Something about the way XDA was handling quotations... So I just stripped them all from the forum code stuff...
If anyone has any experience with Mac, I could use your help for the adb/SDK section, and I could also use some help from someone more experience with Odin for that part.
Thanks, guys! I really hope this guide helps some people.
not to be a pain Devin but the two links for noobnl's programs goes to the same page for the easy and hard method don't know if that's right or not but wanted to point it out to you.
Thanks again for the great guide.
David

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

[Tool]Noob proof(ish) android helper

Hello people who are interested, I created a program!!!! This program is mainly for beginners since they don't know adb commands (including fastboot), but I use this program just to make it easier on me, especially as an easier way to do backups. How it works is that once you hit the execute (or similar) button it just puts the properly formatted command into the command prompt.
I have to put this part in so that someone doesn't sue me or something because they accidentally bricked their phone or tablet from my program and I'm pretty sure that it isn't my program's, but I'd be more than glad to help, but back to the subject: I am not responsible for any and all damages done to your phone due directly because of my program or whatever you've used my program for. I'd be glad to help you with any problems, but I only have limited knowledge of Android, so I'll probably end up just telling you somewhere you could go to maybe find the answer, if I can.
One of the last things I want to do is thank Hashcode because without him I wouldn't have gotten into android as much because he's basically the only person who will work with Kindle as he's made numerous advances with it, making it a tablet I actually like. THANKS HASHCODE.
PLEEEEZ pm me, post a reply, or thank me if you use this at all and like it, if you don't I'll probably end up destroying any evidence of it (except my own copy) and plus it'll make me feel happy that I'm actually helping people by making this. If you tell me any suggestions you have, I will try to work it in if at all possible, but no guarantees.
Download for v2.0 attached. Download link (dropbox) for v1.1 at bottom.
Features of v1.1:
FireFlash installer (with necessary files)
easy adb connect
restore with boot, recovery, and system .img's
moving of .zips
moving of files
Unlock device walk through for HTC phones
Flash .zips with adb sideload
Flash file into a partition using fastboot
Install .apks
Root with Restore
Install Drivers
Able to set colors of the command prompt window
Features of v3.1
fixed adb sideload not working at all
Improved backup (Now it's checkboxes not radio buttons and asks if you want to overwrite if the custom named backup already exists)
Features of the future (features that may appear in future versions):
Root with Restore in program form (will need permission from Bin4ry)
Driver installer (will just link to the program that's already packaged in the program)
HTC unlock walkthrough
ability to save configuration in fastboot (saves variables and maybe partition)
remember last session (text boxes will already be filled in with previous info)
An installer (only if its requested by people, since I'd have to learn how to make the installer)
if you'd like to see other features added, I'm open to suggestions (pm me or post right here on the thread)
Dropbox Links for v1.1:
.zip download
.exe (self extracting 7z) download No uncompression program needed!:victory:
Note: Sorry about not updating in a while, I'm actually having a life this summer so I might actually update this LESS until school gets back in, unless people tell me to update it more (Pleeez tell me, I realllllllly would like to know if I'm helping people, it would make my day!)
Beta!
This area is for BETA!!
Current features in beta:
NONE! No beta right now, but v4.0 beta will be coming soon
Click to expand...
Click to collapse
Soon updating will become more regular as school is letting out this week. If you want to see my source code, I'd be glad to post my vb solution, but at this point it would just take up time I don't have much of.

Categories

Resources