Related
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
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!
Hi all, i passed trough the bad experience of a phone with a broken screen, all my data was trapped inside the device and i couldn't see nothing on the screen :crying:
So i decided to develop a little app, in order to be able to break into my phone again and save the more stuff i could.
Gstreamer (aka Ghost streamer) is able to let you see your device screen once again (that was the primary purpose...) and deal with it by clicking and swiping with your mousepointer on your phone screen picture (yes, it's slow but it gets the job done )but without the need to install softwares like VNC and similars (Gstreamer only allows you to gain access your files in a way or another and try to save it),.
If your dead phone was rooted and with a custom recovery, then yur life will be easy in case of broken screen , but if not , then the music changes a lot, that's why i thought my software could help other people to solve theproblems i meet during my data rescue attempts.
No matter the device screensize, it will adapt to your device screensize and will make your life easier if you broken your phone screen.
I'm still adding features to it, and planning to organize it in a better way, correcting some bugs, testing it on different phones and android versions,but it's actually working and improving day by day
if someone is interested in testing it with me, and report then the experience i'd be happy to cooperate.
at the moment this is the pre-alpha stage for me , but this is how it looks now
{
"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"
}
if you are having bad times with your phone screen this may help you :fingers-crossed: just contact me if interested
use at your own risk it's still experimental, download it from the link below
http://www.filedropper.com/gstreamerv1000release
open for feature requests here , if you want me to add special functions, just ask here and i will see if it can be embedded or not.
get the latest nightly build on my git, just click on the "Download ZIP" button. (link below)
any advice is appreciated, thank you.
changelog!
new release, now the Apk operations are ok , now you can list, uninstall, pull, install apk from your PC.
always get the latest release from my git
https://github.com/TheBrainBooster/Gstreamer/archive/master.zip
BrainBooster said:
open for feature requests here , if you want me to add special functions, just ask here and i will see if it can be embedded or not.
get the latest nightly build here https://github.com/TheBrainBooster/Gstreamer just click on the "Download ZIP" button.
any advice is appreciated, thank you.
changelog!
new release, now the Apk operations are ok , now you can list, uninstall, pull, install apk from your PC.
always get the latest release from my git
https://github.com/TheBrainBooster/Gstreamer/archive/master.zip
Click to expand...
Click to collapse
new changelog! V1.2.1.0 release
added dpad navigation buttons
minor bugfixes
redesigned main panel
new changelog! V1.2.2 is available for the download
added swipe buttons
added memory info
minor bugfixex
check it out and let me know testers are welcome
01/02/2016
new changelog!
minur bug fixes
added file push , pull and sideload functions
...sadly i don't have feedback so i can't be sure it will work with all the android versions
...many changes heve been done, stay tuned for the next release
Hello,
tried you app, but it does not recognize my phone, because it has not debugging mode activated. I tried even "RSA ADB key inejection and..." but with no luck. For anther device, which has debugging mode active, I was able to get its data, but for the one with broken display and no debugging mode, it doesn't.
Any hints?
Regards,
can you provide some more informations about your device?
maybe you could try to repeat the procedure but in recovery mode
Hello,
Thanks for your time. So far you're the only one who gave me something as an information, or tip/hint.
My phone is an Samsung i9300i, with stock rom, only recently when trying to get the data through ADB, I have installed via ODIN an image named "CWM Recovery v6.0.3.6.tar", but still no effect in ADB.
Before replying to you I have tried recovery mode as well (power button, home, volume - and after 5 seconds volume up- as those were the steps required for my model to get into download mode). But I cannot get your up to recognize my phone. I tried with another one (HTC One M8s), with debugging mode on and the app recognize it in a flash. But with the broken one, no luck.
Are there necessary some custom drivers? Do you think some print screens could help?
a screenshot could help for sure
installing the proper adb drivers too, try with this --> http://forum.xda-developers.com/showpost.php?p=50008343&postcount=486
also installing the official kies software by samsung may help
whas the phone rooted?
can it boot normally?
do you see something on the screen?
what is the damage on you phone?
android version?
Hello and good morning (for me it's still morning),
No, the phone was not rooted, was "untouched". I gave up the idea I can retrieve data via software and I was thinking to try to open it and have a display temporary put, but it's time consuming and I'm short on time to recover the data (some business information for my boss).
I'll try the drivers you have wrote and I'll came back with screen shots as well.
Regards,
sorry for the late post edit, but it came to my mind after i wrote
by the way... are you sure you booted into recovery mode?
my software shoud see the phone anyway when you hit the test conection button
Hello and good morning (for me it's still morning),
No, the phone was not rooted, was "untouched". I gave up the idea I can retrieve data via software and I was thinking to try to open it and have a display temporary put, but it's time consuming and I'm short on time to recover the data (some business information for my boss).
I'll try the drivers you have wrote and I'll came back with screen shots as well.
LE: Yes, I'm booting in download/recovery mode (combination of pow+volume minus + home buttons and volume up after 5 -7 seconds - steps specific for Sam i9300i phones)
Regards,
miborion said:
Hello and good morning (for me it's still morning),
No, the phone was not rooted, was "untouched". I gave up the idea I can retrieve data via software and I was thinking to try to open it and have a display temporary put, but it's time consuming and I'm short on time to recover the data (some business information for my boss).
I'll try the drivers you have wrote and I'll came back with screen shots as well.
LE: Yes, I'm booting in download/recovery mode (combination of pow+volume minus + home buttons and volume up after 5 -7 seconds - steps specific for Sam i9300i phones)
Regards,
Click to expand...
Click to collapse
so you shoud see the phone connected maybe it will say: device-12345abcdefyourphoneID-(recovery) but if you have the drivers installed it should appear in the log window, moreover you said maybe you have a CWM recovery installed...
remember to reboot your pc ater the drivers setup
BrainBooster said:
so you shoud see the phone connected maybe it will say: device-12345abcdefyourphoneID-(recovery) but if you have the drivers installed it should appear in the log window, moreover you said maybe you have a CWM recovery installed...
remember to reboot your pc ater the drivers setup
Click to expand...
Click to collapse
Indeed I have had installed CWM (if by that you are referring to "CWM Recovery v6.0.3.6.tar" file - which I did, using ODIN (v.307)), as I thought the debugging mode would be activated, but it seem it doesn't. Please can you give me more details about what did you want to say by " moreover you said maybe you have a CWM recovery installed..."? Is it a bad thing? Should I flash to a stock rom?
And no, it does not show any devices like device-1234afsadsasdasd.
Regards,
what i mean is, if you installed a custom recovery and you also have your phone drivers properly installed you should have an adbd server running on the phone(provided by the custom recovery environment) and an adb client running on the pc, so they should see each other
BrainBooster said:
what i mean is, if you installed a custom recovery and you also have your phone drivers properly installed you should have an adbd server running on the phone(provided by the custom recovery environment) and an adb client running on the pc, so they should see each other
Click to expand...
Click to collapse
Ok, now I understand what is the purpose for that img.
So, bottom line is I cannot seem to install proper drivers. I'll try different combinations of uninstall plus install drivers from your link (i had used the ones from Samsung site, released this year), plus computer reboot, as so far I wasn't able to have ADB listener list my device (or your application).
Regards,
Root it! everything will be much more easy
http://androidmtk.com/root-samsung-galaxy-s3-neo-gt-i9300i
BrainBooster said:
Root it! everything will be much more easy
http://androidmtk.com/root-samsung-galaxy-s3-neo-gt-i9300i
Click to expand...
Click to collapse
I'll try, but, I'm not able to check what is my build number. As far as I know, I have only the stock image (exactly as the phone came with) and am sure it hasn't have the 4.4.4 version, but something like 4.3 something...I have a colleague, back at work which has some same device (Sam I9300i) and I could check the version on that terminal and try my luck.
Thanks again for your time and insight
miborion said:
I'll try, but, I'm not able to check what is my build number. As far as I know, I have only the stock image (exactly as the phone came with) and am sure it hasn't have the 4.4.4 version, but something like 4.3 something...I have a colleague, back at work which has some same device (Sam I9300i) and I could check the version on that terminal and try my luck.
Thanks again for your time and insight
Click to expand...
Click to collapse
anytime
if you need further help , just ask
BrainBooster said:
anytime
if you need further help , just ask
Click to expand...
Click to collapse
Hello,
I've just finished all leads meaning I have successfully rooted the phone by using your link; I got PASS message in ODIN using the exact image as the tutorial indicated. But, still I cannot connect to the phone with ADB, or by using your app.
If I boot normally I can hear the sound, see the top buttons lid and have the popup message in windows which tells me I can browse the mobile phone's content (onStdBoot.jpg).
If I boot in recovery mode (can see COM0 used in ODIN and can flash successfully) I get the devices on the second print screen (BootInDownloadMode.jpg) but cannot access it.
Could you please advise if there is anything else I can try?
Regards,
if you successfully rooted your device, booting it in recovery mode should make it show in my software
{
"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.
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