Develop Bugs

Boot Manager

I've been trying to get boot manager to work and so far no luck. Eerytime I install a rom it gets stuck at the ssplash screen. Sometimes it will freeze myy phone up when it's installing. The roms I been trying to install in the additional slots are Miui and pool party. It does ask something before install about either installing ext2 or ext4. Can someone explain what that is and how I can find out what my current rom ext is? I'm running SkyRaider1.1

Does it not say in the roms description? It usually does, a lot of the new roms are going to ext4, its basically just a different format for your SD card, ext4 is supposedly faster, I would try visiting skyraiders website to see, o, and I read that if the other roms you were trying to install to boot with this are ext4 roms, they will not work, this was only like 2 days ago I read that so unless they have fixed it since then that may be your problem also...
Sent from my ADR6350 using XDA App

bluedegeon said:
I've been trying to get boot manager to work and so far no luck. Eerytime I install a rom it gets stuck at the ssplash screen. Sometimes it will freeze myy phone up when it's installing. The roms I been trying to install in the additional slots are Miui and pool party. It does ask something before install about either installing ext2 or ext4. Can someone explain what that is and how I can find out what my current rom ext is? I'm running SkyRaider1.1
Click to expand...
Click to collapse
it doesnt matter the rom runs off the sdcard. the .img files it creates are each partition for the rom, it asks you what filesystem you want to use for those img files.
Sent from my Incredible 2 using XDA App

No I looked like 10x. Does not say what file extension it is on SkyRaider website. I talked to a dev. and he said the app isn't connecting to the servers and if I tried connecting using data not wifi which I have been and no luck. I'm just going to get a refund

I would listen to guy above me, he's pretty knowledge, but like I said, regardless of that issue, I red under comments on market, if the roms you are trying to use run ext4 they won't work for some reason, I don't know why, just what a lot of people said, it kept me from buying it cause I wanted to try it.
Sent from my ADR6350 using XDA App

I love my boot manager. I always install as ext2 and don't have problem. I'm running CM7 beta as my main phone rom, with Magnolia, MIUI, Carbonite and GingerBangVanilla in the other slots. So much win.
Anyway you can always copy past the bootmanagers log.txt into an email and send it to [email protected] and they'll be more than happy to help.

chattguy said:
I love my boot manager. I always install as ext2 and don't have problem. I'm running CM7 beta as my main phone rom, with Magnolia, MIUI, Carbonite and GingerBangVanilla in the other slots. So much win.
Anyway you can always copy past the bootmanagers log.txt into an email and send it to [email protected] and they'll be more than happy to help.
Click to expand...
Click to collapse
Yeah I've already done that. They told me my app was connecting to servers to install necessary files in order for it to work properly. They told me to open the app using data while wifi disconnected which I always do anyways. I don't use wifi unless im downloading huge files. I told them i tried it and nothing seem to work, Haven't heard from them ever since. If i install as ext 2 it will install but when i want to select rom 1 it will get stuck at splash screen. If i install ext 4, it freezes my phone

bluedegeon said:
Yeah I've already done that. They told me my app was connecting to servers to install necessary files in order for it to work properly. They told me to open the app using data while wifi disconnected which I always do anyways. I don't use wifi unless im downloading huge files. I told them i tried it and nothing seem to work, Haven't heard from them ever since. If i install as ext 2 it will install but when i want to select rom 1 it will get stuck at splash screen. If i install ext 4, it freezes my phone
Click to expand...
Click to collapse
flash skyraider, open terminal emulator or use adb shell, type mount, look for ext4 in the output.
Sent from my Incredible 2 using XDA App

times_infinity said:
flash skyraider, open terminal emulator or use adb shell, type mount, look for ext4 in the output.
Sent from my Incredible 2 using XDA App
Click to expand...
Click to collapse
Didn't find ext4. I see ext3 in some parts though. Weird.. If my rom is ext3 and it only gives me the option to install as ext 2 or 4. Look at my screen shot in OP to see what ik talking about.

I've been playing with boot manager and have found it a bit buggy as well. I was able to install Miui and stock GingerSense, but both Pool Party and OMFGB boot loop.
I'm not complaining though, I'm amazed it works at all considering what it's doing. I'll happily wait for it to be further refined, and I'm happy to support an app like this.

I think I may have found the problem. Correct me if i'm wrong. I'm running skyraider and the file system is ext3. I need ext4 installed on the main rom for boot manager to work? I tried converting it to ext4 but wouldn't boot so i converted it back to ext3 via EXT4 recovery

[ROM] Stock rooted 6.3

In keeping with my tradition of providing stock rooted ROMs, I've re-packaged the new 6.3 update. As with my past ones, this is completely stock except for modifications that provide root access. It does not attempt to block OTAs in any way, and it does not contain any extras like the Market.
This is a full ROM, not an incremental update, so it will wipe your /system partition when installing. If you're coming from a non-stock ROM you'll want to wipe data/cache, but if you're coming from a previous stock ROM you should be okay. This is tested in CWM (it's what I have onhand right now) but TWRP should also work.
Changes between this and a completely stock 6.3 ROM are:
REMOVED FROM ROM
The new /system/bin/check_rooted binary
Stock recovery image
Stock bootloader image
That goofy userdata-backup.zip
ADDED TO THE ROM
Superuser
su
busybox
CHANGES
Removed the entry from init.omap4430.rc that ran check_rooted at boot.
Set ro.secure=0 so adbd runs as root (insecure boot version only)
updater-script doesn't attempt to install recovery, bootloader, or userdata-backup.zip file since they are not in the ROM.
updater-script won't check your /system partition's size before installing. This means it will install on a /system partition that's been resized, but I have not tested this. My assumption is that if you resized /system you'll know how to handle any errors that you may encounter.
I'm providing secure and insecure boot images, as with my past versions. For those unfamiliar, insecure means adbd runs as root on your Fire so you get a root shell when you use adb to connect (i.e. you get # by default). Secure gives you a user shell (the $) by default, but you can still use 'su' to elevate to root.
DOWNLOADS
Stock rooted 6.3, secure boot image (md5: 37f51cd2dfaf58baffac09135236de36)
Stock rooted 6.3, insecure boot image (md5: e551a507ebc64fabe09f7d5387348585)​

What's change on 6.3??
Sent from my LG-P500 using xda premium

acax456 said:
What's change on 6.3??
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Its right there in his description..
Sent from my Nexus One using xda premium

acax456 said:
What's change on 6.3??
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
http://www.amazon.com/gp/help/customer/display.html/ref=hp_k6land_software2?nodeId=200790620

So if I flash this off Modaco gr7 to get to the latest version should I be ok as long as I wipe Dalvik and cache?

CTTKDKing said:
So if I flash this off Modaco gr7 to get to the latest version should I be ok as long as I wipe Dalvik and cache?
Click to expand...
Click to collapse
I would say probably yes since it's mostly stock, but I've never tried so I can't say for certain. Worst case should be that you bootloop, at which point you can always go back into recovery and wipe data, too.

Perhaps the dumb question, shall I just download and flash it by TWRP like other CM Roms? Please excuse I am noob. Thank you

eldarerathis said:
I would say probably yes since it's mostly stock, but I've never tried so I can't say for certain. Worst case should be that you bootloop, at which point you can always go back into recovery and wipe data, too.
Click to expand...
Click to collapse
Just flashed over Modaco GR7 throught TWRP and everything went smoothly and fine!
---------- Post added at 08:20 PM ---------- Previous post was at 08:19 PM ----------
ka724ka said:
Perhaps the dumb question, shall I just download and flash it by TWRP like other CM Roms? Please excuse I am noob. Thank you
Click to expand...
Click to collapse
Just Flashed through TWRP like any other rom (over modacos) and everything went fine !

My first kindle rom. Thanks so much. I really like stock and was happy to make this my first rom. It's awesome.

Just wondering if I can flash intersects kernel with the 6.3 Rom?
Sent from my Kindle Fire using xda premium

xolanir said:
Just wondering if I can flash intersects kernel with the 6.3 Rom?
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I don't see why not
Sent from my Kindle Fire using xda premium

Updated successfully, but for some reason CWM is unable to make a back up, gives me an error listing that it can't write the cache img. Has anyone else had this issue or is it isolated, and is there a fix? Thx in advance for help.
Sent from my Kindle Fire using xda premium

I assume this has the new browser, how do you access the new "reading view" I feel like it should be fairly easy to see but...

xolanir said:
Updated successfully, but for some reason CWM is unable to make a back up, gives me an error listing that it can't write the cache img. Has anyone else had this issue or is it isolated, and is there a fix? Thx in advance for help.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I've had CWM (and TWRP, actually) refuse to mount my cache partition in the past, and rebooting generally fixed it for me. Not sure if that's what's happening to you, though.

eldarerathis said:
I've had CWM (and TWRP, actually) refuse to mount my cache partition in the past, and rebooting generally fixed it for me. Not sure if that's what's happening to you, though.
Click to expand...
Click to collapse
I recently repartitioned my KF following the guide you posted using the GNU parted method. What I did was increased my media storage and shrunk my cache partition to 350MB and userdata partition to 700MB, would those settings affect CWM in anyway? The other thing I noticed was after I get the error, I reboot and check the CWM folder to see if anything did save, and it looks like it doesn't compress the back up while saving it. I found a partial back up of 2.35GB after the error. This is a strange one
Update: okay figured it out. The problem was CWM was trying to back up the /sd-ext volume. I unchecked it in the advanced back up option and ran the back up without a hitch.
Sent from my Kindle Fire using xda premium

Can anyone confirm that the browser did not update to the newest version?
To access reading view, I was told "At the bottom of the display there is an eyeglass Icon tap it the screen says loading and you will have the view. Back arrow out of it."
I don't see an eyeglass icon on this rom.

jacewt said:
Can anyone confirm that the browser did not update to the newest version?
To access reading view, I was told "At the bottom of the display there is an eyeglass Icon tap it the screen says loading and you will have the view. Back arrow out of it."
I don't see an eyeglass icon on this rom.
Click to expand...
Click to collapse
It works for me, but only on certain web pages (I'm guessing ones that are text-heavy). Try viewing some random Wikipedia article, for example. The icon also doesn't appear until about a second or so after the page has completely finished loading.

Just bizarre, I am not getting it. I looked at wikepedia articles too. I am using the insecure rom if that makes a difference.
What version should the browser be now?
I have 1.0.13.328_10008910
Gonna go clear data, etc.
Well, heck, that did it. Thanks for that. Interesting feature!

Flashed this succesfully... but i neglected to wipe the system and accidentally flashed the 4.0 gapps package after. Boots fine but i am getting an android.process.acore FC and a Calender session FC. Any suggestions? I came from JC's ICS build and I am thinking of just going back to that.
Update. Nevermind. Just went back to ICS. The Stock Launcher gives me douche chills.

Swype?
Anyone who has Swype working on 6.2.1 or 6.2.2 installed this? If so can you tell me what happened to your Swype and were you able to get it working again?
I'm still on 6.2.1 (updates blocked with Droidwall) and went through so much hassles getting everything working *just* right, I'm trying to decide if the changes in 6.3 are worth potentially having to re-do Swype, market, calendar/contact sync, etc.
Edit: Any hope for an incremental update on this one? I loved the ones for 6.2.1 and 6.2.2.
Edit2: Any issues with market or calendar/contact syncs (for those of us who had set that up)?

[UTILITY] HellFire Kindle Nullifier 1.0

this is made by Volk released by me with his permission
The Nullifier.
This uses a special command in combination with a special file to overwrite the internal partitions with 0's, hence "Null" for 0 and "-ifier" for the fact that it does something. It also formats *all* the partitions afterward and *new* checks for, and repairs any errors on them.
Some brief need to knows:
1. This is a little lengthy process so please bear with it. The longest wipe is on /data which will take about 7 minutes. Obviously, make sure you have plenty of battery life before running it or are charging.
2. You *must not* power off your tablet without first installing a new ROM or restoring a nandroid after you use this. See post here:
3. I will provide help, support, etc., but I am not, nor is anyone else involved with this, responsible for any problems you may have in the extremely unlikely event that you do.
Folder:
http://www.mediafire.com/?unsvbx50wt3hh13
Q: Why not just format everything?
A: Because a format isn't intended to erase data, though to a degree does so. This script is intended and will wipe out the data and leave a clean set of partitions for a ROM to be installed to.
Q: (Submitted by Cargohook) Would it be idiotic or fruitless to run this and then restore a nandroid backup? I mean, would that defeat the purpose?
A: I highly doubt it would be a waste of your time. On an educated hunch, when you restore a nandroid all CWM does is format the partitions then load the data from the nandroid to those partitions; back to square 1 with old data being left behind.
Q: Why don't I get a message about formatting /boot?
A: Because it doesn't format /boot. Why? In testing I found that it doesn't need it. It's all a matter of how Android uses boot.img and how it's copied.
Q: Does this wipe Dlavik?
A: Technically. Dalvik is contained within /cache which gets Nullified so, yes. And see the following post regarding not needing to wipe the Dalvik on top of wiping /cache:
http://forum.xda-developers.com/show....php?t=1564287
Q: Does this wipe internal or external SD? (added because it keeps getting asked)
A: In a word, no.
Q: Will using this cause nand-failure or make my phone unusable if used too much?
A: In my opinion, no. In other's, yes. To give you a better answer, please see Overground's post on that subject here: http://forum.xda-developers.com/show...&postcount=327
(Thanks for the objective opinion overground)

reserved for later

I'll give it a shot. Sounds like a good deal for a clean install.
Sent from my Amazon Kindle Fire using xda premium

If anyone runs this and has errors please make sure to get the log and either post it or copy the info on it... We wont be guessing as to the error and gotta have specifics to get great resolution. Please and thank you.
Edit:
I'd like to restate this btw:
You *must not* power off your tablet without first installing a new ROM or restoring a nandroid after you use this.

Nice I was wondering if volk would port this for the KF as well.
Sent from my LG-P999 using Tapatalk 2

pio_masaki said:
Nice I was wondering if volk would port this for the KF as well.
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
yea he needs to get the Fire as well... but yup He's been wanting to do it for a while now actually. Glad its finally here too.

As this is being released by hell should I start on the videos for this as well? Also, I would love this for my Acer iconia too. Has this been tested on twrp and cwm yet?
Tapatalked from my A100 - Flex Reaper RF1.

pio_masaki said:
As this is being released by hell should I start on the videos for this as well? Also, I would love this for my Acer iconia too. Has this been tested on twrp and cwm yet?
Tapatalked from my A100 - Flex Reaper RF1.
Click to expand...
Click to collapse
ill leave that one up to you. but afaik its only been tested in cwm.

pio_masaki said:
As this is being released by hell should I start on the videos for this as well? Also, I would love this for my Acer iconia too. Has this been tested on twrp and cwm yet?
Tapatalked from my A100 - Flex Reaper RF1.
Click to expand...
Click to collapse
Yes ran it on cmw
Sent from my LG-P999 using xda premium

OK when I get some time later I'll test it with twrp.
Edit: testing with twrp now, I'll post back battery % used and total time spent nullifying when it completes. Dual wipe, so just half it for a single pass.
Edit 2: here's my findings using dual pass on twrp:
Starting battery 81% at 11:31am
Dual wipe end 77% 11:46am
Install hfks
After flash 76% 11:47am
Reboot
75% 11:51am at system start
Using this information you should get an idea of how much battery is minimum required for nullifying and flashing a rom then rebooting into the system. Works perfectly fine with twrp, so twrp and cwm users rejoice, we have nullifire for the KF! Thanks to Volk and hell for releasing this tool.
Sent from my LG-P999 using Tapatalk 2

Sorry to sound like a noob, but I've never used a script through twrp. How do you do it? I usually just run scripts with from toolbox but don't want to try and have it get screwed. Thanks a lot, I know its probably really simple, just wanted some steps to do it.
Nick B

Its the same as flashing a rom, just pick the nullifier zip instead of a rom. I'm working on a video to show the process in twrp, but for now here goes....
Boot into your recovery ( twrp or cwm doesn't matter), pick install zip from SD card, go to where you have the nullifire.zip, select it, and hit flash. After its done be sure to restore a nandroid or flash a rom, never power down or reboot without one or the other being done first! Also make sure to have 30% or more battery, or be plugged in before starting.
Tapatalked from my A100 - Flex Reaper RF1.

BrooksBlood said:
Sorry to sound like a noob, but I've never used a script through twrp. How do you do it? I usually just run scripts with from toolbox but don't want to try and have it get screwed. Thanks a lot, I know its probably really simple, just wanted some steps to do it.
Nick B
Click to expand...
Click to collapse
its simple. Download the script. then reboot into twrp or cwm then install the script.. once its done then install your chosen rom... wait for it to be done. fix permissions then reboot and enjoy.. super simple and super cool..

Holy crap I'm stupid, if I would've noticed it was a zip I would've known that hahaha sorry guys
Sent from my GT-P1000 using XDA

BrooksBlood said:
Holy crap I'm stupid, if I would've noticed it was a zip I would've known that hahaha sorry guys
Sent from my GT-P1000 using XDA
Click to expand...
Click to collapse
No biggy, I think its a little confusing as its referred to as a script, and generally those are in a zip file, extracted, then run in system, not flashed through recovery.
Tapatalked from my A100 - Flex Reaper RF1.

Ok, I'm really going to come across as a noob, but what are the benefits to running this? I guess I'm confused to what it actually does.

Stage said:
Ok, I'm really going to come across as a noob, but what are the benefits to running this? I guess I'm confused to what it actually does.
Click to expand...
Click to collapse
The concept to its use is to minimize bugs caused by left over data. The wipe process of cwm and twrp is a format, it deletes the arrows pointing to where data is, but the data remains intact. It allows the system to overwrite the data. Nullifier overwrites the data itself with zeros, making it so no leftover data is there to cause problems later, then formats afterwards for rom use. Essentially leaving a blank slate to read and write from without worries of old data creeping in.
Tapatalked from my A100 - Flex Reaper RF1.

pio_masaki said:
The concept to its use is to minimize bugs caused by left over data. The wipe process of cwm and twrp is a format, it deletes the arrows pointing to where data is, but the data remains intact. It allows the system to overwrite the data. Nullifier overwrites the data itself with zeros, making it so no leftover data is there to cause problems later, then formats afterwards for rom use. Essentially leaving a blank slate to read and write from without worries of old data creeping in.
Tapatalked from my A100 - Flex Reaper RF1.
Click to expand...
Click to collapse
Ok thank you!
Sent from my Amazon Kindle Fire using xda premium

I can't get the link to work :-\
Sent from my GT-P1000 using XDA

BrooksBlood said:
I can't get the link to work :-\
Sent from my GT-P1000 using XDA
Click to expand...
Click to collapse
MF was giving me issues too.. but I thought it was my kinda limited data connection in my office building.. give a few ill upload it here...
edit:
Here you go, Ive attached it.

[Q] Incredible running CM7.2 "Low on space" message

My Incredible running CM7.2 keeps showing a warning in the notification bar that says "Low on space". I don't understand it, because when I click on the notification, it goes to the manage applications screen, which indicates that there are 207MB used with 541MB free internal storage, and 156MB used with 184MB free RAM.
This "Low on space" message is what prompted me to root and install CM7.2 in the first place.
Can anybody explain this to me, and give suggestions on how to fix it?

how did you miss this?
http://forum.xda-developers.com/showthread.php?t=1488351

tekweezle said:
how did you miss this?
http://forum.xda-developers.com/showthread.php?t=1488351
Click to expand...
Click to collapse
Well, I didn't, but I thought CM7.2 was supposed to fix that issue, and therefore, the problem was being caused by something else. Was I wrong?

what ROM are you running? I have found out that the Touch of Blue ROM integrates this fix already but my understanding is that others do not.

tekweezle said:
what ROM are you running? I have found out that the Touch of Blue ROM integrates this fix already but my understanding is that others do not.
Click to expand...
Click to collapse
Thanks for the reply. I'm using CM7.2 (CyanogenMod 7.2).
Are you using Touch Of Blue V2.2 available from http://forum.xda-developers.com/showthread.php?t=1492720 ? Have you noticed anything not working properly with Touch Of Blue?
Does anybody else know of any other ROM that fixes this issue with the Incredible? Thanks!

its not the rom that fixes the issue, it;s the ext4 conversion and moving the data partition mod. you might be able to apply it using CWM to your installation without changing the ROM. I only mention that one because it had the fix integrated into it.
i tested it out and it worked okay but I switched to a CM10 Rom because I was still getting the dreaded 2am reboot issue. So I switched to the CM10 Rom in hopes of solving that issue.

tekweezle said:
its not the rom that fixes the issue, it;s the ext4 conversion and moving the data partition mod. you might be able to apply it using CWM to your installation without changing the ROM. I only mention that one because it had the fix integrated into it.
i tested it out and it worked okay but I switched to a CM10 Rom because I was still getting the dreaded 2am reboot issue. So I switched to the CM10 Rom in hopes of solving that issue.
Click to expand...
Click to collapse
The mod found in the dev section should work for all ROMs.
Sent from my Galaxy Nexus using Tapatalk 2

tiny4579 said:
The mod found in the dev section should work for all ROMs.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I don't seem to find anything about this in the dev section. Do you mean
[HOW TO] Fix the "Low on space" problem (in plain English) in Droid Incredible General? If not, which mod were you meaning? Thanks!

Boz1 said:
I don't seem to find anything about this in the dev section. Do you mean
[HOW TO] Fix the "Low on space" problem (in plain English) in Droid Incredible General? If not, which mod were you meaning? Thanks!
Click to expand...
Click to collapse
Yes and also this one http://forum.xda-developers.com/showthread.php?t=1623038 which is the main thread for the no_data_limit mods. The thread you posted is more of a guide for people who arent rooted.
The no data limit mods are very simple to use. They are just a zip file like a rom or any other mod, that you flash thru recovery. The mod then does all the work for you. Just remember to do a backup before flashing, just in case.

Thanks for all of the help everyone has provided so far!
Would it be best to start with Convert2Ext4_no_data_limit_normal_dalvik.v2.0.zip?
In what scenario would Convert2Ext4_no_data_limit_dalvik_moved.v2.0.zip be used?
(The above files are at http://goo.im/devs/tiny4579/mods )

Boz1 said:
Thanks for all of the help everyone has provided so far!
Would it be best to start with Convert2Ext4_no_data_limit_normal_dalvik.v2.0.zip?
In what scenario would Convert2Ext4_no_data_limit_dalvik_moved.v2.0.zip be used?
(The above files are at http://goo.im/devs/tiny4579/mods )
Click to expand...
Click to collapse
No data limit normal dalvik is the most commonly used. It converts /cache and /data to ext4 from ext3, moves the /datadata partition to a folder on the /data partition, leaves dalvik as is.
The dalvik moved mod does the same thing except it takes the dalvik cache, and moves it to the now empty /datadata partition. This one has been known to cause issues for some people with a lot of apps, as it fills up the now tiny dalvik partition messing with and slowing down apps.
So yeah use the no data limit normal dalvik.

Ok. One final question, I hope, and I apologize for my lack of knowledge, but will flashing Convert2Ext4_no_data_limit_normal_dalvik.v2.0.zip cause me to have to reinstall all of my apps and redo the OTA (*22890) programming?

Boz1 said:
Ok. One final question, I hope, and I apologize for my lack of knowledge, but will flashing Convert2Ext4_no_data_limit_normal_dalvik.v2.0.zip cause me to have to reinstall all of my apps and redo the OTA (*22890) programming?
Click to expand...
Click to collapse
No it it wont, at least its not ment to. Like i said make sure you do a backup first. I have seen a few issues where apps dont get moved correctly, but its rare. As to the ota programing definitley wont have to do that.

cmlusco said:
No it it wont, at least its not ment to. Like i said make sure you do a backup first. I have seen a few issues where apps dont get moved correctly, but its rare. As to the ota programing definitley wont have to do that.
Click to expand...
Click to collapse
Once again...THANK YOU! I think I got it applied. I checked, and "noauto_da_alloc" shows in the results of the "mount | grep /data" terminal emulator command.

Boz1 said:
Once again...THANK YOU! I think I got it applied. I checked, and "noauto_da_alloc" shows in the results of the "mount | grep /data" terminal emulator command.
Click to expand...
Click to collapse
No problem. You should be good to go then.

If I decide later to try the "dalvik_moved" version, would I be able to flash it over the "normal" version? Or would I first have to use one of the other files at http://goo.im/devs/tiny4579/mods ?

Boz1 said:
If I decide later to try the "dalvik_moved" version, would I be able to flash it over the "normal" version? Or would I first have to use one of the other files at http://goo.im/devs/tiny4579/mods ?
Click to expand...
Click to collapse
Just flash it over. If you want to undo the dalvik move after you try it, there is a file for that the dalvik moved revert.

Did the mod fix your low space issue?
Sent from my ADR6300 using Tapatalk

tekweezle said:
Did the mod fix your low space issue?
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
It seems to have fixed it. Of course, my internal storage has been reduced to 411MB from the original 541MB because the app data, which was previously in the 149MB app data storage partition, is now using space in internal storage.
I'm now debating whether or not to try the "dalvik_moved" version of the mod so that the 149MB partition isn't just wasted space. My dalvik-cache is currently at 133MB, so I'm not sure. If anybody has any thoughts on this, I'd appreciate the input!

Boz1 said:
It seems to have fixed it. Of course, my internal storage has been reduced to 411MB from the original 541MB because the app data, which was previously in the 149MB app data storage partition, is now using space in internal storage.
I'm now debating whether or not to try the "dalvik_moved" version of the mod so that the 149MB partition isn't just wasted space. My dalvik-cache is currently at 133MB, so I'm not sure. If anybody has any thoughts on this, I'd appreciate the input!
Click to expand...
Click to collapse
You can try it, but if you run out of space for dalvik it may make apps go slower. You can always revert it if you het issues.

Phone is rooted now I need help with installing cyanogen mod.

Good day everyone.
I have successfully rooted my S3 1747.
I have done a backup after installing Rom manager. I also have a nandroid and titanium backup completed.
I would like to install cyanogen mod but its very important that I am able to get my contacts back.
I plan to install through the so called easy method in rom manager.
Am I able to get my stuff back after the install?
Thanks in advance

Most system app data will not be compatible. I don't know about CM, but in TW there's an option to export contacts to SD. It'll save them in a .CSV file. Maybe you can import them to CM contacts like this. Might want to confirm that first though.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

Thanks for the reply. I'm going to do this later. Does cyanogen live up to the hype?

Everyone has their own preference. I personally like touchwiz better. There are plenty who would agree and disagree.
If you've got a nandroid backup of your current set up, its pretty easy to flash a bunch of different ones to see what you like, and then go back if none keep your interest.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

Thanks again for the response and sorry for my late thanks. I was busy at work and overlooked the post.
Sent from my SGH-I747M using Tapatalk

You can use google to back up all contacts and restore them on any android with your google account on it....as for the install I believe our s3 is compatible with the cm installer

crazymonkey05 said:
You can use google to back up all contacts and restore them on any android with your google account on it....as for the install I believe our s3 is compatible with the cm installer
Click to expand...
Click to collapse
When you say cm installer. I assumes you are talking about the app and pc program that does everything automatically. It says my phone is compatible however wouldn't work originally. I had to root and use twrp. Can I use that to update from now on or should I continue to use twrp?
Sent from my SGH-I747M using Tapatalk

Edit - double post

Well for me cwm is the easiest to use as you just wipe and flash.....its purely up to you, if your gunna use twrp just download the zip boot recovery wipe system, cache, dalvik cache, data (factory reset), and hit install zip and bam you got cyanogen

I wouldn't wipe /system before a flash. If the rom fails to flash youll have no OS to boot into, and it can be a huge pain to get it back. If the rom does flash, its first step will be to format /system, so it gets done anyway.
I think this may be one of those things people used to have to do on some older devices, and was carried on to newer ones. I just think its an unneeded extra step, and more than a few times ended up taking a day or two to help people get their device working right again.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
I wouldn't wipe /system before a flash. If the rom fails to flash youll have no OS to boot into, and it can be a huge pain to get it back. If the rom does flash, its first step will be to format /system, so it gets done anyway.
I think this may be one of those things people used to have to do on some older devices, and was carried on to newer ones. I just think its an unneeded extra step, and more than a few times ended up taking a day or two to help people get their device working right again.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
That's good advice that would have helped me a lot. All the instructions I followed online said to wipe/format everytime.
Sent from my SGH-I747M using Tapatalk

Yeah, its extremely common advice. I see it all the time. There are rare times when it is necessary to format system, but I dont feel a rom flash is one of them.
Its still possible to end up with no OS after a failed flash, but the chances are greatly decreased by eliminating that one step!
Sent from my SAMSUNG-SGH-I747 using Tapatalk