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/
Related
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
Hello all, I've come with an interesting problem.
I've recently purchased the incredibly cheap TracFone ZTE Z233, running "3.10.49-gdac61ef-00512-ge30dd04 zte-kerne;@Zdroid-SMT" and have decided to try and root it. After having gone through conventional methods, I would like to ask for your guys's input. I started by attempting the traditional methods, specifically downloading and attempting to run KingRoot.apk on the phone. The resulting message, "Cannot find an app to open this file" sent me to find the google play store. Upon the discovery that there was no google play store, I downloaded and ran the windows version of KingRoot on my PC after connecting the phone. Unfortunately, even though my PC recognized the device and was able to move files on and off of it, KingRoot could not find the phone.
{
"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"
}
Next, I tried to step through the directions Kingroot gave for enabling USB debugging as you can see in the second image. Unfortunately, I parsed through every single setting in the settings menu of the Z233, and no USB debugging option exists on this device. Upon discovering this, I attempted to find other means of rooting ZTE devices and discovered https://forum.xda-developers.com/showthread.php?t=1319257&page=1 was quite popular. However, this method also requires USB debugging. I won't bore you with the five or six other methods I tried, the issue always boiled down to the solution requiring a feature this phone did not have. The point is, as far as I can tell, there is no way to root this phone by conventional means.
I don't absolutely need to root this, (I bought it as a burner phone) but now I'm interested in rooting it as a project. I'm genuinely curious as to whether or not it can be done. I was hoping you guys would have some leads. I'm not afraid to get my hands dirty or do stuff that would risk bricking the phone (like I said, it was cheap.)
Any thoughts, questions or leads? Thanks!
I have ZTE Cymbal Z-320, which is quite similar to this. I can reach USB debug only in FTM mode (when phone is off, PWR ON + VOL DOWN and you in). Root apps are founding phone, tryying to root, but can't. It running android 5.1.1, read more https://androidforums.com/threads/zte-cymbal-z320-root-hack.1290564/
Hello
I am complete new to the "custom ROM for mobile phones" business.
But i am familiar with Linux based Satellite Receivers where you
also can flash custom ROMS to enhance the functionality.
Or in other words - i know what bricked means.
Anyway what i have done so far:
I have an unlocked Bootloader on my Mi A3.
1st time (non permanent) flash of TWRP-3.3.1-2 into recovery for
a full backup of my phone to Sd-Card.
An encounter with Bootloop made
Now i want to make TWRP permament on both partitions.
But, after flashing TWRP into recovery again, i recognizing that
the "Unmodified System Partition" screen is not apearing anymore.
After my 1st twrp flash, twrp showed me a screen where something
about "Keep System Read only" was explained.
With a slider "Swipe to Allow Modifications".
This screen is not more apearing anymore.
Is this mandatory to go on ?
My goal is to have twrp, magisk and lineageos on my phone.
Last but not least i want to say:
A fantastic source of informations here but overwhelming btw. *g*
* Edit *
32 Views but no answers this could mean that my concern is not clear ?
After entering to twrp on my phone for the first time i saw this screen here
{
"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"
}
As i explained above, i only wanted to make a backup from my phone
as a fallback if something goes wrong afterwards.
Due to this i pressed ´Keep Read Only´
Don´t know if the ´Never show this...´ was flaged
My thoughts was:
Keep Read Only is okay for now/backup.
And if necessary i can Swipe for modification next time.
My concern is the screen will not showing again.
In case of i HAVE to swipe to make modifications for the next steps,
what i have to do now that this screen will show up again
that i can make the f*ckn swipe ? :angel:
Thank you
Open twrp, goto mount, there's an option for mount read-only system.
m.h.mahadi said:
Open twrp, goto mount, there's an option for mount read-only system.
Click to expand...
Click to collapse
Thank you.
Hi,
using the Hisense A5. A family member was using the phone and put in a passcode that they forgot.
I am unable to get far enough into the phone to enable USB Debugging.
I am able to get the phone into recovery mode (using power-on, volume down). which is the "Vision" recovery system.
{
"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"
}
I cannot speak or read simplified chinese. Because the Hisense A5 has an eInk screen, I was able to scan the screens and upload it to an OCR site that could convert the image into characters. Then I could use google translate.
Anyway. I chose the first option which is "Recovery".
The screen I get is the following.
Using google translate. I can make out that the first choice is "Reboot", second choice is "Delete user data" and the third choice is "Update system".
I have tried the "Delete user data", and I can seem to make it work. But after the phone reboots, the passcode is still there.
The only other possibility I have is the third option which is "Update System". If I choose that I get the following option.
As you can see, the only thing I am able to do is to get the recovery system to to somehow load the file "update.zip".
I have tried the commercial passcode remover iMyPhone, but it didn't work.
If someone had some ideas, I would really appreaciate them. I am very much stuck right now.
If you don't mind losing data then you can simply reflash your device.
Download the actual chinese Firmware from here
https://forum.xda-developers.com/showpost.php?p=82583733&postcount=28
Follow this guide to re-flash the downloaded Firmware from a microSD
https://forum.xda-developers.com/showpost.php?p=82575517&postcount=21
Hi JLowe, a very big thank you.
I was able to download the firmware. (Took a few attempts, but I got there in the end), and have it installed.
Right now, I'm trying to work out how to put the phone into debugging and put on some other ROMS. Similar to what others have done.
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"
}