Related
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'm sure that a lot of people already know about the -=V6 SuperCharger=- by zeppelinrox.
If you are not familiar with his great work please follow the link above and read more about it on his thread.
Those of you who have already tried it on their HTC One S (stock) will probably know that there is a whole different level of complexity when it comes to installing it on an ICS ROM. First of all, on any ICS ROM you have to patch the framework library services.jar to get the full functionalaty of the V6 SuperCharger. To make matters worse the HTC Sense is an odexed ROM meaning that you have to do all the patching manually, which is by no means a trivial exercise. Of course you may decide that you don't want to go patching any files and you may be happy with the limited functionality that you get from the V6 SuperCharger as it is. If that's the case you probably won't find this thread very useful...
However, if you're one of those who will not settle for anything less than the full functionality, you need not worry anymore!
Over the last few days I've done all the hard work of decompiling and manually patching the stock services.odex library so people don't have to do it themselves anymore. Not only that, but I've prepared separate versions of the services.odex for each of the three launcher SuperCharge options available:
1. Hard-to-Kill (downloads 1 & 5)
2. Die-Hard (downloads 2 & 6)
3. Bullet-Proof (downloads 3 & 7)
In addition, I'm also including the stock services.odex file so you can restore it back to your system in case you have any problems with the patched files.
4. Stock services.odex (download 4)
Installation procedure:
DISCLAIMER: I take no responsibility whatsoever for anything that might go wrong with your phone, for any and all data loss, for bricking your phone, etc. You do this at your own risk and it is 100% your responsibility.
WARNING! The files provided are specifically for, and have only been tested on, HTC One S with Stock Sense ROM v1.53.401.2 (Europe). These files may also work fine on different versions of the Stock Sense ROM but I haven't tested that. However, if you use them on any other (custom) ROM they are most likely to get your phone either stuck at boot or into a boot loop!
REQUIREMENTS:
a. First and foremost your phone needs to be rooted and have BusyBox v1.16.2 or higher installed. This is a requirement for the V6 SuperCharger script to run so there's no way to get around it.
b. To install the patched services.odex file you ideally need to have a custom recovery installed, such as ClockworkMod. This way you can just flash the patched services.odex from the recovery and if anything goes wrong, simply flashing the stock services.odex over should get you out of trouble (stock file also provided as a recovery update). While it is not absolutely necessary to save a recovery image of your ROM, I would strongly advise you to do so as it's always a good idea to have a recent recovery image to hand just in case (e.g. there is a chance that the stock services.odex included in here may not work if you have a region/operator specific Sense ROM on your HTC One S). Please keep in mind that the stock services.odex included in here comes from Stock Sense ROM v1.53.401.2 (Europe) so it may not work on other versions of Sense ROM!
c. If you don't want to use the recovery update file, you can also download just the services.odex and install it manually. However, if you choose to do this then you're on your own as I don't have enough time to write a tutorial on how to install it manually.
Step 1. If you haven't already done it, go to the -=V6 SuperCharger=- thread by zeppelinrox and read up on the script and what it does.
Step 2. Follow the instructions on the thread (see Step 1) on how to install the -=V6 SuperCharger=- on a typical non-ICS system.
You can get the latest version of the script from this post: http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
Step 3. Forget about manually patching the services.jar or the services.odex file! Just download the version you need from the bottom of this post AS WELL AS THE STOCK VERSION! You will need the stock if your phone gets stuck on boot. For the installation, see the two options below. Before you do anything however, I strongly advise you to save a system recovery image just in case.
a.The first 4 attached files, named update-services.odex-[something].zip, are recovery update files meant to be flashed via a custom recovery such as ClockworkMod. After flashing the recovery update, also wipe cache and dalvik cache and then reboot.
b. The last 3 attached files are just archives of the patched service.odex files. If you want to go this route you can find some guidance on the -=V6 SuperCharger=- thread in terms of where it needs to be installed and what permissions it should have. Also, if you're using this method don't forget to do a SuperClean & Reboot using the option in the V6 SuperCharger script.
Step 4. It is normal for the first boot after installation to take longer than usual. If your phone has gone past the boot animation and is displaying a windows saying something like 'upgrading applications...' then it's all gone fine so just wait for it to finish. If your phone hangs on the boot animation longer than usual it means that it's probably stuck there and the patched services.odex file is not compatible with your ROM. DO NOT PANIC! Simply go to the recovery instructions further on.
Recovery.
a. If you phone is stuck on the boot screen, hold the power button pressed for about 10 seconds so that the phone goes into hard power off (the touch keys below the screen will start blinking after a few seconds, that's normal).
b. After that just boot into recovery as you nomally do (while holding the volume down pressed, also press the power button briefly and the phone should start into the boot menu; in there, scroll using the volume up / down keys and select the RECOVERY option by pressing the power key).
c. In the recovery simply flash the stock services.odex update file, wipe cache and dalvik cache and reboot. Now the phone should start up fine but your services.odex will not be patched.
d. If your phone is again stuck on the boot screen, you'll have to do a full restore of your ROM from the image that I have strongly advised you to save earlier.
Good luck and I hope you find this useful!
Oh, and pleeease use the Thanks button!
thanx, just installed busybox then flashed "Hard to kill" thru recovery, booted right up on Noble 4.0
Bxrxyxaxn said:
thanx, just installed busybox then flashed "Hard to kill" thru recovery, booted right up on Noble 4.0
Click to expand...
Click to collapse
Thanks, but if you're using this patch on Noble 4.0 it will have absolutely no effect.
That's because Noble 4.0 is a deodexed ROM which means that the services.odex file you've just installed is simply ignored by the system.
Instead you should patch the services.jar file using the online patching tool for deodexed ROMs provided on the V6 SuperCharger thread.
will try on stock T-MobileUS nand later...but thanx for the heads up, will do, edit: Noble already has it
Flashed bullet-proof on stock TMOUS rooted ROM. Caused boot loop. No surprise, it's a different ROM but thought I would give it a go anyways.
Thanks for the post, will definitely use if I go with an EU ROM.
tmobile us
Will this work on the tmobile us one s? Update: noticed the post above stating it doesnt work for T-Mobile us.
Hello Fire owners!
I open this thread to keep all things of Fire together, only one thread, everything here.
So here we go:
THIS THREAD IS FOR MOTOROLA XT311/XT316/XT317, XT530/XT531, XT532 AND XT611 (aka SMARTFLIP) ONLY. IF YOU HAVE A SIMILAR THREAD, PLEASE PM ME AND PASS ME YOUR POST. LET'S KEEP XDA ORGANIZED!
CWM FOR FIRE XT XT530/XT532, SPICE XT XT531, FIRE XT311, SPICE KEY XT316 OFFICIALLY LAUNCHED
This thread was focused in the 2nd-Init for XT31X and XT530, 531 and 532. For almost six months, we worked patientlly to get the CWM working on our devices. The wait for CWM is OFFICIALLY OVER. In a couple days ago, our friend aweosomeabhijeet found a way to run CWM on Gingerbread. The tutorial (made by himself) will be posted NOW:
Hey Guys
All your wait is over.
Here I'll tell you how to get CWM for Moto Fire XT.
Disclaimer : I'm not responsible for any damage to your phone. I have tried it and finished successfully.
Try only if you know little bit about android.
This is beta version. However, a dev is working on not using a PC to reboot back into system, and is trying to make the installation simplified.
Lot of thanks to andrewidya
Required things
1. Rooted XT
2. Pc
Download these things on your phone:
1. Terminal emulator
2. Busybox(Open it and install)
3. Root browser
4. Pimp my Rom
5. ES file explorer
You can find all of them in the Play Store.
If you have done with it download the attachment.
Now main work.
It is not easy though but I think everyone can do it.
Steps:
1. Extract the attachment and copy it to your sdcard
2. Mount /system as RW.
3. Open Root Browser and copy bootmenu folder from sdcard/XT530 and paste it in /system.
4. Open Pimp My Rom and Add universal init.d support.
5.Create 97bootmenu manually.(For this using ES file explorer is recommended)
Steps:
a.Open /system/etc/init.d
b. Create a file, name it 97bootmenu.
c. Open the file as text
Type:
Code:
#!/system/bin/sh
stop
exec /system/bootmenu/binary/bootmenu
d.save the file
6. Change permissions of 97bootmenu to rwx r-- r--
7. Reboot your phone.
Now your phone will start at bootmenu.
Select Recovery>Custom Recovery
PS: If you want to get back the phone to boot normally. Just connect it to PC, open CMD and type
cd path-to-adb.exe
adb shell
rm -R /system/etc/init.d/97bootmenu
exit
adb reboot
I succeeded here's the video:
http://youtu.be/OyHwMqkBArk
Sorry for poor camera quality.
Thanks to all the members.
Special Thanks to:
Gentrylamp for creating bootmenu.
7amdoun for his great knowledge and modding bootmenu for XT530.
andrewidya for correcting me at every point.
Mazen.kh for everything he did.
Mr.Indigo for giving us hopes.
And all other members whom I forgot to mention here.
Click to expand...
Click to collapse
This above quote is the 1ST post of his thread.
THANKS TO HIM AND TO ALL OF THE DEVELOPERS WHO HELPED TO GET THIS.
ROOTING & UNROOTING
You will follow this tutorial if you have 2.3.5 version of Android:
Downloads:
Here are the apps/files needed for Rooting -
1. SuperOneClick 2.3.3.0
2. SUT LR 1.8.2 (Doesn't seem to be working on 64-bit systems)
3. FXX_PR3_NV.xml and NvDefinition.xml [ATTACHED]
Before Rooting:
Prepare your phone by doing the following:
- Go to Settings > Applications > CHECK "Unknown Sources"
- Go to Settings > Applications > Developer > CHECK "USB Debugging" and "Stay Awake"
- Connect your phone via USB, when prompted DO NOT select USB Mass Storage.
- Extract FXX_PR3_NV.xml and NvDefinition.xml from the attached zip file in to a folder
- Now, install SUT LR, run the app
- Select the FXX_PR3_NV.xml [ensure NvDefinition.xml is also in the same folder as FXX_PR3_NV.xml]
- Your phone will restart.
It does NOT erase anything on the phone, since it only patches the ROM.
Rooting:
After the phone restarts, open SuperOneClick and select root. It will take less than a minute to finish.
Click to expand...
Click to collapse
From: Motorola Fire XT / XT-530 / XT-531 ROOTING! - NEW METHOD - [ DEVS NEEDED ] posted by the user jeet.9890427233
Official Motorola SBF Files
Link: www.grupoandroid.com/topic/43248-motorola-firmwares-superthread/
Just copy and paste.
Custom ROMs
None yet.
Custom Recovery
None Yet.
Custom Kernels
None yet.
Applications that you can removeThere are some apps that you can remove, here is the complete list with all apps:
My ROM is VIVO 2.3.5 and can be different in some ROMs.
7x27_FQC or FQC Program= YES, maybe is F actory Q uality C heck or other thing....
AccountAndSyncSettings.apk= NO
ApplicationsProvider.apk= NO - Will brick apps install/uninstall
APR.apk= ?
BatteryManagerAP.apk= YES
BatteryProtect.apk= ?
Bluetooth.apk= NO
BlueToothTestMode.apk= NO
Browser.apk= YES
Calculator.apk= YES
Calendar.apk= NO
CalendarProvider.apk= NO
Camera.apk= NO
CDA.apk= ?
CDASYSTEM.apk= ?
CertInstaller.apk= NO
Contacts.apk= NO
ContactsProvider.apk= NO
DataConnectionWidget= YES
DateTimeSetup.apk= NO
DbgCfgTool.apk= ?
DefaultContainerService.apk= ?
DeskClock.apk= YES/NO
DMClient.apk= NO
DownloadProvier.apk= NO
DownloadProviderUI.apk= NO
DrmProvider= NO
DxDrmApplication= NO
DxDrmPlugin= NO
ECompassCalibration= NO
Email= NO
Facebook_LT= YES
Fallback= NO
FileManager= YES
FM Radio= ?
Gallery3D= YES, but replace with another gallery app
GenieWidget= ?
- THIS LIST WILL BE UPDATED SOON -
Click to expand...
Click to collapse
If you are a DEV our a guy who can provide a ROM for us, please PM me and i will add you in GTalk. If you have a mod or something useful or want to help me, please PM me and i will add you on GTalk. If we get sucess this thread will be updated!
Thread changelog:
- Initial post
- CG2.smg extractor added to the 2nd Post (THANKS TO: Mazen.kh)
- Chainfire 3D support added ( THANKS TO: Overcrasher)
- Thread stopped a lil bit
- Back with some news
- SUPPORT FOR XT530/531/532 (FIRE XT) Added
- SUPPORT FOR XT317 (FIRE in Brazil) Added
- XT317 kernel tested, but didn't work smoothly as 2.2 kernel
- SUPPORT FOR XT611 (aka SMARTFLIP) added
- SUPPORT FOR XT611 DROPED. See more below.
- CWM FOR FIRE DEVICES LAUNCHED BY aweosomeabhijeet
about CG2.smg
Hey man I'm interested in the thread and i can help you extracting the CG2.smg
Here you are my tut. [for windows] it worked for me
1- unrar the file in the attachments
2- make sure that your file is named to 'CG2.smg' without quotes for sure, and in the same folder..
3- just run the .bat and wait for cmd to finish the job then you will find a folder called 'CG2-extracted' in the same place you extracted my .rar file
Note: you will find in the folder called 'CG2-extracted' some mbn files, systemsec.mbn is the /system folder in the xt311/xt316
extract it easily using unyaffs like a system.img file, if you need help in this PM me. i can help you extracting systemsec.mbn only, i dunno about other files also to repack systemsec.mbn you'll need mkyaffs and i think it's usable on ubuntu only and i can't help you with it
sorry for long reply but press thanks if i helped.
Mazen.kh said:
Hey man I'm interested in the thread and i can help you extracting the CG2.smg
Here you are my tut. [for windows] it worked for me
1- unrar the file in the attachments
2- make sure that your file is named to 'CG2.smg' without quotes for sure, and in the same folder..
3- just run the .bat and wait for cmd to finish the job then you will find a folder called 'CG2-extracted' in the same place you extracted my .rar file
Note: you will find in the folder called 'CG2-extracted' some mbn files, systemsec.mbn is the /system folder in the xt311/xt316
extract it easily using unyaffs like a system.img file, if you need help in this PM me. i can help you extracting systemsec.mbn only, i dunno about other files also to repack systemsec.mbn you'll need mkyaffs and i think it's usable on ubuntu only and i can't help you with it
sorry for long reply but press thanks if i helped.
Click to expand...
Click to collapse
IT WORKED!
Thanks!
It helps me a lot!
Now my device Works!
Thanks!
Sent from my Xt316
Is there any custom rom for XT316/XT311?
luume said:
Is there any custom rom for XT316/XT311?
Click to expand...
Click to collapse
Unfortunately not yet.. Neither custom recoveries
Mr.Indigo said:
IT WORKED!
Thanks!
Click to expand...
Click to collapse
Anytime Sir ! I just want to help in anyway getting this device better, By the way here's a list of useless applications so far !
- 7x27_FQC.apk
- Arabware.apk < 7 megabytes and useless
- Wifipowersavingmode.apk < I think it drains the battery faster -.-
- i also removed all motoswitch APKs, And installed go launcher instead in the system. And removed pre-installed live wallpapers
Also if you have errors like "preparing sd card - checking for errors" in the status bar you can delete system/bin/fsck_msdos since i deleted i get no errors for my partitioned sd card
Q/Request: Do you know how can i customize Notify led ? Like changing color and speed ? also it doesn't work with whatsapp!
Thanks anyway ! Ps. led works by Notifyled.apk.. of course you know xD
And Yeah, i found some srs files also, time ago, i thought it would be awesome to have a panel for it ! but maybe it's the normal speakers at the back and it's drivers..
Mazen.kh said:
Unfortunately not yet.. Neither custom recoveries
Anytime Sir ! I just want to help in anyway getting this device better, By the way here's a list of useless applications so far !
- 7x27_FQC.apk
- Arabware.apk < 7 megabytes and useless
- Wifipowersavingmode.apk < I think it drains the battery faster -.-
- i also removed all motoswitch APKs, And installed go launcher instead in the system. And removed pre-installed live wallpapers
Also if you have errors like "preparing sd card - checking for errors" in the status bar you can delete system/bin/fsck_msdos since i deleted i get no errors for my partitioned sd card
Q/Request: Do you know how can i customize Notify led ? Like changing color and speed ? also it doesn't work with whatsapp!
Thanks anyway ! Ps. led works by Notifyled.apk.. of course you know xD
And Yeah, i found some srs files also, time ago, i thought it would be awesome to have a panel for it ! but maybe it's the normal speakers at the back and it's drivers..
Click to expand...
Click to collapse
No, i don't know, srry!
And we cannot use the control panel with the file incluided in the ROM. Needs a lot of files...
And i'm trying to por XT300 Toggle Widget to XT316. It will be harder but... it's beautiful!
Mr.Indigo said:
No, i don't know, srry!
And we cannot use the control panel with the file incluided in the ROM. Needs a lot of files...
And i'm trying to por XT300 Toggle Widget to XT316. It will be harder but... it's beautiful!
Click to expand...
Click to collapse
It's weird how motorola build their phones and drivers, unlike samsung they give full customization !
And good luck man i wish i could help but i'm not really helpful in porting and modding
Mazen.kh said:
It's weird how motorola build their phones and drivers, unlike samsung they give full customization !
And good luck man i wish i could help but i'm not really helpful in porting and modding
Click to expand...
Click to collapse
Yeah, Motorola lock the bootloader, locks the customization and much more. We need a CWM. FASTER!
Edit: before 2.3 versions, Motorola odexed the roms. All of the files were odexed. But Motorola now deodexed everything. So it will be easier.
And i think we can port the CWM from XT300. So, let's try!
Mr.Indigo said:
Yeah, Motorola lock the bootloader, locks the customization and much more. We need a CWM. FASTER!
Edit: before 2.3 versions, Motorola odexed the roms. All of the files were odexed. But Motorola now deodexed everything. So it will be easier.
And i think we can port the CWM from XT300. So, let's try!
Click to expand...
Click to collapse
I didn't know that there was cwm for xt300, but i think, if there is cwm for xt530/xt531/xt532 it'd be easier to port, since xt53X is to close to our xt311/xt316 and it also have 2.3.5 while xt300 2.1 only
Edit: i think xt311/xt316 users will never have custom recoveries/roms unless the bootloader is unlocked, and it'll be so hard to unlock such bootloader since the phone is not popular
Mazen.kh said:
I didn't know that there was cwm for xt300, but i think, if there is cwm for xt530/xt531/xt532 it'd be easier to port, since xt53X is to close to our xt311/xt316 and it also have 2.3.5 while xt300 2.1 only
Edit: i think xt311/xt316 users will never have custom recoveries/roms unless the bootloader is unlocked, and it'll be so hard to unlock such bootloader since the phone is not popular
Click to expand...
Click to collapse
Some guys tried to do an 2ndInit to maybe try to get CWM work. But didn't worked. A file from the battery (when you turn off the phone and conntect the charger, the big battery icon) was missing. But works without this file.
AND I FOUND WHERE WE CAN ACTIVATE SRS! Is in cda.prop, it's configured to false.
So what happens if i changed the value to true ?
i don't think cda props apply actually i tried to change the value of lock screen support rotation to true and nothing changed.
And Yup i read something about that battery icon too but i didn't understand fully how does that relate to unlocking bootloader
i think the bootloader must get hacked easily since as i see it's a common bootloader in many fones for ex. xt530 xt531 xt532 xt300 xt311 xt316 xt317 or am i wrong ?
If i can test the ROM in my computer (i don't know how to do it), we see if works. And Bootloader it's not the same for every phone series. XT300 executes 2.1 WITH UNLOCKED BOOTLOADER. And XT316 with 2.3.5 WITH THE LOCKED Bootloader.
The SRS file is in the attachments. Just take a look on the 'st line:
BLOCK... I understand that is blocked.
And the battery icon maybe is on a apk or anywhere. We might look better.
EDIT:
I googled around and i found a thread that talks about CG2.smg. They tried to do the same what i doing, and didn't finish very well. The phone was bricked, but they use some files, replace and the ROM was going on very well.
Mr.Indigo said:
I googled around and i found a thread that talks about CG2.smg. They tried to do the same what i doing, and didn't finish very well. The phone was bricked, but they use some files, replace and the ROM was going on very well.
Click to expand...
Click to collapse
i actually didn't understand what you said in the "EDIT" but i read that even with a locked bootloader we can have a custom rom, but not a custom kernel right ?
so you can recompress the edited cg2.smg files and re sbf it again after customizing it or am i saying meaningless words ?
Mazen.kh said:
i actually didn't understand what you said in the "EDIT" but i read that even with a locked bootloader we can have a custom rom, but not a custom kernel right ?
so you can recompress the edited cg2.smg files and re sbf it again after customizing it or am i saying meaningless words ?
Click to expand...
Click to collapse
OK. I will explain the edit first.
They edit the systemsec.mbn, repack the mbn and repack everything. but they've got an error. Then, the phone was bricked and RSD doesn't saw the phone.
A custom kernel will be pretty great, but we have to unlock the bootloader 1st.
Mr.Indigo said:
OK. I will explain the edit first.
They edit the systemsec.mbn, repack the mbn and repack everything. but they've got an error. Then, the phone was bricked and RSD doesn't saw the phone.
A custom kernel will be pretty great, but we have to unlock the bootloader 1st.
Click to expand...
Click to collapse
so what kind of error did they get, cause i wanted to do the same as they and repack the rom as sbf and flash it..
also, can we try porting as .nb0 rom? i can see our stock recovery have the option to flash nb0 files
Mazen.kh said:
so what kind of error did they get, cause i wanted to do the same as they and repack the rom as sbf and flash it..
also, can we try porting as .nb0 rom? i can see our stock recovery have the option to flash nb0 files
Click to expand...
Click to collapse
Maybe... Here is the error they got:
I got this after the flash attempt.
Phone[0000]: Error flashing subscriber unit. Device API error. 0xE002000B Address 0x94C3800 Command: BIN (0xE032300B)
Click to expand...
Click to collapse
I've got from ModMyMobile (M3). They mod and bang! Bricked the device!
But they recovered.
See another error here
The recover is change the FLEX VERSION to please flash please (something like that)
Does this file mean anything ?
Code:
ro.product.model.num=2013
ro.product.name=XT316
ro.product.device=XT316
ro.product.model=XT316
ro.product.brand=Motorola
ro.product.board=XT316
ro.telephony.num.auto.hyphen=false
ro.telephony.gsm.spn.shortname=true
ro.telephony.gsm.wait.switch=true
ro.telephony.rat.network.select=true
ro.telephony.gsm.sms.auto-reg=false
ro.telephony.add.mccmnctable=true
ro.telephony.spn.support.mvno=false
ro.telephony.fdn.data=true
ro.telephony.configurable.mtu=false
ro.nitz.name.ignore.plmns=72405
ro.telephony.cphs-spn.support=true
ro.telephony.dun.show=true
ro.telephony.fast.dormancy=true
ro.tether.denied=false
ro.telephony.mvno.sim.spn=false
ro.telephony.croatia.shortcode=false
ro.CDG_MENU_EVDO_ONLY=false
ro.telephony.custom.showspn=false
ro.telephony.extended.mnc=false
ro.telephony.hidemenu.data=false
ro.telephony.gsm.ecclist=112,911,190
ro.telephony.ecclist=112,911,190
ro.telephony.cdma.ecclist=112,911,190
ro.telephony.gsm.voicemail=*555
ro.telephony.cdma.ecm=false
ro.contacts.number.match.length=11
ro.contacts.number.match.minima=7
ro.contacts.polyphonename=false
ro.sf.lcd_density=120
ro.product.locale.language=pt
ro.product.locale.region=BR
ro.config.dbgcfgtool_config=3
ro.DRM_SOLUTION_ID=1
ro.SYSTEM_CTA_MODEL=false
ro.NETWORK_DISABLE_3G_MODULE=false
ro.USB_PLUG_IN_NOTIFICATION=true
ro.LOCKSCREEN_SUPPORT_ROTATION=false
ro.SETTINGS_ENABLE_MSISDN_ALPHA=true
ro.CC_SEC_INC_CALL_OPTIONS=false
ro.SETTINGS_LANG_HIDE_TW_CHINA=false
ro.CALENDAR_FESTIVALS_OPTION=false
ro.SETTINGS_LOCK_PRELOADED_APN=NONE
ro.PHONE_ENABLE_COUNTRY_CODE=false
ro.MEDIA_ENABLE_SRS=false
ro.FB_ENABLE_HIDE_FOLDER=false
ro.CONTACT_VCARD_VERSION=3.0
ro.NETWORK_SB_CUST_FD_MECH=false
ro.SETTINGS_LOCK_VOICEMAIL_NUM=false
ro.CC_QUERY_CF_ON_BOOT=false
ro.BROWSER_ENABLE_PROXY=false
ro.SETTINGS_REMOVE_SIGNAL_STR=false
ro.SYSTEM_GCF_MODEL=false
ro.CC_HIDE_CB_PW_CHANGE=false
ro.SYSTEM_UI_STYLE_ID=0
ro.SB_SHOW_PLMN=false
ro.SETTINGS_DISABLE_TOUCH_TONE=false
ro.NETWORK_ENABLE_HOTSPOT_SEC=false
ro.CC_ENABLE_MAKE_OOS_CALL=false
ro.NETWORK_NET_MODE_IND=false
ro.NETWORK_ENABLE_OP_LABEL=false
ro.NETWORK_HOTSPOT_AUTO_OFF=false
ro.NETWORK_OP_NAME_OPTION=0
ro.NETWORK_WIFI_SLEEP_POLICY=0
ro.NETWORK_SIGNAL_DISP_STYLE=0
ro.SYSTEM_LED_NOTIFY_STYLE=0
ro.SL_DISABLE_UNLOCK_PROMPT=false
ro.BT_ENABLE_FF_RW=false
ro.MUSIC_DEACTIVATED_BY_FW_BW=false
ro.RSS_DISABLE_COST_PROMPT=false
ro.SETTINGS_HIDE_WIFI_SCAN=false
ro.PHONE_ENABLE_REBOOT_FUNC=false
ro.SYSTEM_SIM_WATCHER=false
ro.CAMERA_DISABLE_H263_ENCODER=false
ro.SYSTEM_SPK_OFF_WHEN_HS_IN=false
ro.NETWORK_REMOVE_GSM_COMBO=false
ro.STANDMODE_ENABLE_TV=false
ro.IME_DISABLE_AUTO_PUNC=false
ro.IME_DISABLE_SHOW_SUGGESTION=false
ro.MEDIA_HIDE_3g2_FILE=false
ro.BROWSER_DL_POPUP_DIALOG=false
ro.CC_HIDE_SIP_UI=false
ro.SYSTEM_DISABLE_LOW_MM_CHECK=false
ro.SYSTEM_ENABLE_FLIP_FONT=false
ro.MUSIC_ENABLE_FORCE_TRNAS_RU=false
ro.DL_PROVIDER_CUSTOMIZED_FUNC=0
ro.com.google.clientidbase=android-motorola
ro.com.google.clientidbase.yt=android-motorola
ro.com.google.clientidbase.am=android-motorola
ro.com.google.clientidbase.gmm=android-motorola
ro.com.google.clientidbase.ms=android-hms-tef-{country}
ro.hwt.softbank=false
ro.cust.cover_shutdown=false
kent_lkc said:
Does this file mean anything ?
Code:
ro.product.model.num=2013
ro.product.name=XT316
ro.product.device=XT316
ro.product.model=XT316
ro.product.brand=Motorola
ro.product.board=XT316
ro.telephony.num.auto.hyphen=false
ro.telephony.gsm.spn.shortname=true
ro.telephony.gsm.wait.switch=true
ro.telephony.rat.network.select=true
ro.telephony.gsm.sms.auto-reg=false
ro.telephony.add.mccmnctable=true
ro.telephony.spn.support.mvno=false
ro.telephony.fdn.data=true
ro.telephony.configurable.mtu=false
ro.nitz.name.ignore.plmns=72405
ro.telephony.cphs-spn.support=true
ro.telephony.dun.show=true
ro.telephony.fast.dormancy=true
ro.tether.denied=false
ro.telephony.mvno.sim.spn=false
ro.telephony.croatia.shortcode=false
ro.CDG_MENU_EVDO_ONLY=false
ro.telephony.custom.showspn=false
ro.telephony.extended.mnc=false
ro.telephony.hidemenu.data=false
ro.telephony.gsm.ecclist=112,911,190
ro.telephony.ecclist=112,911,190
ro.telephony.cdma.ecclist=112,911,190
ro.telephony.gsm.voicemail=*555
ro.telephony.cdma.ecm=false
ro.contacts.number.match.length=11
ro.contacts.number.match.minima=7
ro.contacts.polyphonename=false
ro.sf.lcd_density=120
ro.product.locale.language=pt
ro.product.locale.region=BR
ro.config.dbgcfgtool_config=3
ro.DRM_SOLUTION_ID=1
ro.SYSTEM_CTA_MODEL=false
ro.NETWORK_DISABLE_3G_MODULE=false
ro.USB_PLUG_IN_NOTIFICATION=true
ro.LOCKSCREEN_SUPPORT_ROTATION=false
ro.SETTINGS_ENABLE_MSISDN_ALPHA=true
ro.CC_SEC_INC_CALL_OPTIONS=false
ro.SETTINGS_LANG_HIDE_TW_CHINA=false
ro.CALENDAR_FESTIVALS_OPTION=false
ro.SETTINGS_LOCK_PRELOADED_APN=NONE
ro.PHONE_ENABLE_COUNTRY_CODE=false
ro.MEDIA_ENABLE_SRS=false
ro.FB_ENABLE_HIDE_FOLDER=false
ro.CONTACT_VCARD_VERSION=3.0
ro.NETWORK_SB_CUST_FD_MECH=false
ro.SETTINGS_LOCK_VOICEMAIL_NUM=false
ro.CC_QUERY_CF_ON_BOOT=false
ro.BROWSER_ENABLE_PROXY=false
ro.SETTINGS_REMOVE_SIGNAL_STR=false
ro.SYSTEM_GCF_MODEL=false
ro.CC_HIDE_CB_PW_CHANGE=false
ro.SYSTEM_UI_STYLE_ID=0
ro.SB_SHOW_PLMN=false
ro.SETTINGS_DISABLE_TOUCH_TONE=false
ro.NETWORK_ENABLE_HOTSPOT_SEC=false
ro.CC_ENABLE_MAKE_OOS_CALL=false
ro.NETWORK_NET_MODE_IND=false
ro.NETWORK_ENABLE_OP_LABEL=false
ro.NETWORK_HOTSPOT_AUTO_OFF=false
ro.NETWORK_OP_NAME_OPTION=0
ro.NETWORK_WIFI_SLEEP_POLICY=0
ro.NETWORK_SIGNAL_DISP_STYLE=0
ro.SYSTEM_LED_NOTIFY_STYLE=0
ro.SL_DISABLE_UNLOCK_PROMPT=false
ro.BT_ENABLE_FF_RW=false
ro.MUSIC_DEACTIVATED_BY_FW_BW=false
ro.RSS_DISABLE_COST_PROMPT=false
ro.SETTINGS_HIDE_WIFI_SCAN=false
ro.PHONE_ENABLE_REBOOT_FUNC=false
ro.SYSTEM_SIM_WATCHER=false
ro.CAMERA_DISABLE_H263_ENCODER=false
ro.SYSTEM_SPK_OFF_WHEN_HS_IN=false
ro.NETWORK_REMOVE_GSM_COMBO=false
ro.STANDMODE_ENABLE_TV=false
ro.IME_DISABLE_AUTO_PUNC=false
ro.IME_DISABLE_SHOW_SUGGESTION=false
ro.MEDIA_HIDE_3g2_FILE=false
ro.BROWSER_DL_POPUP_DIALOG=false
ro.CC_HIDE_SIP_UI=false
ro.SYSTEM_DISABLE_LOW_MM_CHECK=false
ro.SYSTEM_ENABLE_FLIP_FONT=false
ro.MUSIC_ENABLE_FORCE_TRNAS_RU=false
ro.DL_PROVIDER_CUSTOMIZED_FUNC=0
ro.com.google.clientidbase=android-motorola
ro.com.google.clientidbase.yt=android-motorola
ro.com.google.clientidbase.am=android-motorola
ro.com.google.clientidbase.gmm=android-motorola
ro.com.google.clientidbase.ms=android-hms-tef-{country}
ro.hwt.softbank=false
ro.cust.cover_shutdown=false
Click to expand...
Click to collapse
This is cda.prop right?
it has some tweaks like build.prop, if you tried to change the mobile model that appears to the market from build.prop it won't work, but if you change it from cda.prop it will work also it have some other tweaks that i actually don't know what's it's use
And Don't Forget Thanks Button ^^
XT316 bricked
Hello guys, sorry if this is not the best place to post a problem but, this is the only one active discussion about XT316 that i have found, i have this phone with Brazil Claro stock 2.3.3 Gingerbread Android installed, then i have installed the ChainFire3D hoping to have better experience with some games...
But i got a bricked phone... when powering on, the phone shows only the Motorola logo, then a black screen with no response, and continous reboot
I started the phone in recovery mode and tryed to perform a Factory Recover, but no sucess, same with Wipe Cache Partition option, so, what is left to do now is my question...
I take no credit for this guide. i found it on the samsung galaxy s2 dev section.
eugene373 is the O.P.
so any shout out, fist bumps, high 5's, hitting of the THANKS button- make sure to send them his way.
Link to original thread
http://forum.xda-developers.com/showthread.php?t=1739457
Below is a copy/pasted version of whats in the main thread. Just spreading valuable information
"App Version:
CPU Sleeper
~Free to all XDA Memebers
~ Must Be Rooted to use App
What is it?
Its a fairly simple App that will put CPU 1/2/3 OFFLINE when the screen turns off. Once the screen comes back on, it will allow CPU 1/2/3 back ONLINE.
How does it work?
Since we have Dual & Quad core CPUs, we have a CPU 0 and a CPU 1/2/3, core 0/1/2/3, while the screen is off we really only need to have 1 core active "CPU0", this App will make sure CPU 1/2/3 shuts off while the screen is off, then resumes normal usage when the screen comes back on.
Compatibility?
Works with any Dual Core & Quad Core Devices!
~ICS
~Gingerbread
Battery Saving?
Battery savings all depends on Usage & idle times.
App Download:
Credits:
Handlerexploit for co-creation of this wonderful App
This time I present to you a script that will in theory (and so far for me, in reality) save us some battery without having to risk our hardware with undervolting! I present to you...
CPU Sleeper
Quote: Honestly the Script can be made to work with any Dual Core / Quad Core! The Only Problem is you need to be Rooted!
~ Currently the issue with CM9, is that the boot becomes incomplete while in init.d folder without Modification to the sysinit..
~ however, with any rooted device you can download the script & continue to use it via a script manager app on every boot.
~ With the Script Manager App, this script virtually can run on any Multi-Processor CPU
Hope that clears things Up,
~~Eugene
What is it?
Its a fairly simple script that will put CPU 1 OFFLINE when the screen turns off. Once the screen comes back on, it will allow CPU 1 back ONLINE.
How does it work?
Since we have dual core CPUs, we have a CPU 0 and a CPU 1, core 1 and core 2, while the screen is off we really only need to have 1 core active, this script will make sure CPU 1 shuts off while the screen is off, then resumes normal usage when the screen comes back on.
WARNING! READ THIS!
This script relies on init.d OR script manager! CM9, for some reason, tends to run this at the exact same time it runs some other script (I forget atm which) and it will clash, causing no boot! CM9 users MUST use the script manager version install! Flex Reaper appears to work fine with it as init.d. I strongly urge you to use the script manager version of this, NOT the flashable version. Always make a nandroid backup before modifying the system, including this!
Instructions
Available in 2 versions, script only version which you can place wherever you want and run however you want, or a CWM/TWRP flashable zip that will place the file for you in /system/etc/init.d and set permissions.
Version 1: Flashable
Same as any of my flashable releases, I did most of the work for you!
Make a full backup
Download to external SD card
Install from SD card
Pick the cpu sleeper zip file
it'll be almost instant
reboot
Shouldn't be any need to clear caches or anything like that.
Version 2: Script only
This can be run in 2 ways, via init.d support, or via script manager. Both are pretty similar, and can be done a number of ways, however this is the basis of how.
Init.d supported kernel:
Make a backup!
Download the script file, making sure no extensions get added onto the file. Copy the file to /system/etc/init.d and set the permissions to the following:
XOX
XOX
XOX
Permissions should be set at 755 or r-xr-xr-x
Once done, reboot the system, and it will take effect when your system is finished rebooting.
Script Manager
This method is probably the better method, and should work with any kernel/ROM. Download the script file, making sure no file extensions get added, and copy it to /system/etc. Set the file permissions to:
XOX
XOX
XOX
Permissions should be set at 755 or r-xr-xr-x
Once done, load up script manager, select browse as root (if it isn't already set from the crossix mod method in the guide) then browse to /system/etc and select the script file S98cpu_sleep, then select ROOT and BOOT options. After this is set, reboot system.
What do I do if I can't boot after using this?
You made that backup, right? Ok, then here is what you do.
Hold the power button until the tablet powers off
Press and hold the volume down button, next to the screen lock switch
Press and hold Power (while holding volume down)
Once the recover kernel message comes up, release the buttons
In CWM go to advanced, mounts, mount system, then format system
In TWRP, go to wipe, then wipe system
In CWM go to restore, advanced restore, restore ONLY system
In TWRP select restore, then uncheck all so ONLY system is checked
After restoring system, wipe cache and dalvik cache, then reboot system.
System should boot normally.
Downloads
Available in 2 versions, script only version which you can place wherever you want and run however you want, or a CWM/TWRP flashable zip that will place the file for you in /system/etc/init.d and set permissions.
Dual Core:
Download: Script Only - Recommend Install via Script Manager App
CPU Sleeper script only
Quad Core:
Download: Script Only - Recommend Install via Script Manager App
cpusleep
Download: ClockworkMod Recovery .zip for T989 / I727
CPU_Sleeper.zip
Thanks to pio_masaki for rewriting the OP"
Always be careful when taking stuff from other devices especially not from HTC.....this mod writes to mmcblock24 partition as system. For us that partition is cache. Flashing to the wrong partition can bork stuff or maybe even brick. Also I'm pretty sure our v3 kernel has this feature.
I would pull the download link before someone bricks
So did the OP test this? I'm glad XMC posted a comment, otherwise I'd be bricked.
Sent from my MIUI V4
AgentCherryColla said:
So did the OP test this? I'm glad XMC posted a comment, otherwise I'd be bricked.
Sent from my MIUI V4
Click to expand...
Click to collapse
it worked for me, i backed up and restored all my apps and data with titanium on my sgs2 and restored on my myt4gs and evrything seemed to be running fine with the script
xmc wildchild22 said:
Always be careful when taking stuff from other devices especially not from HTC.....this mod writes to mmcblock24 partition as system. For us that partition is cache. Flashing to the wrong partition can bork stuff or maybe even brick. Also I'm pretty sure our v3 kernel has this feature.
I would pull the download link before someone bricks
Click to expand...
Click to collapse
pulled links, ill test it out a bit more on my device
but if you flashed the zip yo may not have been so lucky
Nawwwwty, very nawwwwty
I believe v3 does do this anyway, don't quote me on that though.
Sent from my myTouch_4G_Slide using xda app-developers app
xmc wildchild22 said:
Always be careful when taking stuff from other devices especially not from HTC.....this mod writes to mmcblock24 partition as system. For us that partition is cache. Flashing to the wrong partition can bork stuff or maybe even brick. Also I'm pretty sure our v3 kernel has this feature.
I would pull the download link before someone bricks
Click to expand...
Click to collapse
the op has the app in the play store
https://play.google.com/store/apps/...wsMSwxLDEsImNvbS5ldWdlbmUzNzMuY3B1LnNsZWVwIl0.
Hello everyone!
Finally, I am satisfied with my chacha. I was constantly shifting between stock custom rom and cm roms. In stock rom everything works but automatic backlight settings are just terrible (especially dim threshold and keyboard light settings) and status bar is bigger than in cm roms (32px vs 25px). Cm roms have all of this but there are other things that still need improvement (front cam, some stability issues etc.). Therefore I decided to create my own mod of stock rom. It is based on Europe RUU 1.3.3 android 2.3.3. I couldn’t find anywhere 2.3.5 Europe rom but to be honest I don’t see any difference between the two. There are two versions:
1. Full sense rom: Link
What is different: rooted, added busybox, support init.d, dta2sd included (you need to partition your sd to ext2 or ext3 after installation and enter dta2sd commands from terminal emulator – google for the commands if you don’t know them), changed the ugly calculator app, added file explorer, added latest play store, Flash player 11 is working. I haven’t removed any apps because in this version I wanted to leave that to the user according to his/her own preferences. Status bar is smaller (more space on the screen) and I themed it a little, removed charging icon (I know that it is charging because phone’s led is orange ). Automatic brightness is tweaked (added lower brightness level, lowered the max brightness of the f button, and added one level for the keyboard lights (sometimes, in stock roms, I couldn’t see my keyboard clearly and the damn lights just wouldn’t turn on so I had to do this tweak as well). And rom is fully deodexed.
2. Stripped rom (no sense): Link
What is different: rooted, added busybox, support init.d, dta2sd included (you need to partition your sd to ext2 or ext3 after installation and enter dta2sd commands from terminal emulator – google for the commands if you don’t know them), changed the ugly calculator app, added file explorer, added latest play store, removed sense, added widget locker, holo launcher, removed a lot of bloatware (at least, bloatware for me), f button is not assigned (I’ll leave that to the user, I use it to turn my screen off but didn’t changed it to this since several people reported issues). Same automatic backlight and status bar tweaks like in the sense rom and it is also deodexed.
3. Stripped rom (odexed): Link
What is different: Same as in stripped rom with the exeption of these: odexed (now 120mb free out of the box), status bar icons have an ICS look and color (wifi, signal, data, bluetooth etc.), notification toggles app added (fully functional and works great, just in the settings set it as an on-going notification and as old in order to be always on top; it has many different icons and styles and colors are changable as well, really nice app), fb button is set to turn screen off, dta2sd not included, different backlight values.
Automatic backlight and status bar tweak for odexed version: Link
Automatic backlight and status bar tweak (sense and stripped deodexed): Link
Flash Player 11: Link
Instructions:
1. Reboot into recovery; wipe data/factory reset; mounts and storage/format system; install from sd card; choose and install your rom; reboot your phone; finish your first boot setup.
2. Reboot into recovery; install from sd card; choose and install backlight.zip; reboot your phone.
3. Install flash player apk; reboot phone.
That’s it. Hope that someone will like it.
Sorry for the poor screenshots.
Regards
P.S. I am not going to support these mods. Everyone is invited to use them and do with them whatever you want. So please don’t ask me does it support this, does it support that, can you do this, can you do that. For me, it is perfect and I don’t need to do or change anything. Everything is working for me. I just wanted to share it with you. I hope that you can understand this.
Edit: I used this guide (thanks kylon) to improve wifi signal range and it worked for me, so I am going to share these settings with you. Mke sure you do this with your WiFi off. Here is what you have to do:
1. Copy your calibration file (found in proc in the root of your phone) to the sd card (it is best to do all steps with root explorer) and download from the attachments framework.jar (here is a link for an odexed version - extract jar and odex files) and symlinkv2.zip.
2. Move the calibration file to system/etc and set permissions as they are set in the screenshot.
3. Reboot into recovery and install symlinkv2.zip.
4. Open calibration file in system/etc (again, best with root explorer) and change this line: rssi_offset=0 into this: rssi_offset=-30
Delete created bak file if you are using root explorer.
5. Copy downloaded framework.jar (I already modified it according to the offset - 30, and if you are using odexed version copy both jar and odex files) to system/framework and set permissions according to the screenshot. Reboot your phone.
6. Done.
This trick did wonders for me and my wifi, hope it will help you as well. If it doesn't, try different values both in calibration file and framework.jar according to the original thread.
Cheers.
Looks noice
Is it faster/smoother than the stock rom? I would go back to the stock rom if it wasn't so hard to configure and it wasn't so damn sluggish compared to CM7/CM9.
ethancottier said:
Looks noice
Is it faster/smoother than the stock rom? I would go back to the stock rom if it wasn't so hard to configure and it wasn't so damn sluggish compared to CM7/CM9.
Click to expand...
Click to collapse
Every rom that I use is fast enough for me. Even the unmodified stock. I just wanted to get rid of some apps that are obsolete for me, and I needed to improve backlight settings because when it is night the original settings don't dim the lights enough which really hurts my eyes and I hate that because I have to manually dim. In this rom I don't have that issue. Lights dim automatically.
Although, I found out today that there is an issue with the dta2sd, or maybe the kernel itself. DTa2sd moves my apps and dalvik to sd-ext, clockworkmod creates a backup of sd-ext in a backup folder, and when I restore it my rom just will not mount my sd-ext on boot after that, thus I need to do a fresh install. I would appreciate if someone has an idea why this happened? It is not an issue for me, since I am going to use this rom for a while, but I would like to fix it for the others. When I don't use dta2sd there are no issues. I looked in init.rc in ramdisk, but couldn't find anything unusual. This happened to me with Void rom as well, so I really don't know where to start regarding this.
Regards
Edit: I have been using recovery for a different phone. I just realized this and now, with the proper recovery, everything is restoring fine.
didije said:
Every rom that I use is fast enough for me. Even the unmodified stock. I just wanted to get rid of some apps that are obsolete for me, and I needed to improve backlight settings because when it is night the original settings don't dim the lights enough which really hurts my eyes and I hate that because I have to manually dim. In this rom I don't have that issue. Lights dim automatically.
Although, I found out today that there is an issue with the dta2sd, or maybe the kernel itself. DTa2sd moves my apps and dalvik to sd-ext, clockworkmod creates a backup of sd-ext in a backup folder, and when I restore it my rom just will not mount my sd-ext on boot after that, thus I need to do a fresh install. I would appreciate if someone has an idea why this happened? It is not an issue for me, since I am going to use this rom for a while, but I would like to fix it for the others. When I don't use dta2sd there are no issues. I looked in init.rc in ramdisk, but couldn't find anything unusual. This happened to me with Void rom as well, so I really don't know where to start regarding this.
Regards
Click to expand...
Click to collapse
I don't know about data2SD, but I use link2SD, and that works perfectly but with the stock rom, you have to format the sd-ext partition in ext2 rather than ext4, and you can't do it with clockworkmod either, cos it doesn't format it properly :/ you have to use a tool like gparted (if you're a linux user) or some windows/mac equivalent to format it properly
Wow that does look pretty nice.thanks man.
ethancottier said:
I don't know about data2SD, but I use link2SD, and that works perfectly but with the stock rom, you have to format the sd-ext partition in ext2 rather than ext4, and you can't do it with clockworkmod either, cos it doesn't format it properly :/ you have to use a tool like gparted (if you're a linux user) or some windows/mac equivalent to format it properly
Click to expand...
Click to collapse
Link2sd works well. Just tested it. Thanks! I don't have the time to look deeper into the issue with dta2sd..
john9 said:
Wow that does look pretty nice.thanks man.
Click to expand...
Click to collapse
Thank you. In a couple of weeks I will tweak the backlight settings little more, and maybe build a similar 2.3.5 rom (if I find a RUU).
Cheers
Stripped with full stock Facebook Button Functionallity
Great work. This is a solid setup. Thanks for the hard work.
I appreciate that you left the F-Button unassigned for the end user, but is there a way to get back to stock functionallity using your Stripped Rom?
Thank you.
maxwellsk said:
Great work. This is a solid setup. Thanks for the hard work.
I appreciate that you left the F-Button unassigned for the end user, but is there a way to get back to stock functionallity using your Stripped Rom?
Thank you.
Click to expand...
Click to collapse
Unzip Stripped Rom, add attached apks to system/app and attached chacha-keypad.kl (unzip the keypad file) to system/usr/keylayout. Zip it and flash it. Let me know if it works.
Cheers.
didije said:
Unzip Stripped Rom, add attached apks to system/app and attached chacha-keypad.kl (unzip the keypad file) to system/user/keylayout. Zip it and flash it. Let me know if it works.
Cheers.
Click to expand...
Click to collapse
Thank you so much for the exceptionally quick response. Unfortunately I ran into an error. Let me walk you through what I did.
1. Dowloaded Sripped Rom, and all the files in the previous post.
2. I unzipped the Rom on my desktop
3. I inserted each of the files in their respective folders
4. Zipped the Rom back up
5. Transferred to SD
6. Booted to Recovery mode and tried to flash.
Here is what I got ....
CWM-based Recovery v5.0.2.7
-- Installing: /sdcard/Stripped-Chacha_1-3-3.zip
Finding update package...
Opening update package...
Installing update ...
Installation aborted.
maxwellsk said:
Thank you so much for the exceptionally quick response. Unfortunately I ran into an error. Let me walk you through what I did.
1. Dowloaded Sripped Rom, and all the files in the previous post.
2. I unzipped the Rom on my desktop
3. I inserted each of the files in their respective folders
4. Zipped the Rom back up
5. Transferred to SD
6. Booted to Recovery mode and tried to flash.
Here is what I got ....
CWM-based Recovery v5.0.2.7
-- Installing: /sdcard/Stripped-Chacha_1-3-3.zip
Finding update package...
Opening update package...
Installing update ...
Installation aborted.
Click to expand...
Click to collapse
That is weird. I just tested it, and it worked for me. Maybe you zipped it with high compression or sth. Try with normal compression. If that doesn't work, I will upload zip for you later today. I use recovery 5.0.2.8, but I don't think that it matters.
Edit: Here is the link - Link
Flash Player Stopping
Stripped down ROM is great - now have more room for downloading apps.
One problem I've come across on this ChaCha is that Flash Player stops working (returns to home screen) after around 2 seconds of playing anything.
Anyone else had a similar problem?
didije said:
That is weird. I just tested it, and it worked for me. Maybe you zipped it with high compression or sth. Try with normal compression. If that doesn't work, I will upload zip for you later today. I use recovery 5.0.2.8, but I don't think that it matters.
Edit: Here is the link - Link
Click to expand...
Click to collapse
That got it! I'm sooooo happy!!! Thanks!! It is perfect!!
maxwellsk said:
That got it! I'm sooooo happy!!! Thanks!! It is perfect!!
Click to expand...
Click to collapse
That's great. Glad I could help.
Regards
scgellion said:
Stripped down ROM is great - now have more room for downloading apps.
One problem I've come across on this ChaCha is that Flash Player stops working (returns to home screen) after around 2 seconds of playing anything.
Anyone else had a similar problem?
Click to expand...
Click to collapse
As you can see from the screenshot below I don't have that issue. Try different flash player for armv6 devices. There are few, just google it.
dta2sd
Little suggestion. If you are planning to use this rom for a longer time, after your setup, copy your data from your sd card to your computer, go into clockworkmod recovery, in advanced options partition your sd card (I set sd-ext to 256, don't need more) and reboot. After that download terminal emulator from play store. In terminal type this:
su (then press enter and allow superuser permissions)
a2sd reinstall (enter and wait for your phone to reboot. It will take some time)
After it is booted enter this:
su (enter)
a2sd cachesd (press enter and wait for your phone to reboot. It will take some time).
The end result you can see in the attached screenshot. After installing all my apps I still have over 120mb free.
Of course, after everything is done copy your data back to sd card.
Regards
Added wifi tweak to the first post. It works for me, hopefully it will work for you as well.
Regards
languages included in europe rom
What languages are included in this ROM?
Thx!
Thanks for this rom, great daily use
Great Rom, Thank you!
This is the best ChaCha rom I have used so far. Everything works great super fast flash even works!
YouTube can play 240p with no lag, any higher and it will.
BBC iplayer crashes but I have yet to find a rom that bbc iplayer will work on when it comes to the ChaCha.
Perfect rom but can u create a RTL fix for arabic support ?
thanks.