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
Related
I'm having issues with a bootloop on the incredible after rooting using unrevoked 3 and making the mistake of choosing cyanogenmod as the recovery because I'm incredibly new at this. Now granted this isn't an issue, I have root access now and I'm able to assign superuser and the phone boots to what looks like the stock rom. However, I wanted to flash cyanogen 7 rc2 and it's giving me a lot of issues when I try to access the clockworkmod recovery screen. I downloaded the rommanager from the market and flashed the recovery to clockworkmod 3.0.0.8 as per a wiki online and tried to boot to recovery. from there it hits the HTC incredible screen, then flashes every 3 seconds rather than showing the green text it's supposed to show.
I still have S-on and unrevoked won't run properly again. Tried running the factory reset and it's another bootloop. I tried going through the steps for a "manual recovery file flash via cyanogen's wiki, but I'm running into errors.
Summary:
unrevoked 3.32 completed successfully even using the cyanogenmod rom as the recovery file.
Have root access, S-on, radio version ~.7.28
Can't flash back to stock due to bootloop
Can't factory reset due to bootloop
Can't get to clockworkmod recovery screen due to bootloop
phone able to boot to main screen with original
Ideal solution: get to clockworkmod recovery screen and install C7RC2
Any help appreciated!
Why do you think using ClockworkMod was a mistake? It's one of the better AOSP ROMs out there.
It sounds to me like you're probably going to have to download one of the stock RUUs to completely revert your phone to stock. You might have a corrupted recovery. You can't flash ClockworkMod or an alternative recovery via RomManager?
oh don't get me wrong, my huge problem here is that I can't get into recovery, and I didn't load clockworkmod initally, but it is (as rom manager says) my recovery image and it's just not working at all.
I tried going with a RUU and it wouldn't get into bootloader properly (just shows HTC on the screen till the the ruu times out) I'll try on a 32 bit machine when I get home. I was originally able to flash on that and unrevoked was giving me issues till I did a 32 bit xp attempt. Thanks for the response!
whoops, forgot to address your last point. Tried another version of clockwork and the RA_GNM 1.8.1 and neither stopped it from bootlooping rather than recovery screen.
HTCP2newb said:
I'm having issues with a bootloop on the incredible after rooting using unrevoked 3 and making the mistake of choosing cyanogenmod as the recovery because I'm incredibly new at this. Now granted this isn't an issue, I have root access now and I'm able to assign superuser and the phone boots to what looks like the stock rom. However, I wanted to flash cyanogen 7 rc2 and it's giving me a lot of issues when I try to access the clockworkmod recovery screen. I downloaded the rommanager from the market and flashed the recovery to clockworkmod 3.0.0.8 as per a wiki online and tried to boot to recovery. from there it hits the HTC incredible screen, then flashes every 3 seconds rather than showing the green text it's supposed to show.
I still have S-on and unrevoked won't run properly again. Tried running the factory reset and it's another bootloop. I tried going through the steps for a "manual recovery file flash via cyanogen's wiki, but I'm running into errors.
Summary:
unrevoked 3.32 completed successfully even using the cyanogenmod rom as the recovery file.
Have root access, S-on, radio version ~.7.28
Can't flash back to stock due to bootloop
Can't factory reset due to bootloop
Can't get to clockworkmod recovery screen due to bootloop
phone able to boot to main screen with original
Ideal solution: get to clockworkmod recovery screen and install C7RC2
Any help appreciated!
Click to expand...
Click to collapse
Did you try getting to recovery manually power off the phone while its off press power and volume down at the same time you should be in hboot use the volume button to scroll down boot into recovery.....
Sent from my Incredible using XDA App
I don't think unrevoked finish all The way because you should be s-off did you wait until it said "done"..... or did you stop when it said "this is a triumph"
Sent from my Incredible using XDA App
Okay, from a 32 bit system has resolved the flashing back to a stock rom, I will update as to whether I can get into recovery and will wait until I am told "triumphant" this time around.
Will post an update in a bit if this was all that was necessary to fix the issue. Thank you all to have posted so far, please post if you think I'm missing something else.
HTCP2newb said:
Okay, from a 32 bit system has resolved the flashing back to a stock rom, I will update as to whether I can get into recovery and will wait until I am told "triumphant" this time around.
Will post an update in a bit if this was all that was necessary to fix the issue. Thank you all to have posted so far, please post if you think I'm missing something else.
Click to expand...
Click to collapse
No you need to wait till it says done sorry you misunderstood me......let it go till it says done and it stops completely..... because the last thing it does is flash the recovery
Sent from my Incredible using XDA App
Did you try flashing a recovery through hboot?
Sent from my ADR6300 using XDA App
Okay, problem totally resolved. basically what happened was that there was an incomplete unrevoked process for whatever reason or another. I repaired by downloading the RUU off the HTC website and flashing back to stock. That generated an error of "your firmware is too new" which is available elsewhere in XDA, basically solved by going into hboot and factory resetting.
Once I had the factory reset completed, I used a 32 bit system to unrevoke the phone (after setting debugging to on in applications > developer settings >debugging on) then I was able to properly boot into recovery. I recommend Clockworkmod update to 3.0.0.8 in Rom manager, but I used 2.5 and didn't have much of an issue. I backed up and the wiped the memory and cache and installed 7r2 without an issue.
The phone is WAY more stable now (thanks to all the hard work at Cyanogen! Thank you also to everyone who posted here!) Pandora doesn't randomly cut songs in half and battery life seems to have improved. Whether that was verizon's crap or I went market-crazy and had waaaay too many apps syncing... I can't say.
Thank you everyone again!
edit: on a whim I looked at the heimdall command line options and saw "close pc screen" as one of the arguments and tried that and it booted up perfectly!!!!! So relieved it was something that simple!
I got my S4 last night and immediately tried to root it after I got it, I read up on some stuff (not new to rooting, I've rooted multiple devices in the past) and attempted to flash TWRP via Odin but then it said it failed for some reason, I tried again and it failed. I figured everything was fine until I rebooted and got "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again." I tried to connect it to my old Windows XP pc (my main pc runs Arch Linux) and kies kept saying "connecting" no matter how many times I tried to make it connect or reinstall the drivers.
I can get to download mode and I'm trying to flash the stock firmware via heimdall but it's taking forever to uncompress the image. I got the images from here: http://forum.xda-developers.com/showthread.php?t=2258628
I tried to flash cf-autoroot with heimdall in hopes that it would restore my bootloader but it wouldn't flash because it said it was missing an XML file.
I think I'm just missing the bootloader/recovery image but I'm not sure. Am I heading in the right direction?
If you have root and still have access to the phone when u turn it on flash cwm recovery via Odin or if Ur phone turns on nd have root then download goomanager nd you can install twrp with that app with no problems
Sent from my SGH-M919 using xda premium
im having the same issue...
i am flashing Modem_UVUAMDL.tar and philz touch 5.08.5-jfltetmo as recovery, OUDHS jfltetmo also, but nothing is working
i was running infamous 4.0 ROM, flashed the cyanogenmod nightly and somehow everything exploded and now the only thing on my screen is the SGS4 stock image... it wont boot into recovery mode only download.
i am on an OSX using heimdall and i do not ever have access to a PC!
icecreamwithyou said:
im having the same issue...
i am flashing Modem_UVUAMDL.tar and philz touch 5.08.5-jfltetmo as recovery, OUDHS jfltetmo also, but nothing is working
i was running infamous 4.0 ROM, flashed the cyanogenmod nightly and somehow everything exploded and now the only thing on my screen is the SGS4 stock image... it wont boot into recovery mode only download.
i am on an OSX using heimdall and i do not ever have access to a PC!
Click to expand...
Click to collapse
Did you find a fix I have the same issue but I do have a pc?
brando56894 said:
edit: on a whim I looked at the heimdall command line options and saw "close pc screen" as one of the arguments and tried that and it booted up perfectly!!!!! So relieved it was something that simple!
I got my S4 last night and immediately tried to root it after I got it, I read up on some stuff (not new to rooting, I've rooted multiple devices in the past) and attempted to flash TWRP via Odin but then it said it failed for some reason, I tried again and it failed. I figured everything was fine until I rebooted and got "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again." I tried to connect it to my old Windows XP pc (my main pc runs Arch Linux) and kies kept saying "connecting" no matter how many times I tried to make it connect or reinstall the drivers.
I can get to download mode and I'm trying to flash the stock firmware via heimdall but it's taking forever to uncompress the image. I got the images from here: http://forum.xda-developers.com/showthread.php?t=2258628
I tried to flash cf-autoroot with heimdall in hopes that it would restore my bootloader but it wouldn't flash because it said it was missing an XML file.
I think I'm just missing the bootloader/recovery image but I'm not sure. Am I heading in the right direction?
Click to expand...
Click to collapse
I just recently purchased a rooted S4 and I downloaded a ROM from this site that wasn't compatible with my S4 and flashed it (BIG mistake I know now). So now I can't start up my phone. I read here that I should wipe out the divalk cache/cache and restart (didn't work). Reset to factory settings and reboot (didn't work). Download the TWRP flashable zip and flash it from the Recovery memory then reboot (didn't work). Now I'm really worried. Can you please help me?
Warrior1016 said:
I just recently purchased a rooted S4 and I downloaded a ROM from this site that wasn't compatible with my S4 and flashed it (BIG mistake I know now). So now I can't start up my phone. I read here that I should wipe out the divalk cache/cache and restart (didn't work). Reset to factory settings and reboot (didn't work). Download the TWRP flashable zip and flash it from the Recovery memory then reboot (didn't work). Now I'm really worried. Can you please help me?
Click to expand...
Click to collapse
What does it do when you boot up?
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.
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
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.