Related
Instructions for flashing a phone or tablet device with Ubuntu
What to expect after flashing
Flashing the device
Step 1 - Desktop Setup
Setup the Touch Developer Preview Tools PPA
Step 2 - Device unlock
Step 3 - Initial Device Setup
Step 4 - Deploying Image to Device
Restoring Android
Need help?
The Ubuntu Touch Developer Preview is intended to be used for development and evaluation purposes only. It does not provide all of the features and services of a retail phone and cannot replace your current handset. This preview is the first release of a very new and unfinished version of Ubuntu and it will evolve quickly. If you want to install this release, please follow the guide provided, which details the available features and how to navigate the user experience.
This process will delete all data from the device. Restoring Android will not restore this data.
What to expect after flashing
For detailed information check the release notes
Shell and core applications
Connection to the GSM network (on Galaxy Nexus and Nexus 4)
Phone calls and SMS (on Galaxy Nexus and Nexus 4)
Networking via Wifi
Functional camera (front and back)
Device accessible through the Android Developer Bridge tool (adb)
Supported devices and codenames
The table below lists the supported devices and their corresponding factory images, should you want to switch back to Android. The images can be found here.
Device
Codename
Factory firmware from Google
Galaxy Nexus
maguro
takju or yakju
Nexus 4
mako
occam
Nexus 7
grouper
nakasi or nakasig
Nexus 10
manta
mantaray
Flashing the device
Step 1 - Desktop Setup
The following steps are required on your desktop system that you'll need in order to flash and communicate with the device.
Setup the Touch Developer Preview Tools PPA
The PPA has the tools and dependencies to support Precise, Quantal and Raring. Add the Ubuntu Touch PPA by adding the following custom source list entry to your /etc/apt/sources.list file.
sudo add-apt-repository ppahablet-team/tools
Then do the following:
sudo apt-get update
sudo apt-get install phablet-tools android-tools-adb android-tools-fastboot
Step 2 - Device unlock
If the device is already unlocked, skip to Step 3. These steps will wipe all personal data from the device.
With the device powered off, power on the device by holding the Power button + volume up + volume down.
The device will boot into the bootloader.
Plug the device into the computer via the USB cable.
On your computer, press Ctrl+Alt+T to start a terminal. Type sudo fastboot oem unlock, followed by Enter
On the device screen, accept the terms of unlocking.
Boot the device by pressing the power button (pointed by an arrow with Start on the screen).
Step 3 - Initial Device Setup
Follow these initial steps on your device:
If not booted, boot the device into Android
Enable USB debugging on the device
on Ice Cream Sandwich (version 4.0) go to Settings and turn on USB Debugging (Settings > System > Developer options > USB debugging).
on Jelly Bean (versions 4.1 and 4.2) you need to enter Settings, About [Phone|Tablet] and tap the Build number 7 times to see the Developer Options, activate USB Debugging via Settings > Developer options > USB debugging.
on 4.2.2 you will need to accept a host key on the device, if you already had adb installed, do the following
On the workstation-> adb kill-server; adb start-server
Plug the device into the computer via the USB cable.
Depending on the installed Android version, a popup will show up on the device with the host key that needs to be accepted for the device to communicate with the workstation.
Save the version of the current image on the device, if on Android, to use as a reference to revert back to. The version can be found by going to Settings > About Phone > Build Number.
Step 4 - Deploying Image to Device
To install the Ubuntu Touch Developer Preview on your device, you will need to execute the command below. Please note, this will wipe the contents of the device so ensure you have made a back-up. To install and get updates, run the following command:
phablet-flash -b
The -b performs a full bootstrap on the device. If the device is already unlocked it will carry on. If you have already bootstrapped once and want to install a daily just do:
phablet-flash
This will deploy the latest build onto your device. Your device should reboot into the Ubuntu Unity shell.
Note: the files are saved in Downloads/phablet-flash.
Restoring Android
The Ubuntu Touch Preview image is not for everyone and may not suit your current needs (yet). If you wish to roll back to an Android factory image, follow these steps:
Recall the version that was installed before flashing.
Download the factory image corresponding to your device's model and version (initial table has links).
Ensure the device is connected and powered on.
Extract the downloaded file and chdir into the extracted directory.
run adb reboot-bootloader
run ./flash-all.sh (use sudo if lack of permissions on the workstation don't allow you to talk to the device).
Your device should boot into Android after the process is finished.
Click to expand...
Click to collapse
Need help?
If you got lost somewhere, you found a bug or need some help, we're happy to help you. The Touch Developer Preview is put together by a community of many, who are eager to work together with you on this.
If you've got any troubles or questions with these installation instructions, there's a community willing to help: just ask on Ask Ubuntu!
You can also:
Join us on IRC in #ubuntu-phone on irc.freenode.net and/or
Join our mailing list by
Joining the ubuntu-phone team on Launchpad and
Enabling the team mailing list at https://launchpad.net/~/+editemails
Touch/Install (last edited 2013-02-21 17:04:03 by dpm)
The material on this wiki is available under a free license, see Copyright / License for details.
xD
I wonder if we could have in future, flashable zip Ubuntu image for recovery
albsat said:
I wonder if we could have in future, flashable zip Ubuntu image for recovery
Click to expand...
Click to collapse
In due time brother. I am sure we will be able to get it flashable.
flashable zips for ubuntu for android, via a custom recovery http://www.droid-life.com/2013/02/2...view-on-a-nexus-device-using-custom-recovery/
and yea, this thread needs to be moved. you arent developing anything here, just providing instructions(from another site). doesnt belong in development.
You copied this from canonical page. There is already a thread with the flash able .zip instructions. This thread is on the wrong place and its unnecessary.
Sent from my Galaxy Nexus using xda app-developers app
All things aside.....thuis looks very promissing when iets stable andere 100%functional and working
Sent from my Galaxy Nexus using xda app-developers app
I think they will create the section: Galaxy Nexus Ubuntu Development
Now we wait for the threads asking how to do this.
simms22 said:
flashable zips for ubuntu for android, via a custom recovery http://www.droid-life.com/2013/02/2...view-on-a-nexus-device-using-custom-recovery/
and yea, this thread needs to be moved. you arent developing anything here, just providing instructions(from another site). doesnt belong in development.
Click to expand...
Click to collapse
I haven't flashed Ubuntu yet, but I was wondering if I can can just restore my current rom through twrp recovery. I wasn't sure if Ubuntu changes the recovery on my phone when I flash it.
eqjunkie829 said:
I haven't flashed Ubuntu yet, but I was wondering if I can can just restore my current rom through twrp recovery. I wasn't sure if Ubuntu changes the recovery on my phone when I flash it.
Click to expand...
Click to collapse
Yes u can just restore
Sent from my Galaxy Nexus using xda premium
Esteway.619 said:
Yes u can just restore
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I read somewhere that we need to reflash kernel if we want to restore Android again. I really don't know if it's true.
Closed, please go here >>> http://forum.xda-developers.com/showthread.php?p=38351018#post38351018
Hello, i have one question.
I have a Samsung Galaxy Tab 3 7.0 ( SM-T113 ) i can't find any rom and root package for my pad.
Maybe someone can help me?
I support this request. The T113 is a new device. I was thinking of getting me a cheap t110, but the t113 is also cheap. If it would be possible to root this I would take it.
Rooting SM-T113
Hello everybody
I struggled to root my Samsung Galaxy Tab 3 Lite
(SM-T113). So I decided to shared my experience and writing this tuto.
Of course, this is "a non standart" device, and elements for rooting
SM-T110 or SM-T210 didn't work. Android version of this device is 4.4.4
Methodology and tries :
I have proccured myself the Samsung official firmware (here). This image
allow me to get back during beetwen the experimentations. I tried several
experimentation and restore the device after each fail.
Installing with Odin the Clockworkmod (CWM) for SM-T110 , for SM-T210, and
SM-T211. (Has preconnised here) Each time, when loading the CWM, I got a little
(1 ascii character) exclamation mark at the top-left of the screen. The device
didn't boot on recovery
Installing with Odin the (TWRP) for SM-T110. Same symptom
Installing philz_touch : against the message with only the red exclamation
mark.
I conclude of checked of some signature before executing recovery.
Using Kingo root application : software try to root during 20 minutes and
finaly fail.
Using Towel root application : The device isn't reconized
Conclusion: Security breach for rooting have been fixed in this version of android
I have downloaded UPDATE-SuperSU-v2.46 for android. The idea is to push this
application by the standart android update way. (native recovery).
Sending the zip archive 'as is' => failure to check the whole archive
Re-sign the archive with the autosign tools => failure to check footer of archive
Rewriting the update-script (see here) and (here) and auto-sign the archive
: failure to check footer
I am procured myself some pre-rooted image. Odin fail to import them. (and I
have no succed to use heimdall for linux on my debian)
I have try to improve the official samsung Image by adding root manually , using
simg2img and make_ext4fs. Odin fail at the same point
It's remaining me two way : Or I try to generated a correct update file, or I
try to understood why odin fail to import prerrooted system and my custom
image. I choosed the second option.
The offical update is splited by several blocks, each block having is own
header. A master header provide global information about the image (number of
blocks, size, ...). I have putting some spies in simg2img and
observate the headers of official update and of my custom uptate. Result is
surprising : It is missing 4 bytes by headers. in custom update. According to
samsung orginal update, missing values seem to be constant. I suppose it's a 'magic
number', checked by the device to be sure the 'good' update is applied. So I
modifed this headers in make_ext4fs for adding the missing constants. My custom update is now
accepted by my devices, and I got root (!)
I will now describe how to generate and import this update.
DISCLMAIMER
I or Xda-developers are not responsable of any damage one your device, in particular if you bricked it
You waranty will probably void
Rooting device may lead to some dysfonctionnement, or may open some security breach. You are the only responsable.
1. What do you need :
Your device, and a cable to connect it to your PC
A Windows distribution, with Odin (www (dot) samsungodindownload (dot) com/) and the samsung drivers (www (dot) samsung (dot) com/us/support/owners/product/SM-T110NYKAXAR#")
A Linux distribution, with the appropriate compilation package (build-essential), and with git.
A way to transfers big files beetwen your Linux and your Windows.
The Official samsung update (best-tech-reviews (dot) com/update-sm-t113-t113xxu0aoa4-android-4-4-4-2152 or rapidgator (dot) net/file/7140bfdc421eea86eda5a5cbca00216e)
The UPDATE-SuperSU-v2.46 in zip format (download (dot) chainfire (dot) eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1") (or root program for your android)
Method assume you never installed root on your device
2. Generate the update
Uncompress the Samsung official image.
Code:
unzip image_official.zip
tar -xf image.tar.md5
Uncompress and make_ext4fs and simg2img (here)
Code:
cd ..
git clone https:// github.com/YuLaw/ext4-utils.git
cd ext4_utils
Download and applied the patch (see attachment)
Code:
patch -p1 < ../patch_ext4_utils.diff
Build ext4_utils
Code:
make
Extract the image
Code:
cd ..
unzip DBT-T113XXU0AOA4-20150121104149.zip
tar -xf T113XXU0AOA4_T113OXA0AOA4_HOME.tar.md5
ext4_utils/simg2img system.img system.img.raw
Mount the image
Code:
mkdir mount_point
sudo mount -o loop,rw system.img.raw mount_point
unzip the UPDATE-SuperSU-v2.46
Code:
mkdir UPDATE-SuperSU-v2.46
mv UPDATE-SuperSU-v2.46.zip UPDATE-SuperSU-v2.46/
cd UPDATE-SuperSU-v2.46/
unzip UPDATE-SuperSU-v2.46.zip
cd ..
Now, copy common file and armv7 one the mount_point. If you use an other
device, replace the armv7 repository by the appropriate repository according
to your device processor. You can refer to the
UPDATE-SuperSU-v2.46/com/google/android/update-binary to find them.
Code:
sudo cp UPDATE-SuperSU-v2.46/armv7/{su,supolicy} mount_point/xbin
sudo cp UPDATE-SuperSU-v2.46/armv7/su mount_point/xbin/daemonsu/
sudo cp UPDATE-SuperSU-v2.46/armv7/libsupol.so mount_point/lib
sudo mkdir mount_point/etc/init.d
sudo cp UPDATE-SuperSU-v2.46/common/99SuperSUDaemon mount_point/etc/init.d
sudo cp UPDATE-SuperSU-v2.46/common/Superuser.apk mount_point/app
sudo mv mount_point_app/etc/install-recovery.sh mount_point/etc/install-recovery.bak
sudo cp UPDATE-SuperSU-v2.46/common/install-recovery.sh mount_point/etc
sudo chmod 0755 mount_point/xbin/daemonsu
sudo chmod 06755 mount_point/xbin/su
sudo chmod 0755 mount_point/xbin/supolicy
sudo chmod 0644 mount_point/lib/libsupol.so
sudo chmod 0755 mount_point/etc/install-recovery.sh
sudo chmod 0744 mount_point/etc/init.d/99SuperSUDaemon
sudo chmod 0644 mount_point/app/Superuser.apk
We will regenerate the file system. Do not umount them. If patch on
ext4_utils is not applied, you shall applied it now.
Code:
mkdir output
sudo ext4_utils/make_ext4fs -s -a system -l 1500M output/system.img mount_point
cd output
tar -cf system.img system.img.tar
md5sum -t system.img.tar >> system.img.tar
mv system.img.tar system.img.tar.md5
You can now transfert this file to your windows operating system.
3. Android prepartion
You must ensure your device is allowed to install apk from untrusted source. See
in option/application or in developper menu option
Connect the android to you pc.
Boot your android device into downloading mode. On SM-T113 Samsung galaxy Tab3 lite,
press power, volume down and pad when booting.
Run odin, ensure Repartion is NOT checked, and select the AP (PDA) button. (The
only checked case is autoreboot and F.Reset time) Load the previously generated
file and click start.
Your android device may now reboot and install the root application.
Congratulation, you have now rooted your device. You can clean up the downloaded files.
4. One of these step fail, what I can do to come back. :crying:
You may import with odin the official samsung firmware or proceed to a factory return from the recovery.
5. May I eat my devices if I can't root it ?
Samsung user manual say to not do it.
samsung tab 3 sm-t113 root
Thank for the update about for the root. But I don't have Linux and I don't know how to use Linux too. It's there a way without Linux
If you don't have linux, you can try using Cygwin. This is a linux like environment running on Windows.
or if you find my solution is too complicated, I do it for you.
Warning: before following the next step, ensure your device is Samsung Galaxy Tab 3 Lite SM-T113
Simply download the file :
https://drive.google.com/file/d/0Bwao3SgtdOPPYm9XNF8wQXEyWjg/view?usp=sharing
unzip file and upload it to you device with Odin
Nb: This file will remain on my google drive until I need space or until I decide to remove it. (in a long time)
grizzlyfute said:
If you don't have linux, you can try using Cygwin. This is a linux like environment running on Windows.
or if you find my solution is too complicated, I do it for you.
Warning: before following the next step, ensure your device is Samsung Galaxy Tab 3 Lite SM-T113
Simply download the file :
unzip file and upload it to you device with Odin
Nb: This file will remain on my google drive until I need space or until I decide to remove it. (in a long time)
Click to expand...
Click to collapse
Thank you for your great work!!
Do you think the package will work also with Tab3 lite SM-T116? (Sm-t116 should have only the 3g module more than sm-t113)
Root Worked
Thanks for the your great effort grizzlyfute.
Worked perfectly and finally got my device rooted
beodev said:
Do you think the package will work also with Tab3 lite SM-T116? (Sm-t116 should have only the 3g module more than sm-t113)
Click to expand...
Click to collapse
No. Package will erase the system partition, including configuration file (/system/etc), and probably some drivers. Importing the SM-T113 package will probably put the 3G module out of service.
I suggest you to procure an 'official firmware' for your device (see in Settings/about for the exact version) and follow procedure in post#3.
grizzlyfute said:
No. Package will erase the system partition, including configuration file (/system/etc), and probably some drivers. Importing the SM-T113 package will probably put the 3G module out of service.
I suggest you to procure an 'official firmware' for your device (see in Settings/about for the exact version) and follow procedure in post#3.
Click to expand...
Click to collapse
I tried to follow your linux-instructions (by using cygwin, with an official sm-t116 firmware), but something go wrong (i think cygwin doesn't know batch commands like "sudo", or "su" etc..).
I put your md5 file to my sm-t116: the results is that the device is rooted, but no network connection works (Wi-Fi too) .
I jump back to the original firmware, maybe in the future someone will develop the firmware for the sm-t116 version.
Thank you for the Help
Thanks buddy! It works! :good:
Just got my t113 today and now rooted. Awesome!
Light at end of tunnel
grizzlyfute said:
...
Warning: before following the next step, ensure your device is Samsung Galaxy Tab 3 Lite SM-T113
Simply download the file :
https://drive.google.com/file/d/0Bwao3SgtdOPPYm9XNF8wQXEyWjg/view?usp=sharing
unzip file and upload it to you device with Odin
...
Click to expand...
Click to collapse
FABULOUS!!! And thank you! And have i said fabulous? And thank you??? And this, only for giving me rooting hope!
I am a proud user of a gt-i9100 for a few years, rooted/unlocked/custom rom(ehndroix), so, all the 9 miles, but, that´s the phone... And since i am not very proficient when it comes to using odin, and if you don´t write all the steps, i am like a fish out of water (can´t breathe or swim) and i am afraid to do some wrong step.
So, when you say upload it to your device, which will be the parameters in ODIN?
Edit: I confirm, it works, i was afraid of doing something wrong and brick the thingy, but its working fine, thanks to odin and pda and this developpers work!:victory:
!! Thanks !!
I followed these instructions step-by-step on my SM-T113, but for some reason the device would always fail to receive the image I'd built (Odin would just sit there saying NAND Write Start! for a while, then fail. So I tried downloading your precompiled version... and what do you know, it worked straight away.
Thanks a ton, HUGE help!
(q)how to root tab sm-t116nu ?
please help me
cjmac said:
I followed these instructions step-by-step on my SM-T113, but for some reason the device would always fail to receive the image I'd built (Odin would just sit there saying NAND Write Start! for a while, then fail. So I tried downloading your precompiled version... and what do you know, it worked straight away.
Thanks a ton, HUGE help!
Click to expand...
Click to collapse
Sorry for the delay.
I encountered the same problems before I make the patch. Cause of the problem is the file generated by ext4_utils tools is not immediately compatible with the sm-t113 device. I have to add constants in the encapsulation headers for the device to accept the file. You can see details in the patch provided.
To determine theses constants, I put some spies in simg2img and extracts the official firmware. It is not exclude these values change in function of the device.
For the sm-t116, I suggest to open an other thread. I think the works can be picked up and adapted.
wifi issues?
Thanks for your work!
I have successfully rooted my tablet, but its now not connecting to a weak wifi signal it was previuosly connecting to. In fact, it previuosly rratd the same signal as "fair".
Is this connected in any way to the rooting package, and can be resolved somehow?
Hello, thanks for your help! now, i have my Samsung SM-T113 rooted.
but, there any way to put the cmw?
I want to make a backup image and not as .... thanks
Anyone know if this way working in model SM-T113NU ?
Samsung official image ?
grizzlyfute said:
2. Generate the update
Uncompress the Samsung official image.
Click to expand...
Click to collapse
I don't understand what is the "Samsung official image" :
i don't see it neither in the 1. What do you need : list , nor in attached files
I thought it could be "The Official samsung update ", but its name is not "image_official.zip" I see in the first line of code, and moreover I see "unzip DBT-T113XXU0AOA4-20150121104149.zip" in the following lines.
any chance to make more easy the way to get root? btw I have the variant SM-T133NU 4.4.4 KK please!
Minimalistk0 said:
any chance to make more easy the way to get root? btw I have the variant SM-T133NU 4.4.4 KK please!
Click to expand...
Click to collapse
I second that! Rooted custom rom highly appreciated! I'd even pay some bucks
This works only on Linux 64-bit
DISCLAIMER: It is always risky to flash your mobile device. I do not and will not take any responsibility for bootloops and bricks.
Please check carefully that the ROM or recovery.img you want to flash is suitable for your specific device and for the sp_flash_tool. The firmware directory should neither contain meta-inf nor system folder, but something_with_a_scatter.txt and a system.img
Backup your phone before flashing!
Your phone's battery should be at least half charged (50 percent) before you start this.
I successfully ran these steps on my UMI Hammer with Linux Ubuntu 14.04 and 16.04. I do not have other devices or Linux derivates and do not plan to buy/install any.
CREDITS and a zillion thanks to Sergio Rivero for his excellent tutorial on mibqyyo.com!!!!
Also many thanks to N2K1 for giving me some more background information!
So here we go:
Step 1:
If you haven't done so before, install the Linux generic usb-drivers package:
Code:
sudo apt-get update
sudo apt install libusb-dev
Download SP Flash Tool Linux (latest version): http://mtk2000.ucoz.ru/load/soft/soft_mtk/sp_flash_tool/5-1-0-14 (Password to extract currently is mtk2000v3)
or here https://androidmtk.com/smart-phone-flash-tool
In case you haven't done before, install unrar:
Code:
sudo apt install unrar
Extract the downloaded file -> graphic file manager (e.g. Nautilus): double-click and extract. Terminal:
Code:
unrar x path_to_file
(from now on: please adapt paths to your own settings)
Move the new folder „sp_flash_tool“ to a directory of your choice.
Code:
mv /home/username/Downloads/sp_flash_tool /home/username/...
You might also need to install libqtwebkit4 (it just happened to me on Linux Ubuntu 16.04):
Code:
sudo apt install libqtwebkit4
[Only For Ubuntu 16.10 and newer]
Run
Code:
dpkg -x libpng12-0_1.2.54-1ubuntu1.1_amd64.deb /tmp/libpng2
cp /tmp/libpng2/lib/x86_64-linux-gnu/libpng12.so.0.54.0 lib
cd lib
ln -s libpng12.so.0.54.0 libpng12.so.0
These libraries are still required for the flash tool but have been removed from new Ubuntu versions.
Thanks @hanalinqu, @z3r0c00l_2k https://forum.xda-developers.com/showpost.php?p=73484473&postcount=216 and @opticyclic https://forum.xda-developers.com/showpost.php?p=81543495&postcount=285 for this information!
Step 2:
Change into the newly created directory:
Code:
cd /sp_flash_tool
We make one file executable by typing:
Code:
chmod +x flash_tool
In order to avoid running the flash_tool as root user, you need to add a standard user to the usergroup "dialout" (thanks to @egalus for this bit!)
Code:
sudo adduser username dialout
For Arch Linux:
Code:
gpasswd -a username uucp
and activate the membership immediately
Code:
newgrp - dialout
(Arch Linux):
Code:
newgrp - uucp
Step 3:
Now you can open the tool:
Code:
./flash_tool
or double-click on the flash_tool icon.
You can try at this stage if the flash tool connects to your phone:
In the user interface, choose tab „Download“. Hit "scatter-loading", navigate to a directory with a valid firmware for your device and choose the scatter-file.
For testing purposes uncheck "name" and check one of the smaller files in the list below (for example "logo")
Switch off your device. Hit the "Download" button in SP_Flash_Tool and connect your phone to the computer. Some devices require you to take off the battery for about 10 seconds, with others you need to press Vol+ or Vol- while plugging the cable into the phone. Please look up device-specific threads and try out different options.
If nothing happens at all, open a second terminal, run
Code:
dmesg | grep usb
and look out for a MediaTek entry. If there is none → did you install libusb-dev (Step 1?)
If the answer is yes, you might need to create a persistent udev rule for the MTK Preloader:
Code:
sudo gedit /etc/udev/rules.d/80-persistent-usb.rules
Add the following line to the file:
Code:
SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="0e8d", ATTR{idProduct}=="*"
Save the file and exit.
Reload the usb-rules:
Code:
sudo service udev restart
Disconnect the usb data cable from the computer and the smartphone. Close the flash tool. Switch on your phone (fastboot mode will do). Repeat the first paragraph of Step 3.
If the tool connects, within a few seconds a red progress bar will appear. Unfortunately, in my case an error message came along with it:
S_BROM_CMD_JUMP_DA_FAIL (2035)
There is a connection, but also one more obstacle to overcome...
Step 4:
Now we come to the interesting part, which cost me 2 weeks of (futile) research and frustration. Finally I found Sergio Riveros tutorial on mibqyyo. Thanks to him again and again and again for this priceless piece of information
The “modemmanager” package integrated by default within Linux Ubuntu 14.04 and later is not compatible with the MTK Flash Tool for Linux
Click to expand...
Click to collapse
To put it in different words: The modem manager controls port /dev/ttyACM0 and disables the Flash Tool. So we blacklist it for the two MTK vendor IDs the flash tool uses:
Code:
sudo gedit /etc/udev/rules.d/20-mm-blacklist-mtk.rules
You insert these two lines:
Code:
ATTRS{idVendor}=="0e8d", ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{idVendor}=="6000", ENV{ID_MM_DEVICE_IGNORE}="1"
Save the file, exit and restart udev:
Code:
sudo service udev restart
Switch your phone on (fastboot mode will suffice) and off again.
Step 5:
Code:
./flash_tool
or double-click on the flash_tool icon.
Now everything should run smoothly. In case you encounter
Code:
BROM ERROR : S_SECURITY_SF_CODE_FORMAT_FORBIDDEN (6012) , MSP ERROE CODE : 0x00
change the download agent to MTK_AllInOne_DA.bin (screenshot #4)
There are plenty of tutorials on the web for the further steps.
Happy flashing! When a green circle with a white checkmark appears, you are done. You can close the flash tool and disconnect your phone. For a clean start with a new ROM boot into recovery and wipe data/factory reset.
Kudos for the udev rules, I finally managed to root my phone and disable some vendor crap thanks to you!
Thanks, I'm glad to read that it worked for you as well
Great post!
Just wanted to say you saved me HOURS OR DAYS OR WEEKS of time on the modemmanager thing. I have Arch Linux, successfully ported over this tutorial, but I had no idea the modemmanager package was causing the issue. SP Flash Tool was the last frontier for using my Android devices on Linux. Thanks so much!
You are very welcome! Since it took me two weeks to find the cause for "S_BROM_Error [2035]" I wanted to spare other "victims" the experience
This is a very nice, HQ post. Keep up the good work.
But I would like to suggest two corrections:
1) The mv command is unnecessary. you don't have to copy the folder to the root directory to run it as root.
2) Please also add a final step to delete the udev rules so as to re-enable the modem manager after rooting.
Though most of the people who would be reading your thread would be knowledgeable linux users, they won't need these suggestions, but anyways, it would make your guide complete.
Thanks for your feedback @daltonfury42
1) Of course you don't need to move to move the folder to / .As I wrote, you can also use your /home/user directory. But you shouldn't keep it in "/Downloads" or "/tmp", since you might have deleted the folder by the next time you want to use the flash-tool.
Step 2), as you suggest it, is redundant on a private computer, because you blacklist the modemmanager for the flash-tool only, and for nothing else. SP_Flash_Tool uses different Vendor and Product IDs than MTP/USB/ADB/Fastboot mode, and these IDs are not related to your specific device. So the modem manager is up and running - even while you flash - on every other active (network-relevant) usb-port of your computer And it will be up and running on the usb-port you use for the flash-tool when you disconnect the phone and then plug in something else - or the same phone in a different mode... But due to the permanent
Code:
/etc/udev/rules.d/20-mm-blacklist-mtk.rules
entry the modem manager will be automatically blocked if you connect your phone to the SP_Flash_Tool a second time - no matter which port: no further preparations necessary
If you want to check it out, take a look the output of
Code:
dmesg | grep usb
connecting your phone "normally" and compare it with the same command -> output connecting your phone to the SP_Flash_Tool - and/or to the contents of the file "usb_setting.xml" in the SP_Flash_Tool directory My udev rule simply tells the modem manager to ignore two vendor IDs named in that file.
edit: if you "flash" your linux computer more often than your Android device, you should remember to backup the folder and the udev rules
Miss Montage said:
Thanks for your feedback @daltonfury42
1) Of course you don't need to move to move the folder to / .As I wrote, you can also use your /home/user directory. But you shouldn't keep it in "/Downloads" or "/tmp", since you might have deleted the folder by the next time you want to use the flash-tool.
Step 2), as you suggest it, is redundant on a private computer, because you blacklist the modemmanager for the flash-tool only, and for nothing else. SP_Flash_Tool uses different Vendor and Product IDs than MTP/USB/ADB/Fastboot mode, and these IDs are not related to your specific device. So the modem manager is up and running - even while you flash - on every other active (network-relevant) usb-port of your computer And it will be up and running on the usb-port you use for the flash-tool when you disconnect the phone and then plug in something else - or the same phone in a different mode... But due to the permanent
Code:
/etc/udev/rules.d/20-mm-blacklist-mtk.rules
entry the modem manager will be automatically blocked if you connect your phone to the SP_Flash_Tool a second time - no matter which port: no further preparations necessary
If you want to check it out, take a look the output of
Code:
dmesg | grep usb
connecting your phone "normally" and compare it with the same command -> output connecting your phone to the SP_Flash_Tool - and/or to the contents of the file "usb_setting.xml" in the SP_Flash_Tool directory My udev rule simply tells the modem manager to ignore two vendor IDs named in that file.
edit: if you "flash" your linux computer more often than your Android device, you should remember to backup the folder and the udev rules
Click to expand...
Click to collapse
@Miss Montage, very informative. Thankyou.
You're welcome - but please do not post full quotes
Hi. Thanks for the tutorial :good:
I'm getting "PMT changed" error with the right scatter when tried to flash bootimg/recovery only.
Where did you get the scatter file? Generally this error code means that the partition table is different to the one on your device. This should only be the case - occasionally - if you flash a complete firmware.
(Or replace Android through Ubuntu / vc. vs.)
Miss Montage said:
Where did you get the scatter file? Generally this error code means that the partition table is different to the one on your device. This should only be the case - here and then - if you flash a complete firmware.
(Or replace Android through Ubuntu / vc. vs.)
Click to expand...
Click to collapse
I know this error, so I am surprised
scatter is from my stock rom. Same i used to flash.
Hmm, dunno why that is. Can you compare the scatter.txt to the /proc/emmc file on your phone?
And at what stage do you get the error? Immediately after connecting or later?
Miss Montage said:
Hmm, dunno why that is. Can you compare the scatter.txt to the /proc/emmc file on your phone?
And at what stage do you get the error? Immediately after connecting or later?
Click to expand...
Click to collapse
Right now I remembered in windows long ago got the same problem.
This happens if I try to use flash sp tool new versions
In windows:
Working: v5.1352.01
Not Working: v5.1512.00.000
Click to expand...
Click to collapse
The sp_flash_tool_linux 5.1520..... worked perfect for me though... Have you tried an earlier version?
Miss Montage said:
The sp_flash_tool_linux 5.1520..... worked perfect for me though... Have you tried an earlier version?
Click to expand...
Click to collapse
SP_Flash_Tool_Linux_v5.1452.00.100 tested, same problem.
SP_Flash_Tool_Linux_v5.1436.00.100 also tested and same.
No older versions found
The version v5.1504.00.100 works on my 64-bit-system, too... But the error seems to be caused by something else. Have you checked the SP logfile?
Have you also tried the newest version? I just involuntarily re-flashed my UMI Hammer with it... Wanted to choose the twrp only, but too much multi-tasking leads to no good
Miss Montage said:
The 32bit-version v5.1504.00.100 works on my 64-bit-system, too... But the error seems to be caused by something else. Have you checked the SP logfile?
Click to expand...
Click to collapse
Tested and same.
Here logs
Hmm, I will compare these lines to a successful log:
08/13/15 23:57:01.942 BROM_DLL[6767][6774]: FlashTool_ReadPartitionInfo(0x7f7b840038a0,0x7f7b84013310,0x7f7b00000013): mutex: LOCK ... (mutex.cpp:151)
08/13/15 23:57:01.942 BROM_DLL[6767][6774]: FlashTool_ReadPartitionInfo(0x7f7b840038a0,0x7f7b84013310,0x7f7b00000013): mutex: UNLOCK. (mutex.cpp:166)
08/13/15 23:57:01.943 BROM_DLL[6767][6774]: FlashTool_Disconnect(0x840038A0): mutex: LOCK ... (mutex.cpp:151)
Click to expand...
Click to collapse
View attachment 5376913
What is it? What is Ubuntu Touch?
Ubuntu Touch, as comes from naming, is Ubuntu managed to run on phone.
Well, Canonical abandoned it, so community organization, UBports, now develops, maintains, and ports UT to new devices.
And this is what the thread is about. The amount of devices able to run UT was 63(as written on website at the time of writing this post). But now it is 64 devices.
The 64th port to Xiaomi Mi 8.So, lets talk now what works, and what is not(you will also be able to see that on website, as soon as merge request will be accepted).
What works:
Actors
Manual brightness(auto seems not supported by UT, idk)
Notification LED
Vibration
Torchlight
Camera
Flashlight
Photo
Video
Switch between front and rear cameras
Cellular
Carrier info
Calls
SMS
Audio routings (switching between main speaker, and phone speakers)
Volume control
Misc
Battery percentage
Online charging(while phone is on, or in sleep/standby state)
UBports recovery
Network
WiFi(2.4GHz, 5GHz)
Bluetooth
Hotspot(partially, seems that 5G is not supported)
Flight Mode
Sensors
Fingerpring
GPS
Rotation
Touchscreen(ofc, otherwise I would write this post)
Sound
Microphone
Earphones
Loudspeaker
Volume Control
USB
ADB
MTP
Several things, are not tested, such as Wireless Display, NFC, SIM PIN Unlock, MMS, Dual SIM.
Non working features are Offline Charging, Auto-brightness, Proximity Sensor(you need to click the Power Button, that won't stop the call).
Big thanks to TheKit who helped me with the port.
TheKit's Gitlab and UBports forum profile.
Right now, config for UBports Installer is waiting approval of pull request, and merge request for devices.ubuntu-touch.io is still not approved, you will have to do everything manually. UBports Installer config PR finally merged, but only Global versions are supported, since firmware files that are flashed by Installer are for Global. If you do install, be sure to flash vendor and firmware packages for your variant after.
WARNING! YOU MUST HAVE UNLOCKED BOOTLOADER! EVERY THING YOU DO, YOU DO ON YOUR RISK, IF YOU BRICKED DEVICE, THATS YOUR FAULT, NOT MY! I DO NOT TAKE ANY RESPONSIBILITY FOR YOUR BRICKED DEVICE!
Preparations before installation.
Flash TWRP recovery
You need to download and flash stock firmware and vendor from Android 9, MIUI V11.0.6.0.PEAMIXM(be aware that this Vendor+Fw is for Global, if your Device is Chinese or Russian variant, or any other, flash vendor package according your phone variant). It is compressed into ZIP file, so you will have to flash it though TWRP. Do not use adb sideload, push file to any directory you want, and install it from phone.
Download boot.img, system.img, recovery.img from here.
In TWRP go to "Wipe" ==> "Format Data" ==> Type "yes" ==> Enter. Then go to Reboot ==> Recovery. After restarted. Again go to Wipe ==> Advanced Wipe, and select all partition except USB-OTG
Now we have two ways of installation, from TWRP, and from Fastboot.
TWRP
On PC:
Code:
$ adb push system.img /tmp
$ adb push boot.img /tmp/
Now go to "Install"
Get to /tmp/ directory
"Install Image"
Flash boot.img to Boot partition, system.img to System.
Then reboot to system.
If system works, reboot to TWRP again and push recovery.img to /tmp/, then flash it to Recovery partition.
Fastboot method:
Code:
#Simple as that
$ fastboot flash boot boot.img
$ fastboot flash system system.img
$ fastboot flash recovery recovery.img
#Flash recovery only after you are sure system works.
Or you can just install a installable zip archive I've recently made. All my builds will be hosted on GitHub Releases on my repo. New builds will come by every new official OTA release. UBports recovery is not included, installation goes proceeds from TWRP, install just as simple as custom ROM installation. Btw, do you want me to add notch patches to system image, so it doesn't look awkward?
Note: this zip is not signed, so disable signature verification before installing, or installation will fail.
Optionally you can adjust your panel so it doesn't look weird. Rn idk how to move panel below the notch(display cutout, I hate Apple for that). It moves buttons in Panel below, and adjusts height of the panel. This repo will do everything for you. Just download it to device. And run apply-notch-hax.sh. It will automatically find device name, apply patches, and restart Unity.
Note: run the script as standard user, not root.
Note2: if you get bootloop, wipe system, format data, restart bootloader, flash everything again, but before rebooting to system try flashing SELinux permissiver. And don't flash Magisk, it's useless, and may destroy your system.
Device source: Gitlab
Kernel source: Gitlab
Gitlab CI build artifacts: Gitlab
Join Telegram support group if you need any help.
See all supported devices at official website.
P.S. Since you have to use fastboot, and UBports Installer uses fastboot, there may be some difficulties for Ryzen CPU users. I attached zip file with executable (.bat file). It will allow you use fastboot with USB 3.x + Ryzen. Unpack it. And run .bat file as admin. Reboot. Voila, fastboot works as should.
Linux users should either use another laptop with Intel CPU, or flash from Windows, or use USB 2.0 hub.
P.S.S. Ok, I managed to get GitHub CI to work, so now if any of you want to test fixes and new features, head to this GitHub repo, and download artifacts from "Make OTA images"(in Actions tab), and flash them using fastboot.
Amazing work! I've always wanted to port UBTouch to Mi 8 but I couldn't get WiFi and mobile data to work on my attempts. As my primary phone, I needed it to be online as much as possible. Really happy to be able to use it on our devices
I've noticed an issue (I haven't managed to recreate this however):
- The OS can't switch between audio outputs, for example I need to restart my phone to hear sounds from loudspeaker after making a phone call. Please let me know if there's a workaround for this issue.
I'll be looking out for more issues to report. Once again, thanks for this port it's amazing
someone plz port Ubuntu to poco f1 too
gamerlucky said:
someone plz port Ubuntu to poco f1 too
Click to expand...
Click to collapse
It is already ported, a long before Mi 8
@itagizade have you tried waydroid on this?
nSKN3i said:
@itagizade have you tried waydroid on this?
Click to expand...
Click to collapse
No still not.
this amazing work. i have ran some x11 app on my phone,jt works. now i can say hava a pc in my pocket . one problem i found is system partion size too small (only 3g), this not enough if i want install more linux package lije chrome firefox
I updated download link, so if you have already flashed everything, I suggest you to flash a new recovery, as previous one, identified device as Mi MIX 3.
it is still complex for my level of knowledge to install this rom on my Mi 8 and it is with great joy that we have a port like this from Ubuntu Touch and that in the future it will be easier to install and maybe other ports as well as SailfishOS in the menu. Mi 8 great job Dev.
itagizade said:
It is already ported, a long before Mi 8
Click to expand...
Click to collapse
link please
gamerlucky said:
link please
Click to expand...
Click to collapse
See on devices.ubuntu-touch.io.
tried it out and worked great, glad to see something different, keep up the excellent work bro!
hey i was wondering about file system can we use f2fs ?
I tried installing apk files but getting error
Also notch fix gives me this error in terminal
EDIT: nevermind the apk i forgot to run anbox-tool install
EDIT2: nevermind notch fix i just pushed the file to downloads and run sh command
Amazing work! It is the fastest rom I have ever installed! The SIM PIN unlock works well and the offline charging partially (approximately, five minutes after connecting the charger). I hope NFC works, too. In the future, it would be nice if apply-notch-hax.sh was fixed (error, line 57). Anyway, thank you for porting and providing this rom!
For Waydroid support, there are some instructions here. To start the container service, use the following command:
Code:
sudo waydroid container start
Advanced Gears said:
Amazing work! It is the fastest rom I have ever installed! The SIM PIN unlock works well and the offline charging partially (approximately, five minutes after connecting the charger). I hope NFC works, too. In the future, it would be nice if apply-notch-hax.sh was fixed (error, line 57). Anyway, thank you for porting and providing this rom!
For Waydroid support, there are some instructions here. To start the container service, use the following command:
Code:
sudo waydroid container start
Click to expand...
Click to collapse
Glad you enjoy it. Right now I'm a little busy, but asap I will continue the work on this. Gotta make it daily-driver ready.
About error with `apply-notch-hax.sh`, other people have successfully used that script. Could you please specify the error?
The touch has been dead since I flash This rom
MilkywayOpenSource said:
The touch has been dead since I flash This rom
Click to expand...
Click to collapse
You mean Touchscreen is not working? Did you change you stock panel?
No,
MilkywayOpenSource said:
No,
Click to expand...
Click to collapse
Is your device Chinese version, or any other that Global?
It is global and after I install Ubuntu touch the screen never response to touch even in twrp
Teclast M40 Pro DiscoveriesVarious helpful points of knowledge to unlock your bootloader, to root, and use your tablet.
Problem: Where can I obtain the official firmware?
Solution: Teclast Website
Usage: type M1A3 in search
Problem How can I unpack "pac" files?
Solution: Build C utility divinebird / pacextractor
Solution: Download pre built Linux executable pacextractor.zip
Usage: >./pacextractor Firmware.pac
Bash:
git clone https://github.com/divinebird/pacextractor
cd pacextractor
make
Problem: I need tools to flash my device
Solution: Download the latest SPD Upgrade Flash Tool SPD_Upgrade_Tool
Problem: msvcr100.dll missing error in Windows whilst running SPD (Factory/Research/Upgrade) Tools
Solution: Download and install 2010 Visual C++ Distribution
Problem: I want to unlock my bootloader. (Window and Linux kit)
Solution: Download TeclastM40Pro_Unisoc_UnlockTools.zip
Usage: Read readme file.
Problem: How can I remove the dm_verify warning on boot up after unlocking the bootloader?
Untested Solution: digitally sign the vbmeta partition and write it back. See [Tutorial] How to create a custom signed vbmeta.img
Problem: I want to root my device.
Solution: Modify boot.img with Magisk, then sign.
Usage: Upload to your device's download directory, the current boot.img read from your device, or from the same version firmware. Then install Magisk app from here. Use Magisk to patch the boot.img. Sign the partition. Then flash back the signed magisk version of boot.img to "boot_a" partition. Guide to flashing single partition at Hovatek Website
Problem: I need to emergency flash my device?
Solution: Currently only from Windows, use SPD Upgrade Tools to reflash firmware.
Usage: From the tablet powered off, or if boot looping. Hold down the power-button and volume-down for five seconds, release the power-button, and keep the volume-down button still held for another five seconds, then release or release if the detected earlier. Windows and SPD tools should then detect your device to flash.
Problem: I want to improve my Telcast M40 Pro
Solution: List of suggested apps below;
FDroid App Store F-Droid Website
Aurora > via FDroid. App store allowing the direct download from Google Playstore, without your own account.
Lawnchair > via FDroid. Fast open source sophisticated launcher.
AdAway > via FDroid. Removes adverts whilst using apps.
TrackerControl > via FDroid. Manages apps access to internet, and blocks spyware and trackers.
.
Problem: I want root mode without the effort of hacking a rom partition.
Solution: For those with World version Teclast M40 Pro device, here is a signed rooted boot partition I created. Read the readme file inside the zip. You will require an unlocked device, windows setup with USB drivers for Teclast, the complete firmware from Teclast website, and SPD Update Tools installed. If you're successful, then on rooting you will need to install Magisk app to get root active. Magisk will reboot once to finalise.
Download : TeclastM40Pro_ROW__v1p0_signedboot_magiskrooted.zip
Download : TeclastM40Pro_ROW__v1p2_signedboot_magiskrooted.zip
SPD Upgrade Tools is closing while trying to flash stock firmware, both with M40 Pro locked and unlocked bootloader. What should i do?
laurorual said:
SPD Upgrade Tools is closing while trying to flash stock firmware, both with M40 Pro locked and unlocked bootloader. What should i do?
Click to expand...
Click to collapse
Sorry for replying late. I got no indication of the response. To the problem, I can only suggest getting a different version of SPD or m aking sure your computer system is properly updated. I hope you've already solved the issue!
Maybe you're experiencing, "Problem: msvcr100.dll missing error in Windows whilst running SPD (Factory/Research/Upgrade) Tools" See above for solution.
I've noticed a new ROM for world edition, "M40 Pro(M1A3)_Android 11.0_ROW V1.02_20220525", but not getting any system update options for OTA. People flashing their systems may want the latest firmware!
Thanks to your Magisk file I was able to root my tablet, but when updating to the latest version it goes into bootloop, I have tried updating the original firmware image again, but it also goes into bootloop.
Is there any way to install Magisk modules?
Thanks for your post, it helped me a lot to unlock my tablet.
Edit: My version is the M1A1 firmware V1.03_20210804
Edit 2: Finally, when updating my tablet with the root file that is in the post, it did not allow me to install any Magisk module, the solution is to download version 24.3, and update automatically, without changing to a higher version of Magisk
Glad you worked it out Miny !!! Sorry the warning emails for new posts have been going to a gmail account I no longer use.
Also your hardware maybe different and require it's own unique firmware and boot images. It seems the cracking in similar though.
Some questions:
Do I need to unlock my bootloader in order to be able to get root with magisk?
The tools for unlocking the bootloader uses
Code:
fastboot flashing unlock_bootloader
. My version of fastboot (33.0.3p1-android-tools) doesn't have that command. The included one (0.0.0-09219) does, but I wan't to be careful about running softwar from untrusted sources. Where is that version of fastboot from?
Does any of the steps necessary to get root access delete my data?
Hi there.
I have a m40pro (M1A1) running android 11, do you know if I can install firmware Z3A1 to get android 12? Or will be bricked?
Thanks in advance
rubsbcn said:
I have a m40pro (M1A1) running android 11, do you know if I can install firmware Z3A1 to get android 12? Or will be bricked? Thanks in advance
Click to expand...
Click to collapse
To tell you the truth, not sure. Most SoC are impossible or near impossible to brick. They usually allow for an injection or have a read only boot section. Other words you could test. Also research difference in hardware between models, and that may indlicate if something may not work. The kernel/drivers are the improtant aspect.
jorkusjorkus said:
Some questions:
Do I need to unlock my bootloader in order to be able to get root with magisk?
The tools for unlocking the bootloader uses
Code:
fastboot flashing unlock_bootloader
. My version of fastboot (33.0.3p1-android-tools) doesn't have that command. The included one (0.0.0-09219) does, but I wan't to be careful about running softwar from untrusted sources. Where is that version of fastboot from?
Does any of the steps necessary to get root access delete my data?
Click to expand...
Click to collapse
What OS are you using? Google is constantly changing Android Studio and the added modules. Then others may build with options removed. Personally I use Archlinux and load up standalone android-tools from the community repository. Currently v33.0.3-3
Try fastboot --help
Your version may have
Code:
fastboot flashing unlock_critical
minyfriki said:
Thanks to your Magisk file I was able to root my tablet, but when updating to the latest version it goes into bootloop, I have tried updating the original firmware image again, but it also goes into bootloop.
Click to expand...
Click to collapse
What I found works, is when using SPD Research Tool, load up the firmware.pac and then go into settings and click "Select All Files" and again to unselect, which leaves the default required items.
Then manually change BOOT to the Magisk img. Then click on all VBMETA types, and UBOOT_LOADER (may not be required though). Then flash.
You should get bootable tablet (no looping). Warning: UserData partition is written over.
I'll share my Magisk image for v1.2
e8hffff said:
What OS are you using? Google is constantly changing Android Studio and the added modules. Then others may build with options removed. Personally I use Archlinux and load up standalone android-tools from the community repository. Currently v33.0.3-3
Try fastboot --help
Your version may have
Code:
fastboot flashing unlock_critical
Click to expand...
Click to collapse
I'm using the same version as you on the same OS. After some research it seems like unlock_bootloader was removed in this commit from 2018. From what I can tell, unlock_critical does something else (unlock_bootloader runs
Code:
fb_queue_download("unlock_message", data, sz); fb_queue_command("flashing unlock_bootloader", "unlocking bootloader");
while unlock_critical runs
Code:
do_oem_command("flashing", "unlock_critical" and doesn't take the signature argument);
)
I'll see if I can compile the older version with the needed command.
What about my other questions?
Issue: Android not starting. I had the infinite restart when plugged in the usb. I tried to reload the installation package (succeeded), but didn't fixed the issue. Battery was not charging yet. When I started the Teclast M40 pro, the logo showed up, but the tablet turned off again.
Solution: I have disassembled the cover, unplugged the 5 pin plug from the battery for half hour and plugged again. When I tried to turn it on, everything was fine.
dougcwb said:
Solution: I have disassembled the cover, unplugged the 5 pin plug from the battery for half hour and plugged again. When I tried to turn it on, everything was fine.
Click to expand...
Click to collapse
Wow that's weird Doug. Remember this, if you don't already know, that you can do a cold start by holding down the power button for over 10 seconds, on most devices.
I guess you're running now on rooted tablet !!!
e8hffff said:
Wow that's weird Doug. Remember this, if you don't already know, that you can do a cold start by holding down the power button for over 10 seconds, on most devices.
I guess you're running now on rooted tablet !!!
Click to expand...
Click to collapse
I did the installation package process that the Teclast sent me. The last thing they told me to do was keep trying to install the package (wft?). Well, I just open the tablet, unplugged the battery for a while and after that it worked.
Maybe this resolved 2 things:
1-the battery was not properly connected in the first place, so when I plugged the 5 pin to the board it connected as it should.
2- Maybe there is a "memory" in the board attached to the battery that was bricked (or something like that) when I pulled off the plug, this memory was reseted.
BTW, when the tablet came to life again, the battery was at 87%.