First post so I apologise if I'm posting in the wrong area. I have a rooted ulefone power 3s and having a strange overlay on my screen. It's in red and is located top right of the screen but isn't present on lock screen and when reboot is performed the writing takes roughly a minute to appear. The writing reads:
未写入key
I've tried translating it but cannot find anything at all for what it might be. I'm running on 7.1.1 both IMEI are present and correct and phone works fine other than this issue. It appeared after I flashed my rom (official ROM from ulefone website). All my data was wiped and I lost my IMEI etc I've managed to sort IMEI but really struggling with what this writing is any help at all would be muchly appreciated.
Google translate says "not written key" - which is not really explaining too much.
You can go step by step to isolate the root cause of the message like:
- Shutdown the phone and remove all SIM cards and external SD cards
- Start up the phone and see, if the message is still there.
- When exactly does the message appear? ....and so on.
Anyhow - this will probably not fix the issue.
I would restore the original ROM or (even better) download the Oreo ROM from the Ulefone download area:
It's available in the download area for this phone
Good luck!
ulefone power 3s display problem after flash
I have a problem with the display. I see everything double.
It seems that 2 roms play at the same time or that there's a problem with the calibration or the driver of the display.
PLEASE HELP ME
Carlo0082 said:
I have a problem with the display. I see everything double.
It seems that 2 roms play at the same time or that there's a problem with the calibration or the driver of the display.
PLEASE HELP ME
Click to expand...
Click to collapse
Plz I have d same problem too here how did u solve yours
Make full backup data personal files and then flash the stock rom from ulefone https://drive.google.com/drive/folders/11CPEvL8OFJvK9Tbgr0eWYYX_4FMeu_yY
if problem persist you must sent it to a technician to see it......
Carlo0082 said:
I have a problem with the display. I see everything double.
It seems that 2 roms play at the same time or that there's a problem with the calibration or the driver of the display.
PLEASE HELP ME
Click to expand...
Click to collapse
alumi4skop said:
Plz I have d same problem too here how did u solve yours
Click to expand...
Click to collapse
I had the same issue.
The setup is possible with this screen problem, so just do it and then you get a notification about a new OTA Update.
Go ahead and install this, it will fix the screen, but you end up having the same red overlay with the chineese writing.
I found out how to ged rid of the red overlay!!!
It's a service called "sdrpmbFloat view service"
Killing it via developer options -> active services hides the overlay.
So if you have root, you can simply disable this service, or be able to uninstall the app behind this service.
m4rkj4y said:
First post so I apologise if I'm posting in the wrong area. I have a rooted ulefone power 3s and having a strange overlay on my screen. It's in red and is located top right of the screen but isn't present on lock screen and when reboot is performed the writing takes roughly a minute to appear. The writing reads:
未写入key
I've tried translating it but cannot find anything at all for what it might be. I'm running on 7.1.1 both IMEI are present and correct and phone works fine other than this issue. It appeared after I flashed my rom (official ROM from ulefone website). All my data was wiped and I lost my IMEI etc I've managed to sort IMEI but really struggling with what this writing is any help at all would be muchly appreciated.
Click to expand...
Click to collapse
Hello,
i found 3 ways so far to remove it:
1. Killing the "sdrpmbFloat view service" (overlay will be gone since next reboot)
2. Disable permision to show over other apps for Factory Mode:
Settings --> Apps -> 3 dot menu, Show system --> Scroll down to Factory Mode and select it --> scroll down to advanced section on bottom --> select "Draw over other apps" and switch it off.
3. With root, uninstall Factory Mode app
APP PAROU
Acabei de comprar meu Ulefone Power 3S, mas ele fica parando os aplicativos do android: "Google Play Services parou ou "Google Play Services isn't responding" e logo em seguida reinicia sozinho. Não dá para mexer. alguém sabe por que isso acontece?
Delete package
This method worked for me to get rid of the 未写入 tee key message. With adb platform tools use this command line :
adb shell pm uninstall -k --user 0 com.mediatek.factorymode
It deleted the factory mode package and stopped displaying the message.
not Turn on
I was using it normally when I turned the screen off and when I put the fingerprint it did not turn on.
Does anyone know what can it be? I'm suspecting the battery.:Boa:
syltess2009 said:
This method worked for me to get rid of the 未写入 tee key message. With adb platform tools use this command line :
adb shell pm uninstall -k --user 0 com.mediatek.factorymode
It deleted the factory mode package and stopped displaying the message.
Click to expand...
Click to collapse
IT WORKS!!! thank you
joern_h said:
Hello,
i found 3 ways so far to remove it:
1. Killing the "sdrpmbFloat view service" (overlay will be gone since next reboot)
2. Disable permision to show over other apps for Factory Mode:
Settings --> Apps -> 3 dot menu, Show system --> Scroll down to Factory Mode and select it --> scroll down to advanced section on bottom --> select "Draw over other apps" and switch it off.
3. With root, uninstall Factory Mode app
Click to expand...
Click to collapse
A simple way that works for me was restaring the device in Safe mode (hold power botton, when te options of shut down and restart appear on the screen
press the shut down botton on the screen then you going to see a dialog and confirm to reboot to safe mode) in ideveloper options disable: Enable view atrribute inspetion, reboot and its done! :angel:
joern_h said:
Hello,
i found 3 ways so far to remove it:
1. Killing the "sdrpmbFloat view service" (overlay will be gone since next reboot)
2. Disable permision to show over other apps for Factory Mode:
Settings --> Apps -> 3 dot menu, Show system --> Scroll down to Factory Mode and select it --> scroll down to advanced section on bottom --> select "Draw over other apps" and switch it off.
3. With root, uninstall Factory Mode app
Click to expand...
Click to collapse
4. Option is to deinstall the Factory Mode App using ADB/SDK Tools with PC but Without ROOT
All you need to do is Download this: www,mediafire,com/file/cc443705xa3e6mg/minimal_adb_fastboot_v1.3.1_setup_2.rar (remove the comm between www,mediafire,com and set points instead for the commas....... because new account and i cant write links)
U must enable USB-Debugging on your Ulefone Power 3/3s. (no matter which Android version)
Connect your Smartphone with your PC using USB Cable.
Then start the Program you downloaded before.
Maybe you Have to Confirm the Debugging on your Smartphone.
1. Type into the Console:
adb devices
Something like this should pop off:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
0123456789ABCDEF device
2. Type into Console:
adb shell
Something like this should pop off:
Power_3S:/ $
3. Type Into Console:
pm list packages
{
"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"
}
All the Packages you Have installed should Pop off.
4. type Into Console:
pm uninstall --user 0 com.mediatek.factorymode
"Success" should Pop Off
If this Worked you Restart your Phone and The Red 未写入key or 未写入tee key should be away 4 ever.
I hope it Works and sorry 4 my bad English.
Greetings from Germany
m4rkj4y said:
First post so I apologise if I'm posting in the wrong area. I have a rooted ulefone power 3s and having a strange overlay on my screen. It's in red and is located top right of the screen but isn't present on lock screen and when reboot is performed the writing takes roughly a minute to appear. The writing reads:
未写入key
I've tried translating it but cannot find anything at all for what it might be. I'm running on 7.1.1 both IMEI are present and correct and phone works fine other than this issue. It appeared after I flashed my rom (official ROM from ulefone website). All my data was wiped and I lost my IMEI etc I've managed to sort IMEI but really struggling with what this writing is any help at all would be muchly appreciated.
Click to expand...
Click to collapse
I dunno if is the same thing but I got the same message when I updated my Power 3S to Oreo... so I used an ADB command and removed that message. You may try it if you want, but I can't guarantee that it will work for you... or anything but do it at your own risk: adb shell pm uninstall -k --user 0 com.mediatek.factorymode
King !!!! thanks a lot, i have been searching for this for more than 2 months!!!
method 2 worked perfectly for me, thanks again !
I remember I have rooted Ulefone power 3s with Android 7 a year ago.
Now I have Ulefone power3s with Android 8 and I cannot
I go to fastboot (power + volume up and from the mini menu 2nd option) mode and make:
Of course before was programming mode, debug mode, can unlock and unlock by fastboot command, restart, then:
c:\zuk\adb-fastboot-tool-2016\fastboot.exe flash recovery c:\zuk\power3\recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (17836 KB)...
OKAY [ 5.469s]
writing 'recovery'...
OKAY [ 0.266s]
finished. total time: 5.734s
With or without (I have tried both)
c:\zuk\power3\platform-tools\fastboot.exe boot c:\zuk\power3\2\recovery.img
downloading 'boot.img'...
OKAY [ 5.484s]
booting...
OKAY [ 0.078s]
finished. total time: 5.562s
and then if it restart by this command fastboot boot... or without it I can restart by volume up + power or by volume down+power
Any combination goes eventually to Chinese recovery with Chinese letters!
What the hell is going on and why simply fastboot boot recovery.img doesn't work as should work ?
=
My only recovery is like this Samsung
I have never had like this, NEVER:
If you got the same menu after flashing, that means that the root files are not for your phone model or android version.
bejjaniabdo said:
If you got the same menu after flashing, that means that the root files are not for your phone model or android version.
Click to expand...
Click to collapse
I have power 3s and I have tried 3 different recovery.img's from www pages which all were for Ulefone power 3s.
And why the flash has NO error and send/ok message is on terminal during fastboot flash-ing
juyer said:
I have power 3s and I have tried 3 different recovery.img's from www pages which all were for Ulefone power 3s.
And why the flash has NO error and send/ok message is on terminal during fastboot flash-ing
Click to expand...
Click to collapse
Try to fuse Super SU application to grant root, use applications instead of ADB or TWRP methods
Related
Well since its easy to take screenshots on rooted device, non rooted, stock and others find it a bit difficult...
There are few ways to do it:
1. Unlock your device, flash recovery, flash rom(in my case cm7.2 which has built in function when long pressing power button to choose to screenshot it) and install some screenshot app.(there are many free on market)
2. You can do it by using No Root Screenshot It(tested) or Screen Capture -No Rooting 2.2(not tested).
3. By using Android SDK and DDMS
Here is how to:
First you will need your device drivers, if not rooted its done by installing HTC Sync.
Second you will need Android SDK, and you will find it here, it will also ask you to install JDK (Java Development Kit), if you dont have it download it here
Third go to your device, menu/settings/applications/development/usb debugging and tick it.
Fourth, go to your install location(usually c:/program files/android/android-sdk-windows or something like that) and there you will find ddms, open it.
Now connect your device, and in left side of ddms it will appear.
Double click on your device, and there you will see your screen and can refresh, save, rotate and so on ...
UPDATE:
So I tried this one when running custom recovery (cwm tested)
It is the same process as above, you just do a reboot into recovery, or restart your phone, when restarting your phone will loose connection to ddms, but wait a bit since as soon as it opens recovery, your phone will be open inside ddms and you will be again able to capture screens...This is i guess usefull if you want to show someone how to do something into recovery...
{
"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"
}
Screenshots are from ClockWork Mod Recovery v5.0.2.8 which i flashed on top of alquez's cwm v5.0.2.6 via Root Manager
Screenshot number one : Install zip from SD Card (used for flashing new rom or any other flashable zip)
Screenshot number two: CyanogenMod Boot Animation
Screenshot number three: Wiping Cache(which is selected from the main menu-see 1st screenshot option 4)
Screenshot number four: Wiping Data/Factory reset(selected from the main menu option 3)
Screenshot number five: Advanced menu (main menu option 8) where you can wipe dalvik, and of course all other options seen up on ss.
Screenshot number six: Nandroid backup and restore (main menu option 6)
Ok it's working with me .. but once i restart the phone to get into the CWM the DDM list the phone as unknown and i can't take any screenshot .. so is theres something i miss here?
the full path you're looking for is: c:\Program Files (x86)\Android\android-sdk-windows\tools\ddms.bat
D3VI0US said:
Ok it's working with me .. but once i restart the phone to get into the CWM the DDM list the phone as unknown and i can't take any screenshot .. so is theres something i miss here?
Click to expand...
Click to collapse
When you restart, wait to find your phone... Then open ddms? It should be there...
Sent from my GT-I9001 using xda premium
thanks bro, im going to use this to show my noob question
D3VI0US said:
Ok it's working with me .. but once i restart the phone to get into the CWM the DDM list the phone as unknown and i can't take any screenshot .. so is theres something i miss here?
Click to expand...
Click to collapse
I suffer from this problem too,
I'd like to take screenshots of my device in CWM for a guide, but it doesn't want to show the screen in ddms, it lists it as 'unknown' and shows 'screen not available'
More info:
ASUS Eee Pad Transformer Tf101
Rouge XM Touch Recovery V1.5 (Same as Xoom)
Full normal adb access in recovery.
Thanks,
ToD
We GALAXY S2 users are lucky that Screenshot feature comes built-in with phone.
Just by holding "Home key" and "Power Key" for around 2 seconds takes the Screenshot.
Sent from my GT-i9100 equipped with Grenade Launcher and Remote Explosives
DD-Ripper said:
We GALAXY S2 users are lucky that Screenshot feature comes built-in with phone.
Just by holding "Home key" and "Power Key" for around 2 seconds takes the Screenshot.
Sent from my GT-i9100 equipped with Grenade Launcher and Remote Explosives
Click to expand...
Click to collapse
well, on i9001 also, with back button and home button we take screens, BUT it doesnt work in recovery... thats the point =)
Thing O Doom said:
I suffer from this problem too,
I'd like to take screenshots of my device in CWM for a guide, but it doesn't want to show the screen in ddms, it lists it as 'unknown' and shows 'screen not available'
More info:
ASUS Eee Pad Transformer Tf101
Rouge XM Touch Recovery V1.5 (Same as Xoom)
Full normal adb access in recovery.
Thanks,
ToD
Click to expand...
Click to collapse
some drivers from your transformer are not installed on computer, try somewhere else or reinstall drivers... sorry for late answer...
I have the problem too. In CWM 6.0.1.2 my Samsung Galaxy Tab 2 (CM10) doesn't want to show the screen capture in DDMS. At the monitor the device appears as a number. As unknown status. Taking a screenshot is not possible. I can select the Screenshot function, but there is no picture...
No theres a easy way !
Go to play store and find the App Screenshot and Draw it works without root just download the .bat file and run it on your pc and open the apk on your phone and you will be able to take screenshots !
sakibhasaN said:
Go to play store and find the App Screenshot and Draw it works without root just download the .bat file and run it on your pc and open the apk on your phone and you will be able to take screenshots !
Click to expand...
Click to collapse
But how should this help to make screenshots of CWM?
Has anyone already made screenshots in BMM with the XT910?
Taking frame buffer screenshots
Egooktamuck said:
I have the problem too. In CWM 6.0.1.2 my Samsung Galaxy Tab 2 (CM10) doesn't want to show the screen capture in DDMS. At the monitor the device appears as a number. As unknown status. Taking a screenshot is not possible. I can select the Screenshot function, but there is no picture...
Click to expand...
Click to collapse
You can take screenshots with adb copying the frame buffer:
Code:
adb pull /dev/graphics/fb0 fb0.raw
The image (in recovery mode) is in the format RGB 5:6:5 (5 bits red, 6 bits green, 5 bits blue). Open it with IrfanView as raw image 16 BPP 5:6:5, with you device dimension (mine is 240 x 400 pixels, chinese MT6516) and save it in any other format.
See more valuable information: imajeenyus.com/computer/20130301_android_tablet/android/taking_screenshots . h t m l
meiradarocha said:
You can take screenshots with adb copying the frame buffer:
Code:
adb pull /dev/graphics/fb0 fb0.raw
The image (in recovery mode) is in the format RGB 5:6:5 (5 bits red, 6 bits green, 5 bits blue). Open it with IrfanView as raw image 16 BPP 5:6:5, with you device dimension (mine is 240 x 400 pixels, chinese MT6516) and save it in any other format.
See more valuable information: imajeenyus.com/computer/20130301_android_tablet/android/taking_screenshots . h t m l
Click to expand...
Click to collapse
It worked!!! Thanks. :good:
meiradarocha said:
You can take screenshots with adb copying the frame buffer:
Code:
adb pull /dev/graphics/fb0 fb0.raw
The image (in recovery mode) is in the format RGB 5:6:5 (5 bits red, 6 bits green, 5 bits blue). Open it with IrfanView as raw image 16 BPP 5:6:5, with you device dimension (mine is 240 x 400 pixels, chinese MT6516) and save it in any other format.
See more valuable information: imajeenyus.com/computer/20130301_android_tablet/android/taking_screenshots . h t m l
Click to expand...
Click to collapse
That settings didn't work for me, instead had to use the ones specified in the website:
32 BPP, File header size 3, color order BGR. Have a Galaxy S2.
Android: Taking screenshots
Thanks, this was very useful.
Hi, in recovery i have this output:
Code:
adb pull /dev/graphics/fb0 fb0.raw
error: device unauthorized. Please check the confirmation dialog on your device.
I have an xperia m whith cyanogenmod 11 and cwm v6.0.5.1
what can i do?
thanks
Hey guys! Today is a big day for Alcatel 1 owners, since the root is possible. Follow my steps to root your device!
NOTE: This is using a treble gsi rom
[DISCLAIMER] . I am not responsible for dead phones, SD Cards, Alarm clocks failing, etc. You have been warned!
WARNING: Your data will be lost during the process!
=====================================================================================
[Unlocking The Bootloader]
1 - Open Settings, go to About Device and tap Build Number 5 times
2 - Go back, tap on System, Advanced and Developer Options
3 - Check OEM Unlocking
4 - Turn off your phone
5 - Hold down the PWR and VOL+ buttons until the alcatel logo appears
6 - When the logo appears release the PWR button, while holding the VOL+ button
7 - In the recovery menu select reboot to bootloader
8 - In your pc with Minimal ADB and Fastboot installed type "fastboot oem unlock" (w/out the quotes)
9 - On the phone click the VOL+ button
10 - Reboot your phone and wait until the phone factory resets
=====================================================================================
[Installing LAge 16 (Android Pie)]
1 - Go to settings, and search factory
2 - Tap on Factory Reset
3 - When the factory reset is done, turn off the phone
4 - Hold down the PWR and VOL+ buttons until the alcatel logo appears
5 - When the logo appears release the PWR button, while holding the VOL+ button
6 - In the recovery menu select reboot to bootloader
7 - Download https://sourceforge.net/projects/an...910-UNOFFICIAL-treble_arm_avN.img.xz/download to your computer
8 - Open Minimal ADB and Fastboot and type "fastboot -u flash system filelocation.img" (w/out quotes and replace filelocation.img with your "lineage-16.0-20190910-UNOFFICIAL-treble_arm_avN.img" file location
=====================================================================================
[Rooting]
1 - Open Settings, go to About Device and tap Build Number 5 times
2 - Go back, tap on System, Advanced and Developer Options
3 - Tap in Root Access and select ADB and Apps
=====================================================================================
If you have reached this part, congrats! You have successfully rooted the Alcatel 1
{
"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"
}
Thanks dude, that worked perfectly.
Any idea how to get GAPPs working?
What if I only want to root the phone without installing Lineage OS? I just want to remove the bloat apps that came with the phone e.g. Youtube Go, Asistent Go, etc.
I bought a cheap Alcatel 5033D-2BALWE1 from amazon warehouse deals and did not expect to be able to install a custom rom, very nice. But I do have few questions:
Does the rom you linked have some adjustments for this hardware or should any other GSI image work just as well?
Does all the important hardware work (basically LTE, wifi, bluetooth, gps, microphone + speaker + headphone jack, camera)?
Any trusted source for a stock rom that can be flashed with fastboot? There's one on alcatelfirmware.com but not sure how legit it is...
Because amazon warehouse deals sold them so cheap I bought 2, so after trying it I can answer some of my questions. First, my fastboot here (linux) doesn't have a -u switch, but it worked fine without it.
I tried andy yan's build first. Rotation sensor, display brightness, wifi, gps, audio output + micrphone + audio jack switching, camera works. I have not tried bluetooth yet, but the bluetooth settings are there, so there shouldn't be much of an issue. I have not tried a sim card yet.
I wanted something more well known, so I flashed system-quack-arm-aonly-vanilla.img.xz from https://github.com/phhusson/treble_experimentations/releases/tag/v204 and so far everything still seems to work fine. treble version is 27, so I guess all treble roms with support for this version should work. You will need the "aonly" variant, and not the ab one, and it probably has to be the arm (= all arm32?) variant, not the arm32_binder64 one.
ccxxx said:
Because amazon warehouse deals sold them so cheap I bought 2, so after trying it I can answer some of my questions. First, my fastboot here (linux) doesn't have a -u switch, but it worked fine without it.
I tried andy yan's build first. Rotation sensor, display brightness, wifi, gps, audio output + micrphone + audio jack switching, camera works. I have not tried bluetooth yet, but the bluetooth settings are there, so there shouldn't be much of an issue. I have not tried a sim card yet.
I wanted something more well known, so I flashed system-quack-arm-aonly-vanilla.img.xz from https://github.com/phhusson/treble_experimentations/releases/tag/v204 and so far everything still seems to work fine. treble version is 27, so I guess all treble roms with support for this version should work. You will need the "aonly" variant, and not the ab one, and it probably has to be the arm (= all arm32?) variant, not the arm32_binder64 one.
Click to expand...
Click to collapse
isnt the mediatek a 64bit cpu
Good question. /proc/cpuinfo says
Code:
Hardware: MT6739WA
which seems to be a Arm Cortex-A53, which seems to be a 64 bit cpu. I shall try the 64 bit variant of the rom.
ccxxx said:
Good question. /proc/cpuinfo says
Code:
Hardware: MT6739WA
which seems to be a Arm Cortex-A53, which seems to be a 64 bit cpu. I shall try the 64 bit variant of the rom.
Click to expand...
Click to collapse
right something going on after a few flashes, ive tried a few roms and my data in buggered cant get a mobile connection whatsoever ive tried getting into testing mode but no luck!
Any advice>?
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
also getting this quite alot on lots of different roms -FAILED (remote: 'sparse image size span overflow.')
fastboot: error: Command failed
With the arm64 build from https://github.com/phhusson/treble_experimentations/releases/tag/v204 I get this too:
Code:
$ fastboot flash system system-quack-arm64-aonly-vanilla.img
Sending sparse 'system' 1/13 (131068 KB) OKAY [ 38.967s]
Writing 'system' FAILED (remote: 'sparse image size span overflow.')
fastboot: error: Command failed
I guess the system partition is just too big:
1.7G system-quack-arm64-aonly-vanilla.img
1.1G system-quack-arm-aonly-vanilla.img
Are the arm64 binaries really 50% bigger, or is there more stuff in the 64 bit build, or is there empty space in the image?
Anyway, I put my sim card into slot 1 and immediately got a decent 4G connection, I didn't have to do any fiddling (O2/Eplus in germany). I only tried the AOSP image I linked, not the one from andy yan. It seems there are some issues with that image though, alarms and messaging notifications are two things that don't seem to work yet.
I keep getting this:
Code:
fastboot oem unlock
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
FYI i have enabled oem unlock. Any clues?
hello
can i have the source for this because i want to optimize it.
my reason is the boot time is very long.
Hi Guys,
I've been trying since yesterday and get a boot loop on the lineage os boot.
I haven't got past the boot animation.
I've tried to flash to stock with spflash tool. NO success so far.
I need help, please.
I'm running Linux i3.
Thanks a lot!
FNMONTEFALCONE said:
Hi Guys,
I've been trying since yesterday and get a boot loop on the lineage os boot.
I haven't got past the boot animation.
I've tried to flash to stock with spflash tool. NO success so far.
I need help, please.
I'm running Linux i3.
Thanks a lot!
Click to expand...
Click to collapse
Have you tried clearing the cache on the recovery menu and trying to boot again?
Sometimes the phone gets stuck on boot, any clues?
No success with rooting
Chinchila01 said:
Have you tried clearing the cache on the recovery menu and trying to boot again?
Click to expand...
Click to collapse
Dear Chinchila01,
Yes, and yes. I tried everything. The phone is now at my carriers tech support team. It's been more than a week and they can't fix it!!
I'm surprised, I must've really screwed it up somehow!
Well, I got a backup while they decide what to do and I've decided not to touch it.
I guess some phones are just not for fooling around with.
Hope this helps.
Best,
Facundo
I have much the same issues.
Lineage 16 works almost completely if it ever boots, sometimes you get lucky!
Lineage 17 usually boots but doesn't work really well, no gps, etc.
No GAPPS either way.
So close yet so far!
Solution
@caish5
@FNMONTEFALCONE
Hey guys, just to tell you:
Have been trying out this rom: https://github.com/phhusson/treble_experimentations/releases/tag/v32
And so far everything's good.
I installed system-arm-aonly-go-su.img.xz using the following method:
1. Extract it.
2. Reboot to fastboot.
3. fastboot flash system <file>
4. Reboot to recovery
5. Factory reset and cache clean.
6. Reboot.
Thanks, that worked. Even GAPPS!
Chinchila01 said:
@caish5
@FNMONTEFALCONE
Hey guys, just to tell you:
Have been trying out this rom: https://github.com/phhusson/treble_experimentations/releases/tag/v32
And so far everything's good.
I installed system-arm-aonly-go-su.img.xz using the following method:
1. Extract it.
2. Reboot to fastboot.
3. fastboot flash system <file>
4. Reboot to recovery
5. Factory reset and cache clean.
6. Reboot.
Click to expand...
Click to collapse
I've tried a lot of different GSI images, All Pie ones take a long time to boot or don't boot and have to restart until it does.
I got this phone few days ago, Surprised me that it can run GSI's been having a good time testing different roms.
Thought there would be a TWRP but haven't found one. Makes it hard to have a rom with play store and root.
That's what i'm trying to find.
Chinchila01 said:
@caish5
@FNMONTEFALCONE
Hey guys, just to tell you:
Have been trying out this rom: https://github.com/phhusson/treble_experimentations/releases/tag/v32
And so far everything's good.
I installed system-arm-aonly-go-su.img.xz using the following method:
1. Extract it.
2. Reboot to fastboot.
3. fastboot flash system <file>
4. Reboot to recovery
5. Factory reset and cache clean.
6. Reboot.
Click to expand...
Click to collapse
Does that rom have SuperSU ? it say's SU at the end but installed it and no SU app ?
{
"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"
}
TWRP FOR Ulefone Armor X5DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
INSTALLATION
- Go to developer settings and turn on OEM unlock
- Power off the phone and boot to fastboot mode (power and volume +)
- Open a comand prompt and type:
Code:
fastboot flashing unlock
All the data will be loss
- Confirm the oem unlock by pressing the volume + button
- And now type:
Code:
fastboot reboot
- When the phone is turned on, and you complete the setup wizard, type:
Code:
adb reboot bootloader
- When fastboot mode appears in a corner of the phone, type the following command:
Code:
fastboot flash recovery recovery.img
- Now Boot into TWRP, and format data, and reboot to system
If you wanna root it:
- When you are at TWRP and you have formatted data, flash Magisk by sideload
- And reboot to system
Sources:
Device Tree
Download:
TWRP v1
TWRP v2
TWRP v3
Thanks to [Alphabetical Order]:
* Hadenix
* Maanush
* R0rt1z2
* SebaUbuntu
Just a note: This is NOT for the newer mt6765 Android 10 Q phone, If your fone is android 10 Q it will NOT work.
Pachacouti said:
Just a note: This is NOT for the newer mt6765 Android 10 Q phone, If your fone is android 10 Q it will NOT work.
Click to expand...
Click to collapse
Hi
How are you?
My variant is MT6763 one, if you want open pm and we will work for make TWRP for MT6765 variant.
Thanks!
A Only
Thanks dude, but my phone is an 'A' only partition, and as far as I'm aware, only johnwu's phone has actually been done, his being 'A' Only... He made a magisk for his 'A' only phone, but it dont work on mine. To see my firmware, just look at the ulefone stock firmware for android 10_Q, you'll find all you need there... ? It's an armour x5, aarch64, meaning 64bit only I think...
Tried everything I know of, and I do know a bit so not shy in testing any files, I am a competant programmer electronics style, flashing chips etc, so no prob re-flashing errors etc
Edit google johnwu 'A' only and you'll see why its not been done yet... whoever does it will create root for what is coming for all fones...!
X5 pro variant
FYI, this method isn't working on Ulefone Armor x5 Pro variant. (MT6765 - Android 10) Dont know why, but it causes bootlop. Reflashing stock boot img restores the phone functionality (without TWRP obviously). As i'm a new user, i can't post the link to the stock Boot and Recovery images, but if anyone needs them for porting, feel free to PM me.
It wont work because android 9 is the old version of 64bit capable of running 32bit apps, android 10 is pure x64bit. The bootloader is NOT the bootloader anymore, but a preloader, loading BEFORE the bootloader. so flashing bootloader over preloader causes bootloop, makes sense dunnit?
All fones will soon adopt this, and it has already started, since johnwu was bought by apple, and will be made too busy to produce anything anymore, by design of course, and since this new version of a only partitioning has been succesfull in thwarting him, no more root for you. Now you get another file system running on top of your unrootable fone to make you think you have root, pretty much sums it up, this overlayfs...
Shows how good the devs really are nowadays, when nomoretech (hovatek) found out his work dont work on android 10, he ignored my thread, too busy with old android 9 for old fones. upgrade, update, move on, say 'tata root'....
thanks good job on android 9
jmpf_bmx said:
TWRP FOR Ulefone Armor X5DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
INSTALLATION
- Go to developer settings and turn on OEM unlock
- Power off the phone and boot to fastboot mode (power and volume +)
- Open a comand prompt and type:
Code:
fastboot flashing unlock
All the data will be loss
- Confirm the oem unlock by pressing the volume + button
- And now type:
Code:
fastboot reboot
- When the phone is turned on, and you complete the setup wizard, type:
Code:
adb reboot bootloader
- When fastboot mode appears in a corner of the phone, type the following command:
Code:
fastboot flash recovery recovery.img
- Now Boot into TWRP, and format data, and reboot to system
If you wanna root it:
- When you are at TWRP and you have formatted data, flash Magisk by sideload
- And reboot to system
Sources:
Device Tree
Download:
https://github.com/jmpfbmx/android_...eleases/download/twrp_bretzel_v1/recovery.img
Thanks to [Alphabetical Order]:
* Hadenix
* Maanush
* R0rt1z2
* SebaUbuntu
Click to expand...
Click to collapse
Hi,
We try to install it on a Armor X5 with android 9, build Armor_X5_MH1_EEA_V01 and all we have is a green line in the top of the screen then the phone reboot...
Is it many hardwares for the same phone ?
Thank you
wargreen said:
Hi,
We try to install it on a Armor X5 with android 9, build Armor_X5_MH1_EEA_V01 and all we have is a green line in the top of the screen then the phone reboot...
Is it many hardwares for the same phone ?
Thank you
Click to expand...
Click to collapse
Hi,
Can you share a pic of the screen?
Can you try to use adb? (Try adb shell, if works make this, adb shell cat /tmp/recovery.log, and send me the file by here)
Thanks
Regards
Jose
Tomorrow you will have a huge update of TWRP and some news about A11 hehe
"- Now Boot into TWRP, and format data, and reboot to system"
Could you explain exactly How to do this, please
bootloader activated, do I hard reboot pressing power and vol+, and when do I stop pressing ?
thanks
ulysse
"- Now Boot into TWRP, and format data, and reboot to system"
Could you please explain exactly how to do this ?
Bootloader activated, Do I press power and vol+ and keep then pressed ? until what ?
thanks a lot
ulysse
ulysse_21 said:
"- Now Boot into TWRP, and format data, and reboot to system"
Could you explain exactly How to do this, please
bootloader activated, do I hard reboot pressing power and vol+, and when do I stop pressing ?
thanks
ulysse
Click to expand...
Click to collapse
Hi
How are you?
Have you got Bootloader unlocked? (Idk wdym with bootloader activated)
For do that you just need to flash TWRP, reboot phone pressing vol+ and power as you say and when TWRP boots, just go to Wipe -> Format Data (Type yes) and then when the format data has finished, clic on reboot to system
TWRP Updated!
Now MTP and ADB are working better!!
thanks, i try
ulysse
jmpf_bmx said:
- When the phone is turned on, and you complete the setup wizard, type:
Click to expand...
Click to collapse
I start in Engish , skip connect to mobile network (no sim), skip WI-Fi, adjust good date and time, without "use location" and without "send usage and diagnostic data"; acept; "not now" for "protect your phone"
Then I activate the developper mode and in "system/ options for developers" I turn on USB debogage.
Did i miss sommething at this stage ?
jmpf_bmx said:
Can you try to use adb? (Try adb shell, if works make this, adb shell cat /tmp/recovery.log, and send me the file by here)
Click to expand...
Click to collapse
Hello thanks for your help.
Phone powered on, I can go on "Armor_X5:/ $ " if I type "adb shell".
but I don't understand "adb shell cat /tmp/recovery.log,"
I have "cat: tmp/recovery.log: No such file or directory"
appologize for my low level in English and in computering, I write code more on ImageJ and Rstudio.
ulysse_21 said:
I start in Engish , skip connect to mobile network (no sim), skip WI-Fi, adjust good date and time, without "use location" and without "send usage and diagnostic data"; acept; "not now" for "protect your phone"
Then I activate the developper mode and in "system/ options for developers" I turn on USB debogage.
Did i miss sommething at this stage ?
Click to expand...
Click to collapse
Did you opened bootloader?
ulysse_21 said:
Hello thanks for your help.
Phone powered on, I can go on "Armor_X5:/ $ " if I type "adb shell".
but I don't understand "adb shell cat /tmp/recovery.log,"
I have "cat: tmp/recovery.log: No such file or directory"
appologize for my low level in English and in computering, I write code more on ImageJ and Rstudio.
Click to expand...
Click to collapse
I guess that you aren't at recovery, or you didn't disable and enable MTP
Pachacouti said:
Just a note: This is NOT for the newer mt6765 Android 10 Q phone, If your fone is android 10 Q it will NOT work.
Click to expand...
Click to collapse
It works in mt6762 Android 10 version? model Armor_X5_Q_EEA
This guide is the only one made and tested personally by me, I am not responsible for malfunctions or any damage to the device, carefully read every single step and everything will be successful
{
"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"
}
[ATTENTION]: Before proceeding, save all your data on your computer and REMOVE ANY KIND OF UNLOCKING (sequence, pin, fingerprint etc ..); remove the sim and the microSD; get a microSD, at least 3/4 giga, where you can upload the files necessary for the procedure.
[NECESSARY CONDITIONS]: Starting from emui 8; have the cell phone charged to 100%; bootloader unlocked and the only procedure I know and working is the one I propose in the guide, the code is obtained by paying 4 €/$, THERE ARE NO FREE ALTERNATIVES.
[PREREQUISITES]: Download -> HiSuite , Dc-Unlocker
At this point we create a folder on the desktop and we will call it ANDROID1O to have a reference point and we will extract the folder contained in the dc-unlocker archive. Once the folder has been extracted, install adb and fastboot in order. At this point we can also install HiSuite.
[PROCEDURE]
[DOWNGRADE] In
order for dc-unlocker to read the bootloader code it is necessary to go back to an older version of android, so let's proceed as follows:
(1) We connect the mobile phone to the computer and start HiSuite, in some cases it will start automatically, and we follow the procedure that will be shown to us to enable debugging. If you have followed everything correctly HiSuite will read your device without problems.
(2) Remaining on HiSuite, click on the UPDATE SYSTEM item, a window will appear, at this point we can press on PREVIOUS VERSION (now I don't remember the precise wording) and we can start the downgrade. It will take a while.
(3) At the end of the downgrade we can start the mobile phone by skipping and ignoring the various configurations by putting the language in Italian as a matter of practicality, let's move on to the next step
[GET BOOTLOADER CODE]
(1) We go to the system settings ---> information ----> we do many taps until the message "now you are a developer" appears ----> we go back ----> developer options and activate usb debugging.
(2) Let's go to HiSuite and in the settings located at the top right we remove the check mark under "Start when it connects to the device" and close it.
(3) We buy the credits to read the bootloader code from https://www.dc-unlocker.com/buy in this way:
- We select the payment method
- We leave "new user account"
- We enter a username that we like it
- We enter an e-mail address to which we can easily access, here we will be sent the credentials to be able to access dc-ulocker
- We enter 4 in the credits box and then type on confirm
- If everything went well, the screen will appear with the credentials and you will receive a copy on the email
(We now have the necessary credits to be able to read the unlock code)
(4) Let's go back to the folder created on the desktop and start dc-unlocker and clicking on the SERVER item we enter the credentials obtained on the site
(5) At this point in the drop-down at the top left we look for the item HUAWEI PHONES
(6) A guide will appear that in any case I will report here:
- In the call keypad type the following combination * # * # 2846579 # * # *
- Press on MANUFACTURE MODE
(7) We can connect the mobile phone and press on the magnifying glass we see on dc-unlocker and if we have done everything correctly the program it will detect our mobile phone
(8) When the phone has been recognized we go to the UNLOCKING section and press on READ BOOTLOADER CODE, if we have done everything correctly we will get a code that we will enter somewhere so as not to lose it, we will need it later
(I leave you the video dc-unlocker official guide on how to unlock bootloader if you have any doubts ---> Help
(9) We disconnect the mobile phone from the computer
(10) After writing down the bootloader code we can close dc-unlocker, connect the mobile phone to a wifi network and search for system updates to return to the latest version of android and therefore to emui8,
if no updates appear, we try to force them by going to settings, wifi, press and hold on the wifi to which we are connected, modify, check advanced options, press on proxy, manual,
in proxy hostname we write localhost and in the port we write 8080 , we press on connect and if we return to the updates item it should find the most recent version. At this point we can update the mobile phone to the most recent version.
[BOOTLOADER UNLOCK]
(1) After returning to the most recent version of android we turn on the mobile phone
(2) We go to the system settings ---> information ----> do many taps until the message "you are now a developer "----> go back ----> developer options and activate the usb debug and the active voice unlock manufacturer
(3) We connect the mobile phone to the computer, press on transfer files, go back to the developer settings and activate the debug , at this point the mobile will ask us to give permissions to our computer and we confirm
(4) Let's go back to the desktop and at the top right click on file, open windows powershell, open windows poweshell as administrator and click on yes
(5) We type the command "adb devices" (write it without quotes), we wait for the end of the 'execution of the command and type again the command "adb devices" (without quotes)
and so we will see a number that corresponds to our mobile phone
(6) We give the command "adb reboot bootloader" (without quotes) and we send
(7) The mobile phone will start in a white screen with an android, the important thing is that two written in red appear with the words PHONE Unlocked and FRP Unlock
(8) From the Widows poweshell screen opened previously we give the command "fastboot oem unlock CODICEBOOTLOADER" (without quotation marks) (CODICEBOOTLOADER refers to the code obtained with Dc-Unlocker) and press on
enter (9) On the cellualre a warning will appear, press once the volume up key and then the power key to confirm the unlocking of the bootloader
(10) When the procedure is finished, it will take very little time, we give the command "fastboot reboot" (without quotes) and when the mobile phone screen it will go black we unplug it
(11) The cellualre will restart a couple of times with a white and other yellow writing, let it go, it will be returned to the factory settings and we will just have to skip all the configuration procedures but set the language in Italian
Finally the bootloader is unlocked!
Here's a free way https://github.com/SkyEmie/huawei-honor-unlock-bootloader
JanoRasho13 said:
Here's a free way https://github.com/SkyEmie/huawei-honor-unlock-bootloader
Click to expand...
Click to collapse
You try this?
pitrazzu said:
You try this?
Click to expand...
Click to collapse
I didn't, but a friend of mine with p20 lite succeeded unlocking!
JanoRasho13 said:
I didn't, but a friend of mine with p20 lite succeeded unlocking!
Click to expand...
Click to collapse
Knowing this sooner I would do it with this tool. Anyway good to knoe but I don't think I would stay with Huawei brand due to their anti-community mods policy.
DunoCZ said:
Knowing this sooner I would do it with this tool. Anyway good to knoe but I don't think I would stay with Huawei brand due to their anti-community mods policy.
Click to expand...
Click to collapse
Yes, absolutelly. Why you prevent me to mod my phone if the phone is mine?
Here is a free alternative to DC-UNLOCKER
I've unlocked the bootloader and installed TWRP on my wife's phone (emui 8 up to date dec 2020)
Here is the program : Potato NV
Follow these instructions : PotatoNV - wiki
To find where the testpoint is located search for pralx1 STF testpoint on your favourite internet search engine.
PS : By the way, the understanding of how it works goes way beyond my technical skills...
Junkilito said:
Here is a free alternative to DC-UNLOCKER
I've unlocked the bootloader and installed TWRP on my wife's phone (emui 8 up to date dec 2020)
Here is the program : Potato NV
Follow these instructions : PotatoNV - wiki
To find where the testpoint is located search for pralx1 STF testpoint on your favourite internet search engine.
PS : By the way, the understanding of how it works goes way beyond my technical skills...
Click to expand...
Click to collapse
And that means I no longer need to downgrade?
gabefufezan said:
And that means I no longer need to downgrade?
Click to expand...
Click to collapse
I didn't need to downgrade. I've just downgraded after the unlock via dload in order to install Android 11 Rom.
JanoRasho13 said:
Here's a free way https://github.com/SkyEmie/huawei-honor-unlock-bootloader
Click to expand...
Click to collapse
I want to try this way. Did it work for you guys?
This is supossed to happen, right?
gabefufezan said:
View attachment 5273573This is supossed to happen, right?
Click to expand...
Click to collapse
It's almost impossible to find it randomly. There are too many combinations...
If you read the issue section of this git, you'll see it by yourself.
Junkilito said:
It's almost impossible to find it randomly. There are too many combinations...
If you read the issue section of this git, you'll see it by yourself.
Click to expand...
Click to collapse
So that means the tool is unefficient?
gabefufezan said:
So that means the tool is unefficient?
Click to expand...
Click to collapse
I think so.
gabefufezan said:
So that means the tool is unefficient?
Click to expand...
Click to collapse
I tried but It didn't work. Unfortunately I had an aplhanumeric code despite that my device was european, and this made impossible the task to find the code ( it would take millions of years to do a minimum percentage of combinations ).
I found it using PotatoNV, it adds the difficult part to disassemble the phone but it is very efficient.
gabefufezan said:
View attachment 5273573This is supossed to happen, right?
Click to expand...
Click to collapse
It is not supposed to happen this way. You have to see something like "fastboot error: wrong password", so you're probably missing some permissions.
Anyway unless you have a numeric code there is virtually zero chance to find it in that way.
In my case I ran the script and in ~4 hours it tried all the numeric codes supposed to fit with my imei, but with no success. Later I discovered that my code was alphanumeric.
Hi everyone, I've just obtained te bootloader code, but now I'm stuck on EMUI 5.0.3, there are no updates available.
I tried forcing it but nothing changes..
On my P8 Lite 2017, I've tried the PotatoNV method which is, in fact, very easy (the most difficult part was to open the back cover, but with an opening tool it's easier) and no need to downgrade. For me the SkyEmie method was just a waste of time.
pitrazzu said:
(10) After writing down the bootloader code we can close dc-unlocker, connect the mobile phone to a wifi network and search for system updates to return to the latest version of android and therefore to emui8,
if no updates appear, we try to force them by going to settings, wifi, press and hold on the wifi to which we are connected, modify, check advanced options, press on proxy, manual,
in proxy hostname we write localhost and in the port we write 8080 , we press on connect and if we return to the updates item it should find the most recent version. At this point we can update the mobile phone to the most recent version.
Click to expand...
Click to collapse
Hello, i'm stuck at this step, i'm back at EMUI 5.0.3 and when i check for update it tells me "no updates"
Worked for me (PRA-LX1) !!
So easy, except from potatoNV (didn't try back panel is broken, as a result I cannot open my phone) all other free solutions have not worked for me.
Follow anything in this guide at your own risk. I will not accept any responsibility if you are left with a bricked device, and/or a device that is damaged or impaired in some way. These steps are a reconstruction of what I was doing - I haven't actually tested the exact files attached, which should be more cleaner than the ones I was working with.
The inkPalm 5 is a 5.2" eReader with an Allwinner 32-bit ARM B300 CPU and 1GB RAM running Android 8.1 sold in China under Xiaomi's Moaan brand.
This involves writing a file to /system, which may prevent you from installing future OTAs. Be warned that the firmware for this device cannot be downloaded, so you could end up with an unrepairable brick!
Make sure ADB is setup first.
Download dump_kernel_to_system_signed.zip
Reboot the inkPalm into recovery mode :
Code:
reboot recovery
Use the touch screen and/or volume + power buttons to choose the "Apply update from ADB" option
On the computer, run
Code:
adb sideload path\to\dump_kernel_to_system_signed.zip
(making the obvious substitution)
When it's done, choose the first option in the recovery (reboot system now) to boot back into Android
Back in an adb shell, run
Code:
cp /system/bimg.img /sdcard/
Install the Magisk APK
Open Magisk, tap install
I don't think the AVB/dm-verity option needs to be checked, so I left it unchecked. YMMV. The inkPalm doesn't encrypt itself even if you enable a PIN.
Choose bimg.img from your storage and let Magisk do its thing
Transfer the magisk_patched*.img file in your Downloads folder onto the PC
Flashing the patched kernel image with recovery
Rename your magisk_patched.img file to boot.img
Using your favourite archive manager, add your boot.img to the root folder of kernel_flashing_template.zip
In a command prompt, run
Code:
java -jar signapk-1.0.jar -w testkey.x509.pem testkey.pk8 kernel_flashing_template.zip kernel_flashing_template_signed.zip
(If you run into problems, make sure you have JRE 8 installed.)
Reboot back into recovery and
Code:
adb sideload
kernel_flashing_template_signed.zip
Reboot back into Android and hopefully you should have a rooted inkPalm with Magisk
(Flashing with fastboot should work, but I've not tested that.)
EDIT: You can find an extended guide at https://github.com/qwerty12/inkPalm-5-EPD105-root with steps for installing microG.
qwerty12 said:
Follow anything in this guide at your own risk. I will not accept any responsibility if you are left with a bricked device, and/or a device that is damaged or impaired in some way. These steps are a reconstruction of what I was doing - I haven't actually tested the exact files attached, which should be more cleaner than the ones I was working with.
The inkPalm 5 is a 5.2" eReader with an Allwinner 32-bit ARM B300 CPU and 1GB RAM running Android 8.1 sold in China under Xiaomi's Moaan brand.
This involves writing a file to /system, which may prevent you from installing future OTAs. Be warned that the firmware for this device cannot be downloaded, so you could end up with an unrepairable brick!
Make sure ADB is setup first.
Download dump_kernel_to_system_signed.zip
Reboot the inkPalm into recovery mode :
Code:
reboot recovery
Use the touch screen and/or volume + power buttons to choose the "Apply update from ADB" option
On the computer, run
Code:
adb sideload path\to\dump_kernel_to_system_signed.zip
(making the obvious substitution)
When it's done, choose the first option in the recovery (reboot system now) to boot back into Android
Back in an adb shell, run
Code:
cp /system/bimg.img /sdcard/
Install the Magisk APK
Open Magisk, tap install
I don't think the AVB/dm-verity option needs to be checked, so I left it unchecked. YMMV. The inkPalm doesn't encrypt itself even if you enable a PIN.
Choose bimg.img from your storage and let Magisk do its thing
Transfer the magisk_patched*.img file in your Downloads folder onto the PC
Flashing the patched kernel image with recovery
Rename your magisk_patched.img file to boot.img
Using your favourite archive manager, add your boot.img to the root folder of kernel_flashing_template.zip
In a command prompt, run
Code:
java -jar signapk-1.0.jar -w testkey.x509.pem testkey.pk8 kernel_flashing_template.zip kernel_flashing_template_signed.zip
(If you run into problems, make sure you have JRE 8 installed.)
Reboot back into recovery and
Code:
adb sideload
kernel_flashing_template_signed.zip
Reboot back into Android and hopefully you should have a rooted inkPalm with Magisk
(Flashing with fastboot should work, but I've not tested that.)
Click to expand...
Click to collapse
As far as I could gather, with both USB connection and developper mode on, ADB conncection is explicitely rejected. Besides, there is, on InkPalm, below the usuals USB checks, one that reads "...ADB/ADT..." which cannot be checked. The connetion request by wireless ADB, supplying the correct address, is also rejected.... As though the device needed be rooted first !
I haven't tested using ADB over Wi-Fi, but I can honestly say I have had no issues using ADB over USB on the inkPalm. ADB was enabled by default on mine, and not to mention the security of it has been weakened - you don't even need to approve ADB connections for the first time...
So, since mine seems to reject ADB on both USB and WI-FI, what would you suggest to try as next --and desperate ? I cannot find any reference to the manufacturer that would eventually grant me permissions-- step ?
So long,
Sixto Quesada
Bis -- I forget to mention that my primary goal is merely to be able to change the language to English, as I think that there are already many possibilities in-built as to the configuration, including the shell !
squsqu6 said:
So, since mine seems to reject ADB on both USB and WI-FI, what would you suggest to try as next --and desperate ?
Click to expand...
Click to collapse
Is debugging mode actually on? Open the settings, go to the highlighted page and
{
"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"
}
turn the highlighted setting on (make sure the setting above it is on too - it will let you install external APKs)
You can follow these steps to show the Developer Settings, that's up to you: https://github.com/epodegrid/epd106-ADB#step-1-install-adb
squsqu6 said:
Bis -- I forget to mention that my primary goal is merely to be able to change the language to English
Click to expand...
Click to collapse
If you really can't get ADB to work, then there might be another way. Install the APK of my launcher fork (how you do that is up to you - you can try using the built-in browser or transferring the APK over MTP and using the file manager [which I've never opened] to install it).
In the new launcher, tap-and-hold the Settings icon (the one with a dark background),
choose Additional Settings and tap Locale. Then follow the instructions here: https://github.com/philips/inkpalm-5-adb-english#change-the-language
ADB is definit[iv]ely unavailable. But your launcher fork --that I already had, but did not know what to do with-- works, I now have most of the menu in English.
Thank you so much.
This worked great for me thanks a lot. I have a quick question if you know it. Is there anyway to get the old style android soft nav bar on the bottom (home, back, open apps)? The stuff you can do with the home button/logo button in settings is pretty limited.
Thanks.
reaverclan said:
Is there anyway to get the old style android soft nav bar on the bottom (home, back, open apps)?
Click to expand...
Click to collapse
I think it may have removed entirely to save space. That's just a guess though. I tried two Magisk modules to enable it - one sets that qemu property and the other uses an Android resource overlay - and both didn't work. The only workaround I can suggest, untested, would be this: https://github.com/epodegrid/epd106-ADB#step-4-naviation-button
qwerty12 said:
Thanks.
I think it may have removed entirely to save space. That's just a guess though. I tried two Magisk modules to enable it - one sets that qemu property and the other uses an Android resource overlay - and both didn't work. The only workaround I can suggest, untested, would be this: https://github.com/epodegrid/epd106-ADB#step-4-naviation-button
Click to expand...
Click to collapse
Yeah I tried step 4 and adb said the file was to old so rejected it and I tired it in the file manager anyways to see what would happen and it says it's not a working package or not compatible. So I guess it's for another xiaomi device or base android version. I also noticed only the stock file manager can actually invoke the package installer, root explorer gets the prompt to install but never then sends it to the Manger to load it and give the option for an install.
reaverclan said:
Yeah I tried step 4 and adb said the file was to old so rejected it and I tired it in the file manager anyways to see what would happen and it says it's not a working package or not compatible.
Click to expand...
Click to collapse
It's actually because the modified launcher mentioned in this thread uses the package name com.moan.moanwm (credits to whoever found that out; doing that allows the original Settings to be launched), which actually belongs to those navball buttons... I was originally going to suggest to just get rid of the launcher, so you can install the navball buttons, but they're really crashy and useless anyway. Sorry, I don't know what else to suggest - given other "QOL" changes by Moann (see below), I strongly suspect the navigation button code was ripped out entirely to save RAM.
I also noticed only the stock file manager can actually invoke the package installer, root explorer gets the prompt to install but never then sends it to the Manger to load it and give the option for an install.
Click to expand...
Click to collapse
Give Total Commander a try.
Moann really did a number on this device's Android build and messed it up, presumably in the name of "security". Only certain programs can show the original Settings, which messes up other applications' ability to show the app info of programs; the only thing that can force stop programs is Settings (which messes up Titanium Backup) and Root Explorer probably tries to invoke the Android installer directly (if that's a thing).
qwerty12 said:
It's actually because the modified launcher mentioned in this thread uses the package name com.moan.moanwm (credits to whoever found that out; doing that allows the original Settings to be launched), which actually belongs to those navball buttons... I was originally going to suggest to just get rid of the launcher, so you can install the navball buttons, but they're really crashy and useless anyway. Sorry, I don't know what else to suggest - given other "QOL" changes by Moann (see below), I strongly suspect the navigation button code was ripped out entirely to save RAM.
Give Total Commander a try.
Moann really did a number on this device's Android build and messed it up, presumably in the name of "security". Only certain programs can show the original Settings, which messes up other applications' ability to show the app info of programs; the only thing that can force stop programs is Settings (which messes up Titanium Backup) and Root Explorer probably tries to invoke the Android installer directly (if that's a thing).
Click to expand...
Click to collapse
Ah I see that's clever. It's not the end of the world and yeah I think it's cause root explorer does what you said about invoking the thing directly. I just use the stock app to only install and that's it. My journey so far is shown here and regardless of the jank it has been a great device. https://www.mobileread.com/forums/showpost.php?p=4140508&postcount=155
Thanks again for the time to make it even greater. Only thing that sucks is no stock img to un brick if something goes to far. Hopefully someone leaks that at some point. This device seems pretty new to the market still.
squsqu6 said:
ADB is definit[iv]ely unavailable. But your launcher fork --that I already had, but did not know what to do with-- works, I now have most of the menu in English.
Thank you so much.
Click to expand...
Click to collapse
I now have a new, but old !, trouble : battery life. I have enforced all saving possibilities available --from standard menu, from E-Ink Launcher, and, from RomToolBox, processors speed slowing--, and, yet, after 8 hours of use, InkPalm battery is totally empty, even though being totally user-idle --not a single user application being active according to linux 'top' request. Conversely, Kobo reader battery lasts for days in reading mode.
My question : would it be thinkable any possible trick of triggering the sleeping function without pushing the red button, so as to keep the screen as it is --allowing the reading of actual page until next (not a book, a musical partion, which takes longer !)--. Bypassing by script the red button action, or other ? --Note : the screensaver option allows for user-image, like a screenshot, but it requires to move it to the proper place and to renew it at every page...
Sorry for being so long, I am far from being familiar wich Linux (Android).
Greetings,
S. Quesada