Hi all,
I'm in a complete head spin so I'm hoping someone here could shed some light on an issue I'm facing.
As the title says, I currently have a Buzz TV XPL 3000 android box. I'm trying to flash "Aidan's Android TV Custom Rom" onto it. But no matter what I try to do, I simply cannot get the Buzz TV box to interact with my Windows 10 PC.
I have 2 different male-to-male USB cables that I've tried plugging into the box and into my PC, but there is no link between them. The PC nor the Android box don't acknowledge any kind of connection. I know a lot of people will probably say that my cables aren't data cables, but I've actually used one of them previously to flash another Android device.
Whenever I plug the USB cables into my Android box and PC, the ONLY thing that happens, is the PC powers up the Android box. I've tried turning on USB debugging tools from the developer menu, but nothing. The PC doesn't even make a sound when I plug the cable in and there is nothing listed under device manager. Nothing appears on USB Burning Tools under devices.. Just nothing.
I've tried plugging in the USB cable, while holding down the reset button (located on the bottom of the box), but all that does is power on the Android box and load into "Android Recover". Still nothing detected on USB Burning Tools and still no acknowledgement from the PC that a USB device has been connected.
The options I get in the Android Recovery menu are:
Reboot System Now
Apply Update From EXT
Apply Update From Data
Wipe Data/Factory Reset
Wipe Cache Partition
Burn Keys
I've tried selecting "Apply Update From EXT" and manually selecting the .img file. But it says it cannot verify the signature.
I'm literally out of ideas. Can anyone who knows what they're doing please help me!
TheOneIsBack said:
Hi all,
I'm in a complete head spin so I'm hoping someone here could shed some light on an issue I'm facing.
As the title says, I currently have a Buzz TV XPL 3000 android box. I'm trying to flash "Aidan's Android TV Custom Rom" onto it. But no matter what I try to do, I simply cannot get the Buzz TV box to interact with my Windows 10 PC.
I have 2 different male-to-male USB cables that I've tried plugging into the box and into my PC, but there is no link between them. The PC nor the Android box don't acknowledge any kind of connection. I know a lot of people will probably say that my cables aren't data cables, but I've actually used one of them previously to flash another Android device.
Whenever I plug the USB cables into my Android box and PC, the ONLY thing that happens, is the PC powers up the Android box. I've tried turning on USB debugging tools from the developer menu, but nothing. The PC doesn't even make a sound when I plug the cable in and there is nothing listed under device manager. Nothing appears on USB Burning Tools under devices.. Just nothing.
I've tried plugging in the USB cable, while holding down the reset button (located on the bottom of the box), but all that does is power on the Android box and load into "Android Recover". Still nothing detected on USB Burning Tools and still no acknowledgement from the PC that a USB device has been connected.
The options I get in the Android Recovery menu are:
Reboot System Now
Apply Update From EXT
Apply Update From Data
Wipe Data/Factory Reset
Wipe Cache Partition
Burn Keys
I've tried selecting "Apply Update From EXT" and manually selecting the .img file. But it says it cannot verify the signature.
I'm literally out of ideas. Can anyone who knows what they're doing please help me!
Click to expand...
Click to collapse
Hi, You Might Have To Try And Figure Out Mask rom Mode To Force your Device To Be Detected By USB Burn Tool If Using The Reset Button is Unsuccessful, Look For Mask rom Mode Information, You Can Upload Pictures Of Both Sides Of Your Logic Board we can try and figure it out
aidanmacgregor said:
Hi, You Might Have To Try And Figure Out Mask rom Mode To Force your Device To Be Detected By USB Burn Tool If Using The Reset Button is Unsuccessful, Look For Mask rom Mode Information, You Can Upload Pictures Of Both Sides Of Your Logic Board we can try and figure it out
Click to expand...
Click to collapse
Hey man,
Thanks for taking the time to reply.
I managed to get it working. Decided to give it another shot this morning and for some reason, first time around it worked. USB Burning Tool instantly picked the box up, installed perfectly and now I have it up and running!! It definitely seems a lot more snappier than my last firmware.
I do have a question though. With the previous stock firmware, my TV would pick the Android box up with a HDR signal. It no longer does this now. Is that to be expected with this rom or is there something I need to do?
Sir
TheOneIsBack said:
Hi all,
I'm in a complete head spin so I'm hoping someone here could shed some light on an issue I'm facing.
As the title says, I currently have a Buzz TV XPL 3000 android box. I'm trying to flash "Aidan's Android TV Custom Rom" onto it. But no matter what I try to do, I simply cannot get the Buzz TV box to interact with my Windows 10 PC.
I have 2 different male-to-male USB cables that I've tried plugging into the box and into my PC, but there is no link between them. The PC nor the Android box don't acknowledge any kind of connection. I know a lot of people will probably say that my cables aren't data cables, but I've actually used one of them previously to flash another Android device.
Whenever I plug the USB cables into my Android box and PC, the ONLY thing that happens, is the PC powers up the Android box. I've tried turning on USB debugging tools from the developer menu, but nothing. The PC doesn't even make a sound when I plug the cable in and there is nothing listed under device manager. Nothing appears on USB Burning Tools under devices.. Just nothing.
I've tried plugging in the USB cable, while holding down the reset button (located on the bottom of the box), but all that does is power on the Android box and load into "Android Recover". Still nothing detected on USB Burning Tools and still no acknowledgement from the PC that a USB device has been connected.
The options I get in the Android Recovery menu are:
Reboot System Now
Apply Update From EXT
Apply Update From Data
Wipe Data/Factory Reset
Wipe Cache Partition
Burn Keys
I've tried selecting "Apply Update From EXT" and manually selecting the .img file. But it says it cannot verify the signature.
I'm literally out of ideas. Can anyone who knows what they're doing please help me!
Click to expand...
Click to collapse
i just bought this buzz tv box. can you guide me ? Like how to root? Which is the best rom? Best apps ? Adaway etc?
Related
Hi guys and gals !
So a few days ago i rooted/flashed my friends s5830 regular way and uploaded VillainRom, yesterday he came by my house for he has tried to upload LucaRomv2 by using Rom Manager.
As a result the phone stays dead at "Samsung" logo on regular boot, altough if we plug it in the pc it will detect the modem, sd card(not acessing it for it must have usb debugging enabled) and all, just the screen that doesnt pass "Samsung" logo.
So the logical next step is if we have communication is to press the magic buttons VOL- + Home + power ON, and it does work for it goes to download mode, the only problem is has soon has i plug it on my VM (VBox 4.0) it just spits out usb error on VBox and does not connect.
I have tried all combinations Volume+ (flash mode) all enters, its just that when i plug it to VM it spits out an error.
I can even enter recovery mode by HOME+POWER (and for the looks of the register that show when i enter it it complains it cant find /data, /cache .... so my guess is Bootloader is still ok has it enters all these modes and just need to re-upload rom(basically the os)
So leading to usb error in VM i prompted to fully test my VMUSB everything works ok connecting it (storage drive, my vodafone smart, usb cam) and even the s5830 itself while on regular usb connection. This has worked ok before for this is the computer/vm i used it to flash it originally.
Just to relief up i will try the following today:
Clean format a physical computer with winxp and try do the process without VM in the middle
Should i make the usb jig with 301K ? Has anyone actually tried usb jig on ace ? Whats different from this mode to regular vol- + home + power ? From what it seems its factory download mode i guess, an alternative bloader.
In case of JTAG needed does anyone have flash specs ? I mean offsets and such ... i have access to JTAG tools here at work, just a matter of pinout and see if cpu/flash supported.
What is your general opinion about this ?
I have launched this thread for i have not found any info on this kind of situation, people usually have fully bricked (black screen) or can still access download mode and communicate with pc, i have not found similar characteristics.
Thank you !!
Did your friend a wipe after flashing the rom? If not then go to recovery and wipe Dalvik cache - cache and Data/factory reset.
If this doesn't work put the phone in Download Mode and flash with Odin and after this make a wipe.
Sent from my Transformer TF101 using Tapatalk
http://forum.xda-developers.com/showthread.php?p=16699494
steini81: I dont know exactly what he did, i have tried to wipe it via recovery manager but still no go, it still complains on missing mounts /data /cache .... as for flashing with odin i can start download mode on the phone but has soon has i connect it on the usb port of the computer it just gives out an error and does not go online.
Lovetz: I already read that post, the difference is i still can go to download mode, my problem is when i plug on pc it doesn´t go thats why i opened another thread.
--------------------------------
Maybe it´s just Virtualbox playing it´s pranks with async usb, can only eliminate this chance later on for i dont have the sga with me.
how about using a different machine? a machine with the drivers from Kies..
Try it on a Windows PC with Odin and Kies Drivers installed.
Sent from my Transformer TF101 using Tapatalk
Mundix: I´m already using skeys drivers, tried killing processes and not killing them, but this subject goes further then that because i think i have usb connectivity issues, now, it worked ok when i first flashed this device maybe something corrupted my usb1/2 modules for virtualbox (btw running debain squeeze-> virtualbox -> xpsp3, with full usb 2.0 extension loaded (already tried only usb 1.0 only has it has helped before on the first flash). Plus all usb devices work ok, including the samsung itself on "normal" boot so i dont know, maybe has its a raw dump vbox doesnt like it Later on i will format a computer with xpsp3, load skeys, odin and start from there,so basically you agree with my point
Steini81: yeps thats what im gonna do, but i do not use any windows machines all obsd/debian at home and work so ... only virtual, i´ll grab an old borrowed laptop and format it just for this.
-------------------------
Once again i just opened the thread because i havent found anyone with same situation, either its fully bricked or they can usb plugin. No post until now for usb download mode crash. I will follow up here maybe it might help someone in the future, or will confirm brick altough bloader boots and phone detected on "normal" mode.
Mizaiko said:
Mundix: I´m already using skeys drivers, tried killing processes and not killing them, but this subject goes further then that because i think i have usb connectivity issues, now, it worked ok when i first flashed this device maybe something corrupted my usb1/2 modules for virtualbox (btw running debain squeeze-> virtualbox -> xpsp3, with full usb 2.0 extension loaded (already tried only usb 1.0 only has it has helped before on the first flash). Plus all usb devices work ok, including the samsung itself on "normal" boot so i dont know, maybe has its a raw dump vbox doesnt like it Later on i will format a computer with xpsp3, load skeys, odin and start from there,so basically you agree with my point
Steini81: yeps thats what im gonna do, but i do not use any windows machines all obsd/debian at home and work so ... only virtual, i´ll grab an old borrowed laptop and format it just for this.
-------------------------
Once again i just opened the thread because i havent found anyone with same situation, either its fully bricked or they can usb plugin. No post until now for usb download mode crash. I will follow up here maybe it might help someone in the future, or will confirm brick altough bloader boots and phone detected on "normal" mode.
Click to expand...
Click to collapse
My sister's Backflip had a similar issue . All I did was to wipe EVERYTHING then reflash .
Sent from my Awesome Ace with fla.sh ROM and TAPATALK
SOLVED !
1 st Run:
Clean XPSP3 *Laptop* - "Unrecognized USB device ...", exactly has ocurring in VM.
No go.
2 nd Run:
USB JIG (tried 299K, 300K, 301K and 302K accurate resistors 1% tolerance) followed by above method.
No go.
3 rd Run:
Load WIN7PRO on a desktop for s-kies was giving problems with framework4 on XPSP3.
No go. "Unrecognized usb ..." just like on the laptop with XPSP3
Thats when it hit me, "some" devices(MODEM, STORAGE) load ok, odin driver does not, so it does have partial usb communication, this made me go way back in time when i had a USB MSI WIFI that would only work stable under USB 1.0 and was buggy under 2.0, so ...
Step 1 - Take the dust out that powered USB 1.0 Hub from drawer;
Step 2 - Make pigtail from internal desktop 12Vcc to power usb hub for Vcc stability
for power supply been lost like 4 house moves ago(yes i could go external powerless but ... just in case);
Step 3 - Cook a good home meal and mix it with some fine red wine;
Step 4 - Hook up usb hub, let win7 install, hook up SGA while on DOWNLOAD MODE (Vol- + Home + Power) and you can have the batery installed, no need to hot plug it, connect to usb hub.
Step 5 - Be amazed has it detects "Odin" has a new device and Odin square turns yellow just waiting for you to press start ...
*Personal Note : Do not stand up quickly after step 3 !
Now, the funny thing is if i move the USB 1.0 HUB to the XP SP3 Laptop its also a go, same results for in my Virtualbox install. Notice i tried it on 2 physical/1 virtual computer under VBOX4.
In conclusion:
If your SGA still boots to "samsung" and lets you get in Download/Flash/Recovery but gives out an USB communication errors, but still installs some devices like MODEM/Storage, all of this after a run from ROM MANAGER, please *DO* try to put an usb 1.0 hub between your computer and your SGA.
At this moment it works like a charm and i´ve just uploaded coderom.v2x-02, altough if i remove the USB HUB its back on the same problem, trough the hub it works ok aside i have 1.0 transfer speeds ...
Now, some help on debugging, arent there any logs on the system i could analyse? Should i dump trough JTAG ? What could of happened so that it has this symptom now ?
Anyways thanks for those who tried to help, just hope this helps someone in the future !
Hi, I have a Galaxy Player 4.0 that I rooted with SuperOneClick. It was working fine at first then a couple of weeks ago, I noticed that my PC no longer recognizes it as a device, it just charges when I plug it in. So, I looked around andn tried a few things:
Restarted it several times
Tried with all the different modes in USB settings
Tried with different cable
Tried with two other computers, a Mac Mini and a Win7 laptop
Tried to unroot, couldn't get that to work
Did a factory data reset
Nothing works. I can't remember anything I did since rooting that would cause this, except I installed the Samsung Kies driver on the PC. I can't remember if the USB mass storage was working after Kies. Does anyone have other ideas?
Bump. This is rather a big deal, as I cannot transfer files between my PC and Galaxy player in any way other than over WiFi, which does not work reliably. I don't have a microSD card adapter either.
You might want to check if anything related to samsung/android appears in the device manager. Alternatively, to use heimdall I use Zadig to switch from samsung's driver to libusb but it does show you everything connected to your computer via usb when you check the option to list all devices. You should try this with and without usb debuging enabled. If nothing shows up you know it id your player that is at fault.
Ben456 said:
You might want to check if anything related to samsung/android appears in the device manager. Alternatively, to use heimdall I use Zadig to switch from samsung's driver to libusb but it does show you everything connected to your computer via usb when you check the option to list all devices. You should try this with and without usb debuging enabled. If nothing shows up you know it id your player that is at fault.
Click to expand...
Click to collapse
Thanks,
The first time I plugged it in without USB debugging enabled nothing showed up, when I enabled USB debugging, in Zadig and Device manager there showed up an unknown device, trying to update driver in Device manager showed that it already had the best driver, and in zadig driver replacement failed. Now, when I plug it in, either with or without USB debugging enabled, nothing shows up anywhere. I have tried with other computers and other cables, and nothing works, so I am pretty sure it's the player. I am willing to to a complete factory system reset, but I don't know how.
InventiousTech said:
Hi, I have a Galaxy Player 4.0 that I rooted with SuperOneClick. It was working fine at first then a couple of weeks ago, I noticed that my PC no longer recognizes it as a device, it just charges when I plug it in. So, I looked around andn tried a few things:
Restarted it several times
Tried with all the different modes in USB settings
Tried with different cable
Tried with two other computers, a Mac Mini and a Win7 laptop
Tried to unroot, couldn't get that to work
Did a factory data reset
Nothing works. I can't remember anything I did since rooting that would cause this, except I installed the Samsung Kies driver on the PC. I can't remember if the USB mass storage was working after Kies. Does anyone have other ideas?
Click to expand...
Click to collapse
I'm having the same problem with my rooted 5.0. Although it's not a huge problem for me (I use dropbox for file syncing) I would love to sort this out, let me know if your factory reset works!
You can find it in the Privacy section of the settings menu.
InventiousTech said:
Thanks,
The first time I plugged it in without USB debugging enabled nothing showed up, when I enabled USB debugging, in Zadig and Device manager there showed up an unknown device, trying to update driver in Device manager showed that it already had the best driver, and in zadig driver replacement failed. Now, when I plug it in, either with or without USB debugging enabled, nothing shows up anywhere. I have tried with other computers and other cables, and nothing works, so I am pretty sure it's the player. I am willing to to a complete factory system reset, but I don't know how.
Click to expand...
Click to collapse
I suspect you have a faulty usb connector on your device, but it doesn't hurt to do a factory reset. But you might want to backup your data first Did you try to jerk the usb cable in your player? A loose/broken connector would explain all your problems. Even if it is a software problem, I can't see how to flash your device with the original firmware since you don't have a sdcard & usb doesn't work...
Btw, I was referring to zadig only to show the devices attached to your computer, not to change the driver!
Ben456 said:
I suspect you have a faulty usb connector on your device, but it doesn't hurt to do a factory reset. But you might want to backup your data first Did you try to jerk the usb cable in your player? A loose/broken connector would explain all your problems. Even if it is a software problem, I can't see how to flash your device with the original firmware since you don't have a sdcard & usb doesn't work...
Btw, I was referring to zadig only to show the devices attached to your computer, not to change the driver!
Click to expand...
Click to collapse
Thanks, I only tried to change the driver because it showed no driver already installed. I have a bit of electronics background so I may crack it open and take a look at the connector. I already tried the factory reset in the privacy menu, but that only wipes data apparently, not the system. I do have an sd card, I just don't have an adapter to the PC.
EDIT: After wiggling the cable around a bit, it showed the USB icon in the status bar, so I clicked connect USB mass storage, but the computer still showed a badly installed driver and then after some more wiggling the icon disappeared, so I am pretty sure it's a problem with the connector. BTW, how would I flash the stock firmware to unroot?
Firstly I apologise if this has been covered anywhere - I read a load of posts and did a load of searches but came up empty handed about this specific issue.
I bought a Galaxy Ace (GT-S5830 Baseband:S5830NEKA3 OS:2.2.1) as a dev device and it's been working fine up until today, and at some point it decided it doesn't want to be able to connect to my computers. I've tried three different computers, two different operating systems, and ever tried installing Kies (urk) with no luck.
The phone can charge over USB, saying that it's charging over AC, but that's all that happens.
I can't boot in to recovery mode as holding the power+middle button+vol up just gives me a ramdump message.
Can anyone help me out?
Martyn.h said:
Firstly I apologise if this has been covered anywhere - I read a load of posts and did a load of searches but came up empty handed about this specific issue.
I bought a Galaxy Ace (GT-S5830 Baseband:S5830NEKA3 OS:2.2.1) as a dev device and it's been working fine up until today, and at some point it decided it doesn't want to be able to connect to my computers. I've tried three different computers, two different operating systems, and ever tried installing Kies (urk) with no luck.
The phone can charge over USB, saying that it's charging over AC, but that's all that happens.
I can't boot in to recovery mode as holding the power+middle button+vol up just gives me a ramdump message.
Can anyone help me out?
Click to expand...
Click to collapse
When phone is turned off. Press and hold home+power/lock button untill it reaches recovery menu.
Check - that works. Thanks.
I'm now unsure as to how to proceed - neither adb devices nor fastboot devices are reporting anything back.
Connect device to pc. Open device manager (windows). Remove all drivers related to the ace and Samsung.
Remove the device and reboot the pc. Then connect the device. Windows update will detect the device and install the necessary drivers. If it doesn't automatically do that then open up device manager and install them manually by right clicking on the device and selecting update drivers from internet.
From the Galaxies to your Ace...!!
Thanks for your reply.
In windows there's no sign of any Samsung or Galaxy Ace drivers. Plugging it in to my Kubuntu machine gives me identical lsusb results as when not plugged in.
Have done a data wipe, checked that USB debugging is on and tried different cables
think it's screwed.
Think I could stick a ROM on the SD card and flash it? Would that work?
Martyn.h said:
Thanks for your reply.
In windows there's no sign of any Samsung or Galaxy Ace drivers. Plugging it in to my Kubuntu machine gives me identical lsusb results as when not plugged in.
Have done a data wipe, checked that USB debugging is on and tried different cables
think it's screwed.
Think I could stick a ROM on the SD card and flash it? Would that work?
Click to expand...
Click to collapse
hmm.. kies didnt work right? So i guess only option IMO would be card reader or CWM
Yep , the phone's USB port is frayed
This was sent from a Galaxy Ace. Problem?
Hi all, I will try to be as detailed as possible.
I have a MetroPCS LG MS323 which I bought as a second phone to use when I travel as my regular phone is CDMA and I wanted a GSM phone that I could use with a sim card. While on an overseas trip I paid a cellphone place to unlock the phone so I could use other carriers' sim card, it was working fine since then. However, as I don't use the phone on a regular basis it ended up sitting and the battery lost its charge. When I tried to charge it by usb, it started bootlooping (vibrate, LG logo, repeat). After that I pulled the battery and charged it using an external charger. The phone is not rooted. I tried the factory reset key combo, but it gets stuck on the screen which says factory reset processing........ endlessly. I tried to download kdz file and flash with LG flash tool but phone cannot get into download mode. When I press vol key and plug usb cable, it says LOADING.......... press volum up key until download mode starts But it gets stuck there and download mode never starts.
I downloaded adb and fastboot to a Windows 7 laptop, and LG drivers, but when I connect phone and open a terminal adb devices shows no phone connected.
I also downloaded Laf.img for this phone and Laf recovery tool for Windows but again I cannot seem to get computer to see the phone. If I try to use the tool it says "waiting for device"
One difficulty is to trying to plug phone to computer the right way.
Most of the threads say to have phone in battery charge mode with usb debugging enabled, but I can't select any settings if the phone is bricked.
If I just plug the phone to usb when it is turned off it shows a picture of battery but no sign of charging, and computer doesn't detect phone.
If I plug phone to usb first, then hold vol and power key the LG logo will go black and it vibrates, in that case sometimes the Windows laptop will see 2 folders, verinfo and image.
When I plug usb cable to Linux computer and phone is off, same thing just picture of battery but terminal only shows sda1 sda2 sda3 etc no sdb no sdc just like not detected.
If I hold vol down then plug usb it vibrates and stuck on LG logo.
I have also tried to plug usb, then press vol down and power until phone vibrates, then try to let go buttons before LG logo shows up. but it doesn't mount.
If I hold vol up and power, then plug usb. it vibrates and goes to LG logo.
Last night somehow I got it to mount on the linux computer but the file manager was going crazy opening multiple windows and a list of folders would show up for a second, disappear and reappear as if the system was trying to read the folders but having difficulty. Today I am not able to get it to mount.
I have downloaded a linux livecd with adb and fastboot, I haven't tried it yet because I am not sure the path to flash an img file from a different directory on the hard drive on the windows laptop.
I have downloaded aboot.img but don't know how I can flash it if I can't see the phone on any computers.
I have spent days searching for solutions but have not seen the exact same problem, other threads suggest things but often the symptoms are slightly different or with a different phone. So, first of all I need to know what kind of brick I have, because other solutions I have seen posted for completely black screen, or phone detected as qhsusb qualcomm etc. which seems like a different problem.
So the 2 main things are 1, to know which kind of brick because many of the solutions I see posted seem like a different problem.
second, what is the best way to plug to computer so I can see the phone?
I burned a live CD of FWUL and ran adb from linux, still says adb devices nothing shows up. usb cable is plugged in and phone is turned off. Am I doing this wrong? I held down power and vol down until phone vibrates and LG logo appears. adb devices - "list of devices attached" still has nothing showing.. I don't know why even in Linux I can't see any device attached. Also I tried with pressing vol up and power until phone vibrates.
ls /dev/sd* only shows sda sda1 sda2 etc
I have also looked at past threads about unlocking the L70 bootloader, but the bootloader.zip no longer links and the phone does not have busybox installed.
I tried to see it Windows Device Manager but it does not show up anywhere.
This probably won't help, but, when you're at this point, you'll try about anything.
Did you fully install the LG drivers on your PC? Obvious seeming question. I was doing an old Droid Bionic a couple months ago and didnt' switch the USB modes (charging, media, file transfer, whatever it had) to each mode before modding .
As a result, I bricked that Droid bad. It took me almost a week and a half to restore it. I'm not sure if LG drivers work the same way, though I've worked on plenty of them. I think I have an LG Leon still in the scrap heap as a result of trying to replace a cracked digitizer that was bonded to the LCD. If anyone needs parts for one, I've got em, cheap I think that's an MS345 if I recall.
equitube said:
This probably won't help, but, when you're at this point, you'll try about anything.
Did you fully install the LG drivers on your PC? Obvious seeming question. I was doing an old Droid Bionic a couple months ago and didnt' switch the USB modes (charging, media, file transfer, whatever it had) to each mode before modding .
As a result, I bricked that Droid bad. It took me almost a week and a half to restore it. I'm not sure if LG drivers work the same way, though I've worked on plenty of them. I think I have an LG Leon still in the scrap heap as a result of trying to replace a cracked digitizer that was bonded to the LCD. If anyone needs parts for one, I've got em, cheap I think that's an MS345 if I recall.
Click to expand...
Click to collapse
Thanks, yes I had installed latest LG drivers LGMobileDriver WHQL Ver 4.2.0 before trying to flash .kdz file.
A tiny bit of progress to report, after getting a perfect timing to release the power and vol down keys I was finally able to connect to Windows machine. while waiting for drivers to install it was detected as QHSUSB_BULK in device manager, after drivers loaded now it is listed as LGE AndroidNet USB Serial {port (COM4). However when I run adb I still cannot see an attached device. I will look at solutions for the specific type of brick problem which has now been identified.
fofopuka said:
Thanks, yes I had installed latest LG drivers LGMobileDriver WHQL Ver 4.2.0 before trying to flash .kdz file.
Click to expand...
Click to collapse
What I meant was after initially installing the drivers did you switch the USB mode on your LG to all possible settings? Some drivers (like Moto) install more functions only when first called. you'll know if you switch from say charging to MTP or RNDIS you'll see driver install reopen.
also when you first ran ADB and plugged in the phone you probably should have seen more drivers install.
Forgive me if I seem to insult your intelligence. I'm an IT pro w 30 yrs in tech and I didn't know about the multi driver USB functions.
Tom Sgt aka Rootjunky has a good video on this that i initially didn't watch figuring I'd been installing drivers forever. 5 more minutes of watching it would have saved near 40 hrs of work and research
and when r
equitube said:
What I meant was after initially installing the drivers did you switch the USB mode on your LG to all possible settings? Some drivers (like Moto) install more functions only when first called. you'll know if you switch from say charging to MTP or RNDIS you'll see driver install reopen.
also when you first ran ADB and plugged in the phone you probably should have seen more drivers install.
Forgive me if I seem to insult your intelligence. I'm an IT pro w 30 yrs in tech and I didn't know about the multi driver USB functions.
Tom Sgt aka Rootjunky has a good video on this that i initially didn't watch figuring I'd been installing drivers forever. 5 more minutes of watching it would have saved near 40 hrs of work and research
and when r
Click to expand...
Click to collapse
thanks, I found his video for the G2 and no, I have never seen that with the drivers before! good to know. You can't insult my intelligence because most of this is over my head and I'm just trying to follow stuff I found with Google on XDA......
I downloaded and installed the Qualcomm drivers to try and identify if I have the 9006 or 9008 variety brick. However now when I plug in the phone Windows waits to install drivers, then says successful, when I look in device manager now I can't find the phone. But I did notice on the taskbar now there appears an icon named "intel graphics media accelerator driver for mobile" perhaps that is the driver Windows assigned to it? Device manager does have Intel Graphics Media Accelerator under display adapters. The other weird thing is that now it shows the battery as charging, which it never did the other times I plugged it into usb.
fofopuka said:
thanks, I found his video for the G2 and no, I have never seen that with the drivers before! good to know. You can't insult my intelligence because most of this is over my head and I'm just trying to follow stuff I found with Google on XDA......
I downloaded and installed the Qualcomm drivers to try and identify if I have the 9006 or 9008 variety brick. However now when I plug in the phone Windows waits to install drivers, then says successful, when I look in device manager now I can't find the phone. But I did notice on the taskbar now there appears an icon named "intel graphics media accelerator driver for mobile" perhaps that is the driver Windows assigned to it? Device manager does have Intel Graphics Media Accelerator under display adapters. The other weird thing is that now it shows the battery as charging, which it never did the other times I plugged it into usb.
Click to expand...
Click to collapse
have you seen this thread.
https://forum.xda-developers.com/showthread.php?t=2773123
it has the firmware for your model links to drivers and the LG flash tool, (which is warned against newbies (what the hey, it can't get much worse, we were all newbies once, )
Can you boot into fastboot? if so, you could flash the firmware with that.
equitube said:
have you seen this thread.
https://forum.xda-developers.com/showthread.php?t=2773123
it has the firmware for your model links to drivers and the LG flash tool, (which is warned against newbies (what the hey, it can't get much worse, we were all newbies once, )
Can you boot into fastboot? if so, you could flash the firmware with that.
Click to expand...
Click to collapse
Hi, yes although those links no longer work I have found the drivers and flashtool elsewhere. If I try to run flashtool it cannot see the phone. I cannot get into fastboot, and download mode won't load. I cannot see the phone on any Linux machine. The most I can do it see the phone as E: Qualcomm MMC storage USB device in Device Manager, but no other details. Explorer can see 2 folders, image and verinfo. Is there anything I can do with these folders in Windows? adb and fastboot run from terminal still do not list any attached device. Windows did a search for drivers for QHSUSB_BULK, although in device manager it still says LGE AndroidNet USB Serial Port (COM5).
What I really want to do at this point is push aboot.img to the phone, but for some reason I can't access the phone with Linux or adb. maybe because it did not have usb debugging enabled before it bricked. So many of the threads I have seen require a working phone to implement the steps, is there any way to enable usb debugging when the phone doesn't work?
fofopuka said:
Hi, yes although those links no longer work I have found the drivers and flashtool elsewhere. If I try to run flashtool it cannot see the phone. I cannot get into fastboot, and download mode won't load. I cannot see the phone on any Linux machine. The most I can do it see the phone as E: Qualcomm MMC storage USB device in Device Manager, but no other details. Explorer can see 2 folders, image and verinfo. Is there anything I can do with these folders in Windows? adb and fastboot run from terminal still do not list any attached device. Windows did a search for drivers for QHSUSB_BULK, although in device manager it still says LGE AndroidNet USB Serial Port (COM5).
What I really want to do at this point is push aboot.img to the phone, but for some reason I can't access the phone with Linux or adb. maybe because it did not have usb debugging enabled before it bricked. So many of the threads I have seen require a working phone to implement the steps, is there any way to enable usb debugging when the phone doesn't work?
Click to expand...
Click to collapse
Of course, I had forgotten about that. In order to use fastboot, most flashing tools, you HAVE to have USB debugging on.
There are occasional ways around this, though they are few. I do seem to recall oding it on that LG Leon. OR it may have been a Moto e or G, let me look back at previous threads i've asked for help in.
(Hmm, perhaps taking notes, or just leaving a webcam running while I'm doing a new device might be valuable in the future, I think with remarkable hindsight.) :cyclops:
---------- Post added at 02:28 AM ---------- Previous post was at 02:26 AM ----------
And no, you can't do anything to Android files in Windows, except see them. they are generally a different file system
One of the difficulties is just plugging it to a PC. 9 out of 10 times it is not recognized and nothing happens. So far the only way that seems to occasionally work is to plug the usb cable to the Windows 7 laptop, hold vol down and power, release both as soon as it vibrates. Most of the time I can't get it timed exactly right, but if I'm lucky sometimes Windows will detect the usb connection by following these steps. If I try on a Linux machine nothing happens, phone stays invisible. The most I've gotten with Linux is to charge the battery, but will not mount.
It is just a stock phone, not rooted, no busybox, no developer options enabled.
I've been booting LibreELEC/CoreELEC from SD card on my AZW (Beelink) W95 (S905W) box for years now. Yesterday I tried booting into the stock Android system (7.1 I think- I haven't done it for a while) but it wouldn't boot. Not being one to leave well enough alone I decided to try a reset using a toothpick in the reset hole by the power plug. It flashed the start screen for a split second and then stopped. After that it wouldn't boot off the CoreELEC SD card either.
I've tried a clean CoreELEC install, stock firmware, Amlogic Burn Card Maker, and TWRP on the SD card - none of them get me past a black screen.
I don't think the reset button is doing anything (I depress it while plugging in the power jack). In fact, I don't know if it ever worked. My box had previously always booted off a SD card if it was inserted in the slot without having to do anything special.
My box isn't completely dead but comatose. The signs of life are:
1) The blue LED comes on when I plug in the power cord.
2) After about 20 minutes or so the blue LED will go off. If I press the power button on the remote it comes back on.
3) My router sees it on my network as active. But I get connection refused when I try access it using Windows File Explorer or try to SSH into it using Putty.
4) When I insert a SD card into the slot it writes Andriod and LOST.DIR folders to it.
I haven't tried the Amlogic USB Burning Tool yet because I don't have an USB 2.0 Type A male to male cable - but I've ordered one. My concern is I won't be able to put it in reset mode since I'm not sure the reset button does anything (but I can feel it click).
Is there anything else I should try while I'm waiting for my cable to arrive?
Any recommendations on how I should proceed once my cable arrives?
Thanks
RKCRLR said:
I've been booting LibreELEC/CoreELEC from SD card on my AZW (Beelink) W95 (S905W) box for years now. Yesterday I tried booting into the stock Android system (7.1 I think- I haven't done it for a while) but it wouldn't boot. Not being one to leave well enough alone I decided to try a reset using a toothpick in the reset hole by the power plug. It flashed the start screen for a split second and then stopped. After that it wouldn't boot off the CoreELEC SD card either.
I've tried a clean CoreELEC install, stock firmware, Amlogic Burn Card Maker, and TWRP on the SD card - none of them get me past a black screen.
I don't think the reset button is doing anything (I depress it while plugging in the power jack). In fact, I don't know if it ever worked. My box had previously always booted off a SD card if it was inserted in the slot without having to do anything special.
My box isn't completely dead but comatose. The signs of life are:
1) The blue LED comes on when I plug in the power cord.
2) After about 20 minutes or so the blue LED will go off. If I press the power button on the remote it comes back on.
3) My router sees it on my network as active. But I get connection refused when I try access it using Windows File Explorer or try to SSH into it using Putty.
4) When I insert a SD card into the slot it writes Andriod and LOST.DIR folders to it.
I haven't tried the Amlogic USB Burning Tool yet because I don't have an USB 2.0 Type A male to male cable - but I've ordered one. My concern is I won't be able to put it in reset mode since I'm not sure the reset button does anything (but I can feel it click).
Is there anything else I should try while I'm waiting for my cable to arrive?
Any recommendations on how I should proceed once my cable arrives?
Thanks
Click to expand...
Click to collapse
Hi, your device seems to be in a strange state currently, only thing i can reccomend is trying a few firmwares to see what works for you, you should be able to flash most s905w based roms, if your device cant be detected by USB burn tool you might need to use ask Rom Mode" to force your box to be detected by burn tool, this makes it almost impossible to brick a box
Thanks for the suggestions, I'm a complete newbie at this.
Is the Ask ROM Mode an option in USB Burning Tool?
I have an OEM W95 firmware update file (in both .img and and an OTA in .zip format) but they may be older than what is currently on the box. I also found a TWRP file for the S905W. But I don't know how to use any of these.
I downloaded the AMLogic Tools 6.0.0 and tried the AMLogic Flash Tool since it seems to work through the Ethernet port. I assumed this because you access the box via an IP address but I really don't know. I watched the video but couldn't find any detailed instructions on how to use it.
When I pressed the Connect button it said it connected and I had the green Connected display (I was connecting through my LAN - I don't know if I should connect directly with an ethernet cable). I loaded my .img file and said Flash. It says it is flashing and a second or so later it says SUCCESS! However the box still doesn't boot. I tried both Boot and Recovery (I don't know which option I should choose). I think that the SUCCESS! message is incorrect since I get the message even if I press the Flash button without the box connected. However, I can't connect to the box without the ethernet cable connected so the connected message seems correct.
Am I using the AMLogic Flash Tool correctly?
I was thinking about trying the S905W atvExperience ROM but thought I'd wait until I got my USB cable before before doing something more drastic.
Any other suggestions?
Thanks
OK, so my male to male USB cable arrived and I managed to get my box un-bricked using AMLogic USB Burning tool with a factory .img file. It took several tries. I kept getting errors when it tried to erase the bootloader or would get to 7%, progress would stop for about a minute, and then Burning Tool would close.
I finally got it to proceed all the way by holding in the reset button, plugging in the USB cable (no power cable), and keeping the reset button pushed the whole time (I don't know if this was just a coincidence). Also, I hadn't closed Burning Tool after the previous error erasing the bootloader. I'm posting all this in case someone else has a similar problem.
After that, it still wouldn't boot of the CoreELEC SD card with the reset button pushed down. It would go straight into the Android OS. I got it to boot into CoreELEC by installing the Reboot to LibreELEC app. Now it always restarts in CoreELEC the way it used to when the SD card is left in. I think this is how I got LibreELEC working years ago.
So, now I'm contemplating installing atvXperience but I have a couple of questions:
What would be the best way to install atvXperience without being able to the reset button to put the box into recovery mode?
What would be the best way to prepare for not being able to use the reset button to put the box into recovery mode if something were to go wrong during flashing?
Thanks for any help.
OK, so my male to male USB cable arrived and I managed to get my box un-bricked using AMLogic USB Burning tool with a factory .img file. It took several tries. I kept getting errors when it tried to erase the bootloader or would get to 7%, progress would stop for about a minute, and then Burning Tool would close.
I finally got it to proceed all the way by holding in the reset button, plugging in the USB cable (no power cable), and keeping the reset button pushed the whole time (I don't know if this was just a coincidence). Also, I hadn't closed Burning Tool after the previous error erasing the bootloader. I'm posting all this in case someone else has a similar problem.
After that, it still wouldn't boot of the CoreELEC SD card with the reset button pushed down. It would go straight into the Android OS. I got it to boot into CoreELEC by installing the Reboot to LibreELEC app. Now it always restarts in CoreELEC the way it used to when the SD card is left in. I think this is how I got LibreELEC working years ago.
So, now I'm contemplating installing atvXperience but I have a couple of questions:
What would be the best way to install atvXperience without being able to the reset button to put the box into recovery mode? (I did try flashing atvXperience once using USB Burning Tool but I got the same error erasing bootloader)
What would be the best way to prepare for not being able to use the reset button to put the box into recovery mode if something were to go wrong during flashing?
Thanks for any help.
Another follow up post for anyone with the same problem. I did some searching and found out I'm not the only one with a box that the reset button doesn't work. A work around for them was to connect the male to male USB cable, load the image into Burning Tool, press Start, and then plug in the power supply. The image file would then start flashing.
However, my box would start booting as soon as I connected the USB cable (didn't need the power supply). So I loaded the image into Burning Tool, pressed Start, and then connected the USB cable. This appears to be the work around for my box (I probably did this when I got my box to recover the first time - holding the reset button was probably irrelevant).
This procedure works for the stock firmware but when I try to flash the atvXperience image file the box hangs at 7%. So I still need some help there.
Also, is there a ATV ROM better suited for my S905W box (2/16 GB)?
W95 is really ****ing box whenever you feel you get off from the current problem will be into next one.
I have installed atvx Rom but afterthat when I tried adian rom my device bricked.
Without Ubt flashing it's connect but as I start flash it's sound unknown device and give flash error