Database Info

[Q] I don't think my root worked!

Hey guys,
So today I decided to root my phone. I want to be able to use WiFi tethering without paying their ridiculous monthly fee, so I came here and read all I could about rooting my phone.
I downloaded the "Charge Kit V2" and proceeded with the instructions to install the "EE4stock_DXC.tar.md5" file to my phone. Everything worked as advertised and was completed in less than three minutes. I boot the phone, select the reboot option, and everything appears exactly as I left it.
Thinking I was rooted I downloaded the Android WiFi Tether app, but the thing won't work! So I go back to the FAQ and read that I could check to see if I were rooted by downloading a terminal emulator and typing "SU" into it. I did, and got "Permission Denied". I'm thinking this means I'm not rooted...
Am I rooted? If not, what did I do wrong? If so, why won't my WiFi tether work?
Thanks everyone!
ON edit: Just downloaded a root checker...apparently I'm not rooted. What could have gone wrong? Is the file I installed not rooted?

TomB985 said:
Hey guys,
So today I decided to root my phone. I want to be able to use WiFi tethering without paying their ridiculous monthly fee, so I came here and read all I could about rooting my phone.
I downloaded the "Charge Kit V2" and proceeded with the instructions to install the "EE4stock_DXC.tar.md5" file to my phone. Everything worked as advertised and was completed in less than three minutes. I boot the phone, select the reboot option, and everything appears exactly as I left it.
Thinking I was rooted I downloaded the Android WiFi Tether app, but the thing won't work! So I go back to the FAQ and read that I could check to see if I were rooted by downloading a terminal emulator and typing "SU" into it. I did, and got "Permission Denied". I'm thinking this means I'm not rooted...
Am I rooted? If not, what did I do wrong? If so, why won't my WiFi tether work?
Thanks everyone!
ON edit: Just downloaded a root checker...apparently I'm not rooted. What could have gone wrong? Is the file I installed not rooted?
Click to expand...
Click to collapse
I don't think that package is rooted, or at least it didn't root you when flashed (which happens sometimes).. use odin to flash CWM, boot straight into it and flash the superuser apk, when you boot up update the superuser app in the market and update the binary, after that you'll be rooted no problems
http://db.tt/4b3IK0C <--- superuser
blazing through on my 4G Droid Charge

Thanks for the reply!
Is there a good page with instructions on how to do this? I'm paranoid about bricking my phone and very new at this! Does the CWM load the same way the other.tar.md5 loaded?
What is a CWM?
Tried searching and didn't come up with much.
Thanks!

TomB985 said:
Thanks for the reply!
Is there a good page with instructions on how to do this? I'm paranoid about bricking my phone and very new at this! Does the CWM load the same way the other.tar.md5 loaded?
What is a CWM?
Tried searching and didn't come up with much.
Thanks!
Click to expand...
Click to collapse
this: http://forum.xda-developers.com/showthread.php?t=1160580 is a pretty good info thread on how to flash and what everything is though it's a little dated and most of the roms/CWM files are older, everything else like drivers and Odin versions are fine... CWM is short for ClockWorkMod recovery and along with Odin is what we use to flash roms/kernels/etc. to our phones, and yes in Odin it goes in the same PDA spot as a rom and flashes like normal... however since you don't have a custom kernel to make CWM 'stick' in your system its one time use after you flash it in Odin and you will have to Odin flash it again every time you want to use it, making it perfect if all you want to do is simply root the phone

Please use the Q&A Forum for questions Thanks
Moving to Q&A

THANKS!!!
After tinkering with it a few times, as well as a scare with a failed flash and temporarily bricked phone, I got it to work! I'm now rooted and have successfully run the tethering app with no errors.
Thank you for your time, you made this easy! And I didn't destroy my shiny new phone!

TomB985 said:
After tinkering with it a few times, as well as a scare with a failed flash and temporarily bricked phone, I got it to work! I'm now rooted and have successfully run the tethering app with no errors.
Thank you for your time, you made this easy! And I didn't destroy my shiny new phone!
Click to expand...
Click to collapse
nice glad to hear it, its a piece of cake after you do it once and learn it
blazing through on my 4G Droid Charge

[Q] Root Keeping Stock Recovery

Hi,
I would like to root my phone mantaining the stock recovery, and booting temporarily a custom recovery
If i execute a "fastboot boot customrecovery.img" and then i install from zip the "UPDATE-SuperSU-v1.69.zip" for example, I know that i will have a rooted phone with stock recovery.(right?)
I would like to do this in order to receive OTA without manual installation (i'm right?), thing that i have already done on my "old " Galaxy Nexus and now i would like to avoid doing it on the N5. I know that, in a case like this, i will lose root and then i have to do the process again.
The question is: There's just some contraindication doing this?
Thank you very much. I already tryed to find an exaustive answer searching the forum.
PS. Sorry for my poor English

Chainfire has the solution for you. Root and keep everything else stock.
http://forum.xda-developers.com/showthread.php?t=2507211
You will have to unlock your bootloader if you haven't already done so.

DreamLinker said:
Hi,
I would like to root my phone mantaining the stock recovery, and booting temporarily a custom recovery
If i execute a "fastboot boot customrecovery.img" and then i install from zip the "UPDATE-SuperSU-v1.69.zip" for example, I know that i will have a rooted phone with stock recovery.(right?)
I would like to do this in order to receive OTA without manual installation (i'm right?), thing that i have already done on my "old " Galaxy Nexus and now i would like to avoid doing it on the N5. I know that, in a case like this, i will lose root and then i have to do the process again.
The question is: There's just some contraindication doing this?
Thank you very much. I already tryed to find an exaustive answer searching the forum.
PS. Sorry for my poor English
Click to expand...
Click to collapse
Your method of booting a recovery image will work fine. That's the way I would do it.

Thanks you all very much!

[Q] HTC one s Hard Bricked

I'm kind of new to the whole rooting thing. However, I managed to root the Unlock the bootloader, install the recovery and then root it. However when I tried to install a ROM the phone when off after I had wiped the old OS. So at the moment I am stuck in limbo, all the phone does is flash, any ideas? Thanks.

Waggy2014 said:
I'm kind of new to the whole rooting thing. However, I managed to root the Unlock the bootloader, install the recovery and then root it. However when I tried to install a ROM the phone when off after I had wiped the old OS. So at the moment I am stuck in limbo, all the phone does is flash, any ideas? Thanks.
Click to expand...
Click to collapse
You might want to post in the emergency thread for this.
Someone will chime in I am sure. From what little I know, I would try using the RUU (ROM update utility) to restore the phone.
Before you do that, wait a little while and maybe someone else will post with some other method. The RUU will hopefully restore your phone to stock.

I'm trying to do that now buy it just wont boot up so I can't run the program

lost recovery

I rooted my stylo last month and shortly after I flashed a twrp recovery in which I thought it was for my ls770. Well after I did that I got that error 1003 thing when I try to boot into recovery. So I now can't boot into recovery So I found a factory recovery file and flashed it also and I still can't boot into recovery. Can someone help please and thanks..

What version of Android? I did the same thing and luckily I had backed up a recovery with Flashify. I can see if I still have the backup. The recovery was for 5.1.1 ZV5

The one I found I think was for 5.0 but I'm on 5.1.1. That would be great @mabry

mabry said:
What version of Android? I did the same thing and luckily I had backed up a recovery with Flashify. I can see if I still have the backup. The recovery was for 5.1.1 ZV5
Click to expand...
Click to collapse
Do you have the stock recovery or what cause I need it asap

My bad bro. When I updated to Marshmallow I formatted my external SD in hope of the new storage feature. I lost it. I am sure 6th Hokage, or Dominick might have one laying around. They the main devs on the Boost Stylo.

did you ever get the stock recovery, I have the same problem...

ShonPu said:
did you ever get the stock recovery, I have the same problem...
Click to expand...
Click to collapse
No I have been trying like a mad man to get the recovery back but nothing is working. And I can't find anyone that can help me. It is driving me insane...

ShonPu said:
did you ever get the stock recovery, I have the same problem...
Click to expand...
Click to collapse
Add me to the list. I can't get anything but secure boot error 1003.

Me too..
Add me as well....
Rooted and went to install twrp..secure boot error 1003.
Anybody get any news on this?

The TWRP that is available out there right now with all the tutorials isnt for our devices (LS770). Theres not much going on with our devices because of the locked bootloader that lg seems to know nothing about; let alone any support for this devices alongside marshmallow. My goal is to port TWRP to our phones and find a backdoor in but im caught up in a bunch of different projects right now and juggling it with work. Plus ive gotta learn how to build these things. If anybody could tell me anything about our phone that i cant figure out thatd be wonderful. Ill try to get the recovery image posted on my drive when i go on my computer next.

Lg lls770
So I've read even just using King root it will lock up your phone, i had done that with my other lg ls770 and tried installing the twrp recovery. Any ideas if i will run into the same problem just using King root? And how would i go about making a back up of my stock recovery?

The ls770 has a locked bootloader. You can't just put any twrp recovery on it. You may be able to use kingroot temp, but I bricked twice using it, and can't offer any advice. If you have read enough of the ls770 brick stories including mine, you'll see there is no real pattern to bricking with kingroot. I successfully used it and restarted and re temp rooted for days, changing build.prop uninstalling google apps, then WHAM, brick out of thin air. Some were bricking straight away after kingroot with only restarting. If you do use kingroot to temp root I hope you'll report back and tell us how it is going, Thanks

So any idea if checking the oem unlock box in developer options and then going to fastboot/download mode would unlock the bootloader? I'm not very advanced with tinkering with android but i can go about the basics i guess

Finallyrooted said:
So any idea if checking the oem unlock box in developer options and then going to fastboot/download mode would unlock the bootloader? I'm not very advanced with tinkering with android but i can go about the basics i guess
Click to expand...
Click to collapse
The oem unlock will not unlock the bootloader.The bootloader is locked by Boost/sprint/virgin. It's probably not going to be unlocked. The only LG's I know that have unlocked bootloader are Tmobile/metropcs. I hope kingroot gets this worked out as we know they have no future without being able to root phones. I made a post on the kingroot page here at XDA asking about what they might do now with marshmallow. I haven't heard from the main @Kingxteam but I keep hearing they are working on it

Please help

Guys, my son messed up and followed instructions off the Max "HighOnAndroid" at www.galaxynote5root.com
He flashed twrp 3.0.2-1
He followed step by step. After flashing twrp, he booted back into recovery and flashed
No-verify-opt-encrypt
And
Update-SuperSU-v2.46
When he booted it back up, its stuck on the sprint splash screen. It is specifically in the screen that says LTE Plus More spectrum better network.
After I got off from work, I came home to him crying.
Ok, I have started to download the factory ROM from Sammobile but I am wondering if maybe there isnt an easier fix. I am not to familiar with changing kernels. Ive never needed to worry about them. Could I maybe just need to flash a new kernel?
From looking on here, really all he needed to do was flash twrp then SuperSU... Does anyone know a way to fix this faster than waiting 6 hours for the Sammobile stock rom?
Please help

Edit....
Ok guys...
I got the file downloaded from sammobile. I installed it and got it installed and working. Then I tried to do the root myself. I followed the guide on this site. However I still couldn't get it working. It was still bootlooping. But not the same bootloop. This time around, it didn't get past the very 1st screen. I again flashed back the stock ROM and again everything works fine.
The files I tried to install are:
Twrp-3.0.2-1nobleltespr.tar.md5
Then I did the twrp install boot deal, booted into twrp and installed:
BeastMode-Stock-N920P-1.3-O16.tar.md5
BETA-Flashable_SuperSU-2.52
I now take it that the issue is my twrp says noble while I read not to use the noble kernel to use BeastMode. But I could be way off...
Man alive, I didn't know just how much I appreciated CF Auto Root until just now...

You probably already figured this out by now but follow the instructions and links in my thread. You should only reboot directly to twrp from download mode after flashing twrp btw in case you haven't figured it out by now.
The method you are using is from a very old thread. Follow the instructions in the thread below.
[How-to] Root your SM-N920P Device - all versions

tdunham said:
You probably already figured this out by now but follow the instructions and links in my thread. You should only reboot directly to twrp from download mode after flashing twrp btw in case you haven't figured it out by now.
The method you are using is from a very old thread. Follow the instructions in the thread below.
[How-to] Root your SM-N920P Device - all versions
Click to expand...
Click to collapse
Thank you for responding. I was able to get the factory ROM installed and working fine.
I have downloaded the MOAR for the device and plan on giving it a go.
I still haven't been able to root the phone. EVERYTHING I tried resulted in bootloop. So I just decided to stick to stock on his phone until I can actually get it figured out...
As far as the SuperSu being old, I got it directly from the website of the maker. https://download.chainfire.eu/696/supersu/
I REALLY want to get this phone rooted for him, as I am certain he is going to keep trying following random YouTube videos regardless of my instruction.
Like I said in my last post, I have never missed cf auto root so badly...
Sent from my SM-N900T using Tapatalk

auburn2eugene said:
Thank you for responding. I was able to get the factory ROM installed and working fine.
I have downloaded the MOAR for the device and plan on giving it a go.
I still haven't been able to root the phone. EVERYTHING I tried resulted in bootloop. So I just decided to stick to stock on his phone until I can actually get it figured out...
As far as the SuperSu being old, I got it directly from the website of the maker. https://download.chainfire.eu/696/supersu/
I REALLY want to get this phone rooted for him, as I am certain he is going to keep trying following random YouTube videos regardless of my instruction.
Like I said in my last post, I have never missed cf auto root so badly...
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Root on stock is relatively simple.
TWRP + SuperSU only.
But as you saw, it's still easy to get it wrong.

tdunham said:
Root on stock is relatively simple.
TWRP + SuperSU only.
But as you saw, it's still easy to get it wrong.
Click to expand...
Click to collapse
Ok, so since I have flashed TWRP and SuperSU, and all it ever does it bootloop, would I be able to install TWRP, then flash MOAR on top of it? Then I would have a rooted MOAR if I understand correctly. My issue is that ive always had root accomplished before installing a custom ROM.
If all I have to do is flash twrp then SuperSU, I dont understand what I could be doing wrong.
But I'm going to take a look at your link you provided and see if I can't get root 1st.

auburn2eugene said:
Ok, so since I have flashed TWRP and SuperSU, and all it ever does it bootloop, would I be able to install TWRP, then flash MOAR on top of it? Then I would have a rooted MOAR if I understand correctly. My issue is that ive always had root accomplished before installing a custom ROM.
If all I have to do is flash twrp then SuperSU, I dont understand what I could be doing wrong.
But I'm going to take a look at your link you provided and see if I can't get root 1st.
Click to expand...
Click to collapse
Old habits are hard to break. A properly deodexed rom that is pre-rooted only requires twrp and a proper wipe before installing.
For rooting stock, it really is fairly simple. The instructions I provided are probably a little overly detailed but I had to cover as much as possible for those that have never done it before so it 'looks' complex but once you've done it a few times you will see that its really not that hard to do.

tdunham said:
Old habits are hard to break. A properly deodexed rom that is pre-rooted only requires twrp and a proper wipe before installing.
For rooting stock, it really is fairly simple. The instructions I provided are probably a little overly detailed but I had to cover as much as possible for those that have never done it before so it 'looks' complex but once you've done it a few times you will see that its really not that hard to do.
Click to expand...
Click to collapse
Thank you for pointing me to your thread. I was able to get root on my sons phone. Hard to believe the SuperSU was the problem... But it was... I was using the one from chainfires site, but yours worked when his created bootloops.
Thanks again!

Is there a root method for pk1