maemo.org - Talk
Page 3 of 3 12 3
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Applications (https://talk.maemo.org/forumdisplay.php?f=41)
-   -   unable to uninstall *#Starhsah Enabler (https://talk.maemo.org/showthread.php?t=73707)

michaaa62 2013-02-08 18:00
Re: unable to uninstall *#Starhsah Enabler
 
Please try to reflash the kernel only from a firmware image. It seems the failed kernel install makes the device fail.

This is the wiki article giving you the instructions and informations about the processhttp://wiki.maemo.org/Updating_the_t...rt_topic.21.29

Freddie 2013-02-09 07:10
Re: unable to uninstall *#Starhsah Enabler
 
Quote:
Originally Posted by michaaa62 (Post 1321852)
Please try to reflash the kernel only from a firmware image. It seems the failed kernel install makes the device fail.

This is the wiki article giving you the instructions and informations about the processhttp://wiki.maemo.org/Updating_the_t...rt_topic.21.29
↲i managed to see the error just before it goes off, it says, "internal application error. "camera" closed" the off it goes. Am yet to try flashing the firmware,

michaaa62 2013-02-09 07:57
Re: unable to uninstall *#Starhsah Enabler
 
Quote:
Originally Posted by Freddie (Post 1321942)
↲i managed to see the error just before it goes off, it says, "internal application error. "camera" closed" the off it goes. Am yet to try flashing the firmware,
Do not just flash the firmware, try the kernel-only option before. Because camera also depends on kernel modules, that might just got corrupted during the failed kernel change.

Freddie 2013-02-09 15:32
Re: unable to uninstall *#Starhsah Enabler
 
Quote:
Originally Posted by michaaa62 (Post 1321948)
Do not just flash the firmware, try the kernel-only option before. Because camera also depends on kernel modules, that might just got corrupted during the failed kernel change.
The biggest problem I have is that I can't detect my phone. I later installed some windows xp package which recognizes the phone but in Mass Storage mode hence the pc suite or the updater can't explore the device until it is turned into pc suite mode.

I tried the flasher style to no avail since it looks like I'll have to do this from linux since the command looks ubuntuish "sudo....."

To be honest, am not well acquitted with deep programming, anybody can help me roll out this one? I will have to learn more i know but for now I need my tablet back up....:o

The only point am missing and it makes it hard is..."Flashing only the kernel from a FIASCO image"

michaaa62 2013-02-09 17:32
Re: unable to uninstall *#Starhsah Enabler
 
Simply face it, Maemo is also Debian-based, a little knowledge about linux will not hurt you too bad. Windows USB-driver seem to fail in certain situations. But you also could just look into running linux in a virtualbox to access the phone.

Prepare your folder with the fiasco image and the flasher utility package in an easy to access place on your hard disk, like drive C:.
Grab the Live-CD from ftp://ftp.lug.udel.edu/pub/siduction...1212092122.iso This is a Debian system.

Boot your PC from the CD. May be you have to access the BIOS settings to change the boot order to start the CD. Inside the running Debian-Live-CD start a terminal application, gain root rights
Code:
su
Mount the hard disk
Code:
mount /dev/sda2 /media/diskpart2
May be you have to change the number in the code to reflect your PC's setup. Change into the directory (folder), where you have the files ready
Code:
cd /media/diskpart2
That is if you have the files on drive C:. Now install the flasher-utility
Code:
dpkg -i maemo-flasher-3.5*
Shut down your phone. Start the flasher in the terminal
Code:
flasher3.5 -F RX-51_2009SE_3.2010.02-8_PR_COMBINED_MR0_ARM.bin --flash-only=kernel -f -R
Connect the phone now to your PC's USB. This will flash the kernel only from the fiasco image to boot up the phone. If it boots everything is fine.

If not, you have to use the command without the flash-only=kernel option to reset the phone.

Hope it helps!

Please feel free to ask, if necessary

cheers Micha

Freddie 2013-02-10 15:17
Re: unable to uninstall *#Starhsah Enabler
 
Quote:
Originally Posted by michaaa62 (Post 1322029)
Simply face it, Maemo is also Debian-based, a little knowledge about linux will not hurt you too bad. Windows USB-driver seem to fail in certain situations. But you also could just look into running linux in a virtualbox to access the phone.

Prepare your folder with the fiasco image and the flasher utility package in an easy to access place on your hard disk, like drive C:.
Grab the Live-CD from ftp://ftp.lug.udel.edu/pub/siduction...1212092122.iso This is a Debian system.

Boot your PC from the CD. May be you have to access the BIOS settings to change the boot order to start the CD. Inside the running Debian-Live-CD start a terminal application, gain root rights
Code:
su
Mount the hard disk
Code:
mount /dev/sda2 /media/diskpart2
May be you have to change the number in the code to reflect your PC's setup. Change into the directory (folder), where you have the files ready
Code:
cd /media/diskpart2
That is if you have the files on drive C:. Now install the flasher-utility
Code:
dpkg -i maemo-flasher-3.5*
Shut down your phone. Start the flasher in the terminal
Code:
flasher3.5 -F RX-51_2009SE_3.2010.02-8_PR_COMBINED_MR0_ARM.bin --flash-only=kernel -f -R
Connect the phone now to your PC's USB. This will flash the kernel only from the fiasco image to boot up the phone. If it boots everything is fine.

If not, you have to use the command without the flash-only=kernel option to reset the phone.

Hope it helps!

Please feel free to ask, if necessary

cheers Micha
Am grateful for your assistance Micha, am really grateful.

Question; I managed to get a system running on Ubuntu, do I still need the Live-CD? Or do I go into the next step direct.

michaaa62 2013-02-10 16:36
Re: unable to uninstall *#Starhsah Enabler
 
No need for the Live-CD in this case!
But you have to change the commands slightly for Ubuntu. You need to add 'sudo' to the commands that need root privileges. For sudo to succeed you need the password of the user:
Code:
sudo mount /dev/sda2 /media/diskpart2
cd /media/diskpart2
sudo dpkg -i maemo-flasher-3.5*
sudo flasher3.5 -F RX-51_2009SE_3.2010.02-8_PR_COMBINED_MR0_ARM.bin --flash-only=kernel -f -R

Freddie 2013-02-11 18:29
Re: unable to uninstall *#Starhsah Enabler
 
Quote:
Originally Posted by michaaa62 (Post 1322278)
No need for the Live-CD in this case!
But you have to change the commands slightly for Ubuntu. You need to add 'sudo' to the commands that need root privileges. For sudo to succeed you need the password of the user:
Code:
sudo mount /dev/sda2 /media/diskpart2
cd /media/diskpart2
sudo dpkg -i maemo-flasher-3.5*
sudo flasher3.5 -F RX-51_2009SE_3.2010.02-8_PR_COMBINED_MR0_ARM.bin --flash-only=kernel -f -R
Hi Micha,

I keep getting the error, "mount: mount point /media/diskpart2 does not exist" after being prompted for password and inputting the same....kindly assist.

Fred.

michaaa62 2013-02-12 08:31
Re: unable to uninstall *#Starhsah Enabler
 
Sorry my fault, did not adapt all the code to Ubuntu, sorry! I am not that familiar with mount point naming in Ubuntu, but almost everything 'custom-made' works.

To make it clear: The partition number might differ on your PC, this is /dev/sdaX, where X is the digital to correspond to windows drive where you have the files.

Add this command before the above commands
Code:
sudo mkdir /media/diskpart2
The name of the mount point is up to the user, it may be anything, but mkdir will create it.

Freddie 2013-02-14 11:20
Re: unable to uninstall *#Starhsah Enabler
 
2 Attachment(s)
Hi Michaa, all this time av been tryin to flash the kernel image but I seem to get issues anytime anywhere. I was able to mount my phone onto ubuntu bt now my issue is a dpkg error processing instalation, maemo-flasher-3.5. See, the third line of the code you sent me Michaa, any advice?

See below, the error message am getting....
Please assist....



Guys, am so so so so glad I made it. I was not able to flash the kernel alone, said was successful but on restarting, experienced the same issues. So I flashed the firmware and here we go, check out the image just in-case someone else has this same issue; plus please note that I didn't lose my internal memory data...

Thanks to you Michaa, you inspired me to learn Terminal codes..can't thank you enough.

Incase the image ain't visible;
Image '2nd', size 14848 bytes
Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
Version 1.4.14.9+0m5
Suitable USB device not found, waiting.
USB device found found at bus 002, device address 017.
Found device RX-51, hardware revision 2204
NOLO version 1.4.14
Version of 'sw-release': RX-51_2009SE_20.2010.36-2_PR_MR0
Sending xloader image (14 kB)...
100% (14 of 14 kB, avg. 483 kB/s)
Sending secondary image (106 kB)...
100% (106 of 106 kB, avg. 962 kB/s)
Flashing bootloader... done.
Sending cmt-2nd image (79 kB)...
100% (79 of 79 kB, avg. 742 kB/s)
Sending cmt-algo image (507 kB)...
100% (507 of 507 kB, avg. 981 kB/s)
Sending cmt-mcusw image (5826 kB)...
100% (5826 of 5826 kB, avg. 984 kB/s)
Flashing cmt-mcusw... done.
Sending kernel image (1705 kB)...
100% (1705 of 1705 kB, avg. 983 kB/s)
Flashing kernel... done.
Sending and flashing rootfs image (185728 kB)...
100% (185728 of 185728 kB, avg. 987 kB/s)
Finishing flashing... done
CMT flashed successfully


All times are GMT. The time now is 18:17.
Page 3 of 3 12 3
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8