Database Develop

Touch Screen not working after ICS update

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

Has anyone else gotten this while rooting?

Hey guys. I ran into some trouble trying to root my note 3 and got this message. Now the phone won't turn on our connect to kies to try to repair it. I have the Samsung drivers installed and I believe I followed the directions closely. Can any of you tell me how to get back to factory settings or all the way through the root process. I'm stuck at this screen for now. Any help would be awesome.
Sent from my Nexus 7 using xda app-developers

Try using the one click oding to get back to the stock firmware. Put the phone in download mode and flash the first step of the root procedure and then stop and make sure your phone will work in stock form first before you try rooting it again.

Quickvic30 said:
Try using the one click oding to get back to the stock firmware. Put the phone in download mode and flash the first step of the root procedure and then stop and make sure your phone will work in stock form first before you try rooting it again.
Click to expand...
Click to collapse
Instead of Pass in a green box, I get Failed in a red box and the progress bar on the phone stops

That's not good, maybe try a new download. Which firmware are you flashing? MI1 or MI9?

That's actually what happened when I tried to root. It would sit forever and fail due to a timeout. What I did is after the failure..I left the phone in dl mode and connected and closed the odin..then relaunched odin and it worked the second time. That's my experience and your mileage may vary..

Same thing!
xavier6303 said:
That's actually what happened when I tried to root. It would sit forever and fail due to a timeout. What I did is after the failure..I left the phone in dl mode and connected and closed the odin..then relaunched odin and it worked the second time. That's my experience and your mileage may vary..
Click to expand...
Click to collapse
The exact same thing happened to me... I tried to install Kies 3 and add the drivers but to no avail. So from there on I just closed everything. Disconnected my note 3, reconnected it, and ran odin once more. It immeadiately passed and rooted my phone.

I have seen that in the past it is the sign of a brick you definitely have to Odin back to stock to fix that
Sent from my SAMSUNG-SM-N900A using xda app-developers app

Yes it happened to me too. I just figured it was my crappy computer so I continued to try and after the 4th try I was able to achieve root status. Like a previous commenter suggested, it's a timed out issue.

Yea. I must have tried a dozen times a dozen different ways and I was stuck. I just said eff it and got a new phone. Debating if I want to try again, but I don't feel like potentially going thru the same heart ache. Really the only reason I care to root this phone is to get rid of those damn bloat ware apps; especially My Magazine.
Sent from my SAMSUNG-SM-N900A using xda app-developers app

alpinesun said:
Instead of Pass in a green box, I get Failed in a red box and the progress bar on the phone stops
Click to expand...
Click to collapse
It was MI9
Sent from my SAMSUNG-SM-N900A using xda app-developers app

alpinesun said:
It was MI9
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Just went thru this on my Note 3 - chances are youre using a vm on a mac arent you?
Make sure you use a dedicated *windows* machine and not a vm (or at lest not a fusion VM) That was my issue, I havent tried parallels. I grabbed a dedicated win 7 machine and it works perfectly.
I was going to return it of that failed, which luckily it didnt.
Cheers

[HOW TO]Update from stock rooted MF9/MJA/MK2 to NAE (with root) without losing data

Updated for NAE. When the NAE tar.md5 comes out you can just flash it directly rather than doing all this.
This will update everything (firmware, modem, bootloader, ROM, recovery, etc) to NAE. As long as you're coming from stock or mostly stock, this should work, and you will still have all your data and apps. It will also probably work coming from another MF9, MJA, or MK2 based ROM, but you may have problems (in which case you can just wipe data. The whole process should take less than 30 minutes, not counting the time it takes to download the stock tar.md5 image. I recommend starting it now (link in Step 2) so it will be ready when you need it. This will NOT work if you've already tried to take the NAE OTA and it failed because you weren't fully stock.
You will need odin. It can be downloaded from this thread. Alternatively, if you're using OS X or Linux, I found that Heimdall works very well in place of odin. There are a few extra steps involved though, but if you install Heimdall Frontend then you don't have to mess with the terminal.
Step 1: Backup your current ROM with TWRP, CWM, or Philz.
Step 2: Download the MK2 tar.md5 from sammobile. Sammobile is pretty slow to download, but I found a mirror and a second mirror. I also made a torrent that might be faster (please seed if you use it to speed it up for everyone). Flashing this with odin does NOT wipe data. You can verify it by opening it in an a program that supports tar and looking at the files within it; those are the partitions it overwrites. This will give you stock MK2 recovery, bootloader, modem, firmware, and software.
Step 3: Use odin to flash it over your current ROM. To do this, you need to first put the phone into download mode. Power it off completely, then press and hold volume down, home, and power. Then connect it to your computer.
In odin, I just left default odin settings checked. Make sure that you add the tar.md5 in the PDA slot and apply it. Reboot and verify that your data is all there. You can still easily revert to the backup you made in Step 1 if things aren't right.
Step 4: Put the MK2 to NAE OTA on your external sd card (not internal). You don't need to rename it.
Power the phone off completely. Then press and hold home, volume up, and power to get into stock recovery. Navigate to where you put the OTA zip on your external sd card and flash it. It will reboot a couple times during the update, including one time where it seems like it's booted up and done before it powers off again. You'll know it's done when you get a popup notification saying it completed successfully. All your data and apps should still be there.
Note: From this point on, performing any of these steps will set the Knox flag. So if you just purchased the phone (within your return window) or are having issues and may need a replacement, you may want hold off on root. Sprint may or may not check for this during a warranty replacement. Insurance replacements should be fine.
Step 5: Go back into download mode and flash CF Auto Root through odin. You should now have root, and knox will not complain. You'll need to re-download the SuperSU app from the Play Store though. Open the app and let it update the su binary to the newest version.
Step 6: Flash TWRP (or CWM or Philz) through odin (it didn't work for me with goo manager). Optionally reboot into recovery to make sure it actually stuck.

Ingenium13 said:
As long as you're coming from stock or mostly stock, this should work, and you will still have all your data and apps. It will also probably work coming from another MF9 based ROM, but you may have problems (in which case you can just wipe data. See note at the end if you're using Titanium Backup). The whole process should take less than 30 minutes. It will NOT work if you've already tried to take the MJA OTA and it failed.
Step 1: Backup your current ROM with TWRP, CWM, or another recovery.
Step 2: Download the MF9 tar.md5 from sammobile (here is a fast mirror: http://goo.gl/gky86G, sourced from here). This one does NOT wipe data. You can verify it by opening it in an a program that supports tar and looking at the files within it; those are the partitions it overwrites.
Step 3: Use odin to flash it over your current MF9 ROM. Reboot and verify that your data is all there. You can still easily revert to the backup you made in Step 1 if things aren't right.
Step 4: Put the OTA on your external sd card (not internal). Power the phone off completely. Then press and hold home, volume up, and power to get into stock recovery. Navigate to where you put the OTA zip on your external sd card and flash it. It will reboot a couple times during the update, including one time where it seems like it's booted up and done before it powers off again. You'll know it's done when you get a popup notification saying it completed successfully. All your data and apps should still be there.
Step 5: Go back into download mode and flash CF Auto Root through odin. You should now have root, and knox will not complain. You'll need to re-download the SuperSU app from the Play Store though. Open the app and let it update the su binary to the newest version.
Step 6: Flash TWRP (or CWM) through odin (it didn't work for me with goo manager). Optionally reboot into recovery to make sure it actually stuck.
It seems that with all the issues with the new firmware, that it's actually worth the trouble to do it the "official" way to make sure it works, especially since it's trivial to get root back. Follow these steps and you should be fine.
NOTE: For those who want to wipe data anyway (or have to because they're having problems), Titanium Backup is currently not working properly with MJA. The workaround is to manually install your apps from the Play Store and then restore just the data from Titanium Backup. Restoring the apps themselves through Titanium Backup causes problems at the moment.
Click to expand...
Click to collapse
You WILL Knox Warranty Void with this method.

Is there a workaround for tripping Knox?

Not yet. A method will probably be developed, but it will involve flashing a custom kernel that doesn't require the new bootloader. The version of MJA would have to have this kernel included. The stock kernel seems to not boot without the new bootloader. You will have to keep using a custom kernel from that point onward.

Ingenium13 said:
Not yet. A method will probably be developed, but it will involve flashing a custom kernel that doesn't require the new bootloader. The version of MJA would have to have this kernel included. The stock kernel seems to not boot without the new bootloader. You will have to keep using a custom kernel from that point onward.
Click to expand...
Click to collapse
Sorry, where do I find the OTA MJA update?

For those of us new to Odin, can we get a screenshot of what should and shouldn't be checked?
Edit: Nothing NEEDS to be checked.
Checking Auto Reboot does just that, but doesn't seem to work for me.
Checking R.Flash Time resets a counter, not a big deal, either.
The rest uncheck.
Anyways, that all worked. I tried combining the Odin'ing of CF Root and recovery, until I saw that the CF-Auto-Root restores the old recovery as one of the steps...

with this method do we get the mja modem?
if the option available to go back to aosp 4.3 if we dont like it? 4.2 tw?

aberchonbie said:
Sorry, where do I find the OTA MJA update?
Click to expand...
Click to collapse
To be more specific, where is the OTA downloaded to?
I would like help with the file location also. Thanks.
FOUND IT in the Cache folder. You must allow root permissions in your file explorer.

Can I follow these steps if I have TWRP instead of stock recovery?
Also, what update for to apply?

After reading in this forum, non stop since Oct. 28, I took the plunge and did the dirty deed late last night with the downloadable OTA, after restoring to stock.
I woke up this morning and the Keebler elves hooked me up. I was fully rooted and all I had to do was reinstall Clockwork.
Mobile ODIN and SuperUser's Keep root are what's happening.
I have been looking for any glitches this morning but this thing runs perfect. I did see a security warning once that I assume is the Knox thingy I read so much about. Other than that, I'm gravy.
Now, can someone remind me why I upgraded?
I mean, what did I gain by leaping to 4.3? Is there something under the hood I ain't seeing?

Bonefishbf3 said:
To be more specific, where is the OTA downloaded to?
I would like help with the file location also. Thanks.
FOUND IT in the Cache folder. You must allow root permissions in your file explorer.
Click to expand...
Click to collapse
Here's a link to the update zip directly from Google's servers: http://android.clients.google.com/p...CSB_user_RP_to_MJA_CSB_user_RP_Update_FWD.zip
You don't have to rename it, just put it on your external SD card and navigate to it in the stock recovery.
M3wThr33 said:
For those of us new to Odin, can we get a screenshot of what should and shouldn't be checked?
Edit: Nothing NEEDS to be checked.
Checking Auto Reboot does just that, but doesn't seem to work for me.
Checking R.Flash Time resets a counter, not a big deal, either.
The rest uncheck.
Anyways, that all worked. I tried combining the Odin'ing of CF Root and recovery, until I saw that the CF-Auto-Root restores the old recovery as one of the steps...
Click to expand...
Click to collapse
Just leave the default checked, and it will be fine. The only one that really matters is that re-partion is NOT checked.
Memphisjojo said:
with this method do we get the mja modem?
if the option available to go back to aosp 4.3 if we dont like it? 4.2 tw?
Click to expand...
Click to collapse
Yes, you get the MJA modem as well. I believe AOSP 4.3 works fine with the new modem and bootloader, but I haven't tried it.
Bielinsk said:
Can I follow these steps if I have TWRP instead of stock recovery?
Also, what update for to apply?
Click to expand...
Click to collapse
The OTA won't apply with TWRP. Follow the steps and you'll get the stock recovery back when you odin to stock MF9. You can then update to TWRP after re-rooting.

Just did the update only issue im having is No WiFi??Any solutions?? Thanks

rob97ss said:
Just did the update only issue im having is No WiFi??Any solutions?? Thanks
Click to expand...
Click to collapse
Did you try updating to MJA before this?
Sent from my SPH-L720 using Tapatalk

Ingenium13 said:
Did you try updating to MJA before this?
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
No.Any ideas??
Sent from my SPH-L720 using XDA Premium 4 mobile app

rob97ss said:
No.Any ideas??
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Were you coming from stock rooted MF9? Losing wifi is a common problem with anyone who didn't fully take the OTA.
There is a wifi fix in this thread that supposedly will cleanly apply to the stock kernel as well as the custom kernel listed, but I haven't tried it http://forum.xda-developers.com/showpost.php?p=47030804&postcount=1638
Sent from my SPH-L720 using Tapatalk

Ingenium13 said:
Were you coming from stock rooted MF9? Losing wifi is a common problem with anyone who didn't fully take the OTA.
There is a wifi fix in this thread that supposedly will cleanly apply to the stock kernel as well as the custom kernel listed, but I haven't tried it http://forum.xda-developers.com/showpost.php?p=47030804&postcount=1638
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Thanks buddy.. WiFi fixed..Stock kernel...
Sent from my SPH-L720 using XDA Premium 4 mobile app

Ingenium13 said:
Step 2: Download the MF9 tar.md5 from sammobile (here is a fast mirror: http://goo.gl/gky86G, sourced from here). This one does NOT wipe data. You can verify it by opening it in an a program that supports tar and looking at the files within it; those are the partitions it overwrites. This will give you stock MF9 recovery, bootloader, modem, firmware, and software.
Click to expand...
Click to collapse
I had to install this ROM twice via Odin3 to get stock recovery back.

This seems to be the only side affect of flashing to 4.3. I guess it's a Knox thing.
Is there a fix for this?
Sent from my SPH-L720 using XDA Premium 4 mobile app

SpringerRider said:
This seems to be the only side affect of flashing to 4.3. I guess it's a Knox thing.
Is there a fix for this?
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You could freeze the Knox apps (filter for them in titanium backup). I had no issues with knox until yesterday when I got a notification in the drawer when I used su (but su worked fine when this happened). I just froze all the apps with knox in the name and it's been fine since.
Also, there's a check box somewhere in the Android settings to tell it not to update the Knox list. I unchecked that as well.
Sent from my SPH-L720 using Tapatalk

stuck on yellow Sprint Boot Screen after step 3
Help......after running step 3 and using odin I am stuck on the yellow sprint boot screen.
Any Ideas on what to do from here?

WARNING! TOWELROOT:Phone does not boot after enabling U Power Saving Mode

UPDATE2: This only seems to happen if you uninstall the Launcher system app. Mine does not seem to be affected by Xposed or other mods, and works 100% fine now in U Power Saving.
Just decided to try Ultra Power Saving mode after rooting and modding my phone yesterday. I'm not sure what exactly caused it (xposed, root, w.e) but my phone will not boot past the ATT Globe now. Just thought everyone might appreciate a heads up that they may have to factory reset after enabling this setting.
I'll update if my phone decides to boot up (letting it sit now)
UPDATE: It seems that after rooting, U power saving does have the potential to BRICK your phone. DO NOT ENABLE FOR ANY REASON AFTER ROOTING.

My gut says the culprit was uninstalling Launcher.apk (thought it was the google launcher >_>) gonna have to factory reset now.

More info dude
You might have just freaked out a noob here. Root was just achieved yesterday for the Verizon and ATT platform. Please post your hardware software state so we don't get confused here.

chronicaust said:
Just decided to try Ultra Power Saving mode after rooting and modding my phone yesterday. I'm not sure what exactly caused it (xposed, root, w.e) but my phone will not boot past the ATT Globe now. Just thought everyone might appreciate a heads up that they may have to factory reset after enabling this setting.
I'll update if my phone decides to boot up (letting it sit now)
Click to expand...
Click to collapse
Same here cant get past the logo did a factory reset in recovery and still a no go. I tried to Odin back but still a no go as the files we have to return to stock are older I guess than the version I had on my phone. I am not 100% sure what caused it on my phone. Ive let mine sit for 20minutes or so and no go. took out the battery for a few hours etc no go. So now I am looking for Firmware KOT 49.G900AUCU2AND3.

pcidiot said:
Same here cant get past the logo did a factory reset in recovery and still a no go. I tried to Odin back but still a no go as the files we have to return to stock are older I guess than the version I had on my phone. I am not 100% sure what caused it on my phone. Ive let mine sit for 20minutes or so and no go. took out the battery for a few hours etc no go. So now I am looking for Firmware KOT 49.G900AUCU2AND3.
Click to expand...
Click to collapse
Are you sure that your didn't remove or freeze the launcher? If you don't have a third party launcher installed, freezing/removing the launcher.apk will cause the phone to not boot past the logo screen.

cjranucci said:
Are you sure that your didn't remove or freeze the launcher? If you don't have a third party launcher installed, freezing/removing the launcher.apk will cause the phone to not boot past the logo screen.
Click to expand...
Click to collapse
Nope I didn't delete any launchers. I left both in tacked stock and the Google launcher I was using before Root.

yup, enabling ultra power saving blows up the phone confirmed here also.. All i removed was the AT&T crap, shealth, drive mode, anda few other items.,. now phone is stuck at the black and white at&t logo wont do anything else..
---------- Post added at 03:54 PM ---------- Previous post was at 03:53 PM ----------
cjranucci said:
Are you sure that your didn't remove or freeze the launcher? If you don't have a third party launcher installed, freezing/removing the launcher.apk will cause the phone to not boot past the logo screen.
Click to expand...
Click to collapse
had apex launcher running and as default in my case. phone is frozen on (white/black like its in power saving mode AT&T logo)

Never. Delete. Stock. Apps. Just freeze them
Sent from my SAMSUNG-SM-G900A using Tapatalk

robstunner said:
Never. Delete. Stock. Apps. Just freeze them
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
I disagree. There are serious disk space concerns with this phone. If I am not going to use an app,and I have root, I am deleting it to recover the space it takes plus any associated files. If that breaks something, then that sucks. You can always reinstall through factory reset.

I'm fairly confident your wrong. Factory reset won't make uninstalled system apps reappear. That's why they don't let you delete them normally.

Just Odin back to stock after Odin flashes reboot into recovery and wipe all data reboot and all should be well
Sent from my SM-G900F using Tapatalk

cjranucci said:
I disagree. There are serious disk space concerns with this phone. If I am not going to use an app,and I have root, I am deleting it to recover the space it takes plus any associated files. If that breaks something, then that sucks. You can always reinstall through factory reset.
Click to expand...
Click to collapse
except where they said they tried to odin back in and no luck so try again

Suggest that someone change the title to include AFTER TOWELROOT in there. For someone like me who had the files on the phone but just didn't pull the trigger yet, it will better keep them informed.

cyberace1985 said:
except where they said they tried to odin back in and no luck so try again
Click to expand...
Click to collapse
willing to bet there's some user error involved...Odin back to stock should fix any issues.
Sent from my SM-G900F using Tapatalk

djkinetic said:
willing to bet there's some user error involved...Odin back to stock should fix any issues.
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
How much you willing to bet..
You wrong if you have lock bootloader and you took update and bootloader is updated you can't odin back to previous version. We don't have current (updated) odin file for AT&T S5 yet.
Swiping from dark side of Galaxy S5.

Can anyone confirm that after unrooting with superuser it Will be safe to use ultra power saving mode?
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app

vxkillswitchxv37 said:
Can anyone confirm that after unrooting with superuser it Will be safe to use ultra power saving mode?
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I confirm it.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app

Same with Samsung keyboard too. That's the only keyboard that works in UPS mode.

norbarb said:
How much you willing to bet..
You wrong if you have lock bootloader and you took update and bootloader is updated you can't odin back to previous version. We don't have current (updated) odin file for AT&T S5 yet.
Swiping from dark side of Galaxy S5.
Click to expand...
Click to collapse
try flashing the file without the boot loader.
Sent from my One M8 using Tapatalk

djkinetic said:
try flashing the file without the boot loader.
Sent from my One M8 using Tapatalk
Click to expand...
Click to collapse
Worked for me, and so far at least one other person in my thread.

[G925V][ODIN TARS/Tools][Downloads + Guides]

Hey All!
I did not see any threads with these downloads/instructions so I figured I would start one up now with root around the corner!
This thread will be the go to thread for anything related to the Galaxy S6 Edge (VZW.) It will include stock ODIN tar files, debloat tools, firmware files and links to other tools that work with our device such as Flashfire or Multisystem once they are out. I will also be creating and developing my own ROM which will also be linked here (will also have it's own thread in the Android Development thread.)
Included in this first post will be instructions for various processes as well as any tools that are required for most functions such as ODIN, device drivers etc.
PS: I am currently downloading the stock tar file for OC3 for the Verizon S6 Edge and I will then upload it to AFH for others to have access to. I will also be creating a ROM from the TAR file so hopefully as soon as root is available and multisystem/flashfire I will post the process and we will have a ROM ready to roll!
Tools/Necessities:
1) Samsung Smart Switch (replaces KIES, use this to backup+restore data etc.)
2) Samsung Mobile Drivers
3) ODIN
ODIN Flashing Instructions:
1) Ensure drivers are installed and ODIN is installed
2) Download the .tar files you wish to use to the PC (If they are in .zip format, just unzip them to get to the .tar or .tar.md5 file/s inside.)
3) Backup all data using the PC if you need to (if flashing a full ODIN tar, it typically wipes the entire system on the device. If just flashing firmware only it typically does not wipe system but a backup is always recommended.)
4) From powered off device, hold the Home + Volume Down + Power button until the "Download Mode" screen appears
5) Once the screen is on, press Volume Up to enter Download Mode
6) Open ODIN on the PC and Press the AP slot and navigate to and select the .tar file you are going to be flashing
7) Connect the device after ODIN checks the .tar file and once the device is recognized press Start in ODIN. (DO NOT UNPLUG DEVICE DURING THE ODIN FLASH.)
Download links will be in Post 2!

Downloads
Tools:
-Samsung Drivers
-Smart Switch
-Odin 3.10
ODIN Packages:
-G925VVZW1AOC3_REV02_USER_LOW_SHIP.TAR.MD5.ZIP
MD5: 6a29c894cb31551b86d5003acc2b0aad
(The OE2 tar does not wipe internals like OC3 but still always backup before using!)
G925VVRU1AOE2_G925VVZW1AOE2_VZW.ZIP
MD5: 3f39aa914b056d268ad09e3dc49c1c3b
OF1 and OCG (Thanks to Deuces)
WARNING: Read his OP but OF1 and OCG are NOT rooted and NOT downgradeable at this time so only use these if youre not rooted and know what you are doing as we are not responsible if you lose root!
OC3 and OE2 are rootable and downgradeable so use those first if youre able to!
http://forum.xda-developers.com/showthread.php?p=62616382

ROM Thread
Extreme Syndicate
Current Build Is v8:
-Alliance Framework v1.1
-Extremely Debloated
-Rooted + Busybox
-Zipaligned
-Deodexed
-V4A
-Custom Boot Animation
-Based on OE2
-Native Tethering
-DL Booster
-Removed CD Installer
-RAM Management Fix (partial)
-Removed Persistent Wifi Notification
-Smart Manager
-Quick Launch + Music Player Feeds
-MORE!
Link to Thread:
http://forum.xda-developers.com/showthread.php?p=60824588

Trying to reinstall firmware through Smart Switch.... messed up my system permissions by accident and now it is not booting past splash screen. I can handle it with ODIN, but in the meantime while downloading the .TAR I was messing around in Smart Switch and it gives an "Unsupported Device" message when i connect my Verizon S6 Edge.
Both Kies3 and the SmartSwitch.exe included in this post give same "Unsupported Device."
Anyone have any suggestions as to what PC client I am suppose to be using? Really just asking out of curiousity at this point.....ODIN files are almost done downloading.
___________________________________________________________
And OF COURSE, THANK YOU OP! Awesome collection of info and files here. Thanks for the hard work!

RedTerror98 said:
Trying to reinstall firmware through Smart Switch.... messed up my system permissions by accident and now it is not booting past splash screen. I can handle it with ODIN, but in the meantime while downloading the .TAR I was messing around in Smart Switch and it gives an "Unsupported Device" message when i connect my Verizon S6 Edge.
Both Kies3 and the SmartSwitch.exe included in this post give same "Unsupported Device."
Anyone have any suggestions as to what PC client I am suppose to be using? Really just asking out of curiousity at this point.....ODIN files are almost done downloading.
___________________________________________________________
And OF COURSE, THANK YOU OP! Awesome collection of info and files here. Thanks for the hard work!
Click to expand...
Click to collapse
its probably not recognizing it because partition/system is messed up..
i have the vzw s6 edge pit file if you need it but it is also in the full odin tar.. i recommend once you have everything up and running you use smartswitch to backup your phone.. it backed up everything imcluding my text messages for me so when i used it to retrieve the stock tar it restored everything right back!
Sent from my SM-G925V using XDA Free mobile app

elliwigy said:
its probably not recognizing it because partition/system is messed up..
i have the vzw s6 edge pit file if you need it but it is also in the full odin tar.. i recommend once you have everything up and running you use smartswitch to backup your phone.. it backed up everything imcluding my text messages for me so when i used it to retrieve the stock tar it restored everything right back!
Sent from my SM-G925V using XDA Free mobile app
Click to expand...
Click to collapse
and fui, you need to use smartswitch now for our device as kies did not work for me
Sent from my SM-G925V using XDA Free mobile app

Trying to Odin back to factory. I've got a 128GB edge. When I start the flash it hangs on "Partition". Do I need to check the "re-partition" button in Odin. If so, do the PIT files change between the different sizes of the phones?

blulite said:
Trying to Odin back to factory. I've got a 128GB edge. When I start the flash it hangs on "Partition". Do I need to check the "re-partition" button in Odin. If so, do the PIT files change between the different sizes of the phones?
Click to expand...
Click to collapse
its possible pit file is different.. what version odin you using? if 10 doesnt work try the 3.9 odin
Sent from my SM-G925V using XDA Free mobile app

I tried both odin 9 and 10 (same result). finally clicked the "re-partition" button in 10 and the reload took fine. i just checked the phone and it shows 128gb. currently going thru a restore, will post more info as i find it.

Have you tested the tar file in odin?
Sent from my SM-N915V using Xparent Green Tapatalk 2

2swizzle said:
Have you tested the tar file in odin?
Sent from my SM-N915V using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
yes actually lol. few times trying to get my rom to flassh with flashfire.. apparently flashfire wont flash full rom.zips without a custom recovery (at least i cant figure it out.) other simple zips work however..
but i did use it at least 3 times lol. first time had a bit of trouble but if i select anything but auto reboot it would fail so only selecting auto reboot in odin it flashes for me each time
Sent from my SM-G925V using XDA Free mobile app

also to add, the tar file is the exact same tar that smart switch downloaded and is literally untouched.. it was already in the exact format and name and everything and i simply uploaded it without doing anything to it
Sent from my SM-G925V using XDA Free mobile app

The supplied tar file worked for me yesterday when I inadvertently removed a system file I shouldn't have after rooting.. Got me back to stock, re-rooted and I was good to go..
Used the Odin and tar files attached here without any problems.

Any way to quickly unRoot without ODIN flash stock TAR?

Anyone know how to just restore the system.img? As opposed to a full system wipe that is contained in this tar file? Folks have posted both "wipe" and "no wipe" versions from previous Galaxy SX versions.
thanks.

blulite said:
Anyone know how to just restore the system.img? As opposed to a full system wipe that is contained in this tar file? Folks have posted both "wipe" and "no wipe" versions from previous Galaxy SX versions.
thanks.
Click to expand...
Click to collapse
to my knowledge i do not think its possible to edit the tar file since we have a locked BL we xan only flash md5 verified tars...
the ones in past could have been an update.tar.. for example when we get a update can use smartswitch to download the update.tar which wont wipe because its an upgrade vs. a full odin recovery tar
Sent from my SM-G925V using XDA Free mobile app

You guys notice how many freakin Knox apks are in here? Both in system and priv-apps ... pretty crazy stuff. I've got a few small utilities in the works that I should have finished by the weekend (UI tweaks, etc) .. but I'll leave the ROM building to those more capable.
Still can't believe how quickly we got root... those poor souls with Note 4s have been waiting forever.

theresin said:
You guys notice how many freakin Knox apks are in here? Both in system and priv-apps ... pretty crazy stuff. I've got a few small utilities in the works that I should have finished by the weekend (UI tweaks, etc) .. but I'll leave the ROM building to those more capable.
Still can't believe how quickly we got root... those poor souls with Note 4s have been waiting forever.
Click to expand...
Click to collapse
i saw them lol. rom is for the most part ready but no way to flash it lol.. so i cant even test it
Sent from my SM-G925V using XDA Free mobile app

Quick question.
Maybe I'm missing something, but I see two versions floating around. In the ping pong thread, and on my device, I see G925VVRU1AOC3, and here I see G925VVZW1AOC3. Can you clarify this for me? Thanks.

tcollum said:
Quick question.
Maybe I'm missing something, but I see two versions floating around. In the ping pong thread, and on my device, I see G925VVRU1AOC3, and here I see G925VVZW1AOC3. Can you clarify this for me? Thanks.
Click to expand...
Click to collapse
not sure.. i have the ru one and i have vzw s6 edge 64gb black.. you?
fyi, i will be uploading the new update this weekend along with (hopefully) Extreme Syndicate v1 for the VZW S6 Edge if all goes well.. i think i know what my problem is
Sent from my SM-G925V using XDA Free mobile app