Related
First and foremost I take no credit for anything contained in this ROM. I have taken bits and pieces from various ROMs I like and rolled my own.
The base is Binny's stock ROM.
LauncherPro from unrevolved by ozzeh
Has Both HTC and Android Music apps (in case someone, like me, prefers the old one)
Rosie and All Rosie widgets removed
WiFi Tether
TouchFlo port from Samsung included (choose launcher for yourself)
Again, all credit to the Devs listed above. I am no Dev myself, only a chef cooking up something to my own liking and thought I would share.
Anybody wanna test for me?
Download here
Installation...
Copy TouchOfPhotons-v1.zip to your SDCARD and reboot into Clockwork recovery. Then Install Zip and Choose Zip from SDCARD.
Be sure to take a Nandroid Backup and WIPE FIRST!
So far everything seems to be working fine for me...WiFi, BT, etc...
I would recommend Hydra's Undervolt with Wireless-N kernel here. This just needs to be installed like any other zip using Clockwork recovery.
Also I would recommend the MultiTouch Keyboard DANESHM90 managed to pull from the Droid-X here. This can be installed with Astro or an equivalent of your choice.
Thanks to all in the community. I am glad to be a part of it!
UPDATE.... Kernel link above may not work consistently so I am attaching the zip.
For those requesting it, I am attaching the TouchFlo Launcher. Just install via Astro or similar.
UPDATE - 7/7 --- Thanks to bowtiedeuce for pointing out the fix scuccia found for the Facebook constantly syncing issue. I am attaching that patch here (full credit to him, of course). Just install it like any other zip from your sdcard using clockworkmod recovery (install over your current setup, no wipe) and it should resolve the sync issue. Future releases will not have this bug.
No screenshots? It seems like most of the android roms have no screen shots.
I'm downloading it right now. I'll post feedback
Sent from my HTC Incredible
Bxsteez said:
No screenshots? It seems like most of the android roms have no screen shots.
Click to expand...
Click to collapse
Yeah,
Sorry about that. Was headed out the door and wanted to get something up for you guys before I left.
Anywhoo, here are some screenies. You can see I'm using TouchFlo primarily.
Oh, and the MT keyboard I provided a link to...
BTW....
The Live Wallpapers work great with the TouchFlo launcher.
I think I'm going to have to try ,this sounds great thank you looks good to
The rom is actually really nice an smooth. But its just not for me. I do recommend to at least try this rom. Good work man keep up the great work.
Sent from my Droid Incredible
I'm loving this ROM! Just got everything set up on it...
Couple things though... I'm having a hard time pushing a custom bootanimation.zip to /data/local
I had no problem doing it on a just a plain rooted Inc, but I can't with this...
Another would be requesting to get the 2.1 lock screen and not the HTC one... Thanks! Awesome work, keep it up!
each time i download this file ROM and i try to install it, i get an error when it is trying to write to BOOT that says E: No Room Left on Device, failure at Line 394. Has anyone else seen this and if so, have they figured out how to fix it? I have wiped the boot partition and completely formated my whole system. Still the same error, i also redownloaded the file 3 times and still the same issue.
ejlax said:
each time i download this file ROM and i try to install it, i get an error when it is trying to write to BOOT that says E: No Room Left on Device, failure at Line 394. Has anyone else seen this and if so, have they figured out how to fix it? I have wiped the boot partition and completely formated my whole system. Still the same error, i also redownloaded the file 3 times and still the same issue.
Click to expand...
Click to collapse
That's the first I'm hearing of this. Can anyone else confirm?
Sent from my ADR6300 using XDA App
Working great here, do far. I used ROM Manager for the install.
I will be checking it out today.
Great cooking!
Sent from my ADR6300 using XDA App
i am not really a nUbcake either...so that is making me kinda mad. I even messed with the update-script file to see if i could comment out the line that was erroring out, but it was to no avail. Could someone post a nandroid backup of the rom that i could try?
to clarify it is giving me an error saying "Error writing to Boot"
EDIT: got it working by removing the write_raw_image line at the end of the update_script
taypotts said:
I'm loving this ROM! Just got everything set up on it...
Couple things though... I'm having a hard time pushing a custom bootanimation.zip to /data/local
I had no problem doing it on a just a plain rooted Inc, but I can't with this...
Another would be requesting to get the 2.1 lock screen and not the HTC one... Thanks! Awesome work, keep it up!
Click to expand...
Click to collapse
I just pushed the bootanimation.zip from the DroidX to /data/local/ and it worked fine. What animation are you trying to push?
Sent from my ADR6300 using XDA App
The kernel link is not working, anyone know why I got error ?
That's strange. I'm getting an error trying to use that kernel link on my PC but if I click it on my phone (using the XDA app) it downloads. I'll try to get a mirror up.
EDIT - Actually just attached the kernel to the OP.
Sent from my ADR6300 using XDA App
Using this ROM with the Droid-X boot up sound and animation and the undervolt-N kernel. Very nice! My favorite so far and I have tried them all.
Thanks photonmedia!
Im had the same issue as ejlax did. However after the reboot everything seems to be there. Is there anything that didnt install after that error?
pbchris said:
Im had the same issue as ejlax did. However after the reboot everything seems to be there. Is there anything that didnt install after that error?
Click to expand...
Click to collapse
IF anything, I would says possibly the kernel (based on the error he says he got), but I would recommend you use the kernel attached in the OP anyway, so....
Really I don't know why you two are getting those errors and not the others who are testing, though. You are wiping before you install, right? Always the best practice: Nandroid Backup + Wipe.
I've been using it for most of the day - no issues. Phone, Google Voice, SIP phone, BT - looks flawless, so far...
Sent from my ADR6300 using XDA App
photonmedia said:
I just pushed the bootanimation.zip from the DroidX to /data/local/ and it worked fine. What animation are you trying to push?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
That's the same one I'm trying to use.. I'm not sure.. I was able to do it the same way with just stock root, but it won't take now... can you tell me each step that you did to do it? Thanks!
After getting a new hero and using my nandroid from old phone it occurred to me, why not distribute a working backup rather than a rom to flash.
This may not be the best way but if a dev flashed their rom, skipped sign in, made sure everything was functional, then made a backup and distributed that, wouldnt that cut down on people getting mixed results post flash?
Sent from my HTC Hero CDMA using XDA App
Two top reasons, why ROM vs. Nandroid backups...
1. Recovery dependency
2. Customization
andythegreenguy said:
Two top reasons, why ROM vs. Nandroid backups...
1. Recovery dependency
2. Customization
Click to expand...
Click to collapse
1. Specify recovery used or make multiple backups per recovery.
2. Backup would contain basic rom, leaving customization to be done after restore.
After flashing rom, gapps, black market, I always backup then start making changes incase I delete something I'm not supposed to.
Example: lets say I flash my rom and gapps. I start my phone, skip sign in, begun fumbling through menus making sure I get no FCs, etc. Check too see if GPS is working, sms/mms, youtube, camera, etc. At this point everything works and I make a backup. My assumption is that if someone else uses that backup, everything will work for them as well. (google was never linked due to skipping sign in).
Not trying to prove you wrong, just expressing my thoughts until they themselves are proven incorrect.
Sent from my HTC Hero CDMA using XDA App
JWhip804 said:
1. Specify recovery used or make multiple backups per recovery.
2. Backup would contain basic rom, leaving customization to be done after restore.
After flashing rom, gapps, black market, I always backup then start making changes incase I delete something I'm not supposed to.
Example: lets say I flash my rom and gapps. I start my phone, skip sign in, begun fumbling through menus making sure I get no FCs, etc. Check too see if GPS is working, sms/mms, youtube, camera, etc. At this point everything works and I make a backup. My assumption is that if someone else uses that backup, everything will work for them as well. (google was never linked due to skipping sign in).
Not trying to prove you wrong, just expressing my thoughts until they themselves are proven incorrect.
Sent from my HTC Hero CDMA using XDA App
Click to expand...
Click to collapse
Both of you guys are Right in a way, and I kind of had a little Idea from Reading all the Posts!
What if a Developer/User "Whoever" was to Upload a Nand Backup But with a John Doe Google Account Just for Nand Purposes, "Basically for Anyone who wants to Download it"
I Read *SO MANY* Posts where Users Have a Hell of a Time Trying to get certain Roms Installed...
So now let's use me for Instance, Say I was having a Issue with Installing a ROM where it just Wouldn't Work for whatever Reason. Actually lets say I was a Noob with Some or Little to Any Experience and Instead as a Alternative I Used John Doe's Nand Backup just to get it Booted!!
Here's the Catch...
From there Meaning once it Boots, and Correct me if I'm Wrong! Wouldn't I be Able to just Pull the Battery and Do a Full Wipe....
Data/Cache/DalvikCache and Reboot back to the Same ROM Minus the John Doe?
Meaning Now I'd be able to Start the ROM Fresh and Replace the Temporary John Doe Account with My Own Email.gmail.com/Password, Then from there have the Option to Create Another Backup with My Own Customizations!
Remember like I said, Although I Usually I Don't have any Issues during a ROM Install, But Realistically That Doesn't mean Everyones is as Fortunate, So this Might, Could be a Alternative for Whoevers Willing to Try it!!
If Anything I Said, Better Yet more or less Suggested is Wrong... Please Correct Me, But the Above is Based on the Best of my Knowledge!
Good Luck!!
Sent from my Hero using XDA App
PMGRANDS said:
Both of you guys are Right in a way, and I kind of had a little Idea from Reading all the Posts!
What if a Developer/User "Whoever" was to Upload a Nand Backup But with a John Doe Google Account Just for Nand Purposes, "Basically for Anyone who wants to Download it"
I Read *SO MANY* Posts where Users Have a Hell of a Time Trying to get certain Roms Installed...
So now let's use me for Instance, Say I was having a Issue with Installing a ROM where it just Wouldn't Work for whatever Reason. Actually lets say I was a Noob with Some or Little to Any Experience and Instead as a Alternative I Used John Doe's Nand Backup just to get it Booted!!
Here's the Catch...
From there Meaning once it Boots, and Correct me if I'm Wrong! Wouldn't I be Able to just Pull the Battery and Do a Full Wipe....
Data/Cache/DalvikCache and Reboot back to the Same ROM Minus the John Doe?
Meaning Now I'd be able to Start the ROM Fresh and Replace the Temporary John Doe Account with My Own Email.gmail.com/Password, Then from there have the Option to Create Another Backup with My Own Customizations!
Remember like I said, Although I Usually I Don't have any Issues during a ROM Install, But Realistically That Doesn't mean Everyones is as Fortunate, So this Might, Could be a Alternative for Whoevers Willing to Try it!!
If Anything I Said, Better Yet more or less Suggested is Wrong... Please Correct Me, But the Above is Based on the Best of my Knowledge!
Good Luck!!
Sent from my Hero using XDA App
Click to expand...
Click to collapse
Wouldn't really have to wipe, just add another gmail account and delete John Doe's.
Sent from my HTC Hero CDMA using XDA App
JWhip804 said:
Wouldn't really have to wipe, just add another gmail account and delete John Doe's.
Sent from my HTC Hero CDMA using XDA App
Click to expand...
Click to collapse
Yeah that's True, I Never Added More than 1 Account, What do you just go back to Setup??
Sent from my Hero using XDA App
For me, even tho it seems perfectly feasible, I think I'd really miss the first boot of a new ROM and kind of feel like I'm getting a 2nd hand one lol.
Sent from my HERO200 using XDA App
jp2012 said:
For me, even tho it seems perfectly feasible, I think I'd really miss the first boot of a new ROM and kind of feel like I'm getting a 2nd hand one lol.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Funny thing is.... I Guess I Have to Admit Your Right, There Really Isn't Anything else that Compares to Booting a ROM on Your Own!!
Lmao......
Sent from my HERO200 using XDA App
ok so using a John Doe account wont work. Once you sign in, that account can only be removed by reset.
Ok so lets just get these out there for people to try out.
Below is a download link to 2 nandroid backups.
The two recoverys used were CW 2.5.0.7 and RA-Recovery-1.6.2.
Download here.
MegaUpload
DO NOT FLASH ZIP!!!
Unzip file, inside your should find two folders. Use the correct file for your recovery.
As always, Nandroid backup first.
Perform a full wipe.
Restore downloaded backup. (In RA-Recovery, if you get a error message, go Here to see instructions on how to restore using adb.)
Reboot
(Click Market to sign in.)
Test away!!
Once booted you should be running aospCMod, dark horse theme, black market, blue and black facebook, black MIUI Music, LauncherPro (themed widgets if you have unlock code), Black Youtube.
Apps you will NOT see in drawer are camera, gallery, file manager, dev tools. And prob some others, cant remember atm.
Thank you in advance for helping me test this out.
A similiar method is used on certain phones. The dev can make a nand or copy system and data into .img or .tar files. The recovery then unpacks the images into the correct directory.
Sent from my dual-booted liquidsense 2.1
JWhip804 said:
ok so using a John Doe account wont work. Once you sign in, that account can only be removed by reset.
Ok so lets just get these out there for people to try out.
Below is a download link to 2 nandroid backups.
The two recoverys used were CW 2.5.0.7 and RA-Recovery-1.6.2.
Download here.
MegaUpload
DO NOT FLASH ZIP!!!
Unzip file, inside your should find two folders. Use the correct file for your recovery.
As always, Nandroid backup first.
Perform a full wipe.
Restore downloaded backup. (In RA-Recovery, if you get a error message, go Here to see instructions on how to restore using adb.)
Reboot
(Click Market to sign in.)
Test away!!
Once booted you should be running aospCMod, dark horse theme, black market, blue and black facebook, black MIUI Music, LauncherPro (themed widgets if you have unlock code), Black Youtube.
Apps you will NOT see in drawer are camera, gallery, file manager, dev tools. And prob some others, cant remember atm.
Thank you in advance for helping me test this out.
Click to expand...
Click to collapse
Good Thread Man... and Very Handy for a Lot of Noobs!!
Oh Yeah, Almost Forgot! Though I'm Past the Noob days I've been having a Hell of a Time Installing the Pancake 2.2 Rom! So far It's the Only one I Haven't been able to get Running! Although its Far from Stable, I Need it for Development Purposes for my ExpressoEnergyHeroc Rom! Anyone Willing to Get it, and Upload a Nandroid of that for me?
I'd Appreciate it guys, Hopefully with it I'll be able to Fix the Damn Camera Once and for All!
Sent from my HERO200 using XDA App
PMGRANDS said:
Good Thread Man... and Very Handy for a Lot of Noobs!!
Oh Yeah, Almost Forgot! Though I'm Past the Noob days I've been having a Hell of a Time Installing the Pancake 2.2 Rom! So far It's the Only one I Haven't been able to get Running! Although its Far from Stable, I Need it for Development Purposes for my ExpressoEnergyHeroc Rom! Anyone Willing to Get it, and Upload a Nandroid of that for me?
I'd Appreciate it guys, Hopefully with it I'll be able to Fix the Damn Camera Once and for All!
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I'm using this thread as the testing method. Once we confirm the advantages of it and that it works well, I will start threads in dev and theme forums. Not sure if I will need permission from creaters of the roms to do so but I will look into that. Eventually I'd like to have a few people helping to get most roms on there and help keep them updated.
So for now do the testing and report back on the results. Also try the CW backup on earlier and later versions of CW.
Sent from my HTC Hero CDMA using XDA App
JWhip804 said:
I'm using this thread as the testing method. Once we confirm the advantages of it and that it works well, I will start threads in dev and theme forums. Not sure if I will need permission from creaters of the roms to do so but I will look into that. Eventually I'd like to have a few people helping to get most roms on there and help keep them updated.
So for now do the testing and report back on the results. Also try the CW backup on earlier and later versions of CW.
Sent from my HTC Hero CDMA using XDA App
Click to expand...
Click to collapse
Let me know if Need a Hand with Anything, I'll Help you with Whatever I'm Capable of Helping with...
Sent from my HERO200 using XDA App
I'm sorry if someone already asked this question but I was not able find an answer. I am running a custom ROM now, do I have to go back to stock before flashing another ROM?
It is usually not necessarily to do it but it a very good idea to return to stock and master clear with the odin-1-click
Sent from my GT-I9000 using XDA App
No you don't need to go back to stock. Nor is is necessary to master clear. Most if not all the roms on here will do a full wipe of your SD card during the install. Flashing back to stock just adds another chance to mess up your phone. This was advised, several months back but it's not necessary now. This doesn't apply if you want to flash to CM7. They have their own install procedure that is different than anyone elses.
Just to add to what the others said. Make sure u flash a 2.2 based rom over ur curent (if thats what u are.using atm). Also you cant restore system app, it will screw up with ur new rom!
Sent from my SAMSUNG-SGH-I897 using XDA App
BWolf56 said:
Just to add to what the others said. Make sure u flash a 2.2 based rom over ur curent (if thats what u are.using atm). Also you cant restore system app, it will screw up with ur new rom!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
The 2.2 stock will not let you flash a rom over it. Go back to 2.1 stock
Sent from my SAMSUNG-SGH-I897 using XDA App
crystalhand said:
The 2.2 stock will not let you flash a rom over it. Go back to 2.1 stock
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Not what I meant.
If he flashed, lets say, FireFly (which is 2.2 based) then he can't flash over with, lets say, CM7 (which is 2.3 based). Just simple logic
@ OP - You can look on the ROM's thread to see what it is based on.
Thank you for all your help. I'm using Phoenix Ultimate now and want to try out the other ROM.
It takes like ten minutes to odin back to stock. I do it every time, just feels like a cleaner install. Plus all the devs put that in their instructions. I trust the devs.
If you download the CWM update.zip before you Odin to stock and leave it on your phones internal SD card, you don't have to root or get ROM manager. Place your new ROM on the internal card too. Just Odin to stock, allow to boot, and restart into recovery (3 button combo), install updates (twice) then use CWM to install zip from card (ROM you downloaded).
Sent from my SAMSUNG-SGH-I897 using XDA App
quarlow said:
It takes like ten minutes to odin back to stock. I do it every time, just feels like a cleaner install.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
One less time touching Odin is one less time tempting fate. But that's just me. I'm pretty sure every rom dev in here has bricked a phone at least once...
much agreed. less odin. less potential for problems.
roms do a wipe now. doesnt matter what you had on it 2.1 or 2.2
2.3 is the only rom version that has a different partition table.
there is no issue flashing a 2.2 rom over 2.1 or vice versa. how CAN you upgrade from 2.1 to 2.2?? CWM anyone? oh **** right!
the only issue with flashing over 2.2 is the 3e recovery... and thers a fix for that. you dont need to go back to 2.1 to avoid the signature verification error... @crystalhand...
quarlow said:
It takes like ten minutes to odin back to stock. I do it every time, just feels like a cleaner install. Plus all the devs put that in their instructions. I trust the devs.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Not all devs put it in their op. Some devs say flash first thru clockwork and only use odin when there are problems. Odin could be better used as a recovery tool only, not the first thing you do whenever you want to flash a new rom. Just my opinion.
Sent from my SAMSUNG-SGH-I897
1tontomato said:
Odin could be better used as a recovery tool only, not the first thing you do whenever you want to flash a new rom. Just my opinion.
Click to expand...
Click to collapse
EXACTLY as it should be.....
No, odin is potentially more dangerous than any standard rom flash. as has been mentioned, use in case your in some s
I've always flashed back to stock using Odin whenever I flash a new rom. Like someone else on this thread said, it just feels cleaner doing it that way. While I don't doubt you guys when you say it's dangerous, would anyone like to offer a brief explanation as to why that is? And would anyone be willing to guess at what the odds of a permanent brick might be? Are we talking something like 1 in every 10 flashes or more like 1 in 1000?
If it's closer to the first one then we really are playing with fire here but if the odds are more like the second one then I don't consider that much of a risk.
Juanmail15 said:
I've always flashed back to stock using Odin whenever I flash a new rom. Like someone else on this thread said, it just feels cleaner doing it that way. While I don't doubt you guys when you say it's dangerous, would anyone like to offer a brief explanation as to why that is? And would anyone be willing to guess at what the odds of a permanent brick might be? Are we talking something like 1 in every 10 flashes or more like 1 in 1000?
If it's closer to the first one then we really are playing with fire here but if the odds are more like the second one then I don't consider that much of a risk.
Click to expand...
Click to collapse
I highly doubt someone is going to give you a "odds" answer. Phones can be finicky and they often do weird things. The less you're "changing" things, the better. Odining back to stock then flashing again to the ROM of choice just adds another chance for something to go wrong. Not just cable falling out or battery falling out, just weird coincidence. When there's absoutely no reason to go back to stock, why take the chance? Just because you're programed to THINK it's cleaner doesn't mean it is. As has been said several times already, most roms do a complete wipe of the sd card so there's really no reason to odin or masterclear.
axis01 said:
I highly doubt someone is going to give you a "odds" answer. Phones can be finicky and they often do weird things. The less you're "changing" things, the better. Odining back to stock then flashing again to the ROM of choice just adds another chance for something to go wrong. Not just cable falling out or battery falling out, just weird coincidence. When there's absoutely no reason to go back to stock, why take the chance? Just because you're programed to THINK it's cleaner doesn't mean it is. As has been said several times already, most roms do a complete wipe of the sd card so there's really no reason to odin or masterclear.
Click to expand...
Click to collapse
+1
Odin should only be used as a "Oh S**T I bricked my phone" program. But then again, if you read and know what you're doing than it should never be "needed"
axis01 said:
I highly doubt someone is going to give you a "odds" answer. Phones can be finicky and they often do weird things. The less you're "changing" things, the better. Odining back to stock then flashing again to the ROM of choice just adds another chance for something to go wrong. Not just cable falling out or battery falling out, just weird coincidence. When there's absoutely no reason to go back to stock, why take the chance? Just because you're programed to THINK it's cleaner doesn't mean it is. As has been said several times already, most roms do a complete wipe of the sd card so there's really no reason to odin or masterclear.
Click to expand...
Click to collapse
Completely agree just want to clarify 1 thing. The roms don't do a complete wipe of the sdcard. The wipe the /data /cache and /system partitions, leaving the /sdcard completely intact, just like flashing to stock would. Master clear just reformats /sdcard partition and is not really needed as the os doesn't use this to function and including this in a rom would be catastrophic if the zip is in fact on the /sdcard partition you are wiping with it.
The most I do is clear cache, data and disable lagfix.
quarlow said:
If you download the CWM update.zip before you Odin to stock and leave it on your phones internal SD card, you don't have to root or get ROM manager. Place your new ROM on the internal card too. Just Odin to stock, allow to boot, and restart into recovery (3 button combo), install updates (twice) then use CWM to install zip from card (ROM you downloaded).
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
So you'd just drop the update.zip on your internal drive, drop the ROM in as well, boot into recovery and flash it that way?
Lancered said:
So you'd just drop the update.zip on your internal drive, drop the ROM in as well, boot into recovery and flash it that way?
Click to expand...
Click to collapse
Yup. That's how u do it, if you have no need to root before hand and back up, I'm assuming you've done that if I remember right you are the girl I told to brick her phone yesterday to return, is the replacement on eclair or froyo? Ig it on froyo you will have to get past the 3e recovery that's why I ask.
I figured we needed a thread to discuss the BootManager app.
First, big thumbs up to GFlam & Conap for this app! I used Conap's CELEB CM Roms on the Eris for a long time.
Now:
They have a User Manual on their site.
What does it do? You keep your rom on the phone, and you can add up to 4 more on your SD card. You use the app's menu to select which one you want to boot into next.
What is it? it is an apk you can get from the market. It lives on your phone. It doesn't mess with Clockwork and such.
What's the catch? There is something you have to pay attention to...It requires a connection to the market to verify it's authenticity. So, whenever you add a new rom, you need to connect it to the market...the trick: you need to flash gapps right after you flash a rom before you boot into it.
What If I forgot to flash gapps?!? No big deal. If you boot into a rom you installed that doesn't have the market, the BootManager app won't work, so you can't use it to boot back into another rom. They have a solution - boot into recovery and flash the "update.zip" located in the bootmanager>phonerom folder on your sd. Then your phone will reboot into your internal phone rom.
What's the catch, part 2? Some roms have custom scripts that run when they boot, so they don't play well, especially when installed on the SD card.
What else do I need to know? Rom installs take longer. After installing, the roms on the sd card do not lag. You can back up the roms that you install through the app.
This is a dream for people who want to play with nightlies or try a bunch of roms, but need their old-reliable come Monday morning. Check it out!
There is more discussion on this thread: http://forum.xda-developers.com/showthread.php?t=1189459
Disclaimer: I have no affliliation with Init 2 Win It. I just love this app.
I'll start with a question, too. I put BAMF3.0 rc 4.9 in an SD slot. When I boot in, everything works except Titanium Backup can't find root. Anyone else have this problem?
strongergravity said:
I'll start with a question, too. I put BAMF3.0 rc 4.9 in an SD slot. When I boot in, everything works except Titanium Backup can't find root. Anyone else have this problem?
Click to expand...
Click to collapse
Interesting. I'm having a similar problem with MyBackup Pro. The app would request SU permission but then it never acknowledged that it had it. I also had BAMF 3.0 Rc 4.9 running off SD
When I boot into miui from cm7 it won't connect to my wifi to let me authenticate my rom manager
Sent from my ThunderBolt using XDA App
stayin100 said:
When I boot into miui from cm7 it won't connect to my wifi to let me authenticate my rom manager
Click to expand...
Click to collapse
I haven't tried the MIUI yet. It might be another with a custom boot script.
You could try to install it as the internal phoneROM and see if it works. If it doesn't you'll need to restore a nand backup.
Good luck, should you choose to accept this mission. This post will self-destruct in 3...2...1...
ok so maybe someone can help me. im trying to flash CM7 and i flashed it and forgot to flash the GAPPS thing before a reboot. i got back into my original rom and im ready to try it again. i have CM& ready to flash, but how do i flash GAPPS before the reboot? do i do the flash of GAPPS from within bootmanager, rom manager, or hboot? thanks!
Flash gapps through bootmanager just like the rom, in the same slot. Dont wipe anything.
Sent from my Tablet using XDA Premium App
strongergravity said:
Flash gapps through bootmanager just like the rom, in the same slot. Dont wipe anything.
Sent from my Tablet using XDA Premium App
Click to expand...
Click to collapse
worked perfect. now do i flash kernels like imoseymons the same way? overwrite the rom slot?
[email protected]|ice said:
worked perfect. now do i flash kernels like imoseymons the same way? overwrite the rom slot?
Click to expand...
Click to collapse
Yep. The same way.
Remember to rename the slot to help you remember what you have.
strongergravity said:
Yep. The same way.
Remember to rename the slot to help you remember what you have.
Click to expand...
Click to collapse
worked out perfect, thank again for your help.
[email protected]|ice said:
worked out perfect, thank again for your help.
Click to expand...
Click to collapse
That's why I'm here.
disappointed that the synergy nightlies flashed to a slot put me in a boot loop. but was excited that all i had to do to fix it was flash the update.zip under bootmanager/phone
Maybe I'm missing something but where can I find the gapps zip/ every time I try to boot from the app, its telling me either no Rom installed or no image found
I installed all 3 versions of the recently leaked GB ROM using bootmanager and interesting NONE of them will boot up. Best I can tell from adb logcat is that the ROM does a memory test and the wrong memory type is returned causing a boot loop at that point.
Smells like a bit of copy protection testing going on.
Yea something's not working right with the app... I can't get any Rom to install.....
Sent from my Desire HD using XDA Premium App
A lot of the Sense roms fail. I have Monolith running fine.
Hey there, just wondering of anyone else is having the problem of Sd card space going into limbo if the ROM install doesn't go well (i'm talking the install or back up glitches and doesn't finish, not it actually finishing and getting a boot loop. I've tried wiping cache/dalvik cache, all the cleaning functions within the app. Deleting the slots and wiping the slots didn't work either. Like I said it seems to be in limbo, and don't feel like moving all my data off my card and reformatting every time this occurs. Any ideas?
Hey guys,
I love this app. I also had some problems but now I have Gingeritis as my phoneRom and switch between SHIFTS3NS3 and BAMF which are all gb roms.
The trick I found was that if it doesn't load the first time keep trying, it took me about two tries to load SHIFTS3NS3 and about 3 for bamf. Make sure you use ext2.
Also make sure your phone stays awake.
If you have an issue email the Devs they responded to me with in 10 min of the email.
Great app
Sent from my bad ass Thunderbolt with Gingeritis 3D VIII
Delete the installed roms slot via Bootmanager, rebooted and try again
Sent from my bad ass Thunderbolt with Gingeritis 3D VIII
WOW! HOLY CRAP THIS PLACE IS DEAD! Its been a while since I read around these Zio places. Yup, my ol Zio still bootlooped (its around here somewhere). I tried all the "guides" n zip's and skd's and all that other.....stuff, its koo gathering and installing stuff and gettin that lil rush of hope, but then one lil thing goes wrong or ain't in the step-by-step guied, BOOM- all bad, and nobody's around all of a sudden. Alot of HERE, TRY THIS POST FROM SO N SO (not for the Zio), GO TO BLAHBLAH.COM install that n profit (evil setup to rom someone's phone AND wipe it clean), BUT ITS ALL MY BAD, NEWBIE like me shouldn't mess with roots n roms. Don't get me wrong, if I can find somebody that would fix it for cash, id go back to my zio and chuck this HALLWIE A2 (whatever its called) to a dev. Well, I'm probly gona get smashed for posting this. DEEEEP BREATH........K, I FEEL BETTER NOW.
Now I'm soo broke I cant even pay attention!
What you need help on? Bootloop fix? I can help you. Pm me on the details. Could you still get into faatboot or recovery? What service sprint or cricket!?
Sent from my Zio using XDA App
My zio is messed up too. I have no home/launcher or whatever you wanna call it. I can't get to settings to enable usb debugging either so none of the adb stuff works for me (so far). New to this and I don't want to buy another phone just yet. More details can be provided as to how this happened if needed. ty.
Not sure where it is but there was a fast boot zip of launcher apk. If you boot your phone into fast boot and cwm copy the zip to the phone and then flash the zip to your Zio it should resolve the issue
Sent from my Zio
Krsmqn said:
My zio is messed up too. I have no home/launcher or whatever you wanna call it. I can't get to settings to enable usb debugging either so none of the adb stuff works for me (so far). New to this and I don't want to buy another phone just yet. More details can be provided as to how this happened if needed. ty.
Click to expand...
Click to collapse
I can make a launcher apk. flashable zip for ya,just let Me know.
Sent from my LG-P509 using xda premium
openZIO Rom issue
Hi, I just installed the openZIO 2.1.2 ROM. Everything worked fine, but after rebooting and going through the initial set up (i.e. the google user setup blahblah) the VTL Launcher continually force closes and I can't do anything but go back and recover my original boot.img has anyone else had this kind of issue? Any possible fixes? Any help would be appreciated, I know not to many people are in using the Zio forums anymore... but yeah.. Thanks in advance
Try Reflashing again
Sent from my LG-P509 using xda premium
I've actually already done that, and it's still doing the same thing. I've deleted and re-downloaded the ROM, and re-flashed it to my phone, and still having the same issue. VTL Launcher just continually force closes, and it sucks cause I've been waiting months to get to install the ROM cause I couldn't afford a new USB cord. I've read so much on this ROM and everything for the Zio and was excited to actually be able to overclock my phone, and get some pretty good performance boosts out of it. Now I got one, and can't get it to work.. what a sad day
Could you explain your steps when flashing?
Sent from my LG-P509 using xda premium
well I first move the .zip to the sd, then power down and boot up CWM, and "install from SD card" and once it's finished flashing, I reboot the phone. when it comes back up my kyocera logo comes back up and it takes me through the first-boot programming (google sign-in) and once I input my un/pw and sign in, it tells me that VTL had an error and must hit force close. and once I hit force close it continues to come up saying the same thing over and over again. so I rebooted my phone, still the same thing. SO I go back through and flash it back to my original boot.img. I have gone through and completely deleted the openZIO 2.1.2.zip file and re-downloaded it, and gone through the same steps to see if maybe it was just a bad file somehow. But to no avail, still having the same issues.
After you boot into cwm : wipe cache partition, then go into mounts and storage, format: system, data, cache :then go into advanced and wipe dalvick cache.
Now flash rom
Sent from my LG-P509 using xda premium
Ok just went through with what you had mentioned, and still getting the same results. "Sorry! The application VTL.Launcher (process android.process.acore) has stopped unexpectedly. Please try again. with the only option to force close. As soon as I force close, the same message pops up
Have you tryed flashing my rom?
I would try that, and see what happens.
You can always push a launcher with adb or Droid commander.
Sent from my LG-P509 using xda premium
doing this now actually.. been reading for the last hour or so and seems like you did some good work on the ROM. it's flashing now, hopefully all works well I'm excited to see how it goes.
Well it flashed and well... seems to be having a strange issue.
When switching screens, it seems to glitch out? Like you see the icons, and when you switch screens, it's like the icons move but it freezes different frames. imma re-flash it in the morning to see if that helps any.
XCmaster said:
doing this now actually.. been reading for the last hour or so and seems like you did some good work on the ROM. it's flashing now, hopefully all works well I'm excited to see how it goes.
Well it flashed and well... seems to be having a strange issue.
When switching screens, it seems to glitch out? Like you see the icons, and when you switch screens, it's like the icons move but it freezes different frames. imma re-flash it in the morning to see if that helps any.
Click to expand...
Click to collapse
Im outta suggestions, I think you might have a hardware problem, but can't be for sure on that.
I've never heard of anybody having that problem, let me know if you get the issue resolved
Sent from my LG-P509 using xda premium
could defiantly be, this phone is well over a year old and has been dropped quite a number of times lol.
XCmaster said:
could defiantly be, this phone is well over a year old and has been dropped quite a number of times lol.
Click to expand...
Click to collapse
Was your phone acting like that before you flashed openzio?
Sent from my LG-P509 using Tapatalk 2
Nope, I've never had these issues before. And I can still flash it back to my original boot.img and it works like before. I've never had any problems with it, so that's why I'm surprised this is happening lol
XCmaster said:
Nope, I've never had these issues before. And I can still flash it back to my original boot.img and it works like before. I've never had any problems with it, so that's why I'm surprised this is happening lol
Click to expand...
Click to collapse
I guess then its probably not a hardware issue.. hmm.. its almost Like the roms your flashing are getting corrupted some how.
Sent from my LG-P509 using Tapatalk 2
hmm.. .well maybe I'll format my sd and do a factory reset on the phone first, then try to flash the rom?