Hey guys,
i wanna know, why cm uses another path as default, for example:
Stock path: \sdcard0\
CM path: \sdcard0\0\
can i change it to default value?
I think it is because of the android version (stock is 4.1.2) not cyanogenmod itself. Irritated myself as well when I flashed custom roms first time but as far as I know there's no easy way to change the default path, but it's not that much of an effort to get used to the new one.
Sent from my LG-P880 using XDA Premium 4 mobile app
Sinve 4.2.2, new structure is used in order to support multiple users on the same device
Related
I love so much AOSP Roms for our Galaxy S I9000..I have done a nandroid back-up of Galnet MIUI v4 and Cyanogenmod 7..so if i want one of two roms i have to format system/data/cache/datadata from recovery and then restore the back-up..
My question is if is there a way to manage to do a dualboot between this two (or others) Roms..??
I think if it is possible it will be a great develoment for our Galaxy S..
Maybe i'm sayng a stupid thing but i want to read your opinions about this..
Cheers
i dont think its stupid at all, this would be a great feature! I have seen this in other android devices!
I've always wondered this too.
This was done on my previous device (HTC Hero) but it was a bit of a pain. The second Rom was installed on SDcard which was slow, and was FCing constantly, etc.
Whoever's interested can have a look at the HTC Hero forum section. It was ported by Kendon (he was part of VillainROM back then, don't know now).
Hope some developpers can do this ..
If it was possible on Htc Hero with less memory and less power it could be done also on Galaxy S I9000..
But Htc Hero is Htc and Galaxy S is Samsung so..i don't know..
I'm sure this week in dev I saw a trial program to do just this, running up to 4 roms! Will hunt down link if I can! Brb
Sent from my GT-I9000 using XDA Premium App
Where..??On I9000 Development section..??
Just checked back in dev,q & a and general, 10 pages back, so either it is buried deeper, or it was a total phone bricker and mods pulled it, will search some more
Sent from my GT-I9000 using XDA Premium App
slaphead20 said:
Just checked back in dev,q & a and general, 10 pages back, so either it is buried deeper, or it was a total phone bricker and mods pulled it, will search some more
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
saw that 2...it was for the evo if i recall ...
Cant find it anywhere, @silkydude....thanks for confirming, started to think I had lost the plot!
Sent from my GT-I9000 using XDA Premium App
Hi there,
Dual booting is kinda possible.
First one is to have very slims roms so you can install both on the nand and select one using a modded recovery.
Second one is to use redbend_ua script that will backup the current running rom, and then install another one and run it. The operation takes between 5 to 10 min depending on the rom and thats the only possibility to switch from 2.2.1 to 2.3 and vice-verca without having to flash bootloaders as redbend can flash bootloaders.
Also using redbend can be tricky as it can dump and write on partition but if it fail at flashing bootloaders you will be bricked.
Bricked phones can still be recovered using j-tag or 301k resitor.
Here is an attempt by z4ziggy:
http://z4ziggy.wordpress.com/2010/09/15/rom-flashing-using-redbend_ua/
The script in this page does not work but it can be improved.
You should check with him and some good dev like supercurio or codeworkx.
Also before applying any scripts, post it here and ask other people to see if it seems correct.
Happy flashing.
quick edit:
Be sure to dump the whole rom and restore the whole image even empty bml as it may have an importance.
We have to ask to developpers..
Not really, try to make a script that dump some bml, then try to restore them is it works then your good to go further.
Finally when you have a working script use tegrak kernel sources to include a "boot selection" as he did.
(on tegrak at phone boot you can enter recovery using the "home" button, change that to run the script so if you wait it boots normally, if you push "home" it dump the current rom and restore another one to boot on it)
Editing again:
If you use 2.2.1 bootloaders only, you can symlink an rom.img at boot and boot on it, it is easier but it is also pretty slow. (see nexus S rom port by supercurio)
Hey guys, I wanna start a new "little" project and hope for some help from the one or the other.
I just realized, that noone until now really compiled a stock ROM for our device.
That means, we can't get a fully customized ROM. I mean Zeus ROM is close to it, but it's pretty restriced, to the typical "tweaks" like kernel, theming and so on.
So I thought of trying to compile the sourcecode. It's still compiling, but if I already look at the build.prop, it looks like it's not building for our device, although I followed LG's advices that are:
Code:
How to build
1. Android build
(1) Get the android base source code.
- Download the original android source code (Android 2.3.4 gingerbread) from http://android.googlesource.com
(2) Overwrite modules that you want to build.
- Untar opensource packages of P970_BDop_GingerBread_v20s.tar.gz into downloaded android source directory
- And, merge the source into the android source code(gingerbread)
(3) Run the build scripts.
- You have to add google original prebuilt source(toolchain) before running build scripts.
- Run the following scripts to build android
$ ./build/envsetup.sh
$ make -j4
into the android folder
- If the android is built sucessfully, you will find the outputs in this directory,
"out/target/product/generic".
So far it looks and is pretty simple. But like I said, with the commands mentioned, I think it doesnt build for our device.
Had to bypass some errors, since I am using a more recent toolchains as LG seems to have used, but since goolge is my best friend, he told me what to do
Now how can we get this sourcecode compiled?
Do I have to start like rmcc did? And add these files/add the content he added?
https://github.com/CyanogenMod/andr...mmit/04b8b02f13c62239dad2884530ad07b9fe3ebd60
Dont wanna mess up my building environment and start over again, that's why I am asking.
When typing lunch, it only shows:
1. Emulator
2. crespo (I think)
3. some HTC device
4. one more
at least I cant pick p970.
Would be nice, if we could get that done, since it would probably also work for our hopefully soon coming ICS!
Then we could get a VEEERY good ROM for our already lil bit old device
Hope we can make it and I am sure we can
All recommendations are welcome.
About that, you need to setup the proprietary binaries for LGE to be able to setup P970 for lunch. Beside that, the prebuilt must be of the similar version.
Sent from my LG-P970 using Tapatalk 2
GB + LGE ROM sources = nothing...
You have to add p970 as available project for lunch... and you have to get all the proprietary files (right, from LG GB) and al the vendor blobs (from CM7)... but IMHO it would have the same problems as CM7... becuase CM7 is AOSP with some extra stuff...
Huexxx said:
GB + LGE ROM sources = nothing...
You have to add p970 as available project for lunch... and you have to get all the proprietary files (right, from LG GB) and al the vendor blobs (from CM7)... but IMHO it would have the same problems as CM7... becuase CM7 is AOSP with some extra stuff...
Click to expand...
Click to collapse
How about downloading and setting up cm7 for our device, maybe pull latest files from our phone, replace them, add lg s stuff and maybe some minor changes. Do you think, it would build cm or stock rom? Thanks for the input
Sent from my LG-P970 using xda app-developers app
N00BY0815 said:
How about downloading and setting up cm7 for our device, maybe pull latest files from our phone, replace them, add lg s stuff and maybe some minor changes. Do you think, it would build cm or stock rom? Thanks for the input
Sent from my LG-P970 using xda app-developers app
Click to expand...
Click to collapse
It would be CM7...
LG's ROM source code is close to nothing... only mods to non-proprietary stuff... there is NOTHING more. so CM7 sources + LG's source = CM7 source... CM7 has used LG's stuff for its project...
The way IMHO is:
- Take latest Gingerbread AOSP sources.
- Take a existent target (as Crespo) and duplicate all the needed stuff with a different name... as P970.
- Once you can build P970 (a Crespo ROM will be generated), modify all the stuff with vendor blobs from CM7 and proprietary files from LG's GB.
- A way to understand what you are doing is to take AOSP complete code... CM7 complete code, and compare the way both sources compile the same target, (Crespo...) to obtain the differences... Once you understand how change from AOSP to CM7 for Crespo, you will try to make the opposite from CM7 to AOSP for P970...
Regards.
have good luck
:fingers-crossed:
Good luck for your project...:good:
Hi all,
Would like to find out if it is possible to install android without the use of acmeinstaller, the reson for that is that i have a touchpad-go, which is basically 100% the same hardware, but uses a different name for kernel (shortloin instead of tenderloin) and probably some other naming differences. I think the acmeinstaller script refuses to continue due to not finding the right files or signatures, however I believe CM10 should work on it. Would appreciate some input on how to start
Check out the Kexec thread in the Other Development section, he's not done yet, but it sounds promising!
Sent from my slim_tenderloin using xda premium
Hey I'm new to customs ROMs and want to test the various roms available. I was wondering how I would properly switch from one rom to another without losing all of my data. I am using a HTC One running MoDaCo.Switch Beta 13.
SniperSquad said:
Hey I'm new to customs ROMs and want to test the various roms available. I was wondering how I would properly switch from one rom to another without losing all of my data. I am using a HTC One running MoDaCo.Switch Beta 13.
Click to expand...
Click to collapse
you would manually have to backup to computer and restore or use a program like ti backup (not recommended by me though, it seems some people had difficulty with it) or you could use a cloud service like dropbox to backup photos.
You can backup settings and apps downloaded using HTC Backup
Would I need to somehow remove my current ROM before flashing the new one?
Sent from my HTC One with MoDaCo.SWITCH Beta 13 using xda app-developers app
Yes. If you are flashing a new Rom, it's best to do full wipe first then flash. Each room has its own thread and on the first page, there is always information for the Roman as well as the flash instructions. Make sure you read every thing before flashing. Lastly, backup your rom in case anything may go wrong.
Sent from my Nexus 7 using Tapatalk 4
If you were to create a completely new os with new everything including the bootloader. coould you flash a phone compleatly and install your new os? Or would this be impossible?
If you adapt it to your phone then sure. Although it's difficult even to port new Android version to existing devices... There are examples of devices that can run more than one OS.
So, if you can make it, sure.
Sent from my SM-T230 using XDA Free mobile app