Related
the other day i tried restoring a back up via TWRP but it didnt work until i fastboot flashed boot.img...Alright so i updated my TWRP via goomanager app to the latest version (whatever is on there via goomanager) as in the TWRP forum discussions it was stated that previous versions were not working properly wihen restoring. So today i flashed a new ROM (NOS ROM) but that didnt work so i decided what better time than now to try restoring again, no dice didnt work and i had to fastboot flash the boot img for the restore file to take and boot up just fine again...ok peeps what am doing wrong??? again im fairly new at this flashing ROMS scene but i thought witht he TWRP update i would be good to go. Am i missing some settings ticks/options/checks? i saw a check box that said "recovery" i think in the restore or back up process dont remember which process. i tried going onto the TWRP discussion but it is locked down and states that there will no longer be any support for it...should i just switch to CWM?? thanks in advance to whom ever replies
twrp recovery..
kenohki88 said:
the other day i tried restoring a back up via TWRP but it didnt work until i fastboot flashed boot.img...Alright so i updated my TWRP via goomanager app to the latest version (whatever is on there via goomanager) as in the TWRP forum discussions it was stated that previous versions were not working properly wihen restoring. So today i flashed a new ROM (NOS ROM) but that didnt work so i decided what better time than now to try restoring again, no dice didnt work and i had to fastboot flash the boot img for the restore file to take and boot up just fine again...ok peeps what am doing wrong??? again im fairly new at this flashing ROMS scene but i thought witht he TWRP update i would be good to go. Am i missing some settings ticks/options/checks? i saw a check box that said "recovery" i think in the restore or back up process dont remember which process. i tried going onto the TWRP discussion but it is locked down and states that there will no longer be any support for it...should i just switch to CWM?? thanks in advance to whom ever replies
Click to expand...
Click to collapse
What did you have checked while making the backup? data? recovery? cache? system? and did you rename the back up?
System, data and boot are checked...I didn't mess with the options just hit restore and let it do it's thing...should I change something or check the other 2 boxes (one of them being "recovery" forgot what the other option was)?
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
System, data and boot are checked...I didn't mess with the options just hit restore and let it do it's thing...should I change something or check the other 2 boxes (one of them being "recovery" forgot what the other option was)?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I would check recovery as well and try again.....also make sure to wipe everything before flashing anything
---------- Post added at 12:42 PM ---------- Previous post was at 12:34 PM ----------
canemaxx said:
I would check recovery as well and try again.....also make sure to wipe everything before flashing anything
Click to expand...
Click to collapse
also some roms are picky about which recovery is used to install/backup. I can say I have had no issues backing up stock or custom roms with twrp on my DNA
Alright sounds good maybe later on tonight when I'm at my computer just in case thank you for the tips I as well haven't had much trouble flashing ROMS with TWRP, albeit I've only tried flashing 2 or 3 been very happy with ViperDNA just wanted to check out different ones and easily restore back to viper
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
Alright sounds good maybe later on tonight when I'm at my computer just in case thank you for the tips I as well haven't had much trouble flashing ROMS with TWRP, albeit I've only tried flashing 2 or 3 been very happy with ViperDNA just wanted to check out different ones and easily restore back to viper
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Check out NOS its a great rom
canemaxx said:
Check out NOS its a great rom
Click to expand...
Click to collapse
That's exactly what I was trying when all this happened...I flashed it via flash gui app like I've been doing but for some reason it didn't work...when I went to unlock screen it would pull up HTC splash screen and just stay stuck there... I'm not S-off yet so would that have something to do with NOS ROM not functioning?
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
That's exactly what I was trying when all this happened...I flashed it via flash gui app like I've been doing but for some reason it didn't work...when I went to unlock screen it would pull up HTC splash screen and just stay stuck there... I'm not S-off yet so would that have something to do with NOS ROM not functioning?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
no thats how that rom boots....leave it alone for about 5-10 minutes youlll see the notificatiion light come on and your =e good to go
Let me rephrase that...it boots up, screen comes on silver background from butterfly then I go pull ring to unlock and it pulls up the HTC splash screen once I unlock and will not move from there...so that's when I reset and went back to viper...???
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
Let me rephrase that...it boots up, screen comes on silver background from butterfly then I go pull ring to unlock and it pulls up the HTC splash screen once I unlock and will not move from there...so that's when I reset and went back to viper...???
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Flash the new Nos build, and flash cpalmers kernel after the Rom install and then reboot.
Sent from my ADR6425LVW using Xparent Red Tapatalk 2
Haven't tried it since I posted this, but ok I'll give it another spin/attempt this weekend thanks for the tip
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
Haven't tried it since I posted this, but ok I'll give it another spin/attempt this weekend thanks for the tip
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I may have misread but did you wipe everything before loading nos? I saw what was checked for backup but not about wiping. You should wipe everything-system, then cache, then delvik cache-not exactly in that order (make SURE there IS a backup just in case). Load the rom AND flash the correct image file with adb. Also, many roms when FIRST loading up sit a long time before they start up, not sure if nos does this or not-I have been jumpy about the time sitting with a few roms when waiting was all I needed to do. I have had different Viper versions on a few times and moving to another rom was quirky each time I did so, not sure why.
NOS did that to me too. Just wait....it will load into the setup wizard. I think being s-on, which I still am...twrp isn't able to back up and restore your roms boot.img. just a guess but I to failed to restore a backup when an install went awry. Makes sense to be being that you can't install a kernel from recovery either.
Sent from my HTC6435LVW using xda app-developers app
Ajj915 said:
NOS did that to me too. Just wait....it will load into the setup wizard. I think being s-on, which I still am...twrp isn't able to back up and restore your roms boot.img. just a guess but I to failed to restore a backup when an install went awry. Makes sense to be being that you can't install a kernel from recovery either.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I looked at the install instructions for nos, if you are s-on you need to do one extra step. You have to extract the rom into a folder somewhere to get the image file, copy the image file from it. Flash that image file using adb on your pc and THEN install the rom from your phone with goomanager. Without the image file loaded, I don't think it would work. If you are s-off this step is not needed.
rootntootn said:
I looked at the install instructions for nos, if you are s-on you need to do one extra step. You have to extract the rom into a folder somewhere to get the image file, copy the image file from it. Flash that image file using adb on your pc and THEN install the rom from your phone with goomanager. Without the image file loaded, I don't think it would work. If you are s-off this step is not needed.
Click to expand...
Click to collapse
I get that. I'm purely talking about after a full while that I'm not sure if twrp will restore the boot.img from a nandroid. S-On of course.
Sent from my HTC6435LVW using xda app-developers app
Ajj915 said:
I get that. I'm purely talking about after a full while that I'm not sure if twrp will restore the boot.img from a nandroid. S-On of course.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I believe it will, if it had the image from the get go. I believe that the back up has everything it needs. At least my back ups have never needed an image file. I decided I should try NOS myself and must say it would not go for me (S-off) it kept rebooting into recovery. I was going to try and also flash the boot image but have not done so yet.
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
rootntootn said:
I believe it will, if it had the image from the get go. I believe that the back up has everything it needs. At least my back ups have never needed an image file. I decided I should try NOS myself and must say it would not go for me (S-off) it kept rebooting into recovery. I was going to try and also flash the boot image but have not done so yet.
Click to expand...
Click to collapse
Oh yeah, and I restored my back up and that works just fine
rootntootn said:
I believe it will, if it had the image from the get go. I believe that the back up has everything it needs. At least my back ups have never needed an image file. I decided I should try NOS myself and must say it would not go for me (S-off) it kept rebooting into recovery. I was going to try and also flash the boot image but have not done so yet.
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
Oh yeah, and I restored my back up and that works just fine
Click to expand...
Click to collapse
Its the kernel in NOS. Flash NOS and then flash cpalmers kernel. Then reboot and do the setup and if you want to change to the zarboz kernel you need to delete system/bin/thermald or rename it to thermald_old.bak
Sent from my HTC6435LVW using Xparent Red Tapatalk 2
Hmmm well I did everything via my cell (been the way I've been flashing ROMS unless something goes wrong then I use ADB on computer) and everything when properly done works fine using Flash GUI APP love that app! I've flashed super charged hatka 320 (used that for a couple weeks) then switched over to viper...both using Flash GUI I tried using NOS but yes no dice loaded up but when I pull the unlock ring for whatever reason the splash screen comes up and it won't budge from there....and as for my original question haha TWRP did not work for me when restoring it tripped out like if it was missing the boot image (done that before so I'm familiar with that behavior haha)
Oh and I'm still S-on
Sent from my HTC6435LVW using xda app-developers app
CharliesTheMan said:
Flash the new Nos build, and flash cpalmers kernel after the Rom install and then reboot.
Sent from my ADR6425LVW using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
That's what mine does too......just wait til the notification light turns orange and you will be all set......be patient.
canemaxx said:
That's what mine does too......just wait til the notification light turns orange and you will be all set......be patient.
Click to expand...
Click to collapse
Really? After it boots up? That's odd but ok I'll give it a shot again but probably tomorrow will post here again if it doesn't work....thanks everyone for responding. I'm out at the moment and need cell to be functioning hahaha just in case
Sent from my HTC6435LVW using xda app-developers app
Hey guys, I sent my Note 2 into Samsung in Texas to repair it since the wifi was not connecting. Prior to sending it in, I had it rooted and unlocked based on the instructions on this site, but I put it back to stock (using those same directions) to limit the chance that sammy would screw me on my warranty.
I checked the status of my repairs today and it says they replaced the mainboard, so now I am wondering what I will have to do to get it back to its rooted and unlocked state the way it was before sending in. I am guessing that all I will have to do is boot into recovery and flash a rom, but maybe the stock process did more than that.
If anyone could walk me through the steps it takes to get from where it is to where it was, that would be great. Again, it was rooted and unlocked, then I used Odin to go back to stock (which I think means rooted stock, so simply the stock software while still being rooted and unlocked), and now I want to send it back to rooted/unlocked. Also, remember that the mainboard was replaced, and I am not sure if that matters to the whole process.
Thanks!
Head in over to the development section and check out Adam Outlers thread. Very detailed and great way to root and unlock.
Sent from my SCH-I605 using Tapatalk 2
Mandroidified said:
Head in over to the development section and check out Adam Outlers thread. Very detailed and great way to root and unlock.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
But do I need to reroot it? I guess I assumed that putting it back to stock meant rooted/unlocked stock, or stock software. No big deal, I can just reroot/unlock it like I did the first time, but I assumed it was something different.
I'd use triangle away too. I did that before sending it to vzw. Oddly, my counter was at 0
kimdoocheol said:
I'd use triangle away too. I did that before sending it to vzw. Oddly, my counter was at 0
Click to expand...
Click to collapse
Can you explain triangle away? Is that short for odin and what not?
Mindstar1 said:
Can you explain triangle away? Is that short for odin and what not?
Click to expand...
Click to collapse
No it's not. Triangle away is an app that resets your flash counter to 0. You needed to use it before using odin to stock so it's to late right now.
To get back to where you were you will need to repeat the unlock process by Adam. When you used odin you unrooted and relocked your phone. Think of it being just like the day you got it now.
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
No it's not. Triangle away is an app that resets your flash counter to 0. You needed to use it before using odin to stock so it's to late right now.
To get back to where you were you will need to repeat the unlock process by Adam. When you used odin you unrooted and relocked your phone. Think of it being just like the day you got it now.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
You sure about this? I thought the only way TriangleAway works is if you flash back stock ROM/kernel. I never used it before and my flash counter was at 0.
Anyways, also I would reset factory defaults if your firmware shows Modified, as well.
There was something on the lock/unlock thread about going back to stock and keeping the phone unlocked. It said if you were using the ota that made the phone so hard to unlock that you should flash a different tar file (an alternate one) to stay unlocked. I will track it down and post it here, but it made it seem like it would keep the phone unlocked.
Sent from my Nexus 7 using Tapatalk 2
kimdoocheol said:
You sure about this? I thought the only way TriangleAway works is if you flash back stock ROM/kernel. I never used it before and my flash counter was at 0.
Anyways, also I would reset factory defaults if your firmware shows Modified, as well.
Click to expand...
Click to collapse
Yes I'm sure. The bootloader had to be unlocked for triangle away to work (see screen shot from triangle away OP). So when he uses odin and re locks it's to late. Also, flashing stock firmware doesn't trip the flash counter.
Sent from my SGH-T889 using xda app-developers app
Mindstar1 said:
There was something on the lock/unlock thread about going back to stock and keeping the phone unlocked. It said if you were using the ota that made the phone so hard to unlock that you should flash a different tar file (an alternate one) to stay unlocked. I will track it down and post it here, but it made it seem like it would keep the phone unlocked.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
There is an "alternate restore" file that does not flash a boot loader. If that's what you flashed then your boot loader is still unlocked. In the op you didn't specify you just said you restored to stock which would suggest full stock with a lock bootloader.
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
There is an "alternate restore" file that does not flash a boot loader. If that's what you flashed then your boot loader is still unlocked. In the op you didn't specify you just said you restored to stock which would suggest full stock with a lock bootloader.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
I did flash the alternate file, sorry for not specifying. The directions were pretty clear that I had to do the alternate file. Anyways, assuming I did that, do I just have to reroot or just flash a rom?
Sent from my Nexus 7 using Tapatalk 2
Mindstar1 said:
I did flash the alternate file, sorry for not specifying. The directions were pretty clear that I had to do the alternate file. Anyways, assuming I did that, do I just have to reroot or just flash a rom?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Im not sure if it's rooted already or not. If it is then install a recovery and flash a ROM. If not then reroot with root 66 odin install a recovery and flash
Sent from my SGH-T889 using xda app-developers app
My solution
OK, so I got the phone back and ran into a few hiccups but got it worked out.
Basically I got the phone and re-rooted it and when I tried to install a new recovery I got an error telling me that I am using bad software and I should take the phone to VZW (yeah right).
I then hopped back on ODIN and went back to stock, same way I did before sending it in to Sammy. Once I did that, I went back to the thread about rooting/unlocking and found that there was an update since I last visited. Now, there was a one click method so I decided to give that a shot. I plugged her in, had some issues with drivers but got it worked out, then ran the process. Once it was finished, all was well.
I am not sure if the phone was still rooted/unlocked or not, but either way the one click method appeared to straighten it out.
VOTE! Which custom recovery are you guys using on your Rezound?
188 Views, 6 Votes, including mine.
I like to rearrange data and free up space a lot of the time I'm in recovery mode as well. TWRP's UI serves that purpose best. It is also has better support from apps like TiBu than Amon Ra does.
javaguy216 said:
VOTE! Which custom recovery are you guys using on your Rezound?
Click to expand...
Click to collapse
Amon Ra 3.16, better nandroids, can wipe boot.
My name's Harold and I'm a flashaholic.....
hgoldner said:
Amon Ra 3.16, better nandroids, can wipe boot.
My name's Harold and I'm a flashaholic.....
Click to expand...
Click to collapse
wipe boot breaks some kernel installs.... Just sayin
I use CWM
Flyhalf205 said:
wipe boot breaks some kernel installs.... Just sayin
I use CWM
Click to expand...
Click to collapse
I tried all 3. I really like the touch option. The only option I couldn't find in CWM is a way to boot back to bootloader, like the other 2 recoveries offer.
Sent from my Rezound using Tapatalk 2
Flyhalf205 said:
wipe boot breaks some kernel installs.... Just sayin
I use CWM
Click to expand...
Click to collapse
I wonder if this is what happened to me lately. Got a replacement device last week, wiped boot and been having all kinds of problems. Sending back for another replacement tomorrow. Phone has been running hot and not charging correctly and battery has been discharging fast.
Sent from my ADR6425LVW using xda app-developers app
ryryrocco said:
I wonder if this is what happened to me lately. Got a replacement device last week, wiped boot and been having all kinds of problems. Sending back for another replacement tomorrow. Phone has been running hot and not charging correctly and battery has been discharging fast.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Some kernels won't install at all unless there is an existing kernel. We extract the ramdisk from the existing kernel rather than bundling our own, so if the kernel is not there, that part will fail and the system won't boot. Doing it that way ensures the widest possible compatibility with different ROMs and makes sure that we don't overwrite any ramdisk customizations the ROM dev made.
Sent from my SCH-I605 using Tapatalk 2
I used an app suggestion from the guy that wants to get paid for everything to install TWRP on my ATT i527. It installed just fine and ROM Manger shows TWRP as being my recovery system. Only problem is, ATT blocks the recovery and now I can't get to stock recovery.
My biggest problem is I don't know how to to uninstall the TWRP and get back to stock recovery. Any suggestions? Do I unroot and do a factory reset?
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Ugh. That is a tough one. Know who you are talking about too. Nothing is for sure without a recovery rom. Would hate to see you get caught in a bootloop. That's a pain. Still waiting on my phone. Good luck and let us know how it goes.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Think I may just unroot and hit the factory reset option in the Backup menu.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Good luck
2SHAYNEZ
dparrothead1 said:
Think I may just unroot and hit the factory reset option in the Backup menu.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Click to expand...
Click to collapse
AFAIK factory reset won't bring back the stock recovery.
Download your device's Rom, flash it, and you'll have your stock recovery back.
unclefab said:
AFAIK factory reset won't bring back the stock recovery.
Download your device's Rom, flash it, and you'll have your stock recovery back.
Click to expand...
Click to collapse
I know you mean well but laughed when I read this. There is no rom for att mega. Hope you figured something out dparrothead1. Worst case is keep twrp, as long as phone is okay, it shouldn't hurt anything. At least, until we get a rom for this thing.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
I would guess you could flash twrp through Odin with the att version but don't mark my words
2SHAYNEZ
azpatterson3 said:
I know you mean well but laughed when I read this. There is no rom for att mega. Hope you figured something out dparrothead1. Worst case is keep twrp, as long as phone is okay, it shouldn't hurt anything. At least, until we get a rom for this thing.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Yeah az, I had second thoughts about doing the factory reset. I will just keep the TWRP until someone breaks out the bootloader.
The only reason I wanted the stock recovery was to see what this update is all about. The update d/l'ed fine and was going to install but it need stock recovery....I keep hitting the "unauthorized software has been detected... .turn off your phone and take to nearest store". I don't think being rooted has anything to do with it.
I think that sooner or later our phone will be figured out. But I have to tell you. With being rooted and being able to get rid of some bloatware, and with Nova Launcher, I'm really happy with this big assed phone! Sure, I miss some of the customization, but I hated PA and some of the other overloaded roms.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Maybe you could find stock recovery to reflashing it back... I'm not sure though if stock recovery from i.e. I9205 ROM couldn't brick your phone...
Dparrothead1 I received the update message yesterday but clicked out of it in error. I don't know what its for either. Suppose I'll google it in a few. I tried updating from settings and get an error saying update was interrupted.
D's Mega 6.3 ♥★♥ sgh-i527
So I had originally had TWRP/Hyperdrive on my phone, and switched to CWM/Cyanogenmod. I noticed now that I seem to have two different recoveries on my phone, because if I hold up+home+power I can go to a different version of CWM Recovery than if I use the Rom Manager app to boot into recovery. How would I rectify this? Would it involve wiping the /boot partition? I don't know where/how recoveries are stored so I don't understand how I can have two.
Doing a fresh install of a ROM has not resolved this by the way. And actually currently, I can't hold the buttons and boot into recovery at all, it gets stuck on the Samsung logo. I can only get into recovery via Rom Manager or Reboot options if I'm in android.
Markstache said:
So I had originally had TWRP/Hyperdrive on my phone, and switched to CWM/Cyanogenmod. I noticed now that I seem to have two different recoveries on my phone, because if I hold up+home+power I can go to a different version of CWM Recovery than if I use the Rom Manager app to boot into recovery. How would I rectify this? Would it involve wiping the /boot partition? I don't know where/how recoveries are stored so I don't understand how I can have two.
Doing a fresh install of a ROM has not resolved this by the way. And actually currently, I can't hold the buttons and boot into recovery at all, it gets stuck on the Samsung logo. I can only get into recovery via Rom Manager or Reboot options if I'm in android.
Click to expand...
Click to collapse
I would just Odin back to stock MDK and start fresh and choose whichever recovery suits you. I had to do the same a while back myself
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I would just Odin back to stock MDK and start fresh and choose whichever recovery suits you. I had to do the same a while back myself
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I've done that so many times.
Markstache said:
I've done that so many times.
Click to expand...
Click to collapse
My fault ...I see where you adressed that in the last part of your post. I'm no expert either on how recoveries are stored and executed.
I would think though that flashing stock mdk would fix this as it did for me. I used ROM manager to install cwm then I flashed Philz and haven't had a problem since. Hope someone else can help you.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
My fault ...I see where you adressed that in the last part of your post. I'm no expert either on how recoveries are stored and executed.
I would think though that flashing stock mdk would fix this as it did for me. I used ROM manager to install cwm then I flashed Philz and haven't had a problem since. Hope someone else can help you.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
cbmggm said:
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Yea that's what I said before too but the op said they've done that many times with no luck...
Sent from my SCH-I545 using Tapatalk
cbmggm said:
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
That's what I would have figured would fix it, because I'm pretty sure that's supposed to wipe /boot, but I found out I cannot flash kernels on my phone for some reason and when having to fix softbricks while experimenting with why it doesn't work and flashing different kernels, I had to do that whole process so many times I can go from softbrick back to where I'm at now in about 20 minutes.
Is your device in factory mode when using touchwiz roms?
jamesd1085 said:
Is your device in factory mode when using touchwiz roms?
Click to expand...
Click to collapse
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Markstache said:
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Click to expand...
Click to collapse
OK...well try something real quick for me...use a root manager and open your efs folder...are the files still there...if not your efs folder has been formatted to the incorrect format... That would explain funky recovery issues and not being able to flash kernels...that's the only things I can think of
jamesd1085 said:
OK...well try something real quick for me...use a root manager and open your efs folder...are the files still there...if not your efs folder has been formatted to the incorrect format... That would explain funky recovery issues and not being able to flash kernels...that's the only things I can think of
Click to expand...
Click to collapse
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Markstache said:
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Click to expand...
Click to collapse
Definitely don't delete your efs folder. Actually it's good practice to back it up
Sent from my SCH-I545 using Tapatalk
Markstache said:
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Click to expand...
Click to collapse
No!!!!...you will lose your number and all data capability...just wanted to make sure everything was still mounting properly... I'm at a loss as to what else could be causing your issues
Markstache said:
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Click to expand...
Click to collapse
I'd find someone like Philz or a TWRP compiler to ask if u haven't already gone that route. I'm sure one of them will know. Hopefully [emoji41]
Sent from my SCH-I545 using Tapatalk
Something just occured to me. When flashing back to stock with odin I always use the nowipe image because it's all I can find. I think that technically means boot was never wiped. Would that explain my phenomena? Also where to find stock that will wipe?
Markstache said:
Something just occured to me. When flashing back to stock with odin I always use the nowipe image because it's all I can find. I think that technically means boot was never wiped. Would that explain my phenomena? Also where to find stock that will wipe?
Click to expand...
Click to collapse
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
^^^this should fix you up...but backup everything you can to external SD or computer...when it says full wipe its no joke
Mistertac said:
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
So I flashed that one via Odin, followed the guide to root and everything step by step, and now that I'm back on stock kernel and want to install CWM Recovery, I downloaded Rom Manager and hit install recovery and it says everything worked but if I boot into recovery it's just the android stock recovery.
EDIT: Another thing I thought of. Could the fact that at one point I used this method to install CWM recovery on my phone have caused there to be two different recoveries running parallel?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
UPDATE: Using this method I installed the latest version of CWM Recovery Touch but Rom Manager still thinks the normal version is installed, though now if I hit reboot to recovery from the app it actually takes me to the touch instead of a separate one. Is the app dumb or do I still have an issue? Also I cannot install kernels without tripping the count and having my phone tell me I need to go to a verizon store.
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
Markstache said:
So I flashed that one via Odin, followed the guide to root and everything step by step, and now that I'm back on stock kernel and want to install CWM Recovery, I downloaded Rom Manager and hit install recovery and it says everything worked but if I boot into recovery it's just the android stock recovery.
EDIT: Another thing I thought of. Could the fact that at one point I used this method to install CWM recovery on my phone have caused there to be two different recoveries running parallel?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
UPDATE: Using this method I installed the latest version of CWM Recovery Touch but Rom Manager still thinks the normal version is installed, though now if I hit reboot to recovery from the app it actually takes me to the touch instead of a separate one. Is the app dumb or do I still have an issue? Also I cannot install kernels without tripping the count and having my phone tell me I need to go to a verizon store.
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
Click to expand...
Click to collapse
ROM manager may actually be the issue.
And as far as installing kennels I've never had an issue myself. The last link you posted is about flashing the md2 kernel in order to root the phone. Do you mean that?? Or installing say a KToonsez kernel after you're already rooted and have your custom recovery?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
ROM manager may actually be the issue.
And as far as installing kennels I've never had an issue myself. The last link you posted is about flashing the md2 kernel in order to root the phone. Do you mean that?? Or installing say a KToonsez kernel after you're already rooted and have your custom recovery?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
As in installing a KT kernel after rooting and having a custom recovery and ROM on my phone. Right now I have three 3/22 nightly cyanogen up and running but as soon as I install kt it trips the Verizon security and on have to flash back to stock kernel to use my phone. Booting into Odin and canceling out to restart does not let me get past the yellow triangle