yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Android Development] andy hall:
Just installed the latest and seems to be working well. Will report back in a couple of days.
[Galaxy S 4 i9505 Android Development] canodroid15:
New Weeklies live on site, go get em' folks! And as always ENJOY! https://www.teamoctos.com/weekly-builds/
[Galaxy S 4 i9505 Android Development] Soldier50:
Air gesture

Does it have air gesture?
[Fuhu Nabi 2] wither719:
My brother has a Nabi 2 which was rooted, and we recently received an update from Jelly Bean to Kit Kat. We (more like I) tried to do this without unrooting, and it ended up boot looping for around 4 hours before I intervened. I downloaded the latest stock ROM I could find, and I went into TWRP to flash it. Every single time, it says "Unable to flash zip '/external_sdcard/246stock.zip', then tells me that there is no operating system installed. I tried upgrading TWRP, and got 2.8. Touch was very close to unresponsive. I also tried 2.7.1.0, and 2.7.0.0, and also every other version I could find. Every single version either couldn't flash it, couldn't mount anything, or touch was unresponsive. I downloaded all the recoveries from xda's Nabi 2 page. None of them work. Is there anything I can try to fix this?
[Fuhu Nabi 2] aicjofs:
You don't "install" that zip, you "restore" it.

Use TWRP 2.7.0

Download this 3.0.13 stock ZIP

Use an external SDcard and make a backup of just "boot"(this is a setup for next step)

Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.

- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder

- Unzip the 3.0.13 stock you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 3.0.13 ROM.

- Download this 3.0.13 bootloader

- Copy the zip to the SDcard. This will be for the bootloader update.

- Put sdcard in Nabi

- Go to "restore tab", and find the backup under the "yourfolder" you made and unzipped the files to.

- You should be able to select boot, system, and addon and skip the others.

- If everything restores then go to TWRP "install tab", find the bootloader zip you downloaded and install it.

- Reboot
[Fuhu Nabi 2] the_xlr8r:
ok, im in BIG trouble with my daughter... Yep, I managed to brick her Nabi 2 following this tutorial and I dont know really know where I went wrong. But now when the Nabi 2 is powered on, all I see is the nabi logo, but no OS...or TWRP!... eeek!

I had been trying for days to get a stable TWRP on and Gapps, I did get TWRP v2.3.3.0 up and running at one point, but no Gapps installed and no SuperSU to be found, it was as if it wasnt rooted at all. (even after reinstalling both within TWRP). Then of course i found a thread that said Gapps didnt work on nabi 2 version 2.1...!

I do have a TWRP backup folder saved but i dont seem to have any way to get it back onto the Nabi 2... as its no longer detected in windows like it was before..? (despite the ding sound windows makes when plugged in ?).

I can only get to the 1st bootmenu (holding Vol+ and Power ok. Selecting any options results in little (or nothing) happening... i.e. when selected;

Boot Normally - nothing happens, nabi logo only. And if i leave it too long, it freezes here and i have to reboot.

Fastboot Protocol - with usb connected to pc, i do get to the Bootloader menu with, Bootloader, Continue, Reboot-bootloader, Reboot and Poweroff , options. The Pc 'dings' to indicate detection, but is not detected by adb ?

Recovery Kernel - nothing happens, nabi logo only.

Forced Recovery - screen goes black, then nothing follows.

on Fastboot Protocol menu, if i select the options;

Bootloader - without touching anything, pc dings to indicate some connection...?

Continue - if selected, i hear windows drop whatever connection it had previous..?

Reboot-bootloader - nothing happens, nabi logo only.

Reboot - reboots, then nabi logo only.

Poweroff - nabi 2 shuts down.

As it stands , all i can access are these options above, but i dont seem to have a way of getting windows to communicate over the usb cable...? that said, with pdanet running, it does detect the nabi 2, but of course it cant talk to it as I cant get to pdanet on the nabi 2... just gives some weird error that im using wrong adb , or it just cant connect to the nabi.

Tried using Nabilab v2, but device is not detected...?

...so i would be most grateful if some nabi 2 guru could assist with any possible resurrection, otherwise I will remain "the worst daddy ever"...ugh!

cheers in advance
[Fuhu Nabi 2] aicjofs:
Wow I havent been on here in ages, got an email about your quote though.

I have forgotten so much about these Nabis over the last decade?! So how did you get to the non-booting part? You were able to complete the steps above all successfully? or did it fail at some part?

If you successfully flashed 3.0.13 bootloader with install in TWRP then I don't think you will be able to boot the TWRP you had on the device. That would be my guess at this point why you can't get to recovery.

https://xdaforums.com/t/nabi-general-information.3229119/

Read the above. You are pretty much stuck in having to use fastboot.(The driver must be installed if you keep hearing the ding). You will need a fastboot.exe if you don't have one. Search minimal ADB and fastboot. I'd download TWRP 2.8.7 and try to use section 7 to get it on device i.e "fastboot flash recovery recovery.img"

If you unsuccessfully flashed bootloader then you need to use TWRP 2.8.5 Files should be in that thread also or my AHF https://androidfilehost.com/?w=files&flid=41987.

Ill check back later
[Fuhu Nabi 2] the_xlr8r:
Hi, thanks for getting back ...

Q. So how did you get to the non-booting part? You were able to complete the steps above all successfully? or did it fail at some part?

A. yes i followed the tut but once i rebooted that was the end and where my big problems began.

Q. If you successfully flashed 3.0.13 bootloader with install in TWRP then I don't think you will be able to boot the TWRP you had on the device. That would be my guess at this point why you can't get to recovery.

A. Yes, using TWRP i installed 3.013 bootloader.

Q. You are pretty much stuck in having to use fastboot. (The driver must be installed if you keep hearing the ding). You will need a fastboot.exe if you don't have one. Search minimal ADB and fastboot.

A. This may be the issue, i may be using older version of adb and fastboot. I already had minimal adb stored away, so i experimented by copying the adb files over to my NabiLabFull folder, this time it was green (detected) ... sort of...

View attachment 5717961

ill have a read at the links you provided and will report back soon, thanks.
[Fuhu Nabi 2] the_xlr8r:
ok... getting somwehere but not where i expected....

i tried to install the 2 x TWRP versions you mentioned but it wouldnt load into either. So i reverted back to trying 2.3.3.0 and bingo , im in... but shouldnt 2.8.5 or 2.8.7 have worked since Im now showing Navi version as 3.0.13.. (was previously on 2.1.9) ?

im sitting at the TWRP 2.3.3.0 menu now , and still have Nabilab running but am afraid to do anything next lol.... where should i proceed to, from here ? Should I be installing any particular version of Root and Gapps now that im into TWRP 2.3.3.0 (or even try to update TWRP beforehand ?

PS. I am using a UK nabi 2 , in case that makes any difference to files im downloading to it ?

cheers

View attachment 5717999

View attachment 5718003
[Fuhu Nabi 2] aicjofs:
Im not at a location where I can look at the Nabilab script but as I recall the script is pulling it from build.prop on the system partition. This would indicate to me that the system partition flashed, and so likely the addon and boot. Also the fact that you can't boot another TWRP besides 2.3.3, and the normal boot hanging at the logo leads me to believe that the bootloader was not updated.

Again I'm trying to remember here....but as I recall the bootloader for the Nabi is passing a commandline to the kernel. You have a kernel in the 3.0.x ROM and an identical kernel in TWRP 2.8.7. The fact that neither boot would mean to me the bootloader is original and passing the old commandline to a newer kernel.

You have to get things in sync. The bootloader and the boot.img(kernel+ramdisk) have to match each other. The way that makes the most sense is to install the bootloader3013 zip through TWRP. You already tried that obviously and that's how you got here.

1) You could try the bootloader install inside TWRP again, seems like you can recover if it fails now. Of course if it works then 2.3.3 TWRP should no longer work(which is what I thought happened and why you couldn't boot TWRP initially) so you'd have to try the 2.8.7 at that point.

2) Since the bootloader is original(or Jellybean-ish) you could restore your backup and regroup.

When I get to a place I can look at the install script for the bootloader maybe I can jog my memory. I thought it just dd to mmcblock0
[Fuhu Nabi 2] the_xlr8r:
ok. thanks.

so i make no more mistakes, ill check I have all the correct files i need with you first...

I have saved to external sdcard, KK3013bootloader.zip containing;

META-INF

android-info.txt

blob

I have also saved to external sdcard, 3013stock.zip (unzipped)

I have also saved to external sdcard, some old Gapps.zip version (no idea if recent or not) ?

I have also saved to external sdcard, some old root.zip version, again, not sure if correct ?

I think I'm breaking it when i get to here...

1) You could try the bootloader install inside TWRP again, seems like you can recover if it fails now. Of course if it works then 2.3.3 TWRP should no longer work(which is what I thought happened and why you couldn't boot TWRP initially) so you'd have to try the 2.8.7 at that point.

....So, if im in TWRP 2330 now, and I install KK3013Bootloader.zip, it will then no longer boot to TRWP ... is that correct? If so, how then do i get TWRP 285 or 287 working ?

....think i'm getting a smidge lost at this bit lol

[update] - cannot install anything in TRWP 2330 as its not recognizing my 64gb sdcard (formatted to fat32) ... does it have to be a certain formatted type FAT/FAT32/EXT12/3/4 or other ?

Also, i couldnt find a working download link for anyone's scripts... many thanks
[Fuhu Nabi 2] aicjofs:
For #1 You install the bootloader zip. Swipe install then reboot. It won't do anything at first because it installs the "blob" (which is the bootloader) to the staging partition. Reboots for 15 seconds and installs the blob. The only way at that point to get a newer TWRP is by booting bootloader to fastboot, and then fastboot flash the newer TWRP on to it.

No it should recognize fat32. There was something about storage being realigned between versions too. You could always use adb too I guess.

adb push bootloaderXXXX.zip /data/media ?

The end of this thread may be usefully too

https://xdaforums.com/t/recovery-nabi2-twrp-2-3-3-0-2-8-5-0-testing.2074501/page-6

The original TWRP posts

https://xdaforums.com/t/nabi-2-root-and-gapps-install.1905674/page-130#post-59452953

https://xdaforums.com/t/nabi-2-root-and-gapps-install.1905674/page-132#post-62826514
[Fuhu Nabi 2] the_xlr8r:
thanks, am i downloading the correct TWRP zip ?

TWRP 2.8.5.0 Released

TWRP 2.8.5.0 is out now for all currently supported devices.

twrp.me

Which version Gapps should i be using ?

The Open GApps Project

OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.

opengapps.org
[Fuhu Nabi 2] aicjofs:
No download the TWRP in one of the last 2 links I sent. First is 2.8.5, and other is 2.8.7

I thought on KitKat Fuhu actually has Gapps? You will let Playstore update it to whatever version they stopped with for KitKat support.

There is always NabiLabGUI2015 https://drive.google.com/file/d/1x_4btZE2VzYWJ_aag9U20ubIGY9NXjcN/view?usp=sharing

I never really finished the project but it might be easier as it has all the recoveries already in it. Stay away from NVflash/APX stuff for now.
[Fuhu Nabi 2] the_xlr8r:
ok , sorry i already went ahead and installed bootloader3103

then ADB'd on twrp-recovery-KKNV7AUS-287.zip

I can now get TWRP 2.9.7.0 loaded up, but still no OS booting once i have rebooted the nabi2...

maybe the OS is missing ..? how do i reinstall it ? (i tried doing a restore by using the old TWRP backup i had from the start , by pasting in the 3013stock files) but that didnt work.

....still stuck, but getting closer :)

View attachment 5718125
[Fuhu Nabi 2] aicjofs:
No I think we are good, the plan was for you to flash bootloader to proper, and that seems to be the case.

It might not be missing the OS, it might need data/media wiped(factory reset). Of course the tablet is completely wiped during that, don't know if the daughter had stuff on there.

Either way it doesn't hurt to try and restore it again. When you say pasting the 3013 restore files, you mean in the folder with your backup? Over top the files or just a folder in the same folder as the backup?

The fact that Nabilab says 3.0.13 makes me think the system files were restored and not missing. You did all this through NabiLab or TWRP?
[Fuhu Nabi 2] the_xlr8r:
hi , tried every way i could

yes, i copied and pasted the 3013stock files over the top of the old backup and tried to restore, still didnt boot to OS.

tried your NabiLab2015 , UK menu didnt open so i just used the US menu.

tried to follow step.2 "Flash Full" , seemed to start ok , but then..... this happened...

Note: using NabiLab2015, I skipped using step 1. to download stock 3013, as it wouldnt do it, so i copied the 3013.zip i had downloaded earlier into this folder. which seemed to allow step 2 to work...

whats best option to use now that it failed at 30% install ? thanks

View attachment 5718161
[Fuhu Nabi 2] aicjofs:
Looks like the ADB connection reset. This step is copying the files to the tablet to data/media. It failed at addon. Either cable to computer had a glitch or maybe data/media(internal storage) is full. You can retry again, it didn't flash anything to device at all.

Maybe in TWRP, go to advanced, terminal and type bdf? See if filesystem looks ok. Seems like a cable issue right now though
[Fuhu Nabi 2] the_xlr8r:
[UPDATE]

thankyou sir for all your help.

after another try on a Flash Full , everything was installed and it rebooted and updated.

i'm so glad your email still worked after 10 years of not looking at this nabi stuff , otherwise this nabi of mine would be in the bin before now.. lol.... @)

..couple of things, now that its on android 4.4 etc , is it safe to perform any further updates ?

Its running as a US version now, will that affect anything with me being in the UK ?

still not able to get external sdcard detected in TWRP... any ideas ?

many thanks
[Fuhu Nabi 2] aicjofs:
No problem, havent thought about Nabi's in probably 2 years. Some of my favorite memories were helping people on Christmas Day, or this Dad from Brazil on his son's birthday, Mom from Italy etc, etc and imagining the kids didn't even know all the panic haha.

You are pretty much done at 4.4. Really no OS level updates to do. Fuhu never did anything else, the source code they gave us was worthless for kernel building, and honestly this Tegra chipset was at it end anyway. Like I said earlier Google play services will update to the latest for the kitkat version, and that will be it. Apps that still support Android this old will have updates of course.

EDIT: Its funny about NabiLabGUI2015. I get emails about my google drive link because link is so old and I have to manually share it the zip for it. I forgot that it would have been really useful if I ever finished it.
[Fuhu Nabi 2] the_xlr8r:
most of the trouble I was facing was working links on the forum, hardly any worked and I spent days searching.

even searching for NabiLab2015 proved impossible. Only for you providing a new link, i would never have found it... maybe you could update some old posts with fresh links, and that will make some old-timers like myself, feel young again trying this stuff lol.

but andyways, thank you again so much for your help. theres not many out there in this day and age, that would have bothered... so i salute you sir!

kind regards

stay safe

ps. my daughter says Im the best dad in the world again ... I told her the wizard on the tinterweb fixed it using some of Gandalf's magic....
[Verizon Samsung Galaxy S 4] ShadyPossum:
just want to confirm, this is NOT SafeStrap compatible?
[Verizon Samsung Galaxy S 4] jhr5474:
It says it uses the Cyanogenmod based kernel so no it is not safestrap friendly.:(
[Verizon Samsung Galaxy S 4] Grommish:
Correct. If you are above the MDK baseband, you're limited to TouchWiz.

Updated ProjectDB for Firmware Requirements..
[Verizon Samsung Galaxy S 4] Alxoom33:
Congratulations! Would like to try. Is there a DL link? Couldn't find it in the OP.

Thanks![emoji106]

---------- Post added at 02:27 PM ---------- Previous post was at 02:07 PM ----------

Sorry, I am not sure how to use a spoiler in TT.
[Verizon Samsung Galaxy S 4] Grommish:
There isn't anything like that is the OP. If you're seeing that, its TapaTalk doing it. I'd recommend the desktop version, as I do not use TapaTalk or the XDA Mobile app.

All of our releases, license information, and known issues can be found on our website www.teamoctos.com
[Verizon Samsung Galaxy S 4] Sir Lancelot:
I'm not finding it on the web version either.

Perhaps less subtly? I don't mean to be snarky but some of us live on our phones. I can't test what I can't access.

Sent from my rooted tri-corder
[Verizon Samsung Galaxy S 4] Grommish:
We even have a theme specifically for mobile devices. Check the Screenshots below for a step by step. :p:D
[Verizon Samsung Galaxy S 4] Alxoom33:
Good to know! But nobody will go there, unless directed to do so in the OP. I suggest linking your downloads page to the OP.
[Verizon Samsung Galaxy S 4] Grommish:
We've discussed it. At this point, across just the S3 and S4 devices, we've had something like 800 downloads. People are finding it.

Speaking only for myself, I'd rather anyone who either cannot or will not read the OP to move to another ROM. Flashing a device is a risky operation in the best of times. Anyone who says "I can't find" or "Why don't you just tell me", when it is literally the first thing after the logo, means that when they fail to do something and soft-brick their device (or in the case of the jfltevzw, hardbricks their device because they are safestrapped) then I have to listen to it and deal with it. Besides, it makes the entire project look bad.

I went out and got the XDA app, just to see what those who are looking at it see. See the screenshot below.

I will link you directly to a post, however, from the dev-blog entitled There be Dragons here in which I look at people's ability to treat their mobile devices like toys, rather than $700+ electronic devices. Any user who wants to be hand-held can do it in another thread. Flashing is as safe as we can make it, but I've personally had flashes go bad, and the ability to recover the device means following instructions. If anyone cannot figure out how to download the ROM, especially given the screenshot below, again, I'd rather not have them flash it.
[Verizon Samsung Galaxy S 4] Sir Lancelot:
Well. As a usability engineer with 15 years of working on UI and websites I can only say:

1. Blaming your users gets you nowhere.

2. Your level of adoption is in your own hands.
[Verizon Samsung Galaxy S 4] maximusmullivan:
Just stop already. It's on us as users to educate ourselves! We've all had to do it. Don't blame the dev! Not his fault you can't navigate the internet.

Sent from my Nexus 7 2013
[Verizon Samsung Galaxy S 4] Alxoom33:
I understand your point and agree that too many users do not sufficiently educate themselves prior to flashing.

Like a safestrap user who recently twice soft bricked his phone by flashing a gpe ROM. First in a slot, and then when told that he needed a custom recovery flashed it on the stock unsafe side.

However, a DL link in the OP just makes it more convenient for users. Just my opinion.
[Verizon Samsung Galaxy S 4] zekesamas:
Eazy enough to find for me [emoji102] thanks gonna give it a shot soon as my backup is complete. My current ? is running fine but has awful battery life so I'm hoping that this one is better.
[Verizon Samsung Galaxy S 4] cjkacz:
We've created a poll in our Gplus Community concerning our next release. We'd like your thoughts and would appreciate your feedback! Thanks

https://plus.google.com/+DonaldHoskins/posts/PAmttsqceN1
[Verizon Samsung Galaxy S 4] cjkacz:
New 5.1.1 build is up on website! Op updated

www.teamoctos.com
[Verizon Samsung Galaxy S 4] Otakulad:
Hi,

Thanks for working to update the S4 to 5.1.1.

I have a question to those out there currently using this ROM. I was running Danvdh GPE ROM and I could not get Netflix to work on mobile data. When I was on my home's wireless, it worked no problem. I then changed my ROM to Hyperdrive (4.4.2) and it started to work on mobile data again.

Has anyone tried to use Netflix on mobile data with this ROM? I'm curious if it is an issue with Netflix and Lollipop not liking each other, if it is something with my phone, or potentially something with the GPE ROM.

Thanks in advance and thank you again for all of your hard work.
[Verizon Samsung Galaxy S 4] focus242:
No BT issues so far
[Verizon Samsung Galaxy S 4] ktraub:
BT LE (Smartwatch e.g. Moto 360) issues remain

Looks like the Bluetooth LE issues are still there as it won't see my Moto 360.
[Verizon Samsung Galaxy S 4] reggie cheeks:
The latest build retires me. So satisfied. The dark theme is the best look of lollipop I've seen yet. I don't use bluetooth [emoji12]

Most excited I've been in awhile about a rom.

Many thanks Team OctOS!
[Verizon Samsung Galaxy S 4] Cilraaz:
Anyone else able to report their Bluetooth experiences with this ROM? I've been using Euroskank's CM12.1 builds and then my own. I have had continual Bluetooth issues with my car. It's my only complaint about this phone, so if this ROM is the one that was able to fix it, I'd love to know.
[Verizon Samsung Galaxy S 4] focus242:
I was in the same boat. No BT share FC issues with this ROM. I'm able to take calls and play music thru BT in my car with no problems.
[Verizon Samsung Galaxy S 4] Cilraaz:
I guess I'll have to try it to see if it fixes the issue for me. I'm guessing it can be dirty flashed over a standard CM12.1 build, since it's a CM base.

Edit: No dice. I flashed it over my CM12.1 build and was still receiving Bluetooth Share FC's. I wiped system, data, cache, and dalvik, then re-flashed the ROM. It came up as a fresh phone. I hooked it up to my car and while Bluetooth Share didn't crash, the audio didn't play beyond the first connection. If I turned off Bluetooth on either the phone or car and then re-enabled it, YouTube would lag and not play audio. I tried Play Music and Music also. It was actually worse than before as disabling Bluetooth and clearing Bluetooth Share data didn't fix it.
[Verizon Samsung Galaxy S 4] cjkacz:
Try factory reset and reinstalling just to make sure the slate is wiped clean.
[Verizon Samsung Galaxy S 4] Cilraaz:
Yeah. I did that. I said so in my edit.
[Verizon Samsung Galaxy S 4] focus242:
Its night and day for me. No BT share FCs at all. Music plays continuously and calls don't cause any FCs
[Verizon Samsung Galaxy S 4] natec003:
Do you use Pandora at all? The most recent cm builds do fine for me with everything besides Pandora over BT. It usually force closes after 2-3 songs.

Sent from my S4
[Verizon Samsung Galaxy S 4] focus242:
Spotify
[Verizon Samsung Galaxy S 4] stang5litre:
install

Read OP on MDK as far as flashing this do i just flash Rom and then flash the MD5 after? Or is the Zip for the rom sufficient. Never had to flash anything after besides maybe a Kernel. Thanks for your time. Oh and where do i get the Gapps at? the link in the OP is dead