Hey everybody -
Seems folks are wanting some sort of cwm recovery flashable twist on the i577 stock ICS rom that was first posted here, but is also discussed here and can be attained in an easy one-click odin fashion from here thanks to thomas.raines. Well, I think I managed to put one together. I don't know if I will tinker on this much, but you never know - I can't stop myself most of the time.
I AM IN NO WAY RESPONSIBLE FOR ANYTHING THAT HAPPENS (GOOD OR BAD) AS A RESULT OF FLASHING OR ATTEMPTING TO FLASH WHAT IS POSTED HERE!
The process to get here was rather simple (though the updater-script editing was rather annoying). After flashing via thomas.raines's handy dandy odin 1-click tool, I got a system dump. Originally I was just going to open up the system.img.ext4 and get what I needed from there, but I did it this way to figure out some permissions and symlink issues I was having with the updater-script. I then went through and deodexed, debloated, added in busybox, added in SuperSU, and made one small smali hack to Contacts.apk to stop a rather annoying insistence on checking AT&T subscriber crap every time you went into contacts. That's it - so this is not really all that "developed" or anything. All that is contained within the cwm zip is the same stuff that is contained in the one-click - it's just /system and boot.img (kernel) - nothing more (i.e. this does NOT change your modems). That all being said, let me know if things work, or if any oddities come up. Also feel free to comment on how this might improve or if I've gone about anything in a not-so-smart way.
Usual rules apply - make sure to wipe data/factory reset to avoid issues. Flash in CWM recovery.
CWM Installation instructions:
- Backup your current setup/data
- Download file and place on sdcard
- Boot into CWM recovery
- Recommended to wipe data/factory reset in CWM recovery
- Select and install the .zip you put on your sdcard
---DOWNLOAD LINKS - CWM---
Debloated deodexed rooted busybox-ed i577 stock rom and kernel
md5: 5645D032DA35923A9B00F15539D06AEA
---OTHER DOWNLOADS---
i577 ICS Deodexed System Apps
NOTE: This IS NOT CWM RECOVERY FLASHABLE!!!
md5: AC0171AD8010E54FDD7C25D33CA576B3
Empty SystemApp Flasher
NOTE: MUST place apks in the app folder within the system folder inside the zip file PRIOR to flashing
NOTE2: This is the same as what is linked in the Tweaked OP here - which is fine. This works on any blaze setup when using cwm recovery.
md5: F5B562DFCED08D8F55E5CF5EDF4DB444
Let me know if there are any problems! Also - it seems like general discussion should get pointed to here, as it's all the same thing really (read: I didn't think it warranted a new thread).
THANKS GO TO -
j3r3goss - initial letting folks know of i577 possibility and providing a link to a stock tar
2vivid and afoster1003 - bravely flashing said stock tar
thomas.raines - making things one-click easy, both to flash the rom and to return to gingerbread; helping with troubleshooting
2vivid and chjema - testing my attempts
erikmm - because I can
all of the folks in #teamfah-q
all of the folks in teamsbrissenmod, as I would know very little and be able to do even less if it weren't for them
-----------------------------
---CHANGELOG---
Final update - 10/2/12
- Somewhat fixed camera.apk
***** Viewer still appears upside down for rear camera, but all images/videos taken are correct orientation
- Changed stock boot animation
- Updated some apks
Initial Posting - 10/1/12
- Deodexed
- Took out lots of what I call bloat
***** If I took out something you wanted, use the links in the OP to get it back
***** If I left something you didn't want - let me know and I'll think about removing
- Added in SuperSU v0.96 by Chainfire (from here)
- Added busybox 1.19.4 (CM9)
- Edited Contacts.apk to avoid AT&T Subscriber checking when entering Contacts
- Added .bak to PowerOn.ogg in /system/etc/ to eliminate boot sound
-----------------------------
NOTES
Known issues:
1) Camera is upside-down
This only affects the rear-facing camera. The recent "fix" does not change the preview/viewer (the "live action" view of what the camera sees), but now all pictures or videos you take will be right-side up - so it's better than nothing I suppose
2) Softkeys/capacitive buttons no longer work
This seems to happen from time to time (though not very often by any means), in a way/manner that is as of yet predictable. That being said - all three times I have encountered this issue the below process has fixed it (thanks go to j3r3goss for providing the info needed for the solution):
- Open dialer/phone
- Type in the following in the dialer
*#*#2663#*#*
- Once the last * is entered, a new screen will show that has some information and (more importantly) two buttons. Press the BOTTOM buttom (the one that says "Touch key FW update"). Wait for this to complete (NOTE: This can take a LONG time, and you may have to reboot on your own if it hasn't said its completed its process after 10 or so minutes (my experience - no reasoning or logic behind it really, so be cautious)), then reboot the phone.
3) No WiFi Calling ability
Yep. It's an AT&T stock rom, and as they don't have the wifi calling capability, so too does this lack such fun functionality.
Reserved for something... not really sure what though. Figured I should grab it in case this little thing grows in the future - better safe than sorry I suppose.
confirmed flash good, no softkey issues
great job!
Good job man! Going to flash this tonight and make a 1 click for you with some Lightning Zap! goodies and modems (if it all works right...lol)...
saving this for later
Running great so far, definitely a lot snappier on first boot. No errors so far, glad the contact bug was fixed
There sure was a lot of bloat huh? I thought Tmo was bad lol.
Well I guess you beat me to it, way to go.
Sent from my SGH-T769 using xda app-developers app
I heard the radios were a little weak. Did you fix that in this file or is it the same?
Sent from my SGH-T769 using xda app-developers app
There are no radios included, so you keep whatever you had (and the blaze ones do seem a bit better than the exhilarate ones)
I just flashed, loving it btw, but my radios are a little weak? I factory reset, flashed the rom, factory reset again because it said to do so before reboot (idk I was a little paranoid lol) and then flashed system apps and boot.
Edit: i didnt realize earlier but all the bloat and such is remaining too? I'm gonna reflash in a bit and get back to you
Sent from my SAMSUNG-SGH-I577 using xda app-developers app
Push this apk to system to get weather working on lockscreen
WiFi calling should be able to be integrated into the ROM. It's not kernel specific, but might require some framework alterations. IMHO, it would be best to take this new ICS kernel and pair it with the OS from SGS2, that is made for T-mobile.
I haven't gotten a chance yet to look at the kernel to see if the flipped camera can be fixed there, or if just replacing it with the SGS2 camera app might do the trick.
Lots of opportunities for hacking together a great ROM from this.
Concerning the radios guys and gals!
It seems to be an ICS thing with the radios. We had the same issue on the SGS4G. They have to be padded in order to function properly since the SGS4G never got an official ICS update and we are still running on gb modem and kernel... Maybe Sammy will un-ass the update for us and all will be good...lol
thomas.raines said:
Concerning the radios guys and gals!
It seems to be an ICS thing with the radios. We had the same issue on the SGS4G. They have to be padded in order to function properly since the SGS4G never got an official ICS update and we are still running on gb modem and kernel... Maybe Sammy will un-ass the update for us and all will be good...lol
Click to expand...
Click to collapse
Yeah, I use to have a G2x with ICS and the developers always made it clear that the Radio issue is a problem with ICS 4.0.4 itself.
Sent from my SGH-T769 using xda premium
chjema said:
Push this apk to system to get weather working on lockscreen
Click to expand...
Click to collapse
how do you push it to the system? every time I try it just says it has failed
crazydrummer95 said:
how do you push it to the system? every time I try it just says it has failed
Click to expand...
Click to collapse
How are you trying to push, via root explorer (something alike) or adb?
thomas.raines said:
How are you trying to push, via root explorer (something alike) or adb?
Click to expand...
Click to collapse
Well, I tried using ES file explorer and it did not work. So I went into the root settings in the application, and I have everything checked, but when I try to mount the filesystem as writable, it says "failed to mount". I tried setting it as rw in adb, and it said it was a read-only file system
Es never worked for me with the root functions. Always has to use root explorer or adb
Sent from my SGH-T769 using xda app-developers app
skullreapper66 said:
Es never worked for me with the root functions. Always has to use root explorer or adb
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
But the problem is that everytime I try to push a file to /system in ADB it says that its a read-only file system
Related
..::Team Viper Official Sites::..
Team Vipers Official Site
Team Vipers Official Wiki
Team Vipers Official Ticket System
--------------------------------------------------------------------------------------------------------------
Rodderik's 1.2GHz Overclocked Kernel
Genocide_1.2GHzOC_EB13_Kernel_v0.2a.zip
Genocide_1.2GHzOC_EB13_Kernel_v0.2a.zip Mirror
Give Rodderik a thanks and buy him a beer, He paved the way for the Kernels with the first OC!!
--------------------------------------------------------------------------------------------------------------
..::Thanks::..
Thanks to ACS for the DK28 leak. Thanks to mysteryemotionz for some of the images.
--------------------------------------------------------------------------------------------------------------
..::Changelogs::..
ViperROM [TRiNiTY v2.0] EXT4-RFS DK28 Dual 4.0.4
Added New Theme
Added ViperWheelWidget - Custom Viper Widget
Added ViperPad - Custom Viper App Pad (Based of the Palm's SwipePad App)
Removed A Few Scripts Causing Issues
Returned The Artificial Intelligence Sounds
Added TTS Back Into The ROM
Google Nav Works Again
New Boot Animation
Governor Killer Baked In
AOSP Lockscreen Added
Added New App Icons
Moved Data/Tweaks To System/Bin/Tweaks
Optimized More For Speed & Battery
Changed Browser Start Page - Team Vipers Official Site
Added Wallpaper, Wifi Tether, And Launcher Pro To SDCard (VIPERaddons)
Modified Hosts File
Modified Build.prop
Modified Android.policy.jar
Modified MMS.apk
Themed Dialer
Modified SettingsProvider.apk To Always Allow 3rd Party Apps Install
Added ViperComm Widget
Modified A Lot Of Images
New Sounds
ViperROM [FRoZeN] EXT4-RFS DK28 Dual 4.0.3
New Theme
New Shutdown Animation
New Transition Animations
Removed Some Scripts
Added Data/Tweaks
Governor Killer Baked In
Added A Few New Scripts
Modified For Speed
Modified For Battery Life
New Boot Animation
Custom Sounds - By Team Viper
--------------------------------------------------------------------------------------------------------------
..::ROM Downloads::..
ViperROM [TRiNiTY v2.0] EXT4-RFS Dual DK28 4.0.4
ViperROM [FRoZeN] EXT4-RFS DK28 Dual 4.0.3
--------------------------------------------------------------------------------------------------------------
..::Videos::..
ViperROM 4.0.4 Benchmark Scores
ViperROM 4.0.4 Features
--------------------------------------------------------------------------------------------------------------
..::Screenshots::..
COMING SOON!
SDCARD Partitioning Tutorial.
I know that with EXT4, partitioning the sdcard can be a hassle. Here's a little workaround to help you get it partitioned the easiest way I know without having to mount systems and such in Terminal Emulator. This way makes you flash 2 seperate recoveries, but I would rather do this than the other methods which could take upwards of a half hour or even longer. I've seen people that were working on it for a couple hours. Without further adieu:
NOTE: If you are running RFS, just follow step 1. and you'll be done. If you are running EXT4, skip right to step 2. and follow from there.
1. If you are running RFS, then you do not need to follow any other steps. In the green CWM2.5.5 recovery, just go to "advanced" in recovery and choose the Partition option. It's going to give you two questions for sizes that you want. The first size is going to be the ext size. For this it will give you a few options, but I don't recommend choosing anything below 512. You will see all the options when they pop up, just choose what you feel most comfortable with. The next thing it's going to tell you to select is the swap size. I again don't recommend choosing anything below 128 for this option. You will again see a list of options, so choose what you feel most comfortable with.
2. If you are running EXT4, then follow these steps and you'll be up and running with your new partition very soon. First thing you need to do is gather all the tools you're going to need. Here are the list of tools you will need:
A. One Click Root & Recovery 2.5.5
B. One Click Root & Recovery 3.0.0.6
Quite the long list huh? lol ...I told you it's gonna be simple lol.
Download both of these files (if you don't have one or the other already) and extract them to an easy to find location on your computer somewhere.
3. Ok, you're going to do this just the same as you would if you were rooting your phone from a stock state. And to answer your question that's running through your head right now, No, this will not return you to RFS. You will still be on EXT4 the entire time, so there's not real need to backup your sdcard or worry about having to sit through the backup&restore again. Once again, to be very clear... Even though you are flashing cwm2.5.5 recovery, you will REMAIN EXT4. So let's continue. Make sure USB Debugging is on and plug your phone into your computer. Do NOT mount the sdcard, just have the phone plugged in. Open the One Click Root & Recovery 2.5.5, and run the program. When it's finished, your phone will reboot. Do NOT unplug it until the script is complete. The script will say "Operation Complete. Hit any button to continue" or something along those lines. Just hit a button and the script will automatically close. You can now reboot into recovery and you will see the 2.5.5 recovery with the green letters. If you don't have the green letters, then you didn't run the right One Click, and you should start over using the correct one lol . For those that successfully flashed the 2.5.5 recovery, move on to step 4.
4. If you have the green letters, then we'll continue, if not, repeat step 3. with the correct one click lol. Now that you have the green letters, revert to step 1. When you're finished following the same instructions from step 1, move on to step 5. If you have any issues with anything from step 1. (which you shouldn't, but if you do) click here to go to Mibbit's irc chat website. Along the top left side you will see 2 tabs labeled "Home" and "Connect". Make sure you are on the tab that says "Home". When on the tab labeled "Home", you will see the box in the middle of the page. Right beside the letters "IRC:" is a dropdown box. You're going to click on the dropdown arrow and select "EFNET". Next, you're going to enter your nickname, and finally, beside "channel:" type "#viper" and select "Go". That will bring you to Team Vipers chat where one of us will be able to help you.
5. Now that you are partitioned, it's time to restore the EXT4 recovery. If you do not restore the EXT4 recovery, you will not be able to flash any new ROM's or Kernels, so you MUST restore the correct recovery. To do so, you simply do the same steps. Make sure USB Debugging is turned on and plug your phone in. You do NOT need to mount. Now you simply run the 3.0.0.6 One Click Root & Recovery. Let it run through it's process and it will reboot itself. Do NOT exit out of the command prompt until it says "finished, press any key to continue". Once your phone reboots, you can then reboot into recovery and you will see that you have the orange letters again. When you see the orange letters, you now have a partitioned sdcard and you are back on the correct recovery.
**ONCE THE KERNEL IS RELEASED (Which should be within the next 24 hours as long as my testers don't see any issues) THEN MOVE ON TO STEP 6.**
6. Now that you're partitioned, the only thing left to do is flash the kernel. Connect your phone to your computer and copy the Kernel to your sdcard if you have not done so already. To flash it, just choose "Install zip from sdcard" followed by "Choose zip from sdcard" and simply navigate to where you stored it on your sdcard. That's all. It's quite quick and painless and you should be able to do it all within 10-15 minutes.
VIPERrom Store where everything is FREE!
**Cleaned up post 13 January**
**If you want mods and addons download viperstore from the market**
NOTE: stuff is still being ported to the new edify scripting required for clockworkmod 3.0.0.5 so if something doesn't work submit a ticket from our website and we will get it ported over as soon as we can. For now you can access the store's contents that have been converted here.
VIPERchat in your browser chat.efnet.org (enter your nickname and #viper for the channel name)
VIPERchat Downloadable Version VIPERchat.zip (3.38 MB)
Voice Apps were removed in 3.0.3 to save space but if you want them Voice Apps **UPDATED FOR NEW CLOCKWORK**
Stock Sprint Apps (install .apk like normal):
SprintDK28_Navigation.apk (5.6 MB)
SprintDK28_Nascar(updated).apk (385 KB)
SprintDK28_NFLMobile(updated).apk (510 KB)
SprintDK28_SprintTV.apk (879 KB)
SprintDK28_SprintTVWidget.apk (84 KB)
SprintDK28_SprintZone.apk (367 KB)
First to post on this thread besides u
But yea ill look into the link for you right now
if i find it ill give to u
Edit: Here is the link http://forum.xda-developers.com/showthread.php?t=724171
not sure if that will help will look for some more
Reserved.. always wanted to say that.
Nice and clean separate thread me like...
Do i sense a 3.0.1 update to be sweet! or is the current 3.0 this version?
Hi BT. Thanks for the great ROM. I am using 3.0 right now. What is the difference between 3.0 and 3.0.1? Thanks. Keep up the great work! And one quick question. When I try to install lagfix, everythiing works besides the last step, installing viperspeed. It says I cant install it because I dont have enough room. but I have 185MB free. any ideas?
Link? I hope it's not there or else I'll feel more jerky than usual. Oh and super-thanks for those file names on the battery mods, so important... I have a mess of files like GREENBATMODTHISTHAT with no versions or anything and I guess I didn't realize that I needed to keep mods organized by ROM.
azichek said:
Hi BT. Thanks for the great ROM. I am using 3.0 right now. What is the difference between 3.0 and 3.0.1? Thanks. Keep up the great work!
Click to expand...
Click to collapse
3.0.1 is just a new name for it so if we make updates there's less confusion... It's still the same as 3.0, but hopefully this will eliminate some questions in the thread lol.
3.0.1 = 3.0 ...No new updates yet.
BUT!!!
Rodderik did make the battery mods!, check them out!
azichek said:
Hi BT. Thanks for the great ROM. I am using 3.0 right now. What is the difference between 3.0 and 3.0.1? Thanks. Keep up the great work!
Click to expand...
Click to collapse
I think 3.0.1 is just the updated version of 3.0.
3.0.1 does have the aosp lock screen the 4g is fixed
and couple other things... At least that i think lol
Hope that helps
Added A2SD (Download Terminal Emulator, And type "start a2sd" followed by "launch a2sd" and it will back everything up on your sdcard)
Click to expand...
Click to collapse
Can you please clarify this for me, because I tried earlier and it gave an error when trying to install the terminal. Also I have used linux before but never used a terminal on a phone before lol...can you write down a few steps for us newbies
Again Thank you for your work and to your team
Hey BT there is a app called WidgerLocker Lockscreen which lets you put any widget/app i believe on you lock screen that might be helpful i think..
Just installed it and brought back the aosp lock screen might wanna check it out... Send me a pm of ur email so i can send u the apk cause its a paid app
Another quick question BT, what are the other options for in the lagfix? Are they for future upgrades or not necessary at all?
Hey BT I just want to thank you for all your hard work and your great rom. I hope this hasn't been answered but is it necessary to remove my original root before flashing any of your roms? I have flashed most all of them and I have not deleted it. I'm not having any problems with 3.0. Thank you....
hemi dart said:
Hey BT I just want to thank you for all your hard work and your great rom. I hope this hasn't been answered but is it necessary to remove my original root before flashing any of your roms? I have flashed most all of them and I have not deleted it. I'm not having any problems with 3.0. Thank you....
Click to expand...
Click to collapse
nope you don't have to...just wipe 3x, wipe cache 2x, and wipe dalvik cache ONCE and flash the rom then you are good to go (assuming you are using the correct modem and if not then flash it first with odin)
DAVenom said:
Hey BT there is a app called WidgerLocker Lockscreen which lets you put any widget/app i believe on you lock screen that might be helpful i think..
Just installed it and brought back the aosp lock screen might wanna check it out... Send me a pm of ur email so i can send u the apk cause its a paid app
Click to expand...
Click to collapse
Widget locker is good, I installed it and then moved it to system apps. Works perfectly
Sent from my frozen epic4g
neuton said:
Another quick question BT, what are the other options for in the lagfix? Are they for future upgrades or not necessary at all?
Click to expand...
Click to collapse
2.2 is for the vibrant, minfree is setting the phones task killer settings (I recommend doing this), restoring the boot animation gives you a new boot animation, you can set a schedule if you want, and of course all the uninstall options
Sent from my VIPERrom [TRiNiTY] DK28 3.0
BThomas22x said:
3.0.1 is just a new name for it so if we make updates there's less confusion... It's still the same as 3.0, but hopefully this will eliminate some questions in the thread lol.
3.0.1 = 3.0 ...No new updates yet.
BUT!!!
Rodderik did make the battery mods!, check them out!
Click to expand...
Click to collapse
Haha thanks for clearing that up. I also sent you a pm about a weird lag fix problem i'm having. Thanks BT. The ROM is great.
Rodderik said:
nope you don't have to...just wipe 3x, wipe cache 2x, and wipe dalvik cache ONCE and flash the rom then you are good to go (assuming you are using the correct modem and if not then flash it first with odin)
Click to expand...
Click to collapse
I have the correct modem and 3.0 is working great. I have tried most of the other roms and yours have been the best by far. I thank you guys for that.
When I restore data from cockwork it broke lagfix. Anywork around?
Sent from my SPH-D700 using XDA App
Bt, awsome work, wish I had you for a neighbor. Question, scince going to 3.0 my usb tether stopped working, is it not supported in 3.0 ?
Let's test this out...
Please only flash this if you know what you're doing, I don't have a GS4G so I can't test everything.
Some of the things I included
Based on Whitehawkx's & drhonk's KD1
KD1 Kernel
Bali 2.1UV Kernel
Trigger Theme
FUGU tweaks
EDT Init Tweaks (fixes permissions on start up / ram hacks / other tweaks )
Read ahead cache set to 2048kb
Custom startup/shutdown animations
Removed most bloat
removed startup sound (I think I left shutdown sound in...)
ZegoeUI Font
Nexus S sounds
Modded build prop
Removed T-Mobile tab from market
Included black themed market
Added WP7 Gingerbread keyboard
TWiz & EB Productions Gingerbread Launcher
Included a couple apps (titanium, rom manager, battery callibration, quickboot, spareparts)
Flashing Instructions
Please ensure this is what your mounts look like in CWM recovery. Or else it will not boot.
UNMOUNT CACHE
UNMOUNT DATA
MOUNT SDCARD
UNMOUNT SYSTEM
Click to expand...
Click to collapse
-flash ROM
-reboot
-then let the rom sit 10 minutes
-reboot
Fixes
I believe I fixed the permissions issue with 0.2_1, however just in case, here's the fix thanks to corradokng
Code:
adb shell
su (go to phone select allow)
cd /data
busybox chmod 771 /data/app
busybox chmod 644 /data/app/*
exit
Changelog
Code:
0.4
-inlcuded bali kernel (thanks drhonk)
--- this allows init.d to work which allows tweaks to be executed properly
--- also allows my permission script to run, it will fix your permissions every time you reboot
- no more FCs, all apps work on first boot
0.3_2
-settings restored (had the lockscreen one, causing issues)
-framework restored (same thing, left in the lockscreen one)
-both of these fixed the Mms crashing issue
-you must mount system, data, and cache for it to flash properly.
0.3
-fixed big & ugly quickpanel bar
-optimized version
-everything should work without having to mount /system /data and /cache, but it doesn't hurt :)
0.2_2
-fixed the fixed fixed permissions
-mounting in updater-script testing
0.2_1
-removed lock screens until we can get it working without FC in the browser
-updated version to display correctly
-fixed fixed permissions (??? let's hope!)
0.2
-fixed gingerbread keyboard fc
-re-added Samsung boot sequence so it's not blank (if you use a kernel that supports bootanimation.zip you will see the trigger one)
-added Corrandokng's port of Whitehawkx's lockscreens, power menu, & clock options
-fixed permissions on /data/app
-added Bloater, I will add apps in later (please don't try and download Vibrant apps, you may be sorry if you do and it doesn't play nice)
-added zipalign apps at boot (thank the darkyyrom team for their better zipalign script)
-added Trigger theming to dialer & settings
-removed some more bloat
Download 0.4 - Mirror
md5: 5D48D3CD58CFB5E63D64D66E614A656C
"Nightlies"
0.3 Bugs
-factory restore doesn't work in Settings
-have to uninstall apps that come with it for some
Oh shyt some ROM's rollin out!
birgertime said:
Let's test this out...
Please only flash this if you know what you're doing, I don't have a GS4G so I can't test everything.
Some of the things I included
Based on Whitehawkx's & drhonk's KD1
Bali Kernel
KD1 Modem
Trigger Theme
FUGU tweaks
EDT Init Tweaks
Custom startup/shutdown animations
Removed most bloat
removed startup sound (I think I left shutdown sound in...)
ZegoeUI Font
Nexus S sounds
Modded build prop
Removed T-Mobile tab from market
Added WP7 Gingerbread keyboard
TWiz & EB Productions Gingerbread Launcher
Included a couple apps (titanium, rom manager, battery callibration, quickboot, spareparts)
Download
MD5: 01AAE1B84D8389284E1AF07B05AD969F
PLEASE FOR THE LOVE OF GOD MAKE A BACKUP BEFORE FLASHING THIS
Please make sure you have some free time in case the flash doesn't go as planned so I can fix it and reupload it.
That said, please let me know your results
Click to expand...
Click to collapse
Bro gooooood stuff, ill test when I get back from the lake
This is what I'm talking about!!
Sent from my SGH-T959V using XDA Premium App
mikeDCMDVA said:
Oh shyt some ROM's rollin out!
Click to expand...
Click to collapse
don't flash this if you haven't yet... unless you want to odin, something dind't go so right
EDIT: need a couple of brave testers so I can iron the issue out
pm me/twitter me/irc (#einherjar @ freenode)
birgertime said:
don't flash this if you haven't yet... unless you want to odin, something dind't go so right
Click to expand...
Click to collapse
I haven't luckily!
This would be so much easier if I had the damn phone, lol.
Figured out the issue, kernel wasn't flashing properly. Uploading a new version
birgertime said:
This would be so much easier if I had the damn phone, lol.
Figured out the issue, kernel wasn't flashing properly. Uploading a new version
Click to expand...
Click to collapse
Great work bro, ETa?
richielasalsa said:
Great work bro, ETa?
Click to expand...
Click to collapse
soon as my tester says it works
birgertime said:
This would be so much easier if I had the damn phone, lol.
Figured out the issue, kernel wasn't flashing properly. Uploading a new version
Click to expand...
Click to collapse
Dude...your awesome...
Sent from my SGH-T959V using XDA Premium App
Sick bro thanks. Ill try when i get home from work
Sent from my SGH-T959V using XDA App
I traded my original SGS for the 4g...you just made my day with this thread...Can't test the phone because it is my daily driver and i have a full time job...Donation coming when you are finished. Thanks for your time.
eagerly awaiting for the ROM! Thanks again for your hard work!
Kernel still isn't flashing which is resulting in a soft brick. Not sure why.
Also. This rom is just some 7zip magic, nothing too serious, yet.
Sent from my SGH-T959 using Tapatalk
birgertime said:
Kernel still isn't flashing which is resulting in a soft brick. Not sure why.
Also. This rom is just some 7zip magic, nothing too serious, yet.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Ask krylon he a kernal beast
Sent from my SGH-T959V using XDA App
birgertime said:
don't flash this if you haven't yet... unless you want to odin, something dind't go so right
EDIT: need a couple of brave testers so I can iron the issue out
pm me/twitter me/irc (#einherjar @ freenode)
Click to expand...
Click to collapse
get me in DL mode and i'll test it out. tried to Odin my brand new SGS4G to whitehawkx KD1 with root and odin stopped responding. tried to restart the process but now i'm stuck at the phone-exclamation-pc logo. can't get into DL mode.
silverspoon80 said:
get me in DL mode and i'll test it out. tried to Odin my brand new SGS4G to whitehawkx KD1 with root and odin stopped responding. tried to restart the process but now i'm stuck at the phone-exclamation-pc logo. can't get into DL mode.
Click to expand...
Click to collapse
You don't need download mode for that type of brick. I'll quote robbbbit for the answer;
"just odin the *****"
It worked for me. Good luck!
Sent from my Galaxy S 4g onboard
a J22 with the spinnaker flying
silverspoon80 said:
get me in DL mode and i'll test it out. tried to Odin my brand new SGS4G to whitehawkx KD1 with root and odin stopped responding. tried to restart the process but now i'm stuck at the phone-exclamation-pc logo. can't get into DL mode.
Click to expand...
Click to collapse
try using odin from the pc ! phone screen
Are you still uploading a new version or did someone else report a new soft brick? Awesome work btw! My buddy has a sgs4g so I wanna try this out on his device. Trigger has always been one of my faves from the vibrant.
sent from CM7 powered Vibrant
aghoshhajra said:
Are you still uploading a new version or did someone else report a new soft brick? Awesome work btw! My buddy has a sgs4g so I wanna try this out on his device. Trigger has always been one of my faves from the vibrant.
sent from CM7 powered Vibrant
Click to expand...
Click to collapse
got hte kernel flashing but it's still not booting up
sometimes it is, sometimes it's not, gotta find out what's going on
you guys should make tmobile send me a phone
birgertime said:
got hte kernel flashing but it's still not booting up
sometimes it is, sometimes it's not, gotta find out what's going on
you guys should make tmobile send me a phone
Click to expand...
Click to collapse
i'll get a couple of my hit-men to bust a cap on their asses
First of all... Thanks Chainfire!!!! This is totally based on your work.... i made only some MOD....
Ok, the work is quite finished... the CF-ROOT for I9003 is ready!
I called this "beta version" (since i need your tests/opinions) but all might work.
IMPORTANT: This is only for KPH Firmware!!!
You can flash this over any other CWM or over the stock FW.
Many people will ask "Why i have to install this?"... because with this your phone will have:
- Root ( don't need to use SOC or any ZIP);
- Busybox 1.17.2;
- Sqlite3 v3.7.2;
- init.d support (you can put in the folder /system/etc/init.d all the script that you want to be loaded at the startup);
- New fixed CWM ( unyaffs issue has been fixed - offline charge fixed - USB storage mode while in CWM fixed);
- Add EXT4 support to the phone ( so you can convert the filesystem to ext4 to improve performance);
- full working CWM Manager (backup - restore - delete backup - install apk - flash update.zip - flash kernel - reboot to CWM);
- Tweaks Manager with various tweak ( Ram Min Free - SD Speed - I/O Scheduler - Kernel Scheduler - CPU Conservative Governor - Swappiness - Ram Script by Juwe11 - Media Stagefright)---> Many people asked for Juwe Ram Script ---> to enable it completely choose in the Tweaks Manager: Ram Script - Ram Min Free and Swappiness;
- Auto ZIP-Align on boot - You can choose it in the tweaks app(NEW)
- Reviewed tweaks values (some from darky's rom some from hardcore some from other post in XDA)( thanks to bigeyes0x0 and Misledz )(NEW)
- Custom Boot-Animation support (place your custom bootanimation in /system/media/ and call it sanim.zip)(NEW)
To do:
- other tweaks suggested by you...
- whatever can be added.
Let me know what you think
HERE you can find the original post.
HOW TO INSTALL:
1- Flash with Odin the .tar file
or...if you went from a previous version of CF-ROOT
2- Download the .zip file into the external SD the open CWM Manager --> flash Kernel --> select the file you have just downoaded
IMPORTANT:
If you cannot find the two apps on your app drawer maybe you haven't space left on /system so delete some unused apps like aldiko, delere /system/cfroot folder and reboot
IMPORTANT/2: after the flash the phone might take some time to boot. You might think that it freeze on Samsung Logo but it's normal cause the auto-zipalign proc need some time. Just Wait.
UPDATE: Added CF-ROOT with my custom kernel. This have Ext4 inside the kernel (no modules) and OC to 1.1 Ghz. I think that it is secure. I haven't test it very well so please report me the issues you will find.
!
Version 05.09.2011 Changelog:
- added Graphics Boost Tweak (thanks Gana)
- added acid tweaks (thanks to the people that worked on it .. specially Bigeyes0x0);
- reviewed 00tweaks file by Bigeyes0x0;
To disable journaling on ext4 partition apply the attached journaloff.zip in CWM (Not CWM Manager app - it must be fixed).
There're two version of the CF-ROOT, the version with **CWM_Manager** can be flashed with CWM Manager App (select flash kernel) the other with odin (like always)
UPDATE 20.10.2011:
CF-ROOT for XXKPM can be found HERE:
- Standard Version --> http://www.multiupload.com/S463K75UED
- Surprise version ( i suggest you this) --> http://www.multiupload.com/G20L6PL5WC
What's new ?
- I finally finished the custom bootanimation support.... now works like he have to works. Just copy your bootanimation into /system/media and rename it to sanim.zip.... i think that here you can find what you need http://forum.xda-developers.com/showthread.php?p=17322814#post17322814
IMPORTANT!!!
If you have installed the beta version you must know that the ext4 conversion for that doesn't work properly. Ok, system, cache and dbdata will be on ext4 but data not. This because the init binary check on boot if /data have rfs FS and, if not, it format the partition wiping all your data.
In the new version i modified the init binary so it cannot do it more
I must say that i became mad to discover this damn thing !
A few questions: Are you using the latest fixed version of CWM? Also you mentioned that you would be releasing another update soon regarding the Nandroid backup image corruption issue. Is it in this release?
Also: Is this an alternative to ROM manager, apart from the inclusion of the tweaker tool?
Regarding the enhancements, could you please elaborate on some of them and what is safe/not safe to use (particularly in the tweaks and what they do)?
What I understood, after looking over all the posts, was that you optimized the CF-Root by chainfire for the i9003, by using a compatible Root, CWM, and adding an ext4 kernel? Are you going to port the ext4 converter tool as well? Will we be able to use an external SD card with ext4 formatting (Could be used to store files larger than 4GB)?
Sorry about the ton of questions. Trying to learn, and what better way to learn than from the best!
I'm going to take it out for a test drive now on XXKPE with ext4! Will report back later!
Thanks for your valuable work, I'm a huge fan!!!
Cheers
Update: Confirming that the passive charging bug has been fixed! Thanks Skin1980!
I cannot find the CWM or Tweaks icons in the app drawer as indicated in your screenshots. I can access CWM recovery mode using the 3 button combo though.
I had installed the last version of CWM by Amit and formatted with ext4 and I just used ODIN to flash over that install. I tried flashing again, still not appearing in app drawer. Any solutions?
Great job skin.. Hoping for the early release of a stable one.. Will test it later
Sent from my GT-I9003 using XDA Premium App
it's great...>.<
Auguri! Ok wow, This is pure genius . I've always been wondering what our CWM were based off. I guess using this would fix most issues people get when flashing CWM, since it's based off the original firmware
Also I'm loving the tweaks, they seem to make the phone more smooth, Although I've seen a few bugs after applying this I can't seem to use the V6 charger script anymore I get an error, will be posting one shortly. There are some minor hiccups in between and I tend to get FC on some apps when I multitask.
Edit: Turns out It's busybox related, no shell access. I've tried launching Busybox by Stericsons to check and It says no root access was given and boots me out.
i happy that u r belong to this community
Is there any recovery module or tweak available, in which we can handle basic file operation like copy, move from sd card to system or any thing similar?
Erahgon said:
A few questions: Are you using the latest fixed version of CWM? Also you mentioned that you would be releasing another update soon regarding the Nandroid backup image corruption issue. Is it in this release?
Also: Is this an alternative to ROM manager, apart from the inclusion of the tweaker tool?
Regarding the enhancements, could you please elaborate on some of them and what is safe/not safe to use (particularly in the tweaks and what they do)?
What I understood, after looking over all the posts, was that you optimized the CF-Root by chainfire for the i9003, by using a compatible Root, CWM, and adding an ext4 kernel? Are you going to port the ext4 converter tool as well? Will we be able to use an external SD card with ext4 formatting (Could be used to store files larger than 4GB)?
Sorry about the ton of questions. Trying to learn, and what better way to learn than from the best!
I'm going to take it out for a test drive now on XXKPE with ext4! Will report back later!
Thanks for your valuable work, I'm a huge fan!!!
Cheers
Update: Confirming that the passive charging bug has been fixed! Thanks Skin1980!
I cannot find the CWM or Tweaks icons in the app drawer as indicated in your screenshots. I can access CWM recovery mode using the 3 button combo though.
I had installed the last version of CWM by Amit and formatted with ext4 and I just used ODIN to flash over that install. I tried flashing again, still not appearing in app drawer. Any solutions?
Click to expand...
Click to collapse
1- The CWM used is always the last... if i'll update the CWM i'll update the CF-ROOT;
2- The CWM fixed reguard nandroid backup is under test;
3- My CWM isn't ROM Manager compatible... with the CWM Manager from Chainfire you can do a lot of things without going into CWM
4 - to convert in EXT4 just follow the guide on the other thread;
5- Not sure if you can format in XT4 your external_sd... try ;
6- The tweak are all sure... now i haven't time to exlplain better... some don't work.... some other work.
7- If the icon don't appear in app drawer try to check into system/app if the two files are there... if not try to remove /system/cfroot folder and reboot. Maybe your system folder is full so you can install they manually, the original apk are inside /res/misc/ folder.
8- bye
for me wifi not working obtaining ip address,gps not lock can i flas normel bootimg.ur work is awesome thx
bala242 said:
for me wifi not working obtaining ip address,gps not lock can i flas normel bootimg.ur work is awesome thx
Click to expand...
Click to collapse
I'm sorry.. for me everything is working...Before my CF-ROOT all works?
ur a superhero man!!
great ;-)
Skin1980 said:
I'm sorry.. for me everything is working...Before my CF-ROOT all works?
Click to expand...
Click to collapse
ya everything work before,can i reflas ur ver cwm?any body get this error?
Is there any tweak for increasing the 2g speed ??
or getting 3g speed in 2g plans...
I need this very badly...
I am not getting exact idea that what exact cf root does??? Or how cf root is so special...?? Will this make our work easy to do changes in kernal (that would be great)...???
Please can anybody in simple language....!!!
anigr88 said:
Is there any tweak for increasing the 2g speed ??
or getting 3g speed in 2g plans...
I need this very badly...
Click to expand...
Click to collapse
What your asking for is impossible.
Update!
The problem I had turned out to be due to the lack of space in the "/system" folder - as you had predicted Skin1980! Once I deleted some unnecessary software, I was up and running fully within minutes!
The phone works great! The fixes are really good! Having no issues except for one so far. I can't seem to mound "sdcard" in CWM recovery mode and cannot do a restore, for the same reason, from the CF-ROOT menu.
I have a feeling it's something I did wrong earlier, so I'll reflash completely and try again ('cause I have a lotta time on my hands atm and I want the bestest possible phone I can get).
Note: This doesn't seem to be compatible with DDKB2. Assuming that this is mainly for GB firmwares? Can someone corroborate this?
As usual, thanks!
Erahgon said:
The problem I had turned out to be due to the lack of space in the "/system" folder - as you had predicted Skin1980! Once I deleted some unnecessary software, I was up and running fully within minutes!
The phone works great! The fixes are really good! Having no issues except for one so far. I can't seem to mound "sdcard" in CWM recovery mode and cannot do a restore, for the same reason, from the CF-ROOT menu.
I have a feeling it's something I did wrong earlier, so I'll reflash completely and try again ('cause I have a lotta time on my hands atm and I want the bestest possible phone I can get).
Note: This doesn't seem to be compatible with DDKB2. Assuming that this is mainly for GB firmwares? Can someone corroborate this?
As usual, thanks!
Click to expand...
Click to collapse
after a whole day of using it. The phone will tend to lag and build up after a while. You'll notice the phone becomes slow again. I don't know what's going on.
Misledz said:
What your asking for is impossible.
Click to expand...
Click to collapse
I just want a small boost in the speed ....
Misledz said:
after a whole day of using it. The phone will tend to lag and build up after a while. You'll notice the phone becomes slow again. I don't know what's going on.
Click to expand...
Click to collapse
I did notice that initially it was fast. But as I kept it going through the day to recalibrate the battery, it did slow down and start to lag. I thought it was something to do with that. Also I felt that I had done something wrong with the flashing.
Going to overhaul my phone completely: Format, re-partition, XXKPE install (flashing twice), flash fixed CWM from the other thread, root using SOP 2.1.1, install busybox requirements for deodexing (this failed for me the last few times), restore settings using Titanium Backup, Nandroid backup, ext4 this baby, restore, and then install CF-ROOT to monitor.
Wish me luck! See you guys on the other side... again!
anigr88 said:
I just want a small boost in the speed ....
Click to expand...
Click to collapse
You've got the wrong thread mate!
Your bandwidth is capped by you operator and is dependent on how much they allocate you. On top of that 2G is physically limited to certain speeds which, usually, cannot be surpassed by legal means, and the illegal ones give you too less of a boost vs complications and errors to even bother about (I mean big ass hardware)!
Hola peoples!!! Ok so I just thought I'd create my own thread on this matter. Mustangtim started one in apps and themes (and here is the link to that thread) but since I'm taking over this project it was brought to our attention that this should be in the dev section as its no longer just an app.. I am actually tearing .imgs apart trying to figure out what the deuce.
FIRST OFF THIS IS A WORK IN PROGRESS, WE ARE NOT YET FULLY SUPPORTED. HOWERVER I'M DOING MY BEST TO CHANGE THAT.
Secondly if you want to help get this started please visit the market and grab the app here. Its a $3 dollar app for unlimited amount of roms, based on your SD card storage capacity anyway. And speaking of which you need AT LEAST a class 4 or better SD card to make this run smoothly.
Also feel free to visit the forums at http://forum.init2winitapps.com/
Ok so here it is, Boot Manager Pro. Its been a long time coming for the g2x to dual boot. First off let me say long story short, I currently have a bootable SD Rom, known as ROM1. I have yet to be able to recreate my findings tho. But it works and it doesnt brick at all. However it is a bit laggy on my class 4 SD card. Luckily I've already done my research on this project as there are many threads of such awesome info so I'm just going to be lazy about it and quote the good people of xda versus re-writing it based off of their info.
ChrisDDD said:
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of its own, and then sub-folders to hold the different roms you install. When you install a rom, it basically creates images of the usual Android partitions - system, data, cache, & boot. These are standard .img files, just like the ones Clockwork creates when you do a backup. After the images are created and wiped (formatted, which you should do initially) it installs your rom into these essentially the same way as Clockwork installs a rom to your phone's actual partitions. I assume it modifies the kernel that comes with each rom to mount the image files on the SD card instead of the phone's partitions.
When you want to boot a rom, it just replaces your current boot image with the modified one and restarts the phone. With the modified boot image, the system, data and cache images on the SD card are mounted to the correct locations and Android starts up none the wiser. The rom will initially run a little slow, because the SD card is slower than the internal memory, but after things get cached it speed up considerably.
When you want to reboot to another rom, or back to the phone's rom, Boot Manager again swaps boot images that mount the desired rom's partitions (in the case of the phone's rom) or files (in the case of an SD card installed rom).
When you first run Boot Manager, it makes a Clockwork flash able backup of your current boot image, which you can flash if a rom hangs or loops on startup. Alternatively, you can also simply boot into recovery and do an advanced restore, choosing just the boot image to restore from a backup. It accomplishes the exact same thing.
It can be a little hit or miss, with some roms just plain refusing to start through Boot Manager, but it does work and when it does, it's pretty amazing given what it's actually doing.
Click to expand...
Click to collapse
So basically upon installing the app you need to setup your phone so that way you can properly install a ROM, follow these steps:
1. Go into the supersu(or superuser app) and then go to settings then disable logging or click none.
2. Then go into the BMP app and press the menu button on your phone, not the app, and go to settings. Once in settings put a check mark in force large boot.img, screen on during install, and then go into variables, leave tegra alone but change the sdcard block to show mmcblk1p1. Then press finish and let the app restart. By the way I didnt change any of the sizes of the .imgs but feel free to do so. But be warned do not decrease the size of the system.img only increase it, if desired.
3.Then after you've done the above you need to setup the phone rom. Click on 'Setup Phone' under phone rom and follow that process to setup your phone rom.
4. Once your phone rom is setup you may begin to install a zip to rom1 or rom2 or whatever slot you want. This is the tricky part. I have done tons of reading and most people say that if your using CWM, which us g2x'ers do, then you will probably have a better chance of getting a bootable rom by restoring from a nandroid backup you did versus installing new.
5. So after you decide which path you will take, nandroid backup or fresh rom install, choose install. If you choose a fresh rom, wipe system, data, and cache right away. If nandroid, then wipe after the install.
6. Now once you have clicked install put your phone down, DONT MESS WITH YOUR PHONE AT ALL! PUT IT DOWN AND WALK AWAY OR SOMETHING! Don’t mess with it, text from it, xda from it, dont even use the screen as a mirror!!!! lol seriously the app is picky and while under the .img creation process you want nothing to mess that up or you will not get it booted. You may however drag down the notifications bar to follow the progress of the install.
7. Once its complete, tap the install complete notification in the notification bar and let the app do its thing to finalize the install and get you back to your rom selection screen. Now if you did a nandroid back up here is where you click 'manage slot' and then factory reset the backup you did. Just do it, dont ask why.
7.1 Also so if you desire to install gapps and/or possibly a different kernel, now would be the time to do so while your here. I have read mixed reviews of doing this process right after the rom installs. However when I set up my rom1, I booted into it first all happily then realized I had no gapps. So I had to reinstall BMP on rom1 then boot back to phone rom and then I installed GB gapps and had no issues booting back into rom1.
8. Once the above steps are done if your feelin lucky go ahead and tap on boot the rom you installed, and if all goes well it will boot up.
9. If it boots up you need to post confirmation here!!! Provided info such as phone rom and the info on the sd rom you used and slot number and such.
Hopefully it will just work for you. I have done all the above steps using HFP 2.1 as my phone rom and only been able to get 1 bootable rom. Being it was for testing I used HFP as my phone rom and as well as my rom1.
So if the above steps dont wortk out for you and your boot lopped or what ever, then turn your phone off and reboot into cwm. You have 2 options to resolve the boot issue you just created. 1, you may go to restore then advanced restore then restore your boot. Or 2. select install a zip and nav to the bootmanager folder then phone rom then flash the update zip there.. then reboot and you should be back at your phone rom.
Here is a basic run down of everything that I have done so far:
When I first started working on this project I wasn’t doing any dev'ing to change any of the stuff in the boot.img. I just changed settings in the app per all the research I did. So when all was said and done I restored HFP 2.1 to ROM1 and it actually booted!! And it works lovely btw.. I can still boot into this rom today. I then decided to pass the word and ways that I created the working rom1, well I nor anyone else I passed the info to was able to get it working. Only one other person was able to confirm that rom1 works but only after I copied all my rom1 info and sent it to him for testing.. and he was able to boot into my created rom1… As I see it, it was a blue moon event that I have yet to repeat. So I thought eff it lets do some dev'in so I unpacked the boot.img from rom1 then compared that to the unpacked boot.img from rom2 that I created in my trial and error experiences. So in doing so I noticed 4 differences; 1, the mount points obviously, 2, in the sbin folder had a ueventd file from the working rom1 was a text file viewable by gedit in ubuntu. In rom2 it was just a non-readable file. 3, in the init.rc file was also missing a chmod command for system, (the command is in rom1 but not rom2) and 4, there was a ueventd.tegra file that was in rom1 that wasn’t in rom2, but everything else is the same. So I decided to plug and play with the differences to see if she boots and no go. I don’t understand why its boot looping because I am using the same rom as phone rom as for rom1 and rom2. So it boot looped. So I had to restore my boot.img many times in cwm.
So then I said eff it lets do some more research, then I noticed in the .zips folder plus the individual rom folder there are .zips that will let you flash via cwm if you get boot loops and 'should' get you booting to your desired sdrom. I then tried that way and no go.. so then I opened up the zip and had a look at the internals.. first there is the moveboot.sh file that the app runs in cwm flash the given boot.img. I then checked out the meta-inf and opened up the updater-script thinking that the app wasn’t actually flashing the boot.img which is why it loops... Well I think im half way right. However the script itself is lil dodgy... first thing I noticed was at the end of the script they have a command to cp the log from /tmp to /sdcard/bootmanager well the command was wrong so it never copied the log. So I fixed that. I also saw that the assert command was pointing to ‘boot’ instead of mmcblk0p5, so I changed that too. Then I decided to do away with the assert command and the moveboot.sh file they have going on to utilize the same functions that the kernel zips use, which is a kernel folder that holds the boot.img and a run_program that dd's the boot.img to 0p5. plus I even updated the update-binary that the file uses. I used the one from the g2x nullifier as I know that one was made for our phone and should have no issues.. plus there was a noticeable difference in the sizes of the provided binary to that replaced binary. So with the updated.zip file I then rebooted into cwm to flash that being that I was using a different command to flash the boot.img as well as the other changed stuff and still it boot looped. So as of now the only thing I don’t think ive done was grab the boot.img from rom1 then change the mount points, only change that, and then use that for rom2 and see if it boots. I don’t think I’ve done that yet. But every dam process I do I get boot loops. So basically I have came to the conclusion that it’s now NOT a boot.img issue being that I have done everything to change the boot.img and to make sure it flashes, which it does indeed and now creates the log too… I think maybe it has issues with the system.img as that’s what comes next in the boot process. But that’s just my hypothesis. I won’t be able to confirm this till I liberate rom1’s boot.img then change the mount points to point to rom2 and then see if it boots.. if it don’t work then that would mean to me that there is an issue with system.img created. But that’s just my hypothesis…
What I don’t understand is why the eff when I didnt hack the app I got a working sd-rom, but when I do change some stuff with it still don’t work!!???!! I guess maybe ill just edit/hack the apk to see what’s up.. This is getting way more complicated than it needs to be, since it worked prior to all my major changes to the script its using for flashing and the boot.img and what not. Anyone have any ideas feel free to add them.
My next steps are to edit rom1 boot.img one last time to change the mount points to point to rom2 and then if that’s a no go then it’s got to be the system.img that’s getting created. By the way this whole process I have only been restoring my nandroid backup for HFP 2.1. I have not attempted to flash new as with thru my research more times than not people would get a bootable rom via restoring versus flashing new.. so if anyone wishes to experience an sd rom let me know, ill send you a link to download my rom1 to get it going. Mind you that its not perfect and you need a class 4 or better sdcard. Everything works but it just takes a bit longer to load things and get things cached as its on the sdcard and not nand. Also if you have any input or are wishing to help pm me I need more heads to get this sorted as I can’t be the only one who knows how to edit scripts and unpack imgs and such. Either way I will continue to do this until I get it right damit!!! Oh and I just ordered a class 10 sdcard to help with this process…
That was copied from the other thread that mustangtim started. Last night when I went home the first thing I did was change the mount points on rom1 to reflect rom2, I changed nada else, then I tried to boot it... it boot looped. So maybe its a permissions issue or the system.img.
So just as a proof of concept and before anyone calls bs on my work/findings Here is the link to my rom1 that boots and is HFP2.1. *Update, 'm just going to
leave it on my DB for now till I find something better I guess. xda wont let me attach the file since its 233MB. Oh well here is the link :
Code:
[URL="http://db.tt/eBZwrOrs"][U][B]Here it is, my Rom1 HFP 2.1[/B][/U][/URL].
I have also attached my updated script file to flash back to rom1, for now.
The boot.img points to rom1 instead of phone rom, ill add to phone rom
as well, just not the now. :) Feel free to flash this via cwm versus
restoring...
Also this is part of the this: the ‘.zips’ folder you need to replace the file in
that folder as well. It’s an update file for rom1 to flash the boot.img.
..
If you’re going to use this you need install a random rom to rom1 then replace those created files in rom1 with these files in the 7z file..
So I am doing this new thread to get the devs or people with know how to help me out with my findings. I have edited the boot.img so much I could pretty much re-write everything in there by now including using magic to create to my own kernel eff!! lol jk but seriously I need people with knowhow to provide confirmation of go or no go. Basically I have people whom have helped out but It seems that I'm the only one who has dug this far into this app(unless i've been misinformed) and I have no one on my level to talk with except the init2winit devs. Which are very helpful btw.
And lastly:
Conap said:
Guys if it's failing to make the boot.img first make sure your using the market version....others have released cracked versions of our app which they broke...if your using the actual market version just send me a pm or email [email protected] and send your log.txt from BootManager folder on sdcard and we'll get it straightened out. Thanks.
Click to expand...
Click to collapse
or post here or PM me, I'm always down to help out.
Also thanks go to the init2win team, Gflam and Conap as they started this app. and as well to Mustangtim as he brought me into the light of BMP.
So you got all that???!!!??? Now lets get this party started and get full support for dual booting. I will not rest until I get this working. Thanks for your time and possible assistance.
Ok so since I have a book above I thought this is a good place for links and such...
So just incase anyone is curious, here is the Official Boot Manager Manual
Here is a nice link for Tips and Tricks while Installing ROM's that so far has good info to help you watch via adb what the BMP is doing in its creation process.
Some FAQs:
When should I set up my phone ROM?
Set up your phone ROM EVERYTIME you install a new ROM to your phone so you can get back to your phone ROM and won't get stuck on your SD ROM.
My SD ROM seems to lag how can I fix this?
SD ROM lagging may be due to a few things which all have easy fixes. First fix is that most of you have class 2 cards which are what usually come with your phones. These have a much lower read/write then cards of a higher class, we recommend a class 6 card or above. Another easy solution is overclocking merely install a better kernel and use CPU Boost (or any other overclock app) to overclock your phone.
Can I nandroid my SD ROM slots?
Yes and no you can't nandroid them in the traditional sense of the word using recovery but this app works as a recovery for your SD ROM slots and you can back up your ROM slots within the app in the Manage Installed ROMs section which works as a nandroid for your slots by fully backing up your slots to your sdcard which can later be restored.
What if I want to change the sizes of my images, how may I determine the individual sizes easily?
Easiest way is to open up terminal emulator in your app drawer. Type 'su', then grant permissions if need be, then type 'df -h' and it will display such information. You may also use adb in the same fashion. Connect via usb, open up command prompt/terminal and get adb connected and then type 'df - h' again and the same info will show. I will say this again just because, do not decrease the size of your system.img ever! Unless you want mad issues!
Here is the changlog link and just for heck of it the info based on that link:
Code:
V3.2.6
Fixed DroidX/Droid2 Install issue
Fixed UI theme issues
Fixed issue with spaces in name of pic when selecting photo for screen shot
V3.2.5
Fix to allow continue of install if no boot.img is found.
V3.2.4
Added support for HTC Rezound
Added support for rom's with multiple boot.img's
Added support for rom's made for multiple phones
AutoDetect sdcard for usb mounting
Fix for installing ICS gapps
Optimized SDRom Install process
Added support for Motorola RAZR
Added install queue
V3.2.3
Fixed issues with rom's not showing when on emmc on Droid Incredible
Fixed issues with not showing correct booted rom in app
More improvements to sms sync(all rom's will need updated app for changes to apply)
Fix issues with loader
Fixed issue with switching to backup server when main server goes down
Fixed 1x1 widget to show unlimited rom slots
Added 2x2 widget that works with unlimited rom slots
V3.2.2
Fixed force close for img's over 1Gb when resizing
Fixed current booted rom displaying correctly on gnex
Fixed issue with wrong busybox downloading on gnex which should fix alot of install/boot issues
V3.2.1
Fix for errors causing installs to fail.
Fix for some of the licensing stuff.
Removed sdbooster prefs from Galaxy Nexus(Since they don't have sdcard).
V3.2
Changed 4 sd slots to infinite slots!
Galaxy Nexus Support
Sms and Call Log synced between ROMs (you choose what ones too also requries updating boot manager in all slots)
License Check extended to a week
ROMs do not need market installed for boot manager to run (requires updating boot manager in all slots)
Hide su toasts (superuser elite only)
Fix for force close when setting screen shot in MIUI rom's
Thunderbolt defaulted to force large boot.img
Fixed unsupported device using a key
Manually setting variables only accepts numbers
V3.1.1
Fix for various force closes in rom installs and Nand restores
V3.1
Added su binary check
User selectable colors for everything
Better navigation (press title for quick action)
Added compatability for new twrp backups
Better compatiblitlity with memory tweak scripts(i.e. supercharger script and liquids default scripts)
Fix for install process being killed by android
Fix for some themes erasing img's
Fix more force closes during install
Force smaller boot.img option in settings(Fix for some phone's who's boot.img won't fit on the phone after BootManager edit's it)
Improved gapps checker
Improved security
Boot Manager now accepts keys pay for by paypal (see http://init2winitapps.com/stories/BootManager.html)
Added Evo 3d GSM Support
Added notifcation sound/vibrate for finished install (turn on in settings)
Improved data check
V3.0.3
Fix some force closes
V3.0.2
Added backup server (Sorry our server dropped out)
Fixed some force closes
2nd init fixes for Liquid's ROMs
V3.0.1
Last minute UI fixes
V3.0
UI Completely redone
Includes screen shot of each slot
Custom Info
Custom Dialogs
Custom Animations
Custom everything!
Bug Fixes
Added Droid 2 Global support
Screen shot with long press of search
V2.2.1
Bug fixes in file browsers
File browsers only show relevent files
Kernel installer fix
Droid 2 bug fix
V2.2
New security (more advanced and requires data only once a day)
Installs no longer require data
Added Italian translation thanks Black-Ice
Droid X support
Droid 2 support
Fixed status bar notifications
Fixed phone rom rebooter if gapps aren't installed
Bug fixes
V2.1
Restore android_secure to sd from nandroids
Added TWRP nandroid support
Added CWM tar nandroid support
Added Spanish translation
Made widgets easier to use
SD Booster added (Change SD read cache for better preformance)
Added current settings to manually set variables.
Added option to keep screen on during install in settings
Fixed usb layout
Updated Security
Bug Fixes
V2.0
Install now runs from the foreground (status bar)
Restore Nandroids to slots also in the foreground
User can cancel installs as they run
4 new themes added including one by apophis9283
Some phones such as tb moved to new install code (Fix for some sense rom's)
V1.3
Added third theme to app (Red Theme)
Added 4x1 widget and new widget styling
Fixed in app messenger
Added support for Htc Evo 3D
Added support for Htc Sensation
Added Support for Htc Incredible 2
Added Support for Htc Incredible S
Added Support for Htc Desire S
Added support for LG Ally
V1.2
Added option to reboot to phone rom to install gapps in license check dialog
Better error checking and error logging
Automatically install's ext2 libs if not present
Moved Set Names to Manage rom's
Fix for add-on's not installing correctly
Better compatiblility for rom's that use data2ext or apps2sd(user must set larger img's in manual variables)
Trash cleaner added to extras
Better Fix for WiFi issues on Droid 1
Added display to show what rom you are booted into
Fix for updater-script not found errors
Added support for Htc NexusOne
Added support for Htc MyTouch4G
More compatiblity for ext4 support
V1.1
Fix WiFi issues on Droid 1
Fix bug in rom installer for setting permissions correctly
Fix bug for cache size not setting correctly in setting variables manually
Fix for decimals entered into partition sizes causing force close
Fix force close in widget
Fix force closes in installer
Added Wipe data/Factory reset to Manage Rom's section
Added code to show what file's are being unzipped in dialog
Added support for rom's that extract files to sdcard so the files actually end up on your sdcard
Added support for Htc Desire (apps2sd and data2sd rom's support is experimental. Please email if you test it and it works/doesn't work)
Added support for Htc Inspire4g
Added support for Htc DesireHD
Added option to use ext4 filesystem if rom's support it-Experimental Won't work with all rom's.
Added log.txt file to sdcard to log errors during install
V1.0
Initial Release
YEZZZ
glad to finally see this here!
jookdakang23 said:
glad to finally see this here!
Click to expand...
Click to collapse
indeed... hopefully it wont be before too long that I get this app fully supported for us!
This app will be extremely useful for G2X owners and makes the G2X more versatile and desirable.
da-pharoah said:
indeed... hopefully it wont be before too long that I get this app fully supported for us!
Click to expand...
Click to collapse
idk how you get it booted. lol i keep getting bootloops
jookdakang23 said:
idk how you get it booted. lol i keep getting bootloops
Click to expand...
Click to collapse
Are you using the files I supplied or the ones that BMP created for you?
Woo hoo good job bud
Sent from my LG-P999 using xda premium
x0xhellx0x said:
Woo hoo good job bud
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
LOL thanks bro.... Go Team Hellfire!!!!
da-pharoah said:
Are you using the files I supplied or the ones that BMP created for you?
Click to expand...
Click to collapse
i remember requesting the files but think you ever sent them
jookdakang23 said:
i remember requesting the files but think you ever sent them
Click to expand...
Click to collapse
no we had a miscommunication due to our avail times and GB's lacking ability to utilize two accounts on gtalk.... I have posted those files in the op however...
First, I want to thank everyone who has helped with us on this app. Second, I know I picked the right man for the job, did you see that OP! All kidding aside, a lot of you know I write for ACS under screen name artifintel. I just had too much on my plate to give this project the attention and direction it needs. The right guy is in charge, he's a stand up person and very knowledgeable with this app. Good luck everyone!
[email protected]
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Rafase282 said:
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Click to expand...
Click to collapse
what rom are using as phone rom? and you installed to rom1?
da-pharoah said:
what rom are using as phone rom? and you installed to rom1?
Click to expand...
Click to collapse
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Rafase282 said:
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Click to expand...
Click to collapse
and no bootloop you say?? well then it may be the stock rom your using... The app is very picky and if you get a bootloop, I feel that those can get booted with tweaks... but stuck on lg screen is just no bueno.. Try a different rom... maybe one that has its partitions at ext3 format just to try it.. I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
hands down, a badass app...
SiL3nTKiLL said:
hands down, a badass app...
Click to expand...
Click to collapse
lol +1 for sure!
da-pharoah said:
I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
Click to expand...
Click to collapse
positive on ext4
I've been trying to take the phone apk and dialer from one rom and move it onto a stock rooted rom. I have accomplished this but when someone calls me the phone won't play a ringtone at all. So I have to run a nandroid restore on it. Can anyone tell me how to do this please? thank you in advance
Re: [Q] Moving dialer/phone app to stock rom
Which rom are you moving it from and to which rom?
sent from outer space.
Truckerglenn said:
Which rom are you moving it from and to which rom?
sent from outer space.
Click to expand...
Click to collapse
I am wanting the dialer and phone apk from the Aeon Rom and put it on my stock rooted rom found in xda-developers website thread here....
http://forum.xda-developers.com/showthread.php?t=1613523
************ OPTION C *************
I997UCLB3-CWM-root-deodex-extras.rar
Features in this version
- Entropy's Daily Driver kernel
- Red CWM recovery
- Rooted
- Deodexed
- Zipaligned
- Busybox
- AT&T and other bloatware removed
- Scrolling wallpaper fix
- CRT off animation
- 8 lock screens
- Extended power menu
- Accurate battery mod
- Get lidroid's 14 statusbar toggles HERE
Thank your for your time, effort and help in advance,
(Sorry for the edit) It might help and then again it may not. But I am using an AT&T Samsung Infuse 4g sgh-i997 rooted from gb 2.3.6 no modifications except what is found in option C above. and removing some stock libs.
oreo918 said:
I am wanting the dialer and phone apk from the Aeon Rom and put it on my stock rooted rom found in xda-developers website thread here....
http://forum.xda-developers.com/showthread.php?t=1613523
************ OPTION C *************
I997UCLB3-CWM-root-deodex-extras.rar
Features in this version
- Entropy's Daily Driver kernel
- Red CWM recovery
- Rooted
- Deodexed
- Zipaligned
- Busybox
- AT&T and other bloatware removed
- Scrolling wallpaper fix
- CRT off animation
- 8 lock screens
- Extended power menu
- Accurate battery mod
- Get lidroid's 14 statusbar toggles HERE
Thank your for your time, effort and help in advance,
(Sorry for the edit) It might help and then again it may not. But I am using an AT&T Samsung Infuse 4g sgh-i997 rooted from gb 2.3.6 no modifications except what is found in option C above. and removing some stock libs.
Click to expand...
Click to collapse
you may need dialer.apk, phone.apk and maybe contact.apk.
after you move them, set the correct permissions.
reboot.
if that doesn't work, may need to boot into cwm and wipe cache and dalvik.
alternate: you can try using titanium back up..remove those apk and then install the other apks from the myfiles
qkster said:
you may need dialer.apk, phone.apk and maybe contact.apk.
after you move them, set the correct permissions.
reboot.
if that doesn't work, may need to boot into cwm and wipe cache and dalvik.
alternate: you can try using titanium back up..remove those apk and then install the other apks from the myfiles
Click to expand...
Click to collapse
Ok. cool. But when i move them the phone starts to force close like crazy. I move them directly to /system/app/ and replacing the current apps. I didn't move just those apps tho. I also moved phone_Util.apk and PhoneSetupWizard.apk DialerTabActivity.apk and it worked but when someone would call me it wouldn't ring.
So my question is this. Do I just cut/past the ones you just described above to /system/app/ and then fix permissions ignoring FCs to rw-r-r. And reboot. Is that correct?
Thank you for your time. And quick response.
oreo918 said:
Ok. cool. But when i move them the phone starts to force close like crazy. I move them directly to /system/app/ and replacing the current apps. I didn't move just those apps tho. I also moved phone_Util.apk and PhoneSetupWizard.apk DialerTabActivity.apk and it worked but when someone would call me it wouldn't ring.
So my question is this. Do I just cut/past the ones you just described above to /system/app/ and then fix permissions ignoring FCs to rw-r-r. And reboot. Is that correct?
Thank you for your time. And quick response.
Click to expand...
Click to collapse
yeah..just work thru the FC's.
you can also use abd and have no fc issues.
if you are running a rom, you can make those changes to the rom before flashing...either way.
make sure you have a back up of your current set up...zen tool kit allows for a whole rom back up
qkster said:
yeah..just work thru the FC's.
you can also use abd and have no fc issues.
if you are running a rom, you can make those changes to the rom before flashing...either way.
make sure you have a back up of your current set up...zen tool kit allows for a whole rom back up
Click to expand...
Click to collapse
Well I did it like you said worked thru the force closing and changed the permissions of all 3 apks (Contacts.apk DialerTabActivity.apk, Phone.apk)
to rw- r-- r-- is how each apk's permission were then I rebooted the phone. The volume is up and the ringtone is set. But when I call my phone from a different phone it does not ring, and at the bottom of the screen will blink Unknown between the green and red answering/ignore button on screen., even though above that. The picture for the contact calling the cell phone shows up and so do the Name as inputted into phone contacts. I don't know what i'm doing wrong, please help me out if you know what I am doing wrong. Thank you for your time
oreo918 said:
Well I did it like you said worked thru the force closing and changed the permissions of all 3 apks (Contacts.apk DialerTabActivity.apk, Phone.apk)
to rw- r-- r-- is how each apk's permission were then I rebooted the phone. The volume is up and the ringtone is set. But when I call my phone from a different phone it does not ring, and at the bottom of the screen will blink Unknown between the green and red answering/ignore button on screen., even though above that. The picture for the contact calling the cell phone shows up and so do the Name as inputted into phone contacts. I don't know what i'm doing wrong, please help me out if you know what I am doing wrong. Thank you for your time
Click to expand...
Click to collapse
Explain to me what you are trying to do.
Which ROM are you currently running, kernel, root?, odex or deodex? Voodoo (ext4) or stock partition?
It is likely that if you are running simple root stock, with non-voodoo stock kernel, and adding a deodex apk to the mix, the stock kernel may not be able to use the deodex files. you may need to change kernel, or re-odex the apk you are trying to port. Remember, most apk's on the rooted stock has 2 file components.
You can try using the stock deodex base dman made as a base of work from there.
If you are only interested in the appearance of the rom, use 7zip and extract the png's from the apk you want and just paste it into the odex system files to get the same look.
In essence, I think you are trying to theme the stock rom or cook your own.
check here for themes
http://forum.xda-developers.com/forumdisplay.php?f=527
qkster said:
Explain to me what you are trying to do.
Which ROM are you currently running, kernel, root?, odex or deodex? Voodoo (ext4) or stock partition?
It is likely that if you are running simple root stock, with non-voodoo stock kernel, and adding a deodex apk to the mix, the stock kernel may not be able to use the deodex files. you may need to change kernel, or re-odex the apk you are trying to port. Remember, most apk's on the rooted stock has 2 file components.
You can try using the stock deodex base dman made as a base of work from there.
If you are only interested in the appearance of the rom, use 7zip and extract the png's from the apk you want and just paste it into the odex system files to get the same look.
In essence, I think you are trying to theme the stock rom or cook your own.
check here for themes
http://forum.xda-developers.com/forumdisplay.php?f=527
Click to expand...
Click to collapse
I used Odin to flash Option C found here
http://forum.xda-developers.com/showthread.php?t=1613523
Which is Deodexed / Rooted / With Entropy's Daily Driver Kernel. I don't much about the partition stuff yet. Just started to scratch that surface. But i haven't messed with it. I know I have voodoo lagfix in the RED CWM recovery and it did say something about partition when i flashed the rom I can never understand what the chick says tho. But I have not altered it from the file you can download from that thread above. Except for uninstalling a bunch of stock libs.
I am trying to to get the phone app or the dialer setup i guess you can say from the Aeon Rom 1.4 because I can't figure out how to save the Facebook sharing options. via gallery/share/facebook sharing photos and what not. So I went with the stock rom and flash the Lidroid 14 toggle mod. and removed the logsprovider.apk with the modded one found in the same thread with option c in matter of a fact.
Are you saying though that I can unzip Phone.apk and DialerTabActivity.apk here in my PC and take the png?? and paste them to where exactly? I'm sorry I am trying to learn this stuff and It can be very frustrating at times because I am still super new to putting my own rom together. I just want the AEON rom dialer because it has that convenient message tab next to the call tab in the dialer so I want that and the phone to actually ring when someone calls me too.
Thank you for your patience qkster. I still can't believe that you have replied to my thread yourself. I have followed your posts and threads and advice for a long time. I appreciate all your hard work and what not that make ideas likes this possible. YOU ARE THE MAN!!!! lol.
Thank you for your time I hope this was detailed enough for you to get the idea i'm trying to project.
oreo918 said:
I used Odin to flash Option C found here
http://forum.xda-developers.com/showthread.php?t=1613523
I am trying to to get the phone app or the dialer setup i guess you can say from the Aeon Rom 1.4 because I can't figure out how to save the Facebook sharing options. via gallery/share/facebook sharing photos and what not. So I went with the stock rom and flash the Lidroid 14 toggle mod. and removed the logsprovider.apk with the modded one found in the same thread with option c in matter of a fact.
Are you saying though that I can unzip Phone.apk and DialerTabActivity.apk here in my PC and take the png?? and paste them to where exactly? I'm sorry I am trying to learn this stuff and It can be very frustrating at times because I am still super new to putting my own rom together. I just want the AEON rom dialer because it has that convenient message tab next to the call tab in the dialer so I want that and the phone to actually ring when someone calls me too.
Click to expand...
Click to collapse
you are finding out what I consider theory, execution and practice.
in theory, it should work.
execution may not result as intended
practice makes perfect
Couple of issues:
1. you're running jesse's uclb3 rooted with extras. great. it's in an odin format, not a cwm. unfortunately it's not in cwm flashable zip.
you can create one if you google how to make a cwm flashable rom from stock leak.
if you can follow a complex set of instructions, go can try it here: http://forum.xda-developers.com/showthread.php?t=1484578
(Jesse also made this: http://forum.xda-developers.com/showthread.php?t=1711375
essentially the some odin option c you used. (he made that in odin for flash via download mode for borked phones)
his ethereal is essentially the same, meant to flash in RED cwm. except for his themes and sound options similar to sgs3.
the odin option c is essentially stock uclb3)
2. before you do anything, make a back up of your current desired setup with zen tool kit - so you can restore in event of boot loops.
3. have the apk with the icons you want on your pc desktop. use 7 zip. double click into the apk. go to res. go to drawable-hdpi. copies all the png. make a new temp folder on your desktop. call it what you want. paste the copied png into the temp folder and look at in windows, with thumbnail options. you will see the icons you want as it may appear in the rom.
4. pull out the apk of the rom you are running. put it on your desktop. look in it also. using 7zip, pull out the res/drawable-hdpi/ folder onto desktop. if you look in it, you will see the other png that you may no longer want. there are several ways to replace the ones you want but it's easier just to pull all the pngs you want into the drawable-hdpi on the desktop and bring the folder over into the apk or just paste them into the apk's /res/drawable-hdpi/
then flash the modded apk or push it into system
Use this for adb..it's easier to use
http://androidforums.com/esteem-all-things-root/517688-adb-android-commander.html
alternatively:
attached is a cwm-flashable shell...study it with 7zip. look at the updater-script. see what it does.
then put the modded apps into the /app folder and flash.
this can be use to flash framework apk/jar and/or system/app apk
test jesse's ethereal and aeon or any other. mix and match. with zen tool kit restore rom, you want play around and restore it back to where you left off
you can also try just pull the aeon apk into the shell and flash it again
remember too that each dev may have different setup or framework that may not let each apk interact correctly...until you have the right combo of files
qkster said:
you are finding out what I consider theory, execution and practice.
in theory, it should work.
execution may not result as intended
practice makes perfect
Click to expand...
Click to collapse
Thank you very much qkster. I really appreciate your help on this issue. I will be studying these threads and this Android Commander and getting to learn all I can about it. I have followed your posts for awhile and believe you are a very talented developer. I for one appreciate all of your hard work on the Samsung Infuse 4g and insight and advice that you offer.
I'm not gonna just jump right into it, I like to uderstand it all first. But I will definitely be looking this over and trying to absorb it all.
You have kept me busy for probably the next week with this one. Thank You again kind sir. I will let you know in the next day or so to be more realistic as to my progress and if I encounter any problems. Too Bad You don't have a | +1,000,000 THANKS | Button.
oreo918 said:
Thank you very much qkster. I really appreciate your help on this issue. I will be studying these threads and this Android Commander and getting to learn all I can about it.
I'm not gonna just jump right into it, I like to uderstand it all first. But I will definitely be looking this over and trying to absorb it all.
You have kept me busy for probably the next week with this one. Thank You again kind sir. I will let you know in the next day or so to be more realistic as to my progress and if I encounter any problems. | Button.
Click to expand...
Click to collapse
you're welcome.
(btw, i thank you for the compliment but i'm not a dev in the true sense. i can re-using and re-applying what is already out there.)
android commander is a graphic ui for adb..easier to use. you'll see that you can pull/push apks much easier, reboot, etc..
as far as learning ...read as much as your brain can handle and google what info you need...that's how most of us picked up this stuff..gl
Re: [Q] Moving dialer/phone app to stock rom
qkster said:
you're welcome.
(btw, i thank you for the compliment but i'm not a dev in the true sense. i can re-using and re-applying what is already out there.)
android commander is a graphic ui for adb..easier to use. you'll see that you can pull/push apks much easier, reboot, etc..
as far as learning ...read as much as your brain can handle and google what info you need...that's how most of us picked up this stuff..gl
Click to expand...
Click to collapse
I used that program you posted "android commander" and extracted a custom Rom to my PC and then using Android Commander I pushed phone.apk dialertab.apk and camera.apk over to my phone and everything it's working fine. Although I had to change permissions to rxw-rxw-r-x
Instead of rw,r r. But it's all doing fine so far. Phone will ring. Camera takes pictures with the power button and I got my dialer tab wanted. Thank you again man. I appreciate you for real.
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Hey qkster,
I have one more question if you don't mind. Where would i find the File that contains the png's for the notification bar/toggles? I would like to change that stuff around as well and see if I can change the colors and toggle images? Just need to know where to find the file containing those png's
look in:
systemui
settings
frameworks-res
there are several areas...
check the main xda android theme sections
make a revert or backup..once you start playing with settings, systemui and framework-res, you might experience boot loops
use the cwm-shell i posted. put the original working files in the correct location..call it revert...put the experimental files in another shell copy, and call whatever..
Hey qkster ever since I moved those files. that i posted in my last post my text messaging has been acting up. Every once in awhile. I finally narrowed it down to the problem being if the text is too long it fails to send the text message is there a way to fix this while at the same time keeping my alterations I have made to the rom?
oreo918 said:
Hey qkster ever since I moved those files. that i posted in my last post my text messaging has been acting up. Every once in awhile. I finally narrowed it down to the problem being if the text is too long it fails to send the text message is there a way to fix this while at the same time keeping my alterations I have made to the rom?
Click to expand...
Click to collapse
prolly your modem..not your mods
http://forum.xda-developers.com/showthread.php?t=1342978
Re: [Q] Moving dialer/phone app to stock rom
qkster said:
prolly your modem..not your mods
http://forum.xda-developers.com/showthread.php?t=1342978
Click to expand...
Click to collapse
What do ya know ? You were right again. Lol. Thank bro your awesome.
Flashed uclb3 & that fixed. Thanks again
Sent from my SAMSUNG-SGH-I997 using Tapatalk