yashsingh1/xdaforums huggingface dataset:
[Motorola Photon Q 4G LTE] arrrghhh:
You have to make sure the key matches EXACTLY!!! Any typos, extra characters, spaces, etc will cause it to fail.

Good luck.
[Galaxy S III Q&A, Help & Troubleshooting] spoonymoon:
Hi, after installing cm10.1 and reverting back to 10 again my phone dosent connect to any mobil networks, and after looking in about phone theres no imei (or its a false one) i´ve tried to flash other modems, but same result!

So what to do now? suppose stock firmware is the only thing to get imei back? or am i wrong?

Is there any other solutions to recover imei? and no i dont been smart enough to do a backup - damm:crying:

Please advise :eek:

Thanx a bunch in advance
[Galaxy S III Q&A, Help & Troubleshooting] f0xy:
Did you not even back up efi folder?
[Galaxy S III Q&A, Help & Troubleshooting] xSpeced:
Well, good luck without an efs backup. I'm not sure if Kies firmware initializations helps.
[HTC One S] hbkmat:
I notice lately I have been having sim card errors when I wake up the morning. I am having to restart the phone to get connections working. This was not a problem before is this baseband related or something?
[HTC One S] mugetsu666:
I've had them for a long time and whenever I've talked with T-Mobile, they tell me it's a common issue with the phone.
[HTC One S] Goatshocker:
I read about it quite a lot before getting my S. Apparently the S is kinda sensitive with sim cards.

My card, for example, didnt work at all in the S. I had to get a new one from my provider.

So, Id say you need a new sim card. I wouldnt call it an "issue with the phone", its just picky ;)
[HTC One S] mugetsu666:
I'm on my 5th sims from my provider. Lol it's a know issue, especially with the tmous version. At least that what the tmob tech told me
[General Questions and Answers] JavaMocha:
I currently have a Motorola Photon 4G running Android 2.3.4 and build 198_7. Simple question: If I unlock, will I be reset to stock?

The reason I ask...

Not long ago, I was running an installation of 198_6. For grins and giggles (and because I knew I'd be flashing the 198_7 SBF later), I flashed derpunlock.sbf, and successfully unlocked. I got into CWM 5.0.2.8 just fine. But after unlocking, I found my phone had been reset to stock. All I had done was flash derpunlock.sbf with RSDLite, then unlock using fastboot. I didn't think that would send me back to square one with a covert factory reset, but it did.

I should have unlocked right after updating to 198_7. But I didn't, because I'm an idiot. Now, I've put hours into configuring my phone, and don't want to lose it with a surprise reset after unlocking. Backing up with MyBackup and Titanium Backup (which I've done) help, but they don't fully cut it.
[General Questions and Answers] JavaMocha:
Does anyone know? Please.
[General Questions and Answers] Gizmoe:
Yes unlocking will usually do a factory reset. It will inform you on the phone and ask if you want to proceed though. I have never used a Motorola though, so you may want to ask in the specific Q&A forum for your device.
[General Questions and Answers] JavaMocha:
Thank you very much. I certainly wasn't prompted the first time I unlocked and a reset was done. I guess I don't see why it would be any different if I unlocked again.
[Miscellaneous Android Development] katinatez:
Tried your recovery, all I could say it's perfect. Touch screen in TWRP recovery is 100%. Have ben plagued with the touch screen error in recovery prior to aicjofs latest 2.3.3.0 TWRP recovery.

jmztaylor, aicjofs, t499user, e2950 deserve the XDA Nabi 2 award. Have owned the tablet maybe 3 weeks, in that time was able to restore from soft brick, get a working gapps witout 'Android Upgrading", and new updated 2.3.3.0 TWRP recovery. Got to Love XDA community.

All we need now is our own forum :laugh:

Sent from my GT-I9300
[Miscellaneous Android Development] Eric Karz:
+ 1 on all that above

+ i wanted a updated version -

+ thank you

ps: *MY* nabi box says "ages 4-to 40" i think no matter what the age is

they all going to be happy with all this cool stuff.
[Miscellaneous Android Development] oniddy:
good job

Glad to see people are happy u made this

:good:
[Miscellaneous Android Development] knoxploration:
Great to see more development starting to happen for the Nabi 2, thanks!
[Miscellaneous Android Development] Eric Karz:
maybe its just me and i noticed today that i can not get in to Fast boot unless usb is plugged in.

anyone else getting the same ?
[Miscellaneous Android Development] aicjofs:
I have 2 responses from people where this version has touchscreen issues. It is for a 1.9.36(UK Version) and what I believe is a 1.9.34(Madagascar version) I updated the OP but it looks like you should only be using this on 1.9.37 right now.

I always have usb plugged in so I never noticed.
[Miscellaneous Android Development] Eric Karz:
CWM

aicjofs are you doing a CWM recovery for the nabi 2?
[Miscellaneous Android Development] aicjofs:
I did a CWM for the Nabi. Everything worked except I was having a hard time mounting the /sdcard properly. The internal sdcard as we know it is actually in /data/media(so it's on the data partition), I was able to manually "mount" it(symlink) through shell, but I couldn't make it auto mount. I'm sure it's something simple through init.rc or something but I couldn't get it working right to mount at boot time. On a side note to that, since it's on the data partition care has to be made that if the data partition is wiped that the sdcard is moved off and then back. I'm not sure if CWM does that with a loop device or something, just moves it or what, but it's dangerous. Lot's of devices have it set up this way so I think it would be accounted for, but I know TWRP accounts for it. I'm not sure extendcommand was working correctly either, it appeared to, but log was complaining about it. As it was I had early feedback that new TWRP was fixing touchscreen issues so I put it on back burner, as part of the reason for even building CWM was for those that had touchscreen issues. Only real change was to the BoardConfig.mk for BOARD_HAS_NO_SELECT_BUTTON to make CWM "function" less mounting problems.

Now I'm trying to decide if we are better using /dev/block/platform/sdhci-tegra.3/by-name in the recovery.fstab for those Nabi's with different partition structure. jmztaylor was kind enough to give me his ear and I think we should do tegra by name. No reason we shouldn't have one TWRP version, 2 at most. Once I get TWRP working for all Nabi versions for sure, I will probably revisit it.
[Miscellaneous Android Development] aicjofs:
Updated to symlink partitions for Nabi's that have been found that might contain a different partition structure.

Nabi kernel version added for easier troubleshooting

Nabi logo
[Miscellaneous Android Development] Eric Karz:
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
[Miscellaneous Android Development] aicjofs:
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 ;)
[Miscellaneous Android Development] Eric Karz:
before i forget http://xdaforums.com/showthread.php?t=1905674&page=131&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
[Miscellaneous Android Development] Eric Karz:
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 .
[Miscellaneous Android Development] aicjofs:
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.
[Miscellaneous Android Development] Eric Karz:
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.
[Miscellaneous Android Development] Eric Karz:
I see that Twrp is up to 2.4.0.0

Is there anything that nabi 2 users would benifit from it ?
[Miscellaneous Android Development] miggs0817:
Re: [recovery][nabi2] twrp 2.3.3.0

I too am wondering this!
[Miscellaneous Android Development] aicjofs:
Seems interesting, I'll see about making a test build sometime this week unless someone beats me to it.
[Miscellaneous Android Development] aicjofs:
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
[Miscellaneous Android Development] Eric Karz:
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
[Miscellaneous Android Development] aicjofs:
I built it really quick maybe I missed something. That said I just spent an hour playing with it, I set time and it stayed after reboot. I also backed up to internal and external and restored without any error. After rebooting into Android both backups are still there. The only issue I see is that it isn't mounting the internal sd at /sdcard. It just makes an sdcard file in /. Of course everything is still present at /data/media, and if you "Install" tab and select internal it goes correctly to data/media. But it's not mounted at /sdcard like it previously was. Did you flash it or just load to RAM. This is peculiar, usually I can duplicate the issue.
[Miscellaneous Android Development] Eric Karz:
i flashed it with lab - replaced 2330 with the 2400 - quit the process right after it installed-

i tried to back up to my 16 gig external - i had one internal fron lab i could not get that to work ... like the others in 5 seconds it said it was done .

i will try it again if ya want - tell me how you installed it and i will do it the same way .
[Miscellaneous Android Development] aicjofs:
It's possible the build is buggy. You'd think something simple like the clock would work for both of us. Did you delete the .twrp config file in TWRP folder? Maybe that had something to do with it? Maybe just try something quick and easy like backing up boot only and at least seeing if the file is created. It sounds like yours wasn't even creating the file. I know they made some improvements that increased speed a lot but ya I'm thinking 5 seconds is a bit quick. haha.

I'm in the middle of redoing my build virtual machine, so I'll be starting fresh here soon, and will try and make a new one when I get done.
[Miscellaneous Android Development] Eric Karz:
any time i updated twrp ..just flash and that's it. yeah i don't think its a good sign that we both came off the same version and the clock worked for you and not me . The Recovers makes me 100 % clueless- like on my a500 i use thors recover-and his Jb23 and it runs great -even the vulkano app i use on it plays for hours with out crashing( i posted about it on here). i wanted Twrp in it but it just wont work with out some kind of problem.

At least we have 2.3 to hold us over until you and JMZ make us a JB version for Nabi haha.
[Miscellaneous Android Development] DZLRULZ:
2.4.1.0 was released to fix mounting external issues..thought you might be interested.

Sent from my Viper4G3 Ev_O_nE using Forum Runner
[Miscellaneous Android Development] aicjofs:
I did a backup/restore, zip install, and time change. Obviously only for those that want to test and live on bleeding edge. Looking through other 2.4.1 threads not seeing as many issues as 2.4 had.

TWRP 2.4.1.0 Download
[Miscellaneous Android Development] Eric Karz:
2.4.1.0 feed back

Every thing I have tried works – time/Backup/Restore/

thank you sir Much appreciated for the updated version
[Miscellaneous Android Development] aicjofs:
TWRP 2.4.3.0 Download
[Miscellaneous Android Development] Eric Karz:
2.4.3.0 feed back

At first i thought this was a april fools joke because the screen went black had to look at the date today...lol

i see this version has a time out for the screen

Every thing i tested time /back and restore /file manager all worked

thanks aicjofs
[Miscellaneous Android Development] aicjofs:
TWRP 2.4.4 for Nabi2

What's new in 2.4.4.0:

Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)

More fixes for the file selector

Switched from using busybox md5sum to a direct C function call

Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again

Update exFAT to latest commits

Added a build flag to disable using the ioctl for screen blanking

Nabi2 specific: Theme change, new Kernel based on Nabi v2.0.5

TWRP 2.4.4.0 Download
[Miscellaneous Android Development] Macanage:
Having a brain fart. Not sure how to get this recovery installed. Tried flashing through TWRP but failed. Unzipped it and put the "recovery.img" file on the root of sdcard. Tried "flash_image recovery /sdcard/recovery.img" in terminal, and that did not work. "flash_image" not found. Do I need to do this through the bootloader?

Edit: Never mind! Just read up top needs to be flashed through fastboot. Duh!
[Miscellaneous Android Development] Macanage:
2.4.4.0 Seems to work great and its nice to have the updated Kernel. Awesome Job and thank you for all the hard work!

On a side note, I have the game temple run and temple run 2 on the Nabi and have been trying to play them. It seems it will jump and slide just fine but when trying to turn a corner it jumps instead of going right or left. I was hoping the new kernel might fix it, but no luck. Any Ideas how to fix this issue? Subway surfer works like it should and has very similar running jumping and sliding. Thanks a ton...
[Miscellaneous Android Development] aicjofs:
I saw the same comment on the Nabi Facebook page. Seems like others are having it, unless that was you! haha. I'm not sure might be touchscreen driver, have you had the Nabi since the beginning? Did it work better on one version or the other?
[Miscellaneous Android Development] Macanage:
Nope it was not me on the Nabi Facebook page but glad to know it is not just me. It has never worked right on any of the versions and I have had two of them since Dec 2012. Current with the 2.05 rom and driver. Thanks for all your help, great work!
[Miscellaneous Android Development] Eric Karz:
I tried temple run 1 at first I thought it didn't work . then I saw I had to swipe on that yellow arrow just right or you go caput haha
[Miscellaneous Android Development] aicjofs:
TWRP 2.5.0.0 for Nabi2

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] Eric Karz:
aicjofs

Thanks for the 2.5.0.0 update
[Miscellaneous Android Development] DarkAngel:
Been using 2.5 since the 21st with no problems. Before I did I flashed back to stock 1.9.37 and updated to 2.0.5 as " I " have been lagging and just too busy to update my Nabi2 since the release of the OTA update. Anyways, thanks a bunch! Love the Nabi theme ( yea I was still on 2.3.3.0 ) .
[Miscellaneous Android Development] Waleslie:
Incompatible backups?

Are some backups incompatible with different versions of TWRP? I have the latest OTA update (2.0.5) and have TWRP 2.5.0.0 installed. It seems like some of my backups (made with Nabi 1.9.37 and I think TWRP 2.2.2.1) are incompatible. I pick them from the list in under TWRP's restore tab, but nothing happens. If I revert to the older version of TWRP, the backups restore just fine.

Am I doing something wrong?
[Miscellaneous Android Development] n3wt:
I'm pretty sure it should work, no clue why it doesn't. Maybe you've found a bug in the 2.5 version...perhaps you could send your log to the TWRP guys as per this note in the changelog:
[Miscellaneous Android Development] Waleslie:
I picked up a new Nabi 2 today that actually came with 2.0.5 installed already. When I install TWRP 2.5.0.0, there seems to be a problem with the touch screen. I have to hold down for quite a while for it to register a touch. It makes it impossible to swipe... hence I can't accomplish much in TWRP. I tried TWRP 2.4.3.0 and had the same issue.

Touch screen works fine when using the tablet outside of recovery.
[Miscellaneous Android Development] aicjofs:
This might be the first non UK version one I have heard of a touchscreen issue on. It's pretty interesting because we are having a touchscreen issue on the brand new 16GB Nabi JR as well. 2 questions:

1) In the 2.5.0.0 version if you click on "install" it opens a menu with directories on the left and a drill down of the selected folder on the right. Is there a bar through middle that flickers as you touch the screen?

2) Have you tried going all the way back to 2.2.2.1? or trying the UK version one? If we can find one that works for that tablet we might be able to build a specific one that works on a later rev.

Also this is alpha but something you can try to at least do some TWRP functions. https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en
[Miscellaneous Android Development] Waleslie:
1) Yes, I get the flickering bar.

2) The 2.2.2.1 and the UK version both seem to have no touch screen response at all.

I'll look into the alpha thing...