Hello,
I am attempting to flash TWRP 2.6 onto my device, and many attempts have been unsuccessful. Many sources are stating to install the recovery using GooManager, but the service seems to be having issues as of lately, having HTTP 500 errors or downloads not starting.
Seeking the developer's website directly, they state to use either GooManager, or install it using the dd command. Following the instructions, using dd was also unsuccessful, causing my recovery partition to be in-operable, and having to restore to stock recovery.
Having no progress with GooManager after a few days, I attempted to flash ClockworkMod, using both ROM Manager and the Loki method. After installing via ROM manager, this did nothing to the recovery, and Loki stated that aboot does not match the device.
Any help would be appreciated, thank you very much.
Device: Verizon Galaxy S4; SCH-i545
Build Number: MI1
Rooted via Root de la Vega
Image: openrecovery-twrp.2.6.3.0-jfltevzw.img
Did you try "fastboot flash yourimage.img" in windows?
Edit: forgot you're on ml1 so yes you can only install safe strap
prshosting.org
I believe you can only install safestrap (SS) on the MI1 build number and not CWM. Sorry :/
Sent from my SCH-I545 using Tapatalk
Related
Hello, I'm trying to flash CM on to my Samsung GS4 but am having trouble getting past recovery. My phone has build KOT49H.I545VRUFNC5. I gained root access using towelroot and verified through terminal using the SU command (the prompt became #). I installed Clockwork Mod and flashed recovery 6.0.4.7 but when i reboot into recovery (whether manually or through CWM) the phone still goes into stock recovery. I also tried installing recovery through ADB sideload. On the PC terminal window it shows 100% and on the device shows: (and it does this twice before showing installation aborted)
Finding Update package
Opening Update package
Verifing update package
E:footer is wrong
E:signature verification failed
I've tried two different packages from CWM and one from TWRP all with the same results.
recovery-clockwork-touch-6.0.4.7-jfltevzw.img
recovery-clockwork-6.0.4.7-jfltevzw.img
openrecovery-twrp-2.8.0.1-jfltevzw.img
I've read this post on CM (http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw) and it mentions installing an alternate kernal but I have not done so because it warns up top that you must be on I545VRUAMDK or this process will not work and brick your phone. So I'm going around in circles here. Any guidance would be appreciated.
kylo77 said:
Hello, I'm trying to flash CM on to my Samsung GS4 but am having trouble getting past recovery. My phone has build KOT49H.I545VRUFNC5. I gained root access using towelroot and verified through terminal using the SU command (the prompt became #). I installed Clockwork Mod and flashed recovery 6.0.4.7 but when i reboot into recovery (whether manually or through CWM) the phone still goes into stock recovery. I also tried installing recovery through ADB sideload. On the PC terminal window it shows 100% and on the device shows: (and it does this twice before showing installation aborted)
Finding Update package
Opening Update package
Verifing update package
E:footer is wrong
E:signature verification failed
I've tried two different packages from CWM and one from TWRP all with the same results.
recovery-clockwork-touch-6.0.4.7-jfltevzw.img
recovery-clockwork-6.0.4.7-jfltevzw.img
openrecovery-twrp-2.8.0.1-jfltevzw.img
I've read this post on CM (http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw) and it mentions installing an alternate kernal but I have not done so because it warns up top that you must be on I545VRUAMDK or this process will not work and brick your phone. So I'm going around in circles here. Any guidance would be appreciated.
Click to expand...
Click to collapse
You are on NC5. Clockwork Mod and TWRP are not compatible with our device. Nor are pure AOSP ROMs such as CyanogenMOD. Our bootloader is still locked and we can only use Safestrap as our recovery and safestrap compatible ROMs. I am surprised you have not at least soft bricked your phone yet.
Thanks, that explains a lot.
Not saying you missed a detail, but even mdk isn't unlocked, just bypassed.
Hey everyone...!
I have samsung galaxy s4 i545 with the latest version of android 5.0.1 and also it has root access.
I am trying to install the latest twrp or cwm recovery but i cant install.
I used many apps like twrp recovery , flashify etc but when i install the recovery file the message popup something like this "twrp recovery successfully installed fo you like to move up on twrp recovery". Then i press the option yes after reboot it will show the downloading mode. I also tried the loki method but in vain.
So plz help me to install the twrp or cwm recovery so that i will be able to install any rom on my mbl.
Thanks...
And Sorry for my weak english...
The bootloader is locked using knox. Only safestrap used to work. Other then that, there is no recovery options. I don't know if safestrap even works on newest OF1
Sent from my SCH-I545 using Tapatalk
How can i use safestrap.....?
You cannot
KaosMaster is mistaken.
OF1 does not support safestrap as the flash around method does not function on OF1.
The only ROM you can flash is Stang5lire's ROM, with Flashfire.
What about xposed on of1?
Sent from my stang5litre Edition 5.0 using Tapatalk
shiz0id said:
What about xposed on of1?
Sent from my stang5litre Edition 5.0 using Tapatalk
Click to expand...
Click to collapse
You can get xposed thru flashfire. You have to root using Kingroot(I think for OF1, look through the forums, there are several threads on this). Then get SuperSU(or SuperSUME to get rid of the chinese knockoff and install the real deal if you used kingroot) and then flashfire, get the xposed zips, flash thru xposed, and tada.
Sorry no speak english
my problem is that when press the button continue
does not continue with the recovery and Normally start andriod
installed SuperSU by chainfire (admin root)
Installed Bussybox
Installed Kernel and recovery oc1
**** Xda no uploading images and external links bat luck
Unfortunately safestrap doesn't work on oc1. Stuck with flashfire. Far less reliable than safestrap
Can you say : "Time for a Nexus"? Older models are on sale, you know. N6 quite a bargain right now.
Sent from my P01MA using Tapatalk
You cannot install TWRP on any S4 except one with the MDK bootloader.
To check use a terminal emulator and type:
Getprop ro.bootloader
If it does not say I545VRUAMDK you can't flash any custom recovery.
Hi friends,
So here's a thing:
I was trying to update my Nexus 9 to the latest Slimrom build , and I used Chainfire's flashfire app. It didn't work and sent the tablet in a boot loop. But it also wiped my recovery so I couldn't even select my recovery.
So no issues, I used the Wugfresh nexus toolkit to flash it back to stock and unroot. Bootloader is still unlocked, so I just root it again and go ahead and try to install the update using Wugfresh. It works, but says the vendor.img is wrong. So I downloaded the correct vendor.img and tried to flash it, but of course because the tablet is encrypted TWRP asked for a password. I hit cancel and tried to continue, but Wugfresh just hung at that step.
So I tried to manually flash the ROM, but now it gives me a vendor.img error and will not flash anything. Trying to flash anything sends the device in a bootloop.
TLDR; I can restore to stock and root, and also access the bootloader and recovery (TWRP) but can't flash anything without sending the device in a bootloop.
I've currently restored the tablet to stock via wugfresh's tool and rooted. So I'm back at the beginning, except with this vendor.img issue when I'm trying to flash a ROM.
Anyone have any ideas?
I'm having major problems with TWRP, and I need help.
I have a Samsung Galaxy S4 with a properly unlocked bootloader (MDL), rooted, that has had a working version of TWRP 2.8.7.0 and running an older version of Cyanogen.
I'm overhauling the phone, so the first thing I tried to do was to update TWRP.
Since TWRP v2.8.7 supports flashing itself, I booted into recovery and flashed the TWRP update (v3.2.1.0) directly through TWRP. No errors that I saw.
But when I try to boot into recovery, I now get "System Software Not Authorized By AT&T Has Been Found On Your Phone". Fortunately, I can still boot normally - it's only recovery that I'm locked out of.
In trying to fix this, I tried re-flashing TWRP with three different methods:
1. I tried to flash TWRP again through the TWRP app. But I get "Flash Failed".
2. I tried Odin and got "FAIL! (Auth)"
3. I tried flashing v3.2.2.0 using the dd method. This I was able to do without any errors, but I'm still locked out of recovery mode with that same "System Software Not Authorized By AT&T Has Been Found On Your Phone" error.
Help?
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
HippoInWindow said:
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
Click to expand...
Click to collapse
ADB works fine for me, but fastboot does not. It says "waiting for any device". From what I understand, this is a common issue with Samsung phones. I'm using Windows 10, if that helps.
However, I came across a bug report for TWRP here, that reports the exact same problem from 3.0.0.0, and it's still open. That tells me that this may be a general issue with TWRP that they never bothered to fix.
So on a hunch, I tried re-flashing v2.8.7 using the dd method (since that's the only one I can get to work). And SUCCESS! I can now boot into recovery again!
So here's what I need to know:
1. Is there any way to get the latest version of TWRP to work on this phone?
2. Is it safe to flash a current version of LineageOS using this version of TWRP (v2.8.7)?
I'm really wary about that second question, because the last thing I want to do is brick my phone because an old version of TWRP doesn't know how to work with a new version of Lineage/Android. (This phone currently has KitKat on it)
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
HippoInWindow said:
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
Click to expand...
Click to collapse
I finally found an explanation and solution - it would appear that TWRP 3.x does not have the Loki exploit applied. So nothing 3.0+ will work unless it's been Lokied.
Fortunately, the current versions can be Loki patched, so once that's done, they'll install and work properly. Whew!