]Hello i recently upgraded firmware from 6.0.0 to atv 7.1.1 then after reading benifits of custom roms recided to try atv first sistem booted up great ! I set uprom andwas really enjoying it .after about 4 hours the screen flashed to a pinkish color so i restarted system . system booted back up and stayed on for about 15 mins then all of the sudden went black. i triedrebooting ,rebooting into bootable recovery,nothingno signal to hdmi.after reading many posts and trying multipule methods to restore box nothing wirked. i then pluggedbox in to try to use the USB flash tool and system would no llonger connect to tool. pc windows 10 could no longer recognise my box.
i then used the pin method and shorted out the proper pins and got box to reconnect to usb burning tool. although the box connects no matter what firmware i try or what version of burning tool i try or VERSION of windows on different laptops i try nothing will flash and everything stoppes on 2% with the same error code of [HUB2-2][Inf]--IOCTL_IDENTIFY_HOST_Handler ret=-5 error_msg=libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning. and also [Err]--[0x10105002]Romcode/Initialize DDR/Read initialize status/USB Control setup error. drivers are installed i have tried un installing reinstalling still no signall from hdmi. box still has the red light when plugged in and blue light when pushing power on. please help i would really appreciate it . im kinda a noob with boxes ive flashed a few phones ,mods sone adb mostly basic stuff so i hope itsjust something stupid that im over looking .thank you do all devs for your hard work and everyone for reading this im going to post afewe pics of board hope this might help you help me thanks again Kevin
Sorry
Sorry if my post was too long somebody please let me know if it was a bit excessive I don't want to stop people from responding to help me because it's too long to read .
I wish I could help but when boxes are bricked I just leave them aside to work on them later (which I never get to) and pick a new one. Its too much of time consuming. Maybe someone else can help you.
hapishyguy said:
I wish I could help but when boxes are bricked I just leave them aside to work on them later (which I never get to) and pick a new one. Its too much of time consuming. Maybe someone else can help you.
Click to expand...
Click to collapse
Well I appreciate it, as a community who enjoys the technical aspect and trade of all this I assume that's the reason we post for help so we can learn new stuff about where we went wrong and perfect the process also be able to help people in the future. I'm sure someone else that can help will that's what community is all about. I could buy a new box but what's the fun in that Anyways I appreciate the reply hope you have a good day
Sent from my LG-US996 using Tapatalk
Mesman, my boxes are not bricked. So I do not know the interior electronics stuff.
Related
Appreciate the right person to provide us the way to the resurrection of our topaz brick, please many people need to work again our topaz.
Investigate all a brick recovery tutorial, thank you very much
Eject your sd card and pull the battery out.
Download a rom and start the rom with the RUU update tool **** on your pc.
Connect your phone.
Your phone will boot up in recovery mode.
Start the update after RUU found your phone.
The phone will update after the update re-insert your battery and let it charge for à minute or 5 before you start your phone.
Hello my friend, my topaz not start or enter bootloader mode, I'll run what I say and I'll tell you, you are very rewarding in this problem thank you.
Hello my friend, sorry to say that the operation did not work I have indicated, the phone does not recognize the pc and I get error 260. You have another idea to solve this problem?, Thank you
joseramon.gl said:
Appreciate the right person to provide us the way to the resurrection of our topaz brick, please many people need to work again our topaz.
Investigate all a brick recovery tutorial, thank you very much
Click to expand...
Click to collapse
You should be more specific describing your issue. What exactly has happened? What ware the circumstances? What is happening now: does your phone react to power button? Does it enter bootloader? Does your PC see the devise if it’s plugged in? Does your battery charges? etc…..
You're absolutely right, I detail the problem:
1-the problem arose at a bad flash, I run hard spl of mega htc (pack of Harry) was in error, for I have also the mega htc and wanted to investigate the change of rom, but was connected topaz pc loaded and will affect the execution of another program.
2-since then the htc topaz shows no signs of life, does not work, don`t boot into bootloader, it is not recognized by the pc, you are not charging LED light up, but pc connected to the battery if it heats up because I think load.
The situation is complicated solution to the problem you my friend?,
If you killed the bootloader, you'll probably aren't able to recover it only via USB and a PC. Here is the jtag pinout:
http://forum.xda-developers.com/showthread.php?t=669871
This is a programming connector. Don't ask me about how to work with it....I just know that you can program via this connector a broken flash. Hopefully somebody can help you.
yes man, sorry to say, but you are in real trouble. i think you should directly get it touch with the post starter of the jtag thread, mentioned above, mr. the-equinoxe. hi is real tough guy.
Information displayed is perfect, is a great information, now we have to work hard, thank you very much and if you have more information would be of great help.
The truth that I have no idea where to start, if it is attached would not know which pins to which, if you must connect the pins with a PC would know not, can you help?
God bless
joseramon.gl said:
Information displayed is perfect, is a great information, now we have to work hard, thank you very much and if you have more information would be of great help.
The truth that I have no idea where to start, if it is attached would not know which pins to which, if you must connect the pins with a PC would know not, can you help?
God bless
Click to expand...
Click to collapse
sorry. but I have never did this. ask this man http://forum.xda-developers.com/member.php?u=323818
maybe he can help you. write him personal massege.
Mr Egorlev ,You're a gentleman, I will accept your suggestion, I appreciate all your support, thank you very much again .
IM REAL DUMB FOR DOING THIS! i flashed a .tar file in CWM and now i just have blue and green lines across my phone i cant get odin to recognize it and i cant get into download mode should i just quit or is there a fix? Any help would be great THANK YOU!
PLEASE HELP!!
Theres plenty of options but alot of us are tired of writing them all down... there is enough info on this whole forum to fix your issue, its just a matter of time, patience and persistence
Sent from a cell tower to the XDA server to you.
What he said. Search the forum for "UNBRICK MAH VIBRNTZ" or something or other and you'll get a ton of answers, a few of which may involve cheese.
so why dont you point me into the direction to actually help instead of assume ive done nothing but complain on a thread. I have searched the forums and i cant find anything. When i did find something the downloads were dead so i dont know what fixes you are talking about thats why im asking for help
Worst case scenario, you can do the UnBrickable mod... notice there are TWO threads for this in the first few pages of the android dev section..
If youd rather not go there, keep trying to get odin to recognize by: first reinstall drivers on that computer, try different usb cable/port, try gb bootloader key combo and froyo bootloader combos (pull batt and let it sit for a few minutes before each try to make sure its really off).
If you have a diff cable on a diff port on a comp with freshly installed drivers (32bit on a 32bit machine or 64bit on a 64bit machine [or you could try mix and match]) and you try both key combos and it NEVER gets seen by odin, kill yourself.
Kidding... at that point, you can do the unbrickable mod or go to mobiletechvideos dot com (i think thats the ssite) and have them charge you to fix it.
Explicit enough?
Sent from a cell tower to the XDA server to you.
Hey guys. I was going to post this on the Android Forums, but the L9 board there isn't getting hardly any traffic, so I suppose I'll just repaste here:
Hey guys, it's loopy time. xD
I've been through XDA, again, nobody seems to really have an answer for this, or even an answer for me. There's this guy over there named Kuma that made a stock 2nd-init locked bootloader ROM based off of 10e. I don't really desire to go back to it, but I like the fact that it comes with the xposed framework which you all know is an easy way to theme things that you should be able to theme, like making the status bar and notification area transparent.
I made a mistake in thinking that you can install Chainfire 3D on a locked BL, boy was I wrong. Two soft bricks later, I end up on 10d then do the OTA update to 10e. I've got the LG Mobile Support tool working as the offline flash. So I threw d on there and it worked....until I decided that I wanted to enable USB debugging.
There was a thread where I was advised to use Fastboot to flash the U and X boots, which I succeeded, but it wiped most of the partitions. At first I was panicking like...OMG, the family is going to worry because at this point I thought I was hard bricked, and my father is ill yada yada. So after about twenty minutes of crying and flipping out, I was able to get the USB for fastboot working with OMAP (which is tricky to install!) Three bottles of Pepsi Cola later, some chips, and a honey bun, I was able to get back to stock 10d.
Now, I've tried various drivers to try and get this thing to a go for ADB so I could root, install 2nd-init, and get Kuma's ROM back. I tried the updated drivers from the LG website. I have tried LG drivers 3.8.1.
The issue that I am having is that I am unable to access any of the connectivity modes while USB debugging is checked. If I uncheck it and try to plug it in, everything works perfectly. However, when USB Debugging is checked, no matter what connectivity mode I am on, I suffer with the LG Software coming up in autoplay and furthermore disconnecting after about ten seconds.
I tried in Ubuntu Linux to get it to work, and the same thing happens. This leads me to believe that either there is something wrong with the phone or something wrong with my computer, but other devices work. I'm really confused. Is there partitions for 10e MS769 MetroPCS that I can flash via fastboot to correct this? Is there another tool I can use to do this? I pretty much know fastboot is the key, but i'm going to need some assistance.
Hope you guys have an answer. I sure don't.
Please help me with this. I am familiar with fastboot maybe its a bad .bin file?
Assistance would be appreciated.
Thanks,
LoopyD
Bump.
Anyone?
Had the same problem, usb debug and any sort of adb connection doesn't work. Kuma comes to the rescue like the super hero he is and helped me fix it. Here is the post http://forum.xda-developers.com/showthread.php?p=49475336#post49475336 . Oddly enough this problem got worse for me I had it for about 3 months and it resulted in constant crashes and constant resets. Thank Kuma's post if it works!
Thank you sir. The ADB executable installer now shows the device. Problem solved.
Thanks
Sent from my LGMS769 using Tapatalk
Hi guys!
I think I did something stupid while updating my XT1650-03 to Nougat.
What I did was manually flash stock nougat ROM (retbr) through fastboot, following the instructions within flashfile.xml, but, as I've read some bad things about the updated bootloader I stupidly decided not to flash it. The result is that it won't power up, even though I've tried: pressing power+vol. down; power; plugging the charger; fastboot commmands ( I was hoping it was just the screen that was off); to no avail.
I've noticed that when I plug the usb cable to the computer it plays that sound of connected devices.
Any suggestions? I'm probably going to have to take my device to authorised repair (off warranty, I know), but they usually take weeks to fix anything, so you guys are my best bet for now.
Thanks in advance!
martonto said:
Hi guys!
I think I did something stupid while updating my XT1650-03 to Nougat.
What I did was manually flash stock nougat ROM (retbr) through fastboot, following the instructions within flashfile.xml, but, as I've read some bad things about the updated bootloader I stupidly decided not to flash it. The result is that it won't power up, even though I've tried: pressing power+vol. down; power; plugging the charger; fastboot commmands ( I was hoping it was just the screen that was off); to no avail.
I've noticed that when I plug the usb cable to the computer it plays that sound of connected devices.
Any suggestions? I'm probably going to have to take my device to authorised repair (off warranty, I know), but they usually take weeks to fix anything, so you guys are my best bet for now.
Thanks in advance!
Click to expand...
Click to collapse
Don't even bother going to the service center. The same happened with my device and they refused to give me the warranty. Motorola voids it the moment you get the unlock code. So my device was dead for 3 months. And I fixed it few days back. The good news is that your PC is detecting the device.
I will post the solution with a new thread in few minutes.
Manish54 said:
Don't even bother going to the service center. The same happened with my device and they refused to give me the warranty. Motorola voids it the moment you get the unlock code. So my device was dead for 3 months. And I fixed it few days back. The good news is that your PC is detecting the device.
I will post the solution with a new thread in few minutes.
Click to expand...
Click to collapse
Thank you so much for your reply, it's very much appreciated! I didn't think anyone would reply that soon
I'll wait for your thread!
There ya go
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133
So, I'm totally lost.
As I posted in the thread above, even though Manish54 has been very kind to help, that solution did not work for me, so I've been trying to find another way. The thing is, this issue is beyond my comprehension. I'm not new to flashing and stuff, but I am new to moto Z. I understand that I should've been more careful and also have read a bit more before starting to mess with a new device, so feel free to judge me .
For instance, I don't know what fsg.mbm, adspso.bin, BTFM.bin and oem.img are for, since my old phone didn't have those (or at least I didn't need to mess with those), and I also don't know it they're relevant to my problem. If anyone could point me to some info on that, it'd be greatly helpfull.
Besides that, I've found mentions to tools like qualcomm's BoardDiag and QPST QFIL, but I'm not really sure if they apply for my situation, or even if I can manage to adapt the guides I've found to work on the Moto Z.
Any help is very much appreciated!
Thank you!
Solved!
I managed to unbrick my phone.
If anyone needs it, the details are in the thread made by Manish54.
https://forum.xda-developers.com/mo...rick-moto-z-hardbricked-t3590133#post71876064
Is there any way to solve it ?
Hillterpty said:
Is there any way to solve it ?
Click to expand...
Click to collapse
Did you even read the posts?
Ajuda
martonto said:
I managed to unbrick my phone.
If anyone needs it, the details are in the thread made by Manish54.
https://forum.xda-developers.com/mo...rick-moto-z-hardbricked-t3590133#post71876064
Click to expand...
Click to collapse
Amigo tb estou com o meu morto, me ajuda, qual o modelo do seu.
https://uploaddeimagens.com.br/imagens/sem_titulo-jpg--9130
hard brick moto z
Manish54 said:
There ya go
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133
Click to expand...
Click to collapse
hello friends, I'm with hard brick on the moto z xt1650-3
due to an update via ota, when my bootloader was unlocked I was in the android oreo (8.0), however I went back to 7.0, due to an update via ota, the device did not call anymore, I tried several blankflash and nothing, I am very annoyed at this, thinking of dropping my hand, I took some assists nobody can solve, I hope someone here can help me, at least inform me something that is useful to recover my cell phone.
my cell phone is still recognized as "qualcomm hs-usb qdloader 9008 (com3)
please join the telegram group:
https://t.me/motozz
Hey, my phone was dead two (brazilian xt1650-03), i spent three days struggling until i could bring him back. Thanks to the help in this forum. Your phone probably has the latest update opls27-76-51-7-july, so it must work:
first, you have to bankflash it with blankflash_OPL_27.76-51, its in the 30+ page topic tutorial here in this forum. Very important, must be in windows 7 or 8, with usb2.0
second, use this rom opls27-76-51-7-july-moto-z. it must work because its the last one. Its not brazilian, evething works fine but the netflix app didnt , but hey, at least our phone is alive again.
The secret is in the version of the firmware instaled before the brick, it must be the rom installed or latest to work
Hi.
I tried flashing a rom on a H96 Pro Plus 3+32GB box with an Amlogic S912, chip.
First couple of times when i tried flashing, it went up to 3-4% and gave out an error. Then i unchecked the erase flash and erase bootloader options and it went to 8% and then gave out an error once again.
After a couple of tries with the erase bootloader and erase flash options. It succeded flashing. But when i plugged in the box. There was no picture, there was just a blue light on the box.
The computer won't recognize the box after that, i've tried putting a rom on a SDcard, i've tried shorting some pins, not sure if they were the correct ones, but no luck. There is power going to the box, the blue light is on, but it won't turn on or display any signal.
Please help!
Thanks in advance!
Hi if you just search u would find the answer faster than writing this thread
anyway
hopefully it will help
other wise you should give more detailed and explained info
mazjed said:
Hi if you just search u would find the answer faster than writing this thread
anyway
hopefully it will help
other wise you should give more detailed and explained info
Click to expand...
Click to collapse
Hi.
Trust me i've searched for a week without any success. Unfortunately the video didn't help me since my problem currently is that the box is getting power but there is no hdmi signal, nor the box is getting recognized by the pc after flashing the rom.
Thanks for trying to help.
then the only chance you have is the short method
mazjed said:
then the only chance you have is the short method
Click to expand...
Click to collapse
Hi
I tried shorting pins, like in the tutorial but nothing happened. Not getting recognized still.
Hi
Ok, so i've fixed the tv box and it turns out i was doing something wrong. I didn't have power plugging it in. I was relying on the usb connection to give enough power to the box. I've done this to get back the box. Please if you don't know what you are doing, get someone that really knows. I'm not responsible for any damage that may happen. This is just what i've done to recover the box.
1. Hold the reset button on the box
2. Plug in USB in the pc and in the box
3. Wait 2 seconds and then plug in power.
4. Hold the 5th and 6th pin (i think). Please watch the video andmake sure that you know what you are doing, since 1 bad move could render the box totally unusable. Thanks. you should hold the pins for a couple of seconds and it should pop up
Also i wasn't able to install Aidenrom (while flashing it gives out an error) or Atvexperience (it cant get imported by usb burning tool)
I reinstalled the default rom. And i was using USB Burning Tool V 2.0.8
Thanks for your help.