Database Users

[HOW-TO][DEV EDITION ONLY]Root on 4.4 KitKat

https://www.youtube.com/watch?v=NP9WXLIzhTY
I want to first say that I did not figure out this method on my own, I saw it on Google+ via Matthew Pierce and modified it to make it easier to follow
Second, **do not try this on a device with a locked bootloader. You need the unlocked bootloader to do this**.
You'll want to first download these 2 things
1) Superuser zip to be installed in recovery (from Chainfire) -> http://download.chainfire.eu/366/SuperSU/BETA-SuperSU-v1.72B.zip
2) New TWRP for 4.4 KitKat (from Hashcode)->
http://forum.xda-developers.com/showthread.php?t=2534850
________________________________________________________________
Here's the method to get root:
1) let the system fully install the 4.4 Kitkat ota and reboot. **Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.** After it installs, do not do anything else, let it boot into android.
1b) Take the SuperSU installable zip and place it onto the internal storage
2) reboot phone to bootloader.
3) install Hashcode's TWRP using mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img. (**use the motorola fastboot binary**)
4) reboot device to recovery, do not boot into android before this step!
5) go to install and find then select BETA-SuperSU-v1.72B.zip
6) Boot back into android, and if needed, go to the Play Store and install SuperSU from Chainfire
7) enjoy root!

What is the advantage/difference in installing the SuperSU app you linked, in favor of the one included with the TWRP 4.4 recovery?
Sent from my XT1060 using xda app-developers app

Jexx11 said:
What is the advantage/difference in installing the SuperSU app you linked, in favor of the one included with the TWRP 4.4 recovery?
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Probably nothing. The only reason I mentioned the one in the play store, is because TWRP never actually asked me to root in the first place. I thought it was strange, but I didn't really think much of it

alex94kumar said:
Probably nothing. The only reason I mentioned the one in the play store, is because TWRP never actually asked me to root in the first place. I thought it was strange, but I didn't really think much of it
Click to expand...
Click to collapse
That's odd, I used the TWRP version in Hashcodes thread, flashed with the Motorola Fastboot. When I went to restart from TWRP it asked me if I wanted to root and I let it. Now I'm rooted.
Sent from my XT1060 using Tapatalk

Stranger things have happened, I guess. Regardless of which method you use, you'll end up with root either way

This doesn't seem to be working for me. I accidentally rebooted into Android (hit the power button) then tried the whole thing from scratch.
I get an image of andy with "no command" when I boot into recovery.
Edit: Seems like a low battery issue. Will try again after charging.

chaoslimits said:
This doesn't seem to be working for me. I accidentally rebooted into Android (hit the power button) then tried the whole thing from scratch.
I get an image of andy with "no command" when I boot into recovery.
Edit: Seems like a low battery issue. Will try again after charging.
Click to expand...
Click to collapse
same here but i have 85% battery
so i guess we will have to re-flash and push the supersu

The only advice I can give to either of you is to try reflashing TWRP again

Actually i did it again and it worked, guess we can't just skip steps.
Sent from my Nexus 7 using Tapatalk 4

Well im glad it worked out for you in the end

It worked after I charged the phone.
Thanks
Sent from my XT1060 using Tapatalk 2

How do I return my phone to default in order to install OTA
I have already flashed the stock recovery but my phone is still rooted. Do I need to unroot? I tried installing the OTA and it said it failed.

This method should work on any version with with an unlocked bootloader such as Sprint and T-Mobile - not just the dev editions.

alex94kumar said:
https://www.youtube.com/watch?v=NP9WXLIzhTY
I want to first say that I did not figure out this method on my own, I saw it on Google+ via Matthew Pierce and modified it to make it easier to follow
Second, **do not try this on a device with a locked bootloader. You need the unlocked bootloader to do this**.
You'll want to first download these 2 things
1) Superuser zip to be installed in recovery (from Chainfire) -> http://download.chainfire.eu/366/SuperSU/BETA-SuperSU-v1.72B.zip
2) New TWRP for 4.4 KitKat (from Hashcode)->
http://forum.xda-developers.com/showthread.php?t=2534850
________________________________________________________________
Here's the method to get root:
1) let the system fully install the 4.4 Kitkat ota and reboot. **Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.** After it installs, do not do anything else, let it boot into android.
1b) Take the SuperSU installable zip and place it onto the internal storage
2) reboot phone to bootloader.
3) install Hashcode's TWRP using mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img. (**use the motorola fastboot binary**)
4) reboot device to recovery, do not boot into android before this step!
5) go to install and find then select BETA-SuperSU-v1.72B.zip
6) Boot back into android, and if needed, go to the Play Store and install SuperSU from Chainfire
7) enjoy root!
Click to expand...
Click to collapse
Anyone knows how to do UNROOT if I used this method to get root?

I get a preflash validation failed because the file size is over the limit, but I've checked the file size is actually smaller than the limit.
Has anyone experience this?
Sorry this might be a noob question.

1) let the system fully install the 4.4 Kitkat ota and reboot.**Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.**
Can someone explain this to me? i keep reading it, but not understanding what it means.

s0nic69 said:
1) let the system fully install the 4.4 Kitkat ota and reboot.**Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.**
Can someone explain this to me? i keep reading it, but not understanding what it means.
Click to expand...
Click to collapse
If we're already on 4.4, how do we know if we have the first OTA?
Thanks

chillmeow said:
I get a preflash validation failed because the file size is over the limit, but I've checked the file size is actually smaller than the limit.
Has anyone experience this?
Sorry this might be a noob question.
Click to expand...
Click to collapse
I'm getting it too, and I've tried both the mfastboot and regular fastboot and I've tried redownloading the file several times. I'm beyond annoyed at this point I need root so I can restore my apps using titanium backup
---------- Post added at 03:45 PM ---------- Previous post was at 03:28 PM ----------
doctor_evil said:
I'm getting it too, and I've tried both the mfastboot and regular fastboot and I've tried redownloading the file several times. I'm beyond annoyed at this point I need root so I can restore my apps using titanium backup
Click to expand...
Click to collapse
OK I feel like an idiot. I just noticed that in the fastboot screen it shows that it's locked. I thought developer phones were unlocked by default?
ok after unlocking it I was able to install twrp recovery with no problems

Ok, what am I doing wrong?
I've got an unlocked GSM DE with 4.4.
I used the mac mfastboot to flash twrp and then select recovery. After that it just boots to android telling me I have an unlocked bootloader. Help?

pphi said:
Ok, what am I doing wrong?
I've got an unlocked GSM DE with 4.4.
I used the mac mfastboot to flash twrp and then select recovery. After that it just boots to android telling me I have an unlocked bootloader. Help?
Click to expand...
Click to collapse
Are you selecting recovery with the power button or the volume up button? Volume up selects. If you use the power button, the phone just boots normally.

[Help] Recovery is gone after update

Hi folks, I seek the advice of any one who could help me with issue. To give you a bit of background information, I have a D802 version which is rooted with CloudyStock 1.1, android 4.4.2 KK.
Yesterday I tried to update the version of Philz recovery that I had which has never been a problem before. I downloaded the latest version from the dedicated page here and went into the recovery to install the zip.
Whilst the zip was extracted without issue there was an error regarding "lokifying" the boot loader. I turned the phone off and tried to get in the recovery again but this time I had the error "secure booting: boot certification verify".
I never had any problem before, I don't know why the latest version of the recovery would create more problem that the old one.
The thing is that the phone works fine, it boots and runs without issue, I just can't get into recovery mode. Also the download mode works.
I'm sure they must be a way to get the recovery back. I tried to flash CMW with Rom Manager without success.
If anyone knows, I would appreciate the help greatly.
Cheers

considering kitkat has no root yet, getting a recovery on it is going to be difficult.
you will need a via zip flashable distro of kitkat. Which if you search you can make yourself. It was on xda portal some time ago.
That way I think root\recovery is maintained.
send from the jungle

bachera said:
considering kitkat has no root yet, getting a recovery on it is going to be difficult.
you will need a via zip flashable distro of kitkat. Which if you search you can make yourself. It was on xda portal some time ago.
That way I think root\recovery is maintained.
send from the jungle
Click to expand...
Click to collapse
Thank you for your answer Bachera. I am not sure I understand what you mean by "via zip flashable distro of kitkat."
Plus my kitkat version of android is rooted, why would you think kitkat has no root yet?

Light_Addict said:
Hi folks, I seek the advice of any one who could help me with issue. To give you a bit of background information, I have a D802 version which is rooted with CloudyStock 1.1, android 4.4.2 KK.
Yesterday I tried to update the version of Philz recovery that I had which has never been a problem before. I downloaded the latest version from the dedicated page here and went into the recovery to install the zip.
Whilst the zip was extracted without issue there was an error regarding "lokifying" the boot loader. I turned the phone off and tried to get in the recovery again but this time I had the error "secure booting: boot certification verify".
I never had any problem before, I don't know why the latest version of the recovery would create more problem that the old one.
The thing is that the phone works fine, it boots and runs without issue, I just can't get into recovery mode. Also the download mode works.
I'm sure they must be a way to get the recovery back. I tried to flash CMW with Rom Manager without success.
If anyone knows, I would appreciate the help greatly.
Cheers
Click to expand...
Click to collapse
I encountered something similar on my phone. However, i was on 4.2.2 but this worked for me. Give it a shot, it might work for you too
http://forum.xda-developers.com/showthread.php?t=2500441
Good luck

Try Flashify from the Play store to flash a working recovery for your phone. I had the same issue with philz latest version. I had to use an older version of philz to get it to work on my phone.
Sent from my LG-D803 using xda app-developers app

Yeah I misread, I thought you went to a official kitkat. Only way to get root on kitkat is if lucky its maintained with a ota update. or a special made kitkat, thats what I mean with special distribution (distro) one via recovery flashable.
kitkat rooting directly at the moment of writing is not possible due to lg bootloader.
send from the jungle

Thank you all for the help and suggestions. I tried flashify and I did not work.
However freegee worked very well and managed to go back to CMW.
All functional now!
Thanks

Nvidia SHIELD Portable Root

Hi everyone!
This morning I woke up to find my SHIELD with the so waited notification of Lollipop update. I'm really happy to finally have lollipop running on my device, but sadly I found a problem after the update. I was trying to re-root my device, but neither the SHIELD RAM tool or Root Genius could do the trick. But I didn't gave up, I searched in Google any way to root my SHIELD with the still fresh update, and found that the Kinguser app can root it without trouble.
You just need to download the apk, install it on your SHIELD and open it.
Btw, the old recovery isn't working anymore, you can flash it with the RAM tool, but the device will reflash the stock recovery.

Downloaded and it's says shield portable android 5.1 not supported...
Sent from my SM-N910P using Tapatalk

kenmacker said:
Downloaded and it's says shield portable android 5.1 not supported...
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
You need to turn on USB Debugging, and then run the app.

USB debugging is now turned on but it says root access is unavailable
Sent from my SM-N910P using Tapatalk

work great
thanks

Old recovery is working for me - it's CWM 6.0.4.4.
I had to flash it twice, first time it was reflashed to stock.
PS: TWRP 2.8.5.0 (unofficial) is working too.

kenmacker said:
USB debugging is now turned on but it says root access is unavailable
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Look if you have your SHILD's bootloader unlocked, that may be causing the problem.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.

I wanted a full restore/clean version of the ROM without waiting for the factory image to be updated.
I flashed the 101 Factory Image from here. I notice that 103 is there now so just skip this step and flash that now.
I noticed that after flashing the latest SuperSU the device would never boot.
So I had to use KingRoot but for me the apk method never worked so I went with the desktop version.
To get Root I went to KingRoot's XDA page and downloaded the Desktop version.
When running the program it is all in Chinese but is thankfully idiot proof with its one big button on it. Just make sure that USB Debugging is turned on and wait for it to finish, it will reboot during the process.
KingRoot installs its own version of a Super User advisor so it will prompt when something needs root access and for most people that would be enough but I prefer SuperSU, Thankfully KingRoot has a set of instructions, follow these to the letter and it will guide you through removing KingRoot and installing SuperSU. During that process you will get a lot of errors saying that files are no longer there, just ignore them, that means the initial uninstall got the files.
Once I was able to ensure that SuperSU and Root where staying after a reboot I re-installed TWRP (for some reason I couldn't get CWM to stick after a reboot but oh well I like TWRP more >_>) and made a backup of my stock rooted device.
I then went to this page and grabbed the Unofficial Xposed 5.1 .zip and went to this page and grabbed the Xposed Installer.
Rebooted and waited for the App Cache to re-build as the Xposed framework nukes it then installed my mods as normal.
Took a little bit longer than normal to update but oh well, Everything is working smoothly and I'm happy with it.

Rooted my Shield two times wth CWM without problems.

astuermer said:
Old recovery is working for me - it's CWM 6.0.4.4.
I had to flash it twice, first time it was reflashed to stock.
PS: TWRP 2.8.5.0 (unofficial) is working too.
Click to expand...
Click to collapse
Which cmw did you use and where did you get it? I tried using flashify with twrp and it says boot failed when booting into recover.
astuermer said:
Rooted my Shield two times wth CWM without problems.
Click to expand...
Click to collapse

Give me a few mins. I will upload my Recovery package...
Here we go. I've flashed and rooted my SHIELD successfully after OTA upgrade - and today again after flashing the clean 103 factory Image.
SHIELD-Portable-Recoveries.zip
Update: I've attached a ZIP file with 4 different recoveries. Simply execute the Batch file I've included (if you're on Windows) and select 1-4.
stock KitKat recovery (from update 101)
stock Lollipop recovery (from update 103)
ClockworkMod recovery (CWM) 6.0.4.4 (somewhere from XDA, but couldn't find the link)
TWRP recovery 2.8.5.0 (from here)

From @Steel01 The TWRP located here may give people problems and we should be using the one in the MultiROM TWRP located here.
Source here.
EDIT: I will test tonight and see what happens when you image with the factory image and just install MultiROM's TWRP and then try SuperSU's latest BETA.
I was trying to use the other TWRP before and could never boot which is why I did the KingRoot method.

If you wanted to change Kinguser to SuperSU all you have to do is download any "Control Rotation App" and set it as Portrait Mode (if it didn't work make sure that the Nvidia Shield Portable is in a sitting position and flip it , It should work , If not try installing other apps), Install "Super-Sume" , Then touch the big blue button , After that wait until the process is done , You should see SuperSU, In the other hand Kinguser has already vanished (I'm not sure if SuperSU will open automatically or not), Install the binary, Reboot, Done.
Have a nice day

"set warranty bit recovery" sm-t350

Just got this tablet today 2nd hand. Installed twrp, wiped tablet, got it set up. I went into twrp to back everything up and now when i reboot into system i get this message:
"set warranty bit recovery "
and it boots back into twrp.
Is tried powering the device down and and then restarting but it keeps going into twrp.
It looks like i can flash the stock firmware in odin to fix this, but does anyone know can i just flash the custom kernel (in odin) that's available for the T350? Would that be enough.
Thanks
Sent from my Nexus 6 using XDA-Developers mobile app

So flashing the kernel found on this site for the 350 works if anyone comes across this error. I flashed it in odin (as opposed to twrp)
Sent from my Nexus 6 using XDA-Developers mobile app

rrrrrrredbelly said:
Just got this tablet today 2nd hand. Installed twrp, wiped tablet, got it set up. I went into twrp to back everything up and now when i reboot into system i get this message:
"set warranty bit recovery "
and it boots back into twrp.
Is tried powering the device down and and then restarting but it keeps going into twrp.
It looks like i can flash the stock firmware in odin to fix this, but does anyone know can i just flash the custom kernel (in odin) that's available for the T350? Would that be enough.
Thanks
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
If you installed the CF-Autoroot for your SM-T350 (I have this device) then it will softbrick your device, I do not know the cause, but I tried it. Also if you install TWRP for SM-T350, install the Lollipop version! The Marshmallow version is not compatible with 3rd party apps yet but the Lollipop version does. If you want to install SuperSU, then install from here: https://download.chainfire.eu/1012/SuperSU/SR3-SuperSU-v2.78-SR3-20161103171345.zip
YOU HAVE TO FLASH IT IN TWRP! INSTALL LOLLIPOP VERSION TWRP BEFORE YOU FLASH!!! ALSO, IF TWRP ASKS YOU TO INSTALL ROOT, DON'T LET IT!
Happy Flashing and Hope I helped.

LG G3 [D855] Custom Recovery And Rom Flashing

I have went through many tutorials but none of them were able to help me with flashing custom recovery(TWRP). My LG G3 D855 was rooted with towelroot(I think long time ago). I do not know how can I unlock my bootloader or I don't know if it is already unlocked(Picked it off craiglist long time ago). Phone is stuck in fastboot mode. I have tried to fix but I could not. There is no 'download mode'.
Could you please explain each and every step in detail? I really want to reboot my device with a custom ROM.
Phone is running Androind 4.4.2.

So guys? Any help? Just tell me how can I remove that fastboot mode that appears when I restart my device for recovery.

AtaliaKetch said:
So guys? Any help? Just tell me how can I remove that fastboot mode that appears when I restart my device for recovery.
Click to expand...
Click to collapse
Have you flashed TWRP already?
I have a an D855, I don't think you have to worry about a locked bootloader Mate,
but it was a long time since I got rid of the LG crap, because it was the first thing I did after buying new!
You're on 4.4.2 with towel root so it should very simple to download and flash TWRP using the official TWRP app in Playstore or using an app like Flashify etc.
I basically lost my S7 Edge a week ago so I'm back using my old LG G3 now running Resurrection Remix 5.8(Nougat 7.1.2. AOSP based)
If you wanna run anything using Aroma installer then don't go later than TWRP 3.0.0. for now, because the newer versions don't work.
Either download the Quickboot app to boot to recovery or search on Youtube on how to boot to recovery from off..

andi54 said:
Have you flashed TWRP already?
I have a an D855, I don't think you have to worry about a locked bootloader Mate,
but it was a long time since I got rid of the LG crap, because it was the first thing I did after buying new!
You're on 4.4.2 with towel root so it should very simple to download and flash TWRP using the official TWRP app in Playstore or using an app like Flashify etc.
I basically lost my S7 Edge a week ago so I'm back using my old LG G3 now running Resurrection Remix 5.8(Nougat 7.1.2. AOSP based)
If you wanna run anything using Aroma installer then don't go later than TWRP 3.0.0. for now, because the newer versions don't work.
Either download the Quickboot app to boot to recovery or search on Youtube on how to boot to recovery from off..
Click to expand...
Click to collapse
The problem is, there is no recovery. Even though flashing TWRP via flashify resulted in nothing but an error showing "Fastboot mode started" when I tapped on option named "Reboot to recovery". This is the main problem I am facing. I can flash, upgrade/downgrade and etc but this fastboot mode thing is something beyond what I can fix with my current knowledge.

AtaliaKetch said:
The problem is, there is no recovery. Even though flashing TWRP via flashify resulted in nothing but an error showing "Fastboot mode started" when I tapped on option named "Reboot to recovery". This is the main problem I am facing. I can flash, upgrade/downgrade and etc but this fastboot mode thing is something beyond what I can fix with my current knowledge.
Click to expand...
Click to collapse
Maybe first flash back stock, update to the latest firmware and start fresh from there?
There are some good guides in the forums here for that.
Cheers
Sent from my Google Pixel using XDA Labs

If you've to go back to firmware, don't install the newest. Rooting needs an older version. Also described in root-threads here.