[Q] Anyone having problems with latest update: I317UCAMC3 - AT&T Samsung Galaxy Note II

Long time lurker new poster:
I have a stock AT&T Galaxy Note II (never rooted or modified) which has been working fine until a couple of days ago. Last week the micro USB port stopped working and would not charge the phone. I was able to get a replacement dock and installed it two days ago. Everything seems to be working just fine. Yesterday I got the notice for the update from AT&T and I upgraded. Everything seemed to go well but as of last night my reception has gone to crap.
Where I used to have 4 bars I now only get two. If I don't touch the phone text messages will come in but touching the phone makes my reception go to zero (this is w/o moving the phone physically, simply dialing a number on the keypad will cause the phone not to work) and in general the phone is useless even when it shows one or two bars as no calls go through and no data comes through. My BT, WiFi, and GPS are unaffected. Everything else on the phone works and performs as expected.
At first I suspected a HW problem. So I opened up the phone inspected the 4G antenna and the contacts. Everything looks good and frankly I did not touch them in anyway so I would have been surprised if there was an issue. all the connectors to the motherboard have been reseated firmly. Even though it shouldn't affect the reception I switched back to my old (broken) micro-usb dock with no changes in my reception problems. This leads me to suspect a SW problem. I've tried booting into safe mode and have the same results.
Maybe the new FW w/ the new modem kernel broke something? Is anyone else experiencing, or has heard of, problems with the new update? If so I'd like to flash an older revision of the stock FW. Would this cause the phone to be wiped (i.e. would I have to reinstall all of my programs/data)? Is it even possible to downgrade w/o rooting the phone?
TIA for any help and sorry for the long post.

Downgrade without rooting the phone is not possible without losing data...sadly.
Regarding reception issues, we have had a select few reporting a reduction in signal strength.
I for one have an increase in signal with no degradation in performance.
I suppose it's possible that your repairs could contribute to the issue, but that seems unlikely.
We do have a fully stock UCAMA4 build that uses pre loaded root. It is pushed via Odin and will not raise the flash counter or show a modified status.
You could push the image to regain a pure build, then un install super user from within the app to be fully stock again.
There is currently no way to downgrade without losing data. ...
I've used the method several times with success. ..
The thread is titled. .."how to root without tripping your flash counter"....and is located in the development section. The thread was created by Mr. Robinson.
http://forum.xda-developers.com/showthread.php?t=2004650
The method will work. ...If a downgrade is your next step. ...g

Thanks for the info and linkage. I am not against rooting my phone. I just never went down the route because I wanted to avoid having any headaches with the phone. I'd like one gadget in my life just to work w/o me tweaking it/over clocking it/customizing it/etc. Alas it is not to be.
I followed the instructions on the other thread but it failed to flash my phone. Here is what Odin reported:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I317UCAMA4.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried a couple of times with the same results. TIA for any help.

Shadow Lord said:
Thanks for the info and linkage. I am not against rooting my phone. I just never went down the route because I wanted to avoid having any headaches with the phone. I'd like one gadget in my life just to work w/o me tweaking it/over clocking it/customizing it/etc. Alas it is not to be.
I followed the instructions on the other thread but it failed to flash my phone. Here is what Odin reported:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
root66_ATT_I317UCAMA4.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:9)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
I tried a couple of times with the same results. TIA for any help.
Click to expand...
Click to collapse
I believe you need to delete the .md5 off the end after the .tar to make it happen cappen'
Then try it again
Sent from my SGH-I317 using xda premium

roughneckboren said:
I believe you need to delete the .md5 off the end after the .tar to make it happen cappen'
Then try it again
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
No luck there either:
Code:
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Shadow Lord said:
No luck there either:
Code:
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You are in download mode right?
Sent from my SGH-I317 using xda premium

Yes. I get the warning, press up volume to confirm and then I get the android logo and it says "Downloading, Do not turn off target". Do I need ot do anything before hand? On another page I read you need to set the phone into USB debug mode before entering DL mode. Which doesn't make sense to me, and the instructions for the rooted FW did not mention so I did not.

Shadow Lord said:
Yes. I get the warning, press up volume to confirm and then I get the android logo and it says "Downloading, Do not turn off target". Do I need ot do anything before hand? On another page I read you need to set the phone into USB debug mode before entering DL mode. Which doesn't make sense to me, and the instructions for the rooted FW did not mention so I did not.
Click to expand...
Click to collapse
You are putting it in the PDA section right?. I once had firmware that wouldn't flash with odin so i downloaded another one and it would flash perfectly. You may try that.

You NEED to have usb debugging enabled if youre going to root, or flash any rom etc. There is no maybe about it.
Also its a good idea to tick 'allow unknown sources'
As well.
If you are stock and unrooted you shouldnt even be messing with odin especially if you are unsure about what should be ticked on the homescreen of odin.
This is exactly why I always tell people to root and make a recovery.
This new fw update seems to be giving some people headaches.
Your best bet is to follow the kies efr if you click web view theres a guide in my signature.
Gl.

I'm confused here... If you have a bone stock device and the usb port goes out why not have it replaced under warranty? And I would be taking all your other issues to the carrier I bought it from.
I see too many people trying to fix their own HW failures when the phon Whas a warranty.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

freakboy13 said:
You NEED to have usb debugging enabled if youre going to root, or flash any rom etc. There is no maybe about it.
Also its a good idea to tick 'allow unknown sources'
As well.
If you are stock and unrooted you shouldnt even be messing with odin especially if you are unsure about what should be ticked on the homescreen of odin.
This is exactly why I always tell people to root and make a recovery.
This new fw update seems to be giving some people headaches.
Your best bet is to follow the kies efr if you click web view theres a guide in my signature.
Gl.
Click to expand...
Click to collapse
Apparently you do not. I rebooted my PC and everything worked like a charm as it was supposed to/alluded to. don't ask me why but I'd guess windows and the Smasung drivers were not ready to play nice until a second reboot. I am up and running with the old(er) FW and I have the SuperSU application installed. I am at work currently where my reception is always crappy so I have to wait for the drive home to see how the phone behaves. Will report back later tonight if things improved or not by going back to I317UCAMA4.

LittleRedDot said:
I'm confused here... If you have a bone stock device and the usb port goes out why not have it replaced under warranty? And I would be taking all your other issues to the carrier I bought it from.
I see too many people trying to fix their own HW failures when the phon Whas a warranty.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Number of reasons (none of them real good). In retrospect it may have been wiser to send it to Sammy but if this is truly SW related I would have started to have the same problems when I got my phone back. I would now be blaming Samsung's repair and need to send it back to them again starting the back and forth loop w/ tech support which would have wasted time because the problem was something entirely different.
Honestly the phone has not been very impressive to me. I may have a lemon but this is the third "issue" I have had w/ it. A while back the WiFi and BT radios refused to turn on. Called Samsung support and they were more then useless. I finally fixed the issue by turning them on in safe mode and then it started working again. Then the dock failed in the middle of the night (went to bed, phone was set to charge and was charging, woke up and phone was only partially charged - the dock stopped working from that point on). And now this.
I know the other problems are relatively common and I'd be interested to see if more people start reporting problems with this update in the next week or so.

LittleRedDot said:
I'm confused here... If you have a bone stock device and the usb port goes out why not have it replaced under warranty? And I would be taking all your other issues to the carrier I bought it from.
I see too many people trying to fix their own HW failures when the phon Whas a warranty.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
This is exactly what I said to myself. if you never rooted your device you should have brought it back for a replacement under warranty.
I had the same trouble when trying to flash a stock ROM. I had the same failure. Check the link below.
http://forum.xda-developers.com/showthread.php?t=2260948

Shadow Lord said:
Apparently you do not. I rebooted my PC and everything worked like a charm as it was supposed to/alluded to. don't ask me why but I'd guess windows and the Smasung drivers were not ready to play nice until a second reboot. I am up and running with the old(er) FW and I have the SuperSU application installed. I am at work currently where my reception is always crappy so I have to wait for the drive home to see how the phone behaves. Will report back later tonight if things improved or not by going back to I317UCAMA4.
Click to expand...
Click to collapse
Glad you got it working. :thumbup:
Sent from my SGH-I317 using xda premium

Okay w/ the phone flashed back to the older FW the radio seems to be working. Frankly it is a 100x better then it was yesterday with the latest FW. I am not sure if it is back to the way it was before but that could just be in my head: i.e. I am constantly looking at the signal bars so I maybe thinking there is a problem where there really isn't any. In either case I can use the phone again to make calls, text messages are coming through, and data seems to be working. I have to live with it for a week or so before I can say it seems fixed. A few questions:
1. Is there anyway to permanently reject the upgrade? The phone has tried to send me the update once more already. It would be nice if I could skip this one permanently.
2. If I want to go fully stock can I just remove the SuperSU application or do I need to do something else to remove the root?
3. If I am staying stock is there any benefit to having my phone rooted? I guess a VNC server but anything outside of that?
Thanks to everyone for their help.

For pure stock. ...simply go into the super user apk and select the full unroot option. Then a data and cache wipe in the stock recovery will ensure a clean device.
However, if you wish to keep UCAMA4 as your primary build with no update prompt, you could download the pro version of titanium backup. .. (rooted application)...paid version, and freeze the update app.
This would prevent the repeat prompt to update, but root must remain. ..g

gregsarg said:
For pure stock. ...simply go into the super user apk and select the full unroot option. Then a data and cache wipe in the stock recovery will ensure a clean device.
However, if you wish to keep UCAMA4 as your primary build with no update prompt, you could download the pro version of titanium backup. .. (rooted application)...paid version, and freeze the update app.
This would prevent the repeat prompt to update, but root must remain. ..g
Click to expand...
Click to collapse
Thanks! I guess I will be setting up that VNC server as well

Related

[Q] issues with odin, pit, and modem. bricked. please help.

so i had the flashable version of dk28. it hasnt worked out the way i thought it would. since i got my laptop fixed, i thought i might as well odin back to stock with the new 2.2.1 modem and pit. got the correct files from xda. put phone in download mode and plugged in. then followed given instructions from there.
heres my result:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> modem.bin
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
where exactly did i go wrong here? and how do i fix this?
because of this failure, my phone is now bricked.
i really need help and fast because i have no other phone or way of contacting people. and ill be on a charter bus from atl back to orlando tomorrow (or in a few hours) and id like to have my phone up and running by then.
thank you in advance.
EDIT: so i have attempted this multiple times. this latest time around, i re downloaded odin 1.61 and im in the process (3 hour dl...) of dl the dk28 .tar again.
with the re dl of odin and its pit, i am getting:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> modem.bin
...but then it just hangs there.
We need more details like size and exact name of the files u used and does your phone go into download mode and how does it look if you try to turn the phone on normally.
Sent from my SPH-D700 using XDA App
Boot back into Download mode again, and try, try again, doing a battery pull and restarting Odin each time you attempt to flash the modem. Also, try downloading the modem.bin again, just to make sure it is complete... upon right clicking on the DK28 one I have that I know works, and selecting properties, it is 15,597,728 bytes (may not be as good as a md5 sum, but it is something easy to do).
Another thing you can try, if it failed right away without doing anything, is to flash with Odin again using only the pit file. That may allow you to boot the phone to the way you had it before.
I can't do much now but here are some trouble shooting options you can try.
Make sure ur tar file is 255mb I believe.
Make sure the extension is Tar and not mk5.
I can't really think of any thing else but I remember that there was another thread like this a few weeks back in the general section you might want to try checking that out. I think it had a weird name I can't remember. My lack of sleep is finally getting to me sorry.
Sent from my SPH-D700 using XDA App
gtuansdiamm said:
We need more details like size and exact name of the files u used and does your phone go into download mode and how does it look if you try to turn the phone on normally.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
i used the 3 links under "before you start" in the first post on http://forum.xda-developers.com/showthread.php?t=864445 (viper rom).
opening the extracted folder, the names i see are "Odin3+v1.61", "modem.tar", and "victory_8G_100528.pit".
phone goes into download mode without a problem. when i try to boot it normally, all i get is an icon that has a phone on the left, a yellow triangle with an "!" in it, and a computer on the right.
Koadic said:
Boot back into Download mode again, and try, try again, doing a battery pull and restarting Odin each time you attempt to flash the modem. Also, try downloading the modem.bin again, just to make sure it is complete... upon right clicking on the DK28 one I have that I know works, and selecting properties, it is 15,597,728 bytes (may not be as good as a md5 sum, but it is something easy to do).
Another thing you can try, if it failed right away without doing anything, is to flash with Odin again using only the pit file. That may allow you to boot the phone to the way you had it before.
Click to expand...
Click to collapse
ive repeated this process numerous times already, to no avail.
you said "modem.bin". what i downloaded reads "modem.tar". is that the same thing? as i said, im in the process of re dl the modem. but it says it will be finished in 4 hours. like hell im waiting that long.
when accessing the properties of my "modem.tar", it says it is 14.8 MB (15,605,760 bytes). which seems comparable to you files size.
gtuansdiamm said:
I can't do much now but here are some trouble shooting options you can try.
Make sure ur tar file is 255mb I believe.
Make sure the extension is Tar and not mk5.
I can't really think of any thing else but I remember that there was another thread like this a few weeks back in the general section you might want to try checking that out. I think it had a weird name I can't remember. My lack of sleep is finally getting to me sorry.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
255mb seems way too big. as i said, my tar reads 14.8mb. and the extension is .tar.
i just tried to use odin with only the pit file and i clicked start and it did absolutely nothing. it just sat there like i never even clicked start.
Did you uncheck F.Reset Time ?
I did the same thing to my phone before I realized that I had to do that.
NateWhite said:
Did you uncheck F.Reset Time ?
I did the same thing to my phone before I realized that I had to do that.
Click to expand...
Click to collapse
yes, i read that the only thing that was to be checked is auto reboot. so yes, i unchecked f. reset time. in my later tries though, i left it checked to see if it would work. but either way, i still havent gotten this thing to work.
Ok, if you have the modem.tar, I believe you need to place that in the PDA section, while if you open the .tar file with winrar (or equivalent) you can extract the modem.bin file and place that in the PHONE section instead.
You have the wrong file. You need the rom file for doing a rom flash. You are just trying to flash the modem. Use this and get the di18 file and put that into the pfa section, uncheck reset time and dont insert the pit. Just the rom tar file and hit start. Once again just make sure only auto reboot is checked.
http://forum.xda-developers.com/showthread.php?t=794138
Sent from my Evo killer!
Koadic said:
Ok, if you have the modem.tar, I believe you need to place that in the PDA section, while if you open the .tar file with winrar (or equivalent) you can extract the modem.bin file and place that in the PHONE section instead.
Click to expand...
Click to collapse
okay, just did that. but its hanging once again at:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> modem.bin
musclehead84 said:
You have the wrong file. You need the rom file for doing a rom flash. You are just trying to flash the modem.
Sent from my Evo killer!
Click to expand...
Click to collapse
please elaborate and explain and feel free to post links to what i should be using.
EDIT: thank you. ill check that out right now and report back.
It sounds like you are only trying to install the modem with Odin? I would suggest downloading the full DK28 tarball from this post: http://forum.xda-developers.com/showthread.php?t=794138
When you use it with Odin it goes in the 'pda' slot, you can leave the 'pit' slot blank.
Just edited my last post cjeck it oit
Sent from my Evo killer!
Just use that tar file from that link either di18 or dk28 depending on if you want eclair or.froyo and it will work. I use it all the time and dont use the pit file. It can cause it to fail. Good luck.
Sent from my Evo killer!
leatherneck6017 said:
It sounds like you are only trying to install the modem with Odin? I would suggest downloading the full DK28 tarball from this post: http://forum.xda-developers.com/showthread.php?t=794138
When you use it with Odin it goes in the 'pda' slot, you can leave the 'pit' slot blank.
Click to expand...
Click to collapse
musclehead84 said:
Just use that tar file from that link either di18 or dk28 depending on if you want eclair or.froyo and it will work. I use it all the time and dont use the pit file. It can cause it to fail. Good luck.
Sent from my Evo killer!
Click to expand...
Click to collapse
well once again, i play the waiting game. a direct dl from multiupload says it will be finished in 3 (now 4?) hours. yeah, i cant wait that long but it would seem that i have to.
thank you both (and all) for helping. im pretty sure that this will work, just waiting for now. will report back whenever i can with the results.
i know this sounds silly but, after each failure switch to a new usb port. i dont know why this makes a difference but when i flashed roms on my phone it worked the first time. but later i flashed my girlfriends phone and i thought i bricked it ( was failing for 2 hours) so i decided to try different usb ports and once i found the right one , it flashed nice and fast.
fromchaos0646 said:
well once again, i play the waiting game. a direct dl from multiupload says it will be finished in 3 (now 4?) hours. yeah, i cant wait that long but it would seem that i have to.
Click to expand...
Click to collapse
Wow you must have a slow connection! I just clicked the direct d/l link and am getting 1.2 Mbps using 'downloadthemall!' add-on for Firefox. Anyway, yeah it'll be worth the wait. Let us know how it goes.
Ok, while your waiting, go ahead and use the modem.tar that you have, place that in the PDA section, dont use a pit file, and then try to flash it. Worst case scenario, you have to wait for the full DK28 tar file to download anyway.
zombiematt said:
i know this sounds silly but, after each failure switch to a new usb port. i dont know why this makes a difference but when i flashed roms on my phone it worked the first time. but later i flashed my girlfriends phone and i thought i bricked it ( was failing for 2 hours) so i decided to try different usb ports and once i found the right one , it flashed nice and fast.
Click to expand...
Click to collapse
huh interesting. yeah ive noticed that before. i will try that when the new .tar is finished downloading.
leatherneck6017 said:
Wow you must have a slow connection! I just clicked the direct d/l link and am getting 1.2 Mbps using 'downloadthemall!' add-on for Firefox. Anyway, yeah it'll be worth the wait. Let us know how it goes.
Click to expand...
Click to collapse
apparently so. this hotels so called "high speed" internet is getting on my nerves. if it doesnt finish downloading by the time we get on the bus in a few hours, ill just wait until i get home to use my connection.
Koadic said:
Ok, while your waiting, go ahead and use the modem.tar that you have, place that in the PDA section, dont use a pit file, and then try to flash it. Worst case scenario, you have to wait for the full DK28 tar file to download anyway.
Click to expand...
Click to collapse
see first post on the second page.
and i guess ill have to wait. its fine, as long as everything works out in the end.

Not able to go back to stock ROM - Samsung Galaxy S2

Phone: Samsung Galaxy S II Epic 4G Touch - SPH-D710
Carrier: Sprint
Odin version: Odin3-v1.85
Stock image name: HOME_SPH-D710_EK02_CL704398_user.tar
I've tried to use the instructions & stock image posted here and encountered a problem.
When I run Oden, it just sits there at the point where it tries to establish a connection.
I've seen it get a few steps further, and then stall at trying to push an image to the phone.
This is as far as it gets:
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> Sbl.bin
<ID:0/004> zImage
<ID:0/004> factoryfs.img
Then it just sits there. I'm now currently in a bricked state, so I'm extremely open to suggestions
Just realized that this probably should have been posted in the Q&A. Sorry!
Take the battery out, the external SD card (if you have one insert), get a different micro USB cord, then try odin again.
Its usually just the new/different USB cord that does the trick.
If not, try re-downloading the tar, you might have got a bad download.
Close Odin from the red box in the corner then disconnect and pull battery. Put it back and try to go back into download mode. If your phone has any signs of life, it can be saved. I also always Odin with at least 60% battery just to be safe. Also, what Broded said may be the case. It could be a bad download of the tar. It seems like its hanging at the beginning which is much better than hanging in the middle or end
Sent from my Nexus S 4G using xda premium
That one doesn't use an md5 checksum to protect against file corruption. It does have one, but for some reason the file got renamed so it doesn't get used.
If you use the one from my signature, it will not start flashing unless the file contents are verified to be in the proper condition.
Take their advice and redownload the tar file. Get The one that has the .md5 at the end. This will make sure the file is nit corrupted
Sent from my Nexus S 4G using xda premium
Thanks everyone for the replies. I was kind of worried that I'd come back to a bunch of links to the you are a noob video
So I followed the suggestions in this thread including:
I pulled the SD card
The EK02 ROM listed on sfhub's sig w/ MD5.
Switched USB cables & ports on the computer.
Odin still seems to get stuck in the same "SetupConnection.." spot.
From the logs:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710.EK02_CL704398_ROM_PDA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
I think next I will try this on another PC. Maybe a fresh slate will help. Does anyone have any other suggestions? How long should it sit at the SetupConnection.. part?
I had a pretty full battery when I started this, but have been tinkering for a while and I'm getting a bit nervious that it's running low. Is there any way to try charge given stock equipment?
Good news! The phone is un-bricked.
Swapping out the PC that was running Odin seemed to to the trick. Funny thing is.. I used pretty much all the same things.
Odin 1.85
Original USB Cable
MD5 checked ROM
Anyway, thanks again for everyone's help. Now that I know I can get back from a bricked state, I can with confidence go try out some new ROMs.
Great news.
BTW earlier you were using ODIN to flash the EK02 Modem, Kernel, and ROM.
In your most recent log, you were flashing the EK02 ROM only.
Mentioning it in case that wasn't intentional.
sfhub said:
BTW earlier you were using ODIN to flash the EK02 Modem, Kernel, and ROM.
Click to expand...
Click to collapse
It actually was not intentional. Thanks for bringing that up.
And actually since I've restored back to factory, it seems as if I'm have a lot of problems with reception. Think that may be the cause?
Does order matter about what goes on first?
The order doesn't really matter as much as whether the combination you are ending up with will work well with each other.
Here's where things got a bit more interesting for me. I used odin to re-flash the rom, kernal, and modem. Still had crappy signal. I can basically only roam. That's not normal for me.
I figured I'd try the oneclick method in sfhub's sig. This time I'll let it wipe my user data. Fresh start to the phone. No custom apps, not rooted.. But still the same problem.
I called Sprint to check out what's the deal with roaming on my plan.
I dial *2 and get the following message:
"We're sorry, use of this feature is not currently available. Please call cricket customer support at 611"
Cricket? Why is this configured to call cricket? Isn't this supposed to be a sprint ROM?
schlapppy said:
Here's where things got a bit more interesting for me. I used odin to re-flash the rom, kernal, and modem. Still had crappy signal. I can basically only roam. That's not normal for me.
I figured I'd try the oneclick method in sfhub's sig. This time I'll let it wipe my user data. Fresh start to the phone. No custom apps, not rooted.. But still the same problem.
I called Sprint to check out what's the deal with roaming on my plan.
I dial *2 and get the following message:
"We're sorry, use of this feature is not currently available. Please call cricket customer support at 611"
Cricket? Why is this configured to call cricket? Isn't this supposed to be a sprint ROM?
Click to expand...
Click to collapse
*2 doesn't always work when you are roaming.
*If* you can get on a Sprint native network, the first thing I would try is "Update Profile" and "Update PRL" from menu->settings->about phone->system updates
If that doesn't work, I would try a ##786# reset from the dialer. I figure you don't have that much user data to save right now and probably stuff is backed up. You'll need your MSL, so in adb shell type "getprop ril.MSL" It *IS* case sensitive. If you try to do it in android terminal, the swype keyboard may auto-capitalize "I" in "rIl" and it isn't ovious it did so on the small screen.
##786# will reset your NVRAM and Sprint login info and cause the phone to reprovision.
Now be forewarned, that if you actually have a tower down and that is why you are on cricket, then your phone will *NOT* be able to reprovision. It needs to be on a Sprint native network to reprovision using the automated OTA method. Provisioning voice by hand is ok, but data is a little more annoying.
Anyway, I wouldn't spend too much time trying to figure out if this is a ROM issue. If it was, there would likely be far more complaints. It could easily be Sprint doing maintenance work on some towers near you.
If you are not getting on the Sprint network it is some sort of tower, signal, or provisioning issue. Now if you couldn't get on any cell network, even cricket, then that might be something on your phone.
sfhub, you a rock star. Thanks for your help. All is good now, and I'm back up with full signal.
Does anyone know of a way to revert back to stock using a Mac? I've searched the forums and google but have not found anything helpful. thanks
Use heimdall.
Let me try again since im kind of new. Does anyone know of a step by step to revert back to stock on a mac computer? Thanks everyone.
So I restarted my phone today and it wont go past the "android" logo before shutting off. If anyone is interested in helping me out on a mac, I would be willing to donate to you via paypal. I've just decided I would rather get my phone back to stock. I originally rooted via heimdall and I can currently get into CWM. Thanks guys
fredygonz said:
Let me try again since im kind of new. Does anyone know of a step by step to revert back to stock on a mac computer? Thanks everyone.
Click to expand...
Click to collapse
Do what sfhub said...get Heimdall. I haven't used it myself but those with Macs have had much success with it
Sent from my SPH-D710 using Tapatalk
Thanks John. I have heimdall. But I can't figure out how to root it back to stock using heimdall.

[Q] Phone boot loops, can get into Odin mode but Odin stalls

Hi all, I’m having some trouble with my SGS2. I’ve searched for the better part of several days and read a lot of threads with similar but slightly different issues and I haven’t seen any definite solutions so I want to ask the experts before I do something stupid. Sorry for the long post but I want to include as many details as I can so no one has to use their crystal ball to figure out what is going on.
The other day my Sprint (really it is through Ting but it is branded as Sprint) SGS2 would not wake up from sleep after charging all night. It was running a GB27 rooted, full restore stock ROM I flashed through Odin (downloaded via rwilco’s very nice site). The flashing was done over a month ago and I didn’t have any troubles until this. Pressing and holding the power button did nothing, so I removed the battery to restart the phone. It was stuck in a boot loop at the “Samsung Galaxy S2” boot screen. Removed the battery for over an hour, tried again, same thing. I can boot into Odin download mode by using power+vol down. I don’t have CWM so I can’t try any other recovery options.
I tried using Odin to reflash the same ROM--GB27, rooted, full restore. This is Odin v1.81 one-click from rwilco’s site. I made sure all Kies processes were killed and started the reflash process and it got stuck trying to write cache.img. I left it for well over an hour and it never progressed past this point. Usually I’d see the blue progress bar on the phone during the flash process but it never appeared. This is the log from odin:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> cache.img
The log stopped here and after an hour, I unplugged the phone. I can still get to odin download mode, but instead of the “Samsung Galaxy SII” boot screen, I just get the “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.” I gather that a flag is set during the flash process, then is removed once the flash process completes successfully. Tried to flash again many times with different USB cable/port etc, but no luck.
The next step, I read through the FAQ on this forum and decided to try flashing EL29 via odin one-click (downloaded from here: http://www.rwilco12.com/downloads.p...-D710)/Stock ROMs/GB/EL29/Full Restore/Rooted). This used Odin v1.85. I left all options as the default and selected the PDA file but got these messages:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710.EL29_CL852097_ROOTED_PDA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.bin
<ID:0/003> NAND Write Start!!
However, it never seems to progress from here even after an hour. I never see any blue progress bar. Also tried again using different USB cable and port, but no luck.
My phone isn’t viewable from Kies.
I’m at a loss for what to do next. I’d try to flash more versions, but I don’t know enough about this emmc bug and don’t want to trigger it. Reading around, I see suggestions about repartitioning and flashing PIT files, but this seems risky. I am also looking if there is any danger flashing from jellybean to non-jellybean builds.
I read about flashing just the kernel, modem and ROM separately but which files should I use? I also read about flashing a CWM kernel so I can get into recovery mode but I’m still not certain which files I should be using. I will also admit I don’t know how to flash only a kernel through odin. It looks like you use the PDA box like what I did above, but I thought that was for full ROMs? Do you use the PDA box for both kernels and ROMs?
I did find this thread http://forum.xda-developers.com/showthread.php?t=2289007 which is very similar to my issue, but I’m not sure if I messed something up by trying to reflash the same ROM.
What should I try next?
Sorry for the simple questions but I want to learn! Thanks for the help!
Very interesting. Seems like there is some nastiness going around with jellybean and our phones. The emmc bug was initially ICS, don't know if it carried over, but due to the high number of phones crashing, there must be some form of corruption going on.
Sent from my SPH-D710 using xda premium
noobtoob said:
Very interesting. Seems like there is some nastiness going around with jellybean and our phones. The emmc bug was initially ICS, don't know if it carried over, but due to the high number of phones crashing, there must be some form of corruption going on.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Agreed. The fact that it happens unprovoked is particularly worrisome.
This is the exact type issue I tried moving and helping the other day. I an now at quite a loss. We could have you just try and Odin flash a kernel. Yes, you would just use the PDA button to select your .tar file. Put a ROM in your SD card, and clean/flash this way, but that proved unsuccessful least time as well.
Sent from my SPH-D710 using xda premium
noobtoob said:
This is the exact type issue I tried moving and helping the other day. I an now at quite a loss. We could have you just try and Odin flash a kernel. Yes, you would just use the PDA button to select your .tar file. Put a ROM in your SD card, and clean/flash this way, but that proved unsuccessful least time as well.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Thanks. I did find your post here on a similar thread and it was what made me post this... I wasn't sure if I could salvage it before getting to the point where I couldn't get into odin mode.
So you think flashing EL26 with CWM recovery would be my best option? I'm curious if when I tried to flash EL29 it didn't do anything since the previous flash had stalled... so maybe I avoided the scenario mentioned in your post above. From the log it still looks like it flashed recovery.bin though, so I don't know.
tanminivan said:
Thanks. I did find your post here on a similar thread and it was what made me post this... I wasn't sure if I could salvage it before getting to the point where I couldn't get into odin mode.
So you think flashing EL26 with CWM recovery would be my best option? I'm curious if when I tried to flash EL29 it didn't do anything since the previous flash had stalled... so maybe I avoided the scenario mentioned in your post above. From the log it still looks like it flashed recovery.bin though, so I don't know.
Click to expand...
Click to collapse
Well, at this point I don't know. I see this happening a lot now. I have been flashing exclusively through mobile Odin and roms that I had on my SD card except the other day when I tried the pit and tar files from that post. Seems more and more people are running into bricking all of a sudden a lot right now. I think sprint or Samsung need to get involved and do some phone replacement. I would take a poll and see how many people have bricked using just a stock ROM. It could have something to do with the hardware version of something in your phones. I am not anywhere smart enough to figure that stuff out, I can just offer advice and test things I know (or knew) to be safe ATM.
Sent from my SPH-D710 using xda premium
Are you able to flash a one-click ICS or GB ROM? Specifically FL24. My phone didn't like GB27 either (thankfully no bricking). I was able to flash EL26 with CWM by using the one-click twice. The first flash never seemed to work the first time, even though it said it was successful. Flashed several AOSP ROMs from there without issue.
bigj231 said:
Are you able to flash a one-click ICS or GB ROM? Specifically FL24. My phone didn't like GB27 either (thankfully no bricking). I was able to flash EL26 with CWM by using the one-click twice. The first flash never seemed to work the first time, even though it said it was successful. Flashed several AOSP ROMs from there without issue.
Click to expand...
Click to collapse
Flashing with one-click twice? Wouldn't that be a double-click?
I've tried using Odin non-one-click to flash EL26 w/ CWM but Odin just stalls at "NAND Write Start." But interestingly, it is incrementing the flash counter and "current binary" now reads "custom" where before it read "Samsung Official." So at least it's doing something. Time to search on how to get past these stalled flashes... from this thread it doesn't look particularly promising...
Just to provide an update to anyone who comes across this thread and has the same issue. I tried pretty much everything I could think of. I tried flashing all of the odin one-clicks I could get a hold of (GB/ICS/JB). I tried flashing tars. I tried flashing just kernels (GB/ICS/JB). I tried all kinds of recovery kernels, EL26 CWM etc. Of course I used all different versions of odin, different computers, different cables, different USB ports, etc.
I read the repartitioning thread (well at least quite a bit before people started asking the same questions over and over again). I downloaded the 92 different PIT files for the E4GT and tried flashing all of the different kinds of pit files... ones that moved the system partition, ones that moved data, ones that moved factoryFS, ones that shrank the UMS partition. Of each of those I tried different shift amounts...1GB, 3GB, 8GB, etc. I tried flashing with "repartition" unchecked (not sure what it really would do but it was suggested somewhere so I tried it).
Nothing worked. It'd always stall trying to write to the device. For flashing PIT files odin would start with "SET PARTITION" and just hang for over an hour and never progress. Still very strange that I could get into odin and usually on each attempted flash it would increase the flash counter. And strange as well that I was running rooted stock and this seemed to happen on its own.
The best I can figure is I'm really unlucky and have some bad blocks in memory at just the wrong spot to prevent the flashing process from completing.
Thanks for the update tan. Someone else has this very same issue. Looks like as of now there's no solution. That really sucks.
Sent from my SPH-D710 using xda premium
jdsingle76 said:
Thanks for the update tan. Someone else has this very same issue. Looks like as of now there's no solution. That really sucks.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I woke up this morning with the same issue. My phone was fine when I put it on the charger last night. This morning it was off, when I turned it on just samsung logo boot loop. I could not boot to recovery. I've tried to Odin a new recovery and a once-click full ROM. Odin stalls at recovery.bin either way.
wraith404 said:
I woke up this morning with the same issue. My phone was fine when I put it on the charger last night. This morning it was off, when I turned it on just samsung logo boot loop. I could not boot to recovery. I've tried to Odin a new recovery and a once-click full ROM. Odin stalls at recovery.bin either way.
Click to expand...
Click to collapse
Sorry to hear you have the same issue. You may read up on repartitioning and try that---you might have better luck than I did.
tanminivan said:
Sorry to hear you have the same issue. You may read up on repartitioning and try that---you might have better luck than I did.
Click to expand...
Click to collapse
I couldn't perform any of the standard repartitioning methods because recovery was not accessible (couldn't run the bad sector scan), nor was Odin working with any sort of TAR. I also reviewed the various PIT files, but based on your review of the same 100 odd files I was reviewing and finding that none of them seemed to relocate recovery addresses (we are stalling on recovery not sys or user), I threw in the towel and took it into a local Sprint repair store. The tech confirmed the issue, he was unable to factory flash it at all. His diagnosis was "something is seriously corrupted", but was very nice about it. He didn't even mention my dozen or so flash count showing in odin mode from my recovery attempts. Oh, and I told him flat out that I had tried to recover it via odin. I had the Insurion coverage, (drop/break/wet), not full TEP, but they were still able to order a replacement for $53. If you have TEP it might be a no charge replacement. He also noted aside that hes seen this a couple other times lately, not to read to much into that but it may be that the lemon memory modules Samsung pawned off on this device might be starting to just up and die instead of waiting to be overwritten wrong. I only say that because I haven't flashed a thing in months by Odin or recovery, and when mine died it was (or should have been) sleeping.
Thanks for the posts, they saved me the frustration of further investigating the PIT files, and got me into the repair shop quickly. I have a 5 day wait for the replacement, and my pregnant wife is due any time. I can't afford to be without a phone for long. I could have procrastinated for days without finding this research.
I'm up for upgrade in just like 2 weeks now, and this has me wondering if I should even chance another Samsung product. The HTC One is looking better and better, even though I'm not sure I can part with having an SD card and replaceable battery. Time to start looking around to see if the SG3 and Note2 have had all these EMMC issues. I want the SG4 but not if this is a running problem.
Note 2 doesnt.
Sent from my SPH-L900 using Tapatalk 2
wraith404 said:
Thanks for the posts, they saved me the frustration of further investigating the PIT files, and got me into the repair shop quickly. I have a 5 day wait for the replacement, and my pregnant wife is due any time. I can't afford to be without a phone for long. I could have procrastinated for days without finding this research.
I'm up for upgrade in just like 2 weeks now, and this has me wondering if I should even chance another Samsung product. The HTC One is looking better and better, even though I'm not sure I can part with having an SD card and replaceable battery. Time to start looking around to see if the SG3 and Note2 have had all these EMMC issues. I want the SG4 but not if this is a running problem.
Click to expand...
Click to collapse
Thank you, not a problem. Congrats on your upcoming baby!
Unfortunately I'm with Ting, so not am I only out of warranty and official repair options, but the full $500 unsubsidized cost of the phone as well. I'm optimistic, however. I purchased a Sprint SGS2 with a broken screen on ebay for around $50 and swapped the motherboard. Unfortunately it turns out the ESN had been flashed to another carrier so I'm trying to figure out how to flash it back...
I have the same feelings on whether my next phone will be a Samsung device as well. I guess time will tell how good the S4 is.

[Q] HELP! Soft Bricked T889 Note 2 missing pit file

here is my situation:
my phone was rooted, i unrooted it then realized i forgot to remove the custom boot animation file i had for the phone so i attempted to reroot (followed a stupid youtube video) but accidentally used the wrong root file for my phone. using odin, it failed and i tried rebooting the phone but it says to connect to kies and try to restore it, but it didn't work. then i had a friend look at it (they rooted the phone for me to begin with) and they said my phone was missing the pit file and nothing she did worked. she said it kept on mapping? i'm not too familiar with it but she says my phone was soft bricked. i was hoping maybe someone has some knowledge on how to help me fix my situation? thanks!
youtube video i followed....
How to Root your Samsung Galaxy Note 2
this is a log from odin below
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T889UVBMD1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Look up Skips Note 2 Tool Kit, install it, run it and your but will be saved! And all automatically! Definitely the best tool I ever saw. Doesn't matter what you are missing or how you screwed up. It's like Prego. It's in there. Then after you OMG I'm cured, imagine what the pro version can do. Believe me, best 10$ I ever spent. I won't even wish you good luck. Just get it and follow the bouncing ball. Cya
Sent from my SGH-T889 using XDA Premium 4 mobile app
darkmanmd said:
Look up Skips Note 2 Tool Kit, install it, run it and your but will be saved! And all automatically! Definitely the best tool I ever saw. Doesn't matter what you are missing or how you screwed up. It's like Prego. It's in there. Then after you OMG I'm cured, imagine what the pro version can do. Believe me, best 10$ I ever spent. I won't even wish you good luck. Just get it and follow the bouncing ball. Cya
Sent from my SGH-T889 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Guy with 5 posts selling software and promising miraculous results...
Sounds legit.
Hastily spouted for your befuddlement
My Note 2 Has Space Herpes
Coug76 said:
Guy with 5 posts selling software and promising miraculous results...
Sounds legit.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Not selling just suggesting a solution that worked for me..... and crediting where credit is due Mr. Cougar. I was pants down six ways from Sunday and found out that Kies wasn't worth a hoot. Crap, I'm knocked :=/ I just knew I had just crash tested and burned....my very first phone. God bless twrp, I erased and formatted the WHOLE tamale. (Note to self: Maybe smart phones are a bit beyond the parameters of my engineering envelop. :-/ Self, you still have those Hawaiian Punch cans and some cat gut layin around? That concept was right up your alley pal)..but I do digress...
After a good cry, I remembered Skips Magic Note 2 Toolkit.
Heck it was already trashed what else could go wrong. I sucked one in and fired Skips up. Crossed my toes, answered two Q's; had to guess on the third and for gods sakes, Coug... May I call ya Coug? Cool. I pushed the red button. The next thing I know we drop into low. Drivers are loading, the phone squatted down, my computer started smoking and making odd noises. Blink....automatic download factory reset mode happened, three different backups; CWM, TWRP and Philz whipped by and auto installed. The phone started blinking, the room turned black, I stood up so I could stand back.
Then it went Plink, auto reboot, flashed into umm I dunno, maybe fast boot mode..(breathe). Odin popped open and sucked in some file. Things went green after a while, the phone spun around; rebooted again....and then, there it was, Samsung singing that same old Song!!!
Just call me Lazarus dude! It was back and downloading updates by air. And better news yet, I was none the worse for the wear! No Spoof..well perhaps a bit of embellishment here and there..but not that much I swear! The thing's not a toolkit it's AhhhLIVE..and fortunately, so is my phone.....go figure....
Mr. Cougar, that's my story and I'm holding tight to it. There was a bit more. Since it was so neat the first time around, I got cocky and bit it again :=/ However, I regrouped and turned Pro (lmao) But rather than tax you further, I'll save that rubbish for later..
Mr. Cougar, I know that you know how inexperienced I am and how awestruck...nah you can't know but I truly am as I watch and read with great fascination as XDA morphs science fiction into science fact every day. I must tell you Sir, this place really is a treasure!
Plus Bonus! You gave me a grin without knowing...on second thought, you probably did ) Mayhaps I shall return the favor some day....and yes I am still befuddled...but happily so.
Thanks for the shout Mr. Cougar.
dm out~
Thanks for the laugh. I needed that this morning.
Hastily spouted for your befuddlement
I can only go on download mode on my note 2 and i've tried to use the toolkit but it only works through ADB.Do you have any other suggestions? Also i've tried to use odin but i get the missing pit errror message.
I'm interested in knowing how to use the toolkit also
Androidfan253 said:
I can only go on download mode on my note 2 and i've tried to use the toolkit but it only works through ADB.Do you have any other suggestions? Also i've tried to use odin but i get the missing pit errror message.
Click to expand...
Click to collapse
I've tried the full version on my softbricked t889 and it did not work. Neither does Odin. Everything I've read says my phone is a softbrick because it can go into download mode but that's all it does. My phone doesn't loop and stuff like others it has these white noise and colored lines all across it when i boot it regular. Please someone help mmy phone has been broke since the beginning of this year.
This looks like a hardware issue(possibly emmc) but you can always try different versions of ODIN's, a different USB cable or verify USB drivers on your system.

Tried odin to flash s3 now win7 fails to boot

so start off by saying im new to android but been jailbreaking iphones for years and just not sure whats what here.. so i got an s3 t999n for metro and it get stuck at the carrier screen and just sits there.. a few times the blue light would blink green then the screen scrambled and it shutdown. i did the reset and no change.
i can get it into recovery and download modes. i installed kies and odin3.07 and 3.09 and a rom that i think was suppose to root it but odin never saw the device and when i rebooted my pc (win7) it failed to boot due to corrupt boot up file acpi.sys. i mananged to restore from a system image a few weeks old but what the heck happened? id like to not have to go thru that again so would like to do things right and not just pick a thread from random forum and go with it..
how can i tell what version is on it since it doesnt actually boot up?
i see that if its 4.3 i cant go to 4.1.2 so should i just go to 4.3?
and where can i get downloads from reliable sources for the programs needed? odin, roms ect..
just to help me make sense of things..
rom for android is the same as firmware for iphones?
iphone you install tweaks and themes through cydia. Android install custom roms with preloaded things?
hate feeling like a noob again thanks for any help and guidance
I hoghly recommend teading through the stickies here and in the xda general section.
I dont see how anything you did with the device could have affected windows that way. Something else was probably going wrong there.
Uninstall kies. It interferes with odin. You can find everything you need to get going on my signature.
Flash the latest 4.3 build. Since you just got the phone, it will already have the latest firmware. You can only flash the same or newer firmware. You can flash older roms if you like, but if you force the firmware to downgrade itll hard brick.
Sent from my SGH-T999 using Tapatalk
thanks i figured out that the 2 cables i have will only charge the phone and not connect for data. i keep getting errors in odin trying to flash 4.3.. heres what i get..
<ID:0/014> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999NUVUBNC1_T999NTMBBNC1_T999NUVUBNC1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/014> Odin v.3 engine (ID:14)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Get PIT for mapping..
<ID:0/014> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
ill remove kies and try again
brc0703 said:
and where can i get downloads from reliable sources for the programs needed? odin, roms ect..
just to help me make sense of things..
rom for android is the same as firmware for iphones?
iphone you install tweaks and themes through cydia. Android install custom roms with preloaded things?
Click to expand...
Click to collapse
1) To answer your first question, stick to XDA forums, T-Mobile S3 forums not some random site you know nothing about..
2) in a way yes, but ROMs only contain the necessary components to boot and make the phone operable. It is not full firmware, they don't contain modem, bootloader etc, like firmware does. Some ROMs come with tweaks that you can select in aroma installer, others you enable tweaks through your settings, others already have tweaks enabled and you can also install tweaks from an xposed app called modules, this is kind of like cydia but for android. If a ROM is heavily modified, some modules that do tweaks may not work, or some of their settings may not work

Categories

Resources