Follow anything in this guide at your own risk. I will not accept any responsibility if you are left with a bricked device, and/or a device that is damaged or impaired in some way. These steps are a reconstruction of what I was doing - I haven't actually tested the exact files attached, which should be more cleaner than the ones I was working with.
The inkPalm 5 is a 5.2" eReader with an Allwinner 32-bit ARM B300 CPU and 1GB RAM running Android 8.1 sold in China under Xiaomi's Moaan brand.
This involves writing a file to /system, which may prevent you from installing future OTAs. Be warned that the firmware for this device cannot be downloaded, so you could end up with an unrepairable brick!
Make sure ADB is setup first.
Download dump_kernel_to_system_signed.zip
Reboot the inkPalm into recovery mode :
Code:
reboot recovery
Use the touch screen and/or volume + power buttons to choose the "Apply update from ADB" option
On the computer, run
Code:
adb sideload path\to\dump_kernel_to_system_signed.zip
(making the obvious substitution)
When it's done, choose the first option in the recovery (reboot system now) to boot back into Android
Back in an adb shell, run
Code:
cp /system/bimg.img /sdcard/
Install the Magisk APK
Open Magisk, tap install
I don't think the AVB/dm-verity option needs to be checked, so I left it unchecked. YMMV. The inkPalm doesn't encrypt itself even if you enable a PIN.
Choose bimg.img from your storage and let Magisk do its thing
Transfer the magisk_patched*.img file in your Downloads folder onto the PC
Flashing the patched kernel image with recovery
Rename your magisk_patched.img file to boot.img
Using your favourite archive manager, add your boot.img to the root folder of kernel_flashing_template.zip
In a command prompt, run
Code:
java -jar signapk-1.0.jar -w testkey.x509.pem testkey.pk8 kernel_flashing_template.zip kernel_flashing_template_signed.zip
(If you run into problems, make sure you have JRE 8 installed.)
Reboot back into recovery and
Code:
adb sideload
kernel_flashing_template_signed.zip
Reboot back into Android and hopefully you should have a rooted inkPalm with Magisk
(Flashing with fastboot should work, but I've not tested that.)
EDIT: You can find an extended guide at https://github.com/qwerty12/inkPalm-5-EPD105-root with steps for installing microG.
qwerty12 said:
Follow anything in this guide at your own risk. I will not accept any responsibility if you are left with a bricked device, and/or a device that is damaged or impaired in some way. These steps are a reconstruction of what I was doing - I haven't actually tested the exact files attached, which should be more cleaner than the ones I was working with.
The inkPalm 5 is a 5.2" eReader with an Allwinner 32-bit ARM B300 CPU and 1GB RAM running Android 8.1 sold in China under Xiaomi's Moaan brand.
This involves writing a file to /system, which may prevent you from installing future OTAs. Be warned that the firmware for this device cannot be downloaded, so you could end up with an unrepairable brick!
Make sure ADB is setup first.
Download dump_kernel_to_system_signed.zip
Reboot the inkPalm into recovery mode :
Code:
reboot recovery
Use the touch screen and/or volume + power buttons to choose the "Apply update from ADB" option
On the computer, run
Code:
adb sideload path\to\dump_kernel_to_system_signed.zip
(making the obvious substitution)
When it's done, choose the first option in the recovery (reboot system now) to boot back into Android
Back in an adb shell, run
Code:
cp /system/bimg.img /sdcard/
Install the Magisk APK
Open Magisk, tap install
I don't think the AVB/dm-verity option needs to be checked, so I left it unchecked. YMMV. The inkPalm doesn't encrypt itself even if you enable a PIN.
Choose bimg.img from your storage and let Magisk do its thing
Transfer the magisk_patched*.img file in your Downloads folder onto the PC
Flashing the patched kernel image with recovery
Rename your magisk_patched.img file to boot.img
Using your favourite archive manager, add your boot.img to the root folder of kernel_flashing_template.zip
In a command prompt, run
Code:
java -jar signapk-1.0.jar -w testkey.x509.pem testkey.pk8 kernel_flashing_template.zip kernel_flashing_template_signed.zip
(If you run into problems, make sure you have JRE 8 installed.)
Reboot back into recovery and
Code:
adb sideload
kernel_flashing_template_signed.zip
Reboot back into Android and hopefully you should have a rooted inkPalm with Magisk
(Flashing with fastboot should work, but I've not tested that.)
Click to expand...
Click to collapse
As far as I could gather, with both USB connection and developper mode on, ADB conncection is explicitely rejected. Besides, there is, on InkPalm, below the usuals USB checks, one that reads "...ADB/ADT..." which cannot be checked. The connetion request by wireless ADB, supplying the correct address, is also rejected.... As though the device needed be rooted first !
I haven't tested using ADB over Wi-Fi, but I can honestly say I have had no issues using ADB over USB on the inkPalm. ADB was enabled by default on mine, and not to mention the security of it has been weakened - you don't even need to approve ADB connections for the first time...
So, since mine seems to reject ADB on both USB and WI-FI, what would you suggest to try as next --and desperate ? I cannot find any reference to the manufacturer that would eventually grant me permissions-- step ?
So long,
Sixto Quesada
Bis -- I forget to mention that my primary goal is merely to be able to change the language to English, as I think that there are already many possibilities in-built as to the configuration, including the shell !
squsqu6 said:
So, since mine seems to reject ADB on both USB and WI-FI, what would you suggest to try as next --and desperate ?
Click to expand...
Click to collapse
Is debugging mode actually on? Open the settings, go to the highlighted page and
{
"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"
}
turn the highlighted setting on (make sure the setting above it is on too - it will let you install external APKs)
You can follow these steps to show the Developer Settings, that's up to you: https://github.com/epodegrid/epd106-ADB#step-1-install-adb
squsqu6 said:
Bis -- I forget to mention that my primary goal is merely to be able to change the language to English
Click to expand...
Click to collapse
If you really can't get ADB to work, then there might be another way. Install the APK of my launcher fork (how you do that is up to you - you can try using the built-in browser or transferring the APK over MTP and using the file manager [which I've never opened] to install it).
In the new launcher, tap-and-hold the Settings icon (the one with a dark background),
choose Additional Settings and tap Locale. Then follow the instructions here: https://github.com/philips/inkpalm-5-adb-english#change-the-language
ADB is definit[iv]ely unavailable. But your launcher fork --that I already had, but did not know what to do with-- works, I now have most of the menu in English.
Thank you so much.
This worked great for me thanks a lot. I have a quick question if you know it. Is there anyway to get the old style android soft nav bar on the bottom (home, back, open apps)? The stuff you can do with the home button/logo button in settings is pretty limited.
Thanks.
reaverclan said:
Is there anyway to get the old style android soft nav bar on the bottom (home, back, open apps)?
Click to expand...
Click to collapse
I think it may have removed entirely to save space. That's just a guess though. I tried two Magisk modules to enable it - one sets that qemu property and the other uses an Android resource overlay - and both didn't work. The only workaround I can suggest, untested, would be this: https://github.com/epodegrid/epd106-ADB#step-4-naviation-button
qwerty12 said:
Thanks.
I think it may have removed entirely to save space. That's just a guess though. I tried two Magisk modules to enable it - one sets that qemu property and the other uses an Android resource overlay - and both didn't work. The only workaround I can suggest, untested, would be this: https://github.com/epodegrid/epd106-ADB#step-4-naviation-button
Click to expand...
Click to collapse
Yeah I tried step 4 and adb said the file was to old so rejected it and I tired it in the file manager anyways to see what would happen and it says it's not a working package or not compatible. So I guess it's for another xiaomi device or base android version. I also noticed only the stock file manager can actually invoke the package installer, root explorer gets the prompt to install but never then sends it to the Manger to load it and give the option for an install.
reaverclan said:
Yeah I tried step 4 and adb said the file was to old so rejected it and I tired it in the file manager anyways to see what would happen and it says it's not a working package or not compatible.
Click to expand...
Click to collapse
It's actually because the modified launcher mentioned in this thread uses the package name com.moan.moanwm (credits to whoever found that out; doing that allows the original Settings to be launched), which actually belongs to those navball buttons... I was originally going to suggest to just get rid of the launcher, so you can install the navball buttons, but they're really crashy and useless anyway. Sorry, I don't know what else to suggest - given other "QOL" changes by Moann (see below), I strongly suspect the navigation button code was ripped out entirely to save RAM.
I also noticed only the stock file manager can actually invoke the package installer, root explorer gets the prompt to install but never then sends it to the Manger to load it and give the option for an install.
Click to expand...
Click to collapse
Give Total Commander a try.
Moann really did a number on this device's Android build and messed it up, presumably in the name of "security". Only certain programs can show the original Settings, which messes up other applications' ability to show the app info of programs; the only thing that can force stop programs is Settings (which messes up Titanium Backup) and Root Explorer probably tries to invoke the Android installer directly (if that's a thing).
qwerty12 said:
It's actually because the modified launcher mentioned in this thread uses the package name com.moan.moanwm (credits to whoever found that out; doing that allows the original Settings to be launched), which actually belongs to those navball buttons... I was originally going to suggest to just get rid of the launcher, so you can install the navball buttons, but they're really crashy and useless anyway. Sorry, I don't know what else to suggest - given other "QOL" changes by Moann (see below), I strongly suspect the navigation button code was ripped out entirely to save RAM.
Give Total Commander a try.
Moann really did a number on this device's Android build and messed it up, presumably in the name of "security". Only certain programs can show the original Settings, which messes up other applications' ability to show the app info of programs; the only thing that can force stop programs is Settings (which messes up Titanium Backup) and Root Explorer probably tries to invoke the Android installer directly (if that's a thing).
Click to expand...
Click to collapse
Ah I see that's clever. It's not the end of the world and yeah I think it's cause root explorer does what you said about invoking the thing directly. I just use the stock app to only install and that's it. My journey so far is shown here and regardless of the jank it has been a great device. https://www.mobileread.com/forums/showpost.php?p=4140508&postcount=155
Thanks again for the time to make it even greater. Only thing that sucks is no stock img to un brick if something goes to far. Hopefully someone leaks that at some point. This device seems pretty new to the market still.
squsqu6 said:
ADB is definit[iv]ely unavailable. But your launcher fork --that I already had, but did not know what to do with-- works, I now have most of the menu in English.
Thank you so much.
Click to expand...
Click to collapse
I now have a new, but old !, trouble : battery life. I have enforced all saving possibilities available --from standard menu, from E-Ink Launcher, and, from RomToolBox, processors speed slowing--, and, yet, after 8 hours of use, InkPalm battery is totally empty, even though being totally user-idle --not a single user application being active according to linux 'top' request. Conversely, Kobo reader battery lasts for days in reading mode.
My question : would it be thinkable any possible trick of triggering the sleeping function without pushing the red button, so as to keep the screen as it is --allowing the reading of actual page until next (not a book, a musical partion, which takes longer !)--. Bypassing by script the red button action, or other ? --Note : the screensaver option allows for user-image, like a screenshot, but it requires to move it to the proper place and to renew it at every page...
Sorry for being so long, I am far from being familiar wich Linux (Android).
Greetings,
S. Quesada
Related
[TOOLKIT] UNIFIED ANDROID TOOLKIT - SAMSUNG GALAXY NOTE 2 - Drivers, Root, Recovery + MORE
GSM (GT-N7100) and LTE (GT-N7105) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1923956
AUSTRALIAN GSM (GT-N7100T) and LTE (GT-N7105T) SUPPORTED. USE GSM THREAD
SPRINT (SPH-L900) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1957155
TMOBILE (SGH-T889) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1957720
MOBILICITY, VIDEOTRON, WIND [SGH-T889V] SUPPORTED. NO THREAD YET. USE TMOBILE THREAD
AT&T (SGH-L317) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=2052779
BELL, ROGERS, SASKTEL, TELUS [SGH-I317M] SUPPORTED. NO THREAD YET. USE AT&T THREAD
VERIZON ([SCH-I605]) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=2052788
US CELLULAR (SCH-R950) SUPPORTED. NO THREAD YET. USE ANY
KOREAN SK TELECOM [SHV-E250S] SUPPORTED. NO THREAD YET. USE ANY
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit/Windows 10
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk’s to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
{
"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"
}
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: ChainsDD for Superuser, Chainfire for SuperSU and kernel patches, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
**FAQ**
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF (e.g removing system apps).
From Google:
Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components:
A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.
----------------------------------------------------------------------------
Q. I flashed CWM but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on Android that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from the Market). Delete the file recovery-from-boot.p from /system. Now when you flash CWM Recovery it will NOT be overwritten after a reboot. You can also use the Toolkit to rename the files if you wish.
----------------------------------------------------------------------------
Q. What is the difference between Nandroid and Titanium backup?
A NANDROID will backup the whole system including boot, system, data and recovery partitions so you can restore a complete rom and all data and settings.
Essentially Titanium Backup is used to backup apps and associated user data. These could be restored AFTER a full wipe and a new Rom had been flashed on your phone.
The other option now which google added into the new adb command list is the adb backup which is in the ToolKit and can do the same job as Titanium Backup but will store the data on your PC rather than on the phone (where it takes up space and could be deleted).
----------------------------------------------------------------------------
Q. When would i perform a nandroid vs a titanium backup?
You would perform a nandroid backup to back up your entire system including boot image and data and system partitions so you can restore your entire system back to that particular point in the future.
You would use Titanium Backup mainly to back up your installed apps and settings so they could be reinstalled easily and quickly on any future roms. You can also choose individual apps to backup or restore on Titanium Backup whereas if you restore your boot partition via CWM Recovery you are stuck with the whole lot.
----------------------------------------------------------------------------
Q. When I try to open the ToolKit I get a box pop up for a split second and then it goes away. My AntiVirus program says the file may be harmful.
The exe files I compiled are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) will pick it up as potentially harmful when it is not. They pick up ANY file that doesnt contain a purchased Microsoft certificate in the same way. Restore the deleted file and exclude it from further scans and it will be fine.
----------------------------------------------------------------------------
Q. I donated but where do I get my activation code from?
Donation Codes are sent out manually to your PayPal email address [unless otherwise stated] after a confirmation email from PayPal has been receive. The Code can then be entered in the ToolKit Settings, Activate Donators Features Screen. This will enable The Auto Updates, Quick Picks and Extras Features in the ToolKit. Please be patient when waiting for the Code to be sent as it depends very much on what I am doing and whether I am at my PC when the donation is made. Please do not post in the ToolKit's thread or pm me asking for the activation code as it clogs up the thread and my messages. If you haven't received your code after 24 hours then feel free to email me via the skipsoft.net contact page.
Don't worry that you have been forgotten about, I check all emails personally and will deal with it as soon as I can.
----------------------------------------------------------------------------
Q. I have Windows 8 and cannot install the drivers
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
When your computer restarts, select ‘Disable driver signature enforcement‘ from the list. You can now load your modified driver. Reboot again once the driver is installed and all will be well.
----------------------------------------------------------------------------
Q. I flashed the Stock Firmware Image. Odin flashes the file successfully and the phone reboots but it stays stuck on the samsung logo
If the firmware tar file does not include a userdata image (which most Samsung firmware do not) then your userdata partition will be left from your previous setup. If this is incompatible with the new firmware because of build or something else then your system will freeze on boot up.
This is easily fixable by holding the Volume UP, Home and Power buttons all at the same time for about 10 seconds until the device reboots to the Stock Recovery screen. Use the Volume Down button to scroll down to 'wipe data/factory reset' and press the Home button to select it. Go down to yes to confirm and your userdata partition will be wiped. Your device should now boot fine.
*reserved if needed*
How To Videos on the Samsung Galaxy Note II ToolKit
This post belongs to wwjoshdew I am just mirroring his posts from the other Note2 threads.
Reserved for how to videos on this incredible toolkit!
http://www.youtube.com/playlist?list=PLwCVKEYxr_z7FBQYT32dbYw_kdSJmSDH2
How To Root
How To Manually Boot to Custom (or Stock) Recovery
mskips magic
Another one in the series of TOOLKITS from Mskip ( here since the early xdays ) and im v-happy to see this here.
im already rooted but this will make root a safer process for so many Note-2 owners.
here we go
Appreciate your big work Mskip !!!
This is a wonderful and complete tool
Mskip, the legend! !!!!!
Sent from my GT-N7100 using Tapatalk 2
Great news. Thank you so much for this. I'm sure it will come in very handy :good:
Released!!
Download link in first post.
Please let me know of any errors or bugs so I can get them fixed ASAP.
Mark.
hi mskip
Thanks for this great tool, i was using it on my GS3 to and was very useful.
I have a little issue I'm not able to flash the "boot-insecure-xxalj1-n7100.tar" after i hit start it doesn't goes on, i waited more than 15 min and nothing, see attached picture:
Any advise?
Can this be used for Note 2 LTE?
Sent from my GT-N7000 using Tapatalk 2
M3xital said:
hi mskip
Thanks for this great tool, i was using it on my GS3 to and was very useful.
I have a little issue I'm not able to flash the "boot-insecure-xxalj1-n7100.tar" after i hit start it doesn't goes on, i waited more than 15 min and nothing, see attached picture:
Any advise?
Click to expand...
Click to collapse
Its a driver problem with Odin.
Try rebooting your phone and pc and use a different usb port. I had that problem in the past and it usually fixed it. Also make sure you dont have samsung kies on your pc as Odin doesnt play nicely with it at all.
Mark.
zard said:
Can this be used for Note 2 LTE?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
As far as I know the gsm and lte lodels are exactly the same hardware so in theory it should work fine. The only difference would be radios. This is what im hoping so I can keep everything under a single Toolkit. Do you have a link to a Note 2 LTE forum so I can check it?
Mark.
I've used these mskip all in one tools for various Android devices and can thoroughly recommend them. Whilst I have already rooted and modded my 7100 I will be downloading this tool and buying him yet another beer!
Sent from my GT-N7100 using Tapatalk 2
mskip said:
Its a driver problem with Odin.
Try rebooting your phone and pc and use a different usb port. I had that problem in the past and it usually fixed it. Also make sure you dont have samsung kies on your pc as Odin doesnt play nicely with it at all.
Mark.
Click to expand...
Click to collapse
Gonna try to reboot phone and PC and try another USB port. Don't have Kies installed. Will let you know.
hey
Is it a chance for mac version ?
Cheers
P
mskip said:
As far as I know the gsm and lte lodels are exactly the same hardware so in theory it should work fine. The only difference would be radios. This is what im hoping so I can keep everything under a single Toolkit. Do you have a link to a Note 2 LTE forum so I can check it?
Mark.
Click to expand...
Click to collapse
Thanks Mark! That did the trick.
Just another question, after making a Nandroid backup I end up (on my PC) with a 16 mb folder like on a incremental backup but without the blobs folder.
Don't know why not able to download from MediaFire.
Try to get it later again. Thanks anyway.
Ive used it, works like a charm!!!! Thanks so much mate, i wil be making a donation tomorrow.
Sent from my GT-N7100 using Tapatalk 2
mskip said:
As far as I know the gsm and lte lodels are exactly the same hardware so in theory it should work fine. The only difference would be radios. This is what im hoping so I can keep everything under a single Toolkit. Do you have a link to a Note 2 LTE forum so I can check it?
Mark.
Click to expand...
Click to collapse
Sorry, no links as yet. I'm waiting for the Note 2 LTE to launch here (that's the only model to be launched here) this month, thus I had started to read Note 2 threads to get myself ready. I'll pm you if I find any link useful. So far, from the threads in Xda Note 2, there's no good information on LTE.
Sent from my GT-N7000 using Tapatalk 2
NabiRootXD v2
{
"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"
}
This is a tool for rooting, installing Gapps(Play Store, etc), and adding custom TWRP recovery on Nabi XD. It's written as a windows command line batch file, and is based off NabiLab I made for Nabi2.
It was an adventure to say the least. I include some of the hurdles for those that want to duplicate the root process or just to place my thoughts "on paper" because of the 100's of posts I read from those that posted detailed information and allowed me to gain useful insight in how I could adapt things for the XD, and explain in one swoop to the many PM's I have received about "when will we see root on the XD" why it took so freaking long. Those that just want the program can continue to the Overview section.
What started as an interesting avenue was TWRP using the Nabi2 kernel was booting the NabiXD to TWRP without video. I thought it possible to dd the recovery, or boot kernel. Unfortunately it was unable to recognize internal storage as a block device and that ended that. Like a few devices on Android 4.1.1 and above the standard once click program using Bin4ry's ADB restore exploit doesn't work. It doesn't work for a couple of reasons, when restoring fakebackup.ab in locks up writing the first file, and even if it did work placing ro.kernel.qemu=1 in local.prop doesn't work because Jelly Bean doesn't parse any property files to set the ownership of adb daemon. Searching the file system I found su2 in the xbin directory. This was promising as it is the su program but renamed, also unfortunate was its permissions had no setuid bit set and while it was executable it would not change uid to 0. I then foolishly went down the path of nvflash(forced recovery). I attempted a few different avenues here to try and possibly get the SBK to unlock nvflash, that proved uneventful, especially without root access. I tried extracting what "could" be the key from the Nabi2 it hope it was reused. That lead no where, it would be awesome to have access to it for many other reasons but it turned out to be an exercise in learning but ultimately a waste of time. Then on to other Android exploits... Tried Samba, debugfs, and vfat exploit. All of those are either patched or I'm not skilled enough. I finally returned to looking at the ADB restore exploit.
The "tabletS" exploitation showed promise as it takes the avenue of installing /dev/sh vs ro.kernel. A side effect of the failed ADB restore bug was leaving a directory with full permissions. Bads3ctor had an interesting fakebackup.ab that was more reliable at making a directory or file that you simlinked have full permissions. Now you can step through the tabletS script more effectively where you couldn't before by manually setting permissions for files/directories you need by doing the restore for each file and directory you need. The script installs VPNfaker and backs up the /data/app directory, then creates a new app directory. This however will cause the NabiXD to rerun the initial kidsmode setup and breaks everything. You can dance around that by not rebooting, and VPN faker will still give you a Term app with system uid. From there you can't symlink the sysfs links properly to data/property but that can be worked around by moving and then removing files. Finally you can makedev /dev/sh and run su from /data/local/tmp. The end result is that the exploits and bugs found by others are adequate when strung together in the right order on the NabiXD just not the one click solutions provided on the forums, they needed some modifications and done by hand to figure out for the NabiXD
Here is a nice publication I found in my searches that is more layman terms for older root methods. http://www.sourceconference.com/publications/bos12pubs/android-modding-source.pdf
Overview
Video Overview of NabiRootXD - a video tutorial of the use of NabiRootXD.
-Root the Nabi XD
-Install Gapps(Play Store, etc)
-Make a stock backup of unrooted device
-Install stock, or TWRP recovery
-NabiLab patching system to install updates to this program
Version 2
-Fixed scripting error causing early exit
-Added 7z for patching system
Download
Read the installation section below to determine which version you want.
File names:
NabiRootXD.zip 96MB (Version 2)
Download
Download Mirror
Installation
NEW INSTALLS
1) Download NabiRootXD
NabiRootXD.zip 96MB
2) Extract the zip files to a location of your choosing. Run the NabiRootXD.bat file.
Prerequisites
1) Script is for Windows
2) ADB enabled in Android. Enter Mommy/Daddy mode. Open settings->developer options->put a check mark in USB debugging.
3) ADB and Fastboot driver. Most popular are the PDAnet drivers. You can get them here: PDAnet drivers
Usage
Obviously using this script on your NabiXD voids the warranty and I take no responsibility for the damage you cause.
MENU 1 - Root, Gapps, Recovery
Menu Option 1 - Install Root, Recovery and Gapps
This option is best used if you have a brand new Nabi. At this point you should have met the prerequisites of enabling ADB in Android. Follow directions, most sticking points are pressing the volume + and then pressing the volume - button twice and making sure recovery kernel is the one highlighted. After its complete you should have a rooted Nabi, with Gapps and a backup of your unmodified Nabi in the folder TWRP/BACKUPS/YOURSERIAL/stockunrooted on your device. Not a bad idea to copy this off the Nabi to your computer if you need to free space or have it in a second location.
Menu Option 2 - Install Root and Recovery
Same as above but doesn't install Gapps. Some people have trouble with option 1 taking the Gapps install, I personally have never experienced it but the option is this one, or I guess if you are an elite hacker that just wants root.
Menu Option 3 - Install Gapps
Same Gapps installed in the Option 1. Useful for re-installing Gapps. This is Jelly Bean Gapps dated 10/11/2012 without Google Search. This makes NO backup of you Nabi. You will have to already have installed TWRP.
Menu Option 4 - Install Root
Installs root. Nothing fancy here, and likely unneeded but here for completeness if you find yourself in a strange situation. One that comes to mind is that you have a stock backup which you restored and don't want to do another backup so you would just run this and the gapps install. It makes NO backup. You will have to already have installed TWRP.
MENU 2 - Install Recoveries
Menu Option 1 - Install TWRP 2.3.3.0 for Nabi Version 1.2.3
Installs TWRP 2.4.4.0. This is the latest at this time. It has a screen timeout, if the screen goes black touch the screen to wake the screen, it's not locked up.
Menu Option 2 - Install Stock Recovery
Installs stock recovery. This is useful for taking an OTA, or completely returning Nabi to stock.
Notes: TWRP installs are based off my work in this thread if you want to read more.
MENU 3 - Patch NabiLab
Menu Option 1 - Install Patch
For any updates to NabiRootXD this is where you can automatically load them. Basically you will download NabiPatchXD.zip and place the entire zip in the patch folder. No unzipping just the single file. Then run this option.
Credits - If you see these guys buy them a beer.
jzmtaylor - Original Nabi2 script that this is based off of.
Bin4ry, Bads3ctor, HEXcube, drjbliss - all the bugs/exploits needed to accomplish root
Dees_Troy - TWRP build tutorial
Eric Karz - TWRP Theming and rooting assistance
TeamWin - They are the guys that make TWRP possible
Weeee more Easter goodies haha.
thanks aicjofs
Sir can i use this tool for installing Gapps for unrooted Galaxy Tab 7.0+ (wifi)? bcoz i updated my tablet for Honeycomb to Ice creamsandwich (China Firmware), everything is fine except that i cant open google playstore...
first of huge thank-you.. who do i send a bear donation to as a thank-you
there is a possible bug or its just me when pressing the menu button it will pull up a search, or say Google with a white back ground only way to get out isto press home if a menu appears then pressing back produces the same results
srgsng25 said:
first of huge thank-you.. who do i send a bear donation to as a thank-you
there is a possible bug or its just me when pressing the menu button it will pull up a search, or say Google with a white back ground only way to get out isto press home if a menu appears then pressing back produces the same results
Click to expand...
Click to collapse
The gapps removes the problem in system/app/quicksearchbox.apk you can rename it toquicksearchbox.bak
only other way I can think of is some how playstore added it to data/app
rename com.google.android.googlequicksearchbox.apk to com.google.android.googlequicksearchbox.bak
hth
ps: thank the op he spent hours and hours to make this happen = sacrificed his free time
Thanks for the feedback.
Perhaps we should have used the 7/26/2012 gapps? http://goo.im/gapps/gapps-jb-20120726-signed.zip 10/11/2012 is suppose to be 4.1.1 backward compatible, but perhaps there are some bugs with it on XD. Flash over the top of the current one. It will leave behind /system/app/thinkfree.apk, /system/app/microbes.apk and /system/lib/libmicrobes_jni.so, which you could remove manually. Wipe caches.
How about GPS stuff? Is that working?
i was looking at gapps-jb-20120810-JRO03C-Formula84-Custom
it has some things that sort of work like maps/local/ latitude /
I don't think gps is working
Even in the productions test it fails .
could it be a permissions problem ? I have not tried 20120726 .
Eric Karz said:
i was looking at gapps-jb-20120810-JRO03C-Formula84-Custom
it has some things that sort of work like maps/local/ latitude /
I don't think gps is working
Even in the productions test it fails .
could it be a permissions problem ? I have not tried 20120726 .
Click to expand...
Click to collapse
Do we know that the GPS works at all?
aicjofs said:
Do we know that the GPS works at all?
Click to expand...
Click to collapse
with gapps installed it doesn't seem to work .
maybe we are going to need a edited gapps ?
I'm just going to remove Google Search for now. That is highly annoying, I was messing around with ways to fix it, and got it to open in apps when you press the settings button, I was previously only getting it when pressing back button.. I updated the downloads. Until we figure out the fix, it's just too troublesome.
cool that did the trick renaming the file i do have a really stupid question is there a hiden proxy setting that makes the tablet able to bypass our DNS security filters with open dns just curious
srgsng25 said:
cool that did the trick renaming the file i do have a really stupid question is there a hiden proxy setting that makes the tablet able to bypass our DNS security filters with open dns just curious
Click to expand...
Click to collapse
I don't know if there is a hidden proxy. I'm not sure of your question. You could try going to settings-wifi. Long press the name of the network and a pop up will come up. Modify network, show advanced options. There is the proxy and DNS, for DNS you have to be static. I think there is 4.4.4.4 in there by default, plus what your router gives out.
If you are talking about something more underground I think you could use a getprop in adb shell or term.apk. I know I have seen stuff in there for DNS, something like dhcp.wlan0.dns there is stuff in there about "change" too. Should be able to set if you "su" and do a setprop. That would only be good until reboot, but could help you trouble shoot. I think it's set here /system/etc/dhcpcd/dhcpcd-hooks/20-dns.conf, maybe not in Jellybean. Anyway those are places to look if it's more then in settings that you are looking for.
ok it seems that this might be a work around to the quick search problem
edit the buildprop and change
ro.sf.lcd_density=160
to
ro.sf.lcd_density=145
I tried 149,150,59 and 120
120 does seem to fix it also but the screen makes every thing look smaller and some may not like that .(I do)
also I had to install BusyBox in order to get a few things to work including
build prop Editor by Nathan Campos (this tool seems to be a good test app to see if you have proper permissions)
note that the swipe screen will be a bit smaller under 160
maybe some one can use this info to edit quick search box we wouldn't have to change anything?
i am trying to get this tablet to use my network opendns settings and web filters
Can someone direct me to where I can get a Vista MTP driver for the Navi XD? I installed PdaNet as instructed but the tool wont connect, and I have a yellow exclamation mark by MTP Device. Can't seem to find anything else online.
EDIT: After rebooting a few times, then disabling my firewall, the tool connected. Thanks for the awesome tool.
Looks like an OTA was released for the Nabi XD today that bumbs the Nabi XD up to version 1.3.5. I tried doing the stock recovery option but the NabiRootXD app just closes out after selecting it. I looked into the NabiRootXD.bat file and I noticed on line 483 that it says to "GOTO Install_4" which doesn't seem to exist. I believe it should actually say "GOTO Install_2".
After making this change I was able to restore to the stock recovery to perform the OTA.
Now once I tried to install the OTA it appeared to atart the installs and then fails with the dead android symbol about a third of the way through. No idea what the problem is now so I'll just wait for others to try this and see what their results are.
yup getting the dead droid
Reinstall TWRP and "Install" this to update. Have a backup. Should work if you have made no system modifications, except what NabiRootXD did.
Download
TWRP may or may not ask you to reinstall superuser.
Also working on a patch to fix the exiting error in script.
EDIT: New links for a version 2. Fixed scripting error and patch system error. Easier to just download the whole program again then for me to explain fixing the patching system manually.
OTA procedure
srgsng25 said:
yup getting the dead droid [
BOOT into TWRP and perform and system restore to pre-root image
reboot
download and install the OTA
reapply root and gapps
Click to expand...
Click to collapse
aicjofs said:
Reinstall TWRP and "Install" this to update. Have a backup. Should work if you have made no system modifications, except what NabiRootXD did.
Download
TWRP may or may not ask you to reinstall superuser.
Also working on a patch to fix the exiting error in script.
EDIT: New links for a version 2. Fixed scripting error and patch system error. Easier to just download the whole program again then for me to explain fixing the patching system manually.
Click to expand...
Click to collapse
Thanks for the update aicjofs! I'll test this out shortly and let you know how everything goes.
[SIZE=+2]This thread has been created
for
• Questions • Answers • Troubleshooting •[/SIZE]
[SIZE=+2]Dealing with ► Dirty Unicorns ◄ ► Moto G Falcon ◄[/SIZE]
[SIZE=+2]Please feel free to share issues, questions and offer help[/SIZE]
{
"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"
}
[SIZE="+2"]
>> [ROM] [OFFICIAL] Thread: >> Link Here <<[/SIZE]
.
[SIZE=+2]Please Do not clutter the Development thread with non related development chatter[/SIZE]
[SIZE=+2]
Please read the OP in dev thread carefully, it has some very important info in it.[/SIZE]
[SIZE="+1"]Please keep discussion focused, on the topic described in the OP[/SIZE]
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[SIZE=+3]
Please provide ► exact Version and Date ◄ of ROM
Please provide ► exact Version and Date ◄ of Recovery
Please provide ► exact Version and Date ◄ of Kernel
[/SIZE]
Repost:::
[SIZE="+2"]How to report bugs, the proper way ![/SIZE]
http://therealmofu.com/wp/?p=644
Credit:: by TheRealMofu
Credits:
Indirect for his guide
FuzzyMeep Two for his Windows Logcat Tool
[SIZE="+2"]
Connecting your device through adb on Windows/Ubuntu:[/SIZE]
▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼
[SIZE="+1"]Windows:[/SIZE]
On your PC you need to be logged in as an administrator for doin this and make sure that you activated “USB Debugging” in Settings/Developer Options on your phone !!!
Connect your phone with the USB cable to the PC and select MTP mode
Open the Windows command prompt, which you also can open through pressing Win + R on your keyboard
Now type:
Code:
cmd
Now change into the folder you installed adb, for example:
cd c:\adb
Now were we are in the correct folder, type:
Code:
adb
Now you see a lot of commands appering, and when done, type:
Code:
adb devices
and your phone (Device-ID) should be listed in there, that’s it
[SIZE="+1"]Ubuntu:[/SIZE]
Make sure that you activated “USB Debugging” in Settings/Developer Options on your phone !!!
Connect your phone with the USB cable to the PC and select MTP mode
In terminal type:
Code:
cd (TOOLS_PATH)/android-tools
Then issue the following:
Code:
./adb devices
That’s it
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[SIZE="+2"]These are the options for reporting a bug:[/SIZE]
▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼
[SIZE="+1"]Section 1 | Logcat:[/SIZE]
This log should almost always be included just because it provides more info than just saying something doesn’t work. It will essentially tell you which apps are crashing and why and it also gives output of what they’re doing. (Your system is running through apps, the dialer, wireless radio’s, etc are all ran through apps.) so, if something is general, like a system force close, please just include a logcat.
How to get a logcat:
Well, this is REALLY simple, all you need to do is just get adb up and running (google how to do that, I don’t feel like writing a ‘how to use adb’ tutorial for everyone’s phone.) and then type
Code:
adb logcat
then you just right click, select, and paste to
http://pastebin.com/
http://logcat.us/
http://paste.ubuntu.com/
and provide the link in the thread/post.
It’s really that simple!
For Windows users i found an self explaining noob friendly program called Windows Logcat tool 4.0
[SIZE="+1"]Section 2 | Dmesg:[/SIZE]
This is getting into issues such as wifi not working, sleep of death, etc. Basically, things that make us go “OH F***” when we use our devices. Note: You will need adb access for this to work, same as logcat.
What this will do is get us live kernel output so we can know things like “What driver is the kernel loading {or not loading for that matter}” and similar things. This is linux, so kernel output is important if a hardware aspect isn’t working right.
How to get a dmesg:
This is simple as well, no matter what operating system you’re on (mac, windows, linux) just type
Code:
adb shell dmesg > dmesg.txt
and then it will have written the output to a .txt file in your current directory. Either paste the contents to the thread, or attach it to your post.
You can also get the dmesg by using terminal emulator. Instead though, you dont type adb shell, you need to also include it to somewhere you will be able to save it. Like /sdcard so, the command goes
Code:
dmesg > /sdcard/dmesg.txt
Just get it off your sdcard and get the contents to the developer!
[SIZE="+1"]Section 3 | last_kmsg:[/SIZE]
Ok, the last thing is last_kmsg. When android kernels crash, they right to last_kmsg so then you can find out what’s going on. This is usually for issues such as random reboots and other various kernel panic symptoms. A kernel panic happens when the kernel tries to do something it can’t. It doesn’t mean wrong permissions, it could just have errored out on something and died which can cause a few things. Anyway, developers REALLY need this if debugging a kernel because it gives us a viable way to see WHAT it’s trying to do instead of trying to guess what it is trying to do
How to get a last_kmsg:
This is super simple and the same on all phones no matter what, what you need is adb up and running (or terminal emulator) and either in adb shell, or terminal emulator just type
Code:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
or you can do
Code:
adb shell cat /proc/last_kmsg > kmsg.txt
and that will write it to your current working directory from cmd.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[SIZE="+2"]Here is another great instruction tutorial link:[/SIZE]
[SIZE="+2"][WIN][TUTORIAL]HOW TO USE ADB,DDMS AND TAKE A LOGCAT {pictorial explanation} [/SIZE]
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
It's been noticed that sometimes during the install of this it will take a long time to flash.
Just be aware of this known issue
It happens during the format /system of the device
it happens even on the current newest TWRP 2.8.0.1 or twrp-2.8.0.1-xt1032.zip
and sometimes it even happens if you have manually formatted /system in advanced mode
Normal install time ranges from :30 seconds to 1:00 Minute
longer times have ranged with older TWRP recoveries or CWM or Phil's anywhere from 3:00 minutes to 10:00 Minutes
TeamMex has reported that is is most likely an updater-binary issue
reversegear has tested and posted a workaround for those wishing to mod their copy of the ROM
or you can choose to wait out the extra time needed to install this awesome ROM.
one more to hold
Just wanted to say THANK YOU @hhp_211 for creating this thread so that the development thread could possibly level out and get back to where it original was headed
I get the first question. I finally decided to try this out. I'm using the latest official version of CWM; 6.0.4.7 touch. I can report that it did take maybe 5 min to flash the ROM from start to finish. After the first boot, i rebooted to recovery and I then flashed the GAPPs, DU_TBO_GAPPS. I noticed that upon reboot, and signing into my Google account, that the ROM didn't automagically start downloading all my apps from the play store. Is there a setting that I needed to have set?
I went ahead and restored my backup for the time being. The ROM looked nice and smooth.
Thank you.
Sent from my XT1034 using Tapatalk
alfick3 said:
I get the first question. I finally decided to try this out. I'm using the latest official version of CWM; 6.0.4.7 touch. I can report that it did take maybe 5 min to flash the ROM from start to finish. After the first boot, i rebooted to recovery and I then flashed the GAPPs, DU_TBO_GAPPS. I noticed that upon reboot, and signing into my Google account, that the ROM didn't automagically start downloading all my apps from the play store. Is there a setting that I needed to have set?
I went ahead and restored my backup for the time being. The ROM looked nice and smooth.
Thank you.
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
I believe that is a modded apk to be that way
to change go to
Play Store::Settings::Auto-update apps::
and choose your preferred method
@hhp_211, thanks. I didn't think about going into the play store and looking at the settings. I'm used to other GAPPs packages where it just automatically installs my apps from previous ROMs or phones.
Sent from my XT1034 using Tapatalk
I re-installed today, after flashing the latest TWRP (2.8.0.1). I wiped system, data, cache and dalvik cache. I did not wipe my internal SD card. This time I flashed the ROM, then flashed the GAPPs right away instead of booting into the ROM first. Upon reboot, it asked me to sign into my Google account, and then automagically started to download my apps. So far, so good; although it's constantly giving me a "Unfortunately, OmniSwitch has stopped". After all my apps have downloaded, I'll do a reboot and see.
Is it possible to have FM radio app? Zip? Or it is completely unsupported? I'd rather not to buy a third party app.
Thanks in advance
i have a problem with the BACK soft button in landscape, whenever i press it (and in landscape) it goes to "google now"
i dont know what causes this issue right now (it may be the Recents bttn ... i use inverted bttns)
The problem seems to be that the part avobe of the "home" button black part is for some reason usable??
its kind of wierd but right now i cant go "Back" in landscape because it goes to google now !
im on dirty 8.0 the last one Stock
Mao_anguita said:
i have a problem with the BACK soft button in landscape, whenever i press it (and in landscape) it goes to "google now"
i dont know what causes this issue right now (it may be the Recents bttn ... i use inverted bttns)
The problem seems to be that the part avobe of the "home" button black part is for some reason usable??
its kind of wierd but right now i cant go "Back" in landscape because it goes to google now !
im on dirty 8.0 the last one Stock
Click to expand...
Click to collapse
I'd say grab a Logcat
Maybe also include some screenshots of your layout in landscape
I'm still on the test 8.0 and back works OK,, but i also don't use Google now
.
Code:
*** Disclamer
Be aware that you are able to brick your phone with this tool. I take no responsibility for your actions and/or damage and/or malfunction on your device. If you don't know how to use ADB or Fastboot, read tuturials first. You will be responsible for you actions all alone!
Introduction
Hello guys
Beacause many newbies don't want or to mess with the shell or simply dont know how and experienced users and developers are pretty lazy people i developed a tool which takes over basic actions like flashing/wiping partitions, sideloading zips, push/pulling files, taking screenshots or screen video and a lot more. Of course adb and fastboot commands can be executed as usual over the build-in shell.
Until now its a early beta only able to process basic tasks, not everything works as expected yet.
I've sometimes more, sometimes less time to work on this project, so i cant give etas to future releases!
Click to expand...
Click to collapse
Images
{
"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"
}
Click to expand...
Click to collapse
Installation instructions
Download the latest build by following the download link down.
Once downloaded, there is no need to install - just run it and you're ready to go
The ADB/Fastboot binaries are packed with the application, no need to download them aftwerwards. However - if you want to use your own android sdk, you're able to change the working path to your sdk.
Click to expand...
Click to collapse
Download
Download the latest version (build 2801) from 15-06-28 here:
> > http://aafc.leonhard-kuenzler.de
Click to expand...
Click to collapse
Changelog
Code:
Changelog:
(sorted by builds)
2776
[fixed] runCommand handling
[fixed] auto device detection
[added] screenshot feature
2778
[fixed] device serial for auto detect
[fixed] screenshot
2779 - 21.05.15
[fixed] icon settings
[deleted] unused code
2783 - 25.05.15
[changed] Gui title
[added] screen recording
2875 - 28.05.15
[fixed] sideload
[added] preferences window
[changed] Frame behavior
[fixed] insert path (drag_drop)
[fixed] sdk not found error
2801 - 28.06.15 | latest build
[added] apk install/uninstall
[changed] device detection
Click to expand...
Click to collapse
FAQ
-- in progress
Click to expand...
Click to collapse
Thanks To/Credits
Code:
all people testing and giving feedback so far :)
XDA:DevDB Information
AAFC Android ADB Fastboot Commander, Tool/Utility for all devices (see above for details)
Contributors
92lleo
Version Information
Status: Beta
Current Stable Version: -
Current Beta Version: 0.8.5
Beta Release Date: 2015-06-28
Created 2015-06-04
Last Updated 2015-06-28
How-To
After downloading:
(1) startup
On first start you will have to read & accept the disclaimer. You're able to turn that message of.
Now the main frame should show up. If you have installed android sdk, you can use yours instead the build in by setting the sdk path in ">SDK>change path" to your sdk path (most likely C:/Programm Files/Android/android-sdk). Select the android-sdk folder.
(2) connecting your phone:
connect your phone to your computer. on phone, go to "settings>developer options" and enable "usb debugging". if there is no "developer options", go to "(device) info>software info" and tap 7 times on "build-number". Developer options should be visible now.
Your phone should now ask you to confirm usb connection to your computer. if not, go on with (3)
(3) driver-troubleshooting
some vendors ship their drivers with windows update, they should be installed on first connect. Google also ships drivers for its devices with the android sdk. In all other cases, unplug your phone and go to ">options>device drivers". Now you have two options: 1. try the easy way universal-usb drivers from clockworkmod. Install them, connect your phone and try again. You may open the
windows device manager (WIN+R > devmgmt.msc), there you should see your device (either with warning, or successful connected) 2. search for the right vendor driver.
Choose from the list and install the drivers. May you also search for lite packed drivers on xda/web.
.. more comeing soon
Bugs & Features
Known bugs:
When starting tool not from its parent directory, but e.g. from chrome downloads, setting paths somehow fails (you'll get an error message). To start, navigate to your download folder and start it from there. If you still face problems, delete the "adbfbdata" folder in the same directory
Video recording/screenshots not working (stuck after pulling screenshot/video)
(This happens cause some devices don't allow to pull or write from/to /sdcard. Working on a fix right now)
When returning to internal sdk, the realSdk variable in the properties file is erroneously set to true, which results in an exception at the next start.
To solve this, delete the properties file in the /adbfbdata folder or set "realSdk" to false
Planned features:
Backup over adb or recovery
Multi-device support
Device specific actions (e.g. unlock bootloader on htc devices)
device info storage (online) for specific actions, downloads links etc.
Fastboot support for samsung devices via haimdall command line tool
workspace monitoring and intelligent file suggestions
A lot of gui improvement
Version 0.8.4 online
Version 0.8.4 (build 2787) is now online.
Changes:
You don't need to fill in your devices serial number from now - whenever a device is detected, its serial will be shown.
Currently, only one device can be handled (except from your own commands).
Tool will automatically search for updates and notify you in case of a newer version. You also can check manually by clicking Options->Check for Updates
Version is ready for download here.
Version 0.8.5 online (multi OS support)
Version 0.8.5 (build 2798) is now online.
Changes:
You now can use AAFC on your Mac, Windows or Linux machine! All adb & fastboot binaries are packed within the tool (even 64 & 32bit versions for some linux distributions) Please note: Support for Mac OSx and Linux distributions is still in early development (alpha) which means, you'll be able to run commands on every os, but may not use every gui function cause the gui is only optimized for windows for now. Please post your experiences in this thead or write me a message!
Tool will modify internal files and watchdogs for the current os
Tool will now delete whole temp folder, not only files
Look and feel changed to "Nimbus" on Linux because of Gui problems. On Windows and Mac OSx its the known OS layout
Version is ready for download here!
Troubleshooting:
If you're not able to tick the checkboxes in the disclaimer frame, check if there is a information dialog behind it. May the UpdateChecker tries to lay over the frame, but the disclaimer cannot be overlaid. I'm working on that.
If you get an exception like "File not found", please post it here (like any other exception). To solve this problem, try deleting the adbfbtool folder in the same directory (to reset the preferences)
Hey,
i tried your tool (build 2798) and really liked it!
I used it on my macbook and it worked well. Sometimes it gives me an exception like "file not found", but after a restart, it works again. I just needed it to flash diffrent recoverys while bringing my phone back to stock.
i would like the tool to remember the last directory i choose a file in, so i dont have to navigate through all my folders again. Also it would be cool, if you implement the shown backup/restore and apk install function. and maybe some quick actions like flashing a recovery with just a file chooser dialog.
I'm looking forward to the next update and will try it then!
friFroAndro said:
Hey,
i tried your tool (build 2798) and really liked it!
I used it on my macbook and it worked well. Sometimes it gives me an exception like "file not found", but after a restart, it works again. I just needed it to flash diffrent recoverys while bringing my phone back to stock.
i would like the tool to remember the last directory i choose a file in, so i dont have to navigate through all my folders again. Also it would be cool, if you implement the shown backup/restore and apk install function. and maybe some quick actions like flashing a recovery with just a file chooser dialog.
I'm looking forward to the next update and will try it then!
Click to expand...
Click to collapse
Hey, thanks for your feedback! The file not found exception will be gone on linux and mac within the next release, it's left from windows-only.
Remembering directories is planned, in fact, i planned to set a working directory/directories, where the tool searches for .imgs and zips and stuff, so it can suggest them.
Quick actions - or something like that- are comeing when everything else is working
APK install is implemented, you're able to use it with the next release, I'm working on backup (both adb and recovery) right now. Maybe it's usable in the next release, or maybe in other future releases.
New Build 2801 (still 0.8.5) online
Build 2801 is now online.
Changes:
You can now install / uninstall apks over the gui with setting command flags
Device detection now start/stoppable
Small GUI changes
Version is ready for download here!
Im currently working on:
Backup over adb or recovery
Multi-device support
Device specific actions (e.g. unlock bootloader on htc devices)
device info storage (online) for specific actions, downloads links etc.
Fastboot support for samsung devices via haimdall command line tool
workspace monitoring and intelligent file suggestions
A lot of gui improvement
If you miss something or have other feedback, feel free to contribute!
_____
edit:
looks like there is a bug in screenshot/video recording, it doesn't work in older versions as well. You may try it, but it wont work. I'll fix it with the next release!
{
"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"
}
It has LINUX/UNIX and MAC support!
Due to the fact that there is another tool for Android called Android Multi Tools, I decided to rename this one to Lx Multi Tool, future releases will go under this name.
Features: Fastboot
- Unlock/Lock Bootloader
- Flash Recovery Menu (you can choose and add recoveries) - TWRP 2.8.7.2 Included
- Flash any partition (Flashing submenu)
- Flash full Stock images (you can choose and add images)
- Erase partitions (you can choose which of the partitions)
- Reboot (you can choose again...)
Adb
- Sideload .zip files (you can choose and add .zip files) - SuperSU v2.65 (Systemless!) included
- Backup (you can choose the name and place for your backup)
- Restore (you can choose your backup)
- Version (it just shows the version of your adb binaries) - platform-tools 23.1 included
- Logs (DMESG and Logcat)
- Screenshots (you can directly take screenshots to your PC with no Root)
- Reboot (lots of choices)
Others
- Refresh and delete files/folders from menus (Right click or key F5 and Del)
- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)
- Tab key support for easier keyboard navigation
- Tool-tips for all buttons
- Check for updates
- Link to xda-thread (here)
Download links: Windows x86|x64 - Linux x64 - MAC x64
All released versions can be found here.
[ROOT] Use SuperSU 2.62 or higher from here systemless for 6.0.1 and above.
Known bugs/limitations: - For partition Flashing, it is recommended(mandatory?) to do a reboot-bootloader if you want to flash multiple partitions one after the other. (according to the Google flashing scripts) (Implemented in 1.2.1)
- For return to stock, the tool will be stuck after your phone successfully boots, you need to reboot to fastboot again in order to flash the Radio and finish the full return to stock. (Fixed in 1.2.0)
Changelog:
Check the changelog for each release here.
Tutorials/FAQ:
Q: How do I get in bootloader/fastboot mode?
Turn off the phone and turn it on by using Volume down + Power key.
Q: How do I check for updates in your tool?
Follow the instructions in the screen below.
Q: Where can I find the device driver to install it for windows?
Click here, download the driver and run the setup.
Q: How do I root my stock phone?
- Unlock bootloader.
- Flash recovery.
- Use SuperSU 2.62 systemless or higher from here.
(Usually the latest version upon tool release is included in the Sideload folder of the tool, you can either sideload it or copy it to recovery and flash it manually)
Q: I get an error "Cannot open file" on MAC, what should I do?
Open the terminal, go to your application path and paste this command:
Code:
chmod +x LxMultiTool.app/contents/macos/*
Q: What do I need to do in order to be in Fastboot or in ADB mode.
Fastboot mode will be detected only while being in bootloader.
ADB mode will be detected from Recovery (custom) and actual ROM with USB debugging active.
Refresh button needs to be used in order to check for what mode you are in.
Q: Are there any other software that I need to install in order to run this tool?
On Windows and MAC everything is bundled, so nothing needs to be installed, just run.
On Linux you need to install from your package manager libQt5Core, libQt5Widgets, libQt5Gui, libQt5Network.
If it's not enough, use ldd LxMultiTool in terminal to find out what you're missing from your environment.
Q: I have an yellow/orange/red text screen during boot, what's that?
When you unlock you usually get the Orange screen and it's normal, but if you really want to know what's this about, give a reading to this.
Q: Hey, my device is not detected, why?
On windows, you need to manually install the USB drivers, they are not included and probably they won't be included in this tool.
Also, make sure you click the connection Refresh button after connecting the device to your PC.
Q: What do i need to do in order to install a custom ROM?
1. Unlock Bootloader.
2. Flash a custom recovery of your choice.
3. Flash an insecure kernel (boot).
4. Flash custom ROM with no problems via recovery.
All those things are found and can be done via this tool.
Q: Hi, i just downloaded this tool, how do i use it?
First, extract the folder somewhere.
After that, run LxMultiTool.exe on windows by double clicking it, LxMultiTool on linux and the same on mac.
Q: Do I need android-sdk installed or something else?
No! This tool uses it's own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyways.
This tool is fully portable and stand-alone.
Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?
Starting with Android 5.0, you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:
- Enable Developer options
- Enable USB Debugging
- Look for the ‘OEM Unlock’ Option and toggle it.
Q: How do I use the return to stock feature?
First download the latest package from here, then extract the contents (there is an archive in the archive) untill you get the a folder like angler-mda89d
that contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.
Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.
Q: How do I enable Developer options?
- Launch the Settings
- Scroll Down and Tap on About Phone(or About Device)
- Locate the Build Number Section
- Tap on the Build Number Option 7 Times
- Go Back to the Main Settings Page
- Scroll Down and Tap on Developer Options
Q: Hi, i just bought a phone what should i do now?
Well, you firstly need to unlock your bootloader...
Q: What is logcat?
Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.
It is usually used for debugging and entertaiment(?).
When you report an error/bug to somebody, it will be a blessing to provide a logcat (logfile)!
Q: What is a Custom Recovery and why do i need one?
A custom recovery is that thingy that let's you flash .zip files, use your logic and you wil get it why you need one.
Q:There are others guides/tutorials out there, should i check them instead of this?
If you manage to get things done using this one, no, otherwise yes, note that some could be outdated...
Q:What is sideload and how do I use it?
Sideload is a function from adb that let's you flash a zip file while in recovery directly from your PC.
Please note that you need to be in sideload mode on your recovery before doing this.
To enter sideload mode, in TWRP go to Advanced -> ADB Sideload -> Swipe to sideload
Sources: The official and original repository can be found here.
Bug reports/Feature requests: If you have any bug, or you consider a feature to be a must-have, please use the issue functionality on github for more traceability here.
Licensing: Please note that this tool is open source and released under GPL v3 licence which can be read here.
Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.
Tech and stuff: Some additional marketing for stuff used in this tool
Qt - An awesome cross-platform IDE
Vmware - For letting me test this tool on all platforms (Linux and MAC).
Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)
UnixUtils - For the sed utility for Windows.
AndroidFileHost - For the awesome file-management platform for developers.
Donations: Even though this tool is provided free of charge, full open-source, donations are very welcome to support the future development of this tool and to buy me a beer while coding future improvements on it.
This section will also include the hall of fame for donors, as well as on the github repository.
Special thanks for donations:
- @john7760
Disclaimer:I will not be responsible for smashed screens, bricked phones or any other things that you can accuse me of, i've done this tool to help people, use it at your own risk and consider giving a THANKS if you use it and like it.Please consider leaving some feedback, what to improve, what could be done better, what annoys you, it really helps me improve the tool.
Also, to avoid useless threads on general, Q&A or useless posts, please read the FAQ section upside, it's like a Mini-Guide!
Thanks!
I think there will be more people. Need to run a better window.
Windows7 64bit, part of the code.
Now, I have a simple editing of it.Make it look good.:laugh::laugh:
Download link:
https://mega.nz/#!nQBiDL7J!aDd9BhKtRw2tuYrpD7fImUXMn_Hl-qmUzwqKY13bYTc
Getting an error
FAILED(remote: oem unlock is not allowed)
Skies/SANKE said:
Thanks!
I think there will be more people. Need to run a better window.
Windows7 64bit, part of the code.
Now, I have a simple editing of it.Make it look good.:laugh::laugh:
Download link:
https://mega.nz/#!nQBiDL7J!aDd9BhKtRw2tuYrpD7fImUXMn_Hl-qmUzwqKY13bYTc
Click to expand...
Click to collapse
Well, I've looked at your edit and I don't understand what looks better than mine... It might be subjective though...
Pikezer1337 said:
Getting an error
FAILED(remote: oem unlock is not allowed)
Click to expand...
Click to collapse
Will investigate this problem and I hope I will get a solution fast
Edit: The information from this link might help with your problem.
I am running Arch Linux.
My shell is ZSH.
I downloaded and extracted, and ran zsh (filename).
I wanted to go with option 1 and got this
Code:
[= LG Nexus 5X - Multi Tool v0.1 - Linux =]
[1] Unlock bootloader. (via fastboot)
[2] Relock your bootloader. (via fastboot)
[3] Flash Recovery menu. (via fastboot)
[4] Backup and restore. (via adb)
[5] Recovery sideload. (via adb)
[r] Reboot menu.
[l] Logging menu.
[q] Quit.
Select your option:
1
menu:23: command not found: bootloader
127 [email protected] ~/Android/5XMultiTool.v0.1 % :(
any ideas?
paOol said:
I am running Arch Linux.
My shell is ZSH.
I downloaded and extracted, and ran zsh (filename).
I wanted to go with option 1 and got this
Code:
[= LG Nexus 5X - Multi Tool v0.1 - Linux =]
[1] Unlock bootloader. (via fastboot)
[2] Relock your bootloader. (via fastboot)
[3] Flash Recovery menu. (via fastboot)
[4] Backup and restore. (via adb)
[5] Recovery sideload. (via adb)
[r] Reboot menu.
[l] Logging menu.
[q] Quit.
Select your option:
1
menu:23: command not found: bootloader
127 [email protected] ~/Android/5XMultiTool.v0.1 % :(
any ideas?
Click to expand...
Click to collapse
The problem should be fixed in the V0.2, the Linux and MAC versions are not tested before posting, so bugs could still be around there...
added to index
Hi all, imusing linux and just tried to unlock my 5X. it worked but my question is, it is normal that it formated automatically?
after reboot, i have to start all over again with my account and setup.
Yes it's normal
Thanks mate, I'm new with nexus devices. One last thing, do I have to locked again or its OK leave it like that since on every reboot its showing me that I'm unlock. Sorry and thanks
Sent from my Nexus 5X using Tapatalk
You can leave it like that as long as you can deal with that message on every boot. If you lock it, you would have to unlock (and wipe) again if you ever want to flash anything again. Personally, unless you want to stick with the stock ROM OTAs, I'd leave it unlocked.
Would you confirm your Tools Re-Lock feature works with Custom Recovery (TWRP) without bricking device?
Born<ICs said:
Would you confirm your Tools Re-Lock feature works with Custom Recovery (TWRP) without bricking device?
Click to expand...
Click to collapse
Usually, locking your device does not brick anything, if everything works fine before locking, everything will work fine after locking, you are only limited after locking.
Lexmazter said:
Usually, locking your device does not brick anything, if everything works fine before locking, everything will work fine after locking, you are only limited after locking.
Click to expand...
Click to collapse
.
Would you mind answering the question?
With custom recovery, TWRP, installed and unlocked what happens when you use your Tool to go back to Lock?
Have you tested?
Thanks
Born<ICs said:
.
Would you mind answering the question?
With custom recovery, TWRP, installed and unlocked what happens when you use your Tool to go back to Lock?
Have you tested?
Thanks
Click to expand...
Click to collapse
To be honest I never locked my bootloader, didn't found a reason to, so I didn't tested.
But technically speaking, the only thing that happens is that you cannot flash other custom recoveries (fastboot stuff basically) without unlocking again and wiping all the stuff on your device.
OK, thank you. ReLocking to flash factory image was what I was thinking. I read doing so can lead to bootloop. Just trying to make note of things to avoid doing.
Cheers
You can lock and unlock your bootloader as much as your heart desires without consequence
skulldreamz said:
You can lock and unlock your bootloader as much as your heart desires without consequence
Click to expand...
Click to collapse
Well, wiping your data partition can be a pretty big consequence...
-edit-
You used to be able to use BootUnlocker for Nexus Devices to lock and unlock the bootloader from within the OS, but it looks like that's a no-go on the 5X...
I'm new to the nexus devices, but if I unlock the bootloader and root, will I loose both if I take an OTA update?
owenrg said:
I'm new to the nexus devices, but if I unlock the bootloader and root, will I loose both if I take an OTA update?
Click to expand...
Click to collapse
You will definitely lose root. I don't know about the bootloader since I've never taken an OTA, but I would guess that, unless there are bootloader changes in the update, your bootloader would stay unlocked. And to my knowledge the bootloaders are pretty much never updated for incremental OTAs.