Related
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.
Like i've posted in the setup thread from Liquid, this setup is the best i've tried until now, the only one that make missing call an old history in fact
Another better than ever pola 100 nand / nand setup
Download rom (5.5 version - 6 doesn't work with polaris kernel) : Scoot CyanogenMod (RLS5.5) [16.03.2011] and put it on your sdcard in a directory named andboot (at the root level)
with atool download the latest 2.6.32 kernel, modify it as desired
flash your unlocked phone following this tutorial or use atool scripting ability
update needed : none
work : everything except camera !!!! very smooth and very reliable(no missed call for 1 week, that's a revolution) and not so bad battery life
finally, development kernel seems to be not so far from "ready to production" status, with even better nand stability
we're waiting rom update and next krazykilla's kernel with polaris support, for a better stability and ability tu put data on ext4 partition
Thank you to scooter, liquid nr2jt and all androidhtccrew for their tuff work
Nand is not perfect and run corruption sometime that crash your setup : use the nand startup "backup/restore" data ability after you have configured your rom and favorite applications, to avoid loss of everything : it will create a 256Mb image of nand memory in your SD card /andboot directory that you can restore later in case of crash.
you can increment this backup later if you are happy with future modification of your rom
TIPS : noticed that setup as it is is good enough, people at cyanogenmod know their business
- Tip 1 : in atool, you can try to increase advanced battery capacity to improve accuracy because N2jrt has noticed battery calculation is not good and there's a correction factor of 1.6 to apply (i put 1900 but you can increase to 2200 in theory)
- Tip 2 : you can download Roguetool from the market to overclock your phone
- Tip 3 : try the app named killerauto from the market, it does a very good job with very comprehensive settings to free your ram in real time (and increase battery life)
- Tip 4 : In cynogenmod parameters/performance : check the "keep home in memory option" and activate compcache (10%) to get better result - i don't activate JIT
- Tip 5 : i've noticed that's the battery widget is cause of some trouble sometime, you can get rid of it in this case
what's next
- make polaris' atool development kernel compatible with release 6 : thx to scooter and liquid by advance
- Make crazykilla kernel with ext4 support available for polaris (release from his #54 thread doesn't work for me) or maybe unified every kernel to get the best one
crazykilla's kernel is a usual kernel without the polaris support compiled, i don't know why the #54 version don't work and i can't test it anymore (my polaris has a toasted nand).
l1q1d said:
crazykilla's kernel is a usual kernel without the polaris support compiled, i don't know why the #54 version don't work and i can't test it anymore (my polaris has a toasted nand).
Click to expand...
Click to collapse
i get the error message
"install module for this kernel
apply modules/androidupdate.tgz
Failed
from sourceforge"
maybe i missed something
Blinking screen
I've tried it with my XDA Orbit II and all I get is the white blinking screen after running haret. It's written in the man that it takes a lot of time, so I left it and went to sleep When I woke up, the screen was still blinking the same way and had to remove the battery to reboot. WM booted fine, there were files system.img and data.img created on the microsdcard of the size of 300mb (I don't want to flash it on NAND as it is my first attempt to install new software on phone). I tried Froyo, now trying Eclair and after an hour it looks the same. What might be wrong? Should I try stable kernel or other setups?
Krysiul said:
I've tried it with my XDA Orbit II and all I get is the white blinking screen after running haret. It's written in the man that it takes a lot of time, so I left it and went to sleep When I woke up, the screen was still blinking the same way and had to remove the battery to reboot. WM booted fine, there were files system.img and data.img created on the microsdcard of the size of 300mb (I don't want to flash it on NAND as it is my first attempt to install new software on phone). I tried Froyo, now trying Eclair and after an hour it looks the same. What might be wrong? Should I try stable kernel or other setups?
Click to expand...
Click to collapse
i don't know such setup sorry, i work on nand only to get real speed
I don't want to try flashing on NAND until I find a setup that would satisfy me and work well as I would in practice lose the phone for some time while trying to make it work. So far I've succesfully installed this, but I can't make the PIN code work. I tried to disable it in WM in phone settings, but when I do it, it requires me to enter the PIN, and doesn't accept it, just as Android does :/ Does the PIN code problem occurs in NAND installation as well?
this setup is really not ready. i tried so many times and it always hangs and at the end you'd be reinstalling the system back. I'm sticking back to the Not-So-Super-Froyo setup and has since found it to be very very stable although no camera and no GPS working on it. Just a bit of tip to all those who try and occasionally reinstall, after you have found a good stable setup, install your basic favorite apps and games, then get reboot the phone, access the Android Boot Menu and choose Backup Data on the choices. The system will save your stable setup on an image file on your sdcard. So anytime you have a system crash, you can just choose to Restore Data from the Boot Menu. Saves you a lot of installation.
arzakem said:
this setup is really not ready. i tried so many times and it always hangs and at the end you'd be reinstalling the system back. I'm sticking back to the Not-So-Super-Froyo setup and has since found it to be very very stable although no camera and no GPS working on it. Just a bit of tip to all those who try and occasionally reinstall, after you have found a good stable setup, install your basic favorite apps and games, then get reboot the phone, access the Android Boot Menu and choose Backup Data on the choices. The system will save your stable setup on an image file on your sdcard. So anytime you have a system crash, you can just choose to Restore Data from the Boot Menu. Saves you a lot of installation.
Click to expand...
Click to collapse
Yes i've read this technique somewhere, maybe i will try it next time
thank you for the tip anyway
Krysiul said:
I don't want to try flashing on NAND until I find a setup that would satisfy me and work well as I would in practice lose the phone for some time while trying to make it work. So far I've succesfully installed this, but I can't make the PIN code work. I tried to disable it in WM in phone settings, but when I do it, it requires me to enter the PIN, and doesn't accept it, just as Android does :/ Does the PIN code problem occurs in NAND installation as well?
Click to expand...
Click to collapse
yes if i remember well my past haret experience, i had to deactivate PIN in WM to make android work
arzakem said:
although no camera.
Click to expand...
Click to collapse
what kernel do you use ? i use liquid's 2.6.25 + kernel update
I finally follow your advise and came back to "not so super" and begin to use the "backup data" function...
The best setup so far
I've tried deactivating in WM, but that doesn't work as I've written above. I also tried to disable PIN using my friend's LG AT&T and it didn't work either so I guess I have to try some PC software or go to my service provider and ask them to do it. Thanks for replies.
chourmovs said:
what kernel do you use ? i use liquid's 2.6.25 + kernel update
I finally follow your advise and came back to "not so super" and begin to use the "backup data" function...
The best setup so far
Click to expand...
Click to collapse
lol i've read about the 2.6.25 working camera several times yet i chose to follow the blunt idea that "everything current is best ever" setup.
Anyway ill follow your advise now hehe and finally will have a working camera back again. anyway we have a backup hehe. Thanks man!!!
by the way, i liked your post title a lot haha.
arzakem said:
anyway we have a backup hehe.
Click to expand...
Click to collapse
yeah that's why i try other roms today (i'm in a rom rush ) to see if situation is better with backup trick
i saw the great nr2jt say in a topic that he save is data every morning to prevent its loss
that's why i give another try with scoot 5.5 with liquid's 2.6.32
Hey liquid do something for us to use 6 release
post 1 updated
After numerous builds+kernels, loads of frustration (and the inevitable revert to wm for a while) I think I like this setup. Simplicity at its best, Scoot CyanogenMod (RLS5.5) and latest 2.6.32 from atools as per 1st post. Just re-purposed the camera button as 'home'. Even my headset works, albeit intermittently.
Which settings for ATools for pola200?
Hi,
i tried to install this rom on my german pola200. But on the Linux Bootscreen the text is scrolling down and sayes that it installs the rom. But than it scrolls down error messages.
I tried this for houres but it shows no final error or something. The Text is scrolling on and on.
So i think that i used the wrong settings in atool. I used this tutorial to set up atool: http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsNand
What settings should been used?:
- What version to select?: Donut, Eclair or Froyo?
- Best settings for sd-card-partition? I used first partition 3 gb fat32, second partition 1 gb ext2.
- where should i install system and data? Both on second sd-partition? Or should there be a third partition? (the first time i tried to install the system on intern memory but install runs out of space)
Can you please explain the right settings in atool?
best version is froyo.
to choose sd-card partition, you must have your sdcard PREPARED beforehand. Atool does not partition your sdcard for you. As of what to use to partition your sdcard you can search it at google. (im sorry im a little bit short on time now). choose NAND on both system and DATA.
atools has sd partioner inside so you can repart sd card (boot script editor Y), but the sdcard must have only one partition on it (fat32).
i stand corrected thanks l1qu1d.
Hello.
I´m new owner of Xoom "refurbished by motorola" bought on Don´tRetail.
With serie rom, updated by OTA to 3.2, all run perfectly. Enough smooth and run, but Quadrant give me a poor results (1700 points).
After unlock, flash recovery clothwork (3.2.0.0 rc4), I flash tiamat roms (2.0, updated 2.01, and later 2.1 hammerhead).
In all this scenaries, when just flash the new rom, work correctly, but when I installa any application...oh oh...
...when I press power button to suspend it, after eight second Xoom automatic reboot.
I back to stock status (reflash serie rom, serie recovery...all serie) and xoom work correctly.
when I reflash to use another time Tiamat´s rom...here is the problem...when I installed any application, if I suspend Xoom reboot automatically after eight second.
If I plug xoom to pc, and in "cmd terminal" I made:
adb logcat
I can suspend xoom without it reboot.
I tried to elevate minimal frecuencyes in setcpu, but same results.
I tried to do a logcat > logcat.txt in terminal emulator, and suspend the xoom...same result...reboot after eight second.
Any sygestions for I can use Tiamat roms???? With stock rom I have 1700 point in quadrant...with Tiamat without overclock (my xoom don´t let me overclock ) I have 2800 points.
A lot of thanks....Im so frustrated
Ok, I am just asking this to make sure I am 100% clear with this story.
Everytime you do an image with no apps and you shut down, the Xoom doesn't restart, but when you download applications it does... If this is so, I would suggest that you list the applications that you put on your tablet when it does restart, because to me, it sounds like it is an application that is bugging out on the Xoom.
Android systems are set up to force a restart if there are too many system resources being chewed up by applications that are a "High Priority" status and this causes a system resource lock up, and unfortunately, the only way to fix that is to force restart the system. IF it is a app that is doing it, all you need to do is make sure that app is not running to allow it to do so. Good ways of finding out is to use Titanium Backup (Marketplace) to freeze the apps (but that is only for a paid version...) or as someone else just previously suggested in another forum post is Autorun Manager where it allows you to freeze applications from starting up.
I would also suggest that you use the LogCat function in the SDK Tools that is stored in DDMS (aka ddms.bat located in the SDK TOOLS Section). This little program will allow you to do LogCat on your computer as well as save the log as a txt to upload to us (or for easy copy and paste) and as well as allows you to take screen shots and so forth. This might help you out finding the problem too as well as help us
So could you please give us these details to help you out even more?
Is this a Wi-fi only or 3g model that you bought?
Current Rom and Kernel (if I am wrong on the next two posts)
~Guess on Rom is: 2.1 hammerhead
~Guess on Kernal is: (I did not see where you said what the current Kernel was...)
Current Application List that Forces the Xoom to kill itself and reboot, even if it is just one... it might allow us to help you obtain a compatibility issue (if others are having the trouble with the same applications)
You had this trouble after you flashed the new ROMs, are the correct version? (aka Wi-fi only vs 3g romsm, cause there are 3g roms for Tiamat)
Did you clear the cache before and/or after you put the new ROMs on?
I hope we can get this resolved as soon as possible for you!
(links)
to get DDMS if you do not have it yet, please go here -- http://developer.android.com/sdk/index.html -- and you will be able to get step by step walk through to get the SDK. You will need to launch in Terminal/Command Prompt (depending on the Computer Operating System that you use.)
Firts...a lot of thanks for your answer.
With original-stock rom all work all right. My machines arrived with 3.1 Honeycomb, and via OTA updated to 3.2 (HTJ85B).
With this roms, all work correctly. I installed a lot aplications and work allright. I root this rom, and all are working well.
If I try to install any rom from Tiamat, doing previous wipe, the rom runs perfect. I install Titanium to reinstall all my aplications, and all work well. I can work about hours without problems...but with this roms (with all tiamat´s kernel and launpad kernel...) in the moment I suspend, after 8 or 9 second the tablet reboot automatically.
I tried to do a clean install, and only install one aplication, like flash player...and all are ok. After it, install another one, and after it another...but at tirth or fourth there is the problem another time...and tried with diferent aplications. Sometimes the problem go after install flasplayer, sometimes after install RepliGo, sometimes after install dolphinHd...
The more stranger thing is that if a plug the tablet to pc, and make a "adb logcat"...if I suspend de tablet...no problem, no reboot.
It´s possible that mi gpu aren´t righ? I say this because I guess that when the system go suspend, the gpu frecuencies go down (or gpu voltajes) and this made machine reboot... and it´s possible with tiamat´s kernel voltajes and/or frecuencies GPU are diferent than in stock rom.
It´s possible flash a tiamat rom without customiced kernel??? If I could try a tiamat with stock kernel, or with gpu without variation in voltajes or frecuencies.
NOTE: sorry for my english
So could you please give us these details to help you out even more?
Is this a Wi-fi only or 3g model that you bought?
Current Rom and Kernel (if I am wrong on the next two posts)
~Guess on Rom is: 2.1 hammerhead
~Guess on Kernal is: (I did not see where you said what the current Kernel was...)
Current Application List that Forces the Xoom to kill itself and reboot, even if it is just one... it might allow us to help you obtain a compatibility issue (if others are having the trouble with the same applications)
You had this trouble after you flashed the new ROMs, are the correct version? (aka Wi-fi only vs 3g romsm, cause there are 3g roms for Tiamat)
Did you clear the cache before and/or after you put the new ROMs on?
Click to expand...
Click to collapse
Some of my normal aplications:
Beautiful widgets
RepliGo
Documento2go
EzPdf
Titan¡um Backup
SeriesAndroid
Dolphin
Quick Boot
EsTaskManager
Astro, EsFilexplorer, rootexplorer, file manager
Aptoide
Pulse
I tried a lot combinations: for example with or without wifi, changing wifi suspend policy, with or withou configure gmail counts...with or without lock screen...
My Xoom are only WIFI 32gb (MZ604).
anfederin said:
Some of my normal aplications:
Beautiful widgets
RepliGo
Documento2go
EzPdf
Titan¡um Backup
SeriesAndroid
Dolphin
Quick Boot
EsTaskManager
Astro, EsFilexplorer, rootexplorer, file manager
Aptoide
Pulse
I tried a lot combinations: for example with or without wifi, changing wifi suspend policy, with or withou configure gmail counts...with or without lock screen...
My Xoom are only WIFI 32gb (MZ604).
Click to expand...
Click to collapse
I would actually ask if you have your wifi set to go off when the screen is off. This is a known issue...unless the wifi sleep policy is set to Never, the Xoom may reboot when the screen is off. It could be as simple as that.
Oh oh...so many probes that I don´t Know if I change wifi policy or not
But I remember dont change this between flash and install all apks.
At this weekend I´ll probe it and say you, now I need stable tablet to work.
A lot of thanks.
anfederin said:
Oh oh...so many probes that I don´t Know if I change wifi policy or not
But I remember dont change this between flash and install all apks.
At this weekend I´ll probe it and say you, now I need stable tablet to work.
A lot of thanks.
Click to expand...
Click to collapse
You can set it under wifi in Settings--->Networks...
Good luck!
Hola peoples!!! Ok so I just thought I'd create my own thread on this matter. Mustangtim started one in apps and themes (and here is the link to that thread) but since I'm taking over this project it was brought to our attention that this should be in the dev section as its no longer just an app.. I am actually tearing .imgs apart trying to figure out what the deuce.
FIRST OFF THIS IS A WORK IN PROGRESS, WE ARE NOT YET FULLY SUPPORTED. HOWERVER I'M DOING MY BEST TO CHANGE THAT.
Secondly if you want to help get this started please visit the market and grab the app here. Its a $3 dollar app for unlimited amount of roms, based on your SD card storage capacity anyway. And speaking of which you need AT LEAST a class 4 or better SD card to make this run smoothly.
Also feel free to visit the forums at http://forum.init2winitapps.com/
Ok so here it is, Boot Manager Pro. Its been a long time coming for the g2x to dual boot. First off let me say long story short, I currently have a bootable SD Rom, known as ROM1. I have yet to be able to recreate my findings tho. But it works and it doesnt brick at all. However it is a bit laggy on my class 4 SD card. Luckily I've already done my research on this project as there are many threads of such awesome info so I'm just going to be lazy about it and quote the good people of xda versus re-writing it based off of their info.
ChrisDDD said:
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of its own, and then sub-folders to hold the different roms you install. When you install a rom, it basically creates images of the usual Android partitions - system, data, cache, & boot. These are standard .img files, just like the ones Clockwork creates when you do a backup. After the images are created and wiped (formatted, which you should do initially) it installs your rom into these essentially the same way as Clockwork installs a rom to your phone's actual partitions. I assume it modifies the kernel that comes with each rom to mount the image files on the SD card instead of the phone's partitions.
When you want to boot a rom, it just replaces your current boot image with the modified one and restarts the phone. With the modified boot image, the system, data and cache images on the SD card are mounted to the correct locations and Android starts up none the wiser. The rom will initially run a little slow, because the SD card is slower than the internal memory, but after things get cached it speed up considerably.
When you want to reboot to another rom, or back to the phone's rom, Boot Manager again swaps boot images that mount the desired rom's partitions (in the case of the phone's rom) or files (in the case of an SD card installed rom).
When you first run Boot Manager, it makes a Clockwork flash able backup of your current boot image, which you can flash if a rom hangs or loops on startup. Alternatively, you can also simply boot into recovery and do an advanced restore, choosing just the boot image to restore from a backup. It accomplishes the exact same thing.
It can be a little hit or miss, with some roms just plain refusing to start through Boot Manager, but it does work and when it does, it's pretty amazing given what it's actually doing.
Click to expand...
Click to collapse
So basically upon installing the app you need to setup your phone so that way you can properly install a ROM, follow these steps:
1. Go into the supersu(or superuser app) and then go to settings then disable logging or click none.
2. Then go into the BMP app and press the menu button on your phone, not the app, and go to settings. Once in settings put a check mark in force large boot.img, screen on during install, and then go into variables, leave tegra alone but change the sdcard block to show mmcblk1p1. Then press finish and let the app restart. By the way I didnt change any of the sizes of the .imgs but feel free to do so. But be warned do not decrease the size of the system.img only increase it, if desired.
3.Then after you've done the above you need to setup the phone rom. Click on 'Setup Phone' under phone rom and follow that process to setup your phone rom.
4. Once your phone rom is setup you may begin to install a zip to rom1 or rom2 or whatever slot you want. This is the tricky part. I have done tons of reading and most people say that if your using CWM, which us g2x'ers do, then you will probably have a better chance of getting a bootable rom by restoring from a nandroid backup you did versus installing new.
5. So after you decide which path you will take, nandroid backup or fresh rom install, choose install. If you choose a fresh rom, wipe system, data, and cache right away. If nandroid, then wipe after the install.
6. Now once you have clicked install put your phone down, DONT MESS WITH YOUR PHONE AT ALL! PUT IT DOWN AND WALK AWAY OR SOMETHING! Don’t mess with it, text from it, xda from it, dont even use the screen as a mirror!!!! lol seriously the app is picky and while under the .img creation process you want nothing to mess that up or you will not get it booted. You may however drag down the notifications bar to follow the progress of the install.
7. Once its complete, tap the install complete notification in the notification bar and let the app do its thing to finalize the install and get you back to your rom selection screen. Now if you did a nandroid back up here is where you click 'manage slot' and then factory reset the backup you did. Just do it, dont ask why.
7.1 Also so if you desire to install gapps and/or possibly a different kernel, now would be the time to do so while your here. I have read mixed reviews of doing this process right after the rom installs. However when I set up my rom1, I booted into it first all happily then realized I had no gapps. So I had to reinstall BMP on rom1 then boot back to phone rom and then I installed GB gapps and had no issues booting back into rom1.
8. Once the above steps are done if your feelin lucky go ahead and tap on boot the rom you installed, and if all goes well it will boot up.
9. If it boots up you need to post confirmation here!!! Provided info such as phone rom and the info on the sd rom you used and slot number and such.
Hopefully it will just work for you. I have done all the above steps using HFP 2.1 as my phone rom and only been able to get 1 bootable rom. Being it was for testing I used HFP as my phone rom and as well as my rom1.
So if the above steps dont wortk out for you and your boot lopped or what ever, then turn your phone off and reboot into cwm. You have 2 options to resolve the boot issue you just created. 1, you may go to restore then advanced restore then restore your boot. Or 2. select install a zip and nav to the bootmanager folder then phone rom then flash the update zip there.. then reboot and you should be back at your phone rom.
Here is a basic run down of everything that I have done so far:
When I first started working on this project I wasn’t doing any dev'ing to change any of the stuff in the boot.img. I just changed settings in the app per all the research I did. So when all was said and done I restored HFP 2.1 to ROM1 and it actually booted!! And it works lovely btw.. I can still boot into this rom today. I then decided to pass the word and ways that I created the working rom1, well I nor anyone else I passed the info to was able to get it working. Only one other person was able to confirm that rom1 works but only after I copied all my rom1 info and sent it to him for testing.. and he was able to boot into my created rom1… As I see it, it was a blue moon event that I have yet to repeat. So I thought eff it lets do some dev'in so I unpacked the boot.img from rom1 then compared that to the unpacked boot.img from rom2 that I created in my trial and error experiences. So in doing so I noticed 4 differences; 1, the mount points obviously, 2, in the sbin folder had a ueventd file from the working rom1 was a text file viewable by gedit in ubuntu. In rom2 it was just a non-readable file. 3, in the init.rc file was also missing a chmod command for system, (the command is in rom1 but not rom2) and 4, there was a ueventd.tegra file that was in rom1 that wasn’t in rom2, but everything else is the same. So I decided to plug and play with the differences to see if she boots and no go. I don’t understand why its boot looping because I am using the same rom as phone rom as for rom1 and rom2. So it boot looped. So I had to restore my boot.img many times in cwm.
So then I said eff it lets do some more research, then I noticed in the .zips folder plus the individual rom folder there are .zips that will let you flash via cwm if you get boot loops and 'should' get you booting to your desired sdrom. I then tried that way and no go.. so then I opened up the zip and had a look at the internals.. first there is the moveboot.sh file that the app runs in cwm flash the given boot.img. I then checked out the meta-inf and opened up the updater-script thinking that the app wasn’t actually flashing the boot.img which is why it loops... Well I think im half way right. However the script itself is lil dodgy... first thing I noticed was at the end of the script they have a command to cp the log from /tmp to /sdcard/bootmanager well the command was wrong so it never copied the log. So I fixed that. I also saw that the assert command was pointing to ‘boot’ instead of mmcblk0p5, so I changed that too. Then I decided to do away with the assert command and the moveboot.sh file they have going on to utilize the same functions that the kernel zips use, which is a kernel folder that holds the boot.img and a run_program that dd's the boot.img to 0p5. plus I even updated the update-binary that the file uses. I used the one from the g2x nullifier as I know that one was made for our phone and should have no issues.. plus there was a noticeable difference in the sizes of the provided binary to that replaced binary. So with the updated.zip file I then rebooted into cwm to flash that being that I was using a different command to flash the boot.img as well as the other changed stuff and still it boot looped. So as of now the only thing I don’t think ive done was grab the boot.img from rom1 then change the mount points, only change that, and then use that for rom2 and see if it boots. I don’t think I’ve done that yet. But every dam process I do I get boot loops. So basically I have came to the conclusion that it’s now NOT a boot.img issue being that I have done everything to change the boot.img and to make sure it flashes, which it does indeed and now creates the log too… I think maybe it has issues with the system.img as that’s what comes next in the boot process. But that’s just my hypothesis. I won’t be able to confirm this till I liberate rom1’s boot.img then change the mount points to point to rom2 and then see if it boots.. if it don’t work then that would mean to me that there is an issue with system.img created. But that’s just my hypothesis…
What I don’t understand is why the eff when I didnt hack the app I got a working sd-rom, but when I do change some stuff with it still don’t work!!???!! I guess maybe ill just edit/hack the apk to see what’s up.. This is getting way more complicated than it needs to be, since it worked prior to all my major changes to the script its using for flashing and the boot.img and what not. Anyone have any ideas feel free to add them.
My next steps are to edit rom1 boot.img one last time to change the mount points to point to rom2 and then if that’s a no go then it’s got to be the system.img that’s getting created. By the way this whole process I have only been restoring my nandroid backup for HFP 2.1. I have not attempted to flash new as with thru my research more times than not people would get a bootable rom via restoring versus flashing new.. so if anyone wishes to experience an sd rom let me know, ill send you a link to download my rom1 to get it going. Mind you that its not perfect and you need a class 4 or better sdcard. Everything works but it just takes a bit longer to load things and get things cached as its on the sdcard and not nand. Also if you have any input or are wishing to help pm me I need more heads to get this sorted as I can’t be the only one who knows how to edit scripts and unpack imgs and such. Either way I will continue to do this until I get it right damit!!! Oh and I just ordered a class 10 sdcard to help with this process…
That was copied from the other thread that mustangtim started. Last night when I went home the first thing I did was change the mount points on rom1 to reflect rom2, I changed nada else, then I tried to boot it... it boot looped. So maybe its a permissions issue or the system.img.
So just as a proof of concept and before anyone calls bs on my work/findings Here is the link to my rom1 that boots and is HFP2.1. *Update, 'm just going to
leave it on my DB for now till I find something better I guess. xda wont let me attach the file since its 233MB. Oh well here is the link :
Code:
[URL="http://db.tt/eBZwrOrs"][U][B]Here it is, my Rom1 HFP 2.1[/B][/U][/URL].
I have also attached my updated script file to flash back to rom1, for now.
The boot.img points to rom1 instead of phone rom, ill add to phone rom
as well, just not the now. :) Feel free to flash this via cwm versus
restoring...
Also this is part of the this: the ‘.zips’ folder you need to replace the file in
that folder as well. It’s an update file for rom1 to flash the boot.img.
..
If you’re going to use this you need install a random rom to rom1 then replace those created files in rom1 with these files in the 7z file..
So I am doing this new thread to get the devs or people with know how to help me out with my findings. I have edited the boot.img so much I could pretty much re-write everything in there by now including using magic to create to my own kernel eff!! lol jk but seriously I need people with knowhow to provide confirmation of go or no go. Basically I have people whom have helped out but It seems that I'm the only one who has dug this far into this app(unless i've been misinformed) and I have no one on my level to talk with except the init2winit devs. Which are very helpful btw.
And lastly:
Conap said:
Guys if it's failing to make the boot.img first make sure your using the market version....others have released cracked versions of our app which they broke...if your using the actual market version just send me a pm or email [email protected] and send your log.txt from BootManager folder on sdcard and we'll get it straightened out. Thanks.
Click to expand...
Click to collapse
or post here or PM me, I'm always down to help out.
Also thanks go to the init2win team, Gflam and Conap as they started this app. and as well to Mustangtim as he brought me into the light of BMP.
So you got all that???!!!??? Now lets get this party started and get full support for dual booting. I will not rest until I get this working. Thanks for your time and possible assistance.
Ok so since I have a book above I thought this is a good place for links and such...
So just incase anyone is curious, here is the Official Boot Manager Manual
Here is a nice link for Tips and Tricks while Installing ROM's that so far has good info to help you watch via adb what the BMP is doing in its creation process.
Some FAQs:
When should I set up my phone ROM?
Set up your phone ROM EVERYTIME you install a new ROM to your phone so you can get back to your phone ROM and won't get stuck on your SD ROM.
My SD ROM seems to lag how can I fix this?
SD ROM lagging may be due to a few things which all have easy fixes. First fix is that most of you have class 2 cards which are what usually come with your phones. These have a much lower read/write then cards of a higher class, we recommend a class 6 card or above. Another easy solution is overclocking merely install a better kernel and use CPU Boost (or any other overclock app) to overclock your phone.
Can I nandroid my SD ROM slots?
Yes and no you can't nandroid them in the traditional sense of the word using recovery but this app works as a recovery for your SD ROM slots and you can back up your ROM slots within the app in the Manage Installed ROMs section which works as a nandroid for your slots by fully backing up your slots to your sdcard which can later be restored.
What if I want to change the sizes of my images, how may I determine the individual sizes easily?
Easiest way is to open up terminal emulator in your app drawer. Type 'su', then grant permissions if need be, then type 'df -h' and it will display such information. You may also use adb in the same fashion. Connect via usb, open up command prompt/terminal and get adb connected and then type 'df - h' again and the same info will show. I will say this again just because, do not decrease the size of your system.img ever! Unless you want mad issues!
Here is the changlog link and just for heck of it the info based on that link:
Code:
V3.2.6
Fixed DroidX/Droid2 Install issue
Fixed UI theme issues
Fixed issue with spaces in name of pic when selecting photo for screen shot
V3.2.5
Fix to allow continue of install if no boot.img is found.
V3.2.4
Added support for HTC Rezound
Added support for rom's with multiple boot.img's
Added support for rom's made for multiple phones
AutoDetect sdcard for usb mounting
Fix for installing ICS gapps
Optimized SDRom Install process
Added support for Motorola RAZR
Added install queue
V3.2.3
Fixed issues with rom's not showing when on emmc on Droid Incredible
Fixed issues with not showing correct booted rom in app
More improvements to sms sync(all rom's will need updated app for changes to apply)
Fix issues with loader
Fixed issue with switching to backup server when main server goes down
Fixed 1x1 widget to show unlimited rom slots
Added 2x2 widget that works with unlimited rom slots
V3.2.2
Fixed force close for img's over 1Gb when resizing
Fixed current booted rom displaying correctly on gnex
Fixed issue with wrong busybox downloading on gnex which should fix alot of install/boot issues
V3.2.1
Fix for errors causing installs to fail.
Fix for some of the licensing stuff.
Removed sdbooster prefs from Galaxy Nexus(Since they don't have sdcard).
V3.2
Changed 4 sd slots to infinite slots!
Galaxy Nexus Support
Sms and Call Log synced between ROMs (you choose what ones too also requries updating boot manager in all slots)
License Check extended to a week
ROMs do not need market installed for boot manager to run (requires updating boot manager in all slots)
Hide su toasts (superuser elite only)
Fix for force close when setting screen shot in MIUI rom's
Thunderbolt defaulted to force large boot.img
Fixed unsupported device using a key
Manually setting variables only accepts numbers
V3.1.1
Fix for various force closes in rom installs and Nand restores
V3.1
Added su binary check
User selectable colors for everything
Better navigation (press title for quick action)
Added compatability for new twrp backups
Better compatiblitlity with memory tweak scripts(i.e. supercharger script and liquids default scripts)
Fix for install process being killed by android
Fix for some themes erasing img's
Fix more force closes during install
Force smaller boot.img option in settings(Fix for some phone's who's boot.img won't fit on the phone after BootManager edit's it)
Improved gapps checker
Improved security
Boot Manager now accepts keys pay for by paypal (see http://init2winitapps.com/stories/BootManager.html)
Added Evo 3d GSM Support
Added notifcation sound/vibrate for finished install (turn on in settings)
Improved data check
V3.0.3
Fix some force closes
V3.0.2
Added backup server (Sorry our server dropped out)
Fixed some force closes
2nd init fixes for Liquid's ROMs
V3.0.1
Last minute UI fixes
V3.0
UI Completely redone
Includes screen shot of each slot
Custom Info
Custom Dialogs
Custom Animations
Custom everything!
Bug Fixes
Added Droid 2 Global support
Screen shot with long press of search
V2.2.1
Bug fixes in file browsers
File browsers only show relevent files
Kernel installer fix
Droid 2 bug fix
V2.2
New security (more advanced and requires data only once a day)
Installs no longer require data
Added Italian translation thanks Black-Ice
Droid X support
Droid 2 support
Fixed status bar notifications
Fixed phone rom rebooter if gapps aren't installed
Bug fixes
V2.1
Restore android_secure to sd from nandroids
Added TWRP nandroid support
Added CWM tar nandroid support
Added Spanish translation
Made widgets easier to use
SD Booster added (Change SD read cache for better preformance)
Added current settings to manually set variables.
Added option to keep screen on during install in settings
Fixed usb layout
Updated Security
Bug Fixes
V2.0
Install now runs from the foreground (status bar)
Restore Nandroids to slots also in the foreground
User can cancel installs as they run
4 new themes added including one by apophis9283
Some phones such as tb moved to new install code (Fix for some sense rom's)
V1.3
Added third theme to app (Red Theme)
Added 4x1 widget and new widget styling
Fixed in app messenger
Added support for Htc Evo 3D
Added support for Htc Sensation
Added Support for Htc Incredible 2
Added Support for Htc Incredible S
Added Support for Htc Desire S
Added support for LG Ally
V1.2
Added option to reboot to phone rom to install gapps in license check dialog
Better error checking and error logging
Automatically install's ext2 libs if not present
Moved Set Names to Manage rom's
Fix for add-on's not installing correctly
Better compatiblility for rom's that use data2ext or apps2sd(user must set larger img's in manual variables)
Trash cleaner added to extras
Better Fix for WiFi issues on Droid 1
Added display to show what rom you are booted into
Fix for updater-script not found errors
Added support for Htc NexusOne
Added support for Htc MyTouch4G
More compatiblity for ext4 support
V1.1
Fix WiFi issues on Droid 1
Fix bug in rom installer for setting permissions correctly
Fix bug for cache size not setting correctly in setting variables manually
Fix for decimals entered into partition sizes causing force close
Fix force close in widget
Fix force closes in installer
Added Wipe data/Factory reset to Manage Rom's section
Added code to show what file's are being unzipped in dialog
Added support for rom's that extract files to sdcard so the files actually end up on your sdcard
Added support for Htc Desire (apps2sd and data2sd rom's support is experimental. Please email if you test it and it works/doesn't work)
Added support for Htc Inspire4g
Added support for Htc DesireHD
Added option to use ext4 filesystem if rom's support it-Experimental Won't work with all rom's.
Added log.txt file to sdcard to log errors during install
V1.0
Initial Release
YEZZZ
glad to finally see this here!
jookdakang23 said:
glad to finally see this here!
Click to expand...
Click to collapse
indeed... hopefully it wont be before too long that I get this app fully supported for us!
This app will be extremely useful for G2X owners and makes the G2X more versatile and desirable.
da-pharoah said:
indeed... hopefully it wont be before too long that I get this app fully supported for us!
Click to expand...
Click to collapse
idk how you get it booted. lol i keep getting bootloops
jookdakang23 said:
idk how you get it booted. lol i keep getting bootloops
Click to expand...
Click to collapse
Are you using the files I supplied or the ones that BMP created for you?
Woo hoo good job bud
Sent from my LG-P999 using xda premium
x0xhellx0x said:
Woo hoo good job bud
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
LOL thanks bro.... Go Team Hellfire!!!!
da-pharoah said:
Are you using the files I supplied or the ones that BMP created for you?
Click to expand...
Click to collapse
i remember requesting the files but think you ever sent them
jookdakang23 said:
i remember requesting the files but think you ever sent them
Click to expand...
Click to collapse
no we had a miscommunication due to our avail times and GB's lacking ability to utilize two accounts on gtalk.... I have posted those files in the op however...
First, I want to thank everyone who has helped with us on this app. Second, I know I picked the right man for the job, did you see that OP! All kidding aside, a lot of you know I write for ACS under screen name artifintel. I just had too much on my plate to give this project the attention and direction it needs. The right guy is in charge, he's a stand up person and very knowledgeable with this app. Good luck everyone!
[email protected]
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Rafase282 said:
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Click to expand...
Click to collapse
what rom are using as phone rom? and you installed to rom1?
da-pharoah said:
what rom are using as phone rom? and you installed to rom1?
Click to expand...
Click to collapse
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Rafase282 said:
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Click to expand...
Click to collapse
and no bootloop you say?? well then it may be the stock rom your using... The app is very picky and if you get a bootloop, I feel that those can get booted with tweaks... but stuck on lg screen is just no bueno.. Try a different rom... maybe one that has its partitions at ext3 format just to try it.. I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
hands down, a badass app...
SiL3nTKiLL said:
hands down, a badass app...
Click to expand...
Click to collapse
lol +1 for sure!
da-pharoah said:
I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
Click to expand...
Click to collapse
positive on ext4
I installed the rom and i dont have a 4g icon but an H, and there are no apps just basic ones like no market none of that stuff. Does it all have to be downloaded manually or is it supposed to come loaded with some stuff. Iknow i should post this in the WildchildIcE v0.9 section but it wont let me ask any questions cuz im new to the forum
your also supposed to download gapps....i would link you but im on mobile. Check for the gapps download near the regular download.. Im aware that in some cases the H icon will still show and a fix for that will come soon.
ahhh ok dl'ing it now. is there a special way to install gaps
You'll flash gapps zip file from recovery just like the rom.
Sent from my myTouch_4G_Slide using XDA
You will find that the v0.9 version will have the "ROM Control" working wonderfully but the soft keyboard & proximity senser are still borked. If you find those are "deal breakers" for you (and they are for some people) you can flash the 6/19 "nightly" and swap a fix for those two issues for having "ROM Control" FC'ing until XMC has a chance to iron out the issue.
Just my 2 cents.....
....don't forget the gapps
How do I get wifi to work?
I have flashed your v0.9 and followed the installation instructions and I must say it all went very fast and smoothly. However
I'm unable to turn on wifi. It says in the change log that this works. What happens is that when I click on wifi, then go to the wifi screen and touch "on", it quickly moves to on but immediately goes back to off and the screen is stuck saying "turning wifi on". So how do i get this to work?
If it makes any difference I came from another rom, http://forum.xda-developers.com/showthread.php?t=1758767&highlight=v2.
Also, when sending text messages, I use go sms, and for some reason now i no longer have auto correct/spell check.
It actually doesn't recognize about 90 percent of the words I type. It says they're incorrect even though they aren't.
Any thoughts?
Thanks. Awesome work. I'm totally enjoying your roms.
First of all, I would suggest you use ONLY CWM 5.0.2.7 or 5.5.0.4.
Secondly, always do a FULL wipe when coming from another ROM. It's also a known issue with CWM that if you don't do those wipes 2 or 3 times it's very possible to leave bits and pieces behind that may cause glitches like you have described.
Third.....if you have already followed the 1st & 2nd suggestions you may have gotten a few packets corrupted in your DL and should probably at least do another and reflash.
This could make a huge difference and I forgot to even consider it. If you have one of the newer bootloaders you'll need to flash your boot.img file thru ADB after you have flashed your "rom".zip file. You will also want to isolate a copy of your DL and expand the file so that you can copy your boot.img to where you normally flash files from. From what I have personally seen, it is VERY important that it isn't copied directly from your "rom".zip file and flash that because it will remain wholey or partially compressed and have various parts of you ROM disabled just as you described.