Hello, I have noticed that there are many threads regarding bricked dna's, and I was just wondering if the dna is more prone to bricking than other phones? I've had no problem with rooting my thunderbolt in the past, did not really seem like a process that was easy to screw up. May just be how I am seeing it though, just worried that rooting the dna may riskier than when I've rooted my thunderbolt in the past. Thanks for the feedback!
As in everything in life, follow directions and there's no issues. 99% of people (at least in the US) can't comprehend basic spelling or sentence structure, so when they have to do something like follow directions to modify system files they're bound to screw up. What category do you fit in? Then you'll know if you can do it.
lacrosse1991 said:
Hello, I have noticed that there are many threads regarding bricked dna's, and I was just wondering if the dna is more prone to bricking than other phones? I've had no problem with rooting my thunderbolt in the past, did not really seem like a process that was easy to screw up. May just be how I am seeing it though, just worried that rooting the dna may riskier than when I've rooted my thunderbolt in the past. Thanks for the feedback!
Click to expand...
Click to collapse
I don't see how there is any bigger risk we are using HTC developer unlocking. We just need to change what the device looks like to HTC because Verizon said they don't want the phone unlockable. On the rezound for example we had to short out some contacts with wire and stuff now there's a risk for ya. Now remember you can't unlock if you have taken the OTA.
I haven't seen any bricking posts...
There were some bricking posts when the very first exploit came out since then the device ha e updated the exploit and there haven't been as many bricks if any. So I guess the new exploit is easier to follow compared to the old one and the chance of bricking is lrobably really low. Watch the tutorials and follow directions and you should be fine. It honestly isn't that hard.
Sent from my HTC6435LVW using xda app-developers app
I haven't seen many bricking post for DNA either..maybe that will change when the OTA update is rooted
You also have to remember that about half of the "Help! I bricked my phone!" posts aren't really bricks after all. It seems that usually, as soon as someone new to Android or HTC can't boot their phone, they "bricked" it. So a few hundred people may read about someone who bricked their phone before some of the users catch on that they aren't bricked they just dont have a matching boot.img, or didn't wipe, etc. Not having a replaceable battery seems to make users go from "fine to bricked" a lot quicker than when they can pull the battery. Of course that's placebo, but it gives them something to do besides make a thread about bricking their phone.
Related
Ok guys, before you start flaming, bear with me:
First of all, to get it out of the way, with the advent of 2nd init, a locked bootloader no longer prevents custom roms (CM7 2.3.4 runs fine on Defy and Droid X even though they only come with 2.2).
However, by having a locked bootloader, it is impossible for the user to hard-brick their device as no matter how bad you screw up, you can still always flash an SBF to recover. This would not be the case with an unlocked bootloader where someone accidentally overwrote their bl.
Thoughts?
<FLAMESUITON>
I don't believe so. How would someone accidentaly overwrite their bootloader? The person flashing a new kernel will understand the risks involved with tweaking all this low level stuff.
How often do you ever see someone totally brick their device from flashing kernels?
no
never a good thnig
LOTS of bricks were produced because people trying to unlock this thing
Sinful Animosity said:
I don't believe so. How would someone accidentaly overwrite their bootloader? ...
Click to expand...
Click to collapse
lsxrx7 said:
...
LOTS of bricks were produced because people trying to unlock this thing
Click to expand...
Click to collapse
That's one way LOL
Sinful Animosity said:
The person flashing a new kernel will understand the risks involved with tweaking all this low level stuff.
How often do you ever see someone totally brick their device from flashing kernels?
Click to expand...
Click to collapse
You don't really believe that, do you?
The by and large majority of users on this forum have very little understanding of what they're doing and are merely following the instructions posted. And I have seen plenty of "somebody please help me - I can't boot my device" threads!
Granted, a locked bootloader posses some difficulties/challenges for the true developers, but I'm coming around to the opinion that it also serves as a much needed buffer to the type of community that has become the norm on here. Just look at what's been going on in the dev forum since the Atrix came out: an experienced dev will start a thread, then 1k noobs post "is it done yet", or better yet start "demanding" support/results. The dev gets frustrated/irritated, voices his opinion, gets flamed, and moves to a different device. This has nothing to do with the locked bootloader (Moto Defy with a locked bootloader is now in the top 10 most installed/used devices for cyanogenmod), but more to do with the community/attitude...
Over the last few days alone, I have seen/been involved with at least a dozen bricks where a locked bootloader has saved someone's but and helped keep end-user device costs down (warranty).
Arg! I just don't know what to think anymore...
dew.man said:
That's one way LOL
You don't really believe that, do you?
The by and large majority of users on this forum have very little understanding of what they're doing and are merely following the instructions posted. And I have seen plenty of "somebody please help me - I can't boot my device" threads!
Granted, a locked bootloader posses some difficulties/challenges for the true developers, but I'm coming around to the opinion that it also serves as a much needed buffer to the type of community that has become the norm on here. Just look at what's been going on in the dev forum since the Atrix came out: an experienced dev will start a thread, then 1k noobs post "is it done yet", or better yet start "demanding" support/results. The dev gets frustrated/irritated, voices his opinion, gets flamed, and moves to a different device. This has nothing to do with the locked bootloader (Moto Defy with a locked bootloader is now in the top 10 most installed/used devices for cyanogenmod), but more to do with the community/attitude...
Over the last few days alone, I have seen/been involved with at least a dozen bricks where a locked bootloader has saved someone's but and helped keep end-user device costs down (warranty).
Arg! I just don't know what to think anymore...
Click to expand...
Click to collapse
Yea but the only reason they were " saved by the boot loader" is because it's locked in the first place and they're trying to unlock it.
Sent from my MB860 using Tapatalk
Clienterror said:
Yea but the only reason they were " saved by the boot loader" is because it's locked in the first place and they're trying to unlock it.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
No you misunderstood - the soft-bricks that I've dealt with this weekend were on different devices with inexperienced people trying to flash their devices and missing a step here or using a wrong file there...
dew.man said:
No you misunderstood - the soft-bricks that I've dealt with this weekend were on different devices with inexperienced people trying to flash their devices and missing a step here or using a wrong file there...
Click to expand...
Click to collapse
That's their fault. The guidelines are there, and it's the persons responsibility to know if something is going to brick their device, and it's their responsibility to follow all the instructions completely. Now, sometimes, the devs post some crappy tutorial, and it's a possible brick.
If they're on XDA, they know the risks.
Signed bootloaders present nothing but problems.
PixoNova said:
That's their fault. The guidelines are there, and it's the persons responsibility to know if something is going to brick their device, and it's their responsibility to follow all the instructions completely. Now, sometimes, the devs post some crappy tutorial, and it's a possible brick.
If they're on XDA, they know the risks.
Click to expand...
Click to collapse
Not making excuses for them! Merely pointing out that the locked bootloader does not necessarily hamper customization, but does help keep device costs down.
dew.man said:
Not making excuses for them! Merely pointing out that the locked bootloader does not necessarily hamper customization, but does help keep device costs down.
Click to expand...
Click to collapse
It does hamper it down. Imagine a Samsung Captivate without the lagfix. I would've returned mine longggg ago if it hadn't been for that. That's not available with a locked bootloader.
PixoNova said:
It does hamper it down. Imagine a Samsung Captivate without the lagfix. I would've returned mine longggg ago if it hadn't been for that. That's not available with a locked bootloader.
Click to expand...
Click to collapse
Not familiar with with Captivate, but I have a hard time believing that it could not have been fixed even with the locked bootloader. Why not? Heck, we can now overclock a locked kernel?
dew.man said:
Not familiar with with Captivate, but I have a hard time believing that it could not have been fixed even with the locked bootloader. Why not? Heck, we can now overclock a locked kernel?
Click to expand...
Click to collapse
Kernel modules. Ours isn't functional just yet though. Still interacts with the kernel, it just isn't native.
And I don't believe converting all partitions to ext4 is possible without low level access.
Have been reading any and all Rooting Posts and I have come to the conclusion that as of now, Most, if not all of the Rooting techniques are a shot in the dark.
If there is one good way that is reliable and doesn't screw up one thing or another than I have not seen it.
Example......Superoneclick....works on one phone but not the next....Roms....need more fixes to get to work than Microsoft.....
Tell me is there a proven way to unlock the bootloader, Root the phone and get Gingerbread to work fully ?
I may be new to this site and believe me I would love to have a open phone....But I have other things to do than F around trying to get a already KickAss phone to work.....Just saying....
JaB062 said:
Have been reading any and all Rooting Posts and I have come to the conclusion that as of now, Most, if not all of the Rooting techniques are a shot in the dark.
If there is one good way that is reliable and doesn't screw up one thing or another than I have not seen it.
Example......Superoneclick....works on one phone but not the next....Roms....need more fixes to get to work than Microsoft.....
Tell me is there a proven way to unlock the bootloader, Root the phone and get Gingerbread to work fully ?
I may be new to this site and believe me I would love to have a open phone....But I have other things to do than F around trying to get a already KickAss phone to work.....Just saying....
Click to expand...
Click to collapse
There are lots of tutorials in the Development forum on how to do this.
I CAN ASSURE YOU THAT preinstall method is the one IS SAFE and FUNCTIONAL
JaB062 said:
Have been reading any and all Rooting Posts and I have come to the conclusion that as of now, Most, if not all of the Rooting techniques are a shot in the dark.
If there is one good way that is reliable and doesn't screw up one thing or another than I have not seen it.
Example......Superoneclick....works on one phone but not the next....Roms....need more fixes to get to work than Microsoft.....
Tell me is there a proven way to unlock the bootloader, Root the phone and get Gingerbread to work fully ?
I may be new to this site and believe me I would love to have a open phone....But I have other things to do than F around trying to get a already KickAss phone to work.....Just saying....
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
you need to do more reading, no one uses superoneclick for the atrix... http://forum.xda-developers.com/showthread.php?t=1165791
Read the stickies..
Have you ever opened the android dev section?
Almost everything is in the sticky thread of clown.. With faqs guides etc..
Unlock your bootloader depending what atrix you have(att or international), then install the tenfars port of CWM4, and then you can root using the CWM root method..
Sent from my MB860 using XDA App
JaB062 said:
Have been reading any and all Rooting Posts and I have come to the conclusion that as of now, Most, if not all of the Rooting techniques are a shot in the dark.
If there is one good way that is reliable and doesn't screw up one thing or another than I have not seen it.
Example......Superoneclick....works on one phone but not the next....Roms....need more fixes to get to work than Microsoft.....
Tell me is there a proven way to unlock the bootloader, Root the phone and get Gingerbread to work fully ?
I may be new to this site and believe me I would love to have a open phone....But I have other things to do than F around trying to get a already KickAss phone to work.....Just saying....
Click to expand...
Click to collapse
To build on your Microsoft comment...............Some software is not compatible with all versions of Windows. The Atrix came out with Windows 95, has made it to XP, and with GB will be Windows 7. If you are not happy with the devs work, what they have done for everyone, and can't filter through the threads to get what you want, maybe you should get an iPhone and stick Cydia on it!......Or get a Windows phone because you won't have to "fix" anything on it!
If you want help, then you have started out the wrong way. Your post needs to be objective, and not flaming all the work others have done because you can't implement any of it, and are confused.
Root, ROM's, etc., do not need a bunch of fixes............you just have to READ so you know which ones work together for what you want. If you had actually taken the time, you would know that the bootloader has been unlocked, root is working, and GB is awesome. You just have to check the instructions for what you want on your Atrix, whether it be AT&T, Orange, Bell, etc.
Personally, I am on an AT&T Atrix 4G with unlocked bootloader, rooted, with GB 4.5.91, and have absolutely no complaints ot problems!
Since you don't want to F around, watch that door................it's heavy and swings closed fast.........wouldn't want it to hit you between the buttocks on the way out!
Bell ATRIX, unlocked bootloader, rooted, running 2.3.4. No problems
Sent from my MB860 using XDA App
JaB062 said:
Have been reading any and all Rooting Posts and I have come to the conclusion that as of now, Most, if not all of the Rooting techniques are a shot in the dark.
If there is one good way that is reliable and doesn't screw up one thing or another than I have not seen it.
Example......Superoneclick....works on one phone but not the next....Roms....need more fixes to get to work than Microsoft.....
Tell me is there a proven way to unlock the bootloader, Root the phone and get Gingerbread to work fully ?
I may be new to this site and believe me I would love to have a open phone....But I have other things to do than F around trying to get a already KickAss phone to work.....Just saying....
Click to expand...
Click to collapse
Thanks for the post, gave me a nice lol. I lol'd.
I'm sorry if this has been answered before but I'm using tapatalk and can't figure out how to search the forums...
Anyway, after reading this forum, I'm pretty hesitant to do anything major to my phone...I'm pretty content to just wait for the ICS OTA, however when I do get the OTA I would like to at least install Nova launcher and I'm pretty sure you need to be rooted for it to work...
So my first question is, if I do root, do I have to unlock the bootloader? And in doing so does that prevent me from receiving future OTAs?
My second question is about leedroid tweaks...I'm not a huge fan of my pink soft keys and I've read that leedroid tweaks let's you dim or turn them off completely...if I'm wanting to use that would I be romming my phone?
Sorry for sounding like such an idiot...I had a droid x and it was wayyy different from this phone as far as modding goes and from what I've gathered I can't just SBF my Rezound if I get into some trouble like I could on my X...I also had a lot of hardware issues with my X that lead to me going through a whopping 9 replacement phones, so my trust in electronics is minimal and the last thing I want to do is get stuck with a voided warranty.
Thanks for the help in advance and sorry again...I know from the video I watched to sign up that you guys get pretty annoyed with people like me but these forums seem like the most legitimate place for answers.
Hey guys, I was one of the ones who was refraining from rooting my prime because of the defects I wanted to keep it stock in case of RMA. However, after dealing w/ Asus I decided the repair center are not competent enough to repair my software issues.
I am on .21 so I tried searching for any methods to obtain root if I unlocked my boot loader. The only method I came across required rolling the firmware back to .15 & even though I've rooted, unlocked, flashed & modded a dozen or so devices, it was a process that appeared to carry some heavy risks, and required quite a bit of work & knowledge I might add.
I decided to unlock the boot loader, and attempt to install CWM via command prompts, in hopes of flashing a rooted rom. This was a much easier & much shorter process and it also consists of much simpler methods. After I was all setup, I did some searches on anyone else who may have taken the same approach & after quite a bit of thread surfing I found a couple very short discussions in the Q&A forums, that were pretty vague.
I've never written a thread or guide in the Dev section, but if someone more experienced did, and the mods would stickie it, then it would probably help some of the lesser experienced users. It would also prevent a few bricks I'm sure, that then lead to a panicked noob posting HELP threads in the Dev section.
Just a thought on something that could be beneficial to some ppl. Oh, and after I installed Virtuous, I have completely resolved the random reboots & freezes that were happening 4-6 times a day. I just can't believe the terrible software Asus has given us for such a beautiful piece of hardware....
There is a lot more risk unlocking and flashing a custom rom than downgrading and rooting. Not to mention downgrading will preserve all settings and apps,as wee as keep you on Ota updates that won't brick your device. Oh and the biggest reason not to do what you did is unlocking voids warranty whereas rooting does not. So if you just need root I highly suggest you don't do what the op did.
Let me say this. I knew NOTHING and still know NOTHING about ADB. ADB is what you use to downgrade your firmware. How did I learn to use ADB when I knew nothing about it? There is a thread here on the forums for ADB SDK usage.
The only thing you have to do to downgrade your firmware is being able to perfectly replicate less than a SENTENCE of code ALREADY written out for you in the PROPER order. If you can't do that, you probably can't even follow the directions of installing batteries in a small childs toy.
I successfully downgraded my Transformer Prime from .21 to .15 after just 5 minutes of reading and REREADING the directions. Just make sure you understand what happens during each step and that you know what step comes after it. Make sure you do NOT skip a step.
I have never once bricked a device... NEVER! Also, rooting alone will not fix Asus' terrible software! Unlocking the boot loader is not a great risk, its a one click method done with an Asus distributed tool! Lol... Unlocking does void an already worthless warranty, since there are so many documented cases of Primes coming back from the tech centers w/ prominent physical damage, still present issues, & owners losing their device for up to 3 months! All of these circumstances are actual reported incidents I've read right here on the xda threads! So... before anyone jumps in, always ready & willing to condescend as ALOT of ppl here on Xda do, please consider your options if your one of the many dealing w/ being SCREWED by Asus! This is a viable method to make the best of a piece of hardware you've spent what you may consider a lot of money on!
If your interested in getting a custom Rom & you don't know how on the .21 update, then pm me. I will no longer publicly post any comments on xda. As even developers are leaving this community due to the nature of its members. There are quite a lot of rude, condescending youngsters here.
I'm a polite, well educated, respectful, and self made member of society, who is conscious of how to address others on or offline. Somehow, every time I've made a post, community suggestion, or even a comment to thank or encourage others, I seem to get the two cents of the "I know better than you" crowd. Funny..... that doesn't happen on the other development sites?
I am really curious about this.Maybe some can help me understand this in somewhat laymen terms. I and somewhat knowledgeable of the Android system. I have a Verizon Fascinate. I have installed the wrong Rom package on it and it was bricked to such a degree that I needed to find the basic Stock package DI01 and flash back to Stock,but it doesn't break the phone like the Note i717. I also have an Xoom. I have also installed something that wasn't correct and it was stuck on the Motorola screen f( I'm guessing bricked ) and again at that point I needed to find the Stock package to flash but the Note was useless after the brick.
I hope someone can help me with this one. I really feel terrible about bricking my Note i717 having to send it to be JTAGged.
What is your question ??
you need JTAG info ??
My question is why is the Note easily bricked and useless after that but the others that I have mentioned above and perhaps other phones, are not so useless after brick.
My son has a Note ii. He bricked his but was able to regain a flash by booting in DL or Recovery mode. I would like to know why is that so. Maybe others out there also would like to know.
That is my query.
Samsung products break when you flash the wrong rom. Its news to me that other devices survive that error.
But for all phones, brick is brick, and that is from incorrect roms. Everything else isn't brick.
kjacw said:
I am really curious about this.Maybe some can help me understand this in somewhat laymen terms. I and somewhat knowledgeable of the Android system. I have a Verizon Fascinate. I have installed the wrong Rom package on it and it was bricked to such a degree that I needed to find the basic Stock package DI01 and flash back to Stock,but it doesn't break the phone like the Note i717. I also have an Xoom. I have also installed something that wasn't correct and it was stuck on the Motorola screen f( I'm guessing bricked ) and again at that point I needed to find the Stock package to flash but the Note was useless after the brick.
I hope someone can help me with this one. I really feel terrible about bricking my Note i717 having to send it to be JTAGged.
Click to expand...
Click to collapse
kjacw said:
My question is why is the Note easily bricked and useless after that but the others that I have mentioned above and perhaps other phones, are not so useless after brick.
My son has a Note ii. He bricked his but was able to regain a flash by booting in DL or Recovery mode. I would like to know why is that so. Maybe others out there also would like to know.
That is my query.
Click to expand...
Click to collapse
Given the fact that you have bricked more than one device, you might want to learn some more about your devices before you keep flashing things onto them...
wase4711 said:
Given the fact that you have bricked more than one device, you might want to learn some more about your devices before you keep flashing things onto them...
Click to expand...
Click to collapse
Couldn't agree more. I would have kept that information to myself.
I don't see much point of this. It's like asking why did my screen break so easily when I hit it with a hammer?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
MoJoe277 said:
Couldn't agree more. I would have kept that information to myself.
I don't see much point of this. It's like asking why did my screen break so easily when I hit it with a hammer?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Well I didn't create the thread to be picked apart, I was just curious as to why it was so easy to brick my Note and it be useless as opposed to some kinda of software imposed to help Noters. I am not writing here to be picked apart and I really do not appreciate this kind of action. I am just trying to get information. This is a Question and Answer forum and I was asking a question maybe a stupid question albeit a question to know why it was so easy to brick the Note and render it useless where as other cell phones when flashed with the wrong information can still be put in the DL Mode and flashed Stock
OK... I'll give you an answer. First, what you've experienced with your other devices is not considered as " bricking" them, maybe a " soft brick" but not a real true brick. This term (brick) is being used way too often and improperly. When you flash something like a simple mod incorrectly and it causes bootloops, freezing on boot screen, etc, this is not a brick. If you flash something major like a rom that is not for your device and completely shuts down your phone with no life what so ever, this is a brick. This phone is not any easier to brick than any other phone. Companies can only do so much to keep their users from screwing up their devices. Maybe my previous post was a bit harsh.... But considering the nature of this thread and your op, it's a little hard not to point out the obvious. If you researched properly as directed in just about every thread in xda, you wouldn't be asking the question you're asking because you would not have a bricked phone right now.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
I agree with the post above mine ...
Damaging this device is virtually impossible given the JTAG option.
Many other devices do not share that luxury.
The note would then be considered much harder to brick, or at least unbrick after major firmware damage has occured.
And yes, please familiarized yourself with the terms, and read every action 5 times over before Modding a $700.00 device .IMHO ...g
Well my error was not that I didn't read and research. I think my error was that I was trying to flash the "LiquidSmooth" Rom on my note and I was following the instructions that was given specifically for my phone Note i717 and in the instructions there was a dl link for that rom, which I did but it was not from this forum. I think that was my error not as a result of being lazy and wanting something for nothing.
Thanks for the info. I was a bit curious about bricking.
Well, that error has been repeated by several people here recently. The version you downloaded and installed was most likely for the galaxy s3. The one you should have downloaded says "quincy" in the file name.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Thanks for your help MoeJoe277 now I will remember that.