Database Users

Bootloader and Rom information

Hello all, i expected to see work done on a custom rom by now. I know the bootloader wont accept any old rom but are we not able to make modified version of the current R2 rom and flash it over our current one? Speaking of bootloaders has there been any progress on getting the bootloader opened up a little?
All the best

I guess work is still being done on it as seen in the custom rom development thread.

Ppl need to stop nagging about when it's going to be done..
it's not like the devs have the bootloader cracked and they are enjoying it by themselves whilst telling us that it hasn't been cracked just to watch us suffer..
if they have it, they'll post it.. what i don't get is.. ppl keep asking about the progress of the work.. what's it matter to you guys... it's not like knowing where they are is gonna help any of us end users atm.. also, it's not something that's been done before.. so they maybe 99% done, or 2% done.. they just won't know until they actually crack the bootloader.. just wait patiently man

Agreed, I don't know why people have to constantly open new threads acting like ...hey, if I ask in a new thread, I bet they'll answer!
Unfortunately the world is full of people that think others owe them something. When they finish, and make a useable step guild JUST LIKE ROOT, they will release it and we will all be happy then. Until then, sit on your hands and don't type any more useless posts. Please and Thanks

I'm a total noob with the inside of the android OS.. and the Win6.1 Os on the X1 before.. but what I am is appreciative of a bunch of people who are prepared to work and share their results with the world, and then to top it off, right up guide lines so the rest of us can enjoy!
/hattip to devs !!

Talonnb said:
Agreed, I don't know why people have to constantly open new threads acting like ...hey, if I ask in a new thread, I bet they'll answer!
Unfortunately the world is full of people that think others owe them something. When they finish, and make a useable step guild JUST LIKE ROOT, they will release it and we will all be happy then. Until then, sit on your hands and don't type any more useless posts. Please and Thanks
Click to expand...
Click to collapse
OI!!! STEREOTYPICAL GUY HIDING BEHIND HIS INTERNET CONNECTION!! calm it, there is a serious lack of people attempting to create custom roms (at least in the public eye), i was hoping this would spark off discusion about how we would go about doing it, you actually sicken me with your lack of manners! you would NEVER say something like that my face and thats a fact. mainly out of fear that i would punch you in yours for complete disrespect if nothing else, i was actually one of the people telling people to shut up asking for root to be achieved over and over, i am simply seeking information on what stage things where at, where there any one with custom roms in the works. I am a nice person who asks polity for information . i dont nag i dont demand because i dont feel that i deserve anything. you're the real scumbag here not me.

sabianadmin said:
OI!!! STEREOTYPICAL GUY HIDING BEHIND HIS INTERNET CONNECTION!! calm it, there is a serious lack of people attempting to create custom roms (at least in the public eye), i was hoping this would spark off discusion about how we would go about doing it, you actually sicken me with your lack of manners! you would NEVER say something like that my face and thats a fact. mainly out of fear that i would punch you in yours for complete disrespect if nothing else, i was actually one of the people telling people to shut up asking for root to be achieved over and over, i am simply seeking information on what stage things where at, where there any one with custom roms in the works. I am a nice person who asks polity for information . i dont nag i dont demand because i dont feel that i deserve anything. you're the real scumbag here not me.
Click to expand...
Click to collapse
that's because your feeble mind is unable to comprehend the fact that the bootloader isn't cracked, or the implications of that. there is absolutely no point in a custom rom until this is done
Sent from my X10a using XDA App

Mr. Sabianadmin, you should first do some research of what it is required to load a custom Rom in the Android world. Maybe you are coming from the Windows Mobile world and root has a different meaning.
Anyway, this thread is useless because there is no going to be chefs developing custom Roms without the bootloader being hacked. Once the bootloader is hacked and there is a custom recovery for the phone, I am sure tons of chefs will appear with new custom Roms. May I suggest that you go and read the wiki of other rooted Android phones (there is one for the HTC Magic) to educate yourself.

zephyrix said:
that's because your feeble mind is unable to comprehend the fact that the bootloader isn't cracked, or the implications of that. there is absolutely no point in a custom rom until this is done
Sent from my X10a using XDA App
Click to expand...
Click to collapse
How many highly qualified software developers do you know with a feeble mind in that regard? i know its not yet cracked. im saying editing the current stock rom thats ON the device and then transfer, this method was in fact used during the rooting process. (or can you not remember back that far?)
Also *Sent from my X10a using XDA App* should have read Sent from my ass under the guise i was positively contributing,
go do somthing like try and look for methods to patch/circumvent the signing process like i currently am instead of annoying me.

sabianadmin said:
Also *Sent from my X10a using XDA App* should have read Sent from my ass under the guise i was positively contributing,
go do somthing like try and look for methods to patch/circumvent the signing process like i currently am instead of annoying me.
Click to expand...
Click to collapse
wow.. that's the most childish comment i've come across since.. yesterday (hahha surprisingly there ARE a lot of ppl like you on the Internet)
sabianadmin said:
How many highly qualified software developers do you know with a feeble mind in that regard? i know its not yet cracked
Click to expand...
Click to collapse
yes.. you may be a higly qualified software developer..
you maybe trying different ways to prevent/circumvent signing processes..
but if you are a so-called highly qualified software developer, you SHOULD know that if the bootloader hasn't been cracked yet, it's NOT GOING to fire up any discussions among the chefs as you say since it would be totally useless when the bootloader actually gets cracked..
sabianadmin said:
Speaking of bootloaders has there been any progress on getting the bootloader opened up a little?
Click to expand...
Click to collapse
and you SHOULD know that there really is no way of knowing how far the devs have accomplished in terms of progress until the bootloader is actually cracked for public use...
also, just because you are 'working' on other ways, it doesn't mean you can say
sabianadmin said:
i expected to see work done on a custom rom by now.
Click to expand...
Click to collapse
the devs don't owe you anything... it's not like you are their boss and you assigned them a task that was due last week. you write as if you just wrote some innocent comment with no ill intention, but you gotta understand that comments like above really pisses ppl off..
sure some devs maybe doing it for the bounty.. but it still doesn't mean you get to nag at them .. you say you weren't nagging but that you were just simply asking questions.. well my dear.. THAT WAS NAGGING..

[Pet Peeve] ADB? What's that? Oops I bricked my Xoom, HALP!

If you don't have the first clue what ADB is or the intellectual curiosity it takes to learn about it you should not root your Xoom and definately should not try to put custom ROMS on it.
This has been a public service announcement.

Have to learn somehow.

If you dont know what adb is, this helps me out
http://forum.xda-developers.com/showthread.php?t=879701
After you read it and you still havnt a clue what it is stop hacking or read it again and again.

Yes, it seems like there is a new "did I brick?" question each and every day.
Read first, read again, and make sure that you fully undestand the process first. It certainly saves time and frustration later. I am certainly no pro, but I was able to successfully unlock, root, install CWM, upgrade to 3.1, install all of BRD's kernels (now on 1.4.4), and set-up USB tether by reading the excellent information here on XDA.

I bet if more people made one click root methods this wouldn't be a problem...
Sent from my Xoom

bwcorvus said:
I bet if more people made one click root methods this wouldn't be a problem...
Sent from my Xoom
Click to expand...
Click to collapse
It appears that a fair number of people tried real hard to brick their WiFi Xoom using the 3g section of one-click root.

Well, it took me to completely stuff my Xoom, to get how adb works. Yay!
Is there a way to flash official Moto images if my PC won't recognise my Xoom via the usb cable? I can get into CWR, and even reboot via adb, and that's it.
?

To be honest "you have to learn somehow" isn't a good defense, because you can do your research before actually trying and you'll probably avoid a lot of the problems that we see here.
It's not like the only choices are "do it blind"/"don't do it at all".

Some people learn the hard way, I'm a glowing example. Just make sure you read until you get really confused, grab a coffee, and read until it makes sense. If you don't understand what you are trying to do, but you want to give it a go, make sure your your prepared to have the worst happen.
BTW. I finally figured how to restore my system to factory! YAY!!!
Now the fun part of trying it all again....

Learning is great, however blindly trying something that you do not understand can be disastrous. Root, wiping, flashing, etc are all tasks that modify or rework the basic functions of a device. The devs who find these ways to help us do this are simply amazing, but it is NOT for everyone. Too often we see "Help!!!!, or What now???" because people simply see a thread and jump into rooting, and flashing without knowing what they are doing.
I am not an ADB expert, but I do believe that if you take your time and follow the posted instructions to the T, you will be fine. Again, people often report back, myself included that something doesn't work right or it is not doing what it should. After looking back I noticed that I skipped a step or did something out of order because I "thought I knew what I was doing".
I do caution people who are new to the XDA forums and new to Android. I would lurk for a but, gather some knowledge, then try a few things. If you have some issues, PM a member who you see has some good skills or knowledge in the area. This is a forum to help each other and too often it turns into a flame session.
Again, I am no expert I just try to offer some helpful advice.

dubie76 said:
Learning is great, however blindly trying something that you do not understand can be disastrous. Root, wiping, flashing, etc are all tasks that modify or rework the basic functions of a device. The devs who find these ways to help us do this are simply amazing, but it is NOT for everyone. Too often we see "Help!!!!, or What now???" because people simply see a thread and jump into rooting, and flashing without knowing what they are doing.
I am not an ADB expert, but I do believe that if you take your time and follow the posted instructions to the T, you will be fine. Again, people often report back, myself included that something doesn't work right or it is not doing what it should. After looking back I noticed that I skipped a step or did something out of order because I "thought I knew what I was doing".
I do caution people who are new to the XDA forums and new to Android. I would lurk for a but, gather some knowledge, then try a few things. If you have some issues, PM a member who you see has some good skills or knowledge in the area. This is a forum to help each other and too often it turns into a flame session.
Again, I am no expert I just try to offer some helpful advice.
Click to expand...
Click to collapse
Well said, don't forget irc zoom channel.
Sent from my Xoom

Thanks for "getting" the spirit of my post. I wasn't trying to be mean at all just saying... there's so many "help me i screwed up my xoom" posts and what concerns me is that too often the advice given around here is "just go root and and load a custom rom". Well that sounds real attractive until you realize that you have no idea what's going on and your Xoom won't turn on. Then your heart sinks and you don't have many places to turn to, fortunately there is this forum but I just hope that people will take more time in the future to understand what it is that they are getting into or at the very least be absolutely willing to set fire to six to eight hundred bucks

there is no such thing as a bricked xoom. Ill prove it. Send me your bricked xoom along with a $100 PayPal unbricking fee. Ill send you back a restored factory state xoom. If Its truly bricked Ill send the xoom back to you and give you back $120 for the trouble. Any takers, contact me.

gnackattack said:
To be honest "you have to learn somehow" isn't a good defense, because you can do your research before actually trying and you'll probably avoid a lot of the problems that we see here.
It's not like the only choices are "do it blind"/"don't do it at all".
Click to expand...
Click to collapse
dubie76 said:
Learning is great, however blindly trying something that you do not understand can be disastrous. Root, wiping, flashing, etc are all tasks that modify or rework the basic functions of a device. The devs who find these ways to help us do this are simply amazing, but it is NOT for everyone. Too often we see "Help!!!!, or What now???" because people simply see a thread and jump into rooting, and flashing without knowing what they are doing.
I am not an ADB expert, but I do believe that if you take your time and follow the posted instructions to the T, you will be fine. Again, people often report back, myself included that something doesn't work right or it is not doing what it should. After looking back I noticed that I skipped a step or did something out of order because I "thought I knew what I was doing".
I do caution people who are new to the XDA forums and new to Android. I would lurk for a but, gather some knowledge, then try a few things. If you have some issues, PM a member who you see has some good skills or knowledge in the area. This is a forum to help each other and too often it turns into a flame session.
Again, I am no expert I just try to offer some helpful advice.
Click to expand...
Click to collapse
It wasn't really a defense just a "it's what happens" type of thing. Yes people can be smart and read up. But the reality is that most people won't (rather it be because of stubborness or lack of time). Something happens, then you have the "ok i gotta fix this, let me look up..." or "oh noes I brokes it. I'm going to join a forum to whine about it to the people so they can help me. I mean it's their job right?".
Thing is that rooting is most misunderstood to be the equivalent to jailbreaking. Just as jailbreaking is most misunderstood as only being useful for free games and apps. Some people just never want to look into what these type of things really are, because they don't care unless it's the means of getting something for free.

bigrushdog said:
there is no such thing as a bricked xoom. Ill prove it. Send me your bricked xoom along with a $100 PayPal unbricking fee. Ill send you back a restored factory state xoom. If Its truly bricked Ill send the xoom back to you and give you back $120 for the trouble. Any takers, contact me.
Click to expand...
Click to collapse
Sounds like some money to be made here

bigrushdog said:
there is no such thing as a bricked xoom. Ill prove it. Send me your bricked xoom along with a $100 PayPal unbricking fee. Ill send you back a restored factory state xoom. If Its truly bricked Ill send the xoom back to you and give you back $120 for the trouble. Any takers, contact me.
Click to expand...
Click to collapse
I'm sure there's at least one taker out there. Its likely the guy who started the 'Motorola refused to fix xoom' thread. At http://forum.xda-developers.com/showthread.php?t=1107488

bigrushdog said:
there is no such thing as a bricked xoom. Ill prove it. Send me your bricked xoom along with a $100 PayPal unbricking fee. Ill send you back a restored factory state xoom. If Its truly bricked Ill send the xoom back to you and give you back $120 for the trouble. Any takers, contact me.
Click to expand...
Click to collapse
So how would you fix the partitioning of a xoom through cwm? That seems to be the most common "i bricked my xoom" thread.
Sent from my HTC Vision using XDA App

I feel that the best way to go about things is to read all you can about ADB, how the Xoom works and the specific root method or kernel you want to use. Then, if something goes wrong, search, search then search some more to try and find someone who had a similar problem as yours and try to learn what went wrong and how...then solve your own problem. If you are REALLY stuck, PM a user who seems to know what they are doing and appears to be patient, or post a question that includes all the details and ask politely for help. Take the knowledge you are given, add it to your own, then try to help other people in the same pickle.
If you look up the word EDUCATION in Websters, odds are the picture will look something like the paragraph above.
Personally I am not cheesed off too badly by the people who do things without sufficient knowledge. The ones that drive ME nuts are the ones who do that, then come into the forum and demand that someone hold their hand and personally walk them out of hell step by step...or better, blame the hardware/software and then angrily return it to the store, pretending that it just suddenly died.

rschenck said:
Personally I am not cheesed off too badly by the people who do things without sufficient knowledge. The ones that drive ME nuts are the ones who do that, then come into the forum and demand that someone hold their hand and personally walk them out of hell step by step...or better, blame the hardware/software and then angrily return it to the store, pretending that it just suddenly died.
Click to expand...
Click to collapse
Exactly what I was trying to say. And I know what specific thread you're talking about lol

Notice! You will brick this device...

I know everyone is eager to set up their KF HDX how they want it & many of you are new-ish to XDA, so you have been able to rely on tools to automate everything, making it easier to accomplish what you want, but not so great for learning the basics of Android & the core development & debugging tools that are used in the automated processes like the various toolkits you find throughout the forum threads.
At any rate, I am writing a warning about this device ONCE AGAIN. If you really have no idea what the sdk is or how it is used, the HDX is not something you want to start messing with. You know who you are. If you aren't running Linux, or at the very least a dual boot distro like Unbuntu via wubi & you have never installed or used the Android SDK, PLEASE think twice about whatever you are contemplating.
The Kindle Fire HDX is not like other device you have maybe played with, or owned. It is a low level development device that uses an oddball system for updating & while it is vulnerable to several exploits, the bootloader is 100% locked. Complicating this issue is the fact that the device does not have fastboot access & messing with certain system files or permissions CAN & WILL cause issues ranging from wifi & 4G connectivity to a full on hard brick. There are also checks in place that will prevent adb access if you remove or mess up certain binaries or drivers. Some of these things CAN & WILL lead to loss of ADB access. Without ADB access, anything you break CANNOT be fixed.
This is NOT the device to get your feet wet on when it comes to rooting or modding. In the last two days alone, I have had 8 requests from people with devices that are having issue because of something that was done inadvertently or because something was done in the wrong order. I am willing to help WHEN I CAN, but I am an engineer, not a developer, with a busy schedule & a family, so taking care of my responsibilities comes before anything XDA related, for myself, or anyone else.
If you decide to ignore all of the posts about people bricking their devices & you ignore this warning, the SECOND SUCH WARNING, well, fine. After all it's your device & you can do whatever you want to it. Just don't expect to find an easy fix or someone there 24/7 to hold your hand through the process of trying to recover it. After all, this is a development forum, where you are expected to have a certain degree of knowledge, or be in the process of gaining that knowledge & it's not something you are going to learn by osmosis or be able to cram into a panicked couple of hours because you messed up your device.
So, you have been warned. Again. Unless you want a $300 - $700 project you may never finish, read BEFORE you do. Learn about what you are trying to accomplish & just deal with the Amazon only device until you can understand at the very minimum how to use adb & know how to apply all of the various adb commands. The absolute worst time to try to learn anything is when you are panicked & grasping at straws.
Don't be this guy:

I think that http://towelroot.com/ is a good place to start as the apk can be side loaded and should provide root access. I still have root on my Kindle Fire HDX 7" so I dont have any need for this root method, but according to the CVE-2014-3153 most versions of android are affected including 4.2.2. I would say if your a noob and not comfortable with adb and command line then this is your best bet for gaining root. Once you do have root I would suggest installing a firewall app and block everything except the apps you want to have access to the internet this should stop any updates from hitting your device. Have Fun!!
CDub50

cdub50 said:
I think that http://towelroot.com/ is a good place to start as the apk can be side loaded and should provide root access. I still have root on my Kindle Fire HDX 7" so I dont have any need for this root method, but according to the CVE-2014-3153 most versions of android are affected including 4.2.2. I would say if your a noob and not comfortable with adb and command line then this is your best bet for gaining root. Once you do have root I would suggest installing a firewall app and block everything except the apps you want to have access to the internet this should stop any updates from hitting your device. Have Fun!!
CDub50
Click to expand...
Click to collapse
Not helping. Yes, anyone can root there device by installing an apk & clicking a few buttons. The ISSUE is what they do AFTER they root, because now they have access to do things like overwrite graphical drivers with ones that are 4 years old, erase directories from the system partition or just completely WIPE the system partition. These are three examples of things that people have done in the last 24 hours with root. I'd go thru the other 5 from PM's but frankly I don't remember the exact issues, most were some form of the previously mentioned mistakes. But hey, since you are telling people that "aren't comfortable with adb..." they should root, I'll start a brick master thread for you to take care of. :good:

yeap
gsleon3 said:
not helping. Yes, anyone can root there device by installing an apk & clicking a few buttons. The issue is what they do after they root, because now they have access to do things like overwrite graphical drivers with ones that are 4 years old, erase directories from the system partition or just completely wipe the system partition. These are three examples of things that people have done in the last 24 hours with root. I'd go thru the other 5 from pm's but frankly i don't remember the exact issues, most were some form of the previously mentioned mistakes. But hey, since you are telling people that "aren't comfortable with adb..." they should root, i'll start a brick master thread for you to take care of. :good:
Click to expand...
Click to collapse
well said and repeated!

GSLEON3 said:
Not helping. Yes, anyone can root there device by installing an apk & clicking a few buttons. The ISSUE is what they do AFTER they root, because now they have access to do things like overwrite graphical drivers with ones that are 4 years old, erase directories from the system partition or just completely WIPE the system partition. These are three examples of things that people have done in the last 24 hours with root. I'd go thru the other 5 from PM's but frankly I don't remember the exact issues, most were some form of the previously mentioned mistakes. But hey, since you are telling people that "aren't comfortable with adb..." they should root, I'll start a brick master thread for you to take care of. :good:
Click to expand...
Click to collapse
Come on though, this XDA forums, isn't it? Anyone reading these threads should be well aware of the risks involved. With towelroot app rooting the device is simple, and not going to brick your tab. Being reckless and doing some of the other things you mention, well, sorry, but like Clint Eastwood says in Magnum Force, "A man's got to know his limitations".
sent from hdx+ with tapatalk

Lol. When the vroot method was posted a couple days ago the hdx forum was quite silent...
Then BOOM!
"OMG I BROKED MY TABLET! BRICKED HDX! *BLAH BLAH* BROKE MY TABLET! HELP!!!! HELP!!! BRICKED TAB! "
good warning for noobs.
Sent from my SGH-T999 using Tapatalk

I used the towelroot, then used a ota update blocking script and kindlefree, that's it. I bet people are out there installing safestrap, Roms and whatnot.

GSLEON3 said:
Not helping. Yes, anyone can root there device by installing an apk & clicking a few buttons. The ISSUE is what they do AFTER they root, because now they have access to do things like overwrite graphical drivers with ones that are 4 years old, erase directories from the system partition or just completely WIPE the system partition. These are three examples of things that people have done in the last 24 hours with root. I'd go thru the other 5 from PM's but frankly I don't remember the exact issues, most were some form of the previously mentioned mistakes. But hey, since you are telling people that "aren't comfortable with adb..." they should root, I'll start a brick master thread for you to take care of. :good:
Click to expand...
Click to collapse
To think that everyone who roots their Kindle is going Brick their device is laughable. Most people want to root to install google play store and stop future updates. There are always going to be people that are going to brick their device by pulling a bone head move. People know the risk, but if you can make rooting less risky by just installing an .apk sounds like a no brainer to me.
---------- Post added at 09:11 PM ---------- Previous post was at 09:08 PM ----------
jimyv said:
well said and repeated!
Click to expand...
Click to collapse
Please people root phones all of the time and I would say 99% of people dont run into any issues with having root.

sounds like
cdub50 said:
To think that everyone who roots their Kindle is going Brick their device is laughable. Most people want to root to install google play store and stop future updates. There are always going to be people that are going to brick their device by pulling a bone head move. People know the risk, but if you can make rooting less risky by just installing an .apk sounds like a no brainer to me.
---------- Post added at 09:11 PM ---------- Previous post was at 09:08 PM ----------
Please people root phones all of the time and I would say 99% of people dont run into any issues with having root.
Click to expand...
Click to collapse
You just sighned up for brick duty... Where was your energy and sarcasm Friday when Chinese root hit the forum? But yea thx and for chiming in though.

jimyv said:
You just sighned up for brick duty... Where was your energy and sarcasm Friday when Chinese root hit the forum? But yea thx and for chiming in though.
Click to expand...
Click to collapse
Wow. Suggesting people use a simple apk to root their device earns you "brick duty"? And talk about sarcasm, your last sentence is a good example.
What's the point of XDA if we're afraid to do anything to our devices?
sent from an Elix-R nexus 5

afraid?
move_over said:
Wow. Suggesting people use a simple apk to root their device earns you "brick duty"? And talk about sarcasm, your last sentence is a good example.
What's the point of XDA if we're afraid to do anything to our devices?
sent from an Elix-R nexus 5
Click to expand...
Click to collapse
I don't want anybody to be afraid but I expect them to do their own homework and when they cut their sh*t up not come on here acting like a rotten punk and not willing to do any work to help themselves out.... Which is exactly what a 1-Click Apk breeds.., It tells them yay they were good enough to root device.. And they just dive into making other modifications especially on a device that has no fastboot capabilities and a locked bootloader I just don't think they should make anything that easy for a unit that is this hard to recover.. Because obviously you're not going to be here to help the ones that were ignorant enough to get an application to root device but not educated enough to accomplish any other modifications without bricking their units and then come back here implying that it's anybody else's responsibility but their own.... I'm sorry but most the ones here Bricked right right now can't even run batch application without asking how to double-click thre times ... Much less run ADB commands so stick around and help please... if this device had fastboot or unlocked bootloader. I personally would not give a damn

Well, towelroot was made for a variety of devices and just happens to work with the hdx. So are we supposed to pretend it doesn't work just because some people are not able to know what they can and can't do?
Another movie quote :
Forrest Gump "Stupid is as stupid does".
Don't be stupid with your expensive tablet, if you are it's your own damn fault.
sent from an Elix-R nexus 5

tokenpoke said:
Lol. When the vroot method was posted a couple days ago the hdx forum was quite silent...
Then BOOM!
"OMG I BROKED MY TABLET! BRICKED HDX! *BLAH BLAH* BROKE MY TABLET! HELP!!!! HELP!!! BRICKED TAB! "
good warning for noobs.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I made my toolkit to help people avoid bricking issues by waiting for proven methods that work and that I tested. I made it a menu and not a stooped down click and auto run installer. I wanted to give people the choice what they wanted to install, without risk bricking.
I guess people go outside the box for the "easy fix" to a complex problem. People and jobs are like that, doing some half assed thing to keep the wheels turning. I'm just blabbing now.
Be safe when messin' with the hdx. I play with stuff while on a rom slot to avoid a stock rom brick.

move_over said:
Come on though, this XDA forums, isn't it? Anyone reading these threads should be well aware of the risks involved. With towelroot app rooting the device is simple, and not going to brick your tab. Being reckless and doing some of the other things you mention, well, sorry, but like Clint Eastwood says in Magnum Force, "A man's got to know his limitations".
sent from hdx+ with tapatalk
Click to expand...
Click to collapse
Obviously "anybody reading blah blah blah", isn't the case, as evident by the brick posts & my PM inbox. Sure, this is xda, but it's not the XDA it used to be. Part of that is because of the ease with which one can obtain root. You used to have to do everything manually, so you actually had to read, sometimes info for a completely different device, and then spend time figuring out how to apply it to your particular device. I am not saying nobody should root, frankly I do not care either way. What I am saying is that it is probably a bad idea for some people. Seriously, you think the guy that had no idea what Linux was, or the guy that thought you double click on the adb.exe to make it magically unbrick a device are good candidates for having unrestricted world writable access to a device? No. All you have to do is read some of the posts to know it isn't a good idea for some ill-prepared people & they obviously DIDN'T understand the consequences, otherwise they wouldn't have tried doing things that even the newest well informed member would ever try doing.
At any rate, this is what I think of now whenever I think of XDA, particularly the HDX forums lately. LMAO....

Say what?
Do any of you have anything useful to add besides your nanny pandering bull****? It's funny when you start digging for info on rooting a Kindle Fire HDX and this one of the first things you run across, a bunch of nannies moaning about it being too easy? Don't do it because you might break your toy because you are an idiot? Seriously? Is this a day care or am I missing something?

GSLEON3 said:
Obviously "anybody reading blah blah blah", isn't the case, as evident by the brick posts & my PM inbox. Sure, this is xda, but it's not the XDA it used to be. Part of that is because of the ease with which one can obtain root. You used to have to do everything manually, so you actually had to read, sometimes info for a completely different device, and then spend time figuring out how to apply it to your particular device. I am not saying nobody should root, frankly I do not care either way. What I am saying is that it is probably a bad idea for some people. Seriously, you think the guy that had no idea what Linux was, or the guy that thought you double click on the adb.exe to make it magically unbrick a device are good candidates for having unrestricted world writable access to a device? No. All you have to do is read some of the posts to know it isn't a good idea for some ill-prepared people & they obviously DIDN'T understand the consequences, otherwise they wouldn't have tried doing things that even the newest well informed member would ever try doing.
At any rate, this is what I think of now whenever I think of XDA, particularly the HDX forums lately. LMAO....
Having Root does not cause any issues. People create the issues, but who are you tell tell everyone not to root. Its their device if they want to root by all means root it. EVERY ROM and RECOVERY I have ever flashed or created states that in the terms of use that there is a potential they could brick their device. Who cares about your PM's. If you dont want to help them dont help, but dont create a thread just to complain about people bricking their device.
Click to expand...
Click to collapse

Thanks....but....
I'm not a developer....nor a hacker....nor a ...whatever.....just someone who enjoys reading and learning all that I can about my phone and Kindle Fire HDX....have rooted a variety of phones and Kindles through the years - first "mod" was to be able to download music and my own ringtones to a first edition Razr back in the day. I know there are so many people smarter than me - in some areas...not all - and I gratefully use that info and knowledge I get AT MY OWN RISK....as most people do, I think....the XDA site has over 5 million members - will there be some idiots who don't read or throw common sense and caution to the wind and screw up their devices?...sure....shame on them.
But if others with that knowledge have an elitist attitude about the rest of us - well - shame on them too. If someone knows how to make it easy for someone to be able to get the most of their device - while knowing the risks - BUT WON'T SHARE because they feel we don't 'deserve" that info - please....don't post! Just keep it to yourself and enjoy the fruits of your own labors.
PS...think it's a bit of a coincidence that when the romaster root surfaced - from a Chinese developer - all he** broke loose....it seems others had the knowledge but didn't want to share....oh well.....and please...this is just my humble opinion.
I appreciate all the efforts of the developers and testers who make it easier for people like me to really get the most out of their devices - but I think there is a reason that most of the major companies lock down theirs....to stop the ones who will stupidly brick the device and blame the company....thanks for reading.

I have
revircs said:
I'm not a developer....nor a hacker....nor a ...whatever.....just someone who enjoys reading and learning all that I can about my phone and Kindle Fire HDX....have rooted a variety of phones and Kindles through the years - first "mod" was to be able to download music and my own ringtones to a first edition Razr back in the day. I know there are so many people smarter than me - in some areas...not all - and I gratefully use that info and knowledge I get AT MY OWN RISK....as most people do, I think....the XDA site has over 5 million members - will there be some idiots who don't read or throw common sense and caution to the wind and screw up their devices?...sure....shame on them.
But if others with that knowledge have an elitist attitude about the rest of us - well - shame on them too. If someone knows how to make it easy for someone to be able to get the most of their device - while knowing the risks - BUT WON'T SHARE because they feel we don't 'deserve" that info - please....don't post! Just keep it to yourself and enjoy the fruits of your own labors.
PS...think it's a bit of a coincidence that when the romaster root surfaced - from a Chinese developer - all he** broke loose....it seems others had the knowledge but didn't want to share....oh well.....and please...this is just my humble opinion.
I appreciate all the efforts of the developers and testers who make it easier for people like me to really get the most out of their devices - but I think there is a reason that most of the major companies lock down theirs....to stop the ones who will stupidly brick the device and blame the company....thanks for reading.
Click to expand...
Click to collapse
LOL I have noticed everybody that has chimed in about any complaints going on here have not been here to help recover in any of these devices last few days .. Trying to help people that refuse to help themselves.... I mean really we can only feed them so much info and babysit so much and get told please help please hello please help me . And when you attempt too. they have absolutely no clue of what you are talking about or what you're trying to get them to do it just looks too complicated so they keep asking for help... Expecting somebody here to make an easy one click.. To salvage their mistakes and keep their mommy and daddy from finding out they bricked their tablets.....and btw if this device wasnt soo fn locked down.. We would not be having this discussion because recovery of a brick would be easy with fastboot capabilities and unlock bootloader click click done. So I call BS honestly over the last few years out of all these devices I've been here in xda tinkering with.. The only time see false warranty claims are always on devices that are locked up tight.

If they refuse to help themselves then don't help them. Claiming that something shouldn't be easy and the fear mongering and elitism aren't helping anyone. Instead of trying to be a nanny document the known problems and work arounds if there are any. If you don't want to do that then don't. Save the other BS for your significant other cause no one else worth concerning yourself with wants to hear it. This thread is pointless, people here want to root their devices for any number of reasons; they why's don't matter and if it goes south it's not your problem.

I
jptros said:
If they refuse to help themselves then don't help them. Claiming that something shouldn't be easy and the fear mongering and elitism aren't helping anyone. Instead of trying to be a nanny document the known problems and work arounds if there are any. If you don't want to do that then don't. Save the other BS for your significant other cause no one else worth concerning yourself with wants to hear it. This thread is pointless, people here want to root their devices for any number of reasons; they why's don't matter and if it goes south it's not your problem.
Click to expand...
Click to collapse
I understand your point and this thread was not started as a wine fest it was supposed to be started for a fair warning I can't help it if he had a sarcastic tone to his voice from trying to help ignorant people all weekend and I think it's hilarious how people are chiming in complaining about our complaints but none of them have been here to help all the ignorant folk ... I'm just saying as one that has been here for the last five days repairing brick or trying to help that is ... Is a lot of and uneeded tension here I understand .. And it is turning" quite the Flamer thread ... So instead of chiming here to complain about our complaint and tell us to keep our complaints to ourselves as you are here complaining your self .. Please go to the general section or the troubleshooting section and start helping people... For example help him http://forum.xda-developers.com/showthread.php?t=2783591

How do i downgrade my BOG5 Verizon

I upgraded to BOG5 but found unable to downgrade and root.
Can anyone help me solve this peoblem
I would be very grateful

a133232 said:
I upgraded to BOG5 but found unable to downgrade and root.
Can anyone help me solve this peoblem
I would be very grateful
Click to expand...
Click to collapse
No one can help you solve this problem. BOG5 cannot be downgraded and it cannot be rooted. Period. End of story.

landshark68 said:
No one can help you solve this problem. BOG5 cannot be downgraded and it cannot be rooted. Period. End of story.
Click to expand...
Click to collapse
There's always JTAG...right?

dreamwave said:
There's always JTAG...right?
Click to expand...
Click to collapse
Please stop misinforming new people. I told you why JTAG wouldn't work before you even made your lengthy JTAG "brick" thread (which you referred back to your other nonsensical "petition" thread - the exact thread where I answered you WHY JTAG wouldn't work - in the end because you have absolutely no idea what you're doing).

Just remove this thread already. Or sticky it so there's a chance people will read it and never ask this stupid question again...
Sent from my SM-G900V using Tapatalk

Spartan117H3 said:
Please stop misinforming new people. I told you why JTAG wouldn't work before you even made your lengthy JTAG "brick" thread (which you referred back to your other nonsensical "petition" thread - the exact thread where I answered you WHY JTAG wouldn't work - in the end because you have absolutely no idea what you're doing).
Click to expand...
Click to collapse
Where did you reply in those words? I didn't get any of that out of what you said, unfortunately. Also, on the topic of the "petition" it was mainly to try and inform at least a couple more people and possibly gain a couple more arguments that could be used against Verizon through the FCC. I have a valid legal argument, one that you were being pessimistic about with really no backing, and on the JTAG issue...you didn't offer any reason why that was so, and so I didn't back down at the first sight of doubt. I don't mean to be defensive or aggressive in any way, but I respectfully took your opinion into account (and it was indeed an opinion on many of those matters), factored in the overall theme of posts you had made in the past, and decided that there was (and still is) possibility for solutions in each of these issues. Unless JTAG is specifically disabled at the hardware level (which was actually proven false by what I found and documented in my thread) it is still feasible to use it to modify the Qfuse flags.

dreamwave said:
Where did you reply in those words? I didn't get any of that out of what you said, unfortunately. Also, on the topic of the "petition" it was mainly to try and inform at least a couple more people and possibly gain a couple more arguments that could be used against Verizon through the FCC. I have a valid legal argument, one that you were being pessimistic about with really no backing, and on the JTAG issue...you didn't offer any reason why that was so, and so I didn't back down at the first sight of doubt. I don't mean to be defensive or aggressive in any way, but I respectfully took your opinion into account (and it was indeed an opinion on many of those matters), factored in the overall theme of posts you had made in the past, and decided that there was (and still is) possibility for solutions in each of these issues. Unless JTAG is specifically disabled at the hardware level (which was actually proven false by what I found and documented in my thread) it is still feasible to use it to modify the Qfuse flags.
Click to expand...
Click to collapse
For your petition, you keep saying, you have "valid" arguments. If you do, why do you need to keep continuing the thread? Go take it to court then. Start a class action lawsuit. You are correct, what I stated there is my opinion. Pessimistic about? You wrote so many pages for no reason. What does information do if you don't use it? All you were doing was talking about it. I was telling you why it doesn't work, and why Verizon doesn't have to respond to you, a single person, unless you were to take legal action against them, and even then, you are highly unlikely to win. By all means, take it to court. But know that talking doesn't change anything. If you want to argue that publicity is your motive, the 18k bounty got a thousand times more publicity, and the bootloader is STILL unlocked. There were also actual petition threads that people signed at change.com/etc, that have more "weight" than your thread, yet it is, again, locked still. I bet you the devs care more about a bootloader unlock than you do, because that's what most of their work/fun comes from. What did most of them do? Most (not all) of them jumped ship to Tmobile/international versions.
I took your opinion into account, but your legal backing to my eyes is simply, "Verizon must tell ME why/respond to MY claims as a sole person, not, Verizon has no basis for their argument (as I'm sure they have it somewhere, companies always try to hide their asses)." So like I said, go take it to court, by all means. I'm not being rude, I'm just saying, do something about it if you really believe what you think is right. It's also not pessimistic although you view it that way probably because it opposes your opinion, it's realistic and I've given you logical reasons why, whereas you just keep stating, Verizon has some obligation to respond to you.
As for the JTAG, I stated in one of the reasons why a bootloader unlock is not possible:
Spartan117H3 said:
...If you took the time to look at other threads ranging from the S3, Note 4, etc, you'll learn that the S5 isn't the only one. Also, the reason the Devs don't work on it is because a failed bootloader exploit bricks the phone so that not even a JTAG will revive it....
Click to expand...
Click to collapse
The devs already tried this. All you did was write a multi page post talking back and forth with yourself and new people who have no knowledgeable backing. Look back through your thread. The only support you had was from new people, you probably double posted more than their posts. I think only one senior member responded.

Spartan117H3 said:
For your petition...
Click to expand...
Click to collapse
I do apologize for trying a method that I saw absolutely no documentation on any attempts of, it was a fool of me to try and see if it might just work. You said that JTAG would not work, you gave no links and no reasons why. I understand that there might be a kill flag in there, but if the phone believes itself to be running genuine software I don't see much in the way of proof that it wouldn't accept any firmware rewrite then, especially as at that point Samsung and Verizon would stand to benefit from being able to directly write such firmware. The petition was simply to get even just a couple more eyes on the issue, and with the FCC...IT ACTUALLY IS A LEGAL CASE. I have tried to say that, that they are given ,by forfeit of direct control of the issues by Congress and the courts, a requirement that they use internal systems that are run as courts and have the power of a court, while being only possible to challenge if they act "unconstitutionally" outside their given bounds. The petition was a thing I started basically to try and let people outside of the developer community, who are demographically very likely to be vocal on issues of corporate monopoly (based on the crowd change(dot)org attracts.
I tried doing my research for each, and in basic principle found none that matched either. No, I'm not a longstanding member of the XDA community, and no I'm not an ex-oem firmware dev, but if I have an idea and no one gives me a specific reason why it won't work in a manner that would both completely address all facets of it and in a way that would help others to try and build off of the information contained within, then I will try and implement that idea or publicize it so someone who knows how can do it. Notice, on my thread about the SD Card unlock: I completely summarized the content of my findings in the first post, dead ends I ran into, and what I personally think might work in the future. If someone adds to the thread with info that either adds or nullifies an idea then I will update it and tag the post as I care about knowledge on a whole and getting info to everyone who can use it. My rationale behind this is to allow for anyone who might have an idea, or the capability to form a successful one, to research and take into account the findings of others.
TL;DR: It helps everyone, individually and as a community, to explain why an idea won't work than just to declare that it won't and the person's efforts (all of them) are in vain.
I do not mean to insult you or attack you in any way, and I have no "but" or "however" for this statement. Just for the future, instead of saying "no" and then flaming me when I say "why not," maybe say "why not" because if you know that the answer is "no," not that many issues are so black and white that a small bit of explanation or detail physically can't be given.
BTW, in response to one of your replies in a recent thread where you mentioned how a brick would not be possible to undo even by JTAG then talked about that being universal, what I was discussing was not bricking by means of triggering any lock such as that that you mention. I was attempting to reproduce conditions that would lead to a "failed flash of newer software" wherein no flag is tripped, but the phone could not load any usable kernel, modem, or bootloader image as that would allow for using the method here: http://forum.xda-developers.com/verizon-galaxy-s5/help/g900v-hard-brick-t2914847 that I have really worked on for the s3 to try and boot custom software to flash software to the phone. I am actually still optimistic for one method here because no one has said that it would not boot a very carefully crafted debrick image that would act as an external bootstrap and directly load a completely custom system image quite readily with no qualifiers or signature checks.
And sorry to everyone for the long post, I know it's annoying. Please forgive me :fingers-crossed:

@dreamwave, I mentioned that they were found by researching other phones that have bootloaders locked. There is one phone (I forget which one) where they (I believe two developers) DID get a successful bootloader unlock, but because they bricked so many phones that a JTAG would not fix, they sold bootloader unlocks for $25 a pop to recoup costs for the loss. But it was the phone itself, not a carrier specific version of a bootloader unlock. Meaning that phone worked on all carriers. I know you said you wanted links or whatnot, but it's on 100% XDA, and I'm on my phone right now/don't remember where I read it.
I gave you sound logic of why your solutions do not work, and if you take the time to think about what I say, instead of referring back to your own original statement, you would understand why. That's the thing. I state the reason why, whether or not you follow along with it is entirely up to you. I did not flame you in any way, I always responded with reasons why. It's just like you said, you were promoting awareness for people who are legally sound. But nothing was done, yet you keep continuing/promoting the thread, to what end? You're not going to do anything yourself. So why beat the dead horse?
You're right. I don't have hard documentation of answers. But you act like this is the first phone that has been attempted to be bootloader unlocked. There are threads in other forums for other phones that have been tested. There's also a plethora of sound reasoning against what you're trying to do. Do you need scientific proof and factual documentation that wind exists, or can you tell it exists because you can feel it on your skin?
If I have time later/if you want, I can find the links to what I'm talking about or you can look yourself, but for what it's worth, the developers work together in private to deter people from asking nonsensical questions such as, is it done yet/etc. As I'm not a developer (I just looked up this stuff in my free time), I don't have access to your hard evidence. But it has been stated that what you tried has been done on multiple phones in the past. If me saying that, or me finding the quote of someone saying that isn't enough for you, then by all means, go try it yourself. Developers will not come forward to tell you their progress for the reason I mentioned, so if you're looking for that, you won't find it.

@Spartan117H3
That is certainly reasonably sound logic for the most part, and I understand that many of them do it in private, but if you knew about it, especially other than just "no it doesn't work" for a specific experiment, it would be great if you wrote where any roadblock would lay and maybe a reference to where I could learn more about it. I learned that a major roadblock to parts of that method are the self verification of the bootloader and the external signature check from the SoC itself. What I am hoping to do is see whether or not the signature check and the load file commands are separate or integrated. If they are integrated, then that's probably the end of trying to use the SD Card, but if they are separate then it should be possible to dynamically alter the contents of the card after the initial signature check. Of course it's possible that it doesn't do the same signature check for an external SD card, in which case just modifying it to act as a permanent bootstrap would be entirely feasible.
I know that a lot of people have tried and failed, but if no one has tried this one specifically to its full extent I'd like to go for it. Just someone telling me no doesn't show me that they know what they're talking about. Someone telling me no, and then offering a little bit of a clue why (even just saying they found somewhere where someone tried the method then ran into (blank) as an issue) definitely helps me to try and either find a different method or a way around that issue or roadblock.
Also, I remember you telling me JTAG wouldn't work, but never addressing the SD card method... I can't seem to find any of your posts on my thread, though (a few on the petition one, but mostly didn't recognize the FCC as the deciding body, instead stating justification on the part of Verizon.) The FCC decides what their regulations say and mean, just as the courts do, and require adherence to those interpretations. No standing precedent exists that stands on Verizon's side on this issue from the arguments presented so I'm going for it, and just letting everyone know how it's going and leaving it open to discussion and reply if they have an idea that I might pursue to help my case

@dreamwave, what you are asking is the same as what this guy was "trying" to ask:
http://forum.xda-developers.com/verizon-galaxy-s5/help/vz-replacement-s5-oe1-t3190365
And the third post by the moderator clarified. As we have already discussed, you don't have enough knowledge (nor do I for that matter) to successfully start and finish a solution. It's like, if we were to build a building with just a hammer and some dirt. Why don't we leave the building process to the engineers? If you actually do have enough knowledge, contact a developer to get into their private work. Otherwise, you'll leave a building unfinished, cluttering up the streets, so to speak.
Basically, you're asking for either A, someone to go along with you in whatever process you try to do (in which case, it would be easier and quicker for a dev to do it his/herself), or B, just to see where progress is, in which case, it is not useful to you nor I, because it's another "are we there yet" question, and we wouldn't be able to continue with it anyway.
You don't know if it has or hasn't been tried, but I'm sure it's been thought of. You are doing it for free of your own accord. You don't think devs would want that 18k bounty way back when? Like I said above, if you have the knowledge, by all means, contact a developer, prove your worth, and I'm sure he/she will let you into their work, with all their notes or whatnot of what they tried that worked/didn't work.
If the bootloader is locked, that means unsigned code is not allowed at the lowest level. Why would an SD card work, when it goes through the OS which goes through the bootloader? Your idea of a JTAG makes a tiny bit more sense than the SD card one, because JTAG is at low hardware level. I didn't bother posting in your thread, because I figured you'd do what you want to regardless of what people say.
I recognized the FCC argument. I don't have an answer against that, but I'm sure/assuming Verizon does. But my justification was, why does Verizon have to answer to you specifically. You don't have a case because you're not going to court with it.
Edit: I can't remember for the life of me where I read about this stuff, all I remember was searching for some very specific bootloader question (a month ago?) that I wanted to know the answer to. The person was describing why root is so easy to achieve compared to a bootloader unlock and said something along the lines of: for root, all you have to do is inject stuff into a rom and see if it sticks. For a bootloader exploit, a failed attempt bricks the phone so that not even a JTAG will salvage it.
The search also led me to a phone which I also don't remember, I believe it was something older, but two devs "charged" $25 per unlock to recover the costs of the phones they bricked.
It is similar to the HTC M9 where people buy expensive Java cards to unlock phones, and unlock them based on donations, but not the same. I'll keep looking to see if I can pull it up.

@dreamwave, Found it, it was actually the HTC M8, so I was close in my edit above. Note, this post also talks about failed bootloaders killing the phone. And note again the reason that counters your petition, but it has no "hard evidence" other than "some person" says it. But it makes logical sense, so it should be left as is (in my opinion, unless you have profound knowledge that says otherwise, because I know I don't). Verizon doesn't need to prove anything to anyone who isn't suing them, or who isn't causing red tape for them. It's a post by a recognized contributor quoting a moderator, the closest you'll get to what you want.
http://forum.xda-developers.com/showpost.php?p=54644576&postcount=10
The Java card that people are using do currently work for both the HTC M8 and M9, but are limited and expensive in comparison to the Sunshine exploit that they charge $25 for (look at the bottom of this post)
http://forum.xda-developers.com/showpost.php?p=54126788&postcount=359
This is all I can provide for you in terms of hard facts. It is the conclusion made on older phones, and applies even more so on newer/current ones. Hope this helps.

Spartan117H3 said:
@dreamwave, Found it, it was actually the HTC M8, so I was close in my edit above. Note, this post also talks about failed bootloaders killing the phone. And note again the reason that counters your petition, but it has no "hard evidence" other than "some person" says it. But it makes logical sense, so it should be left as is (in my opinion, unless you have profound knowledge that says otherwise, because I know I don't). Verizon doesn't need to prove anything to anyone who isn't suing them, or who isn't causing red tape for them. It's a post by a recognized contributor quoting a moderator, the closest you'll get to what you want.
http://forum.xda-developers.com/showpost.php?p=54644576&postcount=10
The Java card that people are using do currently work for both the HTC M8 and M9, but are limited and expensive in comparison to the Sunshine exploit that they charge $25 for (look at the bottom of this post)
http://forum.xda-developers.com/showpost.php?p=54126788&postcount=359
This is all I can provide for you in terms of hard facts. It is the conclusion made on older phones, and applies even more so on newer/current ones. Hope this helps.
Click to expand...
Click to collapse
Thanks, that helps a lot with the SD card thing and my idea there. As to the legal issue though, I disagree a bit with the person there, as though it is in Verizon's interest to keep locking them, well the letter of the law is the letter of the law...and I spoke to someone who isn't a lawyer by practice but did take the BAR exam, what they said was basically that "A lawsuit would be possible if I suffered damages, but wouldn't do much to their practices necessarily. Going through the FCC would involve two steps: a trial in which they will determine if a violation has occurred (my opinion is that one has occurred, and I posted as my last post on the JTAG unlock discussion thread my current arguments), and then a second trial in which remediatory actions/consequences will be decided. This would cover retroactive steps, which would likely include a system whereby a signed patch would be created, and customized (upon request to download) to respond to a specific IMEI/model number. This would allow for a corporation or licensing group to exclude a set of devices while allowing consumer versions to be unlocked. It really doesn't cost me anything to pursue this, and if it annoys Big Red and that's it, then so be it...I'm happy if it does Of course on the same note, Verizon hasn't specifically countered any of my statements/observations, and have really tried to exploit little technicalities such as footnotes 500 and 502 in the FCC auction release, but in each I was able to create responses that very directly opposed those in a way supported by a large amount of text in the release. I'm hoping it will work, even if I wouldn't bet a million bucks on it doing so.

dreamwave said:
Thanks, that helps a lot with the SD card thing and my idea there. As to the legal issue though, I disagree a bit with the person there, as though it is in Verizon's interest to keep locking them, well the letter of the law is the letter of the law...and I spoke to someone who isn't a lawyer by practice but did take the BAR exam, what they said was basically that "A lawsuit would be possible if I suffered damages, but wouldn't do much to their practices necessarily. Going through the FCC would involve two steps: a trial in which they will determine if a violation has occurred (my opinion is that one has occurred, and I posted as my last post on the JTAG unlock discussion thread my current arguments), and then a second trial in which remediatory actions/consequences will be decided. This would cover retroactive steps, which would likely include a system whereby a signed patch would be created, and customized (upon request to download) to respond to a specific IMEI/model number. This would allow for a corporation or licensing group to exclude a set of devices while allowing consumer versions to be unlocked. It really doesn't cost me anything to pursue this, and if it annoys Big Red and that's it, then so be it...I'm happy if it does Of course on the same note, Verizon hasn't specifically countered any of my statements/observations, and have really tried to exploit little technicalities such as footnotes 500 and 502 in the FCC auction release, but in each I was able to create responses that very directly opposed those in a way supported by a large amount of text in the release. I'm hoping it will work, even if I wouldn't bet a million bucks on it doing so.
Click to expand...
Click to collapse
Ok. Except exchange/military is most likely a greater majority of customers than us who want it unlocked. Time is money. Verizon hasn't countered because you're not talking to them, you're talking in a thread. Good luck with your lawsuit.

Spartan117H3 said:
Ok. Except exchange/military is most likely a greater majority of customers than us who want it unlocked. Time is money. Verizon hasn't countered because you're not talking to them, you're talking in a thread. Good luck with your lawsuit.
Click to expand...
Click to collapse
Thanks (P.S.: I have an ongoing case through the FCC that's independent from XDA, a formal complaint directly to the FCC by methods they've provided)

dreamwave said:
Thanks (P.S.: I have an ongoing case through the FCC that's independent from XDA, a formal complaint directly to the FCC by methods they've provided)
Click to expand...
Click to collapse
Is this really what you choose to "Live Free or Die" about? Or do you have too many irons in the fire, and this is just the most annoying? People in New Hampshire have nothing better to do than to sue Verizon for something they have no chance of winning...

ldeveraux said:
Is this really what you choose to "Live Free or Die" about? Or do you have too many irons in the fire, and this is just the most annoying? People in New Hampshire have nothing better to do than to sue Verizon for something they have no chance of winning...
Click to expand...
Click to collapse
Except I'm not suing them, I'm using the methods our gov't has already put in place specifically for occasions such as this. I'm not arguing damages, it's not a lawsuit, it's an FCC complaint...something really different that I think I've explained a couple times
P.S.: I have a lot more that I do, this doesn't take much of my time and as a high school student I basically consider stuff like this a hobby, and have you ever been to New Hampshire? I'm from the southern half of middle NH...not that many "gun wielding hicks" around these parts
I got the phone from a friend who dunked it in a lake and thought it was dead, I figured I'd try and get some use out of it and discovered the larger issue on the part of Verizon. Considering the number of people at my school who ask me to root their phone, being able to tell them "sure" and not ask if they use Verizon (most of them do) first would be really nice.
...this thread got really off topic didn't it

dreamwave said:
Except I'm not suing them, I'm using the methods our gov't has already put in place specifically for occasions such as this. I'm not arguing damages, it's not a lawsuit, it's an FCC complaint...something really different that I think I've explained a couple times
P.S.: I have a lot more that I do, this doesn't take much of my time and as a high school student I basically consider stuff like this a hobby, and have you ever been to New Hampshire? I'm from the southern half of middle NH...not that many "gun wielding hicks" around these parts
I got the phone from a friend who dunked it in a lake and thought it was dead, I figured I'd try and get some use out of it and discovered the larger issue on the part of Verizon. Considering the number of people at my school who ask me to root their phone, being able to tell them "sure" and not ask if they use Verizon (most of them do) first would be really nice.
...this thread got really off topic didn't it
Click to expand...
Click to collapse
High school student... nevermind, kablock...

What do you mean?

Can Someone Please Answer?!?!?

I've been reading through all the threads, but I've yet to find or get a single answer to any of my questions.
1. Can stock users on Nougat root phone? I'm on A2017U
2. If so what is the exact process? and I mean EXACT process!
Simple 2 questions. I'm tired of sorta descriptions. I'm not good with phones so I need straight up, barney style, cut and dry.

1 sure
2 follow the guide
If you have questions about the guide, ask in that thread.

OK let's rephrase because apparently you don't realize I wouldn't be writing this if I had done that and it worked. Also "sure" to my no. 1 doesn't make me feel better. I need a definite answer as in someone has done it. Also, again, I went through multiple threads, asked questions, and none got answers. I was completely ignored. So unless you can make a nice clean list for me, don't tell me something I've obviously done already. Thank you.

How should I know what you have done already?
Take the time to make a proper post, explaining what you have done and what is going wrong and you will get a better answer.

I haven't done anything with the phone yet. Haven't been able to. Every post I've read gives a link to another post for something else that needs to be done before you can do what the previous post stated you can do. It's utterly confusing. What I'm asking for is a list from start to finish of what needs to be done without being linked all over the place. My head is all over the place right now because not a single OP says this is the absolute first step before you can do anything with the phone. I thought I had it all down and then out of nowhere I find out before you can install LOS you need the universal bootloader flashed. Now I'm back to square 1 trying to figure out what steps go where. Honestly my first post was pretty proper in my request, but for some reason people assume that I haven't read anything. I stated clearly what device I'm on and that I hadn't done any steps yet. I don't know how much more specific I can be.

So again, which guide are you wanting to use and what is your question?
LOS has nothing to do with getting your phone unlocked and twrp installed, try to stay focused.

lafester said:
So again, which guide are you wanting to use and what is your question?
LOS has nothing to do with getting your phone unlocked and twrp installed, try to stay focused.
Click to expand...
Click to collapse
There isn't a guide that answers my questions which is why I asked here. There isn't a single thread that clearly states the axon 7 can be rooted from stock nougat. That's the first thing I want to do. Root, twrp, rom.
update: I read, from a previous reply of yours to someone attempting to do what I'm doing, that they need to flash an unlock zip before doing the fastboot oem unlock. I saw a thread that had multiple unlock zips. which one should I use?
^^^^^^^
This was what I was referring to when I said that I've been hopping from one thread to another just to try and find basic information. I've had plenty of other phones rooted, but by far doing that with this phone is a pain in the arse. There needs to be a single thread that compiles all of the information into a single guide for each phone so people like me aren't losing it reading thousands of replies trying to find out what we can and can't do.

I wouldn't help this guy. Very ignorant posts.

The easiest would be this method.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Choose the package that matches your current system - Bxx_TWRP . There's some redundancy in what it flashes, but that's ok. When done, you'll have twrp along with the fastboot that permits BL unlocking. *You still have to actually unlock the bootloader from fastboot.
FASTBOOT_UNLOCK package will only allow you to unlock the bootloader (pursuant to the above requirement*). You'll then need to manual flash the recovery of your choice .
Once twrp is in place, flash supersu 2.79.
If this is too complicated, promptly return the phone or continue to use in its current state.

borijess said:
I wouldn't help this guy. Very ignorant posts.
Click to expand...
Click to collapse
And you're reply is ignorant in itself. If you've got nothing to say that's constructive and only place judgement then go elsewhere. I'm tired of everyone on this forum and their ego. Take a step back and think for a minute that not everyone is like you. I asked 2 simple questions and this is the response I get. Try to understand, for once, where other people come from when it comes to understanding things in the threads techies post. I nicely asked in most of those threads multiple times for help and I got no answers or replies like yours instead of just simplifying it for me by telling me what comes first when trying to root the phone.

gpz1100 said:
The easiest would be this method.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Choose the package that matches your current system - Bxx_TWRP . There's some redundancy in what it flashes, but that's ok. When done, you'll have twrp along with the fastboot that permits BL unlocking. *You still have to actually unlock the bootloader from fastboot.
FASTBOOT_UNLOCK package will only allow you to unlock the bootloader (pursuant to the above requirement*). You'll then need to manual flash the recovery of your choice .
Once twrp is in place, flash supersu 2.79.
If this is too complicated, promptly return the phone or continue to use in its current state.
Click to expand...
Click to collapse
Thank you for putting an order to the process. That's all I was requesting, but it seemed my request was a bit complicated to understand for most and is apparently ignorant to ask for simplification. I'll do what's written and hope all goes well.

kingoftheafro said:
And you're reply is ignorant in itself. If you've got nothing to say that's constructive and only place judgement then go elsewhere. I'm tired of everyone on this forum and their ego. Take a step back and think for a minute that not everyone is like you. I asked 2 simple questions and this is the response I get. Try to understand, for once, where other people come from when it comes to understanding things in the threads techies post. I nicely asked in most of those threads multiple times for help and I got no answers or replies like yours instead of just simplifying it for me by telling me what comes first when trying to root the phone.
Click to expand...
Click to collapse
I was just questioning the way you were demanding help. Nobody here is obligated to teach someone how to do things. We do it out our kindness of our hearts. Wanting to share information with individuals that are lost. When I rooted my phone and unlock the bootloader I did the research and I asked questions at the same time. I tried to get this figured out with the great help from XDA. You on the other hand are trying to demand someone to give you a step by step tutorial on how to get this done. I think that's the wrong approach of doing things, when you're asking for help. But then again everyone is different and you might feel some kind of entitlement in XDA! Just my honest opinion.

borijess said:
I was just questioning the way you were demanding help. Nobody here is obligated to teach someone how to do things. We do it out our kindness of our hearts. Wanting to share information with individuals that are lost. When I rooted my phone and unlock the bootloader I did the research and I asked questions at the same time. I tried to get this figured out with the great help from XDA. You on the other hand are trying to demand someone to give you a step by step tutorial on how to get this done. I think that's the wrong approach of doing things, when you're asking for help. But then again everyone is different and you might feel some kind of entitlement in XDA! Just my honest opinion.
Click to expand...
Click to collapse
If you had read my first post you would've seen that I had read many posts AND asked questions, but got no answers. I guess you didn't read that part even when I stated it 3 different times. I am quite thankful for those who do this out of the kindness of their hearts, but when you don't even read and understand my post and go off calling someone ignorant, what does that make you? I've participated in 10 different threads, talking with people just like me who had the same issues, asking the same questions, and....for the who knows how many times, got no answers or responses like yours who don't even read the post and place some halfhearted judgment like you're high and mighty. Nowhere in my post did I demand anything. You can construe my English however you want, but learn to read and understand before lashing out at someone without even so much as giving any advice yourself. Good day
Edit: The person who actually decided to give some helpful tips was the first and ONLY person to actually say something that made sense. Now because of him I'm currently booted and setting up LOS with su permissions. I even apologized to him for coming off like an ass, but you don't deserve that.

kingoftheafro said:
If you had read my first post you would've seen that I had read many posts AND asked questions, but got no answers. I guess you didn't read that part even when I stated it 3 different times. I am quite thankful for those who do this out of the kindness of their hearts, but when you don't even read and understand my post and go off calling someone ignorant, what does that make you? I've participated in 10 different threads, talking with people just like me who had the same issues, asking the same questions, and....for the who knows how many times, got no answers or responses like yours who don't even read the post and place some halfhearted judgment like you're high and mighty. Nowhere in my post did I demand anything. You can construe my English however you want, but learn to read and understand before lashing out at someone without even so much as giving any advice yourself. Good day
Edit: The person who actually decided to give some helpful tips was the first and ONLY person to actually say something that made sense. Now because of him I'm currently booted and setting up LOS with su permissions. I even apologized to him for coming off like an ass, but you don't deserve that.
Click to expand...
Click to collapse
Well you might of answered the issue yourself. On why you haven't received much help. It must be an issue with the way you communicate with your posts. I am just saying you might need to look in the mirror. Rather than blaming people here for not helping you.

I'll keep on saying this as much as I need to, I get where you're coming from. There's a lot of data about the correct way of doing things. Best thing to do is read and search. When I got my phone B29 was the new hotness and there was a bunch of older data floating around that I had to sift through. But I did it, I sifted and found my own way and combined two different methods to get my phone rooted and flashed with LOS. Honestly, the trial and error, the searching, the sifting is totally worthwhile because while this device is /DIFFERENT/ compared to methods for HTC and Samsung products, it's not harder. It's better to get yourself properly antiquated to the device you plan on flashing/hacking/rooting because there is /always/ a chance for bricking. Then another thread will be created asking for help to unbrick. Take the time, read now, read everything, understand your device, then push forward.