Related
Hello all,
I have a GTab 8.9 from AT&T. I performed the ICS upgrade last night using Kies and it seemed to load correctly with no errors however the touch screen does not work now. It boots up fine but I cannot do anything with the screen. Power and volume buttons seem to be working fine.
I was able to reboot the device by holding the power button in and then go into download mode and do a factory reset. That went with no errors but the touch screen still does not work.
So, next I thought I would use Odin and try to push the factory rom back to it however Odin never sees the device, (tried multiple usb ports and 2 different pc's Win7 32b and 64b) However if I go ahead and let the GTab boot on up Odin does see it at that point. I can also get to the internal sdcard via my computer.
I also tried to copy the 7300_cwmr files to the sdcard and rebooted back to download mode. I selected apply update from sdcard and went into each of the directories but the device does not see any files in the directories, just the directories themselves.
So.... at this point I'm at a loss what to try next and I'm hoping someone on this forum can give me a nudge in the right direction.
I did reinstall the usb driver
Odin sucessfully recognized this device in download mode 'before' the ICS upgdate, not after.
I am using the factory usb cable and I did try a second one.
I was running version 3.2 before the upgrade.
Not ever rooted
Kies recognizes the device as well, can kies be used to flash my device? (sorry if that's a stupid question)
Thanks ahead
Are you sure you're in download mode, not recovery, when you try Odin. If kies recognizes the device I can't believe Odin won't.
Is the stock rom file you're trying to flash a zip file or a .tar.md5? The recovery is looking for a zip file and that may be why you didn't see it in any folder. Odin uses the tar file.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Thanks for the reply.
Yes I am in download mode. As I mentioned, Odin was able to see my GT before I upgraded to ICS, but not after. At least not in DL mode. If I let the GT go ahead and boot up Odin recognizes it with the port showing up in it's normal amber color.
It boots up fine, the touch screen is not working though so I can't use the GT. Once it boots up I can see it in my computer and place files on on it.
Thanks
Have you tried fixing permissions when you're in recovery mode? Do you have a custom recovery installed our the stock recovery, and if custom which one?
Sent from my SGH-I727 using xda app-developers app
I apologize, I'm not sure what you mean by fixing permissions while in recovery mode. I do not see that option on the screen. Everything is factory on the GT. I have not installed a custom recovery. The only change to the device from stock was the ICS upgrade that I just performed via Kies.
Is there a way that I can recover the device back to 3.2 using either Kies or while in DL/recovery mode? When the device boots I can see it and add files via my computer. Can I place the stock rom that I have downloaded from sammobile on the devices sdcard and reboot into DL mode and do a restore from sdcard? Is there a different way to do this without Odin?
Odin... I am not sure why it is not recognizing it while in DL mode. Odin will recognize it after the device boots. Actually Odin recognizes it just after the "Samsung" logo displays... while the AT&T "Rethink Possible" startup video is playing Odin will see it at that point. Not before. Quite frustrating actually. (I have tried multiple pc's and usb ports)
Thanks again for the help and apologies if I am asking stupid questions.
With the device off, hold down the power and both volume keys. When you see the Samsung logo release the power key but continue to hold down the volume keys for 2 seconds then release them. That should get you into down load mode. It'll say something about pressing the volume up key to continue. Have Odin running and then plug on the usb cable. Have you done something like that?
Sent from my SGH-I727 using xda app-developers app
ok... so I found an old "XP" laptop here at my office and downloaded the usb driver and Odin again and wnet into DL mode and for whatever reason Odin sees it on the XP machine. (whatever) grrr
Anyway... I downloaded and tried pushing both of the roms I found on sammobile.com for AT&T ( i957UCKJ7 and i957UCLK4) to my GT8.9, both times they completed successfully and when rebooting the touch screen would not work.
Is the rom still available for 3.2? Can I revert back to what came with it when it was originally released?
Thanks again for the assistance.
It sounds like you have a bigger problem than putting the stock Rom on it is going to fix. If you're still under warranty I'd take it in.
Sent from my SGH-I727 using xda app-developers app
Yeah I called them up and can toss it back at them, which I will do if I cant find an original factory rom to try and push to it.
I'm still searching for one though I have not been able to find one yet. Can anyone point me to a factory rom for this device?
I'd like to try and flash it back to stock before I send it back to them (if possible) as the touch screen was working just fine before I pushed out the update via kies the other day. Once the update finished and it rebooted, the touch screen did not work after that.
Thanks!
Go to sammobile.com for the stock roms. You'll have to sign-up but it's free.
Sent from my SGH-I727 using xda app-developers app
Yeah I've been to that site, that's where I got the 2 I mentioned above (i957UCKJ7 and i957UCLK4). I believe the UCLK4 file is ICS, correct? I'm not sure what version the UCKJ7 file is. I did try both. Those were the only 2 roms I could find there for the 8.9 ATT GT. I'll go back and look again. Maybe I missed it.
Thanks for your help
I'm sure those are the only two. The other one is honeycomb. They are the official Samsung roms. I think you've done what you can.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
This is the second reported occurrence of this happening. Weird
Sent from my SAMSUNG-SGH-I727 using xda premium
orlandoxpolice said:
This is the second reported occurrence of this happening. Weird
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Make that three ?? .. any resolution so far ?
orlandoxpolice said:
This is the second reported occurrence of this happening. Weird
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Yea, noticed that too. I used the rom from Sammy but didn't have an issue. I wonder if they got the wrong tab version.
OP, can you post what rom you flashed? And do you have an i957?
Sent from my SAMSUNG-SGH-I957
---------- Post added at 07:43 PM ---------- Previous post was at 07:23 PM ----------
wamaOnline said:
Make that three ?? .. any resolution so far ?
Click to expand...
Click to collapse
You're the second. Weird that a couple of you have had the same problem.
Sent from my SAMSUNG-SGH-I957
Regretfully my tab is not under warranty, and I don't know what to try next? Do you have any ideas
In a small way I'm glad to see that others are experiencing this also.
I wonder if anyone out there has a completely stock rom or knows where I can pick one up? I have tried the 2 over at sammobile and neither brought my touch screen back. I have searched and searched online and can't find anything.
I was reading on a different site while researching this issue and he said he reverted back to his original factory image and the touch screen functionality came back. I'd really just like to get my GT back up and running somehow until this ICS touch screen problem gets figured out.
Thanks ahead for any help.
Sammobile is the stock roms. Use the oldest one, honeycomb. The download is a zip file. To use Odin you'll need to extract the .tar.md5 file out of the zip. Use 7-zip to do that.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Yeah I've tried both of the roms on sammobile. Didn't work.
Well, thanks very much for the help. I'll keep checking here through tomorrow to see if anyone else has a suggestion to try and if not I will just mail it back to Samsing on Monday. I hate doing that because I need it for a trip on the 15th. Grrr
Very frustrating.
EraserX33 said:
Yeah I've tried both of the roms on sammobile. Didn't work.
Well, thanks very much for the help. I'll keep checking here through tomorrow to see if anyone else has a suggestion to try and if not I will just mail it back to Samsing on Monday. I hate doing that because I need it for a trip on the 15th. Grrr
Very frustrating.
Click to expand...
Click to collapse
Any updates ? A question, did you try to use a non ATT card ?
Sent from my A500 using xda app-developers app
---------- Post added at 01:50 AM ---------- Previous post was at 01:43 AM ----------
EraserX33 said:
Yeah I've tried both of the roms on sammobile. Didn't work.
Well, thanks very much for the help. I'll keep checking here through tomorrow to see if anyone else has a suggestion to try and if not I will just mail it back to Samsing on Monday. I hate doing that because I need it for a trip on the 15th. Grrr
Very frustrating.
Click to expand...
Click to collapse
One more thing , can you please tell us where did you get your tablet from ? In case it is a he issue from the seller
Sent from my A500 using xda app-developers app
Hi Guys,
I'm a noob so please send me in the right direction if I seem out of place. I have an Exhibit 4G that I managed to root. It was 2.3.6 I believe. All was great until I decided I wanted to change the operating system to a Peach Sunrise (I think) then it became stuck in a boot screen loop. I have tried resetting to factory but that doesn't help. I'm not too savvy with these phones so I'm stuck at a dead end. I'm looking for someone in the Atlanta area to fix it for me. I'm willing to pay. It was a brand new phone bought from an individual. It was only used about two week by me. Please let me know if you can help or have a relatively easy solution. Thanks in advance, Les
Is it the galaxy exhibit 4G T679? It the original exhibit? There are multiple phones with the same name. Also wiping cache/dalvik cache and fix permissions will usually fix a problem like this.
Sent from my SGH-T679 using xda app-developers app
patches0616 said:
Hi Guys,
I'm a noob so please send me in the right direction if I seem out of place. I have an Exhibit 4G that I managed to root. It was 2.3.6 I believe. All was great until I decided I wanted to change the operating system to a Peach Sunrise (I think) then it became stuck in a boot screen loop. I have tried resetting to factory but that doesn't help. I'm not too savvy with these phones so I'm stuck at a dead end. I'm looking for someone in the Atlanta area to fix it for me. I'm willing to pay. It was a brand new phone bought from an individual. It was only used about two week by me. Please let me know if you can help or have a relatively easy solution. Thanks in advance, Les
Click to expand...
Click to collapse
What do you mean by reset to factory? Wiping data does not change the operating system. However do you have cwm installed and yea is it even the t679
Sent from my Nexus 7 using xda app-developers app
i bricked my phone
:i cant get in recovery mode i have bricked my phone i was puting a costum rom on my phone stuck in boot logo and odin is not working please help :crying
allenw420 said:
:i cant get in recovery mode i have bricked my phone i was puting a costum rom on my phone stuck in boot logo and odin is not working please help :crying
Click to expand...
Click to collapse
Do you have the right drivers? Just download Samsung kies and it should be fixed
Sent from my Nexus 7 using xda app-developers app
Dvarl said:
Is it the galaxy exhibit 4G T679? It the original exhibit? There are multiple phones with the same name. Also wiping cache/dalvik cache and fix permissions will usually fix a problem like this.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
Hi Dvarl,
I'm extremely sorry but I forgot to bookmark the sight and finally decided to search my laptop history to find the thread. The phone is the newer model SGH-T679 galaxy exhibit, not the exhibit II. I have tried wiping the cache but i'm not sure exactly how to proceed to do all the procedures that you are talking about. It does not have cwm installed. I did manage to root it before I got myself in this mess.
I can assure you I will be checking the replies frequently and any help is appreciated.
theAPANT said:
What do you mean by reset to factory? Wiping data does not change the operating system. However do you have cwm installed and yea is it even the t679
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I would like to put it back to way it came out of the box or really I would like to have the newest OS on it. After that I think I could root it myself (after performing a backup). It does not have cwm installed on it. It is the newer 4G Exhibit not the exhibit II. Thanks for the reply and sorry I lost the forum and finally searched my history to find it.
Regards,
Les
patches0616 said:
I would like to put it back to way it came out of the box or really I would like to have the newest OS on it. After that I think I could root it myself (after performing a backup). It does not have cwm installed on it. It is the newer 4G Exhibit not the exhibit II. Thanks for the reply and sorry I lost the forum and finally searched my history to find it.
Regards,
Les
Click to expand...
Click to collapse
The t679 IS the exhibit 2 (although it was renamed the galaxy exhibit). The original exhibit aka just plain exhibit 4g t759 is the older model. It sounds like you have the t679 if that is correct, follow these instructions http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
Do not follow those instructions if you do not have that phone. Google if you are unsure about the phone you have because if done right for the right phone these steps are perfectly safe. If however you have the wrong phone you will ruin it pretty badly. On that cheerful note, good luck!
Sent from my Nexus 7 using xda app-developers app
theAPANT said:
The t679 IS the exhibit 2 (although it was renamed the galaxy exhibit). The original exhibit aka just plain exhibit 4g t759 is the older model. It sounds like you have the t679 if that is correct, follow these instructions http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
Do not follow those instructions if you do not have that phone. Google if you are unsure about the phone you have because if done right for the right phone these steps are perfectly safe. If however you have the wrong phone you will ruin it pretty badly. On that cheerful note, good luck!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Wow that was a fast response! I have saved your link so I can try it. You are right, it is the renamed exhibit II. The startup screen used to say exhibit NOT exhibit II. I just wished I had backed it up before I made the big mistake. I have learned my lesson. I'll give it a shot tomorrow and let you know the results. Thanks again for your help, Les
I'm having the same problem. I tried odin but it's not working.. what am I missing?
What I do because it is much much faster IMHO, I would use Odin to put cwm back on the phone then download any ROM I want or the flash to stock, or even better if you followed the rules restore a nandroid
Sent from my SGH-T679 using xda app-developers app
theAPANT said:
The t679 IS the exhibit 2 (although it was renamed the galaxy exhibit). The original exhibit aka just plain exhibit 4g t759 is the older model. It sounds like you have the t679 if that is correct, follow these instructions http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
Do not follow those instructions if you do not have that phone. Google if you are unsure about the phone you have because if done right for the right phone these steps are perfectly safe. If however you have the wrong phone you will ruin it pretty badly. On that cheerful note, good luck!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I do have the renamed t679. I must be doing something wrong. First I put it into restore mode and clear the cache then restart in download mode. Then I start the Odin Multi Downloader (Ancora) and insert into the OPS field the Ancora.ops then insert into the One Package field the T679LG3.tar file then hit start until all automatically finishes.
I am still left with a phone in the boot logo loop. I noticed when I wiped the cache and restarted the phone script said something about " unable to mount \system .... I didn't take a snapshot so I'm not exactly sure of what it was but I know the phone will not start up if it can't mount the system partition, at least I think I saw that somewhere in a thread.
Any suggestions? I wish I knew someone around Atlanta that I could join up with and get this thing working. I loved this phone and only used it for about a week. I'm thinking before all this is over I will be a phone geek instead of a newbie. All the information that I have gotten here is super helpful, I just don't know enough to effectively utilize it.
patches0616 said:
I do have the renamed t679. I must be doing something wrong. First I put it into restore mode and clear the cache then restart in download mode. Then I start the Odin Multi Downloader (Ancora) and insert into the OPS field the Ancora.ops then insert into the One Package field the T679LG3.tar file then hit start until all automatically finishes.
I am still left with a phone in the boot logo loop. I noticed when I wiped the cache and restarted the phone script said something about " unable to mount \system .... I didn't take a snapshot so I'm not exactly sure of what it was but I know the phone will not start up if it can't mount the system partition, at least I think I saw that somewhere in a thread.
Any suggestions? I wish I knew someone around Atlanta that I could join up with and get this thing working. I loved this phone and only used it for about a week. I'm thinking before all this is over I will be a phone geek instead of a newbie. All the information that I have gotten here is super helpful, I just don't know enough to effectively utilize it.
Click to expand...
Click to collapse
OK now use the volume up and power to get to a screen with a box and then hit menu that will bring you to a recovery and just click wipe data factory reset and you should be fine.
Sent from my Nexus 7 using xda app-developers app
theAPANT said:
OK now use the volume up and power to get to a screen with a box and then hit menu that will bring you to a recovery and just click wipe data factory reset and you should be fine.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I've tried that more than ten times to no avail. I get the feeling that the original OS may be corrupt or missing or maybe that "unable to mount" message that I saw.
patches0616 said:
I've tried that more than ten times to no avail. I get the feeling that the original OS may be corrupt or missing or maybe that "unable to mount" message that I saw.
Click to expand...
Click to collapse
OK well if it boots to the android icon with green fire or whatever then you have an os. My only advice is to make sure you check the right things when using Odin.
Edit: there is a very slim possibility that you have a fried emmc chip but I doubt it. Also make sure it says pass before you unplug
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 09:44 PM ---------- Previous post was at 09:20 PM ----------
How far do you boot to? How long does it take for Odin to finish?
Sent from my Nexus 7 using xda app-developers app
Odon does the same thing to me, it says pass but still boot loops, that's why I recommend just doing cwm through Odin and flash the b2s or any ROM you desire
Sent from my SGH-T679 using xda app-developers app
theAPANT said:
OK well if it boots to the android icon with green fire or whatever then you have an os. My only advice is to make sure you check the right things when using Odin.
Edit: there is a very slim possibility that you have a fried emmc chip but I doubt it. Also make sure it says pass before you unplug
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 09:44 PM ---------- Previous post was at 09:20 PM ----------
How far do you boot to? How long does it take for Odin to finish?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
When I run the Odin Multi Downloader program it takes 5 mins and 38 secs to finish. The phone restore Odin is fairly fast when I reset to factory settings but I've never timed it. The phone boots to the t-mobile exhibit screen just beyond the plain white Samsung start up screen.
patches0616 said:
When I run the Odin Multi Downloader program it takes 5 mins and 38 secs to finish. The phone restore Odin is fairly fast when I reset to factory settings but I've never timed it. The phone boots to the t-mobile exhibit screen just beyond the plain white Samsung start up screen.
Click to expand...
Click to collapse
Hmm when I've done it it took about 10min, so perhaps the 300 sec reset option is not set. Try what tazmanion said by using Odin to flash cwm and then you can Mount system in revovery
If it doesn't get to boot animation then yea you have no os
Sent from my Nexus 7 using xda app-developers app
I'm also still having bootloop issues, I wiped cache/dalvik, fixed permissions, wiped battery stats, etc. but best it did was sit on the SAMSUNG for like 2 minutes then go back into a bootloop.
I'd like to keep the original rom/system in tact to not loose any data (didn't backup beforehand, I know...) anyone have suggestions?
Thanks in advance.
(yes this is crossposted, need answer asap, sorry)
You do not have a ROM if it sits in Samsung
Sent from my SGH-T679 using xda app-developers app
:cyclops: hello. (I have been searching for quite some time. and have not found a thread that has helped me along. disclaimer.)
I have recently installed the custom LinaroCM10 ROM for the Samsung Galaxy Exhibit II 4G (t679), and upon restoring my apps and data via Titanium backup, the messaging (i could open the app, but not individual threads), exchange, (and email?) services ceased to function. that it does not come with wifi calling, (which is necessary while I am at home), I searched for another ROM. Excited by the possibility of wifi calling, i immediately endeavored to install jedimindtricks x3, only to find that it is not for my phone in the least. Now, between multiple Clockworkmod (v6.0.1.2) wipes of everything, I am left with a phone that will only boot into recovery or download mode.
I am currently trying to flash the stock file - uvlg3.flash2stock.zip via ADB (platform-tools), but to no avail. I have made many silly mistakes, but I would very much like to bring my phone back to normal, so that I may...root it again. I greatly appreciate any and all assistance kindly bequeathed upon my novice eyes and ears. Thank you.
robbiegeiss said:
:cyclops: hello. (I have been searching for quite some time. and have not found a thread that has helped me along. disclaimer.)
I have recently installed the custom LinaroCM10 ROM for the Samsung Galaxy Exhibit II 4G (t679), and upon restoring my apps and data via Titanium backup, the messaging (i could open the app, but not individual threads), exchange, (and email?) services ceased to function. that it does not come with wifi calling, (which is necessary while I am at home), I searched for another ROM. Excited by the possibility of wifi calling, i immediately endeavored to install jedimindtricks x3, only to find that it is not for my phone in the least. Now, between multiple Clockworkmod (v6.0.1.2) wipes of everything, I am left with a phone that will only boot into recovery or download mode.
I am currently trying to flash the stock file - uvlg3.flash2stock.zip via ADB (platform-tools), but to no avail. I have made many silly mistakes, but I would very much like to bring my phone back to normal, so that I may...root it again. I greatly appreciate any and all assistance kindly bequeathed upon my novice eyes and ears. Thank you.
Click to expand...
Click to collapse
Everything you need is here http://forum.xda-developers.com/showthread.php?t=1686384 in post #2. Have you tried dropping the uvlg3.flash2stock.zip on your external sd card and flashing?
NomadSpin said:
Everything you need is here http://forum.xda-developers.com/showthread.php?t=1686384 in post #2. Have you tried dropping the uvlg3.flash2stock.zip on your external sd card and flashing?
Click to expand...
Click to collapse
Yes. I have the necessary zip files, But my problem is actually getting them through via cmd/ADB
i type
"cd desktop/platform-tools"
brings me to the correct folder
then I don't know what to type to correctly push the file with ADB
file path is:"C:\Users\Robbie\Desktop\platform-tools\uvlg3.flash2stock.zip"
Step 6: http://www.londatiga.net/it/how-to-use-android-adb-command-line-tool/
Edit: try adb push C:\Users\Robbie\Desktop\platform-tools\uvlg3.flash2stock.zip /storage/sdcard0
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
Good luck. Flashing a ROM through adb was only ever really achieved on HTC phones. I would just flash through recovery since you can access it. Or since this is a Samsung phone the other option is Odin. If you attempt an adb flash you may risk bricking your phone.
P.S. first result in Google searching " flash android rom adb."
Sent from my SGH-T679 using xda app-developers app
---------- Post added at 03:33 PM ---------- Previous post was at 03:28 PM ----------
Also the problem you had with your previous rom could have been avoided if you hadn't have restored data with Titanium. This has caused issues over and over, and has been stated in several threads. Many times it is incompatible data from another rom. Restoring apps is fine data is tricky and usually causes problems. Hope you get things sorted out.
Sent from my SGH-T679 using xda app-developers app
Dvarl said:
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
Good luck. Flashing a ROM through adb was only ever really achieved on HTC phones. I would just flash through recovery since you can access it. Or since this is a Samsung phone the other option is Odin. If you attempt an adb flash you may risk bricking your phone.
P.S. first result in Google searching " flash android rom adb."
Sent from my SGH-T679 using xda app-developers app
---------- Post added at 03:33 PM ---------- Previous post was at 03:28 PM ----------
Also the problem you had with your previous rom could have been avoided if you hadn't have restored data with Titanium. This has caused issues over and over, and has been stated in several threads. Many times it is incompatible data from another rom. Restoring apps is fine data is tricky and usually causes problems. Hope you get things sorted out.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
Thank very much you Dvarl. I looked into using ODIN and it does indeed seem I have fixed my phone (using: http://androidforums.com/exhibit-2-...bit-ii-4g-back-its-factory-out-box-state.html). Thank you so much, and everyone else, as well, for the advice!!!
Glad you got it straightened out. Just would hate to see someone brick their phone. Out of of the 8 devices I have rooted I have only ever bricked one. That was my fault alone as I overclocked too high and fried my phone.
Sent from my SGH-T679 using xda app-developers app
Dvarl said:
Glad you got it straightened out. Just would hate to see someone brick their phone. Out of of the 8 devices I have rooted I have only ever bricked one. That was my fault alone as I overclocked too high and fried my phone.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
Haha. Indeed. Hardware destruction seems pretty irrevocable on this scale. Does overclocking usually fry?
If it is kept at safe values no. I made the mistake of going 1.8 for too long safest value for this phone is no higher than 1.4. But it should be noted that these phones vary greatly and some people can only go 1.2, some not at all.
Sent from my SGH-T679 using xda app-developers app
Dvarl said:
If it is kept at safe values no. I made the mistake of going 1.8 for too long safest value for this phone is no higher than 1.4. But it should be noted that these phones vary greatly and some people can only go 1.2, some not at all.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
of course. It depends on the original processing rate, yes?
For the most part. There is a safe level for each processor. On this phone all were stable at 1GZ but some can be safely overclocked, Smartguy found that anything over 1.4 can seriously damage the phone. So that is only a guide, some of these processors can't be over clocked at all. It really depends on your phone. I you want more information about this I suggest reading the kernel threads. There are more experienced answers there.
Sent from my SGH-T679 using xda app-developers app
I purchased the AT&T version of the Galaxy Note 3 a little less than a week ago and, to be honest, I'm not really keen on it. There are a number of reasons, but what it boils down to is that I just don't think I like it all that much. I've already sold my Galaxy Note 2, so I'll have to figure out what I'm going to do about a cell phone, but that's something beyond the scope of this particular posting. What I need help with is how to unroot this device. I used the Root De La Vega procedure very shortly after it came out and it worked like a charm. I noted that when the phone boots up, there is the word "Custom" and an unlocked padlock. How do I get this AT&T model of the Galaxy Note 3 back to the condition, more or less, of when I bought it about a week ago so that I won't have any issues getting the refund processed? I've heard some people requesting help with unrooting and they've been told to use the unroot in SuperUser. Will this get rid of the "Custom" wording on boot-up AND the unlocked padlock? If not, is there a way to get this back to the way it was or am I just out of luck since I only have about another week to return this device. Obviously, if I'm stuck, I'm stuck and I'll find a way to live with it. Who knows...I might actually get to liking it down the road when some of the quirks have been worked out. However, if there's a way to sort all of this out in a timely manner where there's no muss or fuss, that would be the ideal solution. Any help would be greatly appreciated.
KennyXL said:
I purchased the AT&T version of the Galaxy Note 3 a little less than a week ago and, to be honest, I'm not really keen on it. There are a number of reasons, but what it boils down to is that I just don't think I like it all that much. I've already sold my Galaxy Note 2, so I'll have to figure out what I'm going to do about a cell phone, but that's something beyond the scope of this particular posting. What I need help with is how to unroot this device. I used the Root De La Vega procedure very shortly after it came out and it worked like a charm. I noted that when the phone boots up, there is the word "Custom" and an unlocked padlock. How do I get this AT&T model of the Galaxy Note 3 back to the condition, more or less, of when I bought it about a week ago so that I won't have any issues getting the refund processed? I've heard some people requesting help with unrooting and they've been told to use the unroot in SuperUser. Will this get rid of the "Custom" wording on boot-up AND the unlocked padlock? If not, is there a way to get this back to the way it was or am I just out of luck since I only have about another week to return this device. Obviously, if I'm stuck, I'm stuck and I'll find a way to live with it. Who knows...I might actually get to liking it down the road when some of the quirks have been worked out. However, if there's a way to sort all of this out in a timely manner where there's no muss or fuss, that would be the ideal solution. Any help would be greatly appreciated.
Click to expand...
Click to collapse
I'm not super familiar with the unrooting process, but try to unroot using SuperSU and reboot a couple of times to see if it goes away. If that doesn't work then flash the original firmware with odin and that should do it. Pretty easy to do from what I understand.
agent929 said:
I'm not super familiar with the unrooting process, but try to unroot using SuperSU and reboot a couple of times to see if it goes away. If that doesn't work then flash the original firmware with odin and that should do it. Pretty easy to do from what I understand.
Click to expand...
Click to collapse
Perhaps this is showing my ignorance, but since the AT&T Galaxy Note 3 has a locked bootloader (which, as of yet, has not been unlocked), would that prevent Odin from flashing a new image? If I don't need an unlocked bootloader to flash with Odin, do you know where I might find the original image that came with my phone from AT&T in a format that Odin can flash? I haven't tried the SuperSU yet since I want all my options readily available so that if one fails, I can move on to the next one.
KennyXL said:
Perhaps this is showing my ignorance, but since the AT&T Galaxy Note 3 has a locked bootloader (which, as of yet, has not been unlocked), would that prevent Odin from flashing a new image? If I don't need an unlocked bootloader to flash with Odin, do you know where I might find the original image that came with my phone from AT&T in a format that Odin can flash? I haven't tried the SuperSU yet since I want all my options readily available so that if one fails, I can move on to the next one.
Click to expand...
Click to collapse
To my understanding you can flash anything with Odin on a locked bootloader phone that is "signed". If you give me a few minutes I'll help you look for the original odin file to flash.
agent929 said:
I'm not super familiar with the unrooting process, but try to unroot using SuperSU and reboot a couple of times to see if it goes away. If that doesn't work then flash the original firmware with odin and that should do it. Pretty easy to do from what I understand.
Click to expand...
Click to collapse
agent929 said:
To my understanding you can flash anything with Odin on a locked bootloader phone that is "signed". If you give me a few minutes I'll help you look for the original odin file to flash.
Click to expand...
Click to collapse
I really appreciate your help. Every time I've used Odin in the past has involved a phone with a non-locked bootloader (as far as I know) so this is new territory for me.
KennyXL said:
I really appreciate your help. Every time I've used Odin in the past has involved a phone with a non-locked bootloader (as far as I know) so this is new territory for me.
Click to expand...
Click to collapse
Not a problem. I've been looking for that odin file with no luck. I would PM designgears and ask him if he can provide a link for it because you couldn't find it.
agent929 said:
Not a problem. I've been looking for that odin file with no luck. I would PM designgears and ask him if he can provide a link for it because you couldn't find it.
Click to expand...
Click to collapse
Thanks. I'll give that a try.
Use the same file that u used to root. The one with the one click. After it pass, you're back to stock. i just did it yesterday.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
If you looked at the root thread you'd see directions to unroot right there.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
panday74 said:
Use the same file that u used to root. The one with the one click. After it pass, you're back to stock. i just did it yesterday.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Zach Alt said:
If you looked at the root thread you'd see directions to unroot right there.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
What they said
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4
panday74 said:
Use the same file that u used to root. The one with the one click. After it pass, you're back to stock. i just did it yesterday.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried the SuperSU full unroot method - didn't remove the padlock, flashed the one click - didn't remove it, and just flashed the second (for funsies) and that didn't help (probably shouldn't have expected it to).
I'm returning my note and can't get rid of the lock. Will PM Designgears I guess
Did you restart it a few times? Also a factory reset?
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
seanu13 said:
I tried the SuperSU full unroot method - didn't remove the padlock, flashed the one click - didn't remove it, and just flashed the second (for funsies) and that didn't help (probably shouldn't have expected it to).
I'm returning my note and can't get rid of the lock. Will PM Designgears I guess
Click to expand...
Click to collapse
I was kinda wondering how to remove the padlock also. I have read that some people that haven't even rooted have the padlock on boot up also??? I read somewhere about triangle away working, have you tried that?
agent929 said:
Did you restart it a few times? Also a factory reset?
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
Click to expand...
Click to collapse
yes to both (restarted 5 times). since i was already so far into the root process, I added the files to the sdcards that are in the root steps, and the lock went away. Then I finished rooting.
went back and did one click again and still had the lock after rebooting 5 times. Thought about how it went away after adding the files so I skipped through the phone setup, enabled USB debugging again and added a dummy file to the sd card (a .csv I had on my desktop) and then removed it. Rebooted, and the lock was gone.
I'd use the padlock hack in Wanum and hide the root apps via Nova Launcher just to stick it to ATT and return it rooted.
Sent from my SAMSUNG-SM-N900A using xda premium
Omg, just reflash the stock rom from the package. Says so in the instructions.
READ!
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Jammol said:
Omg, just reflash the stock rom from the package. Says so in the instructions.
READ!
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you READ, you will see he already did that.
agent929 said:
If you READ, you will see he already did that.
Click to expand...
Click to collapse
The last post that was here when I posted was yours. That's why I posted for him to Read the instructions.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Ok well here's what I did and the padlock is gone.
Factory reset on the phone
Phone rebooted and I removed the super su app using the setting in the su app.
Then flashed the one click 9 tar
phone reboots on its own after flashing, icon was still there
rebooted the phone twice and the padlock was gone
Not sure if I just got lucky or what lol
Jammol said:
The last post that was here when I posted was yours. That's why I posted for him to Read the instructions.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got ya..tapatalk has been mean to me too lol
---------- Post added at 10:26 AM ---------- Previous post was at 10:25 AM ----------
Quickvic30 said:
Ok well here's what I did and the padlock is gone.
Factory reset on the phone
Phone rebooted and I removed the super su app using the setting in the su app.
Then flashed the one click 9 tar
phone reboots on its own after flashing, icon was still there
rebooted the phone twice and the padlock was gone
Not sure if I just got lucky or what lol
Click to expand...
Click to collapse
I know you have to reboot a few times to set the status somehow, iB4STiD explained it in one of his post before.
So I have an LG G2 that I used AutoRec on and it flashed a different kernel not compatible with the display type. I flashed the stock ROM back thinking it would fix the problem but it did not. Does anyone know how to flash the right kernel for the display? I've been looking but it seems I'm going to have no luck since I just flashed back to stock and I need root and a custom recovery to do so. Any help would be appreciated, thanks.
Pictures of my problem below.
Sent from my SM-N900V using XDA Free mobile app
mexicanhobo said:
So I have an LG G2 that I used AutoRec on and it flashed a different kernel not compatible with the display type. I flashed the stock ROM back thinking it would fix the problem but it did not. Does anyone know how to flash the right kernel for the display? I've been looking but it seems I'm going to have no luck since I just flashed back to stock and I need root and a custom recovery to do so. Any help would be appreciated, thanks.
Pictures of my problem below.
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
The OP has a link under the warning to get the JDI version. http://forum.xda-developers.com/showthread.php?t=2715496 Read ,read, read. There's also a tool in G2 Android Development that will detect if your pannel is LGD or JDI.
Sent from my XDABBEB VS98025A v2.0.0 using XDA free mobile app
I have looked through that whole thread and it seems you need to be able to use recovery and have root permission. Most of them claim to have only a few lines but they are still able to see their screen. Mine stays how it looks in the picture 100% of the time. I used the TOT method before to flash it back to stock but it seems that didn't do anything to fix it, that's why I'm asking on this forum. Since it's complete stock and I have no way of seeing what's going on on the display. For some reason it seems to boot up into download mode also without me doing anything but turning it on. If you have any experience with this issue could you inform me about it? Thanks, man.
Sent from my SM-N900V using XDA Free mobile app
mexicanhobo said:
I have looked through that whole thread and it seems you need to be able to use recovery and have root permission. Most of them claim to have only a few lines but they are still able to see their screen. Mine stays how it looks in the picture 100% of the time. I used the TOT method before to flash it back to stock but it seems that didn't do anything to fix it, that's why I'm asking on this forum. Since it's complete stock and I have no way of seeing what's going on on the display. For some reason it seems to boot up into download mode also without me doing anything but turning it on. If you have any experience with this issue could you inform me about it? Thanks, man.
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
Can you get into recovery? Try grabbing the kernel here and flashing it.
http://forum.xda-developers.com/showpost.php?p=51974589&postcount=281
Otherwise if the screen is like this 100% of the time, I'd say it's farked, use the return to stock guide and take it back for a replacement.
Thank for replying, unfortunately that is the answer to my question. It is like that 100% of the time and I flashed stock back on to it thinking it would fix the problem. This leaves me with a messed up screen and a phone without any root or custom recovery. I will ask, is it possible to flash a kernel in stock somehow with adb or anything of the sort? I have already sent it in for a replacement so I don't think I will be able to send it in again.
Sent from my SM-N900V using XDA Free mobile app