So i haven't been active with the rezound lately and just finished finals and am able to start finally getting back into the scene of development. I am not huge on snazzy roms, I go for reliability. I had a question though, I guess there are new firmwares out and you will need to relock your phone etc. How do I check what firmware I have?
I am currently on CLEANROM Developer Edition (from awhile back) -- I do remember doing some firmware patch during install.
SHIDOOBY said:
So i haven't been active with the rezound lately and just finished finals and am able to start finally getting back into the scene of development. I am not huge on snazzy roms, I go for reliability. I had a question though, I guess there are new firmwares out and you will need to relock your phone etc. How do I check what firmware I have?
I am currently on CLEANROM Developer Edition (from awhile back) -- I do remember doing some firmware patch during install.
Click to expand...
Click to collapse
Settings, About Phone, Software Information, More.
The latest baseband is 1.22.10.0421r, 1.22.10.0424r.
Related
How do you create a flash-able/Odin of my New T959UVJI6 Samsung Vibrant?
This will be my back up (FLASH /ODIN), because there will be some Fresh ROMS that will be released soon, and I want to make the Jump, but I have to at least have a back up.
Knowing how to create this image (or what ever it is called) will help me share more to this community, I would be more than happy to share this image here, and to test more roms, apks, kernals, or patches & updates knowing that I am free to Q.A. the releases if I had a stock image that I could flash or odin at the end of the week or at the end of the test cycle.
Model Number T959UVJI6
Firmware Version: 2.1-update1
Kernel Version: 2.6.29
Build Number: ECLAIR.UVJI6
(I have searched numerous times and the search is not available each time)
I don't think it's possible to create a custom ODIN complete flashable backup yet. It's been worked on but so far not successful -
Here's the original thread:
http://forum.xda-developers.com/showthread.php?t=794425
There are stock images for both 2.1 and 2.2 that can be flashed via ODIN, though. All are easily found in the stickies.
Shrivel said:
I don't think it's possible to create a custom ODIN complete flashable backup yet. It's been worked on but so far not successful -
Here's the original thread:
http://forum.xda-developers.com/showthread.php?t=794425
There are stock images for both 2.1 and 2.2 that can be flashed via ODIN, though. All are easily found in the stickies.
Click to expand...
Click to collapse
Hay Shrivel,
Thanks for the reply, I get the stickies - they are invaluable to the members here.
But most of the stuff out there are at best still in beta, buggy and were configured for or from another user and still needs tweaking.
My phone is like a virgin, and I really don't want to flash her because once you flash, it can become extremely challenging to back to stock.
There is a lot to say about stock, yea it's slow and not as robust, but it is free of bugs.
serendipityguy said:
My phone is like a virgin, and I really don't want to flash her because once you flash, it can become extremely challenging to back to stock.
There is a lot to say about stock, yea it's slow and not as robust, but it is free of bugs.
Click to expand...
Click to collapse
Getting back to stock is really easy - you just have to make sure you can get into download mode reliably and you have the proper drivers on your PC. It's getting back to the current state of your phone that's the tough part (well, not THAT tough, if you know the steps. But not yet possible in a single step.)
OK, don't kill me. New here, just got my Gtab today. I have read a lot and a lot and a lot. Maybe too much. I have not touched my tab yet. Can I start following the easy steps to adding a new ROM, or do I need to do something to the tab first? It looks like vegan is the one to use, but exactly what file is it that I use? I am tech savy, but very new to doing these types of things. Sorry for asking such a noob question. But my brain is in overload right now.
Thanks
Stolly
Just follow the instructions on the vegan thread. You will find the files you need there ;-)
Good luck!
I was ready to roll, but what got me thinking was the bootloader thread. Would that apply to me?
Thanks for the reply
Make sure you know which version android you are on and what bootloader you have. There is a 1.1 and a 1.2 dev branch and I think it makes a big difference. I'm still on 1.1 Vegan 5.1. Froyo and happy with that. Newer builds use different boot loader, make sure you read instructions thoroughly before you flash device.
stolly23 said:
I was ready to roll, but what got me thinking was the bootloader thread. Would that apply to me?
Thanks for the reply
Click to expand...
Click to collapse
Check your version in the settings about tablet screen. Most likely you will have a 1.1 based kernel. So to answer your question, No, it does not apply to you.
Look under system and find "about device". Android version is listed there.
Ok, so I just powered up for the first time. Adroid OS 2.2, Tap 1.1-3389. BUT, to really make things worse, I think I have a dead pixel in the display. CRAP
Well wifey says the pixel does not bother her, So I will go ahead and get the ROM going. Is the Vegan 5.1.1 the correct version?
Thanks again
Yes, vegan 5.1.1 is a 1.1 based Rom, you'll be fine with it. HOWEVER, I do suggest that you at least update to 3588. It's still a 1.1 based Rom so flashing vegan 5.1.1 will be the same. it's just a newer version, and useful in case you want ot go to the 1.2 rom's later on.
HOWEVER, me, personally, since you're stock, I would update to 3588, theen flash teh stock 4349, then flash Brilliant Corners (it's just a 1.2 bootloader port of Vegan 5.1.1) That way, if you want to ever get on the honeycomb bandwagon when all the wrinkles are ironed out, you're already on the 1.2 bootloader.
I WAS running Vegan 5.1.1, and I liked it, don't ge tme wrong. I decided to take the plunge and get to the 1.2 bootloader, since most roms will be going that direction in the future anyway. It was more work to undo what I had already done, just to get back to where you are starting from, so you are already halfway there.
I'm not allowed to post a link to another forum that contains the files and information for Brilliant Corners, but if you use some googling skills, I'm sure you can find it. The developer that was part of Vegan 5.1.1, and created TNT lite, and is currently working on the Honeycomb port, switched most 1.1 roms over to the 1.2 bootloader, including Brilliant Corners.
I'm new to all this rooting as well what helped me was some of the video tutorials on youtube. It helps to see something being done before you do it. I have Vegan-tabs 7.0.0 running on mine.
i just bought my wife this phone. already backed up nv. it keeps prompting for a system update. does this phone have firmware like my lte evo?? do i need to upgrade the firmware on it before flashing a custom rom? kinda lost first samsung. i followed the backup threads already have the imei and nv backed up. so whats next? just root and flash. should i take the upgrade? then root.ITS ANDROID 4.1.2 BUILD jzo54k.l710vpbmb1
kaos420 said:
i just bought my wife this phone. already backed up nv. it keeps prompting for a system update. does this phone have firmware like my lte evo?? do i need to upgrade the firmware on it before flashing a custom rom? kinda lost first samsung. i followed the backup threads already have the imei and nv backed up. so whats next? just root and flash. should i take the upgrade? then root.ITS ANDROID 4.1.2 BUILD jzo54k.l710vpbmb1
Click to expand...
Click to collapse
if the phone prompts for an OTA update, it will logically be a newer version of Android.
If you want to root it anyway and install a custom ROM, I do not really see any reason in upgrading beforehand (I guess your S3 is running a Android version 4.1.2 already?). Hence go ahead, follow the rooting & flashing guides in the FAQ thread.
chrismast said:
if the phone prompts for an OTA update, it will logically be a newer version of Android.
If you want to root it anyway and install a custom ROM, I do not really see any reason in upgrading beforehand (I guess your S3 is running a Android version 4.1.2 already?). Hence go ahead, follow the rooting & flashing guides in the FAQ thread.
Click to expand...
Click to collapse
I ask because on my evo it could include firmware such as boot loader or radios. Logically it's smart to ask before assuming. After all what happens when we assume. But thanks. I finished backing up and rooting last night about 20 minutes after I posted
Sent from magical jelly bean.
the 4.1.2 update does include a new bootloader, but you're already running 4.1.2
kaos420 said:
I ask because on my evo it could include firmware such as boot loader or radios. Logically it's smart to ask before assuming. After all what happens when we assume. But thanks. I finished backing up and rooting last night about 20 minutes after I posted
Sent from magical jelly bean.
Click to expand...
Click to collapse
Some US versions of the S3 have separated their OTA updates into 2 types (one of which is "firmware"). I assume this is the same as you experienced on the Evo.
It is only some US carriers I have ever seen do this however. International versions don't separate them into 2 types. OTA update could be anything. At the most it is ROM, Kernel, Recovery, Radio and Bootloader that is updated.
The use of the word "firmware" annoys me to be honest. Firmware is more low level than the OS. It is embedded, which almost makes sense when you look at how the US carriers separate it out. Android to me is not "Firmware" but unfortunately, on the international forums here and from Samsung themselves, you will see them referring to Android as "Firmware", so if reading the GT-i9300 forum and you see someone say firmware, 9 times out of 10 they're referring to an Android update or ROM that may or May not include a bootloader etc..
I hope this clarifies a little
I got my GS4 back in the summer and I promptly rooted and I believe I even was able to unlock the bootloader. I then flashed Eclipse S4 TW edition (based on MDK) and its been so rock solid I haven't had a reason to touch is since. I'm been staring at my android 4.2.2 version and have been thinking no reason to upgrade. If it isn't broke don't fix it right? Well I'm starting to feel the flashing itch so I decided to jump back on XDA and see whats out there.
I'm trying to get a grasp on what all has changes since the last time I flashed my phone. It looks like there has been a few new builds to drop since I flashed. I'm confused on the details though. With my current state can I flash anything I want using the custom recovery or are there restrictions that I must follow. I have seen posts about using SafeStrap for flashing. I remember SafeStrap from my Razr days as a solution for phones with locked bootloaders. Does one of the OTA's relock the bootloader and make it impossible to unlock or are the SafeStrap posts for people that got the phones after me which already came with a locked bootloader?
Any reason why not to upgrade to the newest builds? I can't find any details on what is different between the builds but I have to imagine there is some new stuff that I might want to play with.
Lastly, can anyone suggest a good solid ROM to similar to Eclipse TW that is based on a newer build?
I appreciate any help you guys can give me. Being away this long and coming back is slightly overwhelming and who has time to navigate through every page of every thread for the past 6 months or so.
I would suggest to read some of the threads....custom Roms for 4.3 and 4.4 are a bit slow in coming. If you are mdk...no need for safestrap....you can still keep your phone rooted and loki'd..and move to 4.3 base
powered by hashcode safestrap hyperdrive 10.2
trevoryour said:
I got my GS4 back in the summer and I promptly rooted and I believe I even was able to unlock the bootloader. I then flashed Eclipse S4 TW edition (based on MDK) and its been so rock solid I haven't had a reason to touch is since. I'm been staring at my android 4.2.2 version and have been thinking no reason to upgrade. If it isn't broke don't fix it right? Well I'm starting to feel the flashing itch so I decided to jump back on XDA and see whats out there.
I'm trying to get a grasp on what all has changes since the last time I flashed my phone. It looks like there has been a few new builds to drop since I flashed. I'm confused on the details though. With my current state can I flash anything I want using the custom recovery or are there restrictions that I must follow. I have seen posts about using SafeStrap for flashing. I remember SafeStrap from my Razr days as a solution for phones with locked bootloaders. Does one of the OTA's relock the bootloader and make it impossible to unlock or are the SafeStrap posts for people that got the phones after me which already came with a locked bootloader?
Any reason why not to upgrade to the newest builds? I can't find any details on what is different between the builds but I have to imagine there is some new stuff that I might want to play with.
Lastly, can anyone suggest a good solid ROM to similar to Eclipse TW that is based on a newer build?
I appreciate any help you guys can give me. Being away this long and coming back is slightly overwhelming and who has time to navigate through every page of every thread for the past 6 months or so.
Click to expand...
Click to collapse
Ok, So heres what you missed. After the MDK release they(Verizon/Samsung) patched the loki bootloader hack so thats why anybody whos not on the MDK release has an locked bootloader. That is where safestrap comes in. Safestrap is a custom recovery that was developed by Hascode, in order to provide those with a locked bootloader a way to get in on the rom action, while keeping there stock rom untouched.
Now that said i would advise you to update but not through the stock "Check Update" tab (as that will lock your phones bootloader). Instead you should just flash a rom that is built with the new update as the base (E.X. Hyperdrive 11). This will allow you to get the new update without locking your bootloader.
Now for roms, i believe there is an updated Eclipse TW Rom & Eclipse AOSP ROM on the Dev's site ( dont know the link but will post it once i find it).
First of all this is my first post. Hello to everyone. I have been searching/reading thru these forums. Great source of info.
Phone info:
Currently S-OFF, unlocked, lateset AT&T 4.4.2 firmware, viperone 6.2.1, twrp
I have a pretty good comprehension of how to install or revert pretty much anything that can be done to this phone and have done so with great success. What I don't understand is the relationship between the firmware base of an RUU and the build of any given ROM. How is it that a custom Rom based off let's say x.xx.401.x work with x.xx.502.x main version? The devs say to update to the most current available firmware. Does that mean I have to flash a firmware base that matches what the Rom base for optimal performance? Because I originally thought that was the case and when I did my phone developed syncing issues particularly with the stock mail and weather apps. They would only sync over WiFi. Everything else about the phone worked as normal. Believing there was a problem with the Rom I flashed a few different popular roms on here. Always returning to full AT&T stock first. I later fully converted to GPE and to my surprise everything worked as normal. So I then converted to stock developer edition by way of zip flash and RUU exe. (By the way, when I say stock I mean s-off & unlocked but otherwise factory.) Received all the ota's. Main version would show as x.xx.1540.x. supposedly this would make my phone a dev edition with AT&T as the provider. And yet the syncing problems returned. So once again I returned back to factory AT&T 4.4.2 and all returned to normal. I then decided to try and use a Rom based off 4.4.2 and not one from 4.4.3; expecting the syncing issues to return only this time they didn't. So now I am really confused.
My questions are:
If coming from 4.4.2 factory firmware, is it best to run a Rom from the same base or am I doing something wrong and I should be able to use a Rom from a newer base on an older firmware?
If the developer edition and GPE can be carried by AT&T then why was I having syncing issues with the developer edition and not GPE?
I thought by being s-off I should be able to flash any RUU from any carrier without problems, just that I would be limited to the network capabilities of the actual service provider.
Everything I know about this stuff I learned from this forum. But I think I missed something.
My AT&T M7 always works best on the stock software.
The only thing I could figure is that AT&T have refined the software and radio so well that all the other versions pale in comparison.
I noticed the Developers Edition always had a horrible Bluetooth and WiFi radio. Signal strength was always weak compared to the stock AT&T software.
To answer your questions
Flash any version Roms you want on the latest AT&T firmware. And you'll have the best your phone can be.
clsA said:
My AT&T M7 always works best on the stock software.
The only thing I could figure is that AT&T have refined the software and radio so well that all the other versions pale in comparison.
I noticed the Developers Edition always had a horrible Bluetooth and WiFi radio. Signal strength was always weak compared to the stock AT&T software.
To answer your questions
Flash any version Roms you want on the latest AT&T firmware. And you'll have the best your phone can be.
Click to expand...
Click to collapse
I get so mixed up with all the terms being used interchangeably. So to clarify, as long as I am using the latest firmware from AT&T (currently 5.12.502.2 kk4.4.2), I can flash any custom ROM base. Whether it is based on 4.4.2 or higher. Correct?
I still want to know why I experienced the sync problems while running the factory x.xx.1540.x dev edition but not with the GPE. I never tried the factory x.xx.401.x WWE firmware either. However, I just got an sim unlock code from AT&T earlier today. I'm gonna try that maybe tomorrow and see if it makes a difference altho I don't believe it should. And I'm not gonna switch to a different provider.
Honestly, I was happy with my phone before I got wrapped up in all of this. I just decided to tinker with the phone and the mod bug has bitten.
ANGRY_robert said:
I get so mixed up with all the terms being used interchangeably. So to clarify, as long as I am using the latest firmware from AT&T (currently 5.12.502.2 kk4.4.2), I can flash any custom ROM base. Whether it is based on 4.4.2 or higher. Correct?
I still want to know why I experienced the sync problems while running the factory x.xx.1540.x dev edition but not with the GPE. I never tried the factory x.xx.401.x WWE firmware either. However, I just got an sim unlock code from AT&T earlier today. I'm gonna try that maybe tomorrow and see if it makes a difference altho I don't believe it should. And I'm not gonna switch to a different provider.
Honestly, I was happy with my phone before I got wrapped up in all of this. I just decided to tinker with the phone and the mod bug has bitten.
Click to expand...
Click to collapse
I think I figured this out. I continued to flash different ROMs and firmwares with the same results as I posted in the OP. Then earlier tonight I decided to try to convert to developer edition again (x.xx.1540.x) and flashed an ruu.zip, went thru the setup process, and as before the same issues returned. Then I had an idea; lets try something I haven't done yet. I pulled the SD card and factory reset the phone. After I completed the basic setup process I inserted the SD card and let the phone do its thing. The phone now works as it should (same as it does with the AT&T xx.502.x firmware installed).
Just figured I would pass this along.
Cheers
I give up
I thought I had this figured out. Last night after to converting to dev edition with all updates, everything seemed normal. I flashed the latest viperone rom as it is the rom I want. Turn the phone on this morning and the sync problems are present once again. I have searched thru a tom of pages on this sight alone. I cant find an answer. So its back to stock at&t.
I solved the problem. Incorrect settings in 4636 menu.