New Thread
http://forum.xda-developers.com/showthread.php?p=23899619
[--Changelog On New Thread--]
why not make it over wifi, would be handy for me as i always misplace my usb cable. or you could develop an apk which does something similar if it has root access
Omg when are going to stop making cool stuff?
Sent from my mini pro running froyocomb by d4
New version, now shows bootanimation preview
Danm....another little thing that make many ppl happy
Devs always make things easier for us... Thx bro
Uploaded a new version, 3.1, bug fixes and Now Show FULL bootanimation, not only the loop part
EDIT: Uploaded 3.11 , now preview resizes to bootanimation size (tested with LDPI, MDPI & HDPI)
Will this work with tablets?
Is it working with Galaxy S on stock ROM...?
do i need rooted phone for it ........?
dont work on my system... no bootanimation will start after coping a "bootanimation.zip" to bootanimation-folder. Nothing starts if i press on the bootanimation what will show up in the list.
Win7 / 64Bit (Service Pack 1)
vroshan96 said:
do i need rooted phone for it ........?
Click to expand...
Click to collapse
You need to root your phone to replace the boot animation anyway, so yes.
dRaCID01 said:
dont work on my system... no bootanimation will start after coping a "bootanimation.zip" to bootanimation-folder. Nothing starts if i press on the bootanimation what will show up in the list.
Win7 / 64Bit (Service Pack 1)
Click to expand...
Click to collapse
Same here... No boot animation.. Updated Java because at first it would not run at all. Win7/64bit SP1.
Update* It will let me backup but not sure if I should try to push lol. On NS4G just playing around.
Last update lol* Ok just did the backup boot then pushed another boot and then pushed backup back and it works! BUT will tinker with program more. Just trying to find a way for preview to work now.
1. Preview doesn't work for 11th Doctor TARDIS bootani: http://forum.xda-developers.com/showthread.php?t=1115717
2. Fails to back up current bootani, "Some Error, occurred!"
Haven't tried pushing new bootani. WinVista 64-bit SP2, Java 6 update 24 (both 32 and 64-bit). HTC EVO 4G, 2.3.3, Sense, not rooted.
bhaelochon said:
1. Preview doesn't work for 11th Doctor TARDIS bootani: http://forum.xda-developers.com/showthread.php?t=1115717
2. Fails to back up current bootani, "Some Error, occurred!"
Haven't tried pushing new bootani. WinVista 64-bit SP2, Java 6 update 24 (both 32 and 64-bit). HTC EVO 4G, 2.3.3, Sense, not rooted.
Click to expand...
Click to collapse
you need to be rooted
The Program will not open for some reason.
I have windows 7
I have ADB
Have JAVA
but when i extract the application on to my desktop and run as an admin it will not open the program and sometimes when i open it it says the program may not have been installed correctly other times it just won't open.
am i doing something wrong?
rooted my Samsung Galaxy mini (s5570) last night. connected phone via USB, extracted Bootanimation Installer to desktop, ran as admin. Put an animation I got into Bootanimations folder, selected it and pressed Push Selected Bootanimation. But it's still not changed. It shows the operator logo at startup and usual other things. Also, when I try to backup current bootanimation, it says something went wrong. Any suggestions?
EDIT : forgot to mention that it didn't restart phone either
not working?
program not working? i tryed putting it on my desktop and the sdk folder and still coudnt preview, backup or push animations, i could however reset my phone tho a more in depth turtorial would b nice.
using windows 7 x64
Rooted HTC Inspire with Kingdom Rom.
Does it have the option to add your own boot image? like a .gif
Verified it works flawlessly on the Moto Xoom.
Related
We've updated a bit....
Download Link: [Here]
We now have a complimentary app on the app store for this A4D App.
What is A4D?
The goal of A4D is for us to move beyond just N1 make it an all in one flashing/upgrading/android utility. We just added a ROM library with MD5s. We are not going to be hosting the actual ROMs by themselves so if you report a dead link, they will be taken down (after a number of reports). You can also add your own ROMs as well into the library.
The ROM library will be supported by both Android and Desktop App. We are rewriting the Desktop apps so that we can do all 3 platforms in one, Linux, Windows, and Mac. You'll love the layout of the app. That's all we can say for now.
Oh one more thing. The android app won the best android app award at the Mobile in the Middle Hack-a-thon over the weekend in Chicago (on 3/6/2010).
I would like you guys to try out the app and tell us feedbacks. Also feel free to add your own ROMs to the Database and tell us how we can make the DB better. There a number of features we are trying to add as well. But with our full time jobs... things are going a little slower than we wanted. Sorry.
Requirements to run the app on Android: Amon_RA's recovery. That's what we tested it with.
Reserved
Reserved for Future Updates / Changelog
Can't wait to see if this is fool proof.
Add md5 check. Make it in this way: user have to enter/copy-past md5 hashsum from forum/site. Program calculates md5 of image and says image is good or bad. Also you can disable flashing with out this check. ;-)
good idea. Will do that. That will help with flashing screwed up downloads.
Hi
Thank you for sharing the application.
Does it flash the radio too? I mean CyanogenMod has two files a radio ROM and a CyanogenMod ROM. Does it flash both of them to the phone?
Thanks.
Radio flash is in there we took it out. May do so in the next release but radio flashing is dangerous (can brick phones) so...
Hey Lwin,
Nice concept man, this is gonna prove very handy for many peeps.
You've come up trumps again
So, this is a desktop application?
Does it flash ROM's from your desktop or copy them over and just run the commands on the phone for you?
I ask, as I'm having some problems flashing now, based round a slightly faulty Micro SD card. Does it store backups on the phone or on your desktop PC?
This program is written so you don't have to do command line commands. Everything else remains the same. If you are doing a Nand backup, it goes where it used to go.
I would recommend fixing your "slightly faulty Micro SD card" by getting a new card.
nice app for those that aren't familiar with cmd or jus pure...lazy lol
maybe the screens should be bigger as quite hard to see clearly whats available.
Pure Genius...
seraph1024 said:
Here is the GUI tool for unlocking, updating, restoring, flashing of the N1 (and in theory should work on all HTC androids).
Try it out and see if it is useful. The tool is made to help for people with very basic skills since the tool at this stage is a wrapper for the shell commands at this point.
Again, as usual, we take no responsibility for loss of sleep, loss of phone or screw ups on our side (due to app) or on your side (due to lack of ability to follow instructions).
I wish to make it more simple. We welcome feed backs.
Seraph1024 - ShadowPyro
Download Link: [Here]
Click to expand...
Click to collapse
Hey Seraph, This is getting better and better everyday.. How is your windows and android port.. Oh and don't forget there little buddy, I need you on my Mobility Team when we arrive to the scene.. Android and Audi... Almost there....
Edit: Okay, can't run on Mac, of course will in VMware, can you please make this mac native too... It would be great as per what MooMoo said, for all who are lazy...
shadowpyro said:
This program is written so you don't have to do command line commands. Everything else remains the same.
Click to expand...
Click to collapse
But I don't use command line now. I didn't realise anyone did. Do you not just boot into RA Recovery and flash from there?
shadowpyro said:
I would recommend fixing your "slightly faulty Micro SD card" by getting a new card.
Click to expand...
Click to collapse
Thanks, I didn't ask for advice.
GodDriven said:
Hey Seraph, This is getting better and better everyday.. How is your windows and android port.. Oh and don't forget there little buddy, I need you on my Mobility Team when we arrive to the scene.. Android and Audi... Almost there....
Edit: Okay, can't run on Mac, of course will in VMware, can you please make this mac native too... It would be great as per what MooMoo said, for all who are lazy...
Click to expand...
Click to collapse
There will be a mac port sometime this week. I can most likely port to linux too but if you know linux and if you have to use wrapper, you have an issue
install issues
I tried to install it but got a system update required....
extracted the sdk to the folder C:\android-sdk-windows
extracted android4dummies and clicked setup
I get a pop up with the following:
unable to install or run the application. the application requires that system assembly system.data, entry version 3.5.0.0 be installed in the global system cache.....???
What do I do now?
Sounds like the app uses .NET framework 3.5.
So goto microsoft website an get 3.5 .Net Framework.
pwvandeursen said:
I tried to install it but got a system update required....
extracted the sdk to the folder C:\android-sdk-windows
extracted android4dummies and clicked setup
I get a pop up with the following:
unable to install or run the application. the application requires that system assembly system.data, entry version 3.5.0.0 be installed in the global system cache.....???
What do I do now?
Click to expand...
Click to collapse
You do need .Net 3.5. It should have asked you, if not installed that as a prerequisite.
I went to MS and downloaded the .net 3.5 installed it (apparently it was already on my pc, so instead of installing I tried to repair it. no success....
pwvandeursen said:
I went to MS and downloaded the .net 3.5 installed it (apparently it was already on my pc, so instead of installing I tried to repair it. no success....
Click to expand...
Click to collapse
Can you send us a screenshot.
Do not unzip into C:\android-sdk-windows. App will install SDK or search for the SDK there.
Unzip on your desktop or temp and install from there.
just to be clear, I unzipped adroid sdk and placed in the mentioned location. the android4dummies is extracted on the desktop and executed from there..
so should I remove the SDK and retry?
After a long time it's a moment to realease HTC HD2 ToolBox app with HBL. Small app that will allow you to boot linux inside android, and display everything on screen or through VNC connection. ToolBox app is also redesigned and added some new functions.
In pack is barebone debian distro with xfce4 interface.
There is also posibility that this app and HBL will work on other phones like leo (desire, nexus one ...)
Everything else you need to know is in Readme file.
Bug reports or suggestions on this thread, i'll answer when i'll get some time.
Enjoy !!!
EDIT: I added Readme file to this post so lazy people can read everything before downloading pack, or asking silly questions!
EDIT 2: I'm currently working on support for sdcard roms and other non-working builds. Also i would like to mention that is possible to run ANY linux distro with HBL (with some modifications) or even to run another android rom!
So consider this early versions only as "technology preview", more support and bug-fixes in next few days...
P.S Thank you all for your support !
Download Link
wow awesome
Does it work within Android like vns versions?
I've been waiting for (something similar, but this should do the work) such an app.
Thank you.
@hd# ..
Read the "Read-me" file ?
been waiting for this too.
But my broadband is down and I've already exceeded my monthly data allowance using wifi tether (500mb !!!)
... might have to do it anyway
Edit; still downloading... I assume there is no sound enabled on this
hi
can i boot ubuntu with it?
hi first big thanks for your hard work.
now i need some help to get linux running from HBL.
i´m using kingdom sense3 rom from dungphp.
i installed hd2 toolbox and copied linux folder to root of sd card.
i installed HBL (Busybos is installed in version 1.19.x.x) i took rootexplorer and give /system/bin/ write permissions for owner/groups/others.
But i need initd support: what i have to do to get this?? or is it on my rom?
please help cause at the moment i´ve bootloops everytime i want to boot linux.
Thank's a lot for this! I've been waiting for this for for a while!!!
So if I understand this right.... which I don't think I did at first..... this is basically the same thing as booting ubuntu and connecting to it with vnc, the ubuntu that is in another thread.... i ask because what I am looking for is usb host support.... which I don't believe is possible with the other ubuntu that boots in android.... and I think if I undestand this right... is not possible with this one either......i do appreciate the work done on this app a lot.... but to me, it's useless unless usbhost is supported because of tiny menus and buttons not being easily clickable with fingers..... so I want to use my wireless mouse that has a usb receiever......
edit: download finally finished, I tried it out.... I really like it, couple questions.... is it normal for shutdown not to work? I chose to boot and show on local screen instead of vnc..... when I did that, it started fine, I messed around a little, then tried to shutdown... it said shutdown command failed or something similar.... then rebooted android..... and when you choose to boot on local screen, is this kicking android out so it's only linux, kind of like haret and booting android from winmo off sd? And last, is it possible for usbhost?
Edit2: I could barely see the text at the bottom of the hotboot screen that says to use log out feature to return to android... I did that instead of shutdown, there were no errors and it went to my android boot animation, then booted back to android just fine.....
Its working well. Thanks .I have the same question as Diesburg does. One more how to make right click.
diesburg said:
So if I understand this right.... which I don't think I did at first..... this is basically the same thing as booting ubuntu and connecting to it with vnc, the ubuntu that is in another thread.... i ask because what I am looking for is usb host support.... which I don't believe is possible with the other ubuntu that boots in android.... and I think if I undestand this right... is not possible with this one either......i do appreciate the work done on this app a lot.... but to me, it's useless unless usbhost is supported because of tiny menus and buttons not being easily clickable with fingers..... so I want to use my wireless mouse that has a usb receiever......
edit: download finally finished, I tried it out.... I really like it, couple questions.... is it normal for shutdown not to work? I chose to boot and show on local screen instead of vnc..... when I did that, it started fine, I messed around a little, then tried to shutdown... it said shutdown command failed or something similar.... then rebooted android..... and when you choose to boot on local screen, is this kicking android out so it's only linux, kind of like haret and booting android from winmo off sd? And last, is it possible for usbhost?
Edit2: I could barely see the text at the bottom of the hotboot screen that says to use log out feature to return to android... I did that instead of shutdown, there were no errors and it went to my android boot animation, then booted back to android just fine.....
Click to expand...
Click to collapse
HBL actually shuts down all android processes (except init and some critical ones) and then switches to linux. It's normal for shutdown not to work right now, in future it will work but for now use log out to exit from linux. USB Host support for now is not possible without modified kernel, but i'm working on custom kernel with usb-host/normal mode switching.
I must admit i didn't have much time to work on this project so many things can be improved, and i hope in fallowing days/weeks i will have much needed time to work on it. So everything is still a "prototype"!
@alltome
99.99% of custom roms have init.d support, just check if you have init.d directory in /etc.
Hi managed to install HBL but when I try to start linux using local screen the screen just hangs on "loading linux..." for ages. Tried vnc but doesn't work either. it doesn't seem to start shutting down android because if I press hardkey back button the phone is normal.
tried changing "writtable" statuses on the mount screen, but no joy. Is this what you mean by " writable /system/bin folder", or must I use rootexplorer?
Many thanks
u rock
hey dan1j3l HBL works flawlessly
keep on rockin'
Robbie P said:
Hi managed to install HBL but when I try to start linux using local screen the screen just hangs on "loading linux..." for ages. Tried vnc but doesn't work either. it doesn't seem to start shutting down android because if I press hardkey back button the phone is normal.
tried changing "writtable" statuses on the mount screen, but no joy. Is this what you mean by " writable /system/bin folder", or must I use rootexplorer?
Many thanks
Click to expand...
Click to collapse
The same problem for me, stuck at "HTC HD2 ToolBox loading linux.." screen
I'm using MIUI Offician 1.5.20
All those with problems starting HBL can you send me output of these few commands so i can get more info (use adb shell)
busybox ps | grep hbl
busybox mount
busybox ls -la /system/bin/hbl
busybox ls -la /etc/init.d
busybox df -h
Hello dan1j3l First of all I'd like to Thank you for your hard work and this cool app which has great potential...
now that being said, I'm also having some troubles like stated above from other users i managed to install HBL (i think, cause i got the success message when clicking install HBL) but when I try to start linux using local screen, the screen just hangs on "loading/booting linux..."
Below i attached the output from commands on adb shell
Have the info you wanted.
Thanks dan1j3l
Have also added signature below
Robbie P said:
Have also added signature below
Click to expand...
Click to collapse
Hmm... I see you are using sdcard rom, never tested HBL with sdcard roms. It seems i need to make a different installer for sdcard builds... I will try to test it this weekend, then i will know more.
when i try to start hbl my phone vibrates two times and restarts. but it starts already with the bootanimation. then it boots back to android.
i'm using ndt miui. busybox is installed and linux image is in the root of the sdcard in linux folder.
I have Xron-ified vB2.9.1 rom installed on my touchpad, when it goes from Moboot to Cyanogenmod there is a quick error message that says the splash screen is too large for the display area, then it goes on to boot normally with the Cyanogenmod loading screen, followed by the colored flipping tiles screen and on to the home screen. This error seems to have no effect on the boot or the performance, but I just wanted to throw it out there. I've had this error on vB2.8 and vB2.9 versions of the rom.
Otherwise, I have no major issues and no complaints. I have been fortunate with these flashes and have somehow avoided all of the major issues I have been reading about.
Thanks guys and keep up the great work!
Gotta update Moboot!
Yup update moboot to the latest version tht will fix the problems.
Sent from my Touchpad using Tapatalk
Thanks guys, does anybody have a link by chance?
N00Bextrordinaire said:
Thanks guys, does anybody have a link by chance?
Click to expand...
Click to collapse
You can find it here.
http://code.google.com/p/moboot/downloads/list
Sent from my Touchpad using Tapatalk
I have the same problem any suggestions?
techihunt said:
I have the same problem any suggestions?
Click to expand...
Click to collapse
Have you updated your moboot to the latest version. For link see above in my previous post.
Sent from my Touchpad using Tapatalk
I have been looking for "how" to update moboot.
First... for those who have not been back to Acme Installer since your initial install... you will need it again. Every post I saw just said update moboot... I had CWM on the brain.... I have many pc's, so had to figure out which one had the Palm sdk installed on it... it also had the acmeinstall tool. You will need both of those.
Second. I went to the above site with my touch pad. Downloaded the file. then used my file manager to move the moboot_0.3.5.zip file to my old cminstall folder.
Third step. On my XP computer I opened a CMD prompt as admin and changed to the directory where the palm sdk was installed. I could see the acme installer in there.
Fourth - Shut off touch pad, plugged the USB cable into the pc
Step 5 - Fired up the touchpad and chose Webos recovery mode from the list. Did not have to hold the volume anymore which was pretty cool.
Last but not least - Rejoice as moboot gets rewritten, sys reboots, and I have a cool Xron logo where the old image does not fit error used to be. =)
If there is a better way than this please share. Worked for me, but who knows...
Forgot to add this line.
novacom boot mem:// < ACMEInstaller
that is what you type at the dos prompt
Just a heads up... Had to re-use this trick a 2nd time today. Decided to update to 3.0.5 of web os. It eliminated moboot.
It was not too tough to fix though. I added a few dual pane file manager in web os. Downloaded moboot again and put it in the cminstall folder.
shut down,
rebooted holding the power and volume up.
the rest was the same as above.
Cannot remember the file manager... Sorry. It was free though. Had what reminded me of a major's rank in the center of it...
I tracked down the file manager I used. It is Tegi's Commander. Took me a second to figure out how to move the file... I tried to just drag it, but it was a long press gig.
theroar said:
Just a heads up... Had to re-use this trick a 2nd time today. Decided to update to 3.0.5 of web os. It eliminated moboot.
Click to expand...
Click to collapse
Had you updated moboot before updating WebOS? As of the moboot update 0.3.4 that shouldn't happen, WebOS updates should not remove moboot (Source: JCSullins). I updated my WebOS to 3.0.5 and moboot remained untouched!!
Also as prev stated 0.3.5 will remove splash-screen size error!!
thanks for the information. I was actually able to figure it out on my own, and thankfully I did exactly what you guys suggested. For anyone else reading this, the instructions above work brilliantly! Thank you guys for your help and your quick responses and please excuse my delayed replies.
A Team Fireballas Release
Requirements:
ROOTED HTC Droid Incredible 4G LTE, Stock ROM
TWRP or CM Recovery
External SD Card
Windows
This was tested on Win 7, but should work on XP, Vista, or 7. A Linux version is possible if there is demand.
Instructions:
Perform a NANDROID backup in TWRP or CM Recovery
Download and unpack bloat.v1.1.zip
Update bloat_list.txt as desired. The included list is intentionally short, and you may desire others to be removed.
Plug in phone and enable USB debugging
Double-click bloat.bat
Follow prompts
The script will reboot your device into recovery to make the needed changes, since some issues can occur if run while booted into system.
You might need to wipe cache afterwards, depending on what apps were removed.
This tool will remove system bloat apps in /system/app/, based on the bloat_list.txt file enclosed. It makes a backup of them in /system/app.disabled/.
It also can remove the DROID boot animation and DROID boot sound. Options are provided to perform any or all of these operations.
Please let me know what you think.
v1.1 Changelog:
Improved variable usage
Improved error-handling
Increased timeout while waiting for reboots
Added choice.exe to the .zip
Cleaned up whitespace
Portable version(Not tested but im 98% sure this will work)
This is portable version if anyone wants to try, all required is script manager which is found on play store to execute it
Requirements:
root
For it to work you have to click root icon on smanager
When downloaded remane it from mobile bloat.zip to mobile bloat.sh, otherwise it wont work
please report back
Didn't work for me. It says:
List of devices attached
HT26JS309742 device
'CHOICE' is not recognized as an internal or external command,
operable program or batch file.
Please attach your device and try again.
Press any key to continue . . .
Choice should be an included Windows batch command.
What version of Windows? I tested on Win 7 Ultimate, so I wonder if maybe you have a home or media center edition that doesn't have it. If that's it then I might need to rework this.
Sent from my ADR6410LVW using xda app-developers app
CaptainRewind said:
Choice should be an included Windows batch command.
What version of Windows? I tested on Win 7 Ultimate, so I wonder if maybe you have a home or media center edition that doesn't have it. If that's it then I might need to rework this.
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
I'm on ultimate.
I will dig into this issue, thanks for letting me know.
Edit: It appears that it's actually part of the Windows Resource Kit.
I will see if it's possible to upload a new zip with it included. In the meantime, could you try installing that from Microsoft and let me know?
Sent from my ADR6410LVW using xda app-developers app
CaptainRewind said:
I will dig into this issue, thanks for letting me know.
Edit: It appears that it's actually part of the Windows Resource Kit.
I will see if it's possible to upload a new zip with it included. In the meantime, could you try installing that from Microsoft and let me know?
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
I copied choice.exe from windows\system32 to the bloat folder and it worked!
But then I got this:
/sbin/sh: /sdcard/nativeBloat.sh: not found
Removing bloat.
mv: can't rename '/system/app/HtcOMADM_SettingsPlugin_VZW.odex': No such file or
directory
mv: can't rename '/system/app/HtcOMADM_VZW.odex': No such file or directory
mv: can't rename '/system/app/TetheringGuard.odex': No such file or directory
Removing sound.
aaaaaaaand the boot animation is still there. Droid sound and bloatware were successfully removed, though.
reserved for later...!!Thanks
jtdogblue said:
I copied choice.exe from windows\system32 to the bloat folder and it worked!
But then I got this:
/sbin/sh: /sdcard/nativeBloat.sh: not found
Removing bloat.
mv: can't rename '/system/app/HtcOMADM_SettingsPlugin_VZW.odex': No such file or
directory
mv: can't rename '/system/app/HtcOMADM_VZW.odex': No such file or directory
mv: can't rename '/system/app/TetheringGuard.odex': No such file or directory
Removing sound.
aaaaaaaand the boot animation is still there. Droid sound and bloatware were successfully removed, though.
Click to expand...
Click to collapse
Had you previously removed those apps listed manually? Also what recovery are you running?
Basically, the .bat is a wrapper for a script that runs natively from recovery I wrote last year for the OG Incredible. It basically just copies two files, then kicks off the script from recovery based on the options you chose. I think now that it might be better for me to simply port all the logic into the parent .bat script, add choice.exe to the zip, and update the OP. This will have the bonus of eliminting the requirements for the resource kit and an sd card.
Will work on that.
Also I think the very first error is a race condition, so maybe 90 seconds isn't long enough to reboot into recovery. This would explain why the animation didn't change but the others did, since I went alphabetically so animation is executed first. Will increase timeout and gracefully handle absence of those .odex files or any others on the list not on the system.
Here is an advantage to the native .sh script, too, since checking for existence of a file on the android system would be really clunky and unreliable from a .bat file. I will try these things before a re-architecture of where the core logic lives. We are already stretching the limits of what Batch can do which is why I used native .sh script to do most of the real work.
Sent from my ADR6410LVW using xda app-developers app
jtdogblue, I've uploaded a v1.1 to the OP, mind trying it?
CaptainRewind said:
jtdogblue, I've uploaded a v1.1 to the OP, mind trying it?
Click to expand...
Click to collapse
Worked like a charm
Removing animation.
Removing bloat.
Removing sound.
==============================================
Rebooting and sleeping for 120 seconds.
Wait 120 seconds, or click c to continue once rebooted.
==============================================
==============================================
Removing script files from device, please standby.
==============================================
Press any key to continue . . .
jtdogblue said:
Worked like a charm
Removing animation.
Removing bloat.
Removing sound.
==============================================
Rebooting and sleeping for 120 seconds.
Wait 120 seconds, or click c to continue once rebooted.
==============================================
==============================================
Removing script files from device, please standby.
==============================================
Press any key to continue . . .
Click to expand...
Click to collapse
Great! Thanks so much for the valuable feedback!!
is there a full list of the bloat
for example
if I don't use twitter (or sence's twitter) what can I remove
if I use a different launcher then I cant use the sense widgets. which ones are those
dcooterfrog said:
is there a full list of the bloat
for example
if I don't use twitter (or sence's twitter) what can I remove
if I use a different launcher then I cant use the sense widgets. which ones are those
Click to expand...
Click to collapse
This remove Verizon bloatware if I'm right, if you wanna remove all of apps you don't use , unlock your bootloader, flash recovery and flash team venoms rom
Sent from my HTC Fireball using xda premium
i am not sure I want to flash a different rom this is my every day phone. I had some issues in the past on other phones
also I would rather remove the stuff myself.
i got rid of the obvious stuff lets golf....
i have frozen a BUNCH OF STUFF and will probably remove it slowly
I'm getting an error when I attempt to run this.. Not sure if its something I'm doing wrong.. Pretty much just download bloatv1.1, extracted, and run as admin for bloat.bat. Also when i checked the properties, I have to "unblock" each file extracted from the bloat.v1.1.zip, However this still did not fix the problem. I'm using windows 7 utl. x64.
C:\Users\quantum\Downloads\bloat.v1.1 (1)>echo off
==============================================
Written by CaptainRewind
Team Fireballas
Team Fireballas is jose51197 and CaptainRewind
==============================================
This script can remove Bloatware and Boot Animations
from the HTC Incredible 4G LTE.
You must be rooted, and have CM or TWRP recovery installed!
Your device must be connected to a USB 2.0 port!
==============================================
BACKUP COPIES OF ALL FILES WILL BE MADE.
==============================================
List of devices attached
(NAME OF DEVICE) device
This version of C:\Users\quantum\Downloads\bloat.v1.1 (1)\choice.exe is not comp
atible with the version of Windows you're running. Check your computer's system
information to see whether you need a x86 (32-bit) or x64 (64-bit) version of th
e program, and then contact the software publisher.
Please attach your device and try again.
Press any key to continue . . .
---------- Post added at 12:42 AM ---------- Previous post was at 12:08 AM ----------
quantumtransfer said:
I'm getting an error when I attempt to run this.. Not sure if its something I'm doing wrong.. Pretty much just download bloatv1.1, extracted, and run as admin for bloat.bat. Also when i checked the properties, I have to "unblock" each file extracted from the bloat.v1.1.zip, However this still did not fix the problem. I'm using windows 7 utl. x64.
C:\Users\quantum\Downloads\bloat.v1.1 (1)>echo off
==============================================
Written by CaptainRewind
Team Fireballas
Team Fireballas is jose51197 and CaptainRewind
==============================================
This script can remove Bloatware and Boot Animations
from the HTC Incredible 4G LTE.
You must be rooted, and have CM or TWRP recovery installed!
Your device must be connected to a USB 2.0 port!
==============================================
BACKUP COPIES OF ALL FILES WILL BE MADE.
==============================================
List of devices attached
(NAME OF DEVICE) device
This version of C:\Users\quantum\Downloads\bloat.v1.1 (1)\choice.exe is not comp
atible with the version of Windows you're running. Check your computer's system
information to see whether you need a x86 (32-bit) or x64 (64-bit) version of th
e program, and then contact the software publisher.
Please attach your device and try again.
Press any key to continue . . .
Click to expand...
Click to collapse
Bloatv1.0 worked just fine. btw.. not sure what i'm doing wrong with 1.1
NABI LAB v2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTE: The program is becoming long in the tooth and not as useful with Jellybean on Nabi. For Jellybean TWRP installs check this repackaged version of Nabilab http://forum.xda-developers.com/showpost.php?p=48987089&postcount=2088
This is a tool for performing various automated tasks on the Nabi 2. It's written as a windows command line batch file, and v1 has been tested by a few members of the forum with positive results. Hopefully this means all the bugs are worked out, most issues have been typos on my part. It's an attempt to include all recent developments in Nabi 2 rooting, Gapps install, recovery methods, and modding and provide and all in one experience. Alot of this is my own original work, and other parts are creations of others intact or modded for Nabi use. Using the latest known working methods, it hopefully prevents users from having to install, break things, uninstall, recover, try new method, ask forum questions, try another method, and all the while for those with kids having them ask why you broke their toy.
Currently you cannot install Gapps on 2.1.27 see here http://forum.xda-developers.com/showpost.php?p=45866724&postcount=1647
A test version of NabiLabGUI is here: http://forum.xda-developers.com/showthread.php?t=2391449
Overview
Video Overview of Nabi Lab v1 mostly the same as v2
-Install ADB/Fastboot digitally self-signed drivers.
-Root the Nabi 2
-Install Gapps(Play Store, etc)
-Fix Android is upgrading message
-Make a stock backup of unrooted device
-Install a stock 1.9.37 in the event of loss of backup.
-Install stock, or TWRP recoveries
-Tablet Information
-Lockscreen modding tool
-NabiLab patching system to install updates to this program
-Fix TWRP touchscreen issues
-While not a built in function using the tools to fix broken Wifi
Download
Read the installation section below to determine which version you want.
File names:
NabiLabFull.zip 1.1GB
Download
NabiLabLite.zip 97MB
Download
Download Mirror
NabiLabv2Update.zip 10.1MB(upgrade patch for v1 users)
Download
Download Mirror
Installation
There are 2 versions of Nabi Lab: Full and Lite. The full edition is 1.1GB and includes a stock 1.9.37 backup of the system, data, and boot partition. It's usefulness is really only of interest to those that need to restore to a stock backup. It should be a rather limited group of people as you should have a backup of your system already that you could use in lieu of this. However in the event you have lost your backup, or have mangled the system to the point you aren't sure what to do, the option to restore to stock 1.9.37 is in the full edition. The likely download of choice is the Lite edition at a more manageable download size of 97MB. It has all the tools of NabiLab just without the ability to restore a stock backup(which of course you have one of your own). The upgrade patch zip is for v1 users.
NEW INSTALLS
1) Download Nabi Lab
NabiLabFull.zip 1.1GB
NabiLabLite.zip 97MB
2) Extract the zip files to a location of your choosing. Run the NabiLab.bat file.
PATCH INSTALLS(For version 1 users)
1) Download NabiLabv2Update.zip 10.1MB
2) Extract the zip IN to the directory NabiLab is in not FROM the directory. What ever your unzip program it should be extracting to X:\somefolder\somefolder\yourNabiFolder\ If you do it right there will be a file RunOncePatch.bat in the same folder as NabiLab.bat, and a NabiPatch.zip in a new folder called patch in your NabiLab folder.
3) Run RunOncePatch.bat
note: This is only necessary this time, any future patches will be applied by downloading a NabiPatch.zip, and installing inside the NabiLab program.
Prerequisites
1) ADB enabled in Android. Enter Mommy/Daddy mode. Open settings->developer options->put a check mark in USB debugging.
2) Unsure you are on version 1.9.37. Enter Mommy/Daddy mode. Open settings->About Tablet->Product Version. If it's at something less then 1.9.37 go up to the "Update" selector and check update and install. You may have to do this more then once.
Notes: At this point it is believed that the Madagascar Nabi 2, and UK version have product versions of 1.9.34, and 1.9.35/6 respectively. You can attempt to use NabiLab at those versions but I cannot guarantee results. Most things should work however.
Usage
Obviously using this product on your Nabi 2 voids the warranty and I take no responsibility for the damage you cause.
MENU 1 - Installing drivers
The provided drivers are for Windows XP,Vista, 7 and 8 32bit and 64bit. They are modded version of the drivers by 1wayjonny found in this thread. The mod to those drivers are adding the Nabi, and the HP Touchpad Tenderloin(only because I have one). The are digitally self signed by "NabiLab".
Menu Option 1 - Auto Install
Check in the top left corner under Detected OS to see if it matches your configuration. The most important part is if it says "x86"(32bit) or "AMD64"(64bit) this is what the auto installer is going to install. If you don't know right click "my computer" and look under system type. If everything looks right proceed. An installer will launch and guide you through install.
Menu Option 2 - Manual Install
If you want to manually install, an explorer window will launch allowing you to pick the NabiDriver32.exe or NabiDriver64.exe. In case it needs stating the NabiDriver32 is for 32bit OS, and NabiDriver64 is for 64bit.
Notes: The driver can be uninstalled by going into control panel and add/remove programs, select Nabi Driver and click uninstall. The digital certificate for Nabi lab is installed in Trusted Root Certification Authorities. Probably the easiest way to view is internet explorer. Go to tools->internet options->content->certificates. It can be removed from here should you feel it's a security risk. I don't think it installs properly on XP, so if you want to add it go to your program files folder->NabiLab->driver and find the NabiLab.cer, right click and select install. When you come to option of where to install manually select Trusted Root Certification Authorities.
MENU 2 - Root, Gapps, Recovery
Menu Option 1 - Install Root, Recovery and Gapps
This option is best used if you have a brand new Nabi. At this point you should have met the prerequisites of enabling ADB in Android and upgrading to 1.9.37. Follow directions, most sticking points are pressing the volume + and then pressing the volume - button twice and making sure recovery kernel is the one highlighted. After its complete you should have a rooted Nabi, with Gapps and a backup of your unmodified Nabi in the folder TWRP/BACKUPS/YOURSERIAL/stockunrooted on your device. Not a bad idea to copy this off the Nabi to your computer if you need to free space or have it in a second location.
Menu Option 2 - Install Root and Recovery
Same as above but doesn't install Gapps. Some people have trouble with option 1 taking the Gapps install, I personally have never experienced it but the option is this one, or I guess if you are an elite hacker that just wants root.
Menu Option 3 - Install Gapps
Same Gapps installed in the Option 1. Useful for re-installing Gapps, and/or getting rid of the Android is Upgrading message. It is the immensely popular t499user Gapps with the 2 stray .odex removed. No sense in reinventing the wheel. This makes NO backup of you Nabi. You will have to already have installed TWRP.
Menu Option 4 - Install Root
Installs root. Nothing fancy here, and likely unneeded but here for completeness if you find yourself in a strange situation. One that comes to mind is that you have a stock backup which you restored and don't want to do another backup so you would just run this and the gapps install. It makes NO backup. You will have to already have installed TWRP.
Note: The layout of this is based on the original work by jmztaylor, modified for what we currently know about the Nabi and tweaked accordingly.
MENU 3 - Return Nabi to Stock Condition
The menu options will only be available if you have downloaded Nabi Lab full. If you have a stock unrooted backup you should try that first.
Menu Option 1 - Return Nabi to Stock 1.9.37. Android can boot.
This is useful if you just want to return your Nabi to stock for regular use, sale, or warranty(morals aside). This is the mode to use if you can boot Android. This operation will take some time to run, so let it. Upon completion TWRP is still installed, to entirely restore to stock you will need to install the stock recovery(see Menu 4). You have the option to put on external or internal storage. Although I don't think I compiled TWRP to use "in place" install, which would mean it still copies to internal. I'm not sure on this one, so internal is probably the best bet, but I have performed it on external and it works fine. You will need space on internal storage to do it.
Menu Option 2 - Return Nabi to Stock 1.9.37. Android not booting.
This is useful if you are in a situation that has left Android unbootable and you have no backup. Otherwise it's the same as Option 1. You will boot to TWRP and then perform the restore. Again TWRP will still be installed afterward, no be completely at stock you will have to remove it by Main Menu 4. I have it this way in the event you plan to immediately reroot it.
Notes: If you want to view this menu in the lite version, you need to open the file havefiles.txt, it is located in the stockimage folder. Change the line backup=false, to backup=true. You can then view the menu. You can then copy files you wanted to the stockimage folder and restore. Since the restore portion is manual I'm not sure why you would ever use it this way but if you want to play around that's how to enable it.
MENU 4 - Install Recoveries
Menu Option 1 - Install TWRP 2.3.3.0 for Nabi Version 1.9.37
Installs TWRP 2.3.3.0. This is the version that everyone should be trying to use first before trying other versions. This is the version that has symlinked paritions since it is thought currently their might be different partition structures for various Nabi's. Newer Nabi kernel and fixes touchscreen issues for some people that were using 2.2.2.1.
Menu Option 2 - Install TWRP 2.3.3.0 for Nabi Versions prior to 1.9.37
Use this option if Option 1 didn't work for you. Older Nabi kernel, otherwise same as Option 1.
Menu Option 3 - Install TWRP 2.2.2.1
This is the original TWRP from the first Nabi rooting thread. Use this if the other 2 don't suit you, or you just trust my compile skills, which may be prudent... :silly:
Menu Option 4 - Install Stock Recovery
Installs stock recovery. This is useful for taking an OTA, or completely returning Nabi to stock.
Menu Option 5 - About Recovery Installer
A leftover from my initial recovery installer, I was too lazy to remove it.
Notes: TWRP installs are based off my work in this thread if you want to read more.
MENU 5 - Tablet Information
Nabi Information, serial, version, build date, device mode, internal/external size, detected backups.
Note: This only detects if a backup folder is present, not if there are backups actually inside the folder. The only way this would be the case is if you manually deleted them or just made a empty folder in there, so be aware. Also if you have made a ramdisk modifying init.rc, used creative symlinking to swap internal and external SD, or used a prebuilt app to swap this screen may be incorrect.
MENU 6 - Lockscreen Mod Tool
Don't use this if you have updated to v2.0.5, I haven't tested but the framework-res.apk was updated in the 2.0.5 update and if you are using the old one you could throw yourself in to a bootloop
Menu Option 1 - Install custom lockscreen
Use this to install a custom lockscreen. You will need a picture that is in .png format and is 1440 x 903. A explorer window will open up showing you the location to put the picture. The file MUST be name lockscreen.png, there is one there that is black, you can overwrite it be there MUST ALWAYS be a lockscreen.png file in that folder if you use the tool. Bad things could possibly happen if it doesn't. You have the option to manually install the lockscreen, or automatically install it after the zip is built. In either case it copies whatever you named the zip(you are prompted for a name) to the internal SD, along with a file called lockorig.zip. The lockorig.zip is there if you mess up and Android won't boot you can manually install the lockorig.zip in TWRP to put it back to stock.
Menu Option 2 - Install stock lockscreen
Use this to return to stock. Remember if you used Option 1 there will already be the stock lockorig.zip on your internal storage.
Notes: If you make a custom lockscreen, while it copies the installable zip to your device it also copies it to your picture folder so you can share with others. Make sure you visit in share your creation over in this thread.
MENU 7 - Patch NabiLab
Menu Option 1 - Install Patch
For any updates to Nabi Lab this is where you can automatically load them. Basically you will download NabiPatch.zip and place the entire zip in the patch folder. No unzipping just the single file. Then run this option.
Note: Since this option wasn't in NabiLab v1, we have to do some trickery when coming from version 1 to install, so the procedure is different, all subsequent patches will be the above method however. Coming from version 1 you will need to download NabiLabv2update.zip and extract it into the NabiLab directory such that RunOncePatch.bat is in same directory as NabiLab.bat, and the other file NabiPatch.zip is in the folder "patch", then run the RunOncePatch.bat If you extract into your NabiLab directory it won't be a problem, the hint you didn't do it right will be if the RunOncePatch.bat isn't right there with NabiLab.bat
Credits
jzmtaylor - Original Nabi root. Nabi device code from which to build newer TWRP
t499user - Gapps fix
Dees_Troy - TWRP build tutorial
Eric Karz - Lockscreen Modding, NabiLab scripting
1wayjonny - Universal Driver base code
TeamWin - They are the guys that make TWRP possible
In all honesty everyone that has participated in the main Gapps thread has indirectly made the program what it is from testing, to information, to troubleshooting and everything else Nabi.
Hmmm just for giggles I installed Nabi Lab on my Computer to change the Lock Screen and it does not want to read my Tablet.
Thanks for this! Driver install didn't work for me on any of my computers...well it did install a driver but didn't read my nabi. Uninstalled nabilab driver and used PDA.net and all was good. Nabilab worked great installing recovery root n gapps! Thanks agn.
Sent from my EVO using xda app-developers app
DarkAngel said:
Hmmm just for giggles I installed Nabi Lab on my Computer to change the Lock Screen and it does not want to read my Tablet.
Click to expand...
Click to collapse
So it's saying error Nabi not detected or no driver? Is the device seen in Device Manger? Really can be only 2 thing, adb conflict or device driver.
strive53 said:
Thanks for this! Driver install didn't work for me on any of my computers...well it did install a driver but didn't read my nabi. Uninstalled nabilab driver and used PDA.net and all was good. Nabilab worked great installing recovery root n gapps! Thanks agn.
Click to expand...
Click to collapse
What operating systems and did you have any previous Android devices connected to the computer? Sometimes I noticed it will conflict with any previous driver installs, and while installing the driver is successful it won't use it. I guess it doesnt matter if it's working for you with PDAnet. If you are on vista or later you can try running pnputil -e from command prompt and look through all the oemxx.inf's and see how many google,inc android drivers there are.
aicjofs said:
So it's saying error Nabi not detected or no driver? Is the device seen in Device Manger? Really can be only 2 thing, adb conflict or device driver.
What operating systems and did you have any previous Android devices connected to the computer? Sometimes I noticed it will conflict with any previous driver installs, and not while installing the driver is successful it won't use it. I guess it doesnt matter if it's working for you with PDAnet. If you are on vista or later you can try running pnputil -e from command prompt and look through all the oemxx.inf's and see how many google,inc android drivers there are.
Click to expand...
Click to collapse
Sorry should have been more specific. It detects it via Device Manager but not via Nabi Lab. I am running Windows 7 x64
DarkAngel said:
Sorry should have been more specific. It detects it via Device Manager but not via Nabi Lab. I am running Windows 7 x64
Click to expand...
Click to collapse
Is it detecting 2 Nabi interfaces in Device Manager? I can see it's detecting the MTP interface, but what about the ADB interface. Usually ADB appears under Android Device and MTP under Portable Devices. Is there anything under "Other Devices"? NABI2-NV7A something or other? Only other thing I could think is that there is a hung up ADB process running, kill it in task manager or reboot.
sorry knew i should have stated my operating system. my main computer is a macbook and i have a old xp laptop n xp netbook that i use for flashing. i also tried it on my moms win7 desktop and a friends win8 desktop without luck. never changed in device manager from NABI2-NV7A with yellow exclamation point. ive flashed a bunch of phones from my laptop and probably do have drivers installed from who knows what.. it did install the driver but nabi wasnt detected as adb interface. rebooted computers n nabi after installs. i didnt have any other device attached at the time.
aicjofs said:
Is it detecting 2 Nabi interfaces in Device Manager? I can see it's detecting the MTP interface, but what about the ADB interface. Usually ADB appears under Android Device and MTP under Portable Devices. Is there anything under "Other Devices"? NABI2-NV7A something or other? Only other thing I could think is that there is a hung up ADB process running, kill it in task manager or reboot.
Click to expand...
Click to collapse
Yes it's detecting on both. The only thing that has been baffling me for some time is back when I had a Windows phone and after I switched to android, what appears to show in "Other" looks like my old TouchPro2. I can not delete that.
strive53 said:
sorry knew i should have stated my operating system. my main computer is a macbook and i have a old xp laptop n xp netbook that i use for flashing. i also tried it on my moms win7 desktop and a friends win8 desktop without luck. never changed in device manager from NABI2-NV7A with yellow exclamation point. ive flashed a bunch of phones from my laptop and probably do have drivers installed from who knows what.. it did install the driver but nabi wasnt detected as adb interface. rebooted computers n nabi after installs. i didnt have any other device attached at the time.
Click to expand...
Click to collapse
I had trouble with computers that has previous drivers installed sometimes, other times not. I tested fresh installs on XP 32, 7 32, 7 64, 8 64 and everything went fine, but it was much more hit and miss with computers that already had a slew of drivers. I'm more concerned that NONE of yours would work, although I guess it's offset by the fact that PDAnet driver worked and that NabiLab itself worked fine.
Yes it's detecting on both. The only thing that has been baffling me for some time is back when I had a Windows phone and after I switched to android, what appears to show in "Other" looks like my old TouchPro2. I can not delete that.
Click to expand...
Click to collapse
Well you have me baffled too! haha. If you run "adb devices" from cmd prompt what is the output? You have a modified cmd processor, that opens batch files? Seems like everything is in place. It case it's something with the program did you come from v1 NabiLab and patch or just v2?
f you want to play with the lockmod while we figure it out, the pic zip you made will still be in "pictures" folder, just let that portion of the program run until it errors when it tries to adb transfer. You can manually transfer to SD and flash TWRP.
aicjofs said:
I had trouble with computers that has previous drivers installed sometimes, other times not. I tested fresh installs on XP 32, 7 32, 7 64, 8 64 and everything went fine, but it was much more hit and miss with computers that already had a slew of drivers. I'm more concerned that NONE of yours would work, although I guess it's offset by the fact that PDAnet driver worked and that NabiLab itself worked fine.
Well you have me baffled too! haha. If you run "adb devices" from cmd prompt what is the output? You have a modified cmd processor, that opens batch files? Seems like everything is in place. It case it's something with the program did you come from v1 NabiLab and patch or just v2?
f you want to play with the lockmod while we figure it out, the pic zip you made will still be in "pictures" folder, just let that portion of the program run until it errors when it tries to adb transfer. You can manually transfer to SD and flash TWRP.
Click to expand...
Click to collapse
This is the first time installing it actually since I Rooted and installed GApps through Ubuntu. I just wanted to try it so I can try and change the lockscreen image and update TWRP while I was there also. I downloaded v2 with the backup. I was going to try v1 to see if that made a difference or try the PDAnet driver.
Sent from my NABI2-NV7A using Tapatalk HD
Worked fine as soon I realised I wasnt waiting for the files to transfer :banghead:
Sent from my GT-I9100 using xda premium
kieronw3 said:
Worked fine as soon I realised I wasnt waiting for the files to transfer :banghead:
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I could add a line that says, go check the mail, run to 7-11, trim the dogs toe nails. Hehe. Glad it worked eventually. 58 or so downloads and not many complaints, I can live with that, better then a brickfest. :laugh:
Nice job on lab update. Good use of the colors
i have a Request
could you add 'upgrade Twrp to the latest version'
maybe under Advanced User tool.
then if for some reason there is changes in the future you could just put the image file down load in that folder and update by click of a button ?
Win 8 64bit... Never had other android drivers installed on this machine. I dont see it listed in device manager at all. But the machine definitely sees it in my computer, and I also see it go into debug mode on the tablet. Confused,,,
Eric Karz said:
Nice job on lab update. Good use of the colors
i have a Request
could you add 'upgrade Twrp to the latest version'
maybe under Advanced User tool.
then if for some reason there is changes in the future you could just put the image file down load in that folder and update by click of a button ?
Click to expand...
Click to collapse
I need something for a version 3, so why not?
delio77 said:
Win 8 64bit... Never had other android drivers installed on this machine. I dont see it listed in device manager at all. But the machine definitely sees it in my computer, and I also see it go into debug mode on the tablet. Confused,,,
Click to expand...
Click to collapse
Are you using NabiLab or just the drivers I linked in another post? Is it detecting it in NabiLab? If it is the drivers have to be there under Android Device.
When I try to install recovery, root, gapps, I get stuck on waiting for device. My device detects just fine. I think it may be an issue with fastboot drivers, not ADB drivers? Because ADB reboots the device into fastboot just fine. But once it's there, it just sits on "waiting for device". Any thoughts?
bradleyw801 said:
When I try to install recovery, root, gapps, I get stuck on waiting for device. My device detects just fine. I think it may be an issue with fastboot drivers, not ADB drivers? Because ADB reboots the device into fastboot just fine. But once it's there, it just sits on "waiting for device". Any thoughts?
Click to expand...
Click to collapse
Have you verified that your fastboot drivers are working? If you navigate to the folder where adb.exe and fastboot.exe are you can just iddues the command fastboot devices to see if the device is connected while in fastboot.
1. How would you update a Nabi that has been originally rooted on .23 with jmz's work. I'd also like to clean up the optimizing android apps issue?
2. Would it be possible for you to add a "Clone Nabi" option to the Lab. Many people have more than one Nabi to tend to and it would be nice if you could duplicate the setup across multiple devices. I did it by hand for a dozen and let's just say it's a bit painful.
Mostly, though I wanted to thank you and all of the other developers for their work. There is a classroom full of 1st graders that use the Nabis everyday. They used to be stuck with nine-year-old Dell computers that would take 15 minutes just to boot...now things are easy and fun. You guys have really made my donation of the Nabis a great project. Thanks!
aicjofs said:
I need something for a version 3, so why not?
Are you using NabiLab or just the drivers I linked in another post? Is it detecting it in NabiLab? If it is the drivers have to be there under Android Device.
Click to expand...
Click to collapse
I am using NabiLab and it said not detected. I eventually got it to work with PDAnet
Ken Esq said:
1. How would you update a Nabi that has been originally rooted on .23 with jmz's work. I'd also like to clean up the optimizing android apps issue?
2. Would it be possible for you to add a "Clone Nabi" option to the Lab. Many people have more than one Nabi to tend to and it would be nice if you could duplicate the setup across multiple devices. I did it by hand for a dozen and let's just say it's a bit painful.
Mostly, though I wanted to thank you and all of the other developers for their work. There is a classroom full of 1st graders that use the Nabis everyday. They used to be stuck with nine-year-old Dell computers that would take 15 minutes just to boot...now things are easy and fun. You guys have really made my donation of the Nabis a great project. Thanks!
Click to expand...
Click to collapse
So is the device still on .23? Probably 3 ways to go about it if that's the case,
1) backup apps with something like Titanium backup, restore the original backup "stockunrooted" of Nabi, reinstall stock recovery, update to 1.9.37, reapply root and gapps, restore app backups, or
2) backup apps, restore a stock 1.9.37 from NabiLab, reapply root, gapps, restore app backup. or
3) you can try updating the safe OTA's people have posted, I came late to the game so I didn't study those, I know there is the wifi issue between kernel and modules if you don't do it right. If you already are on .37 but just rooted back on .23 the only thing to do is gapps to fix android upgrading. The optimizing android is fixed by flashing the fixed gapps.(Gapps only, option 2 then option 3 in NabiLab)
How would you like to see cloning? It just loops through the procedure and you just keep plugging Nabi? Or a restoring image to all of them. Help me visualize what you think would be best.
I'm not sure how you are doing it. How I would do it currenlty for Nabilab if I had 20 brand new Nabi's is like this. Once all Nabi's are at version you want (1.9.37)
Take one Nabi and do a recovery, root, gapps, backup(Option 2, Option 1)
Grab the backup it made and move it to computer.
Take remaining Nabi's
Install TWRP 2.3.3.0(Option 4, Option 1)
Install Root Only(Option 2, Option 4)
Install Gapps Only.(Option 2, Option 3)
What you accomplish here is making the backup only once. So first Nabi takes 15 min, the remaining maybe 3 min.
No thank you for popping in with some feedback.