New to this - I really apologize if this has been covered before but I've been searching all evening and not coming up with a definitive answer.
What's the easiest way to remove a custom recovery (like twrp) and go back to stock? Still on the stock rom, just have custom recovery. I manually deleted a nandroid backup using a file manager from my sd card yesterday, and now when booting into recovery it sits on the twrp screen for easily 10-15 minutes. I can't fathom why that would have an effect on the start up time but that's all I can think of that changed. I've tried re-installing twrp via goomanager - no change.
Is there a way to do so without using usb? I'm curious because the first S4 I had, the usb port went bad after only a month and I was in a panic that I wouldn't be able to get it back to stock (until I finally got it to work long enough to flash it with odin). Really don't want to risk that happening again.
Looking to run some roms once I think I understand at least half of what I'm doing, but trying to be cautious. I'd like to keep twrp but I want to make sure it's working right by loading a clean install of it.
Thanks in advance.
A lot of users are experiencing the lag with TWRP version installed by Goo Manager - (TWRP 2.6.0).
The link below has a flashable zip to version 2.5.0.2, this version seems to be stable and doesn't lag at the TWRP screen for most people including myself.
I would try flashing this and I think it will solve your problem.
http://forum.xda-developers.com/showpost.php?p=45006486&postcount=289
gadget! said:
A lot of users are experiencing the lag with TWRP version installed by Goo Manager - (TWRP 2.6.0).
The link below has a flashable zip to version 2.5.0.2, this version seems to be stable and doesn't lag at the TWRP screen for most people including myself.
I would try flashing this and I think it will solve your problem.
http://forum.xda-developers.com/showpost.php?p=45006486&postcount=289
Click to expand...
Click to collapse
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
bretbretterson said:
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
Click to expand...
Click to collapse
You flash it via recovery. Put in your sdcard/internal boot to recovery amd use the install zip option. Navigate to where it is and flash away.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
bretbretterson said:
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
Click to expand...
Click to collapse
Yes, it is a flashable zip, just flash it in the recovery you have now.
I found this post based on the OP's original question, "how to remove TWRP recovery".
I have been flashing rooted ROMs for a while now via ODIN, but am just now starting to foray into the realm of custom recoveries. Before I install TWRP though, I wanted to know how to remove it just in case something ever goes wrong. That is, I've been avoiding the use of a custom recovery so far because if something ever happened to my device, I could just flash the stock ROM, and having already used Triangle Away, Samsung will never be the wiser and would service my device, but with a custom recovery installed, they would be able to see I'm not running totally stock.
So, is there a way to completely return my device to 100% stock after installing TWRP? And if so, how would I go about doing that?
My device is a Samsung Galaxy Note 10.1 GT-N8013, currently running a root injected stock ROM, 4.1.2
EDIT: I just noticed that this is in the S4 forum, which my N8013 obviously is not, but the answer to my question should be the same regardless, yes?
margentieri said:
I found this post based on the OP's original question, "how to remove TWRP recovery".
I have been flashing rooted ROMs for a while now via ODIN, but am just now starting to foray into the realm of custom recoveries. Before I install TWRP though, I wanted to know how to remove it just in case something ever goes wrong. That is, I've been avoiding the use of a custom recovery so far because if something ever happened to my device, I could just flash the stock ROM, and having already used Triangle Away, Samsung will never be the wiser and would service my device, but with a custom recovery installed, they would be able to see I'm not running totally stock.
So, is there a way to completely return my device to 100% stock after installing TWRP? And if so, how would I go about doing that?
My device is a Samsung Galaxy Note 10.1 GT-N8013, currently running a root injected stock ROM, 4.1.2
EDIT: I just noticed that this is in the S4 forum, which my N8013 obviously is not, but the answer to my question should be the same regardless, yes?
Click to expand...
Click to collapse
Answer would be device specific
Sent from my cm_tenderloin using xda app-developers app
Thanks Gadget, Hex. TWRP 2.5.0.2 works great. But just for future reference, is the only way to revert to the stock recovery by flashing a stock device image via odin over usb? So if the USB port were to fail entirely, I would be SoL - correct?
Related
This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
lucash312 said:
This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
rom manager is useless for the fascinate...
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
MultipleMonomials said:
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
Click to expand...
Click to collapse
if the op would of followed the guides instructions correctly, he would not of ran into that issue in the first place...
droidstyle said:
rom manager is useless for the fascinate...
Click to expand...
Click to collapse
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
You can flash any .zip ROM with CWM. There's no need for ROM Manager. BTW, you can post a link if you uncheck "parse links in text automatically."
Nymblz said:
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
Click to expand...
Click to collapse
all you need to do is boot into cwm recovery via the power menu and flash away. the problem with rom manager on the fascinate is getting into the right recovery...causes more problems than its worth on this device. make sense yet? probably not since you have not been down this road yet, but many of us have. so take the advice given or dont and learn the hard way.
Honestly, I am trying to take the advice given but not all of it fit my situation.
I'm definitely something of a noob to Android (Not to linux or IT though). I've had my phone for all of a month and rooted it only days ago.
It's all starting to come together, finally. It's tricky for a noob because there are so many different versions of the phone hardware, versions of Android, this or that kernel that only works with these ROMs, old/newer versions of those, old posts and advice, newer posts with adjusted advice.. etc.. It's been a week long crash course!
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
So you see, I was in a catch-22; I needed CWM to flash CWM? Odin was my only option at that point.
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Nymblz said:
It's tricky for a noob because there are so many different versions of the phone hardware
Click to expand...
Click to collapse
You are on the Samsung Fascinate. If it is Verizon then it is model number i500. If it doesnt say Fascinate or i500 it isn't for your device and you don't need to worry about it. If you flash something that isn't stated as being for the i500 or VERIZON Fascinate then you will have a lovely new temporary paper weight.
Nymblz said:
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
Click to expand...
Click to collapse
You couldn't have followed it to the letter because it is a well known fact that if you boot up with a stock kernel still flashed it will replace your recovery. Droidstyle certainly knows this and certainly accounted for it in his guide. So, you need to either boot directly into CWM or flash a non-stock kernel prior to rebooting the phone.
Nymblz said:
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Click to expand...
Click to collapse
Yeah it sounds like that will work...not the most elegant way to take care of it...but it sounds like it would be okay.
Nymblz said:
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
Click to expand...
Click to collapse
We already talked about the kernel situation. Consider Geewiz if you want something thats all-in-one and pretty much impossible to mess up. KGB is good. Leankernel always gave me the best battery life but YMMV.
Nymblz said:
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Click to expand...
Click to collapse
He showed no interest in helping the devs here get ROM manager working (again) on the phone. If you gave him money, blame him for not providing the support and resources to get it working on this phone. Some people are umm...."lacking in people skills."
Oh, and as great as the Gingerbread ROMs are...the mtd ICS roms blow them out of the water
Here's the deal:
I rooted my phone a long time ago, and have been using CM since ICS. Mostly nightlies.
A few weeks ago I decided installing a Carbon nightly (4.3), and everything went smooth as usual.
Then new nightly came, so I decided flashing it. (Dirty flash, but it's that way from what I read in the Carbon thread)
The thing is, my phone boots up correctly, but I can't get into recovery mode. Whenever I try booting recovery mode, the logo appears, then the screen flashes gray. I have tried both the advanced reboot menu, the button combo, and ROM Man...jk
I think something might be wrong with the recovery included in the kernel. If that's the case, would it be OK to flash just a new kernel or do I have to reflash the whole thing?
I have already seen some guides on flashing kernels with mobile ODIN, but they're either ancient or for another model. Also, I don't know if that's the right thing to do under this situation.
I'd appreciate if someone pointed me in the right direction. I don't wanna frak up my phone.
You can install a kernel to see if that will solve the issue, but as far as I can see, the Carbon devs do not provide a stand alone kernel for their rom. You could use AJK or one of the other kernels though. Or you could just reinstall the rom to see if it would clear up the problem.
Or, you could extract the zImage from the full rom and use Mobile Odin.
I didnt want to create a new thread for this and get yelled at.. so I am asking the question here:
I had to do the ODIN method and returned my phone from ShoStock 3 to Stock Gingerbread, because for some reason my phone was getting stuck at the "samsung galaxy s2" boot screen.
So I am back on Stock Gingerbreak Rom and trying to install ClockWork Mod Recovery, so that I can restore the backup of ShoStock that I had created.
I am doing the Mobile Odin Lite method and I downloaded the i777 kernel. When I try to install it, I boot in the Android System Recovery (3e) and get the following errors:
Installing package...
Finding Package...
Verifying Update Package...
E: failed to verify whole-file signature
E: signature verification failed.
Before I get yelled at, I searched google and came up with the solution -- all of which say that the issue can be easily fixed by toggling the setting in ClockWork Mod Recovery Mode, but I have to install it first, and whenever I try to install it, I get the above error.
Can someone help please?
jjack0310 said:
I didnt want to create a new thread for this and get yelled at.. so I am asking the question here:
I had to do the ODIN method and returned my phone from ShoStock 3 to Stock Gingerbread, because for some reason my phone was getting stuck at the "samsung galaxy s2" boot screen.
So I am back on Stock Gingerbreak Rom and trying to install ClockWork Mod Recovery, so that I can restore the backup of ShoStock that I had created.
I am doing the Mobile Odin Lite method and I downloaded the i777 kernel. When I try to install it, I boot in the Android System Recovery (3e) and get the following errors:
Installing package...
Finding Package...
Verifying Update Package...
E: failed to verify whole-file signature
E: signature verification failed.
Before I get yelled at, I searched google and came up with the solution -- all of which say that the issue can be easily fixed by toggling the setting in ClockWork Mod Recovery Mode, but I have to install it first, and whenever I try to install it, I get the above error.
Can someone help please?
Click to expand...
Click to collapse
3e recovery is the stock recovery. It means you have not installed a custom kernel yet. Please look at the links in my signature and use the guide information there, which will help you understand what you need to do to install mobile odin lite and then install a custom kernel.
Also, remember that you will need to have the correct version of ClockworkMod Recovery to restore your backup. If the backup and the version of CWM recovery are not compatible, it will not restore.
If you have questions, ask them here, but be aware, I only come on line usually two or three times a day to check the forums.
creepyncrawly said:
3e recovery is the stock recovery. It means you have not installed a custom kernel yet. Please look at the links in my signature and use the guide information there, which will help you understand what you need to do to install mobile odin lite and then install a custom kernel.
Also, remember that you will need to have the correct version of ClockworkMod Recovery to restore your backup. If the backup and the version of CWM recovery are not compatible, it will not restore.
If you have questions, ask them here, but be aware, I only come on line usually two or three times a day to check the forums.
Click to expand...
Click to collapse
I followed Step 3a on this post: http://forum.xda-developers.com/showthread.php?p=18576627#post18576627
Unfortunately, for some reason, ODIN Lite was not recognizing DD_03042012.zip file. So I went with Siyah and downloaded the TAR file used ODIN to get the clockwork mod. It worked.
Now the problem is I cant restore my backup. I know the same backup has worked before, not it is giving me an error "Error while restoring /system". wth!
I dont remember what version of Clockwork Mod I had. I know it was an older version, becuase it didnt have touch.
How do I get a previous version of CWM?
But my problem isn't even remotely similar to this guy!
I'm trying to ask if there's some way to flash a new kernel/rom without using recovery, taking advantage of the fact that my phone boots fine but I can't boot recovery. That's the reason why I mentioned ODIN.
Also, go make your own thread. My question didn't even get answered
Actually,
Creepyncrawly, thanks for your help.
I downloaded ShoStock 3 and flashed it to get the previous version of CWM, and then was able to do a restore.
Sigh.. no harm done.
You can have your thread back... good luck!!
Mighty_Rearranger said:
But my problem isn't even remotely similar to this guy!
I'm trying to ask if there's some way to flash a new kernel/rom without using recovery, taking advantage of the fact that my phone boots fine but I can't boot recovery. That's the reason why I mentioned ODIN.
Also, go make your own thread. My question didn't even get answered
Click to expand...
Click to collapse
Yes, as stated by creepyncrawly, u can use mobile odin or regular odin to flash a kernel.
But i would suggest doing a MD5 check on the Rom u downloaded, because the Rom u flashed may be that of a corrupted download. If MD5 doesn't match then redownload, check MD5 and if good, reflash the Rom.
.....or maybe the nightly is messed up.
Sent from my SAMSUNG-SGH-I747 using xda premium
Mighty_Rearranger said:
Here's the deal:
I rooted my phone a long time ago, and have been using CM since ICS. Mostly nightlies.
A few weeks ago I decided installing a Carbon nightly (4.3), and everything went smooth as usual.
Then new nightly came, so I decided flashing it. (Dirty flash, but it's that way from what I read in the Carbon thread)
The thing is, my phone boots up correctly, but I can't get into recovery mode. Whenever I try booting recovery mode, the logo appears, then the screen flashes gray. I have tried both the advanced reboot menu, the button combo, and ROM Man...jk
I think something might be wrong with the recovery included in the kernel. If that's the case, would it be OK to flash just a new kernel or do I have to reflash the whole thing?
I have already seen some guides on flashing kernels with mobile ODIN, but they're either ancient or for another model. Also, I don't know if that's the right thing to do under this situation.
I'd appreciate if someone pointed me in the right direction. I don't wanna frak up my phone.
Click to expand...
Click to collapse
Mighty_Rearranger said:
But my problem isn't even remotely similar to this guy!
I'm trying to ask if there's some way to flash a new kernel/rom without using recovery, taking advantage of the fact that my phone boots fine but I can't boot recovery. That's the reason why I mentioned ODIN.
Also, go make your own thread. My question didn't even get answered
Click to expand...
Click to collapse
I can see why you could be upset that someone hijacked your thread.
I only see one question in your original post, which I believe I answered. You also requested assistance which I thought I provided.
Let me be a little more specific for you. Yes, you can flash just a kernel without re-flashing the system. However, you will need either an Odin flashable tar of the kernel, or you will need to install Mobile Odin and then you can flash a kernel directly from a zImage file.
However, I think 4-2ndtwin has the right of it. It was probably a bad flash, even though the phone booted normally. You should consider re-flashing the entire rom.
If you are not clear about anything, please ask questions.
Never mind.
I concluded it wasn't worth it just because I was lazy backing up stuff.
I used this: http://forum.xda-developers.com/showthread.php?t=1525821, then flashed a clean ROM.
Thanks for the help, you guys are awesome.
I´m on S3 International and have flashed Philz Recovery with ODIN and flashed Wanam latest 4.3. Works great! I have even flashed the S4 launcher and weatherwidget and all is still well.
However, now I want to try to run MIUI on my S3. After backing up my S3 and started to flash I got Error Status 7. I have read some threads about it and the first I wanted to try was to install another recovery. But even when I flash another recovery I get Error Status 7. I suddenly can´t flash anything at all. Does this have to do with the fact that I ticked the "disable recovery flash" when exiting the Philz recovery after starting this journey when beginning to root and so on? If so... how do I get it "unticked"?
First up...
Will flashing another recovery (CWM for example) help me get past this Status 7 problem?
Second...
If I descide to flash CWM Recovery via ODIN will it reset my current ROM in any way or will everything stay the same?
Third...
I read somewhere that I can modify the updater-script in the META-folder. Is that really a afe way to go about it? It feels kind of wierd when the *.zip´s are made for the right phone, model, version and so on...
Thanx for the help, guys!
Manneman32 said:
I´m on S3 International and have flashed Philz Recovery with ODIN and flashed Wanam latest 4.3. Works great! I have even flashed the S4 launcher and weatherwidget and all is still well.
However, now I want to try to run MIUI on my S3. After backing up my S3 and started to flash I got Error Status 7. I have read some threads about it and the first I wanted to try was to install another recovery. But even when I flash another recovery I get Error Status 7. I suddenly can´t flash anything at all. Does this have to do with the fact that I ticked the "disable recovery flash" when exiting the Philz recovery after starting this journey when beginning to root and so on? If so... how do I get it "unticked"?
First up...
Will flashing another recovery (CWM for example) help me get past this Status 7 problem?
Second...
If I descide to flash CWM Recovery via ODIN will it reset my current ROM in any way or will everything stay the same?
Third...
I read somewhere that I can modify the updater-script in the META-folder. Is that really a afe way to go about it? It feels kind of wierd when the *.zip´s are made for the right phone, model, version and so on...
Thanx for the help, guys!
Click to expand...
Click to collapse
You didn't mention the version of Philz you were using. Anyway, the error 7 can be caused from 2 main reasons:
1- Older recovery version. Flash the lastest recovery available (6.15.4) and try again: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300
2- Corrupted rom download.
To your 2nd question- if it doesn't work with Philz, it will not work with any other recovery.
Well... when I asked about how to go about rooting just a week ago I got links to what I needed. And with that I got a link to Philz Recovery. But now I see that it was an old version (6.07.9)
I´ll try with the latest one and see where that takes me.
Edit:
Flashed the latest Philz and took a new backup just in case. It didn´t work. Still Status 7. So I re-downloaded the ROM just in case it was corrupted but still the same... aborted Status 7.
So... now what? Am I screwed?
I read somewhere that it could have something to do with the fact that I use an external SD-card. Will it really make a difference if I flash it from the internal memory and even if i take the SD out of the phone?
Manneman32 said:
I read somewhere that it could have something to do with the fact that I use an external SD-card. Will it really make a difference if I flash it from the internal memory and even if i take the SD out of the phone?
Click to expand...
Click to collapse
Worth the try
Here 2 relevant threads I found:
http://en.miui.com/thread-6429-1-1.html
Follow galnet post (page 7):
http://forum.xda-developers.com/showthread.php?t=1749392&page=7
Sent from my GT-I9300 using Tapatalk
So... the links refer to downgrading to a really old recovery used for rooting with CF or unticking the "disable signature check" ... feels strange.
Is there anyway to explain why this error occurs?
Last question before giving this up...
If I should downgrade my recovery, is that safe? And how will it work with downgrading from a 4.3 ROM to a 4.1.1 ROM. Is this nothing to be concerned about?
// Manneman
Manneman32 said:
Last question before giving this up...
If I should downgrade my recovery, is that safe? And how will it work with downgrading from a 4.3 ROM to a 4.1.1 ROM. Is this nothing to be concerned about?
// Manneman
Click to expand...
Click to collapse
Downgrade and network problems .
http://forum.xda-developers.com/showthread.php?t=2531221
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
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