I have been trying to update my S4 (vruame7) to the latest. I'm willing to lose root. The issue I'm having though is one that NOBODY seems to have mentioned anywhere: It started where I couldn't update over the air as the update fails. So I tried to update it with Kies on my mac but the program says I need more memory on my phone even though I already have it. This prompted me to unroot my phone and do the update again, but the issue is still there. So I tried booting into recovery and that worked. I decided then to reboot my phone and add CWM touch via ROM toolbox Pro. It said it worked fine, but now I cannot boot into the recovery mode. It just goes straight into ODIN mode and it won't prompt me to confirm it or not. I get into a very soft boot loop if I try and reboot though Rom Toolbox Pro to go into the recovery. I will land in ODIN and then unless I tell the phone manually to go into ODIN and then NOT proceed than it will be in a soft boot loop. So far I've tried unrooting and using Kies, Rooting and trying to load CWM onto my phone and failing, causing OTA to not be able to even start installing, and I've yet tried to go into safe mode and try to reset my phone that way. I might have to do that. if anyone has any other ideas I am open to that.
Your on me7 so you half to use safestrap that's the on way you can have a recover...... You probably half to Odin your phone back to me7 for the update to work. You can't use cwm or twrp on me7, unless u have safetrap installed and the its a version of twrp in it
hyperdrive powered s4
ebsk8er06 said:
Your on me7 so you half to use safestrap that's the on way you can have a recover...... You probably half to Odin your phone back to me7 for the update to work. You can't use cwm or twrp on me7, unless u have safetrap installed and the its a version of twrp in it
hyperdrive powered s4
Click to expand...
Click to collapse
Thanks. I've got safestrap installed sucessfully (it was so easy), and I'm now trying to install the update by wiping my phone and then doing it. I'll see if that works.
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
beez1717 said:
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
Click to expand...
Click to collapse
Heimdall is like odin but its mac.compatible
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Use oden or Heimdall (guess its a Mac thing) to flash back to stock and then you can take the update. You haven't bricked yet but it sounds like you are getting close so be careful.
beez1717 said:
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
Click to expand...
Click to collapse
Sounds like you did a full wipe on non safe side "stock rom" of safestrap so your gonna have to flash a whole factory image cause it all gone the whole os
So after working for hoursx and hours, of working at it, I finally found http://sonofgeektalk.wordpress.com/2013/06/13/heimdall-on-a-mac/ <-- that webpage and it helped walk me through using Helmdall and it worked after much fiddling and discovering that I had to plug in my phone AFTER it got into odin but BEFORE I confirmed I wanted to be in odin. I then had to not wipe the phone clean but just do the install with the right files. It worked and I'm so happy. Now to see if I can update the darn phone. Don't know if I can or not but hey, I've got my phone back up and running and that's a GOOD thing.
I don't care about root as much as I care about getting the latest software if it provides enhancements I like, or security features I want. I think that root is fun, but it can be a pain in the butt as I just saw. Now that I know how to do the whole shtick, I should be able to do a lot more with my phone. I remember when I had to learn the ins and outs of my old Xperia Play. Horrible battery life and sub-par graphics chip but an awesome phone that had an awesome utility that could do just about anything with the phone with minimal work.
Looks like the system is updating itself just fine using OTA. What a LONG workaround I had to do. Thank you all for helping me teach myself a lot more about my phone
I'm having trouble trying to update as well. I unrooted and did a factory reset but the update still fails. What should I be trying?
Sent from my SCH-I545 using xda app-developers app
beez1717 said:
So after working for hoursx and hours, of working at it, I finally found http://sonofgeektalk.wordpress.com/2013/06/13/heimdall-on-a-mac/ <-- that webpage and it helped walk me through using Helmdall and it worked after much fiddling and discovering that I had to plug in my phone AFTER it got into odin but BEFORE I confirmed I wanted to be in odin. I then had to not wipe the phone clean but just do the install with the right files. It worked and I'm so happy. Now to see if I can update the darn phone. Don't know if I can or not but hey, I've got my phone back up and running and that's a GOOD thing.
I don't care about root as much as I care about getting the latest software if it provides enhancements I like, or security features I want. I think that root is fun, but it can be a pain in the butt as I just saw. Now that I know how to do the whole shtick, I should be able to do a lot more with my phone. I remember when I had to learn the ins and outs of my old Xperia Play. Horrible battery life and sub-par graphics chip but an awesome phone that had an awesome utility that could do just about anything with the phone with minimal work.
Click to expand...
Click to collapse
I think the problem here was that you tried to take an official update AFTER you messed with your phone... you should take this as a lesson to always flash back to stock before trying any 'official' updates, or better yet just have some patience for the updated files to show up here on the forums so you don't have to deal with OTAs at all. I don't really see the big rush to get the newest MI1 update anyway, it really doesn't provide any huge benefits at all and plus will possibly void your warranty through that stupid Knox thing if you try to root.
One thing I've learned is use patients dont jump the gun and if your not sure before you do something look here cause someone has already screwed up so the right way will be here somewhere and video will be on youtube!!
Related
I got the S4 back when it first came out, and messed around with some CM ROMs and other custom ROMs that worked fairly well. The big killers for me though were bluetooth audio not working, not being able to use headphone microphones, and the proximity sensor being all weird. So I reverted to stock but kept root, and eventually upgraded to MJ7 while keeping root. When I boot I still get the 'Samsung Custom' bootscreen.
I've never been happy with Touchwiz, and have all of the Samsung features turned off. The stock messaging app is really the thing that bugs the hell out of me, since it takes forever to get messages (sometimes up to an hour, while Handcent will get them right away), and I love my Nexus 7 experience. I'd really like to get as close to a 'Google' phone as possible, but I'm currently stuck on Verizon.
I've tried using GooManager to download the recovery managers again, but it's having problems with 404 errors downloading the scripts. I tried ROM Manager and it says it installs ClockworkMod (6.0.44 in fact), but it refuses to boot into recovery mode. Most of the tools I'm finding are not for MJ7, so I'm kind of hesitant to solutions that aren't for my current version. Since I can't make any backups without being able to boot into a proper recovery mode, that's another kind of notch against using most of the guides.
I don't mind the actual process of doing the work, I'm just not sure where to go from here. What are my options?
dragonmantank said:
I got the S4 back when it first came out, and messed around with some CM ROMs and other custom ROMs that worked fairly well. The big killers for me though were bluetooth audio not working, not being able to use headphone microphones, and the proximity sensor being all weird. So I reverted to stock but kept root, and eventually upgraded to MJ7 while keeping root. When I boot I still get the 'Samsung Custom' bootscreen.
I've never been happy with Touchwiz, and have all of the Samsung features turned off. The stock messaging app is really the thing that bugs the hell out of me, since it takes forever to get messages (sometimes up to an hour, while Handcent will get them right away), and I love my Nexus 7 experience. I'd really like to get as close to a 'Google' phone as possible, but I'm currently stuck on Verizon.
I've tried using GooManager to download the recovery managers again, but it's having problems with 404 errors downloading the scripts. I tried ROM Manager and it says it installs ClockworkMod (6.0.44 in fact), but it refuses to boot into recovery mode. Most of the tools I'm finding are not for MJ7, so I'm kind of hesitant to solutions that aren't for my current version. Since I can't make any backups without being able to boot into a proper recovery mode, that's another kind of notch against using most of the guides.
I don't mind the actual process of doing the work, I'm just not sure where to go from here. What are my options?
Click to expand...
Click to collapse
Well unfortunately for you you're on MJ7 which means your only options right now are rooting and Xposed. Other than that though, there's really nothing else you can do at the moment. If you were on ME7 or MI1 still you could at least run Safestrap, but even then you would be limited to Touchwiz based roms. Unless you're willing to go on the hunt for an MDK S4 you'll just have to deal with your limited options for now. Oh and before you ask, there is absolutely no way to revert back to earlier firmwares. Once you update, you're stuck.
Crawshayi said:
Well unfortunately for you you're on MJ7 which means your only options right now are rooting and Xposed. Other than that though, there's really nothing else you can do at the moment. If you were on ME7 or MI1 still you could at least run Safestrap, but even then you would be limited to Touchwiz based roms. Unless you're willing to go on the hunt for an MDK S4 you'll just have to deal with your limited options for now. Oh and before you ask, there is absolutely no way to revert back to earlier firmwares. Once you update, you're stuck.
Click to expand...
Click to collapse
Yeah, I know I couldn't revert the firmware to something earlier. Is it possible to revert to stock even? At this point I think I just want to revert it and sell this phone off and get something else. I don't care about KNOX status, just getting it back to stock so that whomever buys it won't keep getting security notifications.
dragonmantank said:
Yeah, I know I couldn't revert the firmware to something earlier. Is it possible to revert to stock even? At this point I think I just want to revert it and sell this phone off and get something else. I don't care about KNOX status, just getting it back to stock so that whomever buys it won't keep getting security notifications.
Click to expand...
Click to collapse
Yes I believe it's possible, I found this thread that gives you an Odin image to flash: http://forum.xda-developers.com/showthread.php?t=2507217
The security notification was actually fixed and supposedly an update was pushed out, but maybe yours didn't grab the update properly? I'm not sure, but that Odin image should get you back to factory stock. If I were you I would get an HTC One if you can live with not having a removable battery and sd card.
Awesome, thank you very much.
I'm re-flashing today take it back. I'll have a look at the HTC One, since it wasn't out when I got my S4. I know that (at the time) the S4 was the only Android phone I had found, with the One a close second but not available. I would really love a Google phone, but I get the feeling that will probably never happen on VZW.
Hey guys, has anyone had this issue where your camera refuses to focus on anything further away than say about 6 inches? It can focus just fine close up, but beyond that it's garbage. It goes through the 'animation' of focusing, turns red like i can't focus, and doesn't actually adjust the focus at all. It started in about October and has persisted through 3 or 4 ROMs and various camera APKs.
Has anyone replaced their camera before? I doubt verizon would trade me for a new phone seeing as I've rooted it and flashed a lot of ROMs on it. What should I do? What have you done if this has happened to you? This thread outlines exactly the same thing I'm experiencing and seems as they've concluded it's hardware failure.
Thoughts?
Bump in hopes of someone's experience or advice.
falkon114 said:
Hey guys, has anyone had this issue where your camera refuses to focus on anything further away than say about 6 inches? It can focus just fine close up, but beyond that it's garbage. It goes through the 'animation' of focusing, turns red like i can't focus, and doesn't actually adjust the focus at all. It started in about October and has persisted through 3 or 4 ROMs and various camera APKs.
Has anyone replaced their camera before? I doubt verizon would trade me for a new phone seeing as I've rooted it and flashed a lot of ROMs on it. What should I do? What have you done if this has happened to you? This thread outlines exactly the same thing I'm experiencing and seems as they've concluded it's hardware failure.
Thoughts?
Click to expand...
Click to collapse
I think you're right on the hardware issue. You could always use ODIN to restore the phone back to stock and turn it in for replacement. Verizon can't tell the difference as long as you restore it with the proper factory image. Bad thing is, replacement will probably come locked down with the currently unlockable 4.3 bootloader. At the very least you can restore it with ODIN just to see if it helps the focus issue.
*see below*
Jiggabitties said:
I think you're right on the hardware issue. You could always use ODIN to restore the phone back to stock and turn it in for replacement. Verizon can't tell the difference as long as you restore it with the proper factory image. Bad thing is, replacement will probably come locked down with the currently unlockable 4.3 bootloader. At the very least you can restore it with ODIN just to see if it helps the focus issue.
Click to expand...
Click to collapse
Yeah, i think I might try going back to stock. I wanted to a little while ago just to remember what it was like having a stock system, but I can't find all the files I need. Wasn't there a sticky with Odin and all the right files in one thread? Thought it was stickied, but either I'm blind, or I'm not finding it.
Edit:
Nvm, I'm an idiot
falkon114 said:
Yeah, i think I might try going back to stock. I wanted to a little while ago just to remember what it was like having a stock system, but I can't find all the files I need. Wasn't there a sticky with Odin and all the right files in one thread? Thought it was stickied, but either I'm blind, or I'm not finding it.
Edit:
Nvm, I'm an idiot
Click to expand...
Click to collapse
Yeah sometimes I go back to stock for a day or two just to remind myself why crack flashing is so worth it. But sometimes it's just needed to iron out some bugs. I was having radio issues not too long ago, tried different roms and radios and couldn't fix it. Flashed back to stock, worked like a charm. Haven't had an issue since.
Jiggabitties said:
Yeah sometimes I go back to stock for a day or two just to remind myself why crack flashing is so worth it. But sometimes it's just needed to iron out some bugs. I was having radio issues not too long ago, tried different roms and radios and couldn't fix it. Flashed back to stock, worked like a charm. Haven't had an issue since.
Click to expand...
Click to collapse
Alright, so I remember having some problems when I was first rooting/modifying/Custom recovery-ing...
Couple questions.
1. I use TWRP as my recovery of choice. Can I backup my current ROM as is and store it through there like I normally would when going to a new ROM in case I want to after I go back to stock? Or will going back to stock completely erase all saved ROM images?
If I go back to stock, can I boot into TWRP again like I do now, or is there some process I'll need to follow again to be able to flash my current ROM image? Should I flash the Root66 stock VRALJB 4.1.1 (12/2/12) in the previously linked thread so I can still use custom recovery?
What else should I know? I've become quite good and confident in flashing ROMs, but I'm nervous going back to stock since it seems easier to brick it/lock it down. I remember when I first downloaded and tried installing TWRP, it showed that infamous Yellow Triangle saying the device found unauthorized software and to take it to Verizon, and I remember spending hours trying to flash things to get past that, I don't want to have to deal with that again.
falkon114 said:
Alright, so I remember having some problems when I was first rooting/modifying/Custom recovery-ing...
Couple questions.
1. I use TWRP as my recovery of choice. Can I backup my current ROM as is and store it through there like I normally would when going to a new ROM in case I want to after I go back to stock? Or will going back to stock completely erase all saved ROM images?
If I go back to stock, can I boot into TWRP again like I do now, or is there some process I'll need to follow again to be able to flash my current ROM image? Should I flash the Root66 stock VRALJB 4.1.1 (12/2/12) in the previously linked thread so I can still use custom recovery?
What else should I know? I've become quite good and confident in flashing ROMs, but I'm nervous going back to stock since it seems easier to brick it/lock it down. I remember when I first downloaded and tried installing TWRP, it showed that infamous Yellow Triangle saying the device found unauthorized software and to take it to Verizon, and I remember spending hours trying to flash things to get past that, I don't want to have to deal with that again.
Click to expand...
Click to collapse
Yes, backup your current ROM, if you use the root66 Odin image it should not erase anything you have stored. But to be safe, I would copy your TWRP backup to either an external SD or to your computer for safe keeping. TWRP should survive, as long as you use root66, the others will overwrite recovery and lock the bootloader.
The only reason you should ever get the "Yellow Triangle", or trip any sort of security is if you attempt to install a custom recovery or ROM while the bootloader remains locked, or, you attempted to install the recovery via ODIN.
The most important thing here is, whatever you do, under any circumstance, DO NOT accept any OTA updates. As long as you don't accept the 4.3 OTA, you should be able to keep your TWRP.
You may want to try this flashable version of the stock VRAMC3 before you resort to ODIN http://forum.xda-developers.com/showthread.php?t=2261478
Jiggabitties said:
Yes, backup your current ROM, if you use the root66 Odin image it should not erase anything you have stored. But to be safe, I would copy your TWRP backup to either an external SD or to your computer for safe keeping. TWRP should survive, as long as you use root66, the others will overwrite recovery and lock the bootloader.
The only reason you should ever get the "Yellow Triangle", or trip any sort of security is if you attempt to install a custom recovery or ROM while the bootloader remains locked, or, you attempted to install the recovery via ODIN.
The most important thing here is, whatever you do, under any circumstance, DO NOT accept any OTA updates. As long as you don't accept the 4.3 OTA, you should be able to keep your TWRP.
You may want to try this flashable version of the stock VRAMC3 before you resort to ODIN http://forum.xda-developers.com/showthread.php?t=2261478
Click to expand...
Click to collapse
Thanks. I tried the last link there, and am back to relatively stock and still have the camera issue.
I'm excited for the 4.3 update to be hacked since I would really, really like multi-window and SNote capabilities on my 4.3 ROM, but who knows when that might happen.
Thanks for you help man!
falkon114 said:
Thanks. I tried the last link there, and am back to relatively stock and still have the camera issue.
I'm excited for the 4.3 update to be hacked since I would really, really like multi-window and SNote capabilities on my 4.3 ROM, but who knows when that might happen.
Thanks for you help man!
Click to expand...
Click to collapse
Glad I could help in any way. Bummer about your camera.
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
FranklinPIerce said:
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
Click to expand...
Click to collapse
The ROM may not have Loki support...if you are using the older twrp version it may not auto lokify the ROM...try updating your recovery and give it another go
FranklinPIerce said:
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
Click to expand...
Click to collapse
I would recommend trying out Philz ( cwm ) recovery possibly. There have been random issues like yours reported and usually updating the recovery or just trying a different ROM all together gets better results.
You shouldn't need to go back to stock mdk for anything since you're already rooted and have a custom recovery.
Sent from my SCH-I545 using Tapatalk
Thanks for the suggestions. I did update my recovery, but now that I think of it, I may not have tried to re-flash since upgrading. My preference is to not use CWM, but I will if I have to, I guess.
In either case, I'll try this all out when I get home from work and post back. Thanks for the suggestions.
FranklinPIerce said:
Thanks for the suggestions. I did update my recovery, but now that I think of it, I may not have tried to re-flash since upgrading. My preference is to not use CWM, but I will if I have to, I guess.
In either case, I'll try this all out when I get home from work and post back. Thanks for the suggestions.
Click to expand...
Click to collapse
Let me suggest trying liquid smooth 4.4
Awesome ROM to try.
Sent from my SCH-I545 using Tapatalk
FranklinPIerce said:
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
Click to expand...
Click to collapse
I would try their suggestions. For future reference though, you can use heimdall instead of Odin on Linux. I love it I think its better than odin
Sent from my unknown using Tapatalk
Ok, so I updated TWRP to the latest and tried again. Got the same message as before about unauthorized software and in the upper left, it said something about "Fail: Kernal"
From there, I had a hard time getting back into recovery. It would either say it was booting into recovery and then shut off or it would freeze. I eventually got back in and am restoring now.
Thanks for the information on Heimdall - I wasn't aware of it. The reason I wanted to go with Carbon is that it has a built-in application to control/override application permissions. Does something like that exist for LiquidRom? Or is it compatible with PDroid or something similar? (I didn't see a mention of it in their features, but might have missed it)
One more thought: I am using the Carbon nightlies for KK. Maybe there's a problem with the source file (I've redownloaded 4 times)? Or maybe I'm just destined to be on stock forever. :crying:
Edit: I just tried putting Philz recovery on and now I can't get into recovery as that's now giving the same unauthorized software message.
Edit2: I was able to get TWRP on eventually by going into Odin mode and hitting "Cancel." Each normal reboot would then give the same unauthorized message, so I just went back to TWRP and it's booting normally again. Ah, yay to Verizon and their locked phones.
Ok, I've tried a few more times tonight with no luck, so I'll give it a break for now and look into it more tomorrow or over the weekend.
FranklinPIerce said:
Ok, so I updated TWRP to the latest and tried again. Got the same message as before about unauthorized software and in the upper left, it said something about "Fail: Kernal"
From there, I had a hard time getting back into recovery. It would either say it was booting into recovery and then shut off or it would freeze. I eventually got back in and am restoring now.
Thanks for the information on Heimdall - I wasn't aware of it. The reason I wanted to go with Carbon is that it has a built-in application to control/override application permissions. Does something like that exist for LiquidRom? Or is it compatible with PDroid or something similar? (I didn't see a mention of it in their features, but might have missed it)
One more thought: I am using the Carbon nightlies for KK. Maybe there's a problem with the source file (I've redownloaded 4 times)? Or maybe I'm just destined to be on stock forever. :crying:
Edit: I just tried putting Philz recovery on and now I can't get into recovery as that's now giving the same unauthorized software message.
Edit2: I was able to get TWRP on eventually by going into Odin mode and hitting "Cancel." Each normal reboot would then give the same unauthorized message, so I just went back to TWRP and it's booting normally again. Ah, yay to Verizon and their locked phones.
Ok, I've tried a few more times tonight with no luck, so I'll give it a break for now and look into it more tomorrow or over the weekend.
Click to expand...
Click to collapse
That's odd that flashing Philz didn't work for you. Its a pain I know but probably if you had wiped the phone with stock mdk then tried again it woukd have worked I bet. I had to do that with this phone when i got it. It came with twrp, but was acting real funny not always getting into recovery or just hanging up on reboot. But you have a working twrp so that's good too.
I don't believe liquid has the built in app permissions you're talking about but maybe I missed it. I don't really mess with permissions. Liquid has everything else though and then some!
I know some Roms were having problems with unified builds. I know liquid does not at this point. Maybe it'd be worth trying just so you're not on stock lol you may want to look into the Loki doki zip that you flash after flashing the ROM. I've seen some people on here using that when they were getting the same error you were. Just an idea.
Good luck man!
Sent from my SCH-I545 using Tapatalk
Hi,
I got a new phone last month, a HTC One (M8). Since I didn't need my S2 anymore, I decided to experiment a little bit with it, witch mean, I decided to try and root it. Man, i should never have done that.
First, I followed a guide on wikihow on how to root it. I downloaded Odin and the jeboo kernel they recommended in the guide. A couple minutes later, when everything was done, I tried to reboot my phone without much success. It was stuck on "Samsung Galaxy SII" with the yellow exclamation mark. Did I say that I got my phone from Virgin Mobile in Canada? Anyway, I tried to find a way to make my phone functional again and a couple of hours later, I found a stock Kernel that I immediately flash on my phone using Odin.
Everything worked fine again but I didn't want that outdated Android 2.2 so I installed Kies and plugged my phone in my computer to install the latest update from Samsung. Once again, I couldn't boot my phone, it would loop the Samsung animation over and over. So I re-install Gingerbread using Odin. Everything worked fine again!
But as I am stubborn, I didn't want it! So I search the web again for a solution. I red that cyanogen mod was great and I immediately wanted to try it. So I install everything and since it had an auto installer, I thought it would be very easy and in no time I would be able to play with it. Never have I been so wrong. For a reason that I don't know, the installer wasn't able to speak with my phone even thought I tried everything they said to do in this case.
Now, I can't boot my phone but I can boot in download and recovery mode. The only problem is, my computer doesn't install the drivers when I connect my phone, so I can't re-install 2.2 using Odin.
Anyone have any idea what I should do to solve this issue?
Please, help me 'cause I ****ed up
(Sorry for the mistakes, english is not my native language)
You did not screw anything.
If you can go to recovery, just boot into it, download any ROM you want and flash it through recovery(wipe data/cache/dalvik before you flash) and you'll be fine.
Second thing, once you root your phone, you void your warranty, and you CAN NOT update your phone from official samsung updates.You can do that if you unroot, but you won't need any updates.
Any way, as long as you can get into recovery, you're fine.
Also, what specific model; sticker on phone chassis under the battery ?
Nightshadow931 said:
You did not screw anything.
If you can go to recovery, just boot into it, download any ROM you want and flash it through recovery(wipe data/cache/dalvik before you flash) and you'll be fine.
Second thing, once you root your phone, you void your warranty, and you CAN NOT update your phone from official samsung updates.You can do that if you unroot, but you won't need any updates.
Any way, as long as you can get into recovery, you're fine.
Click to expand...
Click to collapse
Thanks mate, I will try this as soon as I can!
MistahBungle said:
Also, what specific model; sticker on phone chassis under the battery ?
Click to expand...
Click to collapse
It is a GT-I9100M.
Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Psychotic-Cerebellum said:
Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Click to expand...
Click to collapse
OK, from your post it looks like you have done this before. To be sure lets go through the motions one more time.
Your device is updated to 4.4.4 NK4 the latest KitKat version. It's rooted you have supersu icon and run a root checker. First download again ( in case you got a bad download ) a copy of Philz CWM version 6.48.4 here is the link https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hlte/ use "phil'z_touch_6.48.6-hlte.tar.md5" . I like to use odin version v1.85 it's little older but very stable, here is a link https://mega.co.nz/#!oA5xzTAL!LXoVWB...ZlOMSWdRGVX6Uo now flash the .tar file with odin. Make sure you let device boot up on it's own back to the OS, do not pull the cable and boot the device yourself. Then try and boot into recovery.
If it bootloops again, I would backup all your data to the PC desktop, and then do a factory reset get back to bone stock ( that means when your in download mode it says Samsung Official status not custom ) so many times I have seen folks with an unrooted device where the bootloader still says custom and you end up with a dirty flash or worse. It may take a couple factory resets to get back to stock, it doesn't always take the first time. When I flash a custom rom and then decide to go back to stock, I flash the rom two or three times to make sure I'm bone stock.
If the factory reset doesn't work you may have to flash a new stock NK4 OS. Then root again and install the recovery. Here is my thread with all the info you need http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 , Enjoy !!!
Thanks for taking the time to give me a detailed response. Sounds like I'm gonna have to wait till Wednesday or Thursday when im off work and have some time to do this, but yeah, I was thinking maybe just a factory reset, but I'll use your links and try it one more time first. I'll let ya know. Thanks again
Do you have another link to the older Odin (1.85).the link says the file isn't there... Thanks again
Never got to test it out, but she didn't really want a custom rom anyway, just the WiFi hotspot, and I finally found a method that works, big shout out to idone for his awesome app. If anyone else is looking for WiFi hotspot without root that sees this, check out his tread in the apps and themes, for this phone. Worked like a charm. Thanks again jimzweb1. Much appreciate the reply!
Psychotic-Cerebellum said:
Never got to test it out, but she didn't really want a custom rom anyway, just the WiFi hotspot, and I finally found a method that works, big shout out to idone for his awesome app. If anyone else is looking for WiFi hotspot without root that sees this, check out his tread in the apps and themes, for this phone. Worked like a charm. Thanks again jimzweb1. Much appreciate the reply!
Click to expand...
Click to collapse
Awesome, Ya idone is the man when it comes to enabling the mobile hotspot be careful what you click with app. I will correct that link. Thanks
Psychotic-Cerebellum said:
Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Click to expand...
Click to collapse
That's the problem Knox security is getting harder flash engineering boot loader again then try rashr in app store to flash philz