Related
Good morning everyone.
First of all I want to apologize for my english, that I'm afraid it's very poor.
My question goes next: I bought an used Samsung Galaxy tab 2 7'' p3100 3G and it has a very big problem. It can't be connected to any pc, windows or mac. It's not a drivers' problem, so when the device is connected, the pc does nothing. Not even a display in the device manager, or a noise. However, it usually charges. I say usually because sometimes the icon battery shows a red ray, but it charges spending more time. That's all. It has been proved with three different original cables in several computers running different SO.
I don't know if it's a connector problem or it's a Rom one. It has an operator locked SO with Android 4.0.4 that not even shows the OTA update option in the menu. And I cannot select the way I want to be connected by usb in the "Storage" options.
The fact is I cannot update the device and I cannot root it in order to install a better rom or an original stock one.
I've googled all I can do to find a way for rooting the device, but all the roads drive me to the same point: Odin. The software I cannot use because my device can't be connected to any Pc.
I know this forum is my last chance. There are some ways like z4root or framaroot that work in another devices (Galaxy S for example, I think), but they have not been ported to my device. I think my chances are to make it by an apk o perhaps flashing a signed file from the original recovery.
I just need to install a simple clockword mod or having the device temporary rooted to install and run the Odin's apk that allows me to install a pre-rooted rom, an open recovery... Just a simple step for one man, But the Colorado's Canyon for me in my situation.
If someone of you know any solution or want to help me, I'll be truly grateful. And I didn't even mind to pay him for his help.
Thank you very much in advance.
Even_Flow said:
Good morning everyone.
First of all I want to apologize for my english, that I'm afraid it's very poor.
My question goes next: I bought an used Samsung Galaxy tab 2 7'' p3100 3G and it has a very big problem. It can't be connected to any pc, windows or mac. It's not a drivers' problem, so when the device is connected, the pc does nothing. Not even a display in the device manager, or a noise. However, it usually charges. I say usually because sometimes the icon battery shows a red ray, but it charges spending more time. That's all. It has been proved with three different original cables in several computers running different SO.
I don't know if it's a connector problem or it's a Rom one. It has an operator locked SO with Android 4.0.4 that not even shows the OTA update option in the menu. And I cannot select the way I want to be connected by usb in the "Storage" options.
The fact is I cannot update the device and I cannot root it in order to install a better rom or an original stock one.
I've googled all I can do to find a way for rooting the device, but all the roads drive me to the same point: Odin. The software I cannot use because my device can't be connected to any Pc.
I know this forum is my last chance. There are some ways like z4root or framaroot that work in another devices (Galaxy S for example, I think), but they have not been ported to my device. I think my chances are to make it by an apk o perhaps flashing a signed file from the original recovery.
I just need to install a simple clockword mod or having the device temporary rooted to install and run the Odin's apk that allows me to install a pre-rooted rom, an open recovery... Just a simple step for one man, But the Colorado's Canyon for me in my situation.
If someone of you know any solution or want to help me, I'll be truly grateful. And I didn't even mind to pay him for his help.
Thank you very much in advance.
Click to expand...
Click to collapse
Have you manually installed the drivers? If not, download the samsung drivers, install and try again. Read through the link below to find the drivers.
http://forum.xda-developers.com/showthread.php?t=2510669
cwyman said:
Have you manually installed the drivers? If not, download the samsung drivers, install and try again. Read through the link below to find the drivers.
http://forum.xda-developers.com/showthread.php?t=2510669
Click to expand...
Click to collapse
Unfortunately yes. I've tried with several versions of Kies, by installing manually the drivers and it doesn't work. The fact is I connect the device and the pc does nothing. Not even the device manager shows a new device or is alterated in some way. It's like one data pin in the connector was damaged or the rom was corrupted and it doesn't let the device be recognized.
I think my only chance is to make everything inside the device. By sd in the boot manager or with an apk. If not, I'm condemned to an obsolete device that could not even be updated.
Thanks for trying to help me.
Even_Flow said:
Unfortunately yes. I've tried with several versions of Kies, by installing manually the drivers and it doesn't work. The fact is I connect the device and the pc does nothing. Not even the device manager shows a new device or is alterated in some way. It's like one data pin in the connector was damaged or the rom was corrupted and it doesn't let the device be recognized.
I think my only chance is to make everything inside the device. By sd in the boot manager or with an apk. If not, I'm condemned to an obsolete device that could not even be updated.
Thanks for trying to help me.
Click to expand...
Click to collapse
This may sound absurd, but try a different version of the drivers. I had to install like a dozen drivers before it worked
mirzafran said:
This may sound absurd, but try a different version of the drivers. I had to install like a dozen drivers before it worked
Click to expand...
Click to collapse
I agree. The drivers can be so touchy. I'd uninstall and reinstall drivers numerous times before giving up. Good luck!
Sent from my GT-p511x
your cable is faulty. Get another one on ebay cheap.
I'm afraid I've tried with three different cables, as I said (one of them original from Samsung and new), two Windows Pc's, one mac and about fifteen different drivers.
Believe me: I've rooted with no problem more than twenty different devices (and jailbreaked another ones ) and this is the first time I cannot make it.
Think it's a hardware problem or a corrupted rom one. In both cases I have to root it by an apk or a flash from the sd.
Anyway, I appreciate very much your help, boys.
Even_Flow said:
I'm afraid I've tried with three different cables, as I said (one of them original from Samsung and new), two Windows Pc's, one mac and about fifteen different drivers.
Believe me: I've rooted with no problem more than twenty different devices (and jailbreaked another ones ) and this is the first time I cannot make it.
Think it's a hardware problem or a corrupted rom one. In both cases I have to root it by an apk or a flash from the sd.
Anyway, I appreciate very much your help, boys.
Click to expand...
Click to collapse
I'm in a similar situation with a Galaxy Tab 2 p3113tsyxar
It is not recognized by any computer, and my next step is to try another cord manana. Until then (hopefully) I've got a nice paperweight.
You have not rooted ur tab till now......so u have not played with your firmwares! So its better to visit a samsung store. If you have warranty then they will do it in free.(And your android will also get updated!)
If I helped you, just press thanks!
Tech Specs:
Processor Type: Quad-Core Cortex A9 Processor(When I turn on the tablet it says Allwinner A31?)
Processor Speed: 1.20 GHz
System Ram: 1 GB
Hard Drive Size: 8GB
Laptop Screen Size: 7 inch
Screen Type: Capacitive Touch Display
Battery Life: 4 hours
Battery Type: 2800mAh Lithium Ion
Network Connection: 802.11b/g/n Wireless LAN
Connector Type: 1 x HDMI, 1 x Headphone, 1 x MiniUSB 2.0
Operating System: Google Android
Accessories Included: AC Adapter,USB Cable
Operating System Version: Android 4.2 Jelly Bean
This thread is a continuation of some of the discussion that was from this thread: http://forum.xda-developers.com/showthread.php?t=2568427
While not at all high end tablets, it's always fun to see what can be squeezed out of them! As stated in the title, this thread will be regarding the following devices: Nobis NB07, Iview 774TPC, and DA-741QHD (which all appear to be the same hardware) rooting and ROMs. That should be pretty simple for now since, we currently have no ROMs and no proven root method. Some have reported success using the Kingoapp. If anyone is able to obtain root, we would like to ask that you make a copy of the firmware and upload it for those of us having trouble doing so. After doing so, we can modify it and hopefully get more our of the software.
You may also post information regarding tweaking the ROMs for these devices and other ways to make them more useful!
Warning: The following may have unforseen effects including breaking your tablet to the point of being unrepairable.
Option #1, Use KingoApp Some users have reported that this did not work for them, at least one user reported that it did.
Instructions per RawX:
For the drivers the easiest method is just using Top Notch Tablets How to install ADB drivers. That worked on the first one, the second one it didn't not entirely sure why, but you can send a email to support and ask them for development drivers for the nobis tablets and they will send the ADB drivers you need. After you have the drivers installed use kingo while the tablet is in usb debug mode BEFORE plugging it into your usb port and do not turn on usb transfer. the first time after it reboots kingo will report that it was not rooted, leave it plugged in and power off and back on and it should report the root worked. This method gives you SuperSU. Both times. I've done this were for clients of mine but its pretty straight forward.
Click to expand...
Click to collapse
The working drivers for me were: VID_1f3a_PID_efe8
Please consider trying this first and give us some feedback. A word of warning though, there has been some discussion on XDA in the past that this may be malware though I'm not sure this was ever confirmed.
Option #2, Flash firmware for an alternate device that can be rooted easily. Warning!!! Currently, there is no way to get back to stock (until someone who gets root with another method makes a copy of the firmware)
Go to this website: http://www.iviewus.com/firmware788TPC/ and download the firmware. Yes, it is for another tablet. However, the tablet appears to have the same specs as ours. Once downloaded. Install the included PhoenixSuit software. Once it is running, click the button at the bottom right to update the software to the newest version (this may not be required). Then, plug in your tablet using the usb port and install the drivers. I used google and found them all within minutes. Once the software recognizes your tablet go to the firmware tab where you have extracted the .img file and select the file. Next, click upgrade to upgrade your tablet (it has instructions to help your tablet be recognized if you are having difficulty). Once the new firmware has been flashed, then download the file RootFromOTA.zip that can be found on various places such as XDA. Move the file onto an external SD card. Then, go to settings -> backup & reset -> Recovery Mode. Your tablet will restart. Once it does, select the bottom option to install from SD card. Install the RootFromOTA.zip and then reboot. Once rebooted, install the supersu app or another root application of your choice.
Credits: As above to RawX
Congrats... You're rooted.
Mods
Currently, I've managed to get great battery life out of my tablet by installing kernel tuner and changing the settings as such:
Governor: Ondemand (default is fantasys)
Max: 1200 MHz (Default is 1200 MHz)
Min: 240 MHz (Default is 120 MHz, but I had trouble with usability at this setting and Ondemand)
I also recommend setting wifi to turn off when the screen is off and turn off autosync.
This seemed to give me a very useable system but with greatly improved battery life. Doing the above and a few other tweaks here and there have made my battery life so that it drains by about 1% overnight when not in use. I also seem to get better battery life while using the tablet. I haven't had any trouble playing games either.
neatojones said:
Option #2, Flash firmware for an alternate device that can be rooted easily. Warning!!! Currently, there is no way to get back to stock (until someone who gets root with another method makes a copy of the firmware)
Go to this website: http://www.iviewus.com/firmware788TPC/ and download the firmware. Yes, it is for another tablet. However, the tablet appears to have the same specs as ours. Once downloaded. Install the included PhoenixSuit software. Once it is running, click the button at the bottom right to update the software to the newest version (this may not be required). Then, plug in your tablet using the usb port and install the drivers. I used google and found them all within minutes. Once the software recognizes your tablet go to the firmware tab where you have extracted the .img file and select the file. Next, click upgrade to upgrade your tablet (it has instructions to help your tablet be recognized if you are having difficulty). Once the new firmware has been flashed, then download the file RootFromOTA.zip that can be found on various places such as XDA. Move the file onto an external SD card. Then, go to settings -> backup & reset -> Recovery Mode. Your tablet will restart. Once it does, select the bottom option to install from SD card. Install the RootFromOTA.zip and then reboot. Once rebooted, install the supersu app or another root application of your choice.
Congrats... You're rooted.
Click to expand...
Click to collapse
I am assuming the camera is not working using this method or did you figure it out?
And also, do you have a link to the drivers you used off hand or what did you search for to find them?
Hippie459MN said:
I am assuming the camera is not working using this method or did you figure it out?
And also, do you have a link to the drivers you used off hand or what did you search for to find them?
Click to expand...
Click to collapse
Nope, still haven't gotten the camera working. We are missing some config files still. Do you need the camera drivers or the tablet drivers?
The camera drivers are : sp2518 and sp0838, though I also see a module being loaded called cam_detect
I don't recall where I got the adb usb drivers for the tablet, but it would probably be a good thing to mention in this thread so if you have them, let me know and I can add it to one of the top posts. If you're having trouble finding them, I'll remove my drivers and go back through the process to find them again.
Looking for the tablet drivers. I am about ready to tap out on this thing for a while. lol Its driving me crazy.
Hippie459MN said:
Looking for the tablet drivers. I am about ready to tap out on this thing for a while. lol Its driving me crazy.
Click to expand...
Click to collapse
OK. The drivers I used were probably: VID_1f3a_PID_efe8 (or something similar)
You can either google that or try downloading the firmware for TP718AQ here: http://www.agptek.com/forum/viewtopic.php?f=22&t=948
Remove all prior drivers for the tablet. Plug it in and tell Windows to use the drivers from the extracted file you download (Will extract to TP718AQ_Update_Firmware\USB Driver).
Sometimes I have to do a little dance with restarting the device and my computer to get it to recognize it.
As a last resort you could try this: http://www.xda-developers.com/andro...r-solves-your-adb-driver-problems-on-windows/
Let me know if you have any problems.
Good Luck!
Ok, I officially give up trying to root this thing. Stupid windows will not install the drivers in both the links you provided and I cant get windows to even try to install anything after removing them then I got the android ADB drivers to install but still zero luck. All rooting apps fail. Hopefully someone will post the image of their rooted NB07. A few claim to have rooted it just fine but I cant win with this thing.
All I want is to be able to run link2sd and a few other apps that require root. This is officially the longest I have owned an un-rooted android device. lol
I'm the one that got the root working using kingo, so for the drivers the easiest method is just using Top Notch Tablets How to install ADB drivers ( I would post a link but I don't have 10 posts yet on XDA)
That worked on the first one, the second one it didn't not entirely sure why, but you can send a email to support and ask them for development drivers for the nobis tablets and they will send the ADB drivers you need. After you have the drivers installed use kingo while the tablet is in usb debug mode BEFORE plugging it into your usb port and do not turn on usb transfer. the first time after it reboots kingo will report that it was not rooted, leave it plugged in and power off and back on and it should report the root worked. This method gives you SuperSU. Both times I've done this were for clients of mine but its pretty straight forward.
Well, I have decided that for now this tablet of mine is un-rootable. I must have tried with 5 or 6 different drivers about 20 times with each with Kingo. I even tried that other program that is all in Chinese that loads some BS app on to your phone with no luck. So, for now, I am going to give up but if anyone has any other ideas or wants me to try something or they have for sure figured out how to root it, let me know as I am happy to help the best I can.
Edit: Oh yeah, Dont know how much this will help anyone but here is some more specific specs on the Nobis NB07 tablet I pulled off it with Hardware Info 3.0.0. Feel free to put the link in the first or second post if you want. Maybe it will help a little bit more.
http://www.hippie459mn.com/nobis_nb07/index.html
:good:
Hippie459MN said:
Well, I have decided that for now this tablet of mine is un-rootable. I must have tried with 5 or 6 different drivers about 20 times with each with Kingo. I even tried that other program that is all in Chinese that loads some BS app on to your phone with no luck. So, for now, I am going to give up but if anyone has any other ideas or wants me to try something or they have for sure figured out how to root it, let me know as I am happy to help the best I can.
Edit: Oh yeah, Dont know how much this will help anyone but here is some more specific specs on the Nobis NB07 tablet I pulled off it with Hardware Info 3.0.0. Feel free to put the link in the first or second post if you want. Maybe it will help a little bit more.
http://www.hippie459mn.com/nobis_nb07/index.html
:good:
Click to expand...
Click to collapse
Thanks to the work of someone on another forum, I have now got TWRP working on our device and am hoping we will soon have a CM working on it as well. Check back in the near future for further details. Maybe if you can't have a rooted stock, we can get a fully functional CM.
I am assuming you need to have root to flash the TWRP recovery correct. This is good news. Would love to have more info on it. Are you working with people on this site or another site? I would love to follow along.
Hippie459MN said:
I am assuming you need to have root to flash the TWRP recovery correct. This is good news. Would love to have more info on it. Are you working with people on this site or another site? I would love to follow along.
Click to expand...
Click to collapse
On another site for now. Just PM's at the moment so not much to follow yet. But, all you'll need is the Phoenixsuit to install it, so you won't have to root your tab first. You'll have root on the new ROM. You'll have to have drivers fully working though. Once fully working I'll link to the site so people can get the files and hopefully we can get this guy some donations for his work.
Awesome! I would go right to CM on this and skip the whole rooting the stock firmware. Would be nice to be able to root the stock firmware though then things would be so much easier. Think the camera will be working on the CM build? If not no big deal but would be nice to have them working.
Keep me (us) posted on the progress.
Hippie459MN said:
Awesome! I would go right to CM on this and skip the whole rooting the stock firmware. Would be nice to be able to root the stock firmware though then things would be so much easier. Think the camera will be working on the CM build? If not no big deal but would be nice to have them working.
Keep me (us) posted on the progress.
Click to expand...
Click to collapse
Not sure about the camera yet. I have CM booting but no touch yet, so this will be the first task. I'll keep everyone posted.
Any word on getting things to work yet?
Currently, we have CM working with no touch screen/camera. I'm not sure what else all isn't working because I'm waiting on my OTG cable to come in for further testing to see what all is going to be required to get the touchscreen going. Right now, it appears we my be looking at compiling our own drivers which could take some time to do. I think we'll get it eventually, but it may take some time. If you don't need touchscreen or camera, it could be working right now.
Sorry for no updates for a while. My work has been delayed on this since I have a son who is sick and in the pediatric ICU. I'll get back to work when things calm down for me.
No worries man. Family first.
Just a question, Hippie...
On the original ROM, can you see your device in ADB? If you can, and type "adb shell" do you get root? If you have adb access but not root, can you try typing sh and see what happens?
Also, could you try loading the rootfromOTA.zip and see if you can get a printout of the error log if possible?
Also, I tried installing this from the recovery on a similar ROM and it acted like it failed. I went back into the ROM and used adb and was able to get root using vroot or kingo...I don't remember which. This may be worth a shot.
Interestingly, I have been looking for alternative ways to root and found this (but we need to find a way to get to the bootloader):http://whiteboard.ping.se/Android/Rooting
I think that the method to get to bootloader is to turn off the tablet, then hold down the back button while tapping the power button 5 times. But, I also googled and found a method for getting to fastboot from adb in android without root as well which may work.
Hi and thanks so much for taking the time to read this. I'm really new, and I mean really new to flash rom's in the Android OS. So I have spent a few days doing some reading before I registered here. I was hoping for a simple step by step idiot proof way of improving my TF101 without any prior modding knowledge I found a step by step tutorial but was wondering if anything had changed or if there was a video tutorial on how to achieve the desired result of having my TF101 preform at a decent speed. I found this to be helpful http://forum.xda-developers.com/eee-pad-transformer/help/tf101-upgrade-buy-tablet-t2847617. So as to not stuff things up I have decided to reach out to the community and timduru for help and supply my TF101's details in hope that I can receive some kind of assistance.
The TF101 is mainly used for Skype, FB, Yahoo mail, E bay, Diary, GPS, TV Show's and Movies. Movies being somewhat of a problem with the slower speed which I was hoping that the 4.4.4 would possibly address or fix. So would you please be able to share any insight into a step by step of a virgin system? I believe the following details would be required?
SN:B70KAS107648
ANDROID version 4.0.3
GPS version V6.9.12
Wi-Fi version V6.1.1.24
Bluetooth version V8.30
Touch panel version MXT-1.1 build-1
Kernel version 2.6.39.4 [email protected]#1
Build number IML74K.WW_epad-9.2.1.27-20120615
MobileDock version EP101-0213
Please assist as I would like my daughter to inherit this machine as it's a little ripper of a machine which she would have fun using for many years to come. Again I ask if anyone has a video that my assist? But if not I'm also good with reading instructions. Pictures would be nice lol. I'm just hoping to make this machine the best I can
Welcome to XDA, my instructions here still remain true, only difference is the version of the ROM, the latest and greatest is currently #35
Everything else is the same and you should be up and running in not too long following those steps
Any problems, just reply here and I`ll check now and then and try give you a hand
Good luck
Thanks for such a quick responce
Will the TF101 preform better with watching video?
Than 4.0.3 stock, yea almost definitely - I watch 720p videos on mine with KK #35 fine
I'm an idiot
I don't even know where to start I tried following the instructions and nothing happens. From what I can see it has something to do with the tf101 not being rooted??
I need a real idiot proof step by step in detail, Sorry in advance
Stupid windows 8.1
navyant said:
I don't even know where to start I tried following the instructions and nothing happens. From what I can see it has something to do with the tf101 not being rooted??
I need a real idiot proof step by step in detail, Sorry in advance
Click to expand...
Click to collapse
That link is as idiot proof as you can get - no you don't need to be rooted - you just need to use Easyflasher to flash TWRP as per first part of the instructions - once you have TWRP recovery installed you can flash the new ROM
The Easyflasher thread explains how to use Easyflasher - the rest is in my step by step
Here
http://forum.xda-developers.com/showpost.php?p=54841038&postcount=6
If nothing happened with Easyflasher - chances are you didn't install the Universal Naked Drivers as stated at the bottom of my guide (Win 7 32bit recommended)
Once you have them installed - and you connect the TF101, and follow instructions to use Easyflasher - there is no reason it wouldn't work unless your cable or TF is faulty
the drivers
I used the naked drivers as instructed and have my windows 8.1 x64 machine showing the Asus Transformer APX Interface. But the flash doesn't do anything to the TF101? I tried sb1 and sb2 but still nothing? What state is the Asus meant to be in? I just have it connected to the computer via usb and on the home page window. its just frustrating as I can follow the directions but nothing beyond starting the flash program. Unless the first part of the flash program is meant to hang there for a while and I'm just impatient?? I'm just use to flash stuff take a few seconds. could this be my problem or is there something I'm missing ?
Windows 7 32bit as I stated a few times - 64bit and Win 8 require signed drivers, which these are not
You could try disabling driver signing mode using advanced (safemode) boot options with 8 64bit
And again, as stated in the instructions - you need to read instructions or you'll never get this working - the TF needs to be in APX mode - hence the APX drivers
Read everything 3 times, the only reason it's not working is because you're not following all the steps
Heck yeh
Ok I found out my problem, I was missing the power and vol up step as I didn't see anything on the screen and thought something was wrong as my b70 used sbk1 not the expected sbk2 so everything is great and thank to everyone for the help especially *Detection* I feel like such a knob. It was so easy
haha, pleased you got it sorted - sometimes it's good when you don't get it right the first time because it imprints it on your memory for next time, if it all goes smoothly you tend to forget what you did a few months down the line
Now the next really tiny issue
The sound seems to be a little quieter is there any way of boosting the sound?
navyant said:
The sound seems to be a little quieter is there any way of boosting the sound?
Click to expand...
Click to collapse
Yea, the same Dev (Tim) released an app exactly for that, KatApp
http://forum.xda-developers.com/showthread.php?t=1841851
Hello, I bought my shield a while back, rooted in KitKat just to get my backup data from apps from my previous device transferred and then happily ungraded to Lollipop with the intention to stay unrooted since it means unlocking the bootloader which may void my warranty. Recently I came upon an app named Helium which I knew nothing about and which seems to be able to backup app data even without root, but to use the no-root version you need to have ADB drivers installed. I found a bunch of sets of ADB drivers, like for example this http://developer.download.nvidia.com/mobile/shield/SHIELDTablet_WHQL_USB_driver.zip but nowhere real instructions explaining how to install them in a Windows 7 PC. I've searched all over the place with no luck so help would be greatly appreciated. I installed drivers for my older device about 3 years ago so I've done it before but I can't remember a thing about it, even if it was a similar method that I had followed.
Thanks in advance, hope someone replies. Help a fellow keep his data backed up please!
Hey there, man.
First of all, neither rooting or unlocking bootloader will void your wartranty, unless the installation you made after that, break the whole tablet in pieces. For example, if you happened to install Windows 8 and it burns.
As for ADB, just read this thread: http://forum.xda-developers.com/showthread.php?t=2317790
Good luck.
YuriPan said:
Hello, I bought my shield a while back, rooted in KitKat just to get my backup data from apps from my previous device transferred and then happily ungraded to Lollipop with the intention to stay unrooted since it means unlocking the bootloader which may void my warranty. Recently I came upon an app named Helium which I knew nothing about and which seems to be able to backup app data even without root, but to use the no-root version you need to have ADB drivers installed. I found a bunch of sets of ADB drivers, like for example this http://developer.download.nvidia.com/mobile/shield/SHIELDTablet_WHQL_USB_driver.zip but nowhere real instructions explaining how to install them in a Windows 7 PC. I've searched all over the place with no luck so help would be greatly appreciated. I installed drivers for my older device about 3 years ago so I've done it before but I can't remember a thing about it, even if it was a similar method that I had followed.
Thanks in advance, hope someone replies. Help a fellow keep his data backed up please!
Click to expand...
Click to collapse
When I'm faced with a .zip file, the first thing I do is to unzip it and look at the contents. If there's an installer in there, I just double-click on it ... Sorry if this sounds very basic, but it might not occur to everyone =)
If there's not an installer, you'll probably have to install those drivers through Device Manager. Good luck =)
CM17X said:
Hey there, man.
First of all, neither rooting or unlocking bootloader will void your wartranty, unless the installation you made after that, break the whole tablet in pieces. For example, if you happened to install Windows 8 and it burns.
As for ADB, just read this thread: http://forum.xda-developers.com/showthread.php?t=2317790
Good luck.
Click to expand...
Click to collapse
Oh I see. Then I might actually root it but since I have to unlock the bootloader and it will wipe my device I definitely need to make this no-root backup work first >.<
I opened the link. The instructions are just to install the exe? I did but my pc still thinks I have no drivers installed... *sigh* Any ideas?
Ok, I figured it out, I installed via Device Manager after all, I was using a bad set of drivers, apparently some file was missing from them so the DM didn't recognize it as drivers... ugh, such confusion for such a silly little thing! Thank you for your help!
amartolos said:
When I'm faced with a .zip file, the first thing I do is to unzip it and look at the contents. If there's an installer in there, I just double-click on it ... Sorry if this sounds very basic, but it might not occur to everyone =)
If there's not an installer, you'll probably have to install those drivers through Device Manager. Good luck =)
Click to expand...
Click to collapse
I tried unziping it. Dunno what I'm supposed to do next. There's no exe's in there, there are 2 files that are considered "Security Catalog", 2 are "Setup Information" and there's 2 folders and each contains 3 files that are "Application exension"
I'd like to try installing them through Device Manager but... how do I do that?
Ok, ignore whatever I wrote before, I figured it out. Looks like I was using a bad package of adb drivers. The funny thing is, the link I posted above is the one that worked but the one I was trying to install was a different one! I suppose I got confused after finding more than one set of instructions! >.<
Hi everybody ! Ill try to keep it simple as I'm sure its covered somewhere but here goes ....
Ive been using my shield portable, rooted, for ages now no problems.
Like many Ive updated it in short ever since nothing whatsoever has worked properly , most annoyingly the screen doing backflips when you go near it and hundreds endless strange updates when rebooting.
Anyway I don't think you or I or any of us want to waste time trying to figure out why its done any of this but I just want to be able to fix it. I guess I'm going to have to start again somehow! its worth noting here that all my backup apps like Helium now don't seem to work.
After the update I of course ReRooted and it appears fine from boot loader , still says unlocked. but upon usage its clearly very confused about whether its rooted or not !
In short its useless. Advice please My kung Fu warriors
May your arrows fly straight and true
I have no idea about the various issues, but I would perform a factory reset, and clear cache and dalvik cache using at least 3 swipes per each function. The method of rooting I recommend is by flashing a zip of SuperSU from a custom recovery menu. CWM or TWRP are both available for the NSP. After flashing SuperSU, when you reboot and go into SuperSu you'll see that it's installed (locked down tighter) as a system app.
Downloads:
SuperSU (latest stable version) v2.65
CWM Recovery Menu (latest version) v6.0.4.4
TWRP (Modified recovery (based on TWRP v2.8.7.0)
Sorry. This is the best I can offer you right now. If this doesn't work I would reflash the stock images of whatever OTA you wanna be on. The images can be found @:
SHIELD Open Source Resources and Drivers. You'll need at least the platform-tools portion of the Android SDK (to use Fastboot to flash from recovery). A user friendly PC app that can basically do all this sort of stuff is Shield Ram v1.1. You might find that easier to use.
Oh and here's the latest Minimal ADB and Fastboot Drivers installer [v1.3.1]
If you need further help, let me know.
Hi ! Thanks for the good advice.
I should have mentioned, I'm using a Mac now.
From what I understand it's still possible , maybe
Even easier.....
Sorry to throw a spanner in your super helpful works !
Thanks again
[/COLOR]
Marrhead said:
Hi ! Thanks for the good advice.
I should have mentioned, I'm using a Mac now.
From what I understand it's still possible , maybe
Even easier.....
Sorry to throw a spanner in your super helpful works !
Thanks again
Click to expand...
Click to collapse
Yeah, pretty much the rule is generally "as long as you can still see the screen, it's probably fixable". Sounds to me like your best bet, would be to download the OTA you wanna be on, and flash a new install to your Shield. It's the quickest way from A-B. I'm about 99% sure that this would solve the problem (as long as you re-root it properly). Though if you have your reasons, you can try some of the other things first. You're welcome and let me know how things go!
So where does one get the latest OTA?
cheers
Marrhead said:
So where does one get the latest OTA?
cheers
Click to expand...
Click to collapse
I did link up the main Nvidia page that would lead to the OTA images, but here's a direct link to DL just the OTAs:
Edit: you can get there through the link I included in my previous post: SHIELD Open Source Resources and Drivers. I'm having issues with editing posts, and all sorts of odd **** with the link trying to post a more direct link. It's an Nvidia site, just scroll down to Shield Portable Recovery OS Images (something like that).
Unfortunately there are only Linux and Windows downloads available. I'm not sure what your best option would be, as you have a Mac. You could contact Nvidia support, and see what they say about it. Sorry, but I don't think I can probably help much more than this.When I contacted Nvidia support about a year ago, they were pretty helpful. Hopefully you get this sorted soon. Oh and the OTAs are flashed via a terminal/command prompt. So if you can emulate DOS on your Mac (which I don't see why not...DOSbox? maybe) then that sounds to me like the solution.
Ok , hit another brick wall. Im using a windows computer now, followed all the instructions i can find, and now the bootloader seems dysfunctional.
Ive got adb and fastboot and its recognising the device but once rebooted into bootloader which loads fine, the commands say no device found and nothing works in this mode.
If i hit recovery mode then a little dead android appears! poor little guy.
I tried shield ram but it had same problems, seems to run fine but cant find shield once its in bootloader...
Ive got the image zip of the update i want to flash but no idea if im doing it right- not sure how to use it.
Help!