[Guide] Enable external Bluetooth for LineageOS (serranoltexx) - Galaxy S 4 Mini Q&A, Help & Troubleshooting

The goal of this thread is to help you enable external Bluetooth support for Lineage 14.1. You would want this for example in case you need Bluez tools like l2ping for a BlueSmack attack.
Notices:
I am in no way responsible for any damage you do following this guide. Every step is done at own risk.
The only drawback of this method is that the creation of BT sockets will instantly return and never block so that an application must first wait a few seconds on itself.
I know that this method is far from perfect. I spent 70+ hours to make this work even though I'm not a C# developer. If you have a better method feel free to share it.
Please find some useful files as attachments.
Requirements:
1. The ability to build for your device using Lineage source
2. A fully prepared and ready-to-build directory with Lineage 14.1 source (Refer to this guide in case you do not know what to do)
3. An S4 mini and a compatible USB-togo-cable with external powering.
Steps:
1. Start with a terminal in the root directory of the source
2. Update the repo using "repo sync"
3. go to "kernel/samsung/msm8930-common". This directory will be named "kernel directory" by now on.
4. execute "./make_defconfig samsung_serrano_defconfig"
5. in the config enable everything to be built-in in "Networking support/Bluetooth subsystem support"
6. now go to "Bluetooth device drivers" and check "HCI USB driver" to be built-in
7. save and exit
8. go to "net/bluetooth" in your kernel directory and edit hci_core.c
9. find the method "hci_register_dev" and comment out these 2 lines in it:
if (!hdev->destruct)
return -27;
10. open "l2cap_core.c" in "net/bluetooth" in your kernel directory
11. find the method "l2cap_sock_connect"
12. go to the end of this method and remove the "bt_sock_wait_state" call before "wait:"
13. add these two lines where you removed the call from the step above:
sk->sk_state = BT_CONNECTED;
sk->sk_state_change(sk);
14. Finally, build the source and flash to your device. Before you flash make sure you have an emergency copy of a fresh Lineage build on your device in case something with the USB drivers goes wrong
15. Get the app "Linux deploy" and setup Kali Linux.(I tried it with this OS but any other Linux based OS is likely to be working, too)
16. Boot into Kali, plug in your Bluetooth stick and enjoy your working external BT!
Useful Links:
https://wiki.lineageos.org/devices/serranoltexx/build
https://null-byte.wonderhowto.com/h...android-device-with-wireless-adapter-0162943/

Related

[Links Included] Android Eclair 2.1 Beta Releases on i8000 by Almar and his dev team

FROYO IS OUT NOW!!! SEE HERE
FEATURES
Supported features in latest public beta release:
HARDWARE
Display & Touch screen
Hardware keys
Internal & External storage
Vibrator
FM radio
Sound & Audio output via 3.5mm jack
Proximity and Light sensors
Orientation (Accelometer), Magnetic (Compass) and Temperature sensors
CONNECTIVITY
Phone & messaging
Wifi
GSM data (GPRS/2G/3G/..)
USB (ADB)
GPS
SOFTWARE
Android 2.1 (Eclair)
Android market
Rooting
2D/3D acceleration (libs are not included due to legal issues)
Open-source patches: I8000 B7610 M715&M8400
OTHER FEATURES
Battery driver/charging
Brightness control/backlight
COMPATIBILITY ON OTHER PHONES
Omnia pro (B7610): wifi not working
Omnia pro (B7610): hardware keyboard not working fixed
Omnia pro (B7610): some hardware buttons not working fixed
Omnia pro (B7610): vibration not working fixed
T*Omnia II (M715): not working when not connected to USB fixed
T*Omnia II (M715): headphone plug problem fixed
T*Omnia II (M715): some hardware buttons not working fixed
T*Omnia II (M715): phone not working (>rev??)
Show Omnia (M8400): wifi not working fixed
Show Omnia (M8400): USB/headphone plug/hardware buttons problems fixed
Verizon Omnia II (I920): not working
FEATURES UNDER ACTIVE DEVELOPMENT
Camera's
Proximity sensor (only kernel support yet)
Light sensor (only kernel support yet)
Bluetooth (only kernel support yet)
I920: Beta support
FEATURES UNDER DEVELOPMENT
Android 2.2 (Froyo) {sleep bug}
Android 2.3 (Gingerbread) {slooooow and some Eclair features broken}
POSSIBLE FUTURE FEATURES
Android kernel and image build from github.com
TV-Out
B7610: wifi driver
I920: CDMA phone part
___________________________________________________________________
TUTORIALS, MODS, ADD-ONS
BETA 1 INSTALLATION TUTORIAL By Me, l3ong91, XDA
1. Backup the files on your microSD first.
2. Go to Start>Settings>Memory Settings>Storage Card and click Format.
3. Download any one of the files provided on http://o2droid.phj.hu/index_en.php file section.(you can download either 512 partition image or 1GB partition image)
4. Extract the files and put it in My Storage. (Attention: Copy only "o2Beta" folder and default.txt, ext2.tar, haret.exe, log.txt, and zImage to the root of my Storage) Look at attachments.
5. Open "o2Beta" Folder and run haret.exe
6. Wait for it to load and until it say something like reboot, the device will auto reboot so just leave it there.
7. It will boot up Windows Mobile again.
8. Then go to My Storage and click on haret.exe
9. This time it will boot again and after awhile you will see Android logo on the bootscreen.
10. After the Android 2.1 was booted, hold on the "Lock" button for 3-4 sec and
turn off the device. (It will boot up Windows Mobile again, or sometimes you will have to do it manually to turn on the device)
10. Now download and copy http://rapidshare.com/#!download|482l33|443140910|o2bupdate.tar.gz|1480 and http://87.229.73.80/zImage file to root of My Storage and overwrite it.
11. Then run the haret.exe from My Storage (not inside o2Beta folder).
12. This time it will bootup faster than the first time.
13. Yes...Android's dream come true on Omnia i8000
BETA 2 INSTALLATION TUTORIAL By Kapica, MoDaCo
1. Clean SD card of beta1
a) Clean format with SD Formatter, or
Use EASEUS Partition Master and format the EXT2 partition on SD card
2. Rename o2b2filesys.tar.gz to ext2.tar.gz
3. Copy ext2.tar.gz and new zImage to My Storage and overwrite
4. Go to O2Beta directory and run haret.exe
And thats it, u get beta2 installed, rest as usual...
To add 2D/3D rename tar.gz to o2b2update as devs said...
If you experience reboots I think its to lack od 2d/3d, open the 2d/3d o2update.tar.gz and copy system directory into ext2.tar with Total Commander, save archive, copy to My Storage, and try to install now.
BETA 2 INSTALLATION TUTORIAL (EASY ALTERNATIVE) By Me, l3ong91, XDA
1. Download the latest installation package as of 11/2/2011
2. Format SD Card again using Samsung Settings>Format.
3. Delete all the Beta 1 Folder and Beta 1 files in My Storage.(if you have previously installed Beta 1 on your phone)
4. Extract and copy all the files in Beta2 installation package to My Storage.
5. Download one of the 2D/3D driver links below and rename as o2b2update.tar.gz
6. Put it in My Storage.
7. As usual, run haret.exe from o2Beta folder.
8.Then after reboot, run haret.exe from root of My Storage.
2D/3D DRIVER DOWNLOADS
For Beta1 Installation
Download o2bupdate.tar.gz and place in "My Storage\o2bupdate.tar.gz" , this should stop the phone from freezing every 5 minutes:
For Beta2 Installation
Rename as o2b2update.tar.gz
http://rapidshare.com/#!download|482l3...ate.tar.gz|1480
http://www.filesonic.com/file/60103983/o2bupdate.tar.gz
TO ROOT BETA2 by turnado1979, MoDaCo
Download this and put it in root of My Storage
TO PREVENT PHONE FROM SLEEPING DEATH By slmz, MoDaCo
Settings>Wireless &network settings>Mobile networks> Tick "Use only 2G networks"
- 4% last for about 9 hs
BUTTON FIXES AND REMAPPING
Button fixes:
To wake up the phone with Hang up and Lock buttons only - by Rapid81
Menu button unlock policy fix - by ult_nrg
DUAL BOOT WIN-MO AND ANDROID ON OMNIA 2
1. Get Gen.Y DualBOOT from megaupload (http://www.megaupload.com/?d=HRPO9CC7)
2. Only use "Gen.Y DualBOOT WVGA v1.0.6.0 - Storage Card.cab" and delete other cabs.
3. Install cab on "Device Storage" (otherwise doesn't work)
4. Copy/move Haret.exe ,default.txt, zimage to root of SD card.
**If you want fastboot (no pushing OK in Haret) rename default.txt to startup.txt
GET LIVEWALLPAPER WORKING By Aafi-rocks, MoDaCo
1. Boot to windows and Connect your phone to PC in Mass Storage mode
2. Open ext2.tar.gz using 7-zip
3. Then go to below path ext2.tar.gz\ext2.tar\system\lib\
4.unzip the attached lib.zip file and copy all the 3 files here..
5.Then go to below path ext2.tar.gz\ext2.tar\system\app
6. Unzip the attached app.zip file and copy all the files here.. (you can also copy any other APK files for games and apps here, if you want to pre-install them)
7. Now close 7-zip and it will ask you if you want to update the archive.. click yes..
8. Now re-install Android..
Once Android is booted. On the home screen try changing the wallpaper and there you see the live Wallpaper option...Select the Live wallpaper of your choice and Njoy...!!
You can also do this without re-installing Android..
1. Explore your phone using Droid Explorer then navigate to system/lib and copy the files from the attached 'lib.zip' here..
2. Then using droid explorer install the APK files from the attached 'App.zip' file..
ADB INSTALLATION AND TUTORIAL By Rapid81, MoDaCo
1. First af all, you need to set the ports under Android.
To do that, write this to the phone: *#7284#
Then you need to select the followings:
UART -> Modem
USB -> PDA
After this, go to the Settings\Applications\Development and check the USB Debugging if it not checked already.
2. Download the Android SDK from here. Install (if you downloaded the installer) or unzip to a location where you'll easly found it. For example C:\android-sdk-windows.
3. Download Samsung KIES. Install it. It contains 2 of the 3 necessary drivers.
4. Download the SamsungADB.zip and unzip it somewhere, where you'll easly found it.
5. If the Android did not went to sleep after it started, then unplug from USB (if it plugged) and put to sleep with the Hangup button. After that, plug onto the USB. The Windows will install 2 of the 3 drivers automatically. The 3rd one will not be found. This will be the ADB driver. Go to the Device Manager and browse the driver (not just add the path to the search root, you need to select the driver yourself!!!) what you extracted from the SamsungADB.zip. Choose one of the followings:
Samsung Android Composite ADB Interface or ADB testing interface and install it.
If the Windows ask for a confirmation to install a not trusted driver, then say yes.
6. Press Windows+R and type into "cmd".
In the upcoming windows, navigate to the unzipped or installed Android SDK directory with the following command:
For example: "cd c:\android-sdk-windows"
In there, navigate to the "platform-tools" directory with this command:
"cd platform-tools"
7. This is where the party started.
Commands you can use:
adb devices -> If you see your device here, you did a good job.
adb shell -> console
In the console:
logcat -> List all android events/errors
cat /proc/kmsg -> kernel log
adb push filename folder -> Send file from Windows to android, to the specified folder
adb pull filename -> Receive file from Android to Windows
Backup all installed applications (rooting is necessary):
tar czvf /storage/App_backup.tzg /data/app* -> Backup
tar xzvf /storage/App_backup.tzg -> Restore
ADB Installation Guide on Omnia2Droid Google Source Code Page
http://code.google.com/p/omnia2droid/wiki/InstallAppsADB
___________________________________________________________________
EXTERNAL SITES, LINKS, AND PAGES
Beta Release Official Download Page: http://o2droid.phj.hu/index_en.php
Beta Release Source Code Page: http://o2droid.phj.hu/trac
Omnia2Droid Official Source Code Page: http://code.google.com/p/omnia2droid/
Almar's Twitter Account (INB2ENSECURITY): http://twitter.com/#!/INB2ENSECURITY
MoDaCo "Android on Omnia 2" Thread: http://www.modaco.com/content/i8000-omnia-ii-gsm-rom-discussion/322429/android-on-omnia-ii-i8000/
YouTube "Android 2.1 Eclair on Omnia 2" Video: http://www.youtube.com/watch?v=8khXDEOO96Y&feature=player_embedded
Source Code Repository Browser: http://o2droid.phj.hu/trac/browser
Omnia Pro B7610 Discussion Forum:http://www.modaco.com/content/b7610.../331432/android-tutorials-and-known-problems/
Verizon Omnia II(I920) Discussion Forum:http://www.modaco.com/index.php?showtopic=330325&view=getnewpost
___________________________________________________________________
LATEST NEWS & UPDATES
18/1/2011
Beta 1 (Minor Fix) Link: http://o2droid.phj.hu/index_en.php
19/1/2011
New Kernel (zImage) Sleep Issue Fixed Link: http://87.229.73.80/zImage
27/1/2011
Battery charge corrected, missing interface for redio signal level, powerstate,etc. was fixed. Put in root of My Storage and overwrite it. http://o2droid.phj.hu/o2droid.zip
30/1/2011
Script included for apps that needs ROOTED Android device: http://o2droid.phj.hu/suupdate.zip
31/1/2011
Working GSM data network. The o2droid.zip file contain the latest kernel,modules, patches and applications from Rapid and Voyteckst su correction.http://o2droid.phj.hu/o2droid.zip
9/2/2011
Sleep problem solved, Alarm function working, battery drain and percentage correction, upgrading from C4 to D1 the 6500 framework, more powerfull dalvik machine (Linpack 5.x) and all the usable corrections published. There are two version, a simple upgrade to the beta: o2bupdate.zip (just unzip to My Storage) and a new filesystem including all changes and rearranged file structure: o2b2filesys.zip (contains the filesystem as tar.gz and the kernel, must unpack and copy manually - no automatic install). The later one is the beta2 (this will be commiting to the SVN); there are some changes in the automatic updates when using the beta2 image to avoid the mistakes : the new automatic filenames are o2b2update.[tar.gz][sh]. Neither version contains the EGL libraries!http://o2droid.phj.hu/index_en.php
10/2/2011
Bugfix: the init dont allowed the GSM network to get DNS, dalvik vm problems. update it with o2b2update.tar.gz ( for beta2, if you use just the corrected beta, please rename it to o2bupdate.tar.gz). There is a strange error: within telephone conversation in approx.30 seconds the LCD blanks but also the sound muted - UNTIL NOT SOLVE, please use the Call Light application from Market!!!
11/2/2011
We have prepared Beta2 SD card installer (1024mb only). It includes latest update (2011-02-10). Download it http://87.229.73.80/beta2_1024.zip (it will wipe Your current installation). As always it doesn't contain 2D/3D libraries from Samsung (if You found them somewhere on the web put it before first boot to My Storage as o2b2update.tar.gz).
Note: There is still error, when within telephone conversation in approx.30 seconds the LCD blanks but also the sound muted - UNTIL NOT SOLVE, please use the Call Light application from Market!!!
3/3/2011
Updated kernel and modules with support for accelerometer, compass and light sensor, keylayout files for new kernel. Download it here . Install as always: replace zImage, put o2b2update.tar.gz, o2b2update.sh to My Storage. It will work on second boot (because old init.rc is executed first).
So now working things are:
Phone
WiFi
GPS
FM Radio
Market
Data connections (GPRS)
Sensors (only proximity sensor not yet)
2D/3D (Samsung not allowed to us to distribute the 2D/3D library binaries, so they are not included in the image).
Things which are working (low level tests), but without android support for now:
Bluetooth
Camera (there are some works to be done)
8/3/2011
To enable the automatic time update from the GSM there is a simple update script. The timeupdate.zip contains both o2update.sh and o2b2update.sh, copy the proper version (in the case of beta2 image: o2b2update.sh) to the root of the My Storage and haret... At first boot just updating the system database to use the telephone network time, so must reboot again to really use this setting and show the correct time.
9/3/2011
There was a rare condition when the SD card appeared sooner than the internal flash at boot - resulting the "No init found" error in kernel. The reason that the sdhci interfaces was not stricly assigned to an mmc device - the first sdhci was the mmc0. This is corrected now, so the s3c-sdhci.1 is the mmc0, .2 is the mmc1 and so on. The corresponding kernel ( svn version 100): zImage
19/3/2011
New kernel and modules (+ keylayout for those who didn't update it yet). Main changes are: fixes for SDHCI/MMC (ported from 2.6.32, external sd is much faster now), new battery profile (now percentage is more like in WM), compass calibration bugfix. Download here: kernel_19032011.zip.
___________________________________________________________________
UNOFFICIAL RELEASES
There is an ISO file, which was compiled by Mishatir, a MoDaCo member whom is dev team related, I think. I know this is a bit late....I'm sorry because I am unaware of this unofficial release too until recently read the comment on MoDaCo.
Alright to saves time, this is what it does. This ISO is a all-in-one package where it contains the updates and some modification (camera still not working yet though), but may or may not work with devices other than I8000, because currently I only tried out on my device.
From my experience, this ISO file is really amazing, no sleep of death issue, low battery consumption (dropped from 91% to 80% for 12+ hours) and pre-installed with few apps that you can try out.
Comment by MoDaCo member on the ISO
file
Short guide by Mishatir on ISO
Instructions:
1. Wipe out all Beta 1/2 files on your My Storage and format your SD card under Samsung Settings.
2. Download the ISO file here.
3. Unrar the files.
4. Connect your phone in WM mode and placed the "iso folder" under root of My Storage.
5. Run haret.exe in the ISO folder.
6. Android should bootup.
This ISO has few updates (kernel + modules.tar.gz) by Mishatir, if you want to update them,
- zImage --------> Replace zImage under ISO folder
- modules.tar.gz ----------> Rename to o2b2update.tar.gz and placed them under root of My Storage
To avoid Sleep of death , I use "Call End" key to lock and unlock the phone...Pressing" End key" seems to be easier and more responsive to unlock the screen.
Personally I don't recommend to update because since I update it I faced a few problems which eventually cause the Android not booting up....so try all this update at your own risk.
Anyway, this is a very nice and most stable release. Now I can use Android on my daily basis. For more questions, please leave a comment.
CREDITS
Credits to Almar and his dev team, I am not one of them. I'm here to spread this big news over XDA forum to inform every Omnia 2 users about this amazing breakthrough.
Just tried and its works great
Sent from my GT-I8000 using XDA App
problem
there is a problem when it is runing the linux help
Fantastic guys
Sent from my GT-I8000 using Tapatalk
killerkarara said:
there is a problem when it is runing the linux help
Click to expand...
Click to collapse
What problem you faced? Did you follow the instructions provided?
Here is some information for people who don't want to read the whole thread on Modaco.
Video of Beta on Omnia II by Rapid81:
http://www.youtube.com/watch?v=8khXDEOO96Y
Download beta release here:
http://o2droid.phj.hu/index_en.php
Download 2d/3d drivers and install here (you need these else above beta will freeze every 5 mins):
To install 2d/3d drivers download o2bupdate.tar.gz and place in "My Storage\o2bupdate.tar.gz" , this should stop the phone from freezing every 5 minutes:
http://rapidshare.com/#!download|482l3...ate.tar.gz|1480
http://www.filesonic.com/file/60103983/o2bupdate.tar.gz
To manage ext2 partitions from Windows PC and to correctly format your SD card:
To delete ext2 from Windows PC I use EASEUS Partition Master 6.5.2 Home Edition. It is freeware, and seems to work well. Then to format the micro SD I turn on mass storage in samsung settings, connect to PC and use the SD formatting tool 3.0 from sdcard.org. It uses FAT (not FAT32) and 32kb cluster sizes. I do quick format...
For more information and to report bugs:
http://code.google.com/p/omnia2droid/
Almar's (one of the developers) twitter:
http://twitter.com/INB2ENSECURITY
Big thread on Modaco:
http://www.modaco.com/content/i8000-omnia-ii-gsm-rom-discussion/322429/android-on-omnia-ii-i8000/
ummh when installing the heret.exe for the second time it stops for some reason
killerkarara said:
ummh when installing the heret.exe for the second time it stops for some reason
Click to expand...
Click to collapse
I had similar problems, stuck on the linux part. It said it couldn't mount mmcblk0p5, wich is the SDcard. I solved it by reformating my SDCARD in fat32 and it worked.
ive done step by step on what to do but its stuck on the linux boot screen last line displayed is jumping to heart and it stays there. any help would be awesome. ive installed everything to the my storage section on my phone
First of all: INCREDIBLE WORK!!! CONGRATULATIONS!!!
I've tested and it is working, but unfortunately it is freezing time after time...
I have tried this:
bobzero said:
Download 2d/3d drivers and install here (you need these else above beta will freeze every 5 mins):
To install 2d/3d drivers download o2bupdate.tar.gz and place in "My Storage\o2bupdate.tar.gz" , this should stop the phone from freezing every 5 minutes:
Click to expand...
Click to collapse
... but no difference
is this done using harnet?
yes it uses haret.
bobzero, there's a new updated kernel release by Almar...have you tried that out?
Is there any plan for supporting Omnia Pro (B7610)? Most of components are equally identical.
yes, it's working even better! battery drains slower now.
Soul_Master said:
Is there any plan for supporting Omnia Pro (B7610)? Most of components are equally identical.
Click to expand...
Click to collapse
definitely agree with the sentence
B7610 currently not officially supported by Almar's android
maverick_endit81 said:
definitely agree with the sentence
Click to expand...
Click to collapse
Currently Almar and his team only focuses on omnia i8000, perhaps there maybe a tiny possibilities that they will release a android for other samsung phone...try checking out forums and google
Below link is maybe useful to B7610 users: http://www.modaco.com/content/b7610...-android-on-b7610-thnks-to-devs/#entry1566239
i noticed some b7610 users on the modaco thread saying that it works, but with some additional glitches... wifi doesnt work, no menu button mapped...
try it out
bobzero said:
Video of Beta on Omnia II by Rapid81:
http://www.youtube.com/watch?v=8khXDEOO96Y
Click to expand...
Click to collapse
"This video contains content from Believe and Sony Music Entertainment, one or more of whom have blocked it in your country on copyright grounds."
EDIT - Ah. Been a while since I've tried, but you can use an anonymising proxy (I used http://www.hidemyass.com) to get around the restriction on YouTube.
Thanx Almar and other devs team..~~
just to share my method to make android working in my omnia..
format SD card thru samsung setting.. download and combine 1gb 18jan android + 19jan zImage update + 2d/3d patch together. after that I copy that bunch of files into omnia 'My Storage' root. (It content o2beta, default, ext.tar, haret, zImage)
first, run the haret.exe from 'My Storage/o2beta' !! . after press RUN wait till it finish with the partition. more or less than 10minute to get this done. after that, ur phone will auto restart.
after restart, run haret.exe from 'My Storage' root. !! press RUN...
Kabbooom... new life begin
I installed pro launcher n make it my default home screen n it run smoothly..
angry bird is playable too.. to make it short, Am AMAZED with this 1st beta..
just my 2 cents..

[Tutorial] install kitchen in linux en use it! tutorial thanks to theunlockr

Heey everyone here the quide for how to set up kitchen in linux virtualbox
Not made by me but made by the amazing guys from the unlockr Thanks!!!
Part 1
[I Before you begin]
1. This ONLY works for HTC Android devices at the moment, Also other devices!
[II. Download a Virtual Machine and Set It Up.]
1. Download VirtualBox for free from here (the one for Windows Hosts at the top). Then click next on the setup process until it installs.
2. Open VirtualBox and click on New.
3. Name the New Virtual Machine whatever you want (we named it Linux for simplicity’s sake).
4. For Operating System choose Linux, then choose Ubuntu for Version and click next.
5. Click Next again leaving the Memory Setting at what it is preselected at (should be 384mbs).
6. Click Next on the Boot Disk screen as well leaving boot hard disk and create new hard disk both selected.
7. Keep clicking Next until you get to the slider that asks how much space to set for the Linux. Move the slider to 8Gbs and click next.
8. Click next until it is done and shows you the original screen you started on but now with the Linux Machine Powered Off on the left.
[III. Install Linux Ubuntu on the Virtual Machine]
1. Download Ubuntu from here.
2. Once it is downloaded, in the VirtualBox program, click the Start button at the top.
3. Close out all the warnings that come up.
4. Then click on Devices > CD/DVD Devices > More CD/DVD Images… then select the .iso image for Ubuntu you downloaded.
6. Follow the prompts on the screen to install Ubuntu on your Virtual Machine.
7. Once it is installed and reboots, goto Applications > Accessories > Terminal and type this line with hitting enter at the end:
sudo apt-get install sun-java6-bin sun-java6-jre
It will ask you for a password, type in the password you created when you went through the Ubuntu installation process (it asked you for it before finishing the install).
Then it will ask you y/n. Hit y then enter. Then when it shows you the terms and conditions, hit right arrow on your keyboard and click enter to select ok. Then hit left arrow on your keyboard and enter to select Yes.
*NOTE – Your keyboard and mouse will not function on your regular computer once you use them in the Ubuntu virtual machine. To re-enable them, click the Ctrl button on the right side of your keyboard.
**IF YOU GET AN ERROR INSTALLING THE JAVA FILES,
Download the java files manually FROM INSIDE THE EMULATOR/LINUX using Firefox here:
Java6 Bin
Java6 Jre
Then open the Terminal App in Ubuntu and type this with hitting enter at the end of the line:
sudo dpkg -i sun-java6-jre_6.18-4_all.deb sun-java6-bin_6.18-4_i386.deb
And that should fix it.
[IV. Download and Setup The Android ROM Kitchen]
!THIS NEXT SECTION NEEDS TO BE DONE WITHIN THE UBUNTU VIRTUAL MACHINE!
1. Click on the Firefox logo at the top of your Ubuntu installation (in the Virtual Machine).
2. Type this into the url box:
theunlockr.com/2010/03/26/how-to-create-your-own-custom-rom-for-android-part-1-setting-up-the-kitchen (to navigate to this page from within the virtual machine).
3. Now download the latest version of the kitchen file  in the first post from the link below(again from inside the Ubuntu installation on the virtual machine. We are doing this because we want to save this file in our Ubuntu Virtual machine, NOT our regular computer).
Kitchen
4. Again on the Ubuntu machine, Find the .zip file you just downloaded, right click it and click open with Archive Manager and then click Extract at the top.
5. Once you click Extract, it will ask you where. Double click the folder that has the name you created when you installed Ubuntu (my username was theunlockr so my folder is called theunlockr. It is the first folder under recently used in the list on the left). Then click Extract at the bottom right.
[V. Run the Android ROM Kitchen]
1. To run the Android ROM kitchen, click on Applications at the top of Ubuntu > Accessories > Terminal then type the following and hit enter:
./menu
2. You will now be greeted by the simple text menu of the application. Enjoy!
VI. Create Your First Custom ROM
=================================================
Part 2
Before You Begin
1. We are assuming you have already setup the Android kitchen. If not, use our How To Setup The Kitchen procedure and then come back to this one when done.
2. We are also assuming you have already done our How To Root and How To Load a Custom ROM for your phone and have a custom recovery image.
2. This ONLY works for HTC Android devices at the moment, Also other devices
3. Open the Kitchen in your Ubuntu Virtual Machine we created in the Kitchen Setup procedure by typing ./menu in the Terminal window in Ubuntu. Leave it open.
4. All of this is done INSIDE THE UBUNTU VIRTUAL MACHINE (that includes when I say “save to your computer” anywhere in here, means save to you Ubuntu Virtual Machine)!
II. Find a ROM to Dissect
There are two kinds of ROMs you can dissect to create your own custom ROM; Stock ROMs and Custom/Cooked ROMs. DsiXDA, creator of the ROM kitchen we are using, has put together a list of places to get stock ROMs for different devices and a quick how to load them into the kitchen:
From a Cooked ROM (Easiest Method):
1. Copy the update.zip (or equivalent ZIP file) to the original_update folder in the kitchen
2. Type the number for the option “Setup Working Folder from ROM” and hit enter in the Kitchen to create your working folder. (So if its number is 1, type 1 then hit enter).
From a Shipped ROM:
1. Find the shipped ROM for your device, usually from htc.com or from searching xda-developers (check the Wiki or sticky posts under your device’s sub-forum).
The links below may help:
2a. If the shipped ROM is in a .ZIP format, then simply extract the system.img and boot.img.
2b. If the shipped ROM is in .EXE format, then do the following:
A. In Windows, run the shipped ROM’s .EXE file till it gets to the first dialog. Stop there but don’t close the window yet.
B. Go to Start->Run and type: %TEMP%
C. When the folder opens, search for Rom.zip. Then, open it with an unzip tool. If you get errors trying to open the ZIP file with WinZip or the default Windows unzip program, then use 7Zip (download from here) to extract it.
D. Extract only two files from Rom.zip: system.img and boot.img
3. Copy the two .IMG files to your kitchen’s img_files folder in your Ubuntu Virtual Machine.
4. In the Terminal window that you opened in Section I, type 1 and hit enter to create a working folder from the two .img files.
Now, that you have either the update.zip in the original_update folder of the kitchen OR the system.img and boot.img of a shipped ROM in the img_files folder of the kitchen, you are ready to play with the ROM to make it your own.
III. Tweaking the Imported ROM Using the Automated Options in the Kitchen
So this is a basic kitchen, but you can do things like, add Root support, add/remove apps from the ROM, enable saving apps to the sd card, enabling Wifi tethering, do some automatic optimizations, and a few other things automatically just by selecting the option and hitting enter. It even allows you to put in your own scripts for the ROM to run (but that’s for more advanced users who know how to create scripts of course).
1. After importing a ROM using section II, select the options you want to do to the ROM (by typing the number of the option you want into the terminal/kitchen window and hitting enter. They are all pretty self explanatory.)
2. Continue this until you have all the automated options you want in the new ROM.
IV. Adding/Removing Applications from the ROM
1. In your Ubuntu Virtual Machine, goto Places at the top. Then click on Home Folder, then the WORKING folder that was created in section II when you dissected the original ROM or img files. Then goto system > app. (Also check Data > App as .apks can be put in there as well).
2. In the app folder you will see all the .apk files for all the applications you have currently in the ROM. Simply delete the ones you do not want to remove them from the ROM.
3. To add applications, simply copy any .apk file for the applications you want to add into the app folder.
V. Repackage the ROM so it can be Flashed onto a Phone
1. Once you have done whatever changes you want, you just need to type 99 and hit enter in the kitchen/terminal for the kitchen to take the working folder you have been messing with and compile it into a flashable update.zip ROM.
2. Once it is done compiling the ROM, we can transfer it to our phone.
VIa. Setup Ubuntu to See Your Phone via USB
1. In the Virtual Box windows with Ubuntu in it, click on Devices at the top then click Install Guest Additions. (It should autostart, if it doesn’t, click on the CD that appeared on the desktop in Ubuntu and then click on Autostart.sh. It will ask you for your password you created when setting up Ubuntu, put that in and let it install).
2. Once the Guest Additions are installed, close the Virtual Box Ubuntu Window (choose to Power Down the Machine).
3. Now, open Virtual Box itself (not Ubuntu) and highlight the Ubuntu machine, then click on Settings at the top.
4. Click on USB and make sure Enable USB Controller and Enable USB 2.0 are both enabled.
5. Now plug in your Android phone (do NOT mount the SD card, just plug it in).
6. Now in the USB menu of Virtual Box, click the + symbol on the right and then select your Android Device (name may be different).
7. Once that is installed, unplug your phone.
8. Now, Start your Ubuntu Virtual Box.
9. Once Ubuntu boots up, plug in your Android phone (do not mount the memory card yet) and look for the USB symbol at the bottom (fourth icon from the left) and hover over it and wait for it to say USB Device detected and display your phone. Once that happens, mount the sd card by pulling down the notification bar on your phone and clicking mount.
10. Ubuntu should pop up your SD card on the desktop (if any prompts come up just select do nothing and click ok). We can now transfer files to the memory card of our phone.
VIb. Use RapidShare to Transfer the File from Ubuntu to Windows (if Section VIa was giving you trouble)
1. If you can’t get the USB to work in Ubuntu, then simply open a Firefox browser window, goto Rapidshare.com and upload the ROM to there.
2.Once it is done uploading, ON YOUR WINDOWS COMPUTER NOT UBUNTU, put in the link it gave you when you finished uploading it, to download it to your Windows computer so we can transfer it to your phone.
VII. Flash the ROM
5. Copy the .zip file to the root of your SD card (NOT in any folders, just on the SD card itself).
6. Unplug the phone and turn it off.
7. Turn it back on by holding down home and power (do not let go until the recovery screen comes up) to get to recovery mode (you must have a custom recovery screen to do this, if you don’t find out How To Root and Load a ROM procedure for your phone and do those first).
8. Now select Nandroid Backup to create a backup before we flash the new ROM.
9. Once the backup is done, select Wipe Data / Factory Reset in recovery mode.
10. Select flash zip from sd card and select the ROM you just put on the sd card.
11. Once it is done flashing, click reboot. Enjoy!
Enjoy! Will update this as we add more things for you to tweak Feel free to suggest some in the meantime.
Thanks to DsiXDA for his awesome kitchen!
Thanks to Theunlockr For the amazing Guide !!!
greetings safariking
Video tutorials:
Part 2:http://www.youtube.com/watch?feature=player_embedded&v=q-1ErGSW0ik
Part 1: http://www.youtube.com/watch?feature=player_embedded&v=94Az1kcQvc4
Thanks safariking!
Thanks
very good tutorial thanks
Hi there
Does Android Kitchen Only work in virtual Machine for Ubunty? I have a full installtion of Ubunty and when I type ./menu at the terminal "no such file or directory" followed the installation video but I ain't getting nowhere
Cheers
atomicsoul said:
Hi there
Does Android Kitchen Only work in virtual Machine for Ubunty? I have a full installtion of Ubunty and when I type ./menu at the terminal "no such file or directory" followed the installation video but I ain't getting nowhere
Cheers
Click to expand...
Click to collapse
no.
kitchen can be used on all Linux/Unix OS.
中国人正在尝试提高!
(translation:Chinese people are trying to improve themselves!)
Very nice job. We thank you for your time and effort for writing all of that
Thanks
Sent from my GT-S5660 using xda premium
Just a note: linux isnt required
You can use windows, but does require to install cygwin (linux like terminal)
Sent from my GT-S5660 using xda premium

[TUTORIAL]How to setup SP_Flash_Tool_Linux (MTK/MediaTek Soc)

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

[Guide] ALLDOCUBE X NEO Flash Class 101

Hello and welcome here.
I’m Warren, an X NEO user from Mainland China .
X NEO is a great device that opens all low-level permissions to users, but it is undeniable that it is far more difficult to flash than Xiaomi's devices, especially the logic of the A/B partition。
Fortunately, through the help of many people, I successfully overcome many difficult problems, and now I decided to write a Thread like a guide book to integrate some basic knowledge of the flash to X NEO.
Each part of this post will contain the following:
a) Materials needed for flashing
b) Instructions for flashing steps
c) Possible problems and solutions
Attention !!
a) I will spend some time (maybe a few days?) to update everything
b) All content is written in simplified Chinese and translated into English by Google translation machine for reading. This is due to forum restrictions
c) Due to the use of machine translation, the grammar and vocabulary are unavoidably rigid, and I don’t want to manually proofread him for the time being. Because I don’t have enough energy, I have written the original document as closely as possible to the English writing logic
d) I understand English, so I can send out any questions or private messages without worry
e) The content of the post is my own original, but many materials and ideas are provided by users at home and abroad, including several masters from XDA and hardware forums. I just did some trivial sorting and reproduction work, here Thank them for their hard work
f) Have fun
#0 Preparation
Step 1 Download materials & prepare environment
This part is very important, it will be directly related to the success or failure of subsequent work (because of lack of necessary environment or materials)
How to do?
1. Save the file in this MEGA address: HnwhAIhJ#uVaWZIzUOUcAIwAbcrNMsg
2. Download ADB
3. Unzip (you can move the unzipped folder to any place you like)
4. Remember this path. Anytime I say "Run an ADB command/open ADB input", you can open this path, right-click on the blank space of the folder to open the command prompt book and enter the command.
5. Download Magisk on github
Step 2 Flash your device to the Chinese version of the firmware
a) This is because the Chinese version of the firmware is more modifiable than the overseas version
b) The following content will be based on the "200522" firmware (I know this is not the latest, but the updated version has not been confirmed by me)
c) If you insist on downloading the latest firmware, you can go to the official website of Cube China
How to do?
1. Download "XNeo(T1009)-Android9.0-200522-Firmware&Tutorial.rar" in the "Firmware-China" folder of MEGA and unzip it
2. Follow the official instructions in the folder (documents in the root directory) to flash the firmware
note:
a) The device can and can only be flashed in Qualcomm 9008 mode (the official data cable supports this function)
b) The official instruction book is in simplified Chinese, if you don’t understand Chinese, translate it
Step 3 Confirm ADB environment and OEM unlock
How to do
1. Open ADB
2. Type "ADB" and press Enter (the self-check information indicates that the environment is established successfully)
3. Turn on the tablet
4. Enter Settings-System-About Tablet
5. Click the version number until the floating prompt appears
6. Go back to the upper level (system) and enter the developer options
7. At this time, "OEM Unlock" should be opened automatically and cannot be changed
8. Click to open "USB debugging" and connect to the computer to activate the function according to the prompts
9. Click to open "Verify App via USB" to activate the function
#1 Official system customization
a) First of all, the official version of the system is a typical simple ASOP system based on Android 9. It is not much different from third-party customized systems such as Los to a certain extent. If you don’t want to be too tossed, you can use it directly after optimization according to the following guidelines
Step 1 Brush into third-party REC (TWRP)
a) N/A
How to do it?
1. Download "TWRP-CUBE_X_Neo-20200522.img" in the "TWRP" folder in MEGA
2. Copy to the path of ADB
3. Open ADB
4. Type "adb devices" and press Enter
5. Type "adb reboot bootloader" and press Enter
6. Type "fastboot flash boot_a .\recovery.img" and press Enter
7. Enter "fastboot flash boot_b .\recovery.img" and press Enter
8. The flashing completion prompt is displayed twice
9. Now that TWRP has been successfully swiped in, you can enter the recovery mode through the volume button and power button
note:
a) Flashing into a third-party REC will cause OTA failure (over-the-air upgrade is not possible)
Step 2 Flash into Magisk
a) Have Root permissions
b) Flash into the module
c) Conveniently flash into the XP framework
How to do?
1. Enter rec
note:
a) You can use the same method to flash in GAPPS components (Google and download by yourself) to use GMS components and related services
b) Magisk version 21.0 is recommended, which is beautiful and will not automatically fail
c) Recommended modules: font module, scheduling module (search and download by yourself)
Step 3 Flash into the XP framework
a) Use certain software/modules that require special permissions and environments
How to do?
1. Open Magisk
2. Go to the online module library that comes with Magisk
3. Find the Riru-Core module to download and install
4. Find the Riru-EDxposed module to download and install
5. Restart the phone
6. Install and open Edxposed Manger (Google and download by yourself) to activate the module
7. Restart the phone
8. Success
note:
a) Edxposed chooses the YAHAFA version instead of the SANDHOOK version
b) Recommended modules: Youtube background playback related, exercise count modification related, camouflage location related, social software beautification and additional functions related
Step 4 Install auxiliary software
a) Green Guardian: Clean up the background and make 4G memory run smoothly (GooglePlay recommends buying genuine)
b) Streamlined version of fluid gesture software (increase system-level full-screen gestures)
c) Force to rotate the old version of the software (add system-level software horizontal screen support)
d) The download links of the above two apps are too low and I can’t send them out. You can get them by private message
Step 5 Uninstall pre-installed third-party software
a) Complete through a third-party software manager
b) The system software can also be appropriately streamlined (pay attention to safety)

[GUIDE] IMEI / Connection Repair on Asus Zenfone 2E ZE500CL Z00D

[GUIDE] IMEI / Connection Repair on Asus Zenfone 2E ZE500CL Z00D
I am writing this guide because I recently recovered a bricked ZE500CL and after flashing around so many different files I lost my IMEI and connection abilities. After a little research and some thought I easily repaired my IMEI and restored my connection abilities. Just follow the steps below. I don't have this phone long and I am still learning so some of these steps might not be needed. Nevertheless it DOES work if you follow it properly.
What you will need:
1) Asus Flash Tool - https://drive.google.com/open?id=1n7tJr7lAlPnL8-nmK8f5kGmDHbRv5gxo
2) Asus Phone Drivers - https://drive.google.com/open?id=11XLRW5pEScYdBYwh0vDM-Wup9orGPWDf
3) Debug Service Firmware - https://drive.google.com/open?id=1ISofitM3yhYpu46JD0KWGLXybvtLQyAy
4) Intel Phone Tool - https://drive.google.com/open?id=1dQjjlHjWs8tDrfNU_ikgesKK2uKaTyXt
5) Intel Drivers - https://drive.google.com/open?id=1hE9j35VMOD5QGHjDy_aM2vVCs2PVOOm1
6) ADB / Fastboot Tools - https://drive.google.com/open?id=1nbAS8k4JMAXG8YH2qIFHpRjX60TTlYIt
7) IMEI Number - You should have this. If not generate one based off another ZenFone 2E Z00D's IMEI.
8) ZenFone Root Tool - https://drive.google.com/open?id=1NHf516Yex9KfsnufVNz0vkchJWCiMHo2
9) Root File Browser (ES File Explorer, Root Browser etc) - Get from the internet, place on your phone via MTP file transfer or push/install it in adb.
NOTE: If you choose the first way you will have to go into your debugging app in the applications. It will be the one with the magnifying glass and says Asus Log something on it. I no longer have the Service Firmware installed so I can't remember. You will find it though. Once you do go in and find the usb settings and just change modes and you will see the drivers install and device ASUS_Z00D or something similar should appear in device manager under devices. If it fails to load make sure you have the correct ASUS Drivers installed and if that doesn't work the last way is to select the ( ! )Driver and then manually install the USB MTP Device driver which will fix the issue.
10) Factory Folder Backup (This MIGHT not all be needed, still checking to make sure.. for now include it) - https://drive.google.com/open?id=1fvH0QdrzLFM34vsm2KNfQBU5fr8eSM14
First Step:
Download everything above and then install 6,2,5,4 (Install the drivers that come with Intel Tool before installing it. You should be prompted during installation) and then install 1.
Second Step:
Open Asus Flash Tool and make sure your phone is connected to the computer and you are in fastboot mode.
You can get there 2 ways. (1) Turn the phone off, hold Vol+, then push the power button, and when you feel it vibrate release the power button while holding Vol+. (2) Open command prompt and enter "adb reboot bootloader" (this is if you're adb is setup system wide, if not navigate to your SDK Tools folder and enter there).
Flash the Debug Service Firmware you downloaded. Check WIPE to wipe before flashing.
Once you see the phone boot up goto the next step.
Third Step:
Open Intel Phone Tool and follow this guide here to fix your IMEI! -
NOTE: You can skip the setprop commands he enters into adb shell in command prompt. This firmware already has the COM Port opened and USB Debugging enabled for you.
Fourth Step:
Now you will need to root your phone using the Root Tool I linked in the beginning (Do not worry about upgrading the SuperSU Binary.) Next you will need to install a root browser on your phone like ES File Browser, Root Browser etc. Something that allows access to root / hidden files. Navigate to /Factory and /Config and backup these two in their entirety to your MicroSD card or computer. Replace your factory with mine if it is empty and doesn't contain the files in the steps below. Now comes time to edit. Makes these changes to the files. (I am not 100% sure which all DO need to be made so I just modified most all of the values.)
These instructions are thanks to @BORETS24
I have changed them a tad as our handset differs from the one he wrote them for. I am still not entirely sure if everything needs to be copied/modified. Don't have a lot of spare time on this handset to figure out everything. I just know from testing this will get your phone functioning again.
Serial number, WI-MAC, BT-MAC repair instructions
(You will be replacing everything after step 5. Below explains what to edit.)
1. If you have an empty factory partition, use the archive, replace factory folder with archive version to root file system via file manager, ES File Explorer or others (root required and root browsing required of the application). Serial Number, WiFi MAC, BTMAC, colorID you may see on box from phone (or make up something for each value). .. you can generate the WiFi MAC based off these Unassigned? Assignments - 00:90:4C, 00:09:4C or just make one up based off a random Assignment from here - https://regauth.standards.ieee.org/standards-ra-web/pub/view.html#registries. For the Bluetooth - 22:22:AF or something you find on the previous site. You can check easier after you generate here - http://www.coffer.com/mac_find/. For color ID I left mine the same as what is in the factory.zip which is Silver.
2. Then open and edit factory/PhoneInfodisk/bt_addr.conf- this BT MAC, replace 00:00:00:00:00:00 numbers to your MAC.
3 Then open and edit factory/PhoneInfodisk/colorID- color code of your phone. For example silver is 6J.
4. Then open and edit factory/PhoneInfodisk/PhoneInfo_inf- 6F0000000 (yours will be 12 numbers) replace to your serial number, 1C002C... change to you BT-MAC, 00B72... change to your WiFi MAC, 6J change to your color code, RU... change to US,EU,CN,TW,RU (do not think this matters much). I changed mine to US I think.
5. Then open and edit factory/PhoneInfodisk/ssn- enter your serial number replacing 0000000. (12 numbers)
6. Then open and edit factory/wifi/mac.txt- enter your WiFi MAC replacing 00000.
Fifth Step:
Open Asus Flash Tools and flash desired build of RAW firmware over the Debug Service Firmware. I suggest the latest WW firmware which is ver .126. From here you can stay on this firmware after replacing the files below or surf around XDA and find out what customized ROMS are available for this phone. Personally I unlocked my Bootloader, flashed TWRP, flashed .126, flashed Resurrection Remix 5.8.4 ? on Nougat 7.1.1 and then flashed a SU. RR I wouldn't recommend as it is buggy and neither would I of MoKee as it is buggy as well. I am fixing the bugs in RR so it runs fine as I particularly like RR over others since it comes pre installed with a horde of features so you can customize your handset to your hearts desire.
1. Install a root File Browser and root your phone again.
2. Replace /config with your backed up /config.
3. Replace /factory with your backed up /factory.
4. Reboot.
Now check everything in settings and make sure it looks right. All should look A-OK except for serial #. I am still working on that and will edit this once I finish. Layout of our phone is different than the one I took files from. You might have to replace the file again if you flash certain custom ROM's. I flashed RR and didn't have to.
EDIT: After a few reboots I seem to lose my MAC's again and the serial (unknown) is replaced by Medfield1534DD97. Both WiFi and BlueTooth still work though. You just have the random default generated MAC's. I can live with that as long as it works. Though if anyone can shed some light on this issue or anything else I would be extremely grateful.
Enjoy Your Phone!
-------------
For the Asus Zenfone 2E ZE500CL Z00D I will be uploading in the near future somewhere an organized package compiled of all recoveries, roms custom + stock firmware, root, bootload unlockers, tools, apps and guides all together so you can easily download and skip the time consuming research I had to endure. It is around 10GB. I am officially done learning this phone now. It has been a long 3 days and now it is time to ship it out to a buyer. =]
XDA: noidodroid

Categories

Resources