Related
As I said I am thinking about getting this phone but I am worried after reading around that doing the whole htcdev token thing for opening it up for root voids your warranty. So my questions are...
1. Can it be reversed?
2. Can tmobile tell too? Even if it can be reversed?
3. Has anyone tried to see if this works http://forum.xda-developers.com/showthread.php?t=1578908
4. Does htcdev get you s-off?
5. What is s-off?
Sent from my NexusHD2 using XDA
1. Yes and no. The bootloader can be re-locked, but as with all HTC devices, once you've unlocked it, there's signs that you did. Mine says *TAMPERED* for example once I rooted it. I don't think that'll ever go back.
2. T-Mo can tell if you bring it into the store. It doesnt take much work. All they gotta do is load the bootloader.
3. I have no idea, but my guess is that the end-result is the same as #1. The method you've linked in no way hints at being "secretive" about the unlock. I'd also not recommend you use it, since it's not necessarily a tried and true way. Following HTCdev.com's process IS however a tried and true way. I mean -- why NOT use the official HTC route?
4. No, HTCdev does NOT get you S-OFF. I have no idea what does, but you can still load CWM recovery, root, and load ROMs with S-ON anyways. Only reason you need S-OFF is if you start messing with paritions, which I wouldn't recommend unless you know what youre doing and are prepared to accept the consequences.
5. S-OFF lets you mess with partitions as far as I can tell. It may do more, but I'm not sure. I'm brand new to HTC phones (my first phone was a Nexus S).
Keep in mind with all of this, that your worries about unlocking are pretty much useless. Keep in mind -- if you're needing to send your phone in for warranty repair, you're 99% likely sending it in for HARDWARE repair. HTC and other mfr's (Samsung too) generally will honor your warranty if the cause is obvious (vol button breaks, capacitive buttons break, etc).
And if you're unlocking your phone, chances are any software problems you have are going to be taken care of by YOU anyways. Keep that in mind.
Cheers, and happy flashing!
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.
so a while back i tried flashing scverhagen's CM9.1, i think around rc8 or 9. i flashed it like 9 times each time never booting, not even to splash if i remember correctly. i tried different kernels, different gapps, different recoveries. i used blue6IX's superwipes, fastboot erase system -w, wiping everything in recovery. checked MD5sum, nothing would work! but each and every other rom i have flashed to this phone has never had an issue, at least a dozen different ones, not a single issue
(oh and im not a noob)
so my phones been down for a month due to a flexcable gone bad and the supplier i choose sent me a defective cable twice (off topic) and today got the new one and said, huh, ill flash CM9.1 R11. this time it boot, stayed on splash for a half hour but booted. normally would have grabbed a logcat here but the lady was on my computer and i was too lazy to go upstairs.
So again, i tried three different TWRP recoveries, 2 CWM recoveries and almost through my phone against the wall.
So yeah nothing worked, flashed another rom, worked fine. I flashed the latest TWRP again and noticed in its logs that cache and data refused to mount (didnt notice this earlier but wasnt really looking) so i flashed another ROM and got the same errors but it booted fine. Checked in ADB shell and no bad blocks found, used ADB to format cache and data, booted back to recovery and tried to flash CM9 again. nothing
now i said ok time to flash bootloader again (im jbear s-off) so i flashed the 1.45.1313 hboot from fastboot, rebooted into recovery (latest CWM by SilverL and what do you know it boots... in like 30 seconds too...
so my question is why? if anyone bothered to read all this that is, why? partitions should have all been fine, same method of flashing as always, not a single thing different, could my bootloader have been corrupt overtime? i mean i flashed the same one over the same one, and i never had an issue other then previously mentioned?
ok i dont know if i expect anyone to answer this, just frustrating when i cant understand something. like it should be simple and obvious right?
...so disappointed cant even enjoy my ROM
Hmmmmm. A corrupted bootloader? How odd that you would come to that conclusion because that's the only thing I could come up with myself. Only mine was a bit different and evidently more deadly a situation.
As you know I've been doing some ports for our phone lately and in the process you go thru many scenarios that just won't boot. No way back to square one without pulling the battery and going back to recovery for a different flash thru Hboot. After working thru 18 or 20 ROMs and probably a couple of hundred flash attempts over time I hit another hangup. I pulled the battery....waited about 15 seconds, reinserted it & proceed to go back to recovery for a reboot of a different setup. Hboot came back up fine like always, volume buttoned down one to recovery & hit the power button to take me there. My phone just sat there for about 10 seconds which scared me in itself because you KNOW that's only about a ONE second operation. Then she went dark as if I'd hit the "power off" selection by accident when I KNEW I didn't. I pulled the battery once again and reinserted it, volume down & power button to bring it back up .....and NOTHING.
That's when I noticed the only response I was getting was the pale red trackpad "light of death". After I quit freaking out enough, I went into System Devices in Windows to see how it was reading my phone and I had the QHSUSB_DLOAD "Screw You" device showing. Needless to say, I now have a brand new DoubleShot which I'm still kind of babying at the time like you usually do after you've killed one. That was my SECOND meltdown. My first was the CWM 6.0.0.0 series of meltdowns that struck many of us.
The only logical thing I have come up with so far is that SOMEHOW my bootloader got corrupted and that's how whatever happened.....happened. That is unless you or someone else might have a better explaination.
SO......don't throw it against the wall, my friend. At least you're still using yours.
Wow, so you've hit that red light of death twice? Were you bear s off both times? Man that's terrible luck! Did you attempt the unbrick mod at all?
I wonder if these phones have the same issue that the g2 and glacier have (as this is just a glacier with a keyboard and nice camera where the made faulty emmcs that would randomly corrupt and leave you with an expensive paperwieght
Just checked mine out, its a MLL0M
Which of course doesn't mean much unless there is a bunch to compare with, if you want to check what you have boot to recovery and run adb shell
cat /proc/kmsg | grep 'mmc0:0001'
Running fastboot OEM check_emmc_mid it shows its made by Samsung, who by the way was the maker of the faulty emmc thrown in those others phones....
Eh, I'm sure its nothing but strange things happens with technology, I'm just one of those who like answers!
Sent from my Nexus 7 using xda premium
Thanks for the info Demkantor. I like answers too and just as soon as I have a few extra minutes I'll check that out and give you a much more complete response. (I've always said my parents should have named me Murphy, 'cause if ANYONE can mess something up .....it's ME)! LOL
demkantor said:
Wow, so you've hit that red light of death twice? Were you bear s off both times? Man that's terrible luck! Did you attempt the unbrick mod at all?
I wonder if these phones have the same issue that the g2 and glacier have (as this is just a glacier with a keyboard and nice camera where the made faulty emmcs that would randomly corrupt and leave you with an expensive paperwieght
Just checked mine out, its a MLL0M
Which of course doesn't mean much unless there is a bunch to compare with, if you want to check what you have boot to recovery and run adb shell
cat /proc/kmsg | grep 'mmc0:0001'
Running fastboot OEM check_emmc_mid it shows its made by Samsung, who by the way was the maker of the faulty emmc thrown in those others phones....
Eh, I'm sure its nothing but strange things happens with technology, I'm just one of those who like answers!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I get this readout for the first command string:
cat /proc/kmsg | grep 'mmc0:0001'
<6>[ 4.528226] mmcblk0: mmc0:0001 MLL00M 2.25 GiB
For the second, I get:
C:\>fastboot oem check_emmc_mid
... INFOManufacturer ID, MID=15
INFOeMMC should be Samsung
DANG! Not only do they never give us an upgrade they continued to let us use a booby-trapped phone that they know could well "go off" at any time.
Ya know, as well as this DS runs....with the support we've gotten I have no intentions of staying with HTC. Making a lesser phone but actually giving a damn would be a much better thing to say about them!
Well we got the same chip, but I wasn't saying this one is for sure prone to failure, just that Samsung made the chip that was faulty in the other phones, it was a different model number though
There's a lot of things about HTC that I just can't stand, I mean they make (or rather used to make) the phones I want and 99% of the build quality is there, but they refuse to support even their flagship phones, and then make an awesome phone like the double shot and hide it from the public.... I don't feel like going on about them right now, we all have read tons of threads with complaints about HTC
But I really am curious about why this ROM couldn't flash, and why flashing a new hboot seemed to fix it. Also why did to of your phones go bad, somewhat out of the blue? Do you still have them by chance? Want to run some tests?
Sent from my Nexus 7 using xda premium
OH....I misunderstood. They may have swapped out that lot for one that wasn't borked. OR....they could still be waiting on Samsung for an "OTR UPGRADE"! LOL
Yeah, that first one bit the dust on testing CWM 6.0.0.0 where partition tables got chewed up or at least that's the conclusion we came to anyway. I swapped that one with Tmo for a new one last July. Still under factory warranty.
The one that just died I had to mail back in to ASSurion for the replacement I just got. But it WAS out of the blue even though I've been doing ALOT of flashing. Nowhere NEAR the estimated limit though. Plus it crashed from the bootloader & not from or during a flash which is how I would assume it would do if it was the emmc.
demkantor said:
ok, i got a question...
Click to expand...
Click to collapse
Hey, demkantor, thanks for the link in xmc's thread.
My hair-pulling ROM was xmc wildchild22's JellyKang. By now, it's at the point that I am no longer interested in the ROM, but I am still interested in why it would not boot with the original kernel, but WOULD boot after flashing scverhagen's kernel from YOUR 9.1 hair-pulling ROM.
I'm a relative noob, so I did not think to check logs (wouldn't know how to interpret them, anyway), or flash another hboot, but I did a lot of searching, reading, and experimenting without getting any closer to an answer.
If you read my post in the JellyKang thread, you know I wiped till I was raw, tried different recoveries, both TWRP and CWM (not CWM 6.0.0.0, thank goodness), triple checked MD5, re-downloaded the MD5 file, just in case...
None of it helped.
It looks like HBOOT may be the problem in my case too. Each phone has a different HBOOT version. I never intentionally flashed hboot on either phone. I can't really remember if that was part of the rooting process. (see HBOOT, below)
It sounds like you have some ideas. Fire away! I've been keeping both phones near me for a while. My wife got fed up with her phone "going missing" all the time, and went back to her previous phone, the G2, until, as she puts it, I "get over it."
Anyway, it feels good that I am not alone in my curiosity--many nights I would yell out "WHY?!" LOL
WeekendsR2Short said:
I get this readout for the first command string:
cat /proc/kmsg | grep 'mmc0:0001'
<6>[ 4.528226] mmcblk0: mmc0:0001 MLL00M 2.25 GiB
For the second, I get:
C:\>fastboot oem check_emmc_mid
...
INFOManufacturer ID, MID=15
INFOeMMC should be Samsung
...
Click to expand...
Click to collapse
I show almost exactly the same thing as you on both phones:
-- BLACK model DS --
cat /proc/kmsg | grep 'mmc0:0001'
<6>[ 2.581846] mmcblk0: mmc0:0001 MLL00M 2.25 GiB
fastboot oem check_emmc_mid
...
(bootloader) Manufacturer ID, MID=15
(bootloader) eMMC should be Samsung
-- TAN model DS --
cat /proc/kmsg | grep 'mmc0:0001'
<6>[ 1.927336] mmcblk0: mmc0:0001 MLL00M 2.25 GiB
fastboot oem check_emmc_mid
...
(bootloader) Manufacturer ID, MID=15
(bootloader) eMMC should be Samsung
--- HBOOT ---
The only difference I've found between the phones, so far, are:
1. different model numbers (probably just the color)
2. different hboot -- TAN: HBOOT-1.45.0013; BLACK: HBOOT-1.44.1107
3. at the bootloader screen, the BLACK one says "Revolutionary" and the TAN one says "UNLOCKED" (I used the HTC boot unlocker on the tan one)
I'm enough of a noob that I wouldn't even have thought of comparing hboot versions if it hadn't been for demkantor's comments.
Like both of you, I keep railing against HTC to the point that even my dogs look at me funny. But, somehow, I keep buying their stuff. My son just got a Galaxy (I think it's the S2, but may be the S3--huge screen!) and it has some great stuff, but I'll stick to my doubleshot, thank you.
hmm, i think we should change them, if your willing jbear s-off is the way to go.
out of curiosity are you s-on or s-off on the .0013 phone
im under the impression there is s-on and s-off for that bootloader but the .1107 can only be s-off
demkantor said:
hmm, i think we should change them, if your willing jbear s-off is the way to go.
out of curiosity are you s-on or s-off on the .0013 phone
im under the impression there is s-on and s-off for that bootloader but the .1107 can only be s-off
Click to expand...
Click to collapse
Both are S-OFF using different methods (don't remember more, right now).
I'm, planning to flash a new hboot on the problem phone (the TAN one) to see if that's it, but I'm too sleepy to think clearly. That phone has the newer hboot, so I would think the other one should be the problem...
---------- Post added at 12:35 AM ---------- Previous post was at 12:24 AM ----------
WeekendsR2Short said:
... the pale red trackpad "light of death"...
Click to expand...
Click to collapse
OUCH!!!
WeekendsR2Short said:
... That was my SECOND meltdown....
Click to expand...
Click to collapse
DOUBLE OUCH!!!
And there I was, whining just cause I couldn't flash another ROM!
OT: I keep trying out the wealth of ROMs that have come our way recently (kid-in-a-candy-store syndrome), but keep going back to Black Dahlia as my DD--thanks.
wow...
so it happened to me a few weeks back, turned on my double shot and nothing.... then plugged it in thinking the battery may be dead. got the vibrations and blinking red led and constant off then on, off then on. tried a different battery charged via external charger, same. tried different pcs, different cables, different button combos, nothing...
said nuts to this and tossed it aside. tried again a week later... same event...
tried tonight after a week of sitting around with no battery, sim or sd card in, poped in battery and it works like day one.
powered of and poped in sim and sd, all is good.
tried a last_kmsg with nothing worthwhile. not sure if this device is doomed to fail, not sure the cause, its just random hardware faults really get on my nerves...
just venting yall...
So, my original doubleshot I got on launch ended up having a light under the keyboard die after a handful of months. Sent it back to HTC and they fixed the light, thankfully just the light and didn't mess with the memory or anything. I got it back with a working light and s-off.
Fast forward about the same amount of time again, and one night I have netflix running through the tv-out cable to the tv in the room. I wasn't paying it much mind as others were watching ... until it suddenly stopped.
Variety of batteries later that work fine in my other doubleshot to no effect. I haven't had the chance to look too far into it, but with the overclocking experiments I did with it smart money would be on a dead processor.
I ran it pretty consistently at 1.7, that's where it really did shine. As a power user directing every lick of performance I can muster into the timely execution of the tasks at hand ... the times I bumped it back down to 1.2 or 1.5 due to non-use were infrequent.
I also am the curious sort and wanted to see what it could do, really take it for a spin. I had it at some ridiculous levels of speed just to see.
It also happens to be sitting right here next to me. Well, both of them. Once I learned that development is so much easier with two target devices to work with, I at least had a 'back up'.
Now I have one working and one non, but I wouldn't try to file an insurance claim on something likely my own fault. Nevermind the fact that this very instance is what one of the big sticking points in relenting on blocking all handset owners categorically from access to doing that.
I may (probably) or may not have fried the processor, but either way the onus is on me to determine that first due to the way I used - and in part deliberately abused - the device.
Honestly, I am content with the doubleshot I have. From another developer here it's an original rev s-off device, in silver. I put my black backplate on it and a privacy screen protector so the face is solid, unbroken black (no logo) framed in silver. I still use it often for photography, and as a wireless bridge for my devices and printer.
Not much more anymore though i'm afraid. I half-moved into the S3, hated every minute of it despite some of the things I liked about it, then ended up in a note 2. The S3 prepped me for the size of the note 2. Ghastly as it is, it fits a utility purpose of my life so perfectly I can't not have it. Not really a subject for this neck of the woods.
i too have moved on from the doubleshot, well hardly ever used it really, it was the ol ladies and just got it for her being she always wanted a phone with an awesome camera.
she then got the nexus four from me and i stole the doubleshot back. after craking the screen on her n4 i decided to commandeer that and got her a lumia 720 (finally realized android isnt for everyone no matter how much i want it to be)
well she broke that too... ugg... another 100 some dollars later shes back to being happier than ever with her windows phone... oh well.... back to subject
so wifi is not working, three roms and a thousand wipes later still no good. i think i have some serious hardware faults here... damn
also noticed that my bootloader has very few fastboot commands available, just these:
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) checkSbl1
(bootloader) checkHWSecurity
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) gotohboot
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) readpid
(bootloader) writepid
(bootloader) readcid
(bootloader) writecid
(bootloader) readimei
(bootloader) writeimei
(bootloader) readsecureflag
(bootloader) writesecureflag
(bootloader) lock
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) load_modem_emmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
finished. total time: 0.013s
OKAY [ 0.043s]
finished. total time: 0.045s
besides the usual, means no bad block tests etc... damn bootloader...
@Blue6IX , being you have rev-soff and i jbear, mind doing a quick test
fastboot oem ?
is your list of available commands larger or different?
anyway maybe ill grab a new board, oh and can you see what emmc and processor you have?
mine is
MLL00M
version-microp: 0353
just looking for some comparisons here, thanks!
I don't have to check, because I already know they are the same.
We didn't get an engineering bootloader, but what we did get (due to some brave exploring by someone here) is the ability to flash the sensation engineering bootloader for the commands you are looking for.
I forget which thread it was in but the answer is here if that is what you need.
Edit:
Booted to bootloader menu, looking at 0353 as well on microprocessor. Not that it matters but i'm running the 1.44.0007 hboot.
Thanks, I may look into stealing that engineering bootloader as I prefer having full debuuging tools handy with fastboot.
I know some of the microprocessors carried on the nexus1 and some had issues so was just curious as my phone seems to have issues what others have.
There's been a few unexplained bricks in these threads so I'm just looking to see if different variants had different issues
But yeah thanks for checking!
Sent from my Nexus 4 using xda premium
Hello I was wondering if there was a way to secure an Android device after unlocking it and installing a custom rom, maybe somebody has a thread or something.
Theoretically speaking anybody can take the device and do whatever he wants with fastboot or twrp.
Relocking it can have unforeseen consequences as some here have learned. I may be incorrect (depends on the variant too) as I don't root but the more you do, the more can go wrong.
I don't screen lock my device or encrypt my data because I don't want to be locked out, ever.
Physical possession is the only real security, relocking it isn't needed or desirable.
Anyone that tries to take my device is headed to the hurt locker. Consequences.
@fdor
Once an Android device's bootloader got unlocked ( disabling AVB included ) the device's Android is vulnerable.
blackhawk said:
Relocking it can have unforeseen consequences as some here have learned. I may be incorrect (depends on the variant too) as I don't root but the more you do, the more can go wrong.
I don't screen lock my device or encrypt my data because I don't want to be locked out, ever.
Physical possession is the only real security, relocking it isn't needed or desirable.
Anyone that tries to take my device is headed to the hurt locker. Consequences.
Click to expand...
Click to collapse
Thanks for the information, could you elaborate on screen locking? or link a thread I'm not sure what you speak of.
fdor said:
Thanks for the information, could you elaborate on screen locking? or link a thread I'm not sure what you speak of.
Click to expand...
Click to collapse
That's a separate subject but the concept is they same. Anything you lock especially will a password, you can get locked out yourself. Many times through no fault of your own as in a hardware failure.
An unlocked boot loader is a security risk... a bricked device much less so
On a stock Android Pie or higher (even not updated) security isn't an issue unless you do something stupid.
One reason I don't root.
Anytime you load unofficial firmware you're talking a risk plus it's distribution volume is much lower so if any malware is present it doesn't have as much exposure. Meaning it's likely to take longer to be detected.
If I lose my phone or it gets stolen how secure is my pin protected data with an unlocked bootloader as opposed to a locked bootloader?
Pretty sure you have to wipe all to get rid of a pin, so I would say it is almost the same.
Connorsdad said:
If I lose my phone or it gets stolen how secure is my pin protected data with an unlocked bootloader as opposed to a locked bootloader?
Click to expand...
Click to collapse
There are two schools of thought on locked vs. unlocked bootloader security (both which I quote below) that I saw discussed a while back on the subject. It may not directly speak on pin protecting your data -- they discuss some on how your device is encrypted behind your pin so even if stolen, it should still be secure (enough) -- but at the very least there are ways around EFS so your device might still be of some use and/or, maybe given enough time you never know what can happen; which is discussed a bit in the quote & discussion (in the thread they do it in) below...
You could click on either posts (they are made in the same thread) to follow the discussion more (they go on for a bit, but not to too much more of a degree)...
96carboard said:
Everything will work perfectly with an unlocked bootloader. It will just give you an annoying warning screen briefly when powering on.
If you want to know about security risks, they're fairly small, and ONLY apply if your phone is handled physically by someone untrusted for an extended period of time, in which the only thing they could actually do is install a modified boot image. Under those circumstances, the device security has to be assumed compromised whether the bootloader is unlocked or not.
An unlocked bootloader will NOT allow a 3rd party to access data on the device, since it is encrypted and requires your security code to unlock.
Now, you can actually tell if they've rebooted the device, which they would HAVE to do in order to install a different boot image; the unlock screen (which they are NOT able to modify without resulting in boot failure) will tell you!
And I absolutely disagree that it is shortsighted to advise immediate unlocking. Nothing of real benefit comes from having a locked bootloader. Any sense of security you gain from it is smoke and mirrors. It can only be tampered with if someone has physical access, and if somebody has physical access, it has to be assumed compromised regardless of whether it is unlocked or not. If anything, your security is improved because it is now on your mind that it could potentially be tampered with, and you are reminded of it with the id10t warning every time it reboots.
Click to expand...
Click to collapse
bobby janow said:
Everything will not work perfectly. Let's be honest here. Look it up, some banking apps work mine doesn't. Pay will work one day and not the next. And if your bank finds out your account was hacked and your phone is unlocked and/or bypasses bank security protocols who will pay for the missing funds when they find out?
A missing device can be booted into a custom recovery and adb commands will be available to take everything on your device bypassing any security you have. With a locked bootloader that is not possible. So if you know your phone can be compromised you feel more secure? That is ludicrous and really doesn't make sense. I mean talk about smoke and mirrors.
Now that being said there are a lot of folks in your camp that say you're living a pipe dream if you think the phone is more easily hacked or info stolen. I understand that argument entirely and it's possibly correct to a certain degree. But to summarily say immediately unlock your bootloader if you don't plan on rooting because.. well just in case, is really disingenuous to a great many individuals. At the very least look up some articles on why to keep your bootloader locked, especially for someone that hasn't done it in some time, if ever. The beauty of Android is the possibility if you so desire. Just be conscience of the advice you give. Many years ago Chainfire said in his blog that if you have an unlocked bootloader and have financial apps on your device you're asking for trouble and you might want to rethink that. (not in so many words) That weekend I locked my bootloader and never looked back. I haven't missed anything.. well other than flashing MVK kernel for my 6a. ;-) But then I'd need root and that brings a host of other issues.
Click to expand...
Click to collapse