Author Topic: bricked?  (Read 4744 times)

jaykay

  • Newbie
  • *
  • Posts: 10
Re: bricked?
« Reply #15 on: September 12, 2008, 06:22:29 PM »
 :D Thanks Traf! The penny dropped when you said 2 files, I had unzipped to the SD and they were in a folder!

Cheers again.....

JK

traf

  • Guest
Re: bricked?
« Reply #16 on: September 13, 2008, 12:27:44 PM »
result !!
downloaded recovery file for the elonexonet and tried it on my t+ and all the original look and settings are back
wouldn't work using the instructions on the website had to enter ctrl,alt and f3.
i'm happy that i've finally  got a recovery "backup" and i can play about more
ps the look of the default theme on the elonex is far better than the epc700 that i had earlier recovered my (daughters) onet+ with maybe I'll have a start with the theme colours.

womble

  • Newbie
  • *
  • Posts: 19
Re: bricked?
« Reply #17 on: September 13, 2008, 12:55:00 PM »
Hi,

Where did you get the OneT+ recovery from? The one on the elonex site is still bad?


Ooops sorry didnt realise you DL the OneT and not the Onet+  :)
« Last Edit: September 13, 2008, 12:56:40 PM by womble »

womble

  • Newbie
  • *
  • Posts: 19
Re: bricked?
« Reply #18 on: September 13, 2008, 01:16:37 PM »
Hi,

Does anyone have a copy of the Onet recovery file as DL from Elonex seems to be wanting to take hours!

traf

  • Guest
Re: bricked?
« Reply #19 on: September 13, 2008, 05:21:43 PM »

womble

  • Newbie
  • *
  • Posts: 19
Re: bricked?
« Reply #20 on: September 15, 2008, 03:12:21 PM »
Looks like Elonex has now changed the OneT+ recovery link to just down load the OneT recovery file?
Mine is now bricked and wont even go past the Elonex boot screen, Thanks Elonex for making it worse!

jaykay

  • Newbie
  • *
  • Posts: 10
Re: bricked?
« Reply #21 on: September 16, 2008, 12:42:44 PM »
Womble - This might help... when I restored mine instead of the keys elonex instruct you to use, I just pressed & held F3. This took me into the recovery mode and I used the One T image. Good luck,

JK

womble

  • Newbie
  • *
  • Posts: 19
Re: bricked?
« Reply #22 on: September 17, 2008, 09:07:16 PM »
Cool I got the desktop back using the OneT firmware  ;D
Ethernet and wifi still don't work though  :'(

m1bxd

  • Newbie
  • *
  • Posts: 2
Re: bricked?
« Reply #23 on: September 22, 2008, 09:37:48 PM »
I have a Onet+, problems with wifi, support suggested I have a go at re-imaging - but now I have brick...

Steps to brick - "F3" to get recovery prompt

Followed format and image instructions:

Then got:

Recovery
...open input file: No such file or directory
real    0m 0.01s
user    0m 0.01s
sys    0m 0.01s
Syncing... Please wait for a moment
 finished

---
Then I get stuck on this "Elonex" branding screen :-(

Any ideas please?

womble

  • Newbie
  • *
  • Posts: 19
Re: bricked?
« Reply #24 on: September 25, 2008, 12:44:48 PM »
I had that error the first time I did a recovery, after a few attempts of doing more recoveries using the Elonex firmware and the EP700 firmware it eventually recovered ok.
Only thing is that it still didn't fix the Eth port or the Wireless so I called the support again. I thought I would hummor them by following their instructions to do a recovery while they were on the phone and guess what it did the same thing again and came up with that error. This completely baffled the support department and they have gone away to talk to Elonex direct and get them to call me back.

robin2204

  • Newbie
  • *
  • Posts: 5
Re: bricked?
« Reply #25 on: September 27, 2008, 11:33:51 PM »
m1bxd - I'm in the same position - have tried various files but none seem to work - I think the first time through it said recovery successful but failed to reboot, but I wasn't really watching and it cleared the screen very quickly so I may well be wrong, but after that I've retried and retried, and am getting the same as you. Support don't seem to have any idea what to do - excitingly I've now been passed to a higher level who will contact me within 72 hours.   Whoopee !!!

oldgrumpyman

  • Newbie
  • *
  • Posts: 14
Re: bricked? @m1bxd & robin2204
« Reply #26 on: October 02, 2008, 05:32:15 AM »
I found that these Elonex recovery files on root of a USB stick failed:

Recovery.rec 335,12o KB
uImage 1104 KB

I got the same "Caution: the format process will start once you..  and cannot be stopped.
Input your choice"  [s +Enter]

It then looks as everything is going well, but returned in my case:

".......................................................332763136
open inpt file no such file or directory
real  2m 1.93s
user 0m 0.70s
sys  1m 43.81s
syncing.......Please wait for a moment
finished"

And then it rebooted - but all it would do was get as far as the black Elonex boot up screen.  The above is quick - I had to photograph the screen to get those details.

It appears that there's an overwrite instruction built into the Elonex recovery image that doesn't work if you've changed anything in the file system, or maybe the main problem is that their programming for USB doesn't work. Fortunately SD does.
The OS and updated application programs overflow the main 128MB of memory when the Elonex ships, part of these are already written into the 1GB/2GB Solid State Disk (SSD).
Provided you have copied everything you want to re-install, it is clearly better to format the SSD before writing a fresh copy of the OS - but the Elonex instructions don't provide that option.

Using the very same files as above on an SD card, and following the instructions on the littlelinuxlaptop web-site - you should be able to re-install by formatting the SSD first.  Just follow the instructions on littlelinuxlaptop.com.

I don't know exactly what the Elonex recovery image re-installs, but it should be the boot system (in main memory 128MB, equivalent to flashing BIOS) and original OS with the filing system and some applications  that fit in the 128MB. We know this from the file sizes of the Trendtac recovery image.

In addition the Elonex recovery image has more OS than the Trendtac  (built in Wifi), and both slipstreamed OS updates and updated application programs that are written on the SSD drive.   But in making it as simple as possible by only providing for an overwrite, they seem to have not got the USB parts right, although the SD component clearly works.

Hope this helps.


robin2204

  • Newbie
  • *
  • Posts: 5
Re: bricked?
« Reply #27 on: October 03, 2008, 09:09:57 AM »
I had problems running the restore from a USB stick, which I'd formatted to FAT32 as they said - under XP that was the only option. Someone, in another thread on here suggested that I should be using FAT16 - I took an old 512m SD card out of an old camera and just copied the 2 files onto it without formatting it so don't know what format it was, stuck it in the slot, and it worked - now whether its the SD card as opposed to the USB stick, or the formatting, that did the trick, I can only guess, but it worked...
oh, and I'm still waiting for Elonex advanced level support to ring me back 'within 72hours' from a week ago...

oldgrumpyman

  • Newbie
  • *
  • Posts: 14
Re: bricked? @Robin2204
« Reply #28 on: October 04, 2008, 02:47:24 PM »
Confident that I could restore the ONEt+ from the Elonex recovery image, placed on the root of a Veho 4GB SDHC, I completed trying all the available formats on a USB stick.  Because I had already tried so many, and before I restored any of the data files or installed additional programs (Xterm etc) I wanted to be sure that I had tried everything on USB that I could.

I've got 3x 1GB, 2x 2GB, that I no longer use (and 2x 4GB that still get some use).
By far the fastest of these in the ONEt seemed to be a Silver Pearl 1GB - a 9GB DVD, transformed to QVGA avi @15FPS, 128kbps stereo sound, played smoothly straight off this USB stick formatted fat16.

It's a not a good idea to format USB sticks too much, they have a limited life. It's also best to leave them fat16/fat32 because formatting NTFS concentrates on re-use of memory areas, rather than spreading use out more over the whole memory.  But I formatted the 1GB & 2GB sticks as fat16, fat32, NTFS, and under Linux to ext3.   The ONEt+ could read and write to all these formats, but wouldn't install the recovery image from any of them.  (It also helps that I've three desktop PC's running with memory card reader/writers - as well as a laptop;  the desktops have been kept because they all have two or more TV tuners each, another story)
 
So the empirical evidence is that trying to install the current Elonex recovery image from a USB stick, doesn't work.
This doesn't mean that a future recovery image also will not work, from a USB.
But it should save a lot of time and frustration to others, who are trying and failing to attempt install the current  recovery image from USB. 

It's a reiteration, but the current Elonex recovery image only works off an SD or SDHC card (but not an SD MMC card).

I also tried using a Kingston 512MB MMC SD card, formatted fat16 + fat32, with odd effects.
The card appeared to be recognised, showed up in the file system, but could not be read or written to.
However, it did not appear as loaded in the tray icons, and the WiFi tray icon disappeared too, although WiFi could be started manually and worked.   
No idea why, and needless to say the ONEt would not run the recovery image from this MMC SD.

It would help others,  if people who successfully install the Elonex recovery image, post here the make, model, size and format details of the card they used.   



 

oldbloke

  • Full Member
  • ***
  • Posts: 116
  • Hemel Hempstead
Re: bricked? @Robin2204
« Reply #29 on: October 04, 2008, 08:46:19 PM »
<snip>
It would help others,  if people who successfully install the Elonex recovery image, post here the make, model, size and format details of the card they used.   
OK. I have successfully recovered both MBR and OS using a 2GB Toshiba SD card formatted to FAT16 (as it was delivered) using the latest two Elonex files and instructions.
Martin
I know I have my brain backed-up somewhere............