Hello,
I have a general noob question on the custom [ROM] threads.
Do custom ROM's posted go though an alpha, beta, official release stages? I see some [ROM] threads marked with an alpha or beta... while some others are not.
thanks!
U r right, alpha means something major is broken, beta its the "refinig" stage, and final its the complete rom
sent from the gray stuff inside my skull
demonoid phenomenom said:
U r right, alpha means something major is broken, beta its the "refinig" stage, and final its the complete rom
sent from the gray stuff inside my skull
Click to expand...
Click to collapse
Is this process that is true for all ROMs that are posted? I see a few ROMs that don't say alpha or beta. Does it mean they are release grade?
gcretro said:
Is this process that is true for all ROMs that are posted? I see a few ROMs that don't say alpha or beta. Does it mean they are release grade?
Click to expand...
Click to collapse
There is no such thing as release grade. Everything should be considered at least developmental in some form or fashion.
The terms of alpha and beta do not mean what most people think they do in here.
Even the ones marked alpha and beta can still be daily drivers, just take a look at the first post of each ROM you are thinking about and see if the bugs will "bug" you like for instance any of the CM based ROMs here have issues with camera and video and few other small bugs.
Any ROM based off of "stock" will have less/no bugs and therefore not marked as beta or alpha, since they are not compiled.
It all depends on your personal needs as to what you are comfortable with and if you can deal with certain things not working right out of the box, or that you might have to make a work around for.
I call mine "alpha" or "beta" depending on bugs and/or how much more work I expect to put into it... and my mood at the time
Jim explained it well... it's all subjective to the dev and the end-user..
Best to just make a good backup, know how to restore it, and slap a new ROM on your phone to try it out for yourself.
That being said, be on the lookout for a gamma version of Numa ... (j/k - it's been a long time since I was back on ICS)
Sent from my paranoid phone's mind
alteredlikeness said:
I call mine "alpha" or "beta" depending on bugs and/or how much more work I expect to put into it... and my mood at the time
Jim explained it well... it's all subjective to the dev and the end-user..
Best to just make a good backup, know how to restore it, and slap a new ROM on your phone to try it out for yourself.
That being said, be on the lookout for a gamma version of Numa ... (j/k - it's been a long time since I was back on ICS)
Sent from my paranoid phone's mind
Click to expand...
Click to collapse
Thanks.
Regarding making a good back up, Should I just follow the CWM thread? I found this link in the newbie thread. However, there was little explanation on it's use.
http://forum.xda-developers.com/showpost.php?p=19355021&postcount=1
- Does using the CWM recovery to create a back up have any per-requisites? Can I use it on my stock AT&T Atrix2 that is still on GB?
- If I understand correct, this is used to dump an entire image of the phone (firmware, OS, apps, files etc...) to an SD card? And one can later restore back from.
- I am planing flashing the NUMA Rom. If I take a back up using CWM, I assume I can restore everything to they way it was (i.e. back to GB) without risks?
thanks
gcretro said:
Thanks.
Regarding making a good back up, Should I just follow the CWM thread? I found this link in the newbie thread. However, there was little explanation on it's use.
http://forum.xda-developers.com/showpost.php?p=19355021&postcount=1
- Does using the CWM recovery to create a back up have any per-requisites? Can I use it on my stock AT&T Atrix2 that is still on GB?
- If I understand correct, this is used to dump an entire image of the phone (firmware, OS, apps, files etc...) to an SD card? And one can later restore back from.
- I am planing flashing the NUMA Rom. If I take a back up using CWM, I assume I can restore everything to they way it was (i.e. back to GB) without risks?
thanks
Click to expand...
Click to collapse
First, you need to get ICS on your phone if you want to flash Numa. You must be on 4.0.4 firmware to flash any of the ICS and/or JB based ROMs. The choice is yours on how to get there... please search thoroughly, as it has been covered an insane amount of times.
But, to try and answer your questions:
-Yes, the pre-requisites are that you need to be rooted, and have a custom recovery installed on your phone.. and an sdcard. You can do it on your rooted GB phone, but you cannot restore a GB backup while you are on ICS (for the only way to have the option to return to GB from ICS, you need to look here and here - but some will say there's no reason to go back to GB.. maybe nostalgia )
-A backup will backup your current system, data, and sometimes cache - and it will usually make a new folder, named by date, with a few .tar files inside of a "clockworkmod" folder on your sdcard. And yes, those are what you restore (when restoring, you choose the backup by date/folder name).
-No, you can not restore a GB backup from Numa (see above comments.. again) - also see here for a note on compatibly between different custom recovery options (might be easiest/safest to use BMM, I think you can flash all ROMs with that now..)
So if I understand all that correctly, here is my summary of steps to install Numa. Appreciate if you can correct my steps in-line if I am wrong. [Current state of my phone: Atrix2 on stock GB (AT&T). Only thing I have done is uninstalled/removed unwanted apps.]
Steps:
1. First get on ICS leak-1 following Jim thread. [OR OTA to the official/final ICS. But if I do this, I lose the option to return to GB? or will I loose that ability regardless since Numa itself is based on final ICS OTA?]
2. Install CWM A2 bootstrap recover from here.
http://forum.xda-developers.com/showpost.php?p=19355021&postcount=1
(No point taking a backup now I suppose since going back to GB isn't an option after Numa.)
3. Then follow the install instructions under the Numa Rom thread.
4. Once I have Numa up & running, I suppose I am limited to putting only those ICS/JB based roms that don't require me to be on leak-1?
On a side note, I hate how they have removed the "contacts" tab, "Only show contacts with phone number" option etc... from the Dialer app in ICS and replaced it with the People thingy . I like GB dialer. Also, In ICS they seem to have removed the data saver option that was available in GB.
Thx
gcretro said:
So if I understand all that correctly, here is my summary of steps to install Numa. Appreciate if you can correct my steps in-line if I am wrong. [Current state of my phone: Atrix2 on stock GB (AT&T). Only thing I have done is uninstalled/removed unwanted apps.]
Steps:
1. First get on ICS leak-1 following Jim thread. [OR OTA to the official/final ICS. But if I do this, I lose the option to return to GB? or will I loose that ability regardless since Numa itself is based on final ICS OTA?]
If you uninstalled any stock apps, the installation of the update will probably fail, and you will either need to fix your system by replacing everything (very carefully).. or just FXZ back to stock GB<--post is a bit out-dated. [Yes, if you ota to final ICS, you can not return to GB ever. It doesn't matter what the ROM you flash is based on, they basically only change your /system partition (and data) - the problem is the new bootloader in final ICS.
Make a full backup of your stock ICS if you want to go back to it (see below - probably best to use BMM to backup)
2. Install CWM A2 bootstrap recover from here.
http://forum.xda-developers.com/showpost.php?p=19355021&postcount=1
(No point taking a backup now I suppose since going back to GB isn't an option after Numa.)
You could use that, or BootMenu Manager (I heard that it works to flash roms now - it used to not - and I personally have not tested it recently.. so, not sure - and we also have Safestrap, but not sure of the status on that - still a wip, I think). Either way, you will loose it once you flash Numa... you will need to reinstall it to flash a different rom or make a backup (I recommend using BMM to make a backup since it's compatible with the CM10-based recovery, and since it is easy to uninstall)
3. Then follow the install instructions under the Numa Rom thread.
Yup.. maybe a bit outdated also, but wipe data/factory reset, dalvik-cache maybe, then install zip..
4. Once I have Numa up & running, I suppose I am limited to putting only those ICS/JB based roms that don't require me to be on leak-1?
You can put any ICS/JB rom available for our phone, if you wish - or restore the backup you made of stock ICS before installing Numa
On a side note, I hate how they have removed the "contacts" tab, "Only show contacts with phone number" option etc... from the Dialer app in ICS and replaced it with the People thingy . I like GB dialer. Also, In ICS they seem to have removed the data saver option that was available in GB.
There are other ways to get from dialer to contacts in ICS (underneath the favorites tab, scroll down.. or is that only jb?)
Thx
No prob. Good luck.
Click to expand...
Click to collapse
See in-line..
Related
Hi, I'm new to flashing ROM's and wanted to give this a try, but I had a few questions (I searched and read the wiki, but I didn't see these specific questions):
I have the Samsung Galaxy S2 Skyrocket on ATT. I'm rooted on Stock GB 2.3.6
1. I wanted to try flashing this ROM([ROM][CyanogenMod 9 (unofficial)][TeamChopsticks][Alpha 1 - 4/26]), Can I come from gingerbread if I follow the instructions in post 1? Or do I need to have an ICS leak installed first?
2. I assume I can revert back to my rooted-stock ROM by using CWM with my current restore point?
3. If I restore the backup from step-2, does it restore the original radio (the UCLA3 radio)? Or am I stuck with the new one? Any disadvantes to just leaving the new one installed?
4. When flashing the new radio, is it just like flashing a ROM in CWM?
5. How would I get all my apps back on the custom ROM? (I know the contacts are linked to the google cloud) I have titanium backup pro installed now, but I read something about not restoring the apps across different ROMs?
6. If I decide to go back to my stock ROM after looking at a few custom ROMs, would I be able to get the ATT OTA updates? (I know I'd need to un-root and un-freeze all the bloatware, but I assume installing the custom ROM's would trigger the flash counter?)
7. I keep hearing about the "yellow triangle" when the flash counter is triggered. Does it only happen at boot and go away after that? Or is it always there?
Thanks in advance!
skyrockets said:
Hi, I'm new to flashing ROM's and wanted to give this a try, but I had a few questions (I searched and read the wiki, but I didn't see these specific questions):
I have the Samsung Galaxy S2 Skyrocket on ATT. I'm rooted on Stock GB 2.3.6
1. I wanted to try flashing this ROM([ROM][CyanogenMod 9 (unofficial)][TeamChopsticks][Alpha 1 - 4/26]), Can I come from gingerbread if I follow the instructions in post 1? Or do I need to have an ICS leak installed first?
2. I assume I can revert back to my rooted-stock ROM by using CWM with my current restore point?
3. If I restore the backup from step-2, does it restore the original radio (the UCLA3 radio)? Or am I stuck with the new one? Any disadvantes to just leaving the new one installed?
4. When flashing the new radio, is it just like flashing a ROM in CWM?
5. How would I get all my apps back on the custom ROM? (I know the contacts are linked to the google cloud) I have titanium backup pro installed now, but I read something about not restoring the apps across different ROMs?
6. If I decide to go back to my stock ROM after looking at a few custom ROMs, would I be able to get the ATT OTA updates? (I know I'd need to un-root and un-freeze all the bloatware, but I assume installing the custom ROM's would trigger the flash counter?)
7. I keep hearing about the "yellow triangle" when the flash counter is triggered. Does it only happen at boot and go away after that? Or is it always there?
Thanks in advance!
Click to expand...
Click to collapse
1) if you're a newb I wouldn't recommend flashing alpha versions of anything
2)You can revert back
3)No, flash a ginger radio before restoring
4)Yes, wipe cache/dalvik cache
5)You can restore apps accross the same OS, but I never do
6)Yes, if you're on official software. It wont trigger unless you flash with odin or sometimes a custom kernel like cm will trigger it. No big deal, we have a counter reset.
7)only at boot, we have counter reset, so no worries
Wow, that was a quick reply! Thanks.
Sorry if I'm dense, I just wanted to clarify two things before proceeding.
Re 1: I also saw another ROM I wanted to try, I guess I'll do that one ([ROM]SKY ICS--- 4.2D-9). Thanks for the heads up.
Re 3: From your response, am I correct to understand I can't use an ICS radio with GB? (it just wont work? or there's no advantage to keeping it?)
Re 5: Same OS meaning inside GB based ROMs or ICS based ROMs? If I go from stock GB to custom ICS, I need to re-download each app individually?
skyrockets said:
Wow, that was a quick reply! Thanks.
Sorry if I'm dense, I just wanted to clarify two things before proceeding.
Re 1: I also saw another ROM I wanted to try, I guess I'll do that one ([ROM]SKY ICS--- 4.2D-9). Thanks for the heads up.
Re 3: From your response, am I correct to understand I can't use an ICS radio with GB? (it just wont work? or there's no advantage to keeping it?)
Re 5: Same OS meaning inside GB based ROMs or ICS based ROMs? If I go from stock GB to custom ICS, I need to re-download each app individually?
Click to expand...
Click to collapse
1) very good choice, I run it and it is outstanding.
3)they will have a RIL mismatch. You can use them by deleting the system folder out of it, but I would just use the la3 radio and flash that before the rom. After a full wipe, of course.
5)Right, it ensures everything will be clean and run right.
Thanks to everyone on this board - last night I rooted my device, unlocked the bootloader, installed CWM, backed up my stock ROM, and installed CleanROM 3 Lite (which is excellent btw!). My first time doing this, so it was very helpful having all the FAQs and instructions.
On to my question: now that I am running a custom ROM, what happens if there is a newer ROM released? Do I simply re-flash that specific ROM, the same way I installed CleanROM 3 Lite?
If so, it sounds like I lose all my apps/settings... is there some way to keep that across ROMs?
Thanks!
neocryte said:
Thanks to everyone on this board - last night I rooted my device, unlocked the bootloader, installed CWM, backed up my stock ROM, and installed CleanROM 3 Lite (which is excellent btw!). My first time doing this, so it was very helpful having all the FAQs and instructions.
On to my question: now that I am running a custom ROM, what happens if there is a newer ROM released? Do I simply re-flash that specific ROM, the same way I installed CleanROM 3 Lite?
If so, it sounds like I lose all my apps/settings... is there some way to keep that across ROMs?
Thanks!
Click to expand...
Click to collapse
yes. And unless the developer says not to, you can USUALLY skip wiping /data when upgrading to the newer version of that developer's ROM.
As for keeping apps, get Titanium Backup. worth paying for.
If you are going to upgrade to the next cleanrom release, you should be fine...just flash the next release and your apps and info should be fine.
Should you choose to switch to another rom, it is typically recommended that you wipe the phone first, in which case you will lose your apps and info, so make sure everything is backed up.
The problem with keeping apps and settings across different roms is that there can be "compatibility" problems.
That makes a lot of sense, thank you guys. I thought that flashing a ROM automatically wiped everything - but I realize now that's not the case.
I will check out Titanium Backup as well.
neocryte said:
That makes a lot of sense, thank you guys. I thought that flashing a ROM automatically wiped everything - but I realize now that's not the case.
I will check out Titanium Backup as well.
Click to expand...
Click to collapse
Actually, sometimes it does. Recently some Devs are adding Aroma Installer to their ROMS. It only works on touch recoveries (I believe). I am using TWRP and it works great. It backs up your info, lets you choose different options you want for your rom (modifications, different choice of apps, look and feel, sense or senseless, etc), flashes the rom, then restores your info automatically.
Just sharing my experience in upgrading to Jelly Bean on the Captivate.
Before you begin:
Before you begin, back up your efs partition.
Some ICS and JB ROMS have issues where they will forget your IMEI. If this is the case you'll need to restore your efs partition. If you don't already have a back up, you'll have to reflash to stock (pain in the butt) so that you can back up your efs so that you can restore it on your shiny new ROM. Without an IMEI, you won't be able to make calls or access wireless networks.
How to Backup/restore EFS: http://forum.xda-developers.com/showthread.php?t=859914
General Process
ICS and Jelly Bean are too big to put the entire rom in /system, so the current practice is to break up the ROM into 2 or more zip files (the ROM itself and a second zip that has essential apps like the Market). Both have to be flashed.
The ROMs have upgraded CWM (Recovery Modules) so you have to flash the ROM twice. The first time installs the CWM, the second time installs the ROM.
My journey
I had been using Mosaic, which is now defunct. When I started seeing posts from Studacris (former Mosaic developer) from several months ago saying "Gingerbread? What is this the stone age?" I decided perhaps is was time to upgrade to ICS.
Of course when I started looking at ICS ROMS, it turns out that now there are Jelly Bean ROMS available as well. Some people say the JB ROMS solve several problems with ICS. Others say the ICS are more stable for now.
Moral of the story. Your Captivate is unique. You won't know which is which until you try them, but my journey may help you.
1. I want to try Slim Bean, but coming from Gingerbread, it's recommended to start on Cynanogen (CM)
2. So I might as well try CM, but do I try CM9 (ICS) or CM10 (JB)?
3. Ah what the heck, let's go CM10!!!
4. Okay, there's at least four versions. The official, three unofficials of varying "v" releases, the Devil version with datadata (what the heck is datadata?), some guy's custom rolled ROM which he says is likely to brick your phone.
5. Okay, I'll try the latest V8 version with the Devil kernel (note, you should use the version with datadata).
6. Flash goes fine, but now it hangs on black screen with the word Android. After 30 minutes, I figured it really was hanged. Reflashing and rewiping solved that problem.
7. I had a lot of issues with it (see below), so I decided to try Slim ICS.
8. I had other issues with SlimICS (see below), so what the heck, let's try Slim Bean.
9. Slim Bean seems like a keeper to me: Fast; great feautures; decent launcher (vastly better than SlimICS). Only real problem I'm finding is that the Market won't let me install (or even see) Astro Player, which is one of my absolute must have apps. Still trying the dev's workaround.
CM 10 Issues:
Outdated:
1. The home key and back key are reversed.
2. My IMEI was wrong, and restoring EFS didn't help
3. I experienced intermittent lag on the launcher
Update CM10
Everything works fine in CM10 Helly Bean (29.07.2012). Faster than Slim.
http://forum.xda-developers.com/showthread.php?t=1783064.
Slim ICS Issues
The first thing the Slim ICS installer does is install its own CWM and in the process it will erase your sdcard (internal memory)
SO....
1. Back up your internal SDCARD before you start
2. To save time, put the zip files on your external card also (the newer CWM will let you install from the external card)
3. I hate the launcher
4. I still couldn't make phone calls.
Slim Bean issues
Works great except for the market issue. Seems to be a problem with the DPI. Still waiting to see if it resolves. Alternatively, I could try to restore my Mosaic version of Astro Player with Titanium back up.
Update:
1. Market issue resolved after about 36 hours of following the fix on the website.
2. Internal card and sdcard were reversed, (/sdcard and /emmc)
Conclusion
I hope my journey helps someone out there.
patrokov said:
Slim Bean issues
Works great except for the market issue. Seems to be a problem with the DPI. Still waiting to see if it resolves. Alternatively, I could try to restore my Mosaic version of Astro Player with Titanium back up.
Click to expand...
Click to collapse
Apps still aren't showing up in the market, but the TiBu restored apps work fine.
patrokov said:
Slim ICS Issues
The first thing the Slim ICS installer does is install its own CWM and in the process it will erase your sdcard (internal memory)
SO....
1. Back up your internal SDCARD before you start
2. To save time, put the zip files on your external card also (the newer CWM will let you install from the external card)
3. I hate the launcher
4. I still couldn't make phone calls.
Click to expand...
Click to collapse
I initially had that issue of not being able to make any calls. I didn't even have ANY service. Then I went to check which baseband/modem I had and sure enough I found the rom didn't flash a modem. I had to go find one and flash it. After that it worked perfectly.
I also didn't like the new Lightning Launcher so I went back to the old launcher they used - Zeam Launcher.
Ravenmtx said:
I initially had that issue of not being able to make any calls. I didn't even have ANY service. Then I went to check which baseband/modem I had and sure enough I found the rom didn't flash a modem. I had to go find one and flash it. After that it worked perfectly.
I also didn't like the new Lightning Launcher so I went back to the old launcher they used - Zeam Launcher.
Click to expand...
Click to collapse
Which modem did you end up flashing?
CM 10 Issues:
1. The home key and back key are reversed.
2. My IMEI was wrong, and restoring EFS didn't help
3. I experienced intermittent lag on the launcher
Click to expand...
Click to collapse
1 sounds like you did not flash a proper kernel
2 no imei troubles here
3 NO LAG WHAT SO EVER
CheesyNutz said:
1 sounds like you did not flash a proper kernel
2 no imei troubles here
3 NO LAG WHAT SO EVER
Click to expand...
Click to collapse
CM10 comes with the Devil kernel. Flashing another kernel is not part of their installation instructions.
patrokov said:
CM10 comes with the Devil kernel. Flashing another kernel is not part of their installation instructions.
Click to expand...
Click to collapse
It does, but it depends on who ports or where did you get your CM10 rom. That problem you stated occurs when you flash a i9000 devil kernel for what I know. Jelly bean in cappy needs the devil version that has datadata on its filename either VC or CMC. Visit the Hell Bean Thread.
patrokov said:
Which modem did you end up flashing?
Click to expand...
Click to collapse
I tried most of them. I live in the Washington DC area and I found the latest XXJVU worked best for me. You'll just have to find out which one works best for you.
takeoutttt said:
It does, but it depends on who ports or where did you get your CM10 rom. That problem you stated occurs when you flash a i9000 devil kernel for what I know. Jelly bean in cappy needs the devil version that has datadata on its filename either VC or CMC. Visit the Hell Bean Thread.
Click to expand...
Click to collapse
I flashed the CM10 that was to be renamed Helly Bean, following these directions: http://hellybean.site11.com/help.html
(at the time the url was something like cm10.site11.com but the directions are the same.)
takeoutttt said:
It does, but it depends on who ports or where did you get your CM10 rom. That problem you stated occurs when you flash a i9000 devil kernel for what I know. Jelly bean in cappy needs the devil version that has datadata on its filename either VC or CMC. Visit the Hell Bean Thread.
Click to expand...
Click to collapse
Exactly
Sent from my SGH-I897 using Tapatalk 2
CheesyNutz said:
Exactly
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
takeoutttt said:
It does, but it depends on who ports or where did you get your CM10 rom. That problem you stated occurs when you flash a i9000 devil kernel for what I know. Jelly bean in cappy needs the devil version that has datadata on its filename either VC or CMC. Visit the Hell Bean Thread.
Click to expand...
Click to collapse
This is what I originally flashed and had all the issues with. Is this the wrong one?
http://rootaxbox.no-ip.org/divers/devil_jellybean/rom/v8/
Tonight I flashed this one, and everything works perfectly.
http://rootaxbox.no-ip.org/divers/devil_jellybean/rom/20120729/
The reason I ask is that I'm trying to find out whether it was my error or some weirdness on my cappy's part.
patrokov said:
I flashed the CM10 that was to be renamed Helly Bean, following these directions: http://hellybean.site11.com/help.html
(at the time the url was something like cm10.site11.com but the directions are the same.)
Click to expand...
Click to collapse
I don't personally recommend that page because it was not actually tested yet by porters it means that the file in that site was raw JB. Recently derteufel uploaded a version that is "busted". So I would suggest to pay a visit to the HellBean thread and test a version that has already ported.
I just installed the stable CM9 and I don't really like what I am seeing. The lag on the home screen is unbearable and sometimes the notification bar splits into two when I am pulling it down. I will definitely try a CM10 rom and see how well it functions but I want to use the most stable version, or better yet the one with the least issues that I can use as my day to day rom. I really don't want to go through the trouble of installing every single JB rom.
droyd666 said:
I will definitely try a CM10 rom and see how well it functions but I want to use the most stable version, or better yet the one with the least issues that I can use as my day to day rom. I really don't want to go through the trouble of installing every single JB rom.
Click to expand...
Click to collapse
I'd definitely recommend Helly Bean first, in that case.
helly bean all the way. the only problem i have with it is when flashing a new rom (whether its the same to re-flash or upgrading to latest) you lose google now.
I'm running the 8/11 build OF CM10 KANG builds "JELLYBRO" by Makelegs, it's running great! Here's the link below.
http://forum.xda-developers.com/showthread.php?t=1803709
Sent from my SGH-I897 using Tapatalk 2
Definitely Helly Bean. Make sure to do a solid master clear and format of your phone first, then flash the latest helly bean. Long time user of slimics then slimbean and just switched over.
Only jellybean rom I've found that works FAST right out of the box, and even better when changing a few settings with devil kernel config. Only rom in which devil config settings actually stick after reboot as well!
VashTS said:
helly bean all the way. the only problem i have with it is when flashing a new rom (whether its the same to re-flash or upgrading to latest) you lose google now.
Click to expand...
Click to collapse
Not if you flash the add-on like you are supposed to...
Sent from a jelly bean
So far the latest cm9 nightly is the only ics that has worked well for me. All the jb roms I tried have me a lot of issues (sd card switch, no modem-couldn't even flash a modem, etc) so I haven't built up the confidence to try again.
My problems aren't with ROM behavior, but rather the newer versions of system apps. The phone app on gb had a feature at the end of a phone call to redial or text the person you just called. Miss that. Also the clock app doesn't have the world clock. Not a fan of that one. Over all everything is smooth but a lot of features I had with apex 12 are greatly missed.
Sent from my SGH-I897 using xda premium
simple man said:
I'm running the 8/11 build OF CM10 KANG builds "JELLYBRO" by Makelegs, it's running great! Here's the link below.
http://forum.xda-developers.com/showthread.php?t=1803709
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
I also applaud jellybro on my phone and flash each day with new builds as they come. Remeber to have a quick read thro the cherry picks to see what was changed/added/fixed. Runs great!
I do use the devil kernel with it tho - http://rootaxbox.no-ip.org/derteufel/jellybean/Cappy/113/. I use the CMC one.
Matt/eg.
So My old Atrix 2 got sold to my buddy for his mom. I got a new one and installed Leak #1, lapdock audio working great and lapdock battery options are available! Problem is I badly want to try some other ROMs to test lapdock audio. If I do a backup using bootstrap can I restore to it from say SCV7?
Jimbridgeman stated in one of my posts that devs can't add options that don't already exist in some form to custom ROMS. I'm still wondering what ever happened to the battery options I now have in leak #1 No other ROM I have tried, and I believe I tried all atrix 2 ROMs based on ICS and above, at least all available here.
Anyone on Leak #1 knows you can check your lapdock battery level and have options regarding whether it charges your phone or not.
I can take or leave the battery options, it's just why wouldn't you want them, my real deal is I want a better ROM but I do not want to lose lapdock audio again, and from what I understand it's best not to attempt to go back to the leak once another ROM is flashed.
I tried loading scv7 on system 2 last time (first phone/leak install) but had a low memory issue, not enough memory to install apps to internal memory.
Sorry for the long post, I just didn't know a shorter way to explain exactly what I want, which is, a safe way to try other ROMS without losing to option to use leak #1. I guess that's a shorter way lol.
So I can't do a full backup using recovery, flash another rom, then restore the leak #1 backup later right? There has to be a way to create a restore able backup image of my phone as is. Maybe it's time to learn more about development myself and create my own rom based on leak 1.
You can backup with Bootmenu Manager (BMM) and restore with either that or a CM10-based recovery (and vice-versa).
If you backup with the A2 Bootstrap, then ONLY use that to restore.
--DO NOT INSTALL BMM OR A2 BOOTSTRAP ON CM10-BASED RECOVERY (CM10, MagicMod, future ROMs)--
Also, if you are on leak#1 then you can always take the long route back by flashing the leak#1 fxz to GB, then update to leak#1 again... but I'm sure all the lapdock stuff works the same in leak#1 and the final OTA..
Sent from my phone's mind
alteredlikeness said:
You can backup with Bootmenu Manager (BMM) and restore with either that or a CM10-based recovery (and vice-versa).
If you backup with the A2 Bootstrap, then ONLY use that to restore.
--DO NOT INSTALL BMM OR A2 BOOTSTRAP ON CM10-BASED RECOVERY (CM10, MagicMod, future ROMs)--
Also, if you are on leak#1 then you can always take the long route back by flashing the leak#1 fxz to GB, then update to leak#1 again... but I'm sure all the lapdock stuff works the same in leak#1 and the final OTA..
Sent from my phone's mind
Click to expand...
Click to collapse
Thanks, so it's safe to restore a backup even if you aren't on the rom you were using when you created it. I did use bootstrap, so I should un install and then use safestrap to create another. Also, last time I fxz'ed to ota I didn't see the battery options and lost audio on the lapdock(but not non lapdock webtop via hdmi)
The first rom I tried after the leak was scv7 but had entitlement issue, which I fixed but somehow lost home button function, audio never worked again via lapdock, even after fxz to ota (necessitated by a bad Numa flash)
This is my first Samsung phone - had an HTC incredible, then a motorola bionic. I'm a veteran regarding flashing, rooting, etc - but, as many of you know, each device has it's own nomenclature and quirks - so, I'm getting my feet wet. I familiarized myself but had a couple more questions.
I followed this thread first:
http://forum.xda-developers.com/showthread.php?t=1974114
Decided to install latest leaked image - then rooted and unlocked and flashed TWRP. No issues, works great. This had me on VRBMA2.
I got squirrley for a new experience - only took me maybe 24 hours - so, decided to flash a ROM or two. Stuck with stock ROMs based off VRBLK3, CleanROM and Synergy. Both flashed fine, no big issues. I did note however that baseband still read VRBMA2. Because I've had the Bionic for so long with it's *$*%*$* locked bootloader, the idea of flashing custom kernel's and radios is foreign to me. I PRESUME, the baseband is the radio, but I don't know. I realized it was probably ideal to have the VRBLK3 baseband, but, since it was still JB, figured SHOULD be ok. Which it was in general, but, I wasn't sure - so I went back to stock via openyoureyes thread above.
So
1. Can someone clarify the importance of matching the baseband with what the ROM is based off of? How does this relate to non-stock ROMs? i.e. AOSP, AOKP, CM. I'm 99 % sure I've read that the ROM does not modify the baseband or the kernel.
(( 2. openyoureyes files do not modify data (I presume he means data folder with system apps). If I wanted to go back to square one - I presume the image files that he has 'hidden' and warns about using are the original image files to flash via ODIN if I want stock stock. (analagous to an SBF or FXZ file in a motorola device. He just has such serious warnings I wanted to be sure.
** Answered question 2 myself via here -- http://forum.xda-developers.com/showthread.php?t=1762709 section 5 *** ))
Thanks in advance. I love this phone and am having fun learning another device.
MrRedPants said:
This is my first Samsung phone - had an HTC incredible, then a motorola bionic. I'm a veteran regarding flashing, rooting, etc - but, as many of you know, each device has it's own nomenclature and quirks - so, I'm getting my feet wet. I familiarized myself but had a couple more questions.
I followed this thread first:
http://forum.xda-developers.com/showthread.php?t=1974114
Decided to install latest leaked image - then rooted and unlocked and flashed TWRP. No issues, works great. This had me on VRBMA2.
I got squirrley for a new experience - only took me maybe 24 hours - so, decided to flash a ROM or two. Stuck with stock ROMs based off VRBLK3, CleanROM and Synergy. Both flashed fine, no big issues. I did note however that baseband still read VRBMA2. Because I've had the Bionic for so long with it's *$*%*$* locked bootloader, the idea of flashing custom kernel's and radios is foreign to me. I PRESUME, the baseband is the radio, but I don't know. I realized it was probably ideal to have the VRBLK3 baseband, but, since it was still JB, figured SHOULD be ok. Which it was in general, but, I wasn't sure - so I went back to stock via openyoureyes thread above.
So
1. Can someone clarify the importance of matching the baseband with what the ROM is based off of? How does this relate to non-stock ROMs? i.e. AOSP, AOKP, CM. I'm 99 % sure I've read that the ROM does not modify the baseband or the kernel.
2. openyoureyes files do not modify data (I presume he means data folder with system apps). If I wanted to go back to square one - I presume the image files that he has 'hidden' and warns about using are the original image files to flash via ODIN if I want stock stock. (analagous to an SBF or FXZ file in a motorola device. He just has such serious warnings I wanted to be sure.
Thanks in advance. I love this phone and am having fun learning another device.
Click to expand...
Click to collapse
Welcome to the SGS3 :good:
1. Yes, baseband = radio. Any baseband can go with any rom (AOSP or TW). They are separate and not interrelated. I tend to keep mine flashed to the current newest, but use whichever one gives you best reception in your area. It's very subjective and what works for me may not be what works best for you. Flash away
2. The data he talks about is the /data/app folder (all the user apps you have installed from the Play store or otherwise) and the /data/media folder (your internal SD card). All the system apps (camera, contacts, email, phone, etc) are in the /system/app folder, which is part of the /system partition that gets overwritten when you flash the images in his thread. To go back to stock stock, as you put it (stock recovery, unrooted, locked bootloader), look at Section 5 in the OP here.
The difference between the openyoureyes files and the ones in droidstyle's is that droidstyles wipes your internal SD (you lose everything on the internal sd - it doesn't touch the external sd) and openyoureyes does not wipe the internal.
Hope that helps.
MrRedPants said:
So
1. Can someone clarify the importance of matching the baseband with what the ROM is based off of? How does this relate to non-stock ROMs? i.e. AOSP, AOKP, CM. I'm 99 % sure I've read that the ROM does not modify the baseband or the kernel.
Click to expand...
Click to collapse
Welcome aboard!
Basically there isn't any importance with matching your baseband with your rom. Just use whichever you think improves your signal the best. Fyi, you may see these terms thrown around a lot so to clarify: baseband = radio = modem. Your baseband is not flashed when you flash custom roms which is why you saw it stay the same. It will change if you Odin flash a stock rom.
2. openyoureyes files do not modify data (I presume he means data folder with system apps). If I wanted to go back to square one - I presume the image files that he has 'hidden' and warns about using are the original image files to flash via ODIN if I want stock stock. (analagous to an SBF or FXZ file in a motorola device. He just has such serious warnings I wanted to be sure.
Thanks in advance. I love this phone and am having fun learning another device.
Click to expand...
Click to collapse
What you'll want to look out for is whether the stock rom tar will format /sdcard. Open1your1eyes0 has hidden those in his thread I believe. At this point, each of the primary threads that contain Odin specific stock tar detail whether flashing them wipes /sdcard or not. With /sdcard being your internal storage, most user data is stored at /sdcard/data. You're external sd card will not be wiped when using a full wipe Odin tar.
Also, anything ending in ".tar" or ".tar.md5" is flashed only with Odin.
Sent from my SCH-I535 using xda app-developers app