Related
So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon
mentorkyrom said:
So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon
Click to expand...
Click to collapse
The 4.3 OTA installed a locked bootloader, which will prevent you from ODIN'ing back to a previous version. you can flash any ROM you would like from recovery, you CANNOT downgrade the bootloader. As of right now, if you have knox, you are stuck with it.
You are extremely lucky that you didn't brick your phone by using odin to flash a non-4.3 tar. I wouldnt try again.
My advice is, remain rooted with a custom recovery, and find a ROM to your liking, and flash that.
I have also heard that we cannot flash custom kernels on the knox (MK3) bootloader as well, but I havent verified that.
eletendre84 said:
The 4.3 OTA installed a locked bootloader, which will prevent you from ODIN'ing back to a previous version. you can flash any ROM you would like from recovery, you CANNOT downgrade the bootloader. As of right now, if you have knox, you are stuck with it.
You are extremely lucky that you didn't brick your phone by using odin to flash a non-4.3 tar. I wouldnt try again.
My advice is, remain rooted with a custom recovery, and find a ROM to your liking, and flash that.
I have also heard that we cannot flash custom kernels on the knox (MK3) bootloader as well, but I havent verified that.
Click to expand...
Click to collapse
Thank you for the response. Is CyanogenMod an option then? If I go to CM could I flash back a stock 4.3 rom in the future?
As an added bonus question does CM allow wifi tethering?
Again thank you for the response.
mentorkyrom said:
Thank you for the response. Is CyanogenMod an option then? If I go to CM could I flash back a stock 4.3 rom in the future?
As an added bonus question does CM allow wifi tethering?
Again thank you for the response.
Click to expand...
Click to collapse
CM is certainly an option. In fact, its what i am running now. CM11 12-24. Runs great. You can always odin the stock mk3 tar and go back to stock unrooted, at any time.
in order to flash cm11 you MUST be on TWRP 2.6.3.1 or CWM 6.0.4.5 or newer or the assert check will fail.
not sure on the tethering, but im pretty sure it definitely works on cm10.2 and i think it does on 11 as well, but dont quote me on that.
eletendre84 said:
CM is certainly an option. In fact, its what i am running now. CM11 12-24. Runs great. You can always odin the stock mk3 tar and go back to stock unrooted, at any time.
in order to flash cm11 you MUST be on TWRP 2.6.3.1 or CWM 6.0.4.5 or newer or the assert check will fail.
not sure on the tethering, but im pretty sure it definitely works on cm10.2 and i think it does on 11 as well, but dont quote me on that.
Click to expand...
Click to collapse
Tethering is available on CM11 just like it was on 10.2; would strongly recommend latest Philz Touch Recovery over either TWRP or CWM though. Although it is based on CWM, it has proven to be pretty much the superior recovery option for flashing any Android build number, plus it is highly customizable.
Philz Touch Recovery
this is how to downgrade
mentorkyrom said:
So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon
Click to expand...
Click to collapse
do a factory data reset then use odin auto root from computer ok...... after boot u will get a security message supersu will be unfortunately stopping this is ok..... then u will need to download the supersu.app to root of sd then manually install this will update it and now u can turn off knox and have root... then go to market and download odin mobile then flash your .tar file u want and you will be good to go 4.1.2 doesn't have knox and has a unlocked bootloader so have fun bro this method may work for other phones
smuther22 said:
do a factory data reset then use odin auto root from computer ok...... after boot u will get a security message supersu will be unfortunately stopping this is ok..... then u will need to download the supersu.app to root of sd then manually install this will update it and now u can turn off knox and have root... then go to market and download odin mobile then flash your .tar file u want and you will be good to go 4.1.2 doesn't have knox and has a unlocked bootloader so have fun bro this method may work for other phones
Click to expand...
Click to collapse
Do you realize that this thread hasn't been used in a couple of months? I would assume the author has no more need of advice based on the inactivity. Also, once Knox is installed, it is on the phone to stay. PERIOD. NO DOWNGRADING POSSIBLE VIA ODIN. Custom ROMs of any build are fine via custom recovery, but any attempt to change the bootloader will trigger Knox and brick the phone. Dangerous info to be posting here, especially since someone else who doesn't know better might try this.
hey guys,
i recently rooted my galaxy s3 i747 and installed cm11 on it. the whole process was done automatically using one of those cm installers. however, i recently learned that cm11 is not stable yet. so i want to downgrade to 10.2 which is the most recent stable cm.
i did try that, using manual methods, such as flashing it via recovery, however a picture of a dead android with a red warning triangle popped up saying it couldn't be done.
my question is, why would this happen? i know official android doesn't allow downgrade, but rooted ones should allow installation of any custom rom no matter which verison, right?
another question, how do i downgrade to 10.2, or install any other stable custom rom? i am afraid that the phone might become bricked due to my inexperience, but i want stability in my phone.
also, if my phone is indeed hard bricked, would it be possible to get it fixed under $100?
P.S. i am quite new to xda, so sorry if i posted this in the wrong area.
Are you using the most up to date custom recovery for your phone? Are you wiping system, Dalvik, and cache before installting the new ROM?
audit13 said:
Are you using the most up to date custom recovery for your phone? Are you wiping system, Dalvik, and cache before installting the new ROM?
Click to expand...
Click to collapse
used goo manager to install recovery, and wiped system, dalvik cache and cache. you see, i was following a video tutorial, and the custom recovery on that one was an older version. so, although i wiped them all, it was a bit different. you think that might be the problem?
user9560 said:
used goo manager to install recovery, and wiped system, dalvik cache and cache. you see, i was following a video tutorial, and the custom recovery on that one was an older version. so, although i wiped them all, it was a bit different. you think that might be the problem?
Click to expand...
Click to collapse
I would start over by flashing the tar version of Philz Touch via Odin 3.07 from here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att.
Copy CM10.2 to your phone or external SD card, boot into recovery, wipe cache, Dalvik, data, and system. Then install CM10.2, boot into the OS, set things up, boot into recovery, and flash Gapps.
I prefer doing everything via recovery mode.
thanks! aah i'm a little scared though. do you think if i follow the instructions correctly, there'll be little chance of a hard brick? i know nothing's full proof tho.... what do you think? is it worth it? is 10.2 better than cm11 nightly as of yet?
You're using an AT&T s3 i747? What ROM was on the phone before you installed a custom ROM?
If it was any stock 4.3, don't touch the bootloader.
audit13 said:
You're using an AT&T s3 i747? What ROM was on the phone before you installed a custom ROM?
If it was any stock 4.3, don't touch the bootloader.
Click to expand...
Click to collapse
yup s3 i747 with bell. i think its the same as att. the phone came with 4.2 then i updated to 4.3 jelly bean.
also, isn't odin like a software on the computer? could you perhaps point to a tutorial? sorry ^_^' i'm not so familiar with android and there r so many tutorials out there, i wouldnt know which one i should follow in this case.
user9560 said:
yup s3 i747 with bell. i think its the same as att. the phone came with 4.2 then i updated to 4.3 jelly bean.
also, isn't odin like a software on the computer? could you perhaps point to a tutorial? sorry ^_^' i'm not so familiar with android and there r so many tutorials out there, i wouldnt know which one i should follow in this case.
Click to expand...
Click to collapse
The model # for the Bell s3 is i747m. The AT&T version is an i747. Make note of the difference when posting and looking solutions.
Do you have any warranty left on your phone? If you do, installing the 4.3 update will install the 4.3 bootloader and Knox. Once you have upgraded to the 4.3 bootloader, any attempts to downgrade the bootloader will brick the phone. Any reason you updated to 4.3?
Since you have Knox on your phone, installing a custom recovery will trip the knox counter and void your warranty. If you have no warranty left, tripping the counter isn't a problem.
audit13 said:
The model # for the Bell s3 is i747m. The AT&T version is an i747. Make note of the difference when posting and looking solutions.
Do you have any warranty left on your phone? If you do, installing the 4.3 update will install the 4.3 bootloader and Knox. Once you have upgraded to the 4.3 bootloader, any attempts to downgrade the bootloader will brick the phone. Any reason you updated to 4.3?
Since you have Knox on your phone, installing a custom recovery will trip the knox counter and void your warranty. If you have no warranty left, tripping the counter isn't a problem.
Click to expand...
Click to collapse
hmm when i look at my about phone it just says SMASUNG-SGH-I747... so i'm not sure where i747m comes in... i assume there's no warranty for my phone anymore since it's been rooted already. i just updated to 4.3 because i assumed that a reputable company like samsung would give out a good and better performance update. after i updated however, the phone started going haywire. it became laggy and slow. not that noticable, but still bothered me. the main reason i ditched iphone was because of it's sluggy behavior. so i had nothing to do but root. cm11's great, but some features are unstable, like random reboots and stuff. so i wanted to try cm10.2 or miui v5. hmm. i'm still thinking about how to figure out odin..
user9560 said:
hmm when i look at my about phone it just says SMASUNG-SGH-I747... so i'm not sure where i747m comes in... i assume there's no warranty for my phone anymore since it's been rooted already. i just updated to 4.3 because i assumed that a reputable company like samsung would give out a good and better performance update. after i updated however, the phone started going haywire. it became laggy and slow. not that noticable, but still bothered me. the main reason i ditched iphone was because of it's sluggy behavior. so i had nothing to do but root. cm11's great, but some features are unstable, like random reboots and stuff. so i wanted to try cm10.2 or miui v5. hmm. i'm still thinking about how to figure out odin..
Click to expand...
Click to collapse
The Bell, Rogers, and Telus version of the s3 is sgh-i747m. The AT&T version is sgh-i747. Did you get the phone from one of the Canadian carriers?
If you're running a custom ROM, this may be the reason it just shows sgh-i747. Custom ROMs on XDA are designed for the d2att but are compatible with the Canadian version of the s3.
Updating to 4.3 would have loaded a 4.3 bootloader and Knox. Once your phone has the 4.3 bootloader, do not attempt to downgrade the bootloader as it will brick your phone.
Knox software can interfere when trying to root your device.
You updated to 4.3, then installed CM?
audit13 said:
The Bell, Rogers, and Telus version of the s3 is sgh-i747m. The AT&T version is sgh-i747. Did you get the phone from one of the Canadian carriers?
If you're running a custom ROM, this may be the reason it just shows sgh-i747. Custom ROMs on XDA are designed for the d2att but are compatible with the Canadian version of the s3.
Updating to 4.3 would have loaded a 4.3 bootloader and Knox. Once your phone has the 4.3 bootloader, do not attempt to downgrade the bootloader as it will brick your phone.
Knox software can interfere when trying to root your device.
You updated to 4.3, then installed CM?
Click to expand...
Click to collapse
ah i understand now. i got the phone from bell. thanks for clarifying that.
i installed cm after the update, unfortunately. but when i went into recovery mode, i did not see anything related to knox. does it show up on the phone or in recovery mode? as of this moment, i was not thinking about the bootloader. because we're just tyring to downgrade the os, right? or is it something like previous os would not run on an updated bootloader?
user9560 said:
ah i understand now. i got the phone from bell. thanks for clarifying that.
i installed cm after the update, unfortunately. but when i went into recovery mode, i did not see anything related to knox. does it show up on the phone or in recovery mode? as of this moment, i was not thinking about the bootloader. because we're just tyring to downgrade the os, right? or is it something like previous os would not run on an updated bootloader?
Click to expand...
Click to collapse
Go into download mode and look at the screen. What does it say? It will probably have the model #, warranty bit, and whether it is running custom or official software.
Are you running TWRP or CWM?
audit13 said:
Go into download mode and look at the screen. What does it say? It will probably have the model #, warranty bit, and whether it is running custom or official software.
Are you running TWRP or CWM?
Click to expand...
Click to collapse
ok sir, this is what it says:
-ODIN MODE
-PRODUCT NAME: SGH-I747M
-CUSTOM BINARY DOWNLOAD: Yes (2 counts)
-CURRENT BINARY: Custom
-SYSTEM STATUS: Official
-QUALCOMM SECUREBOOT: ENABLE
-Warranty Bit: 1
-BOOTLOADER RP SWERV: 1
This screen tells you that your phone is an i747m, you have knox installed, any warranty on your phone has been voided, and you're loaded 2 custom ROMs.
Since you have a custom recovery, you can wipe data, cache, Dalvik, and install cm10.2.
audit13 said:
This screen tells you that your phone is an i747m, you have knox installed, any warranty on your phone has been voided, and you're loaded 2 custom ROMs.
Since you have a custom recovery, you can wipe data, cache, Dalvik, and install cm10.2.
Click to expand...
Click to collapse
ok now that you mentioned cwm and twrp, i noticed my phone resembles cwm when i boot into recovery. the tutorial i followed was in what looked like twrp. but why would that happen? i followed his instructdions and updated the recovery the same way he did via goo manager. he is using twrp, i am using cwm. is that the problem?
user9560 said:
ok now that you mentioned cwm and twrp, i noticed my phone resembles cwm when i boot into recovery. the tutorial i followed was in what looked like twrp. but why would that happen? i followed his instructdions and updated the recovery the same way he did via goo manager. he is using twrp, i am using cwm. is that the problem?
Click to expand...
Click to collapse
As long as you have a custom recovery, you can try flashing cm10.2.
audit13 said:
As long as you have a custom recovery, you can try flashing cm10.2.
Click to expand...
Click to collapse
i did try it before. booted into recovery, tried to flash rom zip and gapps. but it failed to flash. are you suggesting i do it in DOWNLOAD MODE with the new tar file you have mentioned? would you be able to link me to a place which would give me instructions? i am quite new to this. thanks
user9560 said:
i did try it before. booted into recovery, tried to flash rom zip and gapps. but it failed to flash. are you suggesting i do it in DOWNLOAD MODE with the new tar file you have mentioned? would you be able to link me to a place which would give me instructions? i am quite new to this. thanks
Click to expand...
Click to collapse
What error are you getting when you try to flash a ROM?
audit13 said:
What error are you getting when you try to flash a ROM?
Click to expand...
Click to collapse
it gives me a dead android with a red warning triangle. the one that says rom cannot be flashed.
user9560 said:
it gives me a dead android with a red warning triangle. the one that says rom cannot be flashed.
Click to expand...
Click to collapse
Are there any RPM error messages? What custom recovery do you have on your phone? It should say at the very top.
I have a S4 - with 4.4.2 stock . Sadily ever since the update I had nothing but issues. Getting my 2nd replacement tomorrow to try and resolve this issue where the cell radio locks up and I have no connectivity .
At this point I am ready just say screw the warranty but I dont know what I can do as there so many threads it is very confusing.
Note at this point i dont care about tripping the efuse.
From what I have read is that I can root the phone. But where I am confused at is if I can load custom bootloader /roms I had a moto cliq2 with a locked boot loader that then eventually loaded a 2nd boot loader and then the rom.
Really if anyone can clear up where i stand on getting one of the 4.4.4 aosp roms on the phone I be greatly appreciated.
Bootloader is not locked on this device, so just flash custom recovery with Odin and flash your ROM
+1 serio... If you're not on the evil bastard vzw service, then:root, intstall custom recovery and flash what you want!! You're lucky enough to have a device that hasn't had its n-ts cut off!! I have sprint as a carrier, so I'm in the same boat as you, but I've been collecting phones from all carriers for a while now and since vzw has such a monopoly on the us, I've racked up about 9 vzw phones with locked bootloaders. You're actually quite in luck man. Root, install recovery, ROM, profit!
youdoofus said:
+1 serio... If you're not on the evil bastard vzw service, then:root, intstall custom recovery and flash what you want!! You're lucky enough to have a device that hasn't had its n-ts cut off!! I have sprint as a carrier, so I'm in the same boat as you, but I've been collecting phones from all carriers for a while now and since vzw has such a monopoly on the us, I've racked up about 9 vzw phones with locked bootloaders. You're actually quite in luck man. Root, install recovery, ROM, profit!
Click to expand...
Click to collapse
Actually no root is needed. Just flash recovery with Odin and flash ROM
Fair point, as recovery supercedes root since its not within the os, but whats the fun of romming without rooting?
Sent from my SM-G900P using XDA Free mobile app
youdoofus said:
Fair point, as recovery supercedes root since its not within the os, but whats the fun of romming without rooting?
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
All custom ROMs come pre-rooted. So no reason to root the stock ROM, if all you will be doing is flashing a custom ROM. Just eliminates a step.
Rob
rlichtefeld said:
All custom ROMs come pre-rooted. So no reason to root the stock ROM, if all you will be doing is flashing a custom ROM. Just eliminates a step.
Rob
Click to expand...
Click to collapse
Many people think you have to be rooted to flash a custom recovery, I think this is why they said that
serio22 said:
Actually no root is needed. Just flash recovery with Odin and flash ROM
Click to expand...
Click to collapse
Ok so knox does not lock the boot loader just acts as a trigger for the annoying efuse.
Question still comes down to if I root install recovery and then flash or flash with oldin and not deal with the boot loader. I just got my 2nd replacement another one with 4.4.2 I give it a few days if it does not act up great if it does I just going to flash it .
As the current stock 4.4.2 has caused nothing but connectivity issues for me.
jawa78 said:
Ok so knox does not lock the boot loader just acts as a trigger for the annoying efuse.
Question still comes down to if I root install recovery and then flash or flash with oldin and not deal with the boot loader. I just got my 2nd replacement another one with 4.4.2 I give it a few days if it does not act up great if it does I just going to flash it .
As the current stock 4.4.2 has caused nothing but connectivity issues for me.
Click to expand...
Click to collapse
Just forget the bootloader it is not locked, and no root is needed to flash recovery. Just flash custom recovery of your choice with Odin, reboot straight into recovery RIGHT after, and flash ROM
Edit: and yes pretty much the only thing that will happen is that your counter will be tripped
Just thought of something while flashing a new ROM on my nexus 7 flo. If all custom ROMs are rooted, why then is it then that when you flash some ROMs, root can break? I flashed a different ROM on the n7 and lost root until I went back and reran the exploit
Sent from my SM-G900P using XDA Free mobile app
Hi everyone I hope this is not a repetition of some old thread (I tried but couldn't find though).
I was using my note 2 (T889) on stock 4.3 which i previously flashed via odine. A couple of days ago i came by this good looking kitkat based rom ( eZKAT v2.0 ) and went on to try it. the rom flashed flawlessly and after flashing my modem i got the signals as well but the wifi was not working. tried using dr. ketans wifi patch but didnt get the wifi to working. Anyhow, I decided to go back to 4.3 via odine. The odine flashing completed successfully but i got stuck on T-mobiles boot screen for hours.
Is there anything called "you cant go back to 4.3 from 4.4.2"? If yes, then whats the way around? I really need to go back to the stock.
Thanks.
zetrixNoob said:
Hi everyone I hope this is not a repetition of some old thread (I tried but couldn't find though).
I was using my note 2 (T889) on stock 4.3 which i previously flashed via odine. A couple of days ago i came by this good looking kitkat based rom ( eZKAT v2.0 ) and went on to try it. the rom flashed flawlessly and after flashing my modem i got the signals as well but the wifi was not working. tried using dr. ketans wifi patch but didnt get the wifi to working. Anyhow, I decided to go back to 4.3 via odine. The odine flashing completed successfully but i got stuck on T-mobiles boot screen for hours.
Is there anything called "you cant go back to 4.3 from 4.4.2"? If yes, then whats the way around? I really need to go back to the stock.
Thanks.
Click to expand...
Click to collapse
I had this problem on my Note also. Downgrading versions of Android requires a data wipe. You will need to reflash your 4.4 ROM then backup your data if you want. Save your backup to your computer then install the 4.3 image.
Sent from my Nexus 7
EverDawn4 said:
I had this problem on my Note also. Downgrading versions of Android requires a data wipe. You will need to reflash your 4.4 ROM then backup your data if you want. Save your backup to your computer then install the 4.3 image.
Sent from my Nexus 7
Click to expand...
Click to collapse
I already tried that but still the booting stuck on the t-mobile logo. I read somewhere that locked bootloader don't let you downgrade to previous version. Is this true?
In that case. Try finding a 4.3 rom that's close to stock.
Sent from my Nexus 7
The locked bootloader is always in stock firmwares i.e 4.3 for the Note 2 but not in custom roms meaning u can even install Lollipop custom on it & downgrade smoothly, i have done that many times. The problem is 4.3 stock firmware has locked bootloader hence downgrading still keeps u in 4.3 bootloader even if u remove all the KNOX files.
Stuck trying to downgrade from custom 5.1.1 to stock 4.3
Hi, i have a problem like this, upgrade to a custom 5.1.1 and then sell the phone, the new owner wants to have it stock, i try to downgrade to 4.3 but i cant, in odin i set the phone to flash it but seems like it doesn`t recognize the phone and i dont know why, so, i decided to try in recovery mode installing from the sd card but the sistem abort, so, i don`t know what to do, i`ll appreciates any help, sorry for my english, i do my best. (i have root access before upgrated to 5.1.1).
When I got this note 2, it didn't have the ota to lock the bootloader. I after a year or so on the Alliance 26 rom I had some issues and wanted to upgrade to the newest one. I tried to install it and it didn't take and was stuck in bootloop.
So I used the same files in odin to flash the phone back to stock and start it again.
I was finally able to get it rooted but no recover will install. I am having a hell of a time and I don't understand what I have done wrong. Even casual wont work.
Well when I try to install recovery like twrp the install fails and on boot it says software not supported my Verizon , take to your local vzw store for repair.
Knox has even been tripped as well and it seems like the bootloader is locked. How is that possible? Don't know how, i flash with odin a stock rom as I did when I got the phone rooted and installed a recovery and than a rom. No issues what's so ever.
Now it seems everything I try it either says software not supported by vzw or bad firmware update or boot loops. I have downloaded so many files from all of these recovery threads I'm lost .
Never had the ota update, once I got the phone I flashed it to mj9 per beanstown on the original alliance rom and ran that room ever since.
I think I have tried every how to in this forum. Can someone chime in and tell me what I am doing wrong?
Sent from my SCH-I605 using Tapatalk 2
Phone info..
Sent from my SCH-I605 using Tapatalk 2