Myself, and some others, seem to be experiencing issues after restoring a Nexus 10 from a recovery image. The device, for whatever reason, will not boot and will be stuck in a bootloop.
Solution:
After you've updated from the zip file, open the zip archive and extract userdata.img and cache.img files.
Once you've extracted, you should execute the following commands
Code:
fastboot flash userdata userdata.img
fastboot flash cache cache.img
After this, the device should reboot properly.
If you want something to automatically patch the files, download this application, place in factory image directory and run it.
{
"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"
}
Fixed flash-all.bat:
Code:
@ECHO OFF
:: Copyright 2012 The Android Open Source Project
::
:: Licensed under the Apache License, Version 2.0 (the "License");
:: you may not use this file except in compliance with the License.
:: You may obtain a copy of the License at
::
:: http://www.apache.org/licenses/LICENSE-2.0
::
:: Unless required by applicable law or agreed to in writing, software
:: distributed under the License is distributed on an "AS IS" BASIS,
:: WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
:: See the License for the specific language governing permissions and
:: limitations under the License.
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-mantaray-jop40c.zip
:: MERP patch - manually flash userdata and cache
fastboot flash userdata userdata.img
fastboot flash cache cache.img
echo Press any key to exit...
pause >nul
exit
Fixed flash-all.sh:
Code:
#!/bin/sh
# Copyright 2011 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-mantaray-jop40c.zip
# MERP patch - manually flash userdata and cache
fastboot flash userdata userdata.img
fastboot flash cache "cache.img"
This worked, thanks.
Related
In china ics rom,i find a New version of region file,it's little diff with hc one(and in aio tool)
sames it add a file named "Vendor_054c_Product_0268.kcm",something about keybord
and version changed from 27550173_23 to 27550173_25
i wish condi update this file to aio tool next version
PS,the file of region 27550174 is same as 27550173
dir diff
{
"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"
}
ini diff
prop diff
zip file
View attachment region.zip
<robin> said:
In china ics rom,i find a New version of region file,it's little diff with hc one(and in aio tool)
sames it add a file named "Vendor_054c_Product_0268.kcm",something about keybord
and version changed from 27550173_23 to 27550173_25
i wish condi update this file to aio tool next version
PS,the file of region 27550174 is same as 27550173
dir diff
View attachment 1158572
ini diff
View attachment 1158573
prop diff
View attachment 1158574
zip file
View attachment 1158575
Click to expand...
Click to collapse
Have you read the contents of the kcm file.
Not sure if it matters but here it is.....
Code:
# Copyright (C) 2010 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
# Generic key character map for full alphabetic US English PC style external keyboards.
#
# This file is intentionally very generic and is intended to support a broad rang of keyboards.
# Do not edit the generic key character map to support a specific keyboard; instead, create
# a new key character map file with the required keyboard configuration.
#
type FULL
### Gamepad buttons ###
key BUTTON_B {
base: fallback MENU
}
key BUTTON_X {
base: fallback BACK
}
key BUTTON_Y {
base: fallback DPAD_CENTER
}
key BUTTON_THUMBL {
base: fallback DPAD_CENTER
}
key BUTTON_THUMBR {
base: fallback DPAD_CENTER
}
key BUTTON_START {
base: fallback HOME
}
key BUTTON_SELECT {
base: fallback MENU
}
key BUTTON_1 {
base: fallback MENU
}
Still strange that there is a difference, just not sure if it changes anything. :laugh:
Chur
VID=054C PID=0268,it's Sony Playstation 3 Controller
so this file maybe used to map ps3 pad key to ics keys
START=>HOME
X=>BACK
SELECT/B/1=>MENU
Y/THUMBL/THUMBR=>DPAD_CENTER(recent app?)
maybe every region add this file :laugh:
more .kcm file is in system\usr\keychars
Introduction
Try at own risk
I am a Linux user. Commands are Debian or Ubuntu so you may need to check your package manager for
Linux software for adb if different distro.
If you do not have sudo enabled, then use su - please
On tablet, I use "reboot" by Petrus, as recommended by pogs24ever
I have also installed app= adbd insecure........YMMV
Know that when TWRP is used on removeable sdcard = /sdcard2, you will have a folder
called TWRP so I prefer to rename my image as twrp.img
Credits
Vampirefo for his wonderful help with adb and root id test
pogs24ever for his XDA post for TWRP
AbduL_PT for TWRP for Rockchip
Method
SPOILERS= Click to show content ..... hides images only
Ensure your device is rooted.
{
"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 your method to root is failing try my method here.
http://forum.xda-developers.com/hua...t-huawei-mediapad-7-lite-alternative-t2996675
On tablet go to system settings and enable USB debugging.
Don't worry about setting media transfer, camera or Hisuite
Download and unpack the TWRP* zip to PC and copy TWRP.img to your home folder.
See Original post for latest download
http://forum.xda-developers.com/showthread.php?t=2693100
Latest download is found at
"Dowload the zip file to this"
Install latest adb to Linux PC
Code:
sudo su
apt-get update
apt-get install android-tools-adb
Do NOT close terminal please
Create udev rule if you don't yet have Huawei mentioned in your rules
Code:
echo 'SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", MODE="666", GROUP="plugdev" ' > /etc/udev/rules.d/55-huawei.rules
Refresh udev for distros running "service" such as distros like Ubuntu with next command or
bottom line for distros not running service like Debian.
Code:
service udev restart
udevadm control --reload-rules
Now open terminal as local user please.
I prefer to kill the server and restart it with
Code:
adb kill-server
adb devices
If you do not get a device showing a serial number, you can NOT continue.
Recheck you have enabled USB debugging, kill the server and retry adb devices command.
If you are not sure what device your recovery is on, recheck it please with
Code:
adb shell cat /proc/mtd | grep recovery
Now we need to translate that into a device which is /dev/mtd/mtd3
Now we can flash with
Code:
adb push TWRP.img /sdcard2/twrp.img
# above line copies TWRP to removeable sdcard, change sdcard2 if you
don't use one please.
adb shell su -c "dd if=/sdcard2/twrp.img of=/dev/mtd/mtd3"
adb kill-server
Second last command may fail if you don't yet have a rooted device
also if size of bytes of TWRP image is wrong, recheck it please.
6717440 bytes = 6560 Kb = 6.41 Mb which is far less than max size of recovery image.
Before you test, ensure you have a backup of current recovery on removeable sdcard please.
Now use app to reboot into recovery to test.
Nice.. Hope you can find time to port some Cm rom for this.. I stop digging for this device for sometime now.. We have manage to boot on cm9 but it goes bootloop due to kernel compatibility ..
pogs24ever
I have not attempted to port anything yet. Feel free to pm or post here any links you would like me to look at please.
nor have I attempted to cross compile a kernel for this device but I can see Huawei appear to have source here
http://consumer.huawei.com/en/support/downloads/detail/index.htm?id=18334
cheers
just to make it clear in case others drop by via google
this is the mediapad with model showing as S7-931W
and
ro.product.device=hws7930w
2) you can use huawei and 7930 to see one entrant here
https://www.otaupdatecenter.pro/device-lookup
good luck
{
"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"
}
Droidian for Poco X3/NFC
ABOUT:
Droidian is a Gnu/Linux Distribution which uses Halium to have compatibility with android smartphones
Website: https://droidian.org
Telegram: Device Group | Global Group
Github: https://github.com/droidian
WHAT WORKS?
- Almost everything
WHAT DOESN'T WORK?
- Audio
- You tell me..
DOWNLOADS:
GSI rootfs
Adaptation package
boot-surya.img
boot-karna.img
dtbo-surya.img
dtbo-karna.img
vbmeta-surya.img
vbmeta-karna.img
Surya Installation:
Flash boot.img: fastboot flash boot boot-surya.img.
Flash dtbo.img: fastboot flash dtbo dtbo-surya.img.
Flash vbmeta.img: fastboot --disable-verity --disable-verification flash vbmeta vbmeta-surya.img.
Flash your favorite recovery ( TWRP Recommended ).
Format userdata as ext4 from inside the recovery or via fastboot: fastboot format:ext4 userdata.
Now boot into recovery.
Go into sideload mode and sideload droidian-rootfs-api29gsi-arm64-xxxxxxxx.zip: adb sideload droidian-rootfs-api29gsi-arm64-xxxxxxxx.zip
Now extract adaptation-surya-script.zip on your PC/Laptop and push it to your device: adb push adaptation-surya-script /tmp
Get a shell into your device: adb shell
Change directory to /tmp and run the script: cd /tmp/adaptation-surya-script && chmod +x install.sh && ./install.sh
Now boot into your device.
The first boot will take a while.
Karna Installation:
Flash boot.img: fastboot flash boot boot-karna.img.
Flash dtbo.img: fastboot flash dtbo dtbo-karna.img.
Flash vbmeta.img: fastboot --disable-verity --disable-verification flash vbmeta vbmeta-karna.img.
Flash your favorite recovery ( TWRP Recommended ).
Format userdata as ext4 from inside the recovery or via fastboot: fastboot format:ext4 userdata.
Now boot into recovery.
Go into sideload mode and sideload droidian-rootfs-api29gsi-arm64-xxxxxxxx.zip: adb sideload droidian-rootfs-api29gsi-arm64-xxxxxxxx.zip
Now extract adaptation-surya-script.zip on your PC/Laptop and push it to your device: adb push adaptation-surya-script /tmp
Get a shell into your device: adb shell
Change directory to /tmp and run the script: cd /tmp/adaptation-surya-script && chmod +x install.sh && ./install.sh
Now boot into your device.
The first boot will take a while
Notes:
The default password is 1234.
If you see a black screen, don't worry it takes a long time to boot.
Droidian GSIs are experimental! Bugs and missing features are expected.
You need this miui build LINK
Thanks to: Barry, Javad and myself for making this rom possible
Does VOIP VoLTE work?
im not being sketchy... when you say audio doesnt work... is that global for the phone or glitchy... or because i so want to use a linux os for my phone but i do still need it to be a phone.... i was hoping you might say that phone calls work but the external speaker has a bug or something.... (praying)
nakedpwr said:
im not being sketchy... when you say audio doesnt work... is that global for the phone or glitchy... or because i so want to use a linux os for my phone but i do still need it to be a phone.... i was hoping you might say that phone calls work but the external speaker has a bug or something.... (praying)
Click to expand...
Click to collapse
Nope, they don't work, you can use something like telegram if your headphones have a microphone
Srilakshmidaran said:
Does VOIP VoLTE work?
Click to expand...
Click to collapse
Doesn't work with any Halium-based distro right now, but some people are working on it
To my knowledge Windows Subsystem for Android ( WSA ) is not created to run apps from the Amazon store only, but is configured for testing via ADB, will say run Linux commands in an Android shell, too.
WSA ( what at time of this writing is running Android 12 ) has merged Landley's Toybox v0.8.4, a bag of over 200 Linux command line applets - I have not really counted them.
A typical Linux distribution provides 428 command line applets - the SU incorporated. I have uploaded .ZIP ( 263 MB ) what contains them all here to:
428-cmds
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
If you are interested in this project, too, then it's on you to download and extract the .ZIP and push the 428 files onto Android, preferredly to /storage/emulated/0/428-cmds, and make them executable.
Example .BAT-file - assumed .ZIP got extracted into D:\428-cmds folder & ADB is installed on PC
Code:
adb connect 127.0.0.1:58526
adb devices
adb shell "cd /sdcard & mkdir -p -m06755 428-cmds 2>/dev/null"
adb push "D:\428-cmds" "/sdcard/428-cmds/"
adb shell "SM='getenforce';setenforce 0;cd /sdcard/428-cmds;CMDS='$(find .-name "*" -maxdepth 1 -type f 2>&1 | grep -i -v denied)';while read x;do chmod 06755 "$x" & chown root:shell "$x";done; << "$CMDS";chcon "$x" u:object_r:su_exec:s0;setenforce "$SM";"
{
"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"
}
Note:
The 428 commands provided all are ELF32 binaries, so 32-bit:
That doesn't have to stop you from using them on a x86_64 PC because a 64-bit CPU can handle 32-bit commands.
Hmm... Great Work
I am getting an error on the last command.
/system/bin/sh: here document '$CMDS' unclosed
I tried the method in your toybox thread but it doesn't connect to wsa.
I think it is looking on the wrong port from the looks of the script. I am just trying to get root. I updated my rooted build of wsa and it no longer would load. i have tried different ones making sure to remove the one from the microsoft store first. Installing the one from the microsoft store by installing the amazon store gets wsa working again but without root and without my userdata.vhdx that I backed up. Any help would be appreciated. Thanks
Supported exFAT only 1 Variant
LeOS-T April 2023 Only
============================
Step to install LeOS-T GSI Variant.
DOWNLOAD--firmware from https://samfw.com/
0. Create patch-recovery for fastbootD
☆☆☆ FastbootD video tutorial : https://m.youtube.com/playlist?list=PLvggR4skCxYzhB3SXxpSx4LvRzGwx9k45
1.Create Magisk_patch
patch 2 files (boot.img ,vbmeta.IMG) with Magisk.
2.Include 3 patched files into one tar called 3in1.tar
Enter into Download Mode.[Tablet]
3.flash Stock firmwares(AP, BL,CP, CSC,) and patched file
(USERDATA 3in1.tar)with Odin.
(Flashing Clean Stock Firmware with Root & Recovery patched)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3.1 Reboot with no log-in google account or updated anythings.
3.2 Connect internet.
3.3 Open Developer options.
-Enable OEM unlock
-Enable USB Degugging
-Test Authorizing to your Computer for accessing this tablet.
Code:
adb devices
3.4 Download GSI
and (extract "xxx.img" to platform-tools folder on Computer.
3.flash GSI with fastbootd commands.
Code:
adb reboot fastboot
fastboot erase system
fastboot flash system LeOS-T-VNDKLITE-arm64-bvN.img
# If founded "No spaces to resize partition error"
Code:
fastboot erase product
fastboot resize-logical-partition product 0x0
fastboot getvar all
# (bootloader) partition-sizeroduct:0x0
# FastbootD Menu select
-Enter Recovery
# Recovery Menu select
-Wipe data/Factory reset
confirm
-Reboot system now
------End install GSI-----
**Note: Default Launcher (LeOS Launcher + Neo Launcher) are not suitable for tablet.(lot of bugs) then i try to uses new default AOSP home launcher.
Remove: (if your had RW System)
Code:
adb shell
su
mount -o rw,remount /
rm -R /system/app/Launcher
reboot
4. CREATE NEW LAUNCHER.
4.1)-Flash Magisk modules. and reboot
4.2)-(1.run"Launcher3QuickStep.apk" 2.run"ThemePicker.apk"
New Pop-up Taskbar Navigation.(Split screen /MultiTask by float Taskbar navigation.)
(works when Smallest width > 600 dp )
Vertical screen view
Horizontal screen view.
Home Settings
Dev options to open float taskbar menu.
5.Changes Offline Charging behavior. (Testing)
-Copy hw to /sdcard/Download
Code:
adb shell
su
mount -o rw,remount /
cd /sdcard/Download/hw
cp -R *.* /etc/init/hw/
HOWTO CHARGING:
1. Switch On
2. Insert power cable during Screen Locked .
3. Press power On-off button for checks remain battery .
6.List of testing software
FairEmail
Simple Gallery Pro
Nekogram X
Launcher 3
Retro Music
Vega Bobo DSU
file app (tablet view)
reserved. no.1
Update new version without lost your data.
1. Test new update GSI is compatible with current your installation. with Vega Bobo DSU SideLoader. new version 2.03
2. Flash the new update overwritten old GSI by fastbootD. (Dirty Flash)