A problem with ADB... - General Questions and Answers

I tried installing the 1.4.3 ADB/Fastboot program on all three of my computers... It transfers 0 files and flashes some error message from CMD use... Anyone know why Win 7 pro shouldn't take the Install..?? I even used ADMIN to do it... Nothing... I'd love to just see if my new Chinese tablet has a bootloader or not...
Anyone..?

lentmain said:
I tried installing the 1.4.3 ADB/Fastboot program on all three of my computers... It transfers 0 files and flashes some error message from CMD use... Anyone know why Win 7 pro shouldn't take the Install..?? I even used ADMIN to do it... Nothing... I'd love to just see if my new Chinese tablet has a bootloader or not...
Anyone..?
Click to expand...
Click to collapse
How are you installing it? With a program or something? Here I'll just share mine with you.
https://drive.google.com/file/d/0B3XczzpnAnvwdlFvYURXMl8tbUk/view?usp=drivesdk
This has more than adb and fastboot, but all you have to do is extract all of these files into a folder somewhere. Then open the folder, hold SHIFT, and right click. Then select Open CMD Window Here. Then you're all set. (The apktool and smali/baksmali stuff are different tools for editing .apk files. You probably won't need them, but if you do.... already got 'em. Also, the instructions text file is for apktool. I use the same zip to help people edit apps.)
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
How are you installing it? With a program or something? Here I'll just share mine with you.
https://drive.google.com/file/d/0B3XczzpnAnvwdlFvYURXMl8tbUk/view?usp=drivesdk
This has more than adb and fastboot, but all you have to do is extract all of these files into a folder somewhere. Then open the folder, hold SHIFT, and right click. Then select Open CMD Window Here. Then you're all set. (The apktool and smali/baksmali stuff are different tools for editing .apk files. You probably won't need them, but if you do.... already got 'em. Also, the instructions text file is for apktool. I use the same zip to help people edit apps.)
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
I used three different exe programs... the xda one from the forum... And two others from the internet... i checked each with my norton..., then disabl;ed the anti-virus..., then it loaded fine... wouldn't deposit the four files it was supposed to have.... Thanks for your files... I'll try it next... thanks.... lentmain

RealWelder said:
How are you installing it? With a program or something? Here I'll just share mine with you.
https://drive.google.com/file/d/0B3XczzpnAnvwdlFvYURXMl8tbUk/view?usp=drivesdk
This has more than adb and fastboot, but all you have to do is extract all of these files into a folder somewhere. Then open the folder, hold SHIFT, and right click. Then select Open CMD Window Here. Then you're all set. (The apktool and smali/baksmali stuff are different tools for editing .apk files. You probably won't need them, but if you do.... already got 'em. Also, the instructions text file is for apktool. I use the same zip to help people edit apps.)
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Real welder..., May I ask you a question..? Can you tell me how to find out if I have a bootloader and how to find out... I thank you again for your software... It worked wonders.... But the tablet still refuses to tell me more than what was on the scatter txt page...
I started reading the Beginners pages.., as recommended by another guy.... I downloaded the SDK BIG program... Along with the other programs that help it out...
I'm still not sure how to hook up my Chinese tablet to the SDK program and see what is inside...
Thanks ahead of time...,
lentmain
Do you know of a helper page to show me what to do..? Any help is greatly appreciated.....

It varies from device to device, some companies have disabled fastboot. Typically though, when powering it on if you hold vol+ it will go to recovery and vol- will go to bootloader, but not always. On a Coolpad device I have, I had to boot to recovery then it'll say No Command. Hold power and tap vol+ to bring up the menu. Then one of the menu options was reboot to bootloader.
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
It varies from device to device, some companies have disabled fastboot. Typically though, when powering it on if you hold vol+ it will go to recovery and vol- will go to bootloader, but not always. On a Coolpad device I have, I had to boot to recovery then it'll say No Command. Hold power and tap vol+ to bring up the menu. Then one of the menu options was reboot to bootloader.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Tell me..., if you know..., I just Rooted my Tablet.... Does that mean it doesn't have a locked bootloader..???? I still can't find anyone who is working on these Chinese MTK tablets...
Thanks,
lentmain

lentmain said:
Tell me..., if you know..., I just Rooted my Tablet.... Does that mean it doesn't have a locked bootloader..???? I still can't find anyone who is working on these Chinese MTK tablets...
Thanks,
lentmain
Click to expand...
Click to collapse
Not necessarily, what version of Android is it running? On KK you can root even if the bootloader is locked. Anything newer than that though, would most likely have to be unlocked first.
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
Not necessarily, what version of Android is it running? On KK you can root even if the bootloader is locked. Anything newer than that though, would most likely have to be unlocked first.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
It says it's running 6.0 Marshmallow... I can see a eMMc partition on the scatter txt..., I can see lots of flashing write up but I have tried two and they both failed...
Oh well...

lentmain said:
It says it's running 6.0 Marshmallow... I can see a eMMc partition on the scatter txt..., I can see lots of flashing write up but I have tried two and they both failed...
Oh well...
Click to expand...
Click to collapse
Have you tried adb reboot-bootloader command?
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
Have you tried adb reboot-bootloader command?
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
It makes the tablet screen turn black and returns : * daemon not running; starting now at tcp 5037
* daemon started successfully
I'll put it in bootloader then try it again.......
lentmain

lentmain said:
It makes the tablet screen turn black and returns : * daemon not running; starting now at tcp 5037
* daemon started successfully
I'll put it in bootloader then try it again.......
lentmain
Click to expand...
Click to collapse
Tried it again with the tablet in BOOTLOADER mode...
When you push volup then power..., it goes intoa three way choice... Recovery, Bootloader ans Normal... Recovery seems to put you into the routine recovery you see on cell phone... sideload in ADB, and such...
Fastbooat seems to accept some ADB and fastboot commands...( I don't know them all..)
normal does nothing... I have to hit reset pinholr on all three to get out of them... escape doesn't seem to work...

Related

[Boot Splash] "Inspired" by Light (w/Preview Pic)

I hope you enjoy this. These are pretty easy for me to make, so if you have a request... ... At any rate, "thank" me if you like it and use it. And if you screw anything up and your phone explodes, or breaks, or Smurfs attack from outer space, it's your fault. you have been warned!
How to flash:
1. Unzip the file so you have "splash1.img" and place this file in your "tools" folder of your SDK package.
2. Boot into your bootloader (fastboot mode)
3. From the command prompt: Change directories to your SDK "Tools" folder then type:
Code:
fastboot flash splash1 splash1.img
4. Reboot and enjoy
Got a preview pic by chance. Also check your pm's.
Preview pic should be up... I see it on my end?? It's HUGE. lol..
Anyone else not see the pic?
EDIT: Just checked the OP on a different PC, and pic WAS NOT showing up. This has now been corrected. ...
How do we revert to default, if desired?
smalis said:
How do we revert to default, if desired?
Click to expand...
Click to collapse
You will have to re-flash the default boot splash. Using the same method as mentioned.
Note: I will update the OP with the stock Boot splash as well, once I receive my phone.
OK, stupid question time (my specialty) I get into the Inspire bootloader OK, but then how do I call up or otherwise access "command prompt"? It's not like I have a menu button I can push, and command prompt doesn't seem to be one of the options displayed on the screen. I may be overlooking the obvious, and if so I apologize.
Ultra Droid said:
OK, stupid question time (my specialty) I get into the Inspire bootloader OK, but then how do I call up or otherwise access "command prompt"? It's not like I have a menu button I can push, and command prompt doesn't seem to be one of the options displayed on the screen. I may be overlooking the obvious, and if so I apologize.
Click to expand...
Click to collapse
What T.A.G. was referring to was using the command prompt in Windows. This would also be used in conjunction with having the Android SDK installed in Windows.
Wolf_2 said:
What T.A.G. was referring to was using the command prompt in Windows. This would also be used in conjunction with having the Android SDK installed in Windows.
Click to expand...
Click to collapse
OK, *now* I understand! Told you, dumb questions are my specialty!
Thanks much!
-Mike
The only dumb questions are those that are not asked.
Sent from my Inspire 4G using XDA Premium App.
tribalartgod-
Awesome job!
kimtyson said:
tribalartgod-
Awesome job!
Click to expand...
Click to collapse
Thanks. I've been slacking on a lot of stuff here lately. Bout to go full force on this stuff again soon. (Job and life away from Android takes priority.) Stay tuned.
can this be flashed through cwr?
stryfe2010 said:
can this be flashed through cwr?
Click to expand...
Click to collapse
I have not tried it. So as of right now, the official answer is NO. If you decide to try anyway, it's at your own risk. I'm not responsible if your phone becomes a pretty brick.

One click ADB commands! Back up apps, push apps, reboot, recover and download mode.

Make sure your Samsung drivers are installed. http://www.androphiles.com/files/android/Samsung_Mobile_USB_Driver.exe
I figured this will make it easier for everyone to use certain ADB commands. All you do is extract the file, connect your phone and have it in USB debug mode and click whatever file you want. There is a back up for system files, applications, options to push it back to the phone, reboot, recovery and download mode. I hope this helps some of you guys.
Keep in mind, if the files wont push back its because your phone is in read only mode. You can use ES File Manager; go to settings and select root explorer and check the box under that. After you push the files then reboot your phone. You can also just boot into recovery THEN plug your USB in. Whichever one works.
This will be really useful, but I'm not gonna lie, I feel like a badass typing ADB commands manually.
Sent from my Droid Charge running GummyFroyo 1.9.1
Hahaha, I hear you man. I love typing up all my commands but I know multiple people who get confused so I figured I'd make this to help out.
Shades of Dos!
kvswim said:
This will be really useful, but I'm not gonna lie, I feel like a badass typing ADB commands manually.
Sent from my Droid Charge running GummyFroyo 1.9.1
Click to expand...
Click to collapse
Sounds like someone who truly missed DOS, and finally found a replacement.
I just rooted my Charge using ODIN method.
Is the command "adb reboot download" the same thing as holding the volume down key and pressing the power button. When I do that I get a screen that says Downloading.
Does the command "adb pull /data/app Applications" copy all the apps in phone memory in the folder/data/app into a folder on my computer called Applications??
I found this link after I had rooted and wish I had have found it first.
http://imransarwar.com/index.php/how-to-root-verizon-samsung-droid-charge/
I am not sure what this file which I flashed with CWM is. I think it is a kernel.
I would like to undo the Root I did and try to follow the instructions in the link above. I understand adb but not what I did using ODIN. Where would I get the original kernel from? Thanks for any help.
chrstdvd said:
I just rooted my Charge using ODIN method.
Is the command "adb reboot download" the same thing as holding the volume down key and pressing the power button. When I do that I get a screen that says Downloading.
Does the command "adb pull /data/app Applications" copy all the apps in phone memory in the folder/data/app into a folder on my computer called Applications??
I found this link after I had rooted and wish I had have found it first.
http://imransarwar.com/index.php/how-to-root-verizon-samsung-droid-charge/
I am not sure what this file which I flashed with CWM is. I think it is a kernel.
I would like to undo the Root I did and try to follow the instructions in the link above. I understand adb but not what I did using ODIN. Where would I get the original kernel from? Thanks for any help.
Click to expand...
Click to collapse
That method of rooting will only work with ED1 and you will lose root after doing the EE4 OTA.
_____________________________
Rooted and Bloat frozen Stock EE4
V6 SuperCharger
chrstdvd said:
I just rooted my Charge using ODIN method.
Is the command "adb reboot download" the same thing as holding the volume down key and pressing the power button. When I do that I get a screen that says Downloading.
Does the command "adb pull /data/app Applications" copy all the apps in phone memory in the folder/data/app into a folder on my computer called Applications??
I found this link after I had rooted and wish I had have found it first.
http://imransarwar.com/index.php/how-to-root-verizon-samsung-droid-charge/
I am not sure what this file which I flashed with CWM is. I think it is a kernel.
I would like to undo the Root I did and try to follow the instructions in the link above. I understand adb but not what I did using ODIN. Where would I get the original kernel from? Thanks for any help.
Click to expand...
Click to collapse
Yes, download mode is where you flash your odin files.
And yes to the second part, it backs all your applications that you downloaded into the folder called applications. Then you can use the command to push them back to your phone, itll save you time with the installs. Some apps will force close, some wont.
This was one of my FIRST release when I joined here, lol.
I tried, not the best.

Strange problem on stock

My TF300 is on stock and is unrooted with a locked bootloader. However, despite this, it is no longer booting into the stock ROM. It gets stuck on the bootanimation phase with the loading circle constantly circling round, even after a few hours. It hasn't moved on from this stage unfortunately and I was wondering if there was anything that could be done? I know I could try wiping my data, but there are files and app data that I would not like being lost so is there any way they would be salvageable? Thanks for any help
If ADB is accessible, you could pull /sdcard/, and save it on your computer.
While waiting at the animation, plug it in to your computer, open a terminal, cd into whichever directory ADB resides, and run
Code:
adb devices
If it returns your tablet, then run
Code:
adb pull /sdcard/
adb pull /data/
It should copy everything from your internal storage and your app data into the directory containing ADB, but I'm honestly not sure if you could pull /data/ without root access. And even if you did, I'm not sure how you could safely restore the files without breaking something (or especially without root). At the very least, you'll have the contents of your internal storage.
At that point, you should be OK to wipe your data.
If that doesn't work, then assuming you're on the 4.2 bootloader, you could boot into the bootloader by holding Volume Down as you start your tablet, and you will automatically be in fastboot mode. This should allow you to flash a stock blob with fastboot. Instructions to do so have been posted throughout this forum.
If all else fails, it should still be under warranty since it's locked, so you could get a free replacement. I'm thinking the data wipe should be enough, though. Good luck.
Thank you kindly. I'll thank you later as I seem to be out of thanks today. Admittedly though, I'm not too experienced with this stuff and don't really know which directory ADB is in
Am I right in opening the command window inside sdk--> platform tools?
If so, no devices show up when running the "adb devices" command although I can see my TF300 in device manager
UndisputedGuy said:
Am I right in opening the command window inside sdk--> platform tools?
If so, no devices show up when running the "adb devices" command although I can see my TF300 in device manager
Click to expand...
Click to collapse
That's the right place, unfortunately. I'm assuming you have the ADB drivers installed and everything. Otherwise, install them, and try again.
If you can still get into the bootloader, you should be able to fastboot flash a stock blob. I don't believe that wipes data or your SD card, but I could be wrong. I know that flashing them in a custom recovery wipes both, but I don't think the fastboot method wipes either. Unless tobdaryl or someone else more experienced than I can think of another option, your only next move is using your warranty.
EndlessDissent said:
That's the right place, unfortunately. I'm assuming you have the ADB drivers installed and everything. Otherwise, install them, and try again.
If you can still get into the bootloader, you should be able to fastboot flash a stock blob. I don't believe that wipes data or your SD card, but I could be wrong. I know that flashing them in a custom recovery wipes both, but I don't think the fastboot method wipes either. Unless tobdaryl or someone else more experienced than I can think of another option, your only next move is using your warranty.
Click to expand...
Click to collapse
Thanks again for your help. I'll need to look into using fastboot to flash a stock blob.
I was able to find the device using adb and then run the "adb pull /sdcard/" command (thanks a ton for the help in doing that) but it seems like it's only pulling my files from my downloads and Ringtones folder and even then, it doesn't pull all of them within my downloads folder. Any idea on why this is happening?
UndisputedGuy said:
I was able to find the device using adb and then run the "adb pull /sdcard/" command (thanks a ton for the help in doing that) but it seems like it's only pulling my files from my downloads and Ringtones folder and even then, it doesn't pull all of them within my downloads folder. Any idea on why this is happening?
Click to expand...
Click to collapse
No, I have no idea why it's only pulling a couple directories. It should pull everything from the internal storage since the command includes the whole /sdcard/ directory. I hope someone else knows. If you remember the names of your most important folders, you could try pulling them individually to see if it gives you an error message. If it does, we have a starting point to fix it. If it pulls them fine, then I'll probably be stumped.
EndlessDissent said:
No, I have no idea why it's only pulling a couple directories. It should pull everything from the internal storage since the command includes the whole /sdcard/ directory. I hope someone else knows. If you remember the names of your most important folders, you could try pulling them individually to see if it gives you an error message. If it does, we have a starting point to fix it. If it pulls them fine, then I'll probably be stumped.
Click to expand...
Click to collapse
Thanks! I shall probably try that soon, but I currently want my files from the download folder so will have another stab at that. Thanks again for the assistance :good:
I have been able to pull some files using ADB and thank you greatly for your assistance in doing so. I hadn't really used ABD before but now I'm more familiar with it, so thanks. I have a question regarding using the fasboot method to flash a stock blob. Do I need an unlocked bootloader for flashing a stock blob? The guides I've found have suggested as such. My bootloader is locked.
Honestly, I'm not sure. I would imagine it would do a signature check before flashing, and since you'd be using the official ASUS firmware, it would pass. All I know for sure is that fastboot works on locked tablets. I have no idea to which extent it works.
EndlessDissent said:
Honestly, I'm not sure. I would imagine it would do a signature check before flashing, and since you'd be using the official ASUS firmware, it would pass. All I know for sure is that fastboot works on locked tablets. I have no idea to which extent it works.
Click to expand...
Click to collapse
Thanks again. You've been a great help
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
UndisputedGuy said:
Thanks again. You've been a great help
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
Click to expand...
Click to collapse
I was just about to post that your first step should be to wipe data and see if it boots before we get caught up in fastboot. That is a last resort here. If wiping data may work, fastboot is more work than necessary.
Just to confirm that my tablet did indeed start working again after wiping the data although the stock Asus Backup App fails to restore my app backups from a while ago. It stops at 15%.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Full Screen?

Hi,
I have root,is there anyway we can make use of this great screen easily by getting rid of the navigation on the bottom and the google search bar then use a pie app for navigation?
Cheers.
PS I did search the forum but did not see this question come up.
MJ-12
FYI this has been covered in at least a few threads here.
But this is what I did-
Install this app (it's what I use) or a similar one of your choosing- https://play.google.com/store/apps/details?id=tk.eatheat.pie&hl=en
And add this line to your build.pro to get rid of your navbar- qemu.hw.mainkeys=1
Reboot after editing your build.prop.
That's all you gotta do.
_MetalHead_ said:
FYI this has been covered in at least a few threads here.
But this is what I did-
Install this app (it's what I use) or a similar one of your choosing- https://play.google.com/store/apps/details?id=tk.eatheat.pie&hl=en
And add this line to your build.pro to get rid of your navbar- qemu.hw.mainkeys=1
Reboot after editing your build.prop.
That's all you gotta do.
Click to expand...
Click to collapse
did this and now my phone won't boot, just black screen after google logo
special.k said:
did this and now my phone won't boot, just black screen after google logo
Click to expand...
Click to collapse
Did you edit anything else in your build.prop? All that does is trick the phone into thinking you've got hardware keys, thus eliminating the need for a navbar. There's no reason why that mod alone would cause your phone to not boot. Can you get into fastboot or recovery?
_MetalHead_ said:
Did you edit anything else in your build.prop? All that does is trick the phone into thinking you've got hardware keys, thus eliminating the need for a navbar. There's no reason why that mod alone would cause your phone to not boot. Can you get into fastboot or recovery?
Click to expand...
Click to collapse
I just copy and pasted it in at the bottom, I think that was my problem. I can get into fastboot
special.k said:
I just copy and pasted it in at the bottom, I think that was my problem. I can get into fastboot
Click to expand...
Click to collapse
Well you can try using adb to push an unedited build.prop back to /system and that should get you running again.
_MetalHead_ said:
Well you can try using adb to push an unedited build.prop back to /system and that should get you running again.
Click to expand...
Click to collapse
Okay, where can I find that?
special.k said:
Okay, where can I find that?
Click to expand...
Click to collapse
Just download the stock ROM and pull it out of /system. There should be one over in the dev section.
If you're not familiar with adb, you should probably be able to copy the build.prop over with the file manager in TWRP. Just put it on your SD and use TWRP to move it to /system.
If you have trouble finding the build.prop just let me know and I'll pull mine and post it for you.
_MetalHead_ said:
Just download the stock ROM and pull it out of /system. There should be one over in the dev section.
If you're not familiar with adb, you should probably be able to copy the build.prop over with the file manager in TWRP. Just put it on your SD and use TWRP to move it to /system.
If you have trouble finding the build.prop just let me know and I'll pull mine and post it for you.
Click to expand...
Click to collapse
Okay thanks I will find it, I am on a ubuntu computer right now and am having trouble setting up adb on my old windows xp computer. ADB on ubuntu won't detect my device, I don't have TWRP installed or any recovery of that matter. Can only access fastboot
special.k said:
Okay thanks I will find it, I am on a ubuntu computer right now and am having trouble setting up adb on my old windows xp computer. ADB on ubuntu won't detect my device, I don't have TWRP installed or any recovery of that matter. Can only access fastboot
Click to expand...
Click to collapse
Well that's gotta be annoying. I'm not familiar with ubuntu but have you made sure your drivers are installed on your xp machine?
_MetalHead_ said:
Well that's gotta be annoying. I'm not familiar with ubuntu but have you made sure your drivers are installed on your xp machine?
Click to expand...
Click to collapse
I don't think so, it's not showing that any devices are connected
special.k said:
I don't think so, it's not showing that any devices are connected
Click to expand...
Click to collapse
Look around for the drivers and manually install them. If you can't find them, this toolkit will install them for you- http://forum.xda-developers.com/showthread.php?t=2508817

[Q] The best way to put twrp on your phone when on stock lollipop ?

Is there a way to put twrp on your phone ? I'm on stock lollipop but i don't want to downgrade to kit kat. I'm rooted. Maybe if someone gave me good steps ? i will try. help?
Raz12 said:
Is there a way to put twrp on your phone ? I'm on stock lollipop but i don't want to downgrade to kit kat. I'm rooted. Maybe if someone gave me good steps ? i will try. help?
Click to expand...
Click to collapse
this is what your looking for
http://forum.xda-developers.com/att-lg-g3/development/rom-lg-d850-20f-lollipop-5-0-1-extras-t3052041
clsA said:
this is what your looking for
http://forum.xda-developers.com/att-lg-g3/development/rom-lg-d850-20f-lollipop-5-0-1-extras-t3052041
Click to expand...
Click to collapse
Thanks bro , i did look at this and followed the steps but i couldn't get it to work. I did number one because i'm already rooted and have lollipop. Could you give a more basic step ? like which files to download ? i know the terms. I just can't seem to understand it .
Raz12 said:
Thanks bro , i did look at this and followed the steps but i couldn't get it to work. I did number one because i'm already rooted and have lollipop. Could you give a more basic step ? like which files to download ? i know the terms. I just can't seem to understand it .
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3052041
Since you don't have twrp your best choice is step 1 of autoprime. Just follow the steps. Make sure you have the latest USB drivers for lg g3. Also you need to make sure your device is properly connected via adb. To do that you open a terminal inside the folder containing the files. To get adb correctly you hit shift and right click inside the folder the open terminal. Once terminal is open you start by connecting the device via adb. To check is connected your adb device id must show with the word device in front. If it shows unauthorized you need to allowed the connection on the phone. Once connected you need to push the files to the root of the sdcard
adb push "each file" /sdcard/
Then follow with the commands on step 1. Very important to rename twrp file to the name shown in the command.
netomel said:
http://forum.xda-developers.com/showthread.php?t=3052041
Since you don't have twrp your best choice is step 1 of autoprime. Just follow the steps. Make sure you have the latest USB drivers for lg g3. Also you need to make sure your device is properly connected via adb. To do that you open a terminal inside the folder containing the files. To get adb correctly you hit shift and right click inside the folder the open terminal. Once terminal is open you start by connecting the device via adb. To check is connected your adb device id must show with the word device in front. If it shows unauthorized you need to allowed the connection on the phone. Once connected you need to push the files to the root of the sdcard
adb push "each file" /sdcard/
Then follow with the commands on step 1. Very important to rename twrp file to the name shown in the command.
Click to expand...
Click to collapse
when i first plug up my phone it shows under the devices ID but then it goes away after 30 seconds ? what you think could be the problem ?
Raz12 said:
when i first plug up my phone it shows under the devices ID but then it goes away after 30 seconds ? what you think could be the problem ?
Click to expand...
Click to collapse
I would also download the latest adb drivers or android sdk Package. But yes it is extrange that happens.
netomel said:
I would also download the latest adb drivers or android sdk Package. But yes it is extrange that happens.
Click to expand...
Click to collapse
When it says "internal sdcard" do they mean the storage not on the sd card ? and those 3 links that he posted , we have to download all them files and put them on the sd card or internal ? sorry for questions
netomel said:
I would also download the latest adb drivers or android sdk Package. But yes it is extrange that happens.
Click to expand...
Click to collapse
okay so update now all the other items are being recorded in and out but when it gets to twrp.img it says no such file
netomel said:
I would also download the latest adb drivers or android sdk Package. But yes it is extrange that happens.
Click to expand...
Click to collapse
THANK YOU I GOT IT but i have a quick question , i can now flash exposed on here ? and get roms that are bumped ?
You can flashes any rom bumped since this is bumped as well, if you run into a boot loop make sure to flash the corresponding modem either kk or lollipop. About xposed you can try but you better read the best way to install it because there are issues with lg cover app and the weather app.
i got it working, now im just trying to figure out why G3 tweakbox is not working with xposed
I actuality used the twrp app and it worked like a charm.
Raz12 said:
i got it working, now im just trying to figure out why G3 tweakbox is not working with xposed
Click to expand...
Click to collapse
There are other threads that discuss this matter in detail. I personally don't use xpose until gets more friendly and stable with lollipop.
netomel said:
There are other threads that discuss this matter in detail. I personally don't use xpose until gets more friendly and stable with lollipop.
Click to expand...
Click to collapse
i understand thanks bro
I've been using TWRP manager, since I'm avoiding xposed on 5.0.2 ( APM+ is the only xPosed module I really miss, anyway).
Sent from my LG-V410 using Tapatalk

Categories

Resources