Database Info

Bricked my Magic?

Hi,
my Device is a 32B Device.
i tried to change my vodafone Splash-Screen, so i followed this howto:
showpost.php?p=3843361&postcount=7
nk02 said:
with windows or linux (on wine + net framework 2):
1)download this
password "androidsocket"
2)with createG1splash create your splash (mysplash.rgb565) from a gif or png 332x498
3)put the splash file ( mysplash.rgb565 ) in sdk tools/ directory
4)boot the magic in fastboot mode (witch back+power)
5)on terminal (in sdk tools/ path):
Code:
fastboot flash splash1 mysplash.rgb565
fastboot reboot
(you need [here is a link, but as a new user i cannot post links, look at the original post] haykuro spl to flash splash screen!)
in this thread there are some splash jpg/gif !
Click to expand...
Click to collapse
This howto is linked in the newbie topic btw.
So i flashed the haykuro.spl using the recovery Menu(i booted it from fastboot), but now my phone doesnt work.
Power + Back at the start => no reaction.
Power + Volume Down => no reaction
Power + Home => no reaction
It doesn't boot anymore, the Vodafone Splash Screen freezes.
And if i plug it on my pc, the usb device cannot be recognized.
I think i bricked my Magic ...
I don't understand how this could happen!?
Any Suggestions?

Did you just say you flashed Haykuro's Death SPL?

brick. sorry, no response to "special" boots and no usb = brick
could you possibly list what you did, start to finish, just so we can better understand what's happened? i'm not entirely sure - did you successfully get a new splash screen and then change the spl and that's when it all went bad, or what?
personally, i can live with just about any splash screen, the risks involved with changing it are certainly not worth it imho...

it does nothing at all ? or you got the blue led? if its same advenced as a brick (it does absolutly nothin can be a specific hardware problem not big deal it happend to me because of that even the jtag didn't work )

FirstNoobToBrickHisPhone said:
Did you just say you flashed Haykuro's Death SPL?
Click to expand...
Click to collapse
I second that.... Did you honestly flash this, to an already rooted phone... just to change your spalsh screen?
I keep forgetting how hard it is to READ and COMPREHEND things now a days.
Sorry, but your phone is done for. No amount of questions you ask will change that.

It's people like this that make me afraid to ask questions around here.

kinstinct06 said:
Hi,
Power + Back at the start => no reaction.
Power + Volume Down => no reaction
Power + Home => no reaction
It doesn't boot anymore, the Vodafone Splash Screen freezes.
And if i plug it on my pc, the usb device cannot be recognized.
I think i bricked my Magic ...
I don't understand how this could happen!?
Any Suggestions?
Click to expand...
Click to collapse
Dude, I JUST started having this issue as well! I have a 32a and I was updating my Radio/SPL for 32a Devices and now I can do nothing... I just got the phone yesterday haha... so yea

And replaced at Tmobile a few hours ago

Good thing we have all these (to put it nicely) less than average intelligent human beings to keep hiking up costs for the rest of us with their fraudulent claims and pure stupidity of not knowing how to read.

G1ForFun said:
Good thing we have all these (to put it nicely) less than average intelligent human beings to keep hiking up costs for the rest of us with their fraudulent claims and pure stupidity of not knowing how to read.
Click to expand...
Click to collapse
No kidding. And some of them wonder why there are these releases of unrootable perfected spl's! lol, I think they gave up though (Nexus one, good idea on their part imo!), people probably still manage to brick it.

KAwAtA said:
No kidding. And some of them wonder why there are these releases of unrootable perfected spl's! lol, I think they gave up though (Nexus one, good idea on their part imo!), people probably still manage to brick it.
Click to expand...
Click to collapse
Wow... you have no idea the situation nor the circumstance that people brick their phone. It only takes a small mistake to do so. I just came from having a G1 which I modded and updated constantly just about every other day trying new things. I took apart the phone to replace the physical keyboard and ended up damaging a cable from the screen. I went to Tmobile store and purchased a Fender edition MyTouch which is special in a few ways. I had no problem rooting the phone with the Goldcard method, aside from finding a working 2gb sd... I decided to upgrade the 32a SPL and radio which bricked my phone. I see no reason why it would have bricked it but I wont be trying it again.
Everyone i repeat EVERYONE makes mistakes, all be it some make some pretty wild ones... but we are all Human and calling people idiots that do not know how to read and follow directions will not help anyone here.
These forums are designed to help and assist those who want to get the full potential out of their phones and customize to their own personal wants and needs. We should all be here to help those with questions (even dumb ones... sigh) for none of you would have the knowledge you have if you had not learned it. So please stop the bigotry and ignorance and be a little more helpful to those with issues. For those who have issues, dont go blaming the devs for messing up your phones, you know the risks so proceed cautiously and learn from your mistakes.

Fact is if you had followed directions exactly you wouldn't have bricked your phone. It's doubtful the tutorial was wrong.

heavensblade23 said:
Fact is if you had followed directions exactly you wouldn't have bricked your phone. It's doubtful the tutorial was wrong.
Click to expand...
Click to collapse
+1!
Gerr1985 said:
Wow... you have no idea the situation nor the circumstance that people brick their phone.
Click to expand...
Click to collapse
Um, yes I do. Way to come to that assumption.
Gerr1985 said:
Everyone i repeat EVERYONE makes mistakes, all be it some make some pretty wild ones... but we are all Human and calling people idiots that do not know how to read and follow directions will not help anyone here.
Click to expand...
Click to collapse
What? Another assumption already! I'm not calling anyone an idiot (in this thread LOL) haha, I simply agreed about the people bricking, not following wonderfully provided instructions and hiking up the costs. Sorry to be an ass, but if you stopped coming to those assumptions, perhaps your first phone wouldn't have been a nice brick!

KAwAtA said:
+1!
Um, yes I do. Way to come to that assumption.
What? Another assumption already! I'm not calling anyone an idiot (in this thread LOL) haha, I simply agreed about the people bricking, not following wonderfully provided instructions and hiking up the costs. Sorry to be an ass, but if you stopped coming to those assumptions, perhaps your first phone wouldn't have been a nice brick!
Click to expand...
Click to collapse
I never said the tutorial was wrong just that I made a mistake in picking the wrong one or messing up somewhere... obviously.
I'm not assuming anything... its fact you only have a general idea of how someone breaks their phone in that they made a mistake, but that you dont know how or the circumstances that caused it...
I wasnt assuming you were calling anyone an idiot and sorry I used your post to quote and not the others before generalizing "anyone" who breaks their phone as an idiot who cant follow directions. It could easily be that someone was not aware of specifics and hastily updated items that are not for their particular phone or missed a step.
In life it is far too easy to make mistakes, better to sympathize, say do better next time, and move on... simple as that.
I, for one, can't help but laugh when I make some mistakes. I was fully prepared to pay for another phone because I knew what "I" did broke it and no one was to blame but myself. Life goes on, pick yourself up and move forward. Sorry??? that I took a particular interest with a fellow mytouch user who mistakingly messed up and put the phone in the "break" status. I work as an IT Administrator for many large companies and mistakes can happen all of the time, I'm just glad they can happen to me and not a client
We all know the risks involved when we mess around with the phone. I also had no idea what a bricked phone did when bricked... until this morning

Gerr1985 said:
It could easily be that someone was not aware of specifics and hastily updated items that are not for their particular phone or missed a step.
Click to expand...
Click to collapse
Messing with your phone's baseband is not a time to be in a rush.

Dear all wooters, please don't try to do modding yoga

I may be imagining it, but it seems like there's a steady increase of "help, I bricked my gtab" threads as people are starting to receive their woot's gtabs. Please stop and think. Have you ever done something like modding an android device before? Is it worth it?
If it ain't broken, don't try to fix it.
I currently got 2 gtabs. One I have modded the hell out of and the other I'm keeping the stock rom. What you can do is go to settings and set it to classic. The annoying weather TnT thing will go away and your gtab will work just fine. Very fast. Very sexy. Love you long time.
I beg you, please help yourself and consider just staying with the classic stock rom. I've been playing with it and I see nothing wrong with it. Works wonderfully.
One user on here came and said when he first started playing with the gtab in office depot he was expecting the worst screen ever because of all the negative reviews about the screen. But to his surprise, it turned out to be very pleasant. Why? Because people on the internet like to exaggerate.
And in this case, people really did exaggerate the unusability of the stock rom. If you're not doing aerobics and yoga with the gtab, you won't notice it. Please do yourself (and us all) a favor by not simply plunging into modding as soon as your gtab arrives. Play with the stock rom first. Make sure you set it to classic. Give it a couple days before you decide to whether put a custom rom on there or not.
Please think about what I just said. Amen.

+1 good advice!!!!!!

x2. And please read up on things like adb and nvflash BEFORE you you start modding. Imo, anyone modding their device should have these tools handy, in advance.
"adb", for example, is almost a standard requirement in other Android phone forums. But for some reason it's not stressed here - I am guilty of that as well. I think that, if you are taking the risk (and it IS a risk) to mod your device, you should have the tools to save yourself from yourself. There's a nice writeup on nvflash that I posted (and "Rev" wrote) and adb instructions are all over the place, not just here.
Thanks!

i dont understand where all the problems come from. if you do it just like the guide tells you, shouldnt it work? i havent dont it myself but ive read and reread the guides. arent they all exactly the same out of the box if there ota version is the same? is it people are just not following directions? cause its seems pretty simple to me even though i havent done it before.im planning on doing it and if i follow the directions exactly and it doesnt work, im just gonna throw it out the window.

Also, I forgot to add.
I work in a research lab. Even though I'm an engineer, I'm really the acting tech guy. As a side job, occasionally I make house calls to fix people's computer problems.
It is my experience that not-so tech savy people always manage to find problems that us techies would never find. Not only that, not-so tech savy people most of the time can't remember what they did and can't verbalize what they did. This makes it 100x harder on us techies.
You see, there are unspoken rules in the world of tech. For example, dealing with system files is risky. Deleting them is bad. Things like that. Not-so tech savy people don't know these rules and so they just stumble all over the place finding and creating problems that the tech people would never find.
What I just said above means that when you find (or create) a problem and you didn't follow the proper procedures, you're not always going to find someone that knows a solution. Why? Because the rest of us never dared to go down that dark narrow alley that you decided to run into. We don't know what's in there. And if you manage to find a 3 headed troll, how are we to know what to do since we've never been down that alley?
Take it for what it's worth. If I haven't detered you, at least have adb and nvflash ready. And make sure you know what you're doing with those.

fridge011 said:
i dont understand where all the problems come from. if you do it just like the guide tells you, shouldnt it work? i havent dont it myself but ive read and reread the guides. arent they all exactly the same out of the box if there ota version is the same? is it people are just not following directions? cause its seems pretty simple to me even though i havent done it before.im planning on doing it and if i follow the directions exactly and it doesnt work, im just gonna throw it out the window.
Click to expand...
Click to collapse
(1) Not-so tech savy people like to take short cuts for whatever reason. They also sometimes skip important steps in a procedure even though it's right there in front of them. At least one wooter has already bricked his gtab without backing up.
(2) No, they're not all exactly the same out of the box. Nothing is ever all exactly the same out of the box.
(3) Everything seems simple to me, too. But according to my experience, what seems simple to someone with experience isn't always simple to everyone else.
Just last week, I went to a woman's house to help her with computer problems. She made it sound like life and death on the phone. The only reason I tolerate her is because she might be my in law one day. Anyway, it turned out that the problem was she thought the monitor was the computer. We have explained to her over and over that it's only the monitor and that the box sitting below is the computer. Seems silly to us, but there it is.

fridge011 said:
i dont understand where all the problems come from. if you do it just like the guide tells you, shouldnt it work? i havent dont it myself but ive read and reread the guides. arent they all exactly the same out of the box if there ota version is the same? is it people are just not following directions? cause its seems pretty simple to me even though i havent done it before.im planning on doing it and if i follow the directions exactly and it doesnt work, im just gonna throw it out the window.
Click to expand...
Click to collapse
My transition from stock 3588 to tnt lite 5 now twotapsx went smooth as butter however some devices moving from other mods back down to 3588 and then to twotapsx had problems!!! The biggest issue was a confusion on using clockwork mod recovery as those who tried it with the ttx mostly found themselves semi-bricked which led to a literal borkathon . Most issues were from user error but on some cases there were oddball problems that just popped up!! So my point is that in Modding your tablets to anything other than stock you are risking a BORK but if you follow directions and have the proper backouts tools ready such as nvflash and adb you should be ok.

goodintentions said:
(1) Not-so tech savy people like to take short cuts for whatever reason. They also sometimes skip important steps in a procedure even though it's right there in front of them. At least one wooter has already bricked his gtab without backing up.
Click to expand...
Click to collapse
+100 on this one. I have a friend that I had to help with rooting her evo and Gtab, and had to ask her every step she took to make sure she actually took them. Luckily she learned early on to use Nandroid and keep a backup of the stock rom and any working roms before you switch to another one.

fridge,
I've skipped posts after yours to answer you, so I apologize if I duplicate something.
YES, if you do everything right bad things CAN happen:
1. Android is not a well-documented operating system and something you just "think" your doing it right.
2. The G-Tablet can be cranky. Unexpected things happen. The other day my pristine, perfect tab
was shut down properly. Next time I turned it on I had huge
"android.process.acore" errors and I had to fix it.
3. I don't know of anyone who has revealed themselves on this forum that thoroughly
understands the structure of the OS software on the G-Tablet. Read all the posts
on boot.img and partition structure. It really would help us all if we knew more.
4. There are a lot of good people who "help" others on this forum Most give good
advice most of the time -- but those of us that are human make mistakes once in a while.
And honestly, some helpers may not give good advice -- don't do it if you don't
understand and feel good about it.
5. Some people don't abide by good IT practices. I saw someone trying to get help
the other day that had barely gotten started with the G-Tab and already had CWM and had
tried three or four ROMS and other related software -- and had a soft-brick!
People need to move slow and check things out more carefully.
6. And some of the software posted here for your use may not even work right. I know a
couple of programs I have seen associated with lots of crashes. If a program
is listed in the threads with lots of crashes around it -- you better be careful!
I could go on for a long while further. If you REALLY read the forum and what's going
on instead of just looking for things to install, you will see these patterns.
Rev

Agreed completely with the intention of this post but I don't think the increase of people messing theirs up is due to woot just yet. I ordered one from the woot sale and i am fairly sure that it hasn't even shipped yet, the email said within 5 days. They aren't the fastest at shipping stuff.
It's probably more so just due to the dropping price in general.
People who have not done any moding of other android devices before should absoltely so slow and wait on loading whole roms until they get familiar with it and read up a lot and do their homework otherwise they will risk breaking their device.
Sent from my ACS frozen Epic

May or may not be Wooters but several *have* posted that they have recieved them.
Adding one small thing I've learned over the years: sometimes an install/upgrade/mod just doesn't take the first time. Or the second. Or the third. Patience is a key to sucess in these things. If it doesn't work the first time, come back the next day and try it again.
Repeating again: READ the forums and all the old threads. Go back and read them again.
And if you don't do backups, I have no pity for you.

iamchocho said:
Agreed completely with the intention of this post but I don't think the increase of people messing theirs up is due to woot just yet. I ordered one from the woot sale and i am fairly sure that it hasn't even shipped yet, the email said within 5 days. They aren't the fastest at shipping stuff.
Click to expand...
Click to collapse
Actually, mine from woot is due to arrive tomorrow. May be that's because I ordered mine 10 minutes after midnight.
But regardless, people need to think twice before deciding to take the plunge.
Edit.
And I'm just cranky because I just found out this morning I've been a victim of credit card fraud. Someone's been doing a lot of shopping online with my credit card. Mostly games, so I'm guessing it's some spoiled brat somewhere who got lucky at hitting random numbers and got mine.

roebeet said:
x2. And please read up on things like adb and nvflash BEFORE you you start modding. Imo, anyone modding their device should have these tools handy, in advance.
"adb", for example, is almost a standard requirement in other Android phone forums. But for some reason it's not stressed here - I am guilty of that as well. I think that, if you are taking the risk (and it IS a risk) to mod your device, you should have the tools to save yourself from yourself. There's a nice writeup on nvflash that I posted (and "The Rev" wrote) and adb instructions are all over the place, not just here.
Thanks!
Click to expand...
Click to collapse
I've been lurking on the gTab forums here for the last several days, and have been trying to absorb all of the info I can. I tend to research everything in depth before I plunge into anything. While much information is here, it is fragmented, and what is easy to follow for a developer is not as easy to follow for others. roebeet, you do the best of any I've seen, and I appreciate it. I've done a lot of searches which have helped some. I'm not new to Android (or XDA) as I have a stock Droid Incredible, but I am new to mods to Androids. I have also used Linux in the past, and modded kernels for newer drivers using cookbook approaches, so little scares me if I have enough information. I've sort of figured out how to install and use nvflash, ADB, and CWM using the various guides, but I'm missing some fundamental knowledge on WHEN and WHY I should really be prepared to use them. I've also tried to do some reading on Nandroid, but have found little pertinent to the gTab. So here goes:
1. What is the primary use of each of the following tools, nvflash, ADB, and CWM? When should I expect to have to use each of them? Are there gTab specific guides to their uses and the options for each outside of ROM installation guides, etc? Specific examples of when I should use each, and even more important, when NOT to use them, would be helpful. I've read all of the ROM, nvflash and ADB installation guides, and the various FAQs, and I understand HOW to install each of, just want to understand the best practices for each.
2. After reading a lot, it appears that having a complete backup of my particular ROM would be a good idea since partitions seem to differ even on stock gTabs. I've read posts here that refer to Titanium, and the use of ADB and CWM to do backups, and others that refer obliquely to Nandroid. What is the use of each of the above to do backups? It appears that Nandroid is a piece of CWM, but I may be mistaken. And if I install TnTlite using roebeet's guide, I'm not supposed to use CWM anyway. So how do I do a backup?
3. I plan to use my gTab as I get it, allowing it to do OTA updates only, for a few days, playing with the TNT and normal Android interfaces. I understand that a major OTA may be imminent anyway, possibly based on the leaked 3991 ROM, so my current plan is to wait for it, at least for a week or two. I plan to explore the guts of the file system carefully to fully understand the various instructions I've found here. Is there a way to safely install nvflash and ADB and explore more, or do I need to have an already rooted ROM installed on the GTab.
4. Some people recommend updated to newer or tweaked kernels. I've found the kernels, but haven't found any good step by steps on how to install them. Any links you can point to?
As an aside, I think roebeet's idea of a good wiki for this forum is a good one. The main XDA wiki is about useless. I would expect to see beginners guides to nvflash, ADB, CWM, etc.
Thanks for your help.
Jon

Suggestion. If you are going to install a ROM, pull the detailed instructions from one of the reputable Devs here, paste it into a word processor and add a check box before each step ( can use bullet tool) Then make sure you go thru one step at a time and check the box just in case you get interrupted. If you are unclear on a step ( ie clear cache) research it before you do anything.

thanks for your replies guys, it is definitely good to know that even if i do it perfectly it might still not work the 1st time. ill just nvflash it and try again. this is a really informative forum.

I think a centralized FAQ and / or Wiki is needed, for all the concerns you stated.
"How do I setup adb? What is it used for?"
"What is nvflash? How do I backup all my partitions?"
"What's the difference between clockworkmod and standard recovery? What are the pros and cons of both?"
"What are the difference ROMs available and what are their differences?"
"What is a customized kernel and why would I use it?"
"I have an error <fill in the blank> -- what do I do?"
etc etc. With potentially hundreds of Woot users about to jump into XDA, I think this would be a fantastic thing to have. Heck, it would a good thing to have for ALL of us, myself included.
It's NOT an easy task, however. I would argue that it's a very arduous task and something that would need to be ongoing. But I think it would ease some of the repeat questions here, and give new users a good guide to understand some of the basics.

lamchocho,
Wrong! The wooters are here!
And as the days go by there's going to be more.
Gonna be interesting.
Rev

jonalowe said:
I've been lurking on the gTab forums here for the last several days, and have been trying to absorb all of the info I can. I tend to research everything in depth before I plunge into anything. While much information is here, it is fragmented, and what is easy to follow for a developer is not as easy to follow for others. roebeet, you do the best of any I've seen, and I appreciate it. I've done a lot of searches which have helped some. I'm not new to Android (or XDA) as I have a stock Droid Incredible, but I am new to mods to Androids. I have also used Linux in the past, and modded kernels for newer drivers using cookbook approaches, so little scares me if I have enough information. I've sort of figured out how to install and use nvflash, ADB, and CWM using the various guides, but I'm missing some fundamental knowledge on WHEN and WHY I should really be prepared to use them. I've also tried to do some reading on Nandroid, but have found little pertinent to the gTab. So here goes:
1. What is the primary use of each of the following tools, nvflash, ADB, and CWM? When should I expect to have to use each of them? Are there gTab specific guides to their uses and the options for each outside of ROM installation guides, etc? Specific examples of when I should use each, and even more important, when NOT to use them, would be helpful. I've read all of the ROM, nvflash and ADB installation guides, and the various FAQs, and I understand HOW to install each of, just want to understand the best practices for each.
2. After reading a lot, it appears that having a complete backup of my particular ROM would be a good idea since partitions seem to differ even on stock gTabs. I've read posts here that refer to Titanium, and the use of ADB and CWM to do backups, and others that refer obliquely to Nandroid. What is the use of each of the above to do backups? It appears that Nandroid is a piece of CWM, but I may be mistaken. And if I install TnTlite using roebeet's guide, I'm not supposed to use CWM anyway. So how do I do a backup?
3. I plan to use my gTab as I get it, allowing it to do OTA updates only, for a few days, playing with the TNT and normal Android interfaces. I understand that a major OTA may be imminent anyway, possibly based on the leaked 3991 ROM, so my current plan is to wait for it, at least for a week or two. I plan to explore the guts of the file system carefully to fully understand the various instructions I've found here. Is there a way to safely install nvflash and ADB and explore more, or do I need to have an already rooted ROM installed on the GTab.
4. Some people recommend updated to newer or tweaked kernels. I've found the kernels, but haven't found any good step by steps on how to install them. Any links you can point to?
As an aside, I think roebeet's idea of a good wiki for this forum is a good one. The main XDA wiki is about useless. I would expect to see beginners guides to nvflash, ADB, CWM, etc.
Thanks for your help.
Jon
Click to expand...
Click to collapse
I'm quoting Jon's post in its entirety because he both perfectly articulates a number of my questions as well as captures my sense that after days worth of information mining on this site, I'm semi-well-informed enough to do the kind of damage that will surely add to the confusion you all seem to realize is imminent here.
I may be able to help with question 4. Buried in Clemsyn's kernel thread (52 pp!) ...
http://forum.xda-developers.com/showthread.php?t=895825
...is this:
INSTALLATION INSTRUCTIONS:
1. ROOT, Flash CWM Recovery (if you haven't done this yet)
2. Create a FULL nandroid backup (optional since its just a kernel)
3. Download a kernel of choice
4. Put the kernel on root of sd
5. Boot into Clockwork MOD recovery (either from ROM Manager or manually- hold volume up and down at same time and press power button, then select "apply sdcard: update.zip"
6. In recovery select "Install zip from sd card"
7. Select "Choose zip from sd card"
8. Navigate to the kernel file and select it
9. Let it install, it will take a few minutes...screen will go weird (black with big blue letters) then take you back to recovery.
10. Reboot phone
Click to expand...
Click to collapse

goodintentions said:
Just last week, I went to a woman's house to help her with computer problems. She made it sound like life and death on the phone. The only reason I tolerate her is because she might be my in law one day. Anyway, it turned out that the problem was she thought the monitor was the computer. We have explained to her over and over that it's only the monitor and that the box sitting below is the computer. Seems silly to us, but there it is.
Click to expand...
Click to collapse
Just a fair warning, they (the in-laws) never change.

A little note as to why we'll probably start seeing a lot of uninformed people here is because Viewsonic actually has a link to XDA on the "Favorite gTablet Apps and Resources" page of their site, which is accessible from the main G Tablet home page
It's in the developer resources section, but as everyone already knows that doesn't stop some people.

So You Want to Root and Mod Your HTC One X/XL

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey there! I’m guessing you've got yourself a shiny new HTC One X/XL, and you've heard about this thing called "rooting" and how it supposedly can let you do all sorts of things that your carrier won't let you do, or something like that. You arrived here a little while ago from Google or by clicking a link in some blog, and you're now nosing around trying to figure out what you're supposed to do.
But stop! Wait! You've skipped over the most important question: Should you even be here in the first place?
This is not a trivial question. Making modifications to the software on your phone is not like getting your car painted or putting on some new rims or a spoiler. It's much more analogous to replacing the fuel injectors, or modifying the intake, or changing the valve timing. If you don't know what you're doing, there's a very real chance you can render your phone permanently inoperative.
This post is not going to explain how to root, unlock, or do anything else to your phone, because there are already several other threads in the Development section about that (and no, I'm not linking to them—way too soon for that). The purpose of this post is to help you determine whether you should do it at all, and if so, what you need to know beforehand.
We're going to start by taking a short quiz.
1. Which is the most accurate assessment of your comfort level with computers and electronics?
a. I keep the Geek Squad on speed-dial.
b. I generally know what I'm doing, but I'm careful not to get in over my head.
c. I'm the guy my friends and family come to when they have computer problems.​
2. What is Linux?
a. It's, um, a computer thing.
b. It's the operating system upon which Android is based, but I had to go to Wikipedia to look that up.
c. chmod 004 linuxfordummies.docx​
3. How do you feel when your computer or some other gadget isn't working the way you want it to?
a. It's a royal pain in the ass.
b. It's not the end of the world, but I can do without it.
c. It's an opportunity to learn and problem-solve.​
4. Which most accurately characterizes your relationship with your smartphone?
a. Um, relationship? It's a phone—I just need it to work.
b. I like to play around with the settings and find interesting apps.
c. I'm not happy unless I've tweaked and customized it enough that I feel it's a good reflection of who I am as a person. Also, this reflection changes by the week.​
5. You're in the middle of trying to solve a particularly frustrating problem with your computer when your spouse/significant other announces that s/he wants to have sex. What do you do?
a. Drop everything and seize the booty.
b. Curse your computer under your breath and head for the bedroom.
c. Reply, "Sorry, honey, can you give me ten more minutes?"​
Give yourself 3 points for each "c" answer, 1 point for each "b", and subtract 3 points for each "a". Then total up your score and check the chart below:
13-15: Welcome, brother! You may proceed.
11-12: You'll probably be all right, but be careful. You may be setting yourself up for more frustration than all this is really worth.
10 or less:
Stop now, head over to Android Forums, and don't look back. Trust me, you'll be much better off in the long run.
…
Still here?
Okay. Just because you're coming in with the right attitude and background doesn't mean you aren't still going to get yourself in serious trouble. Before going any further, there are several rules you must commit to memory.
1. Do Not Make Any Changes to Your Phone Until You Have a Good Understanding of What You're Doing
You wouldn't go under the hood of your car and start rewiring things and rerouting hoses based on some vague understanding of something you read on the Internet, right? You shouldn't do the same thing to your phone.
This is the reason that “One-Click” and “All-in-One” solutions should be scrupulously avoided, no matter how attractive they may be to you at the moment.
I cannot stress this too much. Using these tools allows you to skip over important learning processes and avoid learning things you really need to know. They make it much easier for you to get into a situation you have no clue how to get out of (and we’ll come back to that below). You’re better off in the long run skipping the one-click tools and taking the time to learn how to do things manually. Basically, you pay cash now, or pay later with interest.
At a minimum, before you do anything, you should be able to explain these three concepts:
-What root access means
-What you're changing when you unlock your bootloader
-What you're replacing when you flash a custom ROM or kernel​
How do you find all this out? That's the next point.
2. Become Your Own Expert
You're probably feeling pretty intimidated right now looking at all these discussions throwing around terms, abbreviations, and acronyms that make no sense to you. That's normal—in fact, it's a good sign. If you're not intimidated, you should probably leave now, because you're lacking the sense of caution that will keep you out of trouble.
You're naturally going to be drawn to people who appear to know what they're doing. Be very careful about this. Some do know what they're doing, and some only think they do. The problem is that it can be very hard to tell them apart. That's why the worst thing you can do is go into a thread and start asking, "What am I supposed to do here?" before you know enough to be able to weigh the answers you get.
You may get help from someone who knows the answer you're seeking, and you may find someone who's just a recent noob feeling flush with a little new-found expertise. Or, worst of all, you may have the bad luck to run into someone who enjoys tricking noobs into bricking their phones. These folks are thankfully rare, but they do exist.
Ultimately, you've got to do your own learning, not piggyback on someone else's. That leads to our next rule.
3. Google is Your Friend
Yeah, I know, it's a cliché. But it's a cliché because it's true.
Your experiences are not new. Your questions, almost certainly, have been answered before (and in the case of most noob questions, hundreds or thousands of times before). You should start by reading the threads here, but every time you come across a concept or term you're not familiar with, flip to another window and Google it. "How to X" and "What does X mean" are your two most powerful tools. Use them often. (If you're not proficient enough with Google to manage this, you've got no business modding your phone anyway.) Bit by bit, you'll start to feel less lost and start developing the context to understand what people are talking about.
But didn't I just say not to trust what people tell you?
Yes. However:
4. Trust the Hivemind
That rule applies individually, not collectively. In fact, gauging collective experiences is an excellent way to see what's what. When a new exploit, ROM, or mod gets posted, there is invariably a flow of responses as people try it out. Pay close attention to these discussions before you do anything.
There are almost always a few bugs and updates to anything new. That alone shouldn't deter you too much. But it's best to wait until you start seeing people posting praise, thanks, and confirmation that their phones are working well before you dip your feet in the water.
But you're still not there yet. Just because other people are having success doesn’t mean you will.
5. Don't Do Anything to Your Phone That You Don't Know How to Undo
Who are all these people rushing to act as guinea pigs? By and large (there are exceptions), these are experienced modders who know how to get themselves out of any trouble they get into. In general, if you know what you're doing, you can take your phone back to stock without too much effort. But reverting some of these changes often depends on doing things in the right order, making backups before you start, and so on.
All of us were noobs once, and most of the people here are willing to help out new users with the right attitude. But few things are more frustrating than someone who jumps on a new mod or rom, and then posts, "That didn't work, I think I’m bricked, OMG what do I do??"
You need to figure that stuff out beforehand.
Also, it's worth pointing out that everyone makes mistakes. You're going to make a mistake at some point, probably several. Proper planning and preparation will minimize the fallout when you do.
But—there is another "but" here, and it’s a big one.
6. You May Kill Your Phone
Modding your phone carries a certain risk. Phones get permanently bricked around here on a regular basis, especially when new mods and tools get released. No matter what you do, no matter what precautions you take, there is a possibility you may render your phone permanently unusable, with nothing left to do but return it and hope you can get a replacement (and hope your carrier won't realize what you did).
This risk applies to everyone. Even experienced devs have been known to brick phones because they forgot a critical step to some routine process.
If you're not comfortable taking that risk, or you can't afford to deal with the consequences, you need to leave. Period. You've been warned. You'll get sympathy (unless you did something stupid and won't own up to it), but don't expect anyone to reimburse you, least of all the dev who posted the tool you were trying to use. It won't happen, and asking will just get you a lot of derision.
Got all that? Good luck, and happy modding.

Wow that is the greatest post I've ever seen. Gave me a good laugh.
Edit: I've gotta agree with the fact that using one click solutions to root etc really doesn't help you learn because I have almost messed my phone up on a few occasions and without knowing the basics of adb I would have been a goner. There is no one click solution to fixing your problems...
Sent from my One X using xda app-developers app

Nicely done Elvis.
Vote to put as a sticky.
Also, I laughed a little bit reading this. Lol
Sent from my HTC One X using xda premium

Best single post I think I've ever read lol. +1 on the sticky vote
Sent from my One X using Tapatalk 2

Thanks, guys. I actually wrote most of this quite a while ago, but wasn't motivated to post it until the recent influx of noobs.

Nice post.
Sent from my HTC One X

excellent
very nice, stickied.
Thank you,
mf2112
XDA Moderator

It's a funny post, but r-tards can pick up a part time job rooting phones.

Id have to agree on the one click deal also, im also leary of the aroma installer and hub now also. i know its very rare for someone to have problems with them but i did and now it cost me 60 bucks to fix. just because you learn what you are doin and are comfortable with the various things you can do, sometimes things dont go right or there is spaz in the hardware and it will render you useless

Haha! This is a great post!
Sent from my HTC One X using Tapatalk 2

Holly sh!t very well done. This should be the first thing all xda members should read. Read this and watch the video before signing up for xda. Well done!
Sent from my One X using xda premium

OMFG I love this post. Good work!!!

Any chance you'd be willing to port this post to the HTC Droid Incredible 4G LTE device section?
Only minor modifications:
HTC One X/XL to HTC Droid Incredible 4G LTE
Android Forums link

mdmower said:
Any chance you'd be willing to port this post to the HTC Droid Incredible 4G LTE device section?
Only minor modifications:
HTC One X/XL to HTC Droid Incredible 4G LTE
Android Forums link
Click to expand...
Click to collapse
Would that go over well? They don't know me at all over there.

iElvis said:
Would that go over well? They don't know me at all over there.
Click to expand...
Click to collapse
Ah, well if spend most all your time in One X/XL then I understand if you prefer to keep the writeup for this crowd. I did enjoy the read and am glad I stumbled across it.

mdmower said:
Ah, well if spend most all your time in One X/XL then I understand if you prefer to keep the writeup for this crowd. I did enjoy the read and am glad I stumbled across it.
Click to expand...
Click to collapse
I'm happy to share it; I was just concerned that having this as my first post over there might come across as somewhat obnoxious.

iElvis said:
I'm happy to share it; I was just concerned that having this as my first post over there might come across as somewhat obnoxious.
Click to expand...
Click to collapse
If you precede the post with: "mdmower requested this post be ported to the fireball community" you'll run into no issues.

mdmower said:
If you precede the post with: "mdmower requested this post be ported to the fireball community" you'll run into no issues.
Click to expand...
Click to collapse
Okie dokie.

A excellent post.
Your questions and count are very good! Appreciate your sense of humour making a point that is very valid.
Will be reading more.
Thanks again for the support.
David

lol :laugh: awesome post! Nice touch with the gif's bro, freakin Classic!

Hi, I have a Galaxy A5 2017 and have a question about an update and about storage.

Hi, I have a Galaxy A5 2017 and for the "May 2019" update (yes I'm a bit behind lol) it says that you can't go back to a lower version, so I just wanted to make sure that loading this update, or any of the later updates, won't prevent me from having the option to root the phone if I decide to do that someday. It isn't under warranty anymore anyways. Although, (and I could be wrong) but I'm guessing you can't get any further updates once you root it? Also I don't know if you can use either the Galaxy Store, or the Google Play Store once rooted.
My second, sixth?? question (DOH!) is about moving apps over to the external card. Despite doing this, it must be keeping a fair amount of data on the internal because it's almost full. Is there a way to see how much of an app has been offloaded to the external card and how much is still on the internal? I guess I should also ask, if there is an app that can move more over without needing root?
Thanks. Yea... that was more then 2.............. :/
DM

Darkmatterx76 said:
Hi, I have a Galaxy A5 2017 and for the "May 2019" update (yes I'm a bit behind lol) it says that you can't go back to a lower version, so I just wanted to make sure that loading this update, or any of the later updates, won't prevent me from having the option to root the phone if I decide to do that someday. It isn't under warranty anymore anyways. Although, (and I could be wrong) but I'm guessing you can't get any further updates once you root it? Also I don't know if you can use either the Galaxy Store, or the Google Play Store once rooted.
My second, sixth?? question (DOH!) is about moving apps over to the external card. Despite doing this, it must be keeping a fair amount of data on the internal because it's almost full. Is there a way to see how much of an app has been offloaded to the external card and how much is still on the internal? I guess I should also ask, if there is an app that can move more over without needing root?
Thanks. Yea... that was more then 2.............. :/
DM
Click to expand...
Click to collapse
If you plan on rooting the device, don't apply any of the stock updates unless you can verify that the update does not contain a bootloader that is locked, if it's locked, you won't be able to root the device via TWRP or Magisk unless there is a way to unlock the bootloader. If you apply the update and it locks your bootloader and can't be unlocked after that, you won't be able to downgrade the firmware to unlock the bootloader, you'll be stuck with it.
If it can't be unlocked, the best you could hope for is that you get lucky and one of the one-click tools happens to have a exploit that works to root the device.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
If you plan on rooting the device, don't apply any of the stock updates unless you can verify that the update does not contain a bootloader that is locked, if it's locked, you won't be able to root the device via TWRP or Magisk unless there is a way to unlock the bootloader. If you apply the update and it locks your bootloader and can't be unlocked after that, you won't be able to downgrade the firmware to unlock the bootloader, you'll be stuck with it.
If it can't be unlocked, the best you could hope for is that you get lucky and one of the one-click tools happens to have a exploit that works to root the device.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks, but I would have no idea even where to go look to find out if there is a patch that is a "root killer" other than coming... here. Do you have a link or a site name I could google that has information like that?
Thanks!

Darkmatterx76 said:
Thanks, but I would have no idea even where to go look to find out if there is a patch that is a "root killer" other than coming... here. Do you have a link or a site name I could google that has information like that?
Thanks!
Click to expand...
Click to collapse
No, I don't know, I would search by using your model number and the version of the update, I would find threads and websites that have people that have installed the update and see if the threads or sites mention whether or not the update locks the bootloader, or ask someone in those thread or on those sites.
Other than that, it's complicated, you'd have to download the update on PC and extract it to get to the boot.img, if it has one in the update. Then you'd have to extract the boot.img itself to get to the files in the .img, then you'd have to look through certain files look for certain keys, tags and switches that indicate a locked bootloader. It requires understanding what you are looking at in order to tell.
Sent from my SM-S767VL using Tapatalk

again , not trying to butt-in @Droidriven because you're like the "Neo" of Q & A. but xda has a dedicated
forum/thread for the galaxy A series. here's the Q & A thread , might be a start/help :
https://forum.xda-developers.com/samsung-a-series-2017/help

mrrocketdog said:
again , not trying to butt-in @Droidriven because you're like the "Neo" of Q & A. but xda has a dedicated
forum/thread for the galaxy A series. here's the Q & A thread , might be a start/help :
https://forum.xda-developers.com/samsung-a-series-2017/help
Click to expand...
Click to collapse
Lol, again, informing them of what to look for and suggestions of what to look for. I don't always post links. I was, more or less, telling them how to figure it out instead of saying "look here".
I'm not a "quick answer for dummies" helper anymore, I'm a "help give you an idea of "how" to look, not, "where" to look". Learning "how" to look is the first step to finding answers, more important than the answer that is found.
Sent from my SM-S767VL using Tapatalk

& you right. that is a much better way. i'll follow your lead instead of 'spoon feeding'. the old "teach a man to fish ..... " is a much more positive way.:good:

While I totally understand that , especially looking at your post count (WOW), I tried programming and even scripting and I couldn't even script my way out of wet paper bag. Now, computers in general, fine. DOS, C64, also fine, but looking for clues in a download of the file? I wouldn't even know where to start.
I'll try the A Series forum. Sorry that I didn't see it first.
Thanks for trying, but my brain just shuts the door and says, "Um, no." lol
DM

Darkmatterx76 said:
While I totally understand that , especially looking at your post count (WOW), I tried programming and even scripting and I couldn't even script my way out of wet paper bag. Now, computers in general, fine. DOS, C64, also fine, but looking for clues in a download of the file? I wouldn't even know where to start.
I'll try the A Series forum. Sorry that I didn't see it first.
Thanks for trying, but my brain just shuts the door and says, "Um, no." lol
DM
Click to expand...
Click to collapse
I completely agree, I can barely scratch the surface when it comes to reading code and understanding which files, lines of code or their values/switches.
Glad you found the forum, I was aiming for the journey and the moment of discovery to be a bit more organic, the mind is more "in order" for what is found that way. It can get frustrating, but more experience and understanding is gain in such a manner. For all the headaches involved, it has its rewards. I hope you enjoy your experience here at XDA and come back to learn some more, maybe even help others with what you learn here.
---------- Post added at 09:02 PM ---------- Previous post was at 08:48 PM ----------
mrrocketdog said:
& you right. that is a much better way. i'll follow your lead instead of 'spoon feeding'. the old "teach a man to fish ..... " is a much more positive way.:good:
Click to expand...
Click to collapse
Exactly, my friend.
I'll admit, I know it isn't direct enough for those that are impatient and there are those that just want things to be easy. Time here at XDA has tempered my view towards helping in a direction that involves trying to lead users in a direction that teaches them something along the way. A lot of users are already burned out and frustrated when they finally come here, even if you give them the answers directly, they don't understand what they find and even brick their device because they attempted repairs before they knew enough about what was going on. Something they maybe could have avoided if they had taken a little more indirect path to their answer, a path that they might discover more information and understanding along the way. Understanding that helps them pull things off without a hitch, maybe.(this user isn't dealing with repairs, but it's an example)
At the same time, I don't leave them hanging, I nudge them along the way with more defined help, if they continue to ask questions when they don't understand, but not if they seem like they want someone to just make it easy for them by doing all the work.

Droidriven said:
I completely agree, I can barely scratch the surface when it comes to reading code and understanding which files, lines of code or their values/switches.
Glad you found the forum, I was aiming for the journey and the moment of discovery to be a bit more organic, the mind is more "in order" for what is found that way. It can get frustrating, but more experience and understanding is gain in such a manner. For all the headaches involved, it has its rewards. I hope you enjoy your experience here at XDA and come back to learn some more, maybe even help others with what you learn here.
Click to expand...
Click to collapse
Thanks. I remember watching a co-op student get down over something she was having a hard time getting. I showed her some of my early attempts at making frozen soap bubbles (I do photography), including shots of ones at the beginning that were a complete and total loss. It took about 4 outings (it has to be -15c) and getting up at 5am to see if it actually got to -15c which it usually didn't, and I went from things like this,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I managed this, and man was I stoked! lol
Finally by the end I was shooting these.
I told her that the road to success is paved with the cobblestones of your failures, and that this is a necessary process for you to find the path to success.
It seemed to cheer her up. Hopefully it did.
DM

Help each other: firehose and eng bootloader publicly available

Thank you to everyone for patiently waiting - I know these forums have been dark and getting darker. I really hope that this will help bring some life back into the LG Forums; you guys deserve it.
Sorry about this, guys.
Not long ago, @ps3hacker3 and I got our hands on a firehose programmer for the Kona, and the engineering bootloader for the V60.
I created the post as I was under the assumption that we had a working method to provide the ability to unlock the device and root it. Over time as I looked more and more into it, a prevalent issue arose: Sahara refuses to communicate with us when trying to open the partition manager from QFIL.
The original process used on ps3hacker3's LMV600AM model utilized Medusa Pro, but as far as I can tell, I can't help but feel like I'm still missing a piece of this puzzle. Perhaps it's as simple as a setting configuration, and perhaps it's as complex as an entire other part of this process that I'm missing.
Nonetheless, I can leave you with two things.
A) The firehose, one way or another, despite what anybody says or doubts about it, worked on ps3hacker3's phone. Screenshots as proof are available deeper into the thread.
B) The engineering bootloader worked just as well.
I apologize for thinking that I'd gotten you halfway there, and for prematurely creating a thread that posed answers without being able to follow through on the process. In acknowledgement of the time and amount of workload and stress this project and the Stylo 6 projects have taken up in my life, I don't feel that I have the capacity to continue leading any of these projects anymore.
I would still take everything that anyone in this thread, seemingly right or wrong, said with a grain of salt and do your own research and ask people your own questions before concluding anything. It's nothing personal to do with anybody, it's just the best advice that I can give you based off of the situation. I didn't learn anything by taking everybody's word for it. Even if you're wrong at first, or the first hundred times, just keep doubting and testing theories. Keep wondering. Nobody knows everything and even well-established concepts may not be fully fleshed out, especially in the world of consumers and developers attempting to use software and files from OEMs and other manufacturers that is meant to remain unbeknownst to us. There's a lot I don't know, and a lot everyone doesn't know.
Thank you for being here with me on this journey.
I hope that the files can still make themselves useful - I have full confidence that they do.
Regardless, someone I would feel more comfortable not naming due to a recently closed thread was using them to unlock phones for high prices for people. Skipping over the drama, I just wanted to make them available for everybody. I suppose I've done my part, so please take this into your hands and give it all you've got.
The original post contents are in a dropdown below. I advise you to not blindly follow through with all of it.
It's up to you guys now - do your best.
Stay hopeful, and question everything. All the time.
Haise
Spoiler: Original post contents
NOTE:
Apparently, I overlooked a detail as I didn't think it was necessary. QPST was not used here, but rather a patched Medusa that can be found here.
The way this worked was complicated and I overlooked the fact we do not have a patched Medusa.
QPST is apparently unsuccessful at the moment.
I am working on a fix for this.
If anyone has any success with a specific QFIL or QPST version then please be sure to let us know so that I can update the post.
We have the files - hardest part is over. Now we just have to be able to use them.
Apologies to everybody who ran into troubles.
I am testing on the T-Mobile variant as soon as we're able to.
It's over.
Enter 9008:
Qualcomm USB 9008 drivers should be installed prior to this operation. These can be retrieved below, inside the archive along with the necessary files.
Your phone must be plugged into the computer prior to the rest of the process.
With your phone on, hold volume down and power. After about ten seconds, continue to hold power and volume down, while also spamming volume up. This works much better if your device is powered on and your screen is on, as a bar will show up on the bottom and you can initiate the volume up spamming as soon as the bar drains to empty.
As soon as the screen turns black, let go of all of the buttons. The device should appear in 9008 mode in the Device Manager.
I'm going to be honest, guys - I've been working on the Stylo 6 since January and the V60 from some random point a few months ago. From here my memory's foggy, I'm tired, and you guys are smart, so if someone needs help, then help each other, okay?
Generally speaking you can use QPST or another piece of software that can interact with Qualcomm devices in 9008 mode the patched Medusa from the link at the top of the post to flash the engineering bootloader. You will use the firehose attached below along with the eng boot for this.
I don't know why it is that Medusa is required. It is unfortunate.
The previous V40 thread is practically identical and has a lot of prior support and questions answered that, the vast majority of the time, can be adapted to the current model and files. They also cover many potential problems that I did not, and it is strongly recommended that you review that thread.
Be kind. Be patient. Be courteous. Share.
And enjoy.
Haise
Special thanks to @ps3hacker3 for participating in my Discord server and working with me last second on managing to obtain the files.
Donate to him and his partner here: PayPal.me

gonna try it right now since i just unbricked my V60 that i was attempting to unlock the way i did my stylo6's and K51

Thank you sir
Can we flash the V35 engineering bootloader?? From the other thread you mention???

Any word on getting this to work on T-Mobile variant? V40 notes said it does not work on T-Mobile.

krissrmx said:
Thank you sir
Can we flash the V35 engineering bootloader?? From the other thread you mention???
Click to expand...
Click to collapse
No, just the bootloader within the archive posted here

memnon79 said:
Any word on getting this to work on T-Mobile variant? V40 notes said it does not work on T-Mobile.
Click to expand...
Click to collapse
I'm not sure. I have the TMO and I'll be trying I'm a little while. I'll update the post to let everyone know so be sure to keep an eye on it

It's my understanding people are having trouble with QPST.
We used a patched Medusa and it seems unfortunately that it was necessary. I'll be updating the post shortly.

haise.zero said:
I'm not sure. I have the TMO and I'll be trying I'm a little while. I'll update the post to let everyone know so be sure to keep an eye on it
Click to expand...
Click to collapse
Thanks for all the hard work!

This is the firehose file of ZTE phone,not support LG phones.
CN = QCT Attestation CA
O = QUALCOMM
OU = General ztemt attestation
L = San Diego
S = CA
C = US
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

haise.zero said:
It's my understanding people are having trouble with QPST.
We used a patched Medusa and it seems unfortunately that it was necessary. I'll be updating the post shortly.
Click to expand...
Click to collapse
Will you repost the Medusa link?

ebowen 747 said:
Will you repost the Medusa link?
Click to expand...
Click to collapse
There is not Medusa link as of the moment. There was an oversight and I'm looking into this.
QFIL and QPST aren't working either.
Some patience please

wannan1985 said:
This is the firehose file of ZTE phone,not support LG phones.
CN = QCT Attestation CA
O = QUALCOMM
OU = General ztemt attestation
L = San Diego
S = CA
C = USView attachment 5347163
Click to expand...
Click to collapse
Except that it did.
So... say what you will. I genuinely witnessed this file get used. Speculate about the details with someone else. I'm not here to debate. I'm here to provide.
Next time consider asking some questions instead of pointing a finger and implying that I'm wrong because of some information you have without actually elaborating.
I wouldn't be here if it didn't actually work.
<3
EDIT:
Hey, also, your port 8888 is open, and thus so is your site login.
Also, your site is really broken.
Best of luck

For devices that have replaced the CPU, the firehose signature is not verified. You can view it through *#546368#*model#-SVC Menu-MID Info-IMPL
Thank you very much for your reminder, my website is no longer operating.

wannan1985 said:
For devices that have replaced the CPU, the firehose signature is not verified. You can view it through *#546368#*model#-SVC Menu-MID Info-IMPL
Thank you very much for your reminder, my website is no longer operating.
Click to expand...
Click to collapse
This further solidifies my theory, luckily enough. It doesn't pass attestation, but it does function correctly.
So... that's it.
Working on getting the firehose to work tonight. I do know that it does indeed function because we have someone who has an unlocked bootloader because of it.
It may not officially support the V60 due to it being designed for ZTE, but it does functionally support it. Perhaps it's because this is the Kona processor, which is the prototype version of the processor. Either way, it functionally supports it, and the obstacle of getting around attestation is much less daunting to me than not having the files we need or knowing how to unlock the device.

haise.zero said:
Except that it did.
So... say what you will. I genuinely witnessed this file get used. Speculate about the details with someone else. I'm not here to debate. I'm here to provide.
Next time consider asking some questions instead of pointing a finger and implying that I'm wrong because of some information you have without actually elaborating.
I wouldn't be here if it didn't actually work.
<3
EDIT:
Hey, also, your port 8888 is open, and thus so is your site login.
Also, your site is really broken.
Best of luck
Click to expand...
Click to collapse
Bro, this is a fake, the original firehose has a different hash, this one is not from LG.
His phone will not accept, neither through jellyfish, nor through QFIL, you can not tr
It is very important that the hash matches what is required.y.d.y.

haise.zero said:
Thank you to everyone for patiently waiting - I know these forums have been dark and getting darker. I really hope that this will help bring some life back into the LG Forums; you guys deserve it.
NOTE:
Apparently, I overlooked a detail as I didn't think it was necessary. QPST was not used here, but rather a patched Medusa that can be found here.
The way this worked was complicated and I overlooked the fact we do not have a patched Medusa.
QPST is apparently unsuccessful at the moment.
I am working on a fix for this.
If anyone has any success with a specific QFIL or QPST version then please be sure to let us know so that I can update the post.
We have the files - hardest part is over. Now we just have to be able to use them.
Apologies to everybody who ran into troubles.
I am testing on the T-Mobile variant as soon as we're able to.
It's over.
Enter 9008:
Qualcomm USB 9008 drivers should be installed prior to this operation. These can be retrieved below, inside the archive along with the necessary files.
Your phone must be plugged into the computer prior to the rest of the process.
With your phone on, hold volume down and power. After about ten seconds, continue to hold power and volume down, while also spamming volume up. This works much better if your device is powered on and your screen is on, as a bar will show up on the bottom and you can initiate the volume up spamming as soon as the bar drains to empty.
As soon as the screen turns black, let go of all of the buttons. The device should appear in 9008 mode in the Device Manager.
I'm going to be honest, guys - I've been working on the Stylo 6 since January and the V60 from some random point a few months ago. From here my memory's foggy, I'm tired, and you guys are smart, so if someone needs help, then help each other, okay?
Generally speaking you can use QPST or another piece of software that can interact with Qualcomm devices in 9008 mode the patched Medusa from the link at the top of the post to flash the engineering bootloader. You will use the firehose attached below along with the eng boot for this.
I don't know why it is that Medusa is required. It is unfortunate.
The previous V40 thread is practically identical and has a lot of prior support and questions answered that, the vast majority of the time, can be adapted to the current model and files. They also cover many potential problems that I did not, and it is strongly recommended that you review that thread.
Be kind. Be patient. Be courteous. Share.
And enjoy.
Haise
Special thanks to @ps3hacker3 for participating in my Discord server and working with me last second on managing to obtain the files.
Donate to him and his partner here: PayPal.me
Click to expand...
Click to collapse
i have verizon variant
Operation : Read Information
Checking for existing devices...Not Found
Turn Off phone, hold Vol UP + Vol DOWN and insert USB cable.
Some phones may need Special Boot Cable or TestPoint for EDL mode.
Found Port : Qualcomm HS-USB QDLoader 9008 (COM4)
Driver Info : Network Connect, qcusbser.sys, 3.0.0.0
Connecting to phone...OK
Waiting for response...OK
Init Handshake Sequence...OK
Hardware ID : E1300C00 [SD8250] 00003100
OPK_DATA : B7CD248E4DC4A3CAF07E12F2E1F331E3176FCF864871446CD204625C74D9F94A
Initializing Protocol...OK
Sending Loader [prog_ufs_firehose_sdm8250_ddr.elf]...Error
Please use correct loader and check USB port / cable.
Operation Finished.
QcFire Ver. 6.8

haise.zero said:
This further solidifies my theory, luckily enough. It doesn't pass attestation, but it does function correctly.
So... that's it.
Working on getting the firehose to work tonight. I do know that it does indeed function because we have someone who has an unlocked bootloader because of it.
It may not officially support the V60 due to it being designed for ZTE, but it does functionally support it. Perhaps it's because this is the Kona processor, which is the prototype version of the processor. Either way, it functionally supports it, and the obstacle of getting around attestation is much less daunting to me than not having the files we need or knowing how to unlock the device.
Click to expand...
Click to collapse
i have a lg v60 verizon variant frp locked

Moto G. said:
Bro, this is a fake, the original firehose has a different hash, this one is not from LG.
His phone will not accept, neither through jellyfish, nor through QFIL, you can not tr
It is very important that the hash matches what is required.y.d.y.
Click to expand...
Click to collapse
Seriously we are going down this road of nonsense^?
Ok my turn, listen up. The guy he is refering to that he has seen this firehose and ENG boot work on a V60 (AT&T model) is me, I was let known that numerous people were grabbing their pitchforks and calling this fake.
Im no DEV on android or any of the sort, Im just a guy that paid some other dude 20 bucks to root my phone but on the side of things without him knowing I hijacked all the files that he used to root my phone and then proceeded to send @haise.zero here everything that I acquired and every detail I could remember while I was on the phone with him through the process to see if I can get exactly the two files posted above from him.
I have no idea why or how that firehose above works, Thats not my part in this. I dont know, they only I can say is STOP SAYING THIS IS FAKE!! Sit down and listen, this is not fake. This is not some childish scam, This is real. Im literally HOLDING the phone that is rooted/unlocked. IT WORKS, Period. Trying to counter argue that when im holding the phone it was done to and watched right in front of my eyes on my personal computer (With this mysterious cracked medusa software via an octoplus box) makes you look foolish.
You want more proof, You hit me up on discord. Ill voice call you and send you anything and everything you need or want to see for your own eyes. Ill be here waiting for more counter arguments.

Hash validity is important, and I understand that QFIL doesn't like it.
On the other hand, its functionality does work. As seen above, and as witnessed by myself, it does work.
The signature was not for LG, it was for ZTE. Qualcomm's signature for the other company is not to be completely ignored.
The ZTE firehose, if attestation can be worked around, is full and well capable of flashing our device's bootloader.
Medusa Pro was used by the original person. This is our present issue. We are working on it and the original XDA post will be expanded as soon as we have this working.
I appreciate the concern, but instilling fear in people that this is guaranteed to brick their device or that it's completely unsupported is really not helpful whatsoever.
Thank you.

ps3hacker3 said:
Seriously we are going down this road of nonsense^?
Ok my turn, listen up. The guy he is refering to that he has seen this firehose and ENG boot work on a V60 (AT&T model) is me, I was let known that numerous people were grabbing their pitchforks and calling this fake.
Im no DEV on android or any of the sort, Im just a guy that paid some other dude 20 bucks to root my phone but on the side of things without him knowing I hijacked all the files that he used to root my phone and then proceeded to send @haise.zero here everything that I acquired and every detail I could remember while I was on the phone with him through the process to see if I can get exactly the two files posted above from him.
I have no idea why or how that firehose above works, Thats not my part in this. I dont know, they only I can say is STOP SAYING THIS IS FAKE!! Sit down and listen, this is not fake. This is not some childish scam, This is real. Im literally HOLDING the phone that is rooted/unlocked. IT WORKS, Period. Trying to counter argue that when im holding the phone it was done to and watched right in front of my eyes on my personal computer (With this mysterious cracked medusa software via an octoplus box) makes you look foolish.
You want more proof, You hit me up on discord. Ill voice call you and send you anything and everything you need or want to see for your own eyes. Ill be here waiting for more counter arguments.
Click to expand...
Click to collapse
i need for frp lg v60 verizon model i test a lot od trick nothing work