Hello, I've never gone beyond entering developer mode on any of my phones, looking around carefully, then turning that mode off. I own two PH-1 phones, one is in full time service, and I would like to know of a tutorial / step-by-step to do what I need to do to maintain this phone with the images (ROMs?) that are being maintained and updated. I don't need the phone to do anything other-worldly, just keep it updated.
This is the only forum on here I'm allowed to post to, because I've been a listen-only member for a couple years but have never posted. I've just started using Ubunto 20.04 on a new laptop so I can get away from Windows, but I still have a Win7Pro laptop.
Thanks for your recommendations on how to get started -- safely started -- and how to learn what I need to learn.
Also, I just read some of the read-me-first stickys, and please allow this to also be my "Say Hi" email...
"MP"
PS -- I get a captcha, check it, get the green checkmark, but I see *no* image... I'm using firefox w/ NoScript (all scripts enabled for this tab), on an Ubuntu 20.04 laptop.
So no one cares to reply? Did anyone read it besides myself? Whiskeytangofoxtrot
@Messypotamia
If phone's Android OS isn't an A/B-partition-layout-system - what I believe because its Stock ROM is Android 7.1. - then updating a phone's Android requires phone's boot-loader is unlocked. This must get enabled within phone's Developer options - keyword: OEM unlock - what simply sets phone's unlock ability flag to 1 . Additionally it's necessary that ADB ( read: Android Debug Bridge ) gets enabled in phone's Developer options - keyword: USB debugging.
{
"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"
}
Related
Hello
I would like my Android device encrypted, as it contains sensitive data. I'm currently on cm-9.0.0-rc1-tinystream-hephappy-p500 (RC1-Rev.B). Now, here is what happened:
- To encrypt internal
I went to Security in System Settings and touched "Encrypt Device". It gave some confirmations and I've accepted them however, now I'm kind of stuck on this screen.
{
"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"
}
My first thought was "it is encrypting". But after hours of waiting, I wanted to check if it's done already. So I clicked the power-button once (just to unlock) and it asked for my password. I've entered it and it just went into my normal launcher. I've checked if anything had changed and no, my device has not been encrypted. Any logs somewhere? Any ideas what could have caused the problem?
- To encrypt SDcard
I did some research and didn't find something perfectly for my needs. Anyone has any idea on how to encrypt an SD card to properly work together with Android?
Note: I am using LINK2SD.
Thanks for your help
Another question that actually has nothing to do with my previous post that I post here because it's not worth a new thread: every time I plug in my phone into the charger, it boots automaticly. I don't want that, my previous build of CM9 did just recharge without booting, something I prefer. Any way to configure that?
Another question I want to add to the this thread: is it possible to combine a password lock and a slide lockscreen? Like when I encrypt the phone to enter a password to decrypt it again and then just use the normal slide lockscreen to unlock it each time after the decryption?
One last question: is there any way to encrypt the SQL database in Android? As it contains sensitive data... I've read something about SQLCipher but it doesn't get to work (any help would be appreciated).
Thread can be removed. Problems already solved. Discussion about security here: http://forum.xda-developers.com/showthread.php?t=1790964
And for the charging problem: http://forum.xda-developers.com/showpost.php?p=29217540&postcount=1787
Hi, i am new to the xda developers forum and i got a question about the android debugger, since i'm clueless what to do after several hours of searching :silly:
I have an Sony Tablet S with ICS version 4.0.3.r1a (not rooted) and i want to use it for app developing.
Sadly sony does not provide drivers out of the box, so i have to search for working drivers myself. I know, they provide a description of lines, you have to add to the google driver, and i have tried two different methods to get adb working, but my devices still does not show up in the adb devices list.
method 1 (automated driver installer): http://forum.xda-developers.com/showthread.php?t=1488822
method 2 (google driver modification): http://esupport.sony.com/US/p/suppo...=684a6e492d1523ff4081def0a00b48a1&info_id=878
The device seems to use the driver, since it shows up as Android Composite ADB Interface in the devmgmt, but it still does not show up in the adb devices list.
Here some Facts about my os and settings:
My PC:
OS: Win7 ultimate x64
adb-version: 1.0.29
google usb-driver version: 7.0.0.1
My Tablet:
Android-Version: ICS 4.0.3.r1a
USB-Debugging is enabled
Other sources for apps are allowed
here some pictures of my file contents & devices:
{
"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"
}
My head is smoking atm, so i hope you know more about drivers and adb as i do and maybe someone of you had the same problem and can help me, i would be really greatful.
So long,
r3bel
Finally i found a solution of my problem...
As simple as it was, i could kick myself ... the driver seems to have a problem with my usb 3.0 controller, the adb finds the device if it is plugged into a usb 2.0 port.
maybe this helps others who have the same problem
I had same problem (it was working before) and I did system restore to get it to work.
Then I could able to root my tablet.
How did you solve the usb problem?
Hey,
I recently got a cheap, slightly used chinese version Nokia N1. But because without the Google Services its pretty much useless to me, I want to root it and install a custom ROM.
I followed 2 tutorials:
https://forum.xda-developers.com/nokia-n1/help/nokia-n1-root-t3125771
and
https://forum.xda-developers.com/nokia-n1/general/play-store-howto-t3118965
But I always get stuck on the part with the Recovery Launcher.
{
"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"
}
To give some background, here are the steps I did:
Because fastboot and the launcher won't see my device if its in MTP or PTP, I disabled both. That seems to work fine.
I "unlocked" oem in the developer settings and also allowed USB debugging.
I started the Recovery Launcher with admin privileges and used option T4.
It boots into recovery mode, but I just get errors all over the place bacause the device is still locked. So i just typed "fastboot oem unlock". Then T4 again.
Thats where this error occurs. From what I read, this should put me into a CWM recovery session. But it doesn't. It just stays in the fastboot mode window.
I'm pretty new to this android modding thing, so don't expect to much knowledge from me.
with much thanks
~David
Bump
I really hope bumps are allowed here
its seems from ur bootloader, try to re unlock with fastboot unlock oem. if you done try different recovery developed for ur devices.
nuzzydev said:
its seems from ur bootloader, try to re unlock with fastboot unlock oem. if you done try different recovery developed for ur devices.
Click to expand...
Click to collapse
The thing is, there are no other solutions out there I really know about. I searched google up and down and got no real result.
I think my problem is that my android version isn't 5.0.x, like almost every english tutorial suggests. It is 5.1.1.
oh God... my fault sorry
Hey all!
I have a Light Phone 2 which uses Android 8.1. It's a neat little device that I'd love to tinker with. There is a detailed guide explaining the build process ontop of Android 8.1. The TL;DR is the Light Phone uses LightOS which is another word for an app that site on Android 8.1 that has lower-level access, similar to how the settings app works.
There is a medium post outlining the build process entitled Building LightOS with React Native. I cannot link to it as I do not qualify for the 10 post minimum. So you'll have to google it.
I can get to the Android recovery screen. Although from there I can't do anything. As adb is locked to only sideload and mounting the system produces no results on my Linux machine.
I realize very few people have this device and can comment from experience but does anyone have any idea how to go about rooting this phone? Or getting it to a state to begin tinkering?
Thanks!
@kennethashley
Before starting to try to root phone's Android test whether you can enable these 2 options in Android's Settings -> Developer options:
{
"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"
}
If YES then you have to find a Custom Recovery matching your device what is prerequisite to flash any Rooting software.
jwoegerbauer said:
@kennethashley
Before starting to try to root phone's Android test whether you can enable these 2 options in Android's Settings -> Developer options:
If YES then you have to find a Custom Recovery matching your device what is prerequisite to flash any Rooting software.
Click to expand...
Click to collapse
Unfortunately, that is the thing, the phone does not have these settings available. I was hoping there would be a way to do this directly from the recovery menu
@kennethashley You can access the recovery menu by power and volume up at the same time. When you reach the screen that says "no command" press power first, then volume up, then quickly release volume up first then power. There, you should be able to put the phone into recovery mode.
you can then put the phone into fastboot mode and use adb tooling to enable oem unlocking so you can root the device.
This dude did it on reddit: reddit.com/r/LightPhone/comments/jqtfu4/heres_how_to_get_a_shell_on_the_lightphone2_and/
Well, it's a bit of a long story, so I'll try to be as short as possible.
Last year, and after hours of searching on the internet, I found the solution for "Custom binary blocked by frp lock" on this forum (here and here). Both methods promised to fix the lock without erasing my data, but I decided to try the second one (it consists of reinstalling only the boot image with Odin).
Fortunately it worked for me on the first try, and since this method was not well known on the internet, I decided to make a video tutorial to help those who had the same problem and wanted to keep their data.
The fact is that, unfortunately, this method didn't work for everyone, and in many cases it generated bootloops or black screens of death.
And my question is: does anyone know what could be the cause of this?
I tested it on SM-J710MN and SM-G532M, both running Android Marshmallow, and the bootloops/black screens occurred on devices running Android 6, 7, 8 and (I guess) 9 and 10.
Starting with Android 6 FRP on any such Android device is automatically enabled once a Google account is logged in to a device. The only way to get rid of it is by removing the account from the device into which it has been synced.
jwoegerbauer said:
Starting with Android 6 FRP on any such Android device is automatically enabled once a Google account is logged in to a device. The only way to get rid of it is by removing the account from the device into which it has been synced.
Click to expand...
Click to collapse
Thanks for answering.
Maybe I did not express myself in the correct way, but actually I was referring to the block that does not even allow to boot the device and only shows words in red, as seen in this image.
{
"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"
}
But beyond that my question is about why does the bootloop or black screen happen after flashing the boot.img file? Does it have to do with a different/incompatible version of Android/binary/csc or something like that?