Database Users

Help! Connecting thru USB, but not able to flash anything

Brand new phone...can't believe i did something wrong only a few hours into it!?
To cut to it, i am not able to run anything on my PC to my Atrix bc the phone is not visible to it via usb sync. It DOES still see it if i needed to transfer files etc, just not so i can flash anything to it off the PC.
And not sure if it has anything to do with it, but it seems like i ran into my problem when i inserted and formatted my SD card. Here's what i did (and i hadn't gotten very far):
I rooted with SuperOneClick, then I installed DG's Adeo ROM and the update.
I was trying to install Gingerbread and was just putting busybox installer on my phone when i went to put my SD card in there from my old phone. i formatted the card and it seemed after i did that i lost connectivity via the USB. It could still access the phone, but everytime i run ATRIX4G_MobileTV_GBTheme.bat it hangs at "daemon started succesfully" . It also hangs if i try to run SuperOneClick again on "waiting for device."
I wasn't sure what to do to get it running right again so i did a full wipe from the settings. Still can't connect
Any help be greatly appreciated. i've literally had this phone 4 hours so sorry if i'm missing something dumb

Try running aRoot (search this forum) and then trying all that.

thanks for that suggestion, gonna try that....just as soon as the damn search function comes back!!
oh the waiting...i am not going to be able to sleep tonight till i get somethin happenin

No need to search, it's only hanging about 3-5 posts down in this section. It's also here:
http://forum.xda-developers.com/showthread.php?t=981866

Ran aRoot - seems to run through the steps without a failure, but it went VERY fast, like 3 seconds...and it hangs when i try to "unroot"
so, all in all it seems like its still not recognizing the phone as before when connected through USB

Dillsnik said:
Ran aRoot - seems to run through the steps without a failure, but it went VERY fast, like 3 seconds...and it hangs when i try to "unroot"
so, all in all it seems like its still not recognizing the phone as before when connected through USB
Click to expand...
Click to collapse
Do you have Root Explorer? If so, look in /sbin and see if you have 'adbd' showing
OR
Have you tried installing the ADB interface from the Android SDK? See if your device can be seen? If not see THIS ARTICLE (external link to addictivetips) on setting up ADB.

No, I don't have Root Explorer
I installed SDK and ADB and it does show up, but only when the USB setting is set to "Motorola phone portal." None of the other options it shows up in device mgr.

I am kinda stabbing in the dark at this point...thinking maybe it's a driver issue?
maybe if i uninstall all the drivers and start from scratch i might have some luck? i actually did unistall all the drivers thru device mgr, but they just came right back next time i connected...so maybe i need to delete them entirely?
any suggestions to trouble shoot this greatly appreciated...i know it's probably small potatos but i'm really jammed up here...

Moved as not android development

Have you tried installing the latest drivers again directly from the Motorola Mobility site? You can install Media Link or just the drivers with MotoHelper. For some reason my phone installed all of this, but there were updates available immediately.
The ADB interface should function when USB is set to None.
Sent from my Rooted Atrix using Tapatalk Pro

Yeah i actually did a system restore and reinstalled all the drivers etc.
I can see the phone now in the device mgr under ADB interface when connection is set to "None" for USB
But still hangs when trying to flash basically anything

Do you have or can you pick up a Terminal Emulator in the Market and list the files in /sbin? See if you have adbd...
From $
su
cd /sbin
ls (Lower case L, not 1)
Look through list of files for adbd.
Sent from my Rooted Atrix using Tapatalk Pro

OK, No it's not in there

See this post here: http://forum.xda-developers.com/showpost.php?p=11738847&postcount=1 and the cooresponding thread for replacing adbd. There's another post in the thread about changing the permissions so that it doesn't get lost again with a reboot. You might have to purchase Root Explorer since you cannot push anything via ADB over USB.
Sent from my Rooted Atrix using Tapatalk Pro

This seems to be the type of problem i am having, very much thanks for directing me to that other thread.
At this point i have copied ADB to the sbin folder but nothing flashing yet...need to read through that thread more and play with it.
What a PITA so far but thanks so much for the help!

No problem. I hope it works out. If you don't mind, post up and let me know if you get it going and what it took so we can try to help others.
Sent from my Rooted Atrix using Tapatalk Pro

[Q] Re-sizing Partitions

I use my Nook Touch for reading only. I do not need it to access the internet or download apps. From my understanding, these are the main reasons to root one's Nook.
What I am interested in is gaining access to that 1.5 GB or so of internal memory. As the majority of my books are side loaded, it makes much more sense to have 1.5 GB available to me and only 240 MB for B&N downloadable content.
My first question is, if I am going to try to re-size some partitions and I have no interest in apps, which rooter is the simplest for v1.1? SalsichaNooter or TouchNooter?
And finally, I have searched the forum and there are a couple of threads about re-sizing partitions, but they all involve linux terminal work. I think I might be able to figure it out, but could a linux disk partition program (like gparted) be used instead?

Ok, I found a thread posted by ros87 here that details how to go about resizing the partitions. It was very helpful, however, after rebooting back into my Nook, I am no longer able to connect to the internet.
I am not sure if either the sdb6, sdb7, or sdb8 partitions have any connection to wireless internet, but I noticed during the step of:
#mount /dev/sdb8 tmpdata
Click to expand...
Click to collapse
I got some socket warnings relating to a wireless file. ros87 says to ignore the socket warnings, which I did. Then at this step:
#tar xf tmpdata.tar tmpdata
Click to expand...
Click to collapse
I got a whole bunch of errors about unable to write files. But when I checked the drive, it seemed that all the folders copied over okay, so I continued on through the steps.
I probably should have copied the error output, but after discovering that wireless isn't working (it says "Unable to Connect"), I'm thinking maybe something didn't copy over correctly.
Should I try deleting and copying over the tmpdata.tar again?

Go trough dmesg and logcat (in adb shell) to see if you can find any troubles about your wifi connectivity, then post it here, but not the complete logs please!
As for my posted setup, I ran it for several weeks, with wifi enabled, without any troubles at all.
The socket errors is not the problem. A socket cannot be copied, and it is recreated whenever the socket service is started.
-R

Can I use adb if my Nook isn't rooted? As in, would I be fine just using noogie? I won't be able to try this until I get home.
Edit: Found this. I'm not interested in apps and such, so this seems the best option for me. Will post the dmesg and logcat later.

Okay, so I restored my backup image and checked the wi-fi. That is coming up as "Unsuccessfull", too. So maybe the problem is my wifi setup? My ipod connects fine, so I'm not sure what the problem is.
Just for future knowledge, is it safe to erase and de-register the device with different sized partitions?

Could this be a virus?

I left my TPT unattended for two days on.
When I've tried to use it again I got a message that Encryption did not end correctly to make a reset to original values.
This was strange and because recovery was not working I did tried that step as well without success.
Due to low battery, I manage to access settings and came to realize that there are strange certificates install like TURKTRUST Digital Certificate which I came to realize is reported to be a virus http://eromang.zataz.com/2013/01/04/fraudulent-turktrust-digital-certificat-used-in-active-attacks/
In recovery I see that I cannot mount the internal SD or data. I can connect trough ADB but I'm not an expert able to use it properlly.
Any ideas on how to recover my TPT?
Thanks in anticipation.
EDIT:using adb I manage to get the catlog ...hope someone is expert enough to go around this problem.
I only need to format / mount SDCard and data which is blocked now ...

[Q] Backup from TWRP with USB

I've managed to softbrick my nexus 10 by trying to disable extra services (was getting about 1.5 hours battery life with media services running the processor 100% all the time). It worked wonderfully (no negative side effects, went back to 10+ hours with the screen on, or days on standby) until I reboot it and now it won't load past the moving colors (Android 4.4.3, unlocked and all that).
I have TWRP, I was hoping to backup everything possible via usb, but it seems it's incapable of doing so. ADB backup can't be done using TWRP since there's no unlock function (reaaal useful there, recovery mode that doesn't support backups) and adb pull fails if I try to pull everything since there are files and folders with invalid file names (who puts ":" in folder names? they should be shot), and I don't know specifically what to pull, I was just going to get everything put back what I found was missing that I needed. There's no room to do a backup onto the device, and since the N10 has to sd/microsd, well... Useless options are useless.
Is there anyway to just do a proper backup with TWRP over USB? Or is the "recovery" mode as useless as I think it is when it comes to backups? (I'm aware I can get the tablet back to working order if I disregard the data on it, this is a question about backing things up before doing so)
Edit: Also, I have a pro version of SkipSoft ToolKit, but unless you can actually load into the OS the toolkit can't do anything at all.
Just really frustrated with the lack of doing something as basic as copying files from one place to another. Been messing with this all morning.

Diet6 said:
I've managed to softbrick my nexus 10 by trying to disable extra services (was getting about 1.5 hours battery life with media services running the processor 100% all the time). It worked wonderfully (no negative side effects, went back to 10+ hours with the screen on, or days on standby) until I reboot it and now it won't load past the moving colors (Android 4.4.3, unlocked and all that).
I have TWRP, I was hoping to backup everything possible via usb, but it seems it's incapable of doing so. ADB backup can't be done using TWRP since there's no unlock function (reaaal useful there, recovery mode that doesn't support backups) and adb pull fails if I try to pull everything since there are files and folders with invalid file names (who puts ":" in folder names? they should be shot), and I don't know specifically what to pull, I was just going to get everything put back what I found was missing that I needed. There's no room to do a backup onto the device, and since the N10 has to sd/microsd, well... Useless options are useless.
Is there anyway to just do a proper backup with TWRP over USB? Or is the "recovery" mode as useless as I think it is when it comes to backups? (I'm aware I can get the tablet back to working order if I disregard the data on it, this is a question about backing things up before doing so)
Edit: Also, I have a pro version of SkipSoft ToolKit, but unless you can actually load into the OS the toolkit can't do anything at all.
Just really frustrated with the lack of doing something as basic as copying files from one place to another. Been messing with this all morning.
Click to expand...
Click to collapse
Do you still need help? What about mtp mounting? You can pull * for a whole folder
Why not adb sideload a new rom?

I don't think I can MTP mount a Nexus 10, at least not in recovery mode. What I ended up doing was buying a OTG usb drive and making a backup to that. Problem was it split the tar over 4 files, which corrupted them (or at least made them not work with 7zip or tartool) fortunately I was able to get them to work with cygwin enough to get the files I wanted. I didn't want to sideload a new rom until I had backed up certain application data just in case it removed it.
All in all, had to buy a OTG usb drive (I would have just bought a cable but all the stores around here had was this "Dane 16gb OTG drive". So 20 bucks later I had the files I needed. Still annoyed that you can't do a ADB backup from fastboot or recovery mode, it seems like those would be the best places because no system files are in use, but who knows maybe the developers know something I don't.
In summary:
TWRP recovery cannot confirm a ADB backup over USB. ADB backups can only be done from the operating system.
TWRP recovery mode can only backup to OTG (if your device supports it, Nexus 10 does), but if the backup is larger than 2gb it will split the file and you will need some form of linux to extract it.
ADB cannot copy every file in recovery mode over USB due to certain file names being invalid for NTFS (this is probably not a problem on other file system types), this is problematic since the "pull" command has no skip option, it just fails when it hits one of these files.

Well you can easily flash latest rwrp that does well on my Linux mount internal storage but another solution is just flashing a rom with abd sideload and the'the back up from pc the content
---------- Post added at 04:24 AM ---------- Previous post was at 04:23 AM ----------
Or that will just un brick your tablet

Diet6 said:
Still annoyed that you can't do a ADB backup from fastboot or recovery mode
Click to expand...
Click to collapse
adb doesn't work in fastboot mode, only recovery or Android itself.
Diet6 said:
In summary:
TWRP recovery cannot confirm a ADB backup over USB. ADB backups can only be done from the operating system.
Click to expand...
Click to collapse
Maybe because /data (not talking about /data/media) wasn't mounted?
Diet6 said:
TWRP recovery mode can only backup to OTG
Click to expand...
Click to collapse
Huh?
Diet6 said:
ADB cannot copy every file in recovery mode over USB due to certain file names being invalid for NTFS (this is probably not a problem on other file system types), this is problematic since the "pull" command has no skip option, it just fails when it hits one of these files.
Click to expand...
Click to collapse
That's NTFS' problem, not TWRP's.

beekay201 said:
1. adb doesn't work in fastboot mode, only recovery or Android itself.
2. Maybe because /data (not talking about /data/media) wasn't mounted?
3. Huh?
4. That's NTFS' problem, not TWRP's.
Click to expand...
Click to collapse
1. I was just covering that you can't actually do a ADB backup unless you have access to android OS, in case anyone else came across this. (I didn't know when I started, and it took awhile to find it said concretely anywhere)
2. I made sure everything was mounted, the issue is when you send a backup command over ADB it says the "Now unlock your device and confirm the backup operation" message in terminal which you can't do from recovery mode on the device, thus you cannot do a ADB backup command over TWRP (or other recovery modes I'd imagine).
3. I should have been more specific. TWRP can do a backup to the device itself (built in storage), SD card (if your device has one and you mount it), or a OTG (on the go) device via usb directly to media like a flash drive. It cannot issue a backup over USB to a computer.
4. Completely agree it's a NTFS issue, but it could be mostly avoided by allowing files that error to be skipped or renamed rather than terminating the process. (I understand that's on the android devs since pull is made by them, and I doubt they would care to improve the command for a file system I doubt they use). Again I mostly included that so if anyone else is trying to figure it out they can stop looking for "a way" and just accept it can't be done.
Ultimately Khaon is right in that sideloading a rom would have unbricked it and I could have done the ADB backup then, I just wasn't sure how that might affect the app data storage so I was looking for a way to back it up before doing that.

Diet6 said:
1. I was just covering that you can't actually do a ADB backup unless you have access to android OS, in case anyone else came across this. (I didn't know when I started, and it took awhile to find it said concretely anywhere)
2. I made sure everything was mounted, the issue is when you send a backup command over ADB it says the "Now unlock your device and confirm the backup operation" message in terminal which you can't do from recovery mode on the device, thus you cannot do a ADB backup command over TWRP (or other recovery modes I'd imagine).
3. I should have been more specific. TWRP can do a backup to the device itself (built in storage), SD card (if your device has one and you mount it), or a OTG (on the go) device via usb directly to media like a flash drive. It cannot issue a backup over USB to a computer.
4. Completely agree it's a NTFS issue, but it could be mostly avoided by allowing files that error to be skipped or renamed rather than terminating the process. (I understand that's on the android devs since pull is made by them, and I doubt they would care to improve the command for a file system I doubt they use). Again I mostly included that so if anyone else is trying to figure it out they can stop looking for "a way" and just accept it can't be done.
Ultimately Khaon is right in that sideloading a rom would have unbricked it and I could have done the ADB backup then, I just wasn't sure how that might affect the app data storage so I was looking for a way to back it up before doing that.
Click to expand...
Click to collapse
I'd just 'tar' what I wanted on the device and then pull that with adb.

Yeah, I just had no idea what I wanted. I'm not 100% familiar with how the system stores application data, I figured if I copy everything than anything I "miss" after I formated it I'll be able to just research where it was and dig in the backup and pull it out.

Yeah adb sideload a rom will only affect system partition thus your data would not have been modified in any way. So you are done with your issue?
Sent from my Xiaomi MI2s

Khaon said:
Yeah adb sideload a rom will only affect system partition thus your data would not have been modified in any way. So you are done with your issue?
Sent from my Xiaomi MI2s
Click to expand...
Click to collapse
Yes, sorry for the slow reply. I've completed my update, just wanted to follow up on everything I did incase the information is useful for anyone else new to this like I am.

Boot troubleshooting

After working without a glitch for four years, my Nexus 7 (grouper) got stuck in a bootloop after I started it today. Thinking that something is probably wrong with cashe or dalvik cache I've cleared them. Now the bootloop is gone, but the device gets stuck on "Starting apps" after it finishes "optimizing" (filling in the dalvik cache). I would like to see what's going on but I have a problem doing that.
The problem is that I can't get the logcat to do the job. I've tried two "solutions" that seemed obvious, but (for some reason), none of them works.
First "solution": make a simple script and put it in /system/etc/init.d/:
#!/system/bin/sh
logcat > /sdcard/log.txt (set to 755)
I get the file, but even if I leave "Starting apps" to run for some time, when I turn off the tablet and look at the file it only has 65 lines and it still didn't finish initializing the hardware part. No information about started apps or anything. I can retrieve dmesg log from recovery but nothing interesting there as well.
Second "solution": I've tried to make it work trough init.rc, by following this https://stackoverflow.com/questions/17406209/enabling-logcat-in-init-rc (switched /cache/ to /sdcard/). But this also produces no results. Txt file is not generated at all
I don't know what I'm doing wrong.
I don't want to do a factory reset unless absolutely necessary (bunch of games with save files and other apps as well).
I can't do logcat trough adb since device is "unauthorized".
Any help is appreciated.
Thx in advance!
P.S. Using OmniROM (4.4.4)

Boot into TWRP and see if you can create or edit a text file. Reboot back into TWRP again and see if the change you made is still there. If it isn't, your flash memory has gone bad and you are in read only mode. This cant be fixed without a new motherboard. Hopefully this is not your issue.
Sent from my LGLS992 using Tapatalk

Sorry for the late reply, I was on vacation and I left the tablet at home.
The script I've mentioned was inserted trough TWRP so I think this confirms that you can write.
Also there is a log file created, as I've mentioned, it's just super short (I guess if it's in read-only mode there would be no output).