Database Users

[Q] Copy files to the device on twrp?

I installed a rom which had a bad install so i was stuck in a boot loop, And no matter what I try i always get the boot loop, Im able to boot into twrp but going to mount im unable to see it on my windows 7 laptop? I have no idea how to push files to the device with adb as im what you'd call a slow learner lol.
Any ideas would be much apreciated.

I'm in the same boat, I didn't install any custom roms but have twrp and this morning a system update was available and I said yes, it went into twrp and did nothing, I recovered and nothing, it'll only go into twrp and nowhere else. HELP!

Did you guys look here?
[FIX] Installed TWRP and now you're stuck after OTA?

crazyboy81 said:
I'm in the same boat, I didn't install any custom roms but have twrp and this morning a system update was available and I said yes, it went into twrp and did nothing, I recovered and nothing, it'll only go into twrp and nowhere else. HELP!
Click to expand...
Click to collapse
Thats an easy one compared to me lol. go to advanced, terminal command and type in the following minus the brackets (dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota)

metapy said:
Did you guys look here?
[FIX] Installed TWRP and now you're stuck after OTA?
Click to expand...
Click to collapse
My problem isnt anything like the bootloop, Ive done a full wipe and now have nothing on my phone to install, adb sideload isnt working for me for some reason as its coming up as adb is not a recognised command? I feel screwed?
EDIT: I may have solved my problem, currently pushing a rom onto the phone with adb sideload

LG G2 ADB unauthorized device (unable to get into system)

Hey guys, I was running 4.3.x for a while with the loki twrp solution and all was well, after many attempts to flash 4.4 I finally decided to ditch twrp and go to CWM, that went without a hitch and brought me into the latest nightly of CM, yet I wanted a fresh install (No accounts, no pictures media etc etc) so I tried to do factory reset from within the OS and it wouldn't let me. so I then went into recovery and tried to format things from there...
Since then I have been unable to get past the spinning CyanogenMod boot screen and though adb sees there is a device, it is telling me it is "unauthorized". Of course since I can't get into the OS the RSA confirmation thing can't come up and I can't select any system preferences. Before I went messing around in recovery formatting things ADB was working flawlessly.
Any ideas on where to go from here?
Thanks guys,
Lokin

HellaBester said:
Hey guys, I was running 4.3.x for a while with the loki twrp solution and all was well, after many attempts to flash 4.4 I finally decided to ditch twrp and go to CWM, that went without a hitch and brought me into the latest nightly of CM, yet I wanted a fresh install (No accounts, no pictures media etc etc) so I tried to do factory reset from within the OS and it wouldn't let me. so I then went into recovery and tried to format things from there...
Since then I have been unable to get past the spinning CyanogenMod boot screen and though adb sees there is a device, it is telling me it is "unauthorized". Of course since I can't get into the OS the RSA confirmation thing can't come up and I can't select any system preferences. Before I went messing around in recovery formatting things ADB was working flawlessly.
Any ideas on where to go from here?
Thanks guys,
Lokin
Click to expand...
Click to collapse
I had an issue with my adb, it was out dated. I updated the sdk system, and it detected the lg g2, this could possibly help you.

osugsxr said:
I had an issue with my adb, it was out dated. I updated the sdk system, and it detected the lg g2, this could possibly help you.
Click to expand...
Click to collapse
Yeah I considered that but no everything is up to date. It seems more like the RSA auth fingerprint is not being recognized. Plus it does recognize the phone, it just tells me it is unauthorized.

Get back into Recovery mode and use ADB from there

votinh said:
Get back into Recovery mode and use ADB from there
Click to expand...
Click to collapse
How do I get into recovery without being able to "adb reboot recovery"?

unomicu how
Bump. Anything guys? Really struggling here....

Can you get in recovery using button combination?

votinh said:
Can you get in recovery using button combination?
Click to expand...
Click to collapse
Nope, doesn't seem like it. Though I can get into download mode no problem.

Alright guys, since it seems like not many people out there know whats going on with me I'll dow what i can to keep an update.
Finally got back into Recovery using this super convenient little trick I did not know existed.
Though now I am unable to mount anything at all from recovery "E:Can't mount /cache.. etc"

HellaBester said:
Alright guys, since it seems like not many people out there know whats going on with me I'll dow what i can to keep an update.
Finally got back into Recovery using this super convenient little trick I did not know existed.
Though now I am unable to mount anything at all from recovery "E:Can't mount /cache.. etc"
Click to expand...
Click to collapse
I've never been able to mount anything using the recovery. Not sure if it because of the LG phone or of my recovery. But I've tried different ones (CWM, TWRP, Philz Touch), none was able to mount my phone from recovery. Your best bet right now is to flash the files from a OTG cable and flash drive. Also when you said you formatted the phone from the recovery, did you format the system partition as well? TWRP has that option so I assume CWM has it as well

super114 said:
I've never been able to mount anything using the recovery. Not sure if it because of the LG phone or of my recovery. But I've tried different ones (CWM, TWRP, Philz Touch), none was able to mount my phone from recovery. Your best bet right now is to flash the files from a OTG cable and flash drive. Also when you said you formatted the phone from the recovery, did you format the system partition as well? TWRP has that option so I assume CWM has it as well
Click to expand...
Click to collapse
Heyoo, just in the last hour or so I've got it all fixed!
I did a full system, data and cache format om CWM after that there was no OS or amnything of the sort, then I was able to mount the SD and adb push cm11 + gapps-kk to the sdcard, I flashed those two zips restarted, failed, then i did a system reset (resets everything but the OS) and I popped out in CM11 with a perfectly fresh install. got all that setup and am golden now ::

Congratz

Check the .android folder
My problem started when I tried to connect another phone which happened to be the same type of phone as the previous one. Not sure if that's actually related, but my working hypothesis is that ADB gets confused in this scenario. I tried everything listed here and in many other places, and nothing seemed to work. Finally, I did this:
1. Rename .android folder in your user directory (~/username/.android on Mac OSX) to .android_bak (for safe keeping).
2. Restart the adb daemon: "adb kill-server" followed by "adb start-server"
After that, I got the authentication confirmation on the phone (don't forget that part, of course) and all was well.
These steps merely recreate the .android folder and get rid of any authentication credentials you already have. Note of course that this will impact all other phones you may be connecting.

vs980 need help ASAP!

I was attempting to flash a new rom from twrp, I did advanced wipe and accidentally wiped my sd card partition, now I am stuck in twrp with nothing to flash, recoveries are gone as well, how do I add a flashable zip to the phone to fix it??

Jc8206 said:
I was attempting to flash a new rom from twrp, I did advanced wipe and accidentally wiped my sd card partition, now I am stuck in twrp with nothing to flash, recoveries are gone as well, how do I add a flashable zip to the phone to fix it??
Click to expand...
Click to collapse
I had this problem using Philz Recovery, and ultimately sideloaded a zip with ADB and was able to flash that.
Being that it's TWRP, the process will be slightly different.
http://teamw.in/ADBSideload

Bwangster12 said:
I had this problem using Philz Recovery, and ultimately sideloaded a zip with ADB and was able to flash that.
Being that it's TWRP, the process will be slightly different.
http://teamw.in/ADBSideload
Click to expand...
Click to collapse
the phone has been sitting at starting adb sideloadm feature for a while now, does it take a while to load up?

now i cant for the life of me get adb to recognize my device, Ive installed the drivers with no luck

will the rom zip show up in my file list in twrp? or does adb install the rom?

Adb installs it with a push command. You have to put the rom in the same folder as your adb on pc.
Sent from my VS980 4G using Tapatalk

Finally got it, thanks for the info

[Q] LG G2 d802 internal storage formated, TWRP, rooted -> back to stock?

Hello,
After trying a lot of things and search for half of the day my last chance is now to ask one of you guys for help, please.
Problem:
After I have tried to encrypt the internal storage of my LG G2 via the the previous installed Cyanogenmod 11 this attempt resulted into an error and it has told to me that I should reset to factory stock. This has been worked out as the needed directories havent been found via TWRP recovery. So I have tried to do a hard factory reset as well as a a following format of the internal storage from recovery which brings me now to the boot screen with the LG logo. Not going any further. Not possible to turn the phone off anymore. But I am still able to access the TWRP recovery menu. But as the internal storage has been formated its longer possible to boot up into any ROM.
I am also not able to restore via LG Flash tool, as it is not going any further in download mode.
So I would need help with my last thought of a solution: Pushing a custom (or stock rom) ZIP file via ADP in TWRP to the internal storage, so that I can flash this one again as new operation system. Could someone please give me a precise step to step guide for the ADP slide method as I am unfortunately not good regarding any development tools.
Other methods are more than welcome as well, to re-flash stock or a custom rom to the system, without having access to it in any other way than TWRP.
Mac and Windows operation system is available on a computer. USB driver installed. stock rom kdz file downloaded. But I am not able to move forward. So please help.
Thanks!

Columbiana said:
Hello,
After trying a lot of things and search for half of the day my last chance is now to ask one of you guys for help, please.
Problem:
After I have tried to encrypt the internal storage of my LG G2 via the the previous installed Cyanogenmod 11 this attempt resulted into an error and it has told to me that I should reset to factory stock. This has been worked out as the needed directories havent been found via TWRP recovery. So I have tried to do a hard factory reset as well as a a following format of the internal storage from recovery which brings me now to the boot screen with the LG logo. Not going any further. Not possible to turn the phone off anymore. But I am still able to access the TWRP recovery menu. But as the internal storage has been formated its longer possible to boot up into any ROM.
I am also not able to restore via LG Flash tool, as it is not going any further in download mode.
So I would need help with my last thought of a solution: Pushing a custom (or stock rom) ZIP file via ADP in TWRP to the internal storage, so that I can flash this one again as new operation system. Could someone please give me a precise step to step guide for the ADP slide method as I am unfortunately not good regarding any development tools.
Other methods are more than welcome as well, to re-flash stock or a custom rom to the system, without having access to it in any other way than TWRP.
Mac and Windows operation system is available on a computer. USB driver installed. stock rom kdz file downloaded. But I am not able to move forward. So please help.
Thanks!
Click to expand...
Click to collapse
Follow this guide and adb push a Rom to your sd. It must be a zip, not a kdz, place it in your root drive like C:\ and don't forget that adb is case sensitive.

Art Vanderlay said:
Follow this guide and adb push a Rom to your sd. It must be a zip, not a kdz, place it in your root drive like C:\ and don't forget that adb is case sensitive.
Click to expand...
Click to collapse
Hello,
Thanks for this guide which is really easy to use and I would say my ADB on windows are now ready to push. Unfortunately the ADB are not discovering my devices useing TWRP on it, as the sidemode is not starting up. When I am in TWRP recovery and tapping advanced, tapping adb sidemode it shows me that it would start, but it never tells me that it is started.
Is there any other "entrace" to my devices where I could push a new rom zip file onto it without this TWRP adb sidemode? Or can I reinstall TWRP in any way to "repair" the sidemode feature?

Columbiana said:
Hello,
Thanks for this guide which is really easy to use and I would say my ADB on windows are now ready to push. Unfortunately the ADB are not discovering my devices useing TWRP on it, as the sidemode is not starting up. When I am in TWRP recovery and tapping advanced, tapping adb sidemode it shows me that it would start, but it never tells me that it is started.
Is there any other "entrace" to my devices where I could push a new rom zip file onto it without this TWRP adb sidemode? Or can I reinstall TWRP in any way to "repair" the sidemode feature?
Click to expand...
Click to collapse
Don't worry too much about sideload just write adb push C:\ROM name /sdcard/ and then just locate it in twrp
If you are sideloading you need to use the adb sideload /path/to/Rom.zip command

Freezes on Google screen after attempted SU Install from TWRP

Ok I am sure I did this before without any problem, but this time, through TWRP on the NRTK, I installed Magisk, no problems, and then went back to install the SU with the zip file in TWRP again and then on the reboot it freezes on the Google startup screen.
I didnt even want to install the SU zip, but when I ran SU after Magisk installed after reboot, SU gave an error, so I decided to install SU from TWRP.
Did I do something wrong there, so I dont repeat the same error next time?
And how do I get out of this locked state?
I've tried wiping all cache to factory reset without deleting internal storage data... I am hoping I dont have to delete and wipe everything and start all over. I did not have a chance to eve install TiB yet.

Dathaeus said:
Ok I am sure I did this before without any problem, but this time, through TWRP on the NRTK, I installed Magisk, no problems, and then went back to install the SU with the zip file in TWRP again and then on the reboot it freezes on the Google startup screen.
I didnt even want to install the SU zip, but when I ran SU after Magisk installed after reboot, SU gave an error, so I decided to install SU from TWRP.
Did I do something wrong there, so I dont repeat the same error next time?
And how do I get out of this locked state?
I've tried wiping all cache to factory reset without deleting internal storage data... I am hoping I dont have to delete and wipe everything and start all over. I did not have a chance to eve install TiB yet.
Click to expand...
Click to collapse
Flash the stock boot.img from the image/rom you were using before this and reboot. You will have to re-root (properly) afterwards, but your phone should boot up. If you use Magisk, you don't need SU, and vice versa. Use only one method to root.

v12xke said:
Flash the stock boot.img from the image/rom you were using before this and reboot. You will have to re-root (properly) afterwards, but your phone should boot up. If you use Magisk, you don't need SU, and vice versa. Use only one method to root.
Click to expand...
Click to collapse
Hmmm ya I prob should have posted that SU error message instead of what I did, douche move.
But how do I flash the boot.img... I have an original copy of it on my PC... can I somehow while in TWRP on the phone connect to my PC via cable and run commands from my PC in CMD and execute that old boot.img flash? Or is there a location in the stock Nexus already I can use? Because there is no file in the root drive after I did the soft wipe.
P.S. Everything I have done so far has not deleted my whole storage, yet.... not sure if that is necessary at this point bec it seems reflashing the boot.img wipes absolutely everything again? If I have to it is what it is... just painful when this happens before I could get TiB running... unless my Nandroid backup file I have will restore and work after I do this?

Dathaeus said:
Hmmm ya I prob should have posted that SU error message instead of what I did, douche move.
But how do I flash the boot.img... I have an original copy of it on my PC... can I somehow while in TWRP on the phone connect to my PC via cable and run commands from my PC in CMD and execute that old boot.img flash? Or is there a location in the stock Nexus already I can use? Because there is no file in the root drive after I did the soft wipe.
Click to expand...
Click to collapse
While in TWRP you have MTP (file transfer) so you can add files to your device. Transfer the boot.img over to your device via MTP and then use TWRP to flash. Just be sure to select flash IMAGE rather than ZIP. Lesson here is when you get back up and running, install fastboot/adb and make sure it is working well and communicating with your PC. Then you can learn how to use it. This would take literally 5 seconds to flash via fastboot (device in bootloader mode).
---------- Post added at 01:29 PM ---------- Previous post was at 01:26 PM ----------
Dathaeus said:
P.S. Everything I have done so far has not deleted my whole storage, yet.... not sure if that is necessary at this point bec it seems reflashing the boot.img wipes absolutely everything again? If I have to it is what it is... just painful when this happens before I could get TiB running... unless my Nandroid backup file I have will restore and work after I do this?
Click to expand...
Click to collapse
NO, flashing boot.img will not delete any of your files. It will only write to the boot partition. If using fastboot the command is fastboot flash boot boot.img

v12xke said:
While in TWRP you have MTP (file transfer) so you can add files to your device. Transfer the boot.img over to your device via MTP and then use TWRP to flash. Just be sure to select flash IMAGE rather than ZIP. Lesson here is when you get back up and running, install fastboot/adb and make sure it is working well and communicating with your PC. Then you can learn how to use it. This would take literally 5 seconds to flash via fastboot (device in bootloader mode).
NO, flashing boot.img will not delete any of your files. It will only write to the boot partition. If using fastboot the command is fastboot flash boot boot.img
Click to expand...
Click to collapse
Yep I actually had those platform files already, and yes the MTP was active there, I just never tried that before so didnt know it was even a possibility or the right way.
So I tried via flashing my very old boot.img and also the one from
https://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
via TWRP "Install" via image install (not zip) and to the "boot partition"
and no change, same stuck on Google logo screen.
I tried the fastboot command from CMD and it says
< waiting for any device >
and doesnt do anything. I had it on the default TWRP menu screen.... I waited over 20 min although I know it shouldnt take near that long, just in case.
My bootloader is unlocked BTW, I dont want to assume anything here.

You need help getting the latest fastboot/adb binaries working on your PC. So many tutorials on how to do this. Ugh.

Dathaeus said:
Yep I actually had those platform files already, and yes the MTP was active there, I just never tried that before so didnt know it was even a possibility or the right way.
So I tried via flashing my very old boot.img and also the one from
https://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
via TWRP "Install" via image install (not zip) and to the "boot partition"
and no change, same stuck on Google logo screen.
I tried the fastboot command from CMD and it says
< waiting for any device >
and doesnt do anything. I had it on the default TWRP menu screen.... I waited over 20 min although I know it shouldnt take near that long, just in case.
My bootloader is unlocked BTW, I dont want to assume anything here.
Click to expand...
Click to collapse
Which OS security patch were you running? Flash the system (to the system partition in TWRP) and boot images (again) from the 6P factory image of the same name:
https://developers.google.com/android/images?hl=en
See if this helps.
Sent from my Nexus 5X using Tapatalk

v12xke said:
You need help getting the latest fastboot/adb binaries working on your PC. So many tutorials on how to do this. Ugh.
Click to expand...
Click to collapse
Not sure what you mean... I JUST did all that when I redid my phone completely back to factory etc etc.... just few weeks ago and then again on my new replacement. But just to be sure, I downloaded all those files again today and it didnt make any difference.
Still stuck on the
< waiting for any device >
I have to be missing some other step or something else is wrong here.
FYI not sure if this matters but when phone boots to recovery there's a red error message
"Unable to mount storage"
but it loads to TWRP fine anyways.

SlimSnoopOS said:
Which OS security patch were you running? Flash the system (to the system partition in TWRP) and boot images (again) from the 6P factory image of the same name:
https://developers.google.com/android/images?hl=en
Click to expand...
Click to collapse
Yep thats what I been doing.....
So the CMD command still doesnt work, which I think is weird in itself... and when I try to install from recovery, it goes through the whole process, both boot.img and system.img, but then it freezes on the Google logo again, so no change.
Sorry I am not sure what security patch, I just got this used from eBay, and one thing, not sure if this means anything, it says its a beta version or something and that message came up all the time when I rebooted when the phone was working.

Do I need to suck it up and redo the whole phone again........ :/