Search results for query: *

If bricked then you should be able to connect with BCM3 without issue The HW fault is a long shot from what you have said but worth checking voltages. If you do get it going, this is a great source of V2 images (I'm also stuck with v2 images on my dragonworth) Index of /images/Dragonworth

Maybe there's another hw fault and it's not related to the box being bricked at all. If for some reason your box isn't getting 3v @ pin 12 your box wouldn't start and BCM3 would be unable to recognize the chip, may be worth checking

Try switching sda and scl also ensure power is ON on your solo2 my best connection order was to connect all cabling, start BCM3 power on Jtag board then power on Solo2 Even if you get connected it's still likely you will need to change the nand as you will probably still get the start offset error

I have both the 1 and 2 jumper boards. both use the same driver, so I doubt that'll help. Whack 7-64 on your drive and see if that works. I've just reconnected my 2 jumper device and it's still fine. Here's a backup of the driver installed taken using the free driverbackup2 tool. Dropbox -...

are you using a Virtual Machine, maybe it's that or perhaps windows doesn't supply drivers online anymore for it's unsupported OS. Give 7 another go is all i can suggest. Plus Don't run Setup but the .msi files

If you have put a v4 image on a v2 box the chance of jtagging working is very remote. even it the nand has been previously changed. BCM USB is not needed as the drivers are built into the studio3 software. If you have installed drivers from the broadcom website you will not get your jtag board...

If your using Dragonworth V2 Do Not Install Kodi from the Plugins Feed. It will update the drivers on your box and brick it again!!! You have been warned!!

I'm a little worried by this MAC ADDRESS CHECKSUM FAILED. MAC ADDRESS MUST BE PROGRAMMED!, using macprog command But am hoping this will disappear when you flash your box

Obviously, your bootloader is now fine. use front USB port, hold Power Button on front of box for 30 seconds after powering on. I would try Dragonworth images from here (we don't know if you need V2 or V4 firmware) so Dragonworth is safest Index of /images Also, rename this file...

Agreed, I find most thumb drives troublesome, I have 20 or so and always dig out my old faithful 2GB Kingston, it never fails (although does require low lever formatting from time to time) Also, hook up your Solo2 via RS232 null modem cable and check if you see a boot log

you need to connect SDA, SCL and Ground. (3 wires not 4) then start BCM3 then power on your solo2mini If you still get disconnected, recheck soldering. Failing that, I"ve no idea. Device manager should recognise your device as a "Broadcom Test adaptor" if you see "uninitilised" you still have...

do not connect 3.3v, and power on your solo2. try switching SDA / SCL connections

I think you need net framework 3. give this a try http://support.lenovo.com/gb/en/downloads/2110

all files are in my previous post (post 49) flash the bootloader bin file in my Jtag_solo2.zip - Google Drive download link

all you need is here Jtag_solo2.zip - Google Drive flash solo2 bootloader.bin

Yes, that's what I used, no need to use 3.3v though

[DOWNLOAD] Broadbanstudio 3 for Solo2 Clone Jtag

He's probably referring to the mainboard regulators, U 801 (the most commonly damaged) U802 and U805. although there are a bunch of Reg's on the PSU itself that once failed will be really hard to diagnose. My advice would be to change out the caps on the PSU for good quality, named brand ones...

That all depends on what version you have or whether you have updated to V4 security. If unsure use V2 clone images (if you have to run V2 images, Do Not Install Kodi, as this will replace your drivers and Brick your Box) if a V4 box use V4 images. Here is a good source of up to date images, If...

maybe this 100% New Original TC58NVG1S3ETA00 TSOP48-in Integrated Circuits from Electronic Components & Supplies on Aliexpress.com | Alibaba Group