I flashed untouched stock lollypop in my moto x ghost...it flashed well,,but the problem is SuperSU is not installing,I tried both ways,via twrp and direct install from playstore,even not worked...without SuperSU,,phone can't be rooted...plz solve my problem..
Spiderman1992 said:
I flashed untouched stock lollypop in my moto x ghost...it flashed well,,but the problem is SuperSU is not installing,I tried both ways,via twrp and direct install from playstore,even not worked...without SuperSU,,phone can't be rooted...plz solve my problem..
Click to expand...
Click to collapse
You must have to reinstall the ROM
Do this
Go to recovery
Make full wipes
Install SuperSU
Install the rom untouched
Install SuperSU again
Wipe cache and dalvik
Reboot
So,before rom installation also,,SuperSU would must be flash??i thought only rom installation after....thanks dude...I will try
Spiderman1992 said:
So,before rom installation also,,SuperSU would must be flash??i thought only rom installation after....thanks dude...I will try
Click to expand...
Click to collapse
Yep, the SU must be installed before in that ROM, is a bug. Usually it must be installed after but in this case not.
Thank you..it worked
YedanyXD said:
Yep, the SU must be installed before in that ROM, is a bug. Usually it must be installed after but in this case not.
Click to expand...
Click to collapse
Thanks bro...it worked..
Related
Hey guys how are u all
I recently update my phone throw ota update to 4.3
And now i dont find supersu anywhere.
Can anyone help please how i can install supersu on my htc one m7 android 4.3
Aisfkhan said:
Hey guys how are u all
I recently update my phone throw ota update to 4.3
And now i dont find supersu anywhere.
Can anyone help please how i can install supersu on my htc one m7 android 4.3
Click to expand...
Click to collapse
You could flash this in custom recovery: http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
thanks
nkk71 said:
You could flash this in custom recovery: http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
Click to expand...
Click to collapse
Thankyou so much i installed it and now supersu is working properly
Aisfkhan said:
Thankyou so much i installed it and now supersu is working properly
Click to expand...
Click to collapse
:good: No problem
Not sure what to do
Hey all,
I'm new to this and was wondering if I could get a little help. I was trying to flash supersu through twrp but it failed. Are there any steps I should take? I have an HTC one. I am running on a android 4.3 Rom. Any help is appreciated. Thanks!!
Thex13laZe said:
Hey all,
I'm new to this and was wondering if I could get a little help. I was trying to flash supersu through twrp but it failed. Are there any steps I should take? I have an HTC one. I am running on a android 4.3 Rom. Any help is appreciated. Thanks!!
Click to expand...
Click to collapse
Hey can i know the full procedure which u did to install supersu??
Aisfkhan said:
Hey can i know the full procedure which u did to install supersu??
Click to expand...
Click to collapse
I downloaded the zip file, then booted into recovery then I wiped dalvik and cache then I went to install and swiped it then it failed.
Thex13laZe said:
I downloaded the zip file, then booted into recovery then I wiped dalvik and cache then I went to install and swiped it then it failed.
Click to expand...
Click to collapse
Dude simply download zip file(link in above post) then boot into recovery mood go to install and then from sd card chose zip file which u downloaded and it will install perfectly...and dont wipe anything after installation restart ur mobile u will see the supersu app in app drawer
Aisfkhan said:
Dude simply download zip file(link in above post) then boot into recovery mood go to install and then from sd card chose zip file which u downloaded and it will install perfectly...and dont wipe anything after installation restart ur mobile u will see the supersu app in app drawer
Click to expand...
Click to collapse
It's still not working. When I swipe to install it says it failed. Then it gives me the option to reboot, wipe or back. I click reboot then it tells me superuser permissions are messed up would I like to fix them. I click yes swipe then I'm back where I started. With superuser and not supersu.
Thex13laZe said:
It's still not working. When I swipe to install it says it failed. Then it gives me the option to reboot, wipe or back. I click reboot then it tells me superuser permissions are messed up would I like to fix them. I click yes swipe then I'm back where I started. With superuser and not supersu.
Click to expand...
Click to collapse
Flash cwm recovery and try to install supersu from cwm.
Aisfkhan said:
Flash cwm recovery and try to install supersu from cwm.
Click to expand...
Click to collapse
Yea, I was thinking that. I'm not sure how to use cmw just yet. I'll try it soon, but not now. Thanks anyways.
I installed thislauncher , after reboot i get this message every few seconds the process com.android.systemui has stopped. I also uninstalled this app, no luck. Any ideas :crying:
thalada said:
I installed thislauncher , after reboot i get this message every few seconds the process com.android.systemui has stopped. I also uninstalled this app, no luck. Any ideas :crying:
Click to expand...
Click to collapse
Are you rooted? If you are, try install from custom recovery a stock launcher or a different one if you're rooted with a custom recovery.
Hope that helps
thalada said:
I installed thislauncher , after reboot i get this message every few seconds the process com.android.systemui has stopped. I also uninstalled this app, no luck. Any ideas :crying:
Click to expand...
Click to collapse
Are you using stock ROM? If so, which firmware version do you use now? Are your devices rooted? Is it odex or de-odex?
EdwardUong said:
Are you rooted? If you are, try install from custom recovery a stock launcher or a different one if you're rooted with a custom recovery.
Hope that helps
Click to expand...
Click to collapse
omegahanggara said:
Are you using stock ROM? If so, which firmware version do you use now? Are your devices rooted? Is it odex or de-odex?
Click to expand...
Click to collapse
Yes, i am rooted. I am on monxDIFIED ★ Honam1Z™ (442.757) BEST AROMA [v06-02].
Can you link me to the flashable zip of stock launcher?
thalada said:
Yes, i am rooted. I am on monxDIFIED ★ Honam1Z™ (442.757) BEST AROMA [v06-02].
Can you link me to the flashable zip of stock launcher?
Click to expand...
Click to collapse
monxDIFIED installer is flashable zip formated, which is you can flash this installer through recovery such as CWM. If you have the installer, just flash the package through recovery, wipe cache + dalvik cache, and reboot your device. If you lost the installer, get it here
I'm using odex ROM, which mean it won't be compatible with your ROM (even we're on the same stock ROM). Using other flashable deodex system is not recommended since you're using Modded Stock ROM, which mean you might lost some feature from monxDIFIED ROM.
omegahanggara said:
monxDIFIED installer is flashable zip formated, which is you can flash this installer through recovery such as CWM. If you have the installer, just flash the package through recovery, wipe cache + dalvik cache, and reboot your device. If you lost the installer, get it here
I'm using odex ROM, which mean it won't be compatible with your ROM (even we're on the same stock ROM). Using other flashable deodex system is not recommended since you're using Modded Stock ROM, which mean you might lost some feature from monxDIFIED ROM.
Click to expand...
Click to collapse
Already tried bro, no luck.
EDIT: It was an xposed module, which was causing this. Uninstalling the module, fixed the problem.
thalada said:
Already tried bro, no luck.
EDIT: It was an xposed module, which was causing this. Uninstalling the module, fixed the problem.
Click to expand...
Click to collapse
Best of luck, buddy :highfive:
thalada said:
Already tried bro, no luck.
EDIT: It was an xposed module, which was causing this. Uninstalling the module, fixed the problem.
Click to expand...
Click to collapse
Could you please say how you uninstalled the module becouse i cant even get into xposed.
SowCrazy_ said:
Could you please say how you uninstalled the module becouse i cant even get into xposed.
Click to expand...
Click to collapse
Then uninstall xposed.
thalada which module you unistalled? I had the same problem and I'm looking for which of those I have is "indicted"
I want to install Marshmallow on my moto g. when i am going to install any ROM 6.0 it gets installed.
But next step when i flash gapps 6.0 then it says fail install.
what willl be solution for this?
I am using Philz recovery 6.0.2
tried Cynopop v4.5 Marshmallow Rom.
Gapps from OpenGapps type i tried - pico, mini ,nano
nothing worked.
I don't know what your problem is but here's a solution .
Install TWRP 2.8.6.0.
Clean Flash ROM and then flash Gapps.
Mostly you won't get any error.
Hope this helped.
sagar846 said:
I don't know what your problem is but here's a solution .
Install TWRP 2.8.6.0.
Clean Flash ROM and then flash Gapps.
Mostly you won't get any error.
Hope this helped.
Click to expand...
Click to collapse
Sagar I tried on TWRP 2.8.6.01 also.
TWRP didn't work on my mobile.
it restarts my mobile after installing single zip file. I don't know why. so i moved to Philz recovery.
any suggestion?
Are you rooted? Then you can flash TWRP through flashify app and see if it solves your issue.
If not then you'll have to restore to stock and follow the procedures to root and flash again.
FYI I did face this problem once but solved it by reverting to stock (I didn't intend to do this as a solution but it worked anyway).
sagar846 said:
Are you rooted? Then you can flash TWRP through flashify app and see if it solves your issue.
If not then you'll have to restore to stock and follow the procedures to root and flash again.
FYI I did face this problem once but solved it by reverting to stock (I didn't intend to do this as a solution but it worked anyway).
Click to expand...
Click to collapse
Sagar buddy Yes! I rooted!
I am using AICP 10.0 since 6-7 months. there is no problem of root.
Yeah Like I said I fixed it by fluke like I told you (you can try it if you want) but If you want a proper answer. Id suggest you wait for someone to know what's actually wrong. Also post your problem on The TWRP or Philz Thread . Stop Creating New threads for problems.
Keep XDA clean
shindesharad71 said:
Sagar buddy Yes! I rooted!
I am using AICP 10.0 since 6-7 months. there is no problem of root.
Click to expand...
Click to collapse
If u can send the screenshot of the error then I think so someone might help(I can too).
tra_dax
This phone was not rooted prior to being stuck at the boot screen. Actually, it wasn't event stuck at the boot screen. Instead, it turned on and off. I installed PhilZ recovery and was able to backup all files. Then I tried to flash different versions of CM without success. They all get stuck at the boot screen now. No more turning on and off. I also tried to clear cache, wipe dalvik something and reset to factory. Is there something else that can be done? What would be the most likely cause for the failure?
bfürbanane said:
This phone was not rooted prior to being stuck at the boot screen. Actually, it wasn't event stuck at the boot screen. Instead, it turned on and off. I installed PhilZ recovery and was able to backup all files. Then I tried to flash different versions of CM without success. They all get stuck at the boot screen now. No more turning on and off. I also tried to clear cache, wipe dalvik something and reset to factory. Is there something else that can be done? What would be the most likely cause for the failure?
Click to expand...
Click to collapse
Download Odin, using 3.04 or 3.07 for win 7,8,10
http://www74.zippyshare.com/v/18196321/file.html
Put the devices in download mode (Press volume Up + home + power) and install a stock firmware
http://www.sammobile.com/firmwares/database/GT-N7000/
Guide Odin n7000
http://forum.xda-developers.com/showthread.php?t=1424997
If you want to install a custom rom type CM11, CM12 or CM13 you have to install a kernel compatible with recovery
Install PhilZ recovery, then from recovery install a compatible kernel
Kernel CM11
https://www.androidfilehost.com/?fid=24052804347829437
Kernel CM12
http://forum.xda-developers.com/devdb/project/dl/?id=16862
After flashing the kernel do a
Data factory reset
Wipe cache
Wipe Dalvik/ART
Install ROM, install gapps
If it does not work
Data factory reset
Wipe cache
Wipe Dalvik/ART
Format system
Format cache
Format data
Install ROM, install gapps
panamera2011 said:
Download Odin, using 3.04 or 3.07 for win 7,8,10
http://www74.zippyshare.com/v/18196321/file.html
Put the devices in download mode (Press volume Up + home + power) and install a stock firmware
http://www.sammobile.com/firmwares/database/GT-N7000/
Guide Odin n7000
http://forum.xda-developers.com/showthread.php?t=1424997
If you want to install a custom rom type CM11, CM12 or CM13 you have to install a kernel compatible with recovery
Install PhilZ recovery, then from recovery install a compatible kernel
Kernel CM11
https://www.androidfilehost.com/?fid=24052804347829437
Kernel CM12
http://forum.xda-developers.com/devdb/project/dl/?id=16862
After flashing the kernel do a
Data factory reset
Wipe cache
Wipe Dalvik/ART
Install ROM, install gapps
If it does not work
Data factory reset
Wipe cache
Wipe Dalvik/ART
Format system
Format cache
Format data
Install ROM, install gapps
Click to expand...
Click to collapse
I did everything you said. Unfortunately, my device is still stuck at the boot screen. There were no error messages while flashing the roms and no other unusual events.
bfürbanane said:
I did everything you said. Unfortunately, my device is still stuck at the boot screen. There were no error messages while flashing the roms and no other unusual events.
Click to expand...
Click to collapse
This is really strange, try to redo the procedure without installing SuperSU
Sent from my H60-L02 using Tapatalk
panamera2011 said:
This is really strange, try to redo the procedure without installing SuperSU
Sent from my H60-L02 using Tapatalk
Click to expand...
Click to collapse
Where does it say to install SuperSU? How would that be possible when Android is not booting.
bfürbanane said:
Where does it say to install SuperSU? How would that be possible when Android is not booting.
Click to expand...
Click to collapse
I'm sorry but it's really strange, never had installation issues with any version of this rom
Have you tried this kernel to install the rom?
https://www.androidfilehost.com/?fid=24052804347829437
Sent from my H60-L02 using Tapatalk
bfürbanane said:
Where does it say to install SuperSU? How would that be possible when Android is not booting.
Click to expand...
Click to collapse
Alternatively, Odin a stock rom and look for a philz.zip with compatible baseband. You can enter stock recovery and then flash the philz.zip via update option. This is essentially replacing stock recovery with the custom version. I did this on a naturally occurring bootloop phone and it seems to work, this method also bypasses the yellow triangle warning on boot.
From there, if you want to use other custom roms just remember to wipe /data and /system before installing the kernel, followed by rom itself after a reboot to recovery.
bfürbanane said:
Where does it say to install SuperSU? How would that be possible when Android is not booting.
Click to expand...
Click to collapse
Sorry but I confused the message with the MIUI 6.2.12 thread [emoji16]
Sent from my H60-L02 using Tapatalk
AutumQueen92 said:
Alternatively, Odin a stock rom and look for a philz.zip with compatible baseband. You can enter stock recovery and then flash the philz.zip via update option. This is essentially replacing stock recovery with the custom version. I did this on a naturally occurring bootloop phone and it seems to work, this method also bypasses the yellow triangle warning on boot.
From there, if you want to use other custom roms just remember to wipe /data and /system before installing the kernel, followed by rom itself after a reboot to recovery.
Click to expand...
Click to collapse
I tried that. I went to samsung-updates.com and downloaded a version that I believe is compatible with my baseband version. Is there any way to check what baseband version my phone has? Then I flashed with odin and was stuck in a bootloop. I then flashed PhilZ recovery and the boot hangs at the samsung logo.
bfürbanane said:
Is there any way to check what baseband version my phone has?
Click to expand...
Click to collapse
Settings>about phone>
IronRoo said:
Settings>about phone>
Click to expand...
Click to collapse
The phone is not booting.
IronRoo said:
Settings>about phone>
Click to expand...
Click to collapse
Doh! sorry not reading what's in front of me. I did once read that you can get phone number via ADB, maybe the same will work for baseband?
bfürbanane said:
This phone was not rooted prior to being stuck at the boot screen. Actually, it wasn't event stuck at the boot screen. Instead, it turned on and off. I installed PhilZ recovery and was able to backup all files. Then I tried to flash different versions of CM without success. They all get stuck at the boot screen now. No more turning on and off. I also tried to clear cache, wipe dalvik something and reset to factory. Is there something else that can be done? What would be the most likely cause for the failure?
Click to expand...
Click to collapse
Have you tried a clean install ? Wiping /system and /data partitions then installing a custom ROM .. This option can be found in philz under install a new ROM ..
N00b... said:
Have you tried a clean install ? Wiping /system and /data partitions then installing a custom ROM .. This option can be found in philz under install a new ROM ..
Click to expand...
Click to collapse
Yes, I tried that. I also tried installing a ROM with a custom kernel that works on my other N7000, but it is still stuck at the boot screen.
bfürbanane said:
Yes, I tried that. I also tried installing a ROM with a custom kernel that works on my other N7000, but it is still stuck at the boot screen.
Click to expand...
Click to collapse
I think i got same problem as you do. Im digging on internet , if i get something ill write here.
Condox18 said:
I think i got same problem as you do. Im digging on internet , if i get something ill write here.
Click to expand...
Click to collapse
Good to know that I am not alone with my problem. Right now, I am out of ideas. I tried everything I could think of. I hope you have more luck than me.
same problem
bfürbanane said:
Good to know that I am not alone with my problem. Right now, I am out of ideas. I tried everything I could think of. I hope you have more luck than me.
Click to expand...
Click to collapse
Check this thread, post 3207 http://forum.xda-developers.com/showthread.php?t=1774208&page=321, u may have eactly same problem as me.
Condox18 said:
Check this thread, post 3207 http://forum.xda-developers.com/showthread.php?t=1774208&page=321, u may have eactly same problem as me.
Click to expand...
Click to collapse
Thanks for the pointer. I subscribed myself to that thread.
Hi!
Newbie here..
If I Root my 3T running Oxygen OS 4 and I get an OTA, can I just unroot it quickly and root it again afterwards?
Does it work like this or am I on the wrong track?
Thanks!
-Vince
vincedyne said:
Hi!
Newbie here..
If I Root my 3T running Oxygen OS 4 and I get an OTA, can I just unroot it quickly and root it again afterwards?
Does it work like this or am I on the wrong track?
Thanks!
-Vince
Click to expand...
Click to collapse
I had read somewhere that if you were rooted the OTA would fail if you just try to update
I downloaded the OTA on my pc and transfered it onto the phone then booted into TWRP, flashed and rooted and everything went fine
I received OSS4.0.2 update under rooted(flashed superSU) OP3T and both OTA and local upgrade failed even after I unrooted, finally I just flashed the full OTA zip in TWRP and it worked out fine.
Sykojoe said:
I had read somewhere that if you were rooted the OTA would fail if you just try to update
I downloaded the OTA on my pc and transfered it onto the phone then booted into TWRP, flashed and rooted and everything went fine
Click to expand...
Click to collapse
JackieMe said:
I received OSS4.0.2 update under rooted(flashed superSU) OP3T and both OTA and local upgrade failed even after I unrooted, finally I just flashed the full OTA zip in TWRP and it worked out fine.
Click to expand...
Click to collapse
That's great, thanks guys!
Do you just flash over and clear cache, nothing else?
vincedyne said:
That's great, thanks guys!
Do you just flash over and clear cache, nothing else?
Click to expand...
Click to collapse
Yes I just flashed over didn't reboot, flashed SuperSU, cleared cache then rebooted.
Sykojoe said:
Yes I just flashed over didn't reboot, flashed SuperSU, cleared cache then rebooted.
Click to expand...
Click to collapse
Neat. Guessing it works flawless, just like a standard OTA download? ?
vincedyne said:
That's great, thanks guys!
Do you just flash over and clear cache, nothing else?
Click to expand...
Click to collapse
As I can recall, I just cleared cache and flashed ROM and superSU. Didn't even tried ADVANCED SWIPE.
JackieMe said:
As I can recall, I just cleared cache and flashed ROM and superSU. Didn't even tried ADVANCED SWIPE.
Click to expand...
Click to collapse
Nice! Thanks for the help!
marimo1 said:
finally I just flashed the full OTA zip in TWRP and it worked out fine
Click to expand...
Click to collapse
Yeah, i downloaded beta TWRP 3.0.4, seems to work really good