Hi all,
Looking for a little advice -- I've got a completely wiped (ie no data on the internal SD card) Galaxy Tab 10.1v that's stuck in a boot loop -- just continually cycles the first 'Galaxy Tab' logo again and again.
I'd ideally like to reset it to the stock Samsung 3.0.1 rom, but I can't get Odin to see the device.
I can happily get onto the Fastboot/Download mode screen, and Fastboot mode works fine (skitzandroid's recovery image from his rooting guide will let me get into basic recovery mode). However, switching to Download mode and checking with ADB for connected devices just yields a blank list -- ADB seemingly cannot find it, although it shows up in Windows Device Manager just fine.
I've confirmed ADB is working by plugging in my SGSII phone -- it's seen instantly.
I'm presuming that as ADB can't see the 10.1v, Odin can't either.
Does anyone have any advice on getting ADB to work?
Thanks!
------------------------------------------------------------------------------------
Scratch the above -- installed Kies and tried a bunch of different USB ports and that eventually fixed Odin's ability to detect the tablet. (It's worth noting that ADB still couldn't see it, however.)
Hope this helps anyone unfortunate enough to come across the same issue; I'm going to go clean the inside of my pants now.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Related
Hi all,
So, I done effed up. I've been running Elegancia with no problems for a while now, and decided off the cuff to try something new. Long story short, I didn't read properly and ended up flashing an International ROM to my phone by accident. No problem, I think, I'll just ADB sideload Elegancia again.
I boot into TWRP recovery and then find that my computer no longer recognizes my phone. So, I hit restore on TWRP, and restore a backup that I'd made beforehand. After everything finishes restoring, I discover to my dismay that the backup did not include my OS.
Now, when I power up my phone, I can boot only into bootloader. When I try to boot into recovery, the phone is stuck on the TeamWin logo and doesn't move. If I turn on the phone without booting into bootloader, I'm stuck on HTC's logo. My primary goal right now is just
In conclusion, I have no idea what to do with the following problems:
1. When booting into bootloader, my computer no longer recognizes my device, so I have trouble flashing TWRP. Basically, my computer searches for an HTC MTP driver, and then fails to find one/install one. When I try to update the driver manually by downloading a MTP driver and then installing via Device Manager, Windows tells me I'm already using the most up-to-date version.
2. When booting into bootloader and then going to Recovery, my phone will boot into teamwin's logo ... and then not move from there.
I'm aware that I've screwed up pretty bad-- I've done my best to read stuff that's relevant, though. I'd love more help, please! Thanks in advance. Lots of invisible cookies coming your way.
[EDIT: It turns out TWRP was just taking a really, really, really long time to load. That said, my problem now is this:
- When going to Advanced -> ADB Sideload, my computer does not recognize my device when using adb devices.
How can I make sure that this actually works? Thanks again!]
[EDIT #2: Okay, um, I don't know why, but for some reason my computer now lists my device after going into sideload from TWRP. Maybe something to do with a reboot of my computer. If that's true, I feel really stupid. Will update if sideload doesn't work ... I think the cosmic gods are laughing at me. I guess all I had to do was post in xda-developers so that I could publicly embarrass myself before I fix my phone.]
[EDIT #3: Everything works and I'm dumb.]
Please HELP!
Yesterday I flashed my Odys Xelio (Allwinner A10) with CWM. After booting in a working state, I restarted in Recovery too full whipe and whipe dalvik, I installed gapps ans the compatibility.zip also from CWM.
After that I got stuck in a whitescreen. I can not access anything, not even CWM recovery anymore. In win 8 I only could see 1 to 2 undefined devices (should be a problem with the device AND a driver issue).
In Linux I could see a device in adb yesterday and could put it into "adb reboot recovery". Still whitescreen on the tablet, but I could push a recovery file with adb to the /sdcard/. Rebooting didn't bring me to another state.
Today I am not able to connect via adb. It always tells me "List of devices attached" and an empty list.
Display should be okay, no cable issue or sth. else. I really hope someone can help. Perhaps theres a way to JTAG the devices or there is a trick with pressing some buttons and using the USB cable...
BTW: While booting into CarbonRom the first time, the button-behaviour was strange or even totally not working. Perhaps that's a point?
THX in advance
EDIT: Now, after playing around with a needle into a "reset-hole" I finally found a way to see the device in adb. How do I go on!?
My screen and digitizer are broken on my S4. It is running the ME7 firmware (bought it that way), so I can't go back to MDK or apparently use any sideload stuff (such as CWM recovery).. At least, don't think so. I tried blindly doing it, but no luck.
I want to get app data off the phone (not just apks, but save data), was thinking adb, but when I boot into recovery, it shows unauthorized (on the PC that I rooted it with). When I plug in while it's booted, it never shows in the list of devices at all. Yes, I have the latest drivers from Samsung, yes, I have the latest adb, yes I have tried different cables. No, I cannot click or accept or navigate the phone at all through the touchscreen, nor even see what is displayed (broken!)
Is there any way to override this somehow and get access to the internal memory? I already copied everything that it shares by default through the file sharing mode (that still worked fine), but that doesn't give access to /data/data/ etc...
adb Summary:
- Recovery mode shows unauthorized. If I use the menu options (blindly), I can get it into sideload mode. I did something to get it into recovery status in adb, but I have no idea how I did that, and I wasn't able to get any data off in that mode either anyway.
- I can get it into Download mode, but flashing CWM didn't work (with heimdall), and adb shows nothing useful in that mode.
- Booted, it goes into the regular share files mode, but adb devices lists nothing.
Really hoping I won't have to either lose all my save data, or buy the docking station..
Thanks in advance!
Have exactly the same problem
Lander3 said:
My screen and digitizer are broken on my S4. It is running the ME7 firmware (bought it that way), so I can't go back to MDK or apparently use any sideload stuff (such as CWM recovery).. At least, don't think so. I tried blindly doing it, but no luck.
I want to get app data off the phone (not just apks, but save data), was thinking adb, but when I boot into recovery, it shows unauthorized (on the PC that I rooted it with). When I plug in while it's booted, it never shows in the list of devices at all. Yes, I have the latest drivers from Samsung, yes, I have the latest adb, yes I have tried different cables. No, I cannot click or accept or navigate the phone at all through the touchscreen, nor even see what is displayed (broken!)
Is there any way to override this somehow and get access to the internal memory? I already copied everything that it shares by default through the file sharing mode (that still worked fine), but that doesn't give access to /data/data/ etc...
adb Summary:
- Recovery mode shows unauthorized. If I use the menu options (blindly), I can get it into sideload mode. I did something to get it into recovery status in adb, but I have no idea how I did that, and I wasn't able to get any data off in that mode either anyway.
- I can get it into Download mode, but flashing CWM didn't work (with heimdall), and adb shows nothing useful in that mode.
- Booted, it goes into the regular share files mode, but adb devices lists nothing.
Really hoping I won't have to either lose all my save data, or buy the docking station..
Thanks in advance!
Click to expand...
Click to collapse
Did you find a fix?
Hi all,
I tried to back up my samsung galaxy ace and when accessing the playstore the device froze and upon a battery pull
started to get stuck on the samsung logo or a continual system reboot without ever making it into android. I tried a long battery pull, rebooted the system and wied the cache partition none of which worked.
I was hoping to get the text messages and contacts off the internal storage so these can be transferred to a new phone.
Since then I have downloaded the SDK kit for google and downloaded the ADB drivers and can access ADB from a command prompt window.
I am hoping to be able to use ADB to use the "pull" command to retrieve files from the internal storage but when using the ADB devices command the phone does not show up so doing anything with ADB is not an option.
When I put the phone in download mode windows recognised it with an exclamation mark. I downloaded Kies and then windows started associating it with a CDC driver (whatever that is) but I cannot force windows to see the ADB driver.
I have tried manually pointing it to the ADB driver stored within the SDK ...folders but it just won't see it.
Further, I downloaded Clockworkmod for the galaxy ace as I hoped that it would give me options to boot into nandroid and get the files that way. It said the upgrade of firmware worked but now unless I force download mode when starting up, the phone goes straight in to the reboot system now, apply update etc menu but then says"E:failed to mount /system (Invalid argument)" twice and that's it.
I do not have usb debug enabled.
So, help needed please all you kind people out there. How I make windows see the ADB drivers or get it to recognise the phone for ADB access or is there any other way I can get these files off, by installing CWM I've only played around with the boot software and not the actual OS so the data should still be there, am I right?
These texts messages are more than important , both they and the contacts are crucial.
This all happened when I was trying to back up the data and now I can't.
I don't need to spare the phone just the data, surely someone somewhere can get at it?
Thanks
mr_stupot said:
Hi all,
I tried to back up my samsung galaxy ace and when accessing the playstore the device froze and upon a battery pull
started to get stuck on the samsung logo or a continual system reboot without ever making it into android. I tried a long battery pull, rebooted the system and wied the cache partition none of which worked.
...
When I put the phone in download mode windows recognised it with an exclamation mark. I downloaded Kies and then windows started associating it with a CDC driver (whatever that is) but I cannot force windows to see the ADB driver.
I have tried manually pointing it to the ADB driver stored within the SDK ...folders but it just won't see it.
Click to expand...
Click to collapse
Sounds similar to what happened to me, although on my LG G4. The phone randomly froze and then from there only would bootloop the LG screen, never making it to the Verizon screen. It turned out that components came loose within the phone which caused the boot to fail, as it was a known G4 issue.
What happened with my phone is that my computer wouldn't recognize it as anything other than my processor, and I could only stay in Download mode for about 1 minute before power off. Recovery mode literally had no effect other than "power off".
Personally, I wasn't worried about my data, so I sent it off to be repaired, but while searching around I found this post (can't post links yet, sorry):
Code:
forum.xda-developers.com/att-g4/general/lg-g4-stuck-bootloop-rma-solution-t3279690/post67131904#post67131904
This may be a way to get the data off, BUT ONLY IF you are suffering from the same issue. I'm sorry to say, but it is probably NOT the same issue, but seeing how no one has responded yet I figured I'd through you a lifeline. It's a possibility.
Best of luck to you though, and sorry I couldn't really answer the question.
Hello,
I have an LG G watch w100 that only boots to the LG logo. Initially I thought this to be a battery issue however it appears to be pulling correct power, and it also stays powered on while at recovery or fastboot screens. I do not know the entire story behind this as far as how it got to this point. I have been doing some research on here and other forums to figure out how to re flash it with stock firmware. Factory reset on the device does not do anything different. It recognizes in ADB when in "apply update from adb" mode. However I am having a gap of knowledge between this recognizing in ADB and me being able to restore it. I found a link to the original 6.0.1 software on here, but the video was using the round version of the watch. I have the MEC23G version, I saw a post here posting factory images but the link is dead. Not looking to root this by any means, just looking to get it working again. Any help greatly appreciated. I have tried to use the sideload command in ADB with the file I downloaded but it does not recognize that as correct syntax. I also cannot verify if usb debugging is on or off as the device cant boot fully. I have limited ADB experience .
Thank you in advance