Hello.
Could anybody point me towards, or drag me along, a path to revive a Nexus 7, please?
If I have wandered into the big boys forum please feel free to tell me to clear off or, better, suggest an alternative forum more suited to my ability. After two weeks of "research" I am stuck at what I suspect is a simple matter around connectivity. Is this a suitable place to ask for any help & guidance? ; I am well aware that it would be needed in a simplistic form.
As a learning project, I managed to root a Nexus 7 2013 which was displaying problems, and enabled USB debugging.. However, whilst exploring the TWRP options on the Nexus, I wiped everything, including the OS and I had not made a backup.
On a Windows XP tower, I installed Nexus Root Toolkit & an Android OS version plus a multitude of files, such as TWRP & GAPP.
When connected by USB cable, the XP machine finds new hardware, but the installation wizard fails and the Nexus does not show up in Device Manager or elsewhere.
Running NRT shows ADB /Fastboot connectivity as failed. (fastboot gelvar lock)
(I have had no success in trying to follow the NRT proffered solutions including driver updates, although the google drivers show as downloaded.)
On the Nexus I can access the basic TWRP screen and the Android Start screen, from which only the Google lock screen can be displayed.
Thanks for reading so far.
Nexus7 (2013 WiFi) OS 5.1.1
Fastboot mode, Product name Grouper, HU Version ER3, Bootloader version 4.23 Baseband version N/A Signing Not defined Yet, Lockstate UNLOCKED
TW1234 said:
Hello.
Could anybody point me towards, or drag me along, a path to revive a Nexus 7, please?
If I have wandered into the big boys forum please feel free to tell me to clear off or, better, suggest an alternative forum more suited to my ability. After two weeks of "research" I am stuck at what I suspect is a simple matter around connectivity. Is this a suitable place to ask for any help & guidance? ; I am well aware that it would be needed in a simplistic form.
As a learning project, I managed to root a Nexus 7 2013 which was displaying problems, and enabled USB debugging.. However, whilst exploring the TWRP options on the Nexus, I wiped everything, including the OS and I had not made a backup.
On a Windows XP tower, I installed Nexus Root Toolkit & an Android OS version plus a multitude of files, such as TWRP & GAPP.
When connected by USB cable, the XP machine finds new hardware, but the installation wizard fails and the Nexus does not show up in Device Manager or elsewhere.
Running NRT shows ADB /Fastboot connectivity as failed. (fastboot gelvar lock)
(I have had no success in trying to follow the NRT proffered solutions including driver updates, although the google drivers show as downloaded.)
On the Nexus I can access the basic TWRP screen and the Android Start screen, from which only the Google lock screen can be displayed.
Thanks for reading so far.
Nexus7 (2013 WiFi) OS 5.1.1
Fastboot mode, Product name Grouper, HU Version ER3, Bootloader version 4.23 Baseband version N/A Signing Not defined Yet, Lockstate UNLOCKED
Click to expand...
Click to collapse
Did you search/read HERE. That is the forum for the N7. I also have the same model and I also know that posting in that forum will fetch a reply, if at all, at a much later date. That is why I have not moved your thread there.
I also used the NRT in the initial days of my learning process and faced the driver issue also. One solution that worked was to install USBDview and remove all the unnecessary drivers before using NRT for installing drivers and for flashing.
Did you go through the NRT thread for the driver issue?
Thanks. ( I have read through some of the Nexus section threads, but cannot find a suitable solution.)
Using USBDview within NRT enabled me to clear several Nexua & Android items and get folders for Portable Devices and MTR to show in XP Device Manager; however the MTR displays a fault (exclamation) marking, (although it reports as working OK and no better update is found with the wizard.).
Using NRT firstly reports that "updates cannot access serve" and using "Unlock Bootloader" indicates "Fastboot device Connected, before changing the Nexus screen from Start arrow to Google lock screen, At the same time XP reports new hardware found (MTR device) and the wizard reports it as installed
So there must be some form of connection.
However if Full Driver Test is then run, NRT just reports ADR device not found.
TheNRT subsequent suggestions hinge on having USB Debugging toggle access.
Sorry, but I have no idea for a suitable logical rectification route.
Google Asus Nexus 7 (2013) is based on Qualcomm-Snapdragon chipset hence you need to download and install Qualcomm-Snapdragon-suitable USB-drivers ( incl. ADB / Fastboot ) what is a must need to connect a Snapdragon Chipset based device with a computer: the USB-drivers (ADB / Fastboot) what are offered on hundreds of websites - as also here on XDA - are developed by Google for Google Pixel phones, although they may work on other devices, too.
Thanks. I have now got a Qualcomm (unzipped)) folder Driver with sub folders & tried to set this for the MTP device in the XP Device manager. No success, probably due to my lack of knowledge.
How do I proceed, please?
By asking such basic questions, should I abandon the Nexus until I have learned to walk?
TW1234 said:
Thanks. I have now got a Qualcomm (unzipped)) folder Driver with sub folders & tried to set this for the MTP device in the XP Device manager. No success, probably due to my lack of knowledge.
How do I proceed, please?
By asking such basic questions, should I abandon the Nexus until I have learned to walk?
Click to expand...
Click to collapse
In the NRT, there is a section on driver installation and also drivers. After removing redundant drivers with USBDview, try the drivers and methods given in NRT itself. Unless proper drivers are installed, you can't do anything whether with NRT or adb.
Also, try a different PC or laptop.
I tried on a Windows10 laptop but the trial followed exactly the same route as already followed & ended in exactly the same place.
Drivers were installed from within NRT. The NRT signposted ones are Google (No mention of Qualcomm)
Still getting "No ADB connectivity for MTR device"
TW1234 said:
Thanks. I have now got a Qualcomm (unzipped)) folder Driver with sub folders & tried to set this for the MTP device in the XP Device manager. No success, probably due to my lack of knowledge.
How do I proceed, please?
By asking such basic questions, should I abandon the Nexus until I have learned to walk?
Click to expand...
Click to collapse
Why not simply use
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks. I had already tried that Install wizard, but have repeated it. It runs and reports "Drivers installed" (although I cannot find where). The Nexus still shows in XP Device Manager as a portable device and with MTP showing fault requesting reinstall drivers.
Related
I have followed the guide, did the edit to the android_winusb.ini and the 0x54c in the adb_usb.ini but I still can't get it to show up as a device when I type adb devices (did restart ADB via adb kill-server after editing the files)
It took me awhile to change the driver for Win 7 recognise it as "Android Composite ADB Interface". I had to use
Code:
%CompositeAdbInterface% = USB_Install, USB\VID_054C&PID_05B4
otherwise it kept saying it couldn't find a compatible driver
Model is SGPT112GB/S
Any ideas?
try this "Auto-Installer". In most cases it has helped.
http://forum.xda-developers.com/showthread.php?t=1488822
Tried it already, didn't appear to work, plus as I ran ADB with it, it said it was out of date
Go into System Devices whilst the Tab is connected via USB, delete and uninstall the device there and the re-install. Thats what i'd to do because the first time I installed it I missed the ox54c bit and it only half installed.
Tried that, adb still doesn't list any devices :/ ADB definitely works as it picks up my phone (X10 mini pro) when I plug that in
Some pictures can help, adb manager, device manager and probably de ini file.
Is your Tablet showing up in Device Manager and if so what as ?
defsix said:
Is your Tablet showing up in Device Manager and if so what as ?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Before it was showing up under Portable Devices. So I followed the instructions to Update the driver and point to the inf file, but it kept saying couldn't find a compatible driver, so I went into the properties for it and checked the Hardware ID, and it wasn't the same as it said in the guide so I changed it in the inf file, once that was done, I was able to update the driver.
confuserr said:
Before it was showing up under Portable Devices. So I followed the instructions to Update the driver and point to the inf file, but it kept saying couldn't find a compatible driver, so I went into the properties for it and checked the Hardware ID, and it wasn't the same as it said in the guide so I changed it in the inf file, once that was done, I was able to update the driver.
Click to expand...
Click to collapse
As stated in my automated installer, you need TWO devices to show up:
If you're not getting the portable device, you need the MTP driver.
Uninstall both devices and reinstall the drivers or manually force an update on them.
Which OS are you running?
Win 7 64bit, either it shows up under portable devices or under Android phone. Not both. Ive tried your installer but it still doesn't work :/ This probably sounds stupid but if i uninstall, to install again just replug the tablet back in right and do the driver update thing? If not, then maybe thats where im going wrong :S
Update: Ok uninstalled, tried your installer. Now only shows under portable
http://dl.dropbox.com/u/16892708/CloudShot/shot_12022012_001734.png
CMD prompt that opened afterwards: http://dl.dropbox.com/u/16892708/CloudShot/shot_12022012_001000.png
confuserr said:
Win 7 64bit, either it shows up under portable devices or under Android phone. Not both. Ive tried your installer but it still doesn't work :/ This probably sounds stupid but if i uninstall, to install again just replug the tablet back in right and do the driver update thing? If not, then maybe thats where im going wrong :S
Update: Ok uninstalled, tried your installer. Now only shows under portable
http://dl.dropbox.com/u/16892708/CloudShot/shot_12022012_001734.png
CMD prompt that opened afterwards: http://dl.dropbox.com/u/16892708/CloudShot/shot_12022012_001000.png
Click to expand...
Click to collapse
When you uninstall, did you check the box that says "Delete the driver software..."
Is USB debugging checked on your tablet? You have to have two items in Device Manager. One is to transfer files (MPT/Sony Tablet S under Portable Devices) and the other under an Android heading (ADB).
If you're plugging in the tablet with USB Debugging checked and nothing's showing up, something's wrong with your system. At the very least, you should get an unknown device. Go to "View" and check "Show hidden devices" and check to see if anything's there. Try another USB port.
Bottom line: you need both items.
I followed your video exactly, USB debugging is enabled.
As soon as I plug the tablet in, it looks for new software. It then says successfully installed and pops up with the auto play options. Under devices it shows up under "Portable Devices". If I do the Update Driver, choose the .inf file, it installs but then it no longer shows up under Portable Devices but instead I have the "Android Phone" category with the Composite ADB Interface.
When uninstalling, it only comes up with the checkbox asking delete driver software when I uninstall the ADB Interface one, not the tablet under "Portable Devices"
I have done "Show hidden devices" all that changes is it shows a category called "Non-Plug and Play Drivers"
Confuserr, Im in the exact same position - and on win 7 x64.
Ive done both SDK install and Automated, nothing works.
I never could update the usb drivers though as windows decides the one I have is perfectly good - will try your little trick.
As soon as i get it to work ill post here, just wanted you to know that your not alone in this..
//Cliff
---------- Post added at 04:29 PM ---------- Previous post was at 04:15 PM ----------
And a second later it works atleast in the device manager.
I did the USB driver install according to the guide in the root thread http://forum.xda-developers.com/showthread.php?t=1487020, now unistalled the drivers (2 times) and installed again pointing to the correct location (android/extras/usb_drivers/)
Ran the latest version of the exploit from above thread and done, successfully rooted - now i just need to figure out what to do with my new rights (except taking away social feed reader and speed it up a bit)
//cliff
I can only assume the problem lies in the fact that the ADB guide Sony posted http://www.kb.sony.com/selfservice/documentLink.do?externalId=C1024692
Says
Region
Canada
Latin America
United States
Products
SGPT11 Series
Click to expand...
Click to collapse
Where as my Region is United Kingdom and SGPT112GB/S but im just taking stabs in the dark now
I have reinstalled the entire SDK Manager and still having problems :/
Edit: I've sent an email to Sony, lets see what they reply with
for me it worked after the removal of the old drivers and then using the ones downloaded from google, untuched. My guess is that this will work for you aswell. Good luck /Cliff
confuserr said:
I can only assume the problem lies in the fact that the ADB guide Sony posted
Where as my Region is United Kingdom and SGPT112GB/S but im just taking stabs in the dark now
I have reinstalled the entire SDK Manager and still having problems
Click to expand...
Click to collapse
I don't think it is your region. I cannot get adb to recognize my tab either and I am in the US (not region related). The strange thing is, I was able to ROOT... I also noticed, that while the ROOT tool was running, adb recognized my device. So, when the ROOT tool paused and was awaiting for me to press any key, I decided to mess around with a few codes to see what happened. I input:
Code:
su
mount -o remount rw /system
cp /system/build.prop /sdcard
busybox /sbin/sh
reboot
Everything worked as it should have. While the tab was rebooting, I shout down the ROOT tool, and after the tab rebooted, everything seems to be working as it should.
I have NO CLUE what the hell was going on. But, it works now and that is all that matters to me... Now on to perfect the custom recovery...
UPDATE
I figured it out! It's something with windows. For some reason, it is not starting the adb server... Here is the solution:
In command prompt type (cd to the directory where your adb.exe is):
Code:
adb kill-server
then press enter
Then type:
Code:
adb start-server
then press enter
Then you can go ahead and type:
Code:
adb shell
then press enter
And now you are on your way!
Hi all I'm having problems with getting ADB to see my device and was hoping someone with more brains can help me to solve this problem. I've searched this as much as I can on XDA and Google in general but nothing I find works device specifically.
First setup: I'm running the brilliant ARHD 11.0 JB with build.prop tweaks on top of Siya 1.6.8 and I don't think that Mike and GM need any introduction since they are both household names in our forums.
My machine OS: 7 Ultimate 64
The drivers I've installed: (this might be a factor in the problem)
Latest Kies. I've also installed the s3 drivers when connecting the device in download mode. I have uninstalled Kies because it's unless after the device drivers have been installed IMHO.
The ADB I am trying to use: I downloaded the generic ADB since I think the bridge is generic and mentioning the platform is irrelevant. But it was not the one bundled into the SDK since its not necessary. I have run it as Admin
My problem: I have connected my phone with debug enabled and disabled Auto play but as soon as I "adb shell" in cmd (after cd the adb directory) I still get the "error: device not found" message.
I've tried what I can but can figure it out could someone with the brain. I wish I had please slap me around the room and point out my obvious error and set me on the right path or at least cry with me in my frustration.
If I could get a devs input it would be awesome but if anyone could help me out, I would greatly appreciate it.
Please tell me if I've ommited any important info.
Thanx guys!
CM
christophermaisch said:
Hi all I'm having problems with getting ADB to see my device and was hoping someone with more brains can help me to solve this problem. I've searched this as much as I can on XDA and Google in general but nothing I find works device specifically.
First setup: I'm running the brilliant ARHD 11.0 JB with build.prop tweaks on top of Siya 1.6.8 and I don't think that Mike and GM need any introduction since they are both household names in our forums.
My machine OS: 7 Ultimate 64
The drivers I've installed: (this might be a factor in the problem)
Latest Kies. I've also installed the s3 drivers when connecting the device in download mode. I have uninstalled Kies because it's unless after the device drivers have been installed IMHO.
The ADB I am trying to use: I downloaded the generic ADB since I think the bridge is generic and mentioning the platform is irrelevant. But it was not the one bundled into the SDK since its not necessary. I have run it as Admin
My problem: I have connected my phone with debug enabled and disabled Auto play but as soon as I "adb shell" in cmd (after cd the adb directory) I still get the "error: device not found" message.
I've tried what I can but can figure it out could someone with the brain. I wish I had please slap me around the room and point out my obvious error and set me on the right path or at least cry with me in my frustration.
If I could get a devs input it would be awesome but if anyone could help me out, I would greatly appreciate it.
Please tell me if I've ommited any important info.
Thanx guys!
CM
Click to expand...
Click to collapse
Your problem determinated drivers , install drivers for samsung devices, reboot your pc, connect your device to your pc , expect driver installation , then check if updated , then if the sdk is installed correctly , adb devices.... USB Debugging enabled ......
i had an isssue last night with adb...
unplug phone from pc and turn off and then on usb debuging on the phone...
enter cmd mode on pc, then
adb kill-server
adb start-server
adb devices
then hopefully it will show the device is connected....
p.s. drivers should be installed and checked, this step it is mandatory....
hope it helps ...
Thank you both for you input but nothing works unfortunately. I'll continue the search thanx again though
May this help connect your usb to direct motherboard port. Do not use usb hub if you are
Sent from my GT-I9300 using xda premium
christophermaisch said:
Thank you both for you input but nothing works unfortunately. I'll continue the search thanx again though
Click to expand...
Click to collapse
Debug/test apps on device over the air, no cable. Must-have developer tool. WiFi ADB
You just installed the "adb" driver for your device. You still need to install the "fastboot" driver. It is the same driver, it just needs to be installed twice - once when your device is booted normally, and once when it is booted in fastboot mode. I personally would use the Universal Naked Drivers by 1wayjonny
When you have USB Debugging mode turned on on your phone and you connect to the computer and you look at Device Manager (Win+R, devmgmt.msc) do you see this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you get Unknown Devices automatically expanded, then you haven't got the correct drivers installed.
You don't need to install Kies to have the latest drivers installed; you can extract them from the setup itself:
Download KIES and run the setup but don't do anything with it
Open up your Temporary Files folder: Win+R, %TEMP%
Look for the folders that start with a '{' and end with a '}' and have a bunch of letters, numbers and 4 hyphens in them and within this selection of folders find the folder that has its Date Modified timestamp matching the time you opened the KIES installer exe (in my case it was {44A91F3A-3D8C-43DE-A0BC-04E01C756397}). If you're in the right place, you'll find "Samsung Kies.msi".
Grab Less MSIérables, point it to Samsung Kies.msi and extract SAMSUNG_USB_Driver_for_Mobile_Phones.exe somewhere. lessmsi is a little slow...
You'll see a new folder "SourceDir" wherever you chose to extract the file, navigate through it until you find the EXE. Close the KIES installer and run the driver setup
Oh, rather than using some random version of ADB off the Internet, get it from Google themselves. The latest versions can be found in the platform-tools ZIPs for the SDK, but you don't need to install the SDK just for ADB: Open http://dl.google.com/android/repository/platform-tools_r14-windows.zip (14 is the latest version as of this post) and extract the three adb files from the ZIP and place them somewhere. This way you know it's not a problem of using an old ADB version.
You can also check to see if adbd is actually running on the phone when you plug it in by grabbing Terminal Emulator off the market and running: "/system/bin/ps | grep adbd" (note: you only get grep if you have BusyBox instaled)
Finally, if you really can't get USB connections to work, then use https://play.google.com/store/apps/details?id=com.ttxapps.wifiadb&hl=en :\
christophermaisch said:
Thank you both for you input but nothing works unfortunately. I'll continue the search thanx again though
Click to expand...
Click to collapse
Hey,
I had the exact same problem. This Tutorial : http://goo.gl/OS3Vi worked for me.
Hope it helps
I am having some problem remove an Nandroid backup; (it is impossible to remove it either with Root Exporer or in the terminal as root (rm -rf blah)).
However, now I am trying to use ADB to get rid of it I installed adb and some new drivers for my I9300.
Looked through my phone debug-settings, checked if ADB found my phone (adb start-server, adb devices). Then I rebooted my phone into recovery via CWM - however - now my phone does not want to be found.
Windows Device Manager recognize the phone, but the drivers-icon are yellow-ish (not sure if this is how they are supposed to look). adb devices gives me nothing.
I could really use some help over here.
Hi guys, I wanted to try this database system, so I'm expanding upon this thread: http://forum.xda-developers.com/showthread.php?t=2272066
Introduction
CASUAL will guide you through the process. Put your device into “Developer Mode>USB Debugging”. Click the do it button. If you experience a problem, PLEASE USE THE PASTEBIN button to post a log. Just press Ctrl+L then Pastebin and fill out the information.
Overview
You are expected to be STOCK.... Stock anything, but stock. If you are not stock and have a custom recovery, this will cause you to only be able to flash back to stock using Odin or Heimdall. Be stock. You will need to download and execute the CASUAL application below. Then click the Do It! button. You need Java. Do you have Java?. The exploit was developed by Elite Recognized Developer Ralekdev and packaged by AdamOutler.
note: if it fails, try turning everything off and back on, then run it again before posting for help.
Windows 32/64 Users: CASUAL will put your device into Download Mode. It will automatically flash everything. If drivers are required, jrloper's CADI (CASUAL Automated Driver installer) will handle it. Make sure you're connected to the internet.
Linux 32/64/raspberry pi Users There may be a permission escalation in order to install heimdall, either way sit back and relax. CASUAL automates the entire process.
Please run the following in a terminal first:
Code:
sudo apt-get install openjdk-7-jdk dpkg
Mac Users: Mac works easier than any other system at the time of this systems. Please report problems.
Download
CASUALnightly No You Verizon! Always use the highest revision with the latest date. To run CASUAL you need Java. Do you have Java?
For nightly builds click here: http://goo.im/devs/AdamOutler/VZWGalaxyNote2
Help and Troubleshooting
Are you having a problem? First check this post out for remedial troubleshooting. . If that doesn't fix it, then press CTRL+L, press the Pastebin button, come back here and press CTRL+V to paste your log. Don't hit the donate button, that doesn't fix it. Donate only if you feel it's worth donating to. Use CTRL+L and then hit Pastebin and paste the log here if you need help.
Jailbreak video for Windows users only!
This video desmonstrates CASUAL used with Odin to flash the Galaxy Note 2 firmware. Thanks to DroidModderX. While the video uses an old version the procedure is mostly the same.
Jailbreak video for LINUX only!
This video demonstrates the one-click CASUAL Linux Unlock method... at 2AM.. so don't expect me to be cheerful. While the video uses an old version, the procedure is mostly the same.
image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About CASUAL
CASUAL stands for Cross-platform ADB Scripting, Univeral Android Loader. CASUAL jar files are a wrapper for the CASUAL scripting language. CASUAL allows rapid and accurate deployment of hacks and exploits. At any time, if a serious problem is detected with any script, the kill-switch will be flipped and you will be brought to a support page (most likely here) so you can download the latest version. Otherwise for minor corrections, new CASUAL scripts can be deployed remotely.
Updates
CASUAL provides updates WAAAAY quicker than Verizon. As soon as I push an update to the Subversion repo it appears automatically in EVERY casual. See below for the change log.
31July13: initial release
XDA:DevDB Information
CASUAL- NO You Verizon, a Tool/Utility for the Verizon Samsung Galaxy Note II
Contributors
AdamOutler, jrloper, loglud
Version Information
Status: Testing
Current Beta Version: No You Veriz
Beta Release Date: 2013-07-31
Created 2013-07-31
Last Updated 2013-08-02
Very nice work
MY DIRTY LIL NOTE 2
couldnt get the latest nightly to fully load. recog device connection but the do it wouldnt work because the top of the app stayed on loading... please wait.
edit: diff build shows the top, but says disconnected on the bottom. fml
all the videos say to use windows 7. can it work with vista?
master0fursinz said:
all the videos say to use windows 7. can it work with vista?
Click to expand...
Click to collapse
yeah, it should work with Vista. @jrloper could tell you more if there are driver issues.
idkwhothatis123 said:
couldnt get the latest nightly to fully load. recog device connection but the do it wouldnt work because the top of the app stayed on loading... please wait.
edit: diff build shows the top, but says disconnected on the bottom. fml
Click to expand...
Click to collapse
I'm also having this problem. Any help Adam?
Edit: This is what you're looking for http://forum.xda-developers.com/showthread.php?t=2272066
Hi,
I'm currently running Windows 8.1 64 bit and my phone is the Samsung Galaxy Note II android version 4.1.2 stock, model SCH-i605, and baseband version i605vramc3. After downloaded the latest nightly build, the .jar file opened and gave the following error in the application:
There was a problem while excuting the command.
C:\Users\Zack\AppData\Local\Temp\CASUALZack-2013-12-26-17.09.35\adbexe devices
Then it repeated this same error every second or so infinitely until the application was closed. It did this whether the phone was connected, disconnected, in USB debugging mode, in download mode, etc. I have tried everything and I continually get this same error with the "Do It' button greyed out and disabled.
Next I downloaded the previous two builds, and I found that the December 13 build did not get this error and actually found my phone. However, after I clicked "Do It" and confirmed the warning, It rebooted my phone into download mode like it is supposed to. My phone then went into download mode like usual. However, the CASUAL program then said:
looking for download mode devices..........................................................
And kept on looking without ever finding my phone, and every minute or so it came up with a prompt asking why it can't find my device. I also found that my phone would not exit this download mode without doing a battery pull.
Next I retried the entire process with both builds using (a) 3 different USB cords, (b) 3 different computers running windows 8.0 and 7, and (c)every possible USB port on each computer. These options all gave the same exact results.
I have tried everything I can think of but it is not working! Has anyone encountered this problem before or do you have any proposed solutions?
Thanks so much!
Zack
Still can't figure it out.
http://pastebin.com/W3W1HwJi
I keep getting a libusb error -12 at the start and then it ends up failing.
Really need help here. Verizon was trying to force update me and I had to turn it off and go back to my old phone till I can get this done.
Thank you Adam!!
BrickeD?
Hi guys.
I am certain I followed all instructions to the letter, but I have ended up rendering my Note 2 pretty much useless. CAUSAL informed that the device would be started in android but then the next thing my phone displayed was:
"System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
Can I restore my device to the previous state?
thanks
Tried the second time around with CASUAL R570 and got error.
http://pastebin.com/Gpss6vtZ
UPDATE: Gave up hopes (for now) of rooting SCH-i605 running KitKat. Flashed stock rom and revived the device.
Spy26 said:
Tried the second time around with CASUAL R570 and got error.
http://pastebin.com/Gpss6vtZ
UPDATE: Gave up hopes (for now) of rooting SCH-i605 running KitKat. Flashed stock rom and revived the device.
Click to expand...
Click to collapse
There isn't a root method for ND7 4.4.2. for the i605. Also, the bootloader hasn't been able to be unlocked since MJ9 4.3.
mirror
Hosed my phone... infinite bootloop at sammy logo, couldn't get into recovery had to odin a stock image and start over... Had one hell of a time tracking down the casual jar file.
As of this moment the download link in this thread is bad.
the download link in THIS thread, now points to DevHost but the files are not the ~29MB jar file you expect. It is now a 3.5MB exe file that appears to be "shady as hell". All the other download decoy buttons at Dev-host take you to fake java update downloads and other seriously shady looking corners of the interweb.
Additionally goo.im is on holiday...
As such I have posted this temporary Mirror of the .jar file I had in my archives:
http://tweakedrom.com/Other_Files/Note_2.php
(The jar file MD5 appears to be the same as one the developer posted to Dev-Host.)
Outler, if you want me to take this mirror down just let me know.
Cannot find the download to casual sch-i605. All download links I can find lead to nowhere.
mjmplus said:
Cannot find the download to casual sch-i605. All download links I can find lead to nowhere.
Click to expand...
Click to collapse
Well you could go to his very own YouTube video and use the links there
Hey All
Its been a while since I got to play with anything these days but I recently found one of these POS 10in touchscreen units in the dumpster and it fires up into a menu running android. So I was hoping I could reflash this and use it like a tablet given it's also got a small thermal printer in it, so maybe try and save it from e-waste
I searched online for more details and came across this HERE which is identical to what I have so hoping I can root it and flash it with a clean android?
I would love to repurposed this to use as a touch screen tablet or similar, since it's got a GSM module and can take an SDCard too as I opened it up and took some pictures and I managed to get it in a recovery mode as well - from the PIX its using a rockchip RK3368
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am not sure if the mini usb port is a OTG port to try and use ADB but I have not been able to do much with it and hoping someone can guide me through to possibly a reflash or ways to unlook root and add in another bootloader/rom
I've downloaded the files from citaq website but so far not been successful to do much with it, has anyone played with these and turned them into something more practical for the home?
Here's hoping for some tips - Apology if this is in the wrong section, move as needed :good:
Cheers
Kosti
@Kostiz
Device actually is running Android 5.1.1. It seems it has only 1GB RAM what is far too little to run a full fledged Android.
As long as you don't replace device's Stock Recovery by TWRP or similar recoveries, after a successful rooting don't install Magisk and/or Xposed Framework, you're on the safe side to play with, IMHO.
As 1st step check whether device is accessable by means of both ADB and Fastboot.
jwoegerbauer said:
@Kostiz
Device actually is running Android 5.1.1. It seems it has only 1GB RAM what is far too little to run a full fledged Android.
As long as you don't replace device's Stock Recovery by TWRP or similar recoveries, after a successful rooting don't install Magisk and/or Xposed Framework, you're on the safe side to play with, IMHO.
As 1st step check whether device is accessable by means of both ADB and Fastboot.
Click to expand...
Click to collapse
Hey, Thanks for chiming in!
So in order to get ADB and or Fastboot its suggested to enable USB debugging in the device system settings, but I am not sure on how to do this, would it be safe to assume this is already USB debug is already enabled?
Could I back up the original stock recovery
I'm a little green on the whole process hence looking thought I'd ask here, I don't think I even have an OTG cable handy
I will see if I can load ADB on a windows box and try and talk to this unit
Cheers
Kosti
@Kostiz
An OTG-cable isn't needed, because the recovery menu
doesn't give you the opportunity to load something from an USB-device
OK, some success!
I went back and connected a mini USB straight to the PC and ADB driver installed detected the android device.
Ran ADB in windows powershell
So whats the best method to backup the entire ROM, and recovery files in the event I stuff this up?
Do I use just ADB for this or someother tools?
I did try one tool here from the vendors website but stuck as not sure what the Chinese characters mean..
Is the fact that this is only 1G i couldn't run Android at all and needs to be stripped down?
Cheers
Kosti
@Kostiz
Android Oreo Go Edition is a lightweight distribution of Android that runs better than normal Android on devices with <= 1 GB of RAM
How to backup device's Stock ROM is eplained here.
Thanks again mate!
Seem I have to do a lot of reading and thankfully everything is here, just got to spend time to read and have a go!
BTW how do I go about using volume rockers and power button to move around the menu in recovery when there is none but only the two buttons as shown the reset and recovery buttons on the main board?
BTW, the current ROM installed boots into a special menu, all other settings are hidden, would there be a way to enable seeing all the items and when getting the the settings (gear icon) that pops up in the corner, only takes me to the standard wifi menu to choose a wifi, so it seems everything else is hidden, if by enabling these I could potentially not need to do anything other than stop the default application from starting up - if that makes any sense
Could I just get back into a adb shell and try
adb shell
su
pm enable applicationname
I have to read up on rooting first I assume before I do much more, this is getting exciting, LOL :good:
Kostiz said:
BTW how do I go about using volume rockers and power button to move around the menu in recovery when there is none but only the two buttons as shown the reset and recovery buttons on the main board?
Click to expand...
Click to collapse
You use Android's HOME button to navigate within the Recovery menu, use POWER button to select option.
Hi, fellas! Please help me with one of these Citaq H10 POS. All we have is bootloop with some custom ROM showing vendor's logo.
Forcing it into recovery gives me some dead android screen with "No command" text.
Please guide me through this challenge, cause I have no other option but to ressurect it somehow.
Good news is that I have another one that is working fine, so we could try cloning it or something. Please help!
Yet I can't attach pics, cause of few posts, but if needed I can PM some.
citaq h10-2
I am also stuck with this machine citaq h10-2 , i did use a wireless kb to move up/down and not the 2 buttons on the motherboard , i can talk with it with ADB but all you can do is put it in sideload to upload new firmware and put it in fastboot but in fastboot you only get a black screen , what I have don is > opened up developer mode but you have no OEM UNLOCK tick box in side so running any bootloader unlock dose not work and i have run them all, if you google this machine for flashing new firmware you only get XDA this forum, unless any body knows another place to get the info from please let us know as i do think this would make a nice tablet with printer, the firmware is 5.1.1 and would love to put 6.0 or above on it but. i did download some firmware and used sideload to install it but it come up with error , i did try and make a backup but cannot do it ?, I think the firmware was from a galaxy s5 , I am not into all this firmware flashing so I am learning as I go along and if I brick it up well it was for free any way as the takeaway was shutting down and he gave it to me so no loss, if any body knows how we can get 6.0 or above on this machine please let us know.
A big thank you to all that can help put android 6.0 or above on this tablet.
Did you guys take a look at the solution here ? It worked for me ! All with a 2k ohm resistor...
Hola, alguien tiene la Rom de este dispositivo?
So I installed windows 11 on my sony Vaio VPCEG3AEN yesterday and I got an error during installation, so I used Rufus and installed windows as ON THE GO in the hdd.
Now the laptop is running smoothly but I am having trouble setting up the bluetooth.
Firstly there is no option to turn on bluetooth and when I try to add a new device I get a error saying couldn't connect
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the device manager I tried the default bt driver from windows and various other drivers including "Qualcomm Atheros AR3011" bluetooth driver but I keep getting "" icon after refreshing the device manager page, and in the device's description it says
"WINDOWS HAS STOPPED THIS DEVICE BECAUSE IT HAS REPORTED PROBLEMS. (CODE 43)"
Its not a hw damage or loose connection, i have windows 10 installed on another hdd which was previously used in the same laptop, so the bluetooth works fine in windows 10.
I haven't found a way to fix the bt yet
It would be really helpful if anyone have any idea to fix this issue
Update: I tried to backup the bt driver from windows 10 hdd using driver booster and after restoring the driver in windows 11 the bt started working, but some time after a reboot the bt stops working and I have to restore the driver again.
Haven't found a permanent solution
Nikhil Chandran said:
So I installed windows 11 on my sony Vaio VPCEG3AEN yesterday and I got an error during installation, so I used Rufus and installed windows as ON THE GO in the hdd.
Now the laptop is running smoothly but I am having trouble setting up the bluetooth.
Firstly there is no option to turn on bluetooth and when I try to add a new device I get a error saying couldn't connect
View attachment 5358733
In the device manager I tried the default bt driver from windows and various other drivers including "Qualcomm Atheros AR3011" bluetooth driver but I keep getting "" icon after refreshing the device manager page, and in the device's description it says
"WINDOWS HAS STOPPED THIS DEVICE BECAUSE IT HAS REPORTED PROBLEMS. (CODE 43)"
View attachment 5358763
View attachment 5358739
Its not a hw damage or loose connection, i have windows 10 installed on another hdd which was previously used in the same laptop, so the bluetooth works fine in windows 10.
I haven't found a way to fix the bt yet
It would be really helpful if anyone have any idea to fix this issue
Update: I tried to backup the bt driver from windows 10 hdd using driver booster and after restoring the driver in windows 11 the bt started working, but some time after a reboot the bt stops working and I have to restore the driver again.
Haven't found a permanent solution
Click to expand...
Click to collapse
What happens if you just uninstall the driver?
Nothing, in the device manager the bluetooth device gets the default ms driver and it doesn't work .
So now as a temporary fix I have to restore the driver over and over after a reboot or shutdown (sometimes it works even after reboot).
Nikhil Chandran said:
So I installed windows 11 on my sony Vaio VPCEG3AEN yesterday and I got an error during installation, so I used Rufus and installed windows as ON THE GO in the hdd.
Now the laptop is running smoothly but I am having trouble setting up the bluetooth.
Firstly there is no option to turn on bluetooth and when I try to add a new device I get a error saying couldn't connect
View attachment 5358733
In the device manager I tried the default bt driver from windows and various other drivers including "Qualcomm Atheros AR3011" bluetooth driver but I keep getting "" icon after refreshing the device manager page, and in the device's description it says
"WINDOWS HAS STOPPED THIS DEVICE BECAUSE IT HAS REPORTED PROBLEMS. (CODE 43)"
View attachment 5358763
View attachment 5358739
Its not a hw damage or loose connection, i have windows 10 installed on another hdd which was previously used in the same laptop, so the bluetooth works fine in windows 10.
I haven't found a way to fix the bt yet
It would be really helpful if anyone have any idea to fix this issue
Update: I tried to backup the bt driver from windows 10 hdd using driver booster and after restoring the driver in windows 11 the bt started working, but some time after a reboot the bt stops working and I have to restore the driver again.
Haven't found a permanent solution
Click to expand...
Click to collapse
You may try Driver Easy software to scan your drivers.
You could try taking out the cmos battery for a solid 10-20 minutes and see if it still does that. Make sure your pc is shut down, and the power cable is removed from the power supply.
I had the same issue, but with the intel ethernet controller. Properties showed the 43 error, device manager shows that it doesn't work.
Try removing the cmos. Good luck!
Is your BIOS up to date? Also, are you using a driver that is Win 11 compatible? Lastly, are all your hardware Win 11 compatible including your BT?
Processor1 gigahertz (GHz) or faster with 2 or more cores on a compatible 64-bit processor or System on a Chip (SoC).RAM4 gigabyte (GB).Storage64 GB or larger storage device Note: See below under “More information on storage space to keep Windows 11 up-to-date” for more details.System firmwareUEFI, Secure Boot capable. Check here for information on how your PC might be able to meet this requirement.TPMTrusted Platform Module (TPM) version 2.0. Check here for instructions on how your PC might be enabled to meet this requirement.Graphics cardCompatible with DirectX 12 or later with WDDM 2.0 driver.DisplayHigh definition (720p) display that is greater than 9” diagonally, 8 bits per color channel.Internet connection and Microsoft accountWindows 11 Home edition requires internet connectivity and a Microsoft account.
Switching a device out of Windows 11 Home in S mode also requires internet connectivity. Learn more about S mode here.
For all Windows 11 editions, internet access is required to perform updates and to download and take advantage of some features. A Microsoft account is required for some features.
Well for me I got it working with a command line tool. How ever my laptop of choice is a google pixlebook and the Bluetooth was active just would never connect to any devices. I searched all year looking for an answer and finel dropped into my head that i should try it from command line. There is an install package that can be downloaded and a good tutorial.Bluetooth-Comand-Line-Tools.
Worked for me could solve your issues as well.
Check your device
Before starting any complicated fixes, make sure you’ve checked these things:
Make sure your device supports Bluetooth
Make sure your device has turned on Bluetooth
Make sure your PC has turned on Bluetooth
Here’s how to check on Windows 11 PC:
1) Press the Windows logo key + A to open Quick Settings.
2) Make sure the Bluetooth button is enabled.
3) You can re-enable Bluetooth on PC by turning off Bluetooth and then enabling it later. Then check if your device can work on your PC. It may work for some users.
Regards,
J Wick
Must be a common issue as I have exactly the same issue and the same photo's to display too.....I tried a Co called Driver Updater, the free version but that was totally useless, did nothing then they harassed to upgrade repeatedly. Still not got a fix for my W11 VPC but looking into it. Pity Sony have dumped the product range as they used to be pretty good for drivers etc....no longer. I just need to get my mitts on a driver, thought it would be quite simple ....ha!
finally found the driver pack at:
https://ftp.hp.com/pub/softpaq/sp72001-72500/sp72163.exe
and its now up and working on my Sony Vaio VPCEH on Windows 11
Run the Bluetooth troubleshooter
Press the Windows + I keys to open the Settings menu.
Select Troubleshoot from the left.
Click on Other troubleshooters.
Hit the Run button for Bluetooth.
Wait for the troubleshooter to complete the process and do the needful if asked.
I first had the BT issue on my laptop when attempting to use Windows 11 Phone Link to link my iPhone. I got this:
I have been researching this for two weeks. The same thing happened with other programs emulating Phone LInk i.e Wormhole and iMyfone, (Wormhole worked on my Windows 10 desktop and allows me to control all functions of iPhone 14 pro). I did all the installing/reinstalling/getting latests BT drivers from Intel etc. used the BT troubleshooter, which kept telling me that BT radio was not turned on even though it was, and when the troubleshooter offered to turn it on and I agreed, nothing happened and the process then repeated itself.... then I noticed that my iPhone was showing in BT in device manager, so I paired and unpaired etc, other devices like, Razer Pro click mouse, speakers etc all worked perfectly. So there is nothing wrong as far as my diagnosis can make out , with my BT. I have latest Windows 11 updates 22H2, I have uninstalled and reinstalled the Phone Link app, tried safe boot and selective startup, going though the usual procedure of disabling services half and half to figure out if a driver is buggy. (by then it was 4am in the morning and I was gurgling spittle all over the keyboard and the neghbours were knocking on my walls because my shouts of frustration and expletive laden rants at Microsoft had woken them up etc etc) So the app is NOT seeing BT and the sames is true of emulations of the same software. Therefore ,the problem must be within the Windows 11 OS settings somewhere. Also as with another poster on here the BT on off radio button disappeared, I found it again but in a completely different location (I am confusing myself now cos I can't remember exactly where ,but it was through Control Panel) I have posted all over Microsofts communities and support pages, found other users with the same or very similar problems with this app. Microsoft specialist have suggested only things I have already done.I have City and Guilds and Comp Tia certs. for Windows systems and have been fixing them since Windows 98 (all through them and the Vista BSD wars ho ho ho ) so I am not exactly a dunce ... eeeeerm! and yet I cant fix this one seemingly simple bug. Any suggestions or ideas cheerfully tried. Thanks.
SilvaKuff
Razer 15 2020 (Base) i7-10750H CPU OS Build 22621.1778 32GB RAM 2 x 1 TB NVME SSD's Windows 11 pro 64 Bit NVidia Ge Force 2070 Max Q
frankbonatelli said:
Well for me I got it working with a command line tool. How ever my laptop of choice is a google pixlebook and the Bluetooth was active just would never connect to any devices. I searched all year looking for an answer and finel dropped into my head that i should try it from command line. There is an install package that can be downloaded and a good tutorial.Bluetooth-Comand-Line-Tools.
Worked for me could solve your issues as well.
Click to expand...
Click to collapse
Thanks frankbonatelli, I checked this out but it is designed for versions before Windows 11, it could work but might confuse things too.?
SilvaKuff