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
Related
I've got to give one of the units back and need to decide which.
Since it's possible to flash CW recovery using ODIN both locked/unlocked bootloader devices, is there a benefit to having an "unlocked" bootloader?
I've been able to flash both locked/unlocked as well install Kernels..
I understand, nvflash can't be used on locked bootloader units.. but it seems (from what I understand and have read via searching), most everything can be accomplished via ODIN + CW.
Thanks!
scmguru said:
I've got to give one of the units back and need to decide which.
Since it's possible to flash CW recovery using ODIN both locked/unlocked bootloader devices, is there a benefit to having an "unlocked" bootloader?
I've been able to flash both locked/unlocked as well install Kernels..
I understand, nvflash can't be used on locked bootloader units.. but it seems (from what I understand and have read via searching), most everything can be accomplished via ODIN + CW.
Thanks!
Click to expand...
Click to collapse
Lock vs unlock means that if you are unlock you can flash kernels made for ubuntu and other linux distro. Locked bootloaders are generally limited to the samsung kernel so it would be harder to flash other things and make some serious mods that would require nvflash.
Thanks for the reply. Will keep unlocked. Cheers.
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!
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 ^^
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.
I'm finding a very unusual lack of info about those backup bootloaders, considering that flashing over the primary bootloader partition is one of the most usual reasons for people to brick, and the secondary bootloader can be used in some of those devices to just fix the phone in seconds..
On N4, the secondary bootloader only works with Qualcomm fast-download mode, but in the N5 the secondary bootloader is a fully-functional bootloader for fastboot that stays on the original bootloader version that came from the phone (in my case h10x), which literally makes you able to just zero the aboot sbl partitions and boot into the secondary bootloader and just flash a new bootloader and fix the stuff in matter of seconds.
I am not sure if on the newer Nexus there are also backup bootloaders (on N9 there are, don't know if fully functional for fastboot or no), but if there are and they're fastboot-functional, they're a HUGE deal.
Why there's like no info about this anywhere on XDA? Even trying to make a search here or over google for backup bootloaders brings veery small info about this, just isolated cases
I don't know if this belongs to a more technical forum or not
Really.. noone?
Is this a dead forum or wrong forum for this?