What firmware will the vibrant launch with?
Sent using tapatalk
2.1 (Eclair) with 2.2 (FroYo) apparently coming later this summer.
No I know that I mean whats the build number like xxxjb3 or what??
Sent using tapatalk
I'm interested in this as well. Hopefully we don't get one of the old stale firmware versions.
T959UVJFD is what my baseband says.
interesting close to jf3 firmware from russia.
Sent using tapatalk
Have you tried using odin to upgrade your firmware to any other build?
Sent using tapatalk
Scratch that maybe not a good idea until we get a dump and have a restore point. I get mine this week so ill do a system dump and try and put it in .tar format or md5
Sent using tapatalk
Yea, i'm going to wait on trying anything until it's verified it works. Don't need a brick! One weird thing I've noticed thus far is that the email doesn't always sync when you schedule it and for some reason only some ringtones I assign to individual contacts work and on others the default ringtone rings. Other than that it is pretty quick, video is impressive on the super AMOLED and swype is even better than the the HD2.
The WiFi hotspot app is missing from the Vibrant firmware right?
yes but a quick root and installation of wireless tether fixes that!
Just installed jg1 for the I9000
I'll try anything once.... But it works, with even the same system folder bug that the I9000 has when running this ROM. Starts out in Russian, but no biggie. Unfortunately I can't post external links yet, so I'll do my best to direct you in a general direction of my sources.
The first ROM I installed is the JG1 ROM. I looked up "MoDaCo Custom ROM for Samsung Galaxy S".
The tools needed are found on samsung-firmware.webs dot com. Sign up was needed. The tools are Odin3, a .pit file, and like I mentioned before the JG1 Rom. I choose that ROM with the intention of installing the MoDaCo ROM above.
So if you've trashed your original ROM, and then somehow you corrupted your flash card at the same time (bye bye backup), then absolutely, this is a viable option. Like I said everything's working at this point, but thats not gonna stop me.
MS_Guru said:
I'll try anything once.... But it works, with even the same system folder bug that the I9000 has when running this ROM. Starts out in Russian, but no biggie. Unfortunately I can't post external links yet, so I'll do my best to direct you in a general direction of my sources.
The first ROM I installed is the JG1 ROM. I looked up "MoDaCo Custom ROM for Samsung Galaxy S".
The tools needed are found on samsung-firmware.webs dot com. Sign up was needed. The tools are Odin3, a .pit file, and like I mentioned before the JG1 Rom. I choose that ROM with the intention of installing the MoDaCo ROM above.
So if you've trashed your original ROM, and then somehow you corrupted your flash card at the same time (bye bye backup), then absolutely, this is a viable option. Like I said everything's working at this point, but thats not gonna stop me.
Click to expand...
Click to collapse
you mean we can flash i9000 firmware to T9595?
Have you tried I9000XWJG5 ?
MS_Guru said:
I'll try anything once.... But it works, with even the same system folder bug that the I9000 has when running this ROM. Starts out in Russian, but no biggie. Unfortunately I can't post external links yet, so I'll do my best to direct you in a general direction of my sources.
The first ROM I installed is the JG1 ROM. I looked up "MoDaCo Custom ROM for Samsung Galaxy S".
The tools needed are found on samsung-firmware.webs dot com. Sign up was needed. The tools are Odin3, a .pit file, and like I mentioned before the JG1 Rom. I choose that ROM with the intention of installing the MoDaCo ROM above.
So if you've trashed your original ROM, and then somehow you corrupted your flash card at the same time (bye bye backup), then absolutely, this is a viable option. Like I said everything's working at this point, but thats not gonna stop me.
Click to expand...
Click to collapse
This is awesome. So it seems that there is a very good chance for a full compatibility among the ROMs of all Galaxy S variations.
In all honesty, I wouldn't go there. I'm what they call a glutton for punishment. My learning process... And FYI, the 9000 has a home button, the Vibrant does not. Made things interesting to say the least. If your ever get stuck in that position it's, up volume + power, hold through two power cycles, and you should get to the downloader. Lost root in the process, then adb and fastboot decided they would only communicate with my Vibrant when it suited them.
Anyways, after screwin with that for awhile I was able to find firmware. But don't go flashing it just yet, seems kinda buggy. But it is most definitely intended for the Vibrant. If anything, just snag it and save a copy for the community. This seems to be the only working link left out of four.
Good lord, this is retarded. I still can't post links. Will someone please PM me so we can get these links posted before there dead too...
@al74 The only place I had any issues was the radio, and that was an older image I used. I'm pretty comfortable with how far I can push this thing now, which is surprisingly far. I'm gonna go on the rampage again tonight. Maybe I'll try some newer images. But seriously, if this is your only phone, don't do what I do.
Sweet I can finally post links. So here's what I've got. Remember anything you do with any of this is on your shoulders. But snag it you should.
Pretty sure this is the real deal, but not really sure where it originated. Boots as tmo Vibrant Galaxy S, but not sure if its official, hacked, partialy hacked. Play it safe and don't flash it to your only phone. I can attest to the fact that its got bugs and may not boot 100% of the way 100% of the time. Either way, have at it...
megaupload
Here's a link to the PIT file I've been using...
depositfiles
And here's a link to Odin3 v1.00...
depositfiles
These are the drivers I used with all the alien firmwares I've installed. There's an installer included, but I didn't use it. I'm just leaving everything I've been using intact...
Megaupload
I didn't keep notes on my sources, because this really only scratch's the surface of everything I dug through to find what worked. But I do leave the files in there fully intact state, so that if need be I can use Google to relocate them later.
@MS_Guru How did you get it to work? Now my phone won't detect my sim card and my volume buttons are mixed up and in recovery I can not select things with the power button.... I am starting to get worried I might had to live without m phone for a few days and return it to radioshack and hope no one notices what I did...
Reflashing with odin3 using the files you provided fixed the bootloader... now I just can't get into the phone... I am getting closer though, maybe if i update with the dump on the forums somehow...
Flash the older firmware it should fix it until we get a full dump to restore from..
Sent using tapatalk
I believe I did (I started a post like the newb I am titled something about being retarded) but I get a blank screen, but I have the feeling I am doing something wrong. I also tried downloading the dump zip and renaming it to update.zip and tried to install it from the recovery screen but nothing... that or the same thing... ugh, just disappointing to get a new toy and immediatly ruin it for no good reason... and having paid 500ish only makes it worse, but I preordered from radioshack so maybe they will take it back pretty simple...
Sent from my HTC Dream using XDA App
Pretty sure we've already talked via pm. But read the whole post. I warned of the trouble of using these. Remember, this is the Development area. You should never flash firmwares without first considering the dangers, especially when I even warned you, a few times at that. But in all seriousness, you'll be fine. Throw that thing in a drawer, grab your old phone, and let these threads mature a bit. The way things are going, you'll be seeing valid fixes in no time. And seriously, even in my best efforts, I am absolutely unable to brick this thing.
Sorry to say it as I'm sure you've learned a tough lesson, but in the future, read the entire post. If someones saying things like, don't know where its from, hacked?, partially hacked?, Official?, I can attest to bugs, those should all be HUGE red flags. I provided this purely in the spirit of progressing future tools and ROM's, not to provide a functional firmware.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
Hey friend I am feeling very happy to announce, I got my G-Note just half an hr back
Here i have started post to express my experience to Root Device, and complete swapping from my old device (SGS1)
First of all i have still not paid for my device, but i shall give < 32K
Edit : DP is 32600K, + dealer getting many scheme, and who are have huge sale can get much discount and scheme, so purchase from bigger dealer to get more bargain. Sure you will get betwin 31.5K to 32K
Note : Flip cover not come inside box pack, so you ask seperately, it is complimentery from samsung.
As soon as i have switch On, i got msg there is 0.08MB update available, and i have updated OTA.
I have now baseband version N7000DDKJ3 , ginerbread 2.3.5
Kernel : XXKK3
Just Rooting finished, busybox and superuser pushed smoothly, it took < 5 min to finish total procedure
I have followed procedure to root device is here.
which was started by me earlier last week. I have at presently selected, "I want to just Root " methos in above said post. it was uneventful n finished in 5 min.
Rooting : Who want just to use specific application require root e.g faster fix, Titanium backup. You all need to follow "I want just Root" option, Still stock CWM will works with basic function e.g factory reset, update zip from SD card e.g. you will miss Backup/Restore ROM. for that you go with method 2 on above said post
Call Quality : Very nice compare to SGS, where it was horrible to talk without woodoo control plus
Camera Quality : Much better then SGS
GPS : Very fast, i never seen before this in any device so fast. first time it fixed in side my office in <20sec, accuracy 5mtr
even get fixed in my bedroom, which was never happen with my pevious SGS with fater Fix application. Here i dont req such kind of app to solve it.
Data swap from old android device :
Best job can done with Titanium backup
Here some guide for new user
When you swap application + Data from old device to new, dont restore system stuff. Contact can be managed with import /export, SMS can be done with SMS Backup/Restore applcation. Rest of system setting better you done manually
And restoing rest of thing best option is 'Restore User application with data' scenario.
Almost all application worked smoothly after transfering, except Asphalt 5 (lookin for fix)[edit: Asphalt 6 HD working fine, you can get free from samsung Appl]
Navigation best works. I have tried Sygic Aura, Navigon, N-Drive as well Goole world activated Map.
Native Indian Language support :
I can read Gujarati/Hindi language with stock browser
User's Manual Here
ScreenCapture : Tap and hold the screen with S pen to capture screen Shot
File saved in USB storage/ScreenCapture directory
OR
Seep your Palm across the screen to capture scrennshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now stay tuned as i am starting swapping of device, as well planning to CF root to get CWM. I shall update it here as soon as i do finish task.
Thanks for the info
few queries
Which file did you use to root ,
as in your link it says to download relevant file.
and as per your post your firmware is KJ3,but there is no file linked for KJ3
I said, I have used "I want just Root" option, I have not installed CWM, so do not need to select file for kernel
just i have tried in recovery, stock recovery is working with these option
Wipe Data/cache
update Zip from SD card
Rebbot
test band smthing
I dont think i do have need for extra option, as i am usually using stock ROM, so no need to have function to have backup/restore Rom
lets C, but according to chainfire guide you can use KK1
can you please tell us ketan if we can actually in fact use the kk1 kernel...i do not want to brick this *****...please...
I have ask same to ChainFire regarding MobileOdin software, which working on same base, his answer was
"I don't see why not"
still you can confirm with ChainFire
very easily swap all data with TB, will update main post with detail soon
Asphalt 6 HD working fine, you can get free from samsung Appl
dr.ketan said:
I said, I have used "I want just Root" option, I have not installed CWM, so do not need to select file for kernel
just i have tried in recovery, stock recovery is working with these option
Wipe Data/cache
update Zip from SD card
Rebbot
test band smthing
I dont think i do have need for extra option, as i am usually using stock ROM, so no need to have function to have backup/restore Rom
lets C, but according to chainfire guide you can use KK1
Click to expand...
Click to collapse
why did you choose not to install the cwm?
DMax99 said:
why did you choose not to install the cwm?
Click to expand...
Click to collapse
CWM giving previlage to Backup/Restore ROM, as well to flash new firmware.
As i have mention, i am always using stock firmware. and keeping backup of my system/user app data with Titanium backup.
So no any more benifit for me to use CWM.
Just rooting is enough for me.
edit : ya some Chain Fire application can be use if you have CFroot, but really i never used it.
As now most the of Note in world are getting 2.3.6 upgrade, any idea when in India we will get official Android 2.3.6 upgrade?
Other thing, as of now My Note is taking around 5-6 hours to get charge, is that normal. I have done 3 recharge cycle.
The battery backup is also very less its around 8-12 hours, though i know its new and i am using more, but this is very less.
bmunshi said:
As now most the of Note in world are getting 2.3.6 upgrade, any idea when in India we will get official Android 2.3.6 upgrade?
Other thing, as of now My Note is taking around 5-6 hours to get charge, is that normal. I have done 3 recharge cycle.
The battery backup is also very less its around 8-12 hours, though i know its new and i am using more, but this is very less.
Click to expand...
Click to collapse
Sorry for bumping the old thread..Am experiecing the same problem as the above user mentioned..my note is also taking around 5-6 hours to get charge..am rooted lb2 firmware with lb1 cf kernel..any help guys?
are you charging through usb or AC outlet? are you using original charger/battery? i have seen a thread similar to this problem... dont remember what the final solution was.. just check in Q&A..
the average time to charge ur Note fully from almost zero is 4 hours..
also try charging switched off... gives a proper charge without interference..
anjath said:
are you charging through usb or AC outlet? are you using original charger/battery? i have seen a thread similar to this problem... dont remember what the final solution was.. just check in Q&A..
the average time to charge ur Note fully from almost zero is 4 hours..
also try charging switched off... gives a proper charge without interference..
Click to expand...
Click to collapse
Thanks for the reply. Am using ma laptop usb...am using original battery ad usb cable...wht would it be the difference in charing in ac outlet/usb?
Usb charge takes long time,compare to ac charging
Sent from my GT-N7000 using xda premium
dr.ketan said:
Usb charge takes long time,compare to ac charging
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
i experience the same
It will def take alot of time thru usb no doubt abt that!!!!
Sent from my GT-N7000 using xda premium
thnx fr de info ;-)
dr.ketan said:
Seep your Palm across the screen to capture scrennshot
Umm how does one get this Palm sweep to work ?
Click to expand...
Click to collapse
just like in the picture.. make sure you lightly drag your little finger on the screen..
Congrates Ketan on your purchase and welcome to the Note world .....
however just a small concern regarding the price ... I bought this beast for a price of 30,200 INR 1 month back .... and 1 week ago it is available here for price of 28,700 INR .... M from bangalore ..... With Flip cover
Is the price again got increased to 32K ....
Are there any chances of me running into sumkind of bricking issue if i upgrade to ICS ? - I have always been on stock GB firmware and never messed around.
Also, is it so tht OTA updates are safe than kies coz kies will wipe complete data to install ICS and tht will inturn introduce wipe bug ?
PS: I will be downloading Indian official ICS.
In your situation it is highly unlikely you will brick your device since you are coming from stock and have never installed any other ROM
I respectfully disagree, I know there's a lot of talk about weather the ics stock roms are actually dangerous or not, but having seen brick after brick from several different scenarios, from people who've been on custom roms and upgrades, to brand new owners who've done one simple reset, and even a couple who just copied a movie across to their sd card. Unfortunately the casualties are not limited to being routed or with cwm.
There are works in progress jointly with a google coder on the matter of a possible fix, but at present still the only fix is a mobo replacement, or to bypass the problematic section of mmc.
I would highly recommend reading this thread
http://forum.xda-developers.com/showthread.php?t=1659768
Also
http://forum.xda-developers.com/showthread.php?t=1661616
There is a risk, full stop. Of course, it's your decision and I wish you well.
Sent from my GT-N7000 using xda premium
Same situation here... I am also downloading official OTA ics update... I am on stock GB as this screen shot....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
May i update it or not???
olivespin said:
Are there any chances of me running into sumkind of bricking issue if i upgrade to ICS ? - I have always been on stock GB firmware and never messed around.
Also, is it so tht OTA updates are safe than kies coz kies will wipe complete data to install ICS and tht will inturn introduce wipe bug ?
PS: I will be downloading Indian official ICS.
Click to expand...
Click to collapse
If it's official I Dunn see any risk installing it. If it really bricks your device I'm sure Samsung will take full responsibility of it since it's official anyway.
Sent from my GT-N7000 using xda premium
the only safe ICS at the moment is CM9 ,or ROMs based on CM9 Kernel
http://forum.xda-developers.com/showthread.php?t=1627854
if you don't use samsung apps then cm9 is a better all rounder than official ICS ,plus it's safe.
Wondering the same thing...
I have non-rooted German Note, just found out about the official ICS release today (for some reason I never get Sammy alerts) checked for updates and it's there but thought I should come here and check to see if everyone was happy with it...lo and behold not only is it buggy but it can brick your phone???
Damn, after all the hurrying up and waiting this is what they release?
I don't know if the OTA update for non-rooted German Notes has faired any better than other combinations but I've cancelled the update twice as I've read through various threads here, just too scared...
Mate, I'd wait for a further kernel.
Sent from my GT-N7000 using xda premium
If you never flashed any custom ROM, and you are using Kies or OTA upgrade, then the risk is that if something happens, you go to a Samsung Service Centre, and they repair it for you for free. It may take a couple of days for the Service Center to replace the motherboard - which is a hassle.
If that is your case, just flash it
I'd advice that you should NOT perform a factory reset after upgrading to ICS, (unless you don't mind bricking your phone and leave it in the Service Center for a couple of days).
Cheers
MR.change said:
the only safe ICS at the moment is CM9 ,or ROMs based on CM9 Kernel
http://forum.xda-developers.com/showthread.php?t=1627854
if you don't use samsung apps then cm9 is a better all rounder than official ICS ,plus it's safe.
Click to expand...
Click to collapse
Agreed. The only problem now is picking which one to go for!
Sent via carrier pigeon
I'm almost exactly like op. I'm rooted but still on stock gb.
Like the others, I will wait until they develop a fool proof way to upgrade to ICS. It's really not worth it right now to even try it imo. Bricking my note would really suck.
DPMAce said:
I'm almost exactly like op. I'm rooted but still on stock gb.
Like the others, I will wait until they develop a fool proof way to upgrade to ICS. It's really not worth it right now to even try it imo. Bricking my note would really suck.
Click to expand...
Click to collapse
same here... hoping that our patience pays off..
Okay guys,
I got a little adventurous, and updated my Note to official ICS via OTA today.
Will post my experience soon.
olivespin said:
Okay guys,
I got a little adventurous, and updated my Note to official ICS via OTA today.
Will post my experience soon.
Click to expand...
Click to collapse
If you would like a little more peace of mind, you could always install a kernel built from patched Samsung ICS source. So far Franco and SpeedMod seem to be relatively safe. However, there has been one rather unscrupulous report of a brick while on Franco kernel. Because of the nature of the claim though, I, as well as Entropy and others are questioning the validity of the claim. Nevertheless, even though the patched source kernels are supposed to be "safer", only time will tell. Your best bet would have been to avoid the update until after a confirmed safe method of upgrading.
Sent from my GT-N7000 using Tapatalk
well in my case i guess i'm just lucky. i already have flashed 3 ics, from stock gb lc1, namely: full repack (ics leak) by chainfire through mobile odin pro, lpy germany (dbtel) non wipe with cf-root lpy also through mobile odin pro, and lpf (taiwan) using pc odin (full iwpe) and i really like these ics releases than gb due to its smoothness and my battery lasts longer. the only thing that bothers me is that voodoo louder has only +3 db in its maximum whereas it is up to +10.5 db in gb and you could really tell the difference (i am using senheisser hd 449) and i cannot customize boot animation. i'm rooted but cannot modify the bootanimation using the same method as in gb, i.e., push the file in \system\media even if permissions are checked.
Updated my GT-7000 to ICS via OTA .
Running fine. Definitely better than GB.
Wants to do factory reset and data wipe but not enough courage to do that .
Hope this will fix soon.
Cheers
Well i did update and wiped to factory setting but no dead phone. .. Even on gb i had wiped it for many tines but my phone is still safe
Just a word of advice..
if you have Official ICS updates already on your phone, you can always go to a Samsung Center near your place and just have them be the one to flash and upgrade your device.
Why worry for something where you can just let the local subsidiary of sammy (on your area) do it for you?
For peace of mind and confidence, I should say.
This is my initial 9 hours with official ICS updated through OTA. After several time failed with Kies. Previously running GB 2.3.6 No root history.
So far so good.
Sent from my Noble Black Note
Upgraded via OTA. Perfect!
Sent from my GT-N7000 using Tapatalk
Hi! This would be my first thread. I am making this to help those who want to reinstall their firmware due to a faulty update but doesn't want to learn how to flash or to try even flashing firmware through Heimdall or Odin.
In this mini guide, we will make use of the dreaded Samsung Kies.
Now I know a lot of users actually hate this software. I kind of hate it too. It is way too quirky for my tastes.
Let me make a quick background as to WHY this guide is being made.
I have decided that for the first year of owning my new S3 (or as long as I can muster) I would avoid all rooting and flashing on the phone. I went berserk with flashing on my old phone, but I just wanna take it easy and live with stock for now. (Although, I do check in every now and then regarding the developments in the forums)
The time came for my country to update our Galaxy S3 to Jelly Bean. I updated my phone over the air. After the update, I had experienced several bugs regarding the new OS, such as stuttering, hanging, as well as that annoying contact bug where my phone keeps trying to call through the internet rather than through the phone network.
From my previous experience, flashing new firmware can sometimes cause issues if you don't clear your data. In some cases, a reinstall of the firmware of the device had to be done.
I did not want to break my oath (yet), so I tried to see what Kies could do for me in this regard.
I have owned an iPod touch before and went on a Jailbreaking adventure. I know for a fact that iTunes allows a restore of the firmware of the iDevice. I though that Samsung may have something similar on their KIES software. I was right.
Here is what I did.
WARNING! This process DELETES DATA on your device
First, start up KIES and install whatever seemingly random "update" it asks you to make.
Once you are updated, you should see this screen, provided you did not connect your phone yet:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Go ahead and connect your phone. Once your phone is connected properly, it should display your device data, such as current firmware, upgradability, as well as the memory status of your phone.
Just go up to the top bar and choose firmware upgrade and initialization.
It should take you to this prompt:
As you can see, this process is a reformat and reinstallation of the latest firmware for your device. In my case, it was the latest Jelly Bean for my country. If you choose Ok, this next screen should pop up:
This tells you your current version, and what version the reinitialization will install for you.
After choosing OK, you should see a familiar screen. This screen is what you would look at if you were updating through KIES normally, say, from ICS to Jelly Bean. Just follow the prompts, read, and you should get through it in a couple of hours. It will download a fresh copy of the latest firmware for you, that is why it takes a while.
Once the process is complete, do one final restore to factory settings, and you should be as bug free as any other person on Stock firmware, legitimate bugs notwithstanding. For me, the experience is great, the phone is fast, and it was only a matter of time before I am once again back in business.
Thank you for your time in reading this humble guide!
I am not held responsible for anything bad that happens to your device such as bricking or whatever. Doing this is entirely up to you. Still, this is a whole lot safer than flashing, since it is an OFFICIALmethod of reinstalling a firmware. Any issues you get should be redirected to Samsung, the creator of KIES
Cool! Thanks for this.
I used this method last night. I was surprised after the update that all my programs, messages where still intact. I was expecting a freshly formatted phone. Anyway the great result is that this solved my power problems with Jellybean. My phone is now as power efficient or even better than it was with ICS! Thank you xenoyosh!
I'm glad this thread helped someone out.
Thank you so much for doing this tutorial! My Samsung Galaxy Reverb has been a pos since I rooted it, with a custom rom. I must have messed it up somewhere but I'm so thankful you could help! I've looked everywhere and couldn't find a stock recovery rom, that would work without a computer, for my phone. I finally don't feel like such a noob (granted I guess I sounded like one just now)! A million thank yous sir/madam!!! :laugh::victory:
heartofageek said:
Thank you so much for doing this tutorial! A million thank yous sir/madam!!! :laugh::victory:
Click to expand...
Click to collapse
and you didn't click it...
One of my thanks has gone to the OP free of charge .
jje
what if kies tell me that my gti9300 does not support initialization?
I have been advocating this feature for a while now but one problem I found when doing this was that my csc changed to Korean from btu. I don't know if this occurred after performing a factory reset but it may be worth checking in your devices. If you have carried this out then unplug from your computer, reboot handset, reboot computer and then open kies and plug your phone in. Hopefully all is well, it's just something a ran in to on more than one occasion.
Cheers
Drew
Sent from my GT-I9300 using xda app-developers app
---------- Post added at 06:35 PM ---------- Previous post was at 06:32 PM ----------
flaviobd said:
what if kies tell me that my gti9300 does not support initialization?
Click to expand...
Click to collapse
Type it like this GT-I9300
It doesn't like lower case and you need to put the - in.
Drew
Sent from my GT-I9300 using xda app-developers app
Thanks for the tut OP, this has almost tempted me to try Kies! On a serious note, I'm bookmarking this and putting it in my "help me, I'm in the sh*t" folder!
slaphead20 said:
Thanks for the tut OP, this has almost tempted me to try Kies! On a serious note, I'm bookmarking this and putting it in my "help me, I'm in the sh*t" folder!
Click to expand...
Click to collapse
Trying S4 apps i very very nearly needed this .
jje
What to do with this message?
yubobster said:
What to do with this message?
Click to expand...
Click to collapse
Try unplugging your phone. Then open kies and follow the same steps add before without your phone plugged in.then plug it in in download mode when it says.
Sent from my GT-I9300 using xda app-developers app
lol love how you wrote this. Simple and easy to understand
pop-up window for starting upgrade freezes, and nothing can be seen, neither clicked
Hi,
First, compliments on making KIES actually looking workable!
BUT....I got to the point of the last pop-up window to install the update firmware, but this window opens blank (or see through to other windows that are elsewhere open), so I can not agree to nothing and neither continue.
I tried re-installing Kies, after totally de-install and cleaning up my computer etc, but effect is the same.
when I put my mouse below on the task-balk icone I can see the page in small, (not readable, too small for that), but in the pop up window nothing...
How can I fix this?? As I would prefer installing upgrade to JellyBean via KIES, rather than flashing with ODIN...
(Samsung Galaxy Ace 2, manufc Poland, bought in Greece, downloaded Kies via official site Samsung, computer windows Vista)
have you tried putting your phone in download mode before connecting to the computer? are your drivers installed correctly? lastly have you tried to upgrade using kies light? this uses less resources than the full version . allowing the program to update your software more efficiently. also once you connect the phone make sure not to move it or the micro usb cable or the computer. if anything is moved you may not be successful in upgrading due to a loose connection from the pc or phone or cable. If this doesn't work .try odin. Odin was created by samsng for internal use. It is faster and more reliable than kies. Just make sure KIES IS NOT RUNNING en flashing with ODIN. also regardless of which program you upgrade with . You should turn off your antivirus especially.as it can interfere with the update process.
Does this work on a s4 GT-I9505 international rooted phone (Australia)
i read in the tutorial it may cause problems but has anyone successfully updated a rooted 9505?
thanks jamie
phear13 said:
Does this work on a s4 GT-I9505 international rooted phone (Australia)
i read in the tutorial it may cause problems but has anyone successfully updated a rooted 9505?
thanks jamie
Click to expand...
Click to collapse
Hardly going to post S4 I9505 stuff in an S3 forum .
jje
i have a gt-s6312 and my android is not
hi
i have a gt-s6312 now my phone is causing a android problem what to doo
aaaa i think my phone android is curropted
now my android 4.1.2 is not opening but my phone is working only android is not opening what to do help me plssss
mnksngh706 said:
hi
i have a gt-s6312 now my phone is causing a android problem what to doo
aaaa i think my phone android is curropted
now my android 4.1.2 is not opening but my phone is working only android is not opening what to do help me plssss
Click to expand...
Click to collapse
This forum is not for your phone .
After attempting to root my ATT Note3 I have learn a few things. Hopefully my experience will help out some of you, and give new ideas to dev team.
1. ODIN. I realize the updated odin looks diff than the previous software. Firmware on Note3 has so much info that it needed to seperate everything. Plus Sammie might think that this will makes it harder to root the phone. I think they just made it easier
Here are my reason. After I got my phone stuck on bootload. It seem almost impossible to get the stock MJ5 firmware for the ATT. I spent so many hours on trying all kind of method on XDA forum. nothing seems to work out. At this point, I had nothing else to loose but my phone. So I decided give another manufacture firmware a shot. I downloaded TMobile stock firmware. Open ODIN, and loaded all the require MD5 into their perspective place. Hit start, and able to get my phone to loaded again. I had to use T-mobile sim card. Don't know what happen, but apperently, as long that you have all the correct data, ODIN will do the rest. I wanted to test this out further, so I download kitkat for tmobile. (i had to use one click.exe) because the other files doesn't have the MD5. I ran the ODIN that came with the file, but this time I use the Kitkat for ATT instead of TMOBILE. One click.exe install the ATT kitkat on my phone just fine. And now, after 2 days of downloading, and reading rooting article from XDA, droidview, etc. I think we can flash any rom using ODIN as long that you have all 5 MD5 files.Hope this help. I think i'm just lucky.
thanks for this...a lot people saying rooting is easy, but I don't think it is (at least compare to other devices)
Post video of process I'm curious to see this working as well as files needed, I have an AT&T note 3 and want to install T-mobile Rom.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Vi3tDroidz said:
After attempting to root my ATT Note3 I have learn a few things. Hopefully my experience will help out some of you, and give new ideas to dev team.
1. ODIN. I realize the updated odin looks diff than the previous software. Firmware on Note3 has so much info that it needed to seperate everything. Plus Sammie might think that this will makes it harder to root the phone. I think they just made it easier
Here are my reason. After I got my phone stuck on bootload. It seem almost impossible to get the stock MJ5 firmware for the ATT. I spent so many hours on trying all kind of method on XDA forum. nothing seems to work out. At this point, I had nothing else to loose but my phone. So I decided give another manufacture firmware a shot. I downloaded TMobile stock firmware. Open ODIN, and loaded all the require MD5 into their perspective place. Hit start, and able to get my phone to loaded again. I had to use T-mobile sim card. Don't know what happen, but apperently, as long that you have all the correct data, ODIN will do the rest. I wanted to test this out further, so I download kitkat for tmobile. (i had to use one click.exe) because the other files doesn't have the MD5. I ran the ODIN that came with the file, but this time I use the Kitkat for ATT instead of TMOBILE. One click.exe install the ATT kitkat on my phone just fine. And now, after 2 days of downloading, and reading rooting article from XDA, droidview, etc. I think we can flash any rom using ODIN as long that you have all 5 MD5 files.Hope this help. I think i'm just lucky.
Click to expand...
Click to collapse
You can root it using KINGO, but you can not do sim unlock using REGIONAL UNLOCK trick.
Vi3tDroidz said:
After attempting to root my ATT Note3 I have learn a few things. Hopefully my experience will help out some of you, and give new ideas to dev team.
1. ODIN. I realize the updated odin looks diff than the previous software. Firmware on Note3 has so much info that it needed to seperate everything. Plus Sammie might think that this will makes it harder to root the phone. I think they just made it easier
Here are my reason. After I got my phone stuck on bootload. It seem almost impossible to get the stock MJ5 firmware for the ATT. I spent so many hours on trying all kind of method on XDA forum. nothing seems to work out. At this point, I had nothing else to loose but my phone. So I decided give another manufacture firmware a shot. I downloaded TMobile stock firmware. Open ODIN, and loaded all the require MD5 into their perspective place. Hit start, and able to get my phone to loaded again. I had to use T-mobile sim card. Don't know what happen, but apperently, as long that you have all the correct data, ODIN will do the rest. I wanted to test this out further, so I download kitkat for tmobile. (i had to use one click.exe) because the other files doesn't have the MD5. I ran the ODIN that came with the file, but this time I use the Kitkat for ATT instead of TMOBILE. One click.exe install the ATT kitkat on my phone just fine. And now, after 2 days of downloading, and reading rooting article from XDA, droidview, etc. I think we can flash any rom using ODIN as long that you have all 5 MD5 files.Hope this help. I think i'm just lucky.
Click to expand...
Click to collapse
Could you please send me a PM or hit me up on hangouts? [email protected] I have some questions I need to ask you
Sent from my SM-N900A
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did this trip the Knox counter?
Sent from my SAMSUNG-SM-N900A using xda app-developers app
+1
Sent from my Nexus 10 using Tapatalk
15341 69996854
why not using kingo root?
Vi3tDroidz said:
After attempting to root my ATT Note3 I have learn a few things. Hopefully my experience will help out some of you, and give new ideas to dev team.
1. ODIN. I realize the updated odin looks diff than the previous software. Firmware on Note3 has so much info that it needed to seperate everything. Plus Sammie might think that this will makes it harder to root the phone. I think they just made it easier
Here are my reason. After I got my phone stuck on bootload. It seem almost impossible to get the stock MJ5 firmware for the ATT. I spent so many hours on trying all kind of method on XDA forum. nothing seems to work out. At this point, I had nothing else to loose but my phone. So I decided give another manufacture firmware a shot. I downloaded TMobile stock firmware. Open ODIN, and loaded all the require MD5 into their perspective place. Hit start, and able to get my phone to loaded again. I had to use T-mobile sim card. Don't know what happen, but apperently, as long that you have all the correct data, ODIN will do the rest. I wanted to test this out further, so I download kitkat for tmobile. (i had to use one click.exe) because the other files doesn't have the MD5. I ran the ODIN that came with the file, but this time I use the Kitkat for ATT instead of TMOBILE. One click.exe install the ATT kitkat on my phone just fine. And now, after 2 days of downloading, and reading rooting article from XDA, droidview, etc. I think we can flash any rom using ODIN as long that you have all 5 MD5 files.Hope this help. I think i'm just lucky.
Click to expand...
Click to collapse
I don't quite understand your claim on rooting - from what you describe you have just returned to stock UNROOTED firmware.
It would have been VERY interesting what bootloader you had while on TMobile ROM - the original locked MJ5 from AT&T or some TMobile (unlocked) bootloader.
And you are now on KitKat AT&T version, so maybe no downgrade will be possible.
s205702 said:
why not using kingo root?
Click to expand...
Click to collapse
I wouldn't use Kingo because we don't really know how they achieve root, and install SU on your phone. From my experience with Kingo when I softbrick the note 3. In my opinion, I think Kingo was the main source for softbrick. At the time, everything on my phone seems to check out ok. (recovery booting, safestrap, and chainfire SU) yet the phone wouldn't boot. So I think with unstable root access will affect your SU, and in my case it couldn't load safestrap, or finish the rest of the boot. My other reason is" I've heard Kingo sent ur call data to China". If I don't let my own apps collect info w/o my knowledge. I'm sure as hell, not gonna let an app send my data without me knowing.
lildoggs said:
Did this trip the Knox counter?
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
My knox still at 0x0. Like I said, for inexperience rooter like myself. I recommended using Odin for all you trouble since it verify your tar.md5 when you load it for flashing. Heimdall is also a good way of doing things, if you're good with ADB, and understand Linux. I use Odin whenever I can, unless the developer for a Roms, theme, install, etc require a different method.
We take risk when we root our phone, but that doesn't mean you can't choose the process that will minimize your risk. "Rooting is like having safe sex" . You take that .01% risk with a condom and look at all those babies in adoption. The same goes with your phone, and I can tell you there quite alot of Brickster out looking for help.
Vi3tDroidz said:
My knox still at 0x0. Like I said, for inexperience rooter like myself. I recommended using Odin for all you trouble since it verify your tar.md5 when you load it for flashing. Heimdall is also a good way of doing things, if you're good with ADB, and understand Linux. I use Odin whenever I can, unless the developer for a Roms, theme, install, etc require a different method.
We take risk when we root our phone, but that doesn't mean you can't choose the process that will minimize your risk. "Rooting is like having safe sex" . You take that .01% risk with a condom and look at all those babies in adoption. The same goes with your phone, and I can tell you there quite alot of Brickster out looking for help.
Click to expand...
Click to collapse
Damn this sounds mighty tempting. Can you post a tutorial or a video in detail on how you managed to put a tmodile rom without tripping the Knox counter? Everyone will thank you for it.
Sent from my SAMSUNG-SM-N900A using Tapatalk
s205702 said:
why not using kingo root?
Click to expand...
Click to collapse
I've had my brand new Note 3 for 5 days now. I rooted with Kingo...with no problems and then used safestrap for recovery. Sure when it comes to rooting there is always a risk but for anyone to say Kingo can't be used. .. that isn't true. I did my own research and used it
Sent from my SM-N900A using xda app-developers app
Yeah this needs some investigation if theres a way to load tmo stock firmware theres a chance u got an unlocked bootloader that would be a huge bounty for u and happy day for att note 3 users
Sent from my SM-N900A using xda app-developers app
So, due to recent events (probably really young kids spamming the threads of various dead or no-longer-maintained ROMs) I have decided to make this guide. for everyone.
THIS IS THE ROM YOU SHOULD BE USING: http://www.androidfilehost.com/?fid=23501681358542421
Unofficial CyanogenMod 11, compiled by @Unjustified Dev. dated june 4th, 2014.
Now, flashing this ROM is actually kinda difficult. We don't have an active official CM maintainer anymore and TWRP bricks people's phones. So here is the best method of flashing it. (disclaimer: if you're on the stock Samsung ROM, flash cm10.1 and refer to this guide if necessary. this is a clickable link.)
Now, after flashing cm10.1, follow these steps to flash cm11:
1. make a nandroid backup
2. wipe data/factory reset
3. flash cm11. you will probably get an error (probably along the lines of set_metadata_recursive). this is okay. reboot recovery. (advanced options in the main menu)
4. you might see some different bootlogos. this is a good sign. hopefully you'll see a clockworkmod version 6+. this is also a good sign.
5. repeat steps 2 and 3 and then flash whatever google apps package you want. the official one actually isn't bad. http://goo.im/gapps
After all of that, you should be good. If you do get bricked, fear not, you can always use Odin to flash the stock firmware again and use this guide if necessary: click here for the guide of wonderfulness
I dont actually own this phone anymore, so asking for help will probably get you nowhere. I'm sure Android L or whatever might be easier for us to work with unless the recovery devs have higher requirements for their stuff.
I was asking for a working link the other day for an old ROM.. Oh well, I am not a young kid though..This is what it will say when your successful. I rom'd a few times tonight on my kids phone and had no problems flashing through 4.2.2 to 4.4.2 ..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dee3 said:
I was asking for a working link the other day for an old ROM.. Oh well, I am not a young kid though..
Click to expand...
Click to collapse
nah man you're cool i was referring to a certain username inspired by a certain automobile distributor. of expensive, fast cars.
also that cm11 theme you have there is absolutely ridiculous. you know what it's called?
Fuster cluck its on my 6yo sons phone. He really likes all the flashy colors
---------- Post added at 06:23 PM ---------- Previous post was at 06:12 PM ----------
And thanks for the guide and the heads up last week on the cm11 stability. Its been a good ROM so far except I noticed I couldn't install the last update of minecraft PE 0.9.5 on my kids phone as he has had it since 4.2.2 running without issue. I tried to install the the zip on my phone too, got the files from apkgalaxy where I've been getting most paid apps for a while now. Only this ROM will not let minecraft install.. Weird.. when I didn't have this issue on DU 4.4.2, hellybean 4.2.2 , or avatar 4.2.2. And I also notice each time I download a zip from apkgalaxy as soon as I hit the download button, internet explorer and chrome both have issues closing out.. But I haven't noticed anything that would make me not want the ROM as its nice.
Is "flashify" the way to go now ? Or our tried and true method ? Just wondering .
Sent from my SCH-I500 using XDA Free mobile app
I used flashify to flash a kernel that wouldn't flash in recovery. Than I also got another phone that was on cwm 4.0.6.1 a 4.2.2 build I believe to flash through ROM manager when I kept getting can't mount errors when entering cwm recovery. I used the rom manager to push TWRP than got it onto the 4.4.2 unjust 6/04 build its on now after a few cm11 flashes. So there are a few ways to go about it at least for me I've used a couple different ways when I didn't have my laptop handy and would screw up or get errors. Google always fixes my problems as dumb as I am too this all after 4+years of rooting. Still learning..
icemanwbs said:
Is "flashify" the way to go now ? Or our tried and true method ? Just wondering .
Sent from my SCH-I500 using XDA Free mobile app
Click to expand...
Click to collapse
haven't tried flashify, plus i dont have this phone anymore, i upgraded to the s4. locked bootloader ;__;
Well, after many attempts I've only been able to get cm9 up and running. Tried first to Odin back to stock and then 10.1 ( using both droidstyles and the noob guide to kit Kat ) , also tried TWRP , without success. No idea what went wrong.
Sent from my SCH-I500 using XDA Free mobile app
Hmm. Try and get ROM manager pro .apk to flash a cm11
dee3 said:
Hmm. Try and get ROM manager pro .apk to flash a cm11
Click to expand...
Click to collapse
rom manager doesnt work on this phone.
icemanwbs said:
Well, after many attempts I've only been able to get cm9 up and running. Tried first to Odin back to stock and then 10.1 ( using both droidstyles and the noob guide to kit Kat ) , also tried TWRP , without success. No idea what went wrong.
Sent from my SCH-I500 using XDA Free mobile app
Click to expand...
Click to collapse
ok so when you flash cm11 using the cm10.1 clockworkmod image, it will give you an error. after that you have to reboot recovery and flash cm11 again
you have to flash it twice, especially when using clockworkmod. twrp i heard you can just flash once but you have to have a really recent version of twrp (2.6.3.0) and not only is that hard to come by for this phone but it can brick your phone.. i know that the cm11 kernel hhp made bricked my phone before, and i flashed that before cm11.. idk i probably wasnt supposed to
How doesn't ROM manager premium work on this phone? You know I'm dumb to all this so I take your advice serious on these things. I am asking because I used it to push TWRP when I kept getting constant can't mount errors when trying to flash the cm11 build on my sons phone when he was on a cwm 4.0.6.1 4.2.2 build I believe, and I couldn't flash a twrp rom without the can't mount . it got me through to the 6/04 unjust 4.4.2 after some unknown flashing around . I know I didn't follow a guide since I had errors and googled my can't mount errors
Last night/this morning I reflashed his phone down to the slimroms 4.2.2 7/08 build though due to mine craft not installing on cm11 4.4.2. I had no problems going from the 4.4.2 back to a 4.2.2 . I usually don't have problems that cause me to have to re Odin eh03 but when I started rooting I usually would Odin. Now its been all from recovery or the flashify and ROM manager I've used when rooting. No PC needed
dee3 said:
How doesn't ROM manager premium work on this phone? You know I'm dumb to all this so I take your advice serious on these things. I am asking because I used it to push TWRP when I kept getting constant can't mount errors when trying to flash the cm11 build on my sons phone when he was on a cwm 4.0.6.1 4.2.2 build I believe, and I couldn't flash a twrp rom without the can't mount . it got me through to the 6/04 unjust 4.4.2 after some unknown flashing around . I know I didn't follow a guide since I had errors and googled my can't mount errors
Last night/this morning I reflashed his phone down to the slimroms 4.2.2 7/08 build though due to mine craft not installing on cm11 4.4.2. I had no problems going from the 4.4.2 back to a 4.2.2 . I usually don't have problems that cause me to have to re Odin eh03 but when I started rooting I usually would Odin. Now its been all from recovery or the flashify and ROM manager I've used when rooting. No PC needed
Click to expand...
Click to collapse
well i think why the "rom manager doesnt really work" statement goes around is that people would try to flash cwm through rom manager and it would actually brick their phones. that didnt happen to me but i did try it and the recovery couldnt mount anything aka it was a bad recovery. but if it worked for you, hey, that's actually pretty cool. might not work for everyone though
OK maybe I've been out of the flashing loop to long lol. I am a recovering flash addict , I tried many if not all of the cool newest roms using droidstyles guide. Guessing now I just need the most recent files for cm10 and cm11.
Sent from my SCH-I500 using XDA Free mobile app
Thanks, skeptic. 5 days and no regrets with CM11. I've had some phantom keys, but stable so far. Looks like Unjust could get a substantial donation
Still no luck. Can't get the cm10.1 to install today. Keeps aborting. Frustrating to say the least.
Sent from my SCH-I500 using XDA Free mobile app
Damn. That is frustrating for sure. Its been a week and no luck, I can't help any more then I've read here and a few other fascinate forums. That's weird mine flashed to the CM11 without those errors on two devices mine and my sons. I took his from the 4.4.2 cm11 back down to a 4.2.2 ROM so he could play minecraft without using a computer/odin or usb for anything. I'm sure someone will help get it though.
Where do I get a stock ROM? I've tried many links but haven't been able to find one that works.
icemanwbs said:
Still no luck. Can't get the cm10.1 to install today. Keeps aborting. Frustrating to say the least.
Sent from my SCH-I500 using XDA Free mobile app
Click to expand...
Click to collapse
Have you ever thought that maybe we need the error to help you?
Im going to take a guess that its trying to read the build.prop and you wiped.
If so, then you need to remove the build.prop asserts from the updater-script
It shoudl be the first few lines.
Lgrootnoob said:
Have you ever thought that maybe we need the error to help you?
Im going to take a guess that its trying to read the build.prop and you wiped.
If so, then you need to remove the build.prop asserts from the updater-script
It shoudl be the first few lines.
Click to expand...
Click to collapse
he ended up fixing it :good:
i think he odin'd stock, then went to cm10.1, then to kitkat possibly using my method