Hi all!
I'm new to DHD but NOT to android as I have a HD2 running android since July 2010!
However i made a fatal idiot error when i was so existed to the extent where i updated the software directly when getting it and now i'm stuck with it. I have:
-2.3.3 android
-2.42.415.1 build
-12.54.50.25U_26.09.04.11_M2 baseband.
- and of course a stock ROM unrooted and locked!
Ok so here's the minor issues i'm having:
1- Although i have disabled (unticked) all prediction and spell correction in keyboard settings, it's still giving me a red line under wrong words (or so it thinks) and gives me the ability to add it to custom words although i dont want that.
Any help on that?! (i know i can install another keyboard but the stock one is the perfect for me)
2- Weather animation (after unlock) plays 1 on 20 times with sound effects and the remaining 19 times without any sound!
Any help on that too?!
4- The magnification window that is created when u scroll on a keyword while typing is shifted upwards!!!
Example: if i write : asdaksdj asd midnight lkj asdakjd akj daklsj dalkjsd
asd asdl kjas dlkajsd lakjd laksjd daytime laskjd laskjd laskj dlakjfggjwpio
qweoiusdfkj dfknsdlfisdfop
and if slide on "daytime" i can see the word "midnight" magnified while i can see the top of the cursor moving on the word "daytime"!!!
However also 1 on 20 times it works normally!!!
Any help?!
3- Finally one irritating issue is that i cannot set a security lock screen for this phone!
In fact, i "can" set a "pattern" or a "PIN" or a "Password" without any problem, however it does only work once after unlock!!! After that it will be disabled automatically. When i go to settings i can see like if there's no security locks!!!
Any help on that please?! (PS whatever the duration of autolock (i mean immediately, after 3min, etc....) is set, it's still the same)
Thanks guys!
Anyone please?!
red dots are bug(or maybe htc didnt want to disable that) , also all htc gingerbread update have bugs, that's the reason i rooted my phone, because factory reset didnt help me.
i didnt have problem with weather.
try factory reset, and if that does not solve the problem, root is your friend.
before you done factory, remove battery for few seconds, and see if you still have problems.
I think you try doing 'Factory data reset'
Factory data reset will lose all data on your phone memory but not the data on SD card. So make sure you back up SMS, Contacts and calendar entries etc..
Then go to 'Settings > SD & phone storage > Factory data reset
then follow the instructions.
Hope this will help,
Good luck!
the question is
How in the hell you couldn't downgrade ...to get ROOT
Re-written to be more concise and readable:
Long story short: I installed the program "Permissions Denied" from the market and restricted a few games. When I rebooted something was broken and I can't quite figure out what, but it runs deep through the phone.
The phone isn't bootlooping, but when I starts up it will very often become unresponsive immediately after getting to the lockscreen, my theory is that things are trying to load and crashing in the background. The only fix for this is to wait until it appear to reboot itself; the screen will come back on and show me a quick few cycles of the boot animation, then back to the lockscreen. After this, it asks to re-activate on the network. Whether or not everything works after this point has been highly variable. Currently, my phone is on but has no way of signing into a google account (isn't even an option in the list under settings).
If I try to restore a nandroid, at the very end it spits out "Error while restoring /data!". I've done this with a couple nandroids that I've used fine in the past. Fully wiping from CWM and installing a fresh rom yields similar results.
Basically my thinking at this point is to back up anything I want while I have access to the phone and try to do as full a factory reset as possible. Any ideas? Of note is that I've run the "fix permissions" function both in CWM and ROM Manager, and when I run it in ROM Manager the log shows permissions for a bunch of programs that have been wiped. So I'm guessing that permissions settings persist across wipes, but I don't know what to address that with specifically.
Bump? (rewrote OP to make it less of a train wreck of my late-night detective work)
Edit with maybe-progress: I found and installed an older apk for Permissions Denied and even though this is an older nandroid and everything has been wiped time and again, the permissions for the games I changed are still disabled.
Having trouble getting the program to actually undo anything though, and rebooting the phone is a rather tiresome task with all this going on just to find out nothing changed.
Does anyone know
1)Where permissions live, and if I can reflash whatever that is, as it is clearly corrupt here.
2)Where I can get a copy of the v2.9 apk for this app, as maybe it will be better at restoring what it did than the older version I dug up.
Edit2:I eventually just did a factory reset and it fixed everything. I had also emailed the developer of the app and he got back to me with the following advice:
It sounds like the permissions file is locked, packages.xml. Try opening my app, going into the settings, and make sure that the first option is NOT checked.
Then hit the unlock option to unlock the file.
If that doesn't work, try the following in a terminal...
su
chattr -ia /data/system/packages.xml\
Click to expand...
Click to collapse
Intuitively this sounds like it may have fixed the problem, so I'm posting it here in case anyone ends up with similar problems and finds this thread searching.
Code:
Code:
/*
* Your probably long expired warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you
* and point my finger right back at you.
*/
What is this ROM/thread?
This is a port to the i9000 of my work for the SGH-T959P which is the Telus version of the Galaxy S. I initially started work on AOSP to see what exactly needed to be changed from AOSP to work on my device. I had a request for access to an i9000 build hence I created this thread. This is also a place to discuss using my source code to build other ROMs and/or improve it. This is not a place for a general development "How do I build a ROM?" questions - there are plenty of guides on XDA and elsewhere that say how to do this. Since I don't have an i9000, I probably can't reproduce your bug unless it is common on my device as well. As such, I will be able to provide very limited support, so if you have any concerns about your phone bricking, do not flash anything from this thread!!
Installation Instructions
You should be able to flash this from any MTD rom, but it probably works best from a 6.0 or 7.x based ROM. Root does not come pre-installed, instead you need to manually install. Due to our odd partition system, please see http://forum.xda-developers.com/showpost.php?p=69245956&postcount=3 for instructions.
Things to Take Note Of
If you decide to install gapps at a later date (ie after you've installed the ROM), you must do a factory reset first - otherwise you will get force-closes upon bootup
This build is very close to the official AOSP source code. Recovery is TWRP but otherwise there aren't any added "features" - nor will I add any as this is
Gapps eat up about an extra 30MB of RAM so they slow down the device - tread carefully. Opengapps pico should work just fine but are untested
Backup Backup Backup! I'm not responsible for you losing any data or anything else that could go wrong.
Working on my variant
Camera (built-in app needs workaround, see below)
RIL
SMS
Wifi
Vibration
Automatic Brightness
Compass
GPS on T959P
Headset Buttons
Partially working
Bluetooth - first time trying to enable won't work, back out of the Settings page, re-enter it and try enabling again. It should work this time...
Camera and Browser apps need to have all their permissions manually enabled through settings for full functionality. This is because I've used the older Camera app (which hasn't been updated for dynamic permissions) and the older Browser app as the new one is simply a test shell with no features (thanks Google!)
What doesn't
TWRP build is currently broken. To work around this, replace the ramdisk-recovery.img in the zip with the one from CM14.1
SElinux is currently in permissive mode. Still missing are the GPS sepolicies plus the LVM ones. If someone sends me a dmesg, I might be able to change this...
What's been removed
TV-Out - It was removed upstream plus I think binary blobs would need a ton of shimming in Lollipop+ Please do not ask me to implement this, I've tried several times and failed miserably each time.
I haven't actually verified that this boots as I don't have this specific variant!!!
XDA:DevDB Information
AOSP 7.1 ROM/Discussion, ROM for the Samsung Galaxy S I9000
Contributors
xc-racer99, Coldwindofnowhere
Source Code: https://github.com/xc-racer99/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Android 6.0
Based On: AOSP
Version Information
Status: Testing
Created 2016-12-21
Last Updated 2016-12-20
Please have a look at the thread I created for my variant at http://forum.xda-developers.com/galaxy-s-4g/development/rom-aosp-7-x-galaxy-s-4g-t3485237
Build your own!
All the device-specific source code is on my github at https://github.com/xc-racer99/. The branch I've used for the build posted below is the aosp-7.1 branch. The aosp-7.1-ddk-1.19 is test branch that uses the latest DDK 1.19 PVR blobs for OMAP devices. Unfortunately, it breaks hardware decoding (and you would need to compile the correct kernel as it uses a different PVR kernel driver). It is more of interest than of actual use.
Follow https://source.android.com/source/initializing.html. The branch you want when you run repo init is the latest tag from https://source.android.com/source/build-numbers.html#source-code-tags-and-builds of 7.1. Before you run repo sync, from the WORKING_DIRECTORY/.repo folder, run "git clone https://github.com/xc-racer99/local_manifests -b 7.1". Continue on with the build guide, the device codename you want is "galaxysmtd".
If you want to build the kernel, follow the instructions in WORKING_DIRECTORY/kernel/samsung/aries/AOSP_README. Put the resulting arch/arm/boot/zImage in device/samsung/galaxysmtd
Other aries devices (captivate, i9000B, vibrant) should be fairly easy to do (ie the galaxysmtd on my github as well as the captivate trees work). The fascinate and p1 would need a fair bit of work. There is an i9000B kernel uploaded to https://www.androidfilehost.com/?fid=457095661767123305 - simply replace the boot.img in the i9000's zip with this one and it should work (except that in Settings you will appear as an i9000 instead of an i9000B).
For porting to other ROMs, please take note of https://github.com/xc-racer99/android_patches - these are the patches that the custom ROM and/or you must implement to have a successfully booting and functional device. You also need to have busybox and TWRP as part of the build tree.
Download Link and Changelogs
A reminder - I've not personally tested any of these builds...
2017-01-19 Build
Updated interactive governor - should result in fewer slowdowns if you use this governor
Changed low memory killer parameters so it kills a little quicker (ie before it runs out of memory)
Disabled a bit more background stuff to hopefully free a bit more memory
Fixed/cleaned up the shims that are used for the RIL - should prevent SSL issues (eg with Hotmail accounts) as well as being slightly faster and more reliable
Selinux is still in permissive mode (a dmesg could possibly help me in putting this to enforcing, if people are interested). I still don't know if the TWRP included in it is functional or not (someone can let me know, I guess )
Older Builds
2016-12-26 Build
Home button should now work
SD card/internal storage should work properly
Added ability to have /data on microSD (see here for info)
2016-12-19 Build
Anyone can test this build to see if data is working properly on his build ? RIL seems to crash randomly for some reason in 7.1.1 with cm 14.1 ...
Coldwindofnowhere said:
Anyone can test this build to see if data is working properly on his build ? RIL seems to crash randomly for some reason in 7.1.1 with cm 14.1 ...
Click to expand...
Click to collapse
Despite the fact that i have used all my mb to my phone,data opens normally and don't have any problem with crashes etc.
edit:Lost RIL all of a sudden with x on network.rebooted and it laid to TWRP saying no OS is installed.Starting all over again with odin etc.
ioannis_m said:
Despite the fact that i have used all my mb to my phone,data opens normally and don't have any problem with crashes etc.
edit:Lost RIL all of a sudden with x on network.rebooted and it laid to TWRP saying no OS is installed.Starting all over again with odin etc.
Click to expand...
Click to collapse
Hmm, ok. Thanks for testing. I guess that means it boots Did the sdcard(s) get detected properly? In my earlier builds of AOSP I had difficulties with this.
It's possible that my TWRP build is non-functional. Try replacing the ramdisk-recovery.img in the zip with one from @Coldwindofnowhere CM14 build.
Thanks for testing.
First of all thanks for bring AOSP NOUGHT.everything work fine.like
Camera,storage,WiFi, hotspot,Bluetooth, ril.
But I found some issues.
1.browser working but couldn't browse
But third party browser work fine.
2.outgoing call fine.but when come incoming call
Device not wakeup also get hanging till incoming call cut.also network gone.after reboot it work fine.
udhy said:
First of all thanks for bring AOSP NOUGHT.everything work fine.like
Camera,storage,WiFi, hotspot,Bluetooth, ril.
But I found some issues.
1.browser working but couldn't browse
But third party browser work fine.
2.outgoing call fine.but when come incoming call
Device not wakeup also get hanging till incoming call cut.also network gone.after reboot it work fine.
Click to expand...
Click to collapse
Hmm, did you install gapps? I'm assuming by what you mean for "couldn't browse" is that a white screen appeared instead of content. This is likely due to a different webview provider being installed which removed the AOSP one.
Odd that you're getting incoming call issues. Do these happen with @Coldwindofnowhere CM14 build? There are a couple of things I could try to fix but I'm not sure. I rarely if ever make calls on my phone so I don't know what all issues exist.
xc-racer99 said:
Hmm, did you install gapps? I'm assuming by what you mean for "couldn't browse" is that a white screen appeared instead of content. This is likely due to a different webview provider being installed which removed the AOSP one.
Odd that you're getting incoming call issues. Do these happen with @Coldwindofnowhere CM14 build? There are a couple of things I could try to fix but I'm not sure. I rarely if ever make calls on my phone so I don't know what all issues exist.
Click to expand...
Click to collapse
Umm no never had this issue with cm 14.1, but in the latest build sometimes ril just crashes for no apparent reason then it's back one I reboot.
Coldwindofnowhere said:
Umm no never had this issue with cm 14.1, but in the latest build sometimes ril just crashes for no apparent reason then it's back one I reboot.
Click to expand...
Click to collapse
Have you (or anyone else) managed to get a log (radio logcat, dmesg and regular logcat)? Just wondering what exactly is crashing. Likely rild - and there's a bug in our libsec-ril.so so that it won't restart automatically because then it crashes the system...
xc-racer99 said:
Hmm, did you install gapps? I'm assuming by what you mean for "couldn't browse" is that a white screen appeared instead of content. This is likely due to a different webview provider being installed which removed the AOSP one.
Odd that you're getting incoming call issues. Do these happen with @Coldwindofnowhere CM14 build? There are a couple of things I could try to fix but I'm not sure. I rarely if ever make calls on my phone so I don't know what all issues exist.
Click to expand...
Click to collapse
No.i didn't install gapps and not appeared white screen in browser anything browse in browser(sys app) its loading,loading, loading.....
Incoming call working but delay to wakeup when incoming call come.
I used one day full.my device good. Rarely crash ril. These few issues only problem in the otherwise this rom so good.
Sorry for bad english.
Thanks xc-racer99 for making AOSP Android 7.1 .
I just installed it on I9000B with the kernel that you made available for this device. I felt that the time of first boot after installation is faster than cm14.
I found some problems:
1) The home button does not work.
2) The android is having problem with internal storage (Data and Internal Memory). It is displaying strange values of used and available space. Camera can not save photo or video.
I'm not using SD Card External.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3) Randomly is freezing or restarting.
I'm glad that you have made the kernel available to build.
I have a question, in this code is there the patch needed to work the touchscreen of the I9000B?
Thanks,
Daniel
DanielBR911 said:
Thanks xc-racer99 for making AOSP Android 7.1 .
I just installed it on I9000B with the kernel that you made available for this device. I felt that the time of first boot after installation is faster than cm14.
I found some problems:
1) The home button does not work.
2) The android is having problem with internal storage (Data and Internal Memory). It is displaying strange values of used and available space. Camera can not save photo or video.
I'm not using SD Card External.
View attachment 3976988
3) Randomly is freezing or restarting.
I'm glad that you have made the kernel available to build.
I have a question, in this code is there the patch needed to work the touchscreen of the I9000B?
Thanks,
Daniel
Click to expand...
Click to collapse
Right, that kernel is designed for 7.0 and doesn't have the patch to fix the freezes present in 7.1. Try the one from https://www.androidfilehost.com/?fid=673368273298918331
Home button doesn't work - as in doesn't wake the device or doesn't work period? AOSP doesn't support the home button waking the device (OEMs and most custom ROMs implement this).
Internal storage - now that is interesting. In my earliest test builds of 7.0, that was a feature there. I don't know why it's reappeared. Perhaps a data wipe will fix the issue??? The Camera issue is related to this IMO. You could try using OpenCamera as I've had success with it on my device.
udhy said:
No.i didn't install gapps and not appeared white screen in browser anything browse in browser(sys app) its loading,loading, loading.....
Incoming call working but delay to wakeup when incoming call come.
I used one day full.my device good. Rarely crash ril. These few issues only problem in the otherwise this rom so good.
Sorry for bad english.
Click to expand...
Click to collapse
Ok, thanks for the clarification.
xc-racer99 said:
Right, that kernel is designed for 7.0 and doesn't have the patch to fix the freezes present in 7.1. Try the one from
Home button doesn't work - as in doesn't wake the device or doesn't work period? AOSP doesn't support the home button waking the device (OEMs and most custom ROMs implement this).
Internal storage - now that is interesting. In my earliest test builds of 7.0, that was a feature there. I don't know why it's reappeared. Perhaps a data wipe will fix the issue??? The Camera issue is related to this IMO. You could try using OpenCamera as I've had success with it on my device.
Ok, thanks for the clarification.
Click to expand...
Click to collapse
Thank you. Now the android is not freezing anymore.
About the Home Button , no function is working. Usually when it's pressing the apps are closed.
Something strange happened to the internal storage. I performed the Wipe Data.
Now I can not format any other partitions (System, Data, Cache).
I will run Odin with the partition map and Android 2.2.
To install AOSP 7.1 is it necessary to have Android 6 installed before?
Thanks
Daniel
I did some experiences:
1) If I use ramdisk-recovery.img and ramdisk.img from CM 14 or Cm 14.1. In TWRP, the size of the System and Data partitions is usually recognized and I can format them both in EXT4.
But the Android shows that the internal memory is corrupted. Not being able to record anything in memory.
2) If I use the original ramdisk-recovery.img and ramdisk.img from AOSP 7.1, TWRP does not recognize the size of the System and Data partitions and I can not format them.
The android shows that the internal memory is corrupted. Not being able to record anything in memory.
DanielBR911 said:
Thank you. Now the android is not freezing anymore.
About the Home Button , no function is working. Usually when it's pressing the apps are closed.
Something strange happened to the internal storage. I performed the Wipe Data.
Now I can not format any other partitions (System, Data, Cache).
I will run Odin with the partition map and Android 2.2.
To install AOSP 7.1 is it necessary to have Android 6 installed before?
Thanks
Daniel
Click to expand...
Click to collapse
DanielBR911 said:
I did some experiences:
1) If I use ramdisk-recovery.img and ramdisk.img from CM 14 or Cm 14.1. In TWRP, the size of the System and Data partitions is usually recognized and I can format them both in EXT4.
But the Android shows that the internal memory is corrupted. Not being able to record anything in memory.
2) If I use the original ramdisk-recovery.img and ramdisk.img from AOSP 7.1, TWRP does not recognize the size of the System and Data partitions and I can not format them.
The android shows that the internal memory is corrupted. Not being able to record anything in memory.
Click to expand...
Click to collapse
Ok, so it looks like the TWRP included with the ROM is non-functional. I'll make a note of that in the OP.
It is probably necessary to go to Android 6 (or at least 5.1) before going on to 7.1, but I haven't tested. It's just whether or not the package name is correctly detected by updater.sh. Since I don't have the device, I can't test...
With the home button, could you please get me a logcat? See http://forum.xda-developers.com/showthread.php?t=2185929 if you need instructions. A dmesg from the broken recovery would also be useful if you get a chance.
Thanks.
xc-racer99 said:
Ok, so it looks like the TWRP included with the ROM is non-functional. I'll make a note of that in the OP.
It is probably necessary to go to Android 6 (or at least 5.1) before going on to 7.1, but I haven't tested. It's just whether or not the package name is correctly detected by updater.sh. Since I don't have the device, I can't test...
With the home button, could you please get me a logcat? See http://forum.xda-developers.com/showthread.php?t=2185929 if you need instructions. A dmesg from the broken recovery would also be useful if you get a chance.
Thanks.
Click to expand...
Click to collapse
Here my logcat:
View attachment logcat.log
I had a problem to get Kernel log. When i run this command: adb shell su -c dmesg > dmesg.log. I got : su: invalid uid/gid '-c'.
I'm confuse. TWRP (ramdisk-recovery.img and ramdisk.img from AOSP 7.1.1) is now recognizing the System and Data partitions with their correct sizes.
But Android is still showing "SD Internal Corrupt" .
When I click in " SD Card Corrupt" a screen for formatting is opened. When I command to format the internal sd, an error message appears quickly and the screen closes. When I enter in TWRP, it does not recognize the size of the system and date partition.
I should not have done it
Now I'm going to have to run the odin to recover partition again :crying:.
DanielBR911 said:
Here my logcat:
View attachment 3977611
I had a problem to get Kernel log. When i run this command: adb shell su -c dmesg > dmesg.log. I got : su: invalid uid/gid '-c'.
I'm confuse. TWRP (ramdisk-recovery.img and ramdisk.img from AOSP 7.1.1) is now recognizing the System and Data partitions with their correct sizes.
But Android is still showing "SD Internal Corrupt" .
View attachment 3977629
When I click in " SD Card Corrupt" a screen for formatting is opened. When I command to format the internal sd, an error message appears quickly and the screen closes. When I enter in TWRP, it does not recognize the size of the system and date partition.
View attachment 3977630
View attachment 3977631
I should not have done it
Now I'm going to have to run the odin to recover partition again :crying:.
Click to expand...
Click to collapse
Hmm, I think we have two separate problems. I think Android having the issues is probably due to me removing https://github.com/Coldwindofnowher...overlay/frameworks/base/data/etc/platform.xml as I thought this was outdated and unnecessary (as I didn't need it on my device).
TWRP issue is probably different, don't use the one built into the ROM. I'll have another look through the config and try to fix it.
I didn't see any mentions of any buttons (home and/or volume) in the logcat, so we'll figure that problem out later. I'll add some debugging to the next kernel I upload.
Not surprising that the dmesg failed - try instead "adb shell dmesg > dmesg.log" - since we're not CM based we don't need the "-c" part.
xc-racer99 said:
Hmm, I think we have two separate problems. I think Android having the issues is probably due to me removing https://github.com/Coldwindofnowher...overlay/frameworks/base/data/etc/platform.xml as I thought this was outdated and unnecessary (as I didn't need it on my device).
TWRP issue is probably different, don't use the one built into the ROM. I'll have another look through the config and try to fix it.
I didn't see any mentions of any buttons (home and/or volume) in the logcat, so we'll figure that problem out later. I'll add some debugging to the next kernel I upload.
Not surprising that the dmesg failed - try instead "adb shell dmesg > dmesg.log" - since we're not CM based we don't need the "-c" part.
Click to expand...
Click to collapse
Thanks.
Here my dmesg:
View attachment dmesg.log
Thanks for your work!
I've got a few problems with your ROM.
RIL is unreliable at best. Surprisingly I had correct 3G performance at first flash and first boot, but then after subsequent reboots and then newer flashes / wipes, it totally stopped working. I have cell phone reception even though it's slow to get it, but no data at all. About plane mode, it doesn't cut the basic (non-data) cellphone service which is probably a bug too. P.S. : Got back data, see below.
After boot there is a notification about sdcard being corrupt, either when I have a sdcard or not. I cannot access /sdcard.
Home button doesn't work at all, period.
Wifi doesn't work at all, either from quick access or settings. In settings, when I tap to activate wifi, it stays stuck at "Activating wifi..." and doesn't change anything else except the button I tapped. This button reverts to off when I exit.
Bluetooth doesn't work at all, either from quick access or settings. In settings, when I tap to activate bluetooth, it doesn't change anything except the button I tapped. This button reverts to off when I exit. Well, after numerous tries, when I decided to generate my logcats (see below), tapping on "Bluetooth on" actually activated it successfully...and also made 3G work. Wtf?
Logs are attached to this message. Methodology for acquiring them :
Wiped everything. (Re-)flashed this ROM. Wiped data / cache.
Booted system a first time. Acquired LogcatFirst.log.
Rebooted system.
Tryed to toggle Wifi (from settings) on at aprox 02:50:04. Then exited.
Tryed to toggle Blutooth (from settings) on at aprox 02:51:25. Then exited. Please note that at this very moment, Bluetooth started working and I got back a 3G connection. Wtf?
Used home button from settings app at aprox 02:55:??. This does produce zero output to logcat.
Set plane mode from quick panel on at aprox 02:56:30, then off at aprox 02:58:36.
Acquired LogcatSecond.log, Dmesg.log and Radio.log
EDIT : After plane mode, I lost Bluetooth and data again.
Ano59 said:
Thanks for your work!
I've got a few problems with your ROM.
RIL is unreliable at best. Surprisingly I had correct 3G performance at first flash and first boot, but then after subsequent reboots and then newer flashes / wipes, it totally stopped working. I have cell phone reception even though it's slow to get it, but no data at all. About plane mode, it doesn't cut the basic (non-data) cellphone service which is probably a bug too. P.S. : Got back data, see below.
After boot there is a notification about sdcard being corrupt, either when I have a sdcard or not. I cannot access /sdcard.
Home button doesn't work at all, period.
Wifi doesn't work at all, either from quick access or settings. In settings, when I tap to activate wifi, it stays stuck at "Activating wifi..." and doesn't change anything else except the button I tapped. This button reverts to off when I exit.
Bluetooth doesn't work at all, either from quick access or settings. In settings, when I tap to activate bluetooth, it doesn't change anything except the button I tapped. This button reverts to off when I exit. Well, after numerous tries, when I decided to generate my logacts (see below), tapping on "Bluetooth on" actually activated it successfully...and also made 3G work. Wtf?
Logs are attached to this message. Methodology for acquiring them :
Wiped everything. (Re-)flashed this ROM. Wiped data / cache.
Booted system a first time. Acquired LogcatFirst.log.
Rebooted system.
Tryed to toggle Wifi (from settings) on at aprox 02:50:04. Then exited.
Tryed to toggle Blutooth (from settings) on at aprox 02:51:25. Then exited. Please note that at this very moment, Bluetooth started working and I got back a 3G connection. Wtf?
Used home button from settings app at aprox 02:55:??. This does produce zero output to logcat.
Set plane mode from quick panel on at aprox 02:56:30, then off at aprox 02:58:36.
Acquired LogcatSecond.log, Dmesg.log and Radio.log
EDIT : After plane mode, I lost Bluetooth and data again.
Click to expand...
Click to collapse
Alright, thanks for the complete rundown on errors. I'll try to go through them:
Bluetooth - having difficulty activating is not surprising. Android technically doesn't support non BT LE devices such as ours - I had to hack in support for no LE/SMP/GATT (the supporting parts of the BT stack AFAIK) with the patch https://github.com/xc-racer99/android_patches/blob/aosp-7.1/system_bt.patch. There's nothing I can really do about this. If you read the OP, it says
first time it won't enable if enabling through settings, back out and then second time it will. Works just fine from status bar pulldown
Click to expand...
Click to collapse
This was for 7.0, I guess it's changed slightly in 7.1 so I'll update the OP.
Data - this sounds totally bizarre. I wish I had an i9000 to test this. One of the big differences between the i9000 and my device, the SGH-T959P, is that you guys use the (infineon?) XMM616 for your modem while mine uses the M5720 by STE. I have yet to have an issue with data when I've tested it on my variant. Again, I'm afraid I can't do too much about this
Wifi - this sounds weird. There's some noise in the logcat, ie "12-24 02:50:04.778 W/CommandListener( 164): Failed to retrieve HW addr for wlan0 (No such device)". This is very surprising, I have nothing like this in a logcat on my device. I'm thinking perhaps that the MAC address wasn't properly setup. Could you please run "adb shell getprop | grep macaddr"? The RIL actually sets the macaddr so these two issues might be related. Did you check the md5 of the zip after downloading? It almost sounds like a bad download/ flash. The other thing is that yours is a special hardware model which doesn't like having the wifi driver built into the kernel (I did see a reference to this in a commit from the CM10.1 days). @Coldwindofnowhere's CM14 has it as a module so it might be working there.
Home button - I probably messed up the keylayout somewhere. My device has a capactive home button as opposed to a hard button. Please try pushing the attached files to /system/usr/keylayout after removing the ".img" at the end of the filename (to get around XDA's filetype filter).
Corrupt SDCard is probably my fault. Please try the new build at https://www.androidfilehost.com/?fid=529152257862690355 as I think I've found and corrected the issue.
Unfortunately, your logcat is very "chatty" - basically android prevents things from creating too much logspam. This sucks for debugging as we lose many lines, so to turn it off run
Code:
adb logcat -P ""
right at boot
Since we're having so many issues with mobile network/wifi/bluetooth, I'm wondering if our netfilter code in the kernel isn't working properly.... The thing against this theory is that things work on my variant.
Hi,
Somehow I managed to forget my screenlock pattern (freshly changed) on my OnePlus 5T and it seems like my enrolled fingerprints are useless now. I need some help to recover access to my phone (preferably without factory reset).
This is the current situation of my phone:
- Phone Rooted
- TWRP Custom Recovery
- USB Debugging enabled
- WiFi On/Data and GPS OFF
- Currently logged in with my google account on the phone, but can't access it over the google account (i kind of disabled history and other features in my google acc).
- Also "Unknown Sources" is enabled on my phone.
If there is any way to recover the password via ADB, or to unlock the Data, that would be just awesome...
Thanks for any help.
derei said:
Hi,
Somehow I managed to forget my screenlock pattern (freshly changed) on my OnePlus 5T and it seems like my enrolled fingerprints are useless now. I need some help to recover access to my phone (preferably without factory reset).
This is the current situation of my phone:
- Phone Rooted
- TWRP Custom Recovery
- USB Debugging enabled
- WiFi On/Data and GPS OFF
- Currently logged in with my google account on the phone, but can't access it over the google account (i kind of disabled history and other features in my google acc).
- Also "Unknown Sources" is enabled on my phone.
If there is any way to recover the password via ADB, or to unlock the Data, that would be just awesome...
Thanks for any help.
Click to expand...
Click to collapse
Hey Bud,
I had a similar issue when I restored a nandroid backup and the password had been glitched so that I couldn't sign into my phone anymore.
Anyways here's a shortened version of a solution I found here: https://forums.oneplus.com/threads/fix-wrong-pin-pattern-when-restoring-twrp-nandroid-backup.452384/
1. Boot into TWRP
2. Open the file manager inside of TWRP and delete (or rename - they get restored whenever the phone is booted so deleting them does no harm) the following files inside "/data/system":
-password.key
-pattern.key
-locksettings.db-wal
-locksettings.db-shm
-locksettings.db
(they might not all be there but whichever ones you can find, delete/rename)
3. Reboot your phone and you should no longer have any kind of pin/pattern on your lockscreen
4. Re-setup your password and don't forget it this time!
Hope this helps :good:
BenisMusical said:
Hey Bud,
I had a similar issue when I restored a nandroid backup and the password had been glitched so that I couldn't sign into my phone anymore.
Anyways here's a shortened version of a solution I found here: https://forums.oneplus.com/threads/fix-wrong-pin-pattern-when-restoring-twrp-nandroid-backup.452384/
1. Boot into TWRP
2. Open the file manager inside of TWRP and delete (or rename - they get restored whenever the phone is booted so deleting them does no harm) the following files inside "/data/system":
-password.key
-pattern.key
-locksettings.db-wal
-locksettings.db-shm
-locksettings.db
(they might not all be there but whichever ones you can find, delete/rename)
3. Reboot your phone and you should no longer have any kind of pin/pattern on your lockscreen
4. Re-setup your password and don't forget it this time!
Hope this helps :good:
Click to expand...
Click to collapse
Hi, thanks.
I've been checking that post, but something didn't quite match. The following files are available on my phone ( /data/system):
-gatekeeper.password.key
-gatekeeper.pattern.key
-locksettings.db-shm
-locksettings.db
-locksettings.db-wal
So, as you can see, there are two files with the "gatekeeper" prefix. Are those two supposed to be also deleted (renamed)? Did you have them when you did your fix?
Thanks.
derei said:
Hi, thanks.
I've been checking that post, but something didn't quite match. The following files are available on my phone ( /data/system):
-gatekeeper.password.key
-gatekeeper.pattern.key
-locksettings.db-shm
-locksettings.db
-locksettings.db-wal
So, as you can see, there are two files with the "gatekeeper" prefix. Are those two supposed to be also deleted (renamed)? Did you have them when you did your fix?
Thanks.
Click to expand...
Click to collapse
Hey man,
When I fixed my issue I didn't touch those - worst comes to worst just rename the files that were on the list I gave and leave the other 2. If it doesn't work then you can try renaming the files you found from my list as well as the two you have highlighted in red.
Give that a try
BenisMusical said:
Hope this helps :good:
Click to expand...
Click to collapse
Just did the steps (including the gatekeeper. prefixed files) - I just renamed them, so I can revert back. Indeed I was able to get my phone unlocked, but everything is blank. Only a wallpaper, status bar and Nav Bar. No apps, no app drawer, nothing. I can access the Settings, but that doesn't help much... (except that I can set a new password).
Going in Settings -> Apps, shows me all the apps, which is good. But I can't see them on screen.
Also, the following are happening:
- Settings -> Apps -> Defaults: Nothing set up for "Home App". And there is a blank grey menu when I click on it.
- Settings -> Apps -> Application List -> OnePlus Launcher: clicking on Open By Default, crashes the Settings Menu.
Is it possible that I did something wrong here?
derei said:
Just did the steps (including the gatekeeper. prefixed files) - I just renamed them, so I can revert back. Indeed I was able to get my phone unlocked, but everything is blank. Only a wallpaper, status bar and Nav Bar. No apps, no app drawer, nothing. I can access the Settings, but that doesn't help much... (except that I can set a new password).
Going in Settings -> Apps, shows me all the apps, which is good. But I can't see them on screen.
Also, the following are happening:
- Settings -> Apps -> Defaults: Nothing set up for "Home App". And there is a blank grey menu when I click on it.
- Settings -> Apps -> Application List -> OnePlus Launcher: clicking on Open By Default, crashes the Settings Menu.
Is it possible that I did something wrong here?
Click to expand...
Click to collapse
Possibly?
When I followed the method in the link in my previous post I had no issues - I just had to setup a new lock method.
It may have been the gatekeeper files - when I did this method previously I didn't touch those as I didn't know they were there
Do you have a backup from TWRP by any chance that you could restore?
BenisMusical said:
Possibly?
When I followed the method in the link in my previous post I had no issues - I just had to setup a new lock method.
It may have been the gatekeeper files - when I did this method previously I didn't touch those as I didn't know they were there
Do you have a backup from TWRP by any chance that you could restore?
Click to expand...
Click to collapse
Restored the gatekeeper files, but no success. Same behaviour. I have a backup, but is only a "initial backup" - sort of how the phone was at first. I was too dumb to do a backup after I set up everything.
It seems my only way now would be to do a factory reset and lose all data.
Unless there would be a way to recover the password from the database? I know is encrypted and salted, but that salt also has to be stored somewhere... maybe there would be a way to revert that hash into a pattern? grr, this is extremely frustrating.
derei said:
Restored the gatekeeper files, but no success. Same behaviour. I have a backup, but is only a "initial backup" - sort of how the phone was at first. I was too dumb to do a backup after I set up everything.
It seems my only way now would be to do a factory reset and lose all data.
Unless there would be a way to recover the password from the database? I know is encrypted and salted, but that salt also has to be stored somewhere... maybe there would be a way to revert that hash into a pattern? grr, this is extremely frustrating.
Click to expand...
Click to collapse
I apologise for possibly making matters worse whilst trying to help but this is beyond my understanding of TWRP's capabilities
It might be worth restoring your previous backup even if it is blank and then setting up your phone again. During the setup choose an option that should be something like: "Restore from the cloud" which will allow google to restore most of your app data. However, your internal storage will be completely wiped . Once that's all good and setup then definitely make a backup - it's a good habit to get into and will save you a lot of hassle in future.
I don't know if there's anything else I can suggest you to do,
hope this doesn't take up too much time - I personally know how infuriating it is to spend hours on something when there's no easy solution. You'd be better starting from a clean flash of OOS.
Sorry, there's nothing else I can think of to help you out
Best of luck bud.
BenisMusical said:
Sorry, there's nothing else I can think of to help you out
Best of luck bud.
Click to expand...
Click to collapse
I'm grateful for your effort. It offered a solution. It just got more complicated than expected. Probably the last Oxygen update patched some security issues - which is not bad after all (it's just bad for me NOW).
Personal data is encrypted with the screen lock pattern, so your only choice is a factory reset