Related
Hello, all!
I ran through lots of threads, but I cannot find a remedy for my problematic rooting.
Firstly, maybe I have to warn you that I'm noob in rooting devices, I promise I'll catch up!
I very much would like to root my Dell Streak, I chose SuperOneClick 2.3.1 to do so.
I got SuperOneClick, turned my phone in USB debugging mode, allowed unknown apps, unmounted SD card.
Connected all cables...press Root and SuperOneClick gets non-responding after:
(see attached picture)
In this situation if I run adb devices I see mine listed.
Have you had similar situation? Have you got any ideas how to finish rooting my phone?
Ok. Forget SuperOneclick Go to this link and read, absorb, read again, read once or twice more then, absorb. Finally read over many more times and once you think you've taken it all in, read it again. Honestly. Rooting is great if you get it right but it's what nightmares are made off if you brick your phone.
http://forum.xda-developers.com/wiki/Dell_Streak_5/Flashing_Guide#Rooting_your_phone
Basically, you need to install Streakmod (a custom recovery) using "Fastboot". This will enable you to install "Superuser. zip". This will "Root" your phone. Best of luck.
You're nicer to him than I would have been. All I will add to what you said is that the search engine is his best friend and he might want to learn how to use it.
Yeah, but if the OP comes back with the same question i'll send em back to the same link. As you know, there is probably an answer to every "Android" related question within this forum. People just need to look. I'm just being nice cos back in February i was a noob asking the same question. What i quickly learned was, if you bother to look, you find and you learn loads of other valuable stuff along the way.
I had simialar issue and solved it
my dell streak was not able to fastboot dellstreakMOD because after reboot the system auto overwrite mod file. So I need Root first to trick/disable auto overwrite function.
Then I run into SupperOneClick 2.3.1 issue. I solved problem by using much older version supper One Click 1.55.
Good Luck!
One-click root solutions aren't recommended for the Streak because as you found out, they don't always work. However, the method on the wiki has a success rate of 100%. So what I don't understand is, why in the heck would anyone use a method that has a high rate of failure over a method that doesn't.
hey...s.o.c is no more recommended...
just flash the su.zip using streakmod and voila.. nothing else
Sent from my Dell Streak using xda premium
alpharetta said:
my dell streak was not able to fastboot dellstreakMOD because after reboot the system auto overwrite mod file. So I need Root first to trick/disable auto overwrite function.
Then I run into SupperOneClick 2.3.1 issue. I solved problem by using much older version supper One Click 1.55.
Good Luck!
Click to expand...
Click to collapse
The reason, why we are using the SupperOneClick is already mentioned: You are proposing us to do the fastboot method to get the custom recovery running. But to do so on the streak we first need to avoid the automatic restore of the stock-recovery tool. And to do so, we need a rooted device...
You see our point? It's like a cat biting in it's own tail, or a man sucking his own... You got me though?
It's not a proposal. If you bothered to look at the bottom of the flashing guide page on the wiki, you would have seen the following note:
Not recommended: Gingerbreak, SuperOneClick, Universal Androot, Z4Root
Click to expand...
Click to collapse
That note is on the flashing guide for a reason: these methods quite frequently do not work on the Streak. Besides, this really isn't as difficult as you're making it sound. The one thing that needs emphasis is that you'll install StreakMod Recovery twice. The first time is to root. The second time comes after using a file manager to delete install-recovery.sh, the file that causes the recovery to get overwritten.
If that series of steps in the flashing guide is too much for you to handle, I would not recommend rooting. The Streak is arguably the easiest device to root, requiring no special tools like goldcards to do the job. If you want a real challenge, try rooting an HTC Inspire. Without special tools an Inspire cannot be rooted.
Hi there quick question as I just got my hands on a Dell streak I see you post the guide for rooting and say its 100% safe is this 100% correct cause I don't fancy bricking it also will it work on build froyo 2.2.2?
By the way I'm not not a noob as I rooted my dhd the hard way round when it first came out the same way the inspire was rooted also built 2 custom roms and work on 3 others
Only asking cause the set up of the Dell is very different to an htc and a year on htcs are getting easier to root with a one click tool
And please don't say to read read and read again as that's what I will be doing anyway I ain't going to fly before I can walk lol
sent from my dhd
This rooting method works with any stock ROM. One-click methods fail for various reasons, and on a failure are likely to require the restore tool we have for the purpose, QDL Tool, in order to recover from the failed root.
With a Streak you need nothing more than some knowledge of how to use Fastboot to get the recovery on the Streak. This is more educational than using a one-click tool in my opinion. From there, the trick is immedately booting into the recovery after flashing it so you can flash superuser.zip. Once you've got superuser.zip on the device, you're rooted even if the recovery is overwritten. For best results however, you need to make sure to delete the file I mentioned in my prior post and install the recovery a second time. The one part that seems to trip most people up is flashing the recovery twice. They don't anticipate the recovery they just installed being removed when they try to get into it.
Now, is it 100% safe? Unless you do something you're not supposed to such as pulling the cable while in the middle of flashing a recovery or trying to erase the Streak using fastboot -w/fastboot -erase it's very safe. Safer in my opinion than the AAHK for the Inspire because with the AAHK you have numerous opportunities to brick the Inspire (S-OFF, Radio Install, Recovery Install) instead of just one (Recovery Install).
I don't have to tell you to read and read again. My sig takes care of that. But after 3,000+ posts I don't think you have to read my noob FAQ. Especially as you are not a noob.
Strephon Alkhalikoi said:
This rooting method works with any stock ROM. One-click methods fail for various reasons, and on a failure are likely to require the restore tool we have for the purpose, QDL Tool, in order to recover from the failed root.
With a Streak you need nothing more than some knowledge of how to use Fastboot to get the recovery on the Streak. This is more educational than using a one-click tool in my opinion. From there, the trick is immedately booting into the recovery after flashing it so you can flash superuser.zip. Once you've got superuser.zip on the device, you're rooted even if the recovery is overwritten. For best results however, you need to make sure to delete the file I mentioned in my prior post and install the recovery a second time. The one part that seems to trip most people up is flashing the recovery twice. They don't anticipate the recovery they just installed being removed when they try to get into it.
Now, is it 100% safe? Unless you do something you're not supposed to such as pulling the cable while in the middle of flashing a recovery or trying to erase the Streak using fastboot -w/fastboot -erase it's very safe. Safer in my opinion than the AAHK for the Inspire because with the AAHK you have numerous opportunities to brick the Inspire (S-OFF, Radio Install, Recovery Install) instead of just one (Recovery Install).
I don't have to tell you to read and read again. My sig takes care of that. But after 3,000+ posts I don't think you have to read my noob FAQ. Especially as you are not a noob.
Click to expand...
Click to collapse
Thank you very much for the info seems pretty much straight forward will crack on with it in a few days once I'm familiar with as much as I can need to learn the streak more before I start playing lol
As for the inspire its pretty much the same as a dhd and tbh flashing a radio is as simple as flashing a Rom from recovery I also tested flashing the radio from a different htc phone and regardless that it flashed but got stuck on splash screen I could still not brick the phone, now its really difficult to brick inspire or dhd, but it is known that eng s-off can cause issues on the inspire but not on the dhd
Just some info back for yourself mate as a thank you for yours also will hit the thanks button next time I'm pc
sent from my dhd
Thanks for the info. I rooted my roommate's Inspire using the AAHK on the day she got it. It ended up being a little more time consuming than using REVOlutionary to S-OFF my Aria the second time I rooted it*. I proceeded to put Android Revolution on the Inspire and she's a happy camper.
*The first time I rooted the Aria, which was the day I got it a year ago, I used UnrEVOked to root it. At the time there was no S-OFF possible.
Perspective for users of devices with locked bootloaders:
All dell devices are the equivilent of S-OFF/unprotected bootloader devices.
S-OFF, root, and custom are all seperate (but closely intertwined) concepts.
There are equivilents of superuser.zip for the nexus devices, as they ship either S-OFF or have
'fastboot oem lock/unlock' available to allow the user to S-ON or S-OFF at will.
Superuser.zip is equally valid on an already s-off'ed device that has a custom rec installed.
If your device can be officially S-OFFed and you install a custom recovery and use superuser.zip (or the device's equivilent form) you never have to touch a one click tool.
If your device is S-ON and there is no official way to S-OFF you must S-OFF it first, usually that requires making changes on it while it's on, which usually requires root. The only way to root a live device is though exploits in android, this is what one click tools do.
After having S-OFF'ed you can install a custom rec, and then it doesnt matter if you're rooted or not as you can install custom recs.
As long as you remain S-OFF'ed you never have to worry about rooting as custom recs/flashing zips completely bypasses android's security model.
This is the only reason that Android 3.0+ can be rooted, the ONLY ways to root 3.0+ is by rooting outside android. There are no known exploits in 3.0+ (and hence ICS devices are completely unrootable for the time being if S-ON) Every single 3.0+ device is rooted by either by superuser.zip or superboots (which are normal kernels that automatically install superuser.zip without needing a custom recovery)
The problem with superboots are that they are device AND rom specific, during the 2xx era for the s5 there were superboots available. But they had to be remade for every single version as flashing the wrong one will brick your device.
Most of the exploits used by one click tools are patched by 360, and I believe ALL exploits are patched in 4xx. Normally there are known vulnerabilities in 2.3.3, but Dell has added their own fixes to these seeing as it's one of the few devices running 2.3.3 that hasnt been updated to 2.3.4 or higher
Superuser.zip is version independant, and to a degree device independant. As long as it can mount your /system partition it can root it.
The S-ON/S-OFF terminiology is specific to HTC devices, but the concept is common to all android devices;
Dell = always S-OFF
HTC = dependant on device/carrier
Moto = mostly S-ON, some atrix's can be unlocked, xooms always unlocked
Samsung = usually S-OFF
'fastboot oem unlock' = sets S-OFF if allowed
'fastboot oem lock' = sets S-ON if allowed
I have a Velocity Cruz t301. I'm not able to root it yet with ClockworkMod. Is there an instruction manual for ClockworkMod somewhere ???
Dan
you should google clockworkmod and find out what it REALLY does...
Moved to Android Q&A.
The boot image is unsecured on the T301 so you should be able to connect with ADB and push the needed files through there. I don't have a link handy at the moment but I remember seeing a post here somewhere with detailed instructions.
Ok I understand. However I downloaded StevenJHillv0.3. and installed it. As far as I know it was supposed to have su capability "out of the box". So it didn't, but the device won't even let me ADB !! So I can't even ROOT now or do anything. SU was embedded in the StevenJHillv0.3 rom.
I have done machine language programming since TRS-8O and C64 but this thing is locked up tighter than FORT KNOX ! AND that android emulator is a joke.
When I did have ROOT capability in the past, it would only last for a little while. I could only get it back by using a PIN to reset and then going through the ADB process all over again.
I'm thinking that I would better spend my time on the Arduino !
Dan
btw StevenJHillv0.3 has ClockWorkMod and SU combined.
Dan
I'm a newbie here
I'm a newbie here and have been following this thread for a few days. I am the lucky owner of a Cruz T-301 (thanks to Craigslist). I purchased mine recently from a lady who got it last Christmas but since it wouldn't play angry birds......! I decided to try to root it (hence my interest in this thread). I have also visited the SlateDroid forum and noted an alternate method of rooting (and improving the performance) my T-301. I actually tried the adb method to root and speed up my unit. The problem is I don't know if I got the root and speedup done or not. How does one know if my T-301 is rooted? Performance does not appear to be significantly improved.
Hi Everyone,
Wanted to know if anyone has already figured out or through a different method, can help me root my phone.
It's an LG phone under GSM technology by TracFone for Walmart Straight Talk service. the Model is "LG l21g" or "lgl21g".
It is specifically running Android 5.0.1
I've learned it's better to follow a root process specifically made for the exact model of your phone. But since TracFones lack much in rooting fame, I'm hoping that there is a safe method used to provide basic root access to phones/devices that have the respective OS. For which in my case is version 5.0.1
I am new to rooting but not computers in general. I have searched for quite a while for a way to root my device by model. I've found nothing, and AndroidArea51 seemed to have a little success, but are not sharing a clear tutorial sadly. But I am skeptical about 1 click root apps and how they may tend root the device for a few months before unrooting automatically and then forcing the device owner to pay to root again. You know, the old regular malicious hijacking software you can't get rid of without a hard reset or what not.
I am also aware of locked bootloaders but am not sure of what it means for my request to root. Should i unlock mine if it is locked in order to root? Or is it unnecessary unless i want to flash a new rom onto my device? I've obviously read things online, but am still learning the relationships of all these things
I greatly appreciate all your time and help in anyway you can.
Thanks.
I used kingroot for a successful root on my LG destiny. Im hoping for recovery and roms soon but I don't know if any devs are intersted in our phone.
Failbringer60 said:
I used kingroot for a successful root on my LG destiny. Im hoping for recovery and roms soon but I don't know if any devs are intersted in our phone.
Click to expand...
Click to collapse
hey Failbringer60,
Hope your holidays were great and thanks for your comment. I am very skeptical of software such as kingroot and iroot and others of the same nature that are usually one-click root types. Though i'm not against using it if it's the only way to root less popular devices such as ours, i would rather have a little tutorial/guide on how to use the app/software to root the device then get rid of that app and its bloatware (and any other malicious ware that comes from it) and sustain a more honest or reliable superuser app/access to more precisely control the permissions that apps from the app store demand before download and use.
I have seen in other forums where users find that these one-click root apps aren't so trustworthy after a few months, and the device doesn't adhere to them as it did before. It's these kinds of things that sort of scare me. but if you are aware of a way to use these apps to gain root access and then a way to get rid of them while keeping root on my device safely, I would be more than glad to learn.
I am very new to rooting android devices since i've never done it before. and am trying to use my knowlegde from some PC maintenince to understand these things. so i hope that you can excuse me for not fully understand some things. But i am open to any help that can be spared.
Thanks in advance
hi
try kingroot on playmarket it worked in my tablert, only takes some minutes if you are lucky
Thanks.
thewildnative said:
hey Failbringer60,
Hope your holidays were great and thanks for your comment. I am very skeptical of software such as kingroot and iroot and others of the same nature that are usually one-click root types. Though i'm not against using it if it's the only way to root less popular devices such as ours, i would rather have a little tutorial/guide on how to use the app/software to root the device then get rid of that app and its bloatware (and any other malicious ware that comes from it) and sustain a more honest or reliable superuser app/access to more precisely control the permissions that apps from the app store demand before download and use.
I have seen in other forums where users find that these one-click root apps aren't so trustworthy after a few months, and the device doesn't adhere to them as it did before. It's these kinds of things that sort of scare me. but if you are aware of a way to use these apps to gain root access and then a way to get rid of them while keeping root on my device safely, I would be more than glad to learn.
I am very new to rooting android devices since i've never done it before. and am trying to use my knowlegde from some PC maintenince to understand these things. so i hope that you can excuse me for not fully understand some things. But i am open to any help that can be spared.
Thanks in advance
Click to expand...
Click to collapse
Thanks, I hope your holidays were great as well. I understand your reasoning for concern. I haven't been able to successfully use supersu to handle root operations. Busybox will not install correctly either for me. I have successfully achieved root access though through kingroot. I don't remember the version I used but it has been rooted for well over 2 months with zero issues. I have replaced my bootanimations without bootloops as well.
I am currently trying to romdump and pull device tree to see if I can get a KDZ created or ported. As I am trying to get twrp recovery installed. And I think the only way for that to happen is to get to 5.1. But to answer any doubt. My experience with kingroot has been okay. Also rootchecker apps confirm root as well.
Failbringer60 said:
Thanks, I hope your holidays were great as well. I understand your reasoning for concern. I haven't been able to successfully use supersu to handle root operations. Busybox will not install correctly either for me. I have successfully achieved root access though through kingroot. I don't remember the version I used but it has been rooted for well over 2 months with zero issues. I have replaced my bootanimations without bootloops as well.
I am currently trying to romdump and pull device tree to see if I can get a KDZ created or ported. As I am trying to get twrp recovery installed. And I think the only way for that to happen is to get to 5.1. But to answer any doubt. My experience with kingroot has been okay. Also rootchecker apps confirm root as well.
Click to expand...
Click to collapse
Thanks for your reply. I apologize for not being able to understand all the technical jargon when it comes to the android platform, but as i ask questions, i can pick up on it fairly quickly.
For now i take it that you are still figuring out a way to backup your android system, since the only offer the LG Destiny has, is to back up your data to google cloud. It seems that either tracfone devices took that ability away (since i think that any computer like device should have a recovery system - though i could be wrong) or it is a flaw in android 5.0.1 which is what our devices are running.
I take it that you are "romdump"-ing to kinda like create a clone in a storage space which you can turn into a recovery rom in case the device messes up - i think.
I'm glad to hear that Kingroot worked for you. I would like to try it too but i would first love to back up my system entirely so that if a noob like me does mess up, i haven't completely lost everything.
Can i ask you if you are able to delete/uninstall bloatware from your Destiny now that you have it rooted. But you say that you are not able to install supersu (which i assume is software that lets you control your device with admin rights)? Reading things online, i've come to see that kingroot has a supersu type of software, but that it's inferior or malicous or something, hence why people are trying to install supersu in replacement. I may be missing some facts there, but i'm always see a relationship between the two.
Would you lose your root access, or ability to remove bloatware and control other app permissions if you removed kingroot? Or is it supersu that retains the root access that kingroot achieved, but people are ridding their devices of kingroot because kingroot inevitably introduces its own bloatware at the price of a rooted device?
Sorry to sound all over the place. I've just seen a consistent connection between kingroot and supersu online everywhere i look. I've never seen how either of these apps work on a device once installed, but i do know that people are always using supersu right after using kingroot.
Exactly, for the LG leon user they got the update to 5.1 which enabled them to unlock the bootloader and flash a custom recovery for the ability to back up the rom. As for us Destiny users I think we aren't going to ever get anything but root for a while. And yes kingroot does install its own bloat ware. And I have removed all the stock bloatware that came with my phone.
Failbringer60 said:
Exactly, for the LG leon user they got the update to 5.1 which enabled them to unlock the bootloader and flash a custom recovery for the ability to back up the rom. As for us Destiny users I think we aren't going to ever get anything but root for a while. And yes kingroot does install its own bloat ware. And I have removed all the stock bloatware that came with my phone.
Click to expand...
Click to collapse
Hi Failbringer60,
Were you able to somehow successfully backup your Destiny's rom to use as a recovery source? I myself just went through a whole lot of folly and have practically lost my device. I believe my spoiled Destiny is soft-bricked. It will not boot past the LG logo screen. I don't think it's looping since it doesn't fade to black and return repetitively. It's just frozen on that screen. Now i'm diving deep and reading a whole lot more about such problems and solutions, and am learning much more. But sadly, the design Tracfone has left the Destiny (and most likely it's other android models alike) is quite handicapped. I've come to understand that there is absolutely no boot menu with particular options you'd normally find in flagship models, and recovery only works if, well, if the device still works (as far as i've tried everything i know). Part of that recovery would make sense if content was the only concern. Though any system based malfunction is merely a complete loss. I have yet to download and try a few pc applications that others use to connect to their android devices. But since needing exact phone/model firmware or system image backup to fix many android issues are what these pc applications use, and LG having completely omitted the lgl21g model from all their lists on their site (except for the product landing page of course), I have no idea how it would help my situation. For all I've said, i may stand corrected, since i have yet to attempt the revival of my device.
So i hope no one gets annoyed when i ask weird questions, but i'll do what i can and document my findings. If you or anyone else may know how to help me, I would very much appreciate it. If you need more info from me. let me know.
Thanks.
Massive update: I was able to root my phone successfully! Read my post below for detailed steps and why I think it worked!
Hi. New guy around. Disclaimer: I live in the Dominican Republic, using the Orange carrier, despite having a Verizon device.
I currently own a Verizon Galaxy Note 2 SCH-I605 which, until yesterday, was rooted and running a 4.3 stock ROM. Because of the Pokémon Go craze, I did my research and figured I could update the phone to 4.4, the minimum version required for Go. So I downloaded the Samsung software (running Win10 here), connected the phone, and upgraded the OS. After the upgrade, I obviously lost root, but also got a bunch of bloatware I had originally deleted when I first rooted it (NFL, IMDB and a bunch of other crap), and now, no matter what the hell I do, none of the multiple methods I've tried will work for rooting the phone. Off the top of my head, Odin fails with a NAND write error, CASUAL loops trying to install the same thing continuously, and the Android Toolkit clearly states that it can't root (I thought it could).
Currently these are the phone/OS specs:
Android version: 4.4.2
Baseband: I605VRUFND7
Kernel version: 3.0.31
Build number: KOT49H.I605VRUFND7
SE for Android status: Enforcing
Hardware version: I605.06
While doing my research, I've read that if the bootloader is locked, there's no luck for me in trying to root this thing, but I have no way of telling whether it is indeed locked or not. Furthermore, this update applies an unreasonable amount of annoyance to my phone, including not being able to write to the external SD card.
Is there anything I can do to get my phone rooted safely? If not, is there any reasonably foolproof way for me to return to the previous version (4.3) so that I can keep the device rooted?
I will appreciate any input on this. Thanks in advance and apologies if I'm breaking any rules with this thread; I went over the rules and didn't see anything I could be breaking with this.
MrSh1k1 said:
Hi. New guy around. Disclaimer: I live in the Dominican Republic, using the Orange carrier, despite having a Verizon device.
I currently own a Verizon Galaxy Note 2 SCH-I605 which, until yesterday, was rooted and running a 4.3 stock ROM. Because of the Pokémon Go craze, I did my research and figured I could update the phone to 4.4, the minimum version required for Go. So I downloaded the Samsung software (running Win10 here), connected the phone, and upgraded the OS. After the upgrade, I obviously lost root, but also got a bunch of bloatware I had originally deleted when I first rooted it (NFL, IMDB and a bunch of other crap), and now, no matter what the hell I do, none of the multiple methods I've tried will work for rooting the phone. Off the top of my head, Odin fails with a NAND write error, CASUAL loops trying to install the same thing continuously, and the Android Toolkit clearly states that it can't root (I thought it could).
Currently these are the phone/OS specs:
Android version: 4.4.2
Baseband: I605VRUFND7
Kernel version: 3.0.31
Build number: KOT49H.I605VRUFND7
SE for Android status: Enforcing
Hardware version: I605.06
While doing my research, I've read that if the bootloader is locked, there's no luck for me in trying to root this thing, but I have no way of telling whether it is indeed locked or not. Furthermore, this update applies an unreasonable amount of annoyance to my phone, including not being able to write to the external SD card.
Is there anything I can do to get my phone rooted safely? If not, is there any reasonably foolproof way for me to return to the previous version (4.3) so that I can keep the device rooted?
I will appreciate any input on this. Thanks in advance and apologies if I'm breaking any rules with this thread; I went over the rules and didn't see anything I could be breaking with this.
Click to expand...
Click to collapse
Nope you are stuck on 4.4.2 since you upgraded and locked the bootloader. Only way back is to send it to a company but thats located in the states and im sure its not worth it. I believe you can still root though using towel root. Thats why you never accept updates. There are some stock roms you can flash now with that option, using R3Ds rom may be your best option.
Update: I was able to root the phone!
Essentially, this reddit post had what I needed: reddit.com/r/AndroidQuestions/comments/2oekwf/can_i_root_my_verizon_note_2_schi605_442/cmn5y51
What I think saved me was the fact that the phone had been rooted before the upgrade, so Root Browser, SuperSU and Busy Box were still there, even if they weren't running anymore.
I repeated the steps on it up until the second time I had to run adb devices to ensure the device was still connected — at this point I had to kill the adb server and start it again. After that, I finished the process with ghettoroot 0.2.2, but didn't see anything new or different on my phone. Then an idea occurred to me — what if SuperSU was failing to install because it was already there? So I fired up Root Browser (which wasn't deleted with the upgrade) and found the location of the SuperSU apk, reinstalled it, and voilá: root access again!
With full credits to the reddit user who posted that message, I'm going to repost and reorganize the entire process here for future reference:
Ensure you have the device drivers for the Note 2, you can get them from the Samsung site
Download Ghettoroot 0.2.2 and 0.3.2 from here: forum.xda-developers.com/showpost.php?p=55170966&postcount=1
Unzip both in an easily accessible location, make sure each has their own folder
Open a CMD window with "Run as Admin"
In the CMD window, navigate to the folder containing Ghettoroot 0.3.2
Inside this folder, type cd tools\win\adb and run the command adb devices (this should show you if your phone is recognized and connected)
Type cd ..\..\.. to return to the Ghettoroot 0.3.2 folder
Type install.cmd and let it run (remember, we're running 0.3.2)
Let the phone reboot and leave Installer mode
Run the cleanup; chances are it will fail, so try again until it works (it should, eventually — it took me a bunch of tries until it finally worked)
Type cd tools\win\adb to enter the adb folder
Type adb kill-server to kill adb, then type adb start-server to restart it (I needed this step because after running Ghettoroot adb wouldn't see my device anymore)
Type adb devices to ensure your device is still visible to adb
Now navigate to the Ghettoroot 0.2.2 folder
Type Type install.cmd and let it run (remember, this time we're running 0.2.2)
Let the phone reboot and leave Installer mode
Run cleanup again until it works
This SHOULD be enough to root your phone, especially if it was rooted before. If it was indeed rooted before, you should already have Root Browser and SuperSU in your /system/app folder, so navigate there and run/install Superuser.apk and execute it to be granted root access. I can't say if this would work if the phone wasn't rooted on 4.3, and I'm really iffy about mucking around with my device now that I safely got it rooted — apologies for not being able to offer more in-depth testing. But for what it's worth, I was finally able to root my Verizon Note 2 running ND7 with the above steps.
Hope this helps someone else out there.
Thanks so much! Somehow I lost root after a SuperSU update (?) from the Play Store. I'd forgotten how much trouble rooting this was.
I have an at&t variant HTC m8, I recently stitched to cricket wireless. SIM swap went fine. I've been wanting to gain root to remove att bloatware. I'm on android version 5.0.2. My main issue is I've gotten nowhere unlocking boot loader using a pc. Tonight I resorted to using kingroot from Google play,which worked on third attempt. However supersu said it needs an update.
So basically I'm lost and trying to find away to gain root without a computer if possible.
I've never used kingroot. What happens if you try to update the root binary?
May be a bit irrelevant. I think you'll need to unlock the bootloader to do what you want (delete bloatware). I don't think kingroot alone will get it done. Reason being, you can't modify the system partition with root alone. You need kernel mod wp_mod, which is flashed with custom recovery TWRP. And you need an unlocked bootloader to flash custom recovery.
What issues did you have exactly when trying to unlock the bootloader?
I believe my main issue was that my pc is out of date running an unauthorized widows 7 lol. I was unable to obtain adb or any twrp files to unlock boot loader hence my attempt at a one click type solution. I think I'm going to read up more and try the whole process over this weekend, but any tips guides or instructions would be helpful. The more I have looked into this the more conflicted things have become.
Lewis715 said:
I was unable to obtain adb or any twrp files to unlock boot loader hence my attempt at a one click type solution.
Click to expand...
Click to collapse
Not sure what "unable to obtain adb" means if you don't explain what happens exactly, where you are trying to get the files, etc. So all I can do is assume, and hope that I don't suggest you do things you already tried.
If you want an adb/fastboot installer, the following should work, and decently up to date: http://forum.xda-developers.com/showthread.php?t=2317790
Otherwise, there are other adb installers if you just type "easy adb" into the XDA search function.
No such thing as TWRP files that can help you unlock the bootloader. By definition, you can't install custom recovery until the bootloader is unlocked, and TWRP is a custom recovery. So nothing can be done with or by any TWRP files until you unlock the bootloader.
Lewis715 said:
I think I'm going to read up more and try the whole process over this weekend, but any tips guides or instructions would be helpful. The more I have looked into this the more conflicted things have become.
Click to expand...
Click to collapse
Again, can't really help with what is "conflicted" unless you give some specific details.
Its understandable that a lot of the threads may be confusing, as the info is often outdated. This is getting to be an old device, and a lot of folks that wrote the various guides have moved on, and not updating the guides.
The following is a pretty good AT&T specific guide: http://forum.xda-developers.com/showthread.php?t=2799796
But as mentioned, some things are outdated:
1) The driver package is old. You can get updated drivers by downloading HTC Sync from the HTC website. After installing (which will also install HTC drivers) you can uninstall Sync, but keep the drivers; if you don't want Sync (but I haven't had any problems keeping it).
2) I believe the Dropbox link for adb installer is dead, but I already gave an alternative above.
3) The TWRP version is really old, don't use it! Get TWRP 3.0.2 from here: https://dl.twrp.me/m8/
The exception might be in the stock Android version on your phone is old, but if you tell me what it says for OS number on the bootloader screen, I can advise more specifically.
4) TWRP version is old, again, don't use it! v2.76 is the latest "stable" version, and you can get it here: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
Everything else in the guide should still apply.
Vomer's guide is also a good one:
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Again, the TWRP version is out of date (use the current one linked above).
You only need to do Sections 0 and 1, as the remainder of the guide (S-off, SuperCID) doesn't apply for what you are doing (unlock bootloader, custom recovery, and root).
Also, highly recommended to make a TWRP backup of the stock ROM, before you root.
After root, flash wp_mod with TWRP to enable system partition changes to stick (and deleting bloatware is a system change). What wp_mod depends on your Android version. But for Marshallow, the wp_mod can be found here (you just need the zip wp_mod, not the whole ROM): http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
Thanks for the help I'll give it another try, honestly have no real need to mess with device. I know the phone is old but I still have it and it works better than others I've had.
Lewis715 said:
Thanks for the help I'll give it another try, honestly have no real need to mess with device. I know the phone is old but I still have it and it works better than others I've had.
Click to expand...
Click to collapse
Of course, the vast majority of us don't have any real need to mess with the device. But we do, nonetheless!