yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] -Michael_:
+2 UnRevoked your doing a hell of a job, 90% of us understand why the nand unlock has not been released, I want nand but i'm not willing to try what the op has suggested. Perhaps if I were building themes I might use this method for a faster testing procedure. Yet I dont belive it should have been posted here seems alot of new poeple lurking might unplug at the incorrect moment and create issues that would spur a whole bunch of "help me!!" threads.

What UnRevoked is doing is no different than me or anyone else running company server patches in a sandbox for a few weeks before I pushed it to all the servers. Test test test test THEN release!

No doubt HTC has already seen and disected their code. Do you think your the first to figure out how UnRevoked managed to flash the custom recovery? Why has no one else posted this? hmm..

Dont kill me with flames I'm just sayin.

Just my .02 cents
[Droid Incredible Android Development] :
Im trying to get into themeing, so that is why im a bit eager to try this but my two issues with this is

1) a bricked incredible

2) that im doing this, this is not.supporting unrevoled
[Droid Incredible Android Development] -Michael_:
do a forums search, symlink adfree and there is no need.....
[Droid Incredible Android Development] -Michael_:
I understand I do really just .. .. . . . careful. :)

Carefully post as well :)
[Droid Incredible Android Development] :
Im going to try this just to put an end to the whole should i do it or not mindset. I dont approve of it, i just want.to report back.
[Droid Incredible Android Development] jgrimberg1979:
i tried it and it works great i was about to mount the phone in r/w and push fonts to the system and it changed the default font instantly, i didnt have to go in recovery!! awesome!!!
[Droid Incredible Android Development] :
ok, it booted up, but metamorph doesnt work. This is a scchlep method in the true sense, but still good for who need it.

EDIT: metamorph works.
[Droid Incredible Android Development] MachString:
I tried it and the ad free worked, but I could not add or delete from the system directory.
[Droid Incredible Android Development] whiplash000:
Okay people, disclaimer: I am not an expert on bootloaders, embedded device development, or rooting, but I'm no noob to these things... just trying to make things clear.

First off, about HTC figuring out the method used to unlock. I'm fairly sure HTC doesn't hire reverse engineers to combat teams that root their phones (college degrees don't mean THAT much, there's plenty of "hackers" (hate using that word) out there who have FAR more skills than even the better college graduates). Speaking of unrevoked, I had a (he'll say not so) pleasant chat with one of their members who said there's a variety of obfuscation methods in both the code and the data sent over USB in order to make the exploit as difficult to guess as possible. Perhaps HTC will finally figure it out, but by the time they unravel the code that unrevoked released, the NAND-unlocking bootloader will be out and the whole thing will be moot for HTC as everyone moved on to the next step. Stall tactics.

As for this technique... I'd say it's fairly safe, just be sure to hit the correct window (READ: "Waiting for reboot...") or bad things will happen. Simple as that. If you're scared, move on, don't bother, and beg the OP to put a big warning in his post.

Oh, BTW I did this and it works just fine. Adfree updated perfectly. Thanks, TNS201!
[Droid Incredible Android Development] jgrimberg1979:
you still have to mount the system as r/w
[Droid Incredible Android Development] :
doesnt work for me
[Droid Incredible Android Development] Bear3825:
Guys, im a complete noob to the android system and i wont move unless unrevoked says its ok.
[Droid Incredible Android Development] whiplash000:
OP, you can calm a bunch of people down if you include some big warning on your post telling people that you should only do this if you know what you're doing.
[Droid Incredible Android Development] :
Wait for unrEVOked to release the official patched bootloader. Its not worth it. I have to say good job to op for finding this, but it is an on the fly type of thing. Its not something to be dependant on,

SO GOOD WORK OP!!!!!!!! THIS IS A GRRRRREAT FIND FOR SOME!

BuT EVERYONE AS A WHOLE, DO THE RIGHT THING. DONT DO THIS IF YOU are UNSURE. IT IS PRETTY MUCH USELESS TO HAVE FUL NAND UNLOCKED .AS I SAID BEFORE, THIS IS REALLY A WORKAROUND UNTIL NAND IS OFFICIALLY 100% UNLOCKED AND RELEASED BY UNREVOKED.
[Droid Incredible Android Development] Lexus One:
Just curious here. But how would you relock your NAND *if* for some reason somewhere down the road, it was necessary to be locked for some software package to function properly. Or let's just say you want to return to having your NAND locked, for whatever reason.

So, how would you relock it???
[Droid Incredible Android Development] :
Either reboot or run unrevoked3 again
[Droid Incredible Android Development] Lexus One:
You assume that the Unrevoked 3 app will not error out or time out when it attempts to unlock an already unlocked NAND flash. You also said rebooting would do the trick. I was not aware that just simply rebooting the phone would relock the NAND flash. If you are correct then my point is moot and I withdraw my question.
[Droid Incredible Android Development] nfcrockett:
SoCalMiles, we just need to ignore there ignorance.
[Droid Incredible Android Development] Bear3825:
Ive used unrevoked 3 and did the clockwork update using the same. The only reason i even want nand unlock is to get rid of bloat via uninstaller. Other than that all I wanna do is flash a Cricket rom and use their network. I got this phone only for that purpose. My hat is off to you devs that can do this right now. All i wanna do is learn from you all so i can do for myself instead of paying outrageous prices to people i dont know for what i can learn in a matter of days if given tje chance.
[Droid Incredible Android Development] MachString:
Mounted the system as r/w in root manger and just deleted some system apps while phone was on. Thanks OP & jgrimberg1979
[Droid Incredible Android Development] santana11981:
You guys need to stop acting like little girls....if you don't want to try it...just don't do it!!!!

Want a warning??? IF YOU FCUK UP...THEN YOU FCUKED IT UP. Stop blaming others and quit bashing eachother.

I try EVERYONES rom/theme/app....if I like it I post and try and help if I find problems. If i don't like it I just do a restore and enjoy the rest of my day.
[Droid Incredible Android Development] SoCalMiles:
Until you try that thing that isn't easily fixable through a restore...
[Droid Incredible Android Development] santana11981:
Of course....but like I said before if I don't want to try it....I don't. If i fcuk up my phone...then it's my fault.

Oh yea if the app/theme/Rom looks suspect....I don't waste my time.
[Droid Incredible Android Development] PaulG1488:
Can op or anyone else confirm that its safe to try this being rooted with the 720 ota?
[Droid Incredible Android Development] :
Idk about the update, as im running cm6 but it should be safe regardless
[Droid Incredible Android Development] adrynalyne:
Sure are a lot of skittish folk on a development forum....
[Droid Incredible Android Development] MachString:
I have the 720p ota and yea it worked, but as far as safe all I can say is I'm using my phone now.
[Droid Incredible Android Development] whiplash000:
Yeah, this thread is a little sad...

And I don't see how this undermines unrevoked's work. It's just a temporary workaround until unrevoked releases their patched bootloader... and people are screaming bloody murder! Sheesh...
[Droid Incredible Android Development] PaulG1488:
Cool thanks for the confirmation
[Droid Incredible Android Development] Shadowmite:
we never intended this to be done this way. specifically, this causes errors in the boot process which is why nand ends up unlocked. its poosible you will have strange errors leaving it unlocked in this manner. thats really about all i can add to this thread.

a simple reboot relocks it.
[Droid Incredible Android Development] adrynalyne:
Its not leaking their code, its not stealing their source, its just a workaround.

As for it being dangerous....really folks? If something like this scares you this much, you need to unroot your devices, hang your head, and leave your man card at the door. You clearly have no business messing with these devices if you don't know what is going on or what you are doing.

We need a care bear sub forum.
[Droid Incredible Android Development] trunksta:
Agreed. Sort of anyway.

Rooting and nand unlock are completely different so I can see why people are so hesitant to use this method. I've used it and had no problems but as it has been said it was never meant to be used this way and is only meant for experienced users.

Bottom line if your unsure, wait. If your willing to accept the risks go for it but its both better and safer to wait for the finished script from unrevoked. Can't be too much longer.
[Droid Incredible Android Development] Smabbage:
When Shadowmite speaks, I listen. Nuff said. :)
[Droid Incredible Android Development] dreamersipaq:
Calm Down

Guys, two things:

1) I'm sorry to say this, but if you don't like ADB, go back to WinMo or iPhone. Android is LINUX. linux REQUIRES some use of the shell.

2) I don't think this method will hurt anything. You heard Shadowmite himself say that you can rerun and rerun Reflash if it screws up and nothing will happen. That's the difference between Reflash, and the NAND unlock that they're still testing. A screwed up NAND unlock will brick your phone. Following that theory, if Reflash can bomb out at any time, and all you have to do is rerun it to finish, all you're doing is 'manually' bombin reflash so to speak.

3) I don't think that this does a dis-justice to the unrevoked team. This is just a work around. In my opinion, this is much better then when that douche bag posted the actual code a few weeks back w/o any obscuration for all to see. If anything, this is like a 'better' middle ground between having nand locked, and unlocked.

I've posted many times that I highly respect the unrevoked team, but calm down. I don't really think that there is a disjustice being made. It's not like the OP reverse engineered the tool, and posted the code here for all to see.

$.02 cents deposited.
[Droid Incredible Android Development] kentoe:
I just think that some people are hesitant because of the fact that you're dealing with a $500 piece of equipment here. Some want to go down the rabbit hole farther than others. You also have to take into consideration some of the people whom look at the forums and they're jumping the gun trying things like this who don't know any better.

When the reflash+root tool came out there were a lot of people who had no idea of what adb is and the like who had used the tool and they may come in here and think "hey, I can probably do this cool111!!1!1!" when, come to find out, they end up bricking their phone and can't figure out how to fix it.

That is the sort of thing that posting these shady workarounds isn't always good and waiting for the unrevoked team to post the official release is best.
[Droid Incredible Android Development] TNS201:
Is a workaround shady? If anything its shady to hold back information from the public. If someone screws their phone up because they don't know what they are doing, then that's a lesson learned. For more experienced people this information can help them.

Be smart and don't do things you don't know how to do. If you don't know how to use ADB, then you shouldn't be rooting in the first place. Hopefully people have insurance and if they make a mistake its only a $90 brick.
[Droid Incredible Android Development] bonzai299:
Although I agree that what you originally posted wasn't a horrible thing to do, now you are just making an ass out of yourself. Why would they release something to the general public (because that's what were talking about here, not just the people that know what they're doing) if they weren't completely sure it was harmless?

You don't see pharmaceutical companys releasing drugs without doing extensive research and testing, do you?

It's just asking for people of our community to get hurt, which is what we're trying to prevent.

Unrevoked will release things to us when they're ready.
[Droid Incredible Android Development] dreamersipaq:
See, now I was with you until this post. Unless I'm mis-understanding this post, let me say unrEVOked doesn't owe you anything. And if you want it faster then they decide to release it, figure it out yourself. Nuff said.

I applaud you for finding this out and posting this so we have something in the meantime, but now go sit down and don't be a douche. The only reason you even have this method is because unrEVOked decided to release the reflash tool.
[Droid Incredible Android Development] TNS201:
Yea they do research and testing. Then you hear may cause nausea, vomiting, diarrhea, temporary blindness, mental instability, rashes, etc.

Is a "Doing something to your phone might cause a brick disclaimer" really needed? People come here should know that doing such things to their phone can always go wrong. You take your chances. I wasn't necessarily referring to team unrevoked hiding things from the public, but others who have posted in this post and my other post about doing the OTA early seemed to got upset that I posted the information. I see no harm in it but they want to keep it hidden from public eyes. I mostly see this as the people who are complaining have some link to team unrevoked and want to see them get "credit" for work they do. Neither thing I posted takes away from credit of work they done, obviously people know I didn't write the program or involved in anyway or claim to be. I think they were mad about the early OTA thing because unrevoked was working on a way to get it out there without doing the few extra steps to get it on there and they were made because I put the information on how to do it out there.
[Droid Incredible Android Development] aaronjb:
Let's be candid and clear. Keeping the NAND unlock method and other methods obfuscated and private serves two purposes:

1) Assuring that the lag between discovering the exploit and the eventual patching of that exploit as long as possible;

2) Ensuring that Unvrevoked is the single source for such tools.

There are direct benefits to be had for the community for (1), and direct as well as indirect benefits to be had for Unrevoked members for (2).
[Droid Incredible Android Development] kentoe:
They aren't really holding back information from the public. They released a tool for us to use and the next part (NAND unlock/custom bootloader) will be released once the bugs are out and the chances for us to not get a bricked phone are lower. They didn't make the tool and are obligated to tell us how it works, they don't owe us anything for their dedication.

I agree with this statement sort of however, unfortunately, there are people who will go ahead and do this. This is why not having workarounds available are always the best.

+1 I think, little confused on the last part but essentially I agree.
[Droid Incredible Android Development] TNS201:
Well I look at it this way, sure people can F their phone up right now using this method, whats to stop them from from F-ing their phone up when/if they ever release the full nand unlock exploit. Either way you look at it, they can totally brick their phone doing things they shouldn't either route.

If people don't do things like flashing bin files, then doing this is totally safe. Any files deleted in system folders that were once not writable can simply be nandroid restored or the file messed up can be pushed.
[Droid Incredible Android Development] daftlush:
I agree with OP on this one. Thanks for the heads up.

Personally, who gives a frak about bricking a phone... any person with half a brain can go get another -although refurb- from verizon, as long as the H2O sticker is cool.

P.S. Is OP the guy who leaked the root/nand trick earlier... thinking he was doing the community a solid, when in fact it was a diservice. Because that guy was a real piece of ****e! No disrespect to OP if that wasn't you. But if it was, I hope you get nut AND prick cancer from your phone's radiation.
[Droid Incredible Android Development] pardonmyfreedom:
You're missing the point. You have no idea what it does. You didn't write this utility, so for you to claim that it's safe is ridiculous.

I'm not sure why you think it's being a "crybaby" to warn people that you're using a tool in an unintended manner and there's a risk to their phone. Especially when you didn't write it and you have no idea how it works.
[Droid Incredible Android Development] TNS201:
No I did not release that stuff. I did acquire it though when the guy did leak it. If people are smart and know how to use google, then it could easily be found.

I know I didn't write the utility. I seen the file leaked the other week along with the tutorial and commands entered. I am assuming this file that was leaked and commands used are part of the unrevoked method of unlocking the nand to write the recovery and the file leaked along with commands only gave you a temp nand unlock as well.

I have messed with this for several days before posting. From what I can see there is no issue here as long as someone doesnt do something stupid like flashing something to the phone like a boot or recovery or something else of that nature that can cause the phone to be bricked without a chance for recovery. As long as they can get into bootloader and recovery still, they should have no problems.
[Droid Incredible Android Development] kentoe:
THIS is exactly the problem. They didn't want that information out there because of this chance that's happenning.

Yes, we understand that you along with a good amount of us won't do this sort of thing and mess up our phones, however... The unrevoked team wants to create a dead simple way so that they minimize this sort of risk for everybody including the people who are extremely experienced and the people who root and attempt this with zero experience.

They/we don't want any "as long as" 's they/we want "this works, you can't f-it up"
[Droid Incredible Android Development] TNS201:
Why do you keep trying to make a point of this? When they release the full nand unlock, the risks will be the same if NOT GREATER to get a bricked phone.
[Droid Incredible Android Development] bonzai299:
can we just get this thread locked? this is completely pointless.
[Droid Incredible Android Development] rpearl:
Yes, once again: Since the exploit is widely visible and cached on Google, I can guarantee that it will be patched by the time the next OTA hits. And let's be clear: The NAND unlock that was leaked was entirely stolen. There was not even any "dev work" done, it was just unrevoked's work, straight up released. But at least he was "open", right? And published his "work".

There is a balance between being "open" and protecting what we've found. Sure, we'd love to be open with users. But we are currently in an arms race with the device manufacturers. HTC is getting very close to patching up all the easy root exploits. Each new phone is going to be harder and harder to root. It is sad that when this exploid rootshell exploit came out, the Droid X people were happy that there was an unpatched CVE in the Linux kernel. That shouldn't be something we are pleased about, it should be something we are worried about! We should be finding these vulnerabilities and patching them, not exploiting them.

But we can't. Not at the moment. Because there is no legitimate path to get root access on these phones. We have to hack them instead. Given the choice between sacrificing the liberty of running code on our handsets and the liberty of reading the code by which we unlock it, we feel that the millions of handsets are more important. It is unfortunate that we must make such a choice, and we look forward to the day in the future that no such decision need be made.

So as I step off my soapbox, please stop criticizing us for not being open.

And again, I'll repeat what Shadowmite said here. "we never intended this to be done this way. specifically, this causes errors in the boot process which is why nand ends up unlocked. its poosible you will have strange errors leaving it unlocked in this manner. thats really about all i can add to this thread."
[Droid Incredible Android Development] kentoe:
I've been referring to the process of nand unlock, not the after effects/abilities it enables you to do. The process in which full nand unlock takes place has caused bricked phones. Not the abilities once unlock is achieved, wherein that case, I agree - they are the same.

Agreed.
[Droid Incredible Android Development] yojoe600:
agreed as well this is becoming a mess
[Droid Incredible Android Development] TNS201:
It was fine until everyone had to come in here with an objection against it being posted and go way off topic.
[Droid Incredible Android Development] :
+1 i was skeptical at first, but i believe that this works, and doesnt brick phones.

So op, great work. This is a workaround, but it was meant to be a workaround. I respect TNS201 for this, and you should too.

I have stated this many times: do knock our devs or their work. We already lost Jake Day (check ninebysix). We do not want to be killing off devs with flames.
[Droid Incredible Android Development] TNS201:
Im not a Dev, but I like experimenting with my phone and theming. I think Jake Day was full of **** though.
[Droid Incredible Android Development] :
I was just saying not to kill of community members. Believe me, you are more of a dev than jake.
[Droid Incredible Android Development] mrozzeh:
hahahahahahhaahahahahahahahaahahaahahahaha.

But seriously, it sure takes a lot of skills to know that if you unplug something it will interrupt whatever it was doing. Good find brah.
[Droid Incredible Android Development] Gimpeh:
Dev and Jake Day do not belong in the same sentence...hell not even in the same thread.
[Droid Incredible Android Development] :
Heeheehee
[Windows Phone 7 Software Development] drownage:
Hey,

I remember seeing a whole list of images with concept WP7 Software UIs... they were like samples/templates/desings/photoshop-images... just a whole bunch of them... I tried searching them on xda, couldn't find anything... does anyone know/remember what I am talking about? If so, can you point me to the thread?

Thanks...
[Windows Phone 7 Software Development] daniel-t:
Here you go...

http://xdaforums.com/showthread.php?t=728913
[Windows Phone 7 Software Development] drownage:
^

not thsoe, those are control templates... there were just images we saw back in may or april... like zune like UIs... anyone remember?
[Windows Phone 7 Software Development] derFuks:
maybe these?

edit:

wrong link

httpX://on10.net/blogs/sarahintampa/Photoshop-Templates-for-WP7-Mock-Ups/
[Nexus One General] jm1999:
Quicksilverscreen.com

Its kind of hard to navigate with small buttons but the quality is there. Streams wonderfully on hspa+ or 3g. Give it a go.
[Nexus One General] productofusa:
Thats what I hate about all these FREE TV/MOVIES links I run into, is ya gotta jump through so many hoops, watch, click thru so many ads, by the time you get to the meat and potatoes, hell, you could have driven home and watched whatever on your big screen, real TV. And yeah, even Zoomed out the links are still tiny and close together. :mad:

But then there's always the possibility i'm a moron and don't understand how to shortcut through all the crap. :eek:

EDIT> apologize for being a whiner, especially for allegedly free stuff.
[Nexus One General] Blueman101:
im still waiting for a netflix app
[Nexus One General] ericc191:
No, I completely agree with you.
[Nexus One General] jm1999:
Its free and if I'm desperately boredj. Why not. I s how off mhy phone with this site too.
[Nexus One General] rjhay22:
Finished watching a whole movie from this site. Good find indeed. Thanks.
[Nexus One General] hbkmog:
Been using QSS for a long time. It's probably the best free movie/tv site out there.