I have a Nabi2 that I am trying to root (it has the latest 2.3 ROM, Android 4.1.1), and of all the tutorials I have found (Linux or MSWin), none of them work. The one that has gotten part way through is http://forum.xda-developers.com/showthread.php?t=2016463, but once I get to the "adb reboot recovery" command, nothing ever happens, and I have to power-cycle the tablet, and I am right back to absolutely NOTHING having been changed.
I tried the MSWin installs (such as NabiLab), but it seems that ADB is incompatible with VirtualBox, or at least can't manage to KEEP a connection active to the device (even though I set the Nabi as a permanent USB device in the Win7 or Win8.1 VM images).
I would *prefer* to post a message to the appropriate discussions/threads, but apparently XDA won't allow that.
I bought this for my daughter's birthday, and within a month it was already unusable becayse the anemic internal space filled up. So this tablet sits unused, and she ends up using my wife's modded Nook Tablet (CM10.2). My daughter had been using *my* NT (CM11) until it quit working.
I really think it's time to make a road trip to Fuhu's HQ, and shove this p.o.s. sideways up an uncomfortable place on the company CEO Especially after being out of work for 6 months, and I can't be throwing money away on substandard and unusable products.
I've been continuing my attempts to root this thing, and I have an idea; as *all* of the root tips/tutorials are from 2013 and earlier, I think this tablet may be more equivalent to a "Disney and/or Nickelodeon" model. Once I bought it in January 2014 (setting it up for my daughter's birthday in early February) it installed the massive 2-part OTA upgrade that added Gapps and JB (Android 4.1.1). From what I've read, that seems to require a thorough reorganization of the partitions on the Nabi2, so perhaps all those old methods have to be tossed out (or at least marked as for older, non-updated units) and a new set of directions made for the updated units (version "2.3-release-keys"). Either that or determine if the Disney directions are the same for the updated units.
I did see on NabTabHacks ( h t t p : / / nabtabhacks . com /wp-content/uploads/2013/12/Nabipart1.png ) the difference in partitioning between the original Nabi2 and the Disney model; if someone could instruct me on how to gather that information on our unit (without having to have rooted the unit, obviously, since root isn't working) I'd see if we are dealing with a Disney-fied configuration.
Related
I have a Chinese netbook with Android 4.2.1 on it, and I've managed to root it. I've been interested in installing something like CyanogenMod or even Linux on it. The problem is that everything seems to be centered around very specific device information like manufacturers and model number in the ARM/Android world. But unfortunately, the most specific numbers associated with my device tie it back to a chipset manufacturer called WonderMedia, WM8880 GA-1311F. And I can't find anything at all about that device except that there's supposedly a 7-inch tablet or two with the same chipset, but their manufacturers are fairly unknown as well. When I do Google searches for the serial number, I mostly find my own old threads
I keep hitting dead ends trying to figure out how to boot something else on this device, because they expect me to know a specific recovery procedure or have a device specific ROM to apply.
Am I basically stuck with what I've got? I mean, I've been doing searches for days, I've searched for specific strings found under build info, and found nothing. I keep hunting for clues about the nature of the device in the kernel logs, and I keep coming up empty. The closest thing I can find is information about an older WM8650 netbook, and I saw a dead thread somewhere that implied there was an architectural similarity between WM8880 and that one, but I wasn't able to find anything about my device specifically.
I really don't want to waste anymore time with this if I don't have any chance of getting anywhere with it. Just tell me the truth... am I stuck with the pre-installed version of Android on this device?
I was hoping I'd be able to hack the device and do whatever I wanted with it, sort of like a Raspberry Pi in laptop form, but I'm starting to think I made a mistake because this device seems hopelessly locked into running Android 4.2.
Well, I found out that my device actually has something called U-boot built in. It wasn't easy to find because I had to dump a region of flash memory, hunt around in a hex editor, cut off part of the file, and then gunzip it to see it. Apparently my device can be booted from an SD card through a file called "FirmwareInstall/autorun.1.wmt". I also saw an odd reference to a USB disk and "FirmwareInstall/autorun.u.wmt", which may suggest it can also be booted from USB.
At first I tried to have it print a Hello World message, but it didn't work. However, I did notice that when I put the file in place, the machine refused to power down with the SD card inserted, which was abnormal. Clearly, it was changing something, but the console isn't visible. So I tried the "poweroff" command instead, and sure enough the netbook started cycling its power until I removed the SD card.
Apparently there IS a way to get stuff working on here, but I would have to know TONS of low-level memory addresses for loading stuff like the kernel, they recommend installing stuff over the network for some weird reason, and it seems like you have to use a specific device tree to get it up and running. Half the ARM Linux installation documentation was just an apology saying that devices vary and there's no consistent implementation of anything.
So it seems like it's POSSIBLE to get something else working on here, but I would literally have to reverse engineer every little aspect of the machine and study every single subsystem carefully in order to do so. What's frustrating is that there is a person who is doing work on very similar devices like the 8505, 8650, and 8850, but they're not supporting mine because, get this, the developer's 8880 tablet was damaged from messing with those ridiculous analogue console pins, and they can't be bothered to buy another one. So anyone that has my chipset is stuck without any kind of support for anything, and I would be lucky to get a console framebuffer with keyboard support running on this stupid thing.
Overall, everything I read was just more and more bad news... stuff like the default console for the installer often being a serial terminal that you have to break open the computer to use. Everything about ARM devices is painful, and you apparently have to fight tooth and nail to get them to run anything besides their stock version of Android, and all because there's no standardization and no BIOS.
hi do you still have the netbook i need the rom for it
Last year I got annoyed that the Wishlist icon was repopulating itself to my Favorites every time I deleted it, so I got a wild hair to root my Kindle and take care of that junk for good. I did this before reading the numerous warnings about how this was an awful device to root on a whim. I proceeded to delete a bunch of system files related to Amazon ads and tracking. After a reboot, I found myself stuck at a flashing white Favorites screen. I could get to the Settings menus, but most choices didn't work and just took me back to Settings without changing anything. I couldn't connect to a wifi network, but I could see the networks, click on Connect to Network, and then it just took me back to Settings. I couldn't change any of the Developer settings. I did hard resets from that mode and from the boot up recovery menu. Nothing could get me out of this state.
Anyway, I posted thread about this when it happened, here: http://forum.xda-developers.com/kin...iles-flashing-favorites-screen-t3116682/page1
In the end, I didn't have the heart to scam Amazon, so I just bought a used HDX 7 and put the bricked one in the drawer in hopes of a future fix. Last night, my replacement Kindle's screen was crushed by some mysterious force, possibly a kitty cat or an adjustable bed. Though it's tempting to think about trying to swap the screens, I don't want to crack the screen and wind up with two broken displays (plus a bricked Kindle). So I thought I'd check back and see if there were any developments on the fixing-dumb-newbie-mistakes front for the bricked one.
The device does not show up in Windows XP, 7, or 8.1. The Kindle itself recognizes it's charging. As I mentioned in the old thread, I tried a Fastboot cable, but that apparently doesn't work on this model. So any hope? It's so frustrating because it seems like if I could just get the wifi to work I could download the latest OS update and it would fix this.
I understand if there still are no fixes for this. It was a dumb move to tinker with this in the first place. I was just hopeful something might have changed, since last I asked about it.
No adb access? That sucks, as it should be pretty easy to fix if you could adb push. Were it mine, I'd go ahead and try to replace the screen on the functioning tablet. Not what you want to hear, but I think that's the only way to get working again. Best of luck.
Valence1981 said:
Last year I got annoyed that the Wishlist icon was repopulating itself to my Favorites every time I deleted it, so I got a wild hair to root my Kindle and take care of that junk for good. I did this before reading the numerous warnings about how this was an awful device to root on a whim. I proceeded to delete a bunch of system files related to Amazon ads and tracking. After a reboot, I found myself stuck at a flashing white Favorites screen. I could get to the Settings menus, but most choices didn't work and just took me back to Settings without changing anything. I couldn't connect to a wifi network, but I could see the networks, click on Connect to Network, and then it just took me back to Settings. I couldn't change any of the Developer settings. I did hard resets from that mode and from the boot up recovery menu. Nothing could get me out of this state.
Anyway, I posted thread about this when it happened, here: http://forum.xda-developers.com/kin...iles-flashing-favorites-screen-t3116682/page1
In the end, I didn't have the heart to scam Amazon, so I just bought a used HDX 7 and put the bricked one in the drawer in hopes of a future fix. Last night, my replacement Kindle's screen was crushed by some mysterious force, possibly a kitty cat or an adjustable bed. Though it's tempting to think about trying to swap the screens, I don't want to crack the screen and wind up with two broken displays (plus a bricked Kindle). So I thought I'd check back and see if there were any developments on the fixing-dumb-newbie-mistakes front for the bricked one.
The device does not show up in Windows XP, 7, or 8.1. The Kindle itself recognizes it's charging. As I mentioned in the old thread, I tried a Fastboot cable, but that apparently doesn't work on this model. So any hope? It's so frustrating because it seems like if I could just get the wifi to work I could download the latest OS update and it would fix this.
I understand if there still are no fixes for this. It was a dumb move to tinker with this in the first place. I was just hopeful something might have changed, since last I asked about it.
Click to expand...
Click to collapse
You're done if device is running 4.5.2 w/no adb access. There are a few last resort unbrick methods/tools but they are geared toward older versions of FireOS (v3.2.6 and below). Replacing the screen on a 7" HDX is difficult; copious use of glue makes for a tough job. Might check auction sites; prices are pretty low for 16GB models. Also consider the latest 7" tab from Amazon (2015 Fire). Specs are awful vs HDX but it really isn't that bad, especially for video and with apps designed for lower resolution screens (many are). Fully rootable with option for custom roms. FireOS v5 is a nice step up from v4, faster and more 'android like' (although still heavily skinned).
I feel super awkward and a bit embarrassed to ask this question, but I'm asking for help from this community (see last 2 or paragraphs for ask if you want to skip the boring details) and I think I need to explain briefly why to define my ultimate goal and why I even have to ask rather than sift through searches and assemble the steps/versions I need, etc.
My 22 year old daughter died recently (unexpectedly). I obviously want to preserve everything I can of hers, but I'm not firing on all cylinders mentally. I was able take her ThinkPad and virtualize it to my ESX system and also yank and clone the physical drive for safe keeping. But even doing that took me a while (which it shouldn't, that's kind of what I do for a living - I should be able to do that in my sleep, but it took 3 days and a lot of screaming). I was able to access her google accounts, facebook accounts, etc. and preserve a ton of stuff from there.
Ultimately while I would want to do with her phone the same thing I did to her notebook - preserve it virtually so I could examine it without fear of changing/modifying anything, but I don't think the product exists that allows me to virtualize an existing Android phone with apps and everything intact into a PC environment. I think I could install a whole new Android emulator in Windows, but that's not probably what I want.
I had just given her a Samsung S5 SM-G900T running on Ting for her birthday about 2 weeks before she died. It was unlocked but unrooted, it's rare that I would do nothing to the phone prior to giving it to her - but I pretty much just turned it on and handed it over with no custom ROM or anything - mostly because I was pressed for time the day of her party and it was shipped late.
When I got it back from the police a few say ago (they held it for 2 months) and charged it and turned it on 2 days ago, it upgraded from Lollipop to Marshmallow 6.0.1 (baseband is PE1), which was apparently pending. I don't know if that complicates things. It pissed me off, though. I have copied off local photos off and videos and already took control of her Google and Facebook accounts as I mentioned.
My slightly confused brain tells me normally I might install TWRP or CWM and make a NAND backup and copy it off someplace and at least have a restorable copy of her phone. I haven't done much of this sort of thing with phones for a year or two, I don't know what's changed in the latest OS versions and beides, plus I sort of "lose it" a bit, especially going through her personal things.
I'm not an idiot, I'm just not all here, yet. I'm asking if someone can please give me steps to safely preserve an image of her phone (IE, install TWRP or CWM using specific version xxx, etc., using Odin version xxx, etc.) - If I can virtualize it, too, I'd love to know what product does that, but again, I don't think I can.
I don't know why I feel the need to do these things, I just do.
Any help would be greatly appreciated.
Bump. Somebody please help this fellow. This is too important for me to try advising him, I don't know enough.
So even though half my brain is addled, I did some more research and found out a few interesting things, should anyone care to try this. I found there are a couple of open source tools built for android forensics:
Open Source Android Forensics Toolkit
https://sourceforge.net/projects/osaftoolkit/
Santoku
https://santoku-linux.com/about-santoku/
And there are commercial products, , like NowSecureForensics, some (if not most) built on the toolkits I just mentioned. Another is the painfully ironically named (for me, anyway) Autopsy.
This interesting website verified (to me anyway) that rooting the phone and changing access is still fundamentally sound forensically:
http://freeandroidforensics.blogspot.com
And it confirmed there is no way (yet) to truly "virtualize" the phone entirely (unless you are the manufacturer and you have some proprietary software).
For a "live" example virtually, the best you can do is install an Android emulator and restore an ADB backup of an app. This obviously may or may not work if the app is very hardware dependent. But for a simple program it might work fine.
So in addition to rooting my daughter's S5, installing TWRP, and backing it up, I also got my daughter's HTC One M7 to finally power up, and I rooted it and installed TWRP for backup purposes as well. Many of the forensic tools I mentioned will then report from the standard TWRP backups, with no risk to changing the phone. Some want to look at the phone themselves, even offering to root them, which I find more risky.
I haven't found any one tool to fully provide what I need, you need a Windows PC, a Linux PC (or VM), one or more toolsets (each comprised of other toolsets) and then a lot of time/will to really piece together things. I haven't completed the examinations - even typing is harder now for some reason, but should anyone else need this sort of thing (hopefully for different reasons than mine), the above info is a good start.
Hello!
TL/DR version:
How do I ultimately gain complete control over my own phone?
Android version 6.0
SecPatch 2016.03.01
Kernel 3.10.49
Build MRA58K
Software US37510b
CPU: Qualcomm Snapdragon 210
Long version:
For various reasons, I decided I needed a pocket portable Android computer, and a cell phone seemed to be the best option open to me. In researching for what would suit my needs and budget, I discovered the local U.S. Cellular store was having a penny promotion for the LG K8 US375 prepaid. Did some research, and decided it was a good deal for seeing if a phone works for my needs, as I don't care about the phone part.
It has been a headache. I am used to PCs. I knew it would have a reserve amount of storage for system files, but I wasn't expecting 50%. Then I installed the programs to do what I wanted, and was left with 500MB left. This won't do. Got a bargain on a PNY 32GB Class U3 SD card, and installed it. I then discovered I had to manually move files to it, only partial data would be moved, and only certain programs would move at all. I tried to find a way to set it to be a default install location like a second hard drive, but found nothing. Best I could come up with is adoptable storage. Which appeared to be disabled on the phone. I would also like to remove files I don't want or need. I talked it over with an online tech from LG, and he basically said I needed to root the phone.
I have spent two weeks, and I don't even want to know how many hours researching here & elsewhere how to do this. I keep coming up with dead ends. Either the method doesn't work for Marshmallow, doesn't work with LG, doesn't work for this kind of LG phone, is known to brick/bootloop the phone, requires programs that have been removed from the links provided, or required unlocked bootloader. Finding how to unlock the bootloader has been about as fruitful as rooting.
I am done researching. I have lost too many nights being sucked into the project to the point I am rereading the same threads without realizing it. I have 21 bookmarks regarding how to do this, and the best I have is a method for unlocking adoptable storage on a Sony phone with the brief mention that it worked on someone else's K8. I haven't felt this overloaded with tech information since I crammed for the A+ cert test. (I did not pass) I know I need to do this manually, I have unlocked dev commands, picked up adb/fastboot, poked around a bit, and I think I can get to the point where I would have a clean boot. Like installing a new OS after formatting on a PC. It's everything that comes after that I am lost on. Please advise.
mageofthesands said:
Hello!
(...) Please advise.
Click to expand...
Click to collapse
Not everything can be root.
Try asking the thread Lg 2-3g Tool 9.21 Update. LG G5, ...
So Grandma got the my three kids this tablet and even though it has a sdcard slot you can't install anything to it. I'd like to use Appgr III or Move2SD anything to install more than a few games for the kids. I've tried Kingo root (both from google play and from a laptop) but no luck.
Anything else I can try?
Here are the details:
Model:
Y88X Plus
Processor type:
Quadcore-A23
Android version:
5.1.1
Firmware version:
v.3.3rc5
Kernel version:
3.4.39
[email protected] #3
Tue Mar 22 23:27:08 CST 2016
Build number:
A33_U70_U709HB2C_1605213.20160527
Any advise would be greatly appreciated.
Sagz
Bright Tab V90-HD is the same
Other than the processor being an A33 everything you say is the same as this worthless tab I have, I was trying to replace an Acer tab that was slowly dying and when I purchased this one I forgot the old saying "if it sounds too good to be true" you know the rest. After trying to research the tablet and the elusive 16GB that it shows but is inaccessible I have concluded that I just wasted $45 that would have been better invested in a better quality item. The only thing I can tell you is if you can afford it to buy a better tablet that looks the same (most of them do) and not say anything to Grandma about the switch this will save you a ton of frustration that I have already experienced trying to make this work, I wish I could give you a ray of hope but I can only save you the disappointment I have experienced.
Hello,
I have two of this very same tablets, that I bought for my girls.
Since it is only used for playing and videos, I removed and disabled all I could, and I even emailed to support in order to know how to move apps to an SD, since 5.1.1 was supposed to be able to do so. They kindly answered and it was like: sorry you cannot move apps to SD.
I must admit this is a huge problem when you have a couple of paid app (like Disney story central) that are ginormous.
So a few months ago I tried to root it with the Kingo Root from my pc and it did not worked properly (root lost after reboot).
Yesterday I was trying to do some updates with huge problems due to the lack of space and decided to give the Kingo Root apk a try. It took a couple of minutes, got the thing done and moved me to a splash screen that suggested me to buy the premium app (which I avoided, since it was about 50% of the cost of the device ). After that I checked everything and it seemed to work, I removed the cleaner that it installed together with the super user, rebooted twice and still Superuser app was showing the device as rooted. A few ads stated appearing on my device, which annoyed me a LOT.
Since I could not install Titan backup due to lack of space (there are several unwanted bloatware preinstalled) and I am a noob with no big rooting experiece, I decided I would study more, went to Superuser menu and removed the root, the apps and cleared system cache in order to gain enough space for CCleaner.
I will probably try again once the new U1 sd cards will arrive.
Obviously I am not worried about IMEI (no GSM or anything) or data, since the tablets usually run under a Kiddoware parental control interface.
I read about some people suggesting to get rid of the Kingroot/ Kingoroot apps and put Supersu, but I am a bit worried about the risk of bricking the device since it seem less supported and exploited than other major brands.
Any suggestion?