My Arc7HD boots up but gets stuck on set up screen. In the background you can see the deice is connected to wifi but I get an error saying there is something wrong with your wifi and it won't let me go any further.
I can boot into ADB and can even access the Arc's Hard Drive on my PC.
Any Ideas?
Thanks
I have tried sideloading several different zipped ROM's to no avail - The unit doesn't think it can connect to wi-fi for some reason???
Related
I have an AT&T Pure, and I've been trying to install a new ROM after having flashed several ROMs over the past few months. Everything works fine except, when the tri color screen comes up it flashes twice, and it never says USB at the bottom of the screen. Eventually the software gives up and I get a connection error, and the screen gets stuck on the tri color screen.
Windows Mobile Device Manager recognizes my phone. My phone shows up under "my computer". So everything seems to work properly with the exception of the ROM flashing utility being able to access the USB connection. Can anyone help me figure this out?
Make sure on your phone under USB to PC settings it is set to Sync when connected to a PC and not to share internet or act as a hard drive.
Hi, I'm having a huge problem with my TF201.
I have unlocked device (via official tool), it's rooted and I've been running some ancient version of AOKP ROM. I have no idea why, but I was unable to install any other ROM, so I used the AOKP ROM. After a while my device was painfully slow, so I decided to do a factory reset. I invoked it from a running system. Device was restarted, displayed an ASUS logo and got stuck. I waited hours hoping it will do something before trying to restart it. Since then I'm stuck at the stupid ASUS logo and can't do anything about it.
When I press PWR+[WOL_DWN] it restarts, displays ASUS logo and that's all. I have no options as usual, no recovery, USB and other icons. Nothing.
PWR+[WOL_UP] is probably working properly (black screen, new USB device found in Windows / linux), but I have no idea what to do with this. I Googled lots of similar problems, but nothing worked for me. I tried installing various drivers for APX, fastboot and ADB, but nothing worked. Furthest I have gotten was with naked APX driver and nvflash tool, but it says "unknown device found", with other drivers and tools I get only "no devices found".
Does anyone have some idea what to do with this? I would be really grateful.
Thanks in advance!
Since update cm-10.1-20130626-NIGHTLY-tf201.zip, i have the same problem!
Looks like only option is to send it to ASUS and pay for repair... Or to use tablet as coaster under my coffee...
myflower said:
Hi, I'm having a huge problem with my TF201.
I have unlocked device (via official tool), it's rooted and I've been running some ancient version of AOKP ROM. I have no idea why, but I was unable to install any other ROM, so I used the AOKP ROM. After a while my device was painfully slow, so I decided to do a factory reset. I invoked it from a running system. Device was restarted, displayed an ASUS logo and got stuck. I waited hours hoping it will do something before trying to restart it. Since then I'm stuck at the stupid ASUS logo and can't do anything about it.
When I press PWR+[WOL_DWN] it restarts, displays ASUS logo and that's all. I have no options as usual, no recovery, USB and other icons. Nothing.
PWR+[WOL_UP] is probably working properly (black screen, new USB device found in Windows / linux), but I have no idea what to do with this. I Googled lots of similar problems, but nothing worked for me. I tried installing various drivers for APX, fastboot and ADB, but nothing worked. Furthest I have gotten was with naked APX driver and nvflash tool, but it says "unknown device found", with other drivers and tools I get only "no devices found".
Does anyone have some idea what to do with this? I would be really grateful.
Thanks in advance!
Click to expand...
Click to collapse
Same problem here.. Any solution yet?
Hi
New on here so sorry if I don't know to much
I have a Nexus 7 2012. Install Timurs kernel and Rom on my tablet and installed it in my car, and it worked great for months, then the other day it shut down. When I rebooted it, it gets stuck on the Google logo.
If I try boot into recovery it once again gets stuck at the Google Boot logo
I can get it into Fastboot mode but it wont connect to the PC. I am sure the Drivers are ok as I have another nexus 7 and i have today flashed a new rom using the WUGs Nexus Toolkit
Any Ideas anyone as at the moment I would class this as bricked as it wont boot, wont go into recovery and wont connect to the PC
Any advice would be hugely appreciated
Cheers
Aaron
aaronthew said:
Hi
New on here so sorry if I don't know to much
I have a Nexus 7 2012. Install Timurs kernel and Rom on my tablet and installed it in my car, and it worked great for months, then the other day it shut down. When I rebooted it, it gets stuck on the Google logo.
If I try boot into recovery it once again gets stuck at the Google Boot logo
I can get it into Fastboot mode but it wont connect to the PC. I am sure the Drivers are ok as I have another nexus 7 and i have today flashed a new rom using the WUGs Nexus Toolkit
Any Ideas anyone as at the moment I would class this as bricked as it wont boot, wont go into recovery and wont connect to the PC
Any advice would be hugely appreciated
Cheers
Aaron
Click to expand...
Click to collapse
You can't go into your recovery?
Install ADB and try to connect your Nexus to your PC and enter "adb devices". See if your tablet is recognized like that.
How to setup ADB
Do not use toolkits with Nexus devices.
cheers for the advice but nope no luck still wont connect
aaronthew said:
cheers for the advice but nope no luck still wont connect
Click to expand...
Click to collapse
When you plug your tab in, does it even attempt to load drivers and just fails or does it not even recognize that you plugged anything in? Make sure by checking the Device Manager as you plug / unplug. If it just doesn't load correctly, then attempt to load the Naked Universal Drivers manually and then you should be able to get things back on track at least with fastboot flashing the stock img files back to it. If the Device Manager doesn't change or show any differences when you plug in the tab, then that's a bad thing... If you can boot to the bootloader still, most likely it can be fixed. If it only boots to a black screen and when plugged in shows the APX driver, you're boned. That problem IS fixable, but only if you would have saved your blob.bin and wheelie blobs before it went down, which I am certain you didn't do as it is not a common procedure.
es0tericcha0s said:
When you plug your tab in, does it even attempt to load drivers and just fails or does it not even recognize that you plugged anything in? Make sure by checking the Device Manager as you plug / unplug. If it just doesn't load correctly, then attempt to load the Naked Universal Drivers manually and then you should be able to get things back on track at least with fastboot flashing the stock img files back to it. If the Device Manager doesn't change or show any differences when you plug in the tab, then that's a bad thing... If you can boot to the bootloader still, most likely it can be fixed. If it only boots to a black screen and when plugged in shows the APX driver, you're boned. That problem IS fixable, but only if you would have saved your blob.bin and wheelie blobs before it went down, which I am certain you didn't do as it is not a common procedure.
Click to expand...
Click to collapse
Hi
I can get to the bootloader screen and it says Fastboot mode on the tablet.
When i plug the tablet into the Pc, device manger does not refresh and the computer makes no acknowledgement at all when I plug the device in
aaronthew said:
Hi
I can get to the bootloader screen and it says Fastboot mode on the tablet.
When i plug the tablet into the Pc, device manger does not refresh and the computer makes no acknowledgement at all when I plug the device in
Click to expand...
Click to collapse
Hmm. Very odd. Typically if the bootloader is still there, the rest is easily solvable. What happens when you choose the recovery option from bootloader? Unfortunately you have to test some more things to eliminate the easy stuff. These include trying different cords, ports, and computers. If possible, see if you can try a Linux PC as well or at least a Live CD. If TWRP still loads at all and supports USB OTG, you might be able to load something from it as a long shot.
es0tericcha0s said:
Hmm. Very odd. Typically if the bootloader is still there, the rest is easily solvable. What happens when you choose the recovery option from bootloader? Unfortunately you have to test some more things to eliminate the easy stuff. These include trying different cords, ports, and computers. If possible, see if you can try a Linux PC as well or at least a Live CD. If TWRP still loads at all and supports USB OTG, you might be able to load something from it as a long shot.
Click to expand...
Click to collapse
if i choose recover, to gets stuck on the google screen
Tried different cables, Pc and PC ports no luck
I could try get linux on vm when i get home? never used it thou
Sucks man. Such a random thing and not typical of most Nexus issues. This is the only other option I can think of then: http://mobiletechvideos.mybigcommerce.com/asus-nexus-7-2012/ - Brick service. These guys are legit. They have a great reputation and I've personally used their services twice (different devices) and one was fixed while the other was a lost cause, but Josh was nice enough to refund some of the money since it didn't work. I'm guessing they would need to do what's called a JTAG service where they hook up (usually solder) a special cable to a specific port on the board and it kind of circumvents the other issues and reloads the OS back on.
Thanks for all you hep mate will prob give them a try
No problem. Good luck!
i was trying to flash a different rom onto my tab and it got stuck in bootloop. I tried to boot into recovery mode and it just says downloading forever. I originally used goo manager and I don't think it is supported anymore, not sure if that caused it. I was trying to fix it with adb by connecting it to my laptop, but it wont recognize my device and I cant get into it to change any settings. fixable? thanks
update: I got it connected to adb. how do I reset it? while saving or backing up data, if possible
Hi!
I have searched XDA forum and other forum concerning LineageOS. But I have not found a solution.
My latest experiments were with installation of the adb interface on windows. At first, this worked well and I got full massstorage access. The Galaxy and its both memories did show up in Windows Explorer (like in old ages).
At the next restart of Windows (Win 7 64-bit Pro) when I connected my phone, Windows immediately did install the samsung drivers again. And since that things got even worse: No even the MTP and PTP Mode did not work, so that the Smartphone does not show up at all in the Windows Explorer!
At F-Droid, I have found an app, called USB Mountr. I tried this, but without any effort.
In the device manager of Windows I can see an „Android Composite ADB Interface”. It tells, that the device would work OK.
Now I am stuck with this and I hope, someone will help me, to activate usb massstorage access.
BTW: I have flashed my Galaxy S2 with Heimdall, running on Ubuntu. Heimdall on Windows 7 did not work, because of libusb error -12.
Latest status:
I have uninstalled the app USB mountr and did reboot the phone. Now the USBconnector is only active for charging the battery. I even get no connection in PTP or MTP mode.
Then I have deactivated USB debug mode and ADB. did a reboot, reactivated ADB and USB debug etc. and did further reboot the phone but with no success.
USB connection is nearly dead and cannot have connect with LUBUNTU Laptop. On Win 7, I get the signal tone, which is typical for connecting an USB device. The GT.i9100 shows up in Explorer but cannot be connected. Device manager tells me, that it is an Android device and all would be OK.
As a work around I am using MyPhoneExplorer on Win-7 and KDEconnect for Ubuntu.
Please can anybody tell me, what I should do, to get back at least USB connection in MTP or PTP mode???
I have the exact same problem.
I did notice, that after first boot, there was a message (several times) the MTP daemon/service stopped working (Crashed ?)
Does anyone else encounter this ?
Did anyone else resolve this ?
(Currently I was only able to get/send files to the device via BT, which is slow, annoying,
and a lot of work moving files to their required places after transmitting over BT)
Quick Fix for stuck on boot
This probably isn't the right place but you said there weren't many solutions. If your phone randomly gets stuck on boot you need to Delete Everything including system, factory data reset, flash ROM again with ADB, go through setup. The reason it probably hanged is because you installed an old version of SuperSU Binary or because you flash OpenGapps before setting up phone.
Hope this works
P.S Sorry for the late reply