Installation / Removal > Sandisk - Installation/Removal
Accidentally Deleted Partition
Chronon:
That usually means that e200tool is not located in the current directory.
Johnv:
Sorry about that, I had to make it an executable with the command below it, forgot about that.
However, I ran into (-71, Protocol error). According to a thread on anythingbutipod it's because I'm not holding record long enough, but I'm not sure about that.
It also tells me that it could be the i2c but I don't have that for the e270 nor does the e200tool page.
Also, if anyone is able to take it from theirs(e270) and post it I would greatly appreciate it.
Nevermind, I learned that the 280 one is fine to use.
I ran into another( :() problem though:
Searching for device 6666:e200 ... 9 8 7 6 5 4 3 2 1 0 not found! ]Needed to add the usb stub, got past that, but ran into the same error.Tried this again, and it doesn't work anymore.
Alright I'm going to post what the errors have been so far so you can see the full thing:
Using:./e200tool recover BL_SD_boardSupportSD.rom
--- Quote ---e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... found!
Initializing USB stub (4780 bytes) ... done!
Writing 'BL_SD_boardSupportSD.rom' to address 0x10600000
Searching for device 6666:e200 ... 9 found!
Write at 0x10600276
Control message (-71, Protocol error)
--- End quote ---
Using:./e200tool i2cprogram i2c-e280.bin
--- Quote ---e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Programming i2c rom (address=87) range 0x0000-0x2000 from 'i2c-e280.bin'
Searching for device 6666:e200 ... found!
Uploading at 0x052b
Control message (-71, Protocol error)
--- End quote ---
Using:./e200tool recover PP5022.mi4
--- Quote ---e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... found!
Initializing USB stub (4780 bytes) ... done!
Writing 'PP5022.mi4' to address 0x10600000
Searching for device 6666:e200 ... 9 found!
Write at 0x106003b1
Control message (-71, Protocol error)
--- End quote ---
The places to write at alter and I still get this message, I have run out of things to try I think.
Well, I've tried doing the above commands for about 2 hours and I still get the same thing.
So, guys, is there anything else I can do to get this thing to work?
Johnv:
So do you think I should just give up on this thing?
Johnv:
Okay guys, since I've been stuck at this roadblock I'm going to go ahead and purchase the Sansa Fuze. Maybe there will be a fix to this at a later time.
Navigation
[0] Message Index
[*] Previous page
Go to full version