Related
Yes, we're all noobs!!!
I have a brand new Excalibur (I bricked my first one five mins. out of the box) and I attempt to upgrade following instructions on the tutorial posted on these forums.
What's not stated on said tutorial (and no one tells you, only after you bricked your phone) is that YOU MUST BACK UP YOUR ORIGINAL ROM before the upgrade, because if anything goes wrong, that is the only ROM you can flash to your phone to restore it, otherwise IT IS BRICKED. (Believe me, it happened to me).
So, to all you experts reading these, please, help us noobs and post here a complete guide on how to back up your original ROM.
We will thank and worship you forever!!!
These days, there is no need to backup your own Rom.
We have a collection of ROMs on this site alone. Or in my signature.
I do suggest to download one prior to updating your ROM.
This forum uses most of a collection of ROM i have uploaded for everyone.
Click here for the forum of original ROMS
Mikey1022 said:
These days, there is no need to backup your own Rom.
We have a collection of ROMs on this site alone. Or in my signature.
I do suggest to download one prior to updating your ROM.
This forum uses most of a collection of ROM i have uploaded for everyone.
Click here for the forum of original ROMS
Click to expand...
Click to collapse
I have two questions: Firstly, there is no official O2 Xda Cosmo ROM or? Secondly, if you back up the ROM first, how can you flash it back to the device? Is there a tutorial for this?
Thanks
READ this thread
uccellino said:
I have two questions: Firstly, there is no official O2 Xda Cosmo ROM or? Secondly, if you back up the ROM first, how can you flash it back to the device? Is there a tutorial for this?
Thanks
Click to expand...
Click to collapse
yeah i'm waiting for the official O2 Xda cosmo ROM. i need it badly because my camera doesn't work anymore with new ROM. and i am totally agree to write a clear reminder to backup your original ROM first before upgrading in the upgrading ROM thread. just in case for noob like me....
Mikey1022 said:
READ this thread
Click to expand...
Click to collapse
After rereading, I still have the questions:
1. How is it possible to flash back a saved backup ROM image?
2. If I use a USPL and then something goes wrong while flashing a cooked ROM, can I only re-flash my original ROM (i.e. for XDA Cosmo which doesn't exist)?
Thanks
Okay - maybe I just figured out the answer to my own question: if I flash the USPL-RUU first before flashing a ROM update, maybe this means I can reflash if something goes wrong? Is this correct, or is there a chance that the SPL get overwritten before the error and I still get stuck?
Well, in fact, it is necessary...
Mikey1022 said:
These days, there is no need to backup your own Rom.
We have a collection of ROMs on this site alone. Or in my signature.
I do suggest to download one prior to updating your ROM.
This forum uses most of a collection of ROM i have uploaded for everyone.
Click here for the forum of original ROMS
Click to expand...
Click to collapse
...When I mean original ROM, I mean the ROM that could only work on a CID-Locked-by-a-carrier Excalibur, not the HTC WW ROM release.
Also, many of us noobs are international, I doubt that on the ROM database on this website we'll be able to find, say, the Movistar Mexico HTC Excalibur WM5 1.15.0000 ROM, which in my case, is the only one I would be able to flash in case anything goes wrong on the upgrade attempt. (I dedicated a week searching this ROM for the first Excalibur I bricked, no results)
Therefore - and I really hate to contradict -, for many of us, a ROM backup IS necessary and a tutorial from you experts on how to do it would be a great, great contribution to this community. (And also to the database, 'cause I'll definitively upload my ROM once I back it up)
velascoperroni said:
...When I mean original ROM, I mean the ROM that could only work on a CID-Locked-by-a-carrier Excalibur, not the HTC WW ROM release.
Also, many of us noobs are international, I doubt that on the ROM database on this website we'll be able to find, say, the Movistar Mexico HTC Excalibur WM5 1.15.0000 ROM, which in my case, is the only one I would be able to flash in case anything goes wrong on the upgrade attempt. (I dedicated a week searching this ROM for the first Excalibur I bricked, no results)
Therefore - and I really hate to contradict -, for many of us, a ROM backup IS necessary and a tutorial from you experts on how to do it would be a great, great contribution to this community. (And also to the database, 'cause I'll definitively upload my ROM once I back it up)
Click to expand...
Click to collapse
Actually, it's quite easy to CID unlock your phone to load whatever ROM you want. Much easier in fact, than dumping your current ROM and restoring it. I was able to flash my first ROM within about 30 minutes of reading on this forum, and had no problems at all.
velascoperroni said:
...When I mean original ROM, I mean the ROM that could only work on a CID-Locked-by-a-carrier Excalibur, not the HTC WW ROM release.
Also, many of us noobs are international, I doubt that on the ROM database on this website we'll be able to find, say, the Movistar Mexico HTC Excalibur WM5 1.15.0000 ROM, which in my case, is the only one I would be able to flash in case anything goes wrong on the upgrade attempt. (I dedicated a week searching this ROM for the first Excalibur I bricked, no results)
Therefore - and I really hate to contradict -, for many of us, a ROM backup IS necessary and a tutorial from you experts on how to do it would be a great, great contribution to this community. (And also to the database, 'cause I'll definitively upload my ROM once I back it up)
Click to expand...
Click to collapse
I completely agree with you
I just have no idea how to restore a backed-up ROM and I haven't read anything saying how to do it either. As you say, many of us a stuck with devices CID locked to some international ROM that is impossible to get.
So once again the question: Does anyone know how to re-flash a backed-up ROM?
I'm no expert but all I'm going to say is this. If you have a Rom from a different carrier that has not leaked to the public, then you are probably out of luck. You take the risk of hoping your phone will not have serious problems down the line of your contract or usage. You should pick up insurance on your phone depending on the stipulations your carrier has about lost or stolen or even broken phones. In that case you could return/replace your phone if need be after modifying it to your liking. I also would suggest that the entire reason we are here is that we don't want to be like the norm. We want what we paid for and don't want to be restricted. It's a risk. You must make that choice and succeed or fail that's not anyone's problem but your own. With all the Roms out there you should find one to your liking. If you brick your phone which seems so much more difficult than my razr modding days, than sell it for parts and lesson learned.
In the U.S. the Open Headset Alliance is our future so what we do to our phones in the future will be our choice.
Good Modding
Pfunk
C'mon guys...
Wy all the negativity?
I'm I conspiring against copyright laws if I want to have a backup of the ROM I paid for?
Is backing up a ROM frowned upon on this community? or is it so easy (from what I can gather it requires "dumping" and "restoring") that it is even insulting for me to ask you how to do it?
Yes, we are all here because we don't conform to the norm, but we are all HERE to help each other out. Why the closure? Why the elitism?
Like all of you, I want to take full advantage of the piece of technology I acquired without the restrictions installed on them by the phone corps. Yes, I would like to have the minimum risks while doing so, and yes, I would like to do it as cost effective as I can, just as anyone of you would.
It is a risk to upgrade a Cid.Locked phone with the bypass provided on this website, It happened to me and to many: USB cord unplugs and voila, bricked phone.
One alternative is to pay $40 bucks for a permanent Cid.Unlock, which will allow you to flash and flash and flash, even if you get stuck in the middle of one process.
The other, used by many here who wont pay, is to use the Cid bypass, while having a backup original rom "just in case".
What I only ask (for myself and my peer noobs) is to have this same other alternative as many, many of you.
Really, is it to hard to post the following?
1. Downoad these softwares;
2. Do this to "dump";
3. Do that to "restore";
4. To re-flash, do this.
C'mon, all for one and one for all right?
p.s. For my friend asking how to re-flash a backed up ROM, from what I've gathered, it goes something like this: your backed up ROM must be in a *.bn format (I still don't know how to even achieve this); then you must get a hold of any HTC RUU Software, extract it (Winrar) and replace the *.bn file inside the extracted folder with your *.bn file; with the HTC connected in bootloader mode, run the exe file in the extracted folder.
velascoperroni said:
...I doubt that on the ROM database on this website we'll be able to find, say, the Movistar Mexico HTC Excalibur WM5 1.15.0000 ROM, which in my case, is the only one I would be able to flash in case anything goes wrong on the upgrade attempt. (I dedicated a week searching this ROM for the first Excalibur I bricked, no results)
Therefore - and I really hate to contradict -, for many of us, a ROM backup IS necessary and a tutorial from you experts on how to do it would be a great, great contribution to this community. (And also to the database, 'cause I'll definitively upload my ROM once I back it up)
Click to expand...
Click to collapse
The Official ROMs collection is as full as I can make it. To have more images, we need everyone to upload ones that are missing to something like rapidshare, mediafire, or one of a few dozen other hosting sites, then tell up here on xda dev. Or upload it to several yourself. Spreading things on the net is much easier than ripping the ROM out anyway, and you benefit from the online backups, too.
So, yes, if you aren't going to back up your ROM, hope that someone else already has. Or, even better, be that first guy who does it, to make things easier for the rest of us. Besides, we might want to see what kinda goodies are tucked in the Movistar version
Indeed!
Profezza said:
...Or, even better, be that first guy who does it, to make things easier for the rest of us. Besides, we might want to see what kinda goodies are tucked in the Movistar version
Click to expand...
Click to collapse
Thanks for the support Profezza, indeed I intend to be the first, but in order to do that, I need to know how to do it.
I'll keep my hopes up for someone to post here the procedure for backing up my own ROM.
Also, the Movistar version is pretty lame, at least it would be a language addition to the database since it is originally in Spanish.
velascoperroni said:
Thanks for the support Profezza, indeed I intend to be the first, but in order to do that, I need to know how to do it.
I'll keep my hopes up for someone to post here the procedure for backing up my own ROM.
Click to expand...
Click to collapse
My post kinda ignored that point, as... I don't actually know how it is done.
velascoperroni said:
Also, the Movistar version is pretty lame, at least it would be a language addition to the database since it is originally in Spanish.
Click to expand...
Click to collapse
I think the version # system is controlled by HTC and fairly consistent across brandings, so it looks like it is a rather old one, but yeah, it could handy just for the Spanish. And ya never know, maybe a better graphic or two in some odd corner. I'll come back and bump this if it looks like it is fading away.
velascoperroni said:
p.s. For my friend asking how to re-flash a backed up ROM, from what I've gathered, it goes something like this: your backed up ROM must be in a *.bn format (I still don't know how to even achieve this); then you must get a hold of any HTC RUU Software, extract it (Winrar) and replace the *.bn file inside the extracted folder with your *.bn file; with the HTC connected in bootloader mode, run the exe file in the extracted folder.
Click to expand...
Click to collapse
Hi velascoperroni!
Thank you for your help - this is helping me to get closer to understanding
Basically I have my old ROM image as .img files (actually 5 of them) produced by bkondisk, together with a log file saying what goes where. So now all we need to figure out is how to turn these back into a .bn file and we'll be in business. For info on bkondisk, which lets you save your ROM (as .img files), see this wiki http://wiki.xda-developers.com/index.php?pagename=bkondisk
Could anyone point me to some resources on these two file formats? Then maybe we could come up with a conversion program when one doesnt exist
Getting closer!
Great, it seems we are getting closer to our goal!!!
But still surprises me that no one has posted a complete how to... perhaps the only few who know the deal haven't read this thread yet.
Now we know the following:
1. Bkondisk: software that allows to backup ROM in *.img format.
2. The original format of the ROM is *.bn
We don't know if the *.img file needs to be converted to *.bn or if they are compatible.
I also found out about an easier method to re-flash the ROM:
1. Format your SD Card in FAT32;
2. Copy your *.bn file to your SD Card;
3. Turn off phone, insert SD Card, Turn on phone in bootloader mode;
4. The phone should automatically recognize the ROM and start the flashing process.
Uccelino: Try placing the *.img file in the SD Card instead of the *.bn file. Maybe, just maybe the phone also recognizes *img files!
Getting closer!
Great, it seems we are getting closer to our goal!!!
But still surprises me that no one has posted a complete how to... perhaps the only few who know the deal haven't read this thread yet.
Now we know the following:
1. Bkondisk: software that allows to backup ROM in *.img format.
2. The original format of the ROM is *.bn
We don't know if the *.img file needs to be converted to *.bn or if they are compatible.
I also found out about an easier method to re-flash the ROM:
1. Format your SD Card in FAT32;
2. Copy your *.bin file to your SD Card;
3. Turn off phone, insert SD Card, Turn on phone in bootloader mode.
4. The phone should automatically recognize the ROM and start the flashing process.
Uccelino: Try placing the *.img file in the SD Card instead of the *.bin file. Maybe, just maybe the phone also recognizes *img files!
Also...
Sorry for the double post back there!!
Also check out this thread I started when I bricked my first Excalibur:
http://forum.xda-developers.com/showthread.php?t=378050
I never got a feasible response to wether sprite backup would work or not, and I did not want to spend $30 bucks to find out.
velascoperroni said:
Great, it seems we are getting closer to our goal!!!
But still surprises me that no one has posted a complete how to... perhaps the only few who know the deal haven't read this thread yet.
Now we know the following:
1. Bkondisk: software that allows to backup ROM in *.img format.
2. The original format of the ROM is *.bn
We don't know if the *.img file needs to be converted to *.bn or if they are compatible.
I also found out about an easier method to re-flash the ROM:
1. Format your SD Card in FAT32;
2. Copy your *.bin file to your SD Card;
3. Turn off phone, insert SD Card, Turn on phone in bootloader mode.
4. The phone should automatically recognize the ROM and start the flashing process.
Uccelino: Try placing the *.img file in the SD Card instead of the *.bin file. Maybe, just maybe the phone also recognizes *img files!
Click to expand...
Click to collapse
I just had an idea: I will flash a ROM, back it up, and compare the *.bn files to the *.img files I get from backing up - maybe they are or are almost the same, and we can convert them
I will try. Thanks
I just bought an HTC Tilt on eBay. I am pretty sure that the previous owner flashed the original ROM, the info I can find is listed below. I don't use much data, I am interested in running android on the phone. If I read other posts correctly, I have to run android on top of windows. I would prefer to hard flash the ROM if possible but if not, no problem. I have HardSPL and CidUnlocker from the "Flashing Your First Kaiser Rom" post by mskip.
I am looking essentially for a decent android OS I can play around with.
If I can hard flash the ROM I take it I will need to flash a new radio also is that right? Do I need a new radio if I just soft flash?
Any help you can provide will be appreciated
Phone boots with the following:
R-1.65.21.18
G-25.88.40.05H
D-3.TPCElite
ROM version: AthineOS WWE
ROM date: 04/30/09
Radio version: 1.65.21.18
protocol version: 25.88.40.05H
Model No.: Kaiser
Platform: PocketPC
Windows Mobile 6.5 Professional
CE OS 5.2.23016 (Build 23016.5.3.0)
A TPC ROM
Device name: HTC_TyTN_II
No, your phone is not running stock...it's running a custom ROM as should be obvious by TPCElite and AthineOS.
Android DOES NOT RUN ON TOP OF/INSIDE/NEXT TO WINDOWS. It is completely seperate and native.
You can run off of SD card or off of the internal NAND (replaced Windows Mobile).
Do a bit of reading on this thread (there's a link to a great instruction guide). This is by far the newest/best Android I've ever used.
http://forum.xda-developers.com/showthread.php?t=600154
Look at this thread:
http://forum.xda-developers.com/showthread.php?t=643504
Since you are allready running custom you propably allready have a HardSPL installed. Hold down Camera button and reset (pen in small hole near USB connection) to see what HardSPL version you have installed.
You may be better of with a new Radio. I'm using the same version as the author of the polymod 2.1g install.
Then you may want to do the Haret install first just to figure out which panel type you have. However if you flash the wrong one you could just enter the SPL screen with the procedure describe above and reflash until you get one that works so you don't have to go the Haret route unless you really want to.
There is a noticable difference in speed with a NAND install and it also speeds up booting as you do not have to boot Windows Mobile first.
Thanks
Sorry I haven't gotten back sooner, busy working. Thanks for the info. I was wondering if there was a way to check for HardSPL. I'll try out your suggestions soon.
You missed it. Here:
kallt_kaffe said:
Since you are allready running custom you propably allready have a HardSPL installed. Hold down Camera button and reset (pen in small hole near USB connection) to see what HardSPL version you have installed.
Click to expand...
Click to collapse
chambo622 said:
Do a bit of reading on this thread (there's a link to a great instruction guide). This is by far the newest/best Android I've ever used.
http://forum.xda-developers.com/showthread.php?t=600154
Click to expand...
Click to collapse
That build runs real slow for me. I've only launched it from a class four SD card though. Is the NAND much faster? (I can't NAND yet as I need some features not available in this build yet)
deekjx said:
That build runs real slow for me. I've only launched it from a class four SD card though. Is the NAND much faster? (I can't NAND yet as I need some features not available in this build yet)
Click to expand...
Click to collapse
Well, it will run slower on SD-card based installations, if you are running through HaRET, than on NAND-based installations.
You could actually NAND flash your phone and try this out to see if it works out for you and see if the speed suits your needs. You always have the option to go back to WinMo by flashing it back.
Well its self explanitory. I was thinking about putting using WinMo with haret to have more up time for my phone while im testing but I didn't see any good guides with an initial search.
Did you try this?
I will now, thanks for the guide. Perhaps you could put it in your kernel thread?
Edit: Is there any way to see how much of the NAND winmo is using that way I can make my SYS partition as large as possible?
it doesn't make any sense because you can't have windows and android both on nand
Ah ok, I was assuming you could partition the NAND to work like that. No matter I have a class 6 sd anyways.
hey guys
I've been looking for an answer for this question for 5 hours but wasn't able to understand what the next step should be.
My Story (not necessary)
I've successfully rooted my HTC Desire (which was a pain because I had to downgrade my phone first and root it with unrevoked on Ubuntu 10.04). I thought the latest version would be supported, actually it didn't change anything! (well it's rooted now after all...)
I was looking for the best method to update the Desire without loosing root. After hours spent on google looking for an answer
I wanted to know:
The best method to update an HTC Desire without loosing root. As far as I understand gingerbread was the 2.3 release and Froyo all the earlier releases.
Where do I get it?
How do I install it?
thanks in advance!!
ps: All methods from 2009 and 2010 wouldn't work for me.
my specs:
Firmware Version: 2.1-update1
Baseband Version: 32.41.00.32U_4.08.00.09
Kernel Version: 2.6.29-0cfb9f166
[email protected] #1
Build number: 1.21.405.2 CL174215 release-keys
Software number: 1.21.405.2
Update using a custom ROM (see http://forum.xda-developers.com/forumdisplay.php?f=628 for all the threads containing these ROMs, and a how to). I use sebastiaan15's Runnymede AIO which is a Gingerbread with HTC Sense 3.5 ROM (http://forum.xda-developers.com/showthread.php?t=1315961) but there are plenty of others on there, depending on what you want. You will keep root, as the Custom ROM will be rooted.
thanks for your quick answer! it really helped me getting a good overview!
still I have one more question:
that means that every custom rom is rooted?
thethodi said:
thanks for your quick answer! it really helped me getting a good overview!
still I have one more question:
that means that every custom rom is rooted?
Click to expand...
Click to collapse
Yes, they are rooted.
thethodi said:
thanks for your quick answer! it really helped me getting a good overview!
still I have one more question:
that means that every custom rom is rooted?
Click to expand...
Click to collapse
I suppose technically it would be possible for a Custom ROM to not be rooted, but there aren't any that I am aware of, or have ever installed, and I can't see why a dev would produce a non-rooted ROM.
I'd recommend 4ext recovery (install it via the market), so you can take a full ROM backup. That way if you don't like a Custom ROM that you flash, you can just revert back to exactly where you were beforehand. Even if the new ROM won't boot, you can just boot into recovery and restore.
Also, a good idea to use Titanium to do a backup, so that you can then restore your user apps when you're on your new ROM. DON'T restore system when swapping from one ROM to another, or it may very well mess up your new ROM.
Hope that helps. I went through all this, and had all these sorts of questions a couple of months ago, so happy to help you work through it.
beardymarrow said:
I suppose technically it would be possible for a Custom ROM to not be rooted, but there aren't any that I am aware of, or have ever installed, and I can't see why a dev would produce a non-rooted ROM.
I'd recommend 4ext recovery (install it via the market), so you can take a full ROM backup. That way if you don't like a Custom ROM that you flash, you can just revert back to exactly where you were beforehand. Even if the new ROM won't boot, you can just boot into recovery and restore.
Also, a good idea to use Titanium to do a backup, so that you can then restore your user apps when you're on your new ROM. DON'T restore system when swapping from one ROM to another, or it may very well mess up your new ROM.
Hope that helps. I went through all this, and had all these sorts of questions a couple of months ago, so happy to help you work through it.
Click to expand...
Click to collapse
wow thanks, when I first watched the introduction video I thought I wouldn't get that much and awesome help here
There is still a question bothering me:
Concerning SD formatting, there are some guides which say that it is possible to create "virtual ram" by adding a linux swap partition at the end of the sd card, is that actually true? or does that also depend on the rom?
does that really help? (I know that having an ext4,3,2,1 depends on the rom and is used for app2sd)
thanks so much for helping me guys!!
thethodi said:
wow thanks, when I first watched the introduction video I thought I wouldn't get that much and awesome help here
There is still a question bothering me:
Concerning SD formatting, there are some guides which say that it is possible to create "virtual ram" by adding a linux swap partition at the end of the sd card, is that actually true? or does that also depend on the rom?
does that really help? (I know that having an ext4,3,2,1 depends on the rom and is used for app2sd)
thanks so much for helping me guys!!
Click to expand...
Click to collapse
You need to have a swap partition with some ROMs (swap partition is not the same as ext partition!). Select ROMs you like the most and read the first posts really carefully. All usefull info are there! Once you have selected the ROM you want to install, prepare your card accordingly, flash the ROM and ENJOY!
thethodi said:
wow thanks, when I first watched the introduction video I thought I wouldn't get that much and awesome help here
There is still a question bothering me:
Concerning SD formatting, there are some guides which say that it is possible to create "virtual ram" by adding a linux swap partition at the end of the sd card, is that actually true? or does that also depend on the rom?
does that really help? (I know that having an ext4,3,2,1 depends on the rom and is used for app2sd)
thanks so much for helping me guys!!
Click to expand...
Click to collapse
Hi, I've not found I'd ever need any extra RAM, so I've never bothered with a ROM that needs it. In my humble and limited experience I've not seen any that need a swap partition. An ext partition on the other hand is very useful, as you can install more apps. My sdcard for all 4 ROMs that I often use (Seb15's Runnymede, CM7, Stock Froyo and ICS Beta) just has a 1Gb ext4 partition (for apps2sd) and the rest fat32.
Okay, silly question here:
(First of all, YES, I did a brief search through the forums for this exact question. Couldn't find an answer.)
Background: I am a ROM junkie (but a newbie, I admit). I have flashed and re-flashed EVERY ROM on this site (and others) on to my HTC Wildfire S (rooted, but S-ON). Soon, I will release a "report" with all of my findings, comparing each ROM against each other, etc.
With that, I am *quite comfortable* flashing ROMs and tweaking them afterwards. What I do not know is whether it's possible (after flashing a ROM) to subsequently go back an upgrade ONLY the Android version (from 2.3.3 to 2.3.5, for example).
I'm aware of the OTA updates that a "normal" user would be entitled to. But, with a customized ROM, it seems like I am exempt from those upgrades.
N.B.
If anyone replies: "Just find a modified ROM that runs the version of OS you need, and then flash that onto your phone!"... that is not an option (...unless it's the ONLY option!)
If you don't know, don't guess. (Sorry, but I've seen some of the "quality" answers that come back from certain users who are just trying to up their post count, I assume.)
Thanks in advance, to all those who answer.
- Anthony
It is not possible, because the system image (the OS) IS the rom. In fact, if you change anything in your system partition, you change the ROM.
there are no different memory locations for ROM and OS.
You could download an official rom that contains 2.3.5 here:http://forum.xda-developers.com/showthread.php?t=1074445
The rom is the os mate.
Thanks theq86,
So, to be clear, if I am running a custom ROM that happens to be GB 2.3.3, there is no way for me to apply a GB 2.3.5 "upgrade" (if such an animal exists)? The goal here is to leave the rest of the ROM (apk's, settings, internal data, etc.) intact.
Well... that's a tad disappointing, but thanks so much for your answer.
- Anthony
intel007 said:
You could download an official rom that contains 2.3.5 here:http://forum.xda-developers.com/showthread.php?t=1074445
The rom is the os mate.
Click to expand...
Click to collapse
Oh yeah? And do what with it?
(Go back and read my "N.B." from my original post.)
p.s. The ROM is not the OS. You're not the first person who's said this, though.
- Anthony
Tigger31337 said:
Thanks theq86,
So, to be clear, if I am running a custom ROM that happens to be GB 2.3.3, there is no way for me to apply a GB 2.3.5 "upgrade" (if such an animal exists)? The goal here is to leave the rest of the ROM (apk's, settings, internal data, etc.) intact.
Well... that's a tad disappointing, but thanks so much for your answer.
- Anthony
Click to expand...
Click to collapse
You can keep the apks and data(but not settings) if you don't wipe.But that can cause ptoblems on some roms.
Sent from my LG-P350 using XDA premium
Thanks nerot, that's kinda the path I was heading down myself (install, without wipe).
The only thing is that I don't wish to install a ROM over another ROM. I was hoping to somehow sneak just a GB upgrade (into an update.zip, let's say) and then flash that through the recovery menu. That way (in theory) the only thing that gets refreshed in my current ROM are the actual Android OS files.
[Hint: Think of the way you would perform an OS upgrade in the Windows world... one does not have to flash an entire Windows image over the existing one. One could simply upgrade the OS, while keeping applications and settings intact. ]
I see no reason, in principal, why this isn't possible with Android and, quite frankly, I'm surprised some clever XDA hacker hasn't done it already.
- Anthony
Tigger31337 said:
Thanks nerot, that's kinda the path I was heading down myself (install, without wipe).
The only thing is that I don't wish to install a ROM over another ROM. I was hoping to somehow sneak just a GB upgrade (into an update.zip, let's say) and then flash that through the recovery menu. That way (in theory) the only thing that gets refreshed in my current ROM are the actual Android OS files.
[Hint: Think of the way you would perform an OS upgrade in the Windows world... one does not have to flash an entire Windows image over the existing one. One could simply upgrade the OS, while keeping applications and settings intact. ]
I see no reason, in principal, why this isn't possible with Android and, quite frankly, I'm surprised some clever XDA hacker hasn't done it already. An one more thing if ypu don't wipe its like you flashed an upsate.zip but as i sai not wiping when switching between roms can cause problems.
- Anthony
Click to expand...
Click to collapse
I dont think it is possible to use a update.zip on custom roms because they are modified and even if it was possible i think it would be easier for the developer to just compile the whole rom again.
Sent from my LG-P350 using XDA premium
Tigger31337 said:
Thanks nerot, that's kinda the path I was heading down myself (install, without wipe).
The only thing is that I don't wish to install a ROM over another ROM. I was hoping to somehow sneak just a GB upgrade (into an update.zip, let's say) and then flash that through the recovery menu. That way (in theory) the only thing that gets refreshed in my current ROM are the actual Android OS files.
[Hint: Think of the way you would perform an OS upgrade in the Windows world... one does not have to flash an entire Windows image over the existing one. One could simply upgrade the OS, while keeping applications and settings intact. ]
I see no reason, in principal, why this isn't possible with Android and, quite frankly, I'm surprised some clever XDA hacker hasn't done it already.
- Anthony
Click to expand...
Click to collapse
nobody wants to bother, so find the updated version of the rom you wish to install, make titanium backup of your apps, and move on ..
b02 said:
nobody wants to bother, so find the updated version of the rom you wish to install, make titanium backup of your apps, and move on ..
Click to expand...
Click to collapse
Wow, what a very clever answer.
Keep in mind I'm not asking what YOU would do; I'm merely asking if something is technically possible.
While it would be nice to find "the updated version of my ROM", it does not exist (because it's a heavily customized version of an already heavily customized version.)
It's perfectly tweaked the way I like it (and yes, I've been backing up the ROM along the way)... so now, my question is (as before): is it POSSIBLE to overwrite ONLY the Android files, thus giving me a newer version of the OS?
Don't worry about whether or not it's something YOU would do... that's missing the point. And don't worry about whether or not certain apps would break after I perform the upgrade... that's my problem. (I suspect that going from 2.3.3 --> 2.3.5, or 2.3.5 --> 2.3.7 would not cause my phone to explode.)
Simply: is it POSSIBLE to perform an OS upgrade on an EXISTING ROM?!
I've heard one answer so far (of "No") but it seems like that was a "most people don't do this" or "it's not practical"-type of answer.
I'm looking for someone knowledgeable enough (because I'm not) to say whether or not it's technically possible. For me, I don't see why it wouldn't be. If someone can confirm it, then I'll get to work and try creating a flash package to get the job done.
Danke,
- Anthony
Tigger31337 said:
Simply: is it POSSIBLE to perform an OS upgrade on an EXISTING ROM?!
Click to expand...
Click to collapse
A custom ROM (Read Only Memory) as it is so often referred to, is the OS (Operating System) packaged to be flashed into the ROM, which can include the kernel, system, boot image and or other file like data, radio etc.. This is why it is loosely called a custom built ROM.
Yes, it is possible to JUST flash the upgraded files into the OS in the ROM.
The issues most have is when updating some main system files like the systemiu.apk or framework.jar is the /data/data setting files. If those file are not compatible with the newer files you flashed you will get a boot loop issue. I know this since I am modifying my own OS this way from time to time.
Now I am not a expert or a have advance knowledge but I know I what I have done, and the manufactures also do the same with their OTA(Over The Air) updates.
-Mark
The answer IS no.
The files of the rom are the same files of the os.
you can upgade the only the os, but ...
you will not able to start the upgraded os unless you wipe caches and data partition
So you need to:
- backup your apps
- backup your pim data
- upgrade the os (or ROM, whatever term you like more)
- recover pim data
- recover apps
- do the phone settings
having os upgraded and data not wiped is an inconsistent system state.
the only way to upgrade as you like is done by a FOTA update. From 2.33 to 2.35 all the settings and data were kept.
...and so we have a DIRECT contradiction:
One user says it CAN be done; one says it CAN'T.
theq86, although your answer is detailed, here is why I'm having a problem accepting it:
- First, you keep equating OS to ROM. A customized flashable ROM is more than the OS. For example, a ROM can be deodexed, overclocked, embedded with system apps, themed, tweaked, yadda yadda yadda. The OS is merely one component of a ROM package. Please stop equating the two.
- Second (as you already identified) it actually IS possible to do an OS-only upgrade because we are able to receive those types of upgrades today (in the form of OTA updates).
That's my difficulty. Surely, if my phone can handle a package that's designed to upgrade ONLY the OS (say, from 2.3.3 to 2.3.5) then it's just a matter of finding out how that upgrade is packaged and delivered (zip flash, update.zip, whatever) and then re-creating that process offline so that I can apply the upgrade manually.
Here's another description, so you get the picture: Imagine you absolutely LOVE a custom ROM called TiggerROM. It's the best thing you've ever seen in your entire life (you don't get out much) and it happens to be based on GB 2.3.3. Now imagine the author of your custom ROM gets hit by a bus and dies a horrible, twitching death. (There will be no more updates to TiggerROM, sadly). A week after his funeral service, GB 2.3.5 has been released. Your other friends (who have NOT modded their phone) are freely getting the 2.3.5 upgrade OTA, and it does not affect the rest of their phone (i.e. they do not have to re-install all their apps, they did not lose their wallpaper of their pet dog, they did not have to reconfigure their WiFi and Google accounts, etc.) Now, you are saying to yourself, "I want that too! I want to keep my current ROM+settings+tweaks and all I wish to do is upgrade Android from 2.3.3 to 2.3.5" (because you're just the kind of guy who likes to have the latest OS).
...so, what would YOU do?
- Anthony
Tigger31337 said:
...and so we have a DIRECT contradiction:
One user says it CAN be done; one says it CAN'T.
theq86, although your answer is detailed, here is why I'm having a problem accepting it:
- First, you keep equating OS to ROM. A customized flashable ROM is more than the OS. For example, a ROM can be deodexed, overclocked, embedded with system apps, themed, tweaked, yadda yadda yadda. The OS is merely one component of a ROM package. Please stop equating the two.
- Second (as you already identified) it actually IS possible to do an OS-only upgrade because we are able to receive those types of upgrades today (in the form of OTA updates).
That's my difficulty. Surely, if my phone can handle a package that's designed to upgrade ONLY the OS (say, from 2.3.3 to 2.3.5) then it's just a matter of finding out how that upgrade is packaged and delivered (zip flash, update.zip, whatever) and then re-creating that process offline so that I can apply the upgrade manually.
Here's another description, so you get the picture: Imagine you absolutely LOVE a custom ROM called TiggerROM. It's the best thing you've ever seen in your entire life (you don't get out much) and it happens to be based on GB 2.3.3. Now imagine the author of your custom ROM gets hit by a bus and dies a horrible, twitching death. (There will be no more updates to TiggerROM, sadly). A week after his funeral service, GB 2.3.5 has been released. Your other friends (who have NOT modded their phone) are freely getting the 2.3.5 upgrade OTA, and it does not affect the rest of their phone (i.e. they do not have to re-install all their apps, they did not lose their wallpaper of their pet dog, they did not have to reconfigure their WiFi and Google accounts, etc.) Now, you are saying to yourself, "I want that too! I want to keep my current ROM+settings+tweaks and all I wish to do is upgrade Android from 2.3.3 to 2.3.5" (because you're just the kind of guy who likes to have the latest OS).
...so, what would YOU do?
- Anthony
Click to expand...
Click to collapse
If you put it that way it is impossible to do that because you don't know what was edited in the custom rom and os compared to the stock ones it would cause instability an probably boot loop or the system not starting at all.Its almost like you want to upgrade from custom froyo to stock gingerbread using a ota.So the finnal answer is no.
Sent from my LG-P350 using XDA premium
And as for keeping all the other stuff i think that during the update it's all temporarily backuped somewhere(probably the sd card) and then restored.But i think it depends on the update itself for example there is no need to delete apps and google accounts for a Wi-Fi fix but it is necessary to do that when upgrading from froyo to gingerbread(unless my backup theory is correct)
Sent from my LG-P350 using XDA premium
you can not separate os and rom the way you do.
see, android is an OS that has a lot of dependencies. among these dependencies there are apks, themes and all the other stuff of the ROM.
it is sure possible to only upgrade the minimal dependencies that allow you to update your os and keep the rest (possible like: it's possible to fly)
the problem is: everything providers release are ROMs and no OS diffs. So what you want to do is very impractible.
no one does and want to struggle with those OS diffs. If you want to do, feel free. But you are the 1st one here.
so, yes it is possible, as it is possible to catch a fish with your hands. but the amount of work is much more than it it practicable.
Anyway, I got what you want. And the best thing you can do now:
- take a stock rom
- import it into a rom kitchen
- add your holy stuff
- cook your new rom and be careful not to be caught by a bus, because then the next one will arrive here crying that is favourite rom developer has died.
Try to only update the needed files would take you months of work just to find out what you can update.
nerot said:
If you put it that way it is impossible to do that because you don't know what was edited in the custom rom and os compared to the stock ones it would cause instability an probably boot loop or the system not starting at all.Its almost like you want to upgrade from custom froyo to stock gingerbread using a ota.So the finnal answer is no.
Click to expand...
Click to collapse
No, no, no.
In the examples I've been giving, I've always said that the change is minimally incremental (going from 2.3.3 --> 2.3.5, or 2.3.5 --> 2.3.7, for example). In theory, I'm sure you could go from Froyo to GB, but that's never an example I gave (nor something I'd want to do in real life). The bigger the version jump == the bigger the risk!
I am saying, (to repeat, yet again) that I would be working off a ROM that was GB 2.3.3 and then (somehow) apply a patch that would upgrade the bare minimum to get that Android up to 2.3.5. No other parts of the ROM would be touched. Whether or not **** breaks after the OS upgrade - well, that would have to be dealt with after the fact. I suspect not much would break, but that's not my question/concern right now. I'm saying can it be done TECHNICALLY. Is there a delivery method to apply an OS upgrade patch to a ROM. Don't worry about boot loops or broken apps... that's my problem, not yours.
And, if such an OS upgrade zip doesn't exist, then why not? Are they hard to make? Has anyone tried? Wouldn't such an update be HUGELY beneficial to the custom ROM community?
- Anthony
theq86 said:
you can not separate os and rom the way you do.
so, yes it is possible, as it is possible to catch a fish with your hands. but the amount of work is much more than it it practicable.
.
.
.
Try to only update the needed files would take you months of work just to find out what you can update.
Click to expand...
Click to collapse
Okay thanks. I think I'm getting the sense that it's just too much trouble than it's worth.
Thanks so much, everyone who replied.
I guess we are stuck in the hands of the ROM chefs (unless we take the time to learn to cook ROMs ourselves
Thanks again, take care!
- Anthony
Yes, it's technically possible. BUT you'll need to get whoever made the ROM you like to provide another ROM with the Android upgrade already in it. This may not be an insignificant task.
Nicknoxx said:
Yes, it's technically possible. BUT you'll need to get whoever made the ROM you like to provide another ROM with the Android upgrade already in it. This may not be an insignificant task.
Click to expand...
Click to collapse
Yes, but that's just another way of saying "you'll need to flash a new ROM" which is what we're trying to avoid here (because, by flashing new ROM, you'll lose everything - embedded apps, tweaks, themes, Link2SD data, etc.)
We're trying to keep our existing ROM and just change ONLY the Android version (from 2.3.3 to 2.3.5 for example, not a major version change).