Ok this is my problem, I was on a custom rom because kikat was not released for my device. when it was I used odin and flashed the stock jelly bean rom I had. it worked and I went into settings and clicked update. when I came back to my tablet it had stock kikat 4.4.2. I went into download mode to add twrp and root. in download mode there was a new string of text after I flash twrp:
ODIN mode
product name:sm-t310_NA
current binary:
system status:
AP SEREV: A1
the "AP SEREV: A1" was new, For some reason twrp worked but i could not get root access so in twrp I restored a backup of my custom rom. so I gave it another try but when I tried to flash jelly bean, it gave me an error(FAILED) in oden and gave me a "invalid magic string" error in download mode.
What should i do, I am stuck on a custom rom I dont want. if it is a matter of flashing kikat in odin, then please direct me to the American SM-T310 kikat STOCK ROM file
thanks
ps if there is some new way of getting root in kikat that would also help.
androidhacker007 said:
Ok this is my problem, I was on a custom rom because kikat was not released for my device. when it was I used odin and flashed the stock jelly bean rom I had. it worked and I went into settings and clicked update. when I came back to my tablet it had stock kikat 4.4.2. I went into download mode to add twrp and root. in download mode there was a new string of text after I flash twrp:
ODIN mode
product name:sm-t310_NA
current binary:
system status:
AP SEREV: A1
the "AP SEREV: A1" was new, For some reason twrp worked but i could not get root access so in twrp I restored a backup of my custom rom. so I gave it another try but when I tried to flash jelly bean, it gave me an error(FAILED) in oden and gave me a "invalid magic string" error in download mode.
What should i do, I am stuck on a custom rom I dont want. if it is a matter of flashing kikat in odin, then please direct me to the American SM-T310 kikat STOCK ROM file
thanks
ps if there is some new way of getting root in kikat that would also help.
Click to expand...
Click to collapse
Try towel root http://forum.xda-developers.com/showthread.php?t=2784152
androidhacker007 said:
Ok this is my problem, I was on a custom rom because kikat was not released for my device. when it was I used odin and flashed the stock jelly bean rom I had. it worked and I went into settings and clicked update. when I came back to my tablet it had stock kikat 4.4.2. I went into download mode to add twrp and root. in download mode there was a new string of text after I flash twrp:
ODIN mode
product name:sm-t310_NA
current binary:
system status:
AP SEREV: A1
the "AP SEREV: A1" was new, For some reason twrp worked but i could not get root access so in twrp I restored a backup of my custom rom. so I gave it another try but when I tried to flash jelly bean, it gave me an error(FAILED) in oden and gave me a "invalid magic string" error in download mode.
What should i do, I am stuck on a custom rom I dont want. if it is a matter of flashing kikat in odin, then please direct me to the American SM-T310 kikat STOCK ROM file
thanks
ps if there is some new way of getting root in kikat that would also help.
Click to expand...
Click to collapse
This thread DOESNT belong here!!!
This thread must be moved on q&a
Srry can u move it plz
Sent from my SM-T310 using XDA Premium 4 mobile app
androidhacker007 said:
Srry can u move it plz
Sent from my SM-T310 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you are still looking for a 4.4.2 stock rom, try SamMobile.com. I used this one:
SM-T310 Canada 2014 July 4.4.2 T310XXUBNE9 T310XACBNE8
After that, I used this guide to root:
http://www.droidviews.com/root-galaxy-tab-3-8-0-sm-t310-on-kitkat/
and this for getting TWRP:
http://forum.xda-developers.com/showthread.php?t=2619518
Never, ever do an OTA update. You never know what sort of turd you are going to get. See the Knox fiasco, or my iPad 2 that is going to be a rifle target after a retard I loaned it to updated to 7-whatever.
Two things to try.
The Toolkit and this ROM.
If you already have a recovery on your Tab, this should be simple. Download one of the rooted versions of the ROM, get it on to your tablet (SD card preferred), wipe and install.
If all else fails, try GalaTab3. It WILL work, unless your mo-sheen is broken.
ETA: Whoa, does the stock Samsung 4.4.x ROM have Knox as well?
Related
I just rooted my AT&T Galaxy S3
Specs:
Model number: SAMSUNG-SGH-I747
Android Verson: 4.3
I am trying to install the AOKP Rom for my device. I have it all downloaded and know how to install it but I keep getting Status error 7. What is happening? I read a little online and it says this error is for whenever you have the incorrect ROM version? Please help!!
Install the latest cwm onto your phone and flash from recovery mode.
audit13 said:
Install the latest cwm onto your phone and flash from recovery mode.
Click to expand...
Click to collapse
How do I do that?
Check page 3 in the Android development section.
BammS2 said:
Check page 3 in the Android development section.
Click to expand...
Click to collapse
That doesnt help at all /:
Originally Posted by BammS2
Check page 3 in the Android development section.
Click to expand...
Click to collapse
That doesnt help at all /:
Click to expand...
Click to collapse
If you already have a custom recovery CWM then just find the most up to date version of it. You obviously installed once already. Also are you referring to stock 4.3?
Sent from my Awesome Phone using xda app-developers app
Also getting Status 7 error
I had TWRP installed (whatever ver comes with toolbox app)
Read reply, and installed latest version of CWM Touch from: http://forum.xda-developers.com/showthread.php?t=2152769
Still getting Status 7 on two different ROMs.
Now, I had been on 4.1.1, rooted and flashed a custom ROM no problem
Had some problems with my TMO service (I have another thread in this forum) and ended up doing an ODIN flash back to stock (4.0.4)
Which I have now sitting at stock, rooted. Is it possible that I'm getting the status 7 because both of the ROM's I'm attempting to flash are 4.4.2 and that is too big of a leap from 4.0.4? I'm going to grab a 4.1.x rom now to see if any different, but wanted to share history and that I was getting same error
The easiest way for me to get 4.4.2 onto an s3 was this:
1) copy a custom rom to your sd card (internal or external)
2) use Odin to flash back to any stock rom for your phone;
3) use Odin to install the latest version of Philz Touch Recovery from here (get the tar version and flash in PDA): http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att;
4) update to the most recent non-4.3 bootloader: http://forum.xda-developers.com/showthread.php?t=2321310
5) do a full wipe in recovery;
6) flash a custom 4.4.2-based ROM from recovery.
dannymac77 said:
I had TWRP installed (whatever ver comes with toolbox app)
Read reply, and installed latest version of CWM Touch from: http://forum.xda-developers.com/showthread.php?t=2152769
Still getting Status 7 on two different ROMs.
Now, I had been on 4.1.1, rooted and flashed a custom ROM no problem
Had some problems with my TMO service (I have another thread in this forum) and ended up doing an ODIN flash back to stock (4.0.4)
Which I have now sitting at stock, rooted. Is it possible that I'm getting the status 7 because both of the ROM's I'm attempting to flash are 4.4.2 and that is too big of a leap from 4.0.4? I'm going to grab a 4.1.x rom now to see if any different, but wanted to share history and that I was getting same error
Click to expand...
Click to collapse
Your main problem is that you need an updated bootloader. Please read up on this as it has been covered in great and very extensive detail throughout these forums. One bootloader will cause you to no longer to be capable of using ODIN to flash back to any stock based ROM without bricking your phone so you need to be careful.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Read more and you will see that cwm recovery is highly recommended for flashing 4.4.2 roms. Some roms dont flash good with twrp.
So, i decide to root my s3 because i wanted to do some cool stuff. I got odin, got the tar file and tried flashing it. For some reason it didn't work :crying: On odin it gave me a fail. I was in download mode too. So, when i turn on my s3 it is in odin mode but it says "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." i did this in kies and when it was at like 99% it gives me an error. :crying:
so i tried flashing again in odin still fail, but i get on my s3 SV REV CHECK FAIL: Fused 2 > Binary 0. I have no clue what that means, So, i just want my phone to get working again i dont care about rooting anymore. JUST HELP ME FIX IT!!!!:crying:
BTW: I di root my Kindle Fire a while back so i thought I would have experience with this (i kind of do) but i guess I thought wrong.
Was your phone running a stock 4.3 AT&T ROM? What method did you use to try and root the phone?
audit13 said:
Was your phone running a stock 4.3 AT&T ROM? What method did you use to try and root the phone?
Click to expand...
Click to collapse
i think so and i tired using odin and i put the phone in download mode so i could flash the .tar file
Resistance225 said:
i think so and i tired using odin and i put the phone in download mode so i could flash the .tar file
Click to expand...
Click to collapse
Since your phone was running a stock 4.3 ROM, you can't use Odin to install a stock AT&T 4.3 ROM because it doesn't exist. There are leaked ROMs around that you could try flashing.
Alternatively, you could install a custom recovery and install a custom 4.4.2 ROM.
audit13 said:
Since your phone was running a stock 4.3 ROM, you can't use Odin to install a stock AT&T 4.3 ROM because it doesn't exist. There are leaked ROMs around that you could try flashing.
Alternatively, you could install a custom recovery and install a custom 4.4.2 ROM.
Click to expand...
Click to collapse
I will try to do this! Thanks for helping me though, i will keep you updated. :fingers-crossed:
audit13 said:
Since your phone was running a stock 4.3 ROM, you can't use Odin to install a stock AT&T 4.3 ROM because it doesn't exist. There are leaked ROMs around that you could try flashing.
Alternatively, you could install a custom recovery and install a custom 4.4.2 ROM.
Click to expand...
Click to collapse
I installed a recovery and guess what, it started working again! All my data was still there too! Thanks i really appreciate you taking the time to help me! I also was able to succsessfully root it by using the CF auto root .tar file. Once again, thanks a ton!
Resistance225 said:
I installed a recovery and guess what, it started working again! All my data was still there too! Thanks i really appreciate you taking the time to help me! I also was able to succsessfully root it by using the CF auto root .tar file. Once again, thanks a ton!
Click to expand...
Click to collapse
Glad you got it working. We're all here to help.
So, I'm not a complete noob to flashing roms/rooting devices. I flashed cm 11 to my s3, and decided I wanted to go back to stock via Odin. For some reason when I tried to turn on my device it was still showing the cm 11 splash screen and wouldn't proceed any further. It isn't technically bricked. I guess this would be classified as a boot loop to the nth degree. I tired to boot in recovery mode and wipe the cache partition and all user data to the same cm 11 robot taunting me. When I tried the process (flashing stock vi Odin) again to possibly fix whatever might have been a miss, I got the error message on the download screen "secure check fail: sb12." On the download mode screen it also says I am running the official system rom. I don't know what steps I need to take from here to get my phone to actually boot via the stock rom. Has anybody else had this issue or similar? Any help in resolving this would be greatly appreciated.
Is your phone a i747? If you are you running a stock 4.3 bootloader on your i747, you can't use Odin to flash back to stock unless the ROM was specifically designed to be flashed in Odin.
What is shown on the screen in download mode?
audit13 said:
Is your phone a i747? If you are you running a stock 4.3 bootloader on your i747, you can't use Odin to flash back to stock unless the ROM was specifically designed to be flashed in Odin.
What is shown on the screen in download mode?
Click to expand...
Click to collapse
I was under the impression the rom I was attempting to flash was indeed intended for Odin. It is the SGH-I747.
The download screen states,
Product Name: SGH-I747
Custom Binary: Custom
System Status: Official
Qualcom Secure Boot: Enable
Warranty Bit: 1
Bootloader AP SWERV: 2
Here is an added bit of fun, in the midst of the process I accidentally checked "Nand erase all," in Odin at one point.
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
audit13 said:
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
My next question would be how can I move the zip files I download to the internal storage of my phone to flash them through Philz Touch?
Have you tried using kies?
http://forum.xda-developers.com/showthread.php?t=2088809
sjthuss said:
Have you tried using kies?
http://forum.xda-developers.com/showthread.php?t=2088809
Click to expand...
Click to collapse
I did. It said the the device couldn't be updated, or something to that effect.
Kies will not work without a stock recovery or a rooted phone from my experience.
I would be surprised if kies can restore your phone as ATT never released a full 4.3 stock ROM. ATT only made 4.3 available via an OTA update.
audit13 said:
Kies will not work without a stock recovery or a rooted phone from my experience.
I would be surprised if kies can restore your phone as ATT never released a full 4.3 stock ROM. ATT only made 4.3 available via an OTA update.
Click to expand...
Click to collapse
I don't know about AT&T, but I'm on Telus in Canada and I used kies to revert back to stock 4.3 with CWM recovery and phone rooted, and it worked no problem.
audit13 said:
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
So, I know there is a "thanks," button but I feel like that would be a little too informal for how much I appreciate your help! I downloaded ADB to move the rom (I went with AOKP because it was the first one that worked) to my phone, flashed it using TWRP and...BAM! We are back in business. Thanks for the direction, I thought I had a nice, new, shiny brick on my hands for about two days.
sjthuss said:
I don't know about AT&T, but I'm on Telus in Canada and I used kies to revert back to stock 4.3 with CWM recovery and phone rooted, and it worked no problem.
Click to expand...
Click to collapse
Canadian carriers use the i747m while att users get the i747.
The Canadian carriers did release a full 4.3 ROM unlike att who did not.
Hi
I'm trying to downgrade Android 4.4 KitKat to 4.3 JellyBean
Had this error "Invalid magic string" when I flashed from Odin
Flashed a custom Phill Recovery and did a format /system /data thinking it would erase the Knox protection.
Now im stuck with no OS and I cant flash.
Any help?
:crying:
You have to re-flash 4.4.2 KitKat from Odin.
Once you've installed the KitKat bootloader which is KNOX enabled you've already tripped the warranty flag if you have since flashed any unsigned firmware image (recovery, ROM, kernel) and once it is tripped it cannot be reset, nor can the KitKat bootloader be downgraded.
You can flash a Jelly Bean based ROM if you want but that will have no effect on the KNOX flag that you have probably already tripped. Users of supported devices who have not upgraded their bootloader to KitKat can flash @civato's FlexNote ROM if they want to experience KitKat on the Note 8.0 without tripping the Knox flag.
ramjet73
ramjet73 said:
You have to re-flash 4.4.2 KitKat from Odin.
Once you've installed the KitKat bootloader which is KNOX enabled you've already tripped the warranty flag if you have since flashed any unsigned firmware image (recovery, ROM, kernel) and once it is tripped it cannot be reset, nor can the KitKat bootloader be downgraded.
You can flash a Jelly Bean based ROM if you want but that will have no effect on the KNOX flag that you have probably already tripped. Users of supported devices who have not upgraded their bootloader to KitKat can flash @civato's FlexNote ROM if they want to experience KitKat on the Note 8.0 without tripping the Knox flag.
ramjet73
Click to expand...
Click to collapse
Hi Ramjet
Thanks for your kind assistance.
Ive flashed the 4.4.2 KitKat with Odin and the device is working.
However, I was not able to flash the JellyBean rom as it prompted the "Invalid magic string" error again.
I'm using this Google Play: MultiWindow Manager app to enable all my programs to run multi-windows.
With KitKat firmware, I was prompted the following error message after rooting:
java.io.FileNotFoundException: /system/csc/others.xml: open failed: EROFS (Read-only file system)
Hence, I would really need JellyBean back.
Any possibility?
Thanks!
AlaronTamnar said:
Hi Ramjet
Thanks for your kind assistance.
Ive flashed the 4.4.2 KitKat with Odin and the device is working.
However, I was not able to flash the JellyBean rom as it prompted the "Invalid magic string" error again.
I'm using this Google Play: MultiWindow Manager app to enable all my programs to run multi-windows.
With KitKat firmware, I was prompted the following error message after rooting:
java.io.FileNotFoundException: /system/csc/others.xml: open failed: EROFS (Read-only file system)
Hence, I would really need JellyBean back.
Any possibility?
Thanks!
Click to expand...
Click to collapse
Some users have claimed to flash back to 4.2 from 4.4 using Odin but that always excludes the bootloader and strange things can happen when using the KitKat bootloader with a Jelly Bean ROM. Here's a thread from the SamMobile website that talks about those issues. In theory flashing a Jelly Bean ROM zip should be the same as flashing JB with Odin since the KK bootloader can't be downgraded so I'm not surprised that you are having some issues.
There seems to be a variety of experiences when flashing a 4.2 ROM with the 4.4 bootloader installed and there is a thread in the Q&A section that discusses that. I'm running the FlexNote ROM by @civato and it fixes some of the KitKat issues like Spen alignment so I'm not even considering going back to Jelly Bean.
ramjet73
bOOT eRROR
HI i am facing a serious problem. i was just trying to do a factory reset to my phone and i got stuck. It rebooted and it didnt go to team win. i was using DN3 Rom v5 with agni kernel. so i decide to go to stock. and now i have a problem. i booted a 4.1.2 original rom and i was back to stock and then i tried to update using ATT and after rebooting it got stuck in The Samsung Galaxy note 2 boot screen and i tried everything i know to work things out. but it doesnt work. i cannot enter into recovery mode all i can do is go to download mode. i have tried installing jellybean but when i read about it it said kk boot loader is locked and the only way is to install a kk ...4.4.2 rom. but the rom file i have is zip and i dont know how to convert it into md5 file so that i can boot using odin. i would really appretiate if you can help me with this problem. i tried installing a custom recovery but it doesnt work,,, please help
AlaronTamnar said:
Hi
I'm trying to downgrade Android 4.4 KitKat to 4.3 JellyBean
Had this error "Invalid magic string" when I flashed from Odin
Flashed a custom Phill Recovery and did a format /system /data thinking it would erase the Knox protection.
Now im stuck with no OS and I cant flash.
Any help?
:crying:
Click to expand...
Click to collapse
The Only thing you need to do is download another Official Firmware of KITKAT 4.4 and download again ,I hope it you will succeed .I have faced the same error and tried several times but as i have updated my tab to 4.4 with OTA and then if i try to download my old jellybean it wont work .When i downloaded kitkat it succeeded just in first time and my phone got alive again.
I know this an old thread but can anyone provide me link on where to download official firmware of Kitkat 4.4 for ATT galaxy note 8. I am unable to find the firmware. Thanks.
Invalid magic string
Hi everyone
i was fiddling around with my Galaxy Note 8.0 (gt-n5110) and flashed the ressurection remix nougat rom, i wasnt able to flash gapps with it so i decided to factory reset the whole tab and flash the gapps zip again. When I finally factory reset it was stuck on the Samsung logo and i tried flashing the stock 4.1.2 on it using odin but it keeps saying failed on the computer and invalid magic string on the tab
what should i do to revert back to stock android?
AlaronTamnar said:
Hi
I'm trying to downgrade Android 4.4 KitKat to 4.3 JellyBean
Had this error "Invalid magic string" when I flashed from Odin
Flashed a custom Phill Recovery and did a format /system /data thinking it would erase the Knox protection.
Now im stuck with no OS and I cant flash.
Any help?
:crying:
Click to expand...
Click to collapse
Awwwww bummer! I am surprised you did not get any info about down grading FW, before flashing your device. Basically it can cause such an issue, especially if your FW is made for a diff device. I don't think any Note 8.0 tablets ever got 4.3, maybe 4.1.1 at least. 4.2.2 was the first update from stock. 4.4.2 and 4.4.4 were one more upgrade after that.
Hello,
I have an AT&T branded Note 8.0, SGH-I467 with NI3 (4.4.2) firmware. SGH-I467 has a locked bootloader.
Unfortunately, I hate 4.4.2! It has a 2mm (1/16") offset when writing with S Pen. I have heard the older firmware like MF1 (4.1.2) doesn't have this problem.
Here is where I stumble. I am NOT able to flash MF1.
If you browse this other thread, for a different subject however https://forum.xda-developers.com/showthread.php?t=2430540, the author indicates one can downgrade from MF2 OTA back to MF1 using Odin 3.07.
Nevertheless, I am not able to use the same tool to downgrade from NI3 to MF1. What's the difference between the two? When one takes an OTA to upgrade from MF1 to MF2, does the bootloader lock remain at MF1 and hence downgrading back to MF1 is still possible?
I bought my I467 used from eBay. Thus, I don't know if NI3 is the original firmware or someone upgraded it from an earlier version. Any comment is highly appreciated.
By the way, my Odin 3.07 fails immediately, ie. nothing is flashed. The tablet prompts "SW REV. Invaild magic string." (Invaild = Invalid. Samsung's typo)
Here is the Odin message:
.
.
Initialization
Get PIT for mapping
Firmware update start
sboot.bin
NAND Write Start
FAIL!
All threads completed. (succeed 0/ failed 1)
[updated Jan 24th, 2018]
I have just learned above 4.3, downgrade is not possible with SGH-I467's locked bootloader. This explains why I467UCAMF1 wouldn't load since the predecessor on my tablet I467UCUBNI3 is 4.4.2. It also explains why one can downgrade from AMF2 to AMF1 because both are 4.1.2.
To address my original problem of 1/16" (2mm) offset, since training in S Note never works for me, I have found a workaround I can live with. Turn my tablet upside down if I have to draw precisely. In this case, I move the offset from under my S Pen, since I'm right handed, to the left where I can see the cursor (or pointer). By following the cursor instead of the nib, I know when to drop down my S Pen to start drawing.
Gosh and you are complaining instead of finding a solution. The solution to your spen issues are simple. Train it in Snote, by not lifting while drawing at a slight angle with the tip, along the edge of the screen until you meet where you started. Some report that going over a few times without lifting will help. May take a few tries.
I AM HAPPY WITH 4.4.2. NO ISSUES WHAT SO EVER ON BOTH TABLETS.
I know this is a very old Thread But I am running into the Invalid Magic String error while trying to upgrade to 4.4.2 on my GT-N5110 I bought it used and they flashed some form of custom ROM because the status is Custom and the Knox flag is tripped. What can I do to install 4.4.2
Phone was rooted with a custom rom and custom recovery. I tried to do the OTA update to get the latest version of Android Stock and it failed. I downloaded Odin and tried to flash stock recovery and now its stuck in Download Mode.
I have tried all these roms with no success
https://rwilco12.com/downloads.php?dir=Files/Devices/Samsung Galaxy S3 (SPH-L710)/Stock ROMs/
I've tried 4-5 different versions of odin as well and everything fails.
If anyone could help me I'd really appreciate it. Thanks!
cwa82 said:
Phone was rooted with a custom rom and custom recovery. I tried to do the OTA update to get the latest version of Android Stock and it failed. I downloaded Odin and tried to flash stock recovery and now its stuck in Download Mode.
I have tried all these roms with no success
https://rwilco12.com/downloads.php?dir=Files/Devices/Samsung Galaxy S3 (SPH-L710)/Stock ROMs/
I've tried 4-5 different versions of odin as well and everything fails.
If anyone could help me I'd really appreciate it. Thanks!
Click to expand...
Click to collapse
Holy cow. You cannot OTA update with custom ROM and recovery. Not possible. You need Odin with the whole stock ROM (which is KitKat). Ugh
You would have to flash the entire stock .tar in Odin.... Why? It's KitKat... 4.4.2. no security patches.
Flash TWRP and whatever custom ROM you were on.
No backup? It's difficult to help that
madbat99 said:
Holy cow. You cannot OTA update with custom ROM and recovery. Not possible. You need Odin with the whole stock ROM (which is KitKat). Ugh
You would have to flash the entire stock .tar in Odin.... Why? It's KitKat... 4.4.2. no security patches.
Flash TWRP and whatever custom ROM you were on.
No backup? It's difficult to help that
Click to expand...
Click to collapse
i do have a backup
If I could just get TWRP working I would be all set and minimum be back where I started.
I was able to fix the phone.
I installed Kies3Setup
I ran all the updates and then I uninstalled it.
I downloaded L710VPUDNJ2_L710SPRDNJ2_L710VPUDNJ2_HOME.tar.md5
I successfully loaded it in PDA with Odin3v185
hopefully this helps someone else who's stuck in download mode with a Sprint Galaxy s3
cwa82 said:
I was able to fix the phone.
I installed Kies3Setup
I ran all the updates and then I uninstalled it.
I downloaded L710VPUDNJ2_L710SPRDNJ2_L710VPUDNJ2_HOME.tar.md5
I successfully loaded it in PDA with Odin3v185
hopefully this helps someone else who's stuck in download mode with a Sprint Galaxy s3
Click to expand...
Click to collapse
Good job