Hello all,
I have searched the forum for a bit but I could not find a topic silimar to my problem.
So a couple of days ago I flashed LineageOS 17.1 to my 2013 Nexus 7. After that, I tried installing GApps, but I did not have enough space. I decided to wipe the ROM in order to install a smaller ROM through sideload (as I did with Lineage) whereafter I would install GApps.
So I went into my recovery, wiped my OS and went to boot up Sideload. When I connected it to my pc, and typed "adb devices" it showed as offline. Whereas before it worked perfectly.
I tried the basic things like rebooting my pc/tablet, different USB cable, killing the server and starting it again.
Could someone help me figure it out? I don't have a micro usb OTG adapter, and I'm not planning on getting one except if that's my absolute last resort.
Thanks in advance!
jelles01 said:
Hello all,
I have searched the forum for a bit but I could not find a topic silimar to my problem.
So a couple of days ago I flashed LineageOS 17.1 to my 2013 Nexus 7. After that, I tried installing GApps, but I did not have enough space. I decided to wipe the ROM in order to install a smaller ROM through sideload (as I did with Lineage) whereafter I would install GApps.
So I went into my recovery, wiped my OS and went to boot up Sideload. When I connected it to my pc, and typed "adb devices" it showed as offline. Whereas before it worked perfectly.
I tried the basic things like rebooting my pc/tablet, different USB cable, killing the server and starting it again.
Could someone help me figure it out? I don't have a micro usb OTG adapter, and I'm not planning on getting one except if that's my absolute last resort.
Thanks in advance!
Click to expand...
Click to collapse
Hi, no need for Sideload nor OTG. After booting TWRP, just transfer files via MTP. Note that LOS17 requires repartition and no bigger than pico/micro Gapps.
You can automate the entire installation process (including repartition) with CROSS. However LOS17 server is experiencing some issues, but you could drop your existing LOS17 zip file into CROSS' data folder and "Use local ROM file" option.
:fingers-crossed:
k23m said:
Hi, no need for Sideload nor OTG. After booting TWRP, just transfer files via MTP. Note that LOS17 requires repartition and no bigger than pico/micro Gapps.
You can automate the entire installation process (including repartition) with CROSS. However LOS17 server is experiencing some issues, but you could drop your existing LOS17 zip file into CROSS' data folder and "Use local ROM file" option.
:fingers-crossed:
Click to expand...
Click to collapse
That's the other thing, I can't transfer files through MTP. My pc doesnt recognize my tablet. I will try the auto installer tho, thanks.
Related
A few weeks after rooting and installing CM10 on my GS3, it stopped recognizing any form of USB data connection. It still charges from both computer and wall adapter, but I cannot initiate a data transfer or recognize my device using ADB.
I have tried:
three different OEM Samsung cables (from SG3/SG4 phones)
all the ports on two different Win 7 laptops
all the ports on an Ubuntu desktop
enabling or disabling USB debugging
with different combinations each time. No "USB connection" dialog has shown up on the phone, and no "new device" dialog has shown up on any of the computers. I know that I can get ADB working with a different Android phone (HTC Inspire 4G) so I know that my main laptop has USB ports that work and the cables I've tried work as well, so I'm left to assume that the issue is with the GS3. External visual inspection does not suggest the USB port on the phone is damaged, and the phone is only a year old, so I don't believe that is the cause.
Is there a system setting that I may have modified on the GS3 that would disable all forms of USB communication?
(The end goal is to get at least ADB working so I can try and recover some deleted files from the internal memory; I haven't found a reliable method that does not require ADB so I'm trying to get that to work. I know that transferring files on or off can be accomplished with the external SD card or over Wifi but that is not what I'm looking for)
Any suggestions from anyone?
I am not sure. Could be a software issue. I would try backing up your current cm ROM and try installing a fresh touchwiz ROM to see of that works, to rule out software issues. This could also be a android 4.3 issue. Could try stickmount or a similar otg app from the market.
Sent from my Nexus 7
stelv said:
I am not sure. Could be a software issue. I would try backing up your current cm ROM and try installing a fresh touchwiz ROM to see of that works, to rule out software issues. This could also be a android 4.3 issue. Could try stickmount or a similar otg app from the market.
Sent from my Nexus 7
Click to expand...
Click to collapse
I don't think any OTG app like stickmount will help; I'm not trying to connect devices to my phone. I'm trying to get my computer to recognize my phone (and vice versa) in order to get ADB working.
If I can avoid flashing a RAM I'd like to, because I'm still interested in recovering those deleted files. If that is the only thing that would help, though, then I'll do it. Any other suggestions?
Install Kies and that should get the drivers for the pc in place. Odin should recognize the device when it is in the download mode. If that works, then the pc to phone connection is OK and I'd look to software instead of hardware.
Or, if you boot into your custom recovery, either CWM or TWRP, you should be able to get ADB to recognize the device and issue commands including pulling the files on Internal storage. TWRP also has a file browser built in that might be useful.
I have tried uninstalling any Samsung drivers then using the SGS3 toolkit to install the official drivers, but that didn't change anything on the PC end.
Additionally, I tried finding my device while it was in recovery using ADB and there was no connection indication either.
I currently have CWM installed, but I didn't see a mounting option like I've seen for TWRP. Can I flash TWRP without a computer?
Or try this out: Download mode>Connect via USB>Let Windows download and update all drivers until the notification in the bottom right says it's ready to use>Unplug>Battery Pull>Boot normally>connect again. Voila! It works every time when it's being wonky and its a simple way that doesn't require a bunch of downloads!
installing insecure adb might help
Rebooting into download mode does nothing.
I believe rooting and installing CM10 means I already have insecure adb?
thanks
thanks
what next?
aEx155 said:
Rebooting into download mode does nothing.
I believe rooting and installing CM10 means I already have insecure adb?
Click to expand...
Click to collapse
I have this same issue, in download mode, the device is still not connecting.
what is the next step? I have followed this thread and have the still have the same issues.
T-Mobile Galaxy S3 SGH-T999
Rooted
Latest TWRP recovery
CM 10.2 (Nov 6 nightly- Android 4.3.1)
I am trying to fix the storage issue that the multiple user profiles created when going from Android 4.1 to 4.2, where symlink folders are created and multiple instances of every installed app trick the phone into thinking more storage is being consumed than it actually is.
I found a video (Google: youtube how to fix htc one storage) which is specific to HTC One but figured it would work fine for me.
The video basically tells you to do a full factory wipe from TWRP and then ADB Sideload your ROM of preference.
My issues:
A. I installed Android SDK on my home PC (Windows 7 64-bit) as well as the Android USB drivers. I enabled android debugging and did the kill-server and start-server and can get my PC to recognize my Android phone as an 'authorized device' upon entering 'adb devices' on the command line. However, once I wipe the card in recovery, my device ceases to appear in the cmd line. The list is empty. I need to understand why that happens.
B. Even though I've done a 'factory wipe' in recovery, if I reboot my phone, it goes to the CM setup screen and guides me thru initial phone setup.
Looking for some advice on the above issues. Clearly I'll need for my PC and phone to be able to communicate via ADB sideload first, then I can worry about issue B.
I'm not super experienced at this, but appreciate any help someone could provide. Alternatively, if there's a solution to fix the 4.2 storage issue without a full wipe and clean flash (via ADB), then that would be ideal. I've searched for answers on this specific topic to no avail.
Hey there,
I just wanted to update to another ROM and put the .zip file on my device and then rebooted to recovery and wiped my cache etc.
Somehow the .zip file is missing as well now though, I'm not sure why but it seems to have been deleted when I cleared the cache, etc.
Now I'm left without a .zip file to flash and a totally wiped system without a ROM :/
Is there a way to copy data from PC to the Nexus 7 device while in recovery mode? I tried connecting it via USB but it doesn't show up...
edit: Well after a lot of reading it looks like fastboot is the only option for me. Google USB drivers don't seem to be compatible with Windows 8.1 64bit and therefore I cant get my device to show up in "adb devices". Luckily "fastboot devices" works and I guess I'll just try flashing the stock recovery image now.
That's why I have bought an OTG cable (B letter inscribed on the cable, the others I've tried (4 models) without that B, didn't work with my flo, dunno why) and I have an USB strick to get files like zips from my PC. Or get a stick with both micro USB and USB connections.
Hi,
I had a running N2AOS with CM12 install, then did a return2stock but something went wrong
I have orange/blue boot sequence and can get into TWRP without a problem, can boot into fastboot etc. from TWRP. Battery is 100% - ok, too
But system seems empty now. Maybe wiped wrong. I see a lot of empty folders incl. sdcard etc. I've basic ux knowledge - can use TWRP terminal or file manager.
Is there a chance pulling a rom in the twrp using the usb? On win 8.1 I can delete the adb/amazon drivers. then it gets recognized as "Kindle" or "Tate", but can't connect.
My primary system is macOS Sierra, but have a running windows 8.1/ubuntu laptop with usb 2/3.
I think I'm equipped perfectly and the KF7HD2 is not hard bricked, but leaking adb/kindle knowledge. and the most trys end up with "< waiting for device >"
update: when I try TWRP > mount (anything) it gets recognized by win 81 or ubuntu for a short time, but I can't read or write a thing
maybe someone could help?! I read and tried as much as possible, but don't want to kill my old kindle because my girlfriend wants to read with it
thank you very much!
best
tom
addition: can I connect via twrp console and usb or wifi to a local ip or sth to use ftpget
really nobody an idea?
Hey, I guess i've bricked my beloved Mi6.
Here is the facts.
I was using global beta 9.6.27 and as Xiaomi said they won't update it anymore I decided to go back to Stable Rom.
As always I used XiaomiTools V2 and everything worked perfect until my phone starts for the first time.
As soon as it started it showed the following message:
"Find Device storage corrupted. Your device is unsafe now"
Well, it seems the system is here
But as I follow the steps I can't connect to network (wifi)
I can login at google accounts using 4g.
But when I reach the screen for Mi cloud account login
It shows the following message:
"Could'nt check device security info. Can't get device status, wait a minute or two and try again"
And I can't go over it.
Please, do someone know what can I do?
A few more information.
My bootloader is unlocked.
I can use TWRP but I can't transfer a custom rom to storage.
When I try to use miflash it returns the message: "can not found file flash_all.bat"
I saw something about a problem on persist.img, but when I try to install the file trought adb it shows the memory is locked.
malakobakko said:
Hey, I guess i've bricked my beloved Mi6.
Here is the facts.
I was using global beta 9.6.27 and as Xiaomi said they won't update it anymore I decided to go back to Stable Rom.
As always I used XiaomiTools V2 and everything worked perfect until my phone starts for the first time.
As soon as it started it showed the following message:
"Find Device storage corrupted. Your device is unsafe now"
Well, it seems the system is here
But as I follow the steps I can't connect to network (wifi)
I can login at google accounts using 4g.
But when I reach the screen for Mi cloud account login
It shows the following message:
"Could'nt check device security info. Can't get device status, wait a minute or two and try again"
And I can't go over it.
Please, do someone know what can I do?
A few more information.
My bootloader is unlocked.
I can use TWRP but I can't transfer a custom rom to storage.
When I try to use miflash it returns the message: "can not found file flash_all.bat"
I saw something about a problem on persist.img, but when I try to install the file trought adb it shows the memory is locked.
Click to expand...
Click to collapse
You can use an USB memory stick (with an usb c otg) to flash custom rom from it.
mArIuS% said:
You can use an USB memory stick (with an usb c otg) to flash custom rom from it.
Click to expand...
Click to collapse
I have to buy one, as soon as i buy one.
mArIuS% said:
You can use an USB memory stick (with an usb c otg) to flash custom rom from it.
Click to expand...
Click to collapse
I tried it but the device do not recognize the otg conection. I tryed other versions of twrp but it still didn't recognize.
Any other ideas?
malakobakko said:
I tried it but the device do not recognize the otg conection. I tryed other versions of twrp but it still didn't recognize.
Any other ideas?
Click to expand...
Click to collapse
Did you mounted otg from twrp menu? It's strage that it doesn't see the otg....have you wiped data storage? If you can't wipe from TWRP you can wipe it via fastboot.
-Edit- Do a factory reset, wipe dalvik cache, cache, vendor, system and internal storage, wipe data, restart to recovery and try to put a file on internal storage.
Hello guys.
As my last option before EDL I had the idea to try a miui 9 rom and it flashed.
Phone is working as it had never happened.
Thanks for all the help.