As I was running the P.A.C. Man ROM with nightlies, I installed the most recent update at the time, the "pac_mako-nightly-20130722.zip". I have been dirty flashing all the nightlies without any problems, until this morning. I installed the new nightly from TWRP, then wiped the dalvik and cache, and then rebooted the system, but when the phone started up again, I got an SD card error - I cannot view any of the contents of my SD card from ES File Explorer or anything and I cannot open or find any of them (picture, music, etc.) from anywhere.
From the file manager in TWRP, I can see that all the files are still there, but the SD card that is been seen everywhere else is a completely different one. If I plug my phone into my computer, the SD card shows up as a "generic hierarchical" with no contents.
Another thing, I cannot access the internet in anyway anymore. The wifi is stuck on "Turning wifi on..." and my SIM card is getting no response ("No Service") - if I remove my SIM card, my phone doesn't do anything either.
I already tried a factory reset to no avail. Nothing I do is working and right now my phone is pretty much stuck in a state of uselessness. I can start it up and it will load normally, but once loaded, there are errors - wifi stuck on "Turning on," no service, SD card is unreadable, and I can't transfer any files from my computer to my phone because it shows up as a "generic hierarchical" SD card.
What do I do?
Wipe system, data, cache and dalvik. Start fresh, reflash ROM. Might help.
Sent from my Nexus 4 using Tapatalk 4 Beta
ridikolous said:
Wipe system, data, cache and dalvik. Start fresh, reflash ROM. Might help.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I've done all of that twice now, but still it doesn't work.
Try a different ROM. Or return your phone back to stock. There is a guide somewhere.
Sent from my Nexus 4 using Tapatalk 4 Beta
roll back to earlier nightly. 721 cm side issues
ziddey said:
roll back to earlier nightly. 721 cm side issues
Click to expand...
Click to collapse
How can I do that?
NexusAndroid4 said:
How can I do that?
Click to expand...
Click to collapse
adb push or sideload an earlier ROM zip to your phone, or restore your backup.
NexusAndroid4 said:
How can I do that?
Click to expand...
Click to collapse
by flashing an older nightly...?
ziddey said:
by flashing an older nightly...?
Click to expand...
Click to collapse
I deleted my old nightlies to clear up space on my SD card... Does that ruin everything?
NexusAndroid4 said:
I deleted my old nightlies to clear up space on my SD card... Does that ruin everything?
Click to expand...
Click to collapse
No, adb push or adb sideload a different ROM zip, done.
NexusAndroid4 said:
I deleted my old nightlies to clear up space on my SD card... Does that ruin everything?
Click to expand...
Click to collapse
time to buy a new phone
CMNein said:
No, adb push or adb sideload a different ROM zip, done.
Click to expand...
Click to collapse
I downloaded the 07/21 file and the sdk. I'm trying to adb sideload in TWRP but I get the error:device not found - adb devices lists no serial number in TWRP. My device's serial number shows up in the Android OS but not in TWRP. What do I do?
Install the adb drivers again with your phone in recovery and connected and try again.
Sent from my Nexus 4 using Tapatalk 4 Beta
CMNein said:
Install the adb drivers again with your phone in recovery and connected and try again.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I believe I've done this reinstalling and it still failed, but could you tell me how?
NexusAndroid4 said:
I believe I've done this reinstalling and it still failed, but could you tell me how?
Click to expand...
Click to collapse
How to install the drivers?
Check if anything is showing up under your cpu's device manager when your phone is connected in recovery. Right click on that device, go to driver tab, select update driver, and then select the path to where you put the drivers you DL'd.
CMNein said:
How to install the drivers?
Check if anything is showing up under your cpu's device manager when your phone is connected in recovery. Right click on that device, go to driver tab, select update driver, and then select the path to where you put the drivers you DL'd.
Click to expand...
Click to collapse
In Device Manager, my phone shows up as "mako." When I try to update from the path of the AndroidSDK in recovery mode, I get an error.
You're pointing it all the way to the sub folder the drivers are in? It's extras/Google/USB drivers or something similar.
Sent from my Nexus 4 using Tapatalk 4 Beta
CMNein said:
You're pointing it all the way to the sub folder the drivers are in? It's extras/Google/USB drivers or something similar.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes:
C:\...\sdk\extras\google\usb_driver
NexusAndroid4 said:
Yes:
C:\...\sdk\extras\google\usb_driver
Click to expand...
Click to collapse
When your phone is booted is it showing up as "online" or "offline" when you do adb devices?
How old are the drivers you have? Might have to update them. The SE Linux code that broke wireless, etc... didn't affect adb. You're just going to have to mess around until you can get your cpu to recognize your phone while you're in recovery. That's all I got.
CMNein said:
When your phone is booted is it showing up as "online" or "offline" when you do adb devices?
How old are the drivers you have? Might have to update them. The SE Linux code that broke wireless, etc... didn't affect adb. You're just going to have to mess around until you can get your cpu to recognize your phone while you're in recovery. That's all I got.
Click to expand...
Click to collapse
Nothing shows up at all with adb devices. When I do adb devices in the normal Android OS, it works, but not in recovery. I installed the SDK today so that shouldn't be the problem.
Related
Like the title says.
I'm in recovery, I wiped it all (unfortunately even the ROM as zip I put on it) and now I don't have no ROM on it and no zip to flash a ROM.
Thought this was no problem, knowing from smartphone recoveries to mount sdcard and copying the file on it. But Nexus 7, well, has no sdcard.
What can I do?
As it is now, I don't have nothing on it and rebooting it wouldn't lead to anything useful.
I need help.
What can I do?
Thanks in advance.
l33ch0r said:
Like the title says.
I'm in recovery, I wiped it all (unfortunately even the ROM as zip I put on it) and now I don't have no ROM on it and no zip to flash a ROM.
Thought this was no problem, knowing from smartphone recoveries to mount sdcard and copying the file on it. But Nexus 7, well, has no sdcard.
What can I do?
As it is now, I don't have nothing on it and rebooting it wouldn't lead to anything useful.
I need help.
What can I do?
Thanks in advance.
Click to expand...
Click to collapse
If you have Android SDK installed, you can use adb push to push the zip file to your internal storage. Put the ROM zip file in your Android SDK - Platform Tools folder on your computer, reboot the N7 into Recovery (connected to computer of course!), open Command Prompt window and change directories to where ever you keep your Android SDK (for me, it's: cd sdk/platform-tools). Then type:
Code:
adb push <name of ROM zip file> /sdcard
Wait, and after about 20 - 60 seconds it'll complete, then you can flash the ROM. It'll be on the root of your internal sdcard (/sdcard).
Sounds difficult for a bloody rookie like me - is there really no easier way? Like transfering via recovery by just telling recovery to mound internal-sd so that it'll pop up on my pc? (know that from CWM and 4Ext on my smartphone)
Or could you explain the steps so that even the bloodiest rookie of them all could understand it properly :-/
aaaw **** -.-
by the way, device is still in recovery
l33ch0r said:
Sounds difficult for a bloody rookie like me - is there really no easier way? Like transfering via recovery by just telling recovery to mound internal-sd so that it'll pop up on my pc? (know that from CWM and 4Ext on my smartphone)
Click to expand...
Click to collapse
Maybe, I don't know. Have you tried it? What recovery are you using? I use TWRP.
RMarkwald said:
Maybe, I don't know. Have you tried it? What recovery are you using? I use TWRP.
Click to expand...
Click to collapse
TWRP as well. Just unlocked, rooted and flashed recovery and now I wanted to have a custom rom.
I tried to mount data and what else there was in "advanced" - my PC doesn't show me anything
Edit: not in advanced, it's the point "mount"
Restock and reroot.You can use Wugfresh toolkit for this. You just install the toolkit and if you can boot in bootloader mode you're saved. That's what I did and it solved my problem.
Sent from my Nexus 7 using xda premium
l33ch0r said:
TWRP as well. Just unlocked, rooted and flashed recovery and now I wanted to have a custom rom.
I tried to mount data and what else there was in "advanced" - my PC doesn't show me anything
Edit: not in advanced, it's the point "mount"
Click to expand...
Click to collapse
How'd you root/unlock, toolkit of some type?
Using the adb command mentioned is the only way that I know of to push a file to your N7. It's not as difficult to do as it sounds.
RMarkwald said:
How'd you root/unlock, toolkit of some type?
Using the adb command mentioned is the only way that I know of to push a file to your N7. It's not as difficult to do as it sounds.
Click to expand...
Click to collapse
Toolkit by WugFresh - I may try to get into bootloader and get back to stock - hopefully it works...
l33ch0r said:
Toolkit by WugFresh - I may try to get into bootloader and get back to stock - hopefully it works...
Click to expand...
Click to collapse
Yeah that would work, as long as you don't re-lock via fastboot. That's what probably wiped out your sdcard, was the fastboot unlock of your device, as it wipes your sdcard.
andymihail said:
Restock and reroot.You can use Wugfresh toolkit for this. You just install the toolkit and if you can boot in bootloader mode you're saved. That's what I did and it solved my problem.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Is it important which current status I choose?
There are 2 to be chosen: Soft-Bricked/Bootloop and Device is on/Normal
If "Device is on" means, that it's turned on, then this'll be my choice, right?
Totally shocked right now
This ain't even my device :-/
RMarkwald said:
Yeah that would work, as long as you don't re-lock via fastboot. That's what probably wiped out your sdcard, was the fastboot unlock of your device, as it wipes your sdcard.
Click to expand...
Click to collapse
No, wiping of my /sdcard was all my fault. I guess I have to take all credit for that
Well downloading the Stock with the toolkit takes quite some time...
foolish me -.-
Thanks for your help so far.
I'll definetely report whether it worked or not
I've never used any of the toolkits out there, I've done it using adb/fastboot commands in a Command Prompt window.
l33ch0r said:
Is it important which current status I choose?
There are 2 to be chosen: Soft-Bricked/Bootloop and Device is on/Normal
If "Device is on" means, that it's turned on, then this'll be my choice, right?
Totally shocked right now
This ain't even my device :-/
Click to expand...
Click to collapse
I can't remember my choice, was a few months ago.
Don't think you can go wrong with either.
I would try device is on.
Sent from my Nexus 7 using xda premium
RMarkwald said:
I've never used any of the toolkits out there, I've done it using adb/fastboot commands in a Command Prompt window.
Click to expand...
Click to collapse
I would've used your solution immediately but I'm just too unfamiliar with this method
Toolkits are probably the easiest way - and it was pretty easy - who could expect me to wipe the zip, I just moved to the storage before flashing it?...
Why does this file has to be hosted on goo.im?
Goo.im gives me roundabout 120kb/s...
It took a while for me also, but in the end everything worked well.
Sent from my GT-I9100 using xda premium
andymihail said:
It took a while for me also, but in the end everything worked well.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I desperately hope to have the same luck...will the bootloader still be unlocked after that procedure? I understand that root definetely is gone, but that shouldn't be a problem at all.
l33ch0r said:
I desperately hope to have the same luck...will the bootloader still be unlocked after that procedure? I understand that root definetely is gone, but that shouldn't be a problem at all.
Click to expand...
Click to collapse
It will remain unlocked until/unless you run the fastboot command: fastboot oem lock
If you don't run this, it will remain unlocked.
Whoaaaa I could scream!
Now that I downloaded the right one and try to flash it through the toolkit, it tells me, that there's no adb to be found. He doesn't recognize the device in bootloader.
What should I do?
OH THANK GOD! Tried it via recovery, he found it and restarted into bootloader
First of all: thank you so much guys - I was really shocked, but it all worked out
One more question before I make the same mistake again. Where should I put the zip which I wanna flash? When I have it connected to the pc, it shows me a portable device where the folders of the internal storage are (like Alarms, Android, DCIM, Download etc pp) - that's where I put the ZIP before.
Shall I keep it there?
And another question: what should I wipe in order to get it done properly?
Edit: Figured it out - got me CWM, much more familiar with that one
but thanks again for all your help guys
Ok, I've got issues. I accidentally wiped internal storage as I was trying to flash a new ROM. I'm trying to ADB push a new ROM to the phone so I can actually get it functional. I'm running a command prompt from my SDK folder, but it keeps telling me that I don't have a device connected. Now, I know I had working drivers on this PC because it is the one I used to root. Any ideas why it would keep telling me that? Or some drivers that might work. I'm booted into TWRP 2.6.3.3 I have System, Data, and Cache mounted, and when I plug the phone in the PC makes the new device sound. I'm kind of at the end of my options here.
Have you tried flashing back to stock?
Sent from my SGH-I337 using XDA Premium 4 mobile app
Install universal drivers, not carrier ones. They are indeed "limited". You could alternatively try Koush's drivers That are floating around.
doktor buknasty said:
Have you tried flashing back to stock?
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Steamer86 said:
Install universal drivers, not carrier ones. They are indeed "limited". You could alternatively try Koush's drivers That are floating around.
Click to expand...
Click to collapse
So that's what I had to do. Back on bone stock. At least it works again.
at some point in the last 6 months or so, my phone lost the ability to connect to my computer- I've tested by uninstalling and reinstalling the USB drivers on my computer, using virtual drivers, etc. Everything I could- I even tested on other computers that it has worked on in the past. Nothing helps.
I then decided it must be on my phones end, so I went so far as to replace the USB connection board inside my phone and that doesnt even work.
I used to have my phone rooted, but that was lost at some point over a couple OTA updates-- Is there anyway I can restore root access on my device without using a USB connection, or does anyone have any ideas on how to fix the connection issue?
Thanks!
Did you check the cable?
krystyuc said:
Did you check the cable?
Click to expand...
Click to collapse
Multiple cables as well. I'd do that before replacing the board!
crazychris78 said:
Multiple cables as well. I'd do that before replacing the board!
Click to expand...
Click to collapse
Usb debugging enabled?
krystyuc said:
Usb debugging enabled?
Click to expand...
Click to collapse
Tried that as well. I've tried pretty much everything I can think of. the superuser app says it might be a kernal issue
crazychris78 said:
Tried that as well. I've tried pretty much everything I can think of. the superuser app says it might be a kernal issue
Click to expand...
Click to collapse
Try the following
1)Boot into booloader and check in device manager if the phone is detected if so then go flash-all.bat 4.4.3( will wipe your phone,new phone factory)
krystyuc said:
Try the following
1)Boot into booloader and check in device manager if the phone is detected if so then go flash-all.bat 4.4.3( will wipe your phone,new phone factory)
Click to expand...
Click to collapse
bootloader isn't recognized on my PC or any others, either
crazychris78 said:
bootloader isn't recognized on my PC or any others, either
Click to expand...
Click to collapse
Well,in that case...i don't know.Maybe you should go to a specialist.
Look for flashify, a app can flash recovery, once you have recovery, you can have root.
Sent from my Galaxy Nexus using Tapatalk
chongns said:
Look for flashify, a app can flash recovery, once you have recovery, you can have root.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Flashify requires root access
do you have a kernel with fast charge enabled? that disables PC data connection
crazychris78 said:
Flashify requires root access
Click to expand...
Click to collapse
please answer below question
1. what os use on your PC ?
2. do you install others driver beside google adb and fastboot?
3. what version of adb and fastboot you have if you have installed before
4. you said you have OTA udpate from gogole or form the ROM developer?
note:
you need to install latest adb and fastboot. latest version is .31
if you have other 2 or more driver installed before, it may crash or mis regonice the phone, like samsung and google driver for Galaxy nexus which i facing.
some help form external web here
I have same problem, i tried even on linux. What is worst i removed rom from sdcard and now my current rom crashed. When i try to pull new rom via adb, new file is created but is "empty". Usb otg doesn't work in recovery ;/
I am seeing the same thing also. I even bought a USB replacement part on ebay and installed it. The PC still doesn't see the device.
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.
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?