Does anybody have an idea of what the P500 pinout is? And whether it is possible to revive a complitely bricked phone by simply swiching the pins or it will need a box (It's really hard to find boxes for flashing ROMs in Bulgaria).
EDIT: Please only provide answers to my questions, I'm already out of warranty and taking the phone to a service center will cost as much as a completely new phone (Even without replacing thunderg and radios, I'm not sure whether the SIM module is working...)
Wait a little bit. I have some info, but it is somewhere. When I'll find it, all needed info will be in this post
EDIT:
Some info here:
http://cellphonerepairstutorial.blogspot.com/2011/12/android-lg-p500-dead-boot.html
How to make simple JTAG device:
http://marsohod.org/index.php/ourblog/11-blog/163-marsblaster (Use GoogleTranslate if you do not understand, becz i needed)
I hope I helped in any way )
@ashirviskas: Thanks for your efforts. Unfortunately, ROM flash boxes are rare in here, and I don't have any materials and instruments to modify and create integrated circuits. Unless someone else suggests a method without a box,
R. I. P. 4.12.2010 - 21.3.2012 LG Optimus One P500 "nano" (don't laugh about the nickname, it's just a network name for my home server)
JTAG cable designs "So Simple Even A Caveman Can Build Them"
http://wiki.openwrt.org/doc/hardware/port.jtag.cable.unbuffered
http://www.zoobab.com/simple-jtag
Good Luck
Related
Hi there. I have/had wizard g4, but after upgradin' rom by ruu my phone is bricked. he doesn't even respone to charger.
Now technical details: upgrade was done on i/spl 2.21.001/olip, so after hardspl'ing him. Everythin' went just fine, but in 73% i've realised that i'm uploadin' g3 rom... So i let ruu finish his job and now my pda is completly dead.
I won't be askin' for HELP, i will ask for info. Will anyone can tell me: if i take out 'disk on chip' (cause i think that's the flashrom chip), how i can reflash it? I mean: should i just put nk.nbf from 0x0000 or split rom image onto bootloader, radio and os and put it partially? what are adressess of those thinx and lenght of code? and how can i split nk.nbf?
Congrats !
What your are asking is not easy to do,it requires special flashing tools and connectors,which only the manufacturers and vendors have,It needs new bootloaders,you cannot do it yourself.DOC chip might have to be replaced,it means an almost new phone
Btw,have you tried to force it into bootloaders ? might be lucky,if it gets into bootloaders.well there's no harm in trying,if it does,then you might in luck and safe.
whatdy'a mean sayin' 'force it into bootloader'? if you mean pressing cam button while poweing it on- yes i've tried. i even tried to boot linux on desktop computer, connectin' wizard and typin' 'lsusb' in console, hoping that something like 'xxxx:xxxx unkown vendor' occurs. But, still no luck. even linux thoughts that usb port with connected wiz is free.
I know that only vendors and sevice-guyz know 'tricks' about connecting directly to DOC chip... but i'm still hopeing, cause i've found two unused connector places on mainboard(after disassemblin' of corse)- one in the middle, second next to sim card connector and i'm wondering if there's any chance to ommit BGA-welding(sorry 4 my english).
Have you heard about conspiracy theory ? i begun to belive in it... I think that many people know what 2 do, but noone want to help me from one particular reason: if someone helps me, i wouldn't need to pay in service, so someone will not earn money...
anyway, what do you mean about 'force in2 bl'?
lis6502 said:
whatdy'a mean sayin' 'force it into bootloader'? if you mean pressing cam button while poweing it on- yes i've tried. i even tried to boot linux on desktop computer, connectin' wizard and typin' 'lsusb' in console, hoping that something like 'xxxx:xxxx unkown vendor' occurs. But, still no luck. even linux thoughts that usb port with connected wiz is free.
I know that only vendors and sevice-guyz know 'tricks' about connecting directly to DOC chip... but i'm still hopeing, cause i've found two unused connector places on mainboard(after disassemblin' of corse)- one in the middle, second next to sim card connector and i'm wondering if there's any chance to ommit BGA-welding(sorry 4 my english).
Have you heard about conspiracy theory ? i begun to belive in it... I think that many people know what 2 do, but noone want to help me from one particular reason: if someone helps me, i wouldn't need to pay in service, so someone will not earn money...
anyway, what do you mean about 'force in2 bl'?
Click to expand...
Click to collapse
First,let me clear you here, There's no such "Conspiracy theory" being practiced here in this Forum.It's a development Forum and not a Technical Advisory Service of some sort,where experts give advise and earn money.Its a free forum to help the newbies about the problem regarding their phones,We here believe in "Help & Support".The guys and gurus are not trained technical experts,its a voluntary website,where guys help and advise what they have learned and gained to the new guys joining and asking for help and they do it with honesty and to the best of their knowledge without any monetary benefits.
Secondly,Yes ! thats exactly what I meant for 'Force into booltloaders',cuz,may be if it does boot in the bootloaders,then it might be recovered,just a haunch,but if it doesn't,then its another dead paper weight on the desk.
Cheers!
I think it's a misunderstood there. I mean that maybe someone know what to do, but if it would leak to internet then services can lost money, cause what to pay 50$ i.e. if you can repair PDA by yourself?. I mean also that i've searched whole wide web... My polish sites of electronics, pda forums, even those forums where volunteers helps guys who crashed their bioses on PC's. And nothin', no one replies to mails, and if i ask someone directly they say thats no hope for me and my PDA.
I just cannot believe it... Even old PC had protection, if you uploaded wrong code into BIOS and PC cannot boot you always could ISA graphic card and boot from floppy.
lis6502 said:
I think it's a misunderstood there. I mean that maybe someone know what to do, but if it would leak to internet then services can lost money, cause what to pay 50$ i.e. if you can repair PDA by yourself?. I mean also that i've searched whole wide web... My polish sites of electronics, pda forums, even those forums where volunteers helps guys who crashed their bioses on PC's. And nothin', no one replies to mails, and if i ask someone directly they say thats no hope for me and my PDA.
I just cannot believe it... Even old PC had protection, if you uploaded wrong code into BIOS and PC cannot boot you always could ISA graphic card and boot from floppy.
Click to expand...
Click to collapse
focus on the problem:
tell me if u can at least see the bootloader ? If yes then u can have a fair chance of bringing urs back to life
It is because you are not supposed to flash a ROM that is not for your device!
For example, what will happen if you flash a AMIBIOS to a motherboard that uses AWARDBIOS (By your own way for sure)? Flashing G3-only ROMs to G4 device is just like that.
The protection for htc device is not letting you to flash a G3 only RUU in the usual way, you cracked to let it allow any ROM is your own problem, not problem of htc, and htc doesn't have to take care of it.
alber786 said:
focus on the problem:
tell me if u can at least see the bootloader ?
Click to expand...
Click to collapse
few posts ago i've wrote, that i cannot even see red led when pluggin' onto charger. BL mode doesn't work either (cam+ sr or cam+pwr).
i've found another way to resurrect my wiza200. JTAG.
But ofcoz noone knows where are testpoints located. But i'll find it. BTW someone can e-mail me fubu of working g4 wizard? lis6502 (at) gmail (dot) com
starkwong said:
For example, what will happen if you flash a AMIBIOS to a motherboard that uses AWARDBIOS (By your own way for sure)? Flashing G3-only ROMs to G4 device is just like that.
Click to expand...
Click to collapse
yeah, i know what i did. i understand example of bioses misupload. i've explained in that way to some guys who doesn't understand what i did
starkwong said:
The protection for htc device is not letting you to flash a G3 only RUU in the usual way, you cracked to let it allow any ROM is your own problem, not problem of htc, and htc doesn't have to take care of it.
Click to expand...
Click to collapse
Do i cracked it? i just found ONE working ruu which allowed me to upload any rom to my device. i've switched nk.nbf files in folder wich ruu was in.
I know also that HTC wouldn't help mi, i'm not counting on warranty or manufacturer help.
No No...
You installed HardSPL to your device, so your device is already cracked (say patched may be better) by you.
starkwong said:
No No...
You installed HardSPL to your device, so your device is already cracked (say patched may be better) by you.
Click to expand...
Click to collapse
uhm, it may be infatile question, but is it illegal? i know thah chaging IMEI is illegal, but is hardspl'ing too?
Cracking SPL is not an offense in law, just violate the warranty terms only.
2 starwonk: man, i'm from poland. i've bought my spv on polish eqiuvalent of e-bay. It's o2 xda mini s, so warranty is only valid in UK. i've told that i'm not counting on warranty. i need and must do it all by myself. and i will do it. Wish me luck
Ok a few days ago I wasnt paying attention and I installed a ROM on my LG Optimus G and when I restarted, it did not reboot. I have read a number of different forum topics on the subject and done a number of things to attempt to fix it.
From what I read, when the device shows up as QHSUSB_DLOAD in device manager, it is end game.
Ok well I did not immediately give up. I found and installed the Qualcomm drivers. I tried LG FlashTools. Of course to no avail.
This guy on EBAY (item 281151982662) will fix it for $24.99. I think that is a fine deal and since I have exhausted my other options, I was preparing to send it off to him.
AND THEN I found a link to "www(dot)zpsjbbs(dot)com/thread-5097-1-1.html -THIS FORUM POST that implies it may be fixable still with a software solution!!
The challenge is of course, that the post is written in Chinese. Google can translate and I feel I will be able to decipher it and search for and find the various pieces of software and try it out.
Question I have is, is it worth the time? Is it possible? Has anyone tried this method? Anyone have English explanation of it?
Thanks in advance. This is my first post here so I can not post links.
http://webchat.freenode.net/?channels=lg-optimus-g
Try catching Shelnutt2 on this link. This has come up in the past and from memory there is a Qualcomm tool availible, but I am not sure if anyone ever got it to work. There were hex files needed if I remember correctly.
Please , can you tell us what went wrong ?? so no one else tries it if they read it ??
Ive played with the Programs, Its QPST and the hope that it offers up is limited, but Im not a dev either. I can get it to a certain point and that's it, u need hex's off a working phone to get another part of the phone to say ok to get another part of it working... or so it seems, but Im all in on this if anyone wants to dable, this would cure a lot of woes if we hammered this topic. To JTAG my phone it cost 60 bux so the ebay deal if hes credible, is a good deal
Hi all, I've done a research and I know how much this subject was talked about.. ( a lot)
I need to replace my charging port (i think..) and I read that I should order one of the same rev. that I have.
Now, I opened my device (pic att.) and saw that it says "rev0.4".
I've searched a lot of time for the same part and couldnt find a same one!!
plus, there is that small chip at the top left corner, that seems to be missing from all the
charging port parts out there (at least in the pics...)
which part/rev do I need to order?
thanks.
You need to either:-
*Find KeithRoss39's guide to this in General (not stickied; search for 'replace USB charger board', or there's a link in Hopper8's Odin troubleshooting guide which is stickied in general).
*If you're still unsure or if it doesn't have the information you need (and it is very thorough), wait & hope Keith sees your thread & responds. He is the expert on this sort of thing here, and I very much doubt anyone else who posts here regularly will be able to give you useful information.
I've alredy read that guide...
It says clearly " you need to match this REV number with the one on the board you remove",
but it doesnt seems to help much, because I find no mention of my rev (0.4) anywhere...
This part is very cheap and i would have consider to buy other rev even just for testing but
then I see the difference in the pictures (that chip..) ...
ahhh Im frustrated...
*cough*
'If you're still unsure or if it doesn't have the information you need (and it is very thorough), wait & hope Keith sees your thread & responds'
Because I have same problem with the FM antenna and I don’t take any signal, I managed to find the service manual and I like to share it with you.
It has all the exploited view of the board and explains a lot of thing about the chips, even the smallest parts of the board. Can help you find the problem, as I find my own.
And if someone have the abilities to make a module for the IRRC this can help I think.
At first need a little practice but is not difficult to understand the diagrams.
link from onedrive:
https://1drv.ms/b/s!Aspcl1kA_XyilklOlKhg4jQjBX54
Link for the NFC chip module by NXP. It can help with any problem related to nfc :
http://www.nxp.com/documents/application_note/AN11690.pdf
This is a very interesting document.
(I think you are from Greece, right? If that is true, then you can contact me via PM in Greek)
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