Related
This is now discontinued use 2.6.39 build
This is the current state of CyanogenMod 9 for the Toshiba Folio 100
WARNING
This is very experimental build use at your own risk.
CyanogenMod 9 is a work in progress so many thing could be broken
Use only if you understand what your doing.
Flash with CWM, and don't forget to wipe data.
Download ( Last updated : 20/01 ) :
https://rapidshare.com/files/3517203985/update-cm-9.0.0-RC0-folio100-KANG-signed-r4.zip
or
http://dl.free.fr/imlPygB4F
Gapps :
http://www.megaupload.com/?d=04YNQPLZ
Device tree code :
https://github.com/nopy/android_device_toshiba_folio100
Kernel sources :
https://github.com/nopy/kernel_folio100
Working :
- UI
- Wifi
- Bluetooth
- Sensors
- Audio
- Gapps
Not Working :
- camera
- HD Video ( probably never on 2.6.32 )
....
and many more things as it is not fully tested
Update 03/01/2012 :
- Speed improvement
- Fix network and gapps
- Add network usage graph
- Use wifi driver build from sources
- Known issue : sometime wifi stop working after suspend
Update 12/01/2012 :
- Wifi suspend issue fixed
- mtp
- Some "tuning"
Update 20/01/2012
- No device specific changes, just CM upstream changes. this fix some game that was crashing with the previous update
- a semi-working camera : preview corrupted, camcorder FC , but take picture working ...
A video from daveheart ( frandroid forum )
If you want to help, you're welcome, fork on github and send pull request
All credits go to the CyanogenMod team
Huge ! huge! Your the man keep up
thanks for another WIP for our folio
hey man thank u for don´t let folio diw if this rom stay stable we all can donate to you!
Thanks, nice to see someone working in our tablet
Quite impressive, taking into account that it's an experimental release.
Must i flash Kernel too?
Sorry, I'm asking just for sure
Hello.
First for all i want thanks for your nice work and sorry for my bad english... I tried your rom today and i tested some bugs, i hope i can help you:
1º Wifi. I think wifi is semiworking because i installed apk like applanet and i had got a net error. I installed too "Es file Explorer" and i cant access to my pc by lan.
But we can access to webpages without any problem but we can't download any file.
2º Gapps. As u said we can't use gapps. I tried install gapps for CM9 and i had got a loop in homescreen tutorial
3º USB. Usb doesnt work. I can't connect my tablet to my pc for transfer files.
4º Usb host is working!! I have got a external keyboard for my tablet and it works.
This version work nice for be an alpha version (smooth and stable). I think well have a stable version on our tablet soon.
Thanks for this hard work of our developers.
hello
I have installed your rom. I have installed this for the market and all this stuff. I have found that here. The problem is when I try too set my google account than he said "Can not make a reliably connect to the server". How I fix this problem? Than second thing I have seen that not work is the hardware 'home' button. The rom work also very slowly. But after a time the speed is acceptable.
HDMI output also work good!
Thank for all your hard work.
Guys!
Did you flash kernel too?
That's kernel source, not compiled one. It can't be flashed.
sd card doesn't work
hey there first of all i would like to thank you for your work for folio
when i try to install your rom i get
Code:
assert failed: getprop("ro.product.device") =="folio100" || getprop("ro.build.product") == "folio100" getprop("ro.product.device") == "betelgeuse" || getprop("ro.build.product") == "betelgeuse"
does anyone know what to do ??
You have to install another version of CWM(try with one from my signature) or delete all getprop lines from updater-script.
neither of this solutions worked
Saint9192 said:
neither of this solutions worked
Click to expand...
Click to collapse
I had the same problem. Somewere in the folio 100 part of the forum they talk about installling an other recovery, for me this solfed the problem.
That I said. I think that's in CM7 thread.
Sent from my IDEOS S7 Slim using XDA App
I tried 2 CWMs but nothing...still getting the same error
Which recovery is working?
Saint9192 said:
hey there first of all i would like to thank you for your work for folio
when i try to install your rom i get
Code:
assert failed: getprop("ro.product.device") =="folio100" || getprop("ro.build.product") == "folio100" getprop("ro.product.device") == "betelgeuse" || getprop("ro.build.product") == "betelgeuse"
does anyone know what to do ??
Click to expand...
Click to collapse
Boot in recovery and post the results of
Code:
adb shell grep ro.product.device default.prop
i finally got it working with this CWM
Saint9192 said:
i finally got it working with this CWM
Click to expand...
Click to collapse
Finally this CWM works for me!
Great for your work,Nopy!
Now we really need working Gapps,keep working,please
The Acer Iconia Toolkit is supporting following devices at the moment:
B1-A71
B1-710
B1-A710
B1-711
B1-720
A1-810
A1-811
A3-A10
Liquid S1
Only use these methods if you are sure the device cannot be rooted using a custom recovery from the following thread:
http://forum.xda-developers.com/andr...ax-b1-t2875894
Intel based devices will not be supported ever by this toolkit! Only Mediatek chips are supported!
At the moment the following features are available:
Root from scratch (Unix only / recommended)
Root with prerooted Image (see Download links at the bottom)
Unroot
Swap External <-> Internal SD
Odex ROM
Pull system.img.gz off your device
Download Acer Iconia Toolkit Latest Version
Older Versions:
v0.9.0
v0.8.5
v0.8.4
v0.8.3
v0.8.2
Thank you goes to:
FireDiamond, bullbrand, pawitp, alba81, sodaFR, MatrixDJ96, ak6, min-dfreak, Gilly10, agentdeep, nick_1964, sampod
and the testers
Acer Iconia B1-A71:
Unlock Bootloader
CWM update, that removes bloat
thx to FireDiamond
Apply the "Invalid Partition Error" fix before rooting!!!
To avoid unfixable bootloop, first apply this patch from Acer.
Install the APK, start it, click on FixG1PMT (no feedback) and uninstall afterwards. Good luck!
If you're rooting with prerooted system.img.gz here are the Downloads. Pick the one, fitting to the firmware installed on your tablet, otherwise you will get into bootloop!
RV03RC05:
Acer Firmware Update [mirror] [mirror + md5]
RV04RC04:
[system.img.gz] [mirror]
RV05RC05:
Acer Firmware Update [mirror1] [mirror2] [mirror3] [mirror4 + md5] [mirror5 + md5]
[system.img.gz]
RV02RC12:
system.img.gz
Acer Iconia B1-710 / B1-A710:
Unlock Bootloader (thx to FireDiamond and abstrkt1337)
RV04RC01:
system.img.gz [mirror1] [mirror2]
Stock system Images for B1-710 RV04RC01
Hamza91: stock, rooted
RV04RC01_PA_CA:
Stock and Rooted system image
Acer Iconia B1-711:
RV01RC04_WW_GEN1:
system.img.gz
Acer Iconia B1-720:
RV03RC01_WW_GEN1:
system.img.gz (thx to Hayastan)
RV07RC01_WW_GEN1:
system.img.gz (thx to Hayastan)
Acer Iconia A1-810:
Acer Firmwares
Modified XPosed Installer
RV03RC08:
system.img.gz
RV18RC07_WW_GEN1:
update.zip (about 4MB)
system.img.gz with /system RW workaround (MD5 = 214db984aee42ef0c05d1cfa43d193c1) (needs extra config and SuperSU instead of Superuser) [torrent] (see this post also)
RV21RC02_WW_GEN1:
update.zip
system.img.gz with /system RW workaround (needs extra config and SuperSU instead of Superuser) (see this post also)
RV21RC03_TWN:
system.img.gz with /system RW workaround (needs extra config and SuperSU instead of Superuser) (see this post also)
RV27RC02_PA_CA:
stock system.img.gz (rename to system.img.gz first!)
system.img.gz (rename to system.img.gz first!)
RV27RC03_WW_GEN1:
system.img.gz
stock system.img.gz
update.zip
RV18RC10_PA_CA:
system.img.gz with /system RW workaround (needs extra config and SuperSU instead of Superuser) (see this post also)
RV26RC06_PA_CUS1:
system.img.gz
Stock Images: (Workaround to unroot: Put the system.img.gz of your version into system_image and choose root option in toolkit)
RV03RC08:
system.img.gz
RV18RC07:
system.img.gz ( MD5=550ECDB192F5668264B11B1070F4B932 )
How to root from scratch
Acer Iconia A1-811:
RV01RC11_WW_GEN1:
Acer Firmware Update
RV02RC20:
system.img.gz rooted and stock (including xposed) (thx to konsolen!!)
RV02RC22_TWN_GEN1:
system.img.gz with /system RW workaround (needs extra config and SuperSU instead of Superuser) (see this post also)
Unbrick:
Stock Firmware RV01RC11 (copy on SD and flash from recovery)
Acer Iconia A3-A10:
A3-A10_RV05RC01_PA_CA:
stock system image
Your device not listed above?
Help us getting your device to work with the toolkit.
See this post how you can help.
Common
B1-A71 / B1-710 / B1-A710: Install this after rooting: Superuser App on Google Play Store
A1-810 / A1-811 / B1-711: Install this after rooting: SuperSU App on Google Play Store
Verify your root: Root Checker on Play Store
FAQ
Q: I'm stuck inside a bootloop after rooting!!!11
A1: The system.img.gz you applied, wasn't suiting to the firmware version installed on your tablet. Download latest Acer firmware update ( !!! if available !!!), copy it on a micro sd card, plug it into your Iconia, go to recovery by holding Volume up and Power button while device is turned off. Then choose apply update from sd card.
A2: If you cannot apply any Acer firmware, because you always get a partition error while installing, you should do a reboot after you get the error. A user reported that this made her/his device boot into Android again, showing the new version in settings -> info. Good luck
A3: If your device is really bricked you could try bring it back to life. Here you find help: link1, link2, link3, link4 (many thanks to Gilly10, drmad and Hamza91)
A4 (B1-A71, B1-710, B1-711 only): Unbrick
A5: If the A1 - A4 didn't help. Send back the device to Acer. Tell them you tried to apply an update from sd card and ended up in this bootloop. Sending device back to Acer over UPS is free. Good luck!
Q: Successfully rooted, but still no root after rebooting!
A: Have you installed Superuser App from Google Play Store?
(B1-A71 only)Q: Cannot update, always getting ERROR: - Invalid partition setting; 17: fat 238e8000:888e8000; Instalation aborted.
A: Download "Invalid Partition Error" Patch.
(B1-A71 only)Q: I applied update from RV05RC05 to RV05RC06 but still it shows RV05RC05.
A: There is no RV05RC06. It is the RV05RC05. It got on Acers Download section with a RV05RC06 named zip file. But the content is 100% equal to RV05RC05.
Q: Toolkit fails or crashes for any reason and I don't know what to do.
A: Run it again with parameter -d, e.g.: toolkit.exe -d and post the entire output here.
Q: Root from scratch on Linux doesn't work because of Error message: 'No such file or directory bin/posix/64/adb'
A: sudo apt-get install ia32-libs libstdc++6 libgcc1 zlib1g libncurses5 libsdl1.2debian
Q: Can i flash a custom recovery?
A: No, because bootloader is locked. You would brick your tablet.
Q: Are there Custom ROMs?
A: No, see answer above.
Q: Is my data wiped during root?
A: No.
Q: Do i lose root after factory reset or wipe date?
A: No.
Q: I get an error in Engineer mode entering telnet command.
A: If Swiftkey is installed / enabled try settings Google AOSP Keyboard as default.
Q: How can I start telnet server manually?
A: Try this.
What you can do with root:
Apply Supercharger V6 by zeppelinrox and significally speed up your tablet! [My small How-To]
Install Adaway, an ad-blocker for webbrowsers and apps containing ads.
Install ROM Toolbox and customize boot screen and other funny things.
Install Titanium Backup to Backup, Freeze, Uninstall any App and more.
Install Datasync to sync app data like save states between rooted devices.
What you can NOT do with root on these devices:
Change DPI
Flash Custom Recoveries
Flash Custom ROMs
Sources and Changelos @ github (thanks to nikagl)
Changelog:
v0.9.4
======
- Updated SuperSU to 2.46
- Removed Xposed APK
- Added Liquid S1 support!
v0.9.3
======
- Fix Xposed removal
- Wait longer for MTKLogger to press settings
- Add 811 and KK 810 and 811 to root from system.img
v0.9.2
======
- Removed Xposed till it works
- Add global for allatonce
v0.9.1
======
Added option to enable write access to external sdcard
Added comment for Xposed not working
Removed su delete command in invalid section
v0.9.0
======
- A1-811: Kitkat Support
- A1-xxx: Added proper su-binary
- Added timestamps
- Added descision for Superuser/Supersu
- Added selection for Xposed **not working yet**
- Added option to enable write access to external sdcard
- Added selection to continue automatically (also import the system instead of waiting for enter)
- Removed invalid quote and double exit command
- Added forward delete of characters to make sure Run command is empty
- Added some additional messages during the root process
v0.8.5
======
- A1-810: Fixed target directory for system image (no permissions for /cache directory since Kitkat)
- A1-810: Fixed root from scratch for Kitkat versions (thanks to Just_Another_N00b)
v0.8.4
======
- A1-810: Fixed root for Android Kitkat >= 4.4.2
- A1-810: Fixed abd devices id, changed sind Kitkat update
v0.8.3
======
- Fixed pulling system.img.gz from Windows
v0.8.2
======
- New: Supporting B1-720
v0.8.1
======
- A1-81x: Fixed missing read/write permissions for /system partition (thanks
to twu2!)
- All other devices: fixed missing path to su binary (thanks to arzakon.nn)
v0.8.0
======
- New: Pull system.img.gz from your tablet
- New: Supporting A3-A10
v0.7.8
======
- fixed Swap Internal to External for A1 and B1-710
v0.7.7
======
- Supporting Swap Internal to External for A1 and B1-710
- fixed bug in root from scratch: checking for /bin/su although it's not there
Full Changelog inside the Download.
Error "Permision denied"
entonjackson said:
Changelog:
v0.2.1
======
- Windows: Providing an .exe, so Python is no more needed for Windows users. But you could still use the Python script.
- Unix: Python3 compatibility fixes
v0.2.0
======
- supporting windows 64 and 32 bit (only for rooting with prerooted system.img.gz)
- Linux: added option to choose between 'Root from scratch' and 'Root from prerooted image'
- supporting all versions between python 2.7.4 and 3.3
v0.1.1
======
- supporting linux 64 AND 32bit
- instructions at the beginning
- make compatible to python 3.3
v0.1.0
======
- initial release, only supporting linux 64bit
Click to expand...
Click to collapse
Hi Thanks for your effor and sharing with us.
I got error "failed to copy system._image\system.image.gz to cache/system.image.gz , permission denied
can you give me solution.
thanks very much
cakadut said:
Hi Thanks for your effor and sharing with us.
I got error "failed to copy system._image\system.image.gz to cache/system.image.gz , permission denied
can you give me solution.
thanks very much
Click to expand...
Click to collapse
Windows or Linux?
edit: Ok i found the issue, I just fixed it and going to upload a new version this evening.
New version v0.2.2 is up.
entonjackson said:
New version v0.2.2 is up.
Click to expand...
Click to collapse
I thanks for your work.
I have one problem
failed to copy 'system_image\system.img.gz' to '/cache/system.img.gz': Permissio
n denied
Traceback (most recent call last):
File "easy_root_iconia_b1.py", line 724, in <module>
else:
File "easy_root_iconia_b1.py", line 26, in main
win_main(python3)
File "easy_root_iconia_b1.py", line 642, in win_main
out = p.stdout.readline()
File "subprocess.pyc", line 575, in check_output
subprocess.CalledProcessError: Command ' bin\windows\32\adb.exe push system_imag
e\system.img.gz /cache' returned non-zero exit status 1
Thanks for your futur help
sorry for my english
V0.2.2 still Error
entonjackson said:
New version v0.2.2 is up.
Click to expand...
Click to collapse
Dear Eaton,
after dowbload and run v0.2.2 , still found same problem.
No Progress bar during copy image.
and system shown
failed to copy 'system_image\system.img.gz' to '/cache/system.img.gz': Permissio
n denied
Traceback (most recent call last):
File "easy_root_iconia_b1.py", line 724, in <module>
else:
File "easy_root_iconia_b1.py", line 26, in main
win_main(python3)
File "easy_root_iconia_b1.py", line 642, in win_main
out = p.stdout.readline()
File "subprocess.pyc", line 575, in check_output
subprocess.CalledProcessError: Command ' bin\windows\32\adb.exe push system_imag
e\system.img.gz /cache' returned non-zero exit status 1
Note I am using windows 7.- 64 Bit
Regards,
I uploaded a new version where I added some commands that hopefully resolve the permissions issues.
The problem is, that I can't reproduce it.
Are you rooting the Iconia the first time? or did you already have root before?
Regarding the progress bar. It only appears when writing the system.img.gz
I have Windows 7 64 bit, btw.
entonjackson said:
I uploaded a new version where I added some commands that hopefully resolve the permissions issues.
The problem is, that I can't reproduce it.
Are you rooting the Iconia the first time? or did you already have root before?
Regarding the progress bar. It only appears when writing the system.img.gz
I have Windows 7 64 bit, btw.
Click to expand...
Click to collapse
Dear Enton,
Yes this is the first time B1 will rooting,
I will try again, and report to you,
Regards
cakadut said:
Dear Enton,
Yes this is the first time B1 will rooting,
I will try again, and report to you,
Regards
Click to expand...
Click to collapse
Dear Enton,
The Messages still same, I Attached the Error Pic.
Note :
Iconia B1-A71
ROM 16 GB
RAM 512 MB
Android Version : 4.1.2
Kernel Version : 3.4.0
Image Version : Acer_AV051_B1-A71_RV05RC05_WW_GEN1
Build Number : Acer_AV051_B1-A71_1.258.00_WW_GEN1
Regards,
cakadut said:
Dear Enton,
The Messages still same, I Attached the Error Pic.
Note :
Iconia B1-A71
ROM 16 GB
RAM 512 MB
Android Version : 4.1.2
Kernel Version : 3.4.0
Image Version : Acer_AV051_B1-A71_RV05RC05_WW_GEN1
Build Number : Acer_AV051_B1-A71_1.258.00_WW_GEN1
Regards,
Click to expand...
Click to collapse
I will try to fix it asap. The problem is, that I cannot reproduce it.
I assume that the chmod 777 /cache command that I do, before the adb push command fails with "Operation not permitted."
But this I still don't know how to fix. If someone knows, tell me!
error in v.0.2.3
Dear entonjackson,
thanks for your work and for the time you spend on it.
Unfortunately, I too have problems with the tool for Windows since version 0.2.0 and also with the latest version (0.2.3).
The error messages that I receive are identical (with the same line numbers) to those receiving cakadut in his last post.
I am trying to root Iconia for the first time.
I tried with Windows 7-32bit and Windows 7 64-bit.
My configuration:
Iconia B1-A71 8GB ROM, 512Mb ram
Android 4.1.2
kernel 3.4.0
Image version: Acer_AV051_B1-A71_RV04RC04_WW_GEN1
Build Number: Acer_AV051_B1-A71_1.174.00_WW_GE
I hope you can find the solution.
Thank you for sharing your work with us.
Just uploaded a new version. Could you please try again?
It's hard to fix for me, because I don't have the problem, so all I can do is try. Thanks for the patience!
****, I think i found the bug. Don't try 0.2.4 it won't work also.
foxterrier said:
Dear entonjackson,
thanks for your work and for the time you spend on it.
Unfortunately, I too have problems with the tool for Windows since version 0.2.0 and also with the latest version (0.2.3).
The error messages that I receive are identical (with the same line numbers) to those receiving cakadut in his last post.
I am trying to root Iconia for the first time.
I tried with Windows 7-32bit and Windows 7 64-bit.
My configuration:
Iconia B1-A71 8GB ROM, 512Mb ram
Android 4.1.2
kernel 3.4.0
Image version: Acer_AV051_B1-A71_RV04RC04_WW_GEN1
Build Number: Acer_AV051_B1-A71_1.174.00_WW_GE
I hope you can find the solution.
Thank you for sharing your work with us.
Click to expand...
Click to collapse
Ok, people. With pawitp's help I hopefully fixed the permissions bug.
The problem was, that i was trying to chmod the /cache directory directly from adb shell, which isn't possible. I forgot, that this needs to be done from telnet. So in 0.2.6 I'm setting permission with telnet. This should fix it!
Please report!
Good luck :fingers-crossed:
Dear ethon
hi ethon can u do tutorial video cause i can't found the directory for the "step 6 : go to go to connectivity -> CDS Inforamtion ->Network Utility " and Thnk You :good:
diskenz said:
hi ethon can u do tutorial video cause i can't found the directory for the "step 6 : go to go to connectivity -> CDS Inforamtion ->Network Utility " and Thnk You :good:
Click to expand...
Click to collapse
I will try to do a video tutorial, but it's very easy to do.
Download and install Ex Dialer & Contacts.
Launch the app.
Dial *#*#ENGMODE#*#*.
Swipe from right to left (to Connectivity). Then choose CDS Information and Network Utility.
There you paste this command: /data/local/tmp/busybox telnetd -l /system/bin/sh -p 1234
stell no thing happen maybe i must upgrade to pro version ???
diskenz said:
stell no thing happen maybe i must upgrade to pro version ???
Click to expand...
Click to collapse
No.
Try to dial *#*#3646633#*#*
Else I don't know... this should work in any case...
entonjackson said:
Ok, people. With pawitp's help I hopefully fixed the permissions bug.
The problem was, that i was trying to chmod the /cache directory directly from adb shell, which isn't possible. I forgot, that this needs to be done from telnet. So in 0.2.6 I'm setting permission with telnet. This should fix it!
Please report!
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Thanks entonjackson,
unfortunately with version 0.2.6 I can not get the ADB connection with the tablet. The message it gives me is:
"Trying to Establish ADB Connection (If this hangs, ADB Connection failed. CMD Shell Close and open a new one) ..."
and remains so without making the connection.
If I run the command 'adb devices' in another command line session, the device is seen correctly (0123456789ABCDEF device),
but when I run the new version (0.2.6) of the tool, the message is what I wrote above.
Thank you for your patience.
Hello
i tried to install busy Box on My M8 Stock Rom with Busybox app at Google play Market. And every Time i Got Nothing after reboot
Now Don't Worry If You have The Same I Created This File And Works Great
1 - Go To Recovery
2 - Mount System
3 - Flash the Attached File
4 - Congratulations ?
I Hope You Like It
Download : https://mega.co.nz/#!AdsiiLhC!Ftsi1Tp0ltddgeWh1hIYjHZZrvUckAiLOgP3hVeXmZk
{
"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 ##
MultiROM is one-of-a-kind multi-boot mod for Nexus 6. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
Warning!:
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
## Installation ##
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2.Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 4 parts, but you really only need to install 3 parts:
MultiROM Installer:
TWRP Modified Recovery:
Patched Kernel: Primary roms Must have a Kexec Hardboot Patched Kernel
MultiRom UnInstaller:
Adding ROMs:
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 5.0 after first boot (with dalvik cache generated and connected to google account) takes about 1 GiB of space.
Using USB drive:
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs:
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Special Thanks to @Tasssadar..
XDA:DevDB Information
MultiRom V32 Resurrected (D850), ROM for the AT&T LG G3
Contributors
Eliminater74, thewalkingdude, Tasssadar
Source Code: https://github.com/Tasssadar/multirom
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 4.4.x
Version Information
Status: Beta
Created 2015-04-23
Last Updated 2015-07-12
- Download Section
MultiRom V32 Installer: multirom-20150712-v32-UNOFFICIAL-d850.zip
MultiRom Modified TWRP Recovery: TWRP_MultiRom_2.8.7.x_D850_20150712-signed.zip
MultiRom Kexec Hardboot Kernel By @777jon: AOSP-777-Kernel_d850-R10.zip
MultiRom Uninstaller: multirom_uninstaller.zip
Warning: Kernel is for LP 5.1 Only with 32gb variants at question. Sorry 16gigers, I havent done one for you yet.. but you can try this one.. It just may work.
Note: You can compile your own Kexec Hardboot Kernel as well. @fechanaitor and @777jon both have the Correct MultiRom patch that works with this version.
SideNote: Little UnKnownFact. This MultiRom is set up to allow installing Stock OEM roms as secondery as well..
And @777jon's 777Kernel does work on secondary as well with this version..
...
The first 18 lines on iomem
00000000-059fffff : System RAM
00008000-0114c58f : Kernel code
0130e000-016c22fb : Kernel data
0d700000-0f9fffff : System RAM
0ff00000-5fffffff : System RAM
80000000-dd9fffff : System RAM
f9017000-f9017fff : msm-watchdog
f920c100-f92fbfff : f9200000.dwc3
f9824900-f9824a9f : mmc0
f98a4900-f98a4a1b : mmc1
f991d000-f991dfff : msm_serial_hsl
f9923000-f9923fff : f9923000.i2c
f9924000-f9924fff : f9924000.i2c
f9962000-f99620ff : msm_serial_hsl
f9966000-f9966fff : spi_qsd
f9967000-f9967fff : f9967000.i2c
fb21b000-fb21dfff : pmu_base
fc380000-fc3e9fff : fc380000.msm-bimc
My device is a 3 gig on firmware D85020F. I have rooted and installed bumped twrp. Let me know if there's anything I missed. Thank you.
Sent from my LG-D850 using XDA Free mobile app
dginsd said:
The first 18 lines on iomem
00000000-059fffff : System RAM
00008000-0114c58f : Kernel code
0130e000-016c22fb : Kernel data
0d700000-0f9fffff : System RAM
0ff00000-5fffffff : System RAM
80000000-dd9fffff : System RAM
f9017000-f9017fff : msm-watchdog
f920c100-f92fbfff : f9200000.dwc3
f9824900-f9824a9f : mmc0
f98a4900-f98a4a1b : mmc1
f991d000-f991dfff : msm_serial_hsl
f9923000-f9923fff : f9923000.i2c
f9924000-f9924fff : f9924000.i2c
f9962000-f99620ff : msm_serial_hsl
f9966000-f9966fff : spi_qsd
f9967000-f9967fff : f9967000.i2c
fb21b000-fb21dfff : pmu_base
fc380000-fc3e9fff : fc380000.msm-bimc
My device is a 3 gig on firmware D85020F. I have rooted and installed bumped twrp. Let me know if there's anything I missed. Thank you.
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
By your iomem stats, I can already see that location 0x0ff00000 would prob. be the best for you..
I still need a few others to post to get more of an understanding where everyone is at. I dont wanna make 3 versions. I want only to make one version that works for everyone..
Thats why I need the iomem stats. It helps me determine where to put the kexec_mem_min location...
To explain, the kexec_mem_min is the location where kernel stores during a reboot its within the first 256 megs of ram. and the location you would use is
one of your system ram banks in an address that doesnt get written over during reboot.
Thats why this part is a must..
I'll try to help.
How do I grab that info. I'd be happy to help. Thanks for your help Sir!
mcwdude said:
How do I grab that info. I'd be happy to help. Thanks for your help Sir!
Click to expand...
Click to collapse
Use root explorer or similar kind of app and go to root and then to /proc and then there's a text file called iomem. Open in a text editor.
This is also from a D850 3gb on Cyanide
00000000-059fffff : System RAM
00008000-011be32f : Kernel code
01310000-0181c303 : Kernel data
0d700000-0f9fffff : System RAM
0ff00000-5fffffff : System RAM
80000000-dd7fffff : System RAM
dd900000-dd9fffff : System RAM
f920c100-f92fbfff : f9200000.dwc3
f9824900-f9824a9f : mmc0
f98a4900-f98a4a1b : mmc1
f991d000-f991dfff : msm_serial_hsl
f9923000-f9923fff : f9923000.i2c
f9924000-f9924fff : f9924000.i2c
f9962000-f99620ff : msm_serial_hsl
f9966000-f9966fff : spi_qsd
f9967000-f9967fff : f9967000.i2c
fb21b000-fb21dfff : pmu_base
fc380000-fc3e9fff : fc380000.msm-bimc
fc401680-fc401683 : restart_reg
fc4016c0-fc4016c3 : restart_reg
fc401700-fc401703 : clk_base
fc4281d0-fc4291cf : vmpm
00000000-059fffff : System RAM
00008000-0114c58f : Kernel code
0130e000-016c22fb : Kernel data
0d700000-0f9fffff : System RAM
0ff00000-5fffffff : System RAM
80000000-dd9fffff : System RAM
f9017000-f9017fff : msm-watchdog
f920c100-f92fbfff : f9200000.dwc3
f9824900-f9824a9f : mmc0
f98a4900-f98a4a1b : mmc1
D850 on Rooted Lollipop Stock
D85020f
d850 running cyanide 3GB
00000000-059fffff : System RAM
00008000-010a2e27 : Kernel code
0120e000-01710f3b : Kernel data
0d700000-0f9fffff : System RAM
0ff00000-5fffffff : System RAM
80000000-dd9fffff : System RAM
f920c100-f92fbfff : f9200000.dwc3
f9824900-f9824a9f : mmc0
f98a4900-f98a4a1b : mmc1
f991d000-f991dfff : msm_serial_hsl
f9923000-f9923fff : f9923000.i2c
f9924000-f9924fff : f9924000.i2c
f9962000-f99620ff : msm_serial_hsl
f9966000-f9966fff : spi_qsd
f9967000-f9967fff : f9967000.i2c
fb21b000-fb21dfff : pmu_base
fc380000-fc3e9fff : fc380000.msm-bimc
fc401680-fc401683 : restart_reg
fc4016c0-fc4016c3 : restart_reg
fc401700-fc401703 : clk_base
fc4281d0-fc4291cf : vmpm
fc460000-fc463fff : fc460000.msm-sys-noc
fc468000-fc46bfff : fc468000.msm-periph-noc
fc470000-fc473fff : fc470000.msm-ocmem-noc
fc478000-fc47bfff : fc478000.msm-mmss-noc
fc480000-fc483fff : fc480000.msm-config-noc
fc4a8000-fc4a9fff : tsens_physical
fc4bc000-fc4bcfff : tsens_eeprom_physical
fc820000-fc82001f : rmb_base
fc880000-fc8800ff : qdsp6_base
fd485300-fd48530b : halt_base
fda00020-fda0002f : csi_clk_mux
fda00030-fda00033 : csiphy_clk_mux
fda00038-fda0003b : csiphy_clk_mux
fda00040-fda00043 : csiphy_clk_mux
fda04000-fda040ff : fda04000.qcom,cpp
fda08000-fda080ff : fda08000.qcom,csid
fda08400-fda084ff : fda08400.qcom,csid
fda08800-fda088ff : fda08800.qcom,csid
fda08c00-fda08cff : fda08c00.qcom,csid
fda0a000-fda0a4ff : fda0a000.qcom,ispif
fda0ac00-fda0adff : fda0ac00.qcom,csiphy
fda0b000-fda0b1ff : fda0b000.qcom,csiphy
fda0b400-fda0b5ff : fda0b400.qcom,csiphy
fda0c000-fda0cfff : fda0c000.qcom,cci
fdb00000-fdb0ffff : kgsl-3d0
fdb20000-fdb2ffff : kgsl-3d0
fdc80000-fdc803ff : vbif_base
fdce0000-fdce3fff : wrapper_base
fe200000-fe2000ff : qdsp6_base
fec00000-fed7ffff : fdd00000.qcom,ocmem
Wow, ok I guess you are interested..
Be aware:, That CM based LP 5.1's are not working correctly as secondary roms. I am working with @Tasssadar on fixing this problem. But Logs are the main thing needed which its hard to show a log
when it wont write to the last_kmsg file. But this problem is present for the time being.
And once I have this Compiled and good to go, I will need testers, as I dont own a D850.
One more thing, you will have to use the current kexec hardboot patch kernels till I set up one of my roms to build you one with my patch.
I never planed on porting anything to your device, so I dont have a local_manifest setup with your device for building roms/kernels.
That would break my #1 rule. Which I knew would happen sooner or later..
I am no pro Dev, im just a person that learns quick and picks up alot of by trials and errors, I have done 90% of all the hard leg work to get this MultiRom to work very good as it was intended to work on
our devices. all patches was received by Mr @Tasssadar him self.
I am also talking to @Tasssadar about getting our Devices compatible on his MultiROMmgr app thats on Google PlayStore. Which would allow you to boot any rom straight from the app as well as install.
and a few other options.
I cant promise that the first few builds will work good, As I dont have the D850 to test it. But as we go along and tweak it, we can get it working.
Code:
00000000-059fffff : System RAM
00008000-011be32f : Kernel code
01310000-0181c303 : Kernel data
0d700000-0f9fffff : System RAM
0ff00000-5fffffff : System RAM
80000000-dd7fffff : System RAM
dd900000-dd9fffff : System RAM
f920c100-f92fbfff : f9200000.dwc3
f9824900-f9824a9f : mmc0
f98a4900-f98a4a1b : mmc1
It's a 3gig, I think all D850s are 3gig, no?
I'm patiently waiting for an updated multirom-enabled twrp. For what it's worth, I seem to be the only one for whom skin1980's release actually worked as advertised, using CM11 as my primary too! There are however certain roms that fail to boot as secondary.
shimbob said:
Code:
00000000-059fffff : System RAM
00008000-011be32f : Kernel code
01310000-0181c303 : Kernel data
0d700000-0f9fffff : System RAM
0ff00000-5fffffff : System RAM
80000000-dd7fffff : System RAM
dd900000-dd9fffff : System RAM
f920c100-f92fbfff : f9200000.dwc3
f9824900-f9824a9f : mmc0
f98a4900-f98a4a1b : mmc1
It's a 3gig, I think all D850s are 3gig, no?
I'm patiently waiting for an updated multirom-enabled twrp. For what it's worth, I seem to be the only one for whom skin1980's release actually worked as advertised, using CM11 as my primary too! There are however certain roms that fail to boot as secondary.
Click to expand...
Click to collapse
I just spent the last 20 mins reading up on this bump stuff, Since T-Mobiles come unlocked, I never had to worry about bump. But I have the script.
When I release the Modified TWRP Multirom recovery, I will release it in 2 ways,
#1: run this Bump scrip on the img and then package it.
#2: Just releae the recovery.img and let you all run the script to bump it. ( Just in case I mess things up )
Just till I know that I am doing it right, after thats been validated I will just release the package already bumped and good to go.
I wish LG would just unlock all thier phones. Good thing T-Mobile Forced them too.
I didnt forget about anyone here, I will take me a few days, I have alot going on at the moment.
I am still trying to fix the 5.1 bug. So I can boot 5.1 from secondary. At the same time
im trying to move my build environment to Omnirom LP.. Which took changing the BoardConfig.mk and BoardConfigCommon.mk.
Which will also let me compile on CM sources as well. with a sepolicey change for recovery..
With all that said, Just give me a few days.. I know you would hate to hear this, but I put my device first.. Whats the point in porting a not working version.
Eliminater74 said:
I didnt forget about anyone here, I will take me a few days, I have alot going on at the moment.
I am still trying to fix the 5.1 bug. So I can boot 5.1 from secondary. At the same time
im trying to move my build environment to Omnirom LP.. Which took changing the BoardConfig.mk and BoardConfigCommon.mk.
Which will also let me compile on CM sources as well. with a sepolicey change for recovery..
With all that said, Just give me a few days.. I know you would hate to hear this, but I put my device first.. Whats the point in porting a not working version.
Click to expand...
Click to collapse
No problem man we're not in a rush we're just interested in the project.
MultiRom Resurrected (D850) Posted:
MultiRom Resurrected V32 (D850)
Update: Use a pre-kexec Hardboot patched Kernel for now. Might not work well.. but for now its good enough. Till I make you a beter one.
Also, I cant remember what kexec_mem_min location I used, I think its 0x0ff00000 But not sure.. if it works let me know. if it doesnt. Still let me know with logs please.
and Im not sure about the bump thing. I used the bump.py that Cyanogenmod uses. Anyhow, I only bumped the recovery.. I dont think the multirom needs bumping since its only a bunch of scripts..
I posted 3 recovery uploads for a reason, one is the flashable and the other is a bumped image and the last is just a recovery.img not bumped.
Pick your own poison.....................
I need logs if your going to complain about this. Really I only did this as a request from someone..
Dont forget this is still in testing stages, Till I get a feel as to how this works with your device.. Not sure if I got the location correct. but try it and let me know.
Eliminater74 said:
MultiRom Resurrected V32 (D850)
Update: Use a pre-kexec Hardboot patched Kernel for now. Might not work well.. but for now its good enough. Till I make you a beter one.
Also, I cant remember what kexec_mem_min location I used, I think its 0x0ff00000 But not sure.. if it works let me know. if it doesnt. Still let me know with logs please.
and Im not sure about the bump thing. I used the bump.py that Cyanogenmod uses. Anyhow, I only bumped the recovery.. I dont think the multirom needs bumping since its only a bunch of scripts..
I posted 3 recovery uploads for a reason, one is the flashable and the other is a bumped image and the last is just a recovery.img not bumped.
Pick your own poison.....................
I need logs if your going to complain about this. Really I only did this as a request from someone..
Dont forget this is still in testing stages, Till I get a feel as to how this works with your device.. Not sure if I got the location correct. but try it and let me know.
Click to expand...
Click to collapse
Hey thanks for posting so fast. Was able to successfully flash the MultiROM'd TWRP however 2 things:
1. It boots really really slowly. Was wondering if it actually worked or not for the longest until TWRP finally loaded up.
2. I then flashed the multirom zip and then the 777 kernel zip and added Resurrection Remix and MultiRom properly recognized it.
3. However when I tried to run RR it returned an error and a log was created. Sending that log to you via pm now.
arjuna_ said:
Hey thanks for posting so fast. Was able to successfully flash the MultiROM'd TWRP however 2 things:
1. It boots really really slowly. Was wondering if it actually worked or not for the longest until TWRP finally loaded up.
2. I then flashed the multirom zip and then the 777 kernel zip and added Resurrection Remix and MultiRom properly recognized it.
3. However when I tried to run RR it returned an error and a log was created. Sending that log to you via pm now.
Click to expand...
Click to collapse
TWRP takes a bit it seems, you gota understand that I turned off the screen while it boots. Thats how I set it in the BoardConfig.mk because the menu wasnt working the other way around.
and the 777 kernel patch isnt my patch, I said you would have to wait for me to do the correct patch. some roms wont work that great with the old patch.. it uses different memory locations
and set different. My patch was direct from @Tasssadar.. He told me what I needed to change to get it working with our devices. same with the hooks file...
Also, RR 5.1 might have problems......... anything related to 5.1 after the 17th is related to CM issues thats being worked on ( This is only as Secondary rom only) Should work as primary..
Kernel panics, are caused of out of boounds memory location.. thats the reason I needed everyones iomem..
But I think I used the 0x0ff00000 but really cant remember. Alot going on.........
As I said in prev. post. I dont own this device other then the fact I have a G3.. and it will take a lot of testing and a few tweaks to get this to work correctly.
I dont expect the first few to work. As long as the Recovery booted, Then I know I did something right. I was worried about the bump thing..
I didnt want to brick anyones phone. So that worried me.. But since it worked. I know I am doing it right.
I did start creating MultiRom on LP 5.0.2 build. and All the problems that used to be on the 4.4.4 build kinda fixed it self.. Vibration and everything seem to work correctly with the LP builds.
so when we tweak this right. I will convert the D850 BoardConf file over to the cm 12.0+ section as I already have for the D851.. Shouldnt be to hard since I already know what I need to change..
First time took a while. I had to find all the correct files to change for the port over ...........
I just upgraded my windows 10 to build 10061 (Yes im a tester for Microsoft) Been one since 1998.... So I was offline for a bit while the update happened..
But my other system was up and running.. But I was also in the middle of a few updated on my linux system as well.
Anyhow, we will get this working correctly for you.. Just give me time.
Update: I made a little error when I compiled the first MultiRom..
I forgot to change the dir structure from D851 to D850.. So thats why it didnt work.
TWRP should be working.. That has nothing to do with what I forgot to do............
I am compiling a new update. Will post it as soon as its done.................
--=[ Multirom V32 Fixed and RePosted ]=--
Update: I Re-Posted Multirom V32.. Sorry last one has a simple mistake.. This one should work for 90% of you.
kexec_mem_min location I used is: 0x0ff00000 Which by all rights, should work for all. I cant stay that 5.1 roms will work..
Automated GApps and MoreLocale2 Installer + Debloater
for Le Pro 3 AI x7 (codename x650 / x651) without ROOT
...but it is suitable for any ARM64 Android 6+ device without ROOT
to run ONLY under Linux OS x64
Updated post! All further improvements and corrections will be published here.
Linux Script Version 0.1.8 | Developed by: @dilnix in assistance of @master_lie
The Google Apps version of 06/15/2018
Linux dependencies: android-tools
Windows version you can find on 4pda or in the following post of this thread<-- WINDOWS VERSION
Temporary the Windows version placed HERE
Installs and removes a sample Google Apps package, as well as MoreLocale2, with all necessary permissions to these applications.
And also, it allows to partially remove and freeze most unnecessary Chinese programs.
Remember, it will not return your already uninstalled apps!
DOWNLOAD: FEX || MEGA
For start:
0) Have a USB-connected smartphone, with an already-enabled and authorized USB debug running on the stock EUI without installed GApps and MoreLocale2.
1) Unpack the archive anywhere and go to the appeared folder "ML2-GApps-Debloat".
2a) Open the terminal (console) from this folder and run the script file:
Code:
./ML2-GApps-Debloat-Linux.sh
OR...
2b) Simply "Run the file in the terminal window (console)" from the context menu of the file manager by right clicking on the mentioned file.
After the launch, you will get into a simple text menu with a choice of further installation steps.
After installing any of the Google Apps options your smartphone will be rebooted!
All applications are installed by the script in the User Space, and they are not afraid of a typical system update.
Menu options:
1) Check_ADB
2) Install_only_ML2 (Install only MoreLocale2)
3) Install_ML2+CoreGApps (Install MoreLocale2 and Core Google Apps)
4) Install_ML2+CoreGApps+ExtraGApps (Install MoreLocale2 and Basic Google Apps and Additional Google Apps)
5) Install_only_CoreGApps (Install only Basic Google Apps)
6) Install_only_ExtraGApps (Install only Additional Google Apps)
7) Install_CoreGApps+ExtraGApps (Install only Basic Google Apps and Additional Google Apps)
8) Remove_ML2 (Remove only MoreLocale2 without reboot)
9) Remove_GApps (Remove Core and/or Additional Google Apps with reboot)
10) Remove_ALL (Remove All Google Apps and MoreLocale2 without questions but with reboot)
11) Debloat_Menu -------
..............................................................|
..............................................................| This submenu contains options:
..............................................................|
..............................................................1) Uninstall_Chinese (just few boring apps without reboot)
..............................................................2) Hide_Minimal_LeEco (part of LeEco apps that is most useless without reboot)
..............................................................3) Hide_All_LeEco+MTK_Services (All of LeEco & MTK apps and services without reboot)
..............................................................4) Hide_LeEco_Browser (without reboot)
..............................................................5) Hide_LeEco_Launcher (without reboot)
..............................................................6) Hide_LeEco_Music (without reboot)
..............................................................7) Hide_LeEco_SuperManager (without reboot)
..............................................................8) Hide_LeEco_Calendar (without reboot)
..............................................................9) Hide_LeEco_Email (without reboot)
..............................................................10) Hide_LeEco_VideoPlayer (without reboot)
..............................................................11) Return_to_Main_Menu
12) UnHide_Menu -------
..............................................................|
..............................................................| This submenu contains options:
..............................................................|
..............................................................1) UnHide_Minimal_LeEco (part of LeEco apps that is most useless without reboot)
..............................................................2) UnHide_All_LeEco+MTK_Services (All of LeEco & MTK apps and services without reboot)
..............................................................3) UnHide_LeEco_Browser (without reboot)
..............................................................4) UnHide_LeEco_Launcher (without reboot)
..............................................................5) UnHide_LeEco_Music (without reboot)
..............................................................6) UnHide_LeEco_SuperManager (without reboot)
..............................................................7) UnHide_LeEco_Calendar (without reboot)
..............................................................8) UnHide_LeEco_Email (without reboot)
..............................................................9) UnHide_LeEco_VideoPlayer (without reboot)
..............................................................10) Return_to_Main_Menu
Google Apps Packages:
Core Google Apps: GoogleBackupTransport.apk, GoogleContactsSyncAdapter.apk, GoogleLoginService.apk, GoogleServicesFramework.apk, Phonesky.apk, PrebuiltGmsCore.apk
Additional Google Apps: CalendarGooglePrebuilt.apk, GoogleCalendarSyncAdapter.apk, LatinImeGoogle.apk
All questions and support: in this thread of the forum, as well as in the Telegram group "dilnix_LiteMod_EUI" (answering not fast).
Language of informing by script: English.
Inspired by: 4pda community
It is possible to update the script in the future for EUI with Root system access, and to add more functionality.
With today update of v0.1.6 we did:
- options to remove GApps and MoreLocale2 options
- all code optimized and re-visioned
Please enjoy!
With today update of v0.1.7 we added:
- option to remove few Chinese bloatware applications
- options to hide most of LeEco apllications and services
Please enjoy!
Also I prepared a Video manual of:
- installing EUI 5.9.025S via Fastboot
- updating to EUI 5.9.028S via OTA
- removing and hiding most of useless applications with using a tool of topic
- installing GApps with using a tool of topic
Hope you will like it.
*
We say thank you for the much work what you put into it !! :jó:
I'm glad to see it helps you =)
Developing Linux and Windows versions of tool will be separated soon at 4pda. But I hope we'll keep publishing it together here after adding more features.
Kind dilnix, thank you it till now work with what you helped a lot. We would be glad if you would publish your work here in the additional ones because the 4pda-ra to register and to enter rather difficult if somebody does not can in Russian and he does not have a Russian keyboard. Excuse me for the bad English text. With thanks and gratitude!! :good:
msaca said:
Kind dilnix, thank you it till now work with what you helped a lot. We would be glad if you would publish your work here in the additional ones because the 4pda-ra to register and to enter rather difficult if somebody does not can in Russian and he does not have a Russian keyboard. Excuse me for the bad English text. With thanks and gratitude!! :good:
Click to expand...
Click to collapse
Don't be afraid. All my results with x7 device will be published on XDA too.
Nice to see that tool is good for you =)
Thanks Dilnix. Following your thread man. I'll rate this
pls help
i cant run "ML2-GApps-Debloat-Windows.exe". it keeps on closing up..please help
Mysiopao said:
i cant run "ML2-GApps-Debloat-Windows.exe". it keeps on closing up..please help
Click to expand...
Click to collapse
It could be your PC. try to re-download or use a different PC if you have it available man.
Mysiopao said:
i cant run "ML2-GApps-Debloat-Windows.exe". it keeps on closing up..please help
Click to expand...
Click to collapse
please tell me more details,
what is OS version?
did you enabled some options in the file properties, for example, about compatibility?
this is fantastic!
bro you save my life and other user
that number 18 disabled the launcher making it blank on startup funny. i thought i got boot loop im surprised someone call me and noticed that the launcher is missing need to figure how to reformat the phone pressing power button and up go to recovery delete user. try again to install. from option 2 ML2+coreapps then do the debloat use the 15 16 and 17 only. im scared to tried that one again number 18 option
kudos to you:good:
cant install OTA nor install 5.9.25s using PC
i want to install the latest rom for my lex653 4 32GB with new EUI 5.9.28s. I have downloaded the zip file and copy it to my phone, then change the name into update.zip. I wipe out all my data and then update. But it failed when i try to install and then nothing change with my EUI. Then, i found this thread. Then i try to install EUI 5.9.25s with PC. But it always failed because the fastboot and the device didnt match. Please help to solve the problem please!!!:crying::crying::crying:
Hi!
I'm having a problem with executing of gapps file. It keeps on closing.
It says that
C:\users\user\Destop\New' is not recognized as internal or external command
operable program or batch file.
please help me
I hide some more apps and no error encounter:
com.android.calculator2 --> i don't like this calculator
com.android.email --> I use gmail
com.android.gallery3d --> I don't use this gallery
com.letv.android.filemanager --> I use mixplorer
com.letv.android.personalized --> I don't know, i can still open in settings
com.letv.android.themestore --> same as before
com.letv.android.videoplayer --> I use vlc
com.letv.domain --> I don't know
com.letv.leui.sdk.data --> I don't know
Hello dilnix, I am sorry to bother you, but since I can not register in 4pda I ask you around here.
It is true that leeco has sent the source code of the x650 to a 4pda developer?.
A greeting.
kaku1237 said:
bro you save my life and other user
that number 18 disabled the launcher making it blank on startup funny. i thought i got boot loop im surprised someone call me and noticed that the launcher is missing need to figure how to reformat the phone pressing power button and up go to recovery delete user. try again to install. from option 2 ML2+coreapps then do the debloat use the 15 16 and 17 only. im scared to tried that one again number 18 option
kudos to you:good:
Click to expand...
Click to collapse
I do the same this on linux version with 11 > 6, so reformat the cellphone and before de bloat install the Now Launcher bay play store and set as default. then hide Le Eco Launcher.
Then i try to install EUI 5.9.25s with PC. But it always failed because the fastboot and the device didnt match. Please help to solve the problem please!!!
Click to expand...
Click to collapse
When you in Fastboot mode, what is output of following command?
fastboot oem device-info
I'm having a problem with executing of gapps file. It keeps on closing.
It says that
Click to expand...
Click to collapse
You just need to run it from path that excludes any special symbols and spaces.
It is true that leeco has sent the source code of the x650 to a 4pda developer?
Click to expand...
Click to collapse
No, it's not true. Nobody from 4PDA mentioned about that. If somebody got source code and keeping silent it's not good and shame on them but it's all I know.
I have success to install 5.9.025s china roms then use ML2 debloat apps. It works well and i have hide the launcher just like the tutorial. And then, when im playing games. I realize that the super manager (phone manager) has gone. Could you put back the phone manager please or dont include it in the option. Because with phone manager, the phone can enter the high performance mode so the game will not laggy. Im really disappointed because the super manager has gone. Please help.