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)
Hi guys!
Since two days I'm trying to create a ROM based on HTC Sense, porting from HTC Desire to our Nexus One using, as a base, the RCADSmixHD ROM.
I've been able to complete the entire package .zip and installing succesfully, BUT at reboot I'm stuck at the Nexus logo...
Do you think it's a kernel-related issue?
I really don't have any other ideas...
EDIT: I'd also like to know how to develop/modify a kernel for our Nexus One, but based on HTC roms... Someone has guides/links?
Try to Flash this Kernel: 2.6.35.6-eViL--10-7--1-wmcfg by eViL D:
You can find dl link here : http://forum.xda-developers.com/showpost.php?p=16995049&postcount=2
I had problems with the kernel include in RCADS on my N1
Thanks but no changes here... BTW the kernel included in RCADS rom works with my Nexus.. But here in this new ROM that I'm trying to develop I don't know what's wrong...
My guess there's something wrong with the ROM itself you probably have a few lines of code somewhere that are not working right. Were you able to compile the code on your computer?
Well, actually I'm trying to port a Sense ROM from HTC Desire with 250mb fit into /system/... I think that's the problem because my Nexus One could have bad blocks and/or less space into /system/, so this ROM wouldn't fit. I think so.
Regarding the code, I haven't written any kind of code, apart from looking at updater-script to be ok... Other suggestions? Thanks anyway, much appreciated
Now I'm trying to port a different ROM, the Desire S Gingerbread 2.3.5 with Sense 3.0!
But after replacing many folders and files from a Sense Rom of the Nexus One and the target Sense Rom that I'm developing, I have replaced boot.img and edited the updater-script properly (I think).
After installation, it's stuck at the Nexus logo... always!
What's wrong????????
Look at your logcat.
And at your /proc/kmsg.
If you don't know what these 2 mean - read up on those, use some googling.
If you can't - I believe you won't be able to develop anything worthy, or anything at all.
Moreover, Nexus has 145MB on /system partition. You need to utilize SD-EXT partition and symlink parts of the ROM to make it fit.
If I'm speaking Chinese and you can't figure it out - read the previous paragraph
From your posts I can't detrmine if you are developing or just trying to flash the rom to your phone, since you haven't done any coding. Am I misunderstanding?
rugmankc said:
From your posts I can't detrmine if you are developing or just trying to flash the rom to your phone, since you haven't done any coding. Am I misunderstanding?
Click to expand...
Click to collapse
You're right, because I'm not coding for a completely new ROM..
I'm just trying to "assemble" different pieces of ROMs together, a porting!
The only thing to "code" is the updater-script (or update-script)...
I have some errors there and I can't really determine why certain things goes wrong.. for now I don't have full knowledge of system partitions of Android.
And now I don't have enough time to fully explore this complex world
I have just tried for a couple of days...
Iperzampem0 said:
You're right, because I'm not coding for a completely new ROM..
I'm just trying to "assemble" different pieces of ROMs together, a porting!
The only thing to "code" is the updater-script (or update-script)...
I have some errors there and I can't really determine why certain things goes wrong.. for now I don't have full knowledge of system partitions of Android.
And now I don't have enough time to fully explore this complex world
I have just tried for a couple of days...
Click to expand...
Click to collapse
What did you add to the updater-script? And which folders specifically did you replace and change? And did you use a rooted ROM or the OTA one for the desire?
@Ace42:
Hi, I had used a rooted ROM from the Desire thread and I have followed this pretty useful guide which illustrates how to port Sense Roms:
http://forum.xda-developers.com/showthread.php?t=1222746
I have also had a look at almost all the files into each folders to see if there was differences in the code between the 2 roms..!
BTW the problem is in the updater-script...
For example I'm not able to mount "sd-ext", which is one of the most important steps to do for the Rom to being able to run into the device.
Look at that link properly, porting sense to OTHER SENSE DEVICES.
N1 isn't a sense device.
First, porting is more than replacing your boot.img and changing your update-script.
Like the other user said, you need to symlink files to your SD card cause N1 just isn't big enough.
Second, you're taking roms from other devices, most probably you'd have to re-write or mod the drivers.
Third, Porting just isn't that easy.
@illuminarias:
-> I know that, and in fact N1 becomes a Sense device when it has a Sense rom already installed... so it can be compared with other Sense devices.
-> I also know that we must symlink files, and you do that by adding lines of code into the updater-script (or update-script)!
-> If no one starts from something, how do you think that development for N1 can continue??
Iperzampem0 said:
@illuminarias:
-> I know that, and in fact N1 becomes a Sense device when it has a Sense rom already installed... so it can be compared with other Sense devices.
-> I also know that we must symlink files, and you do that by adding lines of code into the updater-script (or update-script)!
-> If no one starts from something, how do you think that development for N1 can continue??
Click to expand...
Click to collapse
The n1 also runs miui, is comparable to the m1? No.
Sent from my HTC Sensation Z710e using xda premium
illuminarias said:
The n1 also runs miui, is comparable to the m1? No.
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
I'm sorry but personally I love HTC Sense, not a-bad-copy-of-iPhone such as MIUI.
And since now I don't have money to change the device, I'll stick with this for other time.
Cheers
Iperzampem0 said:
I'm sorry but personally I love HTC Sense, not a-bad-copy-of-iPhone such as MIUI.
And since now I don't have money to change the device, I'll stick with this for other time.
Cheers
Click to expand...
Click to collapse
Yes, the same for me. I Love my nexus one with sense. Currently i also working on a gb sense rom for my nexus. Update Script is done and system should fit now with 151mb into the nexus rom. I ll will try to install & boot it at the weekend. Base was the currrent 2.3.3 Desire Release... Hopefully it fits into the small system and boots , to get logcats to work with...
If someone want to help & try, please contact me. I can upload the rom then to test. Currently i don´t have a lot of time , maybe together we get a working release...
@Deep-Knight:
Yep, I was working yesterday evening with the official Desire gingerbread update from HTC, but, as always, I'm stuck at the Nexus logo, after the installation is done... :/
I think I'm doing something wrong with system partition.. I know that our N1 can handle only 150mb for /system...
But I must admit that I'm using almost the same updater-script and boot.img as the N1Sensation v0.5 rom or RCADSmixHD rom..
Deep-Knight said:
Yes, the same for me. I Love my nexus one with sense. Currently i also working on a gb sense rom for my nexus. Update Script is done and system should fit now with 151mb into the nexus rom. I ll will try to install & boot it at the weekend. Base was the currrent 2.3.3 Desire Release... Hopefully it fits into the small system and boots , to get logcats to work with...
If someone want to help & try, please contact me. I can upload the rom then to test. Currently i don´t have a lot of time , maybe together we get a working release...
Click to expand...
Click to collapse
Just make a thread and upload your beta version, theres a plenty of people here able to test and help.
Thank you Menelkir for your interest!
But first I'll have to create something useful.. Maybe later on I'll create a new thread..
Till now I'm using some HTC Desire's ROM from the dedicated section here at XDA.
Stay tuned guys
As always graphical glithces will not be solved, until HTC releases Desire's Source Code..
The code is released already.
Unfortunately, the real trouble with porting ROMs is fixing the things that don't work - which will include trackball, hotspot etc - and this is the part where most of ROMs fail, because very few developers are skilled enough for that.
Please delete thread mod
SynysterSilence said:
Hello welcome to the first ever Synyster rom. This is going to be complete 100% dinc stock that i will create from a nandroid back up (im getting a refurbished one today) It will be posted tonight so if anyone wants to be alpha testers PM me or simply comment. Also, if you want to be a tester, i would rather you have a good understanding of rom development. This is so that if you run across a problem you could fix it for me since i know little about this. If you are able to fix something and do it succssfully i will update the post and give you credit for what you did.
Click to expand...
Click to collapse
nice name.
While I love your enthusiasm, Stock+ is a good stock ROM. There's also several other releases of the OTA on here. If you were to develop another stock ROM for this community, it really wouldn't be a very big contribution.
A community built ROM is kind of a cool idea though.
Sent from my ADR6300 using xda premium
yea but theres times when im looking for a pure stock rom for it and i can never find it. I love stock plus its great but i have 2 primary reasons for this: giving people a pure stock rom, and giving people a pure stock rom to use as a base. also i plan to do this for several other devices thatll be the point of the synyster stock rom series is to give different phones absolute stock if needed.
synisterwolf said:
nice name.
Click to expand...
Click to collapse
why thank you sir xD
Why build from a nandroid when the ruu and otas are available? That makes no sense to me personally.
Sent from my ADR6300 using XDA Premium App
SynysterSilence said:
yea but theres times when im looking for a pure stock rom for it and i can never find it. I love stock plus its great but i have 2 primary reasons for this: giving people a pure stock rom, and giving people a pure stock rom to use as a base. also i plan to do this for several other devices thatll be the point of the synyster stock rom series is to give different phones absolute stock if needed.
Click to expand...
Click to collapse
Might I suggest using the latest OTA? A nandroid backup isn't necessarily the best base for a rom.
If you do end up going the way of a nandroid backup, only use the system and boot images. The data and cache partitions will be created on first boot.
I would also suggest making a /data/app folder in your rom zip for bloat/market apps, so the user can uninstall them easier.
wdfowty said:
Might I suggest using the latest OTA? A nandroid backup isn't necessarily the best base for a rom.
If you do end up going the way of a nandroid backup, only use the system and boot images. The data and cache partitions will be created on first boot.
I would also suggest making a /data/app folder in your rom zip for bloat/market apps, so the user can uninstall them easier.
Click to expand...
Click to collapse
will do ill see what i can do if i have any troubles would you be able to help me out with it? ill give you full credit if you do.
blastthenoise said:
Why build from a nandroid when the ruu and otas are available? That makes no sense to me personally.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
cause im originally making this for normal use like any other rom im just allowing people to use it as a base if they so choose. also alot of people that are new to making roms dont know how to use otas or the ruu so using this would be a great way for them to start out
If you want a stock ROM just use the OTA.
Let me google that for you.
SynysterSilence said:
cause im originally making this for normal use like any other rom im just allowing people to use it as a base if they so choose. also alot of people that are new to making roms dont know how to use otas or the ruu so using this would be a great way for them to start out
Click to expand...
Click to collapse
If you are using the kitchen to build your ROMs you are better off using the rom.zip file found in the RUU or one of the other bases already posted on here. There are like 5 or them already. I personally would never use any ROM built off a nandroid even my own. That said I have made my own stock ROMs before using the kitchen and found its best to just use wildstangs gingerbread base which has been cleaned up removing all the Sprint stuff out of it. Saves the time of going in and editing the build.prop file yourself.
To extract the rom.zip file start the RUU and once at the first main screen click Start>Run and type %temp% now, find the newest folder and in there will be a ZIP file called Rom.
Wildstangs base:
http://forum.xda-developers.com/showthread.php?t=1247253
Sorry if this is a stupid question but my phone was running clockwork mod 5.0.2.0. However now looking at the dev forum a lot of Roms now need 4ext recovery. I'm a little confused as to what this is so would like it if someone could shed some light on the subject. Thanks
It gives you more features than CWM and I you can see/change the extentions. I believes our phones are 3 and 4 and some new roms only work on a certain ext hence why certain ppl have had issues (or so I've read in threads)
You can flash multiple zips and check md5 sums etc. The features are on here;
http://slideme.org/application/4ext-recovery-control
Or go to 4ext.net
One of the versions is also touch so your volume keys don't continue to get a battering. Tbh I've stayed with CWM as its going to be updated to touch sensitive and other features as well.
Sent from my Incredible S using xda premium
Does clockwork mod support 4ext?
I don't think so. I assume that's why you need to download 4ext recovery, otherwise surely its pointless the dev even making it if it offers no extra functionality?
Sent from my Incredible S using xda premium
Can you flash android revolution hd with clockwork mod 5.0.2.0? I haven't had my phone as it was being repaired and have I missed something as all the Roms now say you need ext4
incrediblealex said:
Can you flash android revolution hd with clockwork mod 5.0.2.0? I haven't had my phone as it was being repaired and have I missed something as all the Roms now say you need ext4
Click to expand...
Click to collapse
ARHD has always required 4EXT recovery. If the ROM's dev spells it out in his post, then you'd better follow his recommendation.
Thanks guys I will flash 4ext
Hey guys and gals,
Noob here, only installed 1 or 2 ROM's in the past, but I would now like a hand deciding on a suitable ROM for my needs on my Galaxy Tab P1000 (UK/European)
I would like a ROM that is nice and responsive, has good battery life and is fairly customisable, and I guess most come already rooted? I would prefer it to be ICS or JB too I have looked about and seen a few CM10 ones, some MIUI ones and various others but I am lost for choice, I have no idea what ones are best.
I want everything to work (all wireless connections, camera etc...) don't mind things like auto brightness or similar as that isn't major. The main reason for wanting to change from the stock gingerbread is because I find it unresponsive and boring.
Sorry if this is in the wrong section, thought Q&A was my best bet.
Thanks,
Cam.
Actually your best bet is to try them out yourself. All criteria are subjective.
Sent from my GT-P1000 using xda app-developers app
Ok matey, will have a play!
Thanks,
Cam.
Hey again,
Quick question,
For the MIUI v4 ICS ROM, which I like the look of alot, it needs a "restock" and install Overcome or a CM9 guide to be followed. (ROM link: http://forum.xda-developers.com/showthread.php?t=1613842 )
However, do I still need to do this as I haven't already installed any custom ROM? If I do can you give me a feint idea how I can approach it? Or can I just wipe cache/data etc.. and install the ROM?
Sorry if I am being a pain, not had to do any of this before.
Thanks,
Cam.
Many has your problem.
The thing is, newer ( well, post April 2012) ROM use new MTD layout, which need you to come from stock, or from same layout.
If your custom ROM were GB, no issue. They are stock BML partition, which the new rom can convert upon install.
If it were cm9 or 10, watch the mtd layout. The installer isn't made to convert older mtd to new mtd, so need restock.
Sent from my GT-P1000 using xda app-developers app
Ok so as I have no custom ROM at all I need to restock to new layout. No problem, just wanted to know if it was necessary for me to do it.
Thanks for your help,
Cam.
Sent from my GT-P1000 using Tapatalk 2
Think I have got it, can someone please confirm my steps to make sure I am doing it right?
1. Flash latest CWM recovery using Odin
2. Make Nandroid backup using CWM
3. Flash GB-stock-safe, then flash Overcome kernel 4.0.0.tar using Odin for both (do I do these separately or is there a way to flash them together?)
4. Place MIUI v4 ROM and GApps etc.. on Tab's SD card.
5. Boot into recovery, wipe cache, wipe data and flash ROM.
6. Flash GApps and patch's etc...
7. Reboot into ROM
If it doesn't reboot into MIUI I need to reflash the ROM as the first flash converted my Tab to MTD? Is that correct?
Hopefully I have got it,
Thanks in advance,
Cam
Actually, am I right in saying CWM isn't fully supported on P1000? What recovery should I use?
Sorry for all the questions again,
Cam.
Cwm is contained in kernel.
If you are willing to forgo backup, must start with GB stock safe v5
Then overcome kernel.
By then you have a cwm recovery.
Sent from my GT-P1000 using xda app-developers app
Got it all installed/flashed last night. Went all ok and I worked out that the kernel included overcome cwm after reading a guide from the link in your Sig.
I suppose its good that I love the ROM too
Thanks for the help, appreciate it.
Cam.
Sent from my HTC Desire S using Tapatalk 2