Related
Hello to all,
I just tried to unlock and root my GSM Galaxy Nexus with OS X, following the terminal command line steps. I managed to unlock the bootloader, installed superuser, but when I try to access any root application it says that the phone is still not rooted. Could anyone help me please with some specific steps for OS X? I want to install CWM, but I don't know how to flash a ROM on the GN either...
Thank you in advance!
Did you flash the SU binary from CWM?
You will probably have to re-flash CWM through fastboot to get to it again unless you renamed install-recovery.sh
http://forum.xda-developers.com/showthread.php?t=1506536
hEaTLoE said:
Did you flash the SU binary from CWM?
You will probably have to re-flash CWM through fastboot to get to it again unless you renamed install-recovery.sh
http://forum.xda-developers.com/showthread.php?t=1506536
Click to expand...
Click to collapse
Thank you.
How do I flash CWM through fastboot? I downloaded filetransfer for mac, should I just copy the CWM ROM to the device? Or is there some specific folder I should put it in?
Buddhaa said:
Thank you.
How do I flash CWM through fastboot? I downloaded filetransfer for mac, should I just copy the CWM ROM to the device? Or is there some specific folder I should put it in?
Click to expand...
Click to collapse
fastboot flash recovery <name-of-recovery>.img
or if you have root access, you can download ROM manager from the play store
http://galaxynexusroot.com/galaxy-nexus-root/how-to-root-galaxy-nexus/ for a complete guide.
so pretty much what you want to do is,
1. download http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.0.2-maguro.img (MAGURO ONLY... GSM)
2. put it in the same folder as "fastboot-mac"
3. go into bootloader mode
4. fastboot-mac flash recovery <nameofrecovery>.img (I believe.. I could be wrong on this, I don't use mac but it should be somewhat similar)
zephiK said:
fastboot flash recovery <name-of-recovery>.img
or if you have root access, you can download ROM manager from the play store
http://galaxynexusroot.com/galaxy-nexus-root/how-to-root-galaxy-nexus/ for a complete guide.
so pretty much what you want to do is,
1. download http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.0.2-maguro.img (MAGURO ONLY... GSM)
2. put it in the same folder as "fastboot-mac"
3. go into bootloader mode
4. fastboot-mac flash recovery <nameofrecovery>.img (I believe.. I could be wrong on this, I don't use mac but it should be somewhat similar)
Click to expand...
Click to collapse
i'm pretty sure you have to put a ./ infront of fastboot... so it'd be like ./fastboot
Thank you very much!! I will try those steps, I am just Mister Paranoia when it comes to these things, so i want to make sure i am doing it right!
Sent from my Galaxy Nexus using xda premium
Buddhaa said:
Thank you very much!! I will try those steps, I am just Mister Paranoia when it comes to these things, so i want to make sure i am doing it right!
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
If you check the thread I posted above too, it's a guide on unlocking the bootloader and gaining root from a Mac. If you skip to the steps subsequent to locking the bootloader, you should be good to go!
I tried, and I have Superuser installed when I boot my phone, but when I try to access any root application, such as Root Explorer or Titanium backup, it doesn't allow me because it says the device is not rooted. There is no SU pop-up asking permissions either. I also downloaded CWM ROM MANAGER, tried to flash the recovery from there, but again it says it doesn't have permission.
Also half of the commands on terminal don't work...
Could anyone post a very easy step-by-step guide on how I could solve this please?
Thank you!
By the way, I am on 4.0.4
You are flashing a permanent recovery on your mac, right? fastboot flash recovery recovername.img Also, you put SU.zip on your SD card, then went into ClockworkMod recovery (volume up/down + power, choose recovery) and flashed SU.zip from your phone correct? It's still not working?
anton2009 said:
You are flashing a permanent recovery on your mac, right? fastboot flash recovery recovername.img Also, you put SU.zip on your SD card, then went into ClockworkMod recovery (volume up/down + power, choose recovery) and flashed SU.zip from your phone correct? It's still not working?
Click to expand...
Click to collapse
It did work! Thank you for the help!
Use my guide in my sig, sir.
ok you need to have clockworkmod installed...
Code:
fastboot flash recovery recovery.img
(insecure boot.img)
unzip boot.img.zip, boot to bootloader and
Code:
fastboot flash boot boot.img
or flash JRN84D-insecure-boot.zip from recovery
-put the CWM-SuperSU-v0.92-mod.zip on your sd and flash
done. :good:
if you have problems...
flash Koush's Jellybean repack (IMM76I OR IMM30D) http://d-h.st/Gkh
If recovery isn't sticking for you, delete recovery-from-boot.p in /system
I can do this for the other superuser as well...this is chainfire's super su
Thanks. May I clarify if I have to do both to get root or either one?
mcdull said:
Thanks. May I clarify if I have to do both to get root or either one?
Click to expand...
Click to collapse
the boot image is insecure...not necessarily needed
Oic.. thanks alot.
Is there any chance to pack the insecure kernel into cwm package as well?
I have no access to computer that allow me to apply fastboot flash. I am sure a lot of ppl will be in the same situation. Thanks alot.
mcdull said:
Oic.. thanks alot.
Is there any chance to pack the insecure kernel into cwm package as well?
I have no access to computer that allow me to apply fastboot flash. I am sure a lot of ppl will be in the same situation. Thanks alot.
Click to expand...
Click to collapse
sure, give me a minute
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
pablo1215 said:
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
Click to expand...
Click to collapse
bootloader mode -> reflash clockwork recovery using fastboot.
pablo1215 said:
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
Click to expand...
Click to collapse
fastboot a new one in...new one will stick
Code:
fastboot flash recovery recovery.img
Thanks guys appreciate the tip.
not working
Just flashed the two .zips. SuperSU is installed, but it says that the binary needs to be updated. When it tries to update it fails, and no root apps work.
krishmasand said:
Just flashed the two .zips. SuperSU is installed, but it says that the binary needs to be updated. When it tries to update it fails, and no root apps work.
Click to expand...
Click to collapse
reboot, then open supersu and then update
Worked like a charm, I've got clockwork back after a little adb action and now I'm restoring some apps with titanium. Can't wait to see the development on this. Just think I almost sold this phone and bought a Galaxy S3 today, may wait a week or so now.
Thanks guys you are amazing!!!
Flashed both zips in cwm
Super su app is there but needs to update binary
It fails on update
tramane said:
Flashed both zips in cwm
Super su app is there but needs to update binary
It fails on update
Click to expand...
Click to collapse
ok your the second guy...first hasn't responded back. did you reboot and try again?
which "jellybean" version are you on? koush's on rom manager seems to be the best (no wifi issues for one)
ogdobber said:
fastboot a new one in...new one will stick
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Is there a reason why my CWM won't stick? I fastboot a new one in and right after, I can access CWM from the bootloader menu if I don't boot into the OS yet. However, once I do boot into the OS and use ADB to reboot into recovery, it goes back to the Android with the red triangle.
What am I doing wrong? I'm usually pretty good with this stuff.
other superuser
still doesn't work, do you think you can try the other SuperUser app? D:
Enhanced said:
Is there a reason why my CWM won't stick? I fastboot a new one in and right after, I can access CWM from the bootloader menu if I don't boot into the OS yet. However, once I do boot into the OS and use ADB to reboot into recovery, it goes back to the Android with the red triangle.
What am I doing wrong? I'm usually pretty good with this stuff.
Click to expand...
Click to collapse
You'll need to delete that recovery from boot.p file otherwise it'll keep deleting CWM
[please delete]
IINexusII said:
You'll need to delete that recovery from boot.p file otherwise it'll keep deleting CWM
Click to expand...
Click to collapse
I knew common sense told me that I would need to delete the /system/recovery-from-boot.p file, but it wasn't posted here so I didn't bother.
Thanks.
Hi, i have this problem:
Two Galaxy Nexus, one is mine one of my friend 4.1.1 Yakju Maguro both.
I make the procedure with GNex TOOLKIT 7.8.
Install Drivers
Unlock Bootloader
Root
Flash CWM Touch
Download TWRP 2.2.2.0 through site and flash with adb in bootloader.
All works fine! ( mine)
For my friend same procedure, but flashed TWRP Recovery instead CWM
Install BusyBox. ( both with GNex TOOLKIT 7.8)
Recovery start only first time, then i get the Android with triangle and exclamation mark.
Made unroot, unloock and flashed stock Google rom.
Made same procedure as mine, and worked... Since i installed GooManager, and flashed TWRP.
Phone get super slow, Cpu at 90-100%!!!
Android System App doesn't show any threads that makes the cpu goes crazy.
Now i don't know what maybe the problems!!!
Partitioning problems with GNex TOOLKIT 7.8???
TWRP bugs?
My phone works fine, my friends install stock JB another time, root, unlock, but after flashing TWRP through GooManager, same problems...
What could it be?
Thank you very much!!! :good:
19blacktiger77 said:
Hi, i have this problem:
Two Galaxy Nexus, one is mine one of my friend 4.1.1 Yakju Maguro both.
I make the procedure with GNex TOOLKIT 7.8.
Install Drivers
Unlock Bootloader
Root
Flash CWM Touch
Click to expand...
Click to collapse
...
19blacktiger77 said:
Download TWRP 2.2.2.0 through site and flash with adb in bootloader.
Click to expand...
Click to collapse
ADB doesn't flash anything in bootloader, adb is not even available there, only fastboot.
19blacktiger77 said:
All works fine! ( mine)
For my friend same procedure, but flashed TWRP Recovery instead CWM
Install BusyBox. ( both with GNex TOOLKIT 7.8)
Recovery start only first time, then i get the Android with triangle and exclamation mark.
Click to expand...
Click to collapse
stock rom has a file (/system/recovery-from-boot.p) that overwrites the recovery if it finds something else instead of stock recovery (the "Android with triangle and exclamation mark" - pressing vol up+power here opens the recovery menu). delete or rename it.
19blacktiger77 said:
Made unroot, unloock and flashed stock Google rom.
Made same procedure as mine, and worked... Since i installed GooManager, and flashed TWRP.
Phone get super slow, Cpu at 90-100%!!!
Android System App doesn't show any threads that makes the cpu goes crazy.
Now i don't know what maybe the problems!!!
Partitioning problems with GNex TOOLKIT 7.8???
TWRP bugs?
My phone works fine, my friends install stock JB another time, root, unlock, but after flashing TWRP through GooManager, same problems...
What could it be?
Thank you very much!!! :good:
Click to expand...
Click to collapse
can't help you since you didn't do it manually through fastboot official steps. post your question in that toolkit's thread.
don't install a custom recovery from android, flash it from bootloader with fastboot. no need for root to flash it, you see. then just flash (with the recovery you just flashed, of course) a su.zip with su binary/apk and you'll be rooted. mount /system rw in recovery through adb, delete /system/recovery-from-boot.p, and you're done. reboot.
bk201doesntexist said:
ADB doesn't flash anything in bootloader, adb is not even available there, only fastboot.
Click to expand...
Click to collapse
Sorry, fastboot.
bk201doesntexist said:
stock rom has a file (/system/recovery-from-boot.p) that overwrites the recovery if it finds something else instead of stock recovery (the "Android with triangle and exclamation mark" - pressing vol up+power here opens the recovery menu). delete or rename it.
Click to expand...
Click to collapse
I read this, but i remember that with my phone i use a option with Galaxy Nexus ToolKit or Nexus Root Tolkit to prevent the recovery from be rewritten.
bk201doesntexist said:
can't help you since you didn't do it manually through fastboot official steps. post your question in that toolkit's thread.
don't install a custom recovery from android, flash it from bootloader with fastboot. no need for root to flash it, you see. then just flash (with the recovery you just flashed, of course) a su.zip with su binary/apk and you'll be rooted. mount /system rw in recovery through adb, delete /system/recovery-from-boot.p, and you're done. reboot.
Click to expand...
Click to collapse
My phone works fine, i can't understand why in phone's friend after installing GooManager and flash TWRP recovery, system got crazy...
If you did not use the toolkit I may get around my last arse helping you......
Beamed from Maguro
When going through the options before you install your twrp use option 5 to change the name and then use option 5 after you install twrp again... then the recovery will stick. It's all in the tool kit to read. Read everything that's in the instructions. It's right there when you go to install your recovery.
This is meant to be a friendly suggestion, so hopefully I won't get trounced but here goes. In the Sprint GNEX android development section, there are two stickies that explain the GNEX toolkit method of rooting, one by QBKing77 and the other by MSkip., two smart guys. A new guy or gal might think because there's no other way presented here that using a toolkit is the way to go. Maybe a correct, long form rooting guide could be placed along side these two guides in the development section.
In the Q and A section there is a stickie by Jobakuba that explains how to root the "right", long way. It might help new people and even people that have been around a while, if her guide or something similar was along side the QBKing videos and MSkips toolkit guide.
BTW, the QBKing video is new. He added the toolkit method fairly recently with the jellybean OTA. His new video replaces a video that showed the adb, fastboot method. When you go to the old video, you get redirected to the toolkit video.
// rant
// oh please, there's threads to teach how to use a toolkit? :good:
// :sarcasm:
bk201doesntexist said:
// rant
// oh please, there's threads to teach how to use a toolkit? :good:
// :sarcasm:
Click to expand...
Click to collapse
Two threads to teach people how to use the brainless toolkits... vs the 6 or 7 step guide by Jubakuba on how to actually do it yourself and know what's going on.
This is what's wrong with today's Android community.
OP. See here:
http://forum.xda-developers.com/showthread.php?t=1469909
Sent from my Galaxy Nexus using xda premium
El Daddy said:
OP. See here:
http://forum.xda-developers.com/showthread.php?t=1469909
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
EDIT - deleted
Sent from my Galaxy Nexus using Tapatalk 2
Hey guys, this is my first post on XDA forum.
So I've recently bought a nexus 7, I used wugfresh's root kit to root my nexus but then it didn't work... so I've tired the auto root by chainfire. Then I was able to get root. So then I went to playstore and downloaded rom manager to install CWM. I went to recovery then I get this message:
E : Cant mount /cache/recovery/log etc.....
I've tried everything I can do such as researching, changing recovery, and watching a youtube tutorial but nothing helped.
Thanks.
I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.
nhizzat said:
I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.
Click to expand...
Click to collapse
I tried to format using wugfresh couple times but still not working...
DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- https://developers.google.com/android/nexus/images
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.
_MetalHead_ said:
DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- Link Removed
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.
Click to expand...
Click to collapse
I tried to flash TWRP but its still the same error code
z3r0c311 said:
I tried to flash TWRP but its still the same error code
Click to expand...
Click to collapse
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.
_MetalHead_ said:
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.
Click to expand...
Click to collapse
It would be great if u could tell me the commands, im nubby with this fastboot thing.
z3r0c311 said:
It would be great if u could tell me the commands, im nubby with this fastboot thing.
Click to expand...
Click to collapse
I gave you the commands in my first post in this thread.
Here's a guide to get you started-
http://forum.xda-developers.com/showthread.php?t=2277112
Sorry for another nubby question but how do I get flash_all.bat?
z3r0c311 said:
Sorry for another nubby question but how do I get flash_all.bat?
Click to expand...
Click to collapse
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.
_MetalHead_ said:
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.
Click to expand...
Click to collapse
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.
z3r0c311 said:
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.
Click to expand...
Click to collapse
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?
_MetalHead_ said:
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?
Click to expand...
Click to collapse
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...
z3r0c311 said:
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...
Click to expand...
Click to collapse
Did the system image flash successfully?
_MetalHead_ said:
Did the system image flash successfully?
Click to expand...
Click to collapse
using flash-all command, yeah
z3r0c311 said:
using flash-all command, yeah
Click to expand...
Click to collapse
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.
_MetalHead_ said:
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.
Click to expand...
Click to collapse
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...
z3r0c311 said:
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...
Click to expand...
Click to collapse
No, you can only flash custom ROMs if you have a custom recovery.
Dear XDA Members,
I currently run stock 5.1.1 (14.6.A.1.236) with no modifications whatsoever and a locked bootloader.
I would like to install a custom rom (PAC-ROM LP-MR1 5.1.1) on my Z1C.
I did some research and these are the steps i came up with:
1. install sdk and drivers
2. unlock bootloader
3. fastboot flash recovery "fota.img" (shouldn't it specify somehow that i need it to be flashed on the fota partition?)
4. factory reset/wipe
5. install custom rom + gapps
Coming from a locked bootloader a fully stock phone is there anything else i need to do like a new bootloader or something?
Also I'll be doing it through Win 10 64bit, I hope that isn't a problem.
Any advice will be highly appreciated.
Thank you very much
ursidae1 said:
Dear XDA Members,
I currently run stock 5.1.1 (14.6.A.1.236) with no modifications whatsoever and a locked bootloader.
I would like to install a custom rom (PAC-ROM LP-MR1 5.1.1) on my Z1C.
I did some research and these are the steps i came up with:
1. install sdk and drivers
2. unlock bootloader
3. fastboot flash recovery "fota.img" (shouldn't it specify somehow that i need it to be flashed on the fota partition?)
4. factory reset/wipe
5. install custom rom + gapps
Coming from a locked bootloader a fully stock phone is there anything else i need to do like a new bootloader or something?
Also I'll be doing it through Win 10 64bit, I hope that isn't a problem.
Any advice will be highly appreciated.
Thank you very much
Click to expand...
Click to collapse
First things first... Root. If you already did that then you're on the right track.
1. If you're not doing major development stuff, don't install the whole sdk. See here - http://forum.xda-developers.com/showthread.php?p=48915118 There may be issues you'll have to work with on newer versions of Windows. I haven't done it on anything later than 7. Keep in mind, though, that you won't need the computer to flash your boot img or rom, but you will need it to unlock the bootloader.
2. -
3. You can do this with an app called Rashr on your phone with root. Just download a recovery img, then open Rashr and follow the instructions.
4-5. Boot into recovery, full wipe, (system data and caches), flash rom zip and gapps zip. Maybe best to not flash more than that at once to start, in case there's a problem and you have no way to figure out what it is.
BTW, PacMan is a great choice. I've been using it for months.
levone1 said:
First things first... Root. If you already did that then you're on the right track.
1. If you're not doing major development stuff, don't install the whole sdk. See here - http://forum.xda-developers.com/showthread.php?p=48915118 There may be issues you'll have to work with on newer versions of Windows. I haven't done it on anything later than 7. Keep in mind, though, that you won't need the computer to flash your boot img or rom, but you will need it to unlock the bootloader.
2. -
3. You can do this with an app called Rashr on your phone with root. Just download a recovery img, then open Rashr and follow the instructions.
4-5. Boot into recovery, full wipe, (system data and caches), flash rom zip and gapps zip. Maybe best to not flash more than that at once to start, in case there's a problem and you have no way to figure out what it is.
BTW, PacMan is a great choice. I've been using it for months.
Click to expand...
Click to collapse
Thanks a lot for your reply.
I was reading on the cyanogen mod wiki how-to for our phone and it doesn't require a prior root.
I did those steps on my xperia m and it worked and i had never rooted it, the only difference is that i flashed cyanogen recovery and install cm12 which basically roots the phone and then flashed fota recovery.
Should i go this way again to gain root or would you recommend an easier root method for my stock build which is the newest.
If you recommend another root method when should it occur? prior unlocking the bootloader or afterwards?
Thanks
If this is your first time unlocking your bootloader, make sure you backup your DRM-Keys! You need to be rooted for that.
They are lost when bootloader gets unlocked. Some features in regards of camera performance are lost for example.
ursidae1 said:
Thanks a lot for your reply.
I was reading on the cyanogen mod wiki how-to for our phone and it doesn't require a prior root.
I did those steps on my xperia m and it worked and i had never rooted it, the only difference is that i flashed cyanogen recovery and install cm12 which basically roots the phone and then flashed fota recovery.
Should i go this way again to gain root or would you recommend an easier root method for my stock build which is the newest.
If you recommend another root method when should it occur? prior unlocking the bootloader or afterwards?
Thanks
Click to expand...
Click to collapse
True, if bl is unlocked, then you can flash the kernel and recovery via fastboot, then flash your rom. You may need the boot.img from your rom zip file. Then use commands 'fastboot flash boot' for the boot img, and 'fastboot flash recovery' for recovery. If you're rooted already, you can just do it on the phone.
levone1 said:
True, if bl is unlocked, then you can flash the kernel and recovery via fastboot, then flash your rom. You may need the boot.img from your rom zip file. Then use commands 'fastboot flash boot' for the boot img, and 'fastboot flash recovery' for recovery. If you're rooted already, you can just do it on the phone.
Click to expand...
Click to collapse
This is fantastic.
Do you think itll be ok to fastboot flash boot boot.img from cm12.1 rom zip then fastboot flash recovery fota.img instead of the cyanogen recovery that comes with cm12.1?
Do you think that might cause an issue?
ursidae1 said:
This is fantastic.
Do you think itll be ok to fastboot flash boot boot.img from cm12.1 rom zip then fastboot flash recovery fota.img instead of the cyanogen recovery that comes with cm12.1?
Do you think that might cause an issue?
Click to expand...
Click to collapse
Should be fine. It's also a 1 second operation to extract boot.img from your rom zip, which you need already downloaded and on your SD card before you flash imgs. You might even be fine without flashing the boot img - can't hurt to try. Just flash the recovery and reboot and see if you get a purple light. Then, volume button changes purple to orange, and you're in recovery. Some recoveries don't work with some kernels, (been my experience).
levone1 said:
Should be fine. It's also a 1 second operation to extract boot.img from your rom zip, which you need already downloaded and on your SD card before you flash imgs. You might even be fine without flashing the boot img - can't hurt to try. Just flash the recovery and reboot and see if you get a purple light. Then, volume button changes purple to orange, and you're in recovery. Some recoveries don't work with some kernels, (been my experience).
Click to expand...
Click to collapse
I now have cm12.1 with cyanogen recovery.
Which recovery is best for our phone, which one do you use?
I can find 2 options:
FOTA TWRP 2.8.6.0 (http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719)
XZDualRecovery (http://forum.xda-developers.com/showthread.php?t=2647480)
Thanks a lot
ursidae1 said:
I now have cm12.1 with cyanogen recovery.
Which recovery is best for our phone, which one do you use?
I can find 2 options:
FOTA TWRP 2.8.6.0 (http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719)
XZDualRecovery (http://forum.xda-developers.com/showthread.php?t=2647480)
Thanks a lot
Click to expand...
Click to collapse
I have only used xzdr with stock rom. I think in the past I've had it not work for me on CM, so I just stick to straight twrp by default. I know NUT has always been hard at work and has made steady improvements, so maybe not an issue now. Personally I realized that I only need 1 recovery anyway. There's a newer Twrp here - http://forum.xda-developers.com/crossdevice-dev/sony/twrp-v2-8-6-0-f2fs-z1-z1c-z2-z3-z3c-t3098573
One important fact that has already been probably mentioned is that installing custom roms on your XPERIA will worsen your camera, esp the front one. Keep this in mind.