Hi there
First, I know that it might be a stupid question, but I'm new to Android.
I've read about the official unlocking method HTC offers and yesterday I tried it out, worked all fine.
But what has changed? What can I do now which I couldn't before? I don't get it! Can I flash ROMs now? How?
I can only see that it now says "UNLOCKED" at the top of the bootloader. Also, I've read about Clockwork-Mod and TW and so on, so I tried to "install" Clockwork-Mod. Failed. Now it crashes when trying to open "Recovery" in bootloader.
But main question: What can I do now, with unlocked phone?
Thanks! And don't laugh about my English... I've tried my best
Install TWRP recovery, there is a sticky in the dev section. Then you can indeed flash ROMs however since you are s-on still you will have to flash a bit differently. Search the dev section for joeykrim's flash image gui. It has all the instructions you need to flash a custom rom.
A little further explaination, since you are still s-on the kernels don't flash correctly unless you flash using fastboot or joeys gui. If you don't flash this way you can end up in a bootloop or have broken wifi and 4g etc.
3VO Sent
luckyluke02 said:
Hi there
First, I know that it might be a stupid question, but I'm new to Android.
I've read about the official unlocking method HTC offers and yesterday I tried it out, worked all fine.
But what has changed? What can I do now which I couldn't before? I don't get it! Can I flash ROMs now? How?
I can only see that it now says "UNLOCKED" at the top of the bootloader. Also, I've read about Clockwork-Mod and TW and so on, so I tried to "install" Clockwork-Mod. Failed. Now it crashes when trying to open "Recovery" in bootloader.
But main question: What can I do now, with unlocked phone?
Thanks! And don't laugh about my English... I've tried my best
Click to expand...
Click to collapse
New to Android ... One of these days I should put together a guide from start to finish.
Here are a few more details in addition to the great answer already provided in the above post. A link to my applciation, Flash Image GUI, which makes loading custom kernels a little bit simplier and possible without a computer attached to the device.
There are basically three partitions we look to commonly customize on the Android device, boot, recovery and system. Of course, there are times when we customize or upgrade other partitions but they aren't as common or as required.
Boot holds the booting kernel.
Recovery holds the recovery kernel and recovery binary.
System holds the android system.
On many HTC devices, some or all of these partitions are locked by the bootloader which is essentially a very low level write protection.
The s-off revolutionary method removes write protection on all partitions.
The HTC unlock method removes write protection on some partitions and also depends on the mode the device is booted into. This is the first time HTC has made an official unlock method through their stock bootloader. Who knows if they will improve it in the future by unlocking all partitions or if they still stick to their current model.
Hope that helps a bit more background/history to the context! Good luck!
Related
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
Hey guys. Need a big hand here. So I have a HTC One on contract from Three in the UK.
I rooted the phone and all that jazz and decided on putting a custom ROM on my device.
However while in TWRP I wiped the phone and seemingly all the contents on it, including TWRP.
Now I have a bricked phone that boots into recovery/ the bootloader only. I've tried flasing
RUU files on but it fails with the error code 140? I don't know much about this I'm quite a noob.
In recovery the information is as follows:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_UL PVT SHIP S-ON RH
HBOOT- 1.54.0000
RADIO-4A. 17. 3250. 14
OpenDSP-v31.120.274.0617
OS-2.24.401.0
eMMC-boot 2048MB
Please help me. I've read through wonderful guides by other patrons on this website but nothing seems to work.
I'm at my wits end.
Thank you in advance for any help.
I know very little about this, but just to brainstorm (and confirm a few basic facts):
When you rooted originally, did you use HTC's bootloader unlocker or a different method to unlock the bootloader?
How are you flashing ROMS? Are you doing everything through the phone (example, using one-touch-root apps) or are you using the Android Debug Bridge?
The bootloader typically comes with options to reboot, boot into recovery, factory reset, etc. Can you confirm that these options have disappeared (or never existed in the first place)?
My knee-jerk reaction is that you didn't use an HTC bootloader unlocker and, therefore, the HTC GUU detects a bootloader mismatch and aborts. Therefore, you need to see if there's a way to flash a stock HTC bootloader (which, I can tell you from experience, is usually a one-way-trip to super-bricking) or see if the bootloader you already have installed can be unlocked through the ADB.
In my very limited experience and understanding of Android, it's generally pretty difficult to wipe the recovery partition from within the phone - one generally as to flash it from ADB or screw with the bootloader in some way to wipe it. I wonder, therefore, whether the recovery partition is just fine but maybe the bootloader is throwing a fit because it's not the HTC default.
I'm sure you've tried or thought of all of this, but since nobody else is stepping up, I thought I'd help brainstorm a bit and keep the thread fresh.
Borden Rhodes said:
I know very little about this, but just to brainstorm (and confirm a few basic facts):
When you rooted originally, did you use HTC's bootloader unlocker or a different method to unlock the bootloader?
How are you flashing ROMS? Are you doing everything through the phone (example, using one-touch-root apps) or are you using the Android Debug Bridge?
The bootloader typically comes with options to reboot, boot into recovery, factory reset, etc. Can you confirm that these options have disappeared (or never existed in the first place)?
My knee-jerk reaction is that you didn't use an HTC bootloader unlocker and, therefore, the HTC GUU detects a bootloader mismatch and aborts. Therefore, you need to see if there's a way to flash a stock HTC bootloader (which, I can tell you from experience, is usually a one-way-trip to super-bricking) or see if the bootloader you already have installed can be unlocked through the ADB.
In my very limited experience and understanding of Android, it's generally pretty difficult to wipe the recovery partition from within the phone - one generally as to flash it from ADB or screw with the bootloader in some way to wipe it. I wonder, therefore, whether the recovery partition is just fine but maybe the bootloader is throwing a fit because it's not the HTC default.
I'm sure you've tried or thought of all of this, but since nobody else is stepping up, I thought I'd help brainstorm a bit and keep the thread fresh.
Click to expand...
Click to collapse
I unlocked the bootloader originally by getting a specific code from HTC and using it through the command prompt I think. I can go into the bootloader and it has all the fastboot, recovery, factory reset business there. Trying factory reset does nothing. I've downloaded HTC toolkit 2.2 and I tried initially pushing ROMS to flash to TWRP, but it would never detect my phone. Then I stupidly did a full wipe through TWRP and now that's disappeared. All that's left is the bootloader now. I've tried forcing RUU updates through the HTC toolkit but it always fails. So does running the normal RUU process. I can't seem to find the correct one for Three UK. The most I've been able to do is re-lock the bootloader and I'm running out of ideas. Thank you for your reply. I feel so helpless!.
If I've read your message correctly, you are doing everything through the HTC toolkit and not through the Android SDK. Frankly, I don't know how the former works. Especially if the HTC Toolkit isn't detecting your phone, you may want to run over to http://developer.android.com/sdk/ and fetch the SDK for your system and set it up. You don't need the ADT Bundle, just the SDK Tools link at the bottom. This may make it easier for other, more knowledgeable people debug your phone, since they all use the SDK. The weaponry you'll be using is all in the <sdk install location>/tools directory, so get a command prompt window pointed there (by the by, are you using Windows, Mac or Linux?)
If you already have your SDK up, or once you do, you'll want to get familiar with the fastboot command, described in this post: forum.xda-developers.com/showthread.php?t=2277112 . What we want to do is see whether we can flash a new recovery ROM.
As long as you don't attempt to flash over the bootloader, you shouldn't super-brick your phone. Based on the message in your original post, your bootloader may have relocked itself. If your first attempt at installing a new recovery ROM doesn't work, then you'll have to use the procedure you used originally to unlock your bootloader. If you've forgotten how to do that, then these instructions (which assume you're using the SDK) should help: http://wiki.cyanogenmod.org/w/Install_CM_for_m7.
You're currently using TWRP, which I've personally found buggy. Until you have a functioning phone again, you may want to use ClockworkMod (CWM) Recovery instead: http://www.clockworkmod.com/rommanager. It has fewer features, but at least they work properly. If flashing ROMs over fastboot is new to you, there are plenty of guides on the Interwebs to help you. I'll also try to walk you through it if you let me know where you're getting stuck. The critical thing, considering that there are many types of HTC One, is to make sure that you flash the ROM that exactly matches your phone. If you flash the wrong ROM, you probably won't break your phone any more than it is, but let's try not to test that theory. If you're not positive which phone you have, say so and we'll help you find out.
Let us know once you have CWM on your phone or where you got stuck. The advantage of using the SDK, too, is that you can copy and paste the output right back to the forum.
I hope I understood everything correctly. Let me know if I haven't.
Hello,
I wanted to have newer android and have rooted and flashed HTC Amaze with Hasoons toolkit using TWRP recovery system. After flashing Cyanogenmod 10 ROM through ADB Sideload and flashing Cyanogenmod 10 ROM kernel (boot.img file which was included in the zipped folder) manually with Hasoons toolkit, the phone started to boot normally, load welcome screen, but after several seconds it freezes and then restarts. Can you please help what can be the cause of this problem and how can I repair? The phone is rooted and bootloader unlocked, but its still S-ON.
Before installing the Cyanogenmod I have tried to flash other ROMs, but on all of them after flashing kernel, the phone was freezing on booting mode and then just restarting continuously.
I hope there should be some way out and the phone is not bricked. If something I have backed up the data and will try to restore, but would prefer to repair Cyanogenmod ROM.
Thank you guys in advance for your help.
ratijs100 said:
Hello,
I wanted to have newer android and have rooted and flashed HTC Amaze with Hasoons toolkit using TWRP recovery system. After flashing Cyanogenmod 10 ROM through ADB Sideload and flashing Cyanogenmod 10 ROM kernel (boot.img file which was included in the zipped folder) manually with Hasoons toolkit, the phone started to boot normally, load welcome screen, but after several seconds it freezes and then restarts. Can you please help what can be the cause of this problem and how can I repair? The phone is rooted and bootloader unlocked, but its still S-ON.
Before installing the Cyanogenmod I have tried to flash other ROMs, but on all of them after flashing kernel, the phone was freezing on booting mode and then just restarting continuously.
I hope there should be some way out and the phone is not bricked. If something I have backed up the data and will try to restore, but would prefer to repair Cyanogenmod ROM.
Thank you guys in advance for your help.
Click to expand...
Click to collapse
Did you follow the directions posted in the pinned threads at the top of the forums and update to ICS before unlocking and flashing these other ROMs?
I ask because if you say you're unlocked, but s-on, and you need to be on an ICS radio baseband prior to flashing any newer ROM. If you were already on ICS prior to these flash attempts then I suggest you try again with the latest version of 4ext instead of TWRP, and make sure to enable smart-flash. TWRP doesn't flash kernels properly on HTC handsets with s-on, while 4ext does when smart-flash is enabled. Of course all of this comes with the stipulation that you're doing this on a T-Mobile US version handset.
If you're on an Asian or non-branded international version it gets a bit more complicated because you must attain s-off before attempting to flash. This is because these handsets never got an ICS update. So there is no carrier image to flash to, and the only way to install the updated firmware with the ICS baseband is to attain s-off first then flash the T-Mobile US image.
Again, if you haven't I strongly suggest reading the pinned threads at the top of the different forums here as they contain all of the info you need to successfully flash your device to an updated ROM. Good luck.
Ciao
Odysseus1962 said:
Did you follow the directions posted in the pinned threads at the top of the forums and update to ICS before unlocking and flashing these other ROMs?
I ask because if you say you're unlocked, but s-on, and you need to be on an ICS radio baseband prior to flashing any newer ROM. If you were already on ICS prior to these flash attempts then I suggest you try again with the latest version of 4ext instead of TWRP, and make sure to enable smart-flash. TWRP doesn't flash kernels properly on HTC handsets with s-on, while 4ext does when smart-flash is enabled. Of course all of this comes with the stipulation that you're doing this on a T-Mobile US version handset.
If you're on an Asian or non-branded international version it gets a bit more complicated because you must attain s-off before attempting to flash. This is because these handsets never got an ICS update. So there is no carrier image to flash to, and the only way to install the updated firmware with the ICS baseband is to attain s-off first then flash the T-Mobile US image.
Again, if you haven't I strongly suggest reading the pinned threads at the top of the different forums here as they contain all of the info you need to successfully flash your device to an updated ROM. Good luck.
Ciao
Click to expand...
Click to collapse
Thank you for information. It is non-branded international version. It means I will have to try S-off and then flash the ROM with 4ext.
ratijs100 said:
Thank you for information. It is non-branded international version. It means I will have to try S-off and then flash the ROM with 4ext.
Click to expand...
Click to collapse
Please read the pinned threads first. You're going to have to relock your bootloader before proceeding, so save the binary unlock blob you got from HTC as you'll need it to unlock again. Place the stock image in the root of your external SD card and flash from hboot. Then after getting s-off and superCID then you can flash the T-Mobile ICS image. Again read the pinned threads thoroughly or you'll be posting about how to unbrick your handset. Good luck.
Ciao
I had the same issues and had to turn off security with the joupunut bear program. Just to be safe with future flashing I've understood it works best. You should first s-off your phone and then go about flashing whichever firmware you want. Make sure you upgrade to the stock ics rom first as a pre requisite towards flashing any other rom and you'll be fine. Do a search on the stuff needed to gain s-off here in the forums. Report back if you need more assistance
Sent from my T-Mobile myTouch using xda app-developers app
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.
Hi, guys! I'm new to modifying the Android OS, and have a question that I haven't been able to find the answer to, so I was hoping that some of you guys could shine some light on my situation. I have a HTC One Max (T6#UL), running 4.4.2 with HTC SDK API level 6.20 (If that's relevant), that I received from work. When I boot it into the Bootloader, it says that the Bootloader is locked, and S is-Off. What I want to do is root it, and install a new ROM, but I'm confused on what exactly to do in this case. I've read that because S is Off, this overrules unlocking, and I can go ahead and install custom recovery (TWRP) now. Is this the case? Do I have to FDR before doing it? What is the best method to go about this? Please let me know if you need any phone/bootloader info.
Thanks for reading, any help is greatly appreciated!
Laurenozzo said:
Hi, guys! I'm new to modifying the Android OS, and have a question that I haven't been able to find the answer to, so I was hoping that some of you guys could shine some light on my situation. I have a HTC One Max (T6#UL), running 4.4.2 with HTC SDK API level 6.20 (If that's relevant), that I received from work. When I boot it into the Bootloader, it says that the Bootloader is locked, and S is-Off. What I want to do is root it, and install a new ROM, but I'm confused on what exactly to do in this case. I've read that because S is Off, this overrules unlocking, and I can go ahead and install custom recovery (TWRP) now. Is this the case? Do I have to FDR before doing it? What is the best method to go about this? Please let me know if you need any phone/bootloader info.
Thanks for reading, any help is greatly appreciated!
Click to expand...
Click to collapse
I would because as you will find out you can't simply flash twrp as is now. You need an ruu mode version of twrp to flash instead of flashing normally.
dottat said:
I would because as you will find out you can't simply flash twrp as is now. You need an ruu mode version of twrp to flash instead of flashing normally.
Click to expand...
Click to collapse
Okay, thank you, Dottad! This helps a lot.
Sent from my HTC One max using Tapatalk
If you are "Locked" and "S-OFF", that likely means somebody locked it afterwards to use the fingerprint sensor, since that requires a locked bootloader.
What you need now is to go to the bootloader and execute a couple of specific commands.
I believe the specific thread here has the instructions.
I actually did this once to try the fingerprint sensor. Had to figure out the hard way that "fastboot oem unlock" doesn't work after you S-OFF.
After you unlock, you don't need anything else. You can just flash TWRP normally via fastboot.