Develop Bugs

[Q] Wont flash :(

My phone is currently stuck on the boot screen after i mistakenly removed Apex launcher (when it was messed up on monday) whilst forgetting that i had removed the stock launcher
Annoying as i may be, all my stuffs on memory card or on my google account.... so no real loss. I know i can sort it by flashing, but i just couldn't get it to work. Downloaded the latest generic ftf file & (what appears to be) the latest version of flashtool (0.7.0.0 iirc). But whenever i try flashing, it very quickly tells me that its failed.
I think i know the answer to this, but if possible i would really like to retreive the txts that are on the phone. Is there something i can do before flashing..... or do i have to consider them lost
Any help on either of those questions would be very greatfully received!

Not sure where you got your flashtool from, but obviously not the page in the dev section. Try flashing with the latest flashtool and report back. I take it your boot loader isn't unlocked?

You don't need to flash, if you can get into recovery. There mount usb storage, copy Apex.apk onto it, unmount storage, mount sdcard, mount system, and then move Apex.apk into /system/app.
in cmd/terminal:
Code:
adb shell
su
cd /
cp /sdcard/Apex.apk /system/app
that should do the trick. If you cant access recovery, flash with generic files, look for the flashtool in this forum, there should be some links, and tutorials too.

issak42 said:
You don't need to flash, if you can get into recovery. There mount usb storage, copy Apex.apk onto it, unmount storage, mount sdcard, mount system, and then move Apex.apk into /system/app.
in cmd/terminal:
Code:
adb shell
su
cd /
cp /sdcard/Apex.apk /system/app
that should do the trick. If you cant access recovery, flash with generic files, look for the flashtool in this forum, there should be some links, and tutorials too.
Click to expand...
Click to collapse
If that works it would be great. I have tried to get into recovery mode but with no luck..... however that could be the keypress combo i was using. Have found talk of lots of different ways, not necessarily saying what handset its for.
What is the confirmed keypress combo / method for the arc s?
which flashtool works with the latest generic firmware, as i thought i got this but it wouldn't work

mattshaw4 said:
My phone is currently stuck on the boot screen after i mistakenly removed Apex launcher (when it was messed up on monday) whilst forgetting that i had removed the stock launcher
Annoying as i may be, all my stuffs on memory card or on my google account.... so no real loss. I know i can sort it by flashing, but i just couldn't get it to work. Downloaded the latest generic ftf file & (what appears to be) the latest version of flashtool (0.7.0.0 iirc). But whenever i try flashing, it very quickly tells me that its failed.
I think i know the answer to this, but if possible i would really like to retreive the txts that are on the phone. Is there something i can do before flashing..... or do i have to consider them lost
Any help on either of those questions would be very greatfully received!
Click to expand...
Click to collapse
OK, this worked for me when I did something very similar...
start up the phone, and plug it into the computer.
After a while the light on the phone comes on, and the boot animation keeps looping...
The thing is that adb works now so you can install your launcher through adb!
to do this you type in this command on the windows command prompt
Code:
adb install Trebuchet.apk
some notes: -
you may need to type in the path to your copy of adb.exe if you get a "Command not recognised" error.
I used the launcher from CM10 - Trebuchet in the code snippet. You can extract your launcher's apk file from the rom (look in "system/apk"). Then use your launcher's apk name when you type out the command
Good Luck

An update guys.... spent a couple of hours on this only to find a very simple fix......
Using Flashtool in flashmode (?green light)..... noticed the icon for "install apk".... so found a free launcher apk, hit the button & my phone sprung back into life, text messages & all!!!!

Bricked or not? and how to fix if not? A100

So I've tried searching on here, I've tried googling to no success...So time for my first post on this site I guess.
I have an Acer Iconia Tab A100 running stock ICS (rooted) which now stops during its boot sequence.
I've read that when a device is bricked it stops at the Acer logo on boot, mine goes past this but stops before the Android logo appears.
Stuff I did before this happened:
- Friend rooted my device for me using a guide from these forums.
- I tried seeing what I can do with Superuser permissions and got used to the new features.
- Wanted an app that wasn't compatible with my device so I tried using a Device Spoofer to make my device appear as an HTC Thunderbolt.
- Realized it didn't work still so I used the device spoofer to restore back to my default device.
- Device rebooted and I am now stuck between the Acer logo and the Android logo on boot.
Am I bricked and screwed out of a device?
Is there a way to recover my device/restore to factory?
Any help is appreciated. You all most likely know more that I do.
EDIT: The guide that was followed to root: http://forum.xda-developers.com/showthread.php?t=1531646&highlight=root

phracture said:
So I've tried searching on here, I've tried googling to no success...So time for my first post on this site I guess.
I have an Acer Iconia Tab A100 running stock ICS (rooted) which now stops during its boot sequence.
I've read that when a device is bricked it stops at the Acer logo on boot, mine goes past this but stops before the Android logo appears.
Stuff I did before this happened:
- Friend rooted my device for me using a guide from these forums.
- I tried seeing what I can do with Superuser permissions and got used to the new features.
- Wanted an app that wasn't compatible with my device so I tried using a Device Spoofer to make my device appear as an HTC Thunderbolt.
- Realized it didn't work still so I used the device spoofer to restore back to my default device.
- Device rebooted and I am now stuck between the Acer logo and the Android logo on boot.
Am I bricked and screwed out of a device?
Is there a way to recover my device/restore to factory?
Any help is appreciated. You all most likely know more that I do.
Click to expand...
Click to collapse
Is cwm or twrp recovery installed?
Sent via G2x on temasek b135.2 w/ Trinity TD1.58 kernel (testing)

justjackyl said:
Is cwm or twrp recovery installed?
Sent via G2x on temasek b135.2 w/ Trinity TD1.58 kernel (testing)
Click to expand...
Click to collapse
I don't believe either was installed. Is there anyway to fix this problem without those?

phracture said:
I don't believe either was installed. Is there anyway to fix this problem without those?
Click to expand...
Click to collapse
Well for starters what happened was that tool wrecked build.prop which sits in /system. Not a bug issue except it won't be fixed by resetting, you need to replace/repair build.prop or flash a whole new system to it. Did you enable debugging before doing this? If so adb might be used to repair the damage. If not you'll need to flash an official acer ICS ROM by placing it on the root of external SD named update.zip then power on holding the volume key closest to the lock switch.
Tapatalked from my Nexus 7 - Kuroikaze AOSP

pio_masaki said:
Well for starters what happened was that tool wrecked build.prop which sits in /system. Not a bug issue except it won't be fixed by resetting, you need to replace/repair build.prop or flash a whole new system to it. Did you enable debugging before doing this? If so adb might be used to repair the damage. If not you'll need to flash an official acer ICS ROM by placing it on the root of external SD named update.zip then power on holding the volume key closest to the lock switch.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
Click to expand...
Click to collapse
Ahhh okay I think that makes sense to me, and yes I believe I had debugging turned on so I should be able to fix this I guess fairly simply.
Thanks so much will post to say if I've solved or ran into trouble once i get home.

pio_masaki said:
Well for starters what happened was that tool wrecked build.prop which sits in /system. Not a bug issue except it won't be fixed by resetting, you need to replace/repair build.prop or flash a whole new system to it. Did you enable debugging before doing this? If so adb might be used to repair the damage. If not you'll need to flash an official acer ICS ROM by placing it on the root of external SD named update.zip then power on holding the volume key closest to the lock switch.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
Click to expand...
Click to collapse
Could someone be nice enough as to tell me how to access my device to put the build.prop on it?
I have installed adb and downloaded the files for 4.0.3 using android ADK. I see the build.prop file that I need. However when i try to run adb.exe to see how the program works, I just get a window which scrolls through a large amount of text before closing.
EDIT: I am running windows 7 x64. Would this be easier if I tried using adb on my laptop which runs Ubuntu?

phracture said:
Could someone be nice enough as to tell me how to access my device to put the build.prop on it?
I have installed adb and downloaded the files for 4.0.3 using android ADK. I see the build.prop file that I need. However when i try to run adb.exe to see how the program works, I just get a window which scrolls through a large amount of text before closing.
EDIT: I am running windows 7 x64. Would this be easier if I tried using adb on my laptop which runs Ubuntu?
Click to expand...
Click to collapse
First you need to have the acer drivers installed. Second the tab will need to be booted to the recovery to be seen.
Place the build.prop you need to push to the device in the platform tools folder (the one with adb.exe). Make sure the name is properly build.prop
**There are modded ones here in the dev section here that will work, speed up your tab and/or rename it to an A500 to get more apps.
Open a command propt in the platform-tools folder (shift-right click)
type
adb devices
There should be a device listed
type
adb push build.prop /system
Your done, type reboot
It should reboot with the new build.prop

phracture said:
Could someone be nice enough as to tell me how to access my device to put the build.prop on it?
I have installed adb and downloaded the files for 4.0.3 using android ADK. I see the build.prop file that I need. However when i try to run adb.exe to see how the program works, I just get a window which scrolls through a large amount of text before closing.
EDIT: I am running windows 7 x64. Would this be easier if I tried using adb on my laptop which runs Ubuntu?
Click to expand...
Click to collapse
Open a terminal then cd to where you have adb.exe then run it that way, otherwise it just scrolls help and closes like you saw.
Power on and once it gets stuck booting try
adb devices
And see if it shows up, if it does do
adb pull /system/build.prop
This pulls it to where adb.exe is, from there you can check it for errors or even upload it and we can check it out.
Tapatalked from my Galaxy Nexus - CN(A)

Excuse me for butting in but wouldnt it be easer for him to just do the SD card. A lot less confusing at least fo me..

pio_masaki said:
Open a terminal then cd to where you have adb.exe then run it that way, otherwise it just scrolls help and closes like you saw.
Power on and once it gets stuck booting try
adb devices
And see if it shows up, if it does do
adb pull /system/build.prop
This pulls it to where adb.exe is, from there you can check it for errors or even upload it and we can check it out.
Tapatalked from my Galaxy Nexus - CN(A)
Click to expand...
Click to collapse
I'd be fine with uploading it for you guys to check out, but first I need adb to find my device.
I made sure I have the Acer drivers installed, but when I plug it in and run "adb devices" I get no devices listed.
I tried both at the screen where it stops loading as you said and at the recovery screen as Romman0 said.
Romman0 said:
First you need to have the acer drivers installed. Second the tab will need to be booted to the recovery to be seen.
Place the build.prop you need to push to the device in the platform tools folder (the one with adb.exe). Make sure the name is properly build.prop
**There are modded ones here in the dev section here that will work, speed up your tab and/or rename it to an A500 to get more apps.
Open a command propt in the platform-tools folder (shift-right click)
type
adb devices
There should be a device listed
type
adb push build.prop /system
Your done, type reboot
It should reboot with the new build.prop
Click to expand...
Click to collapse
I tried that and no devices are listed as I said above.
Also, the shift+right click blew my mind. That could've been and will be very useful to save me time.

phracture said:
I'd be fine with uploading it for you guys to check out, but first I need adb to find my device.
I made sure I have the Acer drivers installed, but when I plug it in and run "adb devices" I get no devices listed.
I tried both at the screen where it stops loading as you said and at the recovery screen as Romman0 said.
I tried that and no devices are listed as I said above.
Also, the shift+right click blew my mind. That could've been and will be very useful to save me time.
Click to expand...
Click to collapse
So I still haven't gotten my device to be recognized. Should I try to connect using Ubuntu or Mac OS?
As I was told before, there is something i can do where i put the android API in an update.zip and place it on an external SD. By external SD does this mean micro SD card? Could this solve my problem potentially?

phracture said:
So I still haven't gotten my device to be recognized. Should I try to connect using Ubuntu or Mac OS?
As I was told before, there is something i can do where i put the android API in an update.zip and place it on an external SD. By external SD does this mean micro SD card? Could this solve my problem potentially?
Click to expand...
Click to collapse
Yes the microsd. And yes, if you flash the ICS stock ROM http://forum.xda-developers.com/showthread.php?t=1611696
It will fix it to. Rename to update.zip then place it on your microsd card, power off and boot recovery by pressing both the power and volume rocker closest to the corner at the same time until it starts updating.

Romman0 said:
Yes the microsd. And yes, if you flash the ICS stock ROM http://forum.xda-developers.com/showthread.php?t=1611696
It will fix it to. Rename to update.zip then place it on your microsd card, power off and boot recovery by pressing both the power and volume rocker closest to the corner at the same time until it starts updating.
Click to expand...
Click to collapse
Thanks for confirming and giving me that link. Problem is solved. Thanks everyone for helping a noob out.

[AOKP] IceColdJelly421 - 1.6 - JellyBean 4.2.1_r1 : Internal SDCARD not showing up??

Hey Guys,
Being a new person on this forum, I was not able to post on the original thread, so posting here.
I have been on IceColdJelly421 - 1.6 - JellyBean 4.2.1_r1 for last 2 weeks and have found it to be an excellent ROM. However I noticed something very weird today.
My HTC ONE X's (international tegra) SDCARD is gone! when I connect to mac, I can only see my 2.11 GB internal phone storage, same from Settings -> Storage. I tried formatting the SDCARD (~27 GB) from TWN and mac (as FAT) but still it doesnt show up anywhere.
I also tried formatting the SDCARD from settings -> storage page, but that just keeps loading, nothing happens.
Any idea whats wrong here? I tried searching on the forum, but either didnt do a good job on it / didnt get anything
Please help / provide some input.
Update:
1) When I mount USB storage from TWN, i get a message on MAC that disk is not initialized. I format it as FAT from disk utility it works fine but then on reboot, I dont see in Android
2) Again from TWN when I try to format the SDCARD by using Wipe -> External Storage. The log says couldnt load SDCARD or something.
3) when "adb shell", I see my phone internal storage under /sdcard folder. Also I dont see any "0" folder inside my sdcard folder. As I understood from the IceColdJelly421 thread, 4.2.1 onwards, the SDCARD is mounted under 0 folder. But I dont see any.
-Rockingturtle.

Bump ! Any one ?

Have you flashed boot.img between different ROM versions? Because the boot.img in a particular version was bad and it was reverted in the following versions. Can't remember which though.
Try flashing boot from 1.6 for example, or 1.3.1.

I have the following files which I used.
$ md5 boot.img
MD5 (boot.img) = 77b5e63109c54aacca5e783d50cfece4
$ md5 aokp_ICJ421-V1.6.zip
MD5 (aokp_ICJ421-V1.6.zip) = a342a97d8cdbbe3f8f465aa9de809fd5
blackice.omca.co.uk/download/icecoldsandwich/IceColdJelly421 is not opening for me currently, will download again and check.
-Rock

rockingturtle said:
I have the following files which I used.
$ md5 boot.img
MD5 (boot.img) = 77b5e63109c54aacca5e783d50cfece4
$ md5 aokp_ICJ421-V1.6.zip
MD5 (aokp_ICJ421-V1.6.zip) = a342a97d8cdbbe3f8f465aa9de809fd5
blackice.omca.co.uk/download/icecoldsandwich/IceColdJelly421 is not opening for me currently, will download again and check.
-Rock
Click to expand...
Click to collapse
Flashed to another ROM and the problem is gone. Will download the ICJ again / wait for next release and try again.
-Rock

rockingturtle said:
Flashed to another ROM and the problem is gone. Will download the ICJ again / wait for next release and try again.
-Rock
Click to expand...
Click to collapse
Just re install the original recovery and do a factory reset in the bootloader page will erase every thing , then the sd will back again , then flash any recovery you wont.

samooorje said:
Just re install the original recovery and do a factory reset in the bootloader page will erase every thing , then the sd will back again , then flash any recovery you wont.
Click to expand...
Click to collapse
I tried that, but didnt work, the factory reset in TWR failed saying cannot mount /sdcard
When I flashed a different boot.img, TWR was able to mount and format the sdcard. Now I did a re-install of a different ROM (ARHD 18.1) and everything is working fine. Will try with ICJ again shortly. Seems like a lot of folks are reporting issues with 1.7.1.
-Rock

Just installed ICJ 1.7.2 by flashing the ROM from SDCARD, worked like a charm this time, both SDCARD and internal phone memory coming. Facing the following issues with the ROM currently.
1) The battery is draining faster, will let it settle for 1-2 days and then re-check. Will also adjust the brightness level, that helped a lot with 1.6
2) The rotation of home screen is still not working, I dont use that anyways , so no problemo !
3) Noted some disturbance / noise when doing a call in speaker mode. In earphone mode, it was crystal clear.
Thanks "Lord" and all the other team members for this !!

mputeop New
Just installed the 2.0 version from Lord...so far so good Thanks Lord !!
-Rock

Also trouble...
Hi, I'm also having some trouble trying to get to the 2.0.. - looking forward to it, Lord
(btw I have searched, but it's too much info to comprehend)
**1**
AFAIK I need to update my hboot (currently 0.95) and I installed the original backup (clean One X from HTC) and was trying the OTA update, but I get an error where recovery can't find the path ( "[E:...]")
Does it need original recovery?
**2**
Also when I'm trying to use the mv * ../ commands I get this:
mv can't rename '.': Device or resource busy
I'm not that experienced with the cmd/terminal stuff, so I can't really debug on my own yet :/
What does this error mean and how to fix it?
Thanks!

bjornops said:
Hi, I'm also having some trouble trying to get to the 2.0.. - looking forward to it, Lord
(btw I have searched, but it's too much info to comprehend)
**1**
AFAIK I need to update my hboot (currently 0.95) and I installed the original backup (clean One X from HTC) and was trying the OTA update, but I get an error where recovery can't find the path ( "[E:...]")
Does it need original recovery?
**2**
Also when I'm trying to use the mv * ../ commands I get this:
mv can't rename '.': Device or resource busy
I'm not that experienced with the cmd/terminal stuff, so I can't really debug on my own yet :/
What does this error mean and how to fix it?
Thanks!
Click to expand...
Click to collapse
#1 Yes, I have also faced this problem, the best is to restore HTC's stock ROM and recovery (this is important, as custom recoveries dont work) and then update. You can find the orignal recovery in the threads. People have posted them
#2 Did you follow the exact steps of booting into fastboot, adb shell and execute the commands from there? You might want to try a different boot.img for this. I used ARHD boot.img to do the changes and then got back to ICJ. I had to change my boot.img, because the ICJ was not showing my SDCARD at all.
Let me know if this helped.
-Rock

BTW on 2.1 ICJ now and loving it. I am facing some wifi, GPS issues. But that might be just because of my router (for wifi, as I had trouble connecting to my wifi even from mac, restart of router did the trick), for GPS / Signal, I noted low signal from carrier, so will wait for few more days.
Also noted that my soft keys are often skipping. The home button needs to be clicked twice at times. But in general and overall a very good ROM.
Thanks L0rd !!!
-Rock

Facing the following issues with 2.1:
1) The GPS fixing is taking a lot of time. I remember at office, I usually get a fix very quickly, but taking time now.
2) Post playing games (subway surfer), the device gets heated a lot specially around the camera area. This is draining the battery a bit.
3) Still loosing battery a bit faster than it did earlier.
4) The home button / associated vibrations dont register at times and I need to try them again. Also noted in subway surfer that game play is a bit jerky and some of my swipes are not registered. This might be due to any off: ROM, Kernel, Game, a poor screen guard.
Trying to get some data (logs etc) to substantiate the above observations. Might shift to ARHD for sometime to compare the data and provide better inputs.
-Rock

Installed ARHD, details captured here:
http://forum.xda-developers.com/showpost.php?p=38487569&postcount=39640

Yeah, I troubled the guys in their main thread after the HTC RUU exe surpriced me by erasing my SDcard, and mattoffshore gave me this link to a simple flashing tool: http://www.mediafire.com/?oik6tjvo28r9d
it worked out nicely, hboot 1.39 on .401. HTC__Y13 (tags for other unfortunate searchers)
ICJ 2.1 :good: until the next release any day now haven't had any big issues except a few camera FC and random hot reboots
-bjornops

[Q] FP1 - 1.6 unified storage upgrade: Problems

hi!
i installed the regulat 1.6 update to my FP1 and everything was just fine.
then I tried to install the "unified 1.6 update" which worked but the problems begun:
things I noticed:
1. backup ist not really a backup for the apps but just a way to reinstall the apps I had installed without any settings. not a fun way to find that out when reopening your apps.
2. the update to the 1.6 unifyed also messed with my SD card and deleted files and put new ones there. not something I was expecting. luckily I had a backup of the SD card.
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
As all my settings are gone anyway I am open to reinstall the phone from scratch.

fivel_ said:
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
Click to expand...
Click to collapse
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
I am not a mac user but I think you need to install some additional software.
https://www.android.com/filetransfer/

_keesj said:
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
Click to expand...
Click to collapse
thanks a lot, that is what I feared.

hi, i'm also have an upgrade problem: mine is that i can't upgrade at all.
i've repartitioned earlier with the app mentioned in the wiki (wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone).
i've also done the steps _keesj descripes in thread "unified storage setup on re-partitioned FP1" ("Steps for "fiixing" your upgrade").
i'm having Cherry 1.6, and two 7 GB partitions.
does anyone has a solution?

see other (missplaced) post
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642

Donat.Callens said:
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642
Click to expand...
Click to collapse
thanks, i've read it again and tried _keesj's solution again, unfortunately it didn't solve my situation.
i'm a layman in this area, so probably i shoudn't haved 'played' with partitions at all (but with the app it was easy).
my previous post wasn't quite complete... i have had an unified partition before...
because of an app that didn't work, i used the repartition app again to see if that could solve the problem.
it did, but later i wondered if a wrong install in the unified sistuation was the problem... so i thought 'let's try the unified partition again'...
i thought i could simply re-use the Fairphone Updater...
so maybe i'm now having a unified partition divided in 2?
and lost the ability to ever upgrade to newer versions of the Fairphone OS?
i hope someone can help me...

jjjanssen said:
i could simply re-use the Fairphone Updater...
Click to expand...
Click to collapse
Make sure you allow it to reinstall the default recovery.

Donat.Callens said:
Make sure you allow it to reinstall the default recovery.
Click to expand...
Click to collapse
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…

Hi,
jjjanssen said:
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…
Click to expand...
Click to collapse
Non unified images have a different signature. The moment you use the partition upgrader it will change the accepted signature and will no longer allow older images. If all is as I expected your running image is still the parition upgrader image and it contains the tools to perform the last step of the re-partitioning (e.g. calling the script and performing a recovery with format).
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.

_keesj said:
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.
Click to expand...
Click to collapse
I couldn't find any (log) files in /cache/recovery, but...
flashing the EBR1 from the FUSE binaries (FP1U) to my FP1 solved it! :victory:
thanks to _keesj, Rick (from Fairphone) and Christian (Fairphone forum)!
here is Rick's tutorial (with a few notes of my own):
You can only fix this by flashing your phone:
For GURU's only! (flashing with ADB). The alternative is to use the windows flasher tool.
1) Download the original image binaries from Fairphone's site (as a new user I, jjjanssen, can't post links yet).
(Download FP1U's zip: Fairphone_Cherry_1.6_FUSE_Image_2014-07-31.zip)
2) unzip the file
(I chose to unzip to location D:/FP1U.
after that i moved all content from the directory which contained EBR1, to D:/FP1U.)
3) enable usb debugging (on your phone: Settings, Developer options, turn USB debugging on)
4) push EBR1 on the phone: (Open (if you're using Windows) the Command Prompt)
adb push FP1U/EBR1 /mnt/sdcard/
(For instructions on how to use ADB search this site)
5) become root:
adb shell
(after that I also became super user (command su), but maybe that's not necessary; Rick didn't mention it. )
6) override the partition inforation:
dd if=/mnt/sdcard/EBR1 of=/dev/ebr1
7) reboot into recovery:
reboot recovery
8) choose to wipe data and cache
(after that, choose reboot)
Click to expand...
Click to collapse

UBports - Ubuntu Touch - Titan - Installation 2021

This is an installation mode that I use - This method I took from the Moto g2 Titan telegram group: https://t.me/TitanRoms
​I did it from a debian-based distribution
(1) Download these two files:
click-ubuntu-policy_0.1_all.deb
drive.google.com
https://drive.google.com/file/d/1LHqKyr_pOFiRz9IhXHiyQkru0y7rrTSl/view?usp=sharing
(2) open the terminal and go to where I download the files, and install them with the following commands.
sudo apt install debsig-verify kpartx
sudo dpkg -i click-ubuntu-policy_0.1_all.deb
sudo dpkg -i ubuntu-device-flash_0.34-0ubuntu1_amd64.deb
(3) Put your moto g2 in bootloader mode (power button + volume down) and connect it to the PC
(4)Put this command in the terminal and press enter, wait for the whole process to finish.
ubuntu-device-flash --verbose --server=https://system-image.ubports.com touch --device=titan --channel=16.04/community/walid/devel --bootstrap
If everything goes well, in a few minutes you will be using UBtouch on your moto g2 titan.
Many thanks Walid for this Port! and https://t.me/TitanRoms for sharing this installation method​

Zarosky said:
This is an installation mode that I use - This method I took from the Moto g2 Titan telegram group: https://t.me/TitanRoms​​I did it from a debian-based distribution
(1) Download these two files:
click-ubuntu-policy_0.1_all.deb
drive.google.com
https://drive.google.com/file/d/1LHqKyr_pOFiRz9IhXHiyQkru0y7rrTSl/view?usp=sharing
(2) open the terminal and go to where I download the files, and install them with the following commands.
sudo apt install debsig-verify kpartx
sudo dpkg -i click-ubuntu-policy_0.1_all.deb
sudo dpkg -i ubuntu-device-flash_0.34-0ubuntu1_amd64.deb
(3) Put your moto g2 in bootloader mode (power button + volume down) and connect it to the PC
(4)Put this command in the terminal and press enter, wait for the whole process to finish.
ubuntu-device-flash --verbose --server=https://system-image.ubports.com touch --device=titan --channel=16.04/community/walid/devel --bootstrap
If everything goes well, in a few minutes you will be using UBtouch on your moto g2 titan.
Many thanks Walid for this Port! and https://t.me/TitanRoms for sharing this installation method​
Click to expand...
Click to collapse
Hi, I'm new here and if i am honest joined just to ask questions here. I have tried what you said (many thanks as I wasn't sure what to do after finding the link for the rootfs tarball was dead), it is the same command Walidham stated for installing 16.04 but that didn't come with the commands for installing the flashing tools for this method and I probably wouldn't have noticed that command anyway in the original post as I was mostly paying attention to the original instructions for 15.10. Anyway, I tried this method and it all seemed to be going fine but every time when it gets to a certain point it says on the phone that there is insufficient space for pushing one of the files. I am actually using a Moto G2 4G LTE Thea, not Titan so it may not work but I thought I'd try it anyway and I don't know that this error is to do with that as it is to do with running out of internal storage, though I know sometimes error are diagnosed as totally different errors so that might be happening, I don't know.
Mine is 8GB but there is nothing smaller than that. I have changed the data partition format to ext4 by the way and I have tried running this with and without wiping system, data and cache partitions beforehand. The flashing process only gets anywhere when they are present and not wiped, otherwise it complains that it cannot boot recovery. I also noticed that the folder that seems to be referenced by the command has new files even from today (the 25th that is) and when I ran the command it was trying to flash version 779. When you did it it would have been an older version as the files relating to 779 seem to be brand new. I also assume these files are probably experimental. So I don't know if this is a non-working combination, or if I am doing something wrong, or if there is a way to change which version it is trying to flash, or if I can get a rootfs file that will work (I don't know anything about them or what exactly they do) and do it manually. I am also not a developer and am low on technical knowledge (as much as it hurts my ego to say it) if I am honest and I am using Linux mint 20.1 on the PC side of things, which of course is Ubuntu/Debian based so I imagine shouldn't be a problem here.
Thanks for the guide, thanks Walidham for the port, and if you know anything about my error or something else to try I'd appreciate it if you got back to me. Thanks!

Sanizol said:
Hi, I'm new here and if i am honest joined just to ask questions here. I have tried what you said (many thanks as I wasn't sure what to do after finding the link for the rootfs tarball was dead), it is the same command Walidham stated for installing 16.04 but that didn't come with the commands for installing the flashing tools for this method and I probably wouldn't have noticed that command anyway in the original post as I was mostly paying attention to the original instructions for 15.10. Anyway, I tried this method and it all seemed to be going fine but every time when it gets to a certain point it says on the phone that there is insufficient space for pushing one of the files. I am actually using a Moto G2 4G LTE Thea, not Titan so it may not work but I thought I'd try it anyway and I don't know that this error is to do with that as it is to do with running out of internal storage, though I know sometimes error are diagnosed as totally different errors so that might be happening, I don't know.
Mine is 8GB but there is nothing smaller than that. I have changed the data partition format to ext4 by the way and I have tried running this with and without wiping system, data and cache partitions beforehand. The flashing process only gets anywhere when they are present and not wiped, otherwise it complains that it cannot boot recovery. I also noticed that the folder that seems to be referenced by the command has new files even from today (the 25th that is) and when I ran the command it was trying to flash version 779. When you did it it would have been an older version as the files relating to 779 seem to be brand new. I also assume these files are probably experimental. So I don't know if this is a non-working combination, or if I am doing something wrong, or if there is a way to change which version it is trying to flash, or if I can get a rootfs file that will work (I don't know anything about them or what exactly they do) and do it manually. I am also not a developer and am low on technical knowledge (as much as it hurts my ego to say it) if I am honest and I am using Linux mint 20.1 on the PC side of things, which of course is Ubuntu/Debian based so I imagine shouldn't be a problem here.
Thanks for the guide, thanks Walidham for the port, and if you know anything about my error or something else to try I'd appreciate it if you got back to me. Thanks!
Click to expand...
Click to collapse
I just finished installing UBtouch, without any problem

Zarosky said:
This is an installation mode that I use - This method I took from the Moto g2 Titan telegram group: https://t.me/TitanRoms​​I did it from a debian-based distribution
(1) Download these two files:
click-ubuntu-policy_0.1_all.deb
drive.google.com
https://drive.google.com/file/d/1LHqKyr_pOFiRz9IhXHiyQkru0y7rrTSl/view?usp=sharing
(2) open the terminal and go to where I download the files, and install them with the following commands.
sudo apt install debsig-verify kpartx
sudo dpkg -i click-ubuntu-policy_0.1_all.deb
sudo dpkg -i ubuntu-device-flash_0.34-0ubuntu1_amd64.deb
(3) Put your moto g2 in bootloader mode (power button + volume down) and connect it to the PC
(4)Put this command in the terminal and press enter, wait for the whole process to finish.
ubuntu-device-flash --verbose --server=https://system-image.ubports.com touch --device=titan --channel=16.04/community/walid/devel --bootstrap
If everything goes well, in a few minutes you will be using UBtouch on your moto g2 titan.
Many thanks Walid for this Port! and https://t.me/TitanRoms for sharing this installation method​
Click to expand...
Click to collapse
Hi, I'm new on the forum and I don't understand a lot about apps and systems development, but I would like to learn. I followed the entire tutorial for installing Ubuntu touch on my moto G2, but the phone starts on the ubports recovery screen (I left images below).
what should i do after the phone boot on this screen?
I also apologize for my english.

Arthur Mateo said:
Hi, I'm new on the forum and I don't understand a lot about apps and systems development, but I would like to learn. I followed the entire tutorial for installing Ubuntu touch on my moto G2, but the phone starts on the ubports recovery screen (I left images below).
what should i do after the phone boot on this screen?
I also apologize for my english.
Click to expand...
Click to collapse
do not touch anything and look at the computer that continues to do its work, when the cell phone is finished it will only restart

Zarosky said:
do not touch anything and look at the computer that continues to do its work, when the cell phone is finished it will only restart
Click to expand...
Click to collapse
Thanks for the feedback. Really, I think I need to be more patient, but my anxiety doesn't help (lol).
I wait for the computer to finish its work, but the terminal returns the error "Failed to enter Recovery" and the cell phone keep in the ubports recovery screen.
If you have any tips, I appreciate it.

Sanizol said:
Hi, I'm new here and if i am honest joined just to ask questions here. I have tried what you said (many thanks as I wasn't sure what to do after finding the link for the rootfs tarball was dead), it is the same command Walidham stated for installing 16.04 but that didn't come with the commands for installing the flashing tools for this method and I probably wouldn't have noticed that command anyway in the original post as I was mostly paying attention to the original instructions for 15.10. Anyway, I tried this method and it all seemed to be going fine but every time when it gets to a certain point it says on the phone that there is insufficient space for pushing one of the files. I am actually using a Moto G2 4G LTE Thea, not Titan so it may not work but I thought I'd try it anyway and I don't know that this error is to do with that as it is to do with running out of internal storage, though I know sometimes error are diagnosed as totally different errors so that might be happening, I don't know.
Mine is 8GB but there is nothing smaller than that. I have changed the data partition format to ext4 by the way and I have tried running this with and without wiping system, data and cache partitions beforehand. The flashing process only gets anywhere when they are present and not wiped, otherwise it complains that it cannot boot recovery. I also noticed that the folder that seems to be referenced by the command has new files even from today (the 25th that is) and when I ran the command it was trying to flash version 779. When you did it it would have been an older version as the files relating to 779 seem to be brand new. I also assume these files are probably experimental. So I don't know if this is a non-working combination, or if I am doing something wrong, or if there is a way to change which version it is trying to flash, or if I can get a rootfs file that will work (I don't know anything about them or what exactly they do) and do it manually. I am also not a developer and am low on technical knowledge (as much as it hurts my ego to say it) if I am honest and I am using Linux mint 20.1 on the PC side of things, which of course is Ubuntu/Debian based so I imagine shouldn't be a problem here.
Thanks for the guide, thanks Walidham for the port, and if you know anything about my error or something else to try I'd appreciate it if you got back to me. Thanks!
Click to expand...
Click to collapse
About that insufficient space error you had, I think I also had a similar problem, but I'm not sure. It would be nice if you put images or prints of these errors, or give more details.
The insufficient space error that occurred to me actually wasn't in the cell phone as I thought, but in the Linux cache. I manually cleared the linux cache, and the error disappeared.

Arthur Mateo said:
About that insufficient space error you had, I think I also had a similar problem, but I'm not sure. It would be nice if you put images or prints of these errors, or give more details.
The insufficient space error that occurred to me actually wasn't in the cell phone as I thought, but in the Linux cache. I manually cleared the linux cache, and the error disappeared.
Click to expand...
Click to collapse
I wasn't sure at first whether it was meant to be left alone when it brought up the ubports recovery screen but eventuslly concluded it was. I'm busy this weekend but I will try and get some screenshots of my error when I can. I had settled back into using Android for the time being. I'll try what you said you did as well when I get the time. Thanks!

Update: It works!
I actually succeeded in installing the system on the 7th of this month, but I just said it now.
The system has several bugs. The bluetooth, the flashlight and the GPS doesn't work, for some reason the cell phone restarts when I connect to the wifi at home (which doesn't happen when I connect to my main cellphone's wifi in router mode), the notifications and settings bar seems to be cropped, and whenever I turn on the screen the option to turn off or restart the phone appears.
Anyway, I really liked the system, and I would like to contribute to it by solving or notifying the presence of these bugs in the software.
And thanks for the help.

Arthur Mateo said:
Thanks for the feedback. Really, I think I need to be more patient, but my anxiety doesn't help (lol).
I wait for the computer to finish its work, but the terminal returns the error "Failed to enter Recovery" and the cell phone keep in the ubports recovery screen.
If you have any tips, I appreciate it.
Click to expand...
Click to collapse

Arthur Mateo said:
Update: It works!
I actually succeeded in installing the system on the 7th of this month, but I just said it now.
The system has several bugs. The bluetooth, the flashlight and the GPS doesn't work, for some reason the cell phone restarts when I connect to the wifi at home (which doesn't happen when I connect to my main cellphone's wifi in router mode), the notifications and settings bar seems to be cropped, and whenever I turn on the screen the option to turn off or restart the phone appears.
Anyway, I really liked the system, and I would like to contribute to it by solving or notifying the presence of these bugs in the software.
And thanks for the help.
Click to expand...
Click to collapse
Congratulations !!! But I according the tutorials and it's failed . Can you help me ?
Here's what it shows in terminal, which I think is done
In the device it looks like this:
Yeah, I think it goes back to Ubuntu Recovery Interfaces

Sanizol said:
I wasn't sure at first whether it was meant to be left alone when it brought up the ubports recovery screen but eventuslly concluded it was. I'm busy this weekend but I will try and get some screenshots of my error when I can. I had settled back into using Android for the time being. I'll try what you said you did as well when I get the time. Thanks!
Click to expand...
Click to collapse
Hello bro, did you succeed ？

Zarosky said:
This is an installation mode that I use - This method I took from the Moto g2 Titan telegram group: https://t.me/TitanRoms​​I did it from a debian-based distribution
(1) Download these two files:
click-ubuntu-policy_0.1_all.deb
drive.google.com
https://drive.google.com/file/d/1LHqKyr_pOFiRz9IhXHiyQkru0y7rrTSl/view?usp=sharing
(2) open the terminal and go to where I download the files, and install them with the following commands.
sudo apt install debsig-verify kpartx
sudo dpkg -i click-ubuntu-policy_0.1_all.deb
sudo dpkg -i ubuntu-device-flash_0.34-0ubuntu1_amd64.deb
(3) Put your moto g2 in bootloader mode (power button + volume down) and connect it to the PC
(4)Put this command in the terminal and press enter, wait for the whole process to finish.
ubuntu-device-flash --verbose --server=https://system-image.ubports.com touch --device=titan --channel=16.04/community/walid/devel --bootstrap
If everything goes well, in a few minutes you will be using UBtouch on your moto g2 titan.
Many thanks Walid for this Port! and https://t.me/TitanRoms for sharing this installation method​
Click to expand...
Click to collapse
Have you ever encountered such a situation?

Arthur Mateo said:
About that insufficient space error you had, I think I also had a similar problem, but I'm not sure. It would be nice if you put images or prints of these errors, or give more details.
The insufficient space error that occurred to me actually wasn't in the cell phone as I thought, but in the Linux cache. I manually cleared the linux cache, and the error disappeared.
Click to expand...
Click to collapse
Upon finally trying again, this is the error that I was getting. This occurs whilst the phone has booted to the ubports recovery menu but obviously files are still being pushed.
Do you mean you cleared the linux cache on the PC?

xxdgagag said:
Congratulations !!! But I according the tutorials and it's failed . Can you help me ?
Here's what it shows in terminal, which I think is done
View attachment 5575483
In the device it looks like this:
View attachment 5575485
Yeah, I think it goes back to Ubuntu Recovery Interfaces
Click to expand...
Click to collapse
Hi, I did not succeed, no. Mine gets to the stage of displaying that screen but I'm not sure if yours gets further or not as far. Mine seems to make a big deal about copying this one file and ultimately always fails. Yours seems to say it boots to recovery and then stops, though I find it difficult to read what it says on your screenshot because it is low resolution.
Did you succeed in the end by any chance since you last posted?

is there a way to install Ubuntu touch manually? Like using twrp for example.

For anyone having problem installing this is How i did it.
First You Need to do the installation as ROOT.
I use Ubuntu.
Open a terminal and type
sudo su passwd root
Then Go ahead and set a password for root, after that type
su root
And put the password you Just created, Now you proceed with installing ubtouch by using SUDO, like this
sudo ubuntu-device-flash --verbose --server=https://system-image.ubports.com touch --device=titan --channel=16.04/community/walid/devel --bootstrap
Hopefully after this there Will be no problem. (PS: i dont speak english)

Hi all, many thanks to use and install UT on titan, i have bricked my device, i can't repair it. Thats why i stopped work on it, i'm trying to find one her in my country, but not success
Best regards

walidham said:
Hi all, many thanks to use and install UT on titan, i have bricked my device, i can't repair it. Thats why i stopped work on it, i'm trying to find one her in my country, but not success
Best regards
Click to expand...
Click to collapse
Ok. Good Luck! It seems like you were working on it until quite recently though by the repository. Thank you for all the time you have invested so far!
Magzk said:
For anyone having problem installing this is How i did it.
First You Need to do the installation as ROOT.
I use Ubuntu.
Open a terminal and type
sudo su passwd root
Then Go ahead and set a password for root, after that type
su root
And put the password you Just created, Now you proceed with installing ubtouch by using SUDO, like this
sudo ubuntu-device-flash --verbose --server=https://system-image.ubports.com touch --device=titan --channel=16.04/community/walid/devel --bootstrap
Hopefully after this there Will be no problem. (PS: i dont speak english)
Click to expand...
Click to collapse
Thank you. I will try this out soon. I perhaps mistakenly assumed I would get away with just using sudo.