Hello everyone,
Last night I was wiping my phone in TWRP to reinstall a ROM and without paying attention, I accidentally hit clear internal storage when I was checking things to wipe. Now I have nothing to flash to it in ADB and no ROM loaded to the phone. I have ADB on my laptop. How can I use that to push a ROM file from my laptop to my phone so I can use it from TWRP to flash some firmware back onto my phone and boot it up again? I have very little experience in ADB, so any help that can be give with ADB commands would be helpful and appreciated. Thanks in advance.
Here you go, buddy!
http://forum.xda-developers.com/showthread.php?t=1667929
Awesome! Thanks! I wish I had seen that last night. It sounds like it's actually very simple. Now if only I wasn't at work without my phone...haha. I'll give it a shot when i get home.
I've been trying what that post says to do, but I can't get my PC to recognize the phone. I installed the drivers from LG's site for the VS980 (yes, that is my correct model). My computer runs windows 7. When I plug the phone in, my computer says it's an unspecified device and fails to find any drivers to install. Does anyone know of where I can download drivers for my model? Thanks again.
vPro97 said:
Here you go, buddy!
http://forum.xda-developers.com/showthread.php?t=1667929
Click to expand...
Click to collapse
No, "adb sideload name.zip" is the correct way. There are very few devices that have recovery with no sideload functionality. You need to go into TWRP - Advanced - ADB Sideload.
Sent from my LG-D800 using XDA Free mobile app
penser said:
No, "adb sideload name.zip" is the correct way. There are very few devices that have recovery with no sideload functionality. You need to go into TWRP - Advanced - ADB Sideload.
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Actually, I ended up using the push command. I just had to install the ADB universal driver here. Thanks for the help!
Related
Guys I need your help.
I have Nexus 4 16GB pre owned. Bought it with Cyanogenmod 10.2 installed already and rooted. Then CM11 nightlies came and I installed it OTA but it seems that it has a lot of bugs so I rolled back to CM10. When I rolled back and rebooted, it does not come up (Google and Cyanogenmod logo only). I rebooted it to bootload mode, then recovery (TWRP) and accidentally wiped out everything including ROM/OS. I don't have that much knowledge in restoring my phone. I tried connecting it to PC (WinXP) and it does not recognize the device. Tried everything posted in different forums on how to connect my device to PC but to no avail. Cannot do USB debugging thing 'cause I can only utilize device's recovery mode (TWRP). I'm thinking now on having this device repaired by cellphone repair shop just to install OS.Anyone can help? Other forums look like too technical for me. Noob here, really.
Hi I've just had a quick look, try this
http://forum.xda-developers.com/showthread.php?t=2010312
It mentions about installing drivers and says the USB Debugging ones are not required.
Sent from my GT-N7100 using XDA Premium 4 mobile app
MyCanSeeYou said:
Hi I've just had a quick look, try this
http://forum.xda-developers.com/showthread.php?t=2010312
It mentions about installing drivers and says the USB Debugging ones are not required.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks! Still cannot connect my Nexus 4 to either Mac and Windows even after downloading/installing these drivers. PC/Mac still does not recognize my device. Changed USB cables etc and still cannot get through.
spitfiremaxtm said:
Thanks! Still cannot connect my Nexus 4 to either Mac and Windows even after downloading/installing these drivers. PC/Mac still does not recognize my device. Changed USB cables etc and still cannot get through.
Click to expand...
Click to collapse
your bootloader is unlocked? (apologizes for my english, i'm from brasil but i'm trying to help, the same happen to me)
Sent from my Nexus 4 using xda app-developers app
spitfiremaxtm said:
Guys I need your help.
I have Nexus 4 16GB pre owned. Bought it with Cyanogenmod 10.2 installed already and rooted. Then CM11 nightlies came and I installed it OTA but it seems that it has a lot of bugs so I rolled back to CM10. When I rolled back and rebooted, it does not come up (Google and Cyanogenmod logo only). I rebooted it to bootload mode, then recovery (TWRP) and accidentally wiped out everything including ROM/OS. I don't have that much knowledge in restoring my phone. I tried connecting it to PC (WinXP) and it does not recognize the device. Tried everything posted in different forums on how to connect my device to PC but to no avail. Cannot do USB debugging thing 'cause I can only utilize device's recovery mode (TWRP). I'm thinking now on having this device repaired by cellphone repair shop just to install OS.Anyone can help? Other forums look like too technical for me. Noob here, really.
Click to expand...
Click to collapse
Reported your post and recommended it get moved to the Nexus 4 Q/A section. This should allow you to get more accurate answers to your questions.
sconetto said:
your bootloader is unlocked? (apologizes for my english, i'm from brasil but i'm trying to help, the same happen to me)
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes, it's unlocked. Stuck at TWRP recovery mode and can't connect to either Mac or Windows.
spitfiremaxtm said:
Yes, it's unlocked. Stuck at TWRP recovery mode and can't connect to either Mac or Windows.
Click to expand...
Click to collapse
try to put your n4 in bootloader mode, i think its volume down and power button, and connect your n4 to a windows pc with the nexus root toolkit openned, in nrt there is a section, i think is recovery section, select the soft bricked/bootloop, follow the instructions, this proceed solved my problem this option will wipe all your data and files, so you lost all the things you have in your n4. (again, sorry my english, just trying to help) hope i helped
Sent from my Nexus 4 using xda app-developers app
sconetto said:
try to put your n4 in bootloader mode, i think its volume down and power button, and connect your n4 to a windows pc with the nexus root toolkit openned, in nrt there is a section, i think is recovery section, select the soft bricked/bootloop, follow the instructions, this proceed solved my problem this option will wipe all your data and files, so you lost all the things you have in your n4. (again, sorry my english, just trying to help) hope i helped
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thank you! Will try this and let you know if it worked. Thanks again.
Helped me too
spitfiremaxtm said:
Thank you! Will try this and let you know if it worked. Thanks again.
Click to expand...
Click to collapse
ok i hope works
Sent from my Nexus 4 using xda app-developers app
Boot up holding vol down so you are at the android part.
Then attached your phone to your PC and use adb push to push a custom rom or download your source image from google.
Grab the google factory image here https://dl.google.com/dl/android/aosp/occam-krt16s-factory-2006f418.tgz
Then do adb shell
mkdir /sdcard/Download
exit
adb push /donwload folder/name of the zip /sdcard/Download
Then go to recovery twrp and install the zip
Should get you up and running
---------- Post added at 12:34 AM ---------- Previous post was at 12:34 AM ----------
Boot up holding vol down so you are at the android part.
Then attached your phone to your PC and use adb push to push a custom rom or download your source image from google.
Grab the google factory image here https://dl.google.com/dl/android/aosp/occam-krt16s-factory-2006f418.tgz
Then do adb shell
mkdir /sdcard/Download
exit
adb push /donwload folder/name of the zip /sdcard/Download
Then go to recovery twrp and install the zip
Should get you up and running
My phone is rooted, I got that far just fine. I tried using Clockwork Mod on my phone to push the custom ROM I wanted but realized after doing some research and getting the little android with the triangle and exclamation point that it isn't booting into recovery. I did some more research and decided to try and use TWRP. I have made sure I have the right drivers for my phone and that my computer recognizes the device. I have turned debugging on as well, and when the phone connects I go to internet mode and ethernet so that USB Debugging works. I followed the advice here: http://forum.xda-developers.com/showthread.php?t=2449670 and downloaded everything I need. I'm in ADB cmd prompt and when I type the first line to push loki_flash it doesn't work. I even tried using the direct path of C:\Users\Owner\Desktop\loki-master\bin and it didn't work. I can't figure out how to get this recovery on my phone so I can push a custom jelly ROM onto my phone. This isn't my first phone or my first root so I know to read the comments and Q&A and I couldn't find anyone with the same issue. I would be very thankful for any suggestions or direction moving forward. Thanks in advance for any help or guidance.
What is the exact command you're using. Also try to drag the file to the cmd windows instead of writing the directory.
Sent from my LG-D802 using XDA Premium 4 mobile app
Makrilli said:
What is the exact command you're using. Also try to drag the file to the cmd windows instead of writing the directory.
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the quick response, the direct command I'm using is "adb push loki_flash /data/local/tmp/loki_flash" when that didn't work I tried using "adb push loki_flash C:\Users\Owner\Desktop\loki-master\bin" and that didn't work either. AND the error I get is "cannot stat 'loki_flash' : No such file or directory
someone will correct me if Im wrong or there is some reason you shouldnt....... but I used Flashify from the playstore to install TWRP..... worked just fine for me...... of course Im just a novice who knows what worked for him..... so as I said..... I could be way off base
ATT 4.2.2 MDL. I flashed CyanogenMod 10.2 earlier today and it was working fine. Then I installed gapps, cuz, well I need gmail and calendar and the play store. Then my keyboard disappeared and I couldn't set CM up. Googling leads me to believe that it's an issue with the specific gapps package, get the proper package. Get the zip uninstaller for the old gapps. Uninstalled old. Reinstalled new. Then Cyanogenmod has constant popups about gapps failing and cyanogenmod setup wizard failing, to where they are non stop, can't do anything with it. Okay. So I started from scratch, same issue. So then I tried again, thought I did proper procedure (wiped, etc.), but now there's no TWRP folder to pull my CM from to install? How did that disappear? Yes I realize I sound like a moron. Point duly noted. Anyone reading this, where do I go from here? I'm in TWRP now and just... lost.
Do you still have cm on your sdcard? Just install it. Never heard of a gapps uninstaller. Maybe that did something
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Do you still have cm on your sdcard? Just install it. Never heard of a gapps uninstaller. Maybe that did something
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
every directory is empty hunting around the 'Install' area. There used to be a TWRP folder that held my CM zip, gapps zip, etc. It's gone.
Wittyusernametaken said:
every directory is empty hunting around the 'Install' area. There used to be a TWRP folder that held my CM zip, gapps zip, etc. It's gone.
Click to expand...
Click to collapse
Can you boot into the os? Or boot into recovery? If you can you can get cm or another rom on to your device and flash it.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Can you boot into the os? Or boot into recovery? If you can you can get cm or another rom on to your device and flash it.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm in TWRP right now, otherwise it hangs on the Samsung Custom screen. How do I get another ROM from TWRP?
jd1639 said:
Can you boot into the os? Or boot into recovery? If you can you can get cm or another rom on to your device and flash it.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
ADB sideload doesn't seem to work. It's selected from the TWRP and says Starting ADB sideload feature. Then in my terminal I get
"error: device not found"
"error: device not found"
do not understand. by the TWRP page it should work? My command is "adb sideload C:/Users/tho/cm-10.2-20130811-noobdev-jflteatt.zip"
Wittyusernametaken said:
ADB sideload doesn't seem to work. It's selected from the TWRP and says Starting ADB sideload feature. Then in my terminal I get
"error: device not found"
"error: device not found"
do not understand. by the TWRP page it should work? My command is "adb sideload C:/Users/tho/cm-10.2-20130811-noobdev-jflteatt.zip"
Click to expand...
Click to collapse
While the phone is in recovery, you should be able to use "adb push <source_file> /sdcard/filename" to push the ROM to your sdcard. You can then flash it from the recovery.
jmjoyas said:
While the phone is in recovery, you should be able to use "adb push <source_file> /sdcard/filename" to push the ROM to your sdcard. You can then flash it from the recovery.
Click to expand...
Click to collapse
Just tried that, I'm getting "The system cannot find the path specified" and then when I tried it again, "Error: device not found"
I changed the filename to cm10.2.zip for brevity and it's in the same directory as adb. Any other ideas?
Wittyusernametaken said:
Just tried that, I'm getting "The system cannot find the path specified" and then when I tried it again, "Error: device not found"
I changed the filename to cm10.2.zip for brevity and it's in the same directory as adb. Any other ideas?
Click to expand...
Click to collapse
When in recovery type adb devices. Is your device recognized? If not you have a driver issue
Sent from my Nexus 5 using XDA Free mobile app
If jd's suggestion works and your device is recognized. Try it with no .zip on end. If you are using windows.
jd1639 said:
When in recovery type adb devices. Is your device recognized? If not you have a driver issue
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I get "List of devices attached" but then it shows nothing. Interesting since earlier it was the only way to for me to get my phone to reboot into TWRP so it had to have been seeing it at one point. CRAP.
Wittyusernametaken said:
I get "List of devices attached" but then it shows nothing. Interesting since earlier it was the only way to for me to get my phone to reboot into TWRP so it had to have been seeing it at one point. CRAP.
Click to expand...
Click to collapse
Go to your device manager with your phone plugged in. There's probably an asterisk on one of the usb ports. Update that driver manually. Go to let me pick from a list on the computer. Pick andriod adb interface, or something along those lines.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Go to your device manager with your phone plugged in. There's probably an asterisk on one of the usb ports. Update that driver manually. Go to let me pick from a list on the computer. Pick andriod adb interface, or something along those lines.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I've got Other Devices and then underneath it SAMSUNG_Android. Having Windows update the driver does nothing, it cannot find the driver. Manually pointing it to the folder C:\Users\tho\Downloads\SAMSUNG_USB_Driver_for_Mobile_Phones which contains the driver does nothing as well I get another message about "Windows was unable to install your SAMSUNG_Android Windows could not find driver software for your device. If you know the manufacturer of your device, you can visit its website and check the support section for driver software."
Except that driver I got was from the Samsung website? So that makes no sense. I feel like I'm going in circles. What do I do now that Windows won't install any drivers?
I thought installing Keis installs the drivers??.
You could install then uninstall Keis.
Wittyusernametaken said:
I've got Other Devices and then underneath it SAMSUNG_Android. Having Windows update the driver does nothing, it cannot find the driver. Manually pointing it to the folder C:\Users\tho\Downloads\SAMSUNG_USB_Driver_for_Mobile_Phones which contains the driver does nothing as well I get another message about "Windows was unable to install your SAMSUNG_Android Windows could not find driver software for your device. If you know the manufacturer of your device, you can visit its website and check the support section for driver software."
Except that driver I got was from the Samsung website? So that makes no sense. I feel like I'm going in circles. What do I do now that Windows won't install any drivers?
Click to expand...
Click to collapse
Go to below where you search for a driver and to where it says let me pick from a list on the computer. Kies should install the property driver but sometimes doesn't. If you use kies, do what rug said and uninstall it except for the drivers. Kies is a pos
Edit, oh by the way, you're definitely not bricked. You'll be able to get your device working again.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Go to below where you search for a driver and to where it says let me pick from a list on the computer. Kies should install the property driver but sometimes doesn't. If you use kies, do what rug said and uninstall it except for the drivers. Kies is a pos
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
No. I don't have Kies. Previously I was frozen on 4.2.2 MDL and paranoid Kies would update me so no need for it. When I search for it and pick Samsung Android I get to another window that gives me the option of
Samsung Android ADB Interface Version: 2.9.5.916 [9/16/2010]
Samsung Android ADB Interface Version: 2.9.5.916 [9/16/2010]
Samsung Android ADB Interface Version: 2.9.510.0 [5/23/2013]
There's no option for Kies or such.
Wittyusernametaken said:
No. I don't have Kies. Previously I was frozen on 4.2.2 MDL and paranoid Kies would update me so no need for it. When I search for it and pick Samsung Android I get to another window that gives me the option of
Samsung Android ADB Interface Version: 2.9.5.916 [9/16/2010]
Samsung Android ADB Interface Version: 2.9.5.916 [9/16/2010]
Samsung Android ADB Interface Version: 2.9.510.0 [5/23/2013]
There's no option for Kies or such.
Click to expand...
Click to collapse
Pick the newer one and let it do it's thing
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Pick the newer one and let it do it's thing
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm getting somewhere now. Recognized now on adb devices. Pushed the CM file. Flashing now. Is it advisable to Wipe cache/dalvik or just reboot straight in after flashing CM? Thank you so much for your help
Wittyusernametaken said:
I'm getting somewhere now. Recognized now on adb devices. Pushed the CM file. Flashing now. Is it advisable to Wipe cache/dalvik or just reboot straight in after flashing CM? Thank you so much for your help
Click to expand...
Click to collapse
I'd try first just dirty flashing it, no wipes that way it'll save your current settings
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I'd try first just dirty flashing it, no wipes that way it'll save your current settings
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Sweet. I'm in CM. It's not starting the setup wizard, that's odd, but w/e. Do you have any suggestions for google apps (gmail/calendar/play store) since gapps led me on the rabbit trail to destruction. All I want is slimmed down, fast, no bloat and the three previous gapps, but it seems like this is gonna be much trickier than I thought.
phone got wiped, os and all. can only get into team win recovery (no android with !). in recovery file manager there is NOTHING on the phone. can not get phone to be recognized by computer. used sdk to install drivers still nothing. can not activate usb debugging as there is no os. reboot in recovery gives warning no os on phone. there is nothing to restore, all folders in install tab are completely empty. is there anyway to save my phone? there is nothing on it...just enough for safe mode and recovery.
You need to get the computer to recognize your device. When booted into recovery and the device connected to your pc go to device manager and see what the issue is.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You need to get the computer to recognize your device. When booted into recovery and the device connected to your pc go to device manager and see what the issue is.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
got drivers installed sees the device as "android bootloader interface...a link to what to do from this point would work or step by step instruction on how to get os on phone would be great.
Paltirian said:
got drivers installed sees the device as "android bootloader interface...a link to what to do from this point would work or step by step instruction on how to get os on phone would be great.
Click to expand...
Click to collapse
You've got two options
1. Flash the factory image.with fastboot. You'll then have to re-install twrp amrd root
2. Push a rom onto your device using adb in recovery. Then flash that in twrp
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You've got two options
1. Flash the factory image.with fastboot. You'll then have to re-install twrp amrd root
2. Push a rom onto your device using adb in recovery. Then flash that in twrp
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
ok...it is recognized in fast boot but not in recovery. as far as i knew i only need the usb drivers that come from sdk as it is a google device. is there another driver set i need from recovery. where could i find super simple instructions of how to flash image? and if i didnt care about re rooting could i just use fast boot to flash iamge and run with that?
Paltirian said:
ok...it is recognized in fast boot but not in recovery. as far as i knew i only need the usb drivers that come from sdk as it is a google device. is there another driver set i need from recovery. where could i find super simple instructions of how to flash image? and if i didnt care about re rooting could i just use fast boot to flash iamge and run with that?
Click to expand...
Click to collapse
Simplest way is to download the factory image. Google nexus factory image. It's a .tgz file. Extract it using 7-zip. There's a flash-all.bat file in there. Boot into the bootloader and with your device connected to the pc just double click the flash-all.bat. It will wipe your device so if you can, backup first.
Sent from my Nexus 5 using XDA Free mobile app
You are my freaking hero. I'd give you a hug if i could. Will root tomorrow or so... Have you tried lollipop and would you recommend it over KitKat? Again ty so much
Paltirian said:
You are my freaking hero. I'd give you a hug if i could. Will root tomorrow or so... Have you tried lollipop and would you recommend it over KitKat? Again ty so much
Click to expand...
Click to collapse
No problem, glad you got it working. I like lollipop. It looks different but once you get over the difference you like it. I'm running 5.0.1
Sent from my Nexus 9 using XDA Free mobile app
Hey, so today I wanted to install a new ROM on my SM-N900 Note 3. I flashed TWRP, and rebooted. Then I booted into TWRP and opened Android File transfer on my Mac. It kept saying please connect USB device. Other parts of the system do not read the device, however TWRP says the device is charging from my Mac's USB port. I moved to my Windows computer and connected the device. Still nothing. I tried multiple USB cables both 2.0 and 3.0. Nothing works! Can someone help me? I have no OS installed! I don't want to use ODIN or download mode because I would prefer to the install the ROM I'm trying to install because it seems silly that I have recovery access but can't access the file transfer.
Thanks, Justin
No SD Card?
justinxfan said:
Hey, so today I wanted to install a new ROM on my SM-N900 Note 3. I flashed TWRP, and rebooted. Then I booted into TWRP and opened Android File transfer on my Mac. It kept saying please connect USB device. Other parts of the system do not read the device, however TWRP says the device is charging from my Mac's USB port. I moved to my Windows computer and connected the device. Still nothing. I tried multiple USB cables both 2.0 and 3.0. Nothing works! Can someone help me? I have no OS installed! I don't want to use ODIN or download mode because I would prefer to the install the ROM I'm trying to install because it seems silly that I have recovery access but can't access the file transfer.
Thanks, Justin
Click to expand...
Click to collapse
via PC, Odin is the easiest way.
va Mobile, Recovery + ROM in SD card is the easiest way.
nijom said:
via PC, Odin is the easiest way.
va Mobile, Recovery + ROM in SD card is the easiest way.
Click to expand...
Click to collapse
I've used ODIN before but I had thought was incompatible with zips. I'll try it today though. And no, I don't have an SD card. I'm trying to move the files into my internal storage.
Thanks, Justin.
MTP doesn't work with TWRP. You'll have to use adb and push the zip to your internal storage. Then flash it through TWRP.
There are many guides on how to do this, it is very simple. Good luck
Edit- i see you're using a mac, not sure if adb works on there.. never tried myself.. always installed linux on any apple product i've owned
I haven't researched it so it might work straight away, but if not just create a vm with xp, ubuntu or something and use adb through there
Sent from my SM-N9005 using Tapatalk
celderic said:
MTP doesn't work with TWRP. You'll have to use adb and push the zip to your internal storage. Then flash it through TWRP.
There are many guides on how to do this, it is very simple. Good luck
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
That's strange, I'm pretty sure my old Nexus 7 could do this. Oh well.
Code:
adb devices
does not work. It doesn't show the device in recovery. File transfer and ADB only work while the OS is booted up.
justinxfan said:
That's strange, I'm pretty sure my old Nexus 7 could do this. Oh well.
Click to expand...
Click to collapse
Same with my old S2
It's a bug with TWRP for the n9005, i posted in the thread 4 or 5 months ago.
Sorry i've just finished work, will be back in an hour or two.
I thiught there was an ADB button in TWRP?
Sent from my SM-N9005 using Tapatalk
celderic said:
Same with my old S2
It's a bug with TWRP for the n9005, i posted in the thread 4 or 5 months ago.
Sorry i've just finished work, will be back in an hour or two.
I thiught there was an ADB button in TWRP?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
There's a button in TWRP called disable MTP or enable MTP. It has no effect. I cannot find any sign of a ADB button.
justinxfan said:
There's a button in TWRP called disable MTP or enable MTP. It has no effect. I cannot find any sign of a ADB button.
Click to expand...
Click to collapse
ADB sideload, under the advanced tab.
https://twrp.me/faq/ADBSideload.html
I just looked myself and it is there.. if there's a way of taking screenshots in recovery, somebody let me know and i'll post a pic here
Sent from my SM-N9005 using Tapatalk
Ahhh I've seen that button before. Didn't jnowbwhat it did so I didn't touch it. Now that I understand it, I'll give it a try.
Sent from my SM-N900 using XDA Free mobile app
justinxfan said:
Ahhh I've seen that button before. Didn't jnowbwhat it did so I didn't touch it. Now that I understand it, I'll give it a try.
Sent from my SM-N900 using XDA Free mobile app
Click to expand...
Click to collapse
Good luck! Let me know if you run into any problems.
Sent from my SM-N9005 using Tapatalk
Nope. Not working. Started ADB sideload from TWRP and tried to push in a random zip from my computer (about 2 mb). it said error: device not found.
bump
Someone can clarify this?