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
Related
I have searched, and have not found any information that can help me.
I have a touch that the Service Centre want £90 to repair - new motherboard. Is this fixable with a jtag - If so, does the Holly Gates Schematics for a Jtag Dongle work here?
Has anyone successfully JTAG'd an ELF? If so, was it due to a similar circumstance as myself?
Anything I have come across goes to Russian sites - I'm not russian, nor can I read it.
I have seen posts for other devices, but these seem to all be based on a Samsung Chipset, apposed to our OMAP devices?
Any help would be great, even if it is just to go read a post that I have missed when searching.
Stu
Hey, not sure if anyone would care all to much.
I have found a jtag setup I am curently preparing to use, I am going to hopefully be trying to do this tomorrow. I am working on a guide as I do it - as I haven't been able to find one. If this would be useful to anyone let me know, and I will upload it as soon as I have tested it on my broken elfin to make sure it works!
Hey mate, we care and keep us posted with any results.
Good luck!
hey just come into a bit of a stuck point. I have no images to support this.
I am trying to fix the cables to the main board on the jtag points. Aout 5mm wide. I dont really want to solder them on. Does anyone have any suggestions on how best to affix them? I'll try and get some pictures up tomorrow when i can.
Stu
Unable to do pictures today, I will do them tomorrow hopefully on my lunch break, so people can make suggestions.
I am a little scpetical about if this will work. I do not know the history of the device I am tinkering with, but I hope this will fix it.
If anyone has a broken elf they would like to part with for me to test, that would be great (I would pay ofc)
Pic
Hey,
Please see attached image.
This points out the JTAG test points, labelled to what they do (in theory) and what pin they connect to the JTAG device from the LPT cable.
I think these are very small to be able to tape them on, I also do not think that they would give a good enough connection. I am going to try to solder the cables on tonight - but in the mean time, if anyone has any suggestions, please feel free to let me know. Any ideas are good!
Stu
Hi captainstu72,
I have a completely dead HTC Touch P3450. Really dead. Even when I plug the charger to the device, the orange light (as a sign that the phone is charging now) can not light on.
A service man asked me to replace the machine for USD 80, as he said we can not do j-tag to HTC ELF
Your thread is very exciting. Please keep posting, I'll follow this thread.
Thanks
bombom81 said:
Hi captainstu72,
I have a completely dead HTC Touch P3450. Really dead. Even when I plug the charger to the device, the orange light (as a sign that the phone is charging now) can not light on.
A service man asked me to replace the machine for USD 80, as he said we can not do j-tag to HTC ELF
Your thread is very exciting. Please keep posting, I'll follow this thread.
Thanks
Click to expand...
Click to collapse
Hey bombom81,
I'm glad this can be useful for others. I just want to make sure that people don't get their hopes up too soon, thats the thing, I don't know if it is definately able to work, but I know it has been done on other phones with a very similar chipset to ours.
If I have any major break through tonight, I will definately be doing a write up on it tomorrow in my lunch, and If you'd like I can PM you when done so you can give it ago.
Your ELF sounds as though it is in a similar state to mine, so hopefully, if I get this fixed, it may well work on yours!
Stu
captainstu72 said:
Hey bombom81,
I'm glad this can be useful for others. I just want to make sure that people don't get their hopes up too soon, thats the thing, I don't know if it is definately able to work, but I know it has been done on other phones with a very similar chipset to ours.
If I have any major break through tonight, I will definately be doing a write up on it tomorrow in my lunch, and If you'd like I can PM you when done so you can give it ago.
Your ELF sounds as though it is in a similar state to mine, so hopefully, if I get this fixed, it may well work on yours!
Stu
Click to expand...
Click to collapse
Yes..I had this problem months ago and I've made a thread for it :
http://forum.xda-developers.com/showthread.php?t=582913
Unfortunately, every suggestions I got from people here didn't work in my device. And I could not even claim a warranty for it as the seller said that the product warranty is already expired too long ago (in the end I knew that the product was his present from his office, and when he said it is new, means that, It is new because He never used it...LOL, not "new" from the factory). So I just keep it in my cupboard.
I think It will be more valuable for others if we discuss here, on your thread, than PM, as I think there are many people are having the same problem like us (as many as I can find after I google "Repair Totally Dead ELF" )
Please, kindly also check this thread : http://forum.xda-developers.com/showthread.php?t=602233
This guy also found a similar thing like yours. I actually don't know a thing about JTAG. In the future, please forgive me if I might ask you some questions about it and I hope you don't mind about my questions.
Thanks for your kind to share your experience with us, I'll keep watching this thread and hopefully you'll be success with your experiment so it can bring the joy for all of us.
Best Regards,
Bom81
bombom81 said:
Yes..I had this problem months ago and I've made a thread for it :
http://forum.xda-developers.com/showthread.php?t=582913
Unfortunately, every suggestions I got from people here didn't work in my device. And I could not even claim a warranty for it as the seller said that the product warranty is already expired too long ago (in the end I knew that the product was his present from his office, and when he said it is new, means that, It is new because He never used it...LOL, not "new" from the factory). So I just keep it in my cupboard.
I think It will be more valuable for others if we discuss here, on your thread, than PM, as I think there are many people are having the same problem like us (as many as I can find after I google "Repair Totally Dead ELF" )
Please, kindly also check this thread : http://forum.xda-developers.com/showthread.php?t=602233
This guy also found a similar thing like yours. I actually don't know a thing about JTAG. In the future, please forgive me if I might ask you some questions about it and I hope you don't mind about my questions.
Thanks for your kind to share your experience with us, I'll keep watching this thread and hopefully you'll be success with your experiment so it can bring the joy for all of us.
Best Regards,
Bom81
Click to expand...
Click to collapse
Hey,
Likewise, every suggestion I could find had no luck, which I why I decided to dig deeper.
I did come across GallegoT's thread, however, I sent him a PM to see if he had got anything sorted, but I have never heard back - So I created a new one.
I was going to keep this thread posted, don't worry, I was only going to PM you when it was finished - to save you keep checking it
Had a few issues with it last night, tried soldering to the board, but my soldering iron doesn't get hot enough, hasn't got a thin enough tip, and my hands weren't steady enough - Also the wires I was using were fairly wide, I have swapped these for a thinner Kynar wire, and will more then likely be remaking the whole of my setup to make it easier.
Just so you have an idea - I currently have an LPT (male to male) cable which I have taken the end off, and soldered wires to 2 3 4 6 11 and 18-25. 18-25 link then into one wire, as this is to ground the device. 2 3 4 6 and 11 are connected to 100Ω resistors each. These are then connected to wires, which are ready to be connected to the device.
Thats the basics of the device - I do not have an image of what I have planned out avaliable, but you can get the idea of it from what is in this post, and using my image posted earlier.
Maybe you guys have better tools - soldering equipment etc then I do.
When this is done you need to run a program called HJtag, and NoIce. I have an idea on what to do for these, however, I have not tested it yet to want to post it on here.
Like I have said though, I will be making a guide that is as full as I can.
I will try some more tonight, to get the cables connected, and hopefully then will be able to give the whole process a go.
Thanks for your interest in this thread, even if I only manage to help one person, at least then I feel as though I will be giving something back to the community on this site.
(I'll point out now - I did not have a clue about Jtag before now - but I also have some links I will post which make some interesting reading!)
Stu
Hey to anyone who is still watching this.
I have just got my elfin all wired up, ready to go, circuit is fully continuous and there are no bridges (I haven't soldered for more then 8 years!)
However, I have been a bit stupid, my pc doesn't have a parallel port. I'm going to buy one tomorrow and get going - very annoyed about this set back, i'm such an idiot for not checking!
I'll try it tomorrow night hopefully, worst case would be friday/saturday - A long time since starting this projct, but my hopes are high and I really hope I can help some of you guys out there!
Just thought I should update you all, I don't want this thread to become dead... like our elfs
Stu
LOL..no need to worry that your thread is dead.
I'll visit this thread everyday to see how it's going
BTW...do we really need the LPT Socket to do the JTAG? if so, then I will have to ask my IT man in my company to find me a "no-used" LPT socket, lucky I have an old Pentium 3 PC that I might be able to use it for this JTAG matter.
Please update the step-by-step tutorial here with photos so I can follow you easily. FYI, I am blind in this JTAG matter, so please do not mind to answer my next "silly questions".
Keep going! Thanks
Parallel is the only interface I have found to do it on - I would have much prefered usb or something more up to date, but we can't always have what we want.
Below are a few links that I read through before doing anything, just so I could get a vague understanding. I'm workign on the guide today on my lunch - the last part will have to be in theory.
Jtag Introduction
Someone Jtag'd an Ipaq (not the same but the concept)
Has some links to JTAG
Program we will be using for the jtag
NoIceDebugger - A program I will be using
What I think our Processor is
OMAP 850
Again, I will be making a an actual guide, this is just some reading before hand that i did that may be useful!
Stu
hey, well, i have a parallel port and have attempted the jtag.
It didn't work.
My guess is i was using too long cables, or something has come loose. My continuity tester has now died so i will be testing again on the weekend.
I'm going to post the guide i am working and what i did tomorrow. Maybe someone (bom81) would be able to give it a go and do well as i'm sure he will.
Sorry for the failure, but i am really optimistic that it will work, and that it didn't only because of something i may have wired wrong that someone else does right. I'm going to try and get a thirc elf to break and fix as well as it may just be the one i am doing is beyond repair.
Bom81, if you give this a go, good luck. I'm sure you'll have some luck!
If anyone else tries when i have the guide up, please please let this thread know, even if it doesn't work.
Stu
Hi Stu..
Can you give me the russian forum that explain about this jtag on HTC Touch.
I'm going to learn it there.
BTW, how long have you made the cable? have you cut it shorter and try again the connection?
Try to read this thread : http://forum.gsmhosting.com/vbb/f98/htc-elf-dead-after-wrting-elfin-rom-650359/
This guy has the same problem with us but finally (or luckily?), the device could come to Bootloader mode. I'm going to try to PM him, so he can explain how did he get the device work.
Thanks for your try.
Regards,
Bom81
This is for the wizard - same omap 850 http://pda2u.ru/forum/index.php?showtopic=348
I can't find my link for the touch, it may be on my home pc, but it was on the same website iirc.
Cable was about 50cm's - Too long, so I am remaking it to around 15cms tonight, but will be fun as I do not have my continuity tester to make sure that the circuit has the right resistance etc. before I think I was going over by too much due to cable length.
I have started the guide, I just need a few files off my home PC, so I will do this tonight again.
It really annoys me when other threads/sites do not put everything down they have tried, the internet is for information, not for saying, "ha, i've done it!"
I'll try again tonight and tomorrow, I think I have my LPT PCB sockets waiting to be collected, all the way from China, so this will be easier for me to do ultimately.
I haven't yet given up hope, and I'm sure that if I get my document made, someone will be able to tweak it and further help us.
I just don't know how many people are using the Elf's anymore, its fine there being a thread saying we have 900's htc touch's, but how many still use them and are active on this community.... but I digress.
I am really sorry that I am not good in Electronic thing, nor that I know how the electronic equipment works.
But I will try to learn from the website url you provided. Afterall, my HTC is already dead, it will not be a big problem if I make some experiments on it. If I'm lucky enough, I might wake a Frankenstein from his dead. LOL !!
Thanks,
Bom81
JTAG HTC device
Thanks first of all for your effort captainstu72 and bombom81, very interesting thread.
I am also in the same situation - having a bricked device (flashed wrong ROM and/or wrong carrier) and thus also interested in getting a serial cable hooked up to it no bootloader - no reset. The device is therefore software-wise dead.
I would therefore also love to try your procedure to getting a JTAG connection to the device. I have not been dealing with soldering on electronic devices since I did this on commodore 64... quite a few years ago as you imagine but therefore even more exciting.
I will check this thread and get a serial cable. Oh does the H-JTAG Software also run from linux since I only work on linux on this machine?
Thanks in advance and let me know if I can be of any help in this.
Oliver
Hi Stu and ITCons (welcome to the thread)
I've read the Russian website and have made a translation of the thread from Russian to English using Google Traslate.
Unfortunately, as I said before, I have no competency in electronic, but I'll try to learn.
All credits for the compiled document will go to user id : MEDUSH and ARCC in the Russian Forum (PDA2U.Ru), as they mentioned this document might be reprinted by their copyright.
Please have a read to the document I attached...I'll come back if I'm finding out something (as this week I'll face my busiest week of the month, there are some reports in my daily jobs that I need to prepare to my Boss...LOL).
Thanks for your kind attention.
Regards,
Bom81
Thank you very much Bom81
I have found another thread on this forum as well in the gene section, which shows how they did it on the gene too (omap 850 processor as well) I have posted on there to ask if anyone can relink to the revised download, but so far, there has been no update.
I'm going to go through what you have posted tonight bom, it matches most of what I was going which is always good (from my point of view, as it means i wasn't chasing a lost cause)
Sorry for not posting the guide yet, i'm slacking! But now, obviously, it does not matter so much as bom has posted an excellent guide in his post.
ITcons - I have had a (very) quick look, I don't think HJTAG runs on linux, although I would be interested to see how it would work in cedega/wine (this is not something I can test personally), I hope it would be able to use the LPT ports etc correctly - but again, nothing I really have a whole lot of experience about.
I'll see how it goes tonight, hopefully I should have remade my circuit again, and will be ready to test once more! - This time I am using an LPT PCB Socket - hopefully easier to do as there will be less in the way of resistance from excess cables.
Stu
I know that there are several other threads in other device's boards, and was wondering if we could get started here in order to make life a little more convenient and hopefully help out nubblies like myself. If there's a term that you need defined, ask it, and hopefully one of our more senior people will volunteer to answer it.
Here's mine to start:
"Red" CWM/"Green" CWM -
Bootloader -
PIT-
PDA-
Again, thanks to everyone who helps!
really though, if you took the time to type the thread
you could have just as easily typed each of those words in the search.....and got answers to all of those.
we have threads about all that here in the infuse forum.
American Standard said:
I know that there are several other threads in other device's boards, and was wondering if we could get started here in order to make life a little more convenient and hopefully help out nubblies like myself. If there's a term that you need defined, ask it, and hopefully one of our more senior people will volunteer to answer it.
Here's mine to start:
"Red" CWM/"Green" CWM -
Bootloader -
PIT-
PDA-
Again, thanks to everyone who helps!
Click to expand...
Click to collapse
I think it's a great idea, saves people who aren't android literate a lot of time. Some of the abbreviations, phrases etc. can be confusuing. Just...fill it now lol the thread is irrelevant without the info of each of those terms.
the2rrell said:
really though, if you took the time to type the thread
you could have just as easily typed each of those words in the search.....and got answers to all of those.
we have threads about all that here in the infuse forum.
Click to expand...
Click to collapse
ok, so do you care to come down off your high horse and deign to help someone out, or are you just going to ignore the fact that this is the question and answer board?
xIC-MACIx said:
I think it's a great idea, saves people who aren't android literate a lot of time. Some of the abbreviations, phrases etc. can be confusuing. Just...fill it now lol the thread is irrelevant without the info of each of those terms.
Click to expand...
Click to collapse
Exactly. Was kind of hoping someone would fill it out, then I'd either edit it as it came up, or add terms or whatever.
American Standard said:
I know that there are several other threads in other device's boards, and was wondering if we could get started here in order to make life a little more convenient and hopefully help out nubblies like myself. If there's a term that you need defined, ask it, and hopefully one of our more senior people will volunteer to answer it.
Here's mine to start:
"Red" CWM/"Green" CWM -
Blue recovery = Samsung recovery, not CWM (at least in all cases on our phones)
Green = ROM Manager-installed CWM 2.x, which is not Voodoo-lagfix-aware and WILL cause problems if you try to flash anything with it on a device that has Lagfix enabled
Red = Voodoo-aware CWM 2.x, basically the standard CWM version you should be flashing from on the Infuse. If it's anything but red, you'll probably be dead, with one exception:
Orange = CWM 4.x which is included with CM7/MIUI. If you're running CM7 or MIUI, CWM will be orange not red.
Bootloader - In literal terms, bootloader is code that is executed before any Operating System starts to run. The concept of bootloaders is universal to virtually all Operating systems that inculcates operating systems on your PC, laptop, smartphones, and other such devices. Bootloaders basically package the instructions to boot operating system kernel and most of them also have their own debugging or modification environment. As the bootloader kicks off before any piece of software on your device, it makes it extremely processor specific and every motherboard has it’s own bootloader. This is one reason that all Android phones have different Custom ROMS developed due to high variance of processing hardware present on the device. The iDevices running iOS somewhat share the same hardware specs and hence you don’t see much variance in their bootloaders.
PIT- this file repartitions your internal sd card via odin or Heimdell, i think
PDA- and this should be the main system file/rom or whatever that you flashing, like .tar files and what not.
Again, thanks to everyone who helps!
Click to expand...
Click to collapse
There you have it......
bump for thanks! I appreciate it.
{
"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 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
I see people frequently using "brick" as an umbrella term for their device not working the way they want it to, whether this means bootlooping, crashing, failure to boot, etc.
I think it's important to clarify that the term comes from the saying "as useful as a brick", where a device is rendered to no more than an expensive paperweight.
Your device isn't bricked unless you are unable to do ANYTHING - i.e., display doesn't turn on, no response to USB, completely dead and dark.
If your device crashes while running, it's not a brick.
If your device crashes while booting, it's not a brick.
If you get an error message, it's not a brick.
If your device doesn't boot but ends up in bootloader or recovery mode, it's not a brick.
If you're able to send fastboot commands / go into recovery / use Odin, it's not a brick.
If you run into a problem, don't say your device is bricked unless it is COMPLETELY DEAD and doesn't respond to anything that you do.
Describe your problem in detail, including what happened to get to that point, and anything that you have tried to do to fix it. Remember Rule 3:
3. Post using a clear and descriptive subject and message.
You're most likely to receive a helpful answer to your question, if you use a short subject title that describes your problem and a message that explains in detail, what your problem is and what you've done to try solving it.
Click to expand...
Click to collapse
And, don't forget to read the Guide to Forum Etiquette.
Hope this helps.
V0latyle said:
If your device crashes while booting, it's not a brick.
Click to expand...
Click to collapse
V0latyle said:
If your device doesn't boot but ends up in bootloader or recovery mode, it's not a brick.
Click to expand...
Click to collapse
The above two scenarios is what we call 'Soft Brick'.
V0latyle said:
unless it is COMPLETELY DEAD and doesn't respond to anything that you do.
Click to expand...
Click to collapse
This is called 'Hard Brick'.
So you may consider rephrasing your post.
TheMystic said:
The above two scenarios is what we call 'Soft Brick'.
This is called 'Hard Brick'.
So you may consider rephrasing your post.
Click to expand...
Click to collapse
I kind of was going to comment this and on this....
It gets to murky gray area for most new, amateur, & some novice users when there's the term "soft brick" and that's when they may start to not differentiate circumstances when using the term "brick" -- starting to include everything under the term.
An explanation on the term "soft brick" and/or even the plea/argument to faze out the word because of it (not my stance, personally) can even be made....
P.S. A thought; you might even consider alluding to the also similar concept of "expensive paperweight" when explaining where the basis of the term "brick" came from...
TheMystic said:
The above two scenarios is what we call 'Soft Brick'.
This is called 'Hard Brick'.
So you may consider rephrasing your post.
Click to expand...
Click to collapse
I won't, because instead of "brick" it's simple enough to use something that is more accurate and descriptive: "crash", "boot failure", etc.
I explained that "brick" means your device is literally as useful as a smart device as a brick would be.
We can use separate terms without getting complicated.
simplepinoi177 said:
I kind of was going to comment this and on this....
It gets to murky gray area for most new, amateur, & some novice users when there's the term "soft brick" and that's when they may start to not differentiate circumstances when using the term "brick" -- starting to include everything under the term.
An explanation on the term "soft brick" and/or even the plea/argument to faze out the word because of it (not my stance, personally) can even be made....
P.S. A thought; you might even consider alluding to the also similar concept of "expensive paperweight" when explaining where the basis of "brick" came from...
Click to expand...
Click to collapse
Most instances of bricking are Soft Bricking. So a plea to faze out the term 'Hard Brick' and replace it with a much simpler term: 'Dead' would be better IMO.
A 'Dead' phone is one that doesn't respond to anything and is as good as a paperweight.
V0latyle said:
I won't, because instead of "brick" it's simple enough to use something that is more accurate and descriptive: "crash", "boot failure", etc.
I explained that "brick" means your device is literally as useful as a smart device as a brick would be.
We can use separate terms without getting complicated.
Click to expand...
Click to collapse
These terms haven't been coined by users. These terms have historically been used by online resources, including XDA, to mean what I mentioned above.
TheMystic said:
These terms haven't been coined by users. These terms have historically been used by online resources, including XDA, to mean what I mentioned above.
Click to expand...
Click to collapse
This is instruction, not debate.
V0latyle said:
This is instruction, not debate.
Click to expand...
Click to collapse
Then the more appropriate thing to do is to update the Etiquettes Page you linked in OP along with the XDA Forum rules.
V0latyle said:
I see people frequently using "brick" as an umbrella term for their device not working the way they want it to, whether this means bootlooping, crashing, failure to boot, etc.
I think it's important to clarify that the term comes from the saying "as useful as a brick", where a device is rendered to no more than an expensive paperweight.
Your device isn't bricked unless you are unable to do ANYTHING - i.e., display doesn't turn on, no response to USB, completely dead and dark.
If your device crashes while running, it's not a brick.
If your device crashes while booting, it's not a brick.
If you get an error message, it's not a brick.
If your device doesn't boot but ends up in bootloader or recovery mode, it's not a brick.
If you're able to send fastboot commands / go into recovery / use Odin, it's not a brick.
If you run into a problem, don't say your device is bricked unless it is COMPLETELY DEAD and doesn't respond to anything that you do.
Describe your problem in detail, including what happened to get to that point, and anything that you have tried to do to fix it. Remember Rule 3:
And, don't forget to read the Guide to Forum Etiquette.
Hope this helps.
Click to expand...
Click to collapse
Sorry I doubt it will happen, or happen any time soon.
The terms "Soft-Brick" and "Hard-Brick" are not only used here on xda.
They are widely used and found on other forums/message boards.
stack-exchange, reddit, ...
I myself learned the difference and have used the terms for at least a decade, if not more.
I some times forget 2000 is already two decades ago.
Though the years, I have come to read "bricked" as "soft-bricked" since I understand the difference between the two (hard and soft).
My question to you would be..
What would you prefer users to say when referring to soft bricking a device instead?
---
I am not trying to be argumentative.
Just if we start demanding that someone stops use a term, we need to give them an alternative term to use.
Cheers.
ipdev said:
Sorry I doubt it will happen, or happen any time soon.
The terms "Soft-Brick" and "Hard-Brick" are not only used here on xda.
They are widely used and found on other forums/message boards.
stack-exchange, reddit, ...
I myself learned the difference and have used the terms for at least a decade, if not more.
I some times forget 2000 is already two decades ago.
Though the years, I have come to read "bricked" as "soft-bricked" since I understand the difference between the two (hard and soft).
My question to you would be..
What would you prefer users to say when referring to soft bricking a device instead?
---
I am not trying to be argumentative.
Just if we start demanding that someone stops use a term, we need to give them an alternative term to use.
Cheers.
Click to expand...
Click to collapse
Just the facts; model, firmware and the problem.
Improper term use makes it harder to read/understand the post and make it less likely the OP will get a solution.
Screws up searches... which don't need to be more fractured than they already are.
Misuse of terms helps to degrade the overall integrity of the site and its usefulness.
blackhawk said:
Just the facts; model, firmware and the problem.
Improper term use makes it harder to read/understand the post and make it less likely the OP will get a solution.
Screws up searches... which don't need to be more fractured than they already are.
Misuse of terms helps to degrade the overall integrity of the site and its usefulness.
Click to expand...
Click to collapse
To a certain degree.
If a user posts a thread including "is my phone a brick" it will (should) show up in the search results.
---
If someone would post in the OnePlus 6T thread.
I tried to update Lineage on my phone.
Latest stock OOS, TWRP, blah, blah, everything else.
Now my phone boots to a black screen.
I can not reboot into recovery or bootloader.
The msm tool does not find my device.
Am I screwed?
Others that may or may not have a hard-bricked device would not find the post (and the answers) if they search for a "bricked" device.
So it would make searching for a way to recover a soft-bricked device more difficult.
Cheers.
PS.
That actually happens to me (sometimes) on my OnePlus 6T.
When something goes wrong, it boots into EDL mode but, if it not connected to a computer at the time EDL mode will not be detected by the computer.
So I have to boot my old MacBook into Win7. Open the msm tool, connect my 6T and manually force reboot into EDL mode via device key combo.
Then I can flash the last stock OOS image to my 6T.
blackhawk said:
Improper term use makes it harder to read/understand the post and make it less likely the OP will get a solution.
Click to expand...
Click to collapse
blackhawk said:
Misuse of terms helps to degrade the overall integrity of the site and its usefulness.
Click to expand...
Click to collapse
There are clearly two terms in use: Soft Brick and Hard Brick.
As I said above, soft brick is what people experience most of the time, and therefore they simply use brick to imply their device is alive, but stuck in a bootloop or boots back to fastboot/ recovery.
It is XDA that appears to change the use of this common terminology, and it still isn't clear whether this is an 'instruction' or a 'guide'. In either case, a Glossary of terms for XDA would be helpful.
TheMystic said:
There are clearly two terms in use: Soft Brick and Hard Brick.
It is XDA that appears to change the use of this common terminology, and it still isn't clear whether this is an 'instruction' or a 'guide'. In either case, a Glossary of terms for XDA would be helpful.
Click to expand...
Click to collapse
I took this (OP post/thread) more as a PSA than an instruction or guide -- but I do not wish to put words in OP/@V0latyle 's mouth....
There's already an "XDA Encyclopedia" that is not really oft used....so I wonder how effective/assistive/utilized a "Glossary of Terms for XDA" might be.......
simplepinoi177 said:
I took this (OP post/thread) more as a PSA than an instruction or guide -- but I do not wish to put words in OP/@V0latyle 's mouth....
There's already an "XDA Encyclopedia" that is not really oft used....so I wonder how effective/assistive/utilized a "Glossary of Terms for XDA" might be.......
Click to expand...
Click to collapse
This post will get lost as new posts get created. So if XDA wants some terms to be used in ways that is different from general practice, it has to put it up somewhere that people are more likely to find.
And I don't see the point of forcing a change that hardly makes a difference.
simplepinoi177 said:
I took this (OP post/thread) more as a PSA than an instruction or guide -- but I do not wish to put words in OP/@V0latyle 's mouth....
There's already an "XDA Encyclopedia" that is not really oft used....so I wonder how effective/assistive/utilized a "Glossary of Terms for XDA" might be.......
Click to expand...
Click to collapse
I still learn something new about xda almost every day.
---
Took a look at XDA-developer encyclopedia.
Of course there is thread (fourth in the list) Brick.
Cheers.
ipdev said:
there is thread (fourth in the list) Brick.
Click to expand...
Click to collapse
From the link given in the post:
{
"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"
}