FORUMS
Remove All Ads from XDA

[RECOVERY][NABI2] TWRP 2.3.3.0, 2.8.5.0 testing

1,070 posts
Thanks Meter: 1,022
 
By aicjofs, Senior Member on 30th December 2012, 11:58 PM
Post Reply Email Thread
10th January 2013, 02:11 AM |#11  
Senior Member
Thanks Meter: 92
 
More
Test Report
I was able to use the nabi lab but i must admit i had problems
the first was adb\adb.exe start-server stays on when not even using the program. the problem that this caused for me is just way to much to type ...lol

so i added adb\adb.exe kill-server at the bottom of the bat file so it looks like this
:Main_7
adb\adb.exe kill-server
EXIT



The next one i uninstalled pdanet

2nd (Probably the most important step) the install of drivers "android_winusb.inf"
this one is not anything new to me
"right click and install' and i got "The INF file you selected does not support this method".
So my work around was to install it manually.
Now in the Device Manager i see Samsung phone with "Fuhu Nabi 2 ADB Interface" in it (Q is this what we suppose to see?)

3 is a question
after also installing the driver in this state . i see in the device manager Samsung phone with "google galxy nexus ADB Interface" (Q is that correct?)
I ask because i can also change it to " Fuhu Nabi 2 BootLoader Interface "
Both work
4 Suggestion
Make a built in test for both modes before proceeding
like
1) press to make sure you can boot to bootloader mode
Stop here if it didn't work
2) press to make tablet Reboot (when in bootloader mode)
IF its a success you can proceed to the next option .
thanks for the hard work you are doing , Much thanks
10th January 2013, 05:24 AM |#12  
aicjofs's Avatar
OP Senior Member
Flag Portland, Oregon
Thanks Meter: 1,022
 
More
Quote:
Originally Posted by Eric Karz

I was able to use the nabi lab but i must admit i had problems
the first was adb\adb.exe start-server stays on when not even using the program. the problem that this caused for me is just way to much to type ...lol

so i added adb\adb.exe kill-server at the bottom of the bat file so it looks like this
:Main_7
adb\adb.exe kill-server
EXIT



The next one i uninstalled pdanet

2nd (Probably the most important step) the install of drivers "android_winusb.inf"
this one is not anything new to me
"right click and install' and i got "The INF file you selected does not support this method".
So my work around was to install it manually.
Now in the Device Manager i see Samsung phone with "Fuhu Nabi 2 ADB Interface" in it (Q is this what we suppose to see?)

3 is a question
after also installing the driver in this state . i see in the device manager Samsung phone with "google galxy nexus ADB Interface" (Q is that correct?)
I ask because i can also change it to " Fuhu Nabi 2 BootLoader Interface "
Both work
4 Suggestion
Make a built in test for both modes before proceeding
like
1) press to make sure you can boot to bootloader mode
Stop here if it didn't work
2) press to make tablet Reboot (when in bootloader mode)
IF its a success you can proceed to the next option .
thanks for the hard work you are doing , Much thanks

Ok I really need to make a thread for Nabi Lab. Was that a hint? haha. Excellent feedback as always.

1. Yes you are correct that it should be added. I will add it.

:Main_7
adb\adb.exe kill-server
EXIT



2. What version of windows are you using? Also 32bit or 64bit? I had no issues with 7 and 8 64 bit after disabling windows driver signature enforcement, are you sure it took the "disable driver signature enforcement" after the reboot? That's the only thing that I know that would cause that. XP worked but I did manual mode as you did while testing. It's a modified Samsung driver so it might display that.

3. Also possibly related to the above. However I don't think so... It's possible that installing PDA net doesn't remove driver store/inf(depending on windows version). For example on Windows 7 open /windows/system32/driverstore/filerepository and search for "android" there is likely extra ones. So it just reinstalled the PDA net one. It should say Fuhu Nabi 2, so I think you are using the old driver. Both drivers are so you see the option for Nabi labelled one. You would have to unisntall in device manager and then remove all of android infs. Then reinstall.

4. Useful feature. That's not too hard to add since it detects the mode based off of it can run the getprop command. Give me an example when you would want it to do this so I can add it logically. Just really adding "fastboot reboot" and detecting. Are you thinking automatic detection like refreshing on it own?

Thanks for the feedback. You were already credited in the readme, but maybe you need some more credit
10th January 2013, 11:43 AM |#13  
Senior Member
Thanks Meter: 92
 
More
before i forget http://forum.xda-developers.com/show...highlight=nabi post 1302.

i was thinking
after the driver install
something like
1) test 1- Action > adb.exe reboot-bootloader
@echo Do you see the pretty green word "Bootloader" ? lol sorry i am tired
11th January 2013, 04:13 AM |#14  
Senior Member
Thanks Meter: 92
 
More
nabilab.bat
what ya think ?
line 137
explorer.exe .\driver
to
%windir%\explorer.exe .\driver
plus it seem to be the only way it works for me ...lol

i did at one time have some changes in my windows enviroment variables
but i think i changed it back .
11th January 2013, 07:20 AM |#15  
aicjofs's Avatar
OP Senior Member
Flag Portland, Oregon
Thanks Meter: 1,022
 
More
Quote:
Originally Posted by Eric Karz

what ya think ?
line 137
explorer.exe .\driver
to
%windir%\explorer.exe .\driver
plus it seem to be the only way it works for me ...lol

i did at one time have some changes in my windows enviroment variables
but i think i changed it back .

Will that even be necessary if we go with the driver.bat you posted integrated in to the main bat file? I have been busy with my job last few days but I was able to run it in a few environments and it was working. The driver works, Im just working for an experience where anyone that can click a mouse/use a keyboard can install it. I think the PDAnet one is messy, that program even installs the apk to your tablet. Nonetheless the driver from a fundemental standpoint is the most important part, even if most people already have some functional driver. I want to get the driver cleaned up and the 2 known typos(although the 2nd might not be necessary if the driver install changes)

If I get those fixed make a Nabi Lab thread and work on ideas people have or want to see. Since you have been over the code what do you think of my hack job? Haha. Just notepad, not even notepad++, let alone a proper sciprting editor, I just kept adding stuff, it started as a simple recovery installer and then I got sloppy, and my variables and calls are a mess and named ridiculous. Kind of embarrassing. I haven't written that much code from scratch in 20 years, most of the time you have a base and can just work from there. That driver you linked gave me an idea of adding color to highlight errors and important parts, mostly cosmetic. For line by line color changes I have to use chgcolor and echoj. Easy enough to add to the download but changing all the echos is a tone of work.

I hope you know I appreciate your contributions.
11th January 2013, 10:13 PM |#16  
Senior Member
Thanks Meter: 92
 
More
opps my bad - forgetting the part about adding it to the main bat file .
just getting nabi lab to work for every one that uses it is the main goal.
code always has to start some place - i am sure as time goes on people will recommend things to to it.
the color in the Install bat was just to wake you up and watch what you are doing.
here is a example of something my brain skips over - Even though its proper and must be read in order to achive the goal
“Then hit VOL - until Recovery Kernel is selected
My brain only wants to hit vol 1 time haha
my brain should tell me to keep pressing Vol - until I see “Recovery Kernel” selected.
30th January 2013, 01:54 AM |#17  
Senior Member
Thanks Meter: 92
 
More
I see that Twrp is up to 2.4.0.0
Is there anything that nabi 2 users would benifit from it ?
30th January 2013, 02:08 AM |#18  
miggs0817's Avatar
Senior Member
Flag BRONX,NEW YORK
Thanks Meter: 7
 
More
Re: [recovery][nabi2] twrp 2.3.3.0
I too am wondering this!

Sent from my EVO using xda app-developers app
30th January 2013, 10:59 PM |#19  
aicjofs's Avatar
OP Senior Member
Flag Portland, Oregon
Thanks Meter: 1,022
 
More
Quote:

Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
Support for exFAT formatted sdcards (also thanks to bigbiff)
Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
Added wipe cache and dalvik after ADB Sideload
Replaced many system calls with their native C counterparts
Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
Fixed AOSP recovery commands to run after decryption on encrypted devices
Improvements for building TWRP in CM10.1
Other minor bugfixes and improvements

Seems interesting, I'll see about making a test build sometime this week unless someone beats me to it.
31st January 2013, 05:37 AM |#20  
aicjofs's Avatar
OP Senior Member
Flag Portland, Oregon
Thanks Meter: 1,022
 
More
I'm short on time these days. Here is a build that boots. I tested an install. You can try and put through paces. fastboot boot recovery.img to test and not replace current.

Download TWRP 2.4.0.0
31st January 2013, 07:53 PM |#21  
Senior Member
Thanks Meter: 92
 
More
2.4.0.0 feed back
I like the look of it
i have problems with it
fist tried setting/time zone i can change the time but it will not stick after reboot
2nd i tried was a back up seems to work but when going to restore i got error
"restore folder 'external_sdcard_/twrp/backup/000mynumers000/backupName'
E:no partitions selected for restore

Anything else i tried to restore it took about 5 seconds and was finished (its not that fast lol)
at this point i went back to 2.3.3.0 - so i could restore

Looking from the pc there are no files in the twrp/backupName folder
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes