Nabi XD 32 GB, model NV10B - Need to root - General Questions and Answers

I need to root a Fuhu Nabi XD 32GB tablet. Apparently there are different models of this exact same tablet. My model number is NABIXD-NV10B, so the product version is 1.0. The only root programs I can find on this site are for a different Nabi XD model that can be on product version 1.2.3 through 1.5.
I contacted Nabi and they told me the most up to date version for my model is 1.0 and there are no other versions I can install. The problem is the Android OS version for this Nabi product version is 4.1.2 and I need a much more recent Android OS so my daughter can load apps she needs for school.
I tried to use the root programs from this site despite the warning that I needed product version 1.2.3 and discovered the problem is the bootloader on my model/product version of Nabi is different and it appears that fastboot can't communicate with it. So the install gets stuck after rebooting the device and says "< waiting for device >". It just sits there forever. See screen shot:
{
"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"
}
Can anyone help?? (FYI, I am computer knowledgeable as I was a network administrator and systems administrator, but I do not have any coding experience).
Thank you!

soccermom99 said:
I need to root a Fuhu Nabi XD 32GB tablet. Apparently there are different models of this exact same tablet. My model number is NABIXD-NV10B, so the product version is 1.0. The only root programs I can find on this site are for a different Nabi XD model that can be on product version 1.2.3 through 1.5.
I contacted Nabi and they told me the most up to date version for my model is 1.0 and there are no other versions I can install. The problem is the Android OS version for this Nabi product version is 4.1.2 and I need a much more recent Android OS so my daughter can load apps she needs for school.
I tried to use the root programs from this site despite the warning that I needed product version 1.2.3 and discovered the problem is the bootloader on my model/product version of Nabi is different and it appears that fastboot can't communicate with it. So the install gets stuck after rebooting the device and says "< waiting for device >". It just sits there forever. See screen shot:
Can anyone help?? (FYI, I am computer knowledgeable as I was a network administrator and systems administrator, but I do not have any coding experience).
Thank you!
Click to expand...
Click to collapse
The bad news is that there are no other custom ROM's for the NabiXD. Both the NV10A and NV10B are stuck on Jellybean(4.1.2) so rooting isn't going to help. Looking at your screenshot I assume you are using my tool from here: http://forum.xda-developers.com/showthread.php?p=47306510 That tool is only for the NV10A and hence the product version 1.2.3, the NV10B only had a version 1.0 at least as far as I know. So even if you could get by the fastboot issue(which is probably just a driver issue) the TWRP recovery wouldn't work as it has the kernel for the NV10A not the NV10B. If I remember my research correctly the NV10A kernel will not boot a NV10B. However the NV10B kernel will boot a NV10A but the touchscreen won't work. There is a small silver lining in the fact that the nabi source code https://www.nabitablet.com/support/source-code for the NV10B kernel can be compiled, and it will boot both versions. I only have a NV10A to test with and I never could get the touchscreen to work. If someone continued from that point they could make a ROM past Jellybean for the NV10B for sure and likely the NV10A with some more touchscreen work. I honestly only tried for a few hours for maybe 2 evenings.
If your reason for root is only to get the tablet to a higher version then Jellybean 4.1.2 though I'm afraid there isn't a way. Or should I say a way currently, I do think it can be done if someone wanted to spend the time compiling a kernel and ROM.

Thank you!
Thank you so much for the information - I really appreciate it. That is extremely disappointing though. Yes, my reason to root the tablet is to get to a higher version of Android OS then Jellybean 4.1.2. Anyone, out there interested in trying to "compile a kernel and ROM" for the NV10B model???? (that is way too complicated for my computer abilities)
I would greatly appreciate it!

Related

[Q] Bricked TF

Disclaimer: Searching for this brings up far too many results to be useful.
Just attempted a Root of 3.2 using http://forum.xda-developers.com/showthread.php?t=1185104
I'd post this there, but don't have access rights.
Anyways, process went well, rebooted, but once the initial splash screen has cleared, this happens:
{
"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"
}
I've tried using the same tool to restore to stock, but nothing doing at the moment. Help would be appreciated.
EDIT: Annnnnd I've fixed it. This is why I never post. Carry on.
How did you fix it? I ended up bootlooping after flashing the WW HC3.2 boot image. I assume you also flashed the WW version?
Greetz,
speedstra
i had the same thing happening to mine when i first rooted to 1.4 prime. however now ive upgraded the rom to 1.6 and so far no artifacts
I had the same problem. I found it was able to fix it by downloading the latest version of the batch script root method zip file and using it to flash my tablet. You need to MAKE SURE you are using the latest version v5 beta5 because the older version had a problem flashing HC3.2 and gave me that error.
here's the link to the forum entry
http://forum.xda-developers.com/showthread.php?t=1185104
here's the link to v5 beta5
http://www.mediafire.com/?59rzqn61jl445lh
Speedstra said:
How did you fix it? I ended up bootlooping after flashing the WW HC3.2 boot image. I assume you also flashed the WW version?
Greetz,
speedstra
Click to expand...
Click to collapse
I had actually attempted to flash the 3.1 image instead of the 3.2 image. Thus the reason for edit on the original post.
The latest version of the tool should restore it.
EDIT: Annnnnd I've fixed it. This is why I never post. Carry on.
Click to expand...
Click to collapse
Please stop using the incorrect term for 'brick.' IT IS NOT A BRICK when your device turns on. Just stop, please.
Just had this same issue, got the same screen - blood pressure went through the roof, had to go water the plants to calm down
I was following this procedure: http://forum.xda-developers.com/showthread.php?p=14760983#post14760983
My mistake was not replacing the boot.img in the root folder with the newer 8659 .img file (linked at the top of the post, but not called out in the otherwise very detailed instructions).
HOWEVER: I did have an issue in that after flashing the wrong .img and getting the "oh sh!t" screen, I could not get adb to list a connected device, which kind of threw me. I could get it into APX mode by holding down the vol-up and power keys (and paying close attention to the "usb connected" notification sound - hold them down for about 10 seconds, hear the "disconnected" sound, then almost immediately hear the "connected" sound and let them go. The screen should stay dark instead of going to the boot logo) and I could see the driver being used, but "adb devices" returned nothing.
So I just ran root.bat again, as I had nothing to lose - and BOOM! Success!
Followed the rest of the procedure with no issues. Hope this helps someone!
Cheers
PatMan

[Beginners]What does it mean? | Every thing you need to know.

{
"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"
}
Hello every body, I made this guide for thosethose
who are new for Android ( coming from IOS or Windows...)
And for those who wants to know how to understand Guides through XDA.
SO LETS GET STARTED.
Main_Things
About Android
Android is a mobile OS (operating System) currently developed by Google
based on the Linux kernal and designed primarily
for touchscreen mobile devices such as smartphones and tablets.
Now we are going to talk about some main things
that you need in almost every guide:
ADB
A short of : Android Debugging Bridge
What's the ADB??
It's a command line utility which can control your device over USB from
a computer (copy file from and to the device ,install and uninstall apps and more..........).
How to enable it??
Go to Settings>About_Phone>Build _Number and press it 7 times.
Now go back to Settings>Developer_Options and
enable Android Debugging or USB Debugging .
ROOT
What's the ROOT??
Root is the process of allowing users to attain root access over various Android subsystem.
It's like running programs as administor in Windows, or running a command with sudo in Linux.
Notes
1_If you want to root your phone search for it in your device forums.
2_In some modding threads they say:
move it to system>apps and give it rw-r-r. It means to goto app's permissions
and check like in photo.
​
ROM(s) & MOD(s)
What is the deference between ROM(s) and MOD(s)
Rom(s):
Is a whole Android operating system ( firmware,apps......).
Mod(s):
Is a Modifications added to the software stored on the device.
Here you can learn everything you need before installing Rom(s)
Bootloader
ULB: Short of UnLocked Bootloader
LB: Short of Locked Bootloader
What is the Bootloader
Bootloader is a piece of code that runs before android loads up.
Bootloaders usually contain several ways to boot the OS kernal
and also contain commands for debugging and/or modifying
the kernal environment.
Note:
If you want to unlock your Bootloader you can
look for the way of unlocking n your device forums.
Recovery
What is the Recovery
It's the bootable partition that has the recovery console installed:silly:.
Or Simply it's where you can find tools to repair your phone
and install new ROMs.
The stock ROM recovery is very limited,
but the Custom recoveries offer much more,
they are coded to allow backup and restore function,
selective deletion of data So you don't have to
wipe everything and some of them have file explorer.
And here the most famous custom recoveries:
CWM: Short of ClockWork Mod.
TWRP: Short of TeamWin Recovery Project.
Something
In some ROMs thread's titles you could see these words
Official: it means the phone is supported from
the developer and it's Not port.
Unofficial: it means that it's port and it's not officially
supported from the developer.
Nightly: it means the rom have an every night update
for example: CM.
​
Shortcut
ADB: Android Debugging Bridge.
AOSP: Android Open Source Project.
CWM: ClockWork Mod.
TWRP: TeamWin Recovery Project.
CM: CyanogenMod.
ULB: UnLocked Bootloader.
LB: Locked Bootloader.
ICE: ICEcream sandwich 4.0
JB: Jelly Bean 4.1 , 4.2 , 4.3
KK: KiKat 4.4
LP: LolliPop 5.0 , 5.1
M: Marshmallow 6.0
Some shortcut that usually used in forums
OP: it means the "original poster" or "original post".
FCorFS: Short of : force close/stop
BL: Shot of BootLoop, it's when the phone stuck
at bootanimation because of something missed in the system.
Hardbrick: It's when your phone is dead
and you can't even boot,
So you must repair the hardware (motherboard....).
Softbrick: it's a software brick which
could be fixed with flashing stock ROM .
If I forgot anything just told me and please feel free to ask
Blackburn: the framework as from its name is the frame that the app work in it's the entire stack of stuff that makes up the OS.
Like siwtchs, buttons, colors, styles and. So on.
This'd the reason that the same app has different look in Samsung (for example) than Xperia . ​
n78 shadow said:
Shortcut
Softbrick: it's a software brick which
could be fixed with flashing stock ROM .
If I forgot anything just told me and please feel free to ask​
Click to expand...
Click to collapse
Awesome work brother it was very useful.
Just one question what is the android framework???
And thank in advance.

Nokia 3 stuck in Recovery after a 7.1.1

Hi!
Long time iOS jailbreaker finally moving to Android here.
Just got a spare Nokia 3, brand new.
Updated it from 7.0 to 7.1, than updated to 7.1.1.
Already its stuck in recovery mode due to what seems like a bug with the production line of Nokia? I've seen loose forums about this issue but all guides are either in Hindi or don't actually solve the issue. I just need to ask someone to help guide me through this, since I'm from iOS I'm not very aware about what flashing is, scatter file based flashing ect. I downloaded the base 7.0 from Needrombd.com, also downloaded SmartPhoneFlash Tool since that's meant to help.
I've connected the phone whilst its in fastboot mode, than put the scatter in and clicked download. Takes about 4-6 minutes than instantly hits 100% with a error (pic bellow)
Note: I cannot access the recovery page with the Android mascots chest open, only the screen posted in the reply below.
EDIT: Downloaded OST (Nokia's desktop flash editor), not much help as I can't seem to find the type of file its asking for. Seems like it could be a problem with a com port on the phone side seeing as I've mucked about with other cables/sockets.
Any help is so so appreciated right now :victory:
{
"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"
}
Faraheim said:
Hi!
Long time iOS jailbreaker finally moving to Android here.
Just got a spare Nokia 3, brand new.
Updated it from 7.0 to 7.1, than updated to 7.1.1.
Already its stuck in recovery mode due to what seems like a bug? I've seen loose forums about this issue but all guides are either in Hindi or don't actually solve the issue. I just need to ask someone to help guide me through this, since I'm from iOS I'm not very aware about what flashing is, scatters ect. I downloaded the base 7.0 from Needrombd.com, also downloaded SmartPhoneFlash Tool since thats meant to help but I'm still super lost
I've connected the phone whilst its in fastboot mode, than put the scatter in and clicked download. Takes about 4-6 minutes than instantly hits 100% with a error (pic bellow)
Haven't had a proper phone now for half a week and I'm a little anxious and I just want someone to help me out. Can't wait to finally get into Android!
Any help is so so appreciated right now :victory:
Click to expand...
Click to collapse
Whaat!!! Even with all my experience customising android phones, I haven't had the nerve to try flashing my nokia3 with flashtool. Does your phone still enter download mode? If so I recommend that you flash your phone with OST
You can get more information from this link:
https://forum.xda-developers.com/nokia-3/development/nokia-3-official-firmware-india-uae-t3674320
redweaver said:
Whaat!!! Even with all my experience customising android phones, I haven't had the nerve to try flashing my nokia3 with flashtool. Does your phone still enter download mode? If so I recommend that you flash your phone with OST
You can get more information from this link:
https://forum.xda-developers.com/nokia-3/development/nokia-3-official-firmware-india-uae-t3674320
Click to expand...
Click to collapse
https://imgur.com/sIsqZoo
This is the only thing accessible. Good suggestion though. Seems we have a mystery on our hands.

Lenovo Legion Duel Not Working Anymore

So recently my phone was having minor problems.. like randomly restarting and showing overheating warning when the phone isn't even hot.. so ive decided to update it through RSA but turns out RSA dont have the update my phone needed.. I've tried multiple update but not even the china one works even though the phone was originally from china.. can anyone please help.. I'm so sad right now because i dont want to loose this phone
P.s after installing the update from RSA the phone just stuck in boot up then cuts of after
{
"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"
}
You have a Pro not a Duel. You will need this first, extract it and place all the files within it to /ProgramData/RSA/Download/romfiles/L79031(delete whats currently in this folder first, then move all the files you downloaded into this folder). Now run RSA and and flash the correct firmware for your Legion Pro. Upon boot, make sure to run System Update to the latest firmware available (you will have to do this two or three times).
&(*) said:
You have a Pro not a Duel. You will need this first, extract it and place all the files within it to /ProgramData/RSA/Download/romfiles/L79031(delete whats currently in this folder first, then move all the files you downloaded into this folder). Now run RSA and and flash the correct firmware for your Legion Pro. Upon boot, make sure to run System Update to the latest firmware available (you will have to do this two or three times).
Click to expand...
Click to collapse
I think I'm in the same situation- And your link doesn't work. What is 'this'? Can't find any info on it!!!
@xXHotBoxXx420 ,
Pretty sure that link was removed. Here is where you'll find the firmware for your device. Just follow the instructions you quoted by @&(*) after gathering your models firmware.
project_2501 said:
@xXHotBoxXx420 ,
Pretty sure that link was removed. Here is where you'll find the firmware for your device. Just follow the instructions you quoted by @&(*) after gathering your models firmware.
Click to expand...
Click to collapse
Hey thank you, but I actually found a CN ZUI 13.5 ROM that I've never found before and flashed it, and it worked. I have Android 12 now, but my cellular still isn't working, and I want a ROM with Google apps by default- one more like the stock android. I assume that's the global version. Trying to go about unlocking my bootloader and flashing the Legion Duels ROM on my Legion pro, I've heard there is a way. Just need to find a good tutorial.
@xXHotBoxXx420 ,
Here is a guide that will work on this device, make sure you read it carefully and backup what it states. I suggest you read this other guide first so you can recover from any mistakes.
project_2501 said:
@xXHotBoxXx420 ,
Here is a guide that will work on this device, make sure you read it carefully and backup what it states. I suggest you read this other guide first so you can recover from any mistakes.
Click to expand...
Click to collapse
Helpful, but I'm wondering if I can do it the other way around; CN to Global rather than Global to CN. I'm sure it probably works the same way, backup partitions and all that. I just figured you had to unlock the bootloader to be able to flash other ROMs but I have flashed the ROW & EE ROMs and ended up with crashdump/bootloop. Didn't realize flashing partitions could fix that. I think I'll give it a try. Thanks

Stone Age. :)

Dear all ,
I hope your expert team will give me an idea with my old Samsung GT-P5110 (wifi). I had good times with that tablet , but seems like , even if the technology go fast, everybody tell me to throw it away. I am still believe that old devices they do their own job. At least one ( other than clock ).
I stack for days now to find away what I can do to upgrade this as with the 4.0.4 you can do practically a big NOTHING. Neither online update. ( No support from Samsung but when I bought it they loved my money) Sorry but I am not agree with their policies . In now days I would like to use this table just to show me the status of my solar panels, even without android based os ( Linux for tablet was also a good idea ) but nothing to escape from 4.0.4
The problem is that the USB/ samsung port is destroyed, and the only way to update it is via SD card. But I am lost. Everything I try with official firmwares just not make any change. If I am correct after so much reading -Probably I need a file just for update only ex Filename: GT-P5113_P5113XARCLH-OTA-P5113UEBLH3_XAR_280235988.zip | Size: 267 MB but nowhere availabe.
You have any ideas to save my beloved table and to convert it on something more useful than that where the "brick" is same as now for me
Altough I am an old guy - old board, that I was starting at my 5 ys to play with old radio tubes and fixing radios... just for the history.. )
Thank you in advance for your replies and knowledge - much appreciate it.
Pic with About page included.
{
"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"
}
First things first One should not expect to get any further official updates from you manufacturer. You may get a newer Android version by flashing a custom rom. This could be done without a working usb port but if at some point you cannot boot into recovery nor system for some reason, you get a shiny paperweight (usually one would fix that using usb download mode).
Android 4.0.4 is really not new, but the usability greatly depends on what you want to do with it. How would you get the status of your solar panels? You should have a working browser on your tablet, so showing a website with your solar panel statistics should not be a problem.
If you still want to go through the process of installing a custom rom, this is what you could do:
Get root access by using some Root Apps, for example KingoRoot. You will find guides on XDA
Install flashFire and use it to flash a custom recovery
boot into the custom recovery and install the custom rom from SD card.
reboot into your new rom
olympicwave said:
GT-P5113_P5113XARCLH-OTA-P5113UEBLH3_XAR_280235988.zip | Size: 267 MB
Click to expand...
Click to collapse
where have you found this filename?
You may look here for Roms for your device
PauSteu said:
First things first One should not expect to get any further official updates from you manufacturer. You may get a newer Android version by flashing a custom rom. This could be done without a working usb port but if at some point you cannot boot into recovery nor system for some reason, you get a shiny paperweight (usually one would fix that using usb download mode).
Android 4.0.4 is really not new, but the usability greatly depends on what you want to do with it. How would you get the status of your solar panels? You should have a working browser on your tablet, so showing a website with your solar panel statistics should not be a problem.
If you still want to go through the process of installing a custom rom, this is what you could do:
Get root access by using some Root Apps, for example KingoRoot. You will find guides on XDA
Install flashFire and use it to flash a custom recovery
boot into the custom recovery and install the custom rom from SD card.
reboot into your new rom
Click to expand...
Click to collapse
PauSteu, Thank you very much for your reply and guidance.
Yes, I tried old versions of Kingoroot but nothing work. The newer versions reply parse error before even installing. Its quite old the 4.0.4 ( after factory reset ). Thats why I thought that if I will able to upgrade at least to Jelly 4.2 to start doing something. Becuase now even the browser are not compatible with most of web pages, including the solal panels one.
Althout I will continiue try to take the challenge and searching more. Thank you for your time spending for me.
PauSteu said:
where have you found this filename?
You may look here for Roms for your device
Click to expand...
Click to collapse
I founded in some old forums back to 2013 as an update only file that you can feed from SD card and upgrade the tablet from 4.0.4 to 4.2. But not available anymore in any hosting. ( thanks for the link)

Categories

Resources