I'm having the following problems with my TAB and would like to know it's fixable. I treid almost everything to fix it without success. I'm hoping someone can help me. Anyone have these problems before?
1. Doesn't charge normally. It would charge but charge really slow like it's connected via us. It shows an x next to the lightening icon when I charge it using the original charger and cable.
2. I cannot go into recovery mode. I get the black screen with the white line. There's also no boot animation when it boots up.
3. The camera doesn't work. I get a fail message when I open it.
4. My computer doesn't detect it in download mode, kies or mass storage. My computer detect my samsung galaxy s i9000 without any problems so I know it's not the computer. I cannot change the firmware because my computer doesnt detect it.
5. I dont have the receipt to do a warranty repair. What are my other option?
AT&T SGH-i987
Firmware 2.2
Baseband P1000XXJHA
Kernel 2.6.32.9 [email protected] #19
Build XXJMA
Any help is much appreciated! Thanks!
Did you register your Tab with Samsung?
If so, they have a record of your purchase and will be able to provide support.
If not, then try this which I got from their online chat: Hope it helps.
"Kyle: To recover the device via the hardware keys, do the following:
Kyle: 1. Power off the handset.
Kyle: 2. Hold the Vol Down Key + Vol Up Key + Power Key for 15 seconds then release.
Kyle: 3.When the recovery screen comes up, use the volume up key and volume down key to navigate through the selections and the power key to select item.
Kyle: 4. Select Delete all user data to recover the device. To confirm, scroll down and select Yes – delete all user data. The phone reboots and again displays the recovery screen.
Kyle: 5. Select Reboot system to restart the handset again. "
Thanks but I cannot get to that recovery screen like I said above. All I get is a black screen with a white line when I try to go into recovery mode. I also purchase this used with no receipt.
U just need to flash a working rom. Try roto jm... in the dev forum
Your tab was modified. I wont blame Samsung if they wont fix it for u
Sent from my SGH-I987 using XDA App
How do i flash to a different rom if a computer wont detect it?
Do you have the latest kies installed? Is USB Debug on? If it still doesn't detect, have you tried android-sdk or heimdall. Each comes with usb driver. I find it hard to believe your PC doesn't detect the tab. I never heard such thing before unless you're the real first victim then...yeah, try to call Samsung and pay a fee.
Yes, I tried to use android-sdk and heimdall but they don't detect my TAB for me to do anything. I also installed the newest KIES software. I also don't understand why it doesn't detect it in download mode. This is the first time I encounter this problem. I flashed my Galaxy S I9000 phones many times without a problem. Is the combination of the firmware and kernal I have that is causing my computer not to detect the TAB?
Is there a way to root my TAB via an APK? I tried Z4Root but it's not working. It tries to acquirer shell and closes after a few vibrate. yes, debugging mode is on.
starbuck123 said:
Yes, I tried to use android-sdk and heimdall but they don't detect my TAB for me to do anything. I also installed the newest KIES software. I also don't understand why it doesn't detect it in download mode. This is the first time I encounter this problem. I flashed my Galaxy S I9000 phones many times without a problem. Is the combination of the firmware and kernal I have that is causing my computer not to detect the TAB?
Is there a way to root my TAB via an APK? I tried Z4Root but it's not working. It tries to acquirer shell and closes after a few vibrate. yes, debugging mode is on.
Click to expand...
Click to collapse
You've followed Heimdall's README and installed the included driver? Make sure you follow the instructions exactly.
If you have done that and your device still isn't recognised consider trying a another cable, USB port or entirely different PC.
Benjamin Dobell said:
You've followed Heimdall's README and installed the included driver? Make sure you follow the instructions exactly.
If you have done that and your device still isn't recognised consider trying a another cable, USB port or entirely different PC.
Click to expand...
Click to collapse
Thanks for your advice but I already tried above. I didn't have any problems/trouble connecting my Verizon Tab and Galaxy S phone to the computers to change the roms. There is most likely something wrong with the Tab. I gave up and contacted Samsung yesterday. I sent the Tab to them yesterday and hopefully they won't charge me to fix it.
I got a serious problem with the N4 of a friend.
First thing to know: his display was broken and he got it repaired. Afterwards, his phone was running fine. Then, he got the Android 4.3 OTA. He accepted the update, but since then in keeps bootlooping (I won't go past the Nexus-X). As far as I know, everything was stock!
Here are the things I tried:
- first I checked the recovery. Indeed it was the stock one, so nothing to do here.
- I wanted to wipe or flash the stock rom using fastboot but i wasn't able to get a connection. First I thought of driver issues, but my N4 works fine (adb & fastboot) on the same computer.
- Establishing a connection failed on two other computers too (my N4 worked)
- Even the device manager in Windows 7 dosen't even recognize anything when plugging in the usb cable (normally you see the ADB whatever device listed in the device manager)
- Right now I tried to get a connection using Ubuntu. Again, no usb device was recognized when plugging in the cable.
So right now, I'm a bit lost. It seems, that the usb port is broken since I can not establish a connection. And without that, I won't be able to wipe or flash anything using fastboot.
Does anyone have an idea what could have gone wrong? I'm still able to boot into the bootloader and see the information:
Bootloader version: MakoZ20i
Radio: .84
HW Version 11
16GB version
According to these information, it seems that the 4.3 Update finished at least the bootloader and radio. But it won't boot into the rom. Could the download mode be of any help?
I appreciate any help.
Thanks.
Since you are in the bootloader scroll up to recovery and select it.
Now you will see a android opened up with "No command." written below the android.
Press volume up and power until it unlocks the recovery and try to wipe the data and cache partition followed by dalvik cache.
Sent from my Nexus 4 using Tapatalk 4
Thanks for your idea, but it turned out to be hardware problem!
I took the device to the lab and had a look at the usb connector. The contact in the middle was teared of the carrier and was stuck to the back and thus no data connection could be established! I was able to to bend it back (more ore less) to its initial position and now its working. Though I'm wondering how long it will last until its pushed back again.
Fact is, that i was able to connect via fastboot. I tried to flash 4.3 again but it still didn't boot. Its back to 4.2.2 and its working now.
Again - thanks for your idea.
Thread can be closed!
A bit of an SOS situation if anyone knows the right steps please
Well, I restored a Titanium Backup and mistakenly toggled the "restore system apk". It ran fine, all restored and then when I rebooted got stuck.
By "stuck", it re-boots constantly. It shows the LG animation, then all I can see is two messages before it starts booting again:
1) "Unfortunately, Google Play Services Has Stopped"
2) "Unfortunately, System UI has stopped
... and then it does the entire boot sequence, animation, again, and again.
Here is what I can do:
* It is in USB debug mode.
* I have drivers on laptop
* I am able to connect with adb and also shell into phone.
* With adb, I have output to the file an "adb bugreport" as well as an "adb logcat".
* I have several backups:
a) The modemsst1.img and modemsst2.img created by Titanium Backup
b) Titanium backups (full apps and data)
c) an "adb backup - all" backup
* I managed to get it into firmware update mode by pressing the volume up button and the power button and then when it flashed red a few times, just the up button. So, I can get it into Firmware update mode.
Of course, I have never really used adb before, except to dabble a bit. So, I am encouraged that I can somehow get into with shell.
I am not unplugging it until I know what to do!
Since then I have been able to turn the phone off and also put it into charging on USB.
This is what worked:
* Hold down power and volume down button until booting stops and phone turns off completely.
When it does shut down, I kept buttons down until it flashes logo again and then shuts down again. Then I let go. Phone is off and when I plugged in the charger it shows charging animation.
Now, after inspecting the bugreport, I noticed a lot of these messages for all the system apps like this one:
"I/PackageManager(21318): Expecting better updatd system app for com.lge.sizech"
I think the cause of all this shralp is this, I did a LG Mobile Support Tool "Upgrade Recovery" and then in Titanium Backup I restored an older backup (incl system apks). At least that makes sense seeing all the "Expecting better apdat system app" messages in the bugreport.
Still not sure what to do next
I tried the very good instructions here:
[Guide] Unroot/Unbrick - flash official factory firmware with LG Launche
http://forum.xda-developers.com/showthread.php?t=2471370
The update succeeded. However, when I rebooted the phone it is in the same boot-loop with message that it was before.
I used the BELL D803B10D_00.kdz file. Now I will try with the earlier version BELL D803BA_00.kdz file.
We will see what happens ...
do you have nandroid backup from previous rom?
I have three backups:
1) Titanium Backup (full)
* This was my first backup performed right after rooting device and installing Titanium Backup.
2) Titanium Backup (full)
* Did this 2 days ago. Device was working OK and did as precaution.
3) ADB BACKUP. I did this one before my Titanium restore.
I restored the first titanium backup and that (ooooppps!) was after I did an LG Firmware update.
ALSO:
I am on Windows 7 64 and although adb works fine, fastboot does not. I understand that might be a problem with windows 7 64.
So, unless anyone objects, I am going to redo on my windows 32 machine and also "fastbook oem unlock".
Since firmware is OK, if I do the fastboot oem unlock, that will wipe everything. But I can still boot and re-setip the phone, right?
Just checking before I fudge everything up here ..
ALSO ALSO:
I had antivirus/theft security installed and I disabled it partway through last restore.
Maybe that has somethng to do with this all .
But I am still cool because I can ADB and also firmware install seems ok.
ADB works and that is the one good sign.
or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497
zekurosu said:
or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
I don't (didn't) have TWRP installed. How can I sideload without it?
Also, should I adb oem unlock to get it wiped at this point?
I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?
asdfvtn said:
I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?
Click to expand...
Click to collapse
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.
I used adb uninstall package for many user packages and it was success. But I still see the packages listed in the bugreport?
For example: I already uninstalled "com.benhirashima.skiplock" and also "com.lookout".
Why? What to do to really zap them for good?
Sorry, I posted the wrong link earlier.
This was the guide I used which succeeded but made no difference to the boot-loop.
LG G2 Stock Firmware (Go Back to Stock)
http://forum.xda-developers.com/showthread.php?t=2432476&highlight=d803
Just figured out how to do a factory reset.
http://www.youtube.com/watch?v=3ogBvzbPikc
The hard reset worked and now I am configuring the phone settings!
So, again, this is what I did:
1) http://forum.xda-developers.com/showthread.php?p=45293512
2) http://www.youtube.com/watch?v=3ogBvzbPikc
Not sure if it all worked but I am setting the phone up as we speak (or as I type)
natureburger said:
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.
Click to expand...
Click to collapse
Hmm that's strange. Unfortunately for me, I'm already on 64-bit and it still isn't picking it up.
ALL FIXED UP
WORKING 110%
:good:
natureburger said:
ALL FIXED UP
WORKING 110%
:good:
Click to expand...
Click to collapse
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.
zprovo said:
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.
Click to expand...
Click to collapse
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Then .. do hard reset, exactly like this:
http://www.youtube.com/watch?v=3ogBvzbPikc
Does the hard reset screen show and give you hard reset options?
natureburger said:
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Click to expand...
Click to collapse
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:
zprovo said:
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:
Click to expand...
Click to collapse
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
4) Which kpz version did you restore to?
5) Did your "adb devices" ever work? Did your "adb shell" ever work?
natureburger said:
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
Click to expand...
Click to collapse
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.
zprovo said:
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.
Click to expand...
Click to collapse
Hmmmm..... why your adb devices is not working? But the re-pair works and you can then do hard reset.
But that is good information you shared.
Maybe someone else can chime in.
From my experience:
1) adb usb access seems spotty. My win 7 64 connected fine and it even kept the shell through the reboot cycle. But on my win 7 32 machine it was only detecting device and then not able to shell.
2) I was also able to use from the LG website LG MOBILE SUPPORT TOOLS.
Download the LG MOBILE SUPPORT TOOL
I downloaded the most recent one from the LG website and make sure to select your options >> country and then the correct phone model at the upper right hand corner of the tool.
Then install USB driver for correct phone model.
Then see if USB works, "adb device" should return the device code.
"adb shell" should show the shell prompt.
3) There is always fastboot. But I an noob and know 0% about how to properly connect and use it.
Some others please chime in and help this droid bro!
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.