Hey guys!!
I've been asked quite a few times, how to install the newest ROM for the GNex, the easiest way...
I've just tried it a few minutes ago, so I can tell you, waht it did and how to do it
Step 1:
Well, first things first;
you need the drivers. You'll want to download them from: here
Now, you need to download following file: Samsung official ROM
Step 2:
After you have downloaded both files and have installed the drivers, extract the firmware to a location, you can remember
eg.: %userprofile%\Downloads
Put the phone in Odin mode. Via USB Jig or VOL. DWN. + PWR. BTTN.
Once in Odin mode, plug phone in to computer via USB cable, wait for the drivers to install and then open the program. It may take up to 30 secs. to recognize the phone. Then click start. The flash process will take up to 3 Mins and will relock the bootloader, should you have unlocked it.
Final:
now just set your phone up and wait about five minutes, for the update notification to pop up... Now, everything is done, your phone is completely back to stock and nobody can tell you've messed around with it ^^
Though my personal favourite way of doing this, is with my root helper, but never mind about that (Click here to take a peek )
I hope you had fun doing this, I also hope you check out the 3rd link and I very much hope, I could teach you a bit more about the GNex ^_^
I am trying to follow your instructions but they do not work. After starting the drivers install, windows says it's installing drivers and then nothing happens.
Don't use ODIN. Follow any of the stickies at the top of the section on setting up adb and fastboot then flashing a factory build from there.
What xobx said
Sent from my Galaxy Nexus using Tapatalk 2
I've used both Odin and fastboot-method and have never had any single issue with them. Both works fine. If you have time to create tar packages everytime new factory image shows I don't see a reason why I should discourage you from using this tool.
m.kochan10 said:
I've used both Odin and fastboot-method and have never had any single issue with them. Both works fine. If you have time to create tar packages everytime new factory image shows I don't see a reason why I should discourage you from using this tool.
Click to expand...
Click to collapse
Because its a Samsung rather than Android tool and this is a Nexus device.
063_XOBX said:
Because its a Samsung rather than Android tool and this is a Nexus device.
Click to expand...
Click to collapse
And an unsupported tool, at that.
Sent from my Nexus
063_XOBX said:
Because its a Samsung rather than Android tool and this is a Nexus device.
Click to expand...
Click to collapse
Of course but when you reboot your Nexus into Odin/download mode it's technically no longer google's unique developer phone but it becomes a regular Samsung handset (with no download counter though). GNex is equipped with Odin mode not without a reason. This means manufacturer left the door open to use Odin flash as an alternative method. Of course it's not officially recommended but as long as it works fine as a second method I've got nothing against it. The more important here is whether odin flash is a safe and effective method. According to my experience.... it is. I mean I wouldn't recommend it as a primary method, but It's always good to know you have options just in case...
I use fastboot when I am on MacOS (definitely more often) and Odin whenever I flash firmware using Windows.
---------- Post added at 06:37 PM ---------- Previous post was at 06:09 PM ----------
bk201doesntexist said:
And an unsupported tool, at that.
Sent from my Nexus
Click to expand...
Click to collapse
Excuse me, not trying to be sarcastic but unsupported by who?
.... seriously?
Not supported by anyone actually: Google, Samsung, not even the community.
Sent from my Nexus
bk201doesntexist said:
.... seriously?
Not supported by anyone actually: Google, Samsung, not even the community.
Sent from my Nexus
Click to expand...
Click to collapse
Oh that's what you meant. Sure. Well It's kinda obvious that u use it at your own risk just like rooting or flashing anything to your device. I think that everybody is aware of that including OP. No intention to sound ignorant or impolite but this lack of official support is irrelevant for me. If I brick my handset using Odin, cwm, RUU or fastboot it's only me to blame.
m.kochan10 said:
Oh that's what you meant. Sure. Well It's kinda obvious that u use it at your own risk just like rooting or flashing anything to your device. I think that everybody is aware of that including OP. No intention to sound ignorant or impolite but this lack of official support is irrelevant for me. If I brick my handset using Odin, cwm, RUU or fastboot it's only me to blame.
Click to expand...
Click to collapse
Doesn't mean you should recommend that somebody use what is, frankly, an inferior tool. Even a toolkit (I just threw up in my mouth a little) is better than ODIN.
Thing is, if I flash through Odin, I can't say I did, either to Google or Samsung. They will reply that the official tool to reset device to factory state is fastboot. There's not even a mention to download mode. Its a leaked tool, the only way I see Odin as an option is if fastboot isn't available. And even then, I would rather use either Heimdall (which i don't believe supports our device) or OMAPflash.
Sent from my Nexus
No no, as I posted earlier, the primary tool is of course fastboot. It's not like I recommend using Odin. I'm just not a big opponent cos I've never had any bad experiences using it and thus I don't understand this (forgive me expression) fear of using it. If anybody asks me I recommend fastboot at the first place. (It takes even more time to create tar.md5 package in cygwin than to flash every single .img via terminal to be honest) But sometimes people can only enter odin mode using usb jig. Then odin flash seems to be the one and only option.
---------- Post added at 10:15 PM ---------- Previous post was at 10:05 PM ----------
bk201doesntexist said:
Thing is, if I flash through Odin, I can't say I did, either to Google or Samsung. They will reply that the official tool to reset device to factory state is fastboot. There's not even a mention to download mode. Its a leaked tool, the only way I see Odin as an option is if fastboot isn't available. And even then, I would rather use either Heimdall (which i don't believe supports our device) or OMAPflash.
Sent from my Nexus
Click to expand...
Click to collapse
I am not really proud of myself but why would you care about google or samsung, like honestly ? None of them will ever recognize the difference if you send your brick to their service center anyway ...and Heimdall is even less stable than Odin.
BTW. Did any of you notice that Odin flash unlocks your bootloader?
Related
Used to be an iphone addict, a pro at it xD Now I love android but I Have no clue on anything.
I found this post in developmental, but I can't post in it due to the "new member".
http://forum.xda-developers.com/showthread.php?t=1668476
It seem fairly easy to install since the files only contain 2 .exe , one for driver and one for install ics leak I guess?
I'm a noobie, I see some installin instruction but it's mainly for people who has already experience with android.
So anyone who has already installed this leak, can you give me the most dumbed down list of step possible? even like stuff how to enter a mode or button to press specifically.
does this need to be rooted to be install? thank you so much.
dustin4vn said:
Used to be an iphone addict, a pro at it xD Now I love android but I Have no clue on anything.
I found this post in developmental, but I can't post in it due to the "new member".
http://forum.xda-developers.com/showthread.php?t=1668476
It seem fairly easy to install since the files only contain 2 .exe , one for driver and one for install ics leak I guess?
I'm a noobie, I see some installin instruction but it's mainly for people who has already experience with android.
So anyone who has already installed this leak, can you give me the most dumbed down list of step possible? even like stuff how to enter a mode or button to press specifically.
does this need to be rooted to be install? thank you so much.
Click to expand...
Click to collapse
If I remember correctly, all you have to do is run the drivers and then put the phone in debugging mode. To do this, you go to applications, then development, then you'll be able to see it and click it. Then run the .exe and that's it.
Sent from my LG-P930 using xda app-developers app
The ICS leak is the easiest to install "ROM" ever. You don't even need root. Just run the exe file.
Now getting back from the leak because the battery only lasts 4 hours and the signal isn't as strong is the HARD part. And unfortunately, there is NO way to get completely stock again with the Nitro.
Even unbricking it leaves you with a rooted ROM that can't be updated through any official method (OTA nor LG Update Tool). Hell, I couldn't even find an unofficial way to update it after I unbricked it and stay stock. Only V10F is rootable, so nobody can get the IMG files off of V10i or V10j, so you get stuck at V10f if you want to stay stock. That's not necessarily a bad thing since I think V10j had issues with the baseband, but it might make it impossible to update to the stock ICS update when it comes out. Your only option at that point will be to either install CyanogenMOD or some other custom ROM. But if the official ICS ROM isn't rootable, you'll never be able to update to it.
---------- Post added at 10:13 AM ---------- Previous post was at 10:12 AM ----------
osmosizzz said:
If I remember correctly, all you have to do is run the drivers and then put the phone in debugging mode. To do this, you go to applications, then development, then you'll be able to see it and click it. Then run the .exe and that's it.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I don't think you even have to put it in debugging mode. Just let Windows install the drivers when you hook it up and run the exe file. It's an official updater so it shouldn't need debugging turned on. You do have to put it in PC Mode though.
And how do you put it in PC mode?
JINXR said:
The ICS leak is the easiest to install "ROM" ever. You don't even need root. Just run the exe file.
Now getting back from the leak because the battery only lasts 4 hours and the signal isn't as strong is the HARD part. And unfortunately, there is NO way to get completely stock again with the Nitro.
Even unbricking it leaves you with a rooted ROM that can't be updated through any official method (OTA nor LG Update Tool). Hell, I couldn't even find an unofficial way to update it after I unbricked it and stay stock. Only V10F is rootable, so nobody can get the IMG files off of V10i or V10j, so you get stuck at V10f if you want to stay stock. That's not necessarily a bad thing since I think V10j had issues with the baseband, but it might make it impossible to update to the stock ICS update when it comes out. Your only option at that point will be to either install CyanogenMOD or some other custom ROM. But if the official ICS ROM isn't rootable, you'll never be able to update to it.
---------- Post added at 10:13 AM ---------- Previous post was at 10:12 AM ----------
I don't think you even have to put it in debugging mode. Just let Windows install the drivers when you hook it up and run the exe file. It's an official updater so it shouldn't need debugging turned on. You do have to put it in PC Mode though.
Click to expand...
Click to collapse
When you plug it into your computer, it will pop up 4 options in your notification bar. PC mode is one of these options. It basically just allows LG software to see your phone.
Be careful. You are better off rooting your stock and installing cwm. Then you have options. With the leak, you are stuck unless you unbrick.
Sent from my LG-P930 using xda app-developers app
dnorthington is right on the money here. It will be a lot more work later if you choose the lazy route and use the 1-click installer right now. The other option is waiting for AT&T, but nobody wants that, right?
Sent from my LG-P930 using Tapatalk 2
Hey guys, im new to the scene, and while fiddling around with my Galaxy S3, i have managed to brick it! Here is what happened.
I rooted the phone using a tutorial from here:
http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Everything worked fine and the phone successfully rooted. But than i came across roms ... and i found a tutorial that told me how to install CyanogenMod 9:
http://forum.xda-developers.com/showthread.php?t=1778165
I tried to follow the instructions, but i would get (Error 7), and i realized that this tutorial instructed me to install the ClockworkMod Recovery version 5.8.4.7. So i downloaded the file from ClockworkMod's website, and it was in a .img format. When i had rooted my phone and installed ClockworkMod i used a .tar version via Odin, and this time i had a .img. After going through many tutorials, i found someone that showed how to install the .img varient via Android Terminal Emulator. So i followed the instructions:
http://forum.xda-developers.com/showthread.php?t=1363132
After i was finished following the instructions i rebooted the phone. And boom, it would not turn on. I tried all variants of holding the external buttons etc. Than i plugged the phone into a Windows PC. and the phone shows up in device manager as "QHSUSB DLOAD". So after tirelessly researching, i finally found the drivers for this and installed them. And know the phone shows up in Odin as COM10 in yellow. So i tried to flash the stock Image. I fire up Odin, select PDA, than the stock image, and click start. This is all that happens in the "Message Log":
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
(I have attached a screenshot of the above)
Please guys, i just got the phone and now it is bricked, any help would be greatly appreciated. Thanks!!
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Hi, Thanks for your reply. I tried using a "Jig" and it did not put the S3 into download mode. LIke i said previously. When the S3 is connected to my PC it shows up as "QHSUSB DLOAD". And no Samsung drivers would work with it. I had to research and find the drivers that finally worked and allowed Odin v1.85 to see the phone as "COM10", and i select the ROM under the PDA and click the "Start" button. But than it does not go past SetupConnection. I thought maybe the "Jig" was faulty and didnt work, but i tested it with another working Samsung Galaxy S2, and it worked exactly as it was supposed to. Should i still try your suggestion or is it pointless?
neubauej said:
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Click to expand...
Click to collapse
Ouch.
It sounds like your bootloaders might be borked, so kinda pointless.
I would get ahold of Josh at www.mobiletechvideos.com as it sounds like jtag might be required.
Hey, Thanks for the info. But the image i flashed via the Android mobile terminal app on the phone, i was flashing a ClockworkMod v5.4.8.1, that was made for the AT&T i747 (I have the Bell i747M, which i am told is the same thing?) , is that the bootloader? I know someone here that is local that does the jTag repair. But im not sure if the problem i have is in relation to the bootloader. Please let me know. As the phone still does show up when connected to the PC.
neubauej said:
Ouch.
It sounds like your bootloaders might be borked, so kinda pointless.
Get ahold of Josh at as it sounds like jtag might be required.
Click to expand...
Click to collapse
I tried your solution. The phone when connected to the PC with does not show up in Odin 3.07 (Correct version for my phone, from your link), But if i turn on Odin 1.85, the phone shows up fine in that as COM10 in yellow. So does my phone need a jTag? Samsung Canada told me to send the phone in for service and they will reset it and send it back. At the moment the phone does not turn on or go into download mode, and when connected to the computer it shows up as HS-USB QDLoader. So my question is: If i send it to Samsung, will they discover that i have Rooted it and void my warranty and not fix the phone?
neubauej said:
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Click to expand...
Click to collapse
If you send it to Samsung its unlikely they will notice or care that its rooted.
I have sent them 2 devices that I wanted them to reflash after I did stupid things and hardbricked, fully expecting to pay for it, and it was returned to me flashed and at no charge. This was after I told the customer service rep that I was flashing custom firmware and i screwed it up.
YMMV.
The worst case scenario there is they void your warranty and charge you a minimal fee to reflash it.
As for your bootloaders, you pushed a custom recovery that failed, corrupted, or was an incorrect application. The recovery lies in the bootloader..
If it doesn't power up, won't go into download mode, and Odin won't flash it I'd say its jtag or send it to sammy time.
I see, well i do not care if they charge me anything. Money is not an issue, Ok well i just got the email from Samsung with the shipping label. Thanks for your information.
neubauej said:
If you send it to Samsung its unlikely they will notice or care that its rooted.
I have sent them 2 devices that I wanted them to reflash after I did stupid things and hardbricked, fully expecting to pay for it, and it was returned to me flashed and at no charge. This was after I told the customer service rep that I was flashing custom firmware and i screwed it up.
YMMV.
The worst case scenario there is they void your warranty and charge you a minimal fee to reflash it.
Click to expand...
Click to collapse
Goodluck!
Fyi 5.4.8.7 is the clockwork version I'm running.
After doing some more research, i found that another person with a different Samsung phone. Followed the same instructions to flash ClockworkMod via Android Mobile Terminal using the same instructions i did and got the same problem. On his post somebody told him that the flash was made to the wrong partition or something like that. So ... Lesson for next time. READ EVERYTHING BEFORE TRYING IT!
neubauej said:
Goodluck!
Fyi 5.4.8.7 is the clockwork version I'm running.
Click to expand...
Click to collapse
Yeah just go to Samsung. Its too bad u never read that the newer versions of CWM recovery don't work on the 747m. The 747 and our m variants are close but still a bit different in a few ways although when coming here for rooms and stuff we have to use this at&t 747. Section. There is a great rooting post under the development stickies and it mentions the UNICERSAL VERSION OF CWM RECOVERY FOR 747m phones and that is the one I used and all of us 747m users should install. 5.4.0.4 or something like that. Definitely not 5.8.x.x. I could have told u that would brick your phone and most proper posts would too. And unfortunately yes the recovery resides in the boot loader area so it can cause a brick.. so keep that in mind when u get your phone fixed. Either use the earlier cwm rec version or just change to TWRP RECOVERY which I just did and many recommend now anyways.
Good luck and I'll come back to post the link with the best root and cwm rec install forOUR 747M phones and remember there are some differences and not all 747 mods will work for us so please read up first
Sent from my SGH-I747M using xda premium
pchemerys said:
Yeah just go to Samsung. Its too bad u never read that the newer versions of CWM recovery don't work on the 747m. The 747 and our m variants are close but still a bit different in a few ways although when coming here for rooms and stuff we have to use this at&t 747. Section. There is a great rooting post under the development stickies and it mentions the UNICERSAL VERSION OF CWM RECOVERY FOR 747m phones and that is the one I used and all of us 747m users should install. 5.4.0.4 or something like that. Definitely not 5.8.x.x. I could have told u that would brick your phone and most proper posts would too. And unfortunately yes the recovery resides in the boot loader area so it can cause a brick.. so keep that in mind when u get your phone fixed. Either use the earlier cwm rec version or just change to TWRP RECOVERY which I just did and many recommend now anyways.
Good luck and I'll come back to post the link with the best root and cwm rec install forOUR 747M phones and remember there are some differences and not all 747 mods will work for us so please read up first
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
I don't think the version he used was the issue as other Canadian users report that 5.8.x.x works fine.
http://forum.xda-developers.com/showthread.php?p=29664739
Edit: the link with instructions for terminal emulator on the op is for the lg thrill which writes the recovery onto block 6. On this phone it needs to be written to block 18.
Sent from my HTC One S using xda app-developers app
Frowben said:
I don't think the version he used was the issue as other Canadian users report that 5.8.x.x works fine.
http://forum.xda-developers.com/showthread.php?p=29664739
Edit: the link with instructions for terminal emulator on the op is for the lg thrill which writes the recovery onto block 6. On this phone it needs to be written to block 18.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Ah yes..that makes sense. That would pooch the phone. As for cwm it appears I was mislead as I read on few posts that newest versions don't work or not recommended for Canadian variant but it appears u might be right and I'm now seeing more and more report that it is installable. I'll have to check it out. Thanks
You flashed a recovery for the LG Thrill 4G. At what point in time did you assume it was the same phone as the I747M? You have bricked your phone. It needs JTAG service. Samsung will probably cover it under warranty, or you can pay someone that has the equipment to do it. You have no other options at this point. When you get it back from repairs, make sure you only flash AT&T/Bell/Telus/Rogers I747(M) software to the phone....
Ya i got the phone back from Samsung after waiting 3 weeks. They had to change the motherboard on the phone. Yes, it was the wrong instructions i followed which screwed me over! Since than i re-rooted how i did the first time i got the phone. Just a few days ago i saw the new CyanogenMod 10 M1 Rom, which i wanted to install. And again like last time in order to install it i had to upgrade my CWM to the newest version. This time i did not rush into it like last time and consulted with my buddy who is an expert in Android. The problem i had last time was i downloaded the new CWM in an .img file, and this time i ended up finding the newest CWM in a .tar and used Odin to flash it successfully. Than i just installed the rom and was good to go. My main reason for wanting to install a custom rom was i was getting absolutely HORRIBLE battery life from my S3. I ended up buying a juice pack which greatly helped me out. But now that i have CM10 my battery life is phenomenal, + the juice pack i now go maybe 2 days without having to charge. Now my sister who has the Wind Mobile S3 T999V wants me to upgrade her rom to the same as mine. I have found the T-Mobile CWM for her phone, and all the relevant software, but i am still hesitant to install the CWM on her phone. The T-Mobile CWM 6.0.1.2 is compatible with the Wind Mobile S3 T999V right? Or do i have to use a different version?
just to be clear about where you went wrong (im sure its been said already)
the guide you followed to install cwm is from the lg thrill forum. so the command dd if=... of=... had the wrong device id which is the most common cause of a brick
its actually pretty difficult to mess up your phone as long as you don't use mods designed for other devices
jefferson9 said:
just to be clear about where you went wrong (im sure its been said already)
the guide you followed to install cwm is from the lg thrill forum. so the command dd if=... of=... had the wrong device id which is the most common cause of a brick
its actually pretty difficult to mess up your phone as long as you don't use mods designed for other devices
Click to expand...
Click to collapse
Yes, i know that. I realized after i had done everything that the instructions where for another phone. Now im trying to find the CWM 6.0.1.2 for my sister phone T-Mobile S3 T999V that is in a .tar file already. Any suggestions on where i can get it?
I use cwm 5.8 .0.4 i think and it works fine go to the dev stickies and its there
Sent from my SAMSUNG-SGH-I747 using xda premium
JB calhoun said:
I use cwm 5.8 .0.4 i think and it works fine go to the dev stickies and its there
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Ya for my sisters phone i have that version as a flashable tar, however to install CM 10 M1 i need to install CWM 6.0.1.2.
Did u try rom manager
Sent from my SAMSUNG-SGH-I747 using xda premium
Hello,
I've noticed that my volume buttons have pretty much stopped working. I don't think it's ROM related, I'm on tmcode's AOKP rc2 ROM and tried going back to CM10 stable and the problem was still there.
Sometimes they'll work randomly, but they're pretty much a write off it seems. My phone is under a year old purchased from Bell.
I've unlocked, rooted the phone, flashed CWM and have flashed numerous ROMS.
I'd like to try and see if they'll give me a replacement, or fix it or whatever before I get a new phone, which most certainly won't be an LG phone, too bad about the Nexus 4...
What's the easiest way to bring the phone back to a stock state? Do you think if I just flash Bell's ICS ROM it'll be enough?
Thanks
you haven't given us much info... my p930 works fine (edit spelling) on cm10 stable... if yours still aren't working i'm guessing one of two things.
1. maybe your rom flashing procedure is lacking... ? are you doing proper data wipes before flashing new roms?
2. did you jolt your phone? if you smashed your phone from the side the volume buttons are on its easily the contacts could have been damaged.
either way i think if your flash count is that high your warranty is probably useless, unless there is some way to hide all those custom roms you flashed but there isn't as far as i know.
you can only hope your problem can be fixed by doing a proper wipe... just another thought... have you tried restoring a backup from CWM from before you experienced the problem? this should confirm weather it is a hardware or software issue.
KronicSkillz said:
you haven't given us much info... my p930 works fine (edit spelling) on cm10 stable... if yours still aren't working i'm guessing one of two things.
1. maybe your rom flashing procedure is lacking... ? are you doing proper data wipes before flashing new roms?
2. did you jolt your phone? if you smashed your phone from the side the volume buttons are on its easily the contacts could have been damaged.
either way i think if your flash count is that high your warranty is probably useless, unless there is some way to hide all those custom roms you flashed but there isn't as far as i know.
you can only hope your problem can be fixed by doing a proper wipe... just another thought... have you tried restoring a backup from CWM from before you experienced the problem? this should confirm weather it is a hardware or software issue.
Click to expand...
Click to collapse
What do you mean "flash count is that high?" I mean, if they really care about that, just update through the LG updater tool and they would never know you've been flashing all sorts of custom ROMs.. Which, if you think it MIGHT be a software problem, that might not hurt anyway; but I doubt it's software related..
lordcheeto03 said:
What do you mean "flash count is that high?" I mean, if they really care about that, just update through the LG updater tool and they would never know you've been flashing all sorts of custom ROMs.. Which, if you think it MIGHT be a software problem, that might not hurt anyway; but I doubt it's software related..
Click to expand...
Click to collapse
someone told me there was something can counts rom installs or something, they called it a flash count i'm trying to find the thread i read it on... it might be completely wrong
KronicSkillz said:
someone told me there was something can counts rom installs or something, they called it a flash count i'm trying to find the thread i read it on... it might be completely wrong
Click to expand...
Click to collapse
I see what you're talking about now. From what I can tell, it's on Samsung devices; I can't find any other references to it on any other brand... not saying that it isn't on anything else, but Samsung appears to not like people having full control of their device.
I don't think it's a software issue, I'm pretty sure it's hardware.
I know to do a full wipe when flashing between different ROMs.
My phones been dropped a couple times, nothing drastic though, that could have done it maybe. I've got a TPU (sp?) case on the phone.
What is the easiest way to bring the phone back to a stock state? LG GB/ICS ROM, un-rooted?
Thanks again
Sent from my LG-P930 using xda app-developers app
RealyPssd said:
I don't think it's a software issue, I'm pretty sure it's hardware.
I know to do a full wipe when flashing between different ROMs.
My phones been dropped a couple times, nothing drastic though, that could have done it maybe. I've got a TPU (sp?) case on the phone.
What is the easiest way to bring the phone back to a stock state? LG GB/ICS ROM, un-rooted?
Thanks again
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
You can try running the official LG update tool; I'm not sure if that will work without doing anything else... I KNOW it works if you flash v18f and then update with the official software. Basically, run through steps 1-5 of this guide: http://forum.xda-developers.com/showthread.php?t=2044645 and instead of doing anything after all that, just start the official update software and update to Official ICS.
" just start the official update software and update to Official ICS."
I'm using the Bell phone unlocked on Rogers, will I still be able to update to the official ICS ROM?
RealyPssd said:
" just start the official update software and update to Official ICS."
From within the phone it self? Or is it an application I download and run from my PC?
I'm using the Bell phone unlocked on Rogers, will I still be able to update to the official ICS ROM?
Click to expand...
Click to collapse
http://www.lg.com/us/support-mobile/lg-P930#manuals
B2CAppsetup.exe is the app you'll need.
pretty sure by official lg update software he's talking about the tool you run on your pc that autoupdates your phone.
http://www.lg.com/ca_en/support/mobile-support
is where you would find the tool, i'm not 100% positive on this more like 99% if you want confirmation you should wait for him to verify, but i know this is the official lg update tool.
---------- Post added at 06:37 PM ---------- Previous post was at 06:35 PM ----------
if you blocked the lg site from your hosts file like the (*edit* un) bricking guide tells you to, you'll have to remove that line from your hosts file (127.0.0.1 csmg.lgmobile.com) and flushdns in order to communicate with the lg servers again. just in case you run into this, i'll try to have your answer posted before you can ask the question
to flush dns open the run prompt, type cmd, hit enter, type ipconfig /flushdns
you should get a success message this has refreshed your dns and you should be able to communicate with csmg.lgmobile.com again.
---------- Post added at 06:42 PM ---------- Previous post was at 06:37 PM ----------
as per your 2nd question, i'm pretty sure you'll end up with A T&T but im not positive. however the at&t software will work if you enter your carriers APN settings, if you didn't write them down you can get them with a simple google search, go into mobile network settings on your phone select apn, then push the menu button and push new, then enter all your apn settings and your data should connect in a jiffy.
KronicSkillz said:
pretty sure by official lg update software he's talking about the tool you run on your pc that autoupdates your phone.
http://www.lg.com/ca_en/support/mobile-support
is where you would find the tool, i'm not 100% positive on this more like 99% if you want confirmation you should wait for him to verify, but i know this is the official lg update tool.
---------- Post added at 06:37 PM ---------- Previous post was at 06:35 PM ----------
if you blocked the lg site from your hosts file like the (*edit* un) bricking guide tells you to, you'll have to remove that line from your hosts file (127.0.0.1 csmg.lgmobile.com) and flushdns in order to communicate with the lg servers again. just in case you run into this, i'll try to have your answer posted before you can ask the question
to flush dns open the run prompt, type cmd, hit enter, type ipconfig /flushdns
you should get a success message this has refreshed your dns and you should be able to communicate with csmg.lgmobile.com again.
---------- Post added at 06:42 PM ---------- Previous post was at 06:37 PM ----------
as per your 2nd question, i'm pretty sure you'll end up with A T&T but im not positive. however the at&t software will work if you enter your carriers APN settings, if you didn't write them down you can get them with a simple google search, go into mobile network settings on your phone select apn, then push the menu button and push new, then enter all your apn settings and your data should connect in a jiffy.
Click to expand...
Click to collapse
Yeah, the official update tool. That's the one I'm talking about; both links end up going to the same program - B2CAppSetup.exe
Good point on the hosts file, that's pretty important.
thank you just trying to him this guy get his phone going
Alright, once I find a cheapo phone to use while my Nitro HD / Optimus LTE is being repaired, I'll give this a go.
I just want to bring it back to stock state to remove root so they won't deny my warranty.
I remembered after I posted about the "B2CAppSetup.exe " program on LG's site.
My hosts file is untoched, I'm on a new install of Windows 8, I un-bricked a few months ago.
Thanks again for all the help.
I can't really, reliably, enter recovery any more...
I might try flashing the v20f Bell ROM via ROM manager and then try unrooting with super one click.
I do still have the first CWM backup I made of the stock GB ROM as well that I could restore maybe in ROM manager.
Sent from my LG-P930 using xda app-developers app
So I flashed the original GB CWM / Nandroid backup I had made, then I tried un-rooting with SuperOneClick, but for some reason it wouldn't work.
So I used the LG software and updated to the official ICS release, Bell version, and the now the phone is un-rooted.
Time to send it off to hopefully get fixed.. what are the chances that I'll get my actual handset back? I've unlocked it, I'm betting I don't get mine back, but a locked one...
Thanks again for all the help
first of all you dont want yours back, the volume button issue is probably hardware, unless you flashed the wrong rom or a corrupted wrong or something. secondly if you updated to stock ics, your phone is already has a relocked bootloader, you should be so lucky as to get a brand new phone that you can unbrick in an hour...
*edit* unless there is some new security they are putting on the new ones but i haven't heard of such, it has always seemed to me they only implement security to the point where it will stop an unknowledgeable person from breaking the phone. the amount of software "leaks" suggest to me they don't really care if people that know what they are doing mod the phones. having said that they still won't replace a phone they know has been modded, for valid reasons, they shouldn't be responsible for things they didn't do to the phone.
So I got my handset back and the volume buttons have been fixed.
To get root and CWM recovery back is it easiest to just follow an unbrick guide?
Since the new Jelly Bean bootloaders have shown up, I see a lot of people talking about updating them. There are a few things I would recommend to do when flashing them. The first is the small, but present, danger that you can hard brick your phone. And I mean the "Need jtag to make it work" hard brick. Typically the cause of these bricks is an error or interruption of communications between the device and the computer. The other is mismatched or outright improper bootloaders.
Below is a list of things to decrease the possibility of permaborking. Keep in mind that following this list will not 100% remove the danger of flashing bootloaders, but will increase the chances of a successful flash.
Flashing bootloaders is dangerous. They are one of the few things that has the possibility of hard bricking your phone. For that reason, here are some good things to do to prepare for flashing them.
Have a good, reliable data cable. Interruption of communication between your phone and pc will most likely cause a hard brick with bootloaders.
Use a usb port on the back of your computer (or #1 on a laptop). Communication, again.
Have a jig. Not much help if you hard brick, but if you soft brick its very nice to have.
I personally flash bootloaders from a good laptop with a fully charged battery. If there is a power outage, the battery in the laptop will have saved my phone.
When flashing bootloaders,or anything with Odin, don't touch your phone after you connect it in dl mode until the phone reboots. Goes back to the communication issue.
For problems/tips on connection issues, look HERE
To determine which bootloader you have, check out this app:
https://play.google.com/store/apps/details?id=org.freeandroidtools.root_checker
To check your bootloader version
(thanks to KorGuy123 for the link)
For those that like to use Terminal Emulator, just type this:
HTML:
su
getprop ro.bootloader
Hi,
I know this is close to impossible, but still want to bring it up to see if anyone here knows.
My s3's USB port seems damaged physically or something. It charges fine, but it always shows unrecognized USB device when connecting to PC. No matter it is in download mode or booted mode and how hard I try(install updated USB driver, change PC etc. )
No the question comes - can I upgrade boot loader without USB? If not I will be stuck with older version of cm10.1 for ever
TIA
Sent from my SAMSUNG-SGH-I747 using xda premium
xlj1000 said:
Hi,
I know this is close to impossible, but still want to bring it up to see if anyone here knows.
My s3's USB port seems damaged physically or something. It charges fine, but it always shows unrecognized USB device when connecting to PC. No matter it is in download mode or booted mode and how hard I try(install updated USB driver, change PC etc. )
No the question comes - can I upgrade boot loader without USB? If not I will be stuck with older version of cm10.1 for ever
TIA
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
No, you need a usb port to do it. You might try using Heimdall, as it uses a different driver. If you use heimdall, you will need to do a lot of research as it operates a little differently than Odin.
Flashing Bell Galaxy S3 Bootloader on AT&T phone
Would it be possible to flash a SGH-I747M (Bell) bootloader on a SGH-I747 (AT&T). I would like to have the option to toggle LTE off when I am in a non LTE area without going through the Network Control option discussed on xda, as I have been doing.
If it's not the exact bootloader for your phone, don't flash it.
mrhaley30705 said:
No, you need a usb port to do it. You might try using Heimdall, as it uses a different driver. If you use heimdall, you will need to do a lot of research as it operates a little differently than Odin.
Click to expand...
Click to collapse
Maybe use Mobile Odin?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
It is not recommended to write bootloader with Mobile Odin. Furthermore, it just won't do it:
From Chainfire:
All partitions are supported, as are loose files, .tar files and .tar.md5 files. Mobile ODIN will even check the MD5 signatures before flashing. While in theory Mobile ODIN can repartition and flash EFS and bootloaders, it will cowardly refuse to do so, for your own safety.
mrhaley30705 said:
It is not recommended to write bootloader with Mobile Odin. Furthermore, it just won't do it:
From Chainfire:
All partitions are supported, as are loose files, .tar files and .tar.md5 files. Mobile ODIN will even check the MD5 signatures before flashing. While in theory Mobile ODIN can repartition and flash EFS and bootloaders, it will cowardly refuse to do so, for your own safety.
Click to expand...
Click to collapse
Awesome, gotcha. Learn something new every day.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
mi modelo is i747m telcel mexico which should flash
Obridgenut said:
Would it be possible to flash a SGH-I747M (Bell) bootloader on a SGH-I747 (AT&T). I would like to have the option to toggle LTE off when I am in a non LTE area without going through the Network Control option discussed on xda, as I have been doing.
Click to expand...
Click to collapse
I have no idea why you would have to do that. If you have your setting correct it will do it automatically. My does on Telus. Or did you follow some of the instuctions here and loaded a bad image to your phone. Best to flash a stock image to your phone that has been rooted and then use rom manger or goomanager to flash a recovery to your phone if you want one. I have a rooted stock rom and I no recovery as they are a waste of time. I used triangle to reset the trip and I can update OTA with no issues and it states my devise status is normal. I had used some other rom on my phone and it drained the battery all the time. Now it works like a charm. I can even use back track or other linux distro's on it,
As for the other guy having an issue, you can update your phone over Kies. Your issues sound like its a bad rom you put on your phone. And you can never brick your phone. Its what people to say to scare you to get you to use their methods.
Is it possible that installing a custom rom would have installed the latest bootloader. I didn't install myself and it looks like I have the latest per the device info app I downloaded from the play store
Sent from my SGH-I747 using xda premium
osmxgohan said:
mi modelo is i747m telcel mexico which should flash
Click to expand...
Click to collapse
The correct firmware from your provider should have bootloader in then
andy_d0 said:
Is it possible that installing a custom rom would have installed the latest bootloader. I didn't install myself and it looks like I have the latest per the device info app I downloaded from the play store
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
It's possible that the ota update to jelly bean pushed the latest bootloader to your phone.
TheStrokerace said:
I have no idea why you would have to do that. If you have your setting correct it will do it automatically. My does on Telus. Or did you follow some of the instuctions here and loaded a bad image to your phone. Best to flash a stock image to your phone that has been rooted and then use rom manger or goomanager to flash a recovery to your phone if you want one. I have a rooted stock rom and I no recovery as they are a waste of time. I used triangle to reset the trip and I can update OTA with no issues and it states my devise status is normal. I had used some other rom on my phone and it drained the battery all the time. Now it works like a charm. I can even use back track or other linux distro's on it, ]
The AT&T SGH-I747 does not offer the option to toggle LTE off under the Settings Menu, as do the Bell, Telus etc SGH - I747Ms. And although I can and have flashed all sorts of different ROMs, the AT&T modem is RAT locked and I so far have been unsuccessful flashing any modems other than AT&T modems. I am not sure whether this is a software issue or whether it is to do with the AT&T bootloader, hence the question about flashing a Bell bootloader. Any time that I try to flash a non-AT&t MODEM, I temporarily lose my IMEI number and the phone will not work at all. But there is a work around by entering into the Phone Control settings as discussed on xda, ( http://forum.xda-developers.com/showthread.php?t=2116346) which I have been using successfully.
Click to expand...
Click to collapse
I don't think changing the bootloader will change that for you.
mrhaley30705 said:
I don't think changing the bootloader will change that for you.
Click to expand...
Click to collapse
OK, Thanks anyway for your help.
How can I tell what version my bootloader is?
Hey all~
1st, my internet is so sluggish today, I can almost do nothing on the forums, so if this is a repeat question, forgive me, simply reply with the link please.
What I would like to know is how can I find out what version my bootloader is?
I am running CM 10.0 Stable on my Galaxy S3 i747 [AT&T]
I want to update to 10.1 RC4, but I've read warnings relating to the old version of the bootloader, but nothing saying how to tell what version bl I have ...
suggestions?
Thanks
~Jason
ubuntujason said:
Hey all~
1st, my internet is so sluggish today, I can almost do nothing on the forums, so if this is a repeat question, forgive me, simply reply with the link please.
What I would like to know is how can I find out what version my bootloader is?
I am running CM 10.0 Stable on my Galaxy S3 i747 [AT&T]
I want to update to 10.1 RC4, but I've read warnings relating to the old version of the bootloader, but nothing saying how to tell what version bl I have ...
suggestions?
Thanks
~Jason
Click to expand...
Click to collapse
Install this, hit check, goto second screen and it'll say bootlader
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Easiest way to check is install terminal emulator.
Type
su
Grant it permission
Now type:
getprop ro.bootloader
These commands are case sensitive, so type carefully
Hello, my brother have a nexus 5x and one day after a night his phone stop working, it could only enter to download mode, now sometimes it cant even get there, what can i do, its been like 2 weeks since that
Could be the solder issue, there's loads of posts and thread about that. If it is and you're out of warranty, you're also sol. Sorry
Sent from my Nexus 5X using Tapatalk
berndblb said:
Could be the solder issue, there's loads of posts and thread about that. If it is and you're out of warranty, you're also sol. Sorry
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I looked into that, but is it normal that the phone go to a bootloader, then to download mode and after that get stuck in the google animation?
No, it's not normal. But if that is consistent it's probably software and fixable. Try the lgup tool to flash the firmware and/or flash the latest OTA in adb.
See if you can get into recovery from the bootloader.
If you can, flash the full OTA from the Google website in adb. You need neither an unlocked bootloader nor USB debugging enabled for it. Just as long as you use the official Google software.
If you do not have adb in recovery, use the lgup tool. For me it did not fully reflash the phone, something always failed, but it gave me adb in recovery when I did not have it before. Saved my bacon...
If neither helps or applies I'm fresh out of ideas, sorry.
I'll look for the thread I found helpful and add the link later.
Here you go, loads of good leads in this thread
https://forum.xda-developers.com/showthread.php?p=71588229
berndblb said:
No, it's not normal. But if that is consistent it's probably software and fixable. Try the lgup tool to flash the firmware and/or flash the latest OTA in adb.
See if you can get into recovery from the bootloader.
If you can, flash the full OTA from the Google website in adb. You need neither an unlocked bootloader nor USB debugging enabled for it. Just as long as you use the official Google software.
If you do not have adb in recovery, use the lgup tool. For me it did not fully reflash the phone, something always failed, but it gave me adb in recovery when I did not have it before. Saved my bacon...
If neither helps or applies I'm fresh out of ideas, sorry.
I'll look for the thread I found helpful and add the link later.
Here you go, loads of good leads in this thread
https://forum.xda-developers.com/showthread.php?p=71588229
Click to expand...
Click to collapse
Thank you sooo much, i will try this and the ill tell you how it end up:good: