Database Info

[FIXED] [ROM] CyanogenMod 4.2.5 PLUS RAM hack, better a2sd, auto swap, nav/facebook

I would suggest doing a Nandroid backup - just in case
Download: http://www.mediafire.com/?umznkzjtgdz
Someone mentioned a bug for a couple app crashes
All right, screw it. I am going to remove the CM stuff and just push the nav/fb, ram hack, etc as just an incremental update
To-Do:
Music.apk - Rewrite to ignore music less than 30sec long (aka voicemails)
BFS 310 Kernel with 10mb RAM hack (BFS 310 hasn't been tested by anyone else yet, why not try)
Add Fix_Permissions v2.03 (running the default 1.31 right now)
ZipAlign all apps (including Google apps)
[Suggest more!]
Converting from Cliq/Hero/1.5 - see below for instructions
Need Google Apps - see below for instructions
Includes:
10mb hack - working on adding bfs310 (seriously if you can help PLEASE DO)
Google Navigation works
Facebook included
Includes HTC IME
Clears cache of old files
Installs RA Recovery
MANY MANY TWEAKS
Adjusted a2sd (mt3g: one time copy from /system/sd to data for apps)
Note: this discontinues A2SD from then on for better performance after apps have been copied, am making script to copy back to SD
For fastest possible speed: have a swap partition on your SD card
The ROM will load a2sd for G1's
If you don't have /system/sd (and just swap partition), it will swapon to that
Trick is it utilises both Cyanogen's compcache plus the swap
Then with 10mb hack - hell this is a perfectly fast ROM
See at the bottom if you need Google Apps (starting on clean build or converting from any 1.5 ROM (Hero/Cliq) OR if you are starting with a blank phone lol (aka no system partition at all))
Hero/Cliq/1.5: Yyou will have to run the thing at the bottom for your phone to convert to 1.6 Donut - run that first, then run main zip).. if you still have probs see the bottom of this post
If you are switching from Hero or Cliq see the bottom
This rom does NOT include Google Apps
Install this first for Google Apps:
http://www.mediafire.com/?z3ozzmyzrad
If coming from Hero/Cliq
Run recovery mode
Hit console
Type these commands:
mount /data
cd /data/data
rm -r com.google.*
rm -r com.htc.*
rm -r com.android.*
Thanks to Cyanogen, Maxisma(for my base on a2sd), daproy (RAM hack),
Amon_RA (recovery image)
For help:
Search on Wave for the title of this post
Follow me on Twitter @wesgarner

wesgarner said:
Trick is it utilises both Cyanogen's compcache plus the swap for a very FAST build
Click to expand...
Click to collapse
I remember reading somewhere that this will lead to problems, and should not be done. From my understanding you should use one or the other, not both.
(otherwise wouldn't we see alot more Devs using that trick?)

can a no wipe update be done from cm 4.2.5?

Thanks for you~
hey guys Good work

Only thing ive ever had come out of the 10mb hack was random reboots, random ringtones. phone ringing when noone was calling. crashing getting texts...
But thanks for the effort lol

Didn't work. Caused me to get stuck on G1 boot screen for an hour. Then totally wiped and again sat there on the G1 boot screen. What is odd is that for some reason my recovery image disappeared and went to JF 1.42 so I couldn't even use recovery. Now I am trying to get my phone back to the way it was.
Fortunately, I still had all the files I needed on my SD card to get me back to where I was. i reinstalled the recovery image and then was able to load my recovery image again. How it got to JF 1.42 (which hasn't been on the phone is many months) is beyond me. I have been doing phone mods for many years and this is the first one that didn't work out.

So, no go?

Unexpected end of Archive......

I tried to do the same thing (cm 2.4.5 + ramhack + swap) but got nowhere, system became sluggish. This should work very well in theory (this should be fast as dwang but with all cm goodies) but I haven't been able to make it work so I'm following this thread and see how it works.

pascanu said:
I tried to do the same thing (cm 2.4.5 + ramhack + swap) but got nowhere, system became sluggish. This should work very well in theory (this should be fast as dwang but with all cm goodies) but I haven't been able to make it work so I'm following this thread and see how it works.
Click to expand...
Click to collapse
i used to run CM 2.4.x with ramhack and swap no problem, but since 2.4.5 the ramhack slowed my system down so much i just decided it would be better to go without it

btmec said:
Didn't work. Caused me to get stuck on G1 boot screen for an hour. Then totally wiped and again sat there on the G1 boot screen. What is odd is that for some reason my recovery image disappeared and went to JF 1.42 so I couldn't even use recovery. Now I am trying to get my phone back to the way it was.
Fortunately, I still had all the files I needed on my SD card to get me back to where I was. i reinstalled the recovery image and then was able to load my recovery image again. How it got to JF 1.42 (which hasn't been on the phone is many months) is beyond me. I have been doing phone mods for many years and this is the first one that didn't work out.
Click to expand...
Click to collapse
Looking into the G1 bug now, did you get a logcat?
Going to try to test on my old G1 in a few, if you have Wave get on there if you want to help debug

sacredsoul said:
can a no wipe update be done from cm 4.2.5?
Click to expand...
Click to collapse
Yup no wipe

no work.
Did not work ... G1 stays in boot screen and reboot ...

Takenover83 said:
I remember reading somewhere that this will lead to problems, and should not be done. From my understanding you should use one or the other, not both.
(otherwise wouldn't we see alot more Devs using that trick?)
Click to expand...
Click to collapse
Well with the newer compcache modules, it doesn't seem to cause any problems

grafyman said:
Did not work ... G1 stays in boot screen and reboot ...
Click to expand...
Click to collapse
Yea I am about to test on my G1 to look around for the bug - my main phone is my myTouch so I didn't test before I posted LOL - my bad on that (it is just in this recent version since worked fine on a friend's G1 before this post)
If you have wave, could you get on there if you want to help debug?
If you have a logcat, just post it here or on pastebin and shoot me the link on Twitter (@wesgarner)

One big thing I am trying to work on here is going through and doing some things Cyanogen couldn't do
Next version I am going to do zipalign on the Google Apps to post that (on a sep update zip for people who prefer to stay legal, hope I don't get a D&S - don't think anyone else has)
I am thinking about doing a choose your kernel like Cyrowski did here - good idea?
Please give any suggestions, this just seems a good way to do some playing around and experimenting that is a project by everybody - developers and users
Also, next project: Write a test into Music.apk to ignore files less than 30sec (I have my voicemails through Visual Voicemail and Google Voice)
It is annoying as crap! Going to get the GIT for Music.apk later today

Can someone mirror this or create a torrent? media fire is so slow today

Ok im seeding but warning if you go from 4.2.5 like me you may get a boot loop like i am right now good thing i backed up
Torrent link: http://bit.ly/blah234

guys this rom is ****. i flashed a number of times, then i wiped all partitions and tried again. dosent work just g1 boot loops, im going to stop seeding. dont trust this guy this rom is bad

LOL, dude, why are people keep thinking any Rom based on the same rom works better? Wake up people. If you use Cyanogen, use Cyanogen, If you use Dwang, use Dwang. any other so call hack does not make it better. Wake up, wake Up. Wake Up. LOL.
I have been using the so call Ram hack, it does NOT make it better after long hour of usage. It slows it down. At least on my G1. I reverted back to Stock boot img, it just WORKS.

[MOD][ROM][FAST/STABLE][LINKS ADDED] ZXK Eclair [BETA][5/10/10]

...............................................

.....................................

.........................................

`````````````
nice job...try it now!...i saw it on twitter two days ago...

zhang yixi said:
nice job...try it now!...i saw it on twitter two days ago...
Click to expand...
Click to collapse
Okay cool, Let me know how you like it and if you got any problems just post and i will get to them
Fastest way to send a bug is with twitter
LOL i am a twitter addict and have it refreshing every 5 minutes haha

And which is the default frequency? 528? Or...
Anyway, flashing right now. I LOVE ur Roms.... hehehe

Just flash.
I feel abit slower than cm5.0.7 test3.
Thanks for the hard work.

Hello New Thread.
I kinda figured you fell asleep last night Kolohe. I will check your beta when I get home from work later today and put up the mirror. I am going to keep your old ROMs up there too

got a question.
Did a total wipe and when it booted up first time, I got a low space warning. Apparently a whole bunch of my apps that were on SDcard came back as installed. And because on first boot, apps2sd isn't on yet, it tried to put them on internal (I had about +/- 80 apps come back from my 139 total)
So I backed out, rewiped data, dalvik, and ext, and reflashed rom. It boot up fine again, but once again, it immediately installed 7 of the apps (replica island, docs to go, pobs... just to name a few). So I moved them to sd card and all is fine.
The question is:
1. Is this normal? I've never had this happen before CM5 based ROMs. I haven't tried any other Eclair roms except the CM5 based ones and I wasn't sure if this is a behavior that's normal for 2.1 roms.
2. Why only some of the apps come back? Isn't wiping ext supposed to clear it all out or am I mistaken?

Just wanted to let you know, there seems to be a problem with using Backup for Root users. It will break any apps allready installed and fix_permissions or Repair ext will not help, I have found this to be true on all CY5 based roms.
EDIT:Restoring SMS,Call log and even Market DB seems to work fine after running Fix_permissions, Restoring APPS Does Nothing.(No APPS Restored) It Was trying use the Dusted-donuts hack that caused the apps to be Broken.
EDIT:::: The problem WITH APPS NOT WORKING APPEARS TO HAVE BEEN CAUSED BY ME TRYING TO USE THE JIT HACK "DUSTED-DONUTS" LIKE I DID WITH 4.1. I believe the JIT Flash Update for Cy5 will work though.
EDIT: JIT-HACK It does work.http://droidbasement.com/db-blog/?p=245 this is what i used.
Thanks again for a great rom!
This thing Flies!
I'm using the Jit-Hack And AnyKernel OC Patch,changed swappiness to 95 in 86supersettings,and cpu refresh to 1000000(kills batt),and Cpu Min/Max to 122800/716000. Still using SetCPU for Sleep/failsafe Profile.
EDIT2: I just noticed that at the initial google sign in screen you can press menu and in addition to the normal Wireless settings option there is now an option to disable auto restore!( I know you probably already knew that and it has been mentioned a hundred times!)

well gonna give this a try let u know soon for any bugs

To confirm this is JACP?

Watching logcat I saw that debugger daemon is enabled. I/Debug.
and is this based on CE-5.0 t2? or are patches for T3 in place?

quick question:
If I extracted the boot img from this rom and flashed it with my currently installed CM 5.0.7 test 3 would it still have the same speed boost, optimization, and cache clearing settings?
Not that I don't want to flash this rom itself, but I was just wondering if I could also try out the features with another.

Will fix the apparently problem but that might be caused by thenew boot script that wipes the dalvik cache. .. will be working on that later today

quick question:
If I extracted the boot img from this rom and flashed it with my currently installed CM 5.0.7 test 3 would it still have the same speed boost, optimization, and cache clearing settings?
Not that I don't want to flash this rom itself, but I was just wondering if I could also try out the features with another.
Click to expand...
Click to collapse
You can I suppose,
Just needs to be a CM5 based rom

Just wanted to let you know, there seems to be a problem with using Backup for Root users. It will break any apps allready installed and fix_permissions or Repair ext will not help, I have found this to be true on all CY5 based roms.
EDIT:Restoring SMS,Call log and even Market DB seems to work fine after running Fix_permissions, it is just trying to restore apps that messes it up.
EDIT:::: The problem WITH APPS NOT WORKING APPEARS TO HAVE BEEN CAUSED BY ME TRYING TO USE THE JIT HACK "DUSTED-DONUTS" LIKE I DID WITH 4.1. I believe the JIT Flash Update for Cy5 will work though.
Also as a side note, I think apps2sd must be enabled by default,or get rid of the auto app restore thing. I think it is going to confuse people and clutter up the threads.
But thanks again for a great rom!
EDIT2: I just noticed that at the initial google sign in screen you can press menu and in addition to the normal Wireless settings option there is now an option to disable auto restore!( I know you probably already knew that and it has been mentioned a hundred times!)
Click to expand...
Click to collapse
Ohh. I think I might know why that is happening and I think I night be able to fix that.... but seeing that I don't use it I might need to find a tester to see if it works

got a question.
Did a total wipe and when it booted up first time, I got a low space warning. Apparently a whole bunch of my apps that were on SDcard came back as installed. And because on first boot, apps2sd isn't on yet, it tried to put them on internal (I had about +/- 80 apps come back from my 139 total)
So I backed out, rewiped data, dalvik, and ext, and reflashed rom. It boot up fine again, but once again, it immediately installed 7 of the apps (replica island, docs to go, pobs... just to name a few). So I moved them to sd card and all is fine.
The question is:
1. Is this normal? I've never had this happen before CM5 based ROMs. I haven't tried any other Eclair roms except the CM5 based ones and I wasn't sure if this is a behavior that's normal for 2.1 roms.
2. Why only some of the apps come back? Isn't wiping ext supposed to clear it all out or am I mistaken?
Click to expand...
Click to collapse
Yes it is normal but if you want to turn it off before you log in press menu button in setup andthere should be an option to turn it off

Ohh. I think I might know why that is happening and I think I night be able to fix that.... but seeing that I don't use it I might need to find a tester to see if it works
Click to expand...
Click to collapse
I would be willing to test any of your ROMs that would help you out. I am good at BART Backup and Restore! Just let me know.

Ohh. I think I might know why that is happening and I think I night be able to fix that.... but seeing that I don't use it I might need to find a test
Click to expand...
Click to collapse
I would be willing to test any of your ROMs that would help you out. I am good at BART Backup and Restore! Just let me know.
Click to expand...
Click to collapse
Okay when I get home I willtry and fix

[ROM] (Flytouch 2, SuperPad, WWE10) Froyo

This thread is for the custom Froyo rom for the Flytouch 2. It is a port of the first Flytouch 3/Superpad 2 Froyo rom, adapted to run on the flytouch 2. I will update this post whenever a new version has been released.
This rom will only run on tablets which display a version number in the bottom-right "Infotmic" screen when first turned on.. If yours doesn't display a number there, you will need to flash firmware v2852 first, see below in FLASHING V2852
INSTALLATION
Installation is slightly different from normal releases because it requires flashing in 2 steps. Luckily, it's really easy:
1. Download bootable SD-card image and unzip. Pick an image from the RELEASES section at the end of this post.
2. Write image to an SD-card that's at least 1GB in size using Win32DiskImager:
Get Win32DiskImager here: https://launchpad.net/win32-image-writer
In Win32DiskImager: When you open it, there is a button to browse the .img file and after that, at the right of this button there is a selector for the SD-card. Select it, then click write and it's done.
When finished, take out the card.
In linux, you just unzip the file and use dd to write it to the sd-card:
Code:
dd if=/path/to/sdcard.img of=/dev/sdX # (where sdX is your scsi disk device, check dmesg)
3. Turn off tablet and put sd-card in TOP slot (between the 2 usb ports).
4. Turn on tablet. It will report that it is booting off the sd-card, and that it's flashing kernel + filesystems.
5. Take out the sd-card when the tablet asks you to do so (takes less than a minute). Put it in the OTHER sd-card slot (bottom one), and reboot the tablet by holding down the power for 10 seconds to turn it off, then press it again to turn it on.
6. You will now see the tablet booting with a *GREEN* screen. The screen will flash twice to indicate it's starting. The flashing itself will take longer than in the previous step, a few minutes. If succesful, it will automatically reboot, after which you're done and you're booting the new firmware! You'll see a different boot screen (equalizer on a black background)
7. After it has booted and you have unlocked the screen, reboot the tablet first thing! First boots in android always tend to be behave erratically. This is unrelated to this firmware and applies to all Android setups.
If step 6 fails (which is very unlikely), it will stay on the green screen and it will keep on flashing the screen. In that case, you'll have to turn it off. Most likely problem for this is a corrupt SD-card. See troubleshooting below.
Make sure to never put that sd-card back in the top-slot without erasing it first, as it will reflash your tablet!
TROUBLESHOOTING
The 'green screen' keeps flashing!
The installer will dump a text file on the root of the sd-card which you can inspect. The file is called fail_reason.txt. If no such file exists, things are seriously wrong and the tablet couldn't even properly write to the sd-card. If using another SD-card, or rewriting the SD-card doesn't help, please upload the fail_reason.txt file here.
Flashing was succesful, but the system freezes at the android animation!
For this firmware to work, you need to have a recent version of u-boot. You can tell if you have this by looking at the INFOTMIC bootscreen you see when you turn on the tablet. If the bottom right corner does not show a version number, then you don't have it.See instructions below.
FLASHING V2852
You need to flash this firmware to install a new version of u-boot. To flash this firmware, you will need to connect your tablet to your PC using an USB A-A cable, OR create a bootable SD-card.
Download firmware V2852: http://www.mediafire.com/download.php?3bkklw36b1414nd
Download and unpack IUW: http://www.mediafire.com/download.php?3572bd7zfjo0r0y
Start IUW
If you use an USB cable: Click 'Link USB' on the left, select 'easy burn' from USB Mode pulldown in the right. Connect tablet to PC with the tablet turned offf, then turn it on by pressing & holding the menu+home buttons, then pressing the power button until it turns on. Release the menu+home buttons after a few seconds. Windows should now detect a new USB device. Install the drivers that are in the iuw1.1/otg_driver directory.
If you create a bootable SD-card, Click 'boot disk' on the left instead. Select sd-card to flash on the right
Select the IUS file form the v2852 firmware under 'Choose a wrapped image'
Click 'burn' to flash the tablet or create the sd-card. If you created an sd-card, boot the tablet with the sd-card in the top-slot, between the 2 USB connections.
TODO
How to enable 3G support for USB dongles?
(**) Tested:
wifi, ethernet port
battery status works, g-sensor works
touchscreen works, including calibration
HD video playback works (I recommend Meridian player)
Market works (full), Youtube works
angry birds works ( thought I'd mention it )
The firmware has already been rooted! You can connect using adb over wifi, and type 'su' to become root. Find your IP address using the Android System Info app.
GPS confirmed
VIDEO
Video demonstrating how to flash the tablet after having created the bootable SD-card: http://www.youtube.com/watch?v=47kf4-Vbba8#t=3
RELEASES
April 24th 2011, V5: http://www.mediafire.com/?1ka7ngpi82grmfm
Added older version of YouTube (1.6.21) which works
Fix touchscreen calibration
Added LauncherPro as alternative launcher
March 2011, V4: http://www.mediafire.com/?oc1bwnq71smb09k

verandi said:
Hi everyone.
I just made a personal version of system.tar.gz, and I thought it could be usefull for someone.
Most considerable changes:
Calendar and contacts synchronization now working again.
Simple stock froyo keyboard, without chinese characters.
Replaced youtube with the old working version.
Market updated to last version (no paid apps, though.).
Default launcher replaced with launcher pro, which is considerably faster.
Removed phone and telephony settings (see below)
Other changes:
Removed stock browser, replaced with dolphin browser HD.
Removed default file explorer, replaced with File expert (first free file explorer with working root that I found).
Changed alarm clock.
Changed calculator (but has wrong visualization).
Changed music player with music mod.
Added facebook, maps (+ navigation + latitude +places), chrome to phone, google search, google reader, terminal emulator, Titanium backup, voice search. adobe reader.
Maybe I deleted some other stupid flytouch stock apps, but actually I don't remember.
Warning, notes etc...:
All apps are free apps from market.
Phone apps (Phone.apk, TelephonySettings.apk) removed for test, due to suspected battery drain (Someone said so...), so:
Phone settings don't work (gives you force close when you tap on mobile settings menu)
Don't install if you use 3g adapters, as I think you won't be able to use them.
Maybe some future workarounds for paid apps on market won't work.
App2sd doesn't work. (Didn't even work before. I think there's some problem in the kernel with device mapper and crypto). I'll try to implement the fake app2sd that uses an ext partition on sd.
This is just a personal versionof stargulus' system files with apps I'm used to have on my phone, so maybe it won't fit you.
How to install:
First important step: boot in recovery mode (back + home +power until you get in recovery menu), and wipe cache and data. This must be done. It also helps to have stragulus' calibration file installed correctly.
Prepare the sd as described in the first post of this thread using the last Stragulus' sdcard image (v4, See link in this post).
Go to "stage2" directory and replace system.tar.gz and system.tar.gz.md5 with the downloaded ones.
Flash.
The first boot will be quite long, but it's normal.
While using the flytouch for the first time, it will probably lag and hang. Just reboot and it won't happen anymore.
File link: http://www.multiupload.com/Z9CONJVPQO
I hope this will be usefull. Advices are welcome.
Click to expand...
Click to collapse
Cheers! I welcome custom mods of the base rom. I'm willing to add them as alternatives to the first post by linking to the introductory posts. In this case, it looks like parts of it are suitable for integrating into the base froyo rom (e.g. calendar & contact sync fix). What exactly did you do to fix those?

Wonderful, downloading now at 7.8K/sec (why sooooo slow?)
Is Google Sync fixed?
Thanks,
Barak
Later:
Well, if I add Verandi's MOD I get sync but I loose calibration option.
Still, I prefer the MOD with sync.
Thank you guys. Amazing Job !!!
1-5-2011
Please note that verandi has created a V5 mod that adds sync option without eliminating calibration.
http://forum.xda-developers.com/showpost.php?p=13343444&postcount=54
Good luck.

Your uboot - 0.6.1.2 (587) http://www.mediafire.com/?4hx8xt38vnhh22b
My uboot - 0.6.1.5 (587) http://www.mediafire.com/?bv4ixzeq34q5bi7
what's the latest?
which should I use?
EDIT:
If possible enable a swap partition to optimize tablet in ROM? (we have little RAM)
Camera have a problem. Green image in V5 (24/04/2011)

@ Stragulus
I've been waiting for
Thank you for your work

Market will not dowload
Well once again my hats off to you Straguls for a job well done I installed the version 5 rom with no issues however the Android Market still only displays the free apps and will not download and install any of the apps it states download unsuccessful any help with this matter would be greatly appreciated.
Thanks
Steve

stragulus said:
This rom will only run on tablets which display a version number in the bottom-right "Infotmic" screen when first turned on.
Click to expand...
Click to collapse
In my case loader version number is missing. But u0 is 0.6.1.2_1.4.587_OV2655 and u-boot from 2852. And all work fine.
Probably condition is flashing firmware 2852 in the tablet instead of only u0?
IMHO.
Because the firmware is full image and contained u-boot and u0. Flashing u0 need only if camera don't work with 2852 from full image. Of course, if the tablet has not been purchased already with firmware 2852 and above. Without this step you will get many reports of "fre-e-e-ezing" or "stop in android on screen" like in the previous thread.

hello
I have stitched from card Froyo V5
The tablet is loaded and asks calibration, but it does not work: (
Was 3245, but it has ceased to be loaded and I have updated on Froyo
I do not know what at me uboot how it to look? Probably to update it with sd?

jp08 said:
загружатся
Click to expand...
Click to collapse
По русски спроси. Я tuzzz c форума china-iphone.ru.
Ask question in Russian. I tuzzz from the forum china-iphone.ru.

Вообщем поставил Froyo (v5)
после прошивки при первом запуске появляется калибровка экрана, но на нажатия никак не реагирует
поставил назад 3245, на ней все нормально
Возможно ли это из-за загрузчика uboot, как можно посмотреть его версию и возможно ли обновить его с SD, т.к. возможности с ПК нету?
google translate:
In general set Froyo (v5)
after flashing at the first startup, a calibration screen, but clicking does not react
put back 3245, her everything is ok
Is this possible because of the boot uboot, as you can see its version and whether it is possible to update it with SD, because capabilities with a PC no?

Answer on russian forum.
Also read from here and below.

_barsuk_ said:
In my case loader version number is missing. But u0 is 0.6.1.2_1.4.587_OV2655 and u-boot from 2852. And all work fine.
Probably condition is flashing firmware 2852 in the tablet instead of only u0?
IMHO.
Because the firmware is full image and contained u-boot and u0. Flashing u0 need only if camera don't work with 2852 from full image. Of course, if the tablet has not been purchased already with firmware 2852 and above. Without this step you will get many reports of "fre-e-e-ezing" or "stop in android on screen" like in the previous thread.
Click to expand...
Click to collapse
That could be true indeed! I thought those who fixed their problem only flashed U0, but maybe all of them actually tried to flash all of v2852 with the IUW tool. Upshot here is that it should be possible to flash the entire firmware using a bootable SD-card, e.g. not requiring an USB cable.
Can anyone confirm that creating the bootable SD-card for FW2852 using IUW as described in the first post fixed their install of the froyo setup?

If you create a bootable SD-card, Click 'boot disk' on the left instead. Select sd-card to flash on the right
Select the IUS file form the v2852 firmware under 'Choose a wrapped image'
Click to expand...
Click to collapse
After Burn a card sd the empty
This way does not work
Used Win7 x64 and virtual WinXP x86

Excellent Work
Many thanks stragulus!!!!!!!
Now I once again have a usable Pad - the Calibration works perfecly!!!
My route to Froyo was from 3245 to v4. I HAD to flash U-Boot-Nand FIRST. This gave me the Infotm code in the bottom R.H.corner. The only problem was with the calibration.
Again MANY THANKS. Please continue to develop for the Pad.

jp08 said:
After Burn a card sd the empty
This way does not work
Used Win7 x64 and virtual WinXP x86
Click to expand...
Click to collapse
Hmm. I do now recall that someone tried all those methods before to no avail. When I flashed this firmware, I think I did:
* Flash all of FW2852 (over USB)
* Found out that it didn't work 100% as it still booted an older ramdisk
* So after that, flashed U0 with u-boot-nand.bin. That triggered the 2-minute tablet going crazy on first boot.
* Then flashed all of FW2852 again, and now it worked.
Soo.. I think bottomline is, if you haven't seen the tablet go crazy for 2 minutes, it probably didn't work. Question is, is just flashing U0 once with u-boot-nand.bin enough..? It appears this does not work for everyone!?

stragulus said:
Cheers! I welcome custom mods of the base rom. I'm willing to add them as alternatives to the first post by linking to the introductory posts. In this case, it looks like parts of it are suitable for integrating into the base froyo rom (e.g. calendar & contact sync fix). What exactly did you do to fix those?
Click to expand...
Click to collapse
Hi!
I replaced GoogleContactsSyncAdapter.apk and GoogleCalendarSyncadapter.apk with the ones from my phone. I am 98% sure I replaced only these two, because I didn't note down the names.
Now I'm trying to solve the next problem I have in the list: I can't leave the pad in standby, as it drains the battery like it was awake.
Yesterday I had a look at proc/wakelocks file to see which processes are requesting wakelocks.
Comparing this file to others around the net and the one of my phone, I found out that some processes were active during standby (they had 0 value in sleep_time row).
Now I haven't here my flytouch, so I can't be precise (I'll edit this lines next days), but I remember that some processes and powermanager were never sleeping (in all other wakelocks files, powemanager was sleeping on standby but main process not, so I think powermanager is faulty and main process not.).
Powermanager is a class contained in system/framework/services.jar so I tried replacing this file with my phone's one. It worked as the wakelocks file was showing that powermanager began to sleep on standby, but I had no improvement in battery life on standby, as, I'm quite sure, the other processes prevent the full sleep of the device.
To you and everyone who reads this: can you give me a help?
Can you fully recharge the flytouch, then disconnect the power supply, note down the start time, live it in sleep mode and then measure how long it takes to get discharged?
It tried myself today: unplugged at 16.30, left it in standby, died at around 19:20 ---> 2h50m of battery power on standby.
(If you also can tell me how long it stays on when you use it, and what kind of use you made, I would really appreciate too! )

Hail to Stragulus.. unlocking the beast!!!!
stragulus,
as usual.. I am riding on someone else's brilliance.. thanks for the update..
Will load it up tonight when get home from work..
My only wish is app2sd...
it has made such an improvement to my Evo with ability to load programs in..
So if someone wants to come up with a fix.. I am sure you will make many internally grateful!!!!
Edit after flashing:
Flashed the clean version WITHOUT verandi addons..
the Calibration works perfectly
feels fast and clean..
had problems with launcher pro .. and Titanium backup..
for some reason using Launcher pro it would not allow Titanium to see the sdcard.. thus couldnt restore my backups..
Played round for a while.. upgraded to Titanium 3.6.1.1 same thing..
went in and wiped Dalvik cache.. still no go..
have shut down launcher pro and installed ADWlauncher (almost the same as launcher pro)
walla.. now Titanium is seeing the SDcards and backup.. confirmed that it restored backed programs and data..
Market is working for me.. just wondering if we can port market from Myn’s Warm TwoPointTwo - RLS 5 into this rom..
as this may be the workaround that will get past the only free apps showing.. I am using it on my Evo and in China..
so usually only get to see free apps.. but with MWTPT I am getting all apps.. I do understand there is a app floating round that is suppose to be able to reset Market in to thinking it is in a zone that will allow it to show all apps.. may need it to load in to this Rom..
Will put it through its paces and report back over the coming week..

verandi said:
It tried myself today: unplugged at 16.30, left it in standby, died at around 19:20 ---> 2h50m of battery power on standby.
(If you also can tell me how long it stays on when you use it, and what kind of use you made, I would really appreciate too! )
Click to expand...
Click to collapse
Hmmm. This time is extremely low for standby mode. I use kernel from 3245. With this kernel battery indicator won't work properly but OS works more stable.
Also I removed Phone.apk and TelephonyProvider.apk. I don't need 3g modem. And 3g modem still does not work with this firmware.
With full charged battery I disconnected charger from tablet at 22:00 (in my local time). Now is 5:25 in my local time and tablet has ~4% battery indicator. From my experience tablet shut down after 5-10 minutes. All this time tablet is in standby.

Verandi
Excellent work and thank you for the Google sync fix - it makes my wowpad WOW!!!
Can you please add these files to the V5 version? Without them there's no sync. If I add your V4 files to the V5 rom there's no calibration. I wonder what else is lost !!!
Thanks,
B

stragulus said:
Cheers! I welcome custom mods of the base rom. I'm willing to add them as alternatives to the first post by linking to the introductory posts. In this case, it looks like parts of it are suitable for integrating into the base froyo rom (e.g. calendar & contact sync fix). What exactly did you do to fix those?
Click to expand...
Click to collapse
Great job. Thank you about that. I've a little question.
I've updated my Flytouch with you sdcard V5. Everything works fine, but i can't get the connection with USB 3G dongle. How i can do ?
There's a program to get the connections ?
I've tried with "quick setting" but nothing happens.
I'm looking forward to hearing from you about that.
Best regards

[APP] Boot Manager Pro - Dual boot unlimited ROMS! [WIP]

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

[Q] To root or not to root for update

Hi
I have a Samsung Galaxy GT-I5801 with me for past couple of years.
Its current OS spec are:
Firmware version- 2.2
Baseband version- I5801DDJP2
Kernel version- 2.6.32.9 [email protected] #2
Build Number- FROYO.DDJP6
My phone has become kind of slow, like for even basic tasks like opening call log or messaging app, it takes good 10-15 seconds. Sometimes it even goes unresponsive when trying to end a call thus causing call to continue thus carrier balance reduction. There are no 3rd party apps installed on it. Even updating the pre-installed apps gives the message of memory being low.
Now my query is:
Will flashing it to a custom ROM will improve its working at least in the basic areas of call and texting?
If so, then which is the most suitable custom ROM?
Is it necessary to root the phone before flashing it ?
Which tool is best/easiest for said purposes?
Please go easy on me, I've been out of the IT and tech game since past 1 year and bit rusty on these things

RudraP said:
Will flashing it to a custom ROM will improve its working at least in the basic areas of call and texting?
If so, then which is the most suitable custom ROM?
Is it necessary to root the phone before flashing it ?
Which tool is best/easiest for said purposes?
Click to expand...
Click to collapse
I would say yes. I don't know what is causing the freezes, but (beside that this could also be a hardware problem) a custom ROM should fix that.
Any GB-based ROM should do a fine job. There are also Froyo-based ROMs for our device. The CM7.2 build by marcellusbe does a very good job.
Nope. If you flash via Odin (Flash-Software for Windows) you just need a usb-connection. If you flash it via recovery, you may need to flash a custom recovery first.
Derp - another proud Galaxy3 user :highfive:

DerpyDerp said:
I would say yes. I don't know what is causing the freezes, but (beside that this could also be a hardware problem) a custom ROM should fix that.
Any GB-based ROM should do a fine job. There are also Froyo-based ROMs for our device. The CM7.2 build by marcellusbe does a very good job.
Nope. If you flash via Odin (Flash-Software for Windows) you just need a usb-connection. If you flash it via recovery, you may need to flash a custom recovery first.
Derp - another proud Galaxy3 user :highfive:
Click to expand...
Click to collapse
I tried SuperOneClick but it failed to even detect my phone, let alone root. Tried rooting directly through phone by installing z4root on it. It too failed to root my device, just a blue screen saying "Running Exploit" with z4mod logo kept on displaying for 10-15 minutes, after which phone switched off itself. Had to power it back on myself. Tried it couple of times more but no success.
So now if I use Odin to directly flash the firmware to a modded one, would it work, considering the fact that the phone hasn't been rooted. More importantly, would it be wise to do so? Don't want to hard brick the device as its my backup device after my Xperia SP took a plunge in the water and now fails to even boot, just vibrates thrice and that's it.
Update:
Took a leap of faith with Odin and Cyanogen & now the device is rockin' like a grandma with a new hip replacement Lags no more, operation is smooth, but a 2nd minor problem has cropped up.
It now refuses to install any app from Play Store citing Insufficient Space. I changed the default installation space to external but still the problem persists.
Update 2:
For my above mentioned problem, looks like something to do with Gapps but I don't know what it is and what to do about it. Moreover as today I tried to make calls or send messages, I found out I'm unable to do so. The dialler dials after good 2-3 minutes of pressing/selecting the dial option for a number while message inbox is empty but it refuses the receive any sms citing Inbox is full. I thought just flashing the firmware should do the trick but looks like it just was the tip of the iceberg.

You can find the gapps (Google Apps - like Play Store, Gmail, ...) here:
http://goo.im/gapps/
Assuming you're on Gingerbread (CM 7.x) it's this package: http://goo.im/gapps/gapps-gb-20110828-signed.zip
Put this zip-file on your SD card, power off your phone and/or reboot to recovery. Navigate to "Select zip from sd card" -> select your gapps.zip and flash. Then "wipe cache" and "wipe dalvik cache" anywhere in the submenus Just to make sure the gapps get recognized correctly.
Another trick for expanding the internal storage is Link2SD. You need a 2-partition sd-card for this. 1. partition with FAT and 2. one with ext2/3/4
Link2SD will mount this second partition to the internal storage to expand your storage for apps and other system stuff.
You know... Getting the most of a half-dead low-end device needs a bit of geekiness

bad zip
Well I selected erase all data option in the phone which booted it into recovery mode. Here I cleared the cache and the user data. When I tried to install zip file from sd card it gave the following error message, "Can't open /sdcard/gapps-gb-20110828-signed.zip (bad) Installation Aborted"
What seems to be the problem now?
Update:
Tried again and this time it worked. Now everything is running fine. Thanks a ton for the help mate, can't express my gratitude through words.
I do want to ask one thing here.
If I install this, http://forum.xda-developers.com/showthread.php?t=1803180, will the JB experience be coupled with performance drop ?
Honestly Cyanogen has turned me into a junkie, now I want to try on the new but stable mods. Moreover as my Xperia SP is now out of warranty, I'm planning to get it fixed and then root and flash it too!