Database Develop

adb gods I desperately need your help

I bricked my moto x with safestrap. I'm stuck in a boot loop that I can not get out of, nor can I get SS to pop up. The best I can do is get into fastboot and send commands to the phone. I've tried searching but I can't find the commands to pull data from the phone, nor do I know exactly what the path/directory would be where my nandroids are saved.
I have about 3 years of info/apps on this phone that I have been migrating over from phone to phone. It would be a real shame if I had to start over from scratch again over something so dumb. I did everything by the book. I had SS working, I made my nandroid. I created rom slot one and installed. Now bootloop. I never imagined that I would not be able to get back into SS. SS is supposed to be safer than even CWM/TWRP, and as it turns out its the most dangerous thing I've ever used. I have NEVER been put into a situation where I couldn't recover and had to fxz and wipe data. And I've had over 15 android phones.
My issue is that I just don't know the code to extract the data using adb. I can get the phone to reboot when in fastboot using commands on the comp, but thats the extent of my knowledge. Please help.

You obviously didn't search. Try harder. Multiple threads.
Sent from my XT1060 using Tapatalk

1ManWolfePack said:
You obviously didn't search. Try harder. Multiple threads.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Thank you. I am unable to issue commands to the phone through adb. I don't know if its becaues I am doing something wrong or not. I have the commands. They do not work. I'm not sure if the phone can accept adb commands through fastboot. The only way I know out of this is to FXZ, but that wipes the phone and I am trying to use that as a last resort.
The toolkit can reboot the phone and reboot into fastboot, so I assume that adb commands work. However, when I try to use adb it doesn't even show as a device. I'm doing something wrong and need help.
***Edit***
Phone not even showing up in RSD lite. May have to use home comp. This laptop is windows 8.1

Fastboot the system.IMG then move everything to your PC you want to keep then run rsd, or delete the delete user data line in rsd then when running move everything to PC the run full rsd. I've been stuck in this loop many times and you can get the system back but in order to get ss running again your going to have to do a full fxz restore

shane1 said:
Fastboot the system.IMG then move everything to your PC you want to keep then run rsd, or delete the delete user data line in rsd then when running move everything to PC the run full rsd. I've been stuck in this loop many times and you can get the system back but in order to get ss running again your going to have to do a full fxz restore
Click to expand...
Click to collapse
Pm sent!

[email protected] hangouts much easier

shane1 said:
[email protected] hangouts much easier
Click to expand...
Click to collapse
Message sent

Need help unbrick (willing to pay if needed)

I have a VS980:
I rooted and installed twrp recovery.
I triedto install pac_vs980-dev-20140731
I copied it to root of my phone along with the gapps-kk-20140105-signed.zip.
I made a backup of everything on the phone, Then did a full wipe of everything.
I installed the two zips, and it says sucessful. Then goes into a boot loop!
I tried to recover the the backup and it is not found!
IDK what to do it is my girlfriends phone and she is absolutly ripped **** with me. I need serious help to fix this I have no idea what went wrong or how to fix it please help willing to make a paypal payment to anyone who can actually fix this. I was trying a new rom but adb sideload won't load either!
I keep seeing people saying that some commands work for them but when I am in twrp and click advanced and terminal command it loads up what looks like a file browser and I am lost. I seriously need to fix .
I tried the following:
from the TWRP terminal command was to type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
Click to expand...
Click to collapse
But both commands say there's no space left. what should i try now?

I'm new to this phone but can't you just load the phone's SD into the computer in twrp?
That's what I would do with my old phones.

drivenby said:
I'm new to this phone but can't you just load the phone's SD into the computer in twrp?
That's what I would do with my old phones.
Click to expand...
Click to collapse
No this phone doesn't have an SD Card, and the computer isn't seeing the phone at all while plugged in.
I ended up downloading the LG Flash tool and the stock KDZ file it took seconds and completely fixed the phone,
Just had to boot the phone into download mode (Press Volume Up and insert USB cord while phone is off)
and uploaded the KDZ file and all is new, still rooted, but other then that everything is back to full stock.
I don't understand why people don't just make KDZ files for the custom roms! It's much easier!

I know, I meant "mount as USB drive" option in twrp.
They probably need to digitally sign it for a kdz to work , so I don't think they can just "make" a kdz

Have you tried to go back into twrp and wiped the dalvick again. Then tried to reboot.

If all else fails, use the Return To Stock Guide in the general section. What version of Android did you have on the phone before you flashed this? You need to make sure the rom matches the baseband you're using.

[help] got a soft brick after a build.prop edit

A while earlier I was trying to enable tethering on my at&t N6 by editing the build.prop and after the reboot it's stuck in a boot loop. I don't imagine that this is important but it doesn't get to the dots animation; just white Google and the unlock at the bottom. I am still able to get into fastboot and recovery (stock one). I have a backup of the correct build.prop in the /system file named build.prop.back , so I'm hoping that there's a way to revert to that without needing to wipe my device again, but I'm not sure.
I found this thread, however my computer isn't recognizing the device when it's in recovery mode. I have the fastboot drivers installed (needed to root), so that may be why but, again, I'm not sure. the adb devices command shows that there is no device, I imagine because the driver is not installed.
any help would be appreciated. thanks in advance.

Try the ADB & Fastboot installer from this thread - http://forum.xda-developers.com/showthread.php?t=2588979

jj14 said:
Try the ADB & Fastboot installer from this thread - http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Unfortunately that didn't fix the problem.
Do you know if the fastboot driver and recovery driver would be different? As far as I can tell from my research, I think they're the same, but I could be wrong. Hopefully that's the problem and you can direct me towards the correct driver.
If I select "show hidden devices" in the device manager, it shows the phone as ADB Interface, and I tried undating the driver for that but it said it was already up to date. not sure what to do from here.
Thanks for your help.

Install working drivers if you can. This is important on so many levels. If they are installed correctly you type ADB devices, you should see your device. If you do type adb reboot bootloader, it should reboot to bootloader. Type fastboot devices, you should see same device name. Pat self on back.
Once that is all good I'd install the latest TWRP img file for your whale, straight off TWRP website (do you know how to do this? fastboot flash recovery recovery/name.img) . Once you do that go to your new recovery by pushing vol-down twice then your power button, inside TWRP you mount system and go into the file manager inside TWRP and swap/rename build.prop files. At this point, please make a backup inside TWRP. This backup will be on your internal memory, also save a copy to your computer in case you accidentally reformat your internal memory like every noob that uses toolkits. Having a backup is very important when you are screwing around with your phone. Reboot and profit.

jawmail said:
Install working drivers if you can. This is important on so many levels. If they are installed correctly you type ADB devices, you should see your device. If you do type adb reboot bootloader, it should reboot to bootloader. Type fastboot devices, you should see same device name. Pat self on back.
Once that is all good I'd install the latest TWRP img file for your whale, straight off TWRP website (do you know how to do this? fastboot flash recovery recovery/name.img) . Once you do that go to your new recovery by pushing vol-down twice then your power button, inside TWRP you mount system and go into the file manager inside TWRP and swap/rename build.prop files. At this point, please make a backup inside TWRP. This backup will be on your internal memory, also save a copy to your computer in case you accidentally reformat your internal memory like every noob that uses toolkits. Having a backup is very important when you are screwing around with your phone. Reboot and profit.
Click to expand...
Click to collapse
I though I had the working drivers... Whenever I boot into fastboot/ bootloader, I can do fastboot devices and the phone shows up, but for whatever reason adb devices returns an empty list everywhere. It's empty in fastboot and recovery and while the phone is stuck in it's bootloop...
I'm fairly confident I can flash TWRP without any problems. I had an old galxy tab 2 that i flashed cyanogen onto a while ago, however i used clockwork for that recovery. I don't imagine it would be too much different though.
edit: also might be worth noting that I'm using a windows 8.1 computer for this. not sure if it matters or not, but it might be useful

momo5732 said:
I though I had the working drivers... Whenever I boot into fastboot/ bootloader, I can do fastboot devices and the phone shows up, but for whatever reason adb devices returns an empty list everywhere. It's empty in fastboot and recovery and while the phone is stuck in it's bootloop...
I'm fairly confident I can flash TWRP without any problems. I had an old galxy tab 2 that i flashed cyanogen onto a while ago, however i used clockwork for that recovery. I don't imagine it would be too much different though.
edit: also might be worth noting that I'm using a windows 8.1 computer for this. not sure if it matters or not, but it might be useful
Click to expand...
Click to collapse
You are ok w/ your problem because you can get to fastboot screen. Don'y worry about adb drivers for now. Do what I said in my earlier post in the 2nd paragraph, start w/ installing TWRP img then do the rest and it will work for you. Win 8.1 seems to have its difficulties but we'll worry about that later after you get TWRP installled.

jawmail said:
You are ok w/ your problem because you can get to fastboot screen. Don'y worry about adb drivers for now. Do what I said in my earlier post in the 2nd paragraph, start w/ installing TWRP img then do the rest and it will work for you. Win 8.1 seems to have its difficulties but we'll worry about that later after you get TWRP installled.
Click to expand...
Click to collapse
OK. twrp is making a backup as I type. is this backup the same thing as a nandroid backup? i hadnt heard of them before I decided to root.
It should boot properly now. I'll update when it's done.
Edit: IT BOOTS! thank you so much.
Edit 2: So I'm not really sure why it works now but adb recognizes it when its in twrp... odd. I tried to reinstall the drivers with the most recent version i could find, but it didn't look like it actually updated anything. maybe stock recovery was just broken? I'm not sure...

momo5732 said:
OK. twrp is making a backup as I type. is this backup the same thing as a nandroid backup? i hadnt heard of them before I decided to root.
It should boot properly now. I'll update when it's done.
Edit: IT BOOTS! thank you so much.
Edit 2: So I'm not really sure why it works now but adb recognizes it when its in twrp... odd. I tried to reinstall the drivers with the most recent version i could find, but it didn't look like it actually updated anything. maybe stock recovery was just broken? I'm not sure...
Click to expand...
Click to collapse
Cool glad it's working. Yes backup=nandroid
It's cool now I've also noticed the computer recognizes phone in TWRP. You can drag and drop files onto the phone while it's in TWRP not just booted in android, couldn't do that before unless I'm wrong which is often. This is really cool as I always forget a file or two or its location on SD card.

xperia z3c, bricked during restore

Hello!
I had my phone MB replaced during service and before that I got a full TWRP backup, including system and TA.
After I got it back (new MB) i rooted it and restored the full TWRP backup, without thinking too much..
Unfortunately the phone now is hard bricked, only the red light will blink when connected to PC but that's about it. No flashmode or fastboot.
The question is if I can do anything to salvage this phone.. I only have a full TWRP backup (system and TA taken before the MB swap), but I don't know if this can help. Can I try to use S1tool for this, or there is no chance?
any suggestion is welcome, thanks!

correction..
Actually, i did get a full twrp backup before restoring that old backup that crashed the phone. but it is on the phones internal memory, and i have no access anymore.
Assuming that i could get basic adb access to pull that backup out and get a ta.img out of it, or to somehow directly restore the full twrp backup - then it could work by using the s1tool method.
but i dont know if this basic access is possible.. any thoughts? i don't want to disassemble the back if it is hopeless in the first place..

If the phone can't be detected by ADB Access and all other attempts have failed most likely its a hard brick.
There's a great guide on how to recover from problems like such though I cannot guarantee it would work, but its better to try. Click Here
A last resort option would be to send it to Sony

thanks but it is a hard brick in any case, cause i restored a wrong ta (imei, etc). I was hoping to be able to wipe the ta by unlocking the bootloader, via s1tool, but i am not sure this can wipe the ta to the extent that i can reboot the phone or use adb with it. anyone knows?
if i could manage to use adb with it i could pull out the correct ta from the twrp backup in my internal memory and use that to revive the phone, as others have done.. but it seems like a long shot.
also if anyone has any info on where the test point is for this device..
thanks

Help I accidentally wiped everything

So, I really messed up. Instead of doing a factory reset, I wiped everything. I have no backup. The only thing I can do is load up twrp and wish I had a ROM to try to flash. My computer won't recognize I have my phone connected.

You can either load a rom on usb otg drive or fix your computer issue (most likely driver related, but also could be a bad port or cable).
Sent from my XT1254 using XDA-Developers mobile app

Schumplerton said:
So, I really messed up. Instead of doing a factory reset, I wiped everything. I have no backup. The only thing I can do is load up twrp and wish I had a ROM to try to flash. My computer won't recognize I have my phone connected.
Click to expand...
Click to collapse
What do you mean when you say your computer won't recognize it? Does it do absolutely nothing when you plug it in, or does it show up as an "unrecognized device" or something like that?
If it shows up as unrecognized, it might be as easy as needing the right driver. Download this and install it to get that: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481.
TWRP supports MTP, so you should be able to just boot into TWRP, plug your phone into your PC, copy and paste whatever ROM you want to it, and flash it.
If you can't get that to work for whatever reason, you can flash back to stock by following section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
No, it will not re-lock your bootloader.

For some reason TWRP wouldn't show up as a mtp device nor could I sideload a rom file so I just restored to stock and will start over. Thanks for the suggestions!

Schumplerton said:
For some reason TWRP wouldn't show up as a mtp device nor could I sideload a rom file so I just restored to stock and will start over. Thanks for the suggestions!
Click to expand...
Click to collapse
how can I restore to stock and start over?????? please give me like a very detailed step-by-step instruction, this makes day 3 with no phone and its about to make me crazy. i accidentally wiped the system in TWRP.... idk what to do please please please help me?????

[email protected] said:
how can I restore to stock and start over?????? please give me like a very detailed step-by-step instruction, this makes day 3 with no phone and its about to make me crazy. i accidentally wiped the system in TWRP.... idk what to do please please please help me?????
Click to expand...
Click to collapse
Follow section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
Skip steps 1-3. Those only matter if your bootloader is locked. Since you have TWRP, I'm assuming that it isn't.