I've had my NT for about a week and was able to sideload just about everything I wanted without doing a root. Then the dreaded 1.4.1 upgrade struck and I was unable to do anything more. I was able to revert back to 1.4.0, and do a factory reset to get everything working again. Then decided to take the plunge and use Indirect's root process. (yes, it was a big decision because I said I would avoid it if possible).
The problem is, I can't past the first step. I've enabled USB debugging and downloaded the files I need, but the NT will not show up in the device manager with the "!" symbol. I've read through all the threads and tried a number of different things, but the NookandZergy program will not identify the NT.
I think I'm stuck, if I stay where I am I will get hit with the OTA upgrade again, but I can't seem to work through the process to change it.
Any ideas?
Hello @Barry4405 read this: [FAQ] NT Tips & Tricks, How to's | NEWBIE? Having issues? - Please READ! the DRIVERS ISSUES section.
Veronica
Or, rather I should say, "What am I missing ??"
What you are experiencing is a drivers issue use the link i posted below, there you will find a link to a step by step guide to setup drivers and fix this problem.
Veronica
SUCCESS !!!
This forum is AMAZING. I double checked the link you suggested and found what I had missed. It took me about four attempts but I finally was able to get the driver to work, and everything worked great after that.
Thank you so much!
OK, thanks to my own ineptitude I am back to square one.
After installing the root I somehow messed up the launcher, couldn't get to ADW and had no web access. I figured the quickest fix would be to start over again. I did an install of 1.4.0 and wiped everything clean. I followed the instructions that I used before to get the ADB drivers working, and they will not work. Everytime I connect the NT it shows up as drives E and F and windows insists on installing the drivers, even though I have disabled the auto installation.
I've used USBDeview utility and checked and double checked the USB debugging, it still insists on installing drivers for it.
What am I missing???
OK, I think I solved it. Shortly after I sent the last message it occured to me, "I don't need to look for and install the drivers I need, they're already there from the last time." Sure enough, I connected the NT and ran Zerg and..Bazinga. I have a rooted NT again.
Related
Hey Xda-developers. Just quickly, I found this Forum from a few links on other websites (gizmodo, engadget) and some youtube videos of your awesome custom ROMs.
I for my HTC Hero in March, and I should be upgrading around christmas 2011. That's a while, and Android grows fast..much much faster than HTC update my device, so I'm thinking a custom ROM is what I really want.
I've done my research, but honestly I'm pretty much a noob here. I know I need to root the phone, but I've been unable to find any specific instructions for 3 UK, and as far as I can tell all the different carriers use different instructions (a different ROM to downgrade to?), so I don't want to use the wrong ones.
-
Phone Spec
Okay, this is a standard HTC Hero on a 24 month contract carried by 3 UK.
There has been no rooting, no major changes. I have done no more than officially supported. A complete from scratch root would be required.
Currently running 1.5.
UK, 3 Mobile, GSM.
No hardware replacements and no known issues with the phone.
-
I think that's about all, is somebody here able to point me to the right place for a 3 mobile root?
Thanks in Advance,
Callum.
I'm also on 3uk and i rooted my phone using the following guide:
http://androidforums.com/all-things-root-hero/54802-how-root-install-custom-rom-backup-more.html
Hope this helps.
Thankyou very much for your help! I'll be giving that guide a go later.
No probably m8, SenseHERO is a good custom ROM.
Any trouble just post up and ill try and help you out.
Hmm, if I could ask you to take a look at a post, that'd be really helpful. No worries if you don't have a clue though.
Hero, G2 Touch Android Development >
[Guide] Complete Newbie Guide to Install a Custom Rom & Newbie FaQ [Updated 02/05] >
Page 33, Post 1.
Sorry that link is so bad, but they won't let me post a proper one.
That thread was alternative 2 for the 3uk guide you gave me (goldcard section). I'm not sure whether you'll be able to help me, but if you could take a look that'd be massively helpful.
Cheers,
Callum.
I posted a reply to more or less the same problem earlier.
http://forum.xda-developers.com/showpost.php?p=6701261&postcount=268
Let me know how you get on.
Thankyou very much for your reply, but I have already done all of this. I've successfully performed a goldcard on my SD and I'm really close to getting a working custom ROM, but it's dying somewhere there. I have already installed the x64 drivers though.
HTC Sync works perfectly, picking up the phone and synchronizing on demand.
Thanks,
Callum.
What guide are you using, i used this was one to create a goldcard and downgrade:
http://forum.xda-developers.com/showpost.php?p=5855697&postcount=1
The only problem i had was syncing after installing the latest version. I fixed it by downloading a driver manager and updated the drivers for it.
I take it it lets you mount the SD card on your computer?
One thing that might be worth a try is to download the ROM again, it might be corrupt, a shot in the dark but worth a go.
That's the guide I ended up at, after following a link within the guide you provided above.
It does indeed allow me to mount the SD card, everything syncs perfectly. I'll give re-downloading the ROM a go, though. There was two available, so I'll try the other download.
Hmm, I've tried everything I can think of, and nothing is working on this Windows 7 machine. My brother's XP machine is broken, and my dad's away with the XP notebook.
Is there any way that anybody knows of to run XP as a virtual machine temporarily?
Here's a link for a virtual box:
http://www.virtualbox.org/wiki/VirtualBox
I dont know how to run it though.
Someone had a similar problem on win7 yesterday and sorted it by getting a new gold card. Might be worth a try?
Aha, I re-downloaded goldcard, and switched the driver to My HTC once with it normally plugged in, then with bootloader open. And it downgraded!
I've got the Scenehero on the SD card now, I'm just unable to launch the custom recovery screen. It will start normally by hitting power, but while the home button is also held it just loops the first hero screen. Is there any way past that, because I need to perform a wipe and flash scenehero.
Thanks so much for your help so far, you've been amazing!
If your all set up properley you should be able to connect your phone via usb to the PC,
then open a command window and type>"adb shell devices"
your phone should show in the window something like HTLK12345
now type> "adb shell reboot recovery"
this should boot your phone into recovery mode.
Hope this helps.
Thankyou very much for your help, I solved the problem by re-installing my recovery. Not sure what went wrong but it worked after that. All looks good now!
good stuff m8, glad your sorted.
what rom are you running?
I'm currently using the latest version of Sensehero. Really pleased with it so far.
I'm on branch 3, waiting for branch 5, should be here soon hopefully.
If you have'nt already m8 check out the site:
http://www.htcdevscene.co.uk/
Some top lads over there having a good time!!.
Hello All!
Relative noob here...but more seasoned all the time. Firstly my viewpad device info from FTM:
SWVer=3.410
Model: FM6-001
HWVer: 107
In a nutshell: My bluetooth wasn't turning on (would turn on..then off). So tried to fix by:
1) Rooting and install CWM 5.0.2.6 (awesome tool BTW) and various ROMs, all done with success.
2) No good, oh well now want to give up. Contacted Viewsonic got RMA to return unit..however now concerned they'll not honor warranty if I rooted the device (sigh). So thought I'd return to stock. I did backup..but was already rooted when I thought of it.
3) Trying to return to stock using many versions Sutl3 and Sutlr...and on different PCs none work..once it boots to CWM menu...just stalls with error eventually.
4) Tried to install Napster's CWM with Recovery Menu to be able to return to original state with stock recovery. My version of CWM won't install it...errors out (another great tool though by the sounds of it).
5) Can't use fastboot..never sees device...although ADB works OK. Believe that the Bluetooth issue may be a hardware problem and may be effecting devices ability to work in "download mode". Note that HS-USB device is never present in device manager in Windows even though driver is installed.
So...my question...how can I return my device to stock with one of the below .nb0 files without stock recovery, sutlr or sutl3?
Files I have:
FM6-3310-0-5029-A02.nb0
FM6-3350-0-1008-A01.nb0
Can I somehow use CMW? Can I somehow use adb and "flash_image"?
Will super appreciate any thoughts!
Many thanks in advance!
Johnster25
If I remember correctly, you use SUTL3 from Viewsonic on your PC with the *.nb0 file in the same sub/directory - and just run it to flash the stock ROM or return it to factory condition, you do NOT use CWM to flash or re-install the *.nb0 file ... Part of this process involved overwriting the CWM installed on your rooted device & reversing it to become unrooted, look under the Development subforum here in this section as there's a link/discussion about how to restore, please double check on the details written up.
Also, make sure you have a mSD card in the slot - and that the USB drivers are loaded & running (they should be installed already back then) - might want to power down & restart the PC and do the same to the Vpad7.
Let us know how it go & good luck !
Many thanks for your response.
Well, what has happened when I've used SUTL3 so far is that I select the .nbo image I wish to flash, then the program restarts teh VPAD7 into recovery mode.
From what I've read, after a few moments the phone is then supposed to enter some sort of "download mode" whereby the new image is pushed across the USB cable.
It's at this point with SUTL3 seems to error out, and the phone simply remains in CWM.
I've read a few posts that suggest that not using the correct image could produce a response like this, so I'll retry again this PM having tried re-downloaded the two .nbo files I've tried, and one I've not tried.
Will let you know how it goes!
J.
Hi Again,
OK I've retried it with a fresh copy of SUTL3, and new .nb0 files. Still no good.
Take a look at the enclosed pictures. The first time I try to run SUTL3 the device not configure error shows up. By this point CWM is showing on the VPAD7. I try to run SUTL3 again in this state and now the device not detect error shows up.
So all in all it seems to me that the device when in CWM mode is not exposing an interface to the computer...or the computer lacks the driver needed to utilize the interface.
I've also enclosed a picture of my windows devices when the VPAD7 is connected, as well a copy of the drives that show up when it's connected. The only time the drives change is when the VPAD7 is in CWM mode, at which time the H: drive (where the adb program are) is not present.
So am I missing a driver?
BTW: Have tried to copy down the synchronization program that is on the H: Drive and ran it while running SUTL3...thinking somehow it acted like a bridge to the VPAD7 (I've seen some posts that suggest this). Still no good.
J.
OK..one more piece to the puzzle...or maybe off the trail...but when trying on two differnt PCs when the VPAD7 is first plugged in I get one set of driver installs...and note that the HS-USB has an error.
Later when trying to run SUTL on it...another set of driver installs...again HS-USB error.
See enclosed.
try run sutl with viewpad in FTM mode that worked for me good luck
I have same problem before..n my solution is change back CWM with old ..mine to CWM 2.5.1..found that CWM 5.0.2.6 got problem with SUT L3..and everythind done successfully..as long u can still access ur Viewpad to change CWM its ok..
Wow! Thanks so much for your reply! This would be a huge help. Any idea where I might be able to find that older version of CWM?
Alleycatzero you're a genius! Running SUTL in FTM mode has done it!
THANK YOU!!!!!!!!!!!!!!!!!!!!!!
Johnster25 said:
Wow! Thanks so much for your reply! This would be a huge help. Any idea where I might be able to find that older version of CWM?
Click to expand...
Click to collapse
This is under the Development section - just d/l and unpack the zip file, copy to mSD card & follow the instructions. This verison should be the earlier one and I personally find it worked best together with ext3 and/or ext4 partitioning as needed.
http://forum.xda-developers.com/showthread.php?t=1015005
The issues with SUTL3 and other apps not working/running has to do with the usb drivers not auto-installing & running as they should, try to uninstall Vpad7 drivers, reboot the PC - turn off any firewall and anti-virus software, connect the Vpad7 and let it finish installing/rebooting both devices again. Then, turn back on antivirus & firewall so that you will have easier time flashing rom, connecting mSD card & copying/moving files, etc.
Hi,
so I have been using this root guide for my HTC G2 http://forum.xda-developers.com/showthread.php?t=2448887 ,and like in the video, when I opened the first screen to imput code, my phone did not show up. Have I forgotten to install something? it just says searching even though my phone is connected to my computer.
any help is appreciated, rooting is turning out hard for me to do, thank you
SuperSho4 said:
Hi,
so I have been using this root guide for my HTC G2 http://forum.xda-developers.com/showthread.php?t=2448887 ,and like in the video, when I opened the first screen to imput code, my phone did not show up. Have I forgotten to install something? it just says searching even though my phone is connected to my computer.
any help is appreciated, rooting is turning out hard for me to do, thank you
Click to expand...
Click to collapse
Hey SuperSho4,
I'm afraid you need to give a little more information what exactly you are doing, i.e. which software you are using etc. Do you see your phone in lsusb?
I'm using Ubuntu and the latest adb, and I have to be root on my computer for adb to work and find my phone.
You also may try another way of rooting, e.g. I used UniversalAndroot-1.6.2-beta5.apk to do that, which you can transfer to your SD-Card and then select for installation with probably any File Browser, (just make sure that you enabled "other software sources").
For me. there's was a quirk in that method: Using the default settings, UniversalAndroot only claimed to successfully get root-access, but left everything unchanged! Only after finding a comment on some website did I try to check both check-boxes (log and temporary install) - this time it worked (it installs yet another app called SuperUser)! (I then ran it again without the temporary setting enabled, which at least did not revoke the SuperUser-Account).
Good luck!
Hi all,
I recently got a new Dell Venue 7 3740 (yeah, not my first choice, but it was free for buying a computer). Anyway, started reading up on how to root the thing. I have a couple of apps that require root.
I found this thread: http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
and also the main Dell page: http://opensource.dell.com/releases/Venue_7_3740_Merrifield/developer-edition/
Following Dell's guide to rooting appears to NOT root it. Installing Root Checker confirms I don't have root. Unbricked it and got it back up from 4.4.2 to 4.4.4. By reading the first guide for the 3840, my question is ...
Is the boot image linked there compatible with my 3740?
(yeah, I know this should be in the developer section ... unfortunately I don't have enough posts ... also, I am familiar with rooting/flashing/etc, my first device that I put CM7 on was the original Galaxy S1 ... and I have CM10 on my S3.)
Tried, failed
Yeah I got this tablet with a PC too and tried rooting. It FUBAR'd on me and I had to wrestle with unbricking it. Which sorry to say is a job and a half, the images on Dell's site are corrupt for this WiFi only version (no partition.tbl file, system image incomplete). Ending up downloading the LTE versions firmware to get the missing files and rewriting the batch as the file names for the fastboot commands were wrong too. And even then the tablet wouldn't boot, so I had to store the OTA on an SD card and use recovery to flash it. Unfortunately that leaves me with 4.4.2 and the dreaded clock and browser issues. And OTA doesn't work, it keeps saying no updates are available. Spoke with a Dell rep who said OTAs were suspended and to try again in a week but I think OTA was broken for me when I tried rooting and boot loader was unlocked (which the PDF on Dell's site warns you about).
So now I have a working tablet that skips hours ahead and has general stability issues.
reaper-death said:
Yeah I got this tablet with a PC too and tried rooting. It FUBAR'd on me and I had to wrestle with unbricking it. Which sorry to say is a job and a half, the images on Dell's site are corrupt for this WiFi only version (no partition.tbl file, system image incomplete). Ending up downloading the LTE versions firmware to get the missing files and rewriting the batch as the file names for the fastboot commands were wrong too. And even then the tablet wouldn't boot, so I had to store the OTA on an SD card and use recovery to flash it. Unfortunately that leaves me with 4.4.2 and the dreaded clock and browser issues. And OTA doesn't work, it keeps saying no updates are available. Spoke with a Dell rep who said OTAs were suspended and to try again in a week but I think OTA was broken for me when I tried rooting and boot loader was unlocked (which the PDF on Dell's site warns you about).
So now I have a working tablet that skips hours ahead and has general stability issues.
Click to expand...
Click to collapse
Hmm ... Interestingly enough, I ran through the unbrick procedure from Dell, and didn't have any issues with it whatsoever. I'm not sure if they updated the TGZ since you updated.
I have read that root is for ADB to start with. Can anyone confirm this? If so, then which package could I get for a superuser binary?
ProfM2 said:
Hmm ... Interestingly enough, I ran through the unbrick procedure from Dell, and didn't have any issues with it whatsoever. I'm not sure if they updated the TGZ since you updated.
I have read that root is for ADB to start with. Can anyone confirm this? If so, then which package could I get for a superuser binary?
Click to expand...
Click to collapse
I did this process just a couple days ago so everything I pulled from opensource.dell was current. The unbrick tgz on the site shows up as 128mb for the wifi only A1195 and the A5195 shows as 821mb (odd). When I extracted the tgz it said "unexpected end" or something like that on the system image. Then again when I extracted from that extracted tgz.
Following the root process initially worked and the temp cwm recovery let me flash the supersu update. It booted with su just fine and I tried a couple apps that needed root and they worked. Once I rebooted again the tablet showed up with a USB icon and would go no further. Never having dealt with Intel SoC drivers it took me a while to get them installed properly, and then I eventually understood what "full power off" meant lol.
Do you know how I can relock the bootloader and get OTA working again, assuming I'm already on 4.4.2 from the OTA zip installed via recovery?
Thanks.
reaper-death said:
I did this process just a couple days ago so everything I pulled from opensource.dell was current. The unbrick tgz on the site shows up as 128mb for the wifi only A1195 and the A5195 shows as 821mb (odd). When I extracted the tgz it said "unexpected end" or something like that on the system image. Then again when I extracted from that extracted tgz.
Following the root process initially worked and the temp cwm recovery let me flash the supersu update. It booted with su just fine and I tried a couple apps that needed root and they worked. Once I rebooted again the tablet showed up with a USB icon and would go no further. Never having dealt with Intel SoC drivers it took me a while to get them installed properly, and then I eventually understood what "full power off" meant lol.
Do you know how I can relock the bootloader and get OTA working again, assuming I'm already on 4.4.2 from the OTA zip installed via recovery?
Thanks.
Click to expand...
Click to collapse
You better redo the unbrick procces cause as you are now, you won't be able to update your tablet and 4.4.2 has some issues with the clock and browser. The best way to root is by thetered cwm, I did it and it's working great.
reaper-death said:
I did this process just a couple days ago so everything I pulled from opensource.dell was current. The unbrick tgz on the site shows up as 128mb for the wifi only A1195 and the A5195 shows as 821mb (odd). When I extracted the tgz it said "unexpected end" or something like that on the system image. Then again when I extracted from that extracted tgz.
Click to expand...
Click to collapse
This is quite odd. From the documentation, it appears that the A195 is for the LTE version, and the A150 is Wifi only. Since I have the 3740 Wifi only, I only pulled the A150 version.
The Unbricking process was very straightforward and everything went smoothly, and after it rebooted, it prompted that there was a system update from Dell, and that took me from the 4.4.2 from the TGZ, to 4.4.4
ProfM2 said:
This is quite odd. From the documentation, it appears that the A195 is for the LTE version, and the A150 is Wifi only. Since I have the 3740 Wifi only, I only pulled the A150 version.
The Unbricking process was very straightforward and everything went smoothly, and after it rebooted, it prompted that there was a system update from Dell, and that took me from the 4.4.2 from the TGZ, to 4.4.4
Click to expand...
Click to collapse
http://opensource.dell.com/releases/Venue_7_3740_Merrifield/developer-edition/Doc/OSS_A150&A195.pdf
* For Wifi-only device on A150 and Wifi / LTE device on A195
I see it now, I think I was misinterpreting the above statement which means I've been flashing the A195 rom this whole time. Thank you all for your help! :good:
After getting my 3740 back to "Unbricked" mode, and OTA upgraded to 4.4.4, it appears that I'm completely locked out of the rooting process.
I've tried to start over with the Dell info (unlocking bootloader), however, neither of my PC's will detect the tablet when using xFSTK (one PC - Win8.1-64bit, other XP-32bit). The tablet IS detected, however, it appears that the drivers are no longer correct(?).
I normally run Ubuntu, and thats where my Android development setup is on ... I see that xFSTK is available for Linux ... has anyone used it? or would I be better trying to fight Windows?
ProfM2 said:
After getting my 3740 back to "Unbricked" mode, and OTA upgraded to 4.4.4, it appears that I'm completely locked out of the rooting process.
I've tried to start over with the Dell info (unlocking bootloader), however, neither of my PC's will detect the tablet when using xFSTK (one PC - Win8.1-64bit, other XP-32bit). The tablet IS detected, however, it appears that the drivers are no longer correct(?).
I normally run Ubuntu, and thats where my Android development setup is on ... I see that xFSTK is available for Linux ... has anyone used it? or would I be better trying to fight Windows?
Click to expand...
Click to collapse
It is mentioned somewhere that the 3740 and the 3840 use the same firmware. Assuming that, what you can do is download the latest SuperUser zip, copy it to the internal or external storage, then use THIS, or THIS to root through CWM.
graphdarnell said:
It is mentioned somewhere that the 3740 and the 3840 use the same firmware.
Click to expand...
Click to collapse
Hmmm ... I took this to mean that I could use the same boot.img as the Venue 8, and tried the process from this thread: http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
NOPE. (Don't try, it'll cause the tablet to go into the "help my androids' fallen and can't get up" icon. )
ProfM2 said:
Hmmm ... I took this to mean that I could use the same boot.img as the Venue 8, and tried the process from this thread: http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
NOPE. (Don't try, it'll cause the tablet to go into the "help my androids' fallen and can't get up" icon. )
Click to expand...
Click to collapse
I'm curious as to what it is you're trying to do. Why do you insist on having a developer's root (just the use of ADB shell), as opposed to full root flashing SuperSu from custom recovery?
graphdarnell said:
I'm curious as to what it is you're trying to do. Why do you insist on having a developer's root (just the use of ADB shell), as opposed to full root flashing SuperSu from custom recovery?
Click to expand...
Click to collapse
I just want full root.
Most of the info that I've read on here and elsewhere are geared to the 3830/3840. Not as much for the 3740. So, by playing with the device and learning what works/doesn't work, possibly others may find this info useful to them.
I've been having issues seeing the device from XP, Win8.1 and Ubuntu, in the 'off' state of the tablet, when the PC should be seeing the merrifield. Just this morning, after bricking it last night, I discovered that my PC seems to see the device right away if I press Vol+ while plugging in the microUSB. (again, something that may help someone else) I was planning on double checking this info later today, to make sure that it wasn't a fluke.
I do appreciate both of the links that you've posted in this thread, and I will check them out. Of course, both are labelled for the Venue 8, not the Venue 7 that I have. Since I've gained knowledge on the unbrick process I feel more comfortable trying them.
I've installed (or tried to install) SuperSU from the Play store, but it didn't appear to help much, since I didn't have the custom recovery setup at that time. I'll work on that tonight.
ProfM2 said:
I just want full root.
Most of the info that I've read on here and elsewhere are geared to the 3830/3840. Not as much for the 3740. So, by playing with the device and learning what works/doesn't work, possibly others may find this info useful to them.
I've been having issues seeing the device from XP, Win8.1 and Ubuntu, in the 'off' state of the tablet, when the PC should be seeing the merrifield. Just this morning, after bricking it last night, I discovered that my PC seems to see the device right away if I press Vol+ while plugging in the microUSB. (again, something that may help someone else) I was planning on double checking this info later today, to make sure that it wasn't a fluke.
I do appreciate both of the links that you've posted in this thread, and I will check them out. Of course, both are labelled for the Venue 8, not the Venue 7 that I have. Since I've gained knowledge on the unbrick process I feel more comfortable trying them.
I've installed (or tried to install) SuperSU from the Play store, but it didn't appear to help much, since I didn't have the custom recovery setup at that time. I'll work on that tonight.
Click to expand...
Click to collapse
A quick word on getting the device recognized in off mode, what worked for me was it needs to be completely powered off and nothing showing on the tablet screen then connect and bring up the device manager. Whatever shows up needs to be "Intel SoC" so change the driver to that if needed. When flashing firmware to unlock the bootloader the device's boot screen will show an "Intel Inside" logo instead of the normal "Dell" logo. I ended up running xFSTK commands in advance (they'll wait) and then running over to hook up the tablet (powered off) via USB as for some reason it'll show up and then I hear "da-Dunk" in Windows (device disconnected) after a short while which interrupts the process (same with fastboot commands). This was the unbrick process in a nutshell for me and I'm leaving it now as is (OTA'd to 4.4.4) until hopefully the supposed update to Lollipop comes around and maybe some progress is made on rooting it.
Hope this helps you!
reaper-death said:
A quick word on getting the device recognized in off mode, what worked for me was it needs to be completely powered off and nothing showing on the tablet screen then connect and bring up the device manager. Whatever shows up needs to be "Intel SoC" so change the driver to that if needed. When flashing firmware to unlock the bootloader the device's boot screen will show an "Intel Inside" logo instead of the normal "Dell" logo. I ended up running xFSTK commands in advance (they'll wait) and then running over to hook up the tablet (powered off) via USB as for some reason it'll show up and then I hear "da-Dunk" in Windows (device disconnected) after a short while which interrupts the process (same with fastboot commands). This was the unbrick process in a nutshell for me and I'm leaving it now as is (OTA'd to 4.4.4) until hopefully the supposed update to Lollipop comes around and maybe some progress is made on rooting it.
Hope this helps you!
Click to expand...
Click to collapse
I have finally settled down and got the tablet rooted. What's really odd, was Win8.1 kept losing the proper driver. I'm not sure exactly why ... but suffice it to say, I got it working. It did appear to be more stable when I hit the Vol+ and plugged in the USB, but then again it may have been a coincidence.
Open source dell
If you follow the link to dell open source, they do have a detailed PDF download for unlocking the boot loader etc. The file was too large for me to upload on XDA. I just found it today while I was researching how to root this tablet. I have not had a chance to try it yet.
http://opensource.dell.com/
That doesnt work for 3740 lte. I;ve done everything that was in PDF. OTA image should be with unlocker bootloader and root but its not. ;/
Its adb root not su big difference
Does anyone have any idea to root dell venue 7 3740 lte
The open source is for venue 7 3740 wifi
how can i hard reset this device please tell me.
Mahisasur said:
how can i hard reset this device please tell me.
Click to expand...
Click to collapse
Reset any android tbalet with ...
Setting >>>>> Backup & Reset >>>>> Factory Data Reset >>>>> Reset Tablet >>> Erase Everything
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: