Greetings,
S5, Verizon. Was previously running 4.4.4, Stock rooted.
I upgraded to Lollipop Stock rooted. But I do not have a custom recovery.
I grabbed TWRP and it failed, "Secure Magiccode check failed : recovery"
I did a bit of digging, and Verizon's Samsung's GS5 is not on their list of devices.
I checked clockwordmod, they do not list it either.
Am I missing something? I installed Safestrap previously, to install lollipop. However, that does not work with Lollipop, so I've read.
Any suggestions for a custom recovery?
If you're rooted, try this
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en_GB
It's what I use
Nice thought. I grabbed that and installed it. Unfortunately, it didn't work. My phone is now stuck with "Recovery is not seandroid encorcing."
And it's continually trying to boot into recovery.
Research time.
Can you boot into recovery using Vol Up, Home & power?
I think that message is normal, as it's not stock recovery
*Detection* said:
Can you boot into recovery using Vol Up, Home & power?
I think that message is normal, as it's not stock recovery
Click to expand...
Click to collapse
Nope. I get the nice blue "Booting recovery" (or whatever), then the message above.
Then "Start up Failed" blah blah.
Might have to flash a stock ROM back on this to get it booted. I'm still reading up on it.
Thanks for your tips!
jagauthier said:
Nope. I get the nice blue "Booting recovery" (or whatever), then the message above.
Then "Start up Failed" blah blah.
Might have to flash a stock ROM back on this to get it booted. I'm still reading up on it.
Thanks for your tips!
Click to expand...
Click to collapse
I was able to reflash "G900V_OA8_Stock_Partitions.tar.md5", and this rebuilt the recovery partition.
So, I'm functional, but no custom recovery.
Tried using the TWRP manager to flash recovery again since rebuilding recovery?
*Detection* said:
Tried using the TWRP manager to flash recovery again since rebuilding recovery?
Click to expand...
Click to collapse
No, this is where I was before. Doing it again will almost undoubtedly result in the same issue.
Aren't Version S5s all bootloader locked?
*Detection* said:
Aren't Version S5s all bootloader locked?
Click to expand...
Click to collapse
I am not that well versed. I just wanted to install a custom recovery
I was rooted with Kitkat, and installed Safestrap. I booted into that to upgrade to Lollipop.
It's not that big of deal. I was hoping for a simple solution.
*Detection* said:
Aren't Version S5s all bootloader locked?
Click to expand...
Click to collapse
Yeah NO TWRP. If one does manage to replace stock recovery w twrp, a message pops up letting you know its a unauthorized Verizon....... Please go to nearest VZW store.
---------- Post added at 05:16 PM ---------- Previous post was at 05:15 PM ----------
Go Dev Edition if you want TWRP.
Related
Hello all, long time lurker, first time poster
I was wondering if there is currently a way to get a custom recovery on my phone without the use of a computer. I was able to root my phone using towel root, and first thing I did was install Rom Manager and start to make a nandroid backup until I got:
" RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery"
So I went into download mode, hit cancel and was able to boot into android but to this day I am unable to get into recovery, stock or custom. Due to my current complicated situation I do not have access to a computer and was hoping there was a work around to allow me to implement a custom recovery without a pc. I want to be able to make a nandroid backup, flash zips into the OS, and possibly experiment with other roms... I have tried looking into this myself but the only thing I came up with us an app called "Flashing Tool", though I don't know whether that will allow me to do what I want it to. Oh, and I don't care about Knox being flagged by the way.
So ladies and gentlemen of the Xda community, I beg for your assistance and would greatly appreciate any answers you can give me.
My phone is a T-Mobile Note 3, rooted stock Kit Kat rom, any other info needed just let me know.
Brooklynyte said:
Hello all, long time lurker, first time poster
I was wondering if there is currently a way to get a custom recovery on my phone without the use of a computer. I was able to root my phone using towel root, and first thing I did was install Rom Manager and start to make a nandroid backup until I got:
" RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery"
Click to expand...
Click to collapse
That is the standard message while recovery is booting. How long did you wait?
FeralFire said:
That is the standard message while recovery is booting. How long did you wait?
Click to expand...
Click to collapse
After that message it just restarts into a boot loop showing that message over and over until I pull the battery, boot into download mode and then hit cancel so the phone boots up normally. Currently I do not have a recovery menu at all, not stock, and not custom.
Brooklynyte said:
After that message it just restarts into a boot loop showing that message over and over until I pull the battery, boot into download mode and then hit cancel so the phone boots up normally. Currently I do not have a recovery menu at all, not stock, and not custom.
Click to expand...
Click to collapse
Ok, try mobile odin.
FeralFire said:
Ok, try mobile odin.
Click to expand...
Click to collapse
Ok, installed Mobile Odin, first thing it said was to make sure I have the proper boot loader or it could result in a soft brick. Now it shows me the different partitions, one of them being "recovery"... Now what file exactly should I be using? Do I flash it to that partition or do I just use the" Open file" option? Can you guide me through it at all? I appreciate all your help thus far!
Edit: I believe I found the correct file to flash... Please correct me if I'm wrong but being that I have the T-Mobile version of the Note 3, my boot loader should not be locked right? So I should be able to flash this file *n9005-cwm-recovery-6.0.4.7-kk(0125).tar* using mobile odin, and all should be good, right? I would post the link but I'm a new user and cant... But this is the description of the file: SM-N9005/SM-N900T/SM-N900P Qualcomm Note 3 – CWM Recovery -*Download*-*Credits*(Also works for T-Mobile/Sprint)
Brooklynyte said:
Ok, installed Mobile Odin, first thing it said was to make sure I have the proper boot loader or it could result in a soft brick. Now it shows me the different partitions, one of them being "recovery"... Now what file exactly should I be using? Do I flash it to that partition or do I just use the" Open file" option? Can you guide me through it at all? I appreciate all your help thus far!
Click to expand...
Click to collapse
I have never personally used Mobile Odin, but you need to flash the recovery's tar file in the software.
FeralFire said:
I have never personally used Mobile Odin, but you need to flash the recovery's tar file in the software.
Click to expand...
Click to collapse
You my dear friend, have my everlasting gratitude! I now have a working cwm recovery! Maybe I should make a quick guide to show how to root and flash custom recovery without a computer... Lord knows I could have used a guide like that. Thank you Feral....
Brooklynyte said:
You my dear friend, have my everlasting gratitude! I now have a working cwm recovery! Maybe I should make a quick guide to show how to root and flash custom recovery without a computer... Lord knows I could have used a guide like that. Thank you Feral....
Click to expand...
Click to collapse
Just press the thanks button.
And you are welcome.
I think I am having a similar issue to the OP in the following thread http://forum.xda-developers.com/showthread.php?t=3267539
I have unlocked my boot-loader and rooted a flashed factory image of mdb08m using skipsoft.
So I want to flash the new OTA but despite unrooting and using the the function in skipsoft to unroot, remove files, and restore stock recovery the OTA failed. I have since then downloaded the the factory image and re-flashed the stock recovery but every time I go into recovery (to try and sideload) I get the red exclamation with the words "No command" underneath. I then can not do anything.....
Thankfully the phone boots and runs like normal yet I can not do the update ?
Any ideas please?
indyjonesUK said:
I think I am having a similar issue to the OP in the following thread http://forum.xda-developers.com/showthread.php?t=3267539
I have unlocked my boot-loader and rooted a flashed factory image of mdb08m using skipsoft.
So I want to flash the new OTA but despite unrooting and using the the function in skipsoft to unroot, remove files, and restore stock recovery the OTA failed. I have since then downloaded the the factory image and re-flashed the stock recovery but every time I go into recovery (to try and sideload) I get the red exclamation with the words "No command" underneath. I then can not do anything.....
Thankfully the phone boots and runs like normal yet I can not do the update ?
Any ideas please?
Click to expand...
Click to collapse
the ota will likely still fail if you were able to sideload it.
its been my experience with previous devices, you cant really remove root properly and make the phone 100% like it was. that probably why the update is failing.
frequently you need to flash the full stock img to make the phone clean enough for ota's.
i cant guarantee thats the case here, but is very likely.
If you get the 'No command' thingy you should try fastboot flashing the recovery.
That's what did the trick for me.
Casmo said:
If you get the 'No command' thingy you should try fastboot flashing the recovery.
That's what did the trick for me.
Click to expand...
Click to collapse
Yeah I tried that but has not changes things
Did you hold power, tap VOL UP and release both? That is how you enter stock recovery.
fury683 said:
Did you hold power, tap VOL UP and release both? That is how you enter stock recovery.
Click to expand...
Click to collapse
Can't believe I could not find that anywhere! thank you worked first time....
indyjonesUK said:
Can't believe I could not find that anywhere! thank you worked first time....
Click to expand...
Click to collapse
You need to see whether your stock recovery can work with OTA successfully.
Thanks!
fury683 said:
Did you hold power, tap VOL UP and release both? That is how you enter stock recovery.
Click to expand...
Click to collapse
OMG can't believe you have to do this while stuck in "No command", thanks a lot!
First, thank you for any help!
I did look threw the forums, as best I could... I did see any solutions here that worked for me... saw some one another site.. they did not work.
I can no longer get into ANY recovery boot... Every time I do the buttons, to go into recovery... it show "booting into recovery" blinks, vibrates... and then boots into the phone in normal mode....
I recently had to flash it to stock with Odin.... which lost my root.... I tried to install TWRP , so I could root it... did not work... then used KINGOROOT, to root it, which it claims DID work (the rooting) , after two tries... and then it did allow me to go into "stock recovery" mode...
...so i then flashed TWRP with Odin... and ... now, again, I get not get ANY recovery mode to come up.
ARGH!!!!!!!
Please help??
I have a N900T.
Android 5.0
Baseaband: N900TUVUFOL1
I believe it is rooted now
As long as you're flashing the correct file, it should work.
Sent from my SM-N920C
Rosli59564 said:
As long as you're flashing the correct file, it should work.
Sent from my SM-N920C
Click to expand...
Click to collapse
I am flashing TWRP 2.8.7.0 which is the SAME file I used when I flashed it... a year ago?
I know that there is a new version of TWRP... but I have heard there are problems with the newer TWRP flashing ROM's....
On another site, someone said that the problem was that if you flash back to stock, the new (stock) bootloader has a line it it, to check that you can only use stock recovery file... ... >sigh<....
My "simple" project... to upgrade my phone... has become a night mare.....
2.8.7.0-hltetmo?
If it doesn't work, try cwm.
Sent from my SM-N920C
Got it fixed!!
Figured I would say how, in case someone else has the same problem.
I had already rooted the phone with "Kingoroot" , when I was trying to put TWRP on...
By downloading and running "TWRP MANAGER" from the play store, it was able to install it on my phone, and I am now able to boot into recovery.
Good luck!!
Danny
Hi. I was trying to install Cyanogenmod on my LG Leon. First, I rooted my phone using KingRoot and then replaced it with SuperSU. Then, I proceeded to install TWRP. But, because I was installing it my first time in my life, I made a mistake and tried do install it using TWRP Manager, without doing a backup of the stock recovery. After rebooting, secure boot error popped up and I had to take out the battery. Now whatever I do I cannot do anything custom rom related. Do you have any hints?
bokjezd said:
Hi. I was trying to install Cyanogenmod on my LG Leon. First, I rooted my phone using KingRoot and then replaced it with SuperSU. Then, I proceeded to install TWRP. But, because I was installing it my first time in my life, I made a mistake and tried do install it using TWRP Manager, without doing a backup of the stock recovery. After rebooting, secure boot error popped up and I had to take out the battery. Now whatever I do I cannot do anything custom rom related. Do you have any hints?
Click to expand...
Click to collapse
You have to enable OEM unlock in Developer Options to prevent the secure boot error, then flash the recovery using Flashify and reboot.
adefesio said:
You have to enable OEM unlock in Developer Options to prevent the secure boot error
Click to expand...
Click to collapse
I already found an advise like this, but I still cannot find that option. I think I have a little bit too old android. Do you know in which version of android it was introduced? I have 5.0.1. Maybe there is another hidden switch simular to the one enabling developer options used to enable OEM unlock?
bokjezd said:
I already found an advise like this, but I still cannot find that option. I think I have a little bit too old android. Do you know in which version of android it was introduced? I have 5.0.1. Maybe there is another hidden switch simular to the one enabling developer options used to enable OEM unlock?
Click to expand...
Click to collapse
Check if there's a software upgrade available from your provider. I can also suggest flashing back the original stock recovery image. Let me know if you need a download link. Which variant is your Leon?
adefesio said:
Check if there's a software upgrade available from your provider. I can also suggest flashing back the original stock recovery image. Let me know if you need a download link. Which variant is your Leon?
Click to expand...
Click to collapse
Yes, there is an update but currently I can't do it because updating reboots to recovery to update something. I would really like to flash back the original recovery, but I don't have the image, so can I have the link, please? My Leon is LG H340n.
bokjezd said:
Yes, there is an update but currently I can't do it because updating reboots to recovery to update something. I would really like to flash back the original recovery, but I don't have the image, so can I have the link, please? My Leon is LG H340n.
Click to expand...
Click to collapse
I am sending a private message with the link. Let me know if it works.
adefesio said:
I am sending a private message with the link. Let me know if it works.
Click to expand...
Click to collapse
Thanks, it seems to work now, but it refuses to update because it detects root. Is there a way to hide it or do I have to do a full unroot? I already tried the "Hide my Root" app.
Edit: Never mind, I will just do the unroot and then update.
Ok, I've downloaded recovery-H340N.img, but when I try to update, it shows that updating screen and then error 0x1125000 pops up. The phone reboots and then it tells me it detected root, however I did a full unroot... Do you know what that error means? And how does LG check for the root?
bokjezd said:
Ok, I've downloaded recovery-H340N.img, but when I try to update, it shows that updating screen and then error 0x1125000 pops up. The phone reboots and then it tells me it detected root, however I did a full unroot... Do you know what that error means? And how does LG check for the root?
Click to expand...
Click to collapse
Reset to factory settings, do the update, root with Kingroot (DON'T replace with SuperSU), restart, enable OEM unlock, install TWRP using Flashify.
adefesio said:
Reset to factory settings, do the update, root, enable OEM unlock, install TWRP using Flashify.
Click to expand...
Click to collapse
Wait, I need to do a backup of all my data, right?
bokjezd said:
Wait, I need to do a backup of all my data, right?
Click to expand...
Click to collapse
Google backs up most of your data, but not all. If you know other ways then do it.
---------- Post added at 03:53 PM ---------- Previous post was at 03:49 PM ----------
Google backs up most of your data but not all. If you know other ways then do it, then:
Reset to factory settings, do the update, root with Kingroot (DON'T replace with SuperSU), restart, enable OEM unlock, install TWRP using Flashify.
adefesio said:
Google backs up most of your data, but not all. If you know other ways then do it.
---------- Post added at 03:53 PM ---------- Previous post was at 03:49 PM ----------
Google backs up most of your data but not all. If you know other ways then do it, then:
Reset to factory settings, do the update, root with Kingroot (DON'T replace with SuperSU), restart, enable OEM unlock, install TWRP using Flashify.
Click to expand...
Click to collapse
I've reset my phone to factory settings, but it still refuses to update with error code 0x1125000 and after rebooting to home screen it says it detected root. I think I'm gonna update with LG Mobile Support Tool.
Wait, does my mobile operator affect what recovery should I flash? If yes, it is P4, often referred to as PLAY. Or maybe I should also flash the boot image you've sent to me? My PC doesn't detect my phone, so I have to repair the updates...
bokjezd said:
Wait, does my mobile operator affect what recovery should I flash? If yes, it is P4, often referred to as PLAY. Or maybe I should also flash the boot image you've sent to me? My PC doesn't detect my phone, so I have to repair the updates...
Click to expand...
Click to collapse
Too many complications. Just reflash the entire ROM with the most recent kdz. Root with Kingroot and don't replace it with SU. You know the rest.
Still nothing. Now it says it's the newest software available, but I cannot find that oem unlock. Are you sure it's available on Leon? I've read some manufacturers remove it...
Hey all, Ive had this weird issue lately when it comes to to flashing custom roms. I Have just rooted and unlocked the bootloader on my phone and i want to install a custom rom
but every time i try to flash it in twrp it fails and says "This package is for build hltetmo your device is ."
My phone IS hltetmo so im very confused on whats going on here
Any help?
Ferkacete said:
Hey all, Ive had this weird issue lately when it comes to to flashing custom roms. I Have just rooted and unlocked the bootloader on my phone and i want to install a custom rom
but every time i try to flash it in twrp it fails and says "This package is for build hltetmo your device is ."
My phone IS hltetmo so im very confused on whats going on here
Any help?
Click to expand...
Click to collapse
What recovery are you using? Some (<= android 6) ROMs require TWRP 2.8.7 hltevzw and some (>= android 7) require TWRP 3.1.1 hlte or higher.
cssr said:
What recovery are you using? Some (<= android 6) ROMs require TWRP 2.8.7 hltevzw and some (>= android 7) require TWRP 3.1.1 hlte or higher.
Click to expand...
Click to collapse
Im using twrp and the recovery img i used is called twrp-2.8.7.0-hltevzw-4.4.img.tar and im lollipop with OF1
The roms im trying to flash are Oreo roms so does that mean i need a more updated version of twrp?
Ferkacete said:
Im using twrp and the recovery img i used is called twrp-2.8.7.0-hltevzw-4.4.img.tar and im lollipop with OF1
The roms im trying to flash are Oreo roms so does that mean i need a more updated version of twrp?
Click to expand...
Click to collapse
Yes! You need TWRP 3.1.1hlte (not hltevzw) or higher. You can install it in recovery, then go back to TWRPs main screen, select reboot and then select recovery. If you don't reboot into recovery the install will not stick.
https://dl.twrp.me/hlte/twrp-3.2.3-0-hlte.img.html
This a link to the right .img file. To install, at TWRPs main screen select install, go to the folder where the file is, at the bottom right you will see " install image " select that, then select the TWRP .img file, it will ask boot or recovery select recovery, then back to the main screen to reboot into recovery. As always make a backup first in case something goes wrong!
cssr said:
Yes! You need TWRP 3.1.1hlte (not hltevzw) or higher. You can install it in recovery, then go back to TWRPs main screen, select reboot and then select recovery. If you don't reboot into recovery the install will not stick.
https://dl.twrp.me/hlte/twrp-3.2.3-0-hlte.img.html
This a link to the right .img file. To install, at TWRPs main screen select install, go to the folder where the file is, at the bottom right you will see " install image " select that, then select the TWRP .img file, it will ask boot or recovery select recovery, then back to the main screen to reboot into recovery. As always make a backup first in case something goes wrong!
Click to expand...
Click to collapse
The roms work now! Thank you so much
Ferkacete said:
The roms work now! Thank you so much
Click to expand...
Click to collapse
Great!
cssr said:
Yes! You need TWRP 3.1.1hlte (not hltevzw) or higher. You can install it in recovery, then go back to TWRPs main screen, select reboot and then select recovery. If you don't reboot into recovery the install will not stick.
https://dl.twrp.me/hlte/twrp-3.2.3-0-hlte.img.html
This a link to the right .img file. To install, at TWRPs main screen select install, go to the folder where the file is, at the bottom right you will see " install image " select that, then select the TWRP .img file, it will ask boot or recovery select recovery, then back to the main screen to reboot into recovery. As always make a backup first in case something goes wrong!
Click to expand...
Click to collapse
I can't get TWRP to stick. Can u help?
jerryspring said:
I can't get TWRP to stick. Can u help?
Click to expand...
Click to collapse
Did you reboot into recovery after installing the update. You must install the update and then reboot into recovery. If you reboot into the system the update will be lost!
cssr said:
Did you reboot into recovery after installing the update. You must install the update and then reboot into recovery. If you reboot into the system the update will be lost!
Click to expand...
Click to collapse
Seems as if I have both recoveries. SS and twrp
---------- Post added at 11:55 AM ---------- Previous post was at 11:52 AM ----------
cssr said:
Did you reboot into recovery after installing the update. You must install the update and then reboot into recovery. If you reboot into the system the update will be lost!
Click to expand...
Click to collapse
Yea. I did. I am on 4.3 boot loader, and I flashed sepl1 modem. Baseband says sepl1 even though I'm on 4.3 boot loader. Even when I flash stock ROM, the stock ROM won't flash, even though Odin says successful
jerryspring said:
Seems as if I have both recoveries. SS and twrp
---------- Post added at 11:55 AM ---------- Previous post was at 11:52 AM ----------
Yea. I did. I am on 4.3 boot loader, and I flashed sepl1 modem. Baseband says sepl1 even though I'm on 4.3 boot loader. Even when I flash stock ROM, the stock ROM won't flash, even though Odin says successful
Click to expand...
Click to collapse
Try to install the full stock ...OF1 ROM. Samsung will not let you down grade from Android 5.0 to 4.3 and your baseband is showing up as 5.0. After installation of OF1 unlock the bootloader, then install twrp with Odin. After that you can install a custom ROM and the PL1 modem.
cssr said:
Try to install the full stock ...OF1 ROM. Samsung will not let you down grade from Android 5.0 to 4.3 and your baseband is showing up as 5.0. After installation of OF1 unlock the bootloader, then install twrp with Odin. After that you can install a custom ROM and the PL1 modem.
Click to expand...
Click to collapse
I thought bootloader unlock was only capable with 4.4...and will the stock firmware flash successfully? and I don't know why it did not last successfully. I originally came from mje firmware and I was flashing 5.0
cssr said:
Try to install the full stock ...OF1 ROM. Samsung will not let you down grade from Android 5.0 to 4.3 and your baseband is showing up as 5.0. After installation of OF1 unlock the bootloader, then install twrp with Odin. After that you can install a custom ROM and the PL1 modem.
Click to expand...
Click to collapse
I tried flashing of1.. it goes to blue writing saying recovery booting and hangs. Stock firmware will not flash!