Looking for a root solution on this phone
Someone must have had success
Could we use .img root steps as outlined for UMX u673
appreciate some solid info here
i have been asking to no avail also. i am working on trying to pull the stock image, havent figured out how to do so without gaining root first. if i have any success i will be sure to share.
There may be something in the alternate fastboot mode. You can boot into it from the bootloader, which appears to come unlocked on this model.
I've been trying to run fastboot binaries over OTG but my LG isn't rootable and I don't have a PC. I know some ZTE devices had an adb flag to disable write protection from some of those gov't phone providers.
I think the alternate fastboot is called like ffdm or something like that.
Related
Im sure this is a no go but thought i'd ask for the hell of it. Basically, my only PC has been my laptop and I *accidentally* broke it.
I don't know if you're still locked or not but I think you would have to already be unlocked. You do need a pc to get the unlock token and flash that, I don't think there's any way around that, but if there is hopefully someone will post it if you need it.
If you're already unlocked you may be able to. There's an new tool that I believe lets you flash a recovery from your phone (I haven't had a need for it so haven't looked into it in depth), and I know that if you flash Amon Ra you can get root from that by installing su in the developer menu.
http://forum.xda-developers.com/showthread.php?t=1504824
There's no single app like z4root that will root the Rezound. Like feralicious points out you need a PC just to get the unlock token. I tried to create an app for this way back when but it didn't work without the developer USB access. And now that the exploit has been plugged the only way to root is via Amon Ra or by loading a custom ROM with root already installed.
I haven't exactly rooted 100 devices before. Most of the root utilities I've used were things like Z4Root where it's one click and done. I've recently become interested in flashing my Incredible 4G LTE. On top of that, I've already rooted my Nexus 7 using instructions like this here.
http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html
I'm curious if this guide, being that it's more of a manual way to do it since it involves running several commands (I ran this from my Linux desktop to root my N7) is anything like what it would be to root the Incredible manually, or any device. I guess the only device that would be different would likely be the bootloader step (grouper?) since HTC likely did their's differently than Google with the Nexus 7, no?
Just trying to get more insight on it, as I certainly don't want to brick anything but I'd like to get them done. :good:
It seems to me that we would first need a modified bootloader or /system to attempt to flash, but I doubt "fastboot erase ..." is allowed without dev unlock on the bootloader, and "fastboot flash ..." most likely needs a signed image.
Does anyone with more expertise on this topic have any input?
JaSauders said:
I haven't exactly rooted 100 devices before. Most of the root utilities I've used were things like Z4Root where it's one click and done. I've recently become interested in flashing my Incredible 4G LTE. On top of that, I've already rooted my Nexus 7 using instructions like this here.
http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html
I'm curious if this guide, being that it's more of a manual way to do it since it involves running several commands (I ran this from my Linux desktop to root my N7) is anything like what it would be to root the Incredible manually, or any device. I guess the only device that would be different would likely be the bootloader step (grouper?) since HTC likely did their's differently than Google with the Nexus 7, no?
Just trying to get more insight on it, as I certainly don't want to brick anything but I'd like to get them done. :good:
Click to expand...
Click to collapse
What those tools do is use an exploit to write the su and superuser.apk to /system and/or a modified recovery for flashing ROMS and kernels on unlocked bootloader devices.
google has properly patched those exploits as they should as we don't want a malicious app installing Root and hacking data on just anyone's phone.
Some phones with locked bootloaders have had exploits to install custom recovery and/or hacked/leaked bootloaders in order to allow us to use the phone like it was unlocked. HTC fixed this issue with their latest phones.
Their bootloaders now do not run all of the adb commands until unlocked by HTC dev, which limits us a lot. They also made it so that even if we DID manage to find a software exploit and start flashing stuff, the locked bootloader would know, via a signature check, that something was modified... and refuse to boot (Bricked Phone).
HTC Dev unlock is not true unlock either. We still can't modify the HBOOT w/o triggering it to brick the phone. An unlocked HTC bootloader limits changing the kernel to HBOOT mode only, which means u need a PC and extra steps to finish flashing any ROM.
Some brilliant Dev's managed to use RUU files to update the kernel only, but that also causes issues. If one Dev uses a newer RUU, you can't use the another Dev's older RUU to flash a kernel because the unlocked HTC Bootloader doesn't allow you to "Downgrade" firmware. This leads to headaches with people ignoring the kernel step and screaming because their phone won't boot.
The ultimate Holy grail for is is what is known as "S-OFF"
This allows full access to the HBOOT Recovery and system for all of our awesome devs to work their magic. This was obtained (long after HTCDev unlock) with the Rezound only through a HARDWARE exploit. We needed root exploit (which we had on the GB stock ROM), and to physically short out a pin on the mainboard to ground at precise times while the SOFF program ran on your PC.
We have to wait for the less popular HTCDev unlock (which HTC Did give us on the rezound with a middle finger to verizon), or for some1 to find another Exploit that would bypass the signature check of the HBOOT and give us "S-OFF".
Either will give us Root, custom recoveries, and ROMs.
I am no dev, but this is my understanding of what's happening with these devices. This is my 9th android device, 5th HTC, but I am always learning more. Dev's feel free to correct me, or expand on anything I have written here ^^
I've decided to post a little blurb about the difference between rooting and unlocking your bootloader because I've seen too many posts using the terms incorrectly. I will update this based of off information posted here and as more information comes to mind.
Unlocking your bootloader:
First, let me describe what the bootloader is.The bootloader is a piece of software that is (essentially) the first thing that runs when you start up a device (bootloaders are on almost every device with an operating system.) The bootloader is what loads the operating system into memory. Now, unlocking the bootloader modifies the bootloader through a hack or a flag that is toggled in the bootloader (this is how the HTC Dev unlock works) that allows the recovery partition to be flashed (or a non-oem recovery to be flashed.) JCase's exploit (http://forum.xda-developers.com/showthread.php?t=2011611) is not a bootloader unlock; it is a method to allow the bootloader to be unlocked by modifying part of your device to emulate another device. This method allows you to use the HTC Dev website to semi-unlock the bootloader.
Rooting your device:
Rooting your device is gaining what is called root access to your device. On some devices, like the DNA, you must unlock your bootloader before you can gain root access. This is because after you unlock your bootloader you can put a file call 'su' in the /system/bin folder. Root privileges in Linux are equatable to administrator privileges in Windows. This is done by flashing the 'su' file to your device. The 'su' file is called by any program that would like to do things that need root privileges to do. The Superuser or SuperSU app on your phone is a manager for the su binary allowing you to allow and deny access to su. The su manager applications are equatable to firewalls for network access.
If anyone has any suggestions or comments for changes/mis-information let me know, please.
Edit:
Made some changes based off of Jarocks' information.
I'm not positive on this, but don't you need to unlock the bootloader to achieve permanent root on the Droid DNA? (Or even temporary root for that matter?)
Jarocks said:
I'm not positive on this, but don't you need to unlock the bootloader to achieve permanent root on the Droid DNA? (Or even temporary root for that matter?)
Click to expand...
Click to collapse
Yessir, you do.
Edit: I misunderstood your reply, and have modified my answer thusly.
Wanting to root Alcatel Fierce (model #5049z) and trying to discover whether boot loader is "locked". Read all the posts here concerning this phone and still don't know whether it can be rooted (yet). This is a fairly new phone and information for/about it is sparse. Anyone familiar with this phone and can offer up some vital stats/information or where I might obtain the information? This phone has "unlock boot loader" option, but not sure it works? HELP!!!!!! [Android 7.0]
THANX:
Rick
This does have a oem unlock option yet king root or kingo root doesnt work lol anyways I just picked one of these phones up today and looks like I will have to create my own root and hell mise well get a working twrp in order too. Back to the kitchen!
Just check whether bootloader is unlocked using fastboot.
Use rooting tools after unlocking.
Thats the plan, I planned on creating a way to root then once rooted I can make a full dump if all the partitions of the phone with fire flash then off to deodexing and debloating the system and placing SuperSU in the system so no more issues with root
I will like to know the working method as well i have turned on that option to unlock the bootloader but i have failed to google anything that actually works I have tried iroot, rootme, SRSRoot for Android and none of them was able to root the device
Anything yet?
Has anyone going out anything on this phone. Would like to be able to change a few settings on this phone. Thanks.
I am a complete noob. Never rooted any device. The only reason I'm doing this is my kid wants to do gps spoofing on pokemon go. I've been doing research for a couple of days now. There are many tutorials but all are slightly different.
The reddit page called the number 1 hub for pokemon go spoofing says what I need to do is....
Unlock Bootloader.
Install Magisk.
Install Smali Patcher.
This has proven to be more difficult that I first assumed. So far I have unlocked bootloader but I made a mistake because the first few tutorials I followed said nothing about backing up DRM keys or TA keys. So I guess I have lost that option.
Now I'm trying to install Magisk but apparently I need to do this through TWRP.
So trying to install TWRP. Found the right one for my device on TWRP official website says something about extracting stock boot image and patching but can't find any tutorials on how to do this.
Any help from this point will be much appreciated!
I'm starting to question is any of this actually worth it. If I new it was going to be this difficult before I started I don't think I would of bothered. If I was to change my mind is there a way can restore the tablet to its original state. I've read up a bit about relocking the bootloader but does that mean I've lost DRM keys and TA keys for nothing.(Is that even that big of a deal. Will my tablet not perform as it should without them?) I've read a little about Sony Emma or using the Sony companion to restore the tablet. Does that mean I get the DRM or TA keys back?
Ok so I was unsure if I unlocked the bootloader properly. My dialler app has disappeared so can't check it that way. Trying to check through cmd on minimal adb and fastboot but it just hangs when I type fastboot oem device-info. So I installed sony companion and tried software repair and it said it cant repair as the bootloader has been unlocked.
So that confirms it has definitely been unlocked. Will there be a problem If I Relock and try software repair again?
Ok so I got eager and thought f it. I'm just gonna do it. So I got the twrp.img file, put it in the adb and fastboot folder, in cmd wrote fastboot flash recovery TWRP.img. It looked like everything went ok. I'm pretty sure it said successful. So I'm now trying to boot into recovery mode. Holding down and power on and nothing is happening. Just boots up normally. What am I missing.
I downloaded the twrp app from appstore messed around with a bit and its needs root device not rooted. Did I not do the flash right?
Can I use flashtool to flash twrp.img instead of adb and fastboot?