Got a t217s free from sprint, took it home and rooted it using kingoroot(kingo worked wonderfully prior to the NB8 update). then a few weeks later I got the notification for a software update(the NB8 update). Without unrooting, I downloaded it, and it successfully installed. Whent to re-root with kingo and it failed to root(tried all the troubleshooting steps), then I tried oneclickroot and it said I was already rooted, however rootchecker said I wasn't, and none of my root programs worked. So I decided to install cwm recovery and installed superSU, regained root access and didnt really think much of it. Then the word surfaced that we might be getting yet another update(although its not likely) I decided to revert back to a stock recovery. Upon doing so, I booted into recovery and saw the words "no command", and when I selected reboot, it said "error" yet proceeded to boot up normally so I didn't think much of it. Then I wanted to wipe my cache partition and discovered that when I select "wipe cache partition" it says "error" and proceeds to boot up.
I have tried re flashing stock recovery multiple times, with files from multiple sources to make sure its not just a bad download. I have tried factory reset and a fresh flashing of the stock firmware using odin. All to no avail.
Sent from my SM-T217S using XDA Free mobile app
Related
On Monday while I was reading a book on my SGH-T889 my phone suddenly restarted itself and then gave me a message saying "Encryption Failed."
I looked up that problem and found that the only fix was likely a factory reset. I tried just formatting data, wiping cache and dalvik, and fixing permissions but I did eventually have to do a factory reset to fix my issue.
Since the reset cleared my stored ROM files, I used Odin to go back to the stock rooted 4.1.2 firmware and used Odin again to install TWRP 2.5.
I re-installed Jedi X13 and all was well until last night when I tried to boot into recovery to make a new nandroid backup.
The phone went into a bootloop between TWRP and and Samsung logo, so I pulled the battery and tried to boot again but I kept getting the boot loop with TWRP.
At this point I went into download mode and Odined TWRP to the phone again.
Unfortunately, now the only thing that happens when I try to boot the phone is that I get to a white fuzzy screen. Same thing when I try to boot to recovery. I can boot to download mode, but I cannot flash even the stock firmware as it is telling me it cannot find the .pit file. I have tried adding the .pit file from a SGH-T889V as that is the only one I have been able to find but so far no luck.
Can anyone please help?
Luckily my phone is not showing as running any custom firmware so I can send it back in for replacement, but the lady at T-Mobile let me know that the phones are currently on back order.
If you can't Odin then it is bricked the only option is through T-Mobile replacement, try using the toolkit from the original thread
Sent from my SGH-T889 using xda premium
Hello.
I have an AT&T SGH-I317. The OTA upgrade is being pushed, but my phone will not upgrade.
After the download, a Teamwin screen comes up, and after an error message that the "MD5 file not found", the TWRP screen appears, with no indication of how to proceed with the upgrade. I have just tried several different choices, including a factory reset, all to no avail. Before exiting TWRP, it advises that the phone doesn't appear to be rooted, and do I want to install SuperSU (which I've declined).
Can anyone advise as to how to go about the OTA upgrade? Using TWRP, or uninstalling TWRP?
Thanks.
[email protected] said:
Hello.
I have an AT&T SGH-I317. The OTA upgrade is being pushed, but my phone will not upgrade.
After the download, a Teamwin screen comes up, and after an error message that the "MD5 file not found", the TWRP screen appears, with no indication of how to proceed with the upgrade. I have just tried several different choices, including a factory reset, all to no avail. Before exiting TWRP, it advises that the phone doesn't appear to be rooted, and do I want to install SuperSU (which I've declined).
Can anyone advise as to how to go about the OTA upgrade? Using TWRP, or uninstalling TWRP?
Thanks.
Click to expand...
Click to collapse
From what I understand and my experience, you can't get OTA updates with a custom recovery installed. You need to have stock recovery.
There's a great post on going back to stock on these forums that has saved me a couple of times when I thought I bricked my phone. Roll it back and then give it a shot.
InertiaticFlow said:
From what I understand and my experience, you can't get OTA updates with a custom recovery installed. You need to have stock recovery.
There's a great post on going back to stock on these forums that has saved me a couple of times when I thought I bricked my phone. Roll it back and then give it a shot.
Click to expand...
Click to collapse
This^^^^^^^^^^:thumbup::thumbup:
Sent from my SAMSUNG-SGH-I317 using Tapatalk
This is the post I was talking about:
http://forum.xda-developers.com/showthread.php?t=2275844
Just follow those instructions exactly and you should be back to stock in no time. Odin 3.09 cuts the flash time down to 3-4 minutes but 3.07 works just as good.
I looked around but could not find my problem - I sincerely apologize if it has been asked elsewhere.
Yesterday I attempted to install the newest root66 (4.3) on my telus GS3 using odin. Everything seemed to go ok, but the phone was sitting at the samsung logo for a long while (and vibrating every 5 or 10 seconds as well). The phone went through the normal boot process after the flash, including updating the apps, but then rebooted and just sat there. Thinking something was wrong I attempted to flash the root again and had the same problem. After that I used odin to flash the stock image and waited all night and day for it and it was still on the samsung logo. Tonight I went into the stock recovery and cleared the cache and attempted to flash the root66 again. The phone seemed to go through the normal upgrade boot again (after odin said pass) with the android upgrade spinning chest thing and all that.
I can still access download mode and the stock recovery, so I don't think I am in too bad of shape - part of me thinks it is just a matter of patience, which is fine if it is, but if not, I'd like to keep working on it. Any ideas?
In summery - in case that was confusing
1) flashed root66 4.3, odin indicated success, boot after upgrade was similar to what I have seen before
2) Waited for a couple hours
3) tried root66 again, and waited
4) flashed stock, odin indicated success and waited many hours
5) cleared cache, flashed root66, currently waiting again
6) maintain access to stock recovery and download mode
I'd like to not lose everything on the phone if possible, but if I have to so be it.
Any thoughts?
odin to stock 4.3 then root your phone using CF Autoroot by Chainfire... check always the model of ur phone and the file you are downloading if it is for your phone..
Flashing stock with odin just leaves me stuck at the same Samsung screen. Pulsing Samsung and whatnot
jaybeeee said:
Flashing stock with odin just leaves me stuck at the same Samsung screen. Pulsing Samsung and whatnot
Click to expand...
Click to collapse
Reboot into stock recovery and factory reset.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Got a t217s free from sprint, took it home and rooted it using kingoroot(kingo worked wonderfully prior to the NB8 update). then a few weeks later I got the notification for a software update(the NB8 update). Without unrooting, I downloaded it, and it successfully installed. Whent to re-root with kingo and it failed to root(tried all the troubleshooting steps), then I tried oneclickroot and it said I was already rooted, however rootchecker said I wasn't, and none of my root programs worked. So I decided to install cwm recovery and installed superSU, regained root access and didnt really think much of it. Then the word surfaced that we might be getting yet another update(although its not likely) I decided to revert back to a stock recovery. Upon doing so, I booted into recovery and saw the words "no command", and when I selected reboot, it said "error" yet proceeded to boot up normally so I didn't think much of it. Then I wanted to wipe my cache partition and discovered that when I select "wipe cache partition" it says "error" and proceeds to boot up.
I have tried re flashing stock recovery multiple times, with files from multiple sources to make sure its not just a bad download. I have tried factory reset and a fresh flashing of the stock firmware using odin. All to no avail.
Any help would be appreciated. I hope this is the right section for my issue... if its not im sorry.
Sent from my SM-T217S using XDA Free mobile app
I have a samsung tab 3 7" lite (or sm T110.)
I downloaded the CWM recovery which was not a problem. The problem that I encountered however was that I was not able to get to it.
I did not know however, that when you push the power+home+volume up combination that it can take up to 60 seconds to get into CWM recovery.
Frustrated I downloaded an app to get me into the CWM. I downloaded "reboot recovery" by Qbanin from the playstore.
The app said it required root accces which at that point i did not have yet. the app however seemed to work fine.
The app led me straight to the recovery mode. However I am now unable to go back to a normal boot.
I can still get into download mode and or recovery mode but this is all my tablet currently does.
After this debacle i figured there must be some setting somewhere which enables this boot to recovery. So I started whiping the dalvik cache, the regular cache, I did a factory reset. and I also formatted the cache. I installed root acces from a .zip. I installed a custom rom (T110UEUANE4.Full.Rooted.Deodexed.June2014). But nothing helped.
Never did i get any warnings or errors.
I have been googling since friday and cant figure this thing out.
How do I get back to normal boot?
Please help me
Exxoo87 said:
I have a samsung tab 3 7" lite (or sm T110.)
I downloaded the CWM recovery which was not a problem. The problem that I encountered however was that I was not able to get to it.
I did not know however, that when you push the power+home+volume up combination that it can take up to 60 seconds to get into CWM recovery.
Frustrated I downloaded an app to get me into the CWM. I downloaded "reboot recovery" by Qbanin from the playstore.
The app said it required root accces which at that point i did not have yet. the app however seemed to work fine.
The app led me straight to the recovery mode. However I am now unable to go back to a normal boot.
I can still get into download mode and or recovery mode but this is all my tablet currently does.
After this debacle i figured there must be some setting somewhere which enables this boot to recovery. So I started whiping the dalvik cache, the regular cache, I did a factory reset. and I also formatted the cache. I installed root acces from a .zip. I installed a custom rom (T110UEUANE4.Full.Rooted.Deodexed.June2014). But nothing helped.
Never did i get any warnings or errors.
I have been googling since friday and cant figure this thing out.
How do I get back to normal boot?
Please help me
Click to expand...
Click to collapse
You need to install the stock recovery to get it to boot. Then after you re-install CWM, only use the 3-button method to boot into recovery. There is a post in the recovery thread that has the stock recovery. Read the last page or 2 and you will find a link.