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.
Related
Good day
After using different methods to try and install a variety of ROMS inclduing CM11, MUIU, FirefoxOs and KitKat 4.4.4.2 Brannded, I'm stuck in the TWRP 2.6.3.2 gui after using flashify and not making a backup. When I sideload and install miui_g2_ws008_4.5.19_5b586f93ad_4.2 it installs sucessfully according to the log, but I get stuck in boot loop after gapps has been loaded in 1st boot. With cm-11-20140522-NIGHTLY-d802, openrecovery-twrp-2.7.0.0-d2vzw, philz_touch_5.15.0-d2vzw, TWRP_v2.3.3.0_P350 I get the Error Executing Binary Zip. When I sideload openrecovery-twrp-2.7.0.2-t03g it installs successfully, I select reboot, it ask me to install SuperSU I say yes and then get stuck in LG boot loop. LG flash tools get stuck at "waiting for connection" when I try to flash it with LGD800AT-01-V10d-310-410-AUG-14-2013 and LGD800_20130904_LGFLASHv160.
:c rying::cry ing:
Please help I don't know what to do next!
I've made a terrible mistake.
Unlocked the bootloader successfully then tried flashing superuser, then wiped all, then tried installing CM11
Apparently I never got root successfully and now the device has no ROM at all.
It won't write CM11 and I can't throw a stock rooter tmobile rom in the TWRP directory to try that.
"Error executing binary in zip"
did I just wreck the device?
theartialmartist said:
I've made a terrible mistake.
Unlocked the bootloader successfully then tried flashing superuser, then wiped all, then tried installing CM11
Apparently I never got root successfully and now the device has no ROM at all.
It won't write CM11 and I can't throw a stock rooter tmobile rom in the TWRP directory to try that.
"Error executing binary in zip"
did I just wreck the device?
Click to expand...
Click to collapse
You might try to run the RUU 5.14.531.11 of course it will wipe all of your data if you didn't save it before your issue. If you are S-ON, you will need to lock your bootloader after you successfully run the RUU you can unlock it again using your same unlock code.
@theartialmartist
You might try this: HTC Unbricking Project
I got a replacement Tab from sony and I'm having trouble rooting it with the updated firmware. Seems the only real way to do it is to have a custom recovery installed, however I am having trouble with that. When I try installing a recovery through fastboot flash command I get an error FAILED: Remote: Command not Allowed.
The installer version of XZDual just hangs at install.
Has anyone else on Verizon tab found any other ways of rooting after the latest update?
Varekai said:
I got a replacement Tab from sony and I'm having trouble rooting it with the updated firmware. Seems the only real way to do it is to have a custom recovery installed, however I am having trouble with that. When I try installing a recovery through fastboot flash command I get an error FAILED: Remote: Command not Allowed.
The installer version of XZDual just hangs at install.
Has anyone else on Verizon tab found any other ways of rooting after the latest update?
Click to expand...
Click to collapse
You have to downgrade firmware off 4.4.4 and root,
Got it working. I didn't know I had to have the unknown sources checked. Also I didn't realize I was plugged into a 3.0 port in the back of my PC, so that didn't help. Thanks for the help.
I have a Verizon Z2 LTE SGP561 with the latest update of 4.4.4 and i managed successfully to Root it with the latest KingRoot apk.
It was very easy - just download the KingRoot apk to your device , run it from the device and it will do the work.
After it will complete you will have KingRoot user which is the superuser app for permission, no need to install SuperUser of SuperSU.
I checked with root-checker to verify and indeed it was rooted.
even though the bootloader is locked you are rooted.
I managed to remove all Verizon bloatware apps.
You can find the latest KingRoot apk in the following link:
http://downloadandroidapkget.blogspot.co.il/2015/05/download-kingroot-apk-latest-version.html
Varekai said:
I got a replacement Tab from sony and I'm having trouble rooting it with the updated firmware. Seems the only real way to do it is to have a custom recovery installed, however I am having trouble with that. When I try installing a recovery through fastboot flash command I get an error FAILED: Remote: Command not Allowed.
The installer version of XZDual just hangs at install.
Has anyone else on Verizon tab found any other ways of rooting after the latest update?
Click to expand...
Click to collapse
Thanks, I'll try this if I get another replacement device. This one has a dead pixel in it.
I want to root my htc desire x and I more or less followed this - https://www.youtube.com/watch?v=0zdhyDky2MI and have so fare unlocked the bootloader.
At this moment I got twrp-2.6.0.0-protou.img installed.
https://twrp.me/devices/htcdesirex.html
I installed the latest version of supersu through twrp recovery. I did also give the install instructions on the twrp webpage a go but to no avail.
http://forum.xda-developers.com/showthread.php?t=1538053
When i open supersu on the phone I get this error message (loosely translated from danish).
"no binary su program file installed and supersu cannot install one this is a problem"
http://forums.androidcentral.com/ht...uper-su-installation-failed-how-do-i-fix.html
http://forums.androidcentral.com/an...-binary-installed-supersu-cannot-install.html
I do not have root. When I install supersu with twrp recovery mode it delivers a successful message at the end of install however I see no text in the twrp terminal/console during the install of supersu.
I have android-tools installed on my distribution which delivers fastboot as well as ADB. I have not setup SDK and am wondering if that is coursing issues. Though I get no such error messages.
No need to mess yourself with SuperSU as it is included in the ROM. Pick a ROM of your choice (i.e. Vimiro) and install. I assume you are S-ON (look at the bootloader in top). If so, you need to pick the kernel out of the ROM (open the package with Winrar) and take out boot.img. Flash manually as you flashed TWRP: fastboot flash boot boot.img. Then install ROM-package.
I don't particularly want to install a custom ROM. Do I have to?
What I want to achieve is to be able to move or remove some of the bundled apps, e.g. chrome - in an effort to free up storage, to an ext formatted partition on the sd-card.
techgage.com/article/moving_your_non-movable_android_apps_to_an_sd_card
It is not especially needed but handy You discovered already the SuperSu thread, maybo the solution is over there? Sorry, can't help you on SU problems. If nothing helps give another ROM a try (after backup). Most of the ROM's have nice features (also with custom kernel) and a installer on which you can select apps to install or not.
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!