I'm having problems installing any of the franco kernel through twrp 2.6 the latest twrp anyways when I install the zip file it fails. I'm running 9/4 pac also though i don't think that would have anything to do with it failing i tried the 182 and 178 i believe also the jj ones to any help thanks. Oh also i saw the iso files i believe but thought they had to be zipped to install through recovery so maybe that way would work however you install them with the iso thanks again
spriteboost said:
I'm having problems installing any of the franco kernel through twrp 2.6 the latest twrp anyways when I install the zip file it fails. I'm running 9/4 pac also though i don't think that would have anything to do with it failing i tried the 182 and 178 i believe also the jj ones to any help thanks. Oh also i saw the iso files i believe but thought they had to be zipped to install through recovery so maybe that way would work however you install them with the iso thanks again
Click to expand...
Click to collapse
iso files.. for a kernel? what did you actually download? its not a kernel for sure.
simms22 said:
iso files.. for a kernel? what did you actually download? its not a kernel for sure.
Click to expand...
Click to collapse
sorry not iso. I didn't download the img file and meant img file. I only downloaded the zip file from http://forum.xda-developers.com/showthread.php?t=2002782 I first thought it was my recovery was out of date so updated twrp which got me nothing and took forever because goomanager didn't do it so had to use nexus root tool kitv1.7.2 finally got that updated and still the zip file fails also tried the lte zip from http://forum.xda-developers.com/showthread.php?t=2358931 to have lte when and if it ever rolls out in my area but that ones not important plus i think pac's rom has it automatically in it because when i dialed *#*#4636#*#* lte is an option.
Anyways the problems with the zip file when i install it or try to that is it fails with 182 the jj file to and the 178 and jj file don't know what i'm doing wrong and it my mistake again img not iso.
spriteboost said:
sorry not iso. I didn't download the img file and meant img file. I only downloaded the zip file from http://forum.xda-developers.com/showthread.php?t=2002782 I first thought it was my recovery was out of date so updated twrp which got me nothing and took forever because goomanager didn't do it so had to use nexus root tool kitv1.7.2 finally got that updated and still the zip file fails also tried the lte zip from http://forum.xda-developers.com/showthread.php?t=2358931 to have lte when and if it ever rolls out in my area but that ones not important plus i think pac's rom has it automatically in it because when i dialed *#*#4636#*#* lte is an option.
Anyways the problems with the zip file when i install it or try to that is it fails with 182 the jj file to and the 178 and jj file don't know what i'm doing wrong and it my mistake again img not iso.
Click to expand...
Click to collapse
you cant flash img files via recovery.. you either flash it via fastboot or through apps that flash it via fasrboot/terminal for you.
simms22 said:
you cant flash img files via recovery.. you either flash it via fastboot or through apps that flash it via fasrboot/terminal for you.
Click to expand...
Click to collapse
Thanks tried flashing the img file with franco's kernel updater and got a bootloop idk why this is impossible for my phone right now my kernels 3.4.0-perf-g0b3e615 do i have to uninstall it first somehow?
also when i try installing it through twrp it says zip verification fail :-\
spriteboost said:
Thanks tried flashing the img file with franco's kernel updater and got a bootloop idk why this is impossible for my phone right now my kernels 3.4.0-perf-g0b3e615 do i have to uninstall it first somehow?
also when i try installing it through twrp it says zip verification fail :-\
Click to expand...
Click to collapse
I have the same issue with my nexus 4. Installed jelly bam, then had to update tarp to 2.6, yet it still won't flash any version of Franco kernel. Yes they are zip files and from the Dev directly. It gives me zip verification failed so I toggled verify zip signature and it said success. I wipe cache again and reboot. Now I am stuck with with the white Google logo. So I just reinstall jelly bam to get back to a working kernel. I have yet to flash cm to see if a different recovery works, or if it's a problem with the kernel or even jelly bam
SOLVED
I changed the recovery from twrp to cwm and then flashed it. cwm said it worked, but when i wiped cache and rebooted, im still stuck on the white google logo. Looking at your kernel, im assuming you too have jelly bam installed.
It seems you have to manually install it. Download the img file you want off here (use jss versions if you are on jellybam 10.2+)
go to fastboot mode
fastboot flash boot kernel_name.img
this seems to have worked for me. why it has to be this way; i have no idea.
why do you wipe cache? try without wiping!
Gesendet von meinem Nexus 4 mit Tapatalk 4
Its just a habit. Can that actually be the issue? Also I did not check, but maybe the reason it said "success" was because file signature verification was off. Twrp said it worked when I turned it off, so that could be why cwm said successful too
Sent from my Nexus 4 using XDA Premium 4 mobile app
Related
Video Provided by qbking77: http://www.youtube.com/watch?v=jWOLEXqAeCc
Will update the process into a more east to read format as soon as I can.
This isnt a question anymore because the method I will explain below works perfectly. Thanks to Gjones77, Stilesja, marcasant, Mkasik, xBTx and chrisott9628 as well as the acs team for providing the tools needed to root the OTA.
first you need to install the OTA either through the OTA method or through the Google link method.
Next you need to go to the ACS forums and Download the ACS recovery 1.0.0.5.tar.md5 file, http://chris41g.devphone.org/index.php?dir=Epic%2FACSRecovery%2F
You will need this file as well http://downloads.androidsu.com/superuser/su-3.0-efgh-signed.zip
Edit: see the 2 options below first so that you can retain CWM on your phone after reboot as samsung put a script in their kernel that will flush it out after reboot.
You will also need to have the latest version of Odin, Odin3 v1.85.
1) confirm you have gingerbread EI22.
2) download the 2 files above (you can use CWM purple version as well if you dont want the acs Recovery.)
3) Put the su-3.0-efgh-signed.zip file onto your sdcard and turn off the phone.
4) Boot into Download mode by holding the 1 key on the keyboard and the power key
5) open odin and connect the phone to the computer, one of the ID:com boxes will light up to confirm it is connected.
6) put the ACSrecovery.tar.md5 file into the PDA area of odin, make sure everything is uncheck except Auto-reboot and hit start.
7) if done correctly your phone should reboot directly into ACS recovery mode.
8) once in recovery flash the Su-***** .zip file then reboot the phone.
9) If CWM does not stick due to the added script Samsung embedded in the phone kernel you should see below. There are thus far, 2 possible options, Option 1 will give you the Keyboard fix with a relatively Stock experience and Option 2 will give you a Deodexed Rom, nubernal, the keyboard fix and the GPS fix.
Thought id add something to this first:
from gjones77:
gjones77 said:
***UPDATE***
Apparently Samsung included a script that reflashes the stock recovery upon boot, so if you install a custom recovery (ACS or CWM) it will overwrite it upon boot.
Pretty freaking sneaky I gotta say...
Click to expand...
Click to collapse
(Option 1)
Stilesja has a fix for this, I can now confirm this works as I have tried it out my self.
stilesja said:
Ok, I have found a Fix so that Clockwork Sticks
First Odin Mkasik's EI22 Keyboard fix Kernel (PDA - Only check Auto Reboot)
http://forum.xda-developers.com/showthread.php?t=1307980
Then Odin Purple Clockwork.
Now it sticks for me.
Click to expand...
Click to collapse
(Option 2)
You can also make your CWM override the built in Samsung issue as well as add the nubernal. To do this, follow the steps up until you get into ACS recovery or CWM and flash the .zip in this post: http://forum.xda-developers.com/showthread.php?t=1339579 rather than the Su.zip file. This will completely fix your GPS and CWM problems as well as deodex the EI22 version you have.
***UPDATE***
Apparently Samsung included a script that reflashes the stock recovery upon boot, so if you install a custom recovery (ACS or CWM) it will overwrite it upon boot.
Pretty freaking sneaky I gotta say...
gjones77 said:
Yes, I used Odin to flash CWM and then flashed the su zip, I'm rooted and up and running fine.
Click to expand...
Click to collapse
Which version of CWM?
Milkman00 said:
Which version of CWM?
Click to expand...
Click to collapse
I used ACS CWM4 and it worked without issue.
so just flash purple over ota and you can then flash SU.zip? Cool thanks.
Does the ACS CWM go in PDA or Phone in Oden?
Migital Warfare said:
Does the ACS CWM go in PDA or Phone in Oden?
Click to expand...
Click to collapse
I used PDA.
I updated Superuser in the market and lost root capabilities. Uninstalled the update and it has worked fine.
I just noticed that metalblaster said "so just flash purple" after chrisott9628 said to use the ACS CWM. Does it matter which one you use?
i just assumed purple because it was odin that was being used to add it.
I tried to download the .zip of the ACS recovery, but got file not found. Anyone have a working copy/link/mirror?
Milkman00 said:
I tried to download the .zip of the ACS recovery, but got file not found. Anyone have a working copy/link/mirror?
Click to expand...
Click to collapse
http://chris41g.devphone.org/index.php?dir=Epic/ACSRecovery/
I can confirm that this doesnt not infact work for me at least. Ive tryed every odin version as well as renaming the file to a .Tar rather than .md5 as well as using the .md5 and the .zip files. Its no use.
Actually as soon as i posted this i tried the file posted above to try to get CWM and it worked like a charm. You need to place the .md5 file into the pda portion of odin3 v1.85 and check only auto reboot. If done correctly the phoen should boot into CWM directly and then you can flash the Su.zip file to gain root.
***NOOB ALERT***
I asked this in another thread, but its way more appropriate here:
Would Gingerbreak work on EI22? I used it last week to root EC05 and flash Toadlife's EH17 stability rom. It installs a slightly older version of CWM (I think), but it also installs Superuser.
Just wondering.
rvr9999 said:
***NOOB ALERT***
I asked this in another thread, but its way more appropriate here:
Would Gingerbreak work on EI22? I used it last week to root EC05 and flash Toadlife's EH17 stability rom. It installs a slightly older version of CWM (I think), but it also installs Superuser.
Just wondering.
Click to expand...
Click to collapse
No, Gingerbreak hasn't worked since v2.3.3 I think/
Both cwm purple and acs recovery should work without any issues.
Sent from my SPH-D700 using xda premium
Dang, too bad. It was super easy to use. I am new to rooting, and it made it a lot less scary.
Milkman00 said:
I tried to download the .zip of the ACS recovery, but got file not found. Anyone have a working copy/link/mirror?
Click to expand...
Click to collapse
...attached.
If i'm understanding this right, put thw cwm/acs recovery on the sdcard, reboot into stock recovery and update? Do I need to rename the zips?
metalblaster said:
I can confirm that this doesnt not infact work for me at least. Ive tryed every odin version as well as renaming the file to a .Tar rather than .md5 as well as using the .md5 and the .zip files. Its no use.
Actually as soon as i posted this i tried the file posted above to try to get CWM and it worked like a charm. You need to place the .md5 file into the pda portion of odin3 v1.85 and check only auto reboot. If done correctly the phoen should boot into CWM directly and then you can flash the Su.zip file to gain root.
Click to expand...
Click to collapse
I tried it and when rebooting, it reboots into the phone (not into CWM). I reboot the phone with the 3 finger salute and it is still the stock recovery. Odin shows that the recovery flash was successful.
EDIT - Nevermind - was using a downlevel ODIN.
im just letting the S3 users know that i have now got an s3 and will begin developing for s3 now!
starting with my first creation for the s3, i have made a flashable .zip file that flashes the selected recovery, so no need for re-downloading and re-flashing, simply flash the .zip, then aroma will open asking whitch recovery to flash then it will flash then reboot into the new recovery!
coming soon!
ricky310711 said:
im just letting the S3 users know that i have now got an s3 and will begin developing for s3 now!
starting with my first creation for the s3, i have made a flashable .zip file that flashes the selected recovery, so no need for re-downloading and re-flashing, simply flash the .zip, then aroma will open asking whitch recovery to flash then it will flash then reboot into the new recovery!
coming soon!
Click to expand...
Click to collapse
Looking forward, it will be useful, any information about the development state?
mirroalex said:
Looking forward will be useful, any information about the development state?
Click to expand...
Click to collapse
i actually just amde the packages and tested each of them, all ive gotta do is configure aroma and we will be up and running by tommorow arvo!
will it automatically download the newest version of the selected recovery?
chrismast said:
will it automatically download the newest version of the selected recovery?
Click to expand...
Click to collapse
Its a flashable .zip package, I will just gather the latest recoveries and update every month
ricky310711 said:
Its a flashable .zip package, I will just gather the latest recoveries and update every month
Click to expand...
Click to collapse
ok, good luck with it!
personally I do not see the point yet as I just can download the single recovery (there is anyway not that much choice) and flash it but I am sure there are users that will appreciate an Aroma installer.
chrismast said:
ok, good luck with it!
personally I do not see the point yet as I just can download the single recovery (there is anyway not that much choice) and flash it but I am sure there are users that will appreciate an Aroma installer.
Click to expand...
Click to collapse
The point of this being that some recoveries cant flash certain .zip files... eg twrp 2.5.0.0 cannot flash .zip files with aroma, this is also a pachage to help developers!
ricky310711 said:
The point of this being that some recoveries cant flash certain .zip files... eg twrp 2.5.0.0 cannot flash .zip files with aroma, this is also a pachage to help developers!
Click to expand...
Click to collapse
ah ok, didn't know that, anyway as I said for certain people surly helpful! Good luck!
An app that could connect to a central repository and download the latest versions would be great. Then using the same method stweaks by siyah uses to "hijack" recovery or temp boot would make more sense to me.
That way you open app, choose recovery to boot and flash your zips. Then boot back to android...
Rather than boot recovery, flash zip,,choose recovery, flash zip...
Or just use philz recovery and be able to flash all zips anyway
Sent from my GT-I9300 using Tapatalk 2
rootSU said:
An app that could connect to a central repository and download the latest versions would be great. Then using the same method stweaks by siyah uses to "hijack" recovery or temp boot would make more sense to me.
That way you open app, choose recovery to boot and flash your zips. Then boot back to android...
Rather than boot recovery, flash zip,,choose recovery, flash zip...
Or just use philz recovery and be able to flash all zips anyway
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Seems legit, although I do not have time to make a . Apk of it..
Also keep in mibd what if you didnt have data connection, or yet couldnt even boot...
Hi, any help resolving this would be really appreciated. I have updated my Nexus 4 to Android 4.3 by installing through CWM. The upgrade worked fine however I cannot flash the SuperSU zip afterwards. I am using the experimental version released specifically for 4.3 however I just get the message: unable to open 'file', installation aborted (bad). I have tried to redownload in case it was a corrupt zip but I just get the same result. I have also tried reflashing 4.3 but this doesn't make a difference either.The old SuperSU is still installed but states that it has no binaries if I try to open it.
Sorry if this has been covered elsewhere but I have been searching all evening for a solution.
Sam
shardy said:
Hi, any help resolving this would be really appreciated. I have updated my Nexus 4 to Android 4.3 by installing through CWM. The upgrade worked fine however I cannot flash the SuperSU zip afterwards. I am using the experimental version released specifically for 4.3 however I just get the message: unable to open 'file', installation aborted (bad). I have tried to redownload in case it was a corrupt zip but I just get the same result. I have also tried reflashing 4.3 but this doesn't make a difference either.The old SuperSU is still installed but states that it has no binaries if I try to open it.
Sorry if this has been covered elsewhere but I have been searching all evening for a solution.
Sam
Click to expand...
Click to collapse
Did you try flashing the latest supersu? I've flashed this one https://www.dropbox.com/s/p97y9pn4tie9iyi/UPDATE-SuperSU-v1.43.zip pressed "go back" when recovery asked to fix recovery or something like that and it works just fine
Ah, The version I have is 1.41 not 1.43, although I guess I downloaded from an older post in the blog. Thank you, hopefully that will work.
Sent from my Nexus 4 using xda app-developers app
Unfortunately this still hasn't worked, I have tried v1.43 of SuperSU, still failes. I have also changed my recovery from CWM to TWRP but this also fails to flash SuperSU v1.43 with the same error. Any other suggestions?
I think I have resolved this now, I had to sideload the SuperSU file on instead, so far so good.
Thanks.
shardy said:
I think I have resolved this now, I had to sideload the SuperSU file on instead, so far so good.
Thanks.
Click to expand...
Click to collapse
I have the same issue. I also notice root explorer can't look inside zip files. It seems like whatever custom recoveries and other apps use to extract zip files is busted/removed after our 4.3 update. Is this a busybox issue? Side loading might use extraction tools on the computer instead?
I resolved this too. It turned out the super SU zip file I had grabbed for 1.43 wasn't the normal CWM/TWRP recovery package. When I looked at the zip file on my computer I noticed it contained another compressed file. I waited a few days root-less and then noticed that super SU 1.51 had been released. I used this file and it worked like it should have the first time. This package looks like the normal recovery flashable file, with the manifest and directory structure it should have. So either I grabbed the wrong file or there was a moment in time when the chainfire's site was dishing out bad files.
Glad it's working now, root is restored.
shardy said:
I think I have resolved this now, I had to sideload the SuperSU file on instead, so far so good.
Thanks.
Click to expand...
Click to collapse
Can you elaborate, as to what exactly you did to restore the root?
I'm trying to upgrade to the latest twrp but can't seem to flash it.
I've downloaded the .zip but when ibflash with current twrp 2.7.0 it tells me it can't open the zip?
I've also tried flashing with flashify to no avail? Any help?
Valiceemo said:
I'm trying to upgrade to the latest twrp but can't seem to flash it.
I've downloaded the .zip but when ibflash with current twrp 2.7.0 it tells me it can't open the zip?
I've also tried flashing with flashify to no avail? Any help?
Click to expand...
Click to collapse
i would redownload the zip and check that the file size is correct. if it's a corrupted download it wont flash. happened to me several times.
kbkang said:
i would redownload the zip and check that the file size is correct. if it's a corrupted download it wont flash. happened to me several times.
Click to expand...
Click to collapse
Thanks. Got it done now. Must have been a dodgy download. Took several attempts to get it too D/L properly.
Thanks
Valiceemo said:
Thanks. Got it done now. Must have been a dodgy download. Took several attempts to get it too D/L properly.
Thanks
Click to expand...
Click to collapse
while i was testing stuff i found....
from 4.2.2 using different way (some tool) to get recovery (not autorec) i could update to official twrp 2.8.x.x.
using 4.4.2 using autorec cant update to official twrp 2.8.x.x.
but can update to the custom 2.8.x.x availabe here with f2fs version.
I have a Nexus 6p with android 8.1.0 and i was using the pixel 2 mod for nexus 6p, which i installed via TWRP flashing the zip file. I was trying more custom roms, but any worked, so i came back to the pixel 2 mod, but then, when i oppened Super SU, it stated something about the binaries. The solution i found was to install a SuperSU zip file via TWRP, which i did, but after installing it, my nexus wouldnt pass the boot animation, it wasnt acting like the infamous "Bootloop of death" the n6p and n5 has, it just didnt passed the boot animation, so i researched and saw that the solution was to delete de SuperSu file with the TWRP file manager, but whenever i deleted the file, wiped cache and booted again, it wont pass the bootanimation, and when i came back to twrp, SuperSU files were still there, and it seems i cannot erease them. What can I do? I tried restoring the phone with a back up i had, but nothing, flashing again the Pixel 2 mod for nexus 6p and anything.. what can i do?
@ernestomn98 just flash the boot.img of whatever ROM/Firmware you are on. You should use Magisk it's much easier to use and passes safety net so can use Google pay and such.
Exodusche said:
@ernestomn98 just flash the boot.img of whatever ROM/Firmware you are on. You should use Magisk it's much easier to use and passes safety net so can use Google pay and such.
Click to expand...
Click to collapse
Hmmmmm is it really that easy? But where is that img? Because i installed it via zip file
Thank you for responding! Thank you for the suggestion of Magisk as well.
ernestomn98 said:
Hmmmmm is it really that easy? But where is that img? Because i installed it via zip file
Thank you for responding! Thank you for the suggestion of Magisk as well.
Click to expand...
Click to collapse
No problem and yes it's that easy. If the ROM zip is on your computer can just open it, copy the boot.img, then paste outside the folder. You can do that also with good file Xplorer on your phone but yours is not booting so no good. Transfer the boot.img to your phone. Boot into TWRP select install from zip . You will have to press the button to switch from zip to image file. Then select boot.img and flash it to boot section. Now your back to original and can flash Magisk zip. An easier method would be to just dirty flash the ROM your on but what fun is that. ??