Database Users

[Q] can't get to recovery mode after unlocking

Hi, a bit of noob but i did googled alot
My plan was:
Unlock and root with nexus 4 toolkit.
Do nandroid backup
Flash PA rom.
step 1 went okay,
afterwards i tried to go to recovery mode inorder to backup but i got the lying android with the red warning sign.
I did backup using Rom Manager and nexus 4 toolkit but I'm worried I can't get to recovery mode if something goes wrong.
How shall I proceed before flashing the rom?

The robot lying on it's back is the stock recovery. You need to flash CWM/TWRP before you can do a Nandroid

itayze said:
Hi, a bit of noob but i did googled alot
My plan was:
Unlock and root with nexus 4 toolkit.
Do nandroid backup
Flash PA rom.
step 1 went okay,
afterwards i tried to go to recovery mode inorder to backup but i got the lying android with the red warning sign.
I did backup using Rom Manager and nexus 4 toolkit but I'm worried I can't get to recovery mode if something goes wrong.
How shall I proceed before flashing the rom?
Click to expand...
Click to collapse
Do yourself a favour and learn how to use ADB instead of toolkits that do more harm than good if used by inexperienced users and you`ll learn to do it the right way.
Look here http://forum.xda-developers.com/showthread.php?t=1474956 for how to.
Youtube tutorial link http://www.youtube.com/watch?v=ZY4KSrgi-rE.

itayze said:
Hi, a bit of noob but i did googled alot
My plan was:
Unlock and root with nexus 4 toolkit.
Do nandroid backup
Flash PA rom.
step 1 went okay,
afterwards i tried to go to recovery mode inorder to backup but i got the lying android with the red warning sign.
I did backup using Rom Manager and nexus 4 toolkit but I'm worried I can't get to recovery mode if something goes wrong.
How shall I proceed before flashing the rom?
Click to expand...
Click to collapse
If you have Rom Manager Installed and are rooted you should be able to install CWM thru it.

don't have flash recovery on rom manager
I don't have the the "Flash CWM" recovery option on rom manager,
I've attached a screen of what I do have,
I did explore the Recovery Setup but wasn't able to do anything usefull.
Any advice?

itayze said:
I don't have the the "Flash CWM" recovery option on rom manager,
I've attached a screen of what I do have,
I did explore the Recovery Setup but wasn't able to do anything usefull.
Any advice?
Click to expand...
Click to collapse
according to ROM Manager you already have CWM installed and its up to date. Have you tried booting into recovery using ROM Manager?

When I press reboot to recovery directly from rom manager it works...
I'm just affraid that in case that I brick or mess up something I won't be able to get to stock recovery mode.

volume down + power button = bootloader (android on his back) also called fastboot mode
use volume buttons to scroll to recovery then press power button to select it
you should then be in CWM recovery if its installed correctly.
If you are using a custom recovery your stock recovery is gone. You would have to use fastboot to flash the stock recovery image back onto the phone. Its rather simple to do as is flashing the stock image file back onto the phone.

that is why I started this thread.
After I Unlocked and rooted I wasn't able to fastboot and go to recovery mode, it showed my the android on his back.
I've tried it again now and it still doesn't work.
but when I boot directly from rom manager it works...
Edit: I posted before you edited your comment.
even though I don't know adb, should I learn and follow this guide?
http://www.androidauthority.com/nexus-4-clockworkmod-recovery-134114

itayze said:
that is why I started this thread.
After I Unlocked and rooted I wasn't able to fastboot and go to recovery mode, it showed my the android on his back.
I've tried it again now and it still doesn't work.
but when I boot directly from rom manager it works...
Click to expand...
Click to collapse
There is a bug that restores the stock recovery after a reboot and there should be an option in the root toolkit to fix it. Not saying this is what happened but it may have. The stock recovery is stored in system memory somewhere and the bug fix just removes it so it won't restore itself after reboot.
Follow efrants guide for ADB and fastboot
http://forum.xda-developers.com/showthread.php?t=2010312

kzoodroid said:
There is a bug that restores the stock recovery after a reboot and there should be an option in the root toolkit to fix it. Not saying this is what happened but it may have. The stock recovery is stored in system memory somewhere and the bug fix just removes it so it won't restore itself after reboot.
Follow efrants guide for ADB and fastboot
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Its not a bug. Its a script. Intended feature.
Sent from my Nexus 4 using xda premium

El Daddy said:
Its not a bug. Its a script. Intended feature.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I call it a bug because its an annoying feature. There are a number of threads no how to remove it but using a toolkit to do it is just as easy.

thank you,
but after I've read what you wrote about the bug I open the nexus root tool kit and then I realized what I should have done.
I pressed Custom recovery checkbox and rooted again.
now it works !

itayze said:
thank you,
but after I've read what you wrote about the bug I open the nexus root tool kit and then I realized what I should have done.
I pressed Custom recovery checkbox and rooted again.
now it works !
Click to expand...
Click to collapse
Glad you got it working. I would still learn adb and fastboot. Though I too use the tool kit every now and then out of convenience.

Install CWM on Locked Bootloader

Can i install CWM on locked bootloader?

Ben Ling said:
Can i install CWM on locked bootloader?
Click to expand...
Click to collapse
Yes.
An 'exploit' has recently become available for ROOTING the Nexus 7 without unlocking the BOOTLOADER.
This 'exploit' works... I have tested it myself.
Until recently, I believed that because FASTBOOT wasn't an option (as a result of a LOCKED BOOTLOADER), there was no way of FLASHING anything.
Happily, I was disabused of this notion by bftb0... and I can confirm, you can indeed install CWM (or TWRP) with a locked BOOTLOADER.
-----------------------------
Here's how...
First, you need to run this 'exploit' to acquire ROOT.
Upon reboot, you should now be rooted, with Chainfires SuperSU package and associated SU binary installed.
It's important that you are ROOTED before you proceed.
Next, get Android Terminal Emulator from PlayStore.
Download a CUSTOM RECOVERY .img of your choice... either CWM (Both 'Grouper' and 'Tilapia' variants are available)...
...or TWRP for 'Grouper' (N7 WiFi) or TWRP for 'Tilapia' (N7 3G).
Rename it to recovery.img... and copy it to the root of the Nexus 7's internal storage (emulated SD card).
In Terminal Emulator, run the following command...
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Upon completion of this command, shutdown and reboot your device into the BOOTLOADER, and from there, boot into your CUSTOM RECOVERY... in pretty much the same way had you FASTBOOT FLASHED it.
-----------------------------
You are now free to flash whatever ROMs or kernels you like.
However, a word of caution... because the BOOTLOADER remains locked, FASTBOOT is strictly off limits; it simply won't work.
So the first thing you should do after flashing TWRP or CWM is...
*** MAKE A NANDROID BACKUP ***
If the device becomes 'wedged/bootlooped' as a result of some ROM flash gone wrong, then you will have no choice but to unlock the BOOTLOADER (with full wipe) in order to fix it.
But if you have a NANDROID backup... piece of cake... just restore.
-----------------------------
Credits and kudos must go to XDA members, nhshah7, who made this 'exploit' available and bftb0, whose post pointed me in the right direction, with regard to the 'dd' command.
-----------------------------
I can confirm all of this works... my Nexus 7 is currently rooted, running a custom recovery (TWRP), with a custom ROM and Kernel (see sig) installed - all sitting behind a LOCKED BOOTLOADER.
...no Factory Reset (wipe) required...
...and no Unlocked Padlock Symbol upon boot.
Rgrds,
Ged.

Previously I installed cwm and can boot,just 1 time.
I tried to boot into but nothing.
What to do?
Sent from my Sony Xperia™ sola using XDA Premium App

@GedBlake well it works for the first time for me as well,.,., used the TWRP latest..,.,.
afterwards it says "no command"

SSyar said:
@GedBlake well it works for the first time for me as well,.,., used the TWRP latest..,.,.
afterwards it says "no command"
Click to expand...
Click to collapse
This is really peculiar... I had a few problems myself, initially... but I just assumed I made a typo mistake in TE - but I never had a "no command" message. It took me two or three goes before I got it to work.
And it works fine now, without problems.
I recall reading, a while ago, you had to delete a file from /system called recovery-from-boot.p after flashing a custom recovery in order to get the custom recovery to stick. I never had to do this myself, maybe 'cos I'm running a custom ROM.
Are you on stock, or running a custom ROM?
Rgrds,
Ged.

GedBlake said:
This is really peculiar... I had a few problems myself, initially... but I just assumed I made a typo mistake in TE - but I never had a "no command" message. It took me two or three goes before I got it to work.
And it works fine now, without problems.
I recall reading, a while ago, you had to delete a file from /system called recovery-from-boot.p after flashing a custom recovery in order to get the custom recovery to stick. I never had to do this myself, maybe 'cos I'm running a custom ROM.
Are you on stock, or running a custom ROM?
Rgrds,
Ged.
Click to expand...
Click to collapse
I'm on stock JB 4.2.2 JDQ39 Wi-Fi & 3G version,so what to do now?
Sent from my Asus Google Nexus 7 using XDA Premium

Ben Ling said:
I'm on stock JB 4.2.2 JDQ39 Wi-Fi & 3G version,so what to do now?
Sent from my Asus Google Nexus 7 using XDA Premium
Click to expand...
Click to collapse
Have you tried running the dd command again?... As I previously mentioned, it took two or three attempts, before it 'stuck' on my N7.
Now I have no problem booting into TWRP... similarly, I have tested this procedure with CWM - and again no problems.
With a root capable file manager, you could try deleting (or renaming) the file recovery-from-boot.p which can be found in /system, and then try again.
Rgrds,
Ged.

GedBlake said:
Have you tried running the dd command again?... As I previously mentioned, it took two or three attempts, before it 'stuck' on my N7.
Now I have no problem booting into TWRP... similarly, I have tested this procedure with CWM - and again no problems.
With a root capable file manager, you could try deleting (or renaming) the file recovery-from-boot.p which can be found in /system, and then try again.
Rgrds,
Ged.
Click to expand...
Click to collapse
How to boot into cwm?press volume button?
Sent from my Google Nexus 7 using XDA Premium App

Ben Ling said:
How to boot into cwm?press volume button?
Sent from my Google Nexus 7 using XDA Premium App
Click to expand...
Click to collapse
Shut down the tablet completely.
Press and hold the VOL DOWN button... whilst holding, press the POWER button.
This will boot you into the BOOTLOADER.
Using the VOL buttons, navigate to RECOVERY.
Press the POWER button to select.
Rgrds,
Ged.

Just tested this method... again... (using dd to install a Custom Recovery)... with both CWM and TWRP... and in both instances, the installations survived a reboot. So I'm puzzled why there seems to be a problem here.
---------------------------------
I have semi-automated the process in order to avoid typing long complicated commands into Android Terminal Emulator. A process, which, by it's nature, is subject to typographical error.
Here's how...
Download the Custom Recovery of your choice to your Nexus 7.
Rename it to recovery.img
Copy it to the root of the emulated SD card (internal storage).
---------------------------------
Download this script file...
writerecovery.zip
Unzip and copy it to the root of the emulated SD card (internal storage).
(Alongside the recovery.img).
---------------------------------
Install Script Manager from Google Playstore.
Open Script Manager and locate the script file writerecovery.sh on the root of the emulated SD card.
Press ENTER on it...
Select OPEN AS... Script/Executable...
Select SU (root) from the toolbar...
Select Run...
The script will now execute the following command...
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
...writing the recovery.img to the recovery partition.
See attached thumbnails for the sort of thing you should expect to see.
---------------------------------
I have tested this method several times... switching between CWM and TWRP. And performing multiple reboots, to ensure that the Custom Recovery 'stuck' in each instance.
---------------------------------
Hope this works... if it doesn't... then I'm at a loss to explain why.
Maybe somebody with more technical knowledge can assist.
All I know, is it works for me... on my Nexus 7.
Rgrds,
Ged.

well i installed recovery using goo manager ,.,. got this response from other thread and is working for me ,.,., goo manager also has the option to restart in recovery so really good for me

Help with my Condition
OK, I need help with the following Scenario with Nexus 7 2012 Wifi
My USB Port is damaged. Managed to charge batter with external wires. After that I was able to:
> Root my Nexus7 with KingRoot app (several tries does the trick)
> Install CWM (non-touch) with ROM Manager
> Boot into CWM and do a dummy Flash of Update-SuperSU.zip file just to see if it works on Locked Bootloader. It was successful.
Now I came across your thread, What I need help with is:
WILL I BE ABLE TO FLASH A CUSTOM ROM + GAPPS on a Locked Bootloader via CWM ?
This is going to be a one way ride for me, if I brick I have a paperweight.
(I have however a Backup from CWM, which I can restore if the tablet manages to boot into CWM after bricking)
Need assistance, opinions, strategy with this. Response Awaited.

junisheikh said:
OK, I need help with the following Scenario with Nexus 7 2012 Wifi
My USB Port is damaged. Managed to charge batter with external wires. After that I was able to:
> Root my Nexus7 with KingRoot app (several tries does the trick)
> Install CWM (non-touch) with ROM Manager
> Boot into CWM and do a dummy Flash of Update-SuperSU.zip file just to see if it works on Locked Bootloader. It was successful.
Now I came across your thread, What I need help with is:
WILL I BE ABLE TO FLASH A CUSTOM ROM + GAPPS on a Locked Bootloader via CWM ?
This is going to be a one way ride for me, if I brick I have a paperweight.
(I have however a Backup from CWM, which I can restore if the tablet manages to boot into CWM after bricking)
Need assistance, opinions, strategy with this. Response Awaited.
Click to expand...
Click to collapse
Hi, junisheikh...
To answer your question...
junisheikh said:
"WILL I BE ABLE TO FLASH A CUSTOM ROM + GAPPS on a Locked Bootloader via CWM ?"
Click to expand...
Click to collapse
Yes, you should be able to.
---
The bootloader lock state is irrelevant when it comes to flashing stuff via a Custom Recovery (such as CWM or TWRP).
All an unlocked bootloader does, is it allows the device to accept fastboot flash commands from a connected PC or Mac, and which is the usual way of flashing a Custom Recovery, and then subsequently rooting it.
I would, however, advise against using CWM. ClockWorkMod Recovery is old and hasn't been updated for quite some time, and may cause problems.
Instead, you should take a look at TWRP (TeamWin Recovery Project). This Custom Recovery has a better user interface, and is less likely to cause you problems.
---
Although your bootloader is locked, you have managed to acquire root via KingRoot... which means you can flash a Custom Recovery with the Flashify app...
https://play.google.com/store/apps/details?id=com.cgollner.flashify
This app allows you to flash Recoveries and Boot images (stock and custom) directly from the device itself, providing the device is rooted. The free version of Flashify has a limit of 3 flashes per day. This shouldn't be a problem though... Custom Recoveries aren't something you generally flash on a regular basis.
(See my attached screenshots for a flavour of how Flashify works.)
---
You can find the latest version of TWRP for the Nexus 7 WiFi model here...
http://techerrata.com/browse/twrp2/grouper
Download to your Nexus 7, and use the Flashify app to flash.
And then download whatever Custom ROM+GAPPS you like, and flash via TWRP.
Incidentally, the NANDROID backup you've already created with CWM is NOT compatible with TWRP. So you'll need to create a new NANDROID backup, should you choose to flash TWRP.
---
junisheikh said:
This is going to be a one way ride for me, if I brick I have a paperweight.
Click to expand...
Click to collapse
This is possible, because you don't have access to fastboot (due to your broken USB port) you won't be able to fastboot flash back to Google Factory stock should you not be able to boot Android (for whatever reason) after flashing some Custom ROM. But providing you have a NANDROID backup and a Custom Recovery (CWM or TWRP) installed, you **should** be able to recover from softbricks such as bootloops. But having said that, I would tread carefully.
Hope this helps, and good luck.
Rgrds,
Ged.

[help] root n910c 5.1.1 oj5

I tried several steps to root this new firmware but i fail so i decided to ask help from devgods to guide me, i know this is a nooooooob question and is not new but i dare asking than bricking my phone. so anyone know steps to root this firmware?
PS. please dont give me link to obsolete sites and with old steps of rooting. thank you
...also kingroot doesnt work

Any results ? I also want to root my device (only for xposed), but i searching xda and find nothing.

zuli007 said:
Any results ? I also want to root my device (only for xposed), but i searching xda and find nothing.
Click to expand...
Click to collapse
the reason why i want to root my device is because i want to install TWRP and flash custom rom and kernels. well i found a way to install TWRP without ROOT. in case you only want too root your device try flashing custom Kernel which is ROOT ready eg Talexop (my personal favorite) or follow THIS STEPS after flashing TWRP
To install TWRP (no ROOT required)
>Open ODIN
>Press AP and choose THIS .IMG
>Put your Phone on Donwload Mode ( POWER - HOME - VOL DOWN)
>START
Now you can access TWRP (POWER - HOME - VOL UP) and Flash Custom ROMs and KERNELs:good:
CHEERS:highfive:

trixhammerbord said:
the reason why i want to root my device is because i want to install TWRP and flash custom rom and kernels. well i found a way to install TWRP without ROOT. in case you only want too root your device try flashing custom Kernel which is ROOT ready eg Talexop (my personal favorite) or follow THIS STEPS after flashing TWRP
To install TWRP (no ROOT required)
>Open ODIN
>Press AP and choose THIS .IMG
>Put your Phone on Donwload Mode ( POWER - HOME - VOL DOWN)
>START
Now you can access TWRP (POWER - HOME - VOL UP) and Flash Custom ROMs and KERNELs:good:
CHEERS:highfive:
Click to expand...
Click to collapse
I flashed TWRP via odin and i got the message Pass. But when i reboot to recovery stock recovery is there. NO TWRP recovery.

https://dl.twrp.me/treltexx/
you can flash ".img.tar" with odin not ".img"

mudur1998 said:
https://dl.twrp.me/treltexx/
you can flash ".img.tar" with odin not ".img"
Click to expand...
Click to collapse
Yes Flash the file with .tar extension.

mjrifath said:
Yes Flash the file with .tar extension.
Click to expand...
Click to collapse
no bro flash it with the file linked from my previous post
the file extension is correct its .img

Can someone please create a thourough start to finish guide on converting, rooting

Can someone please create a thourough start to finish guide on converting, rooting, recovery, and rom installations?
listen im no noob but im no mater either ive been rooting since the original TMO G1 and it has gotten very complex on top of that ive missed alot since i got my note 4 retail (out of the game) anyways someeone please compile a step by step list of what to do and where to find the neccasary files. and in what order.
please and thank you

For BL unlocking follow this
For rooting
If staying on stock:
Boot into download mode (VOL-DOWN + HOME + POWER) and flash twrp-3.0.2-0-trltevzw via ODIN (MAKE SURE YOU UNCHECK AUTO-REBOOT!!!).
Battery pull phone and then boot straight into recovery (VOL-UP + HOME + POWER) to finish the recovery install process or else it will install the default android recovery.
Then flash the Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P kernal via recovery.
Then flash the BETA-SuperSU-v2.71-20160331103524 via recovery.
Reboot.
If going to a different rom, you should just be able to flash the rom via recovery and get right in. But results may very, check the forums.

refusedchaos said:
For BL unlocking follow this
For rooting
If staying on stock:
Boot into download mode (VOL-DOWN + HOME + POWER) and flash twrp-3.0.2-0-trltevzw via ODIN (MAKE SURE YOU UNCHECK AUTO-REBOOT!!!).
Battery pull phone and then boot straight into recovery (VOL-UP + HOME + POWER) to finish the recovery install process or else it will install the default android recovery.
Then flash the Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P kernal via recovery.
Then flash the BETA-SuperSU-v2.71-20160331103524 via recovery.
Reboot.
If going to a different rom, you should just be able to flash the rom via recovery and get right in. But results may very, check the forums.
Click to expand...
Click to collapse
thank you very much i was a little frustratrated because it seems like the info is very fragmented

Can someone please tell me where I have gone wrong.
I have gotten temproot via kingroot installed and was able to get the unlocker to run and I can see that the device is now a developer device. I am trying to get root to work but not having any luck.
I follwed the instructions at http://forum.xda-developers.com/note-4-verizon/general/guide-noobs-guide-to-perm-root-twrp-t3360883 and had problems in step 8 when trying to run super-sume. I ran it successfully for stage 1 but then it hung when trying to run stage 2. However, I was able to move on to step 9 and install TWRP and the emotion kernel. I have done a full reset and tried a 2nd time but still no luck in getting permament root access.
Root checker shows no root access and superSU is installed but shows no su binary installed.
If I run SuperSUME-Pro then it shows the device is wrte=protected
It seems I can run kingroot again to gain temp root access but not perm root access.
Any ideas on how to proceed from here?

mlcampbe said:
Can someone please tell me where I have gone wrong.
I have gotten temproot via kingroot installed and was able to get the unlocker to run and I can see that the device is now a developer device. I am trying to get root to work but not having any luck.
I follwed the instructions at http://forum.xda-developers.com/note-4-verizon/general/guide-noobs-guide-to-perm-root-twrp-t3360883 and had problems in step 8 when trying to run super-sume. I ran it successfully for stage 1 but then it hung when trying to run stage 2. However, I was able to move on to step 9 and install TWRP and the emotion kernel. I have done a full reset and tried a 2nd time but still no luck in getting permament root access.
Root checker shows no root access and superSU is installed but shows no su binary installed.
If I run SuperSUME-Pro then it shows the device is wrte=protected
It seems I can run kingroot again to gain temp root access but not perm root access.
Any ideas on how to proceed from here?
Click to expand...
Click to collapse
Install SuperSU from TWRP. Does that work?

If you Developer mode and twrp but no root, then what you need to do is install emotional kernel from twrp and reboot device then boot back into twrp and install SuperSU zip and reboot device you should be fine.

After re-checking my recovery I do not believe that I have TWRP installed after all. I was booting into android recovery and it hit me I was not seeing what I expected to see. I need to work on getting TWRP installed. I do indeed have the custom kernel and developer mode enabled!!

refusedchaos said:
For BL unlocking follow this
For rooting
If staying on stock:
Boot into download mode (VOL-DOWN + HOME + POWER) and flash twrp-3.0.2-0-trltevzw via ODIN (MAKE SURE YOU UNCHECK AUTO-REBOOT!!!).
Battery pull phone and then boot straight into recovery (VOL-UP + HOME + POWER) to finish the recovery install process or else it will install the default android recovery.
Then flash the Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P kernal via recovery.
Then flash the BETA-SuperSU-v2.71-20160331103524 via recovery.
Reboot.
If going to a different rom, you should just be able to flash the rom via recovery and get right in. But results may very, check the forums.
Click to expand...
Click to collapse
So what you posted above is all that you need to do for root? You definitely have a much more concise explanation than the main thread. The other instructions made me feel like I was back on my old Droid 2 working from the giant tutorial threads over on rootzwiki, hah.
I'm also guessing that as you mentioned elsewhere that if we wish to run a custom ROM we'll have to reflash the stock kernel before doing so?

Does it matter whether or not its 4.4.4 or 5.1.1
refusedchaos said:
For BL unlocking follow this
For rooting
If staying on stock:
Boot into download mode (VOL-DOWN + HOME + POWER) and flash twrp-3.0.2-0-trltevzw via ODIN (MAKE SURE YOU UNCHECK AUTO-REBOOT!!!).
Battery pull phone and then boot straight into recovery (VOL-UP + HOME + POWER) to finish the recovery install process or else it will install the default android recovery.
Then flash the Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P kernal via recovery.
Then flash the BETA-SuperSU-v2.71-20160331103524 via recovery.
Reboot.
If going to a different rom, you should just be able to flash the rom via recovery and get right in. But results may very, check the forums.
Click to expand...
Click to collapse
Does it matter whether or not its 4.4.4 or 5.1.1

ttall8ball said:
Does it matter whether or not its 4.4.4 or 5.1.1
Click to expand...
Click to collapse
If you're wanting to unlock the bootloader, root and install TWRP then no it doesn't matter. Now if you want to install a custom ROM that is 5.1.1 then you WILL have to be on that firmware if you are currently on 4.4.4
If anyone helps, plz give thanks?
N910V ? BL / KYUBI ROM

MissionImprobable said:
So what you posted above is all that you need to do for root? You definitely have a much more concise explanation than the main thread. The other instructions made me feel like I was back on my old Droid 2 working from the giant tutorial threads over on rootzwiki, hah.
I'm also guessing that as you mentioned elsewhere that if we wish to run a custom ROM we'll have to reflash the stock kernel before doing so?
Click to expand...
Click to collapse
The instructions for rooting suggest installing the Emotion kernel first.
Many of the ROMs available to flash will suggest which kernel to use. You can go directly to that kernel.

I need a little info, my note I just got is already rooted. So I didn't have the joy to do it. A co worker just picked up a refurbished and it has 5.0.1 ., is the 2bog5 able to be rooted?

bingo6104 said:
I need a little info, my note I just got is already rooted. So I didn't have the joy to do it. A co worker just picked up a refurbished and it has 5.0.1 ., is the 2bog5 able to be rooted?
Click to expand...
Click to collapse
Yes it can. But I am pretty sure that you must unlock the bootloader first unless you already have a DevEd.
If anyone helps, plz give thanks?
N910V ? BL / KYUBI ROM

stajam said:
Yes it can. But I am pretty sure that you must unlock the bootloader first unless you already have a DevEd.
If anyone helps, plz give thanks?
N910V ? BL / KYUBI ROM
Click to expand...
Click to collapse
Thanks, I thought that from what I have been reading. To many guides, need to be complied into 2 guides and sticky on the forum for rusty people like me lol
Sent from my SM-N920V using Tapatalk

No problem bruh.
If anyone helps, plz give thanks?
N910V ? BL / KYUBI ROM

ttall8ball said:
Does it matter whether or not its 4.4.4 or 5.1.1
Click to expand...
Click to collapse
Thanks, I got it done
---------- Post added at 08:52 AM ---------- Previous post was at 08:49 AM ----------
stajam said:
If you're wanting to unlock the bootloader, root and install TWRP then no it doesn't matter. Now if you want to install a custom ROM that is 5.1.1 then you WILL have to be on that firmware if you are currently on 4.4.4
If anyone helps, plz give thanks?
N910V ? BL / KYUBI ROM
Click to expand...
Click to collapse
Thanks stajam, I got it done last night.

ttall8ball said:
Thanks, I got it done
---------- Post added at 08:52 AM ---------- Previous post was at 08:49 AM ----------
Thanks stajam, I got it done last night.
Click to expand...
Click to collapse
Good to hear glad you got it going. ?
If anyone helps, plz give thanks?
N910V ? BL / KYUBI ROM

refusedchaos said:
For BL unlocking follow this
For rooting
If staying on stock:
Boot into download mode (VOL-DOWN + HOME + POWER) and flash twrp-3.0.2-0-trltevzw via ODIN (MAKE SURE YOU UNCHECK AUTO-REBOOT!!!).
Battery pull phone and then boot straight into recovery (VOL-UP + HOME + POWER) to finish the recovery install process or else it will install the default android recovery.
Then flash the Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P kernal via recovery.
Then flash the BETA-SuperSU-v2.71-20160331103524 via recovery.
Reboot.
If going to a different rom, you should just be able to flash the rom via recovery and get right in. But results may very, check the forums.
Click to expand...
Click to collapse
can u get a new link to the twrp to flash..I just want root is all...I've download several twrp with same numbers but no luck flashing
thanks so much
Sent from my SM-N910V using XDA-Developers mobile app

Sony Xperia Z2, lost root and custom recovery.(sorry i'm new to rooting)

I'm currently running 6.0.3 paranoid version. And I did obviously have root before installing this ROM. I have tried looking in the developer options to see if it wasn't turned on, but the option isn't available anymore. I'm not sure what information i need to supply. Will I need to root again?
Thanks for reading,
Evitov.

The ROM doesn't ship with root. It isn't needed for the ROM to work.
If you want to root it, just flash SuperSU zip in recovery.

Pirateghost said:
The ROM doesn't ship with root. It isn't needed for the ROM to work.
If you want to root it, just flash SuperSU zip in recovery.
Click to expand...
Click to collapse
It made me lose my custom recovery which was twrp. Which is why i cannot flash it.

Evitov said:
It made me lose my custom recovery which was twrp. Which is why i cannot flash it.
Click to expand...
Click to collapse
You should go ask in your device forum. I've never heard of recovery being removed after flashing a ROM

Pirateghost said:
The ROM doesn't ship with root. It isn't needed for the ROM to work.
If you want to root it, just flash SuperSU zip in recovery.
Click to expand...
Click to collapse
Pirateghost said:
You should go ask in your device forum. I've never heard of recovery being removed after flashing a ROM
Click to expand...
Click to collapse
Okay thanks for your help anyway, i'll try that then.

@Evitov
There may be two reasons for losing recovery:
1.You had dual recovery for stock locked bootloader.
2.You had kernel with built in recovery.
And to get recovery:
Just download twrp for z2
And flash through flashtool.
Thats it

Evitov said:
It made me lose my custom recovery which was twrp. Which is why i cannot flash it.
Click to expand...
Click to collapse
Did you have the latest marshmallow stock build(.291) before this? If so , then connect to computer in fastboot mode, download twrp image for your phone, copy to fastboot folder and type,
Code:
fastboot flash recovery (the twrp image name).img
To get into recovery, hold power and vol down buttons together until sony logo.
I cannot be sure if this will work with your device bc i have a z3 compact
but still, try!