I guess the question im asking is it possible to dual boot if it was devved up ??
I guess that would be a clockwork recovery option and partitioning scheme??
maybe im totally lost but it would be nice to dual boot instead of having to flash back and forth from your daily driver ROM to a experimental ROM that has bugs that need to be corrected and flashing back to your daily driver ROM
I like to toy around but once you get your everyday ROM tweaked in not much changes on it
Can someone give me insight on this maybe a break down of why it would or would not work
I know its a noob question but i would like to learn
Well I'm a n00b also and I found myself with backups I made with rom manager and I would hop back and forth between 2 or 3 setups I had. I found nothing wrong with booting into recovery to restore another rom I had then doing the same thing to a different rom the next day. It's probably a good idea to do it when you battery is at 100% though so you don't kill your battery stats.
yea but wouldnt it be cool to have three or even four booting slots pre setup when the devs really come around to where when you have the chance and time you could install this boot order 1=AOSP 2=MUUI 3=CM7 4=SENSE
and instead of flashing back and forth you could just select from boot menu and boot up to which ever flavor you feel like running that day
or maybe even a script that could run that could maybe flip through ROMS like flipping through themes and instead of rebooting it would just change boot images,system files, and apks in memory like a emulator then you could install one ROM and have the best of many devs work
LOL just thinking stupid stuff but is it possible ??? would love to hear Adrynalynes thoughts or some of these devs around here
LOL just tell me im stupid and it cant happen and ill move on
I am not a dev, but look up dual booting on the Nook color, and you can see that it is possible for Android system. Whether or not it can be done on the TB is another question.
The inc has dual booting. It's possible but will take some time. Only crazy talented devs such as r2doesinc can do stuff like this.
Sent from my thunderbolt
Yeah and the dual booting on the Inc was pretty recent. I had it basically since release and rooted about a week after root was available. Im pretty sure dual booting was just done within the past 2 months...
Related
I was wondering I'm looking to get into android development and I have a few questions that I was hoping someone could point me in the right direction?
I'm looking to make custom roms for the LG Phoenix P505 from scratch or use someones to learn how to? Tutorials or books or something would help, I'm not familiar with the code but I wanna learn so any help would be great, I'll be going into Computer Engineering Technology at a local college so I'm looking for a little head start in some areas.
I understand that a recovery menu or something around those guide lines is needed to use those custom roms? Is there one out for the P505 or is there a compatible one made from a previous rom?
I have the source code for the P505 its up on the LG open source website, can someone tell me what my next step would be?
url for LG Open Source: " lg.com/global/support/opensource/opensource.jsp"
I have the same phone but i cant find any support for recovery or roms! Can we get any help on that?
It would be nice, yeah... seeings how theres a fair amount of developers here,
even tellings us if someone is trying would be nice. I wouldn't mind
customizing my phone a bit more than what stock can do. So a shout
out to the developers, please let us know if anything is going on?
Or is everyone ditching this phone and going for the Thrive?
Any update on this?
I bought a Pheonix as my first android phone and would like to learn how to develop roms for it.
Unfortunately not that I know of, I haven't done any recent searching but yeah like you, the phoenix was my first phone too. Guess perhaps the devs don't wanna do anything for this phone?
Same here. There seems to be progress being made in this thread with the prepaid counterpart but this forum's pesky 10 post minimum doesn't allow me to post in that thread to glean some more information.
rom will be coming for this phone soon I'll make one. But how to you deodex a rom.
giandeli said:
rom will be coming for this phone soon I'll make one. But how to you deodex a rom.
Click to expand...
Click to collapse
you can deodex files using this kitchen:
http://forum.xda-developers.com/showthread.php?t=633246
instructions can be found here (i believe for your scenario you only need to do steps 3 and 5 and your ready to go):
http://forum.xda-developers.com/showthread.php?t=901417
Well, considering I already subscribed to this thread, I'll keep standing by.
yea giandeli we are all here by u! but please keep us updated! but shouldnt we first work on getting a kernel though n then a rom?
Well if its a modification of the original rom, can't you still use
the standard kernel? Or does it need some modification to it first?
i think the most important thing we need for ours is overclock cuz they are a bit slow but i think we need a kernel for that.
This guy is in agreement. Still waiting for something before I up and get another phone with support.
Well, its been two weeks. Is there any progress?
well it seems there is a rom made it isnt much but it is something heres a url:
forum.xda-developers.com/showthread.php?t=1215542
Sweet. Going to check it out when I get home.
however i dont see any instructions to flash it or use it as an update,
so if you have any pointers that'd be great.
I'm in the same boat dude. I've been doing a ton of reading just haven't had the time to act on any of it.
So i have an easy way to get clockworkmod recovery on, however heres my dellema, will and At&T rom work on a rogers phone if it is not unlocked? So is it pointless then for me to install the Carlos rom for phoenix?
** as a note,
A: backups are great
B: AT&T roms on rogers stay stuck at the AT&T logo in a loop of sorts
C: so that means i guess i need help in cooking a rogers rom for my Phoenix... (any pointers/help)
For those that are willing to give it a shot, i sort of had a P500
rom working perfectly, display wise, on a P505....
This is what i did:
1. Installed ClockWorkMod for optimus one through android
market app "Rom Manager"
2. Downloaded the final release of "Devoid"
url: forum.xda-developers.com/showthread.php?t=887281
3. ***MAKE A NANDROID BACKUP***
4. Wiped data, cache, and Dalvik, as well as battery stats
5. install from sd the "devoid" rom zip
Now theres 2 possible routes here....
1. Reboot now, you get the funky cyan messed up video screen
2.... Advanced restore in CWM of your boot partition...
the second route fixed the display, but upon boot, it said the battery
was over heating... and did a shutdown... i have yet to do a boot
up with ac power only, to see if that effects it.
**If anyone can point this at some devs, this may be a possible
work around for some roms?
The rom was a Froyo 2.2 and my boot was for a rooted 2.2.2,
what implications does this have?
So yeah thought i'd post my finding and if anyone knows anything
to add onto this, i don't have 10 posts yet, so I cant put this in
the develop area
***As an update
The "Devoid" Final rom was working full on the P505 from the method above
only if it was plugged in to a power source... It gave 2 errors,
1. When it was plugged in, it said "heat sensor detected high
temps, remove battery and place in cool dry place"
2. When not plugged in, "Battery overheateing, shutting down for safety"
I would like to work on my own ROM and I am starting to get the hang of moding the boot.img and stuff so I would like to start testing. I don't wish to run everything on my GTab all the time. Is there a way to get a custom ROM to run in an emulator? I have read a few threads on this, creating an AVD and swapping out the system.img, but I haven't gotten it to work. My guess is that it could be related to the kernel, but who knows. Anyone have any advice for this?
Honestly, the emulator is for testing App development and does a poor job even at that.
You'll need an actual device to do ROM development.
Most devs use their own device or have a second device to test their builds on.
Thanks T. Thats what I was afraid of.
When I built/compiled SnkBitten ROM for the Motorola Droid I know I locked up my phone hard plenty of times until I finally had everything working properly. Thank goodness for clockworkmod recovery and .sbf files for it. Have a nvflash ready to go if testing on your own device.
I eventually bought a second Droid to make things more convenient....but a phone is a bit more necessary to be functioning than a tablet too.....
Sent from my Viewsonic 10" GTab...GTabComb
OK, Heres the scenario, This is a replacement T-959 vibrant, sent from either TMO or Samsung, really not sure! My 1st phone never had any issues with modding, and always cooperated! Until I used KIES to update one day and It bricked, because of primary and SBL corruptions. [I know!!, found out 5 mins too late about using KIES] Anyway, since Ive had this replacement phone its done nothing but fight me from the start, never has acted right I think and I feel there's something wrong HW wise with it. My problem with it now, is it wont accept any other custom ROM I try to install, and only works with either 2.1 or 2.2 stock OEM ROM's. Meaning, Anything else ROM wise, It wont go past the last part of boot sequence, and just keeps looping, and does it over and over again! Ive tried all of Simple Honeys, Toxic 8's Roms, and each time it goes thru the loading successfully, and then starts it boot-up, but every single Flash Ive done, ROM wise, it hangs up and loops at the very last part of booting up. Ive come to realize now, it isn't the ROMS, but the phone " I THINK" Each time I tried a Custom ROM install, I started with stock fresh JFD install, and wiped and cleared out everything before starting another ROM install, but with each attempt that I try to go past anything other than Froyo stock, It does this boot loop problem at the final part!! It seems like who ever sent it to me, did something to the phone to prevent this. Modding it I mean. like right now I'm on Eugenes Froyo, with the 2E RECOVERY, It was working fine, until I upgraded the Eugenes kernel, which is suppose to work with this ROM, technically the phone still runs, but as soon as I did this, I now cant get into the two drives as mass storage to tranfer files, says insert disk, like as if its a CD Rom drive, WTF!! And like I said, this phone wont accept any other ROMS now, past stock Eclair or Froyo OEM and kernels as well. I don't understand what the problem is, My guess is they flashed something to prevent modding or its just a corrupted HW issue, anybody ever seen this before. I wish I had just JTAG'd my first phone with Josh over at Mobile Tech, and saved myself all this heartbreak and frustration, but its too late for that now! So anyway, I need to determine for sure if this phones screwed, HW wise or if there is SW to get this phone straighten out, to where it'll work right like my first one used to, and begin to accept custom ROM's like it should be able to do!! I'm at my last end with this phone, and I'm desperate to get a solid reason/answer for whats happening here, because Ive followed all the instructions and standard procedures to insure that all the attempted installs of the ROMS I mentioned go correctly. And its boiling down to either HW issues or a SW issue they created before they shipped it to me, or last but least hopefully a SW fix here, that can get the HW/phone to act right again, and maybe salvage this phone, otherwise I'm thinking I need to buy another brand new phone and hope for the best. I just don't want to be stuck and limited with Froyo stock, for the rest of my time using this phone, I want my freedom to choose again, like I had before, and also It ran so much better than OEM anyways!
Go back to stock using the sticky on the q&a then root using that same methOd and when you flash a custom room make sure you wipe dalvik and cache and delete user data
Sent from my SGH-T959 using XDA App
Quote" Go back to stock using the sticky on the q&a then root using that same methOd and when you flash a custom room make sure you wipe dalvik and cache and delete user data"
If you had picked up on it in my post, have already done this dozens of times!! Oh and BTW, when at JFD = 2.1 Eclair, it wont allow the 2 drives access to in Cabled USB mass storage, and therefore unable to CWM flash with zips, then I must go to 2.2 Froyo next to be able to get past that problem, but again when I go from there to any custom ROM, it fails to boot at the very end, and starts its looping. Again, the 1st phone I had, never ever, behaved like this!! Same phone but, different dates of manufacturing and also this one came from either Samsung or TMO in Plano,TX where that's all, they do is send out phones for replacement, and this one wasn't in a original box, something they worked on, grabbed off the shelf, and sent to me!! Its just a shame that 99% of all the ROMS are in zipped form, instead of TAR files, at least then I could've tried flashing some of them from, Eclair to see if that made a difference, but when they are zipped, you must use CWM recovery to flash, and thus again presents another problem as far as what I'm going thru here!
Got any thing else, Idea wise, that actually hasn't been tried yet, that makes sense??
OK, Ive made some progress, It seems for whatever stupid reason, that unlocking my phone, [jailbreaking] was the culprit of this phones renegade behavior, I simply restored it back to a locked status as a TMO provider, and Wholla, the phones now acting right!! And I have been able to get it to the ROM I wanted and flash a better kernel as well with 0 defects!!! And then I jailbroke it again, and its working flawlessly.
Personally I don't understand why that had a bearing on its behavior, but nun the less it did. And has cause me a few extra wrinkles around my eyes in stress trying to figure this out by myself, especially when all the suggestions and procedures I did was for nothing, until this phone was restored to a locked condition again!!
Go figure Right???? Grrrrrrrrrrrrr!!!! Anyway I hope mentioning this will prevent someone else in losing their hair or sanity!!
hello i think we have the problem, i also have openline my vibrant to be able to use here in our country.. i have 2.1 eclair, i just want to know what 2.2 ROM did you used coz you've said that it's ok to upgrade it to 2.2, but not other ROM, where did you get it.. can you pm me the link
thanks
I was running CM10 experimental (supposedly stable) build and was having way too many issues: reboots 5+ times a day, random freezes requiring hard reboot, etc etc. I tried uninstalling latest apps...nope. Tried fixing permissions...nope. Finally decided to reinstall the ROM. Used CWM wiped all 3 times, went to istall from zip, couldn't find the ROM anywhere. I installed an older ICS ROM I found in there and it did it's thing until it was time to boot up...now it's stuck in boot loop. I tried removing battery, turning off with both buttons, connecting to usb...not recognized. It just keeps going thru the booting process until it says "Have a nice day!" and then starts over. How do I get in to fix this? I'm screwed....and of course use my phone all day for business......sheesh. Are there ANY JB ROMs out there that are actually stable...like in real life?
Love this site, love all of you helpful folks....pulling my hair out at this point...;-(
You're kinda asking a lot since jb has to be ported over at the moment which naturally leads to glitches such as the restarts. This is the price you pay to run jb months and months before the note is officially updated. at which time the source code will be come available and we will have rock solid jellybean builds. Until then we take what we get. Run the latest release candidate of cm9 until then if you want something super stable.
Also don't you have a backup you can restore? I'm not allowed to feel sorry for you if you never backed up your device.
Sent from my SAMSUNG-SGH-I717 using xda premium
Thanks for the reply JR, your statement " jb has to be ported over at the moment which naturally leads to glitches such as the restarts" is Greek to me. Are you saying that since it is not an official JB update, there will always be glitches? um...ok.
Yes, I have a few backups in there...but as I said, it is stuck in opening boot loop and I don't know how to get in there to restore or flash another ROM. I may be missing a simple fix here but until I know what it is, I don't know what it is. I have used search under boot loop, for an hour and have not found one thread explaining how to get out of it.
Hopefully someone will excuse my ignorance and point me to a thread or explanation of how to get past the boot loop.
Cheers
do you know how to boot into recovery?
if you can, then do that, and restore one of your backups..
if you dont know how to boot into recovery, you shouldn't be flashing roms until you do
AFAIK that means pressing volume up, home, and power until recovery lights up. Done that many times and all I get is the intermittent vibe, no flash, no screen at all.
I've poured over threads and google all day...no love. Just people telling me to restore my backups...gee thanks.
I CAN get it into Odin....can I flash a ROM from there? I followed one tutorial but when selecting a ROM, it wanted a tar file and I either had the ROM zip or unzipped, a bunch of folders with no tar file in any of them.
I'm not a moron, just screwed myself somehow and am looking for some help fixing it. I thought that's what these forums were for.
hold volume up and down and power at the same time; after the first "samsung" on the screen, release the power button, and keep holding the volume up and down, until recovery appears...
XDA is a development forum, not a newbie forum, and there is an assumption that people who flash stuff to their phones will have the basic knowledge to know how to recover from some of the problems that arise when you do something to your phone that requires the knowledge on how to fix things
The fact that you dont know how to get into recovery properly tells me you didnt bother to read and study enough on how to recover from a problem if you have one, sort of like trying to replace your water pump without actually practicing on a car..
search the forums if you need to find .tar files to restore your phone via Odin back to stock; there are several posts and threads that will show you how, but, try to recover your back up first
This ^^^^^. You have jumped into the deep end without knowing how to swim. Watch videos, read how-to's and look up words if you don't understand them. A basic knowledge of computer hardware and how a computer works pre-boot will also go a long way
redman9 said:
Thanks for the reply JR, your statement " jb has to be ported over at the moment which naturally leads to glitches such as the restarts" is Greek to me. Are you saying that since it is not an official JB update, there will always be glitches? um...ok.
Click to expand...
Click to collapse
It means there is no official jelly bean for the note at this time. Our devs have to take jelly bean code and modify it to work on the note which generally means a few hickups here and there.
Sent from my SAMSUNG-SGH-I717 using xda premium
Well thank you all for the help you have given. I was not releasing the power button after the first Samsung flash and thus not finding recovery. I have a functioning phone now, at least. I do, dig deep trying to find answers, and only post when I am truly stuck.
glad you got it fixed!
Ok, so I'm going to start by saying that I am the furthest thing away from being an android noob, but this is my first Moto android device. I can see right away in terms of rom and kernel flashing it's a bit different than all the other android devices I've owned. I Picked up a RAZR for a really good price and it came loaded with Safestrap and had a 4.2.2 AOKP nightly loaded already on it. KI'm completely unfamiliar with bootstrap and how it works (I plan on reading up and learning everything today), but the guy that gave it to me said he accidently deleted the stock rom. To me, coming from all htc devices, I didn't think that was a big deal because who wants stock anyways? So, I'm not sure if it's critical to get that stock rom loaded back on in one of the slots or not.
I guess the point of this post is to see if anyone would care to share a couple helpful pointers for a first time moto user and hopefully make this learning process a bit easier.
Thanks to anyone who takes the time to reply with something other than "Read the stickies"
If you are happy with the AOKP, no need to install stock ROM. Stock ROM probably have less bugs, working 1080 camcoder, but lack options, that AOKP has.
localceleb said:
Ok, so I'm going to start by saying that I am the furthest thing away from being an android noob, but this is my first Moto android device. I can see right away in terms of rom and kernel flashing it's a bit different than all the other android devices I've owned. I Picked up a RAZR for a really good price and it came loaded with Safestrap and had a 4.2.2 AOKP nightly loaded already on it. KI'm completely unfamiliar with bootstrap and how it works (I plan on reading up and learning everything today), but the guy that gave it to me said he accidently deleted the stock rom. To me, coming from all htc devices, I didn't think that was a big deal because who wants stock anyways? So, I'm not sure if it's critical to get that stock rom loaded back on in one of the slots or not.
I guess the point of this post is to see if anyone would care to share a couple helpful pointers for a first time moto user and hopefully make this learning process a bit easier.
Thanks to anyone who takes the time to reply with something other than "Read the stickies"
Click to expand...
Click to collapse
Next time, make sure dont to delete the stock ROM, you can install other custom ROM on other ROM slots, make your stock rom as a backup if anything happens.
If you want to go back to stock ROM, or if your razr is bricked, i suggest you to download the fastboot file and flash the xml.zip you downloaded using RSD lite from the PC. Its just the same as 'Odin' if youre Samsung user. Download the fastboot file in the link given and also download rsd lite,you can google for it
http://sbf.droid-developers.org/umts_spyder/list.php
Sent from my GT-I9300 using xda app-developers app