My problem is, when i try to install superSU on any rom it just gives me the error and tells me to reboot again and again. Well i got that covered by flashing the zip but when i install Rom updates e.x CM 10.2 nightlies, it deletes superSU but all my other apps are still in tact?
Anyone have a solution???
When you flash SuperSU it will go to the system partition so updates will wipe it BUT you can then just go to the Play Store and download SuperSU from there.
What is actually telling you to reboot and what install method was that?
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
When you flash SuperSU it will go to the system partition so updates will wipe it BUT you can then just go to the Play Store and download SuperSU from there.
What is actually telling you to reboot and what install method was that?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Hmm wierd after getting the "Installation failed" message about 10 times it finally installed from the app :s
Related
Just followed instructions for CM7 on eemc with nightly 106 and OC kernel.
Rom Manager says no superuser? So I installed from market and superuser says there's updated binary but can't complete auto install. But it put a .zip on sd card and said to instal via recovery... which puts me back to step 1 which was trying to use ROM manager to write recovery?
What went wrong here and how to fix? Didn't have any of these problems when I did my son's nc the same way last week.
Sent from my SPH-D700 using XDA Premium App
Don't know how to install cwm w/o rom manager. Put my card back to cwm img and tried to flash the updated binary.... says bad?
Guess there's something broke with 106 and su.
Started afresh with cm 102 (as recommended), gapps, and Oc kernel. All is well...
Zeam Launcher
Nook tweeks
Netflix
Netflix fixer
...good for now!
Sent from my SPH-D700 using XDA Premium App
Had the same problem here. I'm away from my Nook right now, but I fixed it by downloading Superuser from the Extras menu in RomManager, then rebooting to recovery via the normal shutdown screen and applying it manually. The zip is in the clockwork folder, in the goo-inside.me folder. Just select it from "*choose zip" menu and reboot.
I may have the details slightly wrong.
Superuser definitely got left out of #106.
Aloha,
cap
Thanks. I had to do the same to get su.
Wondering why is left out of 106.
I am having the same problem... except every time I try to download the new SU binary it says that there was an error and that I should boot into recovery blahblahblah, but when I do it says that there was an error installing the .zip file. What else can I do?
Knightsofwar210 said:
I am having the same problem... except every time I try to download the new SU binary it says that there was an error and that I should boot into recovery blahblahblah, but when I do it says that there was an error installing the .zip file. What else can I do?
Click to expand...
Click to collapse
I'm still on 102 no prob. They discuss this issue on the cm thread. Try doing it from rom manager.
Download Rom, extras, superuser...
Then instal from cwm under clockwork/downloads/...and some sub directory.
Sent from my NookColor using XDA Premium App
Ahh thank you, I couldn't find it before.
I have CWM as my recovery and PA on the device.
I got a message today saying a new PA is out and grabbed the zip from goo manager.
Now I understand with goo manager you need a openscript recovery to use that to update though it appears CWM recovery doesn't use that but TWP does.
In CM10 you go to the settings and update from the OTA section in the about tab.
PA doesn't use those OTA updates it seems when CM does.
I would still be using CM but was getting a lot of crashes on M3 so I decided to try a few roms and currently running PA.
So what's the best way to update can I just flash the rom over the top of the current system without formatting first?
Thanks
drguild said:
I have CWM as my recovery and PA on the device.
I got a message today saying a new PA is out and grabbed the zip from goo manager.
Now I understand with goo manager you need a openscript recovery to use that to update though it appears CWM recovery doesn't use that but TWP does.
In CM10 you go to the settings and update from the OTA section in the about tab.
PA doesn't use those OTA updates it seems when CM does.
I would still be using CM but was getting a lot of crashes on M3 so I decided to try a few roms and currently running PA.
So what's the best way to update can I just flash the rom over the top of the current system without formatting first?
Thanks
Click to expand...
Click to collapse
Move the zip containing the update to /sdcard (your root documents directory, where all your files are stored- ANdroid, Data, DCIM, Downloads, etc), reboot to CWM, flash zip, select zip and go. That should be all you have to do. :good:
It worked fine for me using CWM and the usual method to update (recovery->install zip->select from SD). The only problem I'm having is a DPI issue in the launcher. Make sure to install the newest gapps as well and clear the cache.
Sent from my Nexus 10
purmou said:
It worked fine for me using CWM and the usual method to update (recovery->install zip->select from SD). The only problem I'm having is a DPI issue in the launcher. Make sure to install the newest gapps as well and clear the cache.
Sent from my Nexus 10
Click to expand...
Click to collapse
Cheers guys I read you can just flash over the top in CWM but just wanted to confirm it.
drguild said:
Cheers guys I read you can just flash over the top in CWM but just wanted to confirm it.
Click to expand...
Click to collapse
Correct.
I rooted my phone with the nexus tool kit (which installed clockworkmod. Then i used ROM Manager to flash cyanogenmod RC 4.. I have tried this a couple of times and my pone doesnt boot up from the cyanogenmod logo screen. Sometimes, it gives me an error that it failed to to launch setup.. Please help.
Right now, my phone is running the unlocked and rooted running the stock android 4.2.2
try to wipe the partitions from the recovery...factory reset it.....then flash cm 10.1 and g-apps.....from the recovery itself
am running rc4....perfectly fine...
djpry said:
try to wipe the partitions from the recovery...factory reset it.....then flash cm 10.1 and g-apps.....from the recovery itself
am running rc4....perfectly fine...
Click to expand...
Click to collapse
I tired that aswell... but it gives me an error which says "unfortunately, the process com.google.process.gapps has stopped"..
what do you recommend?
riki2 said:
I rooted my phone with the nexus tool kit (which installed clockworkmod. Then i used ROM Manager to flash cyanogenmod RC 4.. I have tried this a couple of times and my pone doesnt boot up from the cyanogenmod logo screen. Sometimes, it gives me an error that it failed to to launch setup.. Please help.
Right now, my phone is running the unlocked and rooted running the stock android 4.2.2
Click to expand...
Click to collapse
If you have CWM or TWRP recovery installed do NOT use Rom Manager and uninstall it. It conflicts with CWM and causes errors. Download CM from here http://get.cm/?device=mako&type= the first time, after that you can update and flash from within the rom itself in settings/ about the phone.
riki2 said:
I tired that aswell... but it gives me an error which says "unfortunately, the process com.google.process.gapps has stopped"..
what do you recommend?
Click to expand...
Click to collapse
the gapps version i have download is 4.1.2... if thats wrong. can you give me a link to download gapps from?
That's wrong gasps. Go to goo.im and download 4.2.2 gapps
Sent from my Nexus 4 using xda app-developers app
riki2 said:
the gapps version i have download is 4.1.2... if thats wrong. can you give me a link to download gapps from?
Click to expand...
Click to collapse
Dude read up first before you kill your phone, why the hell are you flashing all kind of stuff if you have absolutely no idea what you are doing?
gee2012 said:
Dude read up first before you kill your phone, why the hell are you flashing all kind of stuff if you have absolutely no idea what you are doing?
Click to expand...
Click to collapse
rom manager downloaded the gapps.. Can you recommend a source i could read? thanks
riki2 said:
rom manager downloaded the gapps.. Can you recommend a source i could read? thanks
Click to expand...
Click to collapse
Here
http://goo.im/gapps
Download gapps 4.2.2
Sent from my Nexus 4 using xda app-developers app
riki2 said:
rom manager downloaded the gapps.. Can you recommend a source i could read? thanks
Click to expand...
Click to collapse
Oke, i help you this once:
1. Uninstall Rom Manager, it serves no purpous anymore
2. Download RC4 from here http://get.cm/?device=mako&type=
3. Download Gapps from here http://goo.im/gapps/gapps-jb-20130301-signed.zip
4. Go in recovery and wipe data, cache, dalvik cache and format system.
5. Flash CM rom and straight after that Gapps
6. Reboot and you`re done.
riki2 said:
I tired that aswell... but it gives me an error which says "unfortunately, the process com.google.process.gapps has stopped"..
what do you recommend?
Click to expand...
Click to collapse
1. uninstall rom manager....Not really required
2. factory reset your current rom
3.go to Cmw or any other recovery.
4.erase cache,d cache and system
5.fresh install....cm 10.1 rc4
6.flash gapps for jb
reboot from recovery
njoy cm goodness
Hi,
I installed TWRP and now, when I restart my nexus 7, it defaultly boots into TWRP. Is there a way to stop this and make nexus automaticaly boots into system? Because now, automatic updates are not working, cause when nexus reboots, it's in TWRP and update stops.
Thanks
In that case you most likely have a corruped boot partition and the kernel cannot be started. In hat case it's going automatically into recovery mode.
AndDiSa said:
In that case you most likely have a corruped boot partition and the kernel cannot be started. In hat case it's going automatically into recovery mode.
Click to expand...
Click to collapse
but when I choose reboot into system, it goes into system normally.
There is also a flag which says 'reboot to recovery', but this should be reset automatically when booting up the recovery. There is a chance that this flag will not get erased. What version of TWRP do you have installed?
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
There is also a flag which says 'reboot to recovery', but this should be reset automatically when booting up the recovery. There is a chance that this flag will not get erased. What version of TWRP do you have installed?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I have v2.6.3.0
Try to flash 2.6.3.1, as far as I remember there were some issues with 2.6.3.0 and KitKat.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Try to flash 2.6.3.1, as far as I remember there were some issues with 2.6.3.0 and KitKat.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
that's the point, I do not have kitkat yet, cause everytime I launch auto-update, nexus reboots into TWRP instead of installing update.
jonny_pasta said:
that's the point, I do not have kitkat yet, cause everytime I launch auto-update, nexus reboots into TWRP instead of installing update.
Click to expand...
Click to collapse
??? But if ypu have TWRP installed as recovery, it's normal that it is booting to TWRP to apply the update. Then from TWRP you need to select "apply the update" and after that you will have KitKat installed. Or didn't I understand you well? But be aware that you will loose TWRP by applying the OTA.
AndDiSa said:
??? But if ypu have TWRP installed as recovery, it's normal that it is booting to TWRP to apply the update. Then from TWRP you need to select "apply the update" and after that you will have KitKat installed. Or didn't I understand you well? But be aware that you will loose TWRP by applying the OTA.
Click to expand...
Click to collapse
there is no such thing as "apply the update", I can only choose "install" and go into memory and select the file. But I do not know where the file is, I found one in chache with some strange name (random string), but it sais, that it's not compatibile with my system.
I was running (and am after the restore) Android 4.3.1 slimBean jflteatt build.2official.
So my friend convinced me to try CM12 lolipop nightly.
I made a backup wiped everything and installed CM12 and the gapps.
upon boot after the instalation all the play services were crashing so we reinstalled CM 12 but without GAPPS and all was fine.
BUT now i CAN"T reboot my phone. Regardless of ROM (except stock) the att galaxy s4 gets stuck on the boot splash screen (the screen before the boot screen) The screen it gets stuck on looks like this: http://img18.imageshack.us/img18/8910/20120813002112.jpg
The screen used to look like this: http://2.bp.blogspot.com/-aCD7kATq-to/UaIBfYW5oKI/AAAAAAAAO88/ShlHR6459kk/s1600/boots4.gif
I have tried restoring and installing a clean ROM but that did not solve my problem. Only way for me to restore is to wipe everything, then format the data and the restore. I restored to stock TW MDL via a TWRP backup i have.
I am running TWRP 2.5.0.1 (I think). I am currently using the SlimRoms 3.4.0 kernal. I am rooted according to root checker.
Can someone please help me solve the reboot problem? (Could it have anything to do with Xposed?)
I would update twrp and try again. You have an old version.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I would update twrp and try again. You have an old version.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
i have 2.5.0.2, what do you suggest i update to ? (and how?)
I've been afraid to update anything because if it aint broke don't fix it.
Do you suggest TWRP 2.8.0.1 touch recovery [2014-09-12]
as this suggests?: http://forum.xda-developers.com/showthread.php?t=2413746
thank you for your reply.
sharpknight said:
i have 2.5.0.2, what do you suggest i update to ? (and how?)
I've been afraid to update anything because if it aint broke don't fix it.
Do you suggest TWRP 2.8.0.1 touch recovery [2014-09-12]
as this suggests?: http://forum.xda-developers.com/showthread.php?t=2413746
thank you for your reply.
Click to expand...
Click to collapse
Flashing roms in an old version of twrp won't work. If your rooted, which I assume you are, get flashify forum the play store. Then download the latest twrp.img and flash it in flashify. http://dl.twrp.me/jflteatt/ The link is for the at&t s4, if you have a different variant you'll need a different image.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Flashing roms in an old version of twrp won't work. If your rooted, which I assume you are, get flashify forum the play store. Then download the latest twrp.img and flash it in flashify. http://dl.twrp.me/jflteatt/ The link is for the at&t s4, if you have a different variant you'll need a different image.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
ok i have succesfully updated to TWRP 2.8.4.0 (newest on the link you provided) via flashify as you suggested.
What do i do now? BTW really appreciate the help.
sharpknight said:
ok i have succesfully updated to TWRP 2.8.4.0 (newest on the link you provided) via flashify as you suggested.
What do i do now? BTW really appreciate the help.
Click to expand...
Click to collapse
If you want cm12 download the zip and gapps and flash those in twrp. Do the default wipe in twrp first. Note, it will wipe your apps but if you have had Google backup your device it will restore them.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
If you want cm12 download the zip and gapps and flash those in twrp. Do the default wipe in twrp first. Note, it will wipe your apps but if you have had Google backup your device it will restore them.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I don't wan't CM12 at this moment. I just need to have old SlimRom working without the reboot issue. too much business related data there at the moment. So should i reinstall slimRom and the restore that data maybe?
Could it be the slimKernal? Ive had the problem where it gets stuck at that screen for a long time now but id just do a batery pull and turn it on and it would work after 2-3 tries.