Database Users

[Q] Nexus S issues with firefox os

Hello all. I flashed Firefox OS onto my nexus s the other day. I am having several issues with it so far.
1. I am not able to connect to my network (t-mobile) using 3g or any data connection for that matter.
2. I am having trouble with screen resolution (know issue)
3. In the messaging app, I cannot go from a conversation back to the list of conversations.
4. The power/unlock button is not working. This is the biggest problem, as I can't use my phone unless I connect it to power, or I have an incoming call. This also prohibits me from rebooting into recovery mode. I tried taking out the battery and holding down the power and volume up button and was able to get into cwr, but the volume and power keys are not working, so I cannot navigate through the menus at all.
5. USB mass storage doesn't work.
6. Fastboot and adb will not recognize the device so I can't reflash anything, which may be related to the fact that the USB connection will not work.
At this point, I just want to put android back on my phone, but I can't figure out a way to do that because of the problems I listed above. Any help would be greatly appreciated, as my phone is basically unusable at this point.
Thanks, Blake

Most of the issues you report are already fixed in newer builds. I recognise a lot of them from running the 'v1-train' version of Gaia instead of the master version. I run a build described here on my Nexus S. Addressing your issues:
1. 3G and Data works on my build using the 'v1-train' version of Gecko but 'master' version of Gaia as described in my post. What model number is your phone? Mines the 9023.
2. Fixed in 'master' gaia. build with HIDPI set to 1 as described in my post.
3. Fixed in 'master' gaia.
4. I have not encountered this one in any build, sorry.
5. Works in my build
6. Check that you have Remote Debugging enabled in Settings/Device Information/More Information/Developer. This is required for ADB to work and is off by default on user builds.

G2 white lines -> can't connect for reflash

Hi, I have a G2 I need some help with. This is a partial repost from [HELP THREAD][Noob Friendly].
Just got a LG G2 for my wife (wedding anniversary). It arrived by post yesterday, yay I though, I got a couple of weeks to sort it out. Am trying to transition her from her old iPhone4S over to Android, and from checking things out, it looked like the OptimusG3 rom was the way to go, in terms of a nice interface.
I shoulda slowed down and been more meticulous with the process, but anyway… I have little knowledge of these things, but have managed to flash custom ROMS to a couple of devices before (HP Touchpad, Ainol Fire), noting that any problems I’d previously encountered were usually due to skipping or not following steps properly.
G2 model is D802. Kitkat 4.4.2 installed by default. From an ebay seller - back case, software and printed instructions all say D802. Opening the back case, internal bottom left corner says D801/D803.
Tried to follow guide here http://forum.xda-developers.com/show....php?t=2788077
Tried to root as per here http://forum.xda-developers.com/show....php?t=2448887
I think the root went through ok, although I had to try more than once (had other stuff happening in the background so not paying 100% attention).
Tried to flash TWRP as per here http://forum.xda-developers.com/show....php?t=2633941
Didn’t seem to be able to get this working.
Uncertain at this point if I was properly rooted, so redid it with https://towelroot.com/ - which seemed to be fine
Then tried to install TWRP with Autorec: http://www.droidviews.com/install-twr...
Which seemed to be successful, and I’m sure I picked the D802 TWRP recovery file, but THIS IS WHERE THE TROUBLE REALLY BEGAN - on reboot to recovery the trouble started – no logo, I’m just seeing a black screen with vertical lines that change for a bit, then go static.
My understanding now (thanks to Art Vanderlay) is this is probably the result of me having a JDI panel - so now I need to reflash a JDI kernal to fix the LGIT kernal that Autorec installed.
I can't read the screen at all - it is just black with white lines and change a bit before going static. I have tried to connect the phone up to the computer in DOWNLOAD mode using the VOLUME UP and ATTACH USB CABLE technique.
When I do this, the computer beeps to let me know a device is attached, and a ADB device turns up in device manager - but then nothing else thinks a device is attached, including SimpleTool, LGFlashTool2014, PDANET (which does say device connected to begin with, but then doesn't proceed any further), ADB (via commandline), MinimalADB, or Linux.
I have tried various permutations and combinations of:
1. different USB ports
2. different USB cables
3. different computers (x3)
4. different drivers (from various places, including LG website, SimpleTool, PDANET). (I even tried a Verizon G2 driver just for the hell of it)
5. two different LINUX distros
...and nothing seems to see the G2.
Any suggestions very very welcome, cos I'm out of ideas.

Did you manage to find a solution to that problem. I am having the same problem

Corrupted file in /systems/etc/ - Bootloop, no recovery & no download mode (D802)

Hello everybody
I recently tried to higher the maximum headphone volume of my rooted LG G2 D802 on stock KitKat. In order to a guide I changed some values in the mixer_paths.xml in /systems/etc/ via ES File Explorer. After that, I restarted the phone which results in a bootloop - the LG boot animation never ends. I already found out that there is a high probability that the mixer_paths.xml is currupted due to wrong codings/line breaks or something.
Sadly, I neither can start the stock recovery (no custom recovery installed) by holding Power+Volume down nor go into download mode by volume up+putting usb cable in. In both cases it just happens nothing. When I connect it via USB to a PC, Windows recognizes a energy load only device. I tried different USB drivers/ports and PCs. There is no entry in the device manager and no new drives in the disk management utility.
I found hundreds of posts and comments where people coplaining that they can't go into download/recovery mode, even with apart from that fully working LG G2s. Therefore I'm not even sure, if both problems - the bootloop and not working download/recovery modes - are connected.
Is there any chance to get my G2 working again? I love it and don't want to buy a new phone.
I would be very thankful for everyone who can help me!

Sailfish OS for the Samsung Galaxy Note - N7000

Code:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! Everything you do, !!
!! you do at your own peril and risk. !!
!! !!
!! I do not bear any responsibility !!
!! for your faulty devices. !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
First I would like to thank elros34, mal, adampigg and all the Sailfish OS porter guys who helped me to make this port.
Thank you very much, guys!
Requirements:
Before you start to download anything, please read all this carefully.
The first requirement is your device must be rooted and you should be able to install a custom recovery (preferably TWRP) onto it.
Installation instructions:
1. Download all files, LOS14.1 zip, Sailfish OS zip and kernel*.img to the external SD card on the phone
2. Reboot into TWRP (Hold buttons: Power on + Home + Volume up)
3. Do a factory reset
4. Still in recovery, flash the LOS14.1 image
5. Still in recovery, flash Sailfish Os image
5. Still in recovery, flash kernel*.img into /boot partition
8. Reboot
9. Enjoy the latest (4.0.1.48) Sailfish OS on your Galaxy Note (N7000)
You will need patience as the first boot will take for a while. Then you can go through the initial Sailfish OS set up.
This Sailfish OS Android HAL based on LOS 14.1.
Downloads:
Nightowl-lineage14.1-20180215-n7000.zip
PhilZ-cwm6-XXLT4-OXA-4.93.6.tar.md5
kernel40148-11-spen.img
Sailfish OS 4.0.1.48
Apps from Openrepos
Apart from the Jolla store, there are plenty of other, community-made apps in Openrepos. There is a user-friendly app to install/remove apps from this source called Storeman. It can be downloaded and install from this location: Storeman
Debug/login/troubleshooting:
In Ubuntu, connect USB cable. telnet 192.168.2.15 2323 or SSH [email protected]
Notes:
On Sailfish OS, as it is a Linux system, you cannot install/run any android apps.
How to make a backup/restore with TWRP:
You can boot into TWRP with the usual button combination (Hold buttons: Power on + Home + Volume up) and can make backup/restore.
Changelog:
24.03.2021
=========
Works:
Screen
Touch
IMEI number is detected
Sensors (Rotation, Acceleration, Gyroscope, Magnetometer, Proximity) - Except Light
GPS
The softkeys (each side of the home button) work as notification LEDs
Wifi
MTP
Calls incoming/outgoing
Messages incoming/outgoing
Mobile data
S-Pen works as a mouse. To make the cursor visible you need to do some manual work as Patchmanager doesn't yet work on sfos 4.0:
install mousetracker
amend '/var/lib/environment/compositor/droid-hal-device.conf' file, add the -plugin evdevmouse:abs:/dev/input/event9 to the end of LIPSTICK_OPTIONS. (That line should look like this:
Code:
LIPSTICK_OPTIONS=-plugin evdevtouch -plugin evdevkeyboard:keymap=/usr/share/qt5/keymaps/droid.qmap -plugin evdevmouse:abs:/dev/input/event9
as final step copy this compositor.qml into /usr/share/lipstick-jolla-home-qt5/
(Rename the existing one in there first!)
External SD card detected and mounted to /run/media/nemo/_sdcard_name_ (where _sdcard_name_ is the name of the sd card when it was formatted like 4B93-785B)
Home button and the Back soft button
Vibra
Pixel ratio and icons set to 1.25
Audio is routed to headphone if that presents
Camera front/rear (only for taking pictures)
Jolla store
findutils is installed by default (updatedb and locate commands work out of the box)
Torch
the charging icon does work properly however there is a little delay
can boot into TWRP recovery with the usual button combination (hold buttons: Power on + Home + Volume up)
kernel and recovery .img can be flashed from TWRP (no need for PC to flash Sailfish OS, kernel and recovery)
Low Power Mode (AKA "sneak peek" or "ambient display") works (install instruction is in this post)
Do not work:
Bluetooth
Light sensor is turned off
Video recording (WIP)
Video playback (WIP - until you can use Kodi for playing videos)
Just like with the S2 (i9100) there is an extra little issue is a delay in screen refresh.
Battery life:
In my experience the battery life is good. (Although the battery I have in the device is VERY old.)

Thanks for sharing

Thanks for sharing! Installed successfully.
In my case I used CWM to flash lineageOS + Sailfish and Heimdall to flash the kernel img.
Found issues
Camera doesn't work (black screen for both rear and front one)
Problem with keyboard switching (to symbols and back). It doesn't redraw itself until you press any button.
Native browser doesn't work at all (wi-fi connection works and another browser installed from jolla store also works)
Everything works very slow as expected for this device.
Anyway it is cool to test this OS even on such an old device.

vladzholud said:
Thanks for sharing! Installed successfully.
In my case I used CWM to flash lineageOS + Sailfish and Heimdall to flash the kernel img.
Found issues
Camera doesn't work (black screen for both rear and front one)
Problem with keyboard switching (to symbols and back). It doesn't redraw itself until you press any button.
Native browser doesn't work at all (wi-fi connection works and another browser installed from jolla store also works)
Everything works very slow as expected for this device.
Anyway it is cool to test this OS even on such an old device.
Click to expand...
Click to collapse
Thanks for sharing your experience.
The camera is an interesting issue because it is working on my device. (I use the very first build, which didn't even boot into the UI and where then I manually applied all fixes. Now it has most of the stuff working.) However, I couldn't make it work in newer builds. No matter what I tried, the camera just reluctant to work.
The other problem relating to the keyboard is, unfortunately, is also a result of that device is being old. (The same issue appears on my Galaxy S2 (i9100) which is an identical device.) I don't think this can be fixed but I think if you are aware of this it is bearable.
The native browser is also painful on these old devices. It might be improved in the newer 4.1 SFOS but I have not built that yet, so cannot confirm. I hope will find some time eventually to refresh all of my ports including this one to SFOS 4.1.
I am glad you are happy to try this OS on this ancient device. It was a nice addition to my collection too.

Came as I was searching for the sailfish os for note9, glad to see some Samsung users enjoying the OS, maybe one day someone will port to other devices too.

only be able to get in the download mode, tried many times to flash stock ROM via odin, but all failed. any thoughts?
much appreciated.
cheers
lenco

lenco75 said:
only be able to get in the download mode, tried many times to flash stock ROM via odin, but all failed. any thoughts?
much appreciated.
cheers
lenco
Click to expand...
Click to collapse
Haven't been here for a while but this might not be too late.
Do the following:
With Odin install Philz recovery: PhilZ-cwm6-XXLT4-OXA-4.93.6.tar.md5
Boot into recovery and install Los14.1 Nightowl-lineage14.1-20180215-n7000.zip or any ROM that is available for the N7000. (The Nightowl ROM will install TWRP, so if you are more familiar with TWRP, just reboot into recovery again and you can flash the wanted ROM.)

I have a problem with mobile data, it cannot connect. thanks for work!

Zarosky said:
I have a problem with mobile data, it cannot connect. thanks for work!
Click to expand...
Click to collapse
I've just tested it on my device. It works. In Settings/Mobile network/Data access point, the protocol is set to IP.

[Guide] Dasaita px6 MTCE_HA update/upgrade Android 10 to Android 11

After spending 2 days on the forums and softbricking my device for several times, here's my 2 cents about on how to do the upgrade from Andorid 10 to Android 11 or even to downgrade ... on the HA units from Dasaita.
First of all, a small disclaimer:
This worked for me, it might not work for you.
You might end up in bootloop, blackscreen, softbrick, be aware of this risk
My device is a Dasaita Max11, I wanted to downgrade to A10, in order to get Magisk and Hal9k v5 mod installed.
After purchasing modinstaller 3pro, and trying to install Andorid10 I ended up in a blackscreen. Hopefully @Hal9k_ will be able to fix this in his further releases.
Remember, this was ONLY tested and worked on a MTCE_HA device. A rather new model sold by Dasaita last december. If you have a HTC or other device this has no or litlle importance to you, since the images atached are ONLY for HA devices. Also, if you have an older Dasaita model, it might not work as described bellow:
What you'll need:
- a USB A to USB A cable (as short as possible)
- the purple usb plug cable (labeled carplay/android auto) that comes out of the back of de divice (this is the only one that recognized my device in bootloader mode. Feel free to try the others, in function of what configuration your device might have.
- driver assistant (see google drive link)
- flash tool (see google drive link)
- full system image of Android 11 or 10 regarding what you want.
- a pin or paperclip to push the reset button.
The procedure is rather simple:
1. Download and install the driver assistant (google drive link at the end), run it to install the drivers on your windows machine
2. Unpack rkdevtool and run the exe (google drive link at the end). At this point the program will display a huge message in the bottom part saying: "no devices found". That's good.
3. Connect the Usb cable to the HU and to the PC, while the device is turned off (like no power, not in sleep mode)
4. Push the reset button and keep it pushed. While doing this turn on the device. At this point if everything is setup correctly you should hear a notification sound from windows and RKDevTool should say: "Found one bootloader device".
4a) If you only hear the notification and the device is not found in boot loader mode by RKDevTool, check Device Manager and try to reinstall the drivers / install other drivers, try another USB port. (at this point, the usbA to usbA might be to long if the device manager shows: unrecognized device)
4b) If you hear no sound, RKDevTool still shows no devices: Turn off the HU, (really of, no power). After 10-30 seconds turn it on, while it is on, press the reset button and keep it pressed (even after side leds flashing) until the device enters bootloader mode and it is recognized by the RKDevTool.
4c) If none of the above work, switch the usb port on the HU, or try another combination of reset pushing (like trying to enter recovery)
4d) If the PC won't recognize the device in bootloader mode, it might be a situation in which the device is not capable of this, and you might need to take it apart and use the direct SOM flash method ... search the forums.
During step 4 the HU display should remain black, so the only indication of being in bootloader mode and connected to the PC, is the windows notification sound and the messege displayed by RkDevTool.
5)With the device in bootloader mode, connected to the PC, in RKDevTool go to the tab that says: Upgrade firmware. Click on the line(empty rectangle) that says firmware and browse for the desired android img. (10 or 11). See drive link. Attention: the zips from the drive MUST be unpacked and the update.img must be loaded in RkDevTool.
6)After selecting the desired update.img, click on the ERASE FLASH button, wait until the process completes. If everything goes well, the device should reboot in maskrom mode.
7)After the device enters maskrom mode, RkDevTool shoul display the message: "Found one MASKROM device". At this point, just click the UPGRADE button. The new android is flashed on the HU. When the process is finished the HU reboots ITSELF. If that doesn't happen after 1-2max, cut the power and power on.
It should boot in the new android.
Final thoughts after 2 days of thinkering:
This worked for me to downgrade from 11 to 10, and also to upgrade from 10 to 11. Be aware it might NOT work for you!
In theory, if one can get the device in bootloader mode it should work also to upgrade from andoid 9 to 10. This is just a theory and I did not test it.
The advantages of Android 10 over 11 are (for me):
- root access via Magisk (for the time being I could not root 11 with any of the tutorials found online)
- less crap and restrictions imposed by the growing Google censorship..
- the possibility to install the Hal9k v5 mod, one of the greatest and customizable mods ever made for MTCD/MTCE devices.
- using both 11 and 10 I could very certainly tell you, that (from my point of view), 11 has no advantages over 10, nor in stability nor in sharpness.
The images from the google drive are vivid for android 10 and max for android 11. Again, this are FULL images, not just OTA. I put them here after endless hours of searching the net. I respectfully thank to those that took the time to upload them on xda and dasaita forums.
Once you install the base 10 or eleven you can easily switch from vivid to max via update.zip flashed from an usbstick.
Also: there are many tutorials that involve a sdcard, sdcardtool and different combinations of zip images. I tested them ALL using the side sd card slot of the device. NONE OF THEM worked for me. I found the OTG flash method to be the fastest and most reliable, once I figured out how to connect de HU to my pc in bootloader mode.
PX6 MTCE_HA Android 10 full image, Android 11 full image, RkDevTool, Driver Assistant link: https://drive.google.com/drive/folders/1eigYrCKl8Z34KQxBoX3Q91Foy2K15CGm?usp=share_link

Nice! Do you perhaps know where to find the files for other headunits? I have a MTCE_HT and have no idea where to look!