Related
For some reason I can't get my Polaris to run the latest Android version (i.e. Froyo).
1. Downloaded latest kernel (polaimg-panel3-320-froyo-07-07-10.nbh)
2. Downloaded last build (Incubus26Jc's Super FroYo RLS10)
3. Put last build (.tar or .tgz file) on SD card in directory /andboot
4. Flashed by using NBH file together with RUU Update Utility
Now it gets tricky:
a) or the system reboots, vibrates twice, I see a red and blue line and then a black screen and nothing;
b) or the system reboots, I get the Android installation menu after pressing middle button, install, but after soft reset I get a "No such file found" kind of system error
Can someone help me getting Android on my old Polaris? Thanks!
SnoopThaDoctor said:
For some reason I can't get my Polaris to run the latest Android version (i.e. Froyo).
1. Downloaded latest kernel (polaimg-panel3-320-froyo-07-07-10.nbh)
2. Downloaded last build (Incubus26Jc's Super FroYo RLS10)
3. Put last build (.tar or .tgz file) on SD card in directory /andboot
4. Flashed by using NBH file together with RUU Update Utility
Now it gets tricky:
a) or the system reboots, vibrates twice, I see a red and blue line and then a black screen and nothing;
b) or the system reboots, I get the Android installation menu after pressing middle button, install, but after soft reset I get a "No such file found" kind of system error
Can someone help me getting Android on my old Polaris? Thanks!
Click to expand...
Click to collapse
Same for me with polaimg-panel3-320, but it works great with polaimg-panel1-320-24-05-10.nbh
Thanks! Got it working with the older NBH file. Not completely flawless, but it works!
Don't use the old polaris panel 1 nbh, instead download the latest and then use this utility to change it to panel 1.
http://forum.xda-developers.com/showthread.php?t=689812
Thanks!!! Got it working with the latest NBH files! Great!!!
Hey, Could anybody unswer me on two questions.
1. why we have to change from panel3 to panel1 in this nbh file?
2. what is that mean panel3 or 1? why DZO do this type of the nbh (with panel3 i mean)?
thanks a lot, ithin it will helps not only me but everyone in future who didn't know about this modification
skydemon said:
Hey, Could anybody unswer me on two questions.
1. why we have to change from panel3 to panel1 in this nbh file?
2. what is that mean panel3 or 1? why DZO do this type of the nbh (with panel3 i mean)?
thanks a lot, ithin it will helps not only me but everyone in future who didn't know about this modification
Click to expand...
Click to collapse
The panel type depends on revision of your polaris, more specifically the make of the lcd panel, see here. I just tried every panel until I found one that works, I use panel 1.
Thanks a lot, but could you please answer me again. How i will know what kind of LCD panel in my Polaris and which number i should use?
these parameters is placed in my start-up file for the haret launcher
#alloctest 0x2000
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz
set cmdline "board-htcpolaris.panel_type=1 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend clock-7x00.mddi=0xa51 hw3d.version=1"
boot
can i use panel type from here?
i have opened this polaimg-panel3-320-froyo-07-07-10.nbh file in NBH editor and saw that the HW3D is set in Eclair. Should i change this to Froyo or left as is?
Thanks a lot for the conception)))
pannel type 1...
Did I brick my Polaris?
Well, it makes me laugh looking at the last post dated back July 2010 but I decide to post anyway because I feel somebody might have passed through my problems and might help.
Following indications on this forum:
1. I downloaded:
- Kernel: polaimg-panel3-240x320-2.6.32-froyo-09-09-10_21.nbh
- Last build: Incubus26Jc's Super FroYo RLS16 All Languages
2. Put last build (androidinstall.tgz) on SD card in directory /andboot
3. Used RUU Update Utility to flash the nbh file
Everything when smoothly. When it reboots, it vibrates, "Smart Mobility" message shows up, vibrates twice and then a blank screen is displayed.
Going through this forum I think I might have used the wrong type of panel and should have used Panel 1 instead of 3. So I downloaded Windows NBH Editor and managed to change the nbh into Panel 1. Then I shall try again.
This time my Windows 7 is unable to recognize my Polaris and all it can see is a new Disk Drive with no ADB device displayed. So I installed PdaNet302.exe to implement the USB driver for HTC Android Phone but it still cannot see my device and the process aborted.
What worries me is that one step of the process requested to change a setting on the Polaris (On your phone, click Settings > Applications > Development and make sure USB Debugging is on.). Obviously I can't do that as the screen is completely white!
I believe if I can manage to have my PC talking with my device then the problem will be fixed with the panel1-based flash. But every attempt to install the USB driver for Android Phone regularly fails on my PC.
All that time the Polaris remains with the lighted blank screen and there is no way to turn it off as the on/off switch refuses to work.
Shall I buy a new phone? Thanks for your help.
Did you try flashing the phone with a regular oficial HTC rom? just try it. Put the phone in the boot mode (press camera button and another one, dont recall which one) It will change to the tri color screen. Then connect it and try it.
Also there is a modified nbh rom which includes nothing, just the tool to recover your rom. Do a search to the forum.
I recently tried to install on my Polaris and it went really wrong. And finally could recover. The file is called ROMUpdateUtility_task29. I will erase everything on the phone but later you will be able to recover it
Form that point no more experiments. Polaris was made to work with Windows Mobile. It's really unstable, video camera is useless. And so on.
PC Carvalhon rom and I can use my phone as I want.
regards.
---------- Post added at 08:16 PM ---------- Previous post was at 07:57 PM ----------
With this you can recover your phone: http://forum.xda-developers.com/showpost.php?p=6227425&postcount=7160
A second life for my Polaris
Kafkacell,
1. Following your suggestions, I successfully started the bootloader (camera touch while reset), the 3-colour screen appeared, Windows 7 recognised the device. I then flashed the offcicial RUU_Polaris_HKCSL_WWE_3.19.831.3_radio_sign_25.85.30.07_1.59.42.15_Ship and everything successfully completed. With enormous pleasure I see again my Polaris back to activity. Thanks for giving my Polaris a second life.
2. Back to Feb 2009, I flashed a pcarvalho eXtreme ROM. I don't recall any longer the version of this ROM but it was very stable and never ever crashed. Recently I downloaded and flashed most recent ROMs. From that moment on, I have no peace. It crashed 2, 3 times a week. Now I wish I could go back to the old version but couldn't find it. Perhaps pcarvalho removed them to save space? May I ask you which pcarvalho eXtreme ROM version do you currently run. Thanks.
Im currently running 29022 version (latest update from PCCarvalho).
Notes:
UPDATE:
29022 is up
this is a fix release...sound issues should be gone...had to remove htc volume control is it still has issues...fixes minor gfx glitches...updated to lastest and probably final leak version of wm6.5.3 (29022)...will from now on work on unresolved issues and finalize rom...this will still take some time due to work...
updated physics engine and utask app by ultrashot...my thanks to him...
patched htc album to novsync, faster scrolling once cache is made...
removed no longer supported apps (my phone and marketplace)...if u need them install via cab...
Here is the link for the rom: http://forum.xda-developers.com/showpost.php?p=15707730&postcount=8079
it was posted on July of this year, and so far it runs great. The trick is to not install a lot of apps in your main memory. Do it on your SD card. Also a hard reset is a must to avoid all kind of problems.
regards and glad you have your phone back to life
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
The reason for this User Thread is so that we can keep the development thread clean. Post in the development thread only if you have something useful to contribute such as a logcat, or any dev-related comments. Post any suggestions, bug reports, questions or comments about the rom in this thread,
What's working and what's not?
Working:
Camera - Yes, this means Camcorder also works! 1080P Video shooting and playback work great.
Bluetooth
WiFi
Audio
SD Card Storage
Battery Meter
And of course Hardware Acceleration!
Not Working:
RIL (Mobile Network) - This means no calls, no SMS, no Data, no anything related to the functions of your SIM Card! T-Mobile WiFi Calling also doesn't work.
Information On Dual Booting Roms
Since we currently have an issue with the network radio on our CM10 roms, most people will not be able to use this rom as a daily driver, and would prefer to stay on a fully functioning GB rom. This dual booting method lets us have the best of both worlds! You can have a buttery smooth and fast CM10 rom for enjoying all of Android Jellybean 4.2.1 goodies and a fully function Gingerbread rom when ever you need to make a call and such. For now, this is the best we can do. It's simple and very fast to switch between roms. What else could you ask for? ;D
Installation Instructions Including Dual Booting
DISCLAIMER
I (WE) AM NOT RESPONSIBLE of any damages to your device related to the use of this ROM or the dualboot toolkit. You do this at your own risk. Even though this has been tested and works well, using NVFLASH may brick your device if done incorrectly.
This ROM comes in two flavours: The dualboot toolkit or the Original flashable ROM
Dualboot ROM Instructions
WARNING! NVFLASH will format EVERYTHING, including internalSD. Make sure you backup your important files on your externalSD card
PART 1 - Resizing system partition
1) Unzip the dualboot toolkit and unzip NVFLASH_Resizer-G2X.zip.
2) Power off your phone and remove the battery. Keep vol. up and vol. down held and plug the phone via USB to a WINDOWS computer.
3) Windows should add an "APX driver". Go to control panel -> Device manager and right click on it -> Update driver -> search in system. Then, browse to the drivers folder inside the NVFLASH package and choose nvidiausb.inf. Approve any error messages (Windows 8 users read my FAQ). Install the Nvidia Fastboot driver.
4) Unplug your phone and hold down vol.up and vol.down. Replug it again and double click on flash.bat inside the NVFLASH folder. KEEP BOTH BUTTONS HELD DOWN DURING THE WHOLE PROCESS!.
5) When NVFLASH is done, unplug the phone and put back the battery. Reboot into recovery with power + vol. down. Plug it back and go to mounts and storage -> mount USB storage. If your PC asks to format the internal SD card, select yes.
PART 2 - Installing ROMS
1) Download the desired "call/SMS" ROM and extract boot.img from it's flashable zip. Rename it to boot1.img. Extract Step3_bootimg.zip from the dualboot toolkit and copy-paste boot1.img into system/boot, replacing the file that is already there. Repack Step3_bootimg.zip.
2) Copy-paste your desired ROM into the 0dualboot folder and send it to your device SDcard with everything it contains (your device should already be in the "mount USB storage" menu).
3) From the recovery, flash Step1_enabler.zip. When the screen goes black, hold power + vol. down to get back into recovery.
4) Flash your desired ROM, then Step2_ROM1.zip. Reboot to the OS.
5) You should have a Systemchanger app. Open it, click on "Switching" and give root permissions. When the screen goes black (again...), hold power + vol. down to get into recovery.
6) Flash ROM2.zip and Step3_Bootimg.zip and reboot in the OS
And there you go! To switch from one OS to another, just open the systemchanger app and click on "switching"!
Credits to bihariel for the original method. See the original thread here.
Original flashable zip ROM instructions
1) Boot into recovery with power + vol. down
2) Wipe data/cache, then mounts and storage -> format system
3) Flash this ROM
4) Advanced -> Wipe dalvik cache and fix permissions
5) Reboot and enjoy!
Special trick : In settings, go to About phone and click 6 times on Build number. This will pop up the developer and performances options. In performances options, CPU settings, change the governor from INTERACTIVE to SMARTASSV2.
Downloads
ROM with DUALBOOT Toolkit ***BETA***
DOWNLOAD HERE!
Original flashable ZIP (For single boot)
DOWNLOAD HERE!
Credits
See Mazout360s original thread here for the full list!
Thanks to bihariel for the original method for the Optimus 2X which I adapted for the P999. Great job!
Special thanks to Core Memory for helping me start this project[/CENTER][/QUOTE]
*All Information On this User Thread is from Mazout360s Thread in the Dev forums. Credits go to him for the Instructions/Downloads/Etc.
Quick template for now.. I'll update it as soon as I can.
Mazout Kernel on Stock 2.3.4
I flashed Mazout360's GB kernel over kwes' rooted 2.3.4/March 2012 basebannd. Was running pretty smooth, but had some problems
> Bluetooth icon at top of screen did not turn off "connected" status when I turned off my headset (BlueAnt q2.1)
> Had a few freezes. Installed SetCPU to keep max speed at 1015MHz but still some stops. Some out of nowhere, some in the middlle of doing stuff
> Finally started shutting down often. Tried to get a terminal emulator from the Market, but Market started crashing, even after several reboots. Could not get a kmsg to send.
Reinstalled my nandroid. No time at the moment to play more, need my phone reliable for some days to come. Hope lots of people try this kernel out and that I get more time with it. Nice to have new Dev activity for the G2x.
Quick question, i was wondering if it matters what zip tool we are using? Can i use 7zip for this, or should i use winzip?
Sent from my Mazout driven Reborn Hellbird.
grantusmantus said:
Quick question, i was wondering if it matters what zip tool we are using? Can i use 7zip for this, or should i use winzip?
Sent from my Mazout driven Reborn Hellbird.
Click to expand...
Click to collapse
Shouldn't matter, but I always use Winrar.
Micro SD card not detected
I was following along the steps and everything was going well until step 5 in part 1. when i rebooted my phone into recovery and pulged it into the PC nothing happened even though i followed exactly what the steps say, then i continued on and everything was going well until the end, where i found out that i couldn't get the data that I backed up to my Micro SD card because the phone doesn't see it.
Please help, I'm a noob around here.
I appreciate all the great work
did this project die?
reeshmd23 said:
did this project die?
Click to expand...
Click to collapse
No it didn't. My build computer broke and I need to setup a new HDD with my build environment. I'll make a new version as soon as possible.
hello,
I have dualboot now with hellfire2.4.2 and cm10 mazout's. So one is cm 7 and the other one is cm 10, I want to flash kernel but how? If I flash cm7 kernel will it block the cm10 rom or vice-versa?
guys I have just realized that I do not have dualboot after that steps
5) You should have a Systemchanger app. Open it, click on "Switching" and give root permissions. When the screen goes black (again...), hold power + vol. down to get into recovery.
6) Flash ROM2.zip and Step3_Bootimg.zip and reboot in the OS
I had systemchanger app and clicked on switching after that I flashed mazout's rom then when I open app drawer in cm10 rom, I noticed that I do not have systemchanger app anymore nor camera app.?? what should I do? If I do all steps all over again sould it be working ?
0b095 said:
hello,
I have dualboot now with hellfire2.4.2 and cm10 mazout's. So one is cm 7 and the other one is cm 10, I want to flash kernel but how? If I flash cm7 kernel will it block the cm10 rom or vice-versa?
guys I have just realized that I do not have dualboot after that steps
5) You should have a Systemchanger app. Open it, click on "Switching" and give root permissions. When the screen goes black (again...), hold power + vol. down to get into recovery.
6) Flash ROM2.zip and Step3_Bootimg.zip and reboot in the OS
I had systemchanger app and clicked on switching after that I flashed mazout's rom then when I open app drawer in cm10 rom, I noticed that I do not have systemchanger app anymore nor camera app.?? what should I do? If I do all steps all over again sould it be working ?
Click to expand...
Click to collapse
If you flash another ROM, you have to flash the corresponding stepX....zip file right after before rebooting, else you won't have the dualboot app.
Since android 4.2.2 just got out, I'll wait until it gets stable and make my upcoming build out of it For now, my phone battery doesn't work very well so I can't really test anything until I get a new one.
Hey. I got everything to work and am dualbooting nicely. My problem is kernel. I flashed a recent CM7 with this and everything went fine. Then I went to install the most recent CM7 kernel from Maz (the OC) and that works until I switch to Rom2 and back. Then the wifi gets an error and wont do anything. The kernel wont stick. Did I miss something?
Also, last night went to bed with my phone charging and when I woke up my phone was burning hot. Had Max OC at 1100.
Thanks! Works great having a taste of 4.2.1 and a phone!
Sent from my LG-P999 using xda app-developers app
Mazout360 said:
If you flash another ROM, you have to flash the corresponding stepX....zip file right after before rebooting, else you won't have the dualboot app.
Since android 4.2.2 just got out, I'll wait until it gets stable and make my upcoming build out of it For now, my phone battery doesn't work very well so I can't really test anything until I get a new one.
Click to expand...
Click to collapse
thank you, I see the problem now, and two question more; do I have to redo PART 1 - Resizing system partition everytime when I install different rom combinations or reinstall same roms and does that Resizing system partition harmful/useless or slows down the phone IF I only use 1 ROM?
I'm considering the dual boot, but want to know if it's possible to go back to single boot if/[hopefully] when radio is fixed. I suppose it'll be a matter of using original nvflash and format to have only one partition?
*edit1* Ok, now I'm getting my toes wet with this. fastboot.bin...what am I doing with this? The instructions say "install NVidia fast boot." Ok, but how? Or, has it already been installed with APX? I'm confused.
*edit2* ok I have dual boot! Wow this is interesting. Been running it through different combinations of reboots through system changer, and it seems when I update gb to the latest mazkrnl it won't stick after switching to jb and back again.
Do I need to use the boot.img from the kernel and repack it into step3?
Sent from my LG-P999
Oh shoots. Somewhere along the line I managed to break the wifi
MAC address comes up as unavailable in jb, just says error whenever I try to turn it on in gb. I'm thinking start the process over?
Sent from my LG-P999
adamiscool said:
Oh shoots. Somewhere along the line I managed to break the wifi
MAC address comes up as unavailable in jb, just says error whenever I try to turn it on in gb. I'm thinking start the process over?
Sent from my LG-P999
Click to expand...
Click to collapse
You need to flash a kernel. I am having the same problem, but flashing a kernel after switching back to GB fixes everything.
Edit: fyi I use maz's latest kernel 0205OC
Sent from my LG-P999 using xda app-developers app
Freakthis08 said:
You need to flash a kernel. I am having the same problem, but flashing a kernel after switching back to GB fixes everything
Click to expand...
Click to collapse
So, you mean that after using system switcher app, do power+vol up and flash kernel? Because any time I've tried that it only works on the first instance when i boot into gb. Once i go to jb and back again, the kernel goes back to stock. I'll try again though. Maybe fix permissions too!
Sent from my LG-P999 using xda app-developers app
adamiscool said:
So, you mean that after using system switcher app, do power+vol up and flash kernel? Because any time I've tried that it only works on the first instance when i boot into gb. Once i go to jb and back again, the kernel goes back to stock. I'll try again though. Maybe fix permissions too!
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
When you system switch back to GB, reboot back into recovery and flash a kernel. I wouldn't say it goes back to stock because if it did there wouldn't be a wifi error like that. But for some reason JB works fine nothing wrong I have seen yet, though I just noticed I don't have a camera/gallery.
After switching back and forth so much I just flash the kernel and don't do anything else because nothing has seemingly changed if I wipe anything or fix anything.
If Maz has answer for this I would be much appreciated or anyone else for that matter.
Sent from my LG-P999 using xda app-developers app
Edit: figured it out. A new boot1.img does need to get made with the new kernel already installed.
I created a new boot.img per the instructions on the original dual boot for p990 thread with maz kernel. Then I repacked step3_bootimg. Reflashed rom2 and the step3, then voila! So, you have to redo a couple steps if you want to update one rom's kernel.
Pic no longer related.
guys im having some trouble, when i go to the systemchanger app and grant permission instead of the screen going blank it gets stuck on a screen with two lg logos.
i think i havent installed the fastboot drivers correctly. i assumed it gets installed when i run flash.bat, but it may need to be installed seperately. if it needs to be installed how do i do it cause its just a .bin file and i have no idea what to do with it
---------- Post added at 10:20 PM ---------- Previous post was at 10:15 PM ----------
adamiscool said:
I'm considering the dual boot, but want to know if it's possible to go back to single boot if/[hopefully] when radio is fixed. I suppose it'll be a matter of using original nvflash and format to have only one partition?
*edit1* Ok, now I'm getting my toes wet with this. fastboot.bin...what am I doing with this? The instructions say "install NVidia fast boot." Ok, but how? Or, has it already been installed with APX? I'm confused.
*edit2* ok I have dual boot! Wow this is interesting. Been running it through different combinations of reboots through system changer, and it seems when I update gb to the latest mazkrnl it won't stick after switching to jb and back again.
Do I need to use the boot.img from the kernel and repack it into step3?
Sent from my LG-P999
Click to expand...
Click to collapse
hey, i have the same question, did u install the fastboot.bin separately or does it get installed with the flash.bat???
Blackout One Pack Edited: png-optimized for speed/loading/size and added full preview
The theme is simple enough:
1) White htc "ONE" logo on black bg at splash (splash.zip)
2) fade in white htc "ONE" logo with 8 white loading bubbles transitioning to green before looping x8 until system startup (vzw_bootup.zip)
3) quick green htc "ONE" logo fade-out for shutdown. (hTC_downanimation.zip)
I've included the zip files referenced above as well a an animated .gif preview (full now)
The entire sequence is as follows: fade up white logo, load bubbles, go green, flash three times, repeat loading animation...
For the splash be sure to place in fastboot folder. from the cmd line enter "fastboot oem rebootRUU" and then "fastboot flash zip splash.zip" once the htc logo comes up in RUU mode and then "fastboot reboot" once you're done.
>>>For animations replace the current ones (typically names as per above) in your /system/customize/resource folder and be sure the permissions are set correctly. You'll need root (for animations) and S-OFF (for splash)
Enjoy!
Working good.
do these need to be renamed bootanimation.zip and downanimation.zip to work? i my resource folder i do not have any files in there named like these files.
thanks
mikey2487 said:
do these need to be renamed bootanimation.zip and downanimation.zip to work? i my resource folder i do not have any files in there named like these files.
thanks
Click to expand...
Click to collapse
if you're running stock, these are the actual conventions. I haven't tried any, but if those are the names of the files in your directory then by all means..
mrcr0nic said:
if you're running stock, these are the actual conventions. I haven't tried any, but if those are the names of the files in your directory then by all means..
Click to expand...
Click to collapse
I'm on viper, i tried doing it that way and renaming them to what they were in the resource tab but it didn't work, viper rom thou has a setting in their tweaks to add a boot animation and i did it that way and it worked. great animation by the way really digging it!
mikey2487 said:
I'm on viper, i tried doing it that way and renaming them to what they were in the resource tab but it didn't work, viper rom thou has a setting in their tweaks to add a boot animation and i did it that way and it worked. great animation by the way really digging it!
Click to expand...
Click to collapse
Awesome. Glad you liked it! Haven't switched over to a custom ROM just yet as I've heavily modified the stock one.. I suspected it was going to require ROM-specific settings. Liking Viper?
Great!! Thanks!! Got rid of that nasty red verizon screen!
mrcr0nic said:
Awesome. Glad you liked it! Haven't switched over to a custom ROM just yet as I've heavily modified the stock one.. I suspected it was going to require ROM-specific settings. Liking Viper?
Click to expand...
Click to collapse
What have you modified about it?!
Yeah I'm really liking it. I never really liked sense or tw that much I'm more of an aosp guy but this rom is pretty bithin. Waiting for cm or slim roms to come out with a build for this phone. Other than that its petty solid. Haven't had any issues with anything and they a have few dark themes which make it really nice
mikey2487 said:
What have you modified about it?!
Yeah I'm really liking it. I never really liked sense or tw that much I'm more of an aosp guy but this rom is pretty bithin. Waiting for cm or slim roms to come out with a build for this phone. Other than that its petty solid. Haven't had any issues with anything and they a have few dark themes which make it really nice
Click to expand...
Click to collapse
This is actually the first time I've been off cm in a while.. I'm waiting for the lightweights as well.. Sense is definitely better than it was in the past, but I've shut off a lot. Hated tw.. Never ran a galaxy on anything other than aosp.. Really like the latest HTC..
Well if anyone had an animation or a mod question feel free. I swapped out the kernel, enabled all the great settings and froze everything else..
So I've been Googling and Googling, but can't find anything on how to implement sounds within CM11 Theme-compatible Boot Animations; is it possible, and do any ROMs for the OnePlus One even support it??
I've tried even circumventing the CM11 Theme Engine completely and just added a line into the desc.txt file to see the OGG file in system/media, but all to no avail.
Any insight into this would be GREATLY appreciated!! I'm trying to see if I can get this to work in this boot animation, and there is surprisingly little current documentation on this that I could find.
So nothing then I guess? Has anyone found anything on this at all?
Did you try to edit build.prop
There a line that disable boot sound change it from 1 to 0 or the upside I don't know exactly
madkita said:
Did you try to edit build.prop
There a line that disable boot sound change it from 1 to 0 or the upside I don't know exactly
Click to expand...
Click to collapse
Thanks for providing some info Madkita!
I did see that option, but I was hoping for a more universally usable option, like something that could be loaded in any ROM with an APK, and without a root hack for those not rooted. I think it might just not be possible that way, so I'll have to abandon this after all.
Could you just add a apk file or make a boot animation with it included?
- Samsung Galaxy Ace ii-x CM 4.4.4.
- Samsung Galaxy Grand Prime 5.1
- Samsung S2 CM 12.1
- Nexus 5 5.1
- Nexus 7 5.2
- LG L5 4.1
- LG P690B 2.3.4.
- HTC One
buffering.... said:
Could you just add a apk file or make a boot animation with it included?
Click to expand...
Click to collapse
It would have to be an APK file for that to work, or maybe an installer ZIP like the one I use for my ctOS Boot Animation.
Either way, the boot sound file is named differently across ROMs, so without creating a script to figure out if the ROM supports it and what the subsequent file is named, I'm really not sure how to best do this.
That being said, if anyone has any ideas of how best to universally implement something like this, I'm all ears! And if anyone wants to take a stab at compiling something for my ctOS Boot Animation, I'll happily put up a bounty of $20 for the first person who can make a CM11/CM12 boot animation sound work across all devices.