[LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide - LG V20 Guides, News, & Discussion

{
"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 method will, when completed, will provide you with root and an unlocked bootloader, with fastboot available. It is a somewhat involved process, but the majority of the process has been simplified as much as possible.
WARNING!!!!This replaces your current bootloader with a debug bootloader. If you attempt to lock this bootloader you may brick your device.
Currently AT&T(H910) and Sprint(LS997) cannot return to stock because no KDZ files are available.
Disclaimer:
Once your phone is unlocked, it will no longer be covered by LG warranty @me2151.
As we cannot guarantee the proper operation of our hardware with custom software, we are not able to maintain the full scope of warranty for your device after you have unlocked the bootloader.
Because of that we have a responsibility to let you know that defects which may result from, or were caused by custom device-software may not be covered by LG warranty @me2151.
LG @me2151 can no longer guarantee the full functionality of your device after you unlock the bootloader. Unlocking your device may cause unexpected side effects that may include but are not limited to the following:
***Your device may stop working.
***Certain features and functionalities may be disabled.*
***Your device may become unsafe to the point of causing you harm.
***Your device becomes physically damaged due to overheating.
***The behavior of your device may be altered.
***Some content on your device may no longer be accessible or playable due to invalid DRM keys.*
***All your user data, settings, and accounts may disappear. (Therefore, we recommend that*you*backup all your data).
** -*Software updates delivered via LG FOTA (Firmware Over the Air) or Web Download services may not work on your device anymore.
LG @me2151 will not be responsible for the damages caused by any*custom software being flashed to your phone.
Known Issues:
AM&FM Radio no longer works
Boot time higher
No way to revert to stock(LS997/H910)
Possible overdose of root awesomeness!
Maybe more. Let us know!
Links:
- v20-root.zip
- TWRP
- Terminal Emulator
- Newest SuperSU(SuperSU v2.78 SR5 or greater is needed)
-Stock LS997 rom. for Sprint users only. (Fix's numerous problems)
Pre-requisites:
- ADB and fastboot setup and Installed
- Terminal Emulator installed onto the phone.
- The above links downloaded and SuperSU placed on the SD Card.
Working Devices:
- Verizon (VS995)
- Sprint (LS997)
- ATT (H910)
- Korean(F800L)
Note: International Variants (E.g.H990DS) May get supported in the future, but are currently being worked on at the moment. If you attempt to use this method on Unsupported Devices(any V20 not listed in working devices) then you are in uncharted territory. It will almost definitely brick your device. YOU HAVE BEEN WARNED!!!!
This will tutorial will be broken up into 2 sections, during the second section the instructions will differ depending on the variant of the phone you are using.
- Unlocking the Bootloader:
1) Copy all the files from inside the "Required Files" (Inside the unzipped "v20-root" folder) and paste it into your active ADB directory. Then copy and paste twrp-3.0.2-1-us996.img to your active ADB directory.
2) If you currently don't have Terminal Emulator then go and download and install now.
3) Plug your device into the computer and verify ADB is working. Then;
On Windows, double-click "RUNMEFIRST.bat, DO NOT CLOSE THE LOG WINDOW THAT OPENS, then double-click "Step1.bat"
On Linux/MacOS ("#" Signifies a comment below)
Code:
./RUNMEFIRST.sh
# OR
bash ./RUNMEFIRST.sh
Open a Separate Terminal next to the RUNMEFIRST terminal, then type:
Code:
./Step1.sh
# OR
bash ./Step1.sh
When you run The sh or Bat files there will be a Permission denied error on 2 files: Flatland and Flatland64. This is normal and nothing to worry about.
3.5) Wait for a shell prompt, then type (or copy):
Code:
run-as con
chmod 0777 /storage/emulated/0/*
4) Open Up Terminal Emulator
Type:
Code:
id
Check if context is "Untrusted_app"
If "Untrusted_app" is displayed, Continue:
Type into Terminal Emulator:
Code:
applypatch /system/bin/atd /storage/emulated/0/dirtysanta
If it doesn't show up as "Untrusted_app", repeat the above steps from Number 1
5) Watch the RUNMEFIRST dialog for when it tells you to run Step2. Then;
On Windows, double-click "Step2.bat"
On Linux/MacOS, type:
Code:
./Step2.sh
# OR
Bash ./Step2.sh
Once step 2 is completed, you'll be in bootloader, procced to "Flashing TWRP" section to continue.
Note/Warning: Verizon Users Vibrator will be constantly going off, until the whole process is complete (Past Android Setup Wizard).
- Flashing TWRP and Fixing Varient Issues:
1) Run Step3, so TWRP can be flashed and a working boot.img flashed (Fix's screen problem) by;
On Windows, double-click "Step3.bat"
On Linux/MacOS, type:
Code:
./Step3.sh
# OR
Bash ./Step3.sh
******Sidenote******
If you get message saying <waiting for device> on Step3.bat then you do not have the fastboot drivers installed(you may have the program but not the drivers).
To fix: Go to your device manager while the device is connected in fasboot and right click the item that says Android and select update drivers. Then select from internet. and let it install the drivers then try step3.bat again.
*************
2) After you're rebooted, and back at the main lockscreen, type;
Code:
adb reboot recovery
Your device will reboot to an LG screen. Keep checking adb devices for your device.
Then type:
Code:
adb reboot recovery
***********
Device should display a red triangle and say corrupt, then it will boot into TWRP.
3)Once in TWRP, Press Cancel on the password prompt and then swipe to allow system modifications.
Note:If you wish to make a back up now, you MUST save it to your SD card, and you cannot backup the data partition.
After the backup is complete, return to the main menu and hit wipe then select ?Format Data?, and follow the instructions there.
4) Steps below will differ, depending on what model you have, choose the correct model and follow its method.
- Verizon(VS995) and ATT(H910):
4.1) Flash SuperSU.zip
4.2) Go back to Main-menu > Wipe > [Format Data] > Type ?Yes?
4.3) Go back to Wipe > Advanced > Check Dalvik, Data and Cache > Slide to wipe
4.4) Go back to Main-menu > Reboot > System
- Sprint(LS997):
4.1) Go to Wipe > Advanced > Check Dalvik, System, Data and Cache > Slide to wipe
4.2) Go back to Wipe > [Format Data] > Type ?Yes?
4.3) Go back to Main menu > Install > LS997 Stock Rom then Flash SuperSU.zip
4.4) Go back to Main-menu > Reboot > System(you will get static on boot. this is normal)
4.5) Sprint users are Done at this point. You do not need anything else. Everything will work except static on boot.​Note:Any following Instructions are for all devices again.
5) During reboot you will get a Red Triangle with a "!" inside, this is normal (First boot after flashing SuperSu will show the Red triangle twice.Wait for system to boot (this will take awhile). It may appear like the system has frozen but it has not. JUST WAIT!
*****VERIZON USERS******
It has come to my attention that some users have encountered abnormally long first boot time(over 20 minutes before first time setup)
To resolve this issue:
Boot into bootloader by pulling the battery and reinserting it and holding VOL- and phugging in the phone. then typing:
Code:
fastboot flash boot bootbackup.img
fastboot reboot
**************
*****ALL USERS*****
If you encounter a "Secure Boot" Password then booting the first time you did not Format data properly.
To reiterate: To properly decrypt the device you need to boot into TWRP and go to WIPE->FORMAT DATA and you will be prompted to type "yes" to format and decrypt.
**************
Once you are booted and have proceeded through the setup wizard, re-enable Android Debugging (ADB) if not already enabled.
Type:
Code:
adb reboot bootloader
6) Once inside bootloader, Type:
Code:
fastboot flash boot bootbackup.img
When it says finished, Type:
Code:
fastboot reboot
The device will boot back into system.
WARNING:This is a required step for non sprint users, it prevents background crashes and fix's battery drain. If you do NOT follow this then the device will have bad battery life, be laggy and crashes will occur regularly.
7) Once full booted back into android, Type;
Code:
adb reboot recovery
8) Once TWRP loads, Then;
- Flash SuperSU.zip
- Go back to Wipe > Advanced > Check Dalvik and Cache > Slide to wipe
- Go back to Main-menu > Reboot > System
You now should have a rooted LG v20, download your favorite root checker app and verify root.
Note:For a root app to work, it will have to support Systemless root.
Contributers/Developers:
@me2151(General)
@glitschi667(General)
@EMSpilot(Debug device) #3
@elliwigy(Ideas and testing) #5
@Matt07211(Formatting this awesome guide and helping out with general stuffs)#4
@1619415(Awesome Santa Pic at the top!)#8

Alright guys. Its time for some fixes!!!
For our known issues:
Comfort view, youtube, boot time and possibly radio.
All fixed by flashing the AT&T H918 Konverged Kernel.
Keep in mind this is a temporary fix until I get a full custom kernel made for our devices(or at least a way to make the screen work out of box that we can use on other kernel sources).
To use this kernel on our phones you need to download the zip, Place on sd card, reboot to twrp, install the zip, wipe dalvik/cache then reboot.
You WILL GET STATIC ON EVERY REBOOT!
After the phone is booted put the screen to sleep by pressing the power button and cover your proximity sensor(so your 2nd screen turns off) then turn your screen back on. Your screen will work until reboot. If you reboot you will have the static again. Just follow the steps I just listed above to get the screen working again.
--------
Other Updates.
I believe I have finally found a way to revert sprint devices sprint devices to unrooted stock. I will be testing the method on my phone in the next couple days.
WooHoo!!!! I bricked attempting to revert!
So heres an update for you guys. Reverting has been confirmed possible using KDZ files for your specific models. Confirmed working for KDZs are H915, VS995 and some others. I do Have a new v20. I am going to pull the stock sprint files tomorrow and see what I can do about making that work.

Nicely done Guys.
@me2151(General)
@glitschi667(General)
@elliwigy(Ideas and testing)
 @Matt07211(Formatting this awesome guide and helping out with general stuffs)
 @1619415(Awesome Santa Pic at the top!)
I am extremely happy that the V20 User Debug I invested in worked out!
Enjoy everyone!!
Cheers

Reserved

Reserved lol

Awesome work guys!
Sent from my LG-LS997 using Tapatalk

reserved
---------- Post added at 04:51 PM ---------- Previous post was at 04:51 PM ----------
pdaddy said:
Awesome work guys!
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
****

Good job @me2151 !!!:good::good::good:

Awesome! Now all the fun can begin!
Thanks for all your hard wprk on getting us root!
Thanks,
Chaz187
Sent from my LG-LS997 using Tapatalk

So awesome to hear, you guys are amazing. Its possible the dev with the h915 is waiting for the firmware update (we're told in time for the holidays?!) that would enable LTE on wind to see if this still applies. Nevertheless, thanks, i dont remember the last time i read so much. Lol
Sent from my LG-H915 using Tapatalk

Ooo Santa you so dirty.. Can't wait to do this
Sent from my VS995 using Tapatalk

SHABBA JOTS said:
So awesome to hear, you guys are amazing. Its possible the dev with the h915 is waiting for the firmware update (we're told in time for the holidays?!) that would enable LTE on wind to see if this still applies. Nevertheless, thanks, i dont remember the last time i read so much. Lol
Sent from my LG-H915 using Tapatalk
Click to expand...
Click to collapse
From the last I hear from him. The bootloader unlocks and twrp installs BUT he has no service(he is Rogers) So he is looking into all that.

AWESOME job, everyone! Thanks so much for this-- I admit I may wait a little while for feedback before trying my own unit, but given that I jumped on the V20 early in hopes that if any version is hacked it'll be the earliest firmwares, I can't imagine it'll be too long before I'm back to enjoying my phone the way I like it!
Definitely will be sending some coffee money along, even though I wasn't in any of the bounties...

Damn I've been waiting for this soooo much but there's only thing. I don't now crap about LG phones I've been a Sammy fanboy for 7 years lol. Guess I'll have to wait till my boy can do it.
Sent from my LG-LS997 using Tapatalk
---------- Post added at 08:13 PM ---------- Previous post was at 08:06 PM ----------
EMSpilot said:
Nicely done Guys.
@me2151(General)
@glitschi667(General)
@elliwigy(Ideas and testing)
I am extremely happy that the V20 User Debug I invested in worked out!
Enjoy everyone!!
Cheers
Click to expand...
Click to collapse
And thank you for purchasing that expensive out of pocket device.
Sent from my LG-LS997 using Tapatalk

Subutek said:
Damn I've been waiting for this soooo much but there's only thing. I don't now crap about LG phones I've been a Sammy fanboy for 7 years lol. Guess I'll have to wait till my boy can do it.
Sent from my LG-LS997 using Tapatalk
---------- Post added at 08:13 PM ---------- Previous post was at 08:06 PM ----------
And thank you for purchasing that expensive out of pocket device.
Click to expand...
Click to collapse
to be honest theres nothing really lg specific besides the files themselves lol.. of course you never use Odin outside of Samsung lol..
majority of it is pc bat or adb commands and then you got your typical twrp stuff but hey, best to have your buddy do it if youre not comfortable

Hey guys I need a little help, last step I was able to complete was running "Step3.sh, after reboot I'm unable to get into recovery mode. does anyone know the manual steps to get to recovery mode?
I also continue to get the popup "com.android.phone" has stopped.
No mobile service

hoopsdavis said:
Hey guys I need a little help, last step I was able to complete was running "Step3.sh, after reboot I'm unable to get into recovery mode. does anyone know the manual steps to get to recovery mode?
Click to expand...
Click to collapse
I'm assuming you're on Mac/Linux. If so, in terminal verify connection with "adb devices". If you're connected fine, enter "adb reboot recovery"

I started but wouldn't get any feedback when I would double RUNMEFIRST or Step 1.... I don't know if windows 10 matters.
I'll try again a little later tonight.
My device was connected and found; adb devices
oh yeah, im also running minimal adb and fastboot.
http://forum.xda-developers.com/showthread.php?t=2317790
Thank you guys for the hard work. So happy to have hotspot working.

dc.wash95 said:
I'm assuming you're on Mac/Linux. If so, in terminal verify connection with "adb devices". If you're connected fine, enter "adb reboot recovery"
Click to expand...
Click to collapse
I'm actually on windows

hoopsdavis said:
I'm actually on windows
Click to expand...
Click to collapse
Well in that case, you probably should have executed the ".bat" not the ".sh"
I'm running Windows 10, and successfully followed the guide. My device is past boot currently, and is installing apps from a Google backup.

Related

Fuhu Nabi2 Backup - Recovery - Root - Gapps on Ubuntu Linux

Here are the steps required to backup the Fuhu Nabi 2, install a custom recovery, root, and gapps using Ubuntu(12.10) Linux.
This also works on Windows(other than installing adb and fastboot) if you just remove the 'sudo' from the commands.
For a scripted Windows install, check out Nabi Lab: http://forum.xda-developers.com/showthread.php?p=36758895
Original root from jmztaylor, Includes the new gapps(t499user) and the new TWRP 2.3.3.0 from aicjofs(thanks!)
You should do all of the OTA updates before rooting(otherwise you might lose WiFi) When I posted this the latest version was 1.9.37. Settings>About Tablet>Update>Check Update
Download the needed files then extract all of the files to your home folder to begin. http://dl.dropbox.com/u/6529005/Fuh...Backup-Root-Recovery-Gapps 30December2012.zip
Open a terminal(ctrl+alt+t) and run the following command to install ADB and Fastboot (Universe).
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
On the device, enable USB debugging in Settings>Developer options, then connect USB cable.
Just in case the adb server is already running, lets kill it using:
Code:
adb kill-server
Now we will start the server and reboot the device:
Code:
sudo adb reboot-bootloader
Once the device has rebooted into the bootloader, we will flash the new recovery image using fastboot:
Code:
sudo fastboot flash recovery recovery.img
When fastboot is finished, boot the new recovery kernel on the Nabi2 by pressing vol+ then vol-(down to recovery) then vol+ to select.
{
"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"
}
We will push the follwing files to the device.
First we will push the Root file.
Code:
adb push root.zip /sdcard/root.zip
Now we will push the Google Apps File
Code:
adb push gapps.zip /sdcard/gapps.zip
This is the script that will backup then install Root and Google Apps onto the device.(you can also skip the script and do it manually if you like, but make sure you do a backup)
Code:
adb push backup-root-gapps.openrecoveryscript /cache/recovery/openrecoveryscript
Now we will reboot the device and let the script do it's thing.
Code:
adb reboot recovery
Once you log into your device, start up SuperSU to make sure that root 'sticks'.
Your Fuhu Nabi2 is now rooted, w/gapps, and a custom recovery, Now click on the "thanks" button
NOTE: The following is if you ever need to do an OTA update, which requires the original Nabi2 recovery.
Download the original Nabi2 recovery image to your home folder https://www.box.com/s/9ogqkk8uu71bqrnpz9w1
Reboot the device into the bootloader
Code:
sudo adb reboot-bootloader
Finally we will flash the original recovery image to the device
Code:
sudo fastboot flash recovery nabi2_original_recovery.img
Thank you very much! In about 10 minutes, everything was the way things should be! Specifically, a nicely rooted tablet so that my son could thoroughly his tablet! Now if I can get XBMC working properly, then life would be perfect! Thanks again!!!!
Fuhu Nabi2 Common issues and FAQ.
Glad it helped you out! It's a great little tablet.
To make Nabi2 more like a regular tablet now that you have Root and Google Play, you can prevent the tablet from starting Nabi Mode/Monarch UI by checking the box in Settings>Security>'Set Parent Mode as default mode'.
You can also remove the files in the /vendor/app/ folder if you want to free up some space. Just make sure to have 'Parent Mode as default mode' checked before you remove these files, or when you reboot the tablet it will give you a blank screen.
Code:
NvCPLSvc.apk, fuhu_AddApps.apk, fuhu_AppZone.apk, fuhu_Books.apk, fuhu_ChoreList.apk, fuhu_Crafts.apk, fuhu_Fan-a-tech.apk, fuhu_KidzMode.apk, fuhu_NabiCare.apk, fuhu_NabiCloud.apk, fuhu_NabiSpinletsPlusICS.apk, fuhu_NabiSpinletsPlusParentICS.apk, fuhu_NabiSync.apk, fuhu_OOBE.apk, fuhu_ParentalDashboard.apk, fuhu_SpinletPlusVideo.apk, fuhu_SwitchKids.apk, fuhu_TreasureBox.apk, fuhu_University.apk, fuhu_Videos.apk, fuhu_Web.apk, fuhu_nabiMD.apk
I used ES File Explorer to remove the files. First you have to go into the ES File Explorer settings and check all the boxes in 'Root Settings'. Alternatively you could use the file manager in the custom recovery we flashed in the first post or any other file manager with root capabilities.
If you need to get into fastboot or recovery manually, turn off the Nabi2 and then hold the vol+ and power button until the menu comes up. You use the vol- to navigate and the vol+ to select.
Nabi2 Teardown Thread: http://forum.xda-developers.com/showthread.php?t=2024105
Technical Specs for the Fuhu Nabi2
Display: 7-inch, Capacitive, Multi-Touch Display, 1024 x 600 Resolution
CPU: NVIDIA® Tegra® 3, Super 4-PLUS-1™ Quad Core with 5th Battery Saver Core
Storage: 8 GB, Expandable via MicroSD (Up to 32 GB); Plus 2 GB FREE Cloud Storage
Memory: 1GB RAM
Camera: 2MP Front Facing Camera; 720p Video
Battery: 3,850 mAh Rechargeable Lithium-ion Battery
Size & Weight: (with Drop-Safe Bumper) Width: 8.69 Inches (220.8 mm) Height: 6.05 Inches (153.7 mm) Depth: 1.14 Inches (29.08 mm)
Weight: 1.31 Pounds (596 g)
OS: Android 4.0, Ice Cream Sandwich
Network: Wi-Fi 802.11 b/g/n Bluetooth 3.0
Input / Output: Micro USB 2.0 Port, Mini HDMI MicroSD Compatible Cartridge Slot, 3.5 mm Standard Audio Jack, Built-In Microphone, DC Connector
Audio + Video Format:
Audio: MP3, AAC
Video: MPEG-4, H.263, H.264
Charger Output: 5vdc 2000mA
Charger Plug: 2.35mm OD and 0.7mm ID
Gmail App will force close if you don't have gmail checked in Settings>Accounts&Sync>Click on email>Checkmark Gmail.
Some games on the Fuhu Nabi2 use openfeint, to disable/block this you can install AdAway https://play.google.com/store/apps/details?id=org.adaway and add the following to the blacklist. This prevents the program from contacting the openfeint servers.
Code:
openfeint.com
api.openfeint.com
scoreloop.com
Some Games that use openfeint:
Code:
Fruit Ninja, Tiny Wings, The Moron Test, Robot Unicorn Attack, Championship Manager series, Bomberman Touch 2: Volcano Party, Fieldrunners, geoDefense, geoDefense Swarm, Minigore, Pocket God, Rollercoaster Rush, Jetpack Joyride
Here is a copy of the build.prop http://pastebin.com/5hCHd4bb
If you really, really messed up and have to restore the device back to stock because you didn't follow directions and lost wifi etc etc, I created a thread for restoring to factory from scratch. http://forum.xda-developers.com/showthread.php?p=35287470
ANDROID UPGRADING MESSAGE:
If you used a different gapps other than the one posted above or http://forum.xda-developers.com/showthread.php?t=2065878 you will probably get an "Android Upgrading" message every time you reboot. This is caused by two stray odex files that need to be removed/deleted. You can just install the new gapps package or take care of the files manually.
Code:
/system/apps/Gallery2.odex
/system/framework/com.google.widevine.software.drm.odex
Thanks for this man. The only thing I'd recommend is adding a piece, or a URL, on how to add the repo's for apt to pull those adb packages. These commands you step through are handy in *nix or Windows(-sudos). Thanks again!
Thanks, I didn't even notice that adb and fastboot were in the Universe repos as I had it enabled already.
I'll go double check then. I am running Ubuntu 13 off USB stick now and had enabled universe repo but maybe didn't get a clean update before checking for pkg. Will try again and see what's up...
I thought it required some custom repos, nothing preconfigured. If it is in universe my bad.
Thank you, for this thread was able to root daughter tablet with this tutorial. Tried the script in other thread but did not help. Thanks again
Sent from my NABI2-NV7A
Yup, its in universe, my bad.
Sent from my SPH-D700 using Tapatalk 2
Here is a quote from tikiral on installing ADB and Fastboot on Windows.
tikiral said:
Speaking of posts
@shizzy t499's post is really an excellent guide. The only thing you'd change if you're on Windows is that instead of doing the 'apt-get' you'll just download and install the SDK Tools from Google (http://dl.google.com/android/installer_r21.0.1-windows.exe) > Start up the SDK Manager.exe file from the install directory > Scroll to the very bottom > Check off Extras>Google USB Driver > Click Install packages...
After install, you should be able to go into Device Manager and update the driver's on any stray android devices and bam, you should be all set to go.
Thanks again for all the info @t499.
Click to expand...
Click to collapse
Finally got a chance to perform this on my Nabi 2. Installed with no problems what so ever and was quick too. I performed the install using Ubuntu 12.10. I found it much easier and less stressful this way. Now I have to do this to both my daughters Nabi 2 tablets.
I just finished up removing the Monarch UI apps for a normal tablet. Man I really love this tablet. I have almost all my G apps installed which I have been wanting for some time now.
Just follow the instructions to the letter and you can't go wrong with Linux. Now if we could get Jelly Bean on this it would be awesome! I posted a question about the Nabi XD in the Q&A and posted specs comparing both if anyone caught it. I am pretty sure it's possible if someone can get a hold of the XD and port it over.
Thanks again t499user and all the devs that worked to make this tablet usable.
Glad it worked for you! I would love to see some JB action on here.
Just wated to shout out and say thanks many texts were sent over getting my sons tablet rooted but we got it finally no thanks to WINDOWS, Linux is the way to go! Thank you so much for the support and late night time spent working on this! :good::victory:
Hi,
Thanks so much for your new gapp package, got it working great now. Can I check if I install the default nabi recovery image again will I loose access to google play store...?
caughron01 said:
Just wated to shout out and say thanks many texts were sent over getting my sons tablet rooted but we got it finally no thanks to WINDOWS, Linux is the way to go! Thank you so much for the support and late night time spent working on this! :good::victory:
Click to expand...
Click to collapse
I am so glad that we got it working, after switching to Linux it was pretty easy eh
dave2986 said:
Hi,
Thanks so much for your new gapp package, got it working great now. Can I check if I install the default nabi recovery image again will I loose access to google play store...?
Click to expand...
Click to collapse
The default recovery would only be needed if you have to apply a new OTA update. Other than that, I would just leave the TWRP recovery, but it has no effect on the play store.
t499user;36219934
The default recovery would only be needed if you have to apply a new OTA update. Other than that said:
I have to say, that I have never been able to reflash the stock recovery after I first flashed TWRP. Every time I tried, all I got was the defective kernelpanic-Android lying on his back and I had to reflash TWRP via fastboot. So far I installed all updates from zip-files via TWRP. However, every update resulted in a defective recovery and after every update I had to reflash TWRP.
If you know that, it takes very little time but I wonder what might have gone wrong in the first place....
If some of you could spread some light, please feel free!
Cheers
DiePlage
BTW: I've tried the stock recovery from this thread http://forum.xda-developers.com/showthread.php?t=2041224
Click to expand...
Click to collapse
DiePlage said:
I have to say, that I have never been able to reflash the stock recovery after I first flashed TWRP. Every time I tried, all I got was the defective kernelpanic-Android lying on his back and I had to reflash TWRP via fastboot. So far I installed all updates from zip-files via TWRP. However, every update resulted in a defective recovery and after every update I had to reflash TWRP.
If you know that, it takes very little time but I wonder what might have gone wrong in the first place....
If some of you could spread some light, please feel free!
Cheers
DiePlage
BTW: I've tried the stock recovery from this thread http://forum.xda-developers.com/showthread.php?t=2041224
Click to expand...
Click to collapse
Have you tried to restore the unrooted stock backup that was made in the beginning of jmz rootpackage, if you didn't make 1 or use it. There are some stock posted. Unrar and put in TWRP/BACKUPS/your number folders and restore from TWRP recovery RESTORE. I have and was completely back to stock.
You can find stock in jmz files but it is any older version. Look thru the many post tho and others have posted stock 1.9.37
http://forum.xda-developers.com/showthread.php?t=1905674
ALD3 said:
Have you tried to restore the unrooted stock backup that was made in the beginning of jmz rootpackage, I have and was completely back to stock.l]
Click to expand...
Click to collapse
I have tried to just flash the stock recovery. I thought this should be enough to do OTAs. Maybe I could find another stock recovery besides the one noted...
DiePlage said:
I have tried to just flash the stock recovery. I thought this should be enough to do OTAs. Maybe I could find another stock recovery besides the one noted...
Click to expand...
Click to collapse
Forgot that I had 1 downloaded already. Try this 1 from my Box. Stock 1.9.37
https://www.box.com/shared/but3ihiutkw62pa4gayd
DiePlage said:
Android lying on his back and I had to reflash TWRP via fastboot.
Click to expand...
Click to collapse
That is the stock recovery, it will happen that way if you don't install root.zip, and possibly after an update.
To get to the menu of the stock recovery, after getting to android laying down, you push the vol buttons.
Really hoping someone can help me. Im trying to Root the Nabi 2 on my Mac. Im following the command lines, without the "sudo" text, and when i flash the recovery, my terminal says waiting for device, and nothing happens.
i know my adb is working, bc it detects the Nabi 2 when i run the ADB devices command, and it will reboot into the bootloader.
Any suggestions??
Edit
Found this link, and all worked out. Didn't have to root, or flash recovery or anything like that, but i only really need youtube as of right now, so it worked well for me
http://everythingnabi.blogspot.ca/2012/08/googlie-booglie.html

[ Q&A Troubleshooting ] Dirty Unicorns 4.4.4 [Falcon]

[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
.

[TOOL] Lx Multi Tool v1.3.2 [WIN/LIN/MAC][Unlock/Recovery/Stock/Kernel/More]

{
"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.

TWRP-3.4.0.0 for Ulefone Armor X5 (aka Bretzel)

{
"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"
}
TWRP FOR Ulefone Armor X5​DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
INSTALLATION
- Go to developer settings and turn on OEM unlock
- Power off the phone and boot to fastboot mode (power and volume +)
- Open a comand prompt and type:
Code:
fastboot flashing unlock
All the data will be loss
- Confirm the oem unlock by pressing the volume + button
- And now type:
Code:
fastboot reboot
- When the phone is turned on, and you complete the setup wizard, type:
Code:
adb reboot bootloader
- When fastboot mode appears in a corner of the phone, type the following command:
Code:
fastboot flash recovery recovery.img
- Now Boot into TWRP, and format data, and reboot to system
If you wanna root it:
- When you are at TWRP and you have formatted data, flash Magisk by sideload
- And reboot to system
Sources:
Device Tree
Download:
TWRP v1
TWRP v2
TWRP v3
Thanks to [Alphabetical Order]:
* Hadenix
* Maanush
* R0rt1z2
* SebaUbuntu
Just a note: This is NOT for the newer mt6765 Android 10 Q phone, If your fone is android 10 Q it will NOT work.
Pachacouti said:
Just a note: This is NOT for the newer mt6765 Android 10 Q phone, If your fone is android 10 Q it will NOT work.
Click to expand...
Click to collapse
Hi
How are you?
My variant is MT6763 one, if you want open pm and we will work for make TWRP for MT6765 variant.
Thanks!
A Only
Thanks dude, but my phone is an 'A' only partition, and as far as I'm aware, only johnwu's phone has actually been done, his being 'A' Only... He made a magisk for his 'A' only phone, but it dont work on mine. To see my firmware, just look at the ulefone stock firmware for android 10_Q, you'll find all you need there... ? It's an armour x5, aarch64, meaning 64bit only I think...
Tried everything I know of, and I do know a bit so not shy in testing any files, I am a competant programmer electronics style, flashing chips etc, so no prob re-flashing errors etc
Edit google johnwu 'A' only and you'll see why its not been done yet... whoever does it will create root for what is coming for all fones...!
X5 pro variant
FYI, this method isn't working on Ulefone Armor x5 Pro variant. (MT6765 - Android 10) Dont know why, but it causes bootlop. Reflashing stock boot img restores the phone functionality (without TWRP obviously). As i'm a new user, i can't post the link to the stock Boot and Recovery images, but if anyone needs them for porting, feel free to PM me.
It wont work because android 9 is the old version of 64bit capable of running 32bit apps, android 10 is pure x64bit. The bootloader is NOT the bootloader anymore, but a preloader, loading BEFORE the bootloader. so flashing bootloader over preloader causes bootloop, makes sense dunnit?
All fones will soon adopt this, and it has already started, since johnwu was bought by apple, and will be made too busy to produce anything anymore, by design of course, and since this new version of a only partitioning has been succesfull in thwarting him, no more root for you. Now you get another file system running on top of your unrootable fone to make you think you have root, pretty much sums it up, this overlayfs...
Shows how good the devs really are nowadays, when nomoretech (hovatek) found out his work dont work on android 10, he ignored my thread, too busy with old android 9 for old fones. upgrade, update, move on, say 'tata root'....
thanks good job on android 9
jmpf_bmx said:
TWRP FOR Ulefone Armor X5​DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
INSTALLATION
- Go to developer settings and turn on OEM unlock
- Power off the phone and boot to fastboot mode (power and volume +)
- Open a comand prompt and type:
Code:
fastboot flashing unlock
All the data will be loss
- Confirm the oem unlock by pressing the volume + button
- And now type:
Code:
fastboot reboot
- When the phone is turned on, and you complete the setup wizard, type:
Code:
adb reboot bootloader
- When fastboot mode appears in a corner of the phone, type the following command:
Code:
fastboot flash recovery recovery.img
- Now Boot into TWRP, and format data, and reboot to system
If you wanna root it:
- When you are at TWRP and you have formatted data, flash Magisk by sideload
- And reboot to system
Sources:
Device Tree
Download:
https://github.com/jmpfbmx/android_...eleases/download/twrp_bretzel_v1/recovery.img
Thanks to [Alphabetical Order]:
* Hadenix
* Maanush
* R0rt1z2
* SebaUbuntu
Click to expand...
Click to collapse
Hi,
We try to install it on a Armor X5 with android 9, build Armor_X5_MH1_EEA_V01 and all we have is a green line in the top of the screen then the phone reboot...
Is it many hardwares for the same phone ?
Thank you
wargreen said:
Hi,
We try to install it on a Armor X5 with android 9, build Armor_X5_MH1_EEA_V01 and all we have is a green line in the top of the screen then the phone reboot...
Is it many hardwares for the same phone ?
Thank you
Click to expand...
Click to collapse
Hi,
Can you share a pic of the screen?
Can you try to use adb? (Try adb shell, if works make this, adb shell cat /tmp/recovery.log, and send me the file by here)
Thanks
Regards
Jose
Tomorrow you will have a huge update of TWRP and some news about A11 hehe
"- Now Boot into TWRP, and format data, and reboot to system"
Could you explain exactly How to do this, please
bootloader activated, do I hard reboot pressing power and vol+, and when do I stop pressing ?
thanks
ulysse
"- Now Boot into TWRP, and format data, and reboot to system"
Could you please explain exactly how to do this ?
Bootloader activated, Do I press power and vol+ and keep then pressed ? until what ?
thanks a lot
ulysse
ulysse_21 said:
"- Now Boot into TWRP, and format data, and reboot to system"
Could you explain exactly How to do this, please
bootloader activated, do I hard reboot pressing power and vol+, and when do I stop pressing ?
thanks
ulysse
Click to expand...
Click to collapse
Hi
How are you?
Have you got Bootloader unlocked? (Idk wdym with bootloader activated)
For do that you just need to flash TWRP, reboot phone pressing vol+ and power as you say and when TWRP boots, just go to Wipe -> Format Data (Type yes) and then when the format data has finished, clic on reboot to system
TWRP Updated!
Now MTP and ADB are working better!!
thanks, i try
ulysse
jmpf_bmx said:
- When the phone is turned on, and you complete the setup wizard, type:
Click to expand...
Click to collapse
I start in Engish , skip connect to mobile network (no sim), skip WI-Fi, adjust good date and time, without "use location" and without "send usage and diagnostic data"; acept; "not now" for "protect your phone"
Then I activate the developper mode and in "system/ options for developers" I turn on USB debogage.
Did i miss sommething at this stage ?
jmpf_bmx said:
Can you try to use adb? (Try adb shell, if works make this, adb shell cat /tmp/recovery.log, and send me the file by here)
Click to expand...
Click to collapse
Hello thanks for your help.
Phone powered on, I can go on "Armor_X5:/ $ " if I type "adb shell".
but I don't understand "adb shell cat /tmp/recovery.log,"
I have "cat: tmp/recovery.log: No such file or directory"
appologize for my low level in English and in computering, I write code more on ImageJ and Rstudio.
ulysse_21 said:
I start in Engish , skip connect to mobile network (no sim), skip WI-Fi, adjust good date and time, without "use location" and without "send usage and diagnostic data"; acept; "not now" for "protect your phone"
Then I activate the developper mode and in "system/ options for developers" I turn on USB debogage.
Did i miss sommething at this stage ?
Click to expand...
Click to collapse
Did you opened bootloader?
ulysse_21 said:
Hello thanks for your help.
Phone powered on, I can go on "Armor_X5:/ $ " if I type "adb shell".
but I don't understand "adb shell cat /tmp/recovery.log,"
I have "cat: tmp/recovery.log: No such file or directory"
appologize for my low level in English and in computering, I write code more on ImageJ and Rstudio.
Click to expand...
Click to collapse
I guess that you aren't at recovery, or you didn't disable and enable MTP
Pachacouti said:
Just a note: This is NOT for the newer mt6765 Android 10 Q phone, If your fone is android 10 Q it will NOT work.
Click to expand...
Click to collapse
It works in mt6762 Android 10 version? model Armor_X5_Q_EEA

[GUIDE] Rooting the Moann inkPalm 5

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

Categories

Resources