I read in a thread that someone lost their imei and it was suggested for them to use *2767*3855# to restore everything back to factory and reactivate the sim. I know this won't update oyur baseband to the newer editions, but it made me think about if someone bought a new phone that has the updated firmware, or somehow got their baseband/radios/kernel updated to the new version (whether through OTA or through getting a new phone), would it be possible to downgrade baseband/radio/firmware back to the previous edition since the VRLF2 version is also signed and authentic?
If it is possible to downgrade, does anyone have the dump files needed from an "older" version to do this? How would it be done, through odin or recovery, or terminal/adb (like backing up and restoring /efs partition)?
Thanks
newuser134 said:
If it is possible to downgrade, does anyone have the dump files needed from an "older" version to do this? How would it be done, through odin or recovery, or terminal/adb (like backing up and restoring /efs partition)?
Click to expand...
Click to collapse
Yep, see http://forum.xda-developers.com/showthread.php?t=1788313 for details.
The forum post has links to both the old and new modem, and full flashing instructions.
yes and I would only use the VLRF2 since it does not have the dumbed down search...the update is a downgrade!! If you like you can upgrade to the VRLG1 radio/modem and stay on the VRLF2 software.
droidstyle said:
yes and I would only use the VLRF2 since it does not have the dumbed down search...the update is a downgrade!! If you like you can upgrade to the VRLG1 radio/modem and stay on the VRLF2 software.
Click to expand...
Click to collapse
True, although you can just get the full featured googlequicksearchbox APK and replace the new one with it.
pjamv5 said:
True, although you can just get the full featured googlequicksearchbox APK and replace the new one with it.
Click to expand...
Click to collapse
indeed...more than one way to skin a cat.
Is there a general concensus yet on the newer modem? seems the posts go both ways... a lot of people saying it's better, others saying it's not.
I guess the only way to be sure is to try it out
Desterly said:
Is there a general concensus yet on the newer modem? seems the posts go both ways... a lot of people saying it's better, others saying it's not.
Click to expand...
Click to collapse
I used the Phone Info app to shut off 4g, and made a number of before/after test of the 3g signal.
It seems to be consistantly 2 or 3 db better with the new modem.
For example, sitting at my desk, I would show -82 dBm with the old modem, and -79 dBm with the new modem.
Can't say if there is any difference in 4g performance, it's nice and fast both before and after.
One change that I noticed, with the new modem, when switching from 3g to 4g, it changes over almost instantly. Before the modem upgrade, it would take maybe 30 seconds or so to pick up the 4g signal.
I535VRLG1 update
I also wondered this. Is there a reason except for the search function to go back to the first radio?
Also on a side note, I never accepted an OTA update! Was this pushed without the user's consent?
excelsisba said:
I also wondered this. Is there a reason except for the search function to go back to the first radio?
Click to expand...
Click to collapse
Updating the radio has nothing to do with the search function. If you currently have the VRLF2 build, you can update the radio (also the kernel) to the newer version without changing the build version.
If you purchased an updated phone, or take an OTA update, then you will have the downgraded google search. As pointed out by pjamv5, that's easy enough to fix if you want the old google search.
I've updated the kernel and radio, here's the end result:
Desterly said:
Is there a general concensus yet on the newer modem? seems the posts go both ways... a lot of people saying it's better, others saying it's not.
I guess the only way to be sure is to try it out
Click to expand...
Click to collapse
I first flashed the G1 radio firmware and kept the F2 ROM. I didn't notice much of a difference. Went ahead and flashed BeanTown R2 ROM which is based on the G1 rom but customized. It all works well for me.
Related
UPDATE: Anyone who broke 4G using unrevoked, there is no fix yet, sorry.
I've been getting alot of questions and comments about this...
Why is this different from others?
Does not flash Recovery
Does not Flash Boot
Radio is a FULL image and not a diff
YOU MUST HAVE ALL THE 1.47.651.1 SYSTEM FILES FOR WIMAX! (Link Removed, Read)
You break your 4G being stupid, not my fault.
This is a full IMG, wont overwrite recovery or anything else, just radio or wimax!
Only requirement is to have the new system files, don't even need the last radio.
RADIO: Torrent or Direct Download
WIMAX: Torrent or Direct Download
*Disclaimer: These files work for me, if you use them properly they should work properly. I'm just not responsible for damage in any form.
If you want to support me, just check out my various websites, and spread word!
On a side note, I say "must" for the new system files as the new WiMax will break without.
I don't know about radio, but even if it does work, it's not good practice to use with older system files.
Baseband Requirement
Does this flash require that you have a certain baseband before flashing? I am running a stock rooted 1.47 rom that Caulkin posted and am still running the stock baseband radio...I have not updated to the 5.31 that toast posted yet.
Do I need to flash 5.31 radio before flashing this? Or I am ok using my stock .24 radio?
Do I need to reflash my recovery_img afterwards?
hecklbrg said:
Does this flash require that you have a certain baseband before flashing? I am running a stock rooted 1.47 rom that Caulkin posted and am still running the stock baseband radio...I have not updated to the 5.31 that toast posted yet.
Do I need to flash 5.31 radio before flashing this? Or I am ok using my stock .24 radio?
Do I need to reflash my recovery_img afterwards?
Click to expand...
Click to collapse
Ah yes, I knew I forgot to say something...you do need to latest radio.
Main post updated!
Like I said, radio may not fully update...but it doesn't break anything and it will update WiMax
I'm guessing that this does NOT require that you use Caulkin's Wimax fix first as well?
hecklbrg said:
I'm guessing that this does NOT require that you use Caulkin's Wimax fix first as well?
Click to expand...
Click to collapse
I'm not aware of any "fix" from Caulkin, but if you referring to his WiMax update, no you don't need it.
I'm honestly surprised nobody posted anything like this before me that didn't include the damn recovery.
It's annoying to have to flash recovery when it's not needed.
So I would have to flash Calkulin's 1.47.651.1 on top of DC 3.2.x then this radio file?
Neotelos_com said:
I'm honestly surprised nobody posted anything like this before me that didn't include the damn recovery.
It's annoying to have to flash recovery when it's not needed.
Click to expand...
Click to collapse
My sentiments exactly.
Anywho has anyone gotten this working yet? I'm not one for subjecting my phone to be a guinea pig when bricking is a possible side effect.
Does any ROM based on the 1.47.651.1 update work with this or does it have to be the stock ROM?
Neotelos_com, did your Baseband version change to reflect this update? Mine hadn't...
good stuff, gonna look into this...
jwegman said:
Neotelos_com, did your Baseband version change to reflect this update? Mine hadn't...
Click to expand...
Click to collapse
I did check and it seems it did not.
I'll look into this, I personally would like the new radio.
I've done it!
I don't know how but I am the first person to have the full new radio image!
WiMax update will be added back in soon!
Neotelos_com said:
I've done it!
I don't know how but I am the first person to have the full new radio image!
WiMax update will be added back in soon!
Click to expand...
Click to collapse
is this based off of the OTA released yesterday which was 21.4 MB or the OTA released today at 30.2 MB ?
im still grabbing the 30.2 MB OTA released today over my slow 3g right now so i haven't had a chance to compare the OTA .zip from yesterday to the one today.
joeykrim said:
is this based off of the OTA released yesterday which was 21.4 MB or the OTA released today at 30.2 MB ?
im still grabbing the 30.2 MB OTA released today over my slow 3g right now so i haven't had a chance to compare the OTA .zip from yesterday to the one today.
Click to expand...
Click to collapse
I wasn't aware of a new OTA today, these would be based off yesterdays.
It's possible Sprint just switched from a diff for the radio, that would cause about 10mb size difference....in witch this will be the same thing.
No guarantees though, until we find out.
why is it a MUST that we use the .47 system files?
KERKEDAGAIN said:
why is it a MUST that we use the .47 system files?
Click to expand...
Click to collapse
It's been said WiMax wont work without.
I don't know about radio...but you can go ahead and try the radio.
It can always be reverted back using toasts old radio update.zip
It's just good practice to use the system files that these were designed for.
I'm still running DamageControl as a base (with .47), it didn't need a clear for me.
ah, ok..i shall report back w/ my findings!
Radio flashed ok. Tried flashing the WiMax zip and it failed and said it couldn't find the radio.diff?
I did notice the wimax zip has the update-script still looking for the radio.diff to update. This probably needs revised?
grkfire said:
Radio flashed ok. Tried flashing the WiMax zip and it failed and said it couldn't find the radio.diff?
Click to expand...
Click to collapse
haha, my bad, I will have it fixed asap
Here you folks go. Off of my phone to you. http://www.multiupload.com/YOXKQ18YW0. You Must have 2.1 with the 3.6 Update. I would recommend making a backup before applying. Use at your own use. If you get a Status 7 error, see my thread in the General forum on how I resolved it. Have Fun!
how is it? faster than 2.1?
Oh yeah. More bloatware, but that's easy to remove. Internet speed is faster. Phone is more responsive. Nice to have the Hotspot feature now. Overall a worthy upgrade. Now to wait for 2.3
can i use this update for my finland rom 3.42? or this is just for TMo version?
runeblade said:
Here you folks go. Off of my phone to you. http://www.multiupload.com/YOXKQ18YW0. You Must have 2.1 with the 3.6 Update. I would recommend making a backup before applying. Use at your own use. If you get a Status 7 error, see my thread in the General forum on how I resolved it. Have Fun!
Click to expand...
Click to collapse
Would you happen to have original t-mobile 2.1 in sbf format?
Unfortunately no-one has one for the US. I'm guessing you updated to the leaked version? The good news is that if my suspicion is correct a nandroid backup of this should play fine with the updated firmware. If you look at the difference its minor. 34.4.9 vs 34.4.4. I have not yet had the time to make one yet. I'll try to do so tonight.
What did you have to do with the update.zip in order to upgrade your defy? I'm on 2.1 with the 3.6 update, I'm rooted with superoneclick, and I have it copied to the root of my sd. Did you use clockworkmod recovery?
nanek921 said:
What did you have to do with the update.zip in order to upgrade your defy? I'm on 2.1 with the 3.6 update, I'm rooted with superoneclick, and I have it copied to the root of my sd. Did you use clockworkmod recovery?
Click to expand...
Click to collapse
Its an update zip file signed by company so you should enter stock recovery by power+vol down and then select update from zip.
hmm... how about flash 3.4.2-107 TMobile US Blur with RSDlite and then
update.zp?
Just tried it. No go.
It checks for the right build fingerprint before it continues. You need to have 6.36.0 or it aborts.
The Nandroid backup theory mught be the one that works...
no clue said:
hmm... how about flash 3.4.2-107 TMobile US Blur with RSDlite and then
update.zp?
Click to expand...
Click to collapse
Beach_Head said:
Just tried it. No go.
It checks for the right build fingerprint before it continues. You need to have 6.36.0 or it aborts.
The Nandroid backup theory mught be the one that works...
Click to expand...
Click to collapse
Thanks for the update.
...... I just want something official now
( I am on official Chinese 2.21 build 1.11, it is fast, specially when you skip Blur registration. But, just in case I need my phone service by t-mobile .... )
The leaked T-Mobile SBF was fast too.
But yeah, an official one would be better.
If the Nandroid method doesn't work, I hope someone posts an SBF soon...
no clue said:
Thanks for the update.
...... I just want something official now
( I am on official Chinese 2.21 build 1.11, it is fast, specially when you skip Blur registration. But, just in case I need my phone service by t-mobile .... )
Click to expand...
Click to collapse
As for right build fingerprint, yes you are right. It is picky as hell. In the other thread I also mentioned that it is checking for apps. For example, I have Blockbuster disabled....it checked for it, didn't find it, and failed. I spent over 4 hours last night getting this to a point that it would work. Way Way too much hassle. Unfortunately I don't think I'm going to get to do a backup tonight. Was up way too late last night/this morning working on this and put in a 12 hour day. As soon as I get a breather I will. Sorry.
No worries!
Is there any way to edit the build.prop file so that I can get the update to work?
runeblade said:
As for right build fingerprint, yes you are right. It is picky as hell. In the other thread I also mentioned that it is checking for apps. For example, I have Blockbuster disabled....it checked for it, didn't find it, and failed. I spent over 4 hours last night getting this to a point that it would work. Way Way too much hassle. Unfortunately I don't think I'm going to get to do a backup tonight. Was up way too late last night/this morning working on this and put in a 12 hour day. As soon as I get a breather I will. Sorry.
Click to expand...
Click to collapse
Unfortunately I don't have an un-updated Defy in front of me to pull the strings. I'll look at one of the ones at work tomorrow. If you read the error though it should tell you exactly what it is looking for. Mine did. Aslo try deleting the logwrapper. The was one of the holdups on mine.
I have the string. I'm just wondering if it would work if I do edit it...
Where do I locate logwrapper?
runeblade said:
Unfortunately I don't have an un-updated Defy in front of me to pull the strings. I'll look at one of the ones at work tomorrow. If you read the error though it should tell you exactly what it is looking for. Mine did. Aslo try deleting the logwrapper. The was one of the holdups on mine.
Click to expand...
Click to collapse
I just loaded this update.zip on my fiance's Defy...didn't wipe data or cache, it's booting right now....stuck at the T-Mobile "Stick Together" screen, waiting for the initial long boot
EDIT: Booted, running 2.2.1 now! So far so good, it's a little slow but it would be while it catches up. I have an Atrix and it's almost the identical interface.
can you make a sbf file of entire build?
Nandriod back up please! im dying for it
zencoran said:
Nandriod back up please! im dying for it
Click to expand...
Click to collapse
just flash the update.zip...why bother with a nandroid?
I have been notified of an update for my EK-GC120 (6ca5626c77cd.update_EK-GC120_GC120VRALL2_To_GC120VRAMC4_FWD-1.zip) is the file i pulled from the cache folder but it refuses to apply to my camera. Is there an alternate recovery available anywhere for this device? TWRP or CWM? I have posted the update here I am hoping it includes the remote viewfinder functionality that was originally missing from this version.
http://d-h.st/users/swjpilot/?fld_id=16995#files
Update: I had changed the GmsCore.apk file...luckily i had backed it up. After restoring the original file the update applied is applying....Hopefully Root will remain will post update as soon as it completes.
Update: SuperSU says it was able to restore Root Access whoohoo!
Last Update: This does finally bring the Remote Viewfinder capability to the stock camera app.
swjpilot said:
I have been notified of an update for my EK-GC120 (6ca5626c77cd.update_EK-GC120_GC120VRALL2_To_GC120VRAMC4_FWD-1.zip) is the file i pulled from the cache folder but it refuses to apply to my camera. Is there an alternate recovery available anywhere for this device? TWRP or CWM? I have posted the update here I am hoping it includes the remote viewfinder functionality that was originally missing from this version.
http://d-h.st/users/swjpilot/?fld_id=16995#files
Update: I had changed the GmsCore.apk file...luckily i had backed it up. After restoring the original file the update applied is applying....Hopefully Root will remain will post update as soon as it completes.
Update: SuperSU says it was able to restore Root Access whoohoo!
Last Update: This does finally bring the Remote Viewfinder capability to the stock camera app.
Click to expand...
Click to collapse
I give up. How did you root this device in the first place?
perlmane said:
I give up. How did you root this device in the first place?
Click to expand...
Click to collapse
ExynosAbuseAPK before the first update. You may be able to ODIN back to 4.1.1, run that tool then keep your root through the subsequent OTA's.
Where does one find 4.1.1
Sent from my SCH-I605 using XDA Premium HD app
perlmane said:
Where does one find 4.1.1
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I would try installing Kies and having it restore the firmware. It will most likely put you back on the original firmware but i don't know that for sure. Worst thing that could happen is a factory reset of your device and you stay on your current code level.
swjpilot said:
I would try installing Kies and having it restore the firmware. It will most likely put you back on the original firmware but i don't know that for sure. Worst thing that could happen is a factory reset of your device and you stay on your current code level.
Click to expand...
Click to collapse
VZW products do not support Kies firmware updates. 4.1.1 does not seem to be available anywhere for this device.
perlmane said:
VZW products do not support Kies firmware updates. 4.1.1 does not seem to be available anywhere for this device.
Click to expand...
Click to collapse
Well i saw this post as well not sure if you have been through it or not..... but this is the last thing i got for you. I have not been able to find the original firmware anywhere either myself.
http://forum.xda-developers.com/showthread.php?t=2086636
Sorry......
swjpilot said:
Well i saw this post as well not sure if you have been through it or not..... but this is the last thing i got for you. I have not been able to find the original firmware anywhere either myself.
http://forum.xda-developers.com/showthread.php?t=2086636
Sorry......
Click to expand...
Click to collapse
Since VZW does not support Kies firmware updates, I am afraid to try it. I will have to wait until someone finds the 4.1.1 release of this device and ODIN it.
Anyone still have the boot.img for the latest verizon? Even the full update will work to extract it. This is the only missing piece to extending the custom kernel to all variants.
perlmane said:
I give up. How did you root this device in the first place?
Click to expand...
Click to collapse
swjpilot said:
ExynosAbuseAPK before the first update. You may be able to ODIN back to 4.1.1, run that tool then keep your root through the subsequent OTA's.
Click to expand...
Click to collapse
If you are still around can you confirm you used the "Exynos" Abuse apk to root your Verizon GC120. The Samsung specs page for it aren't clear about whether it's an Exynos quad core using a qualcomm board or an entire qualcomm chipset/board. Thanks!
And if anyone Verizon has found a way to root the current Verizon version and/or the odin file for 4.1.1 please reply here or let me know! Thanks!
swjpilot said:
I have been notified of an update for my EK-GC120 (6ca5626c77cd.update_EK-GC120_GC120VRALL2_To_GC120VRAMC4_FWD-1.zip) is the file i pulled from the cache folder but it refuses to apply to my camera.
http://d-h.st/users/swjpilot/?fld_id=16995#files
Click to expand...
Click to collapse
That link is dead end. Can you please repost that firmware update?
Another thing I learned while I had my ATT galaxy tab 8.9 was that Samsung likes to use the same hardware in their South Korean version of their devices with cellular and in their US devices with cellular. It's almost certainly because of the LTE requirement. Wouldn't you know that such is the case with the Galaxy Camera. The South Korean version of the camera has a Qualcomm board just like the Verizon one. Maybe the firmware for it, which can be found on Sammobile at the link below, can be helpful.
http://www.sammobile.com/firmwares/1/?model=EK-KC120S&pcode=0
EDIT: To clarify more, the Korean version uses a Qualcomm 9215 baseband board with Exynos 4412 while the Verizon version (based on Samsung own specs page) uses a Qualcomm 9615 which has it's own applications processor.
CPU Z says the Verizon GC120 DOES use the Exynos 4412 (smdk4x12). It makes no mention of the Qualcomm board on Samsungs' own specs page. They don't make this easy...
Still need any Verizon build anyone has (original 4.1.1 or 4.1.2 update which should be found in /cache).
Newest JZO54K.GC120VRAMC4
Previous JZO54K.GC120VRALL2
The one in the op should then be the 4.1.2 update
twistedumbrella said:
Newest JZO54K.GC120VRAMC4
Previous JZO54K.GC120VRALL2
The one in the op should then be the 4.1.2 update
Click to expand...
Click to collapse
I know you think no one else could possibly know better than you but the link in the op leads to nothing.
Jiggity Janx said:
I know you think no one else could possibly know better than you but the link in the op leads to nothing.
Click to expand...
Click to collapse
E:V:A said that a few posts up. I dunno what your problem is, but the more specific the file name, the better chance of finding the right file. If this section were labelled "Jiggity Janx" and not "Galaxy Camera Android Development" I would be directing every post to you. It isn't, and I'm not.
Edit: Did you try editing the build.prop with the values for the old version and attempting to do a system update? I have not researched how FOTA determines eligibility, but if it is like any normal system app, it uses the system properties.
twistedumbrella said:
E:V:A said that a few posts up. I dunno what your problem is, but the more specific the file name, the better chance of finding the right file. If this section were labelled "Jiggity Janx" and not "Galaxy Camera Android Development" I would be directing every post to you. It isn't, and I'm not.
Click to expand...
Click to collapse
edited out...
You can still likely see what was written in your thread quote notification but it doesnt need to be hashed out here.
Jiggity Janx said:
My problem here starts and ends with you. You cant expect to come across the way you do belittleing or correcting everyone every chance you get and then wonder why someone responds that way to something that appears to be a comment directed at the very last thing stated in the post immediately before yours. You dont get to have it both ways and then act innocent and deflect when you are called out on it.
Click to expand...
Click to collapse
It isn't about feelings, its about development.
Did you try editing the build.prop with the values for the old version and attempting to do a system update? I have not researched how FOTA determines eligibility, but if it is like any normal system app, it uses the system properties.
twistedumbrella said:
It isn't about feelings, its about development.
Did you try editing the build.prop with the values for the old version and attempting to do a system update? I have not researched how FOTA determines eligibility, but if it is like any normal system app, it uses the system properties.
Click to expand...
Click to collapse
Github/Sourcforge - post technical information for development, no interaction or FEELINGS required
XDA - development FORUM that requires HUMAN interaction
Now....
I appreciate the robotic side of you not taking anything to heart and continuing to want to assist. Unfortunately I have to return the model I received as I immediately noticed it had the vzw demo app on it and that the screen wouldn't time out. That means it was a verizon floor model and is unusable as intended. I am returning that one for a full refund but already have another on the way that I have been guaranteed does not have that problem (for $25 less even).
So long story short I am only willing to mess with the files so much. I know one wrong move with the build.prop could cause it not to boot and without a way to restore am not willing to take that chance with one I have to return. I will be able to do more than pull files from the other one once I receive it (and have time).
Thank you again for assisting us all with development on this device.
Jiggity Janx said:
Github/Sourcforge - post technical information for development, no interaction or FEELINGS required
XDA - development FORUM that requires HUMAN interaction
Now....
I appreciate the robotic side of you not taking anything to heart and continuing to want to assist. Unfortunately I have to return the model I received as I immediately noticed it had the vzw demo app on it and that the screen wouldn't time out. That means it was a verizon floor model and is unusable as intended. I am returning that one for a full refund but already have another on the way that I have been guaranteed does not have that problem (for $25 less even).
So long story short I am only willing to mess with the files so much. I know one wrong move with the build.prop could cause it not to boot and without a way to restore am not willing to take that chance with one I have to return. I will be able to do more than pull files from the other one once I receive it (and have time).
Thank you again for assisting us all with development on this device.
Click to expand...
Click to collapse
Look at the number of developers who have left xda butt-hurt about some comment a nameless, faceless text blob made about them because of how they read it. The device suffers, the users suffer, and some kid is up in his room crying about a hobby gone wrong.
As for the rollback, it was only theory anyway so if there is any doubt about what to change its better to find an alternative. If you could get images of the partitions from stock condition, it is possible to build the install. At least that is all done off the device where it won't corrupt anything. You could root, get the system, data, cache, and boot then merge those with the Korean release to fill in the missing parts. To the best of my knowledge, the bootloader and such are not region specific. That should be verified first, though, because you can't go back later.
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?
The following files will enable tethering on your I337. Make certain that you use the version applicable to your current build and only use on stock ROM. Use on custom ROM's may cause issues with the ROM. Proceed at your own risk!
Note: This will modify your system causing future ota updates to fail!
Here they are:
I337UCUFNI1_Safestrap_TetherAddOn.zip
(To undo the mod flash the I337_NI1_TetherAddOn_Revert-to-Stock.zip using the same instructions below).
I337UCUFNC1_Safestrap_TetherAddOn.zip
I337UCUFNB1_Safestrap_TetherAddOn.zip
Instructions:
1. Root your device(See Post #2 for rooting options).
2. Install the latest Safestrap.apk.
3. Place the applicable Safestrap_TetherAddOn.zip on ext sdcard.
4. Reboot into Safestrap Recovery and flash the Safestrap_TetherAddOn.zip in Stock Slot (Do Not Wipe Prior to Flashing!)
5. Reboot. Done!
NI1, NC1 & NB1 Rooting Methods
NI1 Users: http://forum.xda-developers.com/galaxy-s4-att/general/how-to-root-i337ucufni1-t2881298
NC1 Users: Use Towelroot.apk
NB1 Users: Flash the NC1_Stock_Kernel in PDA Slot in Odin(AP in Odin v3.09+), then use Towelroot.apk to root your device. (Optional: flash the NB1_Stock_Kernel once rooted).
Alternatively, flash the I337UCUFNB1_4.4_Rootable_Stock_Odin_tar to get back to factory stock NB1 then use Towelroot.apk to root your device.
reserved
thanks. been waiting for a method to install safestrap and to get hotspot. gonna test it out and see how long before AT&T or Net10 lock me out or send me a notice.
After I flashed zip on Golden Eye Rom I get stuck on Samsung boot screen. I did not wipe anything before flashing
Is this only for stock rooted nc1/nb1 or can this applied on top of a custom rom like ShoStock?
smokeythebear3 said:
Is this only for stock rooted nc1/nb1 or can this applied on top of a custom rom like ShoStock?
Click to expand...
Click to collapse
Most custom roms already offer tethering built in. Also they may already have a modified framework-res.apk(which these files replace) and may cause issues. So to answer your question I recommend only using this hack on stock.
I have an att i337 stock mf3, rooted using towel and su access. unlocked sim using tmo sim, which file should i download? also im on 4.2.2.. or if i update to atleast 4.3 with the newer modem will that fix this problem?
muniz_ri said:
Most custom roms already offer tethering built in. Also they may already have a modified framework-res.apk(which these files replace) and may cause issues. So to answer your question I recommend only using this hack on stock.
Click to expand...
Click to collapse
Cuda70383 said:
I have an att i337 stock mf3, rooted using towel and su access. unlocked sim using tmo sim, which file should i download? also im on 4.2.2.. or if i update to atleast 4.3 with the newer modem will that fix this problem?
Click to expand...
Click to collapse
I'm surprised that you are one of the few that still has att i337 mf3 phone. if so, stay on it, root it and disable the update. else, you'll lost pretty much everything unless something else happen. however, the only thing i can recommend is that you follow another guide that can do it or use foxfi and the paid key.
Holy crap dude! Super cool! If only I didn't have a faulty motherboard everything would be almost perfect, only thing I I'm missing is wifi calling but whatever. I'm gonna have to live without it cause the tmobile roms just don't work for me. Thanks so much man! Hey you think tmobile detects this? I have 3gb free a month.
I337UCUFNI1_Safestrap_TetherAddOn.zip
@guut13, @kbraun
I337UCUFNI1_Safestrap_TetherAddOn.zip added to OP.
Reading up on Safestrap now... i didn't think about it until now if I needed it, apparently I've been running without Recovery since I rooted 4.2.2, amateur move!!
I assume this wont wipe anything, just allows me to setup a recovery and flash the tether add on? correct
Pardon the seemingly easy question ( that I haven't found answers to yet)
[alot of updated reading lately since I updated from MF3 4.2.2 and my age old root method]
muniz_ri said:
@guut13, @kbraun
Thanks for the update.
I337UCUFNI1_Safestrap_TetherAddOn.zip added to OP.
Click to expand...
Click to collapse
kbraun said:
Reading up on Safestrap now... i didn't think about it until now if I needed it, apparently I've been running without Recovery since I rooted 4.2.2, amateur move!!
I assume this wont wipe anything, just allows me to setup a recovery and flash the tether add on? correct
Pardon the seemingly easy question ( that I haven't found answers to yet)
[alot of updated reading lately since I updated from MF3 4.2.2 and my age old root method]
Click to expand...
Click to collapse
Correct. Installing safestrap will not wipe anything.
Awesome, installed without issues.
The connection does appear to be quite a bit slower than using the previous theringprovision.apk with 4.2.2.
Would flashing a different modem help this?
kbraun said:
Awesome, installed without issues.
The connection does appear to be quite a bit slower than using the previous theringprovision.apk with 4.2.2.
Would flashing a different modem help this?
Click to expand...
Click to collapse
I don't believe a new modem will help. And I only briefly tested so other users should chime in as to whether they are also experiencing a slow connection.
kbraun said:
Awesome, installed without issues.
The connection does appear to be quite a bit slower than using the previous theringprovision.apk with 4.2.2.
Would flashing a different modem help this?
Click to expand...
Click to collapse
Can you try this version and see if the speed is better? I believe that I made a mistake on the first one: https://www.androidfilehost.com/?fid=23622183712475370
Downloading now...
Is it just as simple as flashing over the previous one, or do I have any maintenance to do first?
kbraun said:
Downloading now...
Is it just as simple as flashing over the previous one, or do I have any maintenance to do first?
Click to expand...
Click to collapse
Nope just flash over previous version.
Flashing it now, I'll get you an update in the morning.
Edit: Seems quite a bit faster after flashing the new file.
I wish I had done a speed test first but the results below are from my second install
36.64Mb down 12.95 up.
Once I rebooted I got the message "Safestrap disabled"
is that ok? I noticed the security policy in the 4.4.2 update with Samsung seems to like the ban hammer with alot of rooted stuff.
kbraun said:
Flashing it now, I'll get you an update in the morning.
Edit: Seems quite a bit faster after flashing the new file.
I wish I had done a speed test first but the results below are from my second install
36.64Mb down 12.95 up.
Once I rebooted I got the message "Safestrap disabled"
is that ok? I noticed the security policy in the 4.4.2 update with Samsung seems to like the ban hammer with alot of rooted stuff.
Click to expand...
Click to collapse
I don't know what kind of LTE speeds you normally get in your location but those speeds that you posted are more than decent. And I wouldn't worry about the safestrap disabled message, that's normal. I definitely made a mistake when compiling the first version of the tether add on but this latest version is definitely correct enjoy.