[HOW TO] Recover from failed BIOS flash using Raspberry PI - Teclast X98 Air 3G

Need:
-rasperry pi with raspbian (this guide is made with a Model B, Works fine with Raspberry PI 2 also).
-A soldering iron
-One DIL-8 socket
-pata cable + breadboard and some cable for connect the DIL-8 socket to raspberry pi
(If you don't have something similar, you would have to solder the wires directly on the RPI.)
on tablet:
-open your tablet
see this video https://www.youtube.com/watch?v=841pMJC_QOk
-unsolder red battery cable
-verify your bios voltage ( if it's one 1.8V add one level converter like this one)
https://www.sparkfun.com/products/12009
and use one 1.8V DC-DC converter
On your Raspberry:
open a terminal run:
-sudo apt-get install subversion
-sudo apt-get install pciutils-dev
-sudo apt-get install zlib1g-dev
-sudo apt-get install libftdi-dev
-sudo apt-get install libusb-dev
-download Flashrom
svn co svn://flashrom.org/flashrom/trunk flashrom
compile flashroom:
cd flashrom
make
sudo make install
Connect DIL-8 socket to the pi:
{
"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"
}
-Rename your bios file to 1.rom and copy it to /tmp (on th pi)
-Erase the chip :
sudo flashrom -E -V -p linux_spi:dev=/dev/spidev0.0
-Flash bios:
sudo flashrom -w /tmp/1.rom -V -p linux_spi:dev=/dev/spidev0.0
if you don't have one raspberry pi use kelebek version.
http://forum.xda-developers.com/x98-air/help/teclast-x98-air-iii-32-gb-m5c5-t3300747

There is one big missing in your post!!!
RPI' SPI port voltage is 3.3V <> mine X98 ID:C5J8 flash chip is 1.8V !!!!!!!!!!!!!!!!!!!!!!!!
I advice: DON'T try anybody without voltage level translator this procedure!!!

i know that but it's not a problem with teclast bios.
I flash my x98 III M5C5 (GigaDevice GD25Q64(B)) 1.8V bios without problem.
CH341A spi programmer work also in 3.3V.
If you want you can add a level converter like this:
https://www.sparkfun.com/products/12009

I think that IT IS A PROBLEM!!!
What do you say if somebofy follow your instruction and his/her tablet flash chip will be destroyed by 3.3V ?
OTHERWISE your GD25Q64 has 3.3V interface level...
http://www.gigadevice.com/product/detail/5/24.html?locale=en_US

Don't forget peoples who need to do that have a dead tablet,and one flash chip it's not expensive and easy to change.
but i've done some modification on my how to.
ps my bios is a GD25LQ64 (1.8V bios)
Single Power Supply Voltage
-Full voltage range:1.65~2.0V
and i don't bunr anything with 3..3V

How do I check the bios voltage?

What are the pins that we should connect, for the Raspberry Model 2/Model B+?

I get this error:
Code:
[email protected]:/tmp$ sudo flashrom -r test.rom -p linux_spi:dev=/dev/spidev0.0
flashrom v0.9.8-r1924 on Linux 3.12.21 (armv6l)
flashrom is free software, get the source code at https://flashrom.org
Calibrating delay loop... delay loop is unreliable, trying to continue OK.
No EEPROM/flash device found.
Note: flashrom can never write if the flash chip isn't found automatically.
What can this mean? (BTW I haven't unsoldered the battery) Can anyone help me? I would like to have my tablet back...

bad connection with DIL-8 socket. but you should unsolder the battery.

Whenever I connect the clip to the chip, the raspberry pi hangs! I have to manually turn it off and back again, and then when I run flashrom it says it can't detect (see error message above). Anyone had this problem? I find it weird that it hangs the pi when I make the connection (which kinda proves it does make a connection, doesn't it?).

Also, how do I step down the voltage? I don't want to fry the board (I'm even afraid I might have already done it)

Raspberry pi 2
I have the same error :
..
No EEPROM/flash device found.
when I try to delete or flash eeprom.
I have verify my connection 5 times.

I finaly found my error. Raspberry PI2 Model B use this shema for GPIO:
ww....raspberrypi-spy.co.uk/wp-content/uploads/2012/06/Raspberry-Pi-GPIO-Layout-Model-B-Plus-rotated-2700x900.png
[email protected] said:
I have the same error :
..
No EEPROM/flash device found.
when I try to delete or flash eeprom.
I have verify my connection 5 times.
Click to expand...
Click to collapse

[email protected] said:
I finaly found my error. Raspberry PI2 Model B use this shema for GPIO:
ww....raspberrypi-spy.co.uk/wp-content/uploads/2012/06/Raspberry-Pi-GPIO-Layout-Model-B-Plus-rotated-2700x900.png
Click to expand...
Click to collapse
Did you get it now? Did you manage to flash the ROM? What was the problem?
Also, did you have to change the voltage at all? Thanks!

please can any one help me to know the value of resisastance on left side of bios chip(resistance front of pin 25 17 21 24 all small balck 6 resistance ) my is damage please help me.... please help me...

so i finally bricked my x98 pro and i need a little help here.
i desoldered the bios chip and soldered it directly to the adapter board in the picture below.
i successfully flashed a laptop bios at 3.3v in the past with a pi and flashrom but i dont understand how to correctly wire the logic level converter for operating at 1.8v.
i've tried myself but failed. either the chip is recognized as unknown or not at all.
at 3.3v the chip is recognized but i can't erase or write to it.
i get the 1.8v reference from the tablet (where the chip was) and the 3.3v from the pi. what about pin 4 and 8 on the adapter board? how is it powered now? i tried several things but i don't get it to work...
any help is highly appreciated.
btw. the pic doesn't show it but the chip is of course soldered to the board.

Related

[HOW-TO]UnBrick the UnBrickable Vibrant

{
"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"
}
Introduction:
After months of research and development, both hardware and software... I'm happy to announce UnBrickable Mod is a matter of modifing your phone once, with a single small wire. From that point on, you can click a button to unbrick. This can even be applied to a phone which is already bricked.
This is an example from the Captivate. The procedure is the same on the Vibrant.
Instructions
You Must have UnBrickable Mod applied to your device. If you're not sure, run this tool under Linux: http://forum.xda-developers.com/showthread.php?t=1257434
This currently only works for Linux based computers or Windows based computers with proper drivers installed, with a Linux Virtual Machine, Get Ubuntu here: http://www.ubuntu.com , Get Virtualbox Here: http://www.virtualbox.org/wiki/Downloads
You must have Java installed on your computer: http://www.java.com/en/download/
Unbricking:
1. Apply UnBrickable Mod to your device:http://forum.xda-developers.com/showthread.php?t=1273083
2. Run UnBrickable Resurrector: Get it from THIS POST: http://forum.xda-developers.com/showthread.php?p=17135277#post17135277 This will only work on linux currently. Install Linux or dual boot if you have windows.
3. Run Heimdall One-Click http://forum.xda-developers.com/showthread.php?t=1278683
4. repeat steps 2 and 3 with bootloader flashing enabled (Heimdall One-Click has a safety mechanism which requires you to flash once before flashing bootloaders).
conclusion
You've unbricked the unbrickable captivate... This should not have been difficult. If it was, you should learn teh computer better... Really. And with that said, I'm happy to announce that you no longer have to flash with a fear of bricking.
HIBL
The HIBL is the key to resurrecting a S5PC110 based processor. I'm going to let Rebellos explain the inner workings of the Hummingbird Interceptor Bootloader. It's really quite amazing. While my work is more hardware and high level tasks like making things into one-clicks, Rebellos' work involves reverse software engineering, assembly language, and more...
Rebellos said:
Okay, so, what is Hummingbird Interceptor Boot Loader (HIBL)?
Basically: It allows to load any amount of data (limited by size of RAM block, the biggest one single block available is 256MB) through USB connection with PC under any specified address into memory and then execute it.
Technically: It does consist of 2 pieces fused together - BL1_stage1 and BL1_stage2.
Each stage starts from 16bytes (4 ARM WORDs) of secure boot header. In stage1 these are mandatory, in stage2 they can be random (nulled them in my code), so EntryPoint of each stage does start at its 0x10 offset.
BL1_stage1, loaded under 0xD0020000 address, is short code, digitally signed by Samsung. It has been released to break "Chain of Trust" and alter Secure Boot into Non-Secure Boot process. Literally stage1 just do some compare operations and then jumpout to BL1_stage2. (Yes, I also see no point of releasing hardware secured CPU version together with software which is bypassing it's security)
BL1_stage2, must be placed at 0xD0022000 address (it's fused together with stage1 into HIBL, so it's at 0x2000 offset of HIBL.bin) it is unsigned because Secure Boot Context, prepared by iROM (BL0) has been already ignored by stage1.
Its FASM_ARM sourcecode:
http://code.google.com/p/hummingbir...unk/HummingBirdInterceptorBootloader/HIBL.ASM
This is where the code start real work, it does begin with standard ARM core jump vector table (just to keep stick to standard, these aren't used anyway).
1. It does use I9000 BL1_stage2 functions (init_system) which I linked to it, these are used to init DMC controllers, as to this point code is executing in and working with very tiny, 96KB iRAM space, after calling this function it turns all 512MB of RAM available.
2. Make sure DMC is configured properly (write some value to address 0x40~~ memory space, then read it and compare with previously written)
3. Reinit iRAM heap to the BL0 initial state (to convince it USB dload mode haven't been called yet), by storing and restoring UART pointer only (to keep debug output flowing properly)
4. Call iROM usb_downloader function.
5. Read the address where downloaded data has been placed.
6. Jump into this address.
This, properly used provides similiar debug output (similiar, because its outdated testlog)
Code:
�������������������������������������������������� ����������������������
Uart negotiation Error
----------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v1.0
Copyright (C) Rebellos 2011
----------------------------------------
Calling IBL Stage2
DONE!
Testing BL3 area
DONE!
iRAM reinit
DONE!
Please prepare USB dltool with BL3
Starting download...
0x00000000
Desired BL3 EP: 0x40244000
Download complete, hold download mode key combination.
Starting BL3...
//OUTPUT BELOW IS COMING FROM SBL
Set cpu clk. from 400MHz to 800MHz.
IROM e-fused - Non Secure Boot Version.
It opens infinite capabilities. Instead of SBL to unbrick, Uboot can be loaded, or any armlinux kernel. It's all up to you - XDA Developers.
Click to expand...
Click to collapse
Tools
Windows32 command line app and drivers http://forum.xda-developers.com/attachment.php?attachmentid=709292&d=1315091521 (doesn't work very well... just want you to know this)
Linux one-click Resurrector: http://forum.xda-developers.com/attachment.php?attachmentid=712232&d=1315349672
Wow. i mark it! thank you for your great work!
I just resurrected a Vibrant today using the method above. This tested great. No problems to note at all.
Here's a picture of my work http://forum.xda-developers.com/showthread.php?p=17896376#post17896376
This is slightly more difficult then a captivate because there is no room to work around the resistors.
thanks to you i finally got my vibrant unbricked thanks a lot for this .....................
Aneez1990 said:
thanks to you i finally got my vibrant unbricked thanks a lot for this .....................
Click to expand...
Click to collapse
You're welcome. Glad this helped.
Very sexy work... its nice to have this as a backup and itll be Very nice once people develop ffirmware to work with the unbrickable mod, like nexus s bootloaders or wp7 or iOs or whatever... thanks again
Sent from a cell tower to the XDA server to you.
younix258 said:
Very sexy work... its nice to have this as a backup and itll be Very nice once people develop ffirmware to work with the unbrickable mod, like nexus s bootloaders or wp7 or iOs or whatever... thanks again
Sent from a cell tower to the XDA server to you.
Click to expand...
Click to collapse
I'd like to see Ubuntu. Turn these devices into a lamp server or security/web cam orsomething when were done with them.
I would also like to see work on Ubuntu. is there any work being done for that? I'm still thinking about getting the UB mod sometime soon.
Hey guys Im having a problem with step #2. It says to download Unbrickable Resurector but this post is the HIBL post with no "Unbrickable resurector" download link. Is that just an error or do I just download the file listed on the previous post called "UltimateUnbrickResurector.zip"? Thanks for any clarification...
Also, when I launch the resurector on the previous post I get the following error smdk-usbdl: not found. Do I need to have Heimdall running prior to launching the resurector? Thanks again...
Code:
Please wait.... Uploading..
-------------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v1.0
Copyright (C) Rebellos 2011
-------------------------------------------------------------
Building command list
Building command list
Requesting Permission to access device/tmp/skorpnHeimdallOneClick51336EBC/Script.sh: 3: /tmp/skorpnHeimdallOneClick51336EBC/UnBrickPack/smdk-usbdl: not found
Moved this post to the "Mod" thread.
The Resurrector is not working, either because the mod was done incorrectly, or my Ubuntu machine has been setup wrong. The Resurrector keeps giving me the smdk-usbdl: not found error, but the file exists. My best guess is that the Mod was done incorrectly, either that or my Linux box is being a pain... Also noticed adb not working as well.
EDIT: Im going to go out on a limb and say this error is telling me the "usb device" has not been found, which would mean my mod did not take.
edit never mind found the answer was just wondering if it were possible to learn the wielding part of the guide on the internet and such also what type of tools would i need please and thank you
dohandrew said:
edit never mind found the answer was just wondering if it were possible to learn the wielding part of the guide on the internet and such also what type of tools would i need please and thank you
Click to expand...
Click to collapse
If you're asking, you will want to find someone more experienced.
i see where would u suggest going to ? im located in california i dont really know of a place that does welding on phones
Adam will do it for $30 + shipping, PM him.
Atleast thats what hes said (correct me if im wrong)
Adam, did you say you can do this mod for $30 + s&h?
Also, Im wondering if you upgraded to Ubuntu 11.10 yet? I just decided to upgrade before even thinking about it possibly effecting the mode detect, heimdal one click or the resurrector. You think the upgrade can break these apps any?
SkOrPn said:
Adam, did you say you can do this mod for $30 + s&h?
Also, Im wondering if you upgraded to Ubuntu 11.10 yet? I just decided to upgrade before even thinking about it possibly effecting the mode detect, heimdal one click or the resurrector. You think the upgrade can break these apps any?
Click to expand...
Click to collapse
Yes I do. No it doesn't.
AdamOutler said:
Yes I do. No it doesn't.
Click to expand...
Click to collapse
Excellent Im on 11.10, and thanks for the info...
I was able to remove the resistor and replace it with another resistor from an old samsung phone. I used a circuit writer pen from radio shack, it lays down a conductive polymer, which I used to adhere the new resistor onto the bottom spot on the board. "the resistors are so small I could not imagine being able to do this with a soldering iron. I would have probably shorted something out because the amount of solder that needs to be laid down might not even fit on an ants back (seriously!)"
Another note: when using resurector, my phone only went into download mode if I pressed on "only" the volume down button.-I hope this helps someone out there with a brick like the one I had.
Does that mean after applying this mod the vibrant will never brick at any cause ???
galaxyfitftw said:
Does that mean after applying this mod the vibrant will never brick at any cause ???
Click to expand...
Click to collapse
yes that is the meaning of this mod....is just awesome

Ubuntu on Galaxy Tab (WIP)

I tried loading Ubuntu using one of the market Ubuntu installers on the 4.0.3 install and convinced my self the kernel did not have loop support. Now I'm not so sure. I tried again with 4.0.4 and realized that the kernel had support, but the mount and umount tools did not. But busybox's commands support loop!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'll update as I figure out more, but the basic drill was:
Download "Complete Linux Installer (NEW)" from Market. You don't really have to do this, it just is a "guide" and has a nice launcher which (so far) does not work because we need some hacks. You could probably download the image off sourceforge and be as well off, but I was trying to get this to work. You download a 3.5MB zip file and then use a zip program (ES choked on it but Astro did ok) to extract ubunutu.img into /sdcard/ubuntu
Since the launcher crashed, I went here http://forum.xda-developers.com/showthread.php?t=962023&page=2
I followed the script by hand in an adb terminal. I suppose you could use a local terminal too. I didn't do the redirects and things I knew I didn't need. All worked except for the pts which I am still investigating. (oops a typo). Also this line:
Code:
busybox mount -o bind /sdcard/external_sd /data/local/mnt/external_sd > /dev/null 2>&1
Should be (for us):
Code:
busybox mount -o bind /mnt/extSdCard /data/local/mnt/external_sd > /dev/null 2>&1
The script will ask you the size (1280x800 although probably should use 1280 x 720 or something to handle the bar at the bottom of the screen.
Then you pick LXDE or Gnome. I picked LXDE.
Off you go. You can connect with an X server, a VNC client, or keep using the shell. Awesome!
I'll update if I fix the pts.
UPDATE: My bad. A typo on the pts line. That script actually works fine as-is except for the difference in the sdcard.
Now need to find a good onscreen keyboard although a real keyboard should work pretty well. The ones I have tried have trouble sending <ENTER> and want to dismiss the keyboard instead.
A few other notes. The init from the app has some output, so you need to NOT redirect the chroot. Also, has to run as root for the chroot to work (unless I have wonked some permission).
There are a few other issues with the image I used.
1) Need to update emacs23 for it to work (from a Ubuntu terminal: apt-get update; apt-get install emacs emacs23)
2) /etc/bash.bashrc needs to have the sudo hinting taken out or you get annoying error messages
3) The scripts attached do not clean up all processes. This may not be a problem if we can get the launcher to work, I'm not sure if it cleans up better or not.
I will post my modified/customized scripts in just a minute. The directory structure is such that /system is all on the android side and everything in /data/local/mnt should be at the ROOT of the Ubuntu files (that is, put them in while running Ubuntu or at least mount Ubuntu and then put everything in the mounted place).
I pulled these off my sdcard so you will need to patch the permissions for the scripts:
For example:
chmod 755 /system/xbin/ubuntu
Here are the files in tar format (use tar xzvf ubuntu-files.z.tar to extract):
View attachment ubuntu-files.z.tar Version 2, 15 July 2012 (fixed bad path in loop mount)
Once you have everything installed, start a terminal and execute:
su -c ubuntu
I have tried making a BTEP shortcut but with no luck yet.
Enjoy!
There is a thread about this including the image links etc (thanks to zacthepack for pointing me to it, now I've got to read it ;-) ).
http://forum.xda-developers.com/showthread.php?t=1585009
P.S. Of the VNC apps I tried that were free Jump (https://play.google.com/store/apps/...GwsMSwxLDEsImNvbS5wNXN5cy5hbmRyb2lkLmp1bXAiXQ..) seemed to work the best. The free version only lets you have one connection.
PocketCloud wasn't bad but you can't get the onscreen mouse all the way to the bottom (it tries to shrink it, but I think it doesn't know about the "permanent" ICS bar down there. If you have a real keyboard/mouse then the AndroidVNC team version works well, but it is a pain to use without a keyboard.
Please post your scripts.
Whats with backtrack? Any idea if the gtab2 support the system with all his funtions?
exebreez said:
Please post your scripts.
Whats with backtrack? Any idea if the gtab2 support the system with all his funtions?
Click to expand...
Click to collapse
There you go. Don't know a thing about backtrack other than I saw it was an option.
wd5gnr said:
There you go. Don't know a thing about backtrack other than I saw it was an option.
Click to expand...
Click to collapse
Had a small bug in the ubuntu script that didn't show up until I rebooted. Updated to v2.
Hello wd5gnr,
Would it be possible that a newbie like me can get a step by step for getting this done?
I have a P5113 with CyanogenMod 9 working great and I would really like to have Ubuntu with Gnome if possible.
Thanks in advance!
Best regards,
galcv2
galcv2 said:
Hello wd5gnr,
Would it be possible that a newbie like me can get a step by step for getting this done?
I have a P5113 with CyanogenMod 9 working great and I would really like to have Ubuntu with Gnome if possible.
Thanks in advance!
Best regards,
galcv2
Click to expand...
Click to collapse
Maybe this weekend. I can tell you that the performance especially with Gnome leaves something to be desired.
You might have better luck with this approach: http://forum.xda-developers.com/showthread.php?t=1782383
THANK YOU!

How to dual boot on me176cx part 1

This is only first part. In this part, I will NOT mention any OSes. I will teach you how to run rEFInd on this device.
In other parts, I will edit rEFInd's config file to make it really "work". BUT, after this tutorial, you may fell happy that dual boot will most likely work on the device you just hod in your hands.
This guide is for me176cx only. Steps for other devices may be similar, only try to do this on other devices if you are sure you know where the differences are and how to change the commands!
So let's begin!
My tablet before doing anything
{
"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"
}
on http://www.rodsbooks.com/refind/getting.html , click on get binary zip file
Extract the downloaded zip
look for the folder "refind" inside the extracted folder
////////////////////////////////////////////////////////////////////////////
Now, we need to move it to Efi System Partition.
Istall busybox. Then, install Android Terminal Emulator.
Using some file browser with root rights, make a folder in the root of your device's memory called "esp"
Then, mount Efi System Partition on it:
Run the Android Terminal Emulator, type su, and confirm the SuperUser dialog.
Then, type: busybox mount /dev/block/mmcblk0p3 /esp
it should have no output.
Then, copy the "refind" folder to file system root.
Then (using terminal emulator) copy the refind folder to the ESP.
Then, make sure it is really there
Then write: busybox umount /esp
///////////////////////////////////////////////////////////////////////
Now, add rEFInd's binary to bootorder and set the bootorder to !!!NOT!!! boot it first, becouse you have to test it first (and you do not want to run and buy the first powered hub to be able to get back in android some complicated way)
Download this file and move it to some location where you will execute it from:
http://forum.xda-developers.com/showpost.php?p=62429430&postcount=2740
(Thanks to social-design-concepts for compiling this to work on android)
Issue this command (the paste function does not work in terminal emulator so you have to rewrite it by hand)
Then, make sure the path is set well:
Then, set the boot order to boot Android first by ./efibootmgr64 -o 0001,0000
Then, set the next boot (only next boot) to rEFInd
////////////////////////////////////////////////////////////////////
Now, just power off the tablet, (do not restart) and power it on again. You will see rEFInd, but you cannot do much without powered hub.
So if you have one, look around with keyboard. If you do not have one (like me), just power off the tablet by holding the power button, power it on again and wait for the next part of this tutorial
EDIT:
tuxic001 edited rEFInd binary so you can select what to boot.
http://forum.xda-developers.com/showpost.php?p=62463032&postcount=60
\\\_///
P.S If you use nandroid backup to update, you only update kernel and ROM (or recovery, fastboot, esp partition and whatever the other partitions are), depends on what you backup. And I don't think UEFI is stored on EMMC, so if UEFI update (or bootloader, recovery, etc. update) is present, you are totally ignoring it. On the other hand, UEFI update is a risk of not being able to access it..
Is refind working with touch or volume\power keys?
A powered hub is non-optional. OTG power is super finicky on this tablet, especially if you're adding a flash drive on top of mouse and KB
t68kv said:
Is refind working with touch or volume\power keys?
Click to expand...
Click to collapse
Voume keys work, but power key doesn't. But tuxic001 is working on editing the source code so it will. Maybe tomorrow this time it will work
Good And Bad news
Which you want to hear first?
Look fo EDIT in the main post.
I also got my tablet down, it boots only to UEFI as there's no efi bootloader to load anymore.... I'll run and get a powered usb hub to try to use the UEFI, cause the vol keys don't cut it.
Awesome guide @Mis012. I got it working on my Lenovo Tab S8-50F.
Did you have a chance to try dual booting anything yet?
EDIT: Making progress
Shump said:
Awesome guide @Mis012. I got it working on my Lenovo Tab S8-50F.
Did you have a chance to try dual booting anything yet?
EDIT: Making progress
Click to expand...
Click to collapse
Yeah I have run grub 2, it was nice. I got stuck somewhere in kali linux booting process, and then ubuntu-based dostros said bad kernel magic number blah blah. So I tried abother grub. First I found was nice, but still not working with ubuntu. So I tried to use ununtu's grub. It didn't show up in rEFInd. Now I can't find the good grub again What about your progress? Did you need to use powered OTG cable?
EDIT: found working grub again, kali linux stuck at this error: http://unix.stackexchange.com/quest...o-find-a-medium-containing-a-live-file-system
Any new?? This tutorial works on Lollipop?? If do this tutorial exist any risk for example brick??
Can you do a tutorial and upload to youtube??
or someone explain me the process?
Thanks in advance.:good:
I get invalid argument on the first command lenovo tab s8
Somewhat more wrong the error invalid argument to execute the first command and at least a thousand times but nothing works I have root and I do everything to the letter I tried on the asus tablet of the same model and my Lenovo Yoga Tab 3 and same error
jet_98 said:
Somewhat more wrong the error invalid argument to execute the first command and at least a thousand times but nothing works I have root and I do everything to the letter I tried on the asus tablet of the same model and my Lenovo Yoga Tab 3 and same error
Click to expand...
Click to collapse
have you installed busybox? as simple as that.

Flashtool Issue W10

Hello guys ,Its possible to flash roms for the tablet with a computer using windows 10 because evertime that i tried to do it i got only a 14% at least
Obviously its a driver issue but there is any update or fix to this thanks :good:
Win 10 is not the best OS to use in order to flash ROMs at the moment..
Maybe try to use Virtual Machine with Win7 installed..
Phantom2332 said:
Hello guys ,Its possible to flash roms for the tablet with a computer using windows 10 because evertime that i tried to do it i got only a 14% at least
Obviously its a driver issue but there is any update or fix to this thanks :good:
Click to expand...
Click to collapse
Better than with Windows:
Yes try with the UEFI method
There is no more risk to brick your X98 than with any other methods if you follow the instructions.
You do it from the same computer/tablet so no no cable and No other computers involved :cyclops:
Just DON'T forget at the end of the process/flashing to shutdown the tablet by pressing the Power button for 15 seconds
How Flash your BIOS via the UEFI shell:
You connect a USB hub to your tablet and connect a Keyboard to the hub and a USB key with the BIOS file + FPT.efi command and the fparts.txt on the USB Drive.
Important: To be recognized by the UEFI SHELL BIOS the USB must be formatted with GPT AND in Fat32, the more EZ is to use the RUFUS utility to format the USB drive. So don't forget to format the USB drive before copying the files
You power up the tablet and press "ESC" key to enter in the BIOS.
In the BIOS you go to the Boot selection and choose "UEFI Shell"
You will see a screen like this:
{
"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"
}
You press any key to have the SHELL prompt (There is not Startup.nsh on tablet it's a generic message in UEFI bios)
You are now in the UEFI shell, it's a little bit like the old DOS shell.
We now need to know where is the USB drive so you will type "map -r" (Without the quotes)
It will list all the devices available:
You try to find your USB drive, usually you will see "Removable Hardrive" in the name somewhere.
To be sure you have the good device you type at the prompt:
"ls FS1:" (Without the quotes) and press "enter"
It will list the files so if you see the BIOS file and the fpt.efi file you are at the right place if not try another device FS1 FS2 etc...
Once you are in the right device it's EZ:
First we will do a back-up of the BIOS, so Type:
"fpt.efi -D MyOriginalBios.bin" (Without the quotes) and press "enter"
It will do a backup of your bios named "MyOriginalBios.bin" saved on the USB drive.
Now we will Flash the BIOS so type:
"fpt.efi -f MyNewBios.bin" (Without the quotes) and replace MyNewBios with the name of the bios file) and press "enter"
The process will begin you wait few minutes till it end and you should receive a message that the process was successful.
IMPORTANT: At this point you shutdown the tablet by pressing the Power button for 15 seconds
That's it ! Enjoy ! :laugh:
N.B.: If you want to remove the Dual Boot menu
Link for Flash Programming Tool: https://mega.nz/#!o4YADKZJ!Q1q3J8wSC9npX1ofrGE3iAwYEMAodREv1v-PhrJIXKI
For the BIOS you can use any BIOS from 1.03 to 2.05

[HOW TO] Root Remix Mini

Hi all,
I have been going on xdadevelopers a lot and have received so much helpful information. Now, I decided to give in my contribution to the forum. This is my first tutorial so there might be some mistakes...please be easy on me.
The reason I write this tutorial is because I have not found a good one yet on the internet. Although this thread "Just rooted my remix mini" provided some information, but I feel like a more detailed tutorial would be appropriate. So here we go!
Success screenshot:
{
"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"
}
Credits: all credits goes to these two links and authors:
http://forum.xda-developers.com/remix/remix-mini/rooted-remix-mini-t3311736
http://23pin.logdown.com/posts/435610-root-remix-mini
Requirements:
- Difficult level: Medium
- Tools:
+ Small screw driver
+ Scissors
+ A USB flash drive.
+ Thin metal wire.
+ Serial Converter (I bought on Amazon.com)
- Software:
+ Appropriate driver for the serial converter. Mine is CP2102 driver. Download here. If your serial converter use PL2303 then download this driver. You can google for your specific driver as well.
+ CoolTerm. Download here
+ SuperSU. Download here
- A lot of patience.
Steps:
1. As you can see, I stripped the wire and cut it in small pieces. As long as it is metal wire, that's okay.
2. Open up the Remix Mini with a screw driver.
2a. Flip it up side down, and rip the rubber ring out. It's okay, it will still adhere to the case afterward. Once you ripped it out, you will see two screws holding the remix mini. Proceed unscrew them and gently take the case apart.
2b. Gently take the case apart:
3. Connecting the serial converter to the board.
3a. Plug the 3 metal wires into RX, TX, and GND cable endings of the serial converter.
3b. Connect the other ends of 3 mental wires into RX, TX, and GND of the board.
3c. Make sure connection as such: RX to TX, TX to RX, and GND to GND. This part took me a lot of patience because the wires kept falling off. So please try to keep them in place.
4. Install appropriate serial converter driver.
5. Plug the serial converter into PC.
6. Extract and open CoolTerm.
6a. Click Options -> Serial Port -> Hit "Re-Scan Serial Ports" so it detects the appropriate port for serial converter. Mine is COM3.
- To find out, go to Device Manager -> Ports
6b. Select the right port. Then change the setting as in the picture:
Baudrate: 115200
Data Bits: 8
Parity: None
Stop Bits: 1
Click to expand...
Click to collapse
6c. Go to tab Terminal -> Select Line Mode.
6d. Hit OK.
7. Power Remix mini up (make sure this happens or you will get serial 103 or 104 error code)
8. Hit Connect button in CoolTerm.
8a. If you have done everything correctly until here, texts will appear in CoolTerm as your Remix Mini booting up.
8b. The texts will keep flowing up. Wait until you only see CPU readings. Then proceed to next step.
9. Download the UPDATE-SuperSU-v2.46.zip file. (Please double check the zip's file name. In my case, I am using SuperSU version 2.46)
9a. Copy UPDATE-SuperSU-v2.46.zip file onto flash drive.
9b. Extract the downloaded "UPDATE-SuperSU-v2.46.zip", from the extracted, go to META-INF/com/google/android/update-binary, copy "update-binary" file onto flash drive.
9c. Make sure you have 2 files, UPDATE-SuperSU-v2.46.zip AND update-binary, on the flash drive.
9d. Plug the flash drive to Remix Mini.
10. Commands: (copy each line and paste into CoolTerm)
Code:
/dev/tty.usbserial 115200
mount -o rw,remount /
mount -o rw,remount /system
mkdir /tmp
cd /system/bin
ln -s busybox-smp unzip
cd /data/local/tmp
cp /mnt/usbhost/Storage01/UPDATE-SuperSU-v2.46.zip /data/local/tmp [COLOR="Red"]<- Double check zip's file name and try Storage02 if Storage01 does not work because it depends on which usb port you plug the flash drive in. [/COLOR]
cp /mnt/usbhost/Storage01/update-binary /data/local/tmp
cd /data/local/tmp
sh update-binary 0 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip
reboot
11. Success. :victory::good:
11a. Wait for Remix Mini booting up, optimizing app..and DONE! CONGRATS! You have now voided your Remix Mini's warranty and cannot receive OTA system update anymore.
I have not figured out how to update manually but please hit me up if anyone knows how.
11b. Download Root checker to verify.
GOOD LUCK!!!!!! :good:
I'm gonna wait for an easier way..
This has got to be a joke.
Bro, have you tried kingroot, I'm not crazy about it but it works 99℅of the time
Sent from my LG-D415 using Tapatalk
No it is not a joke, no it will not get easier. Jide made it clear they will not support rooting. The amount of support available is minimal so this is the way. Difficult not if you have done stuff like this before ( FTA satellite. Etc.) kingoroot and all other software has been proven NOT to work. Hardware hacking is the only way so far.
Note: first boot takes longer than factory. Be patient. Jide will know it has been hacked so no support for updates but the opportunity to customize was worth it for me.
robot_head said:
Bro, have you tried kingroot, I'm not crazy about it but it works 99℅of the time
Sent from my LG-D415 using Tapatalk
Click to expand...
Click to collapse
I tried everything..even Baidu Root...nothing works...I am happy that I can do so many things with the Remix Mini now...rooting it was a genius decision lol
Major kudos, this is a true root method for all the hardware hackers out there. You've never truly "hacked" until you've tapped into a UART console. Very exciting!
So when I try this the remix mini just sits at the splash screen and coolterm just keeps saysing
Code:
/dev/block/mmcblk0p12fs_mgr: exec: pid 1667 exited with return code 1: Unknown error 256fs_mgr: begin to format ext4 buffer : /dev/block/mmcblk0p12fs_mgr: finish format to ext4:
while counting up on the pid number. Any idea why that might be?
bullet25 said:
So when I try this the remix mini just sits at the splash screen and coolterm just keeps saysing
Code:
/dev/block/mmcblk0p12fs_mgr: exec: pid 1667 exited with return code 1: Unknown error 256fs_mgr: begin to format ext4 buffer : /dev/block/mmcblk0p12fs_mgr: finish format to ext4:
while counting up on the pid number. Any idea why that might be?
Click to expand...
Click to collapse
I have not seen that before. May I ask at which step that this occurred? This looked like the device was formatting ext4 itself...it's weird.. can you double check and try everything again carefully?
unloseking2500 said:
I have not seen that before. May I ask at which step that this occurred? This looked like the device was formatting ext4 itself...it's weird.. can you double check and try everything again carefully?
Click to expand...
Click to collapse
I happens at step 8. I think the mini might actually be dead because even closed up it doesn't boot.
Sounds like a software issue. Someone else had a recovery partitionfrom Jide search maybe they could upload it.
bullet25 said:
I happens at step 8. I think the mini might actually be dead because even closed up it doesn't boot.
Click to expand...
Click to collapse
Interesting...yeah, try oncouch1's method..try to recover from a partition..see if it helps?!
oncouch1 said:
No it is not a joke, no it will not get easier. Jide made it clear they will not support rooting. The amount of support available is minimal so this is the way. Difficult not if you have done stuff like this before ( FTA satellite. Etc.) kingoroot and all other software has been proven NOT to work. Hardware hacking is the only way so far..
Click to expand...
Click to collapse
I also believe so. Grats on your success tho.
I have a question:-
I have a Tronsmart Vega S95 Telos with Remix OS firmware (Amlogic S905/Mali-450mp5/2 Gb Samsung DDR3/16 Gb Samsung KLMAG2WEMB-B031 eMMC/Realtek RTL8211F Ethernet/Ampak AP6335 Wifi+BT 4.0/Genesis GL850G USB 2.0 hub/JMicron JM20329 USB 2.0 to SATA bridge).
I opened up the TV box and saw the pin holes for PL2303 interface. I tried connect my PL2303 cable with its driver on Mac OS. The connection was succesful, I saw the response in my terminal in the form of message feed. But, I can't go any further. I'm still new to PL2303 use and I don't know how to go from the message feed to issue some commands. Then I see your thread and I think now I got some hope.
My question (again) is:- Do you think I can use your method to root my Tronsmart S95 Telos (with Remix OS flashed and working)?
Many thanks in advance.
PS. Here is the link to a photo of the S95 Telos board showing the PL2303 interface. The photo is not mine. I linked it from a guy tutoring the teardown, but my board looks exactly the same.
(I'm a new XDA user so I can't attach a photo from outside link, sorry for inconvenience)
www,cnx-software.com/wp-content/uploads/2015/12/Tronsmart_Vega_S95_Telos_Board_Large,jpg
Yoswin said:
I also believe so. Grats on your success tho.
I have a question:-
I have a Tronsmart Vega S95 Telos with Remix OS firmware (Amlogic S905/Mali-450mp5/2 Gb Samsung DDR3/16 Gb Samsung KLMAG2WEMB-B031 eMMC/Realtek RTL8211F Ethernet/Ampak AP6335 Wifi+BT 4.0/Genesis GL850G USB 2.0 hub/JMicron JM20329 USB 2.0 to SATA bridge).
I opened up the TV box and saw the pin holes for PL2303 interface. I tried connect my PL2303 cable with its driver on Mac OS. The connection was succesful, I saw the response in my terminal in the form of message feed. But, I can't go any further. I'm still new to PL2303 use and I don't know how to go from the message feed to issue some commands. Then I see your thread and I think now I got some hope.
My question (again) is:- Do you think I can use your method to root my Tronsmart S95 Telos (with Remix OS flashed and working)?
Many thanks in advance.
PS. Here is the link to a photo of the S95 Telos board showing the PL2303 interface. The photo is not mine. I linked it from a guy tutoring the teardown, but my board looks exactly the same.
(I'm a new XDA user so I can't attach a photo from outside link, sorry for inconvenience)
www,cnx-software.com/wp-content/uploads/2015/12/Tronsmart_Vega_S95_Telos_Board_Large,jpg
Click to expand...
Click to collapse
Hi honestly I had never heard of your box. I am not sure if you can use the same software etc. If you could communicate with the box you should be able to hack it. That being said depending on cost you may want to leave it to someone with experience! Remix was 50 bucks so no big risk for me.
...
oncouch1 said:
Hi honestly I had never heard of your box. I am not sure if you can use the same software etc. If you could communicate with the box you should be able to hack it. That being said depending on cost you may want to leave it to someone with experience! Remix was 50 bucks so no big risk for me.
Click to expand...
Click to collapse
Thanks for reply. I don't think the method can hard brick my device any way. The box itself can be flashed via a PC program made by CPU manufacturer (Amlogic here) and I have both stock firmware and Remix OS firmware images. So I think it's gonna worth a try. Thanks any way for your comment.
Keep us posted, may need one of those!?
Okay got my remix replaced. New remix updated to latest update then did root. It started boot looping. Had to run these commands in coolterm turing a boot loop.
Code:
mount -o rw,remount /system
dd of=/dev/block/by-name/system if=/data/local/tmp/system_image
Don't know if that was the latest update to cause that or what but its all working now. Also was able to easily install the google play services again and get playstore.
Of course I once again broke the power button because that wire is hanging on by a thread.
Apologies for the noob question but what does a root on the Remix Mini allow someone to do with regards to OS options and what are the other advantages?
vinicioh23 said:
I'm gonna wait for an easier way..
Click to expand...
Click to collapse
Please see this: https://secure.avaaz.org/en/petitio...tters_Users_need_root_access_to_remix_mini_1/
Just wanted to give a thanks it worked perfect for me...Just want to add that if you happen to use a built in serial port on an older pc or laptop don't forget to put a ttl converter on your port, or your console screen will be garbage printing out

Categories

Resources