Are devices with MediaTek chipsets unbrickable? - Android Q&A, Help & Troubleshooting

Hi everyone.
So I've been with this question in my mind for some time now... Are they really unbrickable? I have a ZTE Blade L3 on which flashed infinite times ROMs on it. Some completely bricked it - it couldn't even charge. It has a MT6582M processor on it. It was COMPLETELY bricked. And I always got it to work again. Never bricked it for good - and I did many stupid things on it, many experiments. And after a bit, SP Flash Tool would always flash stuff back to it even by flashing wrong ROMs on it.
I also believe I flashed a wrong ROM to a friend's Elephone P8000 B which has a MT6753 processor on it. I thought I had bricked it (this is why I think I flashed a wrong ROM on it) - but SP Flash Tool got back working after a few tries. I did what I wanted with the phone and it didn't brick.
So my thought is that ANY device with a MediaTek chipset with a ROM and a scatter file available and an always unlocked bootloader (preferably - as my Blade L3 had, I believe - since I never heard of this until weeks ago), might be unbrickable. I, supposedly, can do whatever I want on it and I'll always be able to unbrick it.
Is this true what I just wrote? If it is, then I'll try to never leave MediaTek powered devices.
Note: A thread confirmed this thought I had for some time until I found this thread, but it only says it about MT65xx devices, not all the others: https://forum.xda-developers.com/showthread.php?t=1943442 --> "Added on Nov 23, 2012 - MT65xx is truly UNBRICKABLE".
Note 2: Also....... After now reading back a bit of the thread, I found out I did exactly ALL the opposite they recommend there in caps and the phone always unbricked....... XD. So I'm a bit confused with all the careful people are about MediaTek powered devices when I was not careful (stupidly, I know), though it always worked. I have the phone since 2015 and stopped using it last year, but I believe I did the opposite of those things, even though I'm not completely sure. And again, never permanently bricked.
Thank you for any informations!

I'm not going to lie to you, your probably not going to get any other replies to the book you wrote above... I will answer your question however. There is not a single mobile device out there that cannot be unbricked as long as the issues that occurred to cause said brick remains at the software level. It don't matter what brand or carrier it is. If it is a software related issue then it can be fixed as long as you have the knowledge and tools required to do so. As for your experimentation using root, I have done many experiments myself and there are many many things you can do using root that will permanently brick your device. Sounds to me like you got lucky. Simple as that. I'll end this by saying, please do not post your entire relationship with your favorite phone in a single thread like you did. Nothing personal but many probably did not stay long enough to finish what you wrote. You have a valid question. However the rest was just unnecessary and to many, a waste of their time. Hope I helped.

Hi. I didn't even remember about this anymore. This last year I was told I write too much unnecessary things - just like you did. I've been trying to correct that and I believe I improved (no idea if much or not). When you said "the book you wrote" I got embarassed in advance because I knew what was going next, and when I scrolled up I got scared and even more embarassed and it's still increasing as I think more about it . Christ, how did I even post that. I'm very sorry........ I guess we learn as time goes by.... (hopefully haha). Hopefully now it's good enough. If it's still bad, I'll be happy to receive the advice, as I am with the one you gave. Thank you. For everything you said, actually.
Spoiler: Not needed, just curiosity of why I wrote it so big
EDIT: Just a small explanation of the why I wrote the text so big, which was I'd prefer to give all the informations right at the start so people can know exactly what was done and say things according to that. Instead of assuming I did things I might not have done and answer something that might not be correct in my case. But then I write a book and that's beyond stupid. So I've been trying to correct that. That's the wrong point of the view and I think I still need a bit more time, but hopefully I'm getting there - maybe I should start posting on Reddit hahaha. Posting things is not that old for me. Started a few years ago (21 years old - a bit late for my age, I guess, but I didn't go on Internet that much before).

My intent was not to embarass you. I apologize. I should have checked the date this was originally posted. I do hope i was able to answer your question though. That was my true intent.

Tofor said:
My intent was not to embarass you. I apologize. I should have checked the date this was originally posted. I do hope i was able to answer your question though. That was my true intent.
Click to expand...
Click to collapse
Ah no problem at all. Gotta be corrected in some way . That happens with me when I see an enormous stupidity made by me which I did not realize at the time - and this one is 5 months old, which puts it worse haha.
That shall work so I won't forget of not doing this again in the far future xD. Before, some people would tell me about and I'd notice it was a wall of text (like once a person told me). And I appreciate all those who warned me about it. Sooner or later I'll get to a decent amount of text, depending on the forum. I think I didn't know what a paragraph was, as a start xD (though, what you saw there was already an update....). It's still a big post, I think, but hopefully it's readable now. If it's not, I'll cut more of it.
But yes, you did answer the question. Thank you. But to complement it, if you remember, at least, what experiments with root can completely brick a phone? (So I know I won't try them, as a start, but it's also a curiosity.)

Well a good example of some things not to do is changing the system files to allow the device to operate at a level it was not designed to operate at. For example. Messing with the kernel to make the processor run at a higher speed, same goes for the RAM. This will cause it to overheat and will basically fry the system board. Also if you are not sure what you are changing then dont change them. Nothing like accidently changing the EFI settings to where it no longer knows where the internal storage addresses are and does not know it has any type of storage to boot to. However a lot of the efi should be copywrite protected where even a root user cannot modify them but trust me... its possible and may still be repairable but only by the manufacturer who has that level of access and definitely not worth what it would cost. Keep an eye on any files you modify for a copywrite at the top of the file. Changing copywrite files will most likely get you in a whole lot of trouble. If you end up having a web adress listed in the build.prop on every android device you own that brings you to the developers terms and conditions then stop messing with system files. This is more or less a warning telling you that you are breaking the terms and conditions. I would libe to continue but then i would be contridicting myself on my comment about very large messages in the forums. If you would like to know anything else please feel free to PM me and lets put an end to this thread lol.

Guys, speaking of devices with MT chipset, I have a Hannspad HSG1341 that was running Android 5.1 and wanted to root the pad using some tutorial I saw with magisk by installing the APK on this device which creates a modified boot.img. Then using SP Flash Tool I tried to reinstall the stock firmware by replacing the boo.img created by magisk and now the pad would not power on, I have tried searching for means to restore this pad but nothing. Even SP flash tool is now displaying s_ft_enable_dram failed (4032). So please off anyone has any idea how to resolve or is the pad dead for good. The chipset is MT8163. Let me know if you need more info to help out
thanks

Related

[Q] I think I can stump xda forums... seriously messed up 16gb

It's been a while since I've worked on this, and I still can't find anyone with a similar problem on xda. Does anyone have a clue what's going on with this thing?
First, I got it working just fine with CM7 installed to the nook itself, not running from an sd card. That worked for a bit, then it started just shutting off with no obvious reason.
Also, if I make any changes, like uninstalling apps, it goes right back after a reboot - which happens whether I want it to or not. This applies to changes done with CWM as well, even installing a new rom.
On top of that, it won't boot from an sd card, so that sucks too.
Lastly (I think, it's tough to keep track of all these problems) abd doesn't recognize the device, and for that matter the operating system doesn't either. I've been using Ubuntu Lucid if that matters, but it didn't have issues detecting the device before.
I'm pretty novice, but I think this is a very complicated problem in need of expert advice. Any answers, tips, advice, or pointing in the right direction for any of my problems here would be awesome. Does anyone have any ideas?
Thanks.
Dude you say your a novice thats one... Two you are being critical of people who volunteer on this stuff. You can't be serious. You obviously have not read the support threads because you are not the only one with these problems and those that have them also did not read enough initially and failed to follow some step. Moreover, even if your problem were unique who do you think you are getting upset at anyone but yourself for taking the risk. Read the support thread for cm7 Mr. Ungrateful... flash back to stock and leave this forum alone until you 1. Learn what it means to be grateful. 2. Learn to follow instructions. The end
it is impossible to stump xda...
rickyshortcuts said:
Dude you say your a novice thats one... Two you are being critical of people who volunteer on this stuff. You can't be serious. You obviously have not read the support threads because you are not the only one with these problems and those that have them also did not read enough initially and failed to follow some step. Moreover, even if your problem were unique who do you think you are getting upset at anyone but yourself for taking the risk. Read the support thread for cm7 Mr. Ungrateful... flash back to stock and leave this forum alone until you 1. Learn what it means to be grateful. 2. Learn to follow instructions. The end
Click to expand...
Click to collapse
Thanks, that reminds me, I did follow all steps to the letter without a hitch to get CM7 going. It wasn't until after it was running for a few days that this happened. Also, in the aftermath while trying to solve the problem, I did everything I can think of to completely brick the nook so that I might be able to use some of the methods here to unbrick.
And just to defend my good name, I think it's a stretch to imagine I've been critical of anyone. To reference your other post on these forums, perhaps you might reconsider how to be helpful. Let me help you out with that.
because it is SERIOUSLY a hard brick, then you gotta get serious about your attack on this sick puppy. get a #6 torx and open it up and get directly at the internal sd card ( which sounds like you have trashed... )
hth
.
let us know when you got it open...
Dude!!!
rickyshortcuts said:
Dude you say your a novice thats one... Two you are being critical of people who volunteer on this stuff. You can't be serious. You obviously have not read the support threads because you are not the only one with these problems and those that have them also did not read enough initially and failed to follow some step. Moreover, even if your problem were unique who do you think you are getting upset at anyone but yourself for taking the risk. Read the support thread for cm7 Mr. Ungrateful... flash back to stock and leave this forum alone until you 1. Learn what it means to be grateful. 2. Learn to follow instructions. The end
Click to expand...
Click to collapse
One: This was a completely pointless flaming. Two: For being a novice he seems to be a bit more informed than you are. This is an issue, however not a common one. And from what I have read in these forums there is not as yet a fix. Three: I didn't read any ungratefulness, criticism, nor any hint of being upset. And Four: If you can't help out or give any useful advice then maybe you should "leave this forum alone" until you learn to be more civil.
chuckweiss2 said:
Thanks, that reminds me, I did follow all steps to the letter without a hitch to get CM7 going. It wasn't until after it was running for a few days that this happened. Also, in the aftermath while trying to solve the problem, I did everything I can think of to completely brick the nook so that I might be able to use some of the methods here to unbrick.
And just to defend my good name, I think it's a stretch to imagine I've been critical of anyone. To reference your other post on these forums, perhaps you might reconsider how to be helpful. Let me help you out with that.
Click to expand...
Click to collapse
Well put, and Props.....
I don't know if I can help out but I think I can point you in the right direction.
http://forum.xda-developers.com/showthread.php?t=1619615
This seems to be a hardware problem, but I don't think anyone is sure what is causing this.
Good luck with finding a fix.
went and found a XDA link for res-erecting bricked devices. it by @adamoutler and looks like a goodie !
ModeDetect USBID Detector
http://forum.xda-developers.com/showthread.php?t=1257434
hth
.
( you can tell that Adam is passionate about his tech. what do they feed those boys down in Louisiana beside crawdads ? )
Alright, so thanks to old_fart and DavDoc I've determined two of my problems, and I think there are four.
First, DavDoc's linked thread describes perfectly what's happening with problem one, what I'm calling the Groundhog Day Syndrome for no particular reason. Any changes to my nook go right back after it's powered off.
Second, I checked out old_fart's linked thread and I'm pretty sure even though I have a blank screen it's still on in one mode or another. The program doesn't work though because of problem #3 (to be explained) but it seems sensible because to power it back on I must first hold the power button for an extended period of time and release, then hold it again for the normal power-up.
Problem number three is that the nook is not recognized by either Ubuntu or Windows when plugged in anymore. Thus that program not working, and also adb. I may be able to determine that one from error logs as soon as I figure out what in the world the error logs are saying.
Fourth and hopefully final, it won't boot from sd. I'll figure that out too.
Thanks for the advice so far, this forum is definitely indispensable for people who like to learn from playing with technology.

Dual Boot Official GB and ICS rom for HTC EVO 3D GSM and A Few Thoughts!

Disclaimer: Kindly Forgive My Long Post
Some Important Details of My Phone:
Hboot version HTC EVO 3D X515m PG86300 GSM:
***LOCKED***
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.49.009
eMMC-boot
July 18 2011, 12:09:31
ro.carrier:[HTC-India]
Shooteru
CID: [HTC_038]
Android Version: GingerBread 2.3.4
HTC Sense Version: 3.0
Software Number: 1.22.720.4
Kernel Version:
2.6.35.13-g28ad439
[email protected] #1
SMP PREEMPT Thu Jul 21 14:50:22 CST 2011
Baseband Version:
10.54.9020.00U_10.13.9020.20_M
Build Number:
1.22.720.4 CL115289 release-keys
Browser Version:
WebKit/533.1
Dear All, I have taken my time and read through and even posted on most of the forums, but unfortunately not one detailing the stuff I intend to do or proper/clear cut response. First off, I would like you to remember that I am a noob and your elaborate and detailed instructions of the steps involved would invaluably help me and hopefully others looking to do the same, so if you're in a hurry, please don't reply halfheartedly. When you have some free time, reply and I will wait patiently for your instructions on how to go about things. I will wholeheartedly appreciate whatever inputs I can receive from those with some know how about the possibilities/impossibilities of the same and please, like I said, spare the noob with some patience and offer some really helpful posts(even if delayed). Thank you.
My intention listed below: (Have already purchased a 64GB Class 10 Micro SD card)
1. Root to S-Off. (Hopefully with methods to revert back to Original state in case of Jelly bean update being released for the EVO3D or for receiving future updates).
2. Back up my Official GB and apps to be reinstalled with a boot manager to slot 1 as either recovery or First Rom.
3. Obtain The Official ICS update either via OTA or if there is an Official Ruu File for my device. Steps on how to get contacts and apps restored back to this too would be helpful.
4. Back up the ICS Rom to be installed on Slot 2 of boot manager so that dual boot of Official GB and ICS can be done.
5. Possible methods of adding the Jelly Bean Update If/When available to this mix to have a triple booting device with the official ROMs.
Based on the above, this is what I am looking for:
1. Fool proof methods and steps on achieving the same.
2, The necessary apps, recovery programs, region based Stock ROM/Ruu files(in case the backed up Official ROMs are not necessary or deemed applicable), and any other software/apps that may be needed to be downloaded/purchased for performing the same.
3. Step-by-step instructions pertaining to the particular Hboot version, CID, etc of my device.
4. Safety measures to look out for, checklist of files to have before hand and Probable methods of having a safe copy always at hand to recover mobile from any boot loops, bricking, etc.
5. Please note MOST of the links to files are not downloading, especially file factory links of the RUUs. All the other smaller files are there and can be got from alternate sources too, except the more important Big Ones Missing! Kindly rectify the same. Thank You.
I would like to inform some very important things I noticed on the forum/threads in PLENTY and what it would seem like to anyone new on the forums and if you are of sane mind, I am sure you will agree! Not that I'm asking you to, since to someone familiar with things a noob's point of view will ALWAYS seem inferior, because one very easily forgets that he was once a noob too:
1. You have instructions and threads, YES, PLENTY! BUT... There is always a drawback/s mentioned somewhere down the line that too when the thread has nearly 400+ pages! That would only make a person mad for having wasted time to find out that it is a nonworking method, etc. Either the thread has to be cleaned up of repeated questions or WRONG information. Faulty/half-working ROMs have to be either REMOVED or Carry A Warning in the TITLE as well as the 1st post itself so that people won't waste their time reading through the umpteen posts and pages or trying and failing and/or bricking their devices.
2. Too many threads of the same methods to do the same thing whereas there are issues mentioned and argued about with those methods too. Ever heard the saying, "Too many cooks spoil the broth!" ? Also, be more descriptive with titles or threads so that Search will catch it. Eg. If something is either related to GSM or CDMA(even for RUUs, if made known, would help immensely), please have it mentioned first off!
3. In the same way, Methods for Rooting, S-OFF, etc, would be BEST if they were mentioned with the supported/respective Hboot versions or CID numbers since these two seem to be the most important factors from what I have seen. It would be good if members posted their Hboot version [Power off phone, Remove battery, replace it, hold volume button down and then simultaneously press power button for 2 to 3 seconds to go to Hboot menu. Volume buttons to go up or down in the menu, To Exit, move to fastboot, with fastboot highlighted, press power button, scroll down with volume key to reboot, with reboot highlighted, press power button to Exit(see what I mean?! THIS is what a noob would want to know and Not KNOW! Unlike someone flashing 10 to 100 ROMs a day)] and CID version(CID Getter app download from Market/Google Play Store, install and Run. The First Line on TOP in Red shows the CID is...) when they say some method worked for them or DID NOT and be responsible enough to reply when the OP asks if the issue was resolved because it leaves someone reading 500 odd pages left in the dark! And trust me! It isn't an easy task!!!
4. If information is known as to which region RUU/s(Stock Roms) is for a particular CID and Hboot to work without conflicting, kindly link them TOGETHER, if others can be used mention the same, but also how and what files to have in handy in case restoration needs to be done for either warranty or other purposes, since the files will be needed according to the same by each member and having a List/Database in a separate thread with correct details of EACH would immensely help, and then at least the search function would prove more helpful. (Note to Others: Before you change CID or other Important Things, Note Down the About Phone Details of your Phone, CID number, Hboot Version, etc, on a notepad saved as HTC Evo or whatever your phone name is, with a Date in the note for each step you did and when, etc for You To Keep Track, in case the need arises down the line, NOT say you didn't think it was important! Ever try forgetting your wife's birthday or your wedding anniversary, Yeah Right! WE Don't think it's Important, but We'll know better later! ) This is a thousand times better Instead of guess work or time wasted on trial and error and reading a hundred threads that lead people in circles between will work and won't work fights, only to curse the day they thought of trying something with their device!
5. When there is a WRONG INFORMATION passed regarding a ROM/method of S-OFF, etc, get the facts verified ASAP and remove contraindicating or confusing posts or the thread itself if there is an issue, Make it compulsory for OPs to Put up A HUGE WARNING as to the drawbacks of doing something with a particular ROM (or better still Just Remove It), and make known of NON-WORKING things before Hand! Which method pertains to which versions, etc. That way noobs would not end up trying their hands at things that they are not familiar with and end up begging later PLEASE, HEELPPP, etc, on deaf ears in the forum. They can at least have working methods up and try them out and be happy once they succeed and can be even more happy to have entered XDA and can spread the good word!.:highfive:
6. This is supposed to be a forum for productivity, NOT Hold Egos OR Try and test others as guinea pigs and then claim d'oh, or Oh sorry I didn't see or notice that. Your small overlooking of an important factor might cost someone his/her device! Try and sort your $#!T Out BEFORE You post it in a forum! Give detailed answers. If You Don't Know, Say You Don't We Won't Think You Less Wiser, but will Appreciate Your Honesty! Not wait till someone gets Scr3W3D and then later cry hoarse all over the forum! And yet you try to act All High and Mighty After You are Caught With Your Pants Down! Catch My Drift?!
So admins please do clear up things a bit and get rid of unwanted posts or too many topics on the same thing, which would have consequential/negative effects on those visiting those threads, (let them bunch up all their names as credits in the single thread and oh to AVOID the EGO Clash Mention "In No Particular Order" just to make 'em happy!) because it will give a bad name to the forum which I'm sure none of us want to see happening! Just my 20 cents I hope would be useful!:angel: Oh and as a signing off to People Already on The Forum or Coming into the Forum, "I DON'T CARE if You GET Or NOT GET an EVO, JUST PLEASE DON'T GET AN EGO!!!" Take Care and God Bless!
Thank you for your thought out post. I did read the whole thing and agree that in an optimal world, posts would be much more detailed. But, to give that much detail would be a full time job and then some. So many of us give pointers to get people looking in the right direction.
When I rooted my phone as a noob, I had about 20 tabs open researching different sites and consolidating information. I learned a lot that way and am glad someone didn't spoon feed me. But to each his own I guess.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Please Tell Me My Post is Not in Vain!
coal686 said:
Thank you for your thought out post. I did read the whole thing and agree that in an optimal world, posts would be much more detailed. But, to give that much detail would be a full time job and then some. So many of us give pointers to get people looking in the right direction.
When I rooted my phone as a noob, I had about 20 tabs open researching different sites and consolidating information. I learned a lot that way and am glad someone didn't spoon feed me. But to each his own I guess.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Click to expand...
Click to collapse
Hi coal686, thanks for the reply. Reminds me of my school nickname thankfully which never stuck! lol Well I did type out the long post above because I wanted to mention the difficulties ANY noob would have on approaching the site and also what I DID NOT find Anywhere in the threads. (you have dual boot threads, but not the same) What would seem right direction/s to the "quickie" posters might not actually be the right direction if you read through the threads for the target. Like saying go this way, then that way; oh! and there's also this way and that way too and the person travels all those miles(pages in this case) through all those different paths(threads) only to reach the DEAD END of different sides of the SAME CLIFF to jump off! Don't believe me? Read the threads! You'll understand why and tell me honestly that you don't feel the same way when you see some or rather most of the threads after actually reading a gazillion pages.
You say difficult to give that much detail. I thought we all actually want an optimal world, not a world driven by chaos?! There is much MORE wrong detail given in a single thread or how do I put it?, Target-less detail, other than the intended purpose sometimes. If you did read my post, you would have been kinder to notice that that was what I was trying to mention and imply from my experience. Like I mentioned before, It is NO USE having SO much info(some wrong or non-working) scrambled all about with different variants with no proper target or what it is about. Do you know that if a person literally typed out a single page with proper working methods with so called "spoon-feeding explanations steps to a noob" like how I explained in my post(for the Hboot and CID) there would have been lesser space taken up in the forum and it would be BENEFICIAL to one and all who visit the forum. (also for those who don't have Mbps connections to see, again, misguiding or poorly shot videos on the same)
Don't you think those 4 or 5 points that I posted are obviously what is ideal for any/everyone. List of programs for each purpose, steps to do, Note down the About Phone info, Hboot, CID versions, correct files to download for the same, how and when to do the backup, rooting, But still if the methods were already there, there would be no need to revert or go in for warranty anyway! Tell me you see these important instructions in the best of threads up front and at the very beginning and I'll know how well you read those 20 tabs. Still don't trust me?!
I'll be frank with you, a person who is pretty confident too will come in, read, try, scream at least a million WTFs?!! and different profanities by the time he is done with just one part of the process, would have lost half or more of hair and brain cells, and read a "right-looking" thread which ends up being the wrong thread, mess up his phone, beg on the forums, curse in his heart, still beg more and by the end of it all would say $cr3W T#!s and maybe either kill his/her phone or himself/herself! lol I hope that's not the intention of the forum though, or a new depopulation method?! :laugh:MAO
However, Please tell me you don't believe I am asking to be SPOON FED according to you, and that I came and posted WITHOUT READING ANY THREAD. Just like you, I usually take just a day or two continuously reading stuff, actually more than 20 tabs at a given time to get a hold on any new topic and I'm usually done within that time because it's easy to identify the right stuff for me to get the various topics and have an understanding of what I need to know, but I cannot say the same for this experience. Multiple tabs reading of utter confusion, misguidance, so many pages bookmarked, read through, agonizing to learn, that I am asking something about a person's head(Evo 3D GSM) and two eyes(Dual boot GB/ICS) straight up and I am instead replied to with directions to a person's... tail(don't ask!), or what one or many persons think is a person's head, only directed to the wrong head! You get the picture?
Sorry for being a bit coarse, but I hope it puts my point through clearly or better for people to understand the flaw and rectify it, instead of trying to justify it. For that matter, when you see the so called multitude of videos(it's a PITA on 512kbps), which are supposed to be by people doing this stuff day in and day out, Just see the number of times, they stutter through their own stuff! They cannot go through the process correctly, forget a program in between, forget to post the links up front, or steps, things like commands and stuff are thrown about in different graphics! Are you serious?! Then go about it all haphazardly and then think to themselves, they HELPED someone!!! Boy if they were a Driving instructor there would be lesser population!
Just for entertainment purposes, This is how it would go:
noobie driver: What do I do sir?
Instructor: Well you put on your seat belt first, start the car, change the gear, slam down the accelerator.. oh $#!t wait I forgot to tell the mechanic to change the brakes, umm... adjust your mirrors, umm... oh yeah press the brakes, umm... there's a truck heading into us!
noobie driver: WTF?! What is the brakes and where is it sir?!
Instructor: What do you mean you don't know what or where the brakes are?!! It's that damn pedal down there you Noobie Nut job!!! (looks down) Oh s#!t!!! I forgot to refit the brake pedal that I took out too!!! Never mind Bubba say your prayers!!!
CRAAAAASHHHHH!
This is about the same scenario that's happening! Like with computers, just because I know a little, if I instruct someone who has never touched a computer or maybe owns a computer and types stuff on it, blindly saying, put the power cord into the SMPS socket, take the RAM out, clean it and RAM It into slot 1 not slot 2, the one next to the CPU is slot 1. Replace the CMOS battery, Check if Hard disk is connected, Check if DVD writer is SATA/IDE! Clear the CMOS jumper by moving it from pins 1-2 to 2-3 and then back to 1-2. Oh, but first, pull out the power cord before you do! Do you know what reaction I would get?! I would probably hear a BUZZ, see some sparks and have one less person and one less machine on the planet!
Now I know when reading this long post, some might be with their noses pointing in the air saying, Oh we don't have the time for this nonsense! But seriously, you think that others are enjoying the experience like I'm going through?! The neck, back and headache I'm having right now is all proof to it and if experienced by you, you'll definitely not hesitate to even spoon feed me! All this stuff will just put the TRUE picture of how things are, well, at least for now. If Anyone patient enough and want to seriously change things to an optimal world situation, and willing to guide me through though, I will STILL be Patiently WAITING for your knowledgeable inputs.
BTW, still the file factory downloads keep timing out or failing before the end and after three attempts, that too through DTA(down them all) to avoid any failure, it is coming as a failed download or simply beeps completed, but with a html of 21kb!!! Torrents Anyone?! Also for the said Hboot version and CID of my device(or am I supposed to change it?) Which are the RUUs to download? Shooter U GB/ICS Europe or Asia? I am guessing a backup of my own GB would be useful for the future just in case so how to do the needful would be good. Thanks once again for your patience on whoever gets to read this and will as usual appreciate ANY inputs on the same. Cheers and God Bless.
Comments withdrawn
Sorry, If You Missed the Point Be Patient, I Don't Want You To Lose Me! lol
@zcink: Thanks for the quick response. Oh, btw your logo pic is my pet name Micky (in case you change your pic) lol! Also what you mentioned is what I am somewhat hoping to do. Lol and I can imagine why it was quickly shot down! lol Care to post the steps though for my scenario, either here or on a separate thread and it may benefit some, if not many! I did try breaking up the paragraphs for easier reading bro. It's really not that difficult to read and sorry once again if it is. Well other than the seemingly unimportant stuff, this part from my first post being replied to in detail would be more than sufficient:
________________________________________________________________________________________________________________________
My intentions listed below: (Have already purchased a 64GB Class 10 Micro SD card)
1. Root to S-Off. (Hopefully with methods to revert back to Original state in case of Jelly bean update being released for the EVO3D or for receiving future updates).
2. Back up my Official GB and apps to be reinstalled with a boot manager to slot 1 as either recovery or First Rom.
3. Obtain The Official ICS update either via OTA or if there is an Official Ruu File for my device. Steps on how to get contacts and apps restored back to this too would be helpful.
4. Back up of the ICS Rom with apps, etc to be installed on Slot 2 of boot manager so that Dual boot of OFFICIAL GB and ICS ROMs can be done.
5. Possible methods of adding the Jelly Bean Update If/When available to this mix to have a triple booting device with the official ROMs.
Based on the above, this is what I am looking for:
1. Fool proof methods and steps on achieving the same.
2, The necessary apps, recovery programs, region based Stock ROM/Ruu files(in case the backed up Official ROMs are not necessary or deemed applicable), and any other software/apps that may be needed to be downloaded/purchased for performing the same.
3. Step-by-step instructions pertaining to the particular Hboot version, CID, etc of my device.
4. Safety measures to look out for, checklist of files to have before hand and Probable methods of having a safe copy always at hand to recover mobile from any boot loops, bricking, etc.
5. Please note MOST of the links to files are not downloading, especially file factory links of the RUUs. All the other smaller files are there and can be got from alternate sources too, except the more important Big Ones Missing! Kindly rectify the same. Thank You.
________________________________________________________________________________________________________________________
Lol, I can't help but notice that I mentioned the words "Official ROMs" many times just to be clear and it was so easily missed (Sorry, if I am to blame or wasn't clear enough) I am not all too keen on Custom ROMs having one or two (maybe unimportant to some, but important to me) features missing making my phone defunct, but rather thoroughly working with its original ROMs. I would however be more than happy to add Any FULLY working ROMs with maybe Sense 4.0 and Beats to the mix, but I was already told that there are NONE and also explained the reason why they are that way, so I do understand!
Let me guess my friend. Either the installed radio or the kernels must have been the issue because one would have been for GB whereas it won't work for ICS or vice versa. That's why I was hoping that someone who knows or tried out this stuff to the core would know which is the commonly working Kernel or Radio to install both ROMs without error, or if say Maybe Official backed up GB was installed back onto the phone as slot 1 and Official ICS was backed up and installed onto a partition on the SD card as slot 2, with maybe a separate partition for ROMs and Data so that say each ROM stays within that area having their own separate kernels, radios, etc when loaded into via the boot manager and hence not having issues with their working.
Sorry, I am not too well-versed with the workings of android, but I am just trying to give my thoughts based on what I know through my experience with dual booting computers, though I know we're talking different things here, but am sure some things might be common. Just out of curiosity, does maybe android not have ways to direct or redirect the phone to a separate portion to run each particular ROM and maybe because all the files are all dumped in the ROOT there are errors?
Because for example if I were to take both XP and Windows 7 files(though common platform) and place it on the same partition, there are definitely bound to be errors. Whereas GB and ICS are more like Windows XP and Linux(only Android Mobile being the common platform here) so probably placing them all in the same place(Root of phone) is scr3wing up things. Does Android segregate things(files to separate partitions) in the same way as computers do and the boot loader able to direct/redirect to the appropriate partitions/ROMs for smooth performance? OR Does it have NO method of doing so hence the chaos?!
If that was the case, any developers of the boot managers, ROMs, etc who manage to write stuff in a way that it is able to hold different kernels/radios for the respective ROM/s in separate partitions on the memory card (or Phone if enough memory on board) would be able to manipulate the system to make the boot loader redirect correctly to the appropriate partition and hence make it error free in operation since all the needed files would be present in that location. Also a common way to connect to other files(media, etc) on a Separate Data Partition, would enable each ROM to recognize/find/see those files instead of missing/not detecting files, or say getting apps and contacts for EACH Rom reinstalled again and again, similar to as on OS' of computers.
Am I just blabbering/rambling here not knowing what I'm talking about?! I guess so, but Well, just my 2 cents which could hopefully benefit for the future to someone or some developer who tries to think differently like me(err.. the thinking part that is, not the developer part! lol). Thanks and anticipating once again your knowledgeable inputs.
help needed
******LOCKED*******
SHOOTER_U PVT SHIP S-OFF RL
HBOOT-1.49.0018
RADIO-11.25.35.3504.06_M
openDSP-v02.6.0.2226.00.0202
eMMC-boot
oct 3 2011,15;03;01
need help how to revive this phone is urgent thanks in advance

[Q] Comment about terminology and process

I am a new Xperia Ultra owner and whilst not planning to do any flashing just yet I thought tonight I'd take a quick look at threads discussing steps that would be involved in doing this.
Let me qualify what I'm about to say by stating that I appreciate people on this site who develop tools which allow us to hack our devices so we can make better use of our phones. They are incredibly skilled, gifted and generous with their time. I would love to be able to spend the time learning how to do this but I simply don't have the time. So please don't take what I am about to say as a criticism but more as an observation, considering the effort contributors put into this it would indeed be incredibly foolish of me to criticise anyone here.
I can probably safely say that none of the contributors are also trained technical writers and a fair number do not have English as their first language. Its my first and only language and I often have difficulty getting the meaning across succinctly not to mind getting the spelling right . And I know even for large software houses support documentation is not a priority.
I want to approach hacking my phone with confidence this time round. In the past I've reflashed several phones for myself and friends and simply followed steps and not really understanding completely what the hell I was doing. Lordmanhattan I know I sent you an email regarding a contradiction on your thread. And you very kindly got back to me very quickly.....amazing, thank you. And then there is the "TA partition", WTH is that? I did very briefly google this to find a quick answer but no joy....grrrr (also looked in the XDA Wiki acronyms) I'm sure if I looked hard enough I'd find it. It's mentioned everywhere but nobody seems to be offering an explanation what it is or what it does or why it's important or what it stands for !!!!
Very often I find threads on here describing how to do something hard to follow and this is often for the following reasons:
It could be that there is more than one way to achieve something so its a case of different people offering varied procedures, this can be confusing
A process may be described but then to the newbie the author seems to miss out on a step that to the experienced is obvious
The level of English used leads the reader to scratching their head wondering ...did he/she mean this or that
Threads not being updated or corrected even after feedback
Okay I won't go on.
So I have decided my time might be well spent doing some background research before delving into messing about with my Xperia Z Ultra and saving you guys from having to deal with daft questions from me.
Now does this mean I have to spend time reading through threads and trying to piece it all together to find the best way through and possibly getting the wrong end of the stick or reading superseded posts?
OR
Are there a couple of sites that will get me up to speed understanding the terminology, hardware, memory management, etc for my phone?
I have a feeling it's going to be a bit of both......your suggestions please
Oh, I stumbled across XDA University but got the impression it wasn't being maintained???
Some of the pages I visited....
A New User’s Guide to Android.......unfortunately none of the images for this page loaded
Video guides .................................had flash presentations which didn't load
Ferg8080 said:
I am a new Xperia Ultra owner...
Click to expand...
Click to collapse
A good and detailed post, and it's not just the dev's and support that could take note. Some of the people that ask questions really need to read your post and think about what they are trying to say, get help with -- we aren't mind readers either.
I always try and help anew user by using as few TLA as possible in a reply to them. I also try to do the steps as #'d lists with as many steps as possible.
I do think LordManhattan's guide needs a little love as a few things are a little out of date - but it is as comprehensive guide as you could get, and most vagaries are covered in the thread.
TA = trim area, where your unique DRM keys are stored, and god only knows what else.
Thanks for your well written post! First I want to say - like Blueether just did, that we are not mind readers, so we can't possible know people's skill level or what they want to do. That's why I've started to ask them straight up what they want to do and where in the process they are. That way it'll be easier for me to help the other person, and hopefully write a short but complete step by step guide. It won't happen that often, but if I got some time to spare, why not.
My guide is a little out of date now, and I have planned to update it for quite some time, but things are moving so god damn quick around here that even I will get outdated if I take a short break. I recently sent my Ultra in for repairs, and 12 days later when I got it back and ready to get back in the game, a new firmware had been released with a new rooting method. I knew everything one day, and nothing on the other. It's really hard to balance real life and being kept updated at all times. Don't forget that you must be sure about what you know and write when you make a guide, because you don't want to brick people's devices. One slipup and the consequences might be ugly.
There are (of course) one or four ways of doing things around here, and you'll probably get different ways of doing things if you ask me or blueether about rooting or flashing custom ROMs. I guess it's just the way it is. New methods also pop up once in awhile, so some people will adopt these new methods while some other people will stick with the old school method, thus making things a little more complicated for new people who are looking for reliable information.
The TA partition is, like blueether already said, your device's unique DRM keys which makes X-Reality (and other minor things, I guess) work. It's important to make a backup of this partition since you'll lose it when you unlock the bootloader. Why would you unlock the bootloader? You have to unlock it if you want to flash custom ROMs, or if you want to make rooting easier. The problem is that you need to be rooted to back it up, so you'll have to spend some time reading and researching before you start.
Just keep your Ultra stock for now, and just casually read and soak up stuff from different threads around here. Walk around like you do in a new city and check out the locals and see what they do and say. You'll pick up a few things here and there and things will start rolling from there.
Sent from my C6806_GPe using Tapatalk
blueether said:
A good and detailed post, and it's not just the dev's and support that could take note. Some of the people that ask questions really need to read your post and think about what they are trying to say, get help with -- we aren't mind readers either.
Click to expand...
Click to collapse
LordManhattan said:
a new firmware had been released with a new rooting method. I knew everything one day, and nothing on the other. It's really hard to balance real life and being kept updated at all times. Don't forget that you must be sure about what you know and write when you make a guide, because you don't want to brick people's devices. One slipup and the consequences might be ugly.
some other people will stick with the old school method, thus making things a little more complicated for new people who are looking for reliable information.
Just keep your Ultra stock for now, and just casually read and soak up stuff from different threads around here.
Click to expand...
Click to collapse
Yes you can see some people just rush in with questions without giving serious thought to what they want to achieve. I think its people who don't often understand the process properly, haven't thought it through and are following what seems like a straightforward step by step process. Understanding what you are doing requires patience and TIME.
XDA I think is an unrivalled repository of amazing contributions from amazing people on a technology that is constantly evolving. Its also a jungle. One doesn't go into the jungle unprepared
Thanks for the fantastic advice guys and I will heed but I can't promise I might come out with some corkers
One last thing, how on earth do you find the time to lead a normal life? You obviously love what you are doing. It might be easy to assume everyone who contributes here is in IT. I imagine there are plumbers, electricians, mechanics, office workers, retired folk.....

LG G2 section is Unusable!!!

Please admins do some cleaning here. A lot of tutorials is very bad ripoff of another tutorials.
I my case I can not find one logically structured tread with general info about G2 flashing, SW versions and so on.
A lot of people try to make a money, by giving wrong information an later ask money for help to unbrick others phones. This is just terrible!!!
I AM ANGRY DUE TO BAD TUTORIAL I BRICKED MY PHONE REAL BAD.
Please ,clean or make new rules for comment rights, to help other not brick their phones!!!!
Hi
I think problem is not tutorials, but people who used first random tut.
Im sorry you bricked your device, but root G2 is really easy and install twrp.
For root u can use DP Tools from android g2 section, and twrp u can get with autorec from playstore.
That's all, if u wanna use customized roms, u will need install Jelly Bean bootloader, it support kitkat/lollipop/aosp roms. LG G2 is unbrickable by software, every state can be repaired. So, search tutorial for you to unbrick device and use my steps to have full unlocked device and feel free to mods and roms
I just unbricked my G2 after 6 weeks so ask if you need anything to help you.
Ganjax said:
Hi
I think problem is not tutorials, but people who used first random tut.
Im sorry you bricked your device, but root G2 is really easy and install twrp.
For root u can use DP Tools from android g2 section, and twrp u can get with autorec from playstore.
That's all, if u wanna use customized roms, u will need install Jelly Bean bootloader, it support kitkat/lollipop/aosp roms. LG G2 is unbrickable by software, every state can be repaired. So, search tutorial for you to unbrick device and use my steps to have full unlocked device and feel free to mods and roms
Click to expand...
Click to collapse
Nope. G2 community is so bad. No one give solutions, only ask for money , even steel credit card date. I love the phone, but the community is just terrible.
It is quite often that I found solution tread, first tree pages of comments are "nice work" , "good job" and so on , after fifth page real users actually give negative feedback. Now I am reading tread with 77 pages. I am in the middle and I still do not understand is it safe to use tutorial. And there are a lot of treads like this. XDA should give some rating possibility, to delete treads with wrong or not working properly solutions.
I am very disappointed in XDA.
MixXx2005 said:
Nope. G2 community is so bad. No one give solutions, only ask for money , even steel credit card date. I love the phone, but the community is just terrible.
It is quite often that I found solution tread, first tree pages of comments are "nice work" , "good job" and so on , after fifth page real users actually give negative feedback. Now I am reading tread with 77 pages. I am in the middle and I still do not understand is it safe to use tutorial. And there are a lot of treads like this. XDA should give some rating possibility, to delete treads with wrong or not working properly solutions.
I am very disappointed in XDA.
Click to expand...
Click to collapse
So, you mean u dont understand anything. I bricked my device few times, and i had no problem to recover this without any pay to anyone i know how to install cwm, rom, bootloader, how.. If you said we need pay for everything? Open your mind, if u are too lazy to read easy tutorials
Ganjax said:
So, you mean u dont understand anything. I bricked my device few times, and i had no problem to recover this without any pay to anyone i know how to install cwm, rom, bootloader, how.. If you said we need pay for everything? Open your mind, if u are too lazy to read easy tutorials
Click to expand...
Click to collapse
I can provide you with tons of treads in G2 sections, that is outdated or do not work from the begging.
I am reading these in terrible english written treads for straight two days and still nothing that wort been read!
As a matter of fact I am not a noob or total beginner ether....
You show u are, if no one before cried about G2 section everyone can mods, but not u, why? We should ask just u, this is not freakin magic
MixXx2005 said:
I can provide you with tons of treads in G2 sections, that is outdated or do not work from the begging.
I am reading these in terrible english written treads for straight two days and still nothing that wort been read!
As a matter of fact I am not a noob or total beginner ether....
Click to expand...
Click to collapse
So what doesn't work? Most of the things just do work normally but you need ofcourse to have the right bootloader version/modem just like on other devices. English isn't the main language for everybody so their English isn't perfect and so is mine but your's isn't 100% correct either. But they do contribute to the community and that breaks the barrier of languages.
MixXx2005 said:
Nope. G2 community is so bad. No one give solutions, only ask for money , even steel credit card date. I love the phone, but the community is just terrible.
It is quite often that I found solution tread, first tree pages of comments are "nice work" , "good job" and so on , after fifth page real users actually give negative feedback. Now I am reading tread with 77 pages. I am in the middle and I still do not understand is it safe to use tutorial. And there are a lot of treads like this. XDA should give some rating possibility, to delete treads with wrong or not working properly solutions.
I am very disappointed in XDA.
Click to expand...
Click to collapse
MixXx2005 I don't know which threads you are in but I never had anybody ask me for money or steal credit card date? There might be people asking for money or idk exactly what all but that might be going on in the background especially. As some people brick their phone others want to unbrick it and ask money for shipping/not trying to destroy it. If you want to do it free then you have to do it yourself probably. The G2 community does give solutions but there were already so many Q&A threads or people who all ask the same question/don't read properly the threads that some people just don't react anymore.
I had read many unbricking/root tutorials when I just came to this community several months ago already and everything worked fine. Also the hardbrick fix method worked fine for me.
Btw if somebody steals your credit card date then why did you gave them it all? If you have those kinds of problems or want to report something about outdated content then just react on the thread, Contact the OP, and or in cases of scams and those stuff contact a moderator. Moderator and members don't always have time to check or everything is alright so people need to report the problems.
So about "I AM ANGRY DUE TO BAD TUTORIAL I BRICKED MY PHONE REAL BAD. "
You really have to read carefully for which G2 variant is was meant, it doesn't matter if you are experienced or not experienced people also make mistakes just like that I hardbricked my G2 after I left myself on an unrooted rom with no download mode and recovery.
If you can say the problem you have like what kind of bricks, more details then I could might help you for free. The thing it might only costs is time but that's worth it if you fix your brick into an working G2.
I will try to reply asap but school and some other stuff in life might make me forget this so if you have a question please quote or mention my name as I would only then receive a notification about it.
EDIT: I read your thread now about your qh_usb brick and I read the tutorial. The tutorial isn't misleading or whatsoever there could have been an issue due to drivers/binaries and or communication between your device and fastboot itself. The tutorial was also meant for if you had the same message on your screen.
Btw in which mode are you? QHUSB_BULK 9006 or 9008? About the exclamation marks do you have the proper drivers for it? You might need to install the drivers manually with device manager. If you can mention which mode then I could perhaps help. Maybe not immediately but I could probably help you to unbrick your phone .
wulsic said:
So what doesn't work? Most of the things just do work normally but you need ofcourse to have the right bootloader version/modem just like on other devices. English isn't the main language for everybody so their English isn't perfect and so is mine but your's isn't 100% correct either. But they do contribute to the community and that breaks the barrier of languages.
MixXx2005 I don't know which threads you are in but I never had anybody ask me for money or steal credit card date? There might be people asking for money or idk exactly what all but that might be going on in the background especially. As some people brick their phone others want to unbrick it and ask money for shipping/not trying to destroy it. If you want to do it free then you have to do it yourself probably. The G2 community does give solutions but there were already so many Q&A threads or people who all ask the same question/don't read properly the threads that some people just don't react anymore.
I had read many unbricking/root tutorials when I just came to this community several months ago already and everything worked fine. Also the hardbrick fix method worked fine for me.
Btw if somebody steals your credit card date then why did you gave them it all? If you have those kinds of problems or want to report something about outdated content then just react on the thread, Contact the OP, and or in cases of scams and those stuff contact a moderator. Moderator and members don't always have time to check or everything is alright so people need to report the problems.
So about "I AM ANGRY DUE TO BAD TUTORIAL I BRICKED MY PHONE REAL BAD. "
You really have to read carefully for which G2 variant is was meant, it doesn't matter if you are experienced or not experienced people also make mistakes just like that I hardbricked my G2 after I left myself on an unrooted rom with no download mode and recovery.
If you can say the problem you have like what kind of bricks, more details then I could might help you for free. The thing it might only costs is time but that's worth it if you fix your brick into an working G2.
I will try to reply asap but school and some other stuff in life might make me forget this so if you have a question please quote or mention my name as I would only then receive a notification about it.
EDIT: I read your thread now about your qh_usb brick and I read the tutorial. The tutorial isn't misleading or whatsoever there could have been an issue due to drivers/binaries and or communication between your device and fastboot itself. The tutorial was also meant for if you had the same message on your screen.
Btw in which mode are you? QHUSB_BULK 9006 or 9008?
Click to expand...
Click to collapse
Thanks for your replay.
After all day of reading tons of useless information finally unbrick my phone. Now it is fully functional again.
I will explain why I am mad.
1st after official update my phone start to act weird (now i know what caused it, and it do not matter), then after I try to flash stock FW I stuck at LG logo. I found two different tutorials and both of them showed contradictory steps, I decided to follow one of them and like I said get error and booting till LG logo.
Next due to bad tutorial I erase all partitions with fastboot. But in the tut. was not said anything about proper way to do it. So after that tut. I get real brick. Still everyone can brick their phone following it.
http://forum.xda-developers.com/lg-g2/general/mega-tut-how-to-fix-bricked-lg-g2-t3055033 (3. step - how can I know that I should modify provided code with my .img file path? Where is something said about it?)
Then I read FAMOUS "LG G2 is UNBRICKABLE NOW! [FIX REAL HARD BRICK]" . After that I tried to short out test pins. Again I found contradictory informations about test point locations.
To get any life in my dead phone ,I try them both, and luckily I did not damaged eMMC.
There are a lot of wrong information how you should act in different situations in these topics, and these things can permanently destroy your hardware and there are no highlights or any warning about it.
So after qh_usb brick win 7 was unable to detect drivers, but somehow randomly after several hours of search, I found correct Qualqomm drivers, after that the device manager showed connection with 9008 mode brick. Then after I read whole
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830/page42
5th page before end ,give me right tool to fix my phone. tons of contradictory info there - truly TONS.
I can give you treads , where people do not give right topics, but instead give their FB and later ask for money.
Also I can give you proofs about those who said that they will help you for free in TeamViewer and quietly install keyloggers.
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830/ (read this tread , somewhere in middle of it, there are a lot of proofs)
It took me around 15 h with intense bulls*it filtering to get my phone in order.
And the most annoying thing , is that this all, what I describe previously , could be done in 15 min, if there would be ONE normal tread.
If all other/bad/misleading treads would be deleted, then my troubles would not been started in 1st place.
But like I said before this G2 community is terrible from beginners point of view.
Ok here is one thing
1. before doing anything search ( I agree that you will find a lot of outdated threads -- not useless but mostly outdated)
2. There is a help section with people who will understand where the error is and try to help you out
3. Most of the people here ask a question, solve the issue and just write: "fixed", without writing how and possibly contributing
Honestly, If I were a mod I would just delete their useless threads, always thinking of themselves
There isn't any magic tool that will fit everyones needs, people who are new just click random
I hope you fixed the device
bender_007 said:
Ok here is one thing
1. before doing anything search ( I agree that you will find a lot of outdated threads -- not useless but mostly outdated)
2. There is a help section with people who will understand where the error is and try to help you out
3. Most of the people here ask a question, solve the issue and just write: "fixed", without writing how and possibly contributing
Honestly, If I were a mod I would just delete their useless threads, always thinking of themselves
There isn't any magic tool that will fit everyones needs, people who are new just click random
I hope you fixed the device
Click to expand...
Click to collapse
Thanks, everything is good now. But I disagree - there are a lot of wrong and often contradicting treads and a lot of people that make their salary due to this.
I think admins should ban a lot of users here and also implement some kind of tread and user ranking. Because there are also people that do not know anything( I my point of view, they are just helpful fools ,that do not understand what they can cause with their misleading information) ,but they tried to help by just posting random s*it they were hear somewhere else. And I as desperate beginner can make much worse brick by following the advice.
MixXx2005 said:
I can give you treads , where people do not give right topics, but instead give their FB and later ask for money.
Also I can give you proofs about those who said that they will help you for free in TeamViewer and quietly install keyloggers.
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830/ (read this tread , somewhere in middle of it, there are a lot of proofs)
.
Click to expand...
Click to collapse
What proofs of keyloggers? I read it but didnt found anything..
Vihru said:
What proofs of keyloggers? I read it but didnt found anything..
Click to expand...
Click to collapse
Post #63 and below it.
http://forum.xda-developers.com/showpost.php?p=57454159&postcount=63
I don't believe this happened. There would be more people involved in such opinions then.
Tbh the thread name of yours is kind of embarasing for people who create free stuff for everyone.
If you have any issues with any user on xda there are mods and admins and you can report them.
MixXx2005 said:
Nope. G2 community is so bad. No one give solutions, only ask for money , even steel credit card date. I love the phone, but the community is just terrible.
Click to expand...
Click to collapse
Odd.
Because I always found a solution for every problem I had, got an answer for every question. Even the most ridiculous ones.
So I disagree that the community is bad, quite the contrary. Every bit of info is here. You just have to read and understand what you've read.
And people here are nothing but helpful (most of them, at least).
P.S. as long as your G2 boots up, it is not bricked and it can be salvaged.

P769 Bootloader Unlock - is it possible?

This is probably the most desperate post i've made on XDA. I'm not entirely sure if I'm following the forum rules, so I'm sorry if this violates any.
I've got an Optimus L9, model P769BKGO, manufactured March 22nd, 2013. My current understanding is if I have an L9 that was manufactured after June of the same year, the bootloader is encrypted, preventing me from unlocking it. I did work on the phone a while back, and found that it's running the P760's V10b Europe firmware. The bootloader appears to be set up properly, the screen is inverted and "flipped" horizontally as it's supposed to be according to all the tutorials i could find. There's only one problem I'm coming across.
The next step I can find is to flash the radio and connect to mobile data, leaving it connected for 30 minutes or more. I've tried to flash the radio, and it hasn't fixed the modem issues that comes with flashing the firmware to V10b EO. I have an active SIM in it as i'm supposed to, but I can't flash it to another firmware to restart the process because if I do, I have no working links for any of the tools/firmwares I need. They all either pull up a 404 or just don't exist, for example the "All in One" MEGA links in the more popular bootloader unlocking threads.
The Optimus L9 forum has been noticably dead for a while now, but i don't see any better place to seek help. Hopefully someone here can lend me a hand in finding the firmware versions I need to get this done.
If I have learned anything from xda-developers since 2004 when I got my first Windows Mobile smartphone: yes. it IS possible. And MORESO., where there is a will, there is a way.
That said, I've got a couple LG-P769's I'd like to root, so if I dig anything up that works, I'll let you know. Otherwise, my skills as a developer do not extend to reverse engineering (especially encrypted(!)) bootloaders. Creating a custom ROM is more up my alley, and something I may do if we find it is necessary
Toaster42 said:
If I have learned anything from xda-developers since 2004 when I got my first Windows Mobile smartphone: yes. it IS possible. And MORESO., where there is a will, there is a way.
That said, I've got a couple LG-P769's I'd like to root, so if I dig anything up that works, I'll let you know. Otherwise, my skills as a developer do not extend to reverse engineering (especially encrypted(!)) bootloaders. Creating a custom ROM is more up my alley, and something I may do if we find it is necessary
Click to expand...
Click to collapse
I wish I saw this sooner, but I think I can help you out with rooting them. There's something called LGPwn that you might find useful. If it works for you, it'll work well. There's also this one recovery installer that I use, although it's not very up to date... nonetheless, it works too. If I have any custom roms laying around that have dead links, I'll do my best to supply them just in case (since devhost isn't a thing anymore, almost all links here are dead).
Best of luck
Mrhayman12 said:
I wish I saw this sooner, but I think I can help you out with rooting them. There's something called LGPwn that you might find useful. If it works for you, it'll work well. There's also this one recovery installer that I use, although it's not very up to date... nonetheless, it works too. If I have any custom roms laying around that have dead links, I'll do my best to supply them just in case (since devhost isn't a thing anymore, almost all links here are dead).
Best of luck
Click to expand...
Click to collapse
While I don't want to jack this thread, I wanted to comment that LGPwn worked well for me and thanks for the links. I am a bit new to all of this, and I couldn't seem to find any ROMS that would work with the old phone newer than andriod 5.1 - thus also taking the chance here to ask given your already very neat help, if, unlike what I believe - I can use ROMS not made for the phone?
TheDractBar said:
While I don't want to jack this thread, I wanted to comment that LGPwn worked well for me and thanks for the links. I am a bit new to all of this, and I couldn't seem to find any ROMS that would work with the old phone newer than andriod 5.1 - thus also taking the chance here to ask given your already very neat help, if, unlike what I believe - I can use ROMS not made for the phone?
Click to expand...
Click to collapse
I'm suuuuper late on replying to this (I don't mind the bump though), you can use ROMs developed for the p760 as well, although I can't say I'm on familiar territory anymore. My L9 is in the drawer now, since I can't find a way to properly unlock the bootloader. They say there's supposed to be special software available, but that software has since been wiped off the net.
Regardless, I hope that helps.

Categories

Resources