yashsingh1/xdaforums huggingface dataset:
[EVO 4G Q&A, Help & Troubleshooting] bevoosted:
Yeah, I was gonna say, anytime you need to know what donor phone was used to flash your phone..just log into your Boost account and click on "Update Handset" this will tell you exactly what phone is on your account aka used as your donor phone. It will almost always be either the Incognito or Rant. ((But anyone thinking of flashing a phone, should never have this problem because you should always have physical possession of the donor used on your account..there is not one single reason why the person flashing your phone would need to hold on to your donor. Period. So always make sure that you ask for , and receive the donor phone used to activate your Sprint phone)))

That being said...Unfortunately, your phone is going to need reflashed again, and you definitely did not need to activate the previous donor on to your Boost account. You just needed to contact the person who flashed your phone and (hopefully) he still has your donor phone and will be able to pull your passwords (profile info ) out of it again and write it to your Sprint phone. (Like you already seem to be aware of) when your profile was reset, that meant that it did not match what was on your flashed Sprint phone. You'll need to (first activate the donor that was on your account before you just switched it to your previous one) and then update the profile (on that donor) and then put it on your Evo and you'll be good as new...OR just reflash your phone all together with the donor that you just activated on the account.

As far as the Voicemail Update issue...I have noticed this being pushed constantly to the Sprint phones also(including my Evo LTE on Boost) , I honestly don't believe there is a way to stop it. It doesn't really bother me anymore it just sits in the notification tray all the time. I imagine that eventually Sprint will stop pushing it to their phones. If I do ever come up with a fix for it though I will be sure to try and look this thread up or pm you with it. Good luck with getting your Evo back online...and word to the wise..never call Boost for anything if you have a flashed phone on your account...First off they will trouble shoot it as if its the donor phone..Second, their standard protocol is to Update the profile, and/or Factory reset the phone, either of which will interrupt the service on your flashed Sprint phone.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] hoursenghong:
Who is the richest guy here :cool: can donate me some so i can get cool launcher on Google Play :(
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] jayOverkill:
Download it for free if u dont have the money from the internet.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Anthropostar:
Get out.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Gugelhupf:
Have a look: Build your own launcher.

Cheers, Markus
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Woody:
Get a job.

Thread Closed
[Miscellaneous Android Development] aicjofs:
TWRP recovery for the Nabi JR. (NABIJR-NV5A)

​

​

​

At this point this recovery is still considered in testing. The normal disclaimers apply. 2 forum members have tested as working. After flashing to recovery partition sometimes the device would hang and need power button reset and then device works normally.

This is for Nabi JR 4GB

Nabi2 is HERE

NabiXD is HERE

NabiJR 16GB is HERE

Updates

Auto Installer for 2.6.0.0 in NabiLabGUI http://xdaforums.com/showthread.php?p=44258583#post44258583

Initial

-Latest TWRP 2.4.4.0

For more information on TWRP and change log see the TeamWin Website

Download

There are 2 downloads provided. The first is an installer for those less comfortable with the command line, it can install TWRP, and restore the stock recovery if you are updating or returning Nabi to stock. The second are for people that just want TWRP 2.4.4.0 and can do a manual install.

Auto Installer

Recovery Installer for Nabi(Recovery installer for TWRP 2.4.4.0 and STOCK recovery) Use install method 1

Current recovery.img

TWRP 2.4.4.0 for Nabi(Only TWRP 2.4.4.0, manual install) Use install method 2 or 3

Installation

Start with Nabi booted to android, ADB debugging enabled, windows adb and fastboot drivers installed. (PDAnet drivers are popular)

-Method 1 (Recommended install , guided installer)

-Download "Recovery Installer for Nabi" from above

-Extract TWRPupdaterjr.zip

-Run RecoveryUpdater.bat

Select option 1 for a Nabi on v1.0.3 and follow directions
Select option 2 to return your Nabi to stock recovery after restoring stock ROM

-Method 2 (manual temporary install, will keep your current recovery)

-Download "TWRP 2.4.4.0 for Nabi"

-Extract recovery.img from TWRPrecoveryjr.zip to your adb directory

-From a command prompt in your adb directory

adb reboot-bootloader
fastboot boot recovery.img

-Method 3 (manual permanent install, will overwrite your current recovery)

-Download "TWRP 2.4.4.0 for Nabi"

-Extract recovery.img from TWRPrecoveryjr.zip to your adb directory

-From a command prompt in your adb directory

adb reboot-bootloader
fastboot flash recovery recovery.img

Other

Device source https://github.com/aicjofs/android_device_fuhu_junior

TWRP source https://github.com/TeamWin/Team-Win-Recovery-Project/

Credits

TeamWin team for TWRP.

Dees_Troy for build tutorials.

Eric Karz and his hours of testing.
[Miscellaneous Android Development] Eric Karz:
just think, now you don't have to do a factory reset any time you have a problem with JR. thank you aicjofs for contributing such useful items to help make the nabi family experience so much better .
[Miscellaneous Android Development] aicjofs:
TWRP 2.5.0.0 for NabiJR

What's new in TWRP 2.5.0.0

-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection

-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)

-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache

-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)

-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)

-Fixed a problem with md5 verification of backups

-Added a search function to libtar (thanks to kokotas)

-Improve handling of XML errors (fix permissions)

-Fixed handling of subpartitions

-Improvements to recovery.fstab flags

-Fixed a problem with decryption not being able to locate the decryption key in some situations

Nabi specific: Theme change required for 2.5.0.0

Download
[Miscellaneous Android Development] RickR78:
This is awesome, thank you so much for this.
[Miscellaneous Android Development] Archon810:
Just flashed gapps using this recovery on the Nabi Jr with ICS. Fantastic. Thank you. Now it's not a useless POS anymore.
[Miscellaneous Android Development] juanfernandez77:
are there any stock roms or anything i can do if i wiped the original rom that comes from the factory
[Miscellaneous Android Development] aicjofs:
I replied to you in the Root for Nabijr thread. I don't have a NabiJr or I would. I know Eric should have a backup, someone needs to make a stock system image.
[Miscellaneous Android Development] Beatle405:
I've been attempting to flash the recovery, but my Nabi Jr keeps getting stuck on a screen that says, "Checking for RCK.. press key <volume up> in 1 sec to enter RCK" It has options to continue, reboot-bootloader, reboot, or power off. I have tried manually installing using the adb command lines and I've tried the automatic installer. Both get stuck on this screen. Any idea what's going on?
[Miscellaneous Android Development] Beatle405:
Anybody able to help?
[Miscellaneous Android Development] Eric Karz:
is it the 4 or 16 GB tablet ?
[Miscellaneous Android Development] Archon810:
My kid broke the 4GB Tegra 2 ICS Nabi Jr, and I got the 16GB Tegra 3 JB Nabi Jr as a replacement.

Any idea if it will work on that model?

Edit: I can't even test because this Nabi variant shows this screen after reboot-bootloader: http://i.imgur.com/I1rRMgI.jpg, and fastboot is saying waiting for device. Not sure how to proceed.
[Miscellaneous Android Development] Eric Karz:
aicjofs would be able to say better

but I wouldn't use the the one built for 4 gig on the 16 gig version

4 gig is ics and 16 is jelly bean - using it could result in a foobard tablet

Send aicjofs a PM and see if he has time to look in to a recovery for 16 gig version of the nabi jr
[Miscellaneous Android Development] aicjofs:
No way this particular recovery will work. It is Tegra2 based, and the new tablet is Tegra3 based. If anything you could try the Nabi2, or NabiXD recovery they are at least Tegra3, although if it works at all the screen will be completely off because of resolution differences. Be aware that you could damage using those recoveries, although I don't think it will and it just wont boot....anyway... for whatever that is worth... I'm just telling you. Based on what Fuhu did for XD(jelly bean) I'm not sure the Bin4ry root script will work. You can read about that adventure here http://xdaforums.com/showthread.php?t=2207499

As for the fastboot thing. Make sure it is showing the fastboot/bootloader driver in device manager, the menu is definitely different what is that saying above the menu?
[Miscellaneous Android Development] Archon810:
I did try Bin4ry, but I don't think it worked. There was an odd message in the process, and even though the script said it was done, I am not sure it was.

As for the custom recovery, I'm willing to work with you or whoever is interested, to test and get it working for the new Jr. For starters, it'd be great to know how to dump the current recovery. The next step is to figure out why I can't fastboot, and then try other recoveries from XD or custom if someone is testing with me.

The bootloader message says something about RCK - not sure what it means.
[Miscellaneous Android Development] aicjofs:
What did script say something about "cannot mount are you root"?

I'm not sure why fastboot isn't there. Do you get a different menu if you manually boot with Power and vol+ key. Maybe this new bootloader wants a key input within a few seconds of boot to enter recovery or fastboot?

I'm guessing RCK is recovery kernel.

One way or another you need to get fastboot, as you said, to try a custom recovery. So it's best to concentrate on that.
[Miscellaneous Android Development] Archon810:
I don't remember what the script said, but it wasn't that. In fact, it could have worked for all I know, because it thought it did, but there was a "not found" message halfway through the process about something. I can repeat if this is needed.

This is the menu that comes up with adb reboot-bootloader, or by holding Vol-Up and Power. Same menu.

Do you want to connect on gTalk to try to debug this further?
[Miscellaneous Android Development] aicjofs:
I'm mobile right now. Watching my kiddoz playing at park. I can try Gtalk later today.

So I'm looking at the image and 2 things come to mind. The USB icon

1) it's in fastboot now which is why icon is there. Open device manager as you have it plugged in and then power it up and see if there is any activity. Yellow exclamation, bootloader/fastboot driver showing up. Anything to show there is life on tablet side

2) can you use the volume keys to go down and "select" the USB icon. Or is it a touch icon, doesn't look like it but worth a shot.
[Miscellaneous Android Development] Archon810:
OK, I'll pm you my gTalk.

The USB icon is not selectable. It just cycles back to Continue after Poweroff.

This shows up in the device manager when it's hooked up, including when it's in this bootloader mode: http://i.imgur.com/SVMzw8v.png. The Unknown Device isn't related as it's there when the Nabi Jr is unplugged too - I think it's a fingerprint reader, I'm not even sure what it is.
[Miscellaneous Android Development] aicjofs:
Strange that its showing the ADB interface, instead of bootloader one in that task manager screenshot. I'm not thinking of many avenues here less some button pressing sequence we don't know. I tried a quick google search the other day and didn't come up with anything enlightening. You don't actually need fastboot/TWRP to root it but it would make it easier, plus I almost consider it a necessity for the backup purpose alone. It might be wise to post this is a general section and see if anyone else has seen a similar bootloader screen.
[Miscellaneous Android Development] aicjofs:
Ok here is the story on the 16GB Nabijr.

Fastboot commands need to be issued with "fastboot -i 0x0489"

The bootloader is locked on this Nabi. There is good news and bad news. Good news it can be unlocked. The bad news is that it wipes the Nabi to do so.

I was able to gain temp root in adb with motochopper. With this I was able to dd the recovery partition and extract the kernel. I was only interested in temp root, so I don't know if the program can be used as is for permanent root, or if you need to copy su and superuser.apk yourself. You can root with TWRP anyway. With this I was able to build a TWRP for the 16GB junior. Unfortunately the touch screen was very buggy. Hard to get presses to take and especially to swipe. I'm not sure if its just mine or they are all like this. This devices looks quickly thrown together. It's version 1.0, not 1.0.2, or 1.2.3, just 1.0, the build.prop looks like they never even touched it. Maybe it can be fixed with software update(touchscreen firmware update), no kernel source so that route won't work, maybe I don't have the module bound right in TWRP. I'm not sure the recovery is entirely usable with this bad of touch response but let's see what other devices are like.

If you wish to use TWRP for Nabi Jr 16GB this would be the instructions. USE AT OWN RISK!

1) Enter fastboot mode

With the Nabi powered off press and hold power and volume down.

2) Unlock the bootloader. This will erase everything on the device.

fastboot -i 0x0489 oem unlock

after issuing the above look at the Nabi screen and use volume keys to OK the unlock.

3) Enter fastboot mode (as described above)

4) Test and/or flash TWRP to your device.

Extract the TWRP download and place recovery.img in the same folder as your fastboot.exe

Run the command to test out TWRP

fastboot -i 0x0489 boot recovery.img

or this command to make it permanent

fastboot -i 0x0489 flash recovery recovery.img

5) To boot TWRP from power off. Press and hold power and vol up(different then fastboot and vol down)

6) MAKE A BACKUP! If it's like mine the swiping will be hard to start the backup, but just do it. The Nabijr should be in an unmolested(unrooted) condition with your personal info erased if you followed this. I can guarantee one of your fellow Nabi JR owners will at some point needs this so help them and help yourself. Now put a copy of that backup on your computer.

7) When TWRP exits it will ask if you want to root the device. It is hard to swipe on mine, but you can do this instead of the motochopper. We had some trouble with the Gapps for 4.1.2 on XD, will be interesting to see if it works here.

TWRP 2.6 for Nabi JR 16GB

To get your recovery back to stock if you flash TWRP:

Stock Recovery for Nabi JR 16GB

device tree source: https://github.com/aicjofs/android_device_fuhu_juniorb

TWRP source: https://github.com/TeamWin/Team-Win-Recovery-Project/

If it works for everyone I will try and build an auto installer type script at some point, but no promises, I barely had free time to figure this out.
[Miscellaneous Android Development] Archon810:
Trying this at my earliest convenience. Thanks, man. You're a wizard.
[Miscellaneous Android Development] Eric Karz:
Master aicjofs at it again ...lol

on the 4 gig if the usb is plug in the touch screen goes wacky

(enable show touches to see what happens)

Was the 16 gig jr science like the nabi xd ?
[Miscellaneous Android Development] aicjofs:
I read some things about the touchscreen. USB was one of them but it didn't seem to make a difference. There was also talk about a different device where screen brightness made a difference. I found this devices brightness adjust in the init.rc and tried "echo X > /sys/devices/platform/pwm-backlight/backlight/pwm-backlight/brightness" where X is a value between 100 and 1. Didn't make a difference either. I made a special TWRP with TWRP_EVENT_LOGGING := true. (It isn't in the one I posted, just a special test one) Then in the console you can see touch info. It is constantly getting false touches.

As for science. This was in a lot of aspects easier then the XD. Bootloader was obviously more work, but I'd say rooting was easier. Although the search for a working exploit was a bit of work, at least there was one, unlike the XD when I had to string a couple together with a few mods to the code.

EDIT: I saw on twitter a few weeks ago that jmz has a cool looking Android app that is like a TWRP frontend. Or at least that's how I saw it, like you do what you want to do in the app, and then it makes an openrecoveryscript and boots in TWRP and does it? That was what I guessed when I saw it but I have no idea. As long as you have a bootable android it would get around these touch problems.

I have never played with it myself, but have been meaning to https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en
[Miscellaneous Android Development] Archon810:
Yeah, the 4GB while on USB is a total cluster#$%^. Shocking that such quality control issues can get past the manufacturer and into production, but hey - having seen Nabi's products and organization, I'm not surprised at all.
[Miscellaneous Android Development] Archon810:
So far:

- TWRP flash worked like a charm.

- The screen responsiveness is indeed awful in TWRP.

- I found that it's impossible to swipe unless you use this trick: hold one finger at the beginning of the swipe, then start tapping with another finger where you're supposed to end it. The system thinks you've done a full swipe. Just plain swiping is impossible.

- In TWRP, it's impossible to use certain features, like auto-rooting, or fixing root that pops up when TWRP is about to exit because it seems like it's clicking by itself continuously right in the middle of the screen. If there are any buttons there or checkboxes, they get pushed automatically. Resolving this would likely resolve the whole touch problem above.

- Flashing gapps-jb-20130301-signed.zip starts crashing the keyboard immediately and turns the tablet unusable. I'm still looking into figuring out how to fix that.
[Miscellaneous Android Development] Archon810:
Here's the keyboard error btw:

E/ActivityThread( 1083): Failed to find provider info for com.android.inputmethod.latin.dictionarypack
E/AndroidRuntime( 1083): FATAL EXCEPTION: InitializeBinaryDictionary
E/AndroidRuntime( 1083): java.lang.UnsatisfiedLinkError: Native method not found: com.android.inputmethod.latin.BinaryDictionary.openNative:(Ljava/lang/String;JJIIII)J
E/AndroidRuntime( 1083): at com.android.inputmethod.latin.BinaryDictionary.openNative(Native Method)
E/AndroidRuntime( 1083): at com.android.inputmethod.latin.BinaryDictionary.loadDictionary(BinaryDictionary.java:101)
E/AndroidRuntime( 1083): at com.android.inputmethod.latin.BinaryDictionary.<init>(BinaryDictionary.java:77)
E/AndroidRuntime( 1083): at com.android.inputmethod.latin.DictionaryFactory.createMainDictionaryFromManager(DictionaryFactory.java:60)
E/AndroidRuntime( 1083): at com.android.inputmethod.latin.DictionaryFactory.createMainDictionaryFromManager(DictionaryFactory.java:86)
E/AndroidRuntime( 1083): at com.android.inputmethod.latin.Suggest$1.run(Suggest.java:136)
W/dalvikvm( 1083): No implementation found for native Lcom/android/inputmethod/latin/BinaryDictionary;.openNative:(Ljava/lang/String;JJIIII)J
W/dalvikvm( 1083): threadid=11: thread exiting with uncaught exception (group=0x41fd62a0)
I/Process ( 1083): Sending signal. PID: 1083 SIG: 9
I/ActivityManager( 269): Process com.android.inputmethod.latin (pid 1083) has died.
W/ActivityManager( 269): Scheduling restart of crashed service com.android.inputmethod.latin/.LatinIME in 5000ms

---------- Post added at 09:49 AM ---------- Previous post was at 09:19 AM ----------

Keyboard error fixed by flashing the Google keyboard (LatinImeGoogle.apk) from, say, http://xdaforums.com/showpost.php?p=40000860&postcount=74 and deleting the one that shipped with Nabi (LatinIME.apk).

---------- Post added at 09:53 AM ---------- Previous post was at 09:49 AM ----------

What the hell, now the software Back button starts Google Now. Argh.

---------- Post added at 09:54 AM ---------- Previous post was at 09:53 AM ----------

Woo, YouTube finally compatible. On the 4GB Nabi, I had to sideload some old-ass version, that update through the Play Store.

---------- Post added at 10:01 AM ---------- Previous post was at 09:54 AM ----------

Reboot fixed the Google Now back button issue. Wonder what it was...

---------- Post added at 10:09 AM ---------- Previous post was at 10:01 AM ----------

Ha! Nope, it's still doing it, but I figured out when - only in portrait. In landscape, it acts as a normal Back button. What the #$%^?
[Miscellaneous Android Development] aicjofs:
Ok so that sucks about the touchscreen issue. I was hoping it was somehow just mine because I don't really have an idea on why it's doing that. It is constantly clicking somewhere towards the center of the screen, I enabled a debugging feature in a personal build that shows the touchscreen input.

As far as the other issues. This is Jellybean 4.1.2 isn't it? I don't think you should be flashing the 20130301, that's for 4.2.1 or 4.2.2 I'm pretty sure. I think the last for 4.1.2 was like 20121011 or something. Also we had the same exact problem with Google Now on the Nabi XD. We used a modified one that should be in the NabiRootXD program. http://xdaforums.com/showthread.php?t=2207499 It should cure the issues from the sound of it.

Also did you give this a try? I mentioned it above and it might be able to get us by until the touchscreen can be figured out. https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en
[Miscellaneous Android Development] aicjofs:
OK I believe I fixed the NabiJR 16GB touchscreen issue. (Dees_Troy gave me the pointer on where to look. So thank him.)

Same download link as before

TWRP 2.6 for Nabi JR 16GB
[Miscellaneous Android Development] Archon810:
Recovery screen fixed!! Fantastic.

Out of curiosity, what was it?

---------- Post added at 05:31 PM ---------- Previous post was at 05:26 PM ----------

I did flash gapps-jb-20130301-signed.zip at first, which wasn't recommended, got the keyboard crash, then tried flashing gapps-jb-20121011-signed.zip, but the crash didn't go away. So I'm not sure if the keyboard would have crashed if I only flashed gapps-jb-20121011-signed.zip, but I guess I'll never know now unless someone confirms it. Either way, my fix works in case someone has the same problem.
[Miscellaneous Android Development] aicjofs:
The accelerometer(lis3de_acc) was giving touch inputs(which of course were false touches). It needed to be blacklisted from TWRP as input device. Code change to source at twrp/minui/events.c at line 163

old

if (strcmp(e->deviceName, "bma250") == 0 || strcmp(e->deviceName, "bma150") == 0)

new

if (strcmp(e->deviceName, "bma250") == 0 || strcmp(e->deviceName, "bma150") == 0 || strcmp(e->deviceName, "lis3de_acc") == 0)

I think gapps201201011 will work as I did install it but never did much with it. I've always had issues when I mess up the keyboard it's a pain to get back. I did use the one from NabiXD though which removes the Google Now. I also had to clean up the install as it left a stray odex.
[Miscellaneous Android Development] Archon810:
Thanks for the explanation, makes total sense.

I don't think you should worry about a stray odex, unless you have OCD - it will just be ignored. And Google Now can just be uninstalled/disabled if you did already install it, can't it? Although, I'd rather figure out why it reacts to the back button only in portrait.