My Google-fu fails me, I've managed to root my xperia t with the adb backup timing exploit(?) which I'm pleased about, however I want to explore custom roms (specifically cyanogen-mod, which I've been comfortable with since my HTC Desire bravo), however my bootloader is locked, and is not "unlockable" apparently.
Since I have root anyway, isn't there something I could flash directly from terminal that would allow me to use cwm or similar, or am I going about this entirely the wrong way.
Ideas?
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 am trying to understand some more about this tablet, so far I have learned (please correct any errors):
These were given away at Google I/O with fastboot and an unlocked bootloader.
The ones you purchase in the store do not have fastboot, and have a locked bootloader.
An unlocked bootloader will show an unlocked padlock at the bottom of the screen.
You can still root and change ROMs with a locked bootloader, but cannot repartition your device, or use NVFlash without currently-unknown keys.
Without aforementioned keys, you cannot unlock or downgrade the bootloader, even with Odin. That or none of the Odin tars have the old unlocked bootloader.
The reason I am so fixated on the bootloader, is because this tablet seems to be nearly impossible to hard brick.
APX and Odin offer 2 modes of recovery, which should always be available, unless you wipe the bootloader portion of your NAND.
I am more interested in seeing what else I can make the tablet do besides run Android. The TABUNTU project is of great interest to me, but my GT-P7510 won't let me flash via APX...
I'd like to thank you as you have just managed to educate me a little I've only had my tab a few weeks so this was some good information I hope to try out some stuff also now I've herd its possible ill be fixated also
Sent from my HTC Wildfire S A510e using Tapatalk
It seems I have gotten TABUNTU to work via some Odin trickery, by sacrificing Android completely. Just because I cannot repartition the NAND, does not mean I can't use the existing partitions for un-intended uses
linux.img -> boot.img (modified boot.img-cmdline to mmcblk0p8)
ubuntu.img -> data.img
make into odin tar, flash.
Edit: more details here if interested in flashing TABUNTU on locked bootloader
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 ^^
Looking to permanently root my HTC Gratia running stock Froyo 2.2 and HBoot 1.02 but can't figure out what I need to do. I don't want to install any custom recoveries or ROM's just yet so does that mean I don't need to S-Off?
Should I root using http://unrevoked.com/recovery/ in this thread:
http://forum.xda-developers.com/showthread.php?t=788737
Or should I root using revolutionary in this thread which also does S-Off:
http://forum.xda-developers.com/htc-aria/help/root-gratia-aria-2014-confused-t2863923
Do the two links work for the HTC Gratia as well as the Aria as there is a difference in the baseband and I don't want to lose 3G on my Gratia (the Aria has a different frequency for 3G and some have lost their 3G after flashing/rooting).
Also, it seems the CWM custom recovery installed in the two links above may have a bug that causes the display to show the recovery screen when charging (see http://forum.xda-developers.com/showthread.php?t=2474662 and
http://forum.xda-developers.com/showthread.php?t=1159237). Does anyone know which version of CWM is installed by unrevoked and revolutionary and is there a version that doesn't have this bug so you can charge properly off-line?
One last thing, on the HTCDev website, it says the bootloader can be unlocked which also roots the phone. However, if I restart the phone, I think root is lost so this is not permanent. See http://forum.xda-developers.com/showpost.php?p=24831976&postcount=8 and also taken from the HTCDev.com site with relevant section highlighted in red:
"You do not need to turn security off to accomplish the basic installation of a custom rom which even includes providing root access and remounting your system to be writable. Note: you shouldn’t really need to keep the system files writable across reboots as this is primarily useful only while developing.".
If I do unlock the bootloader, does this root the phone or do I have to do something else?
All very confusing so if anyone could advise, that would be great. All I want is root for my stock Gratia Froyo 2.2 without custom recovery (if possible) or firmware or any charging bugs when the mobile is switched off! Thanks in advance.
Anyone able to help with rooting queries in the first post?
First off, ignore anything about unrevoked - it's an exploit for the old bootloader, and doesn't work on the newer one (1.02).
Revolutionary is probably the best way to go... I don't know of a way to get permanent root with the S-ON system protection.
This guide you already linked is the best IMO, and I think should be stickied...
Newer Revolutionary automatically installs its own recovery, so you can skip that part of the guide.
Just unlocking the bootloader doesn't add the required stuff for root (unless it's a script or something that does both).. So you'll need to install the SU zip linked at the bottom of that guide, then you should have root
Off-mode charging doesn't work with some recoveries because it's a part of the same recovery image, just telling it to boot differently - so if a recovery doesn't support off-mode charging, it just boots normally
I dug back a few pages and found this one: http://forum.xda-developers.com/showthread.php?t=1025704
I think I used it a long time ago, but I don't really remember much about it
Should be able to just install the zip from your current recovery. If not, extract recovery.img from it and boot the phone into fastboot, then run "fastboot flash recovery recovery.img" from your PC.
Sorry if I'm too late, there's hardly any activity here anymore so I don't check threads I'm not subscribed to very often
WinSuk said:
First off, ignore anything about unrevoked - it's an exploit for the old bootloader, and doesn't work on the newer one (1.02).
Revolutionary is probably the best way to go... I don't know of a way to get permanent root with the S-ON system protection.
This guide you already linked is the best IMO, and I think should be stickied...
Newer Revolutionary automatically installs its own recovery, so you can skip that part of the guide.
Just unlocking the bootloader doesn't add the required stuff for root (unless it's a script or something that does both).. So you'll need to install the SU zip linked at the bottom of that guide, then you should have root
Off-mode charging doesn't work with some recoveries because it's a part of the same recovery image, just telling it to boot differently - so if a recovery doesn't support off-mode charging, it just boots normally
I dug back a few pages and found this one: http://forum.xda-developers.com/showthread.php?t=1025704
I think I used it a long time ago, but I don't really remember much about it
Should be able to just install the zip from your current recovery. If not, extract recovery.img from it and boot the phone into fastboot, then run "fastboot flash recovery recovery.img" from your PC.
Sorry if I'm too late, there's hardly any activity here anymore so I don't check threads I'm not subscribed to very often
Click to expand...
Click to collapse
Thanks so much Winsuk for taking the time to reply.
You mentioned that unlocking the bootloader doesn't add anything for rooting but is it possible to install the SU zip using the stock recovery? I've read this guide and that guide for other HTC phones that seems to suggest that you can only do this by temporary flashing a custom recovery to install the SU zip. Is it not possible to install a zip using the stock recovery? I really want to do as little as possible and not touch the stock ROM or recovery if at all.
Also, I dont mind if the root is temp and is lost when restarting as I guess I would be able to install Titanium Backup and remove the factory apps I don't want (like FaceBook, Twitter,). Also, if I need to update the hosts file, once updated, if it is re locked by losing root after a restart then that's ok too.
Sorry if all these are too many questions, I'm not really a noob when it comes to rooting but for this little Gratia, there's not much info available and everything seems to be for the Aria which has a different baseband so very wary of flashing anything.
No, the stock recovery only accepts packages signed by HTC.
You can flash it back on after if you extract it from the RUU though. RUU downloads here if you don't already have one: http://www.androidruu.com/?developer=Liberty
Leave the phone unplugged (just in case) and run the RUU.. Once it appears, open task manager and go to processes/details (depending on what Windows you have), right click ARUWizard.exe, and click open file location (or something similar).
In that folder will be rom.zip (copy it out for later use if you want) - open it and inside will be recovery.img (and everything else that could ever be on the phone pretty much)
If you don't have access to a Windows PC, let me know which RUU matches your phone and I can extract it for you. If there isn't one exactly matching your phone, any of them will probably work - I don't think the recovery image differs much, if at all...
Thanks again Winsuk, much appreciated.
My current stock build is 47.54.35.20U_7.13.35.13 and the build is 2.37.405.10 so those RUU's you linked are very old. I've found a slightly newer Gratia Froyo RUU at 2.37.405.11 so that should work and it;s the WWE version rather than Asia WWE.
I'm thinking the best way to do this might be to unlock the bootloader and temporarily install a custom recovery to flash SU.zip. On reboot, the temporary custom recovery is lost but I think the root is also lost too. Seems that S-Off is the only way to achieve permanent root but even that doesn't seem to work cleanly. Revolutionary says that if Titanium doesn't recognise a rooted device then install Busy Box.
Might just leave it unrooted as is
My Lenovo P780 was a piece of cake to root compared to HTC.
Hello. Thanks in advance for your time and advice.
I've got a brand new HTC One M8, AT&T, firmware says 4.4.2 with no available updates.
I want to create an initial backup. I'm a computer technician, and just dabbling in Android, and it's important for me to make a "clone" of my phone before I proceed to wreck things. (This is a replacement phone, the last one had a hardware issue... I swear... I managed to install ViperOne onto it, for a week before the screen faded to white and died.)
I assume I'll need root access to make a proper backup. I also assume I should use Nandroid. I've not used the app before, but I'm sure I can figure it out. As far as root goes, I previously used Hasoon2000's HTC One 2014 (M8) All-In-One Toolkit, which worked well, as far as I could tell. (It's a visual basic program with scripts to download drivers, register at htcdev, get token id, submit it, unlock bootloader, flash recovery, and lots of nice ADB commands. Is this a good option to use? I hear many people use S-Off, but I don't really see a need... ?
So, I assume I'll need a new token ID from HTC, as the previous one I got corresponds to the old, malfunctioning phone.
After it's unlocked, I'd use the toolkit to grant perm root. That would be a great place to be for now. I plan to wait until the 4.4.4 update is pushed, then worry about installing a new rom.
Am I on the right track?
For the AT&T version (and most the major US carrier versions) we are lucky enough to have RUUs. So really, no need to backup the stock configuration. If you like, grab the RUUs and save them to your computer so you have them ready if and when it is needed.
Nandroid isn't a specific app, its just a generic term for a backup made with recovery. The custom recovery is your choice: TWRP, Clockworkmod, Philz.
Just a personal opinion, I would actually strongly recommend against using the toolkit for a couple reasons: most importantly using the toolkit robs you of an important learning opportunity. Doing the steps "manually" is a key way to learning your way around fastboot/adb. Doing the steps manually isn't that hard, and shortcutting the process with the toolkit really doesn't gain you much. Another key issue, is the toolkit introduces an additional point of failure. In fact, I've seen folks have trouble doing some of the steps with the toolkit; where doing the steps "manually" worked without a hitch. And the toolkit hasn't been updated for a long time, and will install an obsolete version of TWRP recovery, which in itself can cause issues.
If you used the toolkit before, you can certainly use it again. This is likely the path of "least" resistance, the the "easy" way to do things. But I wouldn't necessarily call it the "best" way to do it. If you don't already know your way around adb, I would do the steps manually. Since you have a background in computers, you will probably even find the manual process more enjoyable.
Yes, you would need to unlock the bootloader again via HTCDev.com, as the unlock bin code in based on the phone's unique IMEI.
The process would be as simple as unlocking the bootloader using HTCDev.com (very easy, the website is self-explanatory). Use fastboot to install custom recovery. Then to gain root, just flash SU or SuperSU in recovery. If you need a step-by-step guide, there is an excellent one here: http://forum.xda-developers.com/showthread.php?t=2799796
But also be aware that once the 4.4.4 OTA rolls out, you will need to return to stock recovery, and also restore any system files modifed by root, in order to install the OTA.
Thanks, redpoint73
Exactly the answer I was looking for. The guide looks great. Looks like there's a lot of useful information about reverting to stock, too. I guess I'll have a go at it now, as opposed to waiting for the update. Like you say, it's good to know things. Thanks much.
@redpoint73
Now I'm only asking cause I don't know everything. Couldn't those who have S-off just RUU the update once available instead of reverting to complete stock state(no root,no custom recovery, locked Bootlaoder)?
AT&T HTC ONE M8
jball said:
@redpoint73
Now I'm only asking cause I don't know everything. Couldn't those who have S-off just RUU the update once available instead of reverting to complete stock state(no root,no custom recovery, locked Bootlaoder)?
Click to expand...
Click to collapse
Absolutely. In fact S-off is not even required to run an RUU intended for your version (AT&T). If s-on, the added step of relocking the bootloader is all that is needed to run the RUU.
HTC seems to have gotten better about releasing the RUUs promptly. In fact, the previous (ill fated) 4.4.3 update saw the RUU and OTA roll out on the same day. Although this hasn't always been the case. On past devices, the RUUs were not released for weeks (sometimes longer) after the OTA started to roll out. And many folks don't want to wait that long.
Also, relocking the bootloader is not required to OTA, only to RUU.