Database Info

[Q] GT-P7560

Is anybody familiar with this model?
I want to install ICS on it, but unfortunately am at a loss here.
Some kind of 3.2 beta was installed to it and the "About device" settings menu stated that it was a GT-P6800.
Unfortunately Odin failed write a GT-P6800 firmware on it (PDA only).
It was only then that i noticed that it says product name GT-P7560 in the Download Mode. But I cannot find any firmware of that model.
Which firmware shall I use?

herecy said:
Is anybody familiar with this model?
I want to install ICS on it, but unfortunately am at a loss here.
Some kind of 3.2 beta was installed to it and the "About device" settings menu stated that it was a GT-P6800.
Unfortunately Odin failed write a GT-P6800 firmware on it (PDA only).
It was only then that i noticed that it says product name GT-P7560 in the Download Mode. But I cannot find any firmware of that model.
Which firmware shall I use?
Click to expand...
Click to collapse
Umm.. i think u should post this in tab 7.7 forum ?
Sent from my GT-S5830 using Tapatalk 2

pretty good idea actually

herecy said:
pretty good idea actually
Click to expand...
Click to collapse
And i believe i never heard of GT-P7560 before, sorry..
Sent from my GT-S5830 using Tapatalk 2

kevintangi said:
And i believe i never heard of GT-P7560 before, sorry..
Sent from my GT-S5830 using Tapatalk 2
Click to expand...
Click to collapse
Thanks anyway.
Couldn't find any info except the device specs either.

Actually you are in the right section
kevintangi said:
Umm.. i think u should post this in tab 7.7 forum ?
Sent from my GT-S5830 using Tapatalk 2
Click to expand...
Click to collapse
Actually, you are in the proper section.
The following website has the info on your tablet. It is a GT 7+ variation.
http://pdadb.net/index.php?m=specs&id=3142&view=1&c=samsung_gt-p7560_galaxy_tab_7.0_plus_16gb
Why not do a factory reset and go from there. If that does not get you to where you want to go, give Samsung support a call.
Keep us posted on what ou find out.
Cbill

iUnfortunately I can do neither soft nor hard reset.
Due to the failed attempt to install the wrong firmware the tablet does no longer boot.
And nothing happens when I try to access the recovery menu by pressing volume up and the power button.
But even if I was able to reset the device, this would not bring me closer to my ultimate goal of installing ICS on it.
Is there no firmware of another model similar enough to be flashed safely on this model?
Samsung Support would be my last shot.

herecy said:
iUnfortunately I can do neither soft nor hard reset.
Due to the failed attempt to install the wrong firmware the tablet does no longer boot.
And nothing happens when I try to access the recovery menu by pressing volume up and the power button.
But even if I was able to reset the device, this would not bring me closer to my ultimate goal of installing ICS on it.
Is there no firmware of another model similar enough to be flashed safely on this model?
Samsung Support would be my last shot.
Click to expand...
Click to collapse
You'd probably have to as garyd9 or another dev to give ClockWork Recovery support to your model number, install that, make a backup, then you can ask to have your model number added to the what they support in this thread
http://forum.xda-developers.com/showthread.php?t=1576553
when your post count is high enough ...
WiFi isn't working in the build, and other minor glitches.
Good luck?

While I personally think that CyanogenMod is great, it is no option in this case.
I need a stock rom.
Samsung gave us this device in order to test our apps on it.
Seems that it is some pre-release device or a device that never will be released.
I guess I will have to get in touch with Samsung support.

Update: The first Samsung Service Center rejected the device, stating that they do not handle unofficial devices.
At the second however (halfway across the city) they told me that they would have a look at it. The technician there said that the IMEI number printed on this device did not even exist.
By the way: I would like to thank all of you for your pieces of advice.

herecy said:
Update: The first Samsung Service Center rejected the device, stating that they do not handle unofficial devices.
At the second however (halfway across the city) they told me that they would have a look at it. The technician there said that the IMEI number printed on this device did not even exist.
By the way: I would like to thank all of you for your pieces of advice.
Click to expand...
Click to collapse
Hi,
I am having the same issue, were you able to somehow get your device to boot again?
Thanks

[ROOT] PROPER Remake of Full Rooted Stock Image (aka Root66) + Easy CWM Install

SOLVED - How to flash the Proper (Fixed) Stock Rooted Image
Description: This is 100% stock with just Superuser/su added and overwrites every partition to stock but keeps your personal data, apps, settings the same (just like the stock factory image).
Samsung Official USB Drivers - Link
ODIN v3.07 - Link
Proper Rooted Stock Image - Download or (Torrent Link) - MD5 = be4350a56e739eaf7a4184352d653a7b
1. Install USB drivers
2. Download ODIN v3.07
3. Backup your data
4. OPTIONAL: Do a factory reset (highly recommended if you have issues with your current ROM)
***WARNING: Step #4 will erase internal storage but not microSD card***
5. Download the above Proper Rooted Stock Image file and extract the tar file from inside it
6. Boot phone into ODIN mode (See here for how-to)
7. Flash the extracted tar file using ODIN v3.07
You should now have a like new condition stock image and rooted with all issues resolved.
Credit goes completely to mrRobinson for creating this image for us. Thank you sir. (Original Post) + (Details How It Was Made)
To Install Official CWM Recovery
1. After following above process, download "Rom Manager" from the Play Store
2. Open Rom Manager
3. Select "Flash ClockworkMod Recovery"
4. Select "Samsung Galaxy S3 (Verizon)" down at the bottom and let it flash
5. Once completed you can reboot to CWM by selecting "Reboot into Recovery" from Rom Manager
ORIGINAL REQUEST
After various testing, it seems many users are experiencing various issues with the rooted System.img provided by the OP in this thread. Many report findings of "Sprint related elements" as well as various keyboard issues and things not working as they should. I wish I had the knowledge myself but on behalf of the community, I'd like to request for someone with knowledge of this guide to remake the same rooted system.img as in the original but this time confirmed with using the original stock Verizon SCH-I535 image downloadable here.
I'm sure many of us here would highly appreciate this effort and we can also carry out further testing as many users reported that soon as they flash back to that stock image, their issues have disappeared and everything starts working properly.
I will quote another user in reference to this:
BungeBash said:
Just formatted back to stock until issues can be resolved. The stock image (which I'm told this root is + su) lost all Sprint instances and any strange extra options. Also the Keyboards are back to functioning. Not to be a conspiracy theorist, but I feel that the root image has more going on with it than what we are told.
Click to expand...
Click to collapse
Here's to hoping one of you knowledgeable developers are able to assist us with this request.
Click to expand...
Click to collapse

open1your1eyes0 said:
After various testing, it seems many users are experiencing various issues with the rooted System.img provided by the OP in this thread. Many report findings of "Sprint related elements" as well as various keyboard issues and things not working as they should. I wish I had the knowledge myself but on behalf of the community, I'd like to request for someone with knowledge of this guide to remake the same rooted system.img as in the original but this time confirmed with using the original stock Verizon SCH-I535 image downloadable here.
I'm sure many of us here would highly appreciate this effort and we can also carry out further testing as many users reported that soon as they flash back to that stock image, their issues have disappeared and everything starts working properly.
I will quote another user in reference to this:
Here's to hoping one of you knowledgeable developers are able to assist us with this request.
Click to expand...
Click to collapse
If you don't like it, dont flash it.

tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
Hardly helpful for those who already flashed it... I just want it fixed, or a work around. If it's something as simple as uninstalling a few things, or replacing some databases, I'm fine with that. I just don't want to redo everything, and re-restore everything with Titanium Backup.

tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
Not to be rude but we're not. That's why I'm making this request to remake with proper image. Because we are skeptical of the original one that was made. I PMed the OP of that thread and he claims to have used that image but in user's experience something is definitely different from stock, hence we're requesting a remake to test this.

open1your1eyes0 said:
Not to be rude but we're not. That's why I'm making this request to remake with proper image. Because we are skeptical of the original one that was made. I PMed the OP of that thread and he claims to have used that image but in user's experience something is definitely different from stock, hence we're requesting a remake to test this.
Click to expand...
Click to collapse
If you'd like, you can flash the stripped version, and I have a second zip that will restore all the stripped apps.

I did have some odd issues with SwiftKey crashing after flashing the image. Not sure if that has to do with it or not.
tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
Useless post.
What would be useful is someone with the requisite knowledge being able to remake this exploit with the Verizon source in order to have maximum compatibility.

open1your1eyes0 said:
After various testing, it seems many users are experiencing various issues with the rooted System.img provided by the OP in this thread. Many report findings of "Sprint related elements" as well as various keyboard issues and things not working as they should. I wish I had the knowledge myself but on behalf of the community, I'd like to request for someone with knowledge of this guide to remake the same rooted system.img as in the original but this time confirmed with using the original stock Verizon SCH-I535 image downloadable here.
I'm sure many of us here would highly appreciate this effort and we can also carry out further testing as many users reported that soon as they flash back to that stock image, their issues have disappeared and everything starts working properly.
I will quote another user in reference to this:
Here's to hoping one of you knowledgeable developers are able to assist us with this request.
Click to expand...
Click to collapse
Are you talking about the system.img from invisibleks first image?
Link: http://forum.xda-developers.com/showpost.php?p=28402010&postcount=1
Or the stripped and rooted one?
Link: http://forum.xda-developers.com/showpost.php?p=28459565&postcount=1
I think the first one invisiblek made is pretty much what you are asking for. Remember, there's no SCH-I535 source code out there for people to build a system image from. These images are hacked system images from the stock image (found here: http://samsung-updates.com/device/?id=SCH-I535 ). One can't really "remake" the system image until we can fully bypass the encrypted and locked bootloader.
If you want to roll your own system image with the su binary and SuperUser you can follow the instructions here:
http://forum.xda-developers.com/showpost.php?p=27801304&postcount=1
They seem pretty straight forward.
However, I'm pretty sure that's what invisiblek did for his/her first rooted image (the one that isn't stripped).
Hope that helps. I can't do much of anything till my SGS3 arrives tomorrow.
ALQI

alquimista said:
Are you talking about the system.img from invisibleks first image?
Link: http://forum.xda-developers.com/showpost.php?p=28402010&postcount=1
Or the stripped and rooted one?
Link: http://forum.xda-developers.com/showpost.php?p=28459565&postcount=1
I think the first one invisiblek made is pretty much what you are asking for. Remember, there's no SCH-I535 source code out there for people to build a system image from. These images are hacked system images from the stock image (found here: http://samsung-updates.com/device/?id=SCH-I535 ). One can't really "remake" the system image until we can fully bypass the encrypted and locked bootloader.
If you want to roll your own system image with the su binary and SuperUser you can follow the instructions here:
http://forum.xda-developers.com/showpost.php?p=27801304&postcount=1
They seem pretty straight forward.
However, I'm pretty sure that's what invisiblek did for his/her first rooted image (the one that isn't stripped).
Hope that helps. I can't do much of anything till my SGS3 arrives tomorrow.
ALQI
Click to expand...
Click to collapse
The one in bold is what this request is about actually. Basically to remake that. Because the non-stripped rooted system.img that invisiblek is the one causing most issues for people and people have noted things in there that are not in the factory image. I tried to follow that guide myself but I must be missing something because most of those commands do not work for me. Mind you this is on a Windows PC.

I could do it, but it'd require more time than whats it worth. Sorry.

tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
You are a WORM!!!!!!!
Sent from my Galaxy Nexus using xda app-developers app

tonu42 said:
I could do it, but it'd require more time than whats it worth. Sorry.
Click to expand...
Click to collapse
No worries. Very understandable as that guide is quite time consuming and not for everyone. Thanks for your support either way.

tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
tonu42 said:
I could do it, but it'd require more time than whats it worth. Sorry.
Click to expand...
Click to collapse
Two completely pointless comments.
open1your1eyes0 said:
No worries. Very understandable as that guide is quite time consuming and not for everyone. Thanks for your support either way.
Click to expand...
Click to collapse
You sir are a better man than me for being so humble in response to these replies.
I'm assuming invisiblek DID in fact use the VZW image if the phone still had all the VZW nonsense in it (VZ Navigator, for example) as that would not be found in the Sprint image. Equally, if "all" he did was follow the steps in the link, then someone else doing the same is likely to produce the same result.
tonu42 said:
If you'd like, you can flash the stripped version, and I have a second zip that will restore all the stripped apps.
Click to expand...
Click to collapse
If you have these, have you posted them anywhere? That might have been a useful thing to do.

Here is all the removed apk's in a CWR zip.
http://www.mediafire.com/?6jv8wn9l5n0li9y

I actually saw that guide you posted about creating our own. I can try and whip something up tonight if I get some time. If not, tomorrow is my "Friday" at work, so I'll have time tomorrow evening for sure.

BungeBash said:
I actually saw that guide you posted about creating our own. I can try and whip something up tonight if I get some time. If not, tomorrow is my "Friday" at work, so I'll have time tomorrow evening for sure.
Click to expand...
Click to collapse
Thank you much sir. You assistance would be greatly appreciated.
Unfortunately I do not have a linux box so the guide does not work for me.

It's already been diff'd. There is no difference between the stock image and the rooted one here except for su and binaries:
http://rootzwiki.com/topic/29256-ro...erizon-galaxy-s-iii/page__st__110#entry793038
I'm guessing VZW has done more to the stock image on the phone than the stock one that is available for download, which is causing these differences.

Goose306 said:
It's already been diff'd. There is no difference between the stock image and the rooted one here except for su and binaries:
http://rootzwiki.com/topic/29256-ro...erizon-galaxy-s-iii/page__st__110#entry793038
I'm guessing VZW has done more to the stock image on the phone than the stock one that is available for download, which is causing these differences.
Click to expand...
Click to collapse
Considering I loaded the first root mod, then reverted to the image that it was created from and have 2 different setups I'd say two different files were used.

open1your1eyes0 said:
The one in bold is what this request is about actually. Basically to remake that. Because the non-stripped rooted system.img that invisiblek is the one causing most issues for people and people have noted things in there that are not in the factory image. I tried to follow that guide myself but I must be missing something because most of those commands do not work for me. Mind you this is on a Windows PC.
Click to expand...
Click to collapse
If its already been diff'd with the original, maybe the sammy-updates file ain't so good.
Hmm, I wonder if we dump the system.img from an untouched stock phone (like the one I get tomorrow), and inject that img with su, would that work out any better? I'll look into this tomorrow.
I'll also take a look at re-rolling the system.img from the sammy-updates files in the meantime.
I'll report back when and if I have a viable image.
~ALQI

alquimista said:
If its already been diff'd with the original, maybe the sammy-updates file ain't so good.
Hmm, I wonder if we dump the system.img from an untouched stock phone (like the one I get tomorrow), and inject that img with su, would that work out any better? I'll look into this tomorrow.
I'll also take a look at re-rolling the system.img from the sammy-updates files in the meantime.
I'll report back when and if I have a viable image.
~ALQI
Click to expand...
Click to collapse
According to users, flashing that sammy-update firmware got rid of all the issues and the Sprint related stuff. Just, FYI.

If anyone is up for the remake, you might want to try making it out of this one. Not sure if it's any different but it's from another well known Samsung firmware site.
Link to stock factory firmware

Question about installing OTA

I was supposed to be part of the soak but for some reason my phone is invisible to the Moto update servers and they cannot push the update to me. I have the update file someone gave me a link to download. I have two questions about how to install it.
1. Since I am rooted can I just put it where Moto would have downloaded it to and then my phone will update it like it got the OTA?
or
2. If I install it off the SD card will it just do recovery first and then display injured android man, and then have to reselect the zip package again to finish instlling the update?
I would prefer method 1 if possible. If one of the devs or a knowledgeable person could respond I would appreciate it. I'll give Moto about six more hours to get this straightened out, otherwise I am tired of waiting to get my Atrix 2 onto ICS.

Hi. I don't suppose the end result would be different, whatever method you choose.

athani said:
Hi. I don't suppose the end result would be different, whatever method you choose.
Click to expand...
Click to collapse
Where does moto put the zip file so I can try putting it where the OTA would have downloaded to? Then when I go to check for update it should say an update is ready for installing. Do they put it in the cache directory? Someone who knows please let me know. Thanks.

athani said:
Hi. I don't suppose the end result would be different, whatever method you choose.
Click to expand...
Click to collapse
AFAICT this seems true, you I could run a leak#2/soak based ROM as a second system (first system too?) with boot menu manager by following the guides:
http://forum.xda-developers.com/showthread.php?t=1779968
http://forum.xda-developers.com/showthread.php?t=1882335

jboxer said:
Where does moto put the zip file so I can try putting it where the OTA would have downloaded to? Then when I go to check for update it should say an update is ready for installing. Do they put it in the cache directory? Someone who knows please let me know. Thanks.
Click to expand...
Click to collapse
Yes, it is /cache... but I think you also need the .crc file of the same name along with the actual .zip - not positive though. And, it can take a little while for it to recognize it - but I have done it that way, by putting it in the cache folder - also, it will disappear if you reboot.
But, you do know what you are doing, right? There is no fxz yet...
---------- Post added at 08:17 AM ---------- Previous post was at 08:12 AM ----------
Edit.. since it's the same files as leak#2.. for the .crc file, you could just make your own if you don't have it:
-Just create a new blank file with notepad++
-Add this as the first and only line (no blank lines after)
Code:
3114145323
-Then, save it as Blur_Version.55.13.25.MB865.ATT.en.US.crc

alteredlikeness said:
Yes, it is /cache... but I think you also need the .crc file of the same name along with the actual .zip - not positive though. And, it can take a little while for it to recognize it - but I have done it that way, by putting it in the cache folder - also, it will disappear if you reboot.
But, you do know what you are doing, right? There is no fxz yet...
---------- Post added at 08:17 AM ---------- Previous post was at 08:12 AM ----------
Edit.. since it's the same files as leak#2.. for the .crc file, you could just make your own if you don't have it:
-Just create a new blank file with notepad++
-Add this as the first and only line (no blank lines after)
Code:
3114145323
-Then, save it as Blur_Version.55.13.25.MB865.ATT.en.US.crc
Click to expand...
Click to collapse
Yes, I know what I am doing. I used to develop roms for LG P999 but have not played around with my Atrix much. LG does their OTA updates very differently and downloads them in pieces all over the place so no way to use the method I am suggesting for the Atrix. I don't care about being able to fxz back as I just want the phone on official ICS; but I do appreciate your caveat. Thanks for the reply.
If anyone has the .crc file please upload somewhere so I can grab it. Thanks.

jboxer said:
Yes, I know what I am doing. I used to develop roms for LG P999 but have not played around with my Atrix much. LG does their OTA updates very differently and downloads them in pieces all over the place so no way to use the method I am suggesting for the Atrix. I don't care about being able to fxz back as I just want the phone on official ICS; but I do appreciate your caveat. Thanks for the reply.
If anyone has the .crc file please upload somewhere so I can grab it. Thanks.
Click to expand...
Click to collapse
I know you know what you are doing.. just had to throw that in there..
Here's the .crc file from the last leak from 9/5/12... should be the same as the soak one: https://dl.dropbox.com/u/61960599/Leak_09.05.12/Blur_Version.55.13.25.MB865.ATT.en.US.crc

alteredlikeness said:
I know you know what you are doing.. just had to throw that in there..
Here's the .crc file from the last leak from 9/5/12... should be the same as the soak one: https://dl.dropbox.com/u/61960599/Leak_09.05.12/Blur_Version.55.13.25.MB865.ATT.en.US.crc
Click to expand...
Click to collapse
Thanks. I will give them a few hours to get to work and see if my phone is visible to the update servers now that I have done an FDR as they requested. If so, I will just let the OTA do its thing. If not I will manually update my phone.

Also I do not think you can be rooted to update the check will prevent you from updating, also you have to be as close as stock as you can..... Meaning all bloat must be unfroze.....
One more note there is a Q&A section now so try to post questions there.....

jboxer said:
I was supposed to be part of the soak but for some reason my phone is invisible to the Moto update servers and they cannot push the update to me. I have the update file someone gave me a link to download. I have two questions about how to install it.
1. Since I am rooted can I just put it where Moto would have downloaded it to and then my phone will update it like it got the OTA?
or
2. If I install it off the SD card will it just do recovery first and then display injured android man, and then have to reselect the zip package again to finish instlling the update?
I would prefer method 1 if possible. If one of the devs or a knowledgeable person could respond I would appreciate it. I'll give Moto about six more hours to get this straightened out, otherwise I am tired of waiting to get my Atrix 2 onto ICS.
Click to expand...
Click to collapse
Can you share the link of the update file?
Thanks

jboxer said:
Thanks. I will give them a few hours to get to work and see if my phone is visible to the update servers now that I have done an FDR as they requested. If so, I will just let the OTA do its thing. If not I will manually update my phone.
Click to expand...
Click to collapse
Could the fact that you're not in the US, are now unlocked and on another network have something with failure to get the OTA!?

You can be rooted. The update asserts only check for the original system files to make sure they have not been modified or deleted. It does not check for extra files like superuser.apk or busybox. Rooting is not a problem. I set superuser to OTA protect and it worked. After the update my ICS was still rooted without me having to root it.
For the person that wants the leak the OTA is leak # 2. It is exactly the same. Just find thread with download link for leak # 2 and you are good to go.

Would installing beats audio drivers using the app be considered tampering with system files? And would it prevent me from receiving a ota?
Sent from my MB865 using xda premium

athani said:
Could the fact that you're not in the US, are now unlocked and on another network have something with failure to get the OTA!?
Click to expand...
Click to collapse
No, they wanted people like that to make sure it worked. Just had to do an FDR and then was good to go. Got the OTA and on ICS now.

ramosquera said:
Can you share the link of the update file?
Thanks
Click to expand...
Click to collapse
The devs have confirmed that the soak test OTA is identical to ICS leak #2.

jboxer said:
No, they wanted people like that to make sure it worked. Just had to do an FDR and then was good to go. Got the OTA and on ICS now.
Click to expand...
Click to collapse
Sorrry but what mean FDR? because I'm in that situation: Im not in US and I have the phone unlocked, and I'm using it with other operator... Is just ended the soak test?... because the phone say me "Your phone is updated, Is not required a update in this moment" (Translated from Spanish) when I look in Settings -> About the phone -> Update, and I'm have the system version 55.13.25.MB865.ATT.en.US.

nelsonalfo said:
Sorrry but what mean FDR? because I'm in that situation: Im not in US and I have the phone unlocked, and I'm using it with other operator... Is just ended the soak test?... because the phone say me "Your phone is updated, Is not required a update in this moment" (Translated from Spanish) when I look in Settings -> About the phone -> Update, and I'm have the system version 55.13.25.MB865.ATT.en.US.
Click to expand...
Click to collapse
You have to be someone that was invited and filled out a survey about six weeks ago. If you are you need to go to the Motorola Private forum. Go see how others are requesting it (not allowed to really talk about it). FDR means Factory Data Reset and it is an option in Privacy in Settings. It erases all your user settings, app data and you are back to square one like when the phone came out of the box. For many people it was required to get what they wanted.
If you were not invited don't worry. Usually the official rollout of the OTA will come within a week of a soak test if no problems are found. It is the same as leak # 2 so just look on this forum and you can install that manually. The release is solid so I see no reason the OTA won't be going live to all AT&T Atrix 2 devices very soon.

nelsonalfo said:
Sorrry but what mean FDR? because I'm in that situation: Im not in US and I have the phone unlocked, and I'm using it with other operator... Is just ended the soak test?... because the phone say me "Your phone is updated, Is not required a update in this moment" (Translated from Spanish) when I look in Settings -> About the phone -> Update, and I'm have the system version 55.13.25.MB865.ATT.en.US.
Click to expand...
Click to collapse
I think he means Factory Data Reset.. found in settings>backup & reset (?) forgot where it was on GB, but it's in the settings.
Edit: Lol.. jboxer - I've been too slow a lot recently

alteredlikeness said:
I think he means Factory Data Reset.. found in settings>backup & reset (?) forgot where it was on GB, but it's in the settings.
Edit: Lol.. jboxer - I've been too slow a lot recently
Click to expand...
Click to collapse
I hated doing it but it was necessary for some reason. Before it my phone was invisible to the update servers. After it was and I got a push notification to begin the download. Loving ICS.

[Q] Error 402 with 4.1.2 Update?

Hi guys,
I'm a little new to posting on XDA itself, so I'm not quite sure if I'm in the right section, as I don't have my 10 posts yet. So apologies in advance. Move me where you need to.
Alrighty. I'm running 4.1.1 (stock firmware) and I've been getting notifications to update OTA since about a month ago. However, when I try to update, it stops in the middle of the update, restarts the phone, and gives me an error 402. Not quite sure what that means, though an old Verizon forums posts pointed to a corrupt file in the phone's software itself, preventing the update from happening. Aside from that, the phone's been a mite glitchy with home screen transitions, and it's eating up a bunch of my battery life (not going into deep sleep; overheating) when it hasn't done so in the past.
I don't want to give my phone back to Verizon and get a like-new one back, but that seems like it has been the only option I've been given. I've factory reset, cleared cache through recovery, and still no luck. The error 402 keeps happening when updating.
So my question lies here - What should I do? How can I fix this error? How can I update my phone? Or better yet, is there a ROM of the original ICS software (Day one of GS3 release on Verizon) that I can flash through Odin? Then I'd just log in with Google, and let the phone update for about three hours until I'm on current software, and it really wouldn't be susceptible to software corruption if I just let it update all the way through.
Anyone with a similar problem, or does anyone know what I should do?
Thanks, and hope you can help me with this.

buckoman said:
Hi guys,
I'm a little new to posting on XDA itself, so I'm not quite sure if I'm in the right section, as I don't have my 10 posts yet. So apologies in advance. Move me where you need to.
Alrighty. I'm running 4.1.1 (stock firmware) and I've been getting notifications to update OTA since about a month ago. However, when I try to update, it stops in the middle of the update, restarts the phone, and gives me an error 402. Not quite sure what that means, though an old Verizon forums posts pointed to a corrupt file in the phone's software itself, preventing the update from happening. Aside from that, the phone's been a mite glitchy with home screen transitions, and it's eating up a bunch of my battery life (not going into deep sleep; overheating) when it hasn't done so in the past.
I don't want to give my phone back to Verizon and get a like-new one back, but that seems like it has been the only option I've been given. I've factory reset, cleared cache through recovery, and still no luck. The error 402 keeps happening when updating.
So my question lies here - What should I do? How can I fix this error? How can I update my phone? Or better yet, is there a ROM of the original ICS software (Day one of GS3 release on Verizon) that I can flash through Odin? Then I'd just log in with Google, and let the phone update for about three hours until I'm on current software, and it really wouldn't be susceptible to software corruption if I just let it update all the way through.
Anyone with a similar problem, or does anyone know what I should do?
Thanks, and hope you can help me with this.
Click to expand...
Click to collapse
Maybe just root(; lol and flash clean Rom stock 4.1.2
Sent from my SCH-I535 using Tapatalk 4 Beta

I'd really like to avoid rooting at all costs. This phone's been great for me when it's unrooted, unlike my Droid2 which needed Liberty.
But other than that, any options that don't involve rooting?

buckoman said:
I'd really like to avoid rooting at all costs. This phone's been great for me when it's unrooted, unlike my Droid2 which needed Liberty.
But other than that, any options that don't involve rooting?
Click to expand...
Click to collapse
Not unless you can remove the update and try again. Verizon soft bricked you. Don't know if you can remove the update file from memory and try to download again without root. Get a file explorer and look for the file. Not sure of name as I have only taken one OTA over all the years and it worked. If want to Odin the full MB1 update image is on SamMobile. If Odin that don't have to worry about OTA and will have same thing.

prdog1 said:
Not unless you can remove the update and try again. Verizon soft bricked you.
Click to expand...
Click to collapse
Which is kind of what I'm asking. Is there a way to re-flash the software completely through Odin? Or just flash the 4.1.2 through Odin? I haven't really been able to find the image online, though. I'd be happy with any software version as long as it deleted and overwrote my current system files with fresh, non-corrupted ones so I could start over. Since backing up files isn't a problem, or even a concern since I could really care less about keeping my files intact at this point, what can I do?

buckoman said:
Which is kind of what I'm asking. Is there a way to re-flash the software completely through Odin? Or just flash the 4.1.2 through Odin? I haven't really been able to find the image online, though. I'd be happy with any software version as long as it deleted and overwrote my current system files with fresh, non-corrupted ones so I could start over. Since backing up files isn't a problem, or even a concern since I could really care less about keeping my files intact at this point, what can I do?
Click to expand...
Click to collapse
I was editing when you responded. The Full OTA Odin Image is on SamMobile. Just Odin that and you are done.
---------- Post added at 09:27 AM ---------- Previous post was at 09:25 AM ----------
Actually I have it here. Don't know which one is faster. Forgot I uploaded it to my server.
http://d-h.st/Xfe

prdog1 said:
I was editing when you responded. The Full OTA Odin Image is on SamMobile. Just Odin that and you are done.
---------- Post added at 09:27 AM ---------- Previous post was at 09:25 AM ----------
Actually I have it here. Don't know which one is faster. Forgot I uploaded it to my server.
http://d-h.st/Xfe
Click to expand...
Click to collapse
And just making sure, using Odin will completely wipe the phone, yes?

Post your nougat update.zip!

Whoever gets the update tomorrow. PULL THE UPDATE ZIP!
If I get it I will and post it, for the flat variant. I have ready done this from my wife's sprint edge variant.
Here is how you do it:
You have to be on the latest firmware and not rooted.
If you get the update notification.
Download it, but do not install it.
Then root your device. DO NOT WIPE IT
The update.zip is located in /data/fota/update.zip
Pull it using adb or use root Explorer to move it to the root of your SDCard and then your pc.
Please wait for someone to verify it works before flashing the update or unroot.
Come on people, support the community!

billydroid said:
Whoever gets the update tomorrow. PULL THE UPDATE ZIP!
If I get it I will and post it, for the flat variant. I have ready done this from my wife's sprint edge variant.
Here is how you do it:
You have to be on the latest firmware and not rooted.
If you get the update notification.
Download it, but do not install it.
Then root your device. DO NOT WIPE IT
The update.zip is located in /data/fota/update.zip
Pull it using adb or use root Explorer to move it to the root of your SDCard and then your pc.
Please wait for someone to verify it works before flashing the update or unroot.
Come on people, support the community!
Click to expand...
Click to collapse
what is the root of the sd card?

I will if I get
Sent from my Samsung SM-G935T using XDA Labs

comptonhubbard said:
what is the root of the sd card?
Click to expand...
Click to collapse
Jsut not in a folder. But that really doesn't matter unless you are trying to flash it from your SDCard

billydroid said:
Jsut not in a folder. But that really doesn't matter unless you are trying to flash it from your SDCard
Click to expand...
Click to collapse
Since it tried to register too late, I cant do this (would have done so otherwise - I have restored to stock and re-rooted so many times I could do it in my sleep).
Now I will be looking forward to getting my hands on the ODINable download. I will test it right off and contribute feedback here after.
PS - just looked at the terms and conditions - they wouldn't like this at all lol.
PS2 - maybe they have seen these posts and pulled the plug - server down and Beta call in number down also - have bad feeling about this - could that inadvertently been sending out unlocked bootloaders??

I'm waiting for this too.
Sent from my SM-G935U using XDA-Developers mobile app

gaww said:
Since it tried to register too late, I cant do this (would have done so otherwise - I have restored to stock and re-rooted so many times I could do it in my sleep).
Now I will be looking forward to getting my hands on the ODINable download. I will test it right off and contribute feedback here after.
PS - just looked at the terms and conditions - they wouldn't like this at all lol.
PS2 - maybe they have seen these posts and pulled the plug - server down and Beta call in number down also - have bad feeling about this - could that inadvertently been sending out unlocked bootloaders??
Click to expand...
Click to collapse
Yeah no one has got it today. This is starting to look bad
I tweeted at @TmobileHelp, they say it's coming.

billydroid said:
Yeah no one has got it today. This is starting to look bad
I tweeted at @TmobileHelp, they say it's coming.
Click to expand...
Click to collapse
just got through to the galaxy beta program number 1-866-609-3271, currently on hold, all the representatives are currently assisting other customers guess everyone is calling lol ill post any information i get *fingers crossed*
---------- Post added at 09:01 PM ---------- Previous post was at 08:48 PM ----------
Dennis Frogman said:
just got through to the galaxy beta program number 1-866-609-3271, currently on hold, all the representatives are currently assisting other customers guess everyone is calling lol ill post any information i get *fingers crossed*
Click to expand...
Click to collapse
Alright just got off the phone with the customer service representative, they said that they are working with t-mobile as i type this message to get this issue resolved and yes we arev still getting the update. They also said that it's not an issue on Samsung side but rather a problem with t-mobile's server's so guess were gonna have to wait till they get thing's resolved. I asked if it would be fixed today and he said he can't give me a timeline of how or when it will be fixed so stay confident people we are getting it. If you'd like to hear this information with your own ears call the number your selves !!! 1-866-609-3271

gaww said:
Since it tried to register too late, I cant do this (would have done so otherwise - I have restored to stock and re-rooted so many times I could do it in my sleep).
Now I will be looking forward to getting my hands on the ODINable download. I will test it right off and contribute feedback here after.
PS - just looked at the terms and conditions - they wouldn't like this at all lol.
PS2 - maybe they have seen these posts and pulled the plug - server down and Beta call in number down also - have bad feeling about this - could that inadvertently been sending out unlocked bootloaders??
Click to expand...
Click to collapse
this exact post is in the Verizon variants xda page. they uploaded the package.zip file before the install. I don't see it being a problem on here. If it was leaked or something and Samsung didn't release it, then I could see someone being very upset

billydroid said:
Whoever gets the update tomorrow. PULL THE UPDATE ZIP!
If I get it I will and post it, for the flat variant. I have ready done this from my wife's sprint edge variant.
Here is how you do it:
You have to be on the latest firmware and not rooted.
If you get the update notification.
Download it, but do not install it.
Then root your device. DO NOT WIPE IT
The update.zip is located in /data/fota/update.zip
Pull it using adb or use root Explorer to move it to the root of your SDCard and then your pc.
Please wait for someone to verify it works before flashing the update or unroot.
Come on people, support the community!
Click to expand...
Click to collapse
I pull it and I followed the instructions but when I copy the file over to my SD card it shows 0 bytes any suggestions
Sent from my Samsung SM-G935T using XDA Labs

besttech1450 said:
I pull it and I followed the instructions but when I copy the file over to my SD card it shows 0 bytes any suggestions
Click to expand...
Click to collapse
Copy over to your external/internal SD card and move it to your pc. That is what I've done for the tmo flat s7
I was having the same issue. Maybe because the it's encrypted?

billydroid said:
Copy over to your external/internal SD card and move it to your pc. That is what I've done for the tmo flat s7
I was having the same issue. Maybe because the it's encrypted?
Click to expand...
Click to collapse
Ok I try thanks
Sent from my Samsung SM-G935T using XDA Labs

Based on what people from the nouget thread are saying.....we're SOL on getting a .zip file

So it looks like Samsung figured out everyone was sharing the files. For some reason the saved update.zip is failing to update the firmware when it is flashed. No fix yet.
Also I got the beta software so far you aren't missing out on much. It's still not as good as the Note 7s firmware was.

ShrekOpher said:
Also I got the beta software so far you aren't missing out on much. It's still not as good as the Note 7s firmware was.
Click to expand...
Click to collapse
Opinion

ShrekOpher said:
So it looks like Samsung figured out everyone was sharing the files. For some reason the saved update.zip is failing to update the firmware when it is flashed. No fix yet.
Also I got the beta software so far you aren't missing out on much. It's still not as good as the Note 7s firmware was.
Click to expand...
Click to collapse
Do you know for sure or are you just speculating wrong info?
Sent from my SM-G935U using Tapatalk

tengtengvn said:
Do you know for sure or are you just speculating wrong info?
Sent from my SM-G935U using Tapatalk
Click to expand...
Click to collapse
There are people in the beta forums talking about it and Samsung has referred to the Terms of Service saying users are "not supposed to share the beta software". My guess is that they don't have the servers setup to have TONS of people using the software and it feeding them log files etc. That's why they limited the beta to a set number of users. Also the Beta forums that you get access to as a part of the firmware are getting loaded up with comments from people, way more than Samsung staffed to handle.
Its not an assumption that they don't want everyone using it. It is an assumption that they changed the Tmobile firmware to make it so it couldn't be shared. Its a closed beta not open to all users restricting access is a part of a closed beta.
As for the next beta update. They will be making multiple changes over the coarse of the next month and there will be multiple firmware updates pushed out, per the text you receive when you look for a beta update. There is an additional beta setting to help users schedule the installations so they don't use up all their data. Since the tmobile firmware is locked down to specific devices that are a part of the beta program that practice will most likely continue in future beta updates.
If I had to take a wild guess my bet would be that if you are not a registered beta tester you won't get the next update at all and you won't be able to side load/flash it.

ShrekOpher said:
There are people in the beta forums talking about it and Samsung has referred to the Terms of Service saying users are "not supposed to share the beta software". My guess is that they don't have the servers setup to have TONS of people using the software and it feeding them log files etc. That's why they limited the beta to a set number of users. Also the Beta forums that you get access to as a part of the firmware are getting loaded up with comments from people, way more than Samsung staffed to handle.
Its not an assumption that they don't want everyone using it. It is an assumption that they changed the Tmobile firmware to make it so it couldn't be shared. Its a closed beta not open to all users restricting access is a part of a closed beta.
As for the next beta update. They will be making multiple changes over the coarse of the next month and there will be multiple firmware updates pushed out, per the text you receive when you look for a beta update. There is an additional beta setting to help users schedule the installations so they don't use up all their data. Since the tmobile firmware is locked down to specific devices that are a part of the beta program that practice will most likely continue in future beta updates.
If I had to take a wild guess my bet would be that if you are not a registered beta tester you won't get the next update at all and you won't be able to side load/flash it.
Click to expand...
Click to collapse
Its more than that. I got the beta. But i cant even flash the pulled update.zip from my own device. They did something that corrupts if trying to copy it.

Sounds like this is dead for TMo at this point ?

@billydroid and whoever has the update.zip and is rooted
Sounds like the nougat zip needs to be adb pulled from device instead of copying it that might make a differnce because your not copying it directly to sdcard or internal its getting pullled directly to pc thus it should stop it from getting corrupted but you will still need root to pull it from fota.
Sent from my SM-G935U using XDA-Developers mobile app