Database Develop

Clockwork recovery...

Does anyone know an easier way to put clockwork onto my phone? I mean other than (adb).. for some reason it doesn't pick up my phone.. Is there an recovery App coming out soon?
Sent from my LG-P925 using xda premium

make sure you have debugging mode on and that your Windows or Mac proper LG drivers are installed so that the phone is recognized also put CMD in the same folder as platform tools in sdk manager folder vice versa for files needed to be pushed to phone.

I got the drivers from the LG website for my cell, hmmm... ill have to recheck everything else because ADB has never gave me this much trouble
Sent from my LG-P925 using xda premium

I'd be willing to code a one click solution if it would be helpful. Its pretty easy as it is tho
Sent from my LG-P925 using xda premium

I had the same problems. I followed everything step by step and made sure I had the right drivers along with everything I would need with Java. Still no luck. I have the combination of feeling stupid and frustrated. I have rooted and installed custom roms on three different phones before.
A one click solution would be amazing if you could come up with that. I will try the ADB way again later.
Vince

Yes a one click, alot of people would thank you ....and i would be gratefull
Sent from my A500 using xda premium

i agree. ive been trying the adb method all day. for some reason just wont work. im prolly missing something

Try updating all the drivers for adb. It would be helpful for you and it would probably solve your issue.
Sent from my LG Thrill 3D using XDA Premium

Does one click root work for you? If it does, there is nothing wrong with your drivers.
Once you get one click root working, put the recover in the ADB folder that is part of one clock root.... then open that fold, hold shift and right click, select open command prompt, then type in the adb commands from the CWM instructions thread.
LG uses the same drivers for all their Android devices, I used their driver installer app and selected the Verizon LG Fathom since it didn't have the Thrill listed anywhere, have had no problems.

Some reason my comp doesnt do any of this correctly... so much for brand new tech

Does one click root work for you?
If not, you have a driver problem, fix it by downloading LG's driver installer, select Verizon for the carrier and then select the Fathom. If you have a drive issue, and that fails to fix it, try a different USB port... make sure you have your phone in debug mode... can you mount your SD cards?
If one click root does work, then YOU, not your new technology, is doing something wrong. So the question is, what are you doing wrong...
Please answer the question, does one click root work? From there, tell us step by step what you are doing, and we will tell you what needs fixing.

almost done
pjcforpres said:
Does one click root work for you? If it does, there is nothing wrong with your drivers.
Once you get one click root working, put the recover in the ADB folder that is part of one clock root.... then open that fold, hold shift and right click, select open command prompt, then type in the adb commands from the CWM instructions thread.
LG uses the same drivers for all their Android devices, I used their driver installer app and selected the Verizon LG Fathom since it didn't have the Thrill listed anywhere, have had no problems.
Click to expand...
Click to collapse
i put recovery in the adb folder, get all the way through the adb process and it says img can not be found? lol wtf

Did one click root work for you?

installed the fathom drivers, my iphoney 4, or my htc inspire was never this hard to work with

one click is the way i rooted my phone

robertmoore208 said:
one click is the way i rooted my phone
Click to expand...
Click to collapse
Ok, then driver issues isn't a problem, I would take a really close look at your ADB commands, and be sure to wait 30 seconds after each one to let it process.
I would recommend copy pasting the longer commands (right click copy, right click paste, the keyboard shortcuts don't work in command prompt window).

now it says permission denied on first command?

Then you don't have root... run one click root again. I would use it's driver check feature as well before running it.

lol i lost root? wow ok strange... i have superuser

Well... if you get accessed denied you either are typing something wrong, skipping a step, or trying to do something that needs root and you don't have root.
Do you have debug mode turned on? Do you see this active in your phones notification bar? That first line doesn't even need root access, if IIRC.

[Q] How would you root? I'm on day FOUR of unsuccessful attempts

It started here:
http://forum.xda-developers.com/showthread.php?t=2530605
I followed this post.
http://forum.xda-developers.com/showthread.php?t=2509676
Got nowhere because of the puttytel window timeout problem.
Related to this post was this post:
http://forum.xda-developers.com/showthread.php?p=47749358#post47749358
I have an unlocked bootloader on Moto X from sprint. I just need the easiest way to root.
This looked confusing. http://forum.xda-developers.com/showthread.php?t=2536200. Gotta be another way.
Have considered restoring to stock and taking the dang thing back http://atsgadgets.com/how-to-restor...lite-att-t-mobile-sprint-verizon-us-cellular/. So frustrated.
I've offered paypal to those who can do it successfully. I am so burnt out on trying to make this work. This PITA is not worth android. I have a one click jailbroken phone now. And I have successfully rooted and installed custom roms before but this is totally out of hand how complex this is for me. Maybe I'm just remedial but it seems several are having trouble with this model. For open source, this should not be this tough.
/rant. Almost ready to throw in the towel, but still listening.....
Sorry for the multiple posts. Just trying to get some new opinions. HTC Evo 4 g was done in 10 minutes. This has taken 4 days.
:crying:

bullpen7979 said:
I have an unlocked bootloader on Moto X from sprint. I just need the easiest way to root.
This looked confusing. http://forum.xda-developers.com/showthread.php?t=2536200. Gotta be another way.
Have considered restoring to stock and taking the dang thing back http://atsgadgets.com/how-to-restor...lite-att-t-mobile-sprint-verizon-us-cellular/. So frustrated.
I've offered paypal to those who can do it successfully. I am so burnt out on trying to make this work. This PITA is not worth android. I have a one click jailbroken phone now. And I have successfully rooted and installed custom roms before but this is totally out of hand how complex this is for me. Maybe I'm just remedial but it seems several are having trouble with this model. For open source, this should not be this tough.
/rant. Almost ready to throw in the towel, but still listening.....
Sorry for the multiple posts. Just trying to get some new opinions. HTC Evo 4 g was done in 10 minutes. This has taken 4 days.
:crying:
Click to expand...
Click to collapse
Are you on 4.4 and what computer OS are you using?

I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.

bullpen7979 said:
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
Click to expand...
Click to collapse
Here, go into Settings -> About Phone and tell me what your Build Number is (at the very bottom).

Do not put in the cmd window mfastboot, just try fastboot flash recovery twrp 2.6.3.1-ghost-4.4.img. Now also put the recovery image in the same folder as fast boot, I believe its SDK tools folder
Sent on my Moto X

bullpen7979 said:
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
Click to expand...
Click to collapse
The method that you thought was confusing, is the one you should use. If I have time, I could try helping you with it.

ALU0506, the build number is 13.9.0Q2.X-116-MX-17-57-1. Thanks everyone for your help.

I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great

bullpen7979 said:
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
Click to expand...
Click to collapse
I can try helping over gtalk.

bullpen7979 said:
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
Click to expand...
Click to collapse
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?

I will try that as soon as I can and get back to you. I have two computers one at my hotel and one here. I'm not sure I have the ADB tools on my netbook
Sent from my XT1056 using xda app-developers app

bullpen7979 said:
I will try that as soon as I can and get back to you. I have two computers one at my hotel and one here. I'm not sure I have the ADB tools on my netbook
Sent from my XT1056 using xda app-developers app
Click to expand...
Click to collapse
if you are still looking for help i can help you get this done on gtalk as well. send me a pm with your username. it will take virtually no time at all

jayboyyyy said:
if you are still looking for help i can help you get this done on gtalk as well. send me a pm with your username. it will take virtually no time at all
Click to expand...
Click to collapse
especially since he already unlocked the bootloader. Just flash recovery, then flash supersu.zip.

aooga said:
especially since he already unlocked the bootloader. Just flash recovery, then flash supersu.zip.
Click to expand...
Click to collapse
ya during his four days of misery, he could have just read for 1 hour on the stuff so it would seem confusing anymore and then he would have had a rooted phone. But either way, his problem is solvable with a few simple instructions.

OK Jay/Aooga.
Finally back from work.
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
open cmd window, typed adb reboot bootloader, and got:
T063202TFL and fastboot, and then a prompt.

OK Jay/Aooga.
Finally back from work.
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
open cmd window, typed adb reboot bootloader, and got:
T063202TFL and fastboot, and then a prompt.
Phone is in fastboot mode with white, yellow green text.
Device is unlocked. Status code 3.
Battery OK Charging
Transfer mode USB connected.
It looked as though I had to be able to accept the 4.4 kitkat OTA in order to get this done. but when i went to the usual spot to look for system updates it said there were none available.
Anyhow, I am super grateful for your help. Sorry to be such a remedial doofus

Looks like we can wait till tomorrow. Or today. Or whatever timeline it is.

adb and rooting issues

so i am trying to root using this io method i believe it is called i thought i had adb installed but it seems as though it is not. i have tried using a few methods here on xda none seem to work restarted pc several times as well as phone run adb devices and my devices isn't there in fact i got invalid command or whatever. ran the root tool same thing happend yes i am usb debugging enabled, ethernet mode. does anyone have a good guide to get adb to install correctly on windows 8.1 nothing

Bfitz26 said:
so i am trying to root using this io method i believe it is called i thought i had adb installed but it seems as though it is not. i have tried using a few methods here on xda none seem to work restarted pc several times as well as phone run adb devices and my devices isn't there in fact i got invalid command or whatever. ran the root tool same thing happend yes i am usb debugging enabled, ethernet mode. does anyone have a good guide to get adb to install correctly on windows 8.1 nothing
Click to expand...
Click to collapse
ok well i got adb working showed device but when i run root script it says push any key to continue i click it and it says not a valid command or something and exits? not sure what the deal is here a little frustrating i am a bit confused why i haven't seen this talked about any where?

Bfitz26 said:
ok well i got adb working showed device but when i run root script it says push any key to continue i click it and it says not a valid command or something and exits? not sure what the deal is here a little frustrating i am a bit confused why i haven't seen this talked about any where?
Click to expand...
Click to collapse
What exactly did it say?

TheOriginalKyle said:
What exactly did it say?
Click to expand...
Click to collapse
thanks anyway i got it so my questions at this point are: our bootloader is locked on 12b right and is that just stopping us from kernels? last time i remember a locked bootloader you needed a safestrap to flash anything so i am a bit baffled. 2 best way to get custom recovcery what is the best least issues and most compatiable, i have seen some failed efs partitions causing bricks and can we flash any rom placed here in the developement section on any softwasre version with any recovery.thanks for any and all help anyone can give. i have searched the forums just keep getting mixed awnsers to my questions just want to make sure i am doing the right thing.

Bfitz26 said:
thanks anyway i got it so my questions at this point are: our bootloader is locked on 12b right and is that just stopping us from kernels? last time i remember a locked bootloader you needed a safestrap to flash anything so i am a bit baffled. 2 best way to get custom recovcery what is the best least issues and most compatiable, i have seen some failed efs partitions causing bricks and can we flash any rom placed here in the developement section on any softwasre version with any recovery.thanks for any and all help anyone can give. i have searched the forums just keep getting mixed awnsers to my questions just want to make sure i am doing the right thing.
Click to expand...
Click to collapse
1. I believe our bootloader is locked, I don't think safe strap is necessary just make a backup before you flash anything too risky
2. For the custom recovery this method seems to work the best http://forum.xda-developers.com/showthread.php?t=2449670 it also explains #1 better. You can also flash Clockwork Recovery the difference is mainly personal preference. To get the latest TWRP on you'll need to flash the .img then when it's all set up flash the .zip.
3. For the failed efs partitions here's a link to back that up (I had no idea that was a problem). http://forum.xda-developers.com/showthread.php?t=2451390 I only used this when I flashed a different radio, also the only brick that I know of is with FreeGee on 12b but that's the lazy way and who knows maybe he fixed it.
4. ROM's will usually tell you what is compatible and what isn't, if you have the latest TWRP or CRP you should be fine on 12b just read the instructions and scan the comments for issues.
Glad I could help

Thanks!
Sent from my VS980 4G using Tapatalk

Adb now working on chrome OS. Can I run M now?

It's been quite a while since the days of rootif and such for me. I haven't had a windows machine for many years now. I'm still not interested in rooting and roming. But I would like to try the latest update even if it has bugs. Is adb and some instructions all I need to push the update?

Yes that should work, ADB push the download. I'll have to try ADB on my Chromebook now.

All the instructions I see say to have fastboot. Is this necessary? But I remember adb being all you need back in the day I think.
If you manage to get it working hook me up with instructions. Don't know all the file locations or exact commands specific to chrome OS.

rican408 said:
All the instructions I see say to have fastboot. Is this necessary? But I remember adb being all you need back in the day I think.
If you manage to get it working hook me up with instructions. Don't know all the file locations or exact commands specific to chrome OS.
Click to expand...
Click to collapse
Yes, you have to use fastboot. And you'll need to unlock your bootloader.

If have adb should have fastboot. They in the same tools package. ADB works in OS. Fastboot works in bootloader. They are together but have separate uses.

Thank you I was very confused about that. Thought fastboot was a whole other program.

rican408 said:
Thank you I was very confused about that. Thought fastboot was a whole other program.
Click to expand...
Click to collapse
Same package. Just the starting command is either adb or fastboot. To tell if working type "adb devices" in OS or "fastboot devices" in bootloader. In either instance should show your device ID number. Neither will see device in the wrong device mode. If see waiting on device either in wrong mode or or path to tools is wrong.

In case anyone is wondering, this is what I'm using
https://chrome.google.com/webstore/detail/adb-for-chrome/njhehnieenekbompacofnhlljnobgcga?hl=en

rican408 said:
In case anyone is wondering, this is what I'm using
https://chrome.google.com/webstore/detail/adb-for-chrome/njhehnieenekbompacofnhlljnobgcga?hl=en
Click to expand...
Click to collapse
If it doesn't enable fastboot don't help a lot.

How to manually apply OTA?

Full stock LVY48H on Fi . I've been wanting to go Marshmallow, but Google hasn't gotten around to sending me the OTA. I found this thread in the General forum and downloaded the appropriate .ZIP, but the contents don't look a bit like the ROM downloads, so fastboot doesn't appear to be an option. How do I put it on?

Download factory image, extract, flash each img file separately except for userdata.

Mostlyhrmlss said:
Full stock LVY48H on Fi . I've been wanting to go Marshmallow, but Google hasn't gotten around to sending me the OTA. I found this thread in the General forum and downloaded the appropriate .ZIP, but the contents don't look a bit like the ROM downloads, so fastboot doesn't appear to be an option. How do I put it on?
Click to expand...
Click to collapse
If your bootloader is unlocked, you can flash it manually in ABD or use that toolkit (for factory image). I did that but it it also wiped my phone, which was fine by me, it needed a good cleaning after flashing updates to another custom 5.1.1 rom over and over again!

@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
@Tower1972: Attached is a screenshot of the contents of the ZIP. How would I go about flashing that with ADB?

Mostlyhrmlss said:
@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
Click to expand...
Click to collapse
RTFM

Tower1972 said:
If your bootloader is unlocked, you can flash it manually in ABD or use that toolkit (for factory image). I did that but it it also wiped my phone, which was fine by me, it needed a good cleaning after flashing updates to another custom 5.1.1 rom over and over again!
Click to expand...
Click to collapse
when youre giving advice to someone, make sure that its correct. you dont flash anything with adb, you use fastboot. fastboot is different than adb.

@boomerbubba: FTFY: Here's a guide on how to do that. I prefer civility when applicable; my sympathies for whatever is going on in your life to make you want to answer in such a way.
@simms22: Turns out the advice was correct: "adb sideload [OTA file].zip" is the appropriate command to accomplish what I'm after here.
Some strategic Googling found me the answer while I was awaiting responses, here it is for the benefit of anyone who should have the same question. Prollyshooda done that first.

Mostlyhrmlss said:
@boomerbubba: FTFY: Here's a guide on how to do that. I prefer civility when applicable; my sympathies for whatever is going on in your life to make you want to answer in such a way.
@simms22: Turns out the advice was correct: "adb sideload [OTA file].zip" is the appropriate command to accomplish what I'm after here.
Some strategic Googling found me the answer while I was awaiting responses, here it is for the benefit of anyone who should have the same question. Prollyshooda done that first.
Click to expand...
Click to collapse
actually, you were incorrect. you said use adb to manually flash. now you said adb for adb sideload. those are two completely different things. all adb sideload does is move a file from your computer to your phone.
edit.. now you are right, i read your response wrong :angel:

Contrition on the Internet? Whodathunkit! We should get together for a beer, I like your kind of folk.

Mostlyhrmlss said:
Contrition on the Internet? Whodathunkit! We should get together for a beer, I like your kind of folk.
Click to expand...
Click to collapse
contrition is one of the things that pull me down. but its honesty, and the truth. so i stay with it

Mostlyhrmlss said:
@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
@Tower1972: Attached is a screenshot of the contents of the ZIP. How would I go about flashing that with ADB?
Click to expand...
Click to collapse
I don't know what zip file that is, but it's not a factory image from Google. If you download a factory image from Google, you extract every img file and flash using fastboot.
What is everyone's fascination with adb sideload?

nhizzat said:
What is everyone's fascination with adb sideload?
Click to expand...
Click to collapse
It doesn't require an unlocked bootloader. Which for the people that haven't done that, it wipes your phone as part of the unlock process.
Also, it is a smaller download if you are on an ISP with limited bandwidth.

Google says....
http://https://developers.google.com/android/nexus/images
That will get you going, but since the included script won't work, you have to unzip the zip package, what you will find inside the parent folder. Happy flashing

nhizzat said:
I don't know what zip file that is, but it's not a factory image from Google. If you download a factory image from Google, you extract every img file and flash using fastboot.
What is everyone's fascination with adb sideload?
Click to expand...
Click to collapse
That ZIP is an OTA downloaded from the thread referenced in my original post. My fascination with adb sideload (now that I know what it is) is that I can accomplish an upgrade with a single command, which suits my advanced case of laziness very well . Seems much easier than unzipping a file, then unzipping a file from that file (more than doubling the storage requirement, I have a rather small SSD) and issuing several fastboot commands with slightly different syntaxes and hoping I didn't miss (or mistype) something.
I already know how to do a full flash, I unlocked the bootloader and did so first thing when I bought it used to make sure it was cleared of the previous owner's data and completely up-to-date. What I wasn't sure of is if it would be safe to do so for a full version jump. I'm much more comfortable with OTAs since I've applied several and it stands to reason that a carrier would never issue one if it might cause an undue number of problems for their support staff to address.

Martend said:
That will get you going, but since the included script won't work...
Click to expand...
Click to collapse
That script just burns my biscuits. Why in the name of all that is neat and groovy can't Google fix such a basic problem?

Mostlyhrmlss said:
That script just burns my biscuits. Why in the name of all that is neat and groovy can't Google fix such a basic problem?
Click to expand...
Click to collapse
because its fixed in the latest version of fastboot, that no one seems to be using..

simms22 said:
because its fixed in the latest version of fastboot, that no one seems to be using..
Click to expand...
Click to collapse
Why break it in the first place? lol It's the first thing you learn here, debug & test before releasing it to the masses

So, I got the latest ADB and FASTBOOT from here, put the device in ADB update mode through recovery mode (already OEM unlocked and USB debugging enabled), ran 'adb sideload <filename>' as instructed onscreen, and got "error: device (null) not found" from the command. The device shows up in the Windows device manager when in bootloader mode, but disappears when I go to recovery mode. What am I doing wrong?

Mostlyhrmlss said:
So, I got the latest ADB and FASTBOOT from here, put the device in ADB update mode through recovery mode (already OEM unlocked and USB debugging enabled), ran 'adb sideload <filename>' as instructed onscreen, and got "error: device (null) not found" from the command. What am I doing wrong?
Click to expand...
Click to collapse
do you have the drivers installed? fastboot wont see your device until then.

I installed the drivers as part of the ADB/FASTBOOT package referenced above, but that's not the problem: the device is not shown at all in the Windows device manager, as if it wasn't plugged in.