Related
i want to flash CM11
i have done many a times in samsung..but sony its hectic.
plzz help me out..i have unlocked my bootloader.
do i have to install superuser? but how?
nd trying different methods but not succesfull..
m on latest stock firmware....
thnkx in advance
Firstly, make sure you are in 15.4.A.0.23 and above.
1. Head over to this site. Download the latest build for Nicki.
2. Extract boot.img from the downloaded zip and flash in fastboot.
3. Wipe /data and /cache through CWM.
4. Put the CM11 zip in any storage then flash it in CWM.
5. (Optional) Download GApps from here. Make sure it's for 4.4.4. Then flash it in CWM.
If you are having root permission problems, download the latest SuperSU flashable zip from here then flash it in CWM. Disable the default Superuser app (it can be found in Developer Options by tapping the Build Number 7 times) in CM11 and untick the box in SuperSU that states "Respect CM root settings."
That's it. Hope I helped.
elmkzgirxp said:
Firstly, make sure you are in 15.4.A.0.23 and above.
1. Head over to this site. Download the latest build for Nicki.
2. Extract boot.img from the downloaded zip and flash in fastboot.
3. Wipe /data and /cache through CWM.
4. Put the CM11 zip in any storage then flash it in CWM.
5. (Optional) Download GApps from here. Make sure it's for 4.4.4. Then flash it in CWM.
If you are having root permission problems, download the latest SuperSU flashable zip from here then flash it in CWM. Disable the default Superuser app (it can be found in Developer Options by tapping the Build Number 7 times) in CM11 and untick the box in SuperSU that states "Respect CM root settings."
That's it. Hope I helped.
Click to expand...
Click to collapse
does 4.4 Gapps have photo sphere or not?
theperson333 said:
does 4.4 Gapps have photo sphere or not?
Click to expand...
Click to collapse
I don't think so. They removed it because it doesn't work for most devices.
elmkzgirxp said:
I don't think so. They removed it because it doesn't work for most devices.
Click to expand...
Click to collapse
for anyone interested, I have found that it is due to our devices lacking gyro.
WARNING: THIS IS NOT A FLASHABLE ZIP
This is a modified kernel for Android 5.0 that allows root to work.
This kernel alone will not grant root access.
Flash this in custom recovery to obtain root: http://download.chainfire.eu/591/SuperSU/BETA-SuperSU-v2.17.zip
The kernel boot.img can be flashed using fastboot.
Credit goes to Chainfire. After seeing this post: https://plus.google.com/+Chainfire/posts/VxjfYJnZAXP ,
I took it upon myself to decompile, edit, then recompile the stock manta LPX13D kernel since he had only done so for the Nexus5/7.
Link: https://plus.google.com/+Chainfire/posts/ZzXaU1W7Uzm
Keep in mind this kernel allows root to work, but most apps that require root will need to be updated in order to fully work on Android 5.0.
Chainfire explains this in greater detail in the first G+ post i linked.
Damn, titanium backup is a no go.
great! works perfect, thanks a lot
newellj79 said:
Damn, titanium backup is a no go.
Click to expand...
Click to collapse
TiBu Works on 5.0!!!
Link: Experimental Version of TiBu that works on Andriod 5.0
phrix626 said:
TiBu Works on 5.0!!!
Link: Experimental Version of TiBu that works on Andriod 5.0
Click to expand...
Click to collapse
Thanks I'll give it a shot.
phrix626 said:
TiBu Works on 5.0!!!
Link: Experimental Version of TiBu that works on Andriod 5.0
Click to expand...
Click to collapse
What has your experience been with this so far? Does it delete system apps too? Thanks for the link!
anoneemooz said:
What has your experience been with this so far? Does it delete system apps too? Thanks for the link!
Click to expand...
Click to collapse
So far I've only restored a previous backup of flappybird from tibu on 5.0, I'm restoring a twrp backup of kitkat now so i can run a new backup in tibu, then restore lollipop, then test all the things!
It force closes when trying to sync with my Google cloud backup.
So far I've found that the experimental version of TiBu fails to uninstall system apps claiming "Cannot remove system app, failed to locate the apk file."
But... It does restore backups (app + data)
phrix626 said:
So far I've found that the experimental version of TiBu fails to uninstall system apps claiming "Cannot remove system app, failed to locate the apk file."
But... It does restore backups (app + data)
Click to expand...
Click to collapse
Aw man. That's all I really want right now. I'm about to give rooting this a shot now. Hopefully to try out some ad removing stuff like adaway! Thanks for the updates on TiBu!
I can't seem to get this to work. I flashed the boot.img via fastboot using "fastboot erase boot" followed by "fastboot flash boot boot.img" and then I reboot into recovery to flash the superuser zip in this thread..and I still get the same error with SuperSU about missing stuff and all root apps I've tried say I'm not rooted. I'm using the latest TWRP. Anything I'm missing?
Off topic: if you only need root to restore TiBu backup - create update zip from your backup, then flash the update zip in recovery. No root needed.
On topic: since you followed Chainfires' method, this won't set the whole system to permissive, right?
edit: I believe not, if TiBu is not working with this boot image. TiBu has not adopted to the new 5.0 SELinux environment yet.
Thanks for this kernel. İs there anybody tried this kernel ? I havent got much experience about android.
Thanks, this gave me root. Just need to wait for the various apps to be updated in due course. First one I tried, rashr, gained root access but said device not supported.
as an aside, anyone looking to block ads with or without root you can always flash this from recovery http://forum.xda-developers.com/showthread.php?t=1916098
Keep up to date with the latest versions of TiBu. Check out their Twitter feed.
https://mobile.twitter.com/TitaniumBackup/status/524487475738443776
The first test version I linked was older. I haven't had a chance to test this one yet.
Flashed the modified boot image & flashed SuperSu 2.17
SuperSU app won't let me update the binaries - so no root. SuperSU 2.16 doesn't work for me either.
Where to look? Can't find flashable SU binaries either.
Thanks!
Ti2 said:
Flashed the modified boot image & flashed SuperSu 2.17
SuperSU app won't let me update the binaries - so no root. SuperSU 2.16 doesn't work for me either.
Where to look? Can't find flashable SU binaries either.
Thanks!
Click to expand...
Click to collapse
If you flashed the boot.img and the SuperSU zip, root access should work.
The SuperSU zip includes the SuperSu app and the su binaries. It won't let you update the binaries because 2.16 is the latest stable release.
To test root:
Download and open Terminal Emulator > type "su" > you should get a SuperSU promt > grant access to Terminal Emulator.
The $ should now be a # , this confirms you are using the shell as root user.
Latest tibu test version working ok here for backup and restore :good:
phrix626 said:
If you flashed the boot.img and the SuperSU zip, root access should work.
The SuperSU zip includes the SuperSu app and the su binaries. It won't let you update the binaries because 2.16 is the latest stable release.
To test root:
Download and open Terminal Emulator > type "su" > you should get a SuperSU promt > grant access to Terminal Emulator.
The $ should now be a # , this confirms you are using the shell as root user.
Click to expand...
Click to collapse
No # for me... not even the prompt (duh..)
I flashed the boot.img and the SuperSU zip. I just don't have root.
What build of Lollipop are you running?
I flashed the images from this post :http://forum.xda-developers.com/showpost.php?p=56505625&postcount=99
Edit: that build is android-5.0.0_r2 (LRX21M)
I have trying to install viper4android on my q1010i from past 2 months and have tried every mentioned thing on the vipers forum as well as other threads.
The thing is its showing error- "Driver installation failed, the busybox found on your device doesn't work. this usually means you installed the wrong or broken busybox, V4A needs stericson busybox to work. If you are sure about having installed the proper busybox, then please confirm your device has been properly rooted."
Things i have tried
- Installing both busybox(free from playstore as well as pro)
- Tried unrooting and rerooting the device
- Flashed different versions of supersu
- Tried different versions of V4A
- Tried flashed different versions of V4A
Please help me!!...The thing is V4A works with jb but not working with kk.
I have currently stock kk s002 with exposed framework installed
Cheers... I did it !
nishantgupta107 said:
I have trying to install viper4android on my q1010i from past 2 months and have tried every mentioned thing on the vipers forum as well as other threads.
The thing is its showing error- "Driver installation failed, the busybox found on your device doesn't work. this usually means you installed the wrong or broken busybox, V4A needs stericson busybox to work. If you are sure about having installed the proper busybox, then please confirm your device has been properly rooted."
Things i have tried
- Installing both busybox(free from playstore as well as pro)
- Tried unrooting and rerooting the device
- Flashed different versions of supersu
- Tried different versions of V4A
- Tried flashed different versions of V4A
Please help me!!...The thing is V4A works with jb but not working with kk.
I have currently stock kk s002 with exposed framework installed
Click to expand...
Click to collapse
Suggestion: (Why Don't you update to S009, Its much more smooth!)
My Xolo Q1010i on 4.4.2 is working good with "Viper".
At start even i faced a lot of Problem but at last got a Solution :victory:
Technical Info:
(This problem is there in KK because there is no space left in kitkat System to Put any other file)
So, what u have to do is
1. You should have flashed a Stock 4.4.2 Kitkat Rom which is already SUed(Rooted) / Or root ur Kitkat by flashing custom Recovery and flashing SuperSu after that (google it for further details)
2. You need to delete some system App (To Get some space In System)
*Use Root Explore / ES File Explorer in root mode
To do this, U need to go In System>App> DELETE AN APP {PREFER GOOGLE PLUS(As u can intall it again)}
3. Restart
4. Upate SuperSu Binary(How to ?>Google It)
5.Install Busy Box
6. Enjoy Super Cool Audio Quality
But Viper have An Issue on Kitkat, If you clear viper from Recent... it will stop to work.
And Ya I'm using Multiwindow!
Check Here: ( http://forum.xda-developers.com/q10...ws-android-t3116786/post60931397#post60931397 )
I am stuck with s002 coz i was nt properly able to root s009 (luck patcher and other root app not working)
couldn't find the extra and awesomeness in s009 which was not in s002 so not gonna update.
And i have apprx 73.8mb in my system and i think that's enough for viper.
Also i have already uninstalled most of the system apps(before asking for help).
Other suggestions??
nishantgupta107 said:
I am stuck with s002 coz i was nt properly able to root s009 (luck patcher and other root app not working)
couldn't find the extra and awesomeness in s009 which was not in s002 so not gonna update.
And i have apprx 73.8mb in my system and i think that's enough for viper.
Also i have already uninstalled most of the system apps(before asking for help).
Other suggestions??
Click to expand...
Click to collapse
Notice: None of Rooting App will work for Xolo Q1010i... u need to follow this to do that, else u will always be there with s002!
The Problem is, Your Xolo is not properly Rooted(No proper Su binary Available)! [And simple copy / paste do not work in kitkat]
So, i strongly Recommend You to,
1. Download SU'ed "S009" from here : ( http://forum.xda-developers.com/q1010i/orig-development/rom-stock-xolo-q1010i-rom-one-d-t2883342 )
{You Seriously Need To Flash To Get Root, I Flashed Some 10-12 times to discover how to properly root our Xolo with s009 Kitkat}
2. Flash It With Flashing Tool
3. Follow Instruction What I have given Above properly.
4. I guarantee S009 works on Root poperly n buttery smooth with great battery backup N With Viper ofcourse :laugh:
(And Ya, Reminding Again Flashing The Above SUed Rom is important, after that follow my steps. Else you will never be able to properly Root Your Xolo Q1010i )
And Remember, If Viper works on Mine Xolo with Kitkat S009.... It will work for you, for sure. Just give it a proper Try buddy
ok, i'll try this and will post result after sometime.(having exams)
and do i have to flash latest super su binary also...after flashing pre su'ed s009.
nishantgupta107 said:
ok, i'll try this and will post result after sometime.(having exams)
and do i have to flash latest super su binary also...after flashing pre su'ed s009.
Click to expand...
Click to collapse
Nah, Just update it via play Store.
Then, SuperSu will ask you to update binary itself. Done!(Make Sure u delete some file from system before updating SuperSu)
i have tried on sued s009..nothing happened...still same error...
i don't know what i m doing wrong...
Finally after working whole night i have viper fully working in my kk now..!!!
i m soo happy...
the thing was my os was missing audio_effects.conf which i mistakenly deleted when i uninstalled dsp manager...
Disable "MOUNT SPACE SEPARATION" on Super SU
posting fix I found someone else figured out
nishantgupta107 said:
I am stuck with s002 coz i was nt properly able to root s009 (luck patcher and other root app not working)
couldn't find the extra and awesomeness in s009 which was not in s002 so not gonna update.
And i have apprx 73.8mb in my system and i think that's enough for viper.
Also i have already uninstalled most of the system apps(before asking for help).
Other suggestions??
Click to expand...
Click to collapse
This is what fixed my busybox error with V4A driver install:
"OK all I have a fix for installing Viper on the Tab S.
Use any file explorer and navigate to /system/vendor/etc
Copy the audio_effects.conf in that location
Navigate to /system/etc and paste the file you copied there
Once copied change the permissions to match the other files in the /system/etc folder
Install Viper and it should work this time, apparently the audio.effects.conf file is expected to be in the /system/etc location and is not there by default for some reason....*"
The file was already where it said to copy to, but contents were different. Either way, afterwards opening V4A apk file (without even having to reinstall), it prompted for driver install and did it!
zach
killerBRs said:
Disable "MOUNT SPACE SEPARATION" on Super SU
Click to expand...
Click to collapse
The voice of sanity.
Go into SuperSU. If everything is installed correctly (rooted, supersu, viper, and busybox), this WILL be the proper solution.
killerBRs said:
Disable "MOUNT SPACE SEPARATION" on Super SU
Click to expand...
Click to collapse
:good: it works!:good:
I'm using version 15.1-20180430-NIGHTLY-shamu version with latest TWRP on Nexus 6. There is an update on LineageOS updater, versioned 15.1. I clicked download, install and reboot. It rebooted to TWRP but did nothing. I browsed /data/data/org.lineageos.updater/ in TWRP but there is neither an app_updates folder there nor any zip file in existing folders. What should I do? I've searched the forum but couldn't find any solutions.
deastr said:
I'm using version 15.1-20180430-NIGHTLY-shamu version with latest TWRP on Nexus 6. There is an update on LineageOS updater, versioned 15.1. I clicked download, install and reboot. It rebooted to TWRP but did nothing. I browsed /data/data/org.lineageos.updater/ in TWRP but there is neither an app_updates folder there nor any zip file in existing folders. What should I do? I've searched the forum but couldn't find any solutions.
Click to expand...
Click to collapse
The newest updater allows you to save the downloaded file by long pressing on it. So you can flash in twrp from a good to remember folder.
kurtn said:
The newest updater allows you to save the downloaded file by long pressing on it. So you can flash in twrp from a good to remember folder.
Click to expand...
Click to collapse
When I long press the available update only option I get is Copy URL. Should I use that to download the update instead of auto-downloader?
deastr said:
When I long press the available update only option I get is Copy URL. Should I use that to download the update instead of auto-downloader?
Click to expand...
Click to collapse
You can do both.
kurtn said:
You can do both.
Click to expand...
Click to collapse
Auto-updater does some preparation after downloading and before rebooting. Do I need to anything similar or just install the zip within TWRP? Also if I use TWRP to install myself will it reset my data/settings/etc?
deastr said:
Auto-updater does some preparation after downloading and before rebooting. Do I need to anything similar or just install the zip within TWRP? Also if I use TWRP to install myself will it reset my data/settings/etc?
Click to expand...
Click to collapse
Just install. Nothing will be reset
Hey guys like the title says this months update is ready. I'm wondering if I can do the restore stock boot img thru magisk even tho I'm using MVK kernel?? Will it send me into boot loop??
** No bootloop everything worked out just fine **
Just a note tho, if you've rooted by patching the boot img you won't have a backup in magisk. You'll have to take the stock boot img from your current build and compress it with this file name stock_boot_0.img in a .gz compression then copy that to the /data folder in root storage. Then go into /sbin folder and go into .magisk folder, tap on config and change the SHA value to 0 and save it.
After that's done you can restore your stock boot thru magisk, take the OTA update, don't reboot yet, install magisk to the inactive slot, once done you can reboot and your good to go and still rooted
Perfect
Grabbed the full factory image. Removed the -w in flash-all. Flashed, patched boot.img. Works great!
Anyone having trouble with root on Jan update getting lost after a rebooot?
Tried 3 times now and same result each time.
Load magisk patched boot image for January via fastboot
Root fully operational
Install a magisk module
Required reboot after installing above module
Phone is no longer rooted
Can anyone confirm or deny if they get the same.
adm1jtg said:
Anyone having trouble with root on Jan update getting lost after a rebooot?
Tried 3 times now and same result each time.
Load magisk patched boot image for January via fastboot
Root fully operational
Install a magisk module
Required reboot after installing above module
Phone is no longer rooted
Can anyone confirm or deny if they get the same.
Click to expand...
Click to collapse
No..root still working here after reboot.
adm1jtg said:
Anyone having trouble with root on Jan update getting lost after a rebooot?
Tried 3 times now and same result each time.
Load magisk patched boot image for January via fastboot
Root fully operational
Install a magisk module
Required reboot after installing above module
Phone is no longer rooted
Can anyone confirm or deny if they get the same.
Click to expand...
Click to collapse
Working just fine here
adm1jtg said:
Anyone having trouble with root on Jan update getting lost after a rebooot?
Tried 3 times now and same result each time.
Load magisk patched boot image for January via fastboot
Root fully operational
Install a magisk module
Required reboot after installing above module
Phone is no longer rooted
Can anyone confirm or deny if they get the same.
Click to expand...
Click to collapse
UPDATE: thanks to the feedback i got it working... Turns out was a bad magisk module, updated and all is well. Thanks
thatsupnow said:
Hey guys like the title says this months update is ready. I'm wondering if I can do the restore stock boot img thru magisk even tho I'm using MVK kernel?? Will it send me into boot loop??
** No bootloop everything worked out just fine **
Just a note tho, if you've rooted by patching the boot img you won't have a backup in magisk. You'll have to take the stock boot img from your current build and compress it with this file name stock_boot_0.img in a .gz compression then copy that to the /data folder in root storage. Then go into /sbin folder and go into .magisk folder, tap on config and change the SHA value to 0 and save it.
After that's done you can restore your stock boot thru magisk, take the OTA update, don't reboot yet, install magisk to the inactive slot, once done you can reboot and your good to go and still rooted
Click to expand...
Click to collapse
I've done all steps up until the OTA part. It keeps giving me "Couldn't update, Installation problem" after numerous tries. Both here and the Magisk guide say DO NOT reboot. Am I screwed if I reboot or just have to repeat the process?
Thanks
Basically I was on November update with magisk and a custom kernel installed I couldn't take otas so how I fixed it was @mbk17 I had to flash the matching boot IMG in fastboot from the update I was on to get installation problem error to go away so I could take an ota.
Download matching factory image from goggles website
Then unzip the file
Then also unzip the image bonito zip
The boot IMG is inside second zip
Flash boot IMG in fastboot issue fixed :victory:
thatsupnow said:
Just a note tho, if you've rooted by patching the boot img you won't have a backup in magisk. You'll have to take the stock boot img from your current build and compress it with this file name stock_boot_0.img in a .gz compression then copy that to the /data folder in root storage. Then go into /sbin folder and go into .magisk folder, tap on config and change the SHA value to 0 and save it.
After that's done you can restore your stock boot thru magisk, take the OTA update, don't reboot yet, install magisk to the inactive slot, once done you can reboot and your good to go and still rooted
Click to expand...
Click to collapse
Actually, there is an easier way. Get the stock boot.img for the current build, put it on your phone, and patch that boot.img through Magisk. It will backup that original boot.img before it patches it. Don't need to do anything with the patched boot.img, but when you restore images, it will take the backup you just created.
---------- Post added at 10:03 PM ---------- Previous post was at 09:59 PM ----------
mbk17 said:
I've done all steps up until the OTA part. It keeps giving me "Couldn't update, Installation problem" after numerous tries. Both here and the Magisk guide say DO NOT reboot. Am I screwed if I reboot or just have to repeat the process?
Thanks
Click to expand...
Click to collapse
I know it's too late but in the future if you get this, you're still rooted until you reboot, so just reinstall magisk through direct install. Now when you reboot, you're still rooted.
That said, if you can't update through the ota, you're going to have to update through ADB, and you'll lose root anyway.
Bramton1 said:
Actually, there is an easier way. Get the stock boot.img for the current build, put it on your phone, and patch that boot.img through Magisk. It will backup that original boot.img before it patches it. Don't need to do anything with the patched boot.img, but when you restore images, it will take the backup you just created.
Tried that and didn't work. Kept saying backup didn't exist, hence why I posted this steps
Click to expand...
Click to collapse