Hey Folks,
I am totally new to this but I want to put CM 12.1 on my SPG621. I have unlocked the bootloader so far and I was looking for hours for a step by step guide that is noob-safe.
There are many guides and tutorials that tell different things and it is very hard for me to get the essence of it.
What I understand is as follows:
- I have an unlocked bootloader (and lost my DRM Keys, good job)
- get root
- install custom recovery
- install CM 12.1
Is that the correct order? How do I do that in detail? I don't understand how to install a custom recovery without root and I don't understand how to get root.
I have downloaded Flashtool so far. I would be glad if I got any helpful advices. Thanks a lot!
These are what I did to have root and twrp:
1. Check what version you are on right now. If you are on 5.0.2, you can root it by using Kingroot 4.5 (here)
2. If not, you can download stock 5.0.2 from here and flash it via Flashtool; then you can install Kingroot 4.5 and get root
3. Turn on usb debugging and unlock the bootloader again as you have converted to stock
4. Install twrp - download from here
5. Download CM12.1 and Gapps and install via twrp here
Hope it helps!
Thanks for your quick answer.
I now obtained root access via Kingroot. I would like to install TWRP Recovery now. I downloaded it via PlayStore. I chose my device and tapped on Install Recovery.
It now asks me to confirm a partition /dev/block/platform/msm_sdcc.1/by-name/FOTAKernel else I would risk bricking the device. How can I make sure that this is the correct partition? I can't see this path in my file commander.
Cheers,
ArctiCMooN
Edit: Never mind, I didn't click on the link. I will install it with your link then and post the result here.
Mocha7 said:
These are what I did to have root and twrp:
1. Check what version you are on right now. If you are on 5.0.2, you can root it by using Kingroot 4.5 (here)
2. If not, you can download stock 5.0.2 from here and flash it via Flashtool; then you can install Kingroot 4.5 and get root
3. Turn on usb debugging and unlock the bootloader again as you have converted to stock
4. Install twrp - download from here
5. Download CM12.1 and Gapps and install via twrp here
Hope it helps!
Click to expand...
Click to collapse
I have a few problems now that I try installing the dual recovery.
Root Checker says I successfully have rooted my device. BUT: I cannot find the KingUser App anywhere.
When I try to install TWRP via this dual recovery method, it asks me if I want to use SuperSU or SuperUser method, but I don't have anyone of the, is that correct?
Did something go wrong?
ArctiCMooN said:
I have a few problems now that I try installing the dual recovery.
Root Checker says I successfully have rooted my device. BUT: I cannot find the KingUser App anywhere.
When I try to install TWRP via this dual recovery method, it asks me if I want to use SuperSU or SuperUser method, but I don't have anyone of the, is that correct?
Did something go wrong?
Click to expand...
Click to collapse
Look at this thread: http://forum.xda-developers.com/z3-tablet-compact/general/how-to-root-easy-t3115418
You'll have the answers of your questions.
It worked perfectly for me.
guizmogwai said:
Look at this thread: http://forum.xda-developers.com/z3-tablet-compact/general/how-to-root-easy-t3115418
You'll have the answers of your questions.
It worked perfectly for me.
Click to expand...
Click to collapse
Thanks a lot for the help.
I managed to get CM12.1 on my Sony Xperia Z3 Compact Tablet.
I basically did what Mocha7 told me, although I wasn't sure about KingRoot 4.5 (trustworthy or not?). I gave it a try, the first time it failed, the second time the root was successful.
I did not install SuperSU or SuperUser and directly continued with the installation of XZDualRecovery and chose SuperSU method in the Windows Command Terminal.
This worked perfectly and the tablet directly started into TWRP. From there I started the installation of CM 12.1.
After that, I did a factory reset of CM 12.1 to erase all data of the old system and reinstalled XZDualRecovery.
I downloaded the latest Gapps from CM Wiki and installed it via Recovery.
The system works fine and I am extremely happy that I got rid of Sony's Stock Android. There are some very small bugs in CM 12.1: Rebooting erases some shortcuts on the homescreen and the lowest brightness setting is still quite bright.
Thanks again for the help!
ArctiCMooN said:
Thanks a lot for the help.
I managed to get CM12.1 on my Sony Xperia Z3 Compact Tablet.
I basically did what Mocha7 told me, although I wasn't sure about KingRoot 4.5 (trustworthy or not?). I gave it a try, the first time it failed, the second time the root was successful.
I did not install SuperSU or SuperUser and directly continued with the installation of XZDualRecovery and chose SuperSU method in the Windows Command Terminal.
This worked perfectly and the tablet directly started into TWRP. From there I started the installation of CM 12.1.
After that, I did a factory reset of CM 12.1 to erase all data of the old system and reinstalled XZDualRecovery.
I downloaded the latest Gapps from CM Wiki and installed it via Recovery.
The system works fine and I am extremely happy that I got rid of Sony's Stock Android. There are some very small bugs in CM 12.1: Rebooting erases some shortcuts on the homescreen and the lowest brightness setting is still quite bright.
Thanks again for the help!
Click to expand...
Click to collapse
Sorry I was out of town for the labour day long weekend so I didn't see your replies.
So glad to hear that you nailed the CM 12.1! Enjoy!!:good::good:
Hi, Please report how is the condition of Cynogen mod 12.1, is it stable for daily use already?
wow, man! I read your post and think this is ME!! haha I just got my Z3 Tablet a few days ago and had the same struggle. I got it with 4.4.4 installed and jumped right to CM12.1. Also tried crDroid and like it actually much better^^ I got a big problem though. With these custom roms my camera would not focus! the back camera is useless. front is ok though. Have you anything like that??
Schuan said:
Hi, Please report how is the condition of Cynogen mod 12.1, is it stable for daily use already?
Click to expand...
Click to collapse
It works really well so far. No crashes or anything. very nice! :good:
Schuan said:
Hi, Please report how is the condition of Cynogen mod 12.1, is it stable for daily use already?
Click to expand...
Click to collapse
Hi, CM 12.1 is quite stable but has a few bugs.
Restarting the device deletes most of my homescreen shortcuts.
The adaptive brightness options seems a little bit buggy. It switches brightness way too fast and too often, is not smooth, so I turned that off.
Besides that, I did not experience any further bugs.
knauji said:
It works really well so far. No crashes or anything. very nice! :good:
Click to expand...
Click to collapse
Now there is a problem. I tried to update to a more recent nightly of CM 12.1. I did it via the settings menu and let everything happen.
Now I can't boot my device anymore nor can I boot into recovery. The device just tries to boot, shows the Sony symbol and then turns off and tries to boot again. So it is in a boot loop.
Can anybody help with this?
This happened to me a few times. Try to flash the recovery again and the flash the rom from there. If it works, good, if not....
It happened to last night when I tried the latest nightly. I could not do anything so I flashed the sony stock rom with flashtool. After that I could flash TWRP again. Not sure of any other way.
Yeah I had huge problems getting recovery on my device. I reinstalled stock 5.0.2, rooted it and tried to get the same dual recovery on it I used before, but it didn't work. So I downgraded to 4.4.4 and managed to get Custom Recovery on it and from there I managed to install CM 12.1 again. Now everything works fine, but my nerves need a rest now^^
glad it works. take a rest and enjoy haha
I have to wait some more or maybe even sell it because of the camera bug.... I don't like sony stock os ....
Related
Hi,
Try as I may. I cant unlock my Tablet Z LTE (SGP321) bootloader.
Im using FlashTool 0.9.18.4 and am currently on stock KK 4.4.4. firmware (SGP321_10.5.1.A.0.283_CE.ftf)
Everytime I try to ulock the bootloader it fails with FlashTool message that drivers need to installed
I've trird installing the drivers via the \FlashTool\Drivers directory.......but always get the following message "DPInst.exe doe not execute on your current operating system" - I'm running Windows 7 Ultimate 64bit
Any and all help would be greatly appreciated as I'm desperate to install CM KK 4.4.4 and get rid of the Sony stuff.
Thanks in advance
_____________________________
Sony Xperia Tablet Z LTE/WIFI SGP321
vybztymz said:
Hi,
Try as I may. I cant unlock my Tablet Z LTE (SGP321) bootloader.
Im using FlashTool 0.9.18.4 and am currently on stock KK 4.4.4. firmware (SGP321_10.5.1.A.0.283_CE.ftf)
Everytime I try to ulock the bootloader it fails with FlashTool message that drivers need to installed
I've trird installing the drivers via the \FlashTool\Drivers directory.......but always get the following message "DPInst.exe doe not execute on your current operating system" - I'm running Windows 7 Ultimate 64bit
Any and all help would be greatly appreciated as I'm desperate to install CM KK 4.4.4 and get rid of the Sony stuff.
Thanks in advance
_____________________________
Sony Xperia Tablet Z LTE/WIFI SGP321
Click to expand...
Click to collapse
don't use flashtool for unblocking BL (cause you can use instruction from Sony's site), or install drivers properly: look for dpinst.exe in your temp folder and set compability mode with WinVista in it's properties and it will install properly.
Rootk1t said:
don't use flashtool for unblocking BL (cause you can use instruction from Sony's site), or install drivers properly: look for dpinst.exe in your temp folder and set compability mode with WinVista in it's properties and it will install properly.
Click to expand...
Click to collapse
Thanks for your reply/suggestion. Unfortunately I do not have the "set compatibility" option in DPInst.exe properties. I have found 2 x dpinst.exe and 2 x dpinst64.exe files on my system.
I've tried using the Sony site instructions but
1. When i attch the tablet to my laptop in Fastboot mode (Vol up), and type "fastboot devices" at the cmd prompt, i dont get any indication that my tablet has been/is recognised (see scrrenshot 1)
2. When I run the unlock command using the unlock code obtained from Sony, command line sticks at "waiting for device" (screenshot 2)
i'm at a loss as to whats wrong \ what Im doing wrong
All / any suggestions welcomed as am desperate to install CM11/12.
Thanks in advance
Vybz
vybztymz said:
Thanks for your reply/suggestion. Unfortunately I do not have the "set compatibility" option in DPInst.exe properties. I have found 2 x dpinst.exe and 2 x dpinst64.exe files on my system.
I've tried using the Sony site instructions but
1. When i attch the tablet to my laptop in Fastboot mode (Vol up), and type "fastboot devices" at the cmd prompt, i dont get any indication that my tablet has been/is recognised (see scrrenshot 1)
2. When I run the unlock command using the unlock code obtained from Sony, command line sticks at "waiting for device" (screenshot 2)
i'm at a loss as to whats wrong \ what Im doing wrong
All / any suggestions welcomed as am desperate to install CM11/12.
Thanks in advance
Vybz
Click to expand...
Click to collapse
Check that your tablet's fastboot drivers are installed correctly in device manager on windows. I haven't done this on the tablet z (yet), but if you do not have the drivers installed on a nexus you wont see any device in the fastboot devices option.
So i would suggest you download the correct drivers (preferably from sony, but google drivers might also work), and check that the device manager dont have any unknown devices (tablet z) and if you do not try reinstalling the driver by uninstalling the current one and getting the correct one from sony or the google drivers.
marcusorwen said:
Check that your tablet's fastboot drivers are installed correctly in device manager on windows. I haven't done this on the tablet z (yet), but if you do not have the drivers installed on a nexus you wont see any device in the fastboot devices option.
So i would suggest you download the correct drivers (preferably from sony, but google drivers might also work), and check that the device manager dont have any unknown devices (tablet z) and if you do not try reinstalling the driver by uninstalling the current one and getting the correct one from sony or the google drivers.
Click to expand...
Click to collapse
Thanks - you were right, it was drivers. Finally managed (I think) to unlock bootloader.........but am now stuck in a bootloop .
Any suggestions welcomesed
Use flashtool and simply flash any stock version on top.
Alternatively, you can use some non stock ROM, but for that your first need to install the custom recovery via fastboot.
vybztymz said:
Any suggestions welcomesed
Click to expand...
Click to collapse
Have a look at this guide for installing a CM ROM
vybztymz said:
Thanks - you were right, it was drivers. Finally managed (I think) to unlock bootloader.........but am now stuck in a bootloop .
Any suggestions welcomesed
Click to expand...
Click to collapse
If your stuck in a bootloop i would suggest trying and flash recovery through flashtools and see if you can clear dalvik cache in the custom recovery.
it might help.
but otherwise do as the others say and flash a custom rom (CM preferably).
Lost Root after installing CN12 Nightly (Lollipop 5.0x)
marcusorwen said:
If your stuck in a bootloop i would suggest trying and flash recovery through flashtools and see if you can clear dalvik cache in the custom recovery.
it might help.
but otherwise do as the others say and flash a custom rom (CM preferably).
Click to expand...
Click to collapse
hanks for you help.
I have rooted and unlocked the boot loader of my SGP321 (WiFi/LTE).
But every time I install CM12 (flashed zip via TWRP), I lose Root......and as far as I can see, there's no way back from that, bar a complete re-install of stock (KK444)
Really frustrated as have wanted to flash CM and get rid of the Sonly bloatware (example: of 2gb internal memory, the stock firmware leaves only c.500mb free....thats just plain ridiculous. Compared to CM12 which leaves 1.7 GIGS free.
any suggestions.......?
vybztymz said:
hanks for you help.
I have rooted and unlocked the boot loader of my SGP321 (WiFi/LTE).
But every time I install CM12 (flashed zip via TWRP), I lose Root......and as far as I can see, there's no way back from that, bar a complete re-install of stock (KK444)
Really frustrated as have wanted to flash CM and get rid of the Sonly bloatware (example: of 2gb internal memory, the stock firmware leaves only c.500mb free....thats just plain ridiculous. Compared to CM12 which leaves 1.7 GIGS free.
any suggestions.......?
Click to expand...
Click to collapse
CM12 should have root built in, check developer options for it on your device.
If not then just flash SuperSU.zip from chainfire (i prefer chainfire's version of super user).
Chainfire's SuperSU is here: http://forum.xda-developers.com/showthread.php?t=1538053
please note that i have not tested this on a Tab Z but it should work.
marcusorwen said:
CM12 should have root built in, check developer options for it on your device.
If not then just flash SuperSU.zip from chainfire (i prefer chainfire's version of super user).
Chainfire's SuperSU is here: http://forum.xda-developers.com/showthread.php?t=1538053
please note that i have not tested this on a Tab Z but it should work.
Click to expand...
Click to collapse
Thanks for the speedy reply. Really appreciated. I've gone intp developer options.....but what am i looking for?
[EDIT] In Developer Options, and under "Root Access" it says "Disabled"
[EDIT 2] Downloaded a RootChecker and it tells me I'm not rooted
I'm totally frustrated.....have been trying to install CM12 for the last 6 hours!!!!
NUT (duallockedrecovery) has done a fantastic job developing the xzdr.........but i have to say that, in common with a lot of devs.... not very good at writing nstructions.
I'm an IT manager and often train staff in systems etc, including writing user guides. When writing guides/instructions, I ALWAYS assume that the end user KNOWS NOTHING......and so the guides/etc are very detailed. Yes, it takes a while to write them, but feedback shows its the right track to take.
Almost all the articles on flashing CM12/using Fastboot etc lack small, but important, details......!!! I'm still not really sure if i should be using TabZ-lockeddualrecovery or XZ-lockeddualrecovery..........!!!!!!
i've got as far as I have by pulling together numerous XDA posts in order to get a (full'ish) picture of what to do. Devs, pls make your instructions clearer for people who aren't devs. Rant over
My current position is that my Xperia Tablet Z is
1. On KitKat 444 (Firmware ver. 283)
2. Rooted
3. Bootloader unlocked
4. SuperSU & SuperSu Pro installed
How do i get from this position to a successful CM12 install?
I have CM12 Nightly (7th May), GApps 5.0x Minimal ready and waiting....
I'm not a stupid person, but trying to do this has made me feel like a complete idiot.....help!!!
vybztymz said:
Thanks for the speedy reply. Really appreciated. I've gone intp developer options.....but what am i looking for?
I'm totally frustrated.....have been trying to install CM12 for the last 6 hours!!!!
NUT (duallockedrecovery) has done a fantastic job developing the xzdr.........but i have to say that, in common with a lot of devs.... not very good at writing nstructions.
I'm an IT manager and often train staff in systems etc, including writing user guides. When writing guides/instructions, I ALWAYS assume that the end user KNOWS NOTHING......and so the guides/etc are very detailed. Yes, it takes a while to write them, but feedback shows its the right track to take.
Almost all the articles on flashing CM12/using Fastboot etc lack small, but important, details......!!! I'm still not really sure if i should be using TabZ-lockeddualrecovery or XZ-lockeddualrecovery..........!!!!!!
i've got as far as I have by pulling together numerous XDA posts in order to get a (full'ish) picture of what to do. Devs, pls make your instructions clearer for people who aren't devs. Rant over
My current position is that my Xperia Tablet Z is
1. On KitKat 444 (Firmware ver. 283)
2. Rooted
3. Bootloader unlocked
4. SuperSU & SuperSu Pro installed
How do i get from this position to a successful CM12 install?
I have CM12 Nightly (7th May), GApps 5.0x Minimal ready and waiting....
I'm not a stupid person, but trying to do this has made me feel like a complete idiot.....help!!!
Click to expand...
Click to collapse
Yea i know what you mean by guides not being written to include alot of details and missing out on small stuff that might be important, but anyway.
In the Developer Options there should be a box called Root Access, and it should be defaulted to Disabled ones you have installed CM12 for the first time, its just a matter of enabling this.
Im guessing you already know how to enable Developer Options, but if you dont here is how:
Go to About Device (or Phone/Tablet) and click on Build number a bunch of times (i think its 5-6 times), and the developer options should be visible in the settings.
If that dosent work you might want to try and flash the SuperSU binary through recovery, the zip to use is the one found in chainfires xda-thread here: http://forum.xda-developers.com/showthread.php?t=1538053
But here is the direct link for the zip https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Just put that on your device internal memory (or SD-Card) and flash it in your recovery of choice, it should work in CWM, TWRP and Odin (but you dont have a samsung so the last one dosent matter).
This should install the SuperSU app, and its basic su binary onto your CM12 rom.
In both cases i would recommend you install root checker (https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck) and see if root is available to you.
Also to note is that the Root Access option built into CM12 isnt that customizable and i would still recomend you install SuperSU, but if the Root Access option is working you can just download the SuperSU application from the play store and let it install SU binary and then you can disable CM12's built in root option ones you make sure the SuperSU was installed correctly.
Thanks so much for your help/patience......but i'm afraid im giving up (for now).
Will try again in a few days......so its back to rooted stock 444
By the way, why have CM decided to go with their own (as good as useless) recovery????
I forgot to say that you've helped fill in a few more gaps for me in respect of this i.e. flashing SU; changing Root Access in Dev. Options etc.
These are the things that all the articles ive read FAILED to mention.
Thanks so much
vybztymz said:
I forgot to say that you've helped fill in a few more gaps for me in respect of this i.e. flashing SU; changing Root Access in Dev. Options etc.
These are the things that all the articles ive read FAILED to mention.
Thanks so much
Click to expand...
Click to collapse
No problem, if you have any other questions just tell me and i might be able to help you
I have also been in the dark about this stuff before, and im still not used to other manufacturers style of rooting and unlocking the bootloader (sony is the next best after Nexus) since samsung and the others usually you have a harder time unlocking and rooting.
But good luck if you try it again :victory:
Hi all,
Just want to help a bit with the CM12S. Flash the attached zip if you want root in apps and ADB.
I grabbed a debuggable boot.img from the official CM servers here:
Code:
http://builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS0YL-bacon/2263178b74/cm-12.0-YNG1TAS0YL-bacon-boot-debuggable.img
EDIT: New OTA [YNG1TAS17L]:
Code:
http://builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS17L-bacon/e816218e8a/cm-12.0-YNG1TAS17L-bacon-boot-debuggable.img
Then, I simply put them in a flashable zip format together with su binary from the latest CM12 nightly. I have tested it on my own phone and so far, there is no issue.
I have only tested it using TWRP, flash on your own risk.
Credits to @julian_klode:
https://forums.oneplus.net/threads/flashable-zip-enable-integrated-superuser.75511/
Note: I initially wasn't aware about the source of the base zip file that I used to pack the necessary files until julian_klode mentioned it in the Q&A thread.
There is no difference between this one and his, just the fact that I update mine manually. So, I think you should follow his thread instead.
Or just flash the SuperSu zip via recovery.
Sent from my A0001
Outstriped! I was thinking to make Debug kernel, but they released it sooner
Thank you so much. Puzzle and Dragons doesn't like Supersu, but works perfect with CM's superuser.
works fine here, thanks!
Vivek_Neel said:
Or just flash the SuperSu zip via recovery.
Sent from my A0001
Click to expand...
Click to collapse
Some people, like me, prefer CM's own root. Integration with Privacy Guard is pretty nifty, you know?
thank you , works perfectly!
inscythe said:
Some people, like me, prefer CM's own root. Integration with Privacy Guard is pretty nifty, you know?
Click to expand...
Click to collapse
thx:good:
Works great please keep this updated with each OTA if possible!
Vivek_Neel said:
Or just flash the SuperSu zip via recovery.
Sent from my A0001
Click to expand...
Click to collapse
That did not work for me
droidextra said:
That did not work for me
Click to expand...
Click to collapse
sorry for my noob question. but i actually flashed supersu. that wont affect anything. i am asking this cause yesterday i had to factory reset my device 4 times as it got stuck at cyanogen boot animation. It would boot fine couple of times and then get stuck.
srgudhka said:
sorry for my noob question. but i actually flashed supersu. that wont affect anything. i am asking this cause yesterday i had to factory reset my device 4 times as it got stuck at cyanogen boot animation. It would boot fine couple of times and then get stuck.
Click to expand...
Click to collapse
I have never tried SuperSU in my OPO Lollipop since I found out about the built-in root support, so I can't say what's wrong with it. Bootloops may be caused by stuck up boot process, which may be caused by kernel.
If I'm not wrong, I remember last time when Lollipop launched that SuperSU need to patch the kernel in a certain way for it to run properly. My solution also works with a different kernel, albeit it is provided officially by Cyanogen.
If you really want SuperSU for some reason, you can try flashing SuperSU and then flash the boot.img from the link above (or extract it from my zip). Latest TWRP will do it just fine.
inscythe said:
I have never tried SuperSU in my OPO Lollipop since I found out about the built-in root support, so I can't say what's wrong with it. Bootloops may be caused by stuck up boot process, which may be caused by kernel.
If I'm not wrong, I remember last time when Lollipop launched that SuperSU need to patch the kernel in a certain way for it to run properly. My solution also works with a different kernel, albeit it is provided officially by Cyanogen.
If you really want SuperSU for some reason, you can try flashing SuperSU and then flash the boot.img from the link above (or extract it from my zip). Latest TWRP will do it just fine.
Click to expand...
Click to collapse
SuperSU plus CM root don't play well together. Take a look through Caulk's stock 5.0.2 thread and you'll see several people having problems - manifested by flashing SuperSU and then trying to open Developer Options. It FCs. Just use the built-in CM root or disable CM root before you flash SuperSU.
All good here! I went into the Supersu settings and did a FULL UNINSTALL OF ROOT. Once that was done, I went into TWRP and flashed CM zip provided by OP... Bam. Done and no problems. Thank you, OP!
Wisiwyg said:
SuperSU plus CM root don't play well together. Take a look through Caulk's stock 5.0.2 thread and you'll see several people having problems - manifested by flashing SuperSU and then trying to open Developer Options. It FCs. Just use the built-in CM root or disable CM root before you flash SuperSU.
Click to expand...
Click to collapse
I perhaps wasn't very clear about my above suggestion.
What I meant is that, there is an official insecure boot.img (the kernel) which I linked above and included in my zip package. I'm not telling him to install both SuperSU and the built-in root.
SuperSU has some features that is not present in the built-in root though, like logging or tapjacking protection. Privacy Guard is pretty nifty, but I still miss the old interface of SuperSU.
inscythe said:
Hi all,
Just want to help a bit with the CM12S. Flash the attached zip if you want root in apps and ADB.
I grabbed a debuggable boot.img from the official CM servers here:
Code:
http://builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS0YL-bacon/2263178b74/cm-12.0-YNG1TAS0YL-bacon-boot-debuggable.img
Then, I simply put them in a flashable zip format together with su binary from the latest CM12 nightly. I have tested it on my own phone and so far, there is no issue.
I have only tested it using TWRP, flash on your own risk.
Click to expand...
Click to collapse
Is there any way to make this work with franco kernel r41? Thanks...
ten_tickles said:
Is there any way to make this work with franco kernel r41? Thanks...
Click to expand...
Click to collapse
I think it's the issue with Franco's own kernel... Even the nightly CM12 users with the built-in root enabled also had the root access disabled.
SuperSU works in this case because it relies on an init.d su-enabling service.
Just wait for Franco to fix it, since the CM11S versions works well with the built-in root. I am also a FK paid user, so this is a bad situation for me as well...
If you could update this asap to the YNG1TAS17L build that would be awesome thanks a lot for your hard work! Edit: nvm was able to make my own.
Link_of_Hyrule said:
If you could update this asap to the YNG1TAS17L build that would be awesome thanks a lot for your hard work! Edit: nvm was able to make my own.
Click to expand...
Click to collapse
Care to share it? I presume that the version in the OP won't work with the new v5.02 OTA?
I uploaded it here sorry it's not a better host but I'm on my phone ATM lol. http://uploadmirrors.com/download/R8ADOYOG/icial-12.0-signed-YNG1TAS17L-bacon-superuser.zip All I did was get the ota URL from here and changed the ending to cm-12.0-YNG1TAS17L-bacon-boot-debuggable.img I guess the system automatically makes the debug images when the ota rolls out. So I imagine the same thing would work for next ota. You just rename it to boot.img and replace the one in the zip from this thread and rename the zip and flash.
Link_of_Hyrule said:
If you could update this asap to the YNG1TAS17L build that would be awesome thanks a lot for your hard work! Edit: nvm was able to make my own.
Click to expand...
Click to collapse
Not that hard to make, right? But super practical to keep this if you often jumping ROMs.
SimonTS said:
Care to share it? I presume that the version in the OP won't work with the new v5.02 OTA?
Click to expand...
Click to collapse
Sorry, was doing overtime at work. I've updated the OP too.
I have a nubia z7 with rom version 2.05 (Android 5 and Nubia UI 3), with google apps working without problems. Even youtube.
It took 3 days to figure out how to do it, without rooting the phone.
But some tools are needed...
I upgraded my phone rom (which came with version 2.26, a modified 1.26), put rom 2.02 then 2.03 and at last 2.05, which is the last one in nubia chinese site.
I used nubia rom updater, for the roms version 2.02 and 2.03 you have to decompress to each folder and point nubia updater to that folder.
The last one (version 2.05), i used option update of the phone.
Then uninstalled every chinese app. Downloaded gapps micro for android 5.0.1 and copy to the internal storage.
Then rebooted the phone with TWRP and installed the zip file. With TWRP root the phone, in advanced menu.
After that, i reboot into android system and made login into google play and updated everything.
It's a google phone now.
I think this should work for Nubia Z7 mini and Nubia Z7 Max
I hope this help someone
link: https://drive.google.com/folderview?id=0B52DgCiPfqeTYkFmUjNSbm44RDA&usp=sharing
greetings
I managed to get as far as upgrading firmware to v2.05. The files worked great thanks. How do I use the twrp to install gapps? Thanks for the help
helobot said:
I managed to get as far as upgrading firmware to v2.05. The files worked great thanks. How do I use the twrp to install gapps? Thanks for the help
Click to expand...
Click to collapse
hi, i'm Senh0r. I had logged with an old account.
now you can uninstall all chinese apps ,that you don't want.
then copy file gapps to internal storage.
Check if you have port ADB selected, by inserting on dial number *#7678# , if not, select it.
Now run the TWRP, which is in chinese, when the menu show up, choose option 3 and wait for the phone reboot into TWRP.
When you enter in TWRP, on bottom of screen you can choose english language.
After that is only to install the zip file. don't check for signature.
Now it's only need to reboot phone.
To enter on TWRP you need always to run the program to reboot your phone.
Anything ask
greetings
Thanks for that. I got them installed but when I boot the phone I get a google services has stopped and the phone shuts down I'm
Not sure what I did wrong
helobot said:
Thanks for that. I got them installed but when I boot the phone I get a google services has stopped and the phone shuts down I'm
Not sure what I did wrong
Click to expand...
Click to collapse
try to root the phone first and then install gapps again.
it's in advanced options, i think
did you managed to do it?
Hi Guys,
got my NX506J today, so a word of warning, I am pretty new to this
I am a little bit lost at the start,
Some Infos on the phone
Hardware Revision: NX506JMB_B
Build Number: NX506J_CNCommon_V2.26
NUBIA UI: V2.6.3
Rooted with TowelRoot
I'd appreciate it if you guys can point me in the right direction
THanks in advance
Hi,
just follow the first post.
greetings
Senh0r said:
Hi,
just follow the first post.
greetings
Click to expand...
Click to collapse
having the same issue as helobot.
update to 2.05 no problem
But after installing gapps it crashes in the setup phase
any ideas ?
Did you rooted the phone before installing gapps by twrp?
Rooted from twrp, installed gapps, rebooted.
After a few minutes it started, google setup wizard.
It crashes with an exception.
Gonna give it a shot in a few
Call me an idiot, but I didn't make a backup of the delivered stock ROM KitKat 2.26.
Please have you guys an image? I am stuck for good.
And cleaned the cache and dalvik partition too? Mine its working with no problems.
Cleaned cache etc.
I could hit me for being so stupid to forget backing the original ROM up.
I can easily go to a stock Chinese ROM but at least a KitKat Google ROM would be nice.
Señor or anyone, can you provide a image of 2.26?
Unfortunately I didn't backup it either , but soon I will create a zip file with my Rom with Google apps installed.
I will check Nubia site for older roms too.
Getting the hands on an 1.26 is relatively easy, but the googlefied 2.26 seems to be rather hard to find ...
vision0815 said:
Getting the hands on an 1.26 is relatively easy, but the googlefied 2.26 seems to be rather hard to find ...
Click to expand...
Click to collapse
Hi, I have my phone with 2.26, I have rooted it with kingo, if you can provide me a custom recovery I can do a nandroid back up of complete rom.
Hi Steveyknoxville, Señor shared a custom recovery based on twrp and that works very well. I would really appreciate if you could provide us with the 2.26 ROM
The link is in the first posting of this thread.
vision0815 said:
Hi Steveyknoxville, Señor shared a custom recovery based on twrp and that works very well. I would really appreciate if you could provide us with the 2.26 ROM
The link is in the first posting of this thread.
Click to expand...
Click to collapse
Hi, I have read that senor twrp does not work on 4.4.2, are you confirming it does. My biggest question I need answered before I do anything is, if I install twrp how do I go back to stock recovery so I can do Ota updates to get to lollipop. Thanks.
Sorry but I can't confirm weather it fully works or not. I followed señor's guide and updated the phone. But if I recall the thread correctly from nubia cn forums the stock ROM should be a slightly modified twrp anyways.
Try just going into the recovery mode.
You should be able to backup the ROM.
Thanks for the invested time.
Hi all!
I'm new here, so please instruct me if I'm doing anything wrong.
I have a Coolpad Y82-820. It's a Chinese phone, I think.
I'm in the process of getting it rooted. ---- Was rooted before, but an update on their side (to CoolUI V24. [phone model#]. 160407) removed the root and now makes it a bit difficult to root at the moment, though I'm sure it will be done eventually. For those who have this phone, I'd suggest not to update, as this update deletes any rooting applications installed on reboot/restart.
Once rooted, I don't really mind waiting, I would like to put a Custom Rom on this phone, but not sure what options are available. I see posts about the Coolpad Note/Dazen/Shine/Rogues etc. Though nothing about this one, though spec wise it's not too far off from the others.
I'd be grateful if anyone could help with confirmations, information, on how to select a correct custom rom for this device and the steps to do. Also if there's any info on how to root this current version, even better.
Thanks!
Some details of the phone below:
Model Number
Coolpad Y82-820
CPU
Qualcomm Technologies, Inc MSM8916 Quad-core 1.2 GHz
RAM
2G
Internal memory
Total 8G
Resolution
960 * 540
Android version
4.4.4
Kernel version
3.10.28
[email protected] #1
Thu Apr 7 17:01:56 CST 2016
Build number
4.4.005.150730.Y82_820
Any help possible?
Rooting maybe? Even possibly downgrading would be an option.
Johny2k9 said:
Any help possible?
Rooting maybe? Even possibly downgrading would be an option.
Click to expand...
Click to collapse
Did you try towelroot?It's best for rooting Kitkat.https://towelroot.com/
Røbin said:
Did you try towelroot?It's best for rooting Kitkat.https://towelroot.com/
Click to expand...
Click to collapse
Gave it a shot. Failed, as well. I've tried most of the popular rooting apps. King Root, Kingo, One click, and so on as well as a few Chinese rooting apps, as well. They've all failed.
The previous version was rooted with King Root though.
Johny2k9 said:
Gave it a shot. Failed, as well. I've tried most of the popular rooting apps. King Root, Kingo, One click, and so on as well as a few Chinese rooting apps, as well. They've all failed.
The previous version was rooted with King Root though.
Click to expand...
Click to collapse
In that case you have to root your phone manually by unlocking bootloader.But as a Chinese phone don't need to unlock bootloader.But you need to have a recovery that can install flashable zip.Most of this phone have built in recovery.You can go to recovery by turning off your phone and press power+volume down button.Then see if there's any option to install zip.
Røbin said:
In that case you have to root your phone manually by unlocking bootloader.But as a Chinese phone don't need to unlock bootloader.But you need to have a recovery that can install flashable zip.Most of this phone have built in recovery.You can go to recovery by turning off your phone and press power+volume down button.Then see if there's any option to install zip.
Click to expand...
Click to collapse
There is an option there to install zip files. Though I do not know the process well of doing so. Most zips I have tried have failed. I did install GMS several days ago using the install zip method. Not certain if that was a good idea though...
If I can find a flashable zip then I wouldn't mind giving it a try. I've restored this phone countless times hoping to go back to factory firmware, but that doesn't seem to be the case. It seems to go back to the most recent updated OTA which makes it unable to root with regular apps at the moment.
Not sure what the closest phone model for this phone would be. If you have ideas I'm willing to give them a shot an report back in with any findings.
Johny2k9 said:
There is an option there to install zip files. Though I do not know the process well of doing so. Most zips I have tried have failed. I did install GMS several days ago using the install zip method. Not certain if that was a good idea though...
If I can find a flashable zip then I wouldn't mind giving it a try. I've restored this phone countless times hoping to go back to factory firmware, but that doesn't seem to be the case. It seems to go back to the most recent updated OTA which makes it unable to root with regular apps at the moment.
Not sure what the closest phone model for this phone would be. If you have ideas I'm willing to give them a shot an report back in with any findings.
Click to expand...
Click to collapse
https://download.chainfire.eu/696/supersu/ go to this link,download UPDATE-SuperSU-v2.46.zip and install it.This is the way to have root manually.
Røbin said:
https://download.chainfire.eu/696/supersu/ go to this link,download UPDATE-SuperSU-v2.46.zip and install it.This is the way to have root manually.
Click to expand...
Click to collapse
I got an error:
正在查找更新包
正在打开更新包
正在验证更新包
E : failed to verify whole-file signature
E : signature verification failed 安装失败
我会汉语一点儿，所以这个汉字我都明白了，如果你有问题我可以试一试告诉你。 My Chinese isn't too bad, so if there's something you don't understand let me know.
Letting you know the steps I did, just in case I did it wrong.
- Downloaded the UPDATE-SuperSU-v2.46.zip
- Placed it on the phone internal memory (recovery only recognizes internal)
- Powered off
- Went into recovery mode
- Then tried installing the file.
Then the mentioned error.
Should I have restored the phone to the most recent OTA, cleared cache, data, first etc?
Johny2k9 said:
I got an error:
正在查找更新包
正在打开更新包
正在验证更新包
E : failed to verify whole-file signature
E : signature verification failed 安装失败
我会汉语一点儿，所以这个汉字我都明白了，如果你有问题我可以试一试告诉你。 My Chinese isn't too bad, so if there's something you don't understand let me know.
Letting you know the steps I did, just in case I did it wrong.
- Downloaded the UPDATE-SuperSU-v2.46.zip
- Placed it on the phone internal memory (recovery only recognizes internal)
- Powered off
- Went into recovery mode
- Then tried installing the file.
Then the mentioned error.
Should I have restored the phone to the most recent OTA, cleared cache, data, first etc?
Click to expand...
Click to collapse
Ok i'll give you a last solution to root your device.
first go to this linkhttp://www.file-upload.net/download-7267586/usb_driver.rar.html and download the driver file and extract the file.Now first enable developer options in your phone to enable usb debug and connect your phone to pc.In your pc right click on Computer/My PC icon and go to manager.click device manager and you will see your connected device.Now click on your device and find install driver,go and find the extracted file to install driver.After installing driver download root genius from this linkhttps://mega.nz/#!G4US0aTA!rfkmf4GSUJ75FSpq3_OBzKw58WLlExImjzlHVti5rbM,Install it and open the app.Your device will automaticlly connect to root genius.Now the final step is to click root word,click the green box,wait for 10 minute to complete the rooting process.your phone will reboot.all done.now check your device if its rooted or not by installing root checker app via google play store.
Røbin said:
Ok i'll give you a last solution to root your device.
first go to this linkhttp://www.file-upload.net/download-7267586/usb_driver.rar.html and download the driver file and extract the file.Now first enable developer options in your phone to enable usb debug and connect your phone to pc.In your pc right click on Computer/My PC icon and go to manager.click device manager and you will see your connected device.Now click on your device and find install driver,go and find the extracted file to install driver.After installing driver download root genius from this linkhttps://mega.nz/#!G4US0aTA!rfkmf4GSUJ75FSpq3_OBzKw58WLlExImjzlHVti5rbM,Install it and open the app.Your device will automaticlly connect to root genius.Now the final step is to click root word,click the green box,wait for 10 minute to complete the rooting process.your phone will reboot.all done.now check your device if its rooted or not by installing root checker app via google play store.
Click to expand...
Click to collapse
Also failed.
I guess it's too difficult to root this new version/update. If only I could downgrade then it might be possible to root.
Johny2k9 said:
Also failed.
I guess it's too difficult to root this new version/update. If only I could downgrade then it might be possible to root.
Click to expand...
Click to collapse
There's no available firmware to downgrade. Bad luck for you.
Røbin said:
There's no available firmware to downgrade. Bad luck for you.
Click to expand...
Click to collapse
Is upgrade impossible without rooting?
Johny2k9 said:
Is upgrade impossible without rooting?
Click to expand...
Click to collapse
You can upgrade or downgrade your android version without rooting but it has to be official firmware. If you want to flash custom rom you'll need custom recovery installed and unlocked bootloader.
Røbin said:
You can upgrade or downgrade your android version without rooting but it has to be official firmware. If you want to flash custom rom you'll need custom recovery installed and unlocked bootloader.
Click to expand...
Click to collapse
I wouldn't mind upgrading. Though what would be the process to get the official firmware?
Johny2k9 said:
I wouldn't mind upgrading. Though what would be the process to get the official firmware?
Click to expand...
Click to collapse
I think you didn't get what I said.You are already using updated android version. You can't update more if your service provider don't give anymore updates.And I also searched very hard to find official firmware for your device but unluckily your phone have very less information in web.So there's no one haven't uploaded any firmware or no discussion available for your device.You can though upgrade your device using custom rom but you need to have root and custom recovery .without root you can't install custom recovery.
Røbin said:
I think you didn't get what I said.You are already using updated android version. You can't update more if your service provider don't give anymore updates.And I also searched very hard to find official firmware for your device but unluckily your phone have very less information in web.So there's no one haven't uploaded any firmware or no discussion available for your device.You can though upgrade your device using custom rom but you need to have root and custom recovery .without root you can't install custom recovery.
Click to expand...
Click to collapse
Hahh... So after combing through various Chinese sites and using my limited knowledge of Chinese, I've got a ROM (previous version before there update), got the appropriate flashing software (CoolPad Download Assistant) and have successfully flashed it after disassembling the phone to get into fastboot.
Good news:
I am Rooted... again. With KingRoot.
Bad news:
The CoolPad has there update in the background. Found where it's stored and deleted. The Phone re-downloads the update.
A restart will probably update this phone making it un-rootable again.
Edit: Deleting the update file before immediately restarting gives an error in the update on restart, so I guess that's a good thing.
For now, I will just operate for now without turning the phone off. Though I do have the necessary files if I have to flash it again.
Rooting is the first requirement you mentioned... what do I need to do next? Download what? Compatible ROM's etc?
Johny2k9 said:
Hahh... So after combing through various Chinese sites and using my limited knowledge of Chinese, I've got a ROM (previous version before there update), got the appropriate flashing software (CoolPad Download Assistant) and have successfully flashed it after disassembling the phone to get into fastboot.
Good news:
I am Rooted... again. With KingRoot.
Bad news:
The CoolPad has there update in the background. Found where it's stored and deleted. The Phone re-downloads the update.
A restart will probably update this phone making it un-rootable again.
Edit: Deleting the update file before immediately restarting gives an error in the update on restart, so I guess that's a good thing.
For now, I will just operate for now without turning the phone off. Though I do have the necessary files if I have to flash it again.
Rooting is the first requirement you mentioned... what do I need to do next? Download what? Compatible ROM's etc?
Click to expand...
Click to collapse
If you have no interest in custom rom and now you can root your device then you don't need to do anything right now.And you are saying new update automatically downloading,just in download setting select "do not auto download"or"update via wifi only"this will prevent from auto downloading update.
Røbin said:
If you have no interest in custom rom and now you can root your device then you don't need to do anything right now.And you are saying new update automatically downloading,just in download setting select "do not auto download"or"update via wifi only"this will prevent from auto downloading update.
Click to expand...
Click to collapse
I disabled the update part, thank you.
I would prefer a custom rom, what options would I have?
Johny2k9 said:
I disabled the update part, thank you.
I would prefer a custom rom, what options would I have?
Click to expand...
Click to collapse
Not sure if there's any custom rom available for your phone You can somehow install custom twrp recovery but the main problem is custom rom availability.But I would suggest you to use xposed instead installing custom ROM.You can customize and control your device using xposed installer.
Røbin said:
Not sure if there's any custom rom available for your phone You can somehow install custom twrp recovery but the main problem is custom rom availability.But I would suggest you to use xposed instead installing custom ROM.You can customize and control your device using xposed installer.
Click to expand...
Click to collapse
Installed Xposed Installer, but the Download section is empty.
I am in China currently, so a lot of things may be blocked. A VPN should fix this, I believe.
What things I should install. Xposed Installer is new to me.
Dear forum,
I had installed the Nexus Custom ROM with TWRP on my Kindle HDX which worked out fine so far. Then I and wanted to go to CM11. Probably because my device was still locked and/or because I wiped too many things in the wipe-menu, my kindle is stuck in the Boot loop and stops loading while displaying the grey kindle logo. I am still able to access TWRP and the device is found by windows.
I would like to go back to the stock rom and read a lot of threads in the forum but I am not really sure where to start without making my situation worse. I tried to install back my backup (several *.win files) but that does not work. Can you please help me what I need to do?
Kind regards,
Aldaris001
Aldaris001 said:
Dear forum,
I had installed the Nexus Custom ROM with TWRP on my Kindle HDX which worked out fine so far. Then I and wanted to go to CM11. Probably because my device was still locked and/or because I wiped too many things in the wipe-menu, my kindle is stuck in the Boot loop and stops loading while displaying the grey kindle logo. I am still able to access TWRP and the device is found by windows.
I would like to go back to the stock rom and read a lot of threads in the forum but I am not really sure where to start without making my situation worse. I tried to install back my backup (several *.win files) but that does not work. Can you please help me what I need to do?
Kind regards,
Aldaris001
Click to expand...
Click to collapse
TWRP or Safestrap (version)? They are not the same thing. Makes a big difference in the potential solution set.
Thanks for your swift reply! I have TWRP 2.8.6.0 installed.
Aldaris001 said:
Thanks for your swift reply! I have TWRP 2.8.6.0 installed.
Click to expand...
Click to collapse
Strongly recommend unlocking bootloader with 1-click utility (here). Otherwise you run the risk of permanently bricking your device if the recovery partition holding TWRP becomes damaged/unbootable. Once unlocked you can flash a modified build of FireOS 4.5.5 from here
Of course, once unlocked you could flash a higher version of Nexus, CM 11 (both KitKat based), CM 12.1 (Lollipop), CM 13 (Marshmallow) or several other rom variants. Each is a heck of a lot better than Stock FireOS v4.
At some point you should also consider moving to the latest version of TWRP (here).
Hi Davey,
Thanks a lot for the hint! I have tried the 1-click bootloader but running in an issue that the ADB device is not recognized. The drivers seem to work though. Do I need to activate ADB in TWRP somewhere or is it activated by default? The ADB sideload option seem to be something else, right?
Aldaris001 said:
Hi Davey,
Thanks a lot for the hint! I have tried the 1-click bootloader but running in an issue that the ADB device is not recognized. The drivers seem to work though. Do I need to activate ADB in TWRP somewhere or is it activated by default? The ADB sideload option seem to be something else, right?
Click to expand...
Click to collapse
Drivers are always a PiTA with Windows and Amazon devices. You'll need to fight through it taking clues from various posts on the topic. Some tips:
- nothing needs to be enabled in TWRP
- drivers need to work in both ADB and Fastboot modes
- cleanest approach IMO:
>> launch windows device manager, tether device, see what shows up in device manager, uninstall those device(s), disconnect, reboot both devices (important), reconnect and then guide windows to the drivers of your choosing
Thanks a lot for your help, I got it running again! In the end it did not work with the 1-click method but manually I could unlock the bootloader and flashed CM 12.1.
Aldaris001 said:
Thanks a lot for your help, I got it running again! In the end it did not work with the 1-click method but manually I could unlock the bootloader and flashed CM 12.1.
Click to expand...
Click to collapse
Thanks for the update. Glad you got things sorted; manual unlocking isn't that bad with a little patience. CM 12.1 is solid (probably my next stop; still rocking Nexus) but keep an eye on CM 13 as the dev team hammers out a few final issues. Enjoy your liberated HDX!