Database Info

[PC-UTIL] [Discontinued] [Source Opened] Android RTL Auto-Patcher + ProTools (v.1.5)

Discontinuation Notice + Source Opened!
This project is now discontinued, as I have moved on to Android 4.X (ICS) which has perfect built-in RTL support.
I will still provide basic support as much as I can, but if your device has it, I recommend you move on to ICS as well.
If you wish to continue working on this project and improving, you have my blessing (as long as you credit me, of course).
Source code is available here, but be-ware: it's an undocumented, unorganized mess.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Android RTL Auto-Patcher
Version 1.5
The Problem
It's a well known fact that while Android has Hebrew and Arabic fonts, it has a problem with Right-To-Left alignment. The problem: It doesn't exist.
Sure, MOST programs display text correctly, but mix text and numbers in the same line and you'll get reverse numbers (123 appears as 321), and in SOME Google apps (like Gmail and Maps) the words themselves are reverse (so 'apple' appears as 'elppa').
The Old Solution
There is a solution for this, however you have to create a separate patch for every build, because the patch changes files in the build's framework. It's a relatively easy process, but for people who change builds constantly, it can get tiresome.
This Program
This program detects if a build is compatible with the patch, and if so - creates it almost automatically and install it back to the phone. A process that took about 10 minutes to complete before and required some knowhow, now takes only seconds and requires almost no prior experience!
{
"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"
}
ProTools
The ProTools are a collection of tools that will allow you to patch ROMs manually either directly to ZIP files, to the phone, or to framework files. It will also allow you to push, pull, extract and manipulate files to and from ROMs of all kinds, with great flexibility and ease!
​​
Compatibility
This program is intended for use with custom DEODEXED roms of Android versions 2.1 and above. The program will inform you if your build is not deodexed.
The program will allow you to either push the fix directly to the device or flash via recovery.
WARNING: Some 'squashedFS' builds have been reported not to be compatible, and the program can not - at the moment - detect those!
Warnings
This program is in Beta stage!
Many features have not been thoroughly tested and error handling is far from perfect.
It may give some errors, crash or stall - at which point I ask that you please send me your log.txt (to find it, click 'About' and then 'Locate Log') or as an upload in this thread.
I do request - however - that you try to be as specific as possible regarding your build, your computer, and what caused the problem.
Also, if you include the log here, please enclose it in 'code' tags.
Requirements
You MUST have Microsoft .Net Framework 4 installed for this to work.
You will also need the latest Java Runtime Environment
You must also have the ADB drivers already installed:
In Windows Vista/7, just connect the phone and let Windows Update do it's thing.
In Windows XP, you need to manually install the drivers available here.
ADB itself comes with the program, so you don't need that.
How to use
If available, boot into recovery (recommended for non-rooted devices!)
Connect your phone to USB and make sure the computer recognizes it
Run the program, and select 'Test Connection'
After connection has been made, if the build is compatible - select the correct Sense version. The program WILL attempt to auto-detect, but it's not 100% reliable, so please confirm that the program detected correctly
Select distribution method:
Push to Device (Recommended) - does simply that, the program will attempt to automatically patch the phone for you.
Create ZIP - creates a ZIP file that's flashable through Recovery (Clockwork Recovery Mod). Will also offer you to save the ZIP on the SD card (doesn't even require mounting USB).
Show File - will just show you the patched 'framework.jar' so you can do whatever you want with it.
Select any additional options you might be interested in (Gingerbread keyboard, for example - is a fixed Gingerbread keyboard with fixed Hebrew RTL that is compatible with the patch the program installs. It should work on 2.2 devices as well, and replaces the stock Android keyboard).
GO GO GO!
Reporting bugs
Please be sure to provide the name and type of your build when giving feedback or reporting bugs. For better bug-squashing, please also provide your log.txt file, which you will find in the application's directory.
Also, even if you experienced no bugs, your logs will be appreciated.
Finally, if you put the the log content in your post, PLEASE encode it with 'code' tags.​
If you have any additional non-bug-related questions, feel free to ask them in this thread. I will do my best to improve this program as time goes by.
Thank you, and good luck!
Download
Always available here:

Changelog, Known Issues and Planned Features
Changelog
1.5 - 14/08/2011
Advanced build numbers to 1.5 due to massive advances in the program.
Added global error handling - might not solve ALL problems, but will hopefully help avoid unlogged crashes.
When "Install Gingerbread Keyboard" and "Create Zip" are both selected, it will now also install the keyboard on the Zip.
The program will now also try to mount sd-ext in addition to system before patching (as will the flashable Zip).
When patching fails, the program will offer you to save the patched file to your computer for use with ProTools.
In the 'About' window, added the option to find the log file on your computer (for easier error reports).
Other minor undocumented improvements.
Completely overhauled the ProTools:
Offline Patching: Allows patching ROM Zips or 'framework.jar' files directly.
Manual Operations: Pretty much what ProTools was before, except with an easier straight-forward interface and with the option to operate on a ROM Zip file, from your phone, or directly from a 'framework.jar' file.
Added the option to manually push or pull anything to or from anywhere (with specific buttons for 'framework.jar', 'framework-res.apk' (for theming) and 'build.prop'.
Added the option to manually patch the Keyboard to the phone or the a ROM Zip.
1.1.2 - 20/07/2011 - minor update
Improved Sense 3.0 Detection
Updated build detection strings
1.1.0 - 14/06/2011
Fixed critical interface bug that caused the operation compelte / restart prompt not to appear if 'Push' was selected.
1.1.0 - 14/06/2011
Removed support for SD/SDRAM based builds
Instead, created three distribution methods: Push file, Create flashable zip or just Display file
Flashable zip will be flashable via recovery, and will attempt to push itself to the device's SD card.
Version 1.0.0 Beta
Build Detection:
Improved build properties detection
Vastly improved Sense detection mechanism
Sense versions now distinct by Sense version
Added Sense 2.1 (Gingerbread) support
'Pro Tools' (Beta) - Every single function of the patcher can now be called on seperately and manually.
Changed versioning scheme. Version 1.0.0 to be assigned.
Updated core framework files (fixed a lot of stability issues in Sense2.0 builds)
Planned Features
I plan to seriously improve the RTL fix itself in the near future, but since I lack the knowledge to do so myself, I'm waiting for some new methods currently under development by the excellent devs at iAndroid.co.il to be released.
I do plan to release to program's source code eventually, it's just such a mess at this point that I'm more ashamed of it than anything else.
I also plan to include a logcat monitor. Because the patch causes the phone to rebuild dalvik cache, first boot after patching often takes a VERY LONG time, and some users wrongfully assume their phone is frozen. I plan to include a logcat monitor that will hopefully know to differentiate between bootloops, errors, and dalvik rebuilding, so users can tell if their phone is actually frozen or just working. If this works, I might release this as an actual separate program.
Known Issues
Build 1.1.0 - If 'Push' is selected, when patching process finishes, no message is displayed and the program doesn't prompt to restart. - fixed in 1.1.1
There is hardly any error handling in the ProTools section. If they are called with no device available, it MAY freeze/crash the program. Will be fixed in upcoming release.
Fixes for Squashed filesystem roms do not work! Mostly.
Error handling is STILL utter ****e, may give unexpected errors (or not at all and just fail altogether).
If HTC Sync is installed and active, stuff may go nuts all around (as of 0.0.5 this is detected by the program and warns user).
Credits
Program and Graphics created by Elad Avron using Visual Studio 2010 Express.
ZIP Functions created by Elad Avron using free libraries from the IC#Code group, available at http://www.icsharpcode.net/opensource/sharpziplib/
Special thanks:
From HTCAddicts.com: Ronenpg, Ohect.
From XDA-Developers.com: TheAgent1982, silverbluem, mdeejay and the entire HD2 dev crew
From iAndroid.co.il: Classicaldude (Original fix, the hero of RTL!), Dudyk (Original fix), rasmux (Modified fix), Liavk1 (partial SenseHD fix), Avicohh (Gingerbread Keyboard), N1Man (RTL fix for Gingerbread Keyboard).
Keyboard fix by Avicohh and N1Man (from iAndoird.co.il)​

If it will work man i'll give you a real big THANKS!

Just tried it V 001 , successfully connected + fetched framework+modified then pushed classes back....
log attached
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Device restarted, passed the first splash (hTC) screen, took very long on the animation one, then started !
Changes :
1-No right side line alignement..
2-Numbers are still wrongly placed..

Tested and it workes!
Got an error in middle of the prosses but in the end it did what it was supposed to do.
Sent from my HTC HD2 using XDA App

congratulation
Congratz of your new Project!
I will give it a shot as soon as i can

my teset here ..
this is my test in the log file attached
thx

I appreciate your efforts
reverse numbers problem still exits
big thanks

Voffchik said:
Tested and it workes!
Got an error in middle of the prosses but in the end it did what it was supposed to do.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Thanks
Can you send me your log.txt?
I'd like to see what the error was.

Sup3r said:
I appreciate your efforts
reverse numbers problem still exits
big thanks
Click to expand...
Click to collapse
Can I get build type and log file please?
Thank you
jaguaralani said:
Just tried it V 001 , successfully connected + fetched framework+modified then pushed classes back....
log attached
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Device restarted, passed the first splash (hTC) screen, took very long on the animation one, then started !
Changes :
1-No right side line alignement..
2-Numbers are still wrongly placed..
Click to expand...
Click to collapse
The log indicates that you did everything right and experienced no errors, so there are two things I'd like you to try:
In the 'Toolbox' dir in the app dir, the leftover files from the creation process are left. Try pushing framework.jar manually to the device.
If that doesn't work, try putting 'classes_new.dex' in 'framework.jar', renaming it to 'classes.dex' (thus replacing the old one), and repeat step 1.
If that doesn't work something went wrong in the patching process itself, i.e. my source files aren't good for your build (they should be), the compression failed, or any step in between. Let me know if the leftover framework.jar and classes_new.dex solve the problem, and we'll try to isolate the problem from there.
Thank you all for helping

Thank you
Thank you very much for your great work.

The alignment works great for Arabic, but the thing with Arabic is that letters need to be connected with each other when they are in one word. From what I gather, this means needing to change stuff in libskia.so and libwebcore.so (both in /system/lib/).
For more info, you can check out the efforts to add Arabic support for many Android devices at http://ardoid.com/

NSider said:
The alignment works great for Arabic, but the thing with Arabic is that letters need to be connected with each other when they are in one word. From what I gather, this means needing to change stuff in libskia.so and libwebcore.so (both in /system/lib/).
For more info, you can check out the efforts to add Arabic support for many Android devices at http://ardoid.com/
Click to expand...
Click to collapse
Yes, I understand it's a problem with a lot of software, not only Android.
I will try to implement patching of Arabic characters in the future, once the program has a more solid base.

this is my log
my build is : MDJ's gingerbread CyanogenMod 7 v. 2.1 [A2SD+][GRH78][RMNET][Kernel: MDJ S10.2 OC
wating the Arabic characters fix
thanks :0

Ambious said:
Thanks
Can you send me your log.txt?
I'd like to see what the error was.
Click to expand...
Click to collapse
I sent it yesterday via PM
I sent the log file + screenshot
U said u'll look in to it
Sent from my HTC HD2 using XDA App

Voffchik said:
I sent it yesterday via PM
I sent the log file + screenshot
U said u'll look in to it
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Right, sorry, my bad
I worked around your reported error in v.0.0.2, it was a little oversight I had in interface design.
Thank you for the report
Sent from my Android HTC HD2 using XDA App

Sup3r said:
my build is : MDJ's gingerbread CyanogenMod 7 v. 2.1 [A2SD+][GRH78][RMNET][Kernel: MDJ S10.2 OC
wating the Arabic characters fix
thanks :0
Click to expand...
Click to collapse
Thank you for the log.
From the log it seems like there were no errors and that everything went as planned. I'm using the same build as you, so I know it's compatible.
What I'd like you to try, if it's not too much hassle, is this:
In the 'toolbox' dir in the app dir, there are leftover files from the process. Push 'frameowkr.jar' to your device's "/system/framework/" using:
Code:
adb push framework.jar /system/framework/
and reboot.
If that solves it, the issue was with the push command (I currently have no method to actually detect if it was successful or not, I hope to fix that in future version).
If even that doesn't solve it, open 'framework.jar' using any zip/rar program, delete 'classes.dex' from it, insert 'classes_new.dex' (from the toolbox dir) into the 'framework.jar' file, and rename to 'classes.dex'. Push to the device, restart, and try again.
If you don't mind doing those things, it would help me greatly to detect where the patching process failed.
Thank you so much, and I promise to include Arabic fix as soon as the program structure is solid enough!

Tried V 002
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Log attached
changes
Nothing

jaguaralani said:
Tried V 002
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Log attached
changes
Nothing
Click to expand...
Click to collapse
Yeah, well, v002 changes nothing in the process, only the interface.
I'd like you to try, if not too much hassle - to push the framework file manually and reboot.
If that doesn't work, try to put 'classes_new.dex' into 'framework.jar' and rename it to 'classes.dex' and push framework.jar again.
If any of that works then I can narrow down the issue.
On another note, I got reports from other people using DesireZ that the process worked for them, so I know it's compatible, it's just a localized issue.

This doesn't specifically belong to NAND development.
Moved.
(Regardless of that, it's a wonderful project).

[ROM][Gingerbread] Kustom Ginger v5 for Nextbook Premium 7

RETIRED: Since I no longer own this device I am unable to update/maintain this any further! Furthermore it was only designed to support certain models that are no longer sold so to answer all questions NO it won't work on the new ones. As of Dec 20th, 2014 all downloads have been removed (Sorry for the inconvenience)
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Rooted and Google Apps enabled rom for late generation Nextbook Premium 7 tablets. Now based on the recently released ota that runs faster and enables setup wizard support.
Screenshots
{
"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"
}
Setup Wizard
Homescreen
Notifications
Apps
Storage
Accounts & Sync
About
Play Store
Network Location
Supported
Any Nextbook Premium 7 in the YF1011XXXXX serial number Series (May work on newer models)
Download
Discontinued (Sorry for the inconvenience)
Extra Apps
None currenty
Features
Rooted (su,Superuser,Busybox), Google Apps (Including setup wizard), Custom boot animation, Google Calendar, Google Play Store, Zeam as launcher, most of the default apps removed,Titanium Backup, Quick Sync Settings (allows access to accounts and sync), OI File Manager, and 1gb userdata partition
Install/Upgrade
Download and extract the folder fromKustom-Ginger_n7p-v5.zip to any folder of your choice
Reboot device using paper clip then quickly press and hold reset until you get black screen with usb plugged in
When windows wants driver give it the respective folder for your os (32bit or 64bit) from Drivers folder
Run RK29update.exe if status bar on bottom reads Found RKAndroid rock usb you are good but if it shows
No Found RKAndroid rock usb repeat steps 2-3
Leave the default selected items if you are doing fresh install or just select Boot,Kernel,and System if it is upgrade
f you are doing fresh install Select Loader and Click EraseIDB after it finishes then click Run otherwise JUST do Run
if you are upgrading
If there was no errors your device now is on my Kustom-Ginger_n7p-v5 rom
WARNING: Installing this will remove all your data & apps if you select more than Boot,Kernel,and System!!!
Factory Restore
Reboot device using paper clip then quickly press and hold reset until you get black screen with usb plugged in
When windows wants driver give it the respective folder for your os (32bit or 64bit) from Drivers folder
Run RK29update.exe if status bar on bottom reads Found RKAndroid rock usb you are good but if it shows
No Found RKAndroid rock usb repeat steps 1-3
Select Loader and Click EraseIDB after it finishes then click Run
If there was no errors your device now is on stock v2.0.30 rom
WARNING: Restoring factory default will remove all your data & apps!!!
Version History
v1 ~ Inital fully rooted ext3 read/write /system build, Updated to latest* Google Play Store
v2 ~ Fully deodexed, Latest* Google Play Store, Latest* Gmail, Latest* Titanium Backup, Removed rom built in flash!
v3 - v4 ~ Unreleased builds
v5 ~ Rebased from recent ota (version v2.0.30), discontinued cramfs version
Credit
Google: For their work on Android and the related apps
ChainsDD: Superuser/SU
Michael Bentz: Zeam Launcher
CyanogenMod: disclaimer
Titanium Track: Titanium Backup
Shantanu Goel: Quick Sync Settings
finlessbob: 1gb userdata partition
OpenIntents: OI File Manager
wendal: ext3 system
Notes
All builds from now on are ext3 only.
Key
* ~ Latest as of the time of post
! ~ Removed due to future of flash for android (and rom version was majorly out of date)

another rom for my np7.... awesome ill try it soon and get back to you
is your rom ro or rw as well?

demkantor said:
another rom for my np7.... awesome ill try it soon and get back to you
is your rom ro or rw as well?
Click to expand...
Click to collapse
Sadly only RO like the rest... as far as i know there is no proven method to gain on the fly write access.

Again thanks for all the hard work. I have a few requests. first since we cant change the Adhoc ( using wifi from another android device) on the fly with out RW access can you please add the ability to connect to adhoc wifi in the next build? Also i love google currents app but we cant use is on our device because we don't have map's installed. can that be added as well?

fireproof34 said:
Again thanks for all the hard work. I have a few requests. first since we cant change the Adhoc ( using wifi from another android device) on the fly with out RW access can you please add the ability to connect to adhoc wifi in the next build? Also i love google currents app but we cant use is on our device because we don't have map's installed. can that be added as well?
Click to expand...
Click to collapse
Will need to look into the adhoc wifi thing... but Google Currents is now attached to first post .

kibmcz said:
Will need to look into the adhoc wifi thing... but Google Currents is now attached to first post .
Click to expand...
Click to collapse
Sorry I didn't explain well enough. Maps and Google framework have to be installed with the rom for currents to install. If you try to install currents currently it fails.
Sent from my NXM726HN using XDA App

fireproof34 said:
Sorry I didn't explain well enough. Maps and Google framework have to be installed with the rom for currents to install. If you try to install currents currently it fails.
Sent from my NXM726HN using XDA App
Click to expand...
Click to collapse
I installed currents via adb to my next7p without maps installed and it it worked properly.

kibmcz said:
I installed currents via adb to my next7p without maps installed and it it worked properly.
Click to expand...
Click to collapse
O my bad I didn't relize I had to install I through adb. Ill give that a shot. Thsnks!
Sent from my NXM726HN using XDA App

kibmcz said:
I installed currents via adb to my next7p without maps installed and it it worked properly.
Click to expand...
Click to collapse
Flashed the latest rom and was ableto get current s to run! Thanks for that ! The one thing I am see ing thogh is Google framework keeps wanting to force close every half hour or so. With that it seems auto sync is not syncing (Gmail). Any one else seeing this? Any one flashed a rom this the wpa-suplicant file changed so we can connect to ad hockey WiFi networks?
Sent from my NXM726HN using XDA App
Sent from my NXM726HN using XDA App

Syncs to gmail just fine. Every network i have saved is found as soon as i enter that house or business. Wifi and syn are perfect. Havent tried to tether my phone yet (no need) but i will try it out and let you know if i can get it to work. (Not one forced close)
Sent from my NXM726HN using XDA App

demkantor said:
Syncs to gmail just fine. Every network i have saved is found as soon as i enter that house or business. Wifi and syn are perfect. Havent tried to tether my phone yet (no need) but i will try it out and let you know if i can get it to work. (Not one forced close)
Sent from my NXM726HN using XDA App
Click to expand...
Click to collapse
Figured out the sync problem was just a WiFi power setting . Set it to not turn off when the screen goes off and it seems to be working perfect now . Tether is the only thing missing now .and I'm sure that will be solved soon . Thanks for all the work .
Sent from my NXM726HN using XDA App

fireproof34 said:
Figured out the sync problem was just a WiFi power setting . Set it to not turn off when the screen goes off and it seems to be working perfect now . Tether is the only thing missing now .and I'm sure that will be solved soon . Thanks for all the work .
Sent from my NXM726HN using XDA App
Click to expand...
Click to collapse
The ability to connected to phone tether works on any tether app (including official built into android) app that uses access point mode (Tested and working when connected to my ICS powered nexus s tether).
If i knew what was needed to enable/test adhoc mode i could look into adding it.
Also i really should look into updating the build.prop to have more cleaner names LOL (eg Nextbook Premium 7 instead of NXM726HN).

kibmcz said:
The ability to connected to phone tether works on any tether app (including official built into android) app that uses access point mode (Tested and working when connected to my ICS powered nexus s tether).
If i knew what was needed to enable/test adhoc mode i could look into adding it.
Also i really should look into updating the build.prop to have more cleaner names LOL (eg Nextbook Premium 7 instead of NXM726HN).
Click to expand...
Click to collapse
ro.product.model or Ro.Product.name look like the ones that would need changed in Build Prop i like Next7p.(That's whats on the back as Model NO. but its your rom so you do what you like.)
Here is the link to the instruction on how to make this work on a "rooted' tab. http://androidtablethacks.com/android-tablet-hacks/how-to-enable-adhoc-wifi-on-android-tablets/
Here are the instructions as well.
For those of you who want to connect/tether your Android tablet to your Adhoc Wifi such as your smartphone, you can do it by enabling Adhoc on your tablet device.
In this example, I will use my Galaxy Tab 10.1 but should work on any Android tablet device.
Step 1. Download adhoctablets.zip and unzip to the root folder of your hard disk such as c:\adhoctablets.
Step 2. Put your Android tablet into USB Debugging Mode by going to Settings->Applications->Development.
Step 3. Open up a command prompt by typing “cmd” under Start->Search for Windows or open up a shell in Linux or Mac.
Step 4. Browse to the directory you unzipped adhoctablets.zip. For Windows, type:
cd \adhoctablets
Then type this to enter shell:
adb shell
For Linux:
adb-linux shell
For Mac:
adb-mac shell
Then type:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cp /system/bin/wpa_supplicant /sdcard/wpa_supplicant.original
cp /sdcard/wpa_supplicant /system/bin/.
chmod 755 /system/bin/wpa_supplicant
chown system.wifi /data/misc/wifi/wpa_supplicant.conf
exit
Reboot your tablet and you should now be able to connect to Adhoc wireless devices.
If something goes wrong, you can get back into adb shell and type the following to revert:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/wpa_supplicant.original /system/bin/.
chmod 755 /system/bin/wpa_supplicant
chown system.wifi /data/misc/wifi/wpa_supplicant.conf
exit

Hey....nice rom man, thanks alot! if you want to get adhoc working you will need to add/modify wpa_supplicant. i tether with a hot spot so no problems but i used to tether with ad hoc on my a100. thanks again!

but no one has made a rom for the np7 that is writable... so it wont work

demkantor said:
but no one has made a rom for the np7 that is writable... so it wont work
Click to expand...
Click to collapse
There was some experimental write support by the creator of the unpacking/packing tool but its either hacky (earlier one) or risky (newest one).
In theroy if the adhoc stuff is integrated at rom level it should work.

demkantor said:
but no one has made a rom for the np7 that is writable... so it wont work
Click to expand...
Click to collapse
That is the point. That's why I have asked him to cook it in to the rom.

fireproof34 said:
That is the point. That's why I have asked him to cook it in to the rom.
Click to expand...
Click to collapse
In looking at the other post the supplicant config may be a issue with the read only file system.
Ill dig up one of my old zydas wifi b usb sticks/old xp machine and so some testing.
Sent from my Kustom Ginger powered Nextbook Premium 7

FYI
Originally Posted by Dochoppy
OK HEADS UP! Watch the first post for changes.
1st off. With the new Rom You will need to learn how to put your tablet into flash mode.
I will be posting 2 Roms from here on out.
1 will be based off of the existing cramfs.system file Rom.
2 Rom will be based off of COMPLETELY ROOTED Rom with ext3 file system.
So All in All, With help from Finless Bob! (Great guy!) I figured out what the issue was I was having. Finless Is also going to be creating a Rom for this tablet. Both Finless's Rooted Rom and Mine will have to be flashed the same way! Stay Tuned for an update.
But here is just a taste.
891MB of internal storage free with all apps that are currently loaded in the Cramfs version of the Rom. Fully RW System. Stay Tuned!
http://http://www.freaktab.com/forum.php

fireproof34 said:
FYI
Originally Posted by Dochoppy
OK HEADS UP! Watch the first post for changes.
1st off. With the new Rom You will need to learn how to put your tablet into flash mode.
I will be posting 2 Roms from here on out.
1 will be based off of the existing cramfs.system file Rom.
2 Rom will be based off of COMPLETELY ROOTED Rom with ext3 file system.
So All in All, With help from Finless Bob! (Great guy!) I figured out what the issue was I was having. Finless Is also going to be creating a Rom for this tablet. Both Finless's Rooted Rom and Mine will have to be flashed the same way! Stay Tuned for an update.
But here is just a taste.
891MB of internal storage free with all apps that are currently loaded in the Cramfs version of the Rom. Fully RW System. Stay Tuned!
http://http://www.freaktab.com/forum.php
Click to expand...
Click to collapse
I know of the ext3 method it is using... wendel (creator of the tool that was used to make all the custom roms for this device) posted it up on slatedroid a while back but no tool to automate it. Early results were hit and miss but im sure its been stabilzed.
It consists of 3 tasks:
1. Flashing ext3 enabled bootloader (usually handled by the upadate image)
2. Modifying the ramdisk in boot.img to mount system as ext3 (handled by rom maker)
3. Converting system.img to ext3 (handled by rom maker)
That being said 1 is a unknown risk and 2 & 3 due to my distance from linux for years are not really easy but im getting a friend to help.
Thats all for now
Sent from my Kustom Ginger powered Nextbook Premium 7

[Cube U9GT2/Window N90/Visture V2/Easypad 970] Guides & Tips

This thread is for guides and tips related to Cube U9GT2, Window N90, Visture V2, and Easypad 970.
Questions: For further questions some very nice threads already exist in: XDA (EN), SlateDroid (EN), Chinamobiles (DE), 4PDA (RU), and Moage (CN).
Everyone is welcome to post here their own guides/tips, even when already similar topics exist. Unfortunately often guides and tips vanish in endless thread pages. Here is a suitable place to bundle all these in one place together and link them in needed user posts.
Guides & Tips - How to:
01. Use the storage of my device (#2)
02. Root (#3)
03. Flash a Firmware (#4)
04. Use Moage's ROMs (#5)
05. Make Gameloft Games visible/installable (#6)
06. Use 3G (#32 by Darkjesus)
07. Stabilize my WiFi (#34)
08. Use Ad-hoc WiFi (extLink.01; extLink.02 + special wpa_supplicant)
09. Customize ROMs (extLink.01 + extLink.02)
10. Use a different charger (extLink)
11. Fix the "Google Play Store" (extLink)
12. Use CIFS (extLink)
13. Improve speaker quality + volume (#35)
14. Install GApps correctly (#36)
15. Do Screenshots in ICS without root (#37)
16. Tweak build.prop (extLink)
17. Unpack an IMG
18. Open the Tablet
19. Make Bluetooth working

(01) How to: Use the storage of my device
1. Turn tablet (on), and switch debugging (off)
-> 2.3.1 Settings/Applications/Development -> USB-debugging
-> 4.0.3 Settings/Developer options -> USB-debugging
2. Connect device with PC (Win7) and use tablet's upper microUSB port (not OTG)
3. Windows will now try to install drivers, this will last ~20sec, mostly Win7 will succeed
-> if not then download "RK2918-USB-Drivers" and direct Win7 to those drivers; sometimes it will happen that windows cannot handle Intel drivers -> then choose AMD drivers
-> the result should be, e.g.:
{
"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"
}

(2) How to: Root
I. Preparation, "ADB Driver" installation:
1. Turn tablet (on), and switch debugging (on)
-> 2.3.1 Settings/Applications/Development -> USB-debugging
-> 4.0.3 Settings/Developer options -> USB-debugging
2. Connect device with PC (Win7) and use tablet's upper microUSB port (not OTG).
3. Windows will now try to install drivers, but Win7 will not succeed - if already drivers are installed (yellow triangle) remove them completely.
4. Open device manager (start/control panel/device manager) and click on your tablet-device name (e.g. Cube) and choose "update driver".
5. Now select: Browse my Computer -> Let me pick -> All Devices -> Have Disk.
6. Download and unzip "ADB-Drivers" then navigate (see step 5.) to "android_winusb.inf"; next: choose "Android ADB Interface". ADB Drivers will now be installed.
II. Root
1. Download suitable root software:
a) 2.3.1: GingerBreak-v1.20.apk, SuperOneClick 1.7,
b) 4.0.3: SuperOneClick 2.3.1.0 (changed CN), SuperOneClick 2.3.3 (Changed by Verdeler).
2. Start GingerBreak.apk on tablet or SuperOneClick.exe on PC (run as administrator).
3. Click "root" within SuperOneClick -> done.

(03) How to: Flash a Firmware
I. Preparation
1. Choose and download an IMG (Firmware):
a) StockROM: Cube U9GT 2, Window N90, Visture V2, Easypad 970.
b) CustomROM: XDA (wackym), SlateDroid (s1eepy), SlateDroid (db260179), Moage (磨叽哥), FlashMyAndroid (prox32).
2. If necessary download "RKBatchTool".
3. Extra Driver shouldn't be needed, Win7 will recognize the device -> therefore don't install manually ADB-, or USB-Driver.
4. Charge Tablet to >70%
II. Flash
1. Turn tablet (off) and disconnect every cable and charger.
2. Start on PC "RKBatchTool.exe" and choose under the item "FW Path" an IMG (see I. Preparation).
3. Now press Volume (-) on tablet -> keep pressing and connect at the same time the tablet (upper microUSB port, not OTG) with PC -> as soon as you hear the PC is successfully connected or you see in RKBatchTool under "Connected Devices" a green light, then you can stop pressing Volume (-) and the tablet should be recognized from "RKBatchTool".
4. Click in RKBatchTool "Restore" (not Upgrade) and the flash process should begin; the first-time boot will last longer than normally - you can close RKBatchTool and disconnect the USB cable as soon as the tablet is booted.
good luck

(04) How to: Use Moage's ROMs
I. Preparation:
1. Download Moage's ROM and unzip: Link
2. Charge Tablet to >70%
3. Switch tablet (off) and disconnect every cable and charger
II. Flash Moage's ROM:
1. Moage's FlashTools:
a) Moage 4.3.5: Open "MoageRomFlash.exe" and choose how much space for applications you would like to have, don't get confused from chinese you will nevertheless see numbers those are important -> click the number you like most, after this the "MoageRKtool.exe" will start automatically
b) Moage x.x.x: when there is no "MoageRomFlash.exe" then start "MoageRKtool.exe" and go on with step 2.
2. Now press Volume (-) on tablet -> keep pressing and connect at the same time the tablet (upper microUSB port, not OTG) with PC -> as soon as you hear the PC is successfully connected or you see in MoageRKtool "Found RKAndroid...", then you can stop pressing Volume (-) and the tablet should be recognized from "RKBatchTool".
3. In "MoageRKtool" select all items except "Backup" and manually link to those files
=> then click at first "EraseIDB" (red circle), after that: click "Run"(blue circle) -> even when it is in chinese the buttons order will be the same.
4. Wait until the device is booted, then remove USB cable and close FlashTools.
Done.
Extra-Feature:
=> If your tablet wont boot anymore, and you don't want to lose your data and settings, then do this to fix the boot problem:
1. Start "MoageRKtool.exe" and select: "Loader", "Parameter", "Boot" and "System"
2. Click "Run" (don't click EraseIDB). Now it will replace just some important system files and the rest will remain.

(05) How to: Make Gameloft Games visible/installable
Two ways:
1. Modify manually "build.prop" /System (source):
=> you need to change 3 things:
ro.product.model=GT-P1000
ro.product.device=GT-P1000
ro.product.manufacturer=samsung
2. Exchange the build.prop:
=> download an already modified "build.prop", e.g. source; then rename in "build.prop" and exchange the original "build.prop" in "/System" at tablet -> before that it would be wise to backup the original file
Hint: after changing or switching build.prop clear data from "Google Service Framework" and "Google Play Storage" then reboot
The result will be:
Extra Information: Optimizing build.prop

superb!!! Million Thanks..
Now i can try on moage rom now..

Waiting for the next tutorials!!!
Superb!

dozz01 said:
I. Preparation
1. Firmware download:
a) StockROM: Cube U9GT 2, Window N90, Visture V2, Easypad 970,
b) CustomROM: XDA (wackym), SlateDroid (s1eepy), SlateDroid (db260179), Moage (磨叽哥).
2. If necessary download "RKBatchTool".
3. Extra Driver shouldn't be needed, Win7 will recognize the device -> therefore don't install manually ADB-, or USB-Driver.
II. Flash
1. Switch tablet (off) and disconnect every cable and charger.
2. Start on PC "RKBatchTool.exe" and choose under the item "FW Path" an IMG (see I. Preparation).
3. Now press Volume (-) on tablet -> keep pressing and connect at the same time the tablet (upper microUSB port, not OTG) with PC -> as soon as you hear the PC is successfully connected or you see in RKBatchTool under "Connected Devices" a green light, then you can stop pressing Volume (-) and the tablet should be recognized from "RKBatchTool".
4. Click in RKBatchTool "Restore" (not Upgrade) and flashing should start; the first-time boot will last longer than normally - you can close RKBatchTool and disconnect the USB cable as soon as the tablet is booted.
good luck
Click to expand...
Click to collapse
What is the reason for using the restore button rather than the upgrade
Button?
I have used the upgrade on two firmwares
Thank you

dmagee said:
What is the reason for using the restore button rather than the upgrade Button?
I have used the upgrade on two firmwares
Click to expand...
Click to collapse
Me too. Used upgrade button in RKBatchTool v1.3 and v1.4 without any problems.

druelf said:
Me too. Used upgrade button in RKBatchTool v1.3 and v1.4 without any problems.
Click to expand...
Click to collapse
Also in the original firmware install guide for the cube it states to use the upgrade button to flash firmware?
Sent from my SK17i using Tapatalk

dmagee said:
What is the reason for using the restore button rather than the upgrade
Button?
I have used the upgrade on two firmwares
Thank you
Click to expand...
Click to collapse
Upgrade only install the firmware, restore delete the last version and install the new.
Restore is a better option.

Thank you for that
Sent from my SK17i using Tapatalk

This thread is super helpful. I have an oem u9gt2 on the way and was looking for a straightforward guide. Kinda curious what rom everyone is running?
From reading around the net it seems wackym's is popular as well as Visture android 2.3 stock rom.

bytemuncher said:
This thread is super helpful. I have an oem u9gt2 on the way and was looking for a straightforward guide. Kinda curious what rom everyone is running?
From reading around the net it seems wackym's is popular as well as Visture android 2.3 stock rom.
Click to expand...
Click to collapse
I have tried the stock v1.5 gingerbread with the Honeycomb ui from the Cube website and found it very fast and stable, also tried the Wackym v1.08 Ics and found that excellent, not quite as nippy but still excellent, I changed the built in Ics launcher for Apex launcher on the market and this improved the speed of the functionality, really well with tons of options!. Unfortunately on the Wackym firmware the flash is flaky with things like iPlayer etc but that is not down to him, as flash on Ics is not officially supported even if on the market the latest version states support for Android 4 devices. I am sure this will be fixed in the coming months though.
Wackym firmware
http://forum.xda-developers.com/showthread.php?t=1420553
Stock firmware Ics and Gingerbread
http://www.51cube.com/tools.asp
Hope this helps
Sent from my SK17i using Tapatalk

dmagee said:
What is the reason for using the restore button rather than the upgrade Button? I have used the upgrade on two firmwares. Thank You
Click to expand...
Click to collapse
The "upgrade" button works just sometimes, e.g. if you upgrade from one Easypad ROM to another. But if you switch to a different ROM, then the "upgrade" button often doesn't work anymore. With "restore" you have a clean flash procedure. It can also be useful, for new devices or after flashing a new ROM, to do a "factory data reset" (in 2.3.1 under settings/private; 4.0.3 settings/Backup&reset). This will sometimes stabilize the firmware and prevent unexpected failures or bugs.

dmagee said:
I have tried the stock v1.5 gingerbread with the Honeycomb ui from the Cube website and found it very fast and stable, also tried the Wackym v1.08 Ics and found that excellent, not quite as nippy but still excellent, I changed the built in Ics launcher for Apex launcher on the market and this improved the speed of the functionality, really well with tons of options!.
Click to expand...
Click to collapse
Hi, thanks for your reply. I am downloading this one "U9GT 2固件V1.05（安卓2.3系统固件）" from cube's website. I assume this is the gingerbread version you were referring to.
The honeycomb ui is included in the rom or is that something you added? Apologies if it's a stupid question as this will be my first android tablet.
Seems a few people are sticking with gingerbread until the bugs are worked out of ICS. I recall reading that someone thought graphics looked clearer or sharper with ICS on the u9gt2...wondering if this was just the user's imagination or if there is some logic behind this.

Yes that 's the Gingerbread version and the honeycomb ui is built in, however I have installed Go Launcher Ex on the Gingerbread Rom makes it really quick. That replaces the honeycomb launcher but you still get all the other honeycomb parts like the bottom taskbar etc. Try it you won't regret it. As for the graphics looking better under Ics maybe the menus look clearer etc due to the new fonts but that is about it. The excellent IPs screen makes is look superb on Gingerbread and Ics.
Sent from my SK17i using Tapatalk

Hi,
Please provide a link to download MoageRKtool.exe.
Thanks

the Moage tools are included in Moages ROMs - maybe they are also to big for uploading here

[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3

15 seconds ADB Installer v1.4.3
ADB, Fastboot and Drivers
{
"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"
}
​What is this?
This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in early 2013. I saw another ADB installer on XDA, but it wasn't good enough for me so i'm finaly posting it here. It's very small and fast installer for tools and drivers.
Features:
Small - 9.18 MB
Fast - 15 seconds install (many times its even less)
AIO - ADB, Fastboot and also Drivers
Easy to install - just run it and program will guide you
Clean - ADB and Google Drivers from latest SDK
Install process:
1. Run it (Require administrator privileges)
2. Press Y/Yes to install ADB and Fastboot or N/No to skip
3. Press Y/Yes to install ADB system-wide or N/No for current user only
4. Press Y/Yes to install Drivers or N/No to skip
5. Continue Driver installation
6. 15 seconds passed - finished!
Notes:
System-wide: ADB and Fastboot are installed to %SystemDrive%\adb directory, and added system-wide path.
Current user only: ADB and Fastboot are installed to %UserProfile%\adb directory, and added path for current user.
CMD can use ADB and Fastboot from any directory.
Drivers are installed to system - no need to install them from directories.
Installer automaticly decides if install 32-bit or 64-bit drivers.
If anybody got problem with detecting device, go see picture guide View attachment howto_driver.zip
If installation fails, then post here contents of "adb-installer.log" from desktop. (if there is any)
If you have problem with driver enumeration in Windows 8.1 install update KB2917929
If you have older Google USB Driver installed, please uninstall it from Control Panel before installing new
If you have previously installed it as system-wide and now you want it current user only (or vice-versa), it won't remove it, you must do it yourself. (at least for now)
Mod edit
In this post it was brought to my attention that this installer installs a very outdated version of ADB and its related tools.
It's highly recommended you use the latest version from this XDA Portal post instead, as it fixes issues with newer devices.
If you wish to proceed, that is of course okay as this installer arguably provides an easier way to get going with ADB for some people, but do know that it's currently very outdated.
Downloads: Version 1.4.3
XDA Mirror added by Mod @Redline
Downloads: Version 1.4.2
Google Drive
Userscloud
Zippyshare
Dropbox
Version 1.3 (If upper one doesn't work)
Google Drive
If you like my work, want to support development and have few coins spare:
Video tutorials: (thanks goes to savadam)
Used tools:
BRAIN, 7-Zip, Notepad++, WDK, ResourceHacker, UPX, Android SDK, and maybe something else
Click to expand...
Click to collapse

Changelog
Changelog​​
Next version (WIP)
I will completely rewrite the project and make 2 versions, offline and online one.
Can also download latest files.
Will be open-source, code hosted on GitHub.
Version 1.4.3
- Updated adb and fastboot to API 23 version (Android 6.0)
Version 1.4.2
- Updated adb and fastboot to API 21 version (Android 5.0)
Version 1.4.1
- Fixed bug refusing to set %PATH%
Version 1.4
- Fixed %PATH% for Windows XP (SETX missing)
- Updated Google USB Driver to version 11.0.0000.00000
- Errorlog
- Cleanup
Version 1.3
- Now use 7-Zip SFX (instead of WinRAR)
- Add choice for "system-wide" or "current user only" installation of adb
- Newer DPInst (WDK 8.1)
- Reduced size
- Fixed bug
Version 1.2
- Update only files that need to be updated
- Add to PATH only when its not already present (prevent having it twice or more)
- Updated Google USB Driver to version 9.0.0000.00000
- 2KB bigger
Version 1.1
- Added Y/N option for installations (you can choose what to install)
- Changed installation directory to "%SystemDrive%\adb" and added PATH
- Will also remove adb from WINDIR if you still have it here
- Changed x86/x64 detection system
- Faster
- 0.01MB smaller than previous version
Version 1.0
- Initial release​.

Nice! Thank you. Will give this a shot. My adb/fastboot quit working when I moved and I cannot get it uninstalled or reinstalled for some reason. Have even tried other one click packages and still no go. Will try tonight. Does this need internet connection to install proper drivers, or are they packaged?
Edit: I just looked at the driver pics and it appears they're local. Great! Thank you.
Sent from my EVO 4G LTE using XDA Premium 4 mobile app

scottspa74 said:
Nice! Thank you. Will give this a shot. My adb/fastboot quit working when I moved and I cannot get it uninstalled or reinstalled for some reason. Have even tried other one click packages and still no go. Will try tonight. Does this need internet connection to install proper drivers, or are they packaged?
Edit: I just looked at the driver pics and it appears they're local. Great! Thank you.
Sent from my EVO 4G LTE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is WinRAR SFX archive that will start batch script, adb is copied using xcopy and drivers are installed using DPInst - Driver Package Installer from Windows Driver Kit, whole thing is extracted to temp directory and deleted after completition.
And yes, no internet conection is required.
How much did installation took ?

thank you snoop05, the installation on win 8.1pro x64 only took about 10 seconds at most, and adb commands are working great. yet to try fastboot.

Just saw this in the XDA Portal. Congratulations. I'm downloading now and about to try this out. My Nexus 5 is a pain to transfer files and get the correct drivers to do so. Thank You.

ADB installer.
Thank you for the application!
Will this work on the Moto-G and X variants as well?
I hope it will, as my wife is getting me a new phone, and the 'G' is the model she also wants.
I will try it on the 'G' once I get it in my hands, if nobody else has tried by that time (Jan. 22-ish), I will report my progress here.
Thanks again!

working on Windows 8.1 x64 with my new Moto G
great stuff

Wow. Finally ADB and fastboot are working on my Win8.1 x64 machine. You are awesome!

Nice script. Any reason for installing into %windir% instead of your own folder, then modifying PATH (either per-user or system wide)?

Just saw this on portal and wanted to tell you that you are the man!!!! Thanks for this

thak you so much for this awesome tool

Installed under 15 seconds running window 8.0. Thanks.

Great app. Nice that adds path to %windir%, Thx

Fantastic! Thank you so much for building and sharing.
Sent from my EVO 4G LTE using XDA Premium 4 mobile app

@Snoop05
On behalf of all the guys that spend all day in the Q&A section explaining how to install ADB and Fastboot, and what users did wrong, I thank you for this simple installer. We salute you

@Snoop05 , this is great! people now how no excuse to ask how to install adb..
may you add autokilling the adb daemon after not executing a command after a minute or so?

Thanks

it took exactly 71 seconds bro !

Super stuff newly installed windows and this tool comes out. Thanks! :victory:

[TOOL] AAFC ADB Fastboot Commander - Cross Platform - 0.8.5b (28-06-18)

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!