Just saw that the bootloader is locked on the Transformer! Is there anyway to unlock this? I would love the ability to be able to dual boot another linux distro on this tablet... but it seems like those dreams may be crushed
as far as i understand it is still unclear whether the bootloader is to be locked or not. even the official sources seem to contradict each other.
ontoptherock said:
Just saw that the bootloader is locked on the Transformer! Is there anyway to unlock this? I would love the ability to be able to dual boot another linux distro on this tablet... but it seems like those dreams may be crushed
Click to expand...
Click to collapse
even then, it's highly unlikely you'll be able to dual boot another OS, well, atl least one in a useable state.
maybe so, but wouldnt mind trying... thats the fun of new toys!
We mostly suspect it isn't locked, we just don't have the right nvflash available at the moment.
i guess we will find out soon enough...
im already rooted and i have as of now hd rev rom.
But why is it that my hboot remains 1.17.0008?
whats the use of hboot by the way?
and how can i upgrade it to 1.17.1011?
do i have to upgrade or it is ok to stay in .0008?
sory for this questions
tnx guys
Woah, double post here.
Why are you worried about the bootloader? Why would it matter in your everyday use what version you have? To answer your question, the bootloader basically starts that rest of the system. Checks to make sure files are intact. It's like the first thing that fires up when you turn on your phone. That and the radio. They check each other out. Make sure everything is legit and then the bootloader tells the phone what to load, the priority, and confirms that it did load. No it's okay that you still have 008. The higher bootloader number (.011) really won't effect you at all cuz you aren't devving. Even then it really wouldn't. You are in good shape. Nothing to worry about.
smoochiezz24 said:
Why are you worried about the bootloader? Why would it matter in your everyday use what version you have? To answer your question, the bootloader basically starts that rest of the system. Checks to make sure files are intact. It's like the first thing that fires up when you turn on your phone. That and the radio. They check each other out. Make sure everything is legit and then the bootloader tells the phone what to load, the priority, and confirms that it did load. No it's okay that you still have 008. The higher bootloader number (.011) really won't effect you at all cuz you aren't devving. Even then it really wouldn't. You are in good shape. Nothing to worry about.
Click to expand...
Click to collapse
Hahaa, seems that a lot of new users are worried about it. Saying that their bootloaders are not the newest one and it's causing overhheating problems and such.
i see, so maybe ill stick with it.
ty guys
I used the jellybean RUU from HTC after relocking my bootloader, and now it won't "turn on." When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing. Any help appreciated.
I'm guessing you were SuperCID, and S-on? If so, sorry to say you are now bricked.
Should have read this, stickied to the top of General: http://forum.xda-developers.com/showthread.php?t=2181929
Wow. The level of suck here is amazing. Thanks. Nothing that can be done at all?
Jonathan_A said:
When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing.
Click to expand...
Click to collapse
Does the phone power on at all? Its not clear when you say "power it on" whether you are talking about the phone or the computer.
Any charge LED when the phone is plugged to USB or the wall charger?
Any message about QHSUSB_DLOAD drivers popup on the computer when you connect the phone by USB? If you get this, and no charge LED, you are bricked.
redpoint73 said:
Does the phone power on at all? Its not clear when you say "power it on" whether you are talking about the phone or the computer.
Any charge LED when the phone is plugged to USB or the wall charger?
Any message about QHSUSB_DLOAD drivers popup on the computer when you connect the phone by USB? If you get this, and no charge LED, you are bricked.
Click to expand...
Click to collapse
I meant the phone, when I power the phone on, I hear the device connect sound through the computer. No charge LED, but I do get the QHSUSB_DLOAD in device manager. So crap . Thanks for your help (not sarcasm). Level of stupidity/annoyance that I'm feeling right now is OVER NINE THOUSAND. Can't believe I missed a sticky. Thanks a million for the informative thread there though, I'll never use an RUU again, bet your bottom dollar.
Jonathan_A said:
I meant the phone, when I power the phone on, I hear the device connect sound through the computer. No charge LED, but I do get the QHSUSB_DLOAD in device manager. So crap . Thanks for your help (not sarcasm). Level of stupidity/annoyance that I'm feeling right now is OVER NINE THOUSAND. Can't believe I missed a sticky. Thanks a million for the informative thread there though, I'll never use an RUU again, bet your bottom dollar.
Click to expand...
Click to collapse
Some people have resurrected their phones from this using the JET tool. Failing that, it's fixable via jtag, though it wil set you back about $100.
Everyone makes stupid mistakes once in a while. But yeah, that really sucks. If you have access to a Linux computer, you might try the JET tool in Development, or check the unbricking thread in General. But I don't think anyone has been able to come back from this after the 3.18 RUU or OTA + SuperCID.
Beyond that, you can try to find a repair shop that will JTAG the phone. It will cost you, but better than buying a new phone.
iElvis said:
Some people have resurrected their phones from this using the JET tool. Failing that, it's fixable via jtag, though it wil set you back about $100.
Click to expand...
Click to collapse
Well, it's still under warranty, and I'm hoping that since the bootloader was relocked and the RUU technically succeeded, they'll just send me a new one or something. Though I'll take a whack at the JET thing if I can find my Linux live CD... Thanks a ton, I'm feeling pretty dumb here and you guys have been really helpful.
Jonathan_A said:
I'll never use an RUU again, bet your bottom dollar.
Click to expand...
Click to collapse
RUU is usually a safe thing to do (typically its a good tool for recovering from all sorts of issues). It really shouldn't cause a brick, and nobody is really sure why it does in this case. So really, its kind of an honest mistake. Its folks that OTA while rooted, etc. without doing any reading that I kinda wonder about.
redpoint73 said:
RUU is usually a safe thing to do (typically its a good tool for recovering from all sorts of issues). It really shouldn't cause a brick, and nobody is really sure why it does in this case. So really, its kind of an honest mistake. Its folks that OTA while rooted, etc. without doing any reading that I kinda wonder about.
Click to expand...
Click to collapse
Ah well, thanks for making me feel less stupid I guess I meant that I'll do some checking before I RUU again, heh.
Jonathan_A said:
Ah well, thanks for making me feel less stupid I guess I meant that I'll do some checking before I RUU again, heh.
Click to expand...
Click to collapse
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
exad said:
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
Click to expand...
Click to collapse
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Jonathan_A said:
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Click to expand...
Click to collapse
Good luck bud!
Sent from my HTC One X using xda app-developers app
Jonathan_A said:
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Click to expand...
Click to collapse
HTC will give you some grief. AT&T doesn't appear to care and from what I have seen has happily replaced lots of bricked phones without being concerned about relocking.
iElvis said:
HTC will give you some grief. AT&T doesn't appear to care and from what I have seen has happily replaced lots of bricked phones without being concerned about relocking.
Click to expand...
Click to collapse
Ooh, thanks. Good to know. They'll be my next try. You all have probably just saved me ~$300
Jonathan_A said:
I used the jellybean RUU from HTC after relocking my bootloader, and now it won't "turn on." When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing. Any help appreciated.
Click to expand...
Click to collapse
Happened to me too :c Has anyone had any luck using JET?
If the emmc partition table is still intact its feasible, but im pretty sure the ruu/ota kills it upon install. who knows why. seems to be a security "feature" since s-off seems to work fine.
Just called AT&T, they're sending me the replacement and then I send this one back in the box that the replacement came in and then the replacement is free. They said that they basically can't do anything with the dead one since it's dead, so I think all's well that ends well? Updates as events warrant, if need be. Thanks so much Redpoint73, iElvis, and exad.
I had a similar issue where my screen wouldn't turn on but it was still on and usable. I went to the AT&T store and got a replacement. Tell them you installed the AT&T update and then the screen stopped working. They probably won't be able to fix it but they'll give ya a new phone if you're under warranty. My phone was far from stock (rooted, bootloader unlocked, S-off, custom kernel and ROM), and they still gave me a new one. Make sure you go to an AT&T store though, I tried three different Best Buys and they were all noobs that had no idea what to do.
Edit: Didn't read post above so you can disregard this. But if you go to a store they can give you a new one on the spot instead of having to wait for one to be shipped to you.
Jonathan_A said:
Just called AT&T, they're sending me the replacement and then I send this one back in the box that the replacement came in and then the replacement is free. They said that they basically can't do anything with the dead one since it's dead, so I think all's well that ends well? Updates as events warrant, if need be. Thanks so much Redpoint73, iElvis, and exad.
Click to expand...
Click to collapse
Since the phone is bricked, there is really no way of them knowing (by checking the phone anyway) that you modded it. And as mentioned, AFAIK there has never been a reported case of AT&T denying warranty service due to the bootloader having been unlocked (and probably aren't even going to check). AT&T is much less strict then HTC, as its in AT&T self interest to keep you as a happy customer (paying that big old monthly bill), rather then fight over something like a single warranty exchange.
There have been some cases of the OTA randomly bricking devices that are fully stock (and probably possible with the RUU as well). Any time you mess with the hboot, if things get interrupted somehow, its possible to brick the phone. So for all AT&T knows, this is what happened in your case.
I'm normally not a big fan of making a warranty claim for your own negligence, and as a result of you modding the phone. But I suppose this is a bit of a gray area, since the RUU really shouldn't brick the phone solely due to SuperCID.
---------- Post added at 10:04 AM ---------- Previous post was at 09:58 AM ----------
exad said:
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
Click to expand...
Click to collapse
Did HTC actually deny your warranty service due to a record of you having unlocked the bootloader? Just curious, because it would be the first I have heard of that actually happening.
Yes, as the warning state when you unlock the bootloader, it voids the warranty (at least in theory). But in actual practice, whether they honor the warranty or not after BL unlock seems to be much more of a gray area.
Its true that the carrier will be more lenient than HTC. But I know there was some discussion on the "international" (quad core) One X forum, where HTC was actually honoring the warranty if the bootloader was unlocked. But they were actually denying warranty service if any custom ROM had ever been installed on the device. Even if the device was returned to the stock ROM before sending in. So apparently, they have some way of knowing a custom ROM was previously installed (even if uninstalled). If the phone was bricked, I wonder if they would still be able to check this?
Of course, how HTC honors the warranty may also vary from region to region.
I first unlocked my google pixel (Verizon) bootloader, i then went on to try to root it. This went on to go into a boot loop. Me being dumb, forgot that you can just flash the stock firmware. I locked the bootloader. Now im stuck, when i try to boot it gives me the "Your device is corrupt" screen and it goes to the white battery display. I try to reinstall stock firmware and it says i need an unlocked bootloader. In order for me to unlock the bootloader i need usb debugging enabled. I can't get into the phone to enable it so im at a stuck point... I really would appreciate some help. I have extended warranty if Verizon can do anything with that.
Unfortunately, the instructions were pretty clear to not relock the bootloader unless the phone was 100% stock. From what I've seen, you are stuck. Haven't heard anyone recovering from relocking the bootloader with a bad install.
You made the decision to void your warranty when you unlocked the bootloader, so Verizon owes you nothing (extended warranty or not). That being said, they may replace it if you "played dumb" and said it happened during an update, but that poses an ethical quandary. So it's up to you how to proceed.
thanks for the reply
stranula said:
Unfortunately, the instructions were pretty clear to not relock the bootloader unless the phone was 100% stock. From what I've seen, you are stuck. Haven't heard anyone recovering from relocking the bootloader with a bad install.
You made the decision to void your warranty when you unlocked the bootloader, so Verizon owes you nothing (extended warranty or not). That being said, they may replace it if you "played dumb" and said it happened during an update, but that poses an ethical quandary. So it's up to you how to proceed.
Click to expand...
Click to collapse
Thanks a ton, yeah gonna try that "playing dumb" tactic today, was thinking the same thing... lets hope it works.
This is why providers lock bootloaders. Passing the cost to them instead of owning up to your screw up. Im sorry you bricked your device but that cost should be on you not verizon.
Sent from my Pixel using Tapatalk
jbjancuski said:
Thanks a ton, yeah gonna try that "playing dumb" tactic today, was thinking the same thing... lets hope it works.
Click to expand...
Click to collapse
For your sake, I hope it works. But, as I said, this is ethically questionable (on a personal level) and wrong on a grander level. You took responsibility when you unlocked the bootloader. If you are fortunate and Verizon gives you a new one. Either leave it stock, or read more thoroughly before making changes to your phone.
maulich said:
This is why providers lock bootloaders. Passing the cost to them instead of owning up to your screw up. Im sorry you bricked your device but that cost should be on you not verizon.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Unfortunately, this is absolutely the case. When we make the decision to do things to our phones that operators don't want us doing, we are accepting responsibility for the phone, and if we brick it we should deal with that consequence. But of course, some people aren't really prepared for this reality, and want someone else to get them out of it.
Agreed.......i have had to pay the piper before for my screw ups. Even a brand new device of my wifes that i was trying to get twrp on. Phone was less than 6 hours old and rendered a paper weight. Expensive lessons are a part of life.........The sad thing is verizon will get a ton of these returned for this very thing, and it will only force them to lock down the bootloader even better hurting the individuals who want a little freedom for a better price.
Sent from my Pixel using Tapatalk
Has anyone found away we can get rid of the bootloader unlocked warning? If not what's stopping people from finding out how to fix it?
Well, the Pixel has new partitions. That's about it from what I can tell.
Sadly it was already impossible with the Nexus 5X, so I would not be suprised if the same would be with Pixel. :'(
Tapatalkkal küldve az én Pixel eszközömről
I kind of like the warning. It reminds me that nothing has changed with my BL since unlocking.
zalcsooo said:
Sadly it was already impossible with the Nexus 5X, so I would not be suprised if the same would be with Pixel. :'(
Tapatalkkal küldve az én Pixel eszközömről
Click to expand...
Click to collapse
Apparently, this guy was able to change it on the 5x.
http://forum.xda-developers.com/showpost.php?p=63826602&postcount=7
mrZoSo said:
Apparently, this guy was able to change it on the 5x.
http://forum.xda-developers.com/showpost.php?p=63826602&postcount=7
Click to expand...
Click to collapse
Without reading throught that thread again, I just remembered that I was able to change the imgdata and get rid of the warning screen, but only with an older version bootloader, not the latest one. It was more like a workaround than a real "hack". (But I donno what I am talkin about when the imgdata change is also just a workaround xD)
Sent fron my Pixel
zalcsooo said:
Without reading throught that thread again, I just remembered that I was able to change the imgdata and get rid of the warning screen, but only with an older version bootloader, not the latest one. It was more like a workaround than a real "hack". (But I donno what I am talkin about when the imgdata change is also just a workaround xD)
Sent fron my Pixel
Click to expand...
Click to collapse
LOL, it's all good.
If it gets figured out, that would be nice. But as it is, I can live with it. You don't see it that often to begin with,, heh
I hope someone figures this out. I sold our MXP's after getting Pixels and it was pretty easy to change on that phone. The one downfall was in re-locking it to sale it. When I flashed it to full stock and re-locked the warning came back due to a flag being set to 2 (re-locked) instead of 1 (locked). I could still fastboot flash an image to replace it (even with a locked bootloader) but I have a feeling it's going to come back the first time the phone receives and OTA.
A little off topic, but I hope someone figures it out for this phone.
Sent from my Pixel using Tapatalk
Why is it something that needs to be fixed??
aholeinthewor1d said:
Why is it something that needs to be fixed??
Click to expand...
Click to collapse
Some people just don't like so see it. And they buy Android for the customization
I'm sure the reason that they lock this out is so that someone can't remotely unlock the bootloader and then replace the boot image somehow via malware. Not to say that I love it, but it's a nice little thing to have for people who may not recognize a hack otherwise. Not that I really think there is likely to be malware that advanced for this phone but I suppose it is theoretically possible
Shiftydogit said:
Has anyone found away we can get rid of the bootloader unlocked warning? If not what's stopping people from finding out how to fix it?
Click to expand...
Click to collapse
Not sure, but I know a lot of people are looking into it.
I've looked into the pixel's partitions and there is a litteral crap load I've been trying to see if I could get CM14 running now with CM dead and moving to LineageOS and this phone being really hard to figure out I'm not surprised the partitions are an issue and please note I'm trying to port CM to be the first custom ROM out it's just to see how the phone works and what info I can learn yet to no avail so remember it's a personal "play around" project
If they can't handle a couple seconds when booting then they can always link their bootloader again.