Hellohello I am new here so please bear with me.
My Duo randomly decided today that it is going to be stuck in a bootloop. I don't use cloud services so unfortunately none of my pictures were backed up; I'm trying to pull those from my phone.
I can get it into ADB sideload mode, and my computer recognizes it, but when I use ./adb pull, it returns an error, "closed."
Can anyone help? Please be patient with me, and break things down for me; my degree is in engineering, not computer science, so I'm not very familiar with common commands and such.
Thank you!
Try mounting system from the recovery menu before doing adb pull.
Related
Hi everyone,
Well I'm in that freak out stage.... where I am sure some of you have been.
Heres my issue...
I have a transformer prime that;
I just unrooted using Vipermod
Then did a factory reset
Now I am stuck in CWM recovery
I attempted to do a restore but after it gets done it brings me back into the recovery
I attempted to ADB but the command prompt opens and closes right away ( I assume from not being in USB debugging, which I cant get into without a rom)
I have no rom's currently downloaded into the prime as I just wiped everything in there as well.
Please i'll gladly pay $5 to anyone who can fix this without it breaking more (hard bricking if I havent already done so)
AHHH please guys help, I'm afraid it will run out of battery soon then I'll be royally screwedddd
anyone?
are you on windows 7?
yes windows 7 professional sp 1 32bit . to reiterate I am stuck in Clockwork mod Recovery without root, and with no roms on the internal SD. I have access to one restore that works but after it completes it reboots back in recovery.
birchnick10 said:
yes windows 7 professional sp 1 32bit . to reiterate I am stuck in Clockwork mod Recovery without root, and with no roms on the internal SD. I have access to one restore that works but after it completes it reboots back in recovery.
Click to expand...
Click to collapse
Turn on your tablet, let it boot into CWM.
Open cmd, cd to the directory with adb (for example cd C:\android), then copy this line of text below and right click > paste in the command prompt window.
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
Click to expand...
Click to collapse
That should get you out of CWM into Android, assuming your restore works fine.
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
can i fastboot push a rom to the internal sd card or better yet can i install a rom from the external SD card via Clockwork mod recovery?
birchnick10 said:
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
Click to expand...
Click to collapse
Navigate to %android sdk folder%\extras\google\usb_driver, open android_winusb.inf and copy the following in the sections
"Google.NTx86" and "Google.NTamd64"
; TF201
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4D01&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4D03&MI_02
;
; Fastboot for all projects
%SingleBootLoaderInterface% = USB_Install, USB\VID_0B05&PID_4DAF
Click to expand...
Click to collapse
Save the file and then try running the adb command I gave again.
Says error device not found. I appreciate the help keep it coming it's keeping my hope alive. I really hope this isnt truly hard bricked.
I cant get ADB to read the transformer prime. When I type adb devices nothing shows up . it starts the daemon successfully but then doesn't show the tfp.
Thank you again for helping. I am honestly going to pay who ever finds the true fix. This stress sucks
birchnick10 said:
Says error device not found. I appreciate the help keep it coming it's keeping my hope alive. I really hope this isnt truly hard bricked.
I cant get ADB to read the transformer prime. When I type adb devices nothing shows up . it starts the daemon successfully but then doesn't show the tfp.
Thank you again for helping. I am honestly going to pay who ever finds the true fix. This stress sucks
Click to expand...
Click to collapse
Try the instructions here. Try using this only as a last-ditch resort.
it wont shut off either... i tried both of the above mentions and cant get adb to recognize the prime
Attempted both and stuck at recovery loop without root. any more ideas? is it possible to flash rom from external sd? or is there a recovery I could fastboot rhat has this feature?
Attempted both and neither work. I need to somehow get usb debugging enabled while in clockwork mod. Or figure out a way to install a rom via external SD card while in CWM. Any more help is appreciated!
birchnick10 said:
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
Click to expand...
Click to collapse
No adb debugging is needed in cwm. Even without any ROM installed. Recovery is different from Android.
Try to long press power (at least ten seconds) to hard reboot, and see if it changes something in device detection.
Did a hard reset and it boots me back into Recovery.
I was able to get a new rom into the internal SD via the emergency/backup.zip method but after it completes and I do a reboot it just boots right back into recovery again.
Any help please is apprecaited.
$5 bounty for a fix via paypal
Oh joy. This one is a spaghetti western in the making.
Okay. Question first : Does Windows 7 RECOGNISE the device in any way shape or form. To find out if this can be done, you need to power up the device and hold the power and volume down buttons, DO NOT press volume up when it suggests a kernel image. If you get three icons, hit vol down once and up once, then plug the USB cable into the PC and the tablet.
If it sees "Something", you've a chance. Download the naked universal USB driver from the dev forum, install it and have your device pick it up on the windows computer. I'm assuming from your comments that you've GOT a working fastboot and adb so I'm going to skip the instructions on that.
If you do have a something, and it's recognised, hit fastboot -i 0x0b05 reboot, if it reboots of it's own accord at this point, you can confirm you have working ADB and Fastboot access. From there you've a few choices. My personal preference would be to ADB push a rom down -after- doing a rebuild of the recovery image via fastboot (I really recommend TWRP for this bit).
http://forum.xda-developers.com/showthread.php?p=26093546#post26093546 - This post here which I wrote will explain how to flash TWRP from fastboot access, presuming you can get it. Once that step is done, wipe EVERYTHING from TWRP, and I mean the whole nine yards, including /system. Raze the memory down to only things it can't actually nuke. Once that's done, reboot to fastboot protocol, get a ROM pushed via ADB and install from inside TWRP.
That -should- get you back in business. Though judging by the tangle you're in, I make no promises.
ADB wont recognize the device. I have installed and uninstalled the drivers about 5 times.
It wont boot into fastboot - just goes directly into Clockwork Mod recovery. Even while holding power and volume down text comes up that says looking for asus recovery. then says clockwork recovery and boots directly into that.
The only way I can get anything into the internal SD card is with MasterZen88's Emergency script tool that puts any 1 file into the internal SD card as backup.zip
It was unrooted prior to all of this as well.
*cringe*
If ADB isn't working -at all- and it's not using the naked USB drivers to get you any kind of workable access. You're starting to smell very much like a hard brick scenario. I'm honestly not sure if there's a way out of that. A lot of the solutions for unbricking absolutely require that the device is able to talk to the outside world, if it's not and the ADB shell is essentially telling you it's talking to dead air, you're in a world of pain.
It's a long shot but it may be worth speaking to ASUS to see if they are willing to, for a fee, restore your tablet to factory settings. Though I can't imagine that will be cheap or simple. If you are able to get an RMA or a means of getting ASUS to poke it, make sure to take photos. Their techies appear to have the worst case of butterfingers in the world.
Go over Pandaball's suggestion, because that's really the last step I can think of before contacting ASUS
I'm trying my hand at porting a ROM to my device (S4 HTC One X/XL, Evita) and I've gotten as far as the bootscreen, but it hangs there (with the bootanim still running). I'd like to take a look at what's happened on the device, but I can't seem to use adb with it at this point. I've made sure drivers are installed and used multiple USB ports. ADB works in recovery and fastboot works in fastboot, but adb returns Offline when I run adb devices while the phone is sitting at the bootscreen.
Found this on StackExchange: http://android.stackexchange.com/que...-for-debugging
According to some of the replies, it's possible to use adb at boot, so I'm not sure why adb returns offline. I tried running adb logcat while the phone is off and letting it boot, but adb never establishes a connection to the phone. Not sure why it can't. Hopefully it's not another adb driver issue. I've already spent a ton of time getting adb working with this phone while booted/in recovery.
Try this it should capture a logcat of the phone booting up, power off the phone while still connected to the usb and enter the following it should say - waiting for device -
Power on the phone then cross your fingers if all goes well you should capture the logcat to bootlog.txt file in your temp directory.
Code:
adb -d logcat>c:\temp\bootlog.txt
Sent from my PACman GT-i9100 using Xparent ICS Tapatalk 2
AuSSiELaMbChOpS said:
Try this it should capture a logcat of the phone booting up, power off the phone while still connected to the usb and enter the following it should say - waiting for device -
Click to expand...
Click to collapse
Protogon said:
I tried running adb logcat while the phone is off and letting it boot, but adb never establishes a connection to the phone. Not sure why it can't. Hopefully it's not another adb driver issue. I've already spent a ton of time getting adb working with this phone while booted/in recovery.
Click to expand...
Click to collapse
The ROM is 4.2.1-based, so if the USB Debug Whitelist was implemented in that version, that might be the problem. Running adb logcat from power off with a ROM that boots fine reveals that adb starts pretty much as soon as the bootscreen comes on and logcat should start spitting out data just as quickly.
If it's not a whitelist issue, something is preventing even adb from starting on the phone.
This is a problem I too have run into while porting a ROM to my GiONEE Dream D1 (MTK 6589) Device. Have you had any luck?
Wish there was a field in build.prop to say "boot with verbose remote logging"
RickyGoldsmith said:
This is a problem I too have run into while porting a ROM to my GiONEE Dream D1 (MTK 6589) Device. Have you had any luck?
Wish there was a field in build.prop to say "boot with verbose remote logging"
Click to expand...
Click to collapse
Replying to self.
You need to modify the init shipped on your OS and instruct it to start adbd asap.
Protogon said:
I've gotten as far as the bootscreen, but it hangs there (with the bootanim still running). I'd like to take a look at what's happened on the device, but I can't seem to use adb with it at this point.
Click to expand...
Click to collapse
You can try to reboot into a working system right after (e.g. the recovery) and retrieve the last kernel boot messages by:
adb shell cat /proc/last_kmsg > last_kmsg
and then see whether you can figure out what happens by reading this log file
Hello friends,
I was using a General Mobile etab4 tablet,
rooted,
bootloader locked,
not backed up, i tried but apps wont recognize the brand,
the stock rom is not available anywhere but I managed to find some custom ones.
This tablet is actually a given by government for educational purposes, and it has no download mode, I can only initiate recovery mode with volume up+power button combo, and there is no sd card in it.
Here is what happened. It was running with problems so I decided to flash a custom rom I find on this forum. First I tried flashing using adb sideload. I got an error message "Installation aborted" with no error codes after verification step but it does not state whether verification is failed or not. I don't know what actually failed. Then I tried to flash it using adb shell as root (the system image was in /sdcard directory). It freezed, I exit the shell using Ctrl+C command. Then whenever I try to start shell i got "error:closed" message. I see my device with adb devices with sideload, but it is not seen in fastboot devices.
When I try to open it, I guess it enters in a small boot loop (screen flickers multiple times with brand name on it) and after some time I got dead android with no command written.
I tried,
reflashing it again with Android AIO Flasher,
use fastboot to unlock bootlader (it says "waiting for device") although adb devices sees it,
re-installing the adb drivers after uninstalling them,
disassembling the device to see if I can detach memory to edit it and to see if disconnecting the battery helps,
I even used a simple jig to see if i can initiate download mode (know it works for specific devices but you know hope)
Apparently, I messed up the device but the hardware must be all fine. So I think there must be a way out. What can you suggest, I wish I have unlocked the bootloader. I can send the pictures of its motheboard it helps,
Thanks in advance.
My e970 got smashed, and touch screen is out.
I cannot get into the phone as the lock screen is impossible to swipe. I tried the ADB method of editing the lock screen settings of the ROMs . However I am not able to get into the ADB shell to execute the commands. ADB only works in recovery and lists device as a recovery and not as a device proper.
There a way thru the ADB in recovery by executing pull command but ADB cannot access the System / data folders for the Build.prop file to be edited. In my situation, as ADB only connects in recovery mode, it is not entering the sytem area and file cannot be found.
Please advise on the way forward, as I cannot find a guide in this situation, most guides show the ADB pull command, which in my case does not work.
Milind
milindchitale said:
My e970 got smashed, and touch screen is out.
I cannot get into the phone as the lock screen is impossible to swipe. I tried the ADB method of editing the lock screen settings of the ROMs . However I am not able to get into the ADB shell to execute the commands. ADB only works in recovery and lists device as a recovery and not as a device proper.
There a way thru the ADB in recovery by executing pull command but ADB cannot access the System / data folders for the Build.prop file to be edited. In my situation, as ADB only connects in recovery mode, it is not entering the sytem area and file cannot be found.
Please advise on the way forward, as I cannot find a guide in this situation, most guides show the ADB pull command, which in my case does not work.
Milind
Click to expand...
Click to collapse
Hmm, what are you planning to do after unlocking the phone? If it's to back up files, I think TWRP automatically mounts your phone storage (it does for me) when plugged in and started up.
Vampir1c said:
Hmm, what are you planning to do after unlocking the phone? If it's to back up files, I think TWRP automatically mounts your phone storage (it does for me) when plugged in and started up.
Click to expand...
Click to collapse
NO there is a specific app from the Govt. in Singapore that is not compatible with my standby Samsung s3. It requires synching my data by blue tooth, which I am not able to do without my e970 touch functionality. Hence need this help:
I need to be able to get into the phone unlock, then enable bluetooth to sync my data to the app.
Hope that explains why I need to get more than data which I also knew long back.
regards.
Milind
try http://forum.xda-developers.com/showthread.php?t=2620456
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.