For some reason(i'm on windows 7, running in compatibility mode) I can't get mauimeta to function properly. I'm having a hard time tuning my baseband. Is it a night and day difference, or only slightly better with a tune? If anyone wants to help me troubleshoot, when I open mauimeta, I get the error "create meta sp dll log failed, please change path" and no matter where I change the path too, I always get this error. When I try and connect my omate, it never makes a connection to the program. If it's not that much of a difference, I guess I won't worry about it, but if it will make a big difference, I'll troubleshoot further until I can get the tuned baseband on my watch! Thank you for any input!
Related
Plz pardon my rant but I need major helpppppppppp lol, I've spent days scouring this site & google to try to fix this myself. I've built pc's but delayed learning droid because it's worse then mickersoft from what I've seen. I babysit for a lady raising her 3 granddaughters, they don't have net & were only able to access a few things. Sooo I volunteered to add some games, I was so flabbergasted at the bloat, shear greed and limitations of both versions of dis ui. I wanted to just disable it to use a different launcher but nooo to easy. no good deed goes unpunished lol. I updated the stock to the current as of two weeks ago ota kitkat and it went down hill fast, the dis ui worked for the most part but it wouldn't let me in the settings that's on the nabi mode for no apparent reason.
So not being able to find much current info for dis version, I made the huge mistake of using kingroots apk. it chocked but then work fine except I still had the above problem. no matter what I tried to clean or debloat. I got stupid tired and did a factory reset it now won't boot fully. I only get a pop up loop even in safe mode of nabiSetup has stopped. I can only turn off but can access recovery and the fastboot etc! I give it wins this round lol.
I have tried both win 10 32 & 64bit I only got it to connect once, it said I unlocked the bootloader but nothing can find the device to reboot-bootloader thru adb or NabiLab, 15 sec abd and etc. I'm to tired to think straight and to new to this so I must be missing something. there has to be away to get droid back on it! I can usually access the tablet and the sd card thru win explorer but no matter witch drivers I've tried it will not connect properly or the drivers won't install fully even with drive sig disabled. so it has to be because of the bitmap error I found in recovery or because it won't fully boot to access the usb on the tablet??
cliff-notes
1. the devise will not fully boot I get a nabiSetup has stopped popup loop in normal & safe mode I can only shut it off.
2a I can still get in recovery I tried to flash it but I assume I was using the wrong file nothing would load, but noticed E: missing bitmap stage_empty & stage_fill it seems to be a common droid problem but no info to be found for this devise version.
2b In the device manager fastboot comes and goes or I see a USB device descriptor failed or set address I think it was and pdanet stalls. I'm gonna fdisk laptop again it's had way to many driver attempts to be sure that's some of problem not operator error or usb in a mood again.
3. being brain-dead tired & a droid newbieish. I can't get to the usb to play nice so I can't install twrp. I assume because of the usb drivers ie google and etc not showing up right in device mangr. no usb on nabi which I just remembered the developer options vanished, that's why I decide to reset since what I think is the reset pinhole didn't work?
p.s I can access win explorer most of the time. the common droid/disney folders are showing but I'm unclear what all is missing.. can someone please give me a laymens clue how to get the os back on it. I deleted the cache and etc to no avail. I pieced together other peeps info here but so far I'm special no one has my exact errors lol. my gut says it's fixable from what I have read it seems to makes a difference its a disney version I don't care what's on it as long as it works at this point any ideas or help is deeply appreciated. I'm running win 10 ent 64bit at the moment and it was stock disney version of NABI2-NV7A-US-D with 4.4.1 before bad update of kitkat ota.
Twink225 said:
Plz pardon my rant but I need major helpppppppppp lol, I've spent days scouring this site & google to try to fix this myself. I've built pc's but delayed learning droid because it's worse then mickersoft from what I've seen. I babysit for a lady raising her 3 granddaughters, they don't have net & were only able to access a few things. Sooo I volunteered to add some games, I was so flabbergasted at the bloat, shear greed and limitations of both versions of dis ui. I wanted to just disable it to use a different launcher but nooo to easy. no good deed goes unpunished lol. I updated the stock to the current as of two weeks ago ota kitkat and it went down hill fast, the dis ui worked for the most part but it wouldn't let me in the settings that's on the nabi mode for no apparent reason.
So not being able to find much current info for dis version, I made the huge mistake of using kingroots apk. it chocked but then work fine except I still had the above problem. no matter what I tried to clean or debloat. I got stupid tired and did a factory reset it now won't boot fully. I only get a pop up loop even in safe mode of nabiSetup has stopped. I can only turn off but can access recovery and the fastboot etc! I give it wins this round lol.
I have tried both win 10 32 & 64bit I only got it to connect once, it said I unlocked the bootloader but nothing can find the device to reboot-bootloader thru adb or NabiLab, 15 sec abd and etc. I'm to tired to think straight and to new to this so I must be missing something. there has to be away to get droid back on it! I can usually access the tablet and the sd card thru win explorer but no matter witch drivers I've tried it will not connect properly or the drivers won't install fully even with drive sig disabled. so it has to be because of the bitmap error I found in recovery or because it won't fully boot to access the usb on the tablet??
cliff-notes
1. the devise will not fully boot I get a nabiSetup has stopped popup loop in normal & safe mode I can only shut it off.
2a I can still get in recovery I tried to flash it but I assume I was using the wrong file nothing would load, but noticed E: missing bitmap stage_empty & stage_fill it seems to be a common droid problem but no info to be found for this devise version.
2b In the device manager fastboot comes and goes or I see a USB device descriptor failed or set address I think it was and pdanet stalls. I'm gonna fdisk laptop again it's had way to many driver attempts to be sure that's some of problem not operator error or usb in a mood again.
3. being brain-dead tired & a droid newbieish. I can't get to the usb to play nice so I can't install twrp. I assume because of the usb drivers ie google and etc not showing up right in device mangr. no usb on nabi which I just remembered the developer options vanished, that's why I decide to reset since what I think is the reset pinhole didn't work?
p.s I can access win explorer most of the time. the common droid/disney folders are showing but I'm unclear what all is missing.. can someone please give me a laymens clue how to get the os back on it. I deleted the cache and etc to no avail. I pieced together other peeps info here but so far I'm special no one has my exact errors lol. my gut says it's fixable from what I have read it seems to makes a difference its a disney version I don't care what's on it as long as it works at this point any ideas or help is deeply appreciated. I'm running win 10 ent 64bit at the moment and it was stock disney version of NABI2-NV7A-US-D with 4.4.1 before bad update of kitkat ota.
Click to expand...
Click to collapse
It's hard to understand all of that but it sounds like perhaps you deleted some bloat that you should have, you sound like having driver issues, and possibly wrong TWRP version. Need to clear that up and then reinstall the stock Disney ROM.
I'd start here it has all the tools/TWRP/ROM's you need.
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
So sorry hun, toshiba is driving me nuts and I'm having a bad add moment or three lol. I read about you retiring. so I tried hard not to bother you. now I'm really confused. I've read your nabi2 general info post and even ran across your youtube vids. the problem is I'm not familiar with adb. & the included NabiLabGUI drivers, win10 either fails to finish saying it was interrupted. or it just won't install the 32 bit drivers, I thought I as suppose to use.
The 64bit driver 3 out of 4 install but, I can not get the Google Inc, driver to install properly even with the inf file. (ie the android_winusb.inf ) it says the system can't find the file, it can install the older versions from NabiLabGUI or naked drivers. but doesn't show in add/remove and it still won't detect the tablet most of the time lol.
Pda also has conflicts with adb, I got the nablab disney option to detect it but still failed to install twrp saying it can't find devise and I noticed in device manager 2 driver problems that will not let me update manually or they go missing if I try to force windows to reinstall. (device descriptor request & set address failed)
I must be missing something big, I also tried the 15sec and minimal adb. I assume because the tablet won't fully boot up, windows doesn't know what to do with it. when I tried different cables. windows 10 enterprise won't play nice at all now. so I will format again to be safe but lost what to try next.
I guess my questions should be is there a work around or a full inf version of the newer drivers for NabiLabGUI2015 that might work with this demonic disney nabi2.
&
Is NabiLabGUI compatible with .net framework 4.6 advanced services? (I may have to downgrade o/s. on the nabhacks site is says .net 4.5 is a prerequisites.) I don't know much about the app but saw 4.6 comes preinstalled, I can't install 4.5 yet, I saw there has been compatibility issues. and it won't let you revert versions easily if at all.
I'm to tired of this tab to think straight anymore and so grateful any help I'm in way over my head here.
Update
I lost the battle but I won the war, now google & supersu are messing with me as usual but it boots so I win lol :victory::silly:
Hi all,
I bought a couple of chinese gps tracker smartwatch for my kids (Wonlex GW1000 and GW2000) and wanted to clean them up a bit as the have things like WeeChat and such. The problem I'm running into is that there is no 'Enable USB debugging' or even a developer's menu on those phones. I have tried the usual tap 7 times on that build number to enable the developers menu but got nothing so I am assuming it is already done and they have come how disabled/hidden these options.
I have tried using Miracle box + loader and got to the point of extracting a rom dump but I think it might not be valid as the initial test I wanted to do was to flash that same dump back just to validate and I get an error (something like `No Table`) which googling it tells me that it is probably an invalid rom.
I also tried MTK Droid tools but it doesn't even detect the watches so didn't get very far.
I have also tried Uni Android tool to see if that was worth paying for but also couldn't get it to even see the devices.
Can anyone point me in the right direction as to how to dump -> change -> re flash an image so that I can customize these watches?
Specs:
Android 4.2.2
Kernel 3.4.5
Build number: g76lca_hw13_gw_rb1b8_ru_akq_td_js_20171220
Thanks!
I can install images without a problem, but cant install any roms. TWRP says that I don't have an OS, I guess it got somehow corrupted. I can install recoveryes through fastboot, I have tried twrp and other ecovery coming with LineageOS.
When I try to install rom on twrp, it gives "error applaying update: 7 (ErrorCode::kInstallDeviceOpenError)" and then updater ends with error 1 and at last it gives error installing zip file. If I try to flash stock rom, it's just the same, just not the update part.
Any advice?
The MSM Tool Unf*cketh.
Unless you have fried hardware (dropped in ocean, etc) I've never heard of this not fixing it.
Pay careful attention to getting into EDL mode for the flash, that's tricky sometimes.
Okay, thanks a lot, will give it a try.
Edit: I actually read about that tool before but I'm running linux. But I guess this is important enough to setup vm.
You can download a W10 install disk free, run it on VirtualBox, and get the flash done prior to it requiring activation. Not endorsing that or anything, of course, just saying... it can be done. Make sure you kill internet on the VM ASAP or it will self-update itself to death. (I can neither confirm nor deny that POS Windows Update rebooted DURING A FLASH. I've been on Linux too long to remember the horrors of that world, may you not have PTSD when you try)
I couldn't get it to work. Problem is that my phone is stuck booting to fastboot-mode, so I cant enter edl. I also tried to enter edl through adb and fastboot, but it is possible that I somehow passed the phone to vm wrong. It has been a while when I last used virtual machine and I'm super exhausted.
I have to try tomorrow again.
If you can get the phone off with some battery life left, you can do EDL. Don't try using either adb or fb commands, do it from the volume keys with the phone OFF. It will do EDL before it even goes into bootloader. If you are getting into FB or recovery AT ALL - even if an infinite loop - you should be able to pull it off.
There's a bunch of stuff that tripped me up when I was doing it:
-Virtual Box needed some additional plugins to make USB a pass-through
- Virtual Box needed one of its minions to get added to a Linux user group so it could see (permissions for) USB
- There's a separate Qualcomm driver that needs installing to that icky OS
- When the phone is OFF, and you ***HOLD*** the volume buttons, then insert the cable, EDL is only enabled for like five seconds (or something absurdly short). You have to have the MSM tool up and running, waiting to click.. do the phone physics, wait for it to say connected, then click on the button in the tool to get it to start. Once you see the "firehose upload beginning" or whatever you can let go of the buttons, it will remain in EDL till it is done.
- As hinted above you have to keep the VM OS from rebooting itself trying to install terabytes of useless updates while you are flashing. (Cutting the NIC from the VM works nicely.) I was, luckily, still able to re-flash again and it worked.
I've bricked a few phones in my Android life, and pretty much only endorse OnePlus now because of the support for recovery when you screw up. It has some tricks, but thanks to lots of n00b errors writing my own debloat script and carving out essential parts of Android, I've got it down and repeatable (though I luckily haven't needed it in a while).
Get some sleep, get some green tea, or ethanol, or whatever your poison is, and try again... LMK /exactly/ what fails and I can do my best to help.
I spent some time picking through the local upgrade utility Verizon packages with the phone, and discovered that directly before attempting the reflash the phone from download mode, the installer drops the following file, which by comparison to others I have found, appears to be a firehose. Additionally, the certificate inside the file matches Alcatel/TCL and seems to be for this platform.
I have tried on my own device with no success. However, I'm beginning to draw the conclusion that my phone may have been factory defective, since I cannot reset it successfully, and others do not seem to have the same problems with their devices as I do.
Nonetheless, it may be worth it for someone to try using the file in the common Qualcomm utilities like EFS Explorer and QPST to see if its possible to pull ( and hopefully push ) files to and from these devices - like the full bootloader partition.
I'm going to give it a go and see what happens
ᐯerified Developer said:
I'm going to give it a go and see what happens
Click to expand...
Click to collapse
Any go?
Honestly it's been a min I was trying to figure it out but I can't get my phone to detect on QPST I remember when I originally had gotten the phone I was able to get it to pull up like diagnostic mode and then it would pull up under EFS and stuff I'm not no pro or anything when it comes on stuff like that I was just looking through the files and what not trying to figure it out but anyway I have updated my phone knowingly I shouldn't have and I just can't seem to get it back recognizing on my computer at least under that mode so I'm not sure hopefully this makes sense
I have downloaded an android 13 GSI on my infinix zero 8i and after installing magisk the wifi and bluetooth completely stopped and I figured the reason is the driver got wiped some how since when I try to view the certificate for the WiFi or Bluetooth it gives me unavailable, I got a stock rom on my PC and its got a file called md1img.img and I am pretty sure it is the modem driver because on the product info txt file in the firmware file it says modem a couple times under md1img, I tried to flash it by typing fastboot flash md1img md1img.img and I keep getting the error that the directory does not exist, how do I flash the driver?
also the UI becomes really slow sometimes after the device has been on for a little, its not that important but is there a fix for that too?
also also not so important, the camera notch is obstructing a lot of the notifications and time, is there a fix for that?
PS. I do not want to flash the stock ROM I have already wasted an entire weekend trying to get the GSI installed so please don't suggest that
PS PS. I understand close to nothing on the subject matter so if you have a soloution please type it out step by step so I don't brick my phone again.