SailfishOS on Motorola Droid 4 XT894 (alpha port) - Page 5 - maemo.org

Active Topics

Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 11 hrs, 7 mins ago
The N900 is now 15 years old! (6)
to Nokia N900 by Macros - 2 days, 7 hrs ago
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 2 days, 20 hrs ago
n770 youtube video (0)
to General by nmdv - 6 days, 19 hrs ago
more...

Page 5 of 15

Thread Tools

QWERTY_Slider	2017-03-11 , 09:15
Posts: 3 \| Thanked: 2 times \| Joined on Mar 2017	#41

Originally Posted by TheKit

Booting from stock slot doesn't work, as it was found in the topic before, I should have updated the first post to say this explicitly. For modern phone I would connect it to charger and leave for some time even if it doesn't display anything on screen, but not sure if this phone will charge without OS running, need someone who is more familiar to it to confirm. In the worst case you can use universal battery charger like this one.

Sorry that it went this way for you.

I don't blame you. I know that there are risks. I'm happy that there even is Sailfish OS port

. I'm just wondering what went wrong?

My Droid 4 didn't charge during night so I already bought another Droid 4. I should get before end of this month. Then I have two units to play with

. I'm sure I get the old one working again with fully charged battery.

Quote & Reply |

t-b	2017-03-11 , 10:20
Posts: 368 \| Thanked: 975 times \| Joined on Aug 2013	#42

I always make sure my battery level is fully charged before flashing. Would be even better if safestrap checks battery level before flashing or at least warns you.

@TheKit I don't care that much for stock OS so will replace that for SFOS or Lineage OS anyway. Any chance you will make it possible to flash stock with SFOS later?

@QWERTY_Slider pretty sure you are not the first with an issue like this and is not SFOS specific. You can also post your problem at the XDA forum if TheKit's suggestion doesn't work.
https://forum.xda-developers.com/droid-4

Quote & Reply |

The Following User Says Thank You to t-b For This Useful Post:
juiceme

	mp107	2017-03-11 , 10:38
	Posts: 166 \| Thanked: 454 times \| Joined on Apr 2015 @ Poland	#43

Originally Posted by t-b

@TheKit I don't care that much for stock OS so will replace that for SFOS or Lineage OS anyway. Any chance you will make it possible to flash stock with SFOS later?

But why to remove installed stock ROM on stock slot when you can use safe slot to install Sailfish OS without any affecting the performance (in opposite to virtual slots 1-4)?
On my Droid 4 I currently have stock ROM (in case of problems), CM11 (in the safe slot - as the main used OS at the moment) and Sailfish OS on virtual slot 1 (for testing it out).

EDIT:
As I can see currently the fixboot.sh file inside ramdisk.img in the base CM11 build does not allow to install Sailfish OS in the safe slot. It recognizes only stock and virtual slots 1-4.
@TheKit Is it possible to include such a possibility in the next build?
It may be done as described here: http://www.internauta37.altervista.o...install-webtop
In case of problems I have encountered when following that - the block size must be equal before and after modification. Otherwise the OS won't boot.

Last edited by mp107; 2017-03-11 at 11:19. Reason: Fixed typo, added info about safe slot

Quote & Reply |

The Following 2 Users Say Thank You to mp107 For This Useful Post:
juiceme, maegon9y00

t-b	2017-03-11 , 11:24
Posts: 368 \| Thanked: 975 times \| Joined on Aug 2013	#44

Originally Posted by mp107

But why to remove installed stock ROM on stock slot when you can use safe slot to install Sailfish OS without any affecting the performance (in opposite to virtual slots 1-4)

Well, basically only one reason. Not going to use it so keeping it is a waste of space.
In this case I agree it was my mistake to use stock slot initially though, I should have used a virtual slot because it is just an early port.

I blame lack of experience and lack of patience

Quote & Reply |

The Following User Says Thank You to t-b For This Useful Post:
juiceme

	mp107	2017-03-11 , 11:30
	Posts: 166 \| Thanked: 454 times \| Joined on Apr 2015 @ Poland	#45

Originally Posted by t-b

Well, basically only one reason. Not going to use it so keeping it is a waste of space.
In this case I agree it was my mistake to use stock slot initially though, I should have used a virtual slot because it is just an early port.

I agree - it wastes space. I haven't booted it at all since few months (~latest flashing).
But in case of problems might be useful.

Originally Posted by t-b

I blame lack of experience and lack of patience

To be honest, shortly after I've bought the Droid 4 bricked it once or twice.

Quote & Reply |

The Following User Says Thank You to mp107 For This Useful Post:
juiceme

	mp107	2017-03-11 , 18:34
	Posts: 166 \| Thanked: 454 times \| Joined on Apr 2015 @ Poland	#46

Originally Posted by QWERTY_Slider

Something went horribly wrong! First I wiped everything excluding internal storage. Then I flashed CM11 and SFOS. I tried to boot but got black screen for about 10min. Then I rebooted to safestrap and selected ROM slot 1 instead of stock ROM. Then I tried flashing again and got black screen for 10min.

After that I was not able to boot safestrap again. I was able to boot AP Fastboot so I tried to flash FXZ. After 5min FXZ failed because I was out power. My Droid 4 doesn't charge anymore. I guess that I need new Droid 4 with fresh battery so that I'm able to recover my old Droid 4.

I don't know what I did wrong

It looks like you need a special cable (buy it or make it) to be able to bring it back to life without battery replacement.
https://docs.google.com/document/d/1...FBR9VBa80/edit
https://forum.xda-developers.com/sho....php?t=1077414

I haven't tested it on my own, though.

Quote & Reply |

The Following 2 Users Say Thank You to mp107 For This Useful Post:
juiceme, t-b

QWERTY_Slider	2017-03-12 , 08:33
Posts: 3 \| Thanked: 2 times \| Joined on Mar 2017	#47

Originally Posted by TheKit

Booting from stock slot doesn't work, as it was found in the topic before, I should have updated the first post to say this explicitly. For modern phone I would connect it to charger and leave for some time even if it doesn't display anything on screen, but not sure if this phone will charge without OS running, need someone who is more familiar to it to confirm. In the worst case you can use universal battery charger like this one.

Sorry that it went this way for you.

I don't blame you. I know that there are risks so this is my own fault. I'm just happy that there is Sailfish OS port for Droid 4

.

My Droid 4 didn't charge during night so I bought another Droid 4. I should get it before end of this month. Then I have two units to play with

. I'm sure that I will get the old one working again. I'm just wondering what went wrong in the first place. Was it that I used stock ROM slot at first?

Originally Posted by mp107

It looks like you need a special cable (buy it or make it) to be able to bring it back to life without battery replacement.
https://docs.google.com/document/d/1...FBR9VBa80/edit
https://forum.xda-developers.com/sho....php?t=1077414

I haven't tested it on my own, though.

Yeah, I already searched over the net and found that thread. I don't mind to have two droid 4. I believe that it is the easiest method. Can't just wait to receive it

.

PS: For some reason moderators blocked my previous post yesterday

Quote & Reply |

The Following User Says Thank You to QWERTY_Slider For This Useful Post:
juiceme

	mp107	2017-03-15 , 18:38
	Posts: 166 \| Thanked: 454 times \| Joined on Apr 2015 @ Poland	#48

@TheKit
Where can/should I report bugs?

Quote & Reply |

The Following User Says Thank You to mp107 For This Useful Post:
juiceme

TheKit	2017-03-16 , 12:15
Posts: 194 \| Thanked: 1,167 times \| Joined on May 2016	#49

Originally Posted by mp107

@TheKit
Where can/should I report bugs?

Here in topic, or create issues at https://github.com/NotKit/droid-config-maserati/issues.

Originally Posted by mp107

EDIT:
As I can see currently the fixboot.sh file inside ramdisk.img in the base CM11 build does not allow to install Sailfish OS in the safe slot. It recognizes only stock and virtual slots 1-4.
@TheKit Is it possible to include such a possibility in the next build?
It may be done as described here: http://www.internauta37.altervista.o...install-webtop
In case of problems I have encountered when following that - the block size must be equal before and after modification. Otherwise the OS won't boot.

Missed your edit before. Safe slot should be supported in current (old) build. fixboot.sh isn't used by SailfishOS directly, but I integrated parts of it into SailfishOS ramdisk init script.

Last edited by TheKit; 2017-03-16 at 12:23.

Quote & Reply |

The Following 2 Users Say Thank You to TheKit For This Useful Post:
juiceme, mp107

matemana	2017-03-16 , 15:16
Posts: 163 \| Thanked: 279 times \| Joined on Feb 2017 @ Tbilisi, Georgia (caucasus)	#50

Originally Posted by TheKit

Booting from stock slot doesn't work, as it was found in the topic before, I should have updated the first post to say this explicitly. For modern phone I would connect it to charger and leave for some time even if it doesn't display anything on screen, but not sure if this phone will charge without OS running, need someone who is more familiar to it to confirm. In the worst case you can use universal battery charger like

Sorry that it went this way for you.

Thr phone will not charge without os on it. One way to fix this is to take out the battery find its + and - terminals and charge it with 5 v for about 10-15 minutes. This will revive the battery.