Develop Bugs

Maybe a stupid question but is the Verizon GN rootable?

And unlockable etc? All the instructions I see say GSM etc. just dont want to mess up my phone

psufan5 said:
And unlockable etc? All the instructions I see say GSM etc. just dont want to mess up my phone
Click to expand...
Click to collapse
Yes.
fastboot OEM unlock to unlock
If you want it to be very simple you can use superboot to root (you can boot it, you don't have to flash it)
http://forum.xda-developers.com/showthread.php?t=1352413

krohnjw said:
Yes.
fastboot OEM unlock to unlock
If you want it to be very simple you can use superboot to root (you can boot it, you don't have to flash it)
http://forum.xda-developers.com/showthread.php?t=1352413
Click to expand...
Click to collapse
Every single person I have seen flooding this forum today with "OMG my phone is brooooooken!" has used Superboot on their LTE phone.
Not sure if it's related, but I'd recommend rooting manually.

josteink said:
Every single person I have seen flooding this forum today with "OMG my phone is brooooooken!" has used Superboot on their LTE phone.
Not sure if it's related, but I'd recommend rooting manually.
Click to expand...
Click to collapse
I always root manually. I forgot to mention im using MacOSX - but I do have access to a PC, so I will just use that.
Thanks a ton!
Where are the manual instructions I should use? Is there a macOSX version ? I normally root with that etc.

josteink said:
Every single person I have seen flooding this forum today with "OMG my phone is brooooooken!" has used Superboot on their LTE phone.
Not sure if it's related, but I'd recommend rooting manually.
Click to expand...
Click to collapse
Don't flash the boot image. Use fastboot boot to boot it.
If it hangs (as it did on my GSM update to 4.0.2) just pull battery and reboot. You are still on your stock boot image and it should have rooted (mine did and this is what others report as well).
If you overwrite the stock boot image (fastboot flash boot boot.img) all bets are off (boot.img contains the kernel, init scripts and initramfs).

psufan5 said:
I always root manually. I forgot to mention im using MacOSX - but I do have access to a PC, so I will just use that.
Thanks a ton!
Where are the manual instructions I should use? Is there a macOSX version ? I normally root with that etc.
Click to expand...
Click to collapse
Normally you could flash CWM and flash the su binary via an update package. As of a week ago though that didn't properly mount system so it would not work. IDK if it has been updated since then. Thus necessitating booting an insecure boot image (to mount /system rw) and then either pushing SuperUser.apk and su via ADB or using one of the "superboot" images.

Update to Android 4.0.2
Unlock bootloader
Use SuperBoot
???!?!?!?!
PROFIT
Method worked just fine for me.
Also, when using Superboot, be patient, it takes 10 min to boot and if it doesn't boot battery pull and try again.

Nice easy manual way of doing the bootloader unlock and rooting if this is a new concept for you.
http://www.droid-life.com/2011/12/05/how-to-unlock-the-galaxy-nexus-bootloader/
http://www.droid-life.com/2011/12/1...xus-4g-lte-and-flash-custom-recovery-verizon/

[HELP] Can't Figure Out Why I'm Not Rooted?

Here's some info:
GSM Galaxy Nexus - Retail (bought from amazon).
Version: 4.0.1 (says no further update available).
Build Number: ITL41F
Can't remember if I rooted, then updated to ITL41F or not.
Followed THESE instructions successfully:
Code:
- Got drivers for Galaxy Nexus installed.
- Used "fastboot-windows oem unlock" and unlocked bootloader.
- Used "install-superboot-windows.bat"
Does this mean I am rooted permanently or have I missed out something?
I do not have Clockwork MOD installed. I don't plan on putting a custom ROM on the phone, I just want root access on the stock ROM.
Superuser is installed.
RootExplorer is denied superuser permissions (never had a prompt or anything). I can navigate to system/app/ and see superuser is in there. RootExplorer does see all the folders and files, but cannot be mounted in R/W mode.
Superuser Update fixer app says (under "force):
Code:
Checking signatures... ok!
extracting tiny busybox... ok!
extracting superuser.apk... ok!
Gaining root access ... fail!
In laymans terms, what do I need to do now to gain root access to my phone?
Also, to clarify, if I run a OTA update to the stock ROM, will it un-root my phone?
Thanks

Easiest thing is to unlock your bootloader, flash CWM, and then apply a su.zip.
I rarely ever actually root a phone. Usually I will install CWM and then flash a stock root rom.
Look in this thread for the Clockworkmod boot method...should work like a charm.
http://androidforums.com/galaxy-nexus-all-things-root/452146-how-root-samsung-galaxy-nexus.html

fastboot-windows.exe boot boot.superboot.img
Should have just used this after you unlocked boot loader for route
Anyways , the above will get you sorted
Merry Christmas

40Glock said:
Easiest thing is to unlock your bootloader, flash CWM, and then apply a su.zip.
I rarely ever actually root a phone. Usually I will install CWM and then flash a stock root rom.
Look in this thread for the Clockworkmod boot method...should work like a charm.
http://androidforums.com/galaxy-nexus-all-things-root/452146-how-root-samsung-galaxy-nexus.html
Click to expand...
Click to collapse
Thanks. However:
1) I'm hoping my bootloader will still be unlocked. Therefore will flashing CWM reset the phone, IE delete all the apps?
2) What happens if I don't really want to install CWM? Can I not be rooted without it?
3) It doesn't really explain why I don't seem to be rooted :/
I should also add that Root Explorer does see all the files and folders, but it cannot be mounted in r/w mode.
But I'll take a look at the link, thanks.

I don't understand why you want to be rooted then...
Sent from my Galaxy Nexus using XDA App

you should move your question to the galaxy nexus q&a forum, you will get more help there, if not find someone who already had the same issue. Read ALL stickies at the top of the forums. This will help solve your problem. Posting here will most likely get you bad attitudes fyi
Sent from my Galaxy Nexus

anotherxdauser said:
Thanks. However:
1) I'm hoping my bootloader will still be unlocked. Therefore will flashing CWM reset the phone, IE delete all the apps?
2) What happens if I don't really want to install CWM? Can I not be rooted without it?
3) It doesn't really explain why I don't seem to be rooted :/
I should also add that Root Explorer does see all the files and folders, but it cannot be mounted in r/w mode.
But I'll take a look at the link, thanks.
Click to expand...
Click to collapse
1. Unlocking the bootloader wipes the device not CWM. Mine came unlocked from retail store.
2. According to Superboot thread you can root without CWM.
3. Did you install busybox like the instructions say?
Similar to the previous post...since you have a GSM phone post/look in GSM thread for proper help.
Sent from my Galaxy Nexus using xda premium

Ditto what alot of others have said. Post about GSM model in CDMA area, plus not dev related. Asked for post to be moved to help you out.
merry xmas and good luck

Thanks for not flaming guys!
Thread moved......

drpancake said:
I don't understand why you want to be rooted then...
Click to expand...
Click to collapse
I need to be rooted to allow various apps to run to their full potential.
Well, tried the rooting process again, now no matter what method I choose, they are all saying "waiting for device".
Any pointers on what to do next?

you can try below if you like.
first of all, make sure your boot loader is unlocked.
secondly,
download CWM recovery from below.
http://forum.xda-developers.com/showthread.php?t=1357642
then download below su binary package i have made
http://forum.xda-developers.com/showthread.php?t=1395155
place su_signed_signed.zip into your sdcard (copy into your phone internal storage)
then turn off you phone, boot into bootloader mode (hold vol+ and vol- and power button).
once you are in it,
type
"fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img".
then using vol+ switch to boot recovery option and press the power button.
once you are in Clockwork Mode Recovery,
choose option "install zip from sdcard"
then browse and select "su_signed_signed.zip"
once it has done, you have rooted your phone.
now all you need to do is, reboot your phone, go to android market,
and install https://market.android.com/details?id=com.noshufou.android.su
then run Superuser,
go to settings,
then select "Su binary v3.XXX, tap to check for updates".
after you tap on that, it should say that SU is out of date.
click on update su binary, then you will be prompted for Superuser request.
once you have permitted it, it will then download the latest su binary and install it.
then you are done.

^^ Except I DO NOT WANT CLOCKWORK MOD on my phone.
However, as closure, I did manage to re-root my phone. I dried different drivers for the Samsung and somehow it just accepted the deivce and rooted it for me.

[Q] Will Galaxy Nexus rooting wipe my phone's data?

1. Will Galaxy Nexus rooting wipe my phone's data?
2. Which method is recommended? I've found Toolkit 5.7, and that one:
http://forum.xda-developers.com/showthread.php?t=1454314
Maybe they all do exactly the same?

Unlocking wipes phone, rooting comes after..Copy anything from sd card you want to save to pc. Use mskip's toolkit and read all instructions and you will be fine. Google saves all your apps in market and contacts will sync when you sign into google.
Hope this helps.

Use my guide.
Stickied above...and linked in my sig.
But yes, it will wipe your data.
You could, however, use the backup method detailed in my guide.
DON'T use these damn toolkits...
If you someday soft brick your phone (and if you tinker...you will, I promise) you're going to want to know how to utilize the resources you needed to root it manually...and if you used a toolkit, you'll be far worse off as you won't even know if adb/fastboot are set up properly...and will cause a huge barrier of troubleshooting your problems.
I personally promise...
Do it the manual way...and you'll end up with a rooted phone in an hour.
It's not hard.

I also root my nexus without using those tool kits (seems don't have any when I got my nexus)
you may follow Jubakuba's guide, it's safe and not that hard, I root my nexus within 30mins (not following Jubakuba's guide, but almost the same)

Jubakuba said:
DON'T use these damn toolkits...
If you someday soft brick your phone (and if you tinker...you will, I promise) you're going to want to know how to utilize the resources you needed to root it manually...and if you used a toolkit, you'll be far worse off as you won't even know if adb/fastboot are set up properly...and will cause a huge barrier of troubleshooting your problems.
I personally promise...
Do it the manual way...and you'll end up with a rooted phone in an hour.
It's not hard.
Click to expand...
Click to collapse
X3. I used the toolkit for the drivers when I couldn't get mine properly installed. Otherwise, everything else was done in the command prompt with ADB and Fastboot. Very simple and you'll learn what these toolkits are doing behind the scenes so you can better troubleshoot later.

I also rooted my Nexus one without tool kits, it's very easy!

bullka said:
1. Will Galaxy Nexus rooting wipe my phone's data?
2. Which method is recommended? I've found Toolkit 5.7, and that one:
http://forum.xda-developers.com/showthread.php?t=1454314
Maybe they all do exactly the same?
Click to expand...
Click to collapse
If your bootloader is locked, and you are running 4.0.1 or 4.0.2, you can root using this method.
If you want, you can then install ROM Manager from the market and do a backup. Then copy that backup off your device, and proceed to unlock your bootloader (which will wipe) if you want, but then you can restore your backup, and you will have all your data and an unlocked bootloader.

Hi,
I have my bootloader unlocked at the moment after the upgrade to 4.0.4 using this guide: http://forum.xda-developers.com/showthread.php?t=1391881
So I understand that rooting won't erase my phone. Right?
To root I need (I'm skipping blablabla and leaving just the important):
1) fastboot reboot-bootloader
2) fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
3) select the "Recovery Mode" option again on your phone.
You should get a new recovery menu here. Select "install zip from sd card" and "choose zip from sd card."
Find the Superuser-3.0.7-efghi-signed.zip
4) find "Rom Manager" from the market. (The free version is fine.) Use the "Flash ClockworkMod Recovery" option
I'm rooted permanently without loosing my data (as I already have bootloader unlocked), right?

bullka said:
Hi,
I have my bootloader unlocked at the moment after the upgrade to 4.0.4 using this guide: http://forum.xda-developers.com/showthread.php?t=1391881
So I understand that rooting won't erase my phone. Right?
To root I need (I'm skipping blablabla and leaving just the important):
1) fastboot reboot-bootloader
2) fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
3) select the "Recovery Mode" option again on your phone.
You should get a new recovery menu here. Select "install zip from sd card" and "choose zip from sd card."
Find the Superuser-3.0.7-efghi-signed.zip
4) find "Rom Manager" from the market. (The free version is fine.) Use the "Flash ClockworkMod Recovery" option
I'm rooted permanently without loosing my data (as I already have bootloader unlocked), right?
Click to expand...
Click to collapse
Correct.
Just remember that un-locking/locking DOES reset your SD.
But as you said, you're already unlocked. So you're good!
Edit:
PLEASE let me know if that superuser.zip works for you, btw.
I had to update the OP recently to fix 4.0.4 users not being able to root...but wanted the same file to also root us CDMA users and GSM users who aren't on 4.0.4.
If that zip doesn't work...you simply won't have root access. Nothing bad will happen.
Let me know if that happens though (I can't test a 4.0.4 gsm phone, obviously) and I'll get you a .zip that I KNOW works for 4.0.4 users.

Quick question: does the SuperUser app developer has his homepage? Who's the author of that?
Now I understand that there're tons of superuser.apk modifications in the internet. Right?

bullka said:
Quick question: does the SuperUser app developer has his homepage? Who's the author of that?
Now I understand that there're tons of superuser.apk modifications in the internet. Right?
Click to expand...
Click to collapse
http://androidsu.com/superuser/
There are binaries required in 4.0.4 that aren't officially updated, it seems.
Hence my new .zip that is compiled from official SU, but with new binaries.

Jubakuba said:
Correct.
Just remember that un-locking/locking DOES reset your SD.
But as you said, you're already unlocked. So you're good!
Edit:
PLEASE let me know if that superuser.zip works for you, btw.
I had to update the OP recently to fix 4.0.4 users not being able to root...but wanted the same file to also root us CDMA users and GSM users who aren't on 4.0.4.
If that zip doesn't work...you simply won't have root access. Nothing bad will happen.
Let me know if that happens though (I can't test a 4.0.4 gsm phone, obviously) and I'll get you a .zip that I KNOW works for 4.0.4 users.
Click to expand...
Click to collapse
Hi,
Thanks.
Just followed you guide and I have now superuser installed and working. Thanks.
Your guide has some errors. Link is to Maguro and your guide says to flash Toro. Fix the links.
When I flashed Clockwork Recovery with ROM Manager, superuser app asked to confirm the SU request by ROM Manager.
So I assume rooting works well.

bullka said:
Hi,
Thanks.
Just followed you guide and I have now superuser installed and working. Thanks.
Your guide has some errors. Link is to Maguro and your guide says to flash Toro. Fix the links.
When I flashed Clockwork Recovery with ROM Manager, superuser app asked to confirm the SU request by ROM Manager.
So I assume rooting works well.
Click to expand...
Click to collapse
I should probably implement that better.
Guide originally came from a CDMA only forum.
And a GSM only forum.
Merged the posts here...
But it does mention changing the code.
I'll fix it up so it's more obvious now.
And yes, if it asked for SU...
It's fine.
Great news. I hadn't had anyone test yet.
Thanks for being a guinea pig .

[Q] Unrooting with a broken USB connector

My USB connector is broken on my nexus. Amazon has sent me a replacement, which I have at hand. I would like to lock my boot loader on my nexus with the broken USB connector before sending it back to amazon.
Any thoughts as to how I may accomplish this?
If not, can you at the least convince me amazon won't care that my boot loader is unlocked?

EDIT: Never mind, it seems the awesome developers have figured out ways to relock the bootloader.

https://play.google.com/store/apps/details?id=aperture.ezekeel.gladoscontrol
Potentially.
MAYBE.
Just Maybe you can re-lock with this.
I'm not sure if it requires SU or not.
And I haven't given anyone this advice yet, so you'll be the first.
But as the above poster said...
Mobile Odin first.

mt6272 said:
My USB connector is broken on my nexus. Amazon has sent me a replacement, which I have at hand. I would like to lock my boot loader on my nexus with the broken USB connector before sending it back to amazon.
Any thoughts as to how I may accomplish this?
If not, can you at the least convince me amazon won't care that my boot loader is unlocked?
Click to expand...
Click to collapse
Not sure if Amazon will even care if it is locked or not.
Thanks to AdamOutler and a few others, you can re-lock the bootloader without being plugging into a computer, but root (and busybox) is required.
Download the attachment from this post, and extract the files to the root of /sdcard. Then open a terminal emulator on your device and type the following commands:
su
dd if=/sdcard/param.lock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param
That should re-lock your bootloader.
Now you need to make sure you are running a stock ROM and stock recovery.
Once that is done, you can then remove busybox, and finally, you can delete /system/app/Superuser.apk and su.
EDIT: For those that are curious, to unlock your bootloader without wiping, replace the command above with this:
su
dd if=/sdcard/param.unlock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param

efrant said:
Not sure if Amazon will even care if it is locked or not.
Thanks to AdamOutler and a few others, you can re-lock the bootloader without being plugging into a computer, but root (and busybox) is required.
Download the attachment from this post, and extract the files to the root of /sdcard. Then open a terminal emulator on your device and type the following commands:
su
dd if=/sdcard/param.lock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param
That should re-lock your bootloader.
Now you need to make sure you are running a stock ROM and stock recovery.
Once that is done, you can then remove busybox, and finally, you can delete /system/app/Superuser.apk and su.
Click to expand...
Click to collapse
Awesome efrant, thank you.
I'll reference to this later if need be.

efrant said:
Not sure if Amazon will even care if it is locked or not.
Thanks to AdamOutler and a few others, you can re-lock the bootloader without being plugging into a computer, but root (and busybox) is required.
Download the attachment from this post, and extract the files to the root of /sdcard. Then open a terminal emulator on your device and type the following commands:
su
dd if=/sdcard/param.lock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param
That should re-lock your bootloader.
Now you need to make sure you are running a stock ROM and stock recovery.
Once that is done, you can then remove busybox, and finally, you can delete /system/app/Superuser.apk and su.
Click to expand...
Click to collapse
couldnt you take it a step further?
doesnt mobile odin work properly even if the bootloader is locked?

Zepius said:
couldnt you take it a step further?
doesnt mobile odin work properly even if the bootloader is locked?
Click to expand...
Click to collapse
Yeah, he could use mobile odin to flash to stock (and thus, no need to remove custom recovery, root, etc.), but mobile odin will not re-lock his bootloader.

efrant said:
Yeah, he could use mobile odin to flash to stock (and thus, no need to remove custom recovery, root, etc.), but mobile odin will not re-lock his bootloader.
Click to expand...
Click to collapse
ah i figured you could still use mobile odin to restore to stock with the bootloader already locked when you first run it.
ive never used it so i guess i didnt understand completely what it did.

Zepius said:
ah i figured you could still use mobile odin to restore to stock with the bootloader already locked when you first run it.
ive never used it so i guess i didnt understand completely what it did.
Click to expand...
Click to collapse
No, you're right. You CAN use mobile odin with a bootloader already locked. However, you need root to use it.

efrant said:
No, you're right. You CAN use mobile odin with a bootloader already locked. However, you need root to use it.
Click to expand...
Click to collapse
so you could then change the param file, which locks the bootloader, then use mobile odin to go back to 100% stock and still have a locked bootloader.

Zepius said:
so you could then change the param file, which locks the bootloader, then use mobile odin to go back to 100% stock and still have a locked bootloader.
Click to expand...
Click to collapse
Yes. That's what I was trying to say in my earlier post, but I guess it wasn't clear. Mobile Odin will not change the lock state of the bootloader, but will work in either a locked state or an unlocked state, assuming you have root.

More details on my phone: It is rooted, running aokp m5 & franco m3. It sounds like there is a solution to my problem contained within this thread - however, things are a bit hazy to me when it comes to what order to perform these operations and which apps to use when.
My thanks to the first person who compiles a step-by-step (albeit brief and concise) guide to unrooting, re-locking the bootloader, and restoring to stock WITHOUT being connected to the computer!

I don't know how you have broken USB, but my friend had it broken - it didn't want to charge longer than few seconds, connection to PC was extremely inconsistent...
Samsung told him that it happens on SGNs sometimes and that it is caused by oxidation of USB. It isn't covered by warranty.
But he solved it very simply - you can clean the USB by soft toothbrush and it works like a charm again. Hope this helps you.

mt6272 said:
More details on my phone: It is rooted, running aokp m5 & franco m3. It sounds like there is a solution to my problem contained within this thread - however, things are a bit hazy to me when it comes to what order to perform these operations and which apps to use when.
My thanks to the first person who compiles a step-by-step (albeit brief and concise) guide to unrooting, re-locking the bootloader, and restoring to stock WITHOUT being connected to the computer!
Click to expand...
Click to collapse
It is not that difficult, and I'm sure you do not need a step by step.
I haven't tried this on my device, as I don't really feel like wiping, but:
1) Lock your bootloader as per my post above. EDIT: I just looked at Mobile Odin, and it seems that Chainfire has implemented flashing the param partition as well in his app, so you can skip this step and go straight to step two.
2) Download the param file from the same post mentioned in step 1, and extract it to the root of your /sdcard.
3) Rename the param.lock file to param.img
4) Download version of the stock ROM for your device from here, e.g., if you have a GSM device, download the maguro factory image, if you have a Verizon device, download the toro factory image.
5) Extract the system, boot, userdata and recovery images from within and place them on the root of your /sdcard.
6) Buy Mobile Odin Pro from the Play Store. [You can use get the free version from the XDA thread here, but it needs setting up, and I'm not going to guide you through that.]
7) Run Mobile Odin Pro and follow the instructions here. It should be pretty obvious what you need to do.

I'm running AOKP 4.2, their latest release. I, too, have a failed USB connection. I downloaded the latest recovery from the link for my Verizon Toro. When I used the paid version of Mobile Odin, it says "partition could not be found in file". I tried the older, ICS image, but it just factory reset my AOKP install, not reflash to stock. So far, I've locked the boot loader, but I can't get rid of AOKP. I think it is because Mobile Odin doesn't reflash the bootloader, which I learned after my attempt, and I attempted to Odin back to factory ICS, which is a different bootloader. My other thought was to get into TWRP and flash an older AOKP ICS build, which flashes the older bootloader(right??), and try again, but I have no recovery, stock or otherwise after my Mobile Odin attempt. Any advice at this point? Should I just send it to Verizon as-is and let the chips fall where they may?

Quick update: I used Goomanager from the market to instantly flash TWRP. BAM! Recovery restored! I just finished flashing AOKP Jellybean Milestone 1, which is 4.1.2. I also figured out my JRO030 issue. It was a bad .tar file. When I browsed it with Winrar, it containted another file with the same name and no extension. I found another .tar file with the entire file structure inside. I'm currently booting into AOKP M1 as I type. I'll attempt to Mobile Odin with the JRO030 factory image (4.1.1) over 4.1.2 and then update this thread again. I hope I can save others some heartache.

The JRO030 update said something about "unable to extract update script". So I gave up on Jelly Bean and went futher back. I found an old AOKP ICS build, Milestone 6, flashed to that and used the monster 470 mb 4.0.2 update file that was linked to in a galaxynexusforums post with Mobile Odin. TADA! It worked like a charm. No root. Stock software. The only downside is that recovery is broken. It shows an Android guy with a red exclamation point over his belly. Whatever. I'm on 4.0.2 stock VZW software. That's all I care about. Let me know if anyone needs help with this.

scubamike said:
Snip
The only downside is that recovery is broken. It shows an Android guy with a red exclamation point over his belly. Whatever. I'm on 4.0.2 stock VZW software. That's all I care about. Let me know if anyone needs help with this.
Click to expand...
Click to collapse
That IS the stock recovery.
Sent from my Nexus 4 using Tapatalk 2

efrant said:
That IS the stock recovery.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I thought it was too, but, just for the heck of it, I tried taking the OTA. It rebooted and stuck on the android guy with the red exclamation. I had to pull the battery.

It is the stock recovery and no, you did not have to pull the battery. The Android with the red triangle is the main screen of the stock recovery . To access the menu from the main screen, hold power and press volume up. This is covered in at least 2 of the stickies in the General section.
Sent from my Nexus 4 using Tapatalk 2

Hi guys, I need your assistance. I am unable to transfer movies from phone memory to

Sent from my HTC One_M8 using XDA Free mobile app

KitKat and SD card issue, if you are stock and rooted - use this http://goo.gl/UfqPKb

Thanks for your reply. My m8 is stock...n I am not planning to root my phone yet as I am new to android. Is there a fix for stock m8
Sent from my HTC One_M8 using XDA Free mobile app

beastyricky said:
Thanks for your reply. My m8 is stock...n I am not planning to root my phone yet as I am new to android. Is there a fix for stock m8
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Nope, no way.
You have to switch to the dark side (root) of android users only ;D

Hahaha...I will try it out then...hope my phone won't get bricked...
Sent from my HTC One_M8 using XDA Free mobile app

You won't brick your phone rooting it. HTC even provide the tools to help achieve it by unlocking the boot loader. All you need do then is install twrp recovery and it will do the rest.

Don't even need to install/flash TWRP to get it rooted, can just boot TWRP and still flash SuperSU to get root, which is what I have done. Benefit - You get to keep stock recovery for future OTA's (Even though you can flash it later on, I know... =oP )

BerndM14 said:
Don't even need to install/flash TWRP to get it rooted, can just boot TWRP and still flash SuperSU to get root, which is what I have done. Benefit - You get to keep stock recovery for future OTA's (Even though you can flash it later on, I know... =oP )
Click to expand...
Click to collapse
good to hear HTC let you do this again!!! I thought they stopped doing this on the first hboot update on m7, great stuff!!! :good:

BerndM14 said:
Don't even need to install/flash TWRP to get it rooted, can just boot TWRP and still flash SuperSU to get root, which is what I have done. Benefit - You get to keep stock recovery for future OTA's (Even though you can flash it later on, I know... =oP )
Click to expand...
Click to collapse
cool, how do I just boot TWRP without actually installing it so I can retain my regular stock recovery to take OTA's? I thought I had to install it? I have not rooted M8 yet, but I did my EVO 4G LTE - was just hanging back to make sure the initial OTA's were all out before rooting - but if I can just boot TWRP to install supersu that would make life so much easier.

tommy_riley said:
cool, how do I just boot TWRP without actually installing it so I can retain my regular stock recovery to take OTA's? I thought I had to install it? I have not rooted M8 yet, but I did my EVO 4G LTE - was just hanging back to make sure the initial OTA's were all out before rooting - but if I can just boot TWRP to install supersu that would make life so much easier.
Click to expand...
Click to collapse
Boot into bootloader, connect phone to PC, open command prompt, change directory to adb.exe / fastboot.exe folder. Type fastboot devices to make sure your device gets picked up, should show you serial number of the phone. Then type fastboot boot name_of_recovery.img. Just make sure you have the custom recovery(TWRP) extracted(not in .zip form) in the fastboot/adb folder as well.
Done, that's it :good:
Edit: Of course I'm sure you know the bootloader needs to be unlocked as well.

BerndM14 said:
Boot into bootloader, connect phone to PC, open command prompt, change directory to adb.exe / fastboot.exe folder. Type fastboot devices to make sure your device gets picked up, should show you serial number of the phone. Then type fastboot boot name_of_recovery.img. Just make sure you have the custom recovery(TWRP) extracted(not in .zip form) in the fastboot/adb folder as well.
Done, that's it :good:
Edit: Of course I'm sure you know the bootloader needs to be unlocked as well.
Click to expand...
Click to collapse
excellent, thanks for the quick reply and also not saying "go search for it" - yeah, very familiar with the bootloader unlocking method via htc website - I don't know a lot but have spent some time with unlocking
I also feel proud to be one of the few who knows how to get adb/flashing to work via my windows 8.1 USB3.0 only system - but that's another story.
thanks again for the response - going to go do this later today.