Hi -
Asking again after several weeks, hoping that someone has fixed this issue.
I had a rooted N7 with stick mount on it. USB operation worked properly. The OTA came and the kids let it upgrade. After that, there was no more usb connectivity. The unit charges, but will not connect. I have tried: different drivers and different computers. I used another android device to prove that the cable and drivers worked. They did. But, not with the N7.
I am guessing that the OTA caused the N7 usb "driver" to stop working. Either as a result of being rooted or using stick mount. That said:
Is there a way to return the N7 to stock by loading the firmware to internal storage and then having the N7 update?
Hope you can help.
You should probably refer to the Stickie threads at the top of this forum to return to stock. I have an N7 rooted with stickmount and I flashed a 4.3 update zip through TWRP recovery and flashed Supersu through TWRP to regain root. I have not had any USB connection problems. Mine still works as before the update. You might want to try a factory/data reset before returning to stock.
there is no usb
Groid said:
You should probably refer to the Stickie threads at the top of this forum to return to stock. I have an N7 rooted with stickmount and I flashed a 4.3 update zip through TWRP recovery and flashed Supersu through TWRP to regain root. I have not had any USB connection problems. Mine still works as before the update. You might want to try a factory/data reset before returning to stock.
Click to expand...
Click to collapse
Thanks for the reply. But there is NO usb connectivity. There is no way to use a PC to send data through the usb port. The only possible way to get to the os is to put a file on internal storage and "execute" it or force an upgrade using it. Also, there is NO root. So any tools that rely on root will also not work. However, the updater obviously has root rights.
Anyone have any other ideas?
Thanks
Related
Just switched over to Tmobile from Sprint and before even signing into google i went ahead and tried to root my phone. Rooting was a success. Used Flashify to flash twrp recovery. Downloaded rooted stock D80110G rom and began debloating it (like I did with the Sprint version) and then booted to recovery, wiped twice, flashed and reboot. Well, now it will just keep rebooting back to recovery and thats it!
I still have access to download mode
still have access to custom recovery
Did not do a nand backup unfortunately
cant mount in twrp because computer no longer recognizes phone!
shows up under unknown devices as LG D801
Tried the stock recovery using LG Flash tool posted in generals but ran into the "can not update because of your device policy" or something like that. Reinstalled and tried it again many times, even switching languages and countries (the last step)
Tried using the ubuntu method posted by partager.info but even ubuntu does not recognize the device. Matter of fact nothing even happens when i plug the phone in.
Tried reinstalling drivers, tried on 2 different laptops (one windows 8.1, one windows 7, and an ubuntu usb boot) and my desktop computer (windows 8.1) and am just unable to mount using twrp because none of them recognizes it!
tried using the adb sideload but twrp just stays trying to load adb sideload forever and adb terminal cant even find the connected usb device.
Tried factory reset but that just takes me to twrp.
I've redownloaded the rooted stock rom and left everything as is. I'm assuming I just need to get it onto the phone somehow so I can flash it.
I have an otg cable but not quite sure how to work it wit twrp or if that's even an option; I've just purchased it.
I feel like I've exhausted my options. Anything else I can try?
Thanks in advance.
EDIT: Should've just used Titanium to debloat instead of trying to do a fresh install! I know I know
Figured it out! not sure how to delete this thread now
zaft1 said:
Just switched over to Tmobile from Sprint and before even signing into google i went ahead and tried to root my phone. Rooting was a success. Used Flashify to flash twrp recovery. Downloaded rooted stock D80110G rom and began debloating it (like I did with the Sprint version) and then booted to recovery, wiped twice, flashed and reboot. Well, now it will just keep rebooting back to recovery and thats it!
I still have access to download mode
still have access to custom recovery
Did not do a nand backup unfortunately
cant mount in twrp because computer no longer recognizes phone!
shows up under unknown devices as LG D801
Tried the stock recovery using LG Flash tool posted in generals but ran into the "can not update because of your device policy" or something like that. Reinstalled and tried it again many times, even switching languages and countries (the last step)
Tried using the ubuntu method posted by partager.info but even ubuntu does not recognize the device. Matter of fact nothing even happens when i plug the phone in.
Tried reinstalling drivers, tried on 2 different laptops (one windows 8.1, one windows 7, and an ubuntu usb boot) and my desktop computer (windows 8.1) and am just unable to mount using twrp because none of them recognizes it!
tried using the adb sideload but twrp just stays trying to load adb sideload forever and adb terminal cant even find the connected usb device.
Tried factory reset but that just takes me to twrp.
I've redownloaded the rooted stock rom and left everything as is. I'm assuming I just need to get it onto the phone somehow so I can flash it.
I have an otg cable but not quite sure how to work it wit twrp or if that's even an option; I've just purchased it.
I feel like I've exhausted my options. Anything else I can try?
Thanks in advance.
EDIT: Should've just used Titanium to debloat instead of trying to do a fresh install! I know I know
Figured it out! not sure how to delete this thread now
Click to expand...
Click to collapse
Hi, I have the exact same problem as you. Did you end up using otg? how did you finally end up getting a rom in your device and flashing it? I sent you a pm hope fully you see it. please respond im desperate!
mnb91 said:
Hi, I have the exact same problem as you. Did you end up using otg? how did you finally end up getting a rom in your device and flashing it? I sent you a pm hope fully you see it. please respond im desperate!
Click to expand...
Click to collapse
Hey sorry, I haven't been on the site for a couple days.
I used the flashtool to go back to stock. Had to enter download mode and work from there. The big issue I was having was a driver issue. Uninstalled every driver related to android and then reinstalled after a restart and that did the trick. For some reason android phones are giving me a lot of driver issues on windows 8.1
follow these steps here but make sure you read a chunk of the thread as the steps in the main post are not complete
http://forum.xda-developers.com/showthread.php?t=2432476
I've been trying to sideload the lollipop ota since yesterday and after 10 hours of failing, I've finally got it running. The problems I got during the period including adb driver errors, recovery errors, and my USB ports problem.
Here are some tips for the other if facing a lot of problem sideloading the lollipop ota zip.
-Use Windows if possible. I tried using Ubuntu but adb won't work correctly. Even sometimes it works, fastboot fails. Use Windows and install the drivers needed namely Google USB Driver. It can be found on Android official website.
-Plug your device directly to the motherboard. Etc. back USB port. My desktop defective front USB ports caused me the most time as Windows/Ubuntu won't work correctly with them. Windows shows USB malfunction.
-Custom recoveries won't work. I tried twrp and cwm. They won't work. They show incompatible build fingerprint/user release keys. Flash stock recovery. I tried wugfresh but can't figure out how to use it so I have it up and flash with adb in Windows. Of course you need to install the drivers properly.
-If adb/fastboot can't detect device in os/bootloader/sideload/recovery/whatever mode, most probably drivers aren't installed correctly. Google the problem and you'll find solutions to it. It's out there and you can find it.
-Check the index thread in the general forum for useful tools/image/utilities
-Sideloading is quite easy if you have drivers installed correctly assuming you have no hardware problems (defective USB port)
Those are most of the problems I faced when trying to sideload ota. Hope this helps those who are facing same problem as me.
ImjuzCY said:
I've been trying to sideload the lollipop ota since yesterday and after 10 hours of failing, I've finally got it running. The problems I got during the period including adb driver errors, recovery errors, and my USB ports problem.
Here are some tips for the other if facing a lot of problem sideloading the lollipop ota zip.
-Use Windows if possible. I tried using Ubuntu but adb won't work correctly. Even sometimes it works, fastboot fails. Use Windows and install the drivers needed namely Google USB Driver. It can be found on Android official website.
-Plug your device directly to the motherboard. Etc. back USB port. My desktop defective front USB ports caused me the most time as Windows/Ubuntu won't work correctly with them. Windows shows USB malfunction.
-Custom recoveries won't work. I tried twrp and cwm. They won't work. They show incompatible build fingerprint/user release keys. Flash stock recovery. I tried wugfresh but can't figure out how to use it so I have it up and flash with adb in Windows. Of course you need to install the drivers properly.
-If adb/fastboot can't detect device in os/bootloader/sideload/recovery/whatever mode, most probably drivers aren't installed correctly. Google the problem and you'll find solutions to it. It's out there and you can find it.
-Check the index thread in the general forum for useful tools/image/utilities
-Sideloading is quite easy if you have drivers installed correctly assuming you have no hardware problems (defective USB port)
Those are most of the problems I faced when trying to sideload ota. Hope this helps those who are facing same problem as me.
Click to expand...
Click to collapse
Sounds like you need you need to save what every data you can if you can through recovery to maybe an OTG adapter.. Then go ahead and Completely WIPE your Nexus. Follow the instructions and download the Android Lolipop LRX31P image, and all the other files needed to properly root your device.. Flash to Stock+Unroot, then once finished reboot and put in your email and settings, download all your backed up apps.. Then once finished, then go back to the Nexus Toolkit by Wugsfresh, and use the tool to root the device, it will put your device into Booloader/Fastboot, and let it do its thing.. Make sure you have USB debugging selected..
If you have a custom kernel on your current rom, it will not sideload.. if you made any changes, if its rooted it will not OTA.. You need to flash to Stock Android 5.0 and go through the motions.... I was on Carbon Rom 4.4.4, and went through the paces, and gave me no issue.. It just takes about 5 or so mins at first boot.. So if it seems to hang.. don't worry.. Just let it do its thing, put in your email info and there you go.. The tool is dummy proof.. even if you soft brick the device, you can use the Advanced Utilities while manually booting into Fastboot/Bootloader mode..
Edit: also make sure you have the correct ADB drivers.. The took kit has those drivers, just follow the instructions, and you should have ADB, or you can flash manually through fast boot if you select your device as soft bricked.. I had the same problem when I first tried to side load an OTA..
Good luck
Zaphodspeaks said:
Sounds like you need you need to save what every data you can if you can through recovery to maybe an OTG adapter.. Then go ahead and Completely WIPE your Nexus. Follow the instructions and download the Android Lolipop LRX31P image, and all the other files needed to properly root your device.. Flash to Stock+Unroot, then once finished reboot and put in your email and settings, download all your backed up apps.. Then once finished, then go back to the Nexus Toolkit by Wugsfresh, and use the tool to root the device, it will put your device into Booloader/Fastboot, and let it do its thing.. Make sure you have USB debugging selected..
If you have a custom kernel on your current rom, it will not sideload.. if you made any changes, if its rooted it will not OTA.. You need to flash to Stock Android 5.0 and go through the motions.... I was on Carbon Rom 4.4.4, and went through the paces, and gave me no issue.. It just takes about 5 or so mins at first boot.. So if it seems to hang.. don't worry.. Just let it do its thing, put in your email info and there you go.. The tool is dummy proof.. even if you soft brick the device, you can use the Advanced Utilities while manually booting into Fastboot/Bootloader mode..
Edit: also make sure you have the correct ADB drivers.. The took kit has those drivers, just follow the instructions, and you should have ADB, or you can flash manually through fast boot if you select your device as soft bricked.. I had the same problem when I first tried to side load an OTA..
Good luck
Click to expand...
Click to collapse
Oops you misunderstood my post. I've done sideloading 5.0 and its running now before i post this thread. This thread i created is meant to give help to those who need it. Everythings running good for me right now. I successfully flashed stock recovery through adb and after that sideloading ran smoothly. Those problem written above is those problems i faced during it and now i already solved the problem and 5.0 is already running without full wipe. Thanks anyway
ImjuzCY said:
Oops you misunderstood my post. I've done sideloading 5.0 and its running now before i post this thread. This thread i created is meant to give help to those who need it. Everythings running good for me right now. I successfully flashed stock recovery through adb and after that sideloading ran smoothly. Those problem written above is those problems i faced during it and now i already solved the problem and 5.0 is already running without full wipe. Thanks anyway
Click to expand...
Click to collapse
Because of how Lolipop handles file location, I recommend doing a complete factory reset/wipe..
But if its working for you.. Thats alright.. But Android 5.0 handles the SDcard Location in a different area.. Something to do with the multiple profile ability I believe.
Zaphodspeaks said:
Because of how Lolipop handles file location, I recommend doing a complete factory reset/wipe..
But if its working for you.. Thats alright.. But Android 5.0 handles the SDcard Location in a different area.. Something to do with the multiple profile ability I believe.
Click to expand...
Click to collapse
You mean internal storage? I dont think nexus devices have an external microsd slot. Thanks for the suggestion anyway. I will do a factory reset if problems starts to bug me.
ImjuzCY said:
You mean internal storage? I dont think nexus devices have an external microsd slot. Thanks for the suggestion anyway. I will do a factory reset if problems starts to bug me.
Click to expand...
Click to collapse
Yes internal storage.. and yes a factory reset would correct that problem..
That just defeats the whole sideload thing, where you could just do a Titanium backup first, restore Data only when needed. Just install the factory image, and restore the Titanium back up... not the app, but the Data becaus the app will crash.. Its the easiest way to save your settings in your Launcher and your apps..
Its too much trouble to sideload when your rooted, with a custom Kernel.... you wasted 10 hours, when it could of taken less than 10 mins
Zaphodspeaks said:
Yes internal storage.. and yes a factory reset would correct that problem..
That just defeats the whole sideload thing, where you could just do a Titanium backup first, restore Data only when needed. Just install the factory image, and restore the Titanium back up... not the app, but the Data becaus the app will crash.. Its the easiest way to save your settings in your Launcher and your apps..
Its too much trouble to sideload when your rooted, with a custom Kernel.... you wasted 10 hours, when it could of taken less than 10 mins
Click to expand...
Click to collapse
Luckily i was using stock kernel. Ive disabled root beforehand and the problems i faced was all on the pc side. Evrything should be easy if my pc doesnt show so much problems. And i like to take challenges so i chose to sideload haha
My friend has a VZW S5 with a busted pin on his micro USB connector. The power connection is fine, so at least he can charge his phone. From what he read, replacing the USB connector has a high probability of breaking the screen.
But, he's having a lot of problems with the stock Sammy Lollipop ROM. Is there any way I can "upgrade" his phone to a newer custom ROM without the USB data connection working? Maybe some way over TCP/IP?
I suspect not, but I thought I'd ask ...
So you're saying the data connection pin on the microUSB cable doesn't allow him to transfer files to/from a computer?
If he's not rooted, no. A data USB connection is required for the new root method using adb, and it's required for flashing kernels and such via odin.
If he IS already rooted, you can just pull out the microSD card, attach it to a computer with a USB adapter, copy a ROM file to that, and install it with FlashFire.
Thanks, painiac - That's what I expected.
So your only options are to replace the broken phone, or try a factory reset to see if it resolves any of the other issues he's been having.
painiac said:
So your only options are to replace the broken phone, or try a factory reset to see if it resolves any of the other issues he's been having.
Click to expand...
Click to collapse
couldnt he just download the rom from whereever onto his phone and then just transfer it over to his sd card? and flash it with flashfire???
Veid71 said:
couldnt he just download the rom from whereever onto his phone and then just transfer it over to his sd card? and flash it with flashfire???
Click to expand...
Click to collapse
The problem with my friend's phone is that he's unrooted, and still on the stock VZW GS5 ROM (He ignored my offers to root a bunch of times). I'm pretty sure I would have to find a way to install a new Recovery Mode first, right? AFAIK, that requires a USB connection to Odin.
¿GotJazz? said:
The problem with my friend's phone is that he's unrooted, and still on the stock VZW GS5 ROM (He ignored my offers to root a bunch of times). I'm pretty sure I would have to find a way to install a new Recovery Mode first, right? AFAIK, that requires a USB connection to Odin.
Click to expand...
Click to collapse
Hmmm I think it would only require it for the custom recovery but he can take it into a best buy and there should be a Samsung rep there and ask if they can fix it I'm not sure if its under warranty but even if its not they'll still try to help you
Have you tried using the standard 2.0 USB cord to connect to the port? I've seen the guy from RootJunky use (and recommends) using the standard 2.0 USB cable in numerous of his S5 rooting and flashing videos. Worth a shot....
¿GotJazz? said:
The problem with my friend's phone is that he's unrooted, and still on the stock VZW GS5 ROM (He ignored my offers to root a bunch of times). I'm pretty sure I would have to find a way to install a new Recovery Mode first, right? AFAIK, that requires a USB connection to Odin.
Click to expand...
Click to collapse
SafeStrap installation doesn't require a USB connection in KitKat, but in Lollipop you need to be able to flash a kernel with Odin, so no dice there.
You could have used FlashFire rather than installing SafeStrap, which does not require kernel flashes OR a separate recovery environment. But either way, he would need root.
---------- Post added at 08:26 AM ---------- Previous post was at 07:31 AM ----------
Veid71 said:
Hmmm I think it would only require it for the custom recovery but he can take it into a best buy and there should be a Samsung rep there and ask if they can fix it I'm not sure if its under warranty but even if its not they'll still try to help you
Click to expand...
Click to collapse
You do not need a data connection to install SafeStrap or to use FlashFire, both of which can flash files from storage without needing access to a data connection.
But you DO need root access to install either of those, and you DO need a data connection to root Lollipop.
Hi everyone,
I just want to ask for tips and recommendations to resolve my problem on my phone. I used TWRP to root the phone but failed and i also used kingo root apk apps on it but still failed. But after that, my phone just shut down and when i open it, it no longer boot and stocked in the samsung logo blinking. I tried KIES and ODIN apps to recover my phone in download mode but my computer didn't detect my phone. I tried also to wipe-up data using the TWRP progam on boot loader. I am not sure if was able to enable the USB Debugging on my device. What i want to try is if i can install the firmware of my phone using the TWRP but i just dont know what to do or what i needed to download. i downloaded the stock firmware of the phone but when i tried the TWRP to install it, it didnt work. I already go to the repair center but they just did what i did and they also failed to do. Please help me guys. I know that lots of members here are generous and willing to help each other. Thanks
gen0ske said:
Hi everyone,
I just want to ask for tips and recommendations to resolve my problem on my phone. I used TWRP to root the phone but failed and i also used kingo root apk apps on it but still failed. But after that, my phone just shut down and when i open it, it no longer boot and stocked in the samsung logo blinking. I tried KIES and ODIN apps to recover my phone in download mode but my computer didn't detect my phone. I tried also to wipe-up data using the TWRP progam on boot loader. I am not sure if was able to enable the USB Debugging on my device. What i want to try is if i can install the firmware of my phone using the TWRP but i just dont know what to do or what i needed to download. i downloaded the stock firmware of the phone but when i tried the TWRP to install it, it didnt work. I already go to the repair center but they just did what i did and they also failed to do. Please help me guys. I know that lots of members here are generous and willing to help each other. Thanks
Click to expand...
Click to collapse
Hey there,
First off, you can't flash stock firmware through custom recoveries. It can be done only with Odin or Heimdall.
Second, make sure you use the back USB ports of the computer and also try different windows versions.
Wiping data through recovery doesn't help because root apps are usually installed on the system partition.
You could probably flash a custom rom on it. It will at least get the phone working again. You can go from there.
Good luck.
GDReaper said:
Hey there,
First off, you can't flash stock firmware through custom recoveries. It can be done only with Odin or Heimdall.
Second, make sure you use the back USB ports of the computer and also try different windows versions.
Wiping data through recovery doesn't help because root apps are usually installed on the system partition.
You could probably flash a custom rom on it. It will at least get the phone working again. You can go from there.
Good luck.
Click to expand...
Click to collapse
Thank you.
Is the USB Debugging Option has nothing to do with the computer to detect my phone. The technician told me that they will replace the USB female socket on my phone because it was defective. I will spend much on the replacement yet i'm afraid it might not still work. The idea of installing a custom roms might work as you have said. I will try that.
gen0ske said:
Thank you.
Is the USB Debugging Option has nothing to do with the computer to detect my phone. The technician told me that they will replace the USB female socket on my phone because it was defective. I will spend much on the replacement yet i'm afraid it might not still work. The idea of installing a custom roms might work as you have said. I will try that.
Click to expand...
Click to collapse
The computer should detect your device no matter what. I mean, how else would you transfer files between the two, since USB debugging is disabled by default.
GDReaper said:
The computer should detect your device no matter what. I mean, how else would you transfer files between the two, since USB debugging is disabled by default.
Click to expand...
Click to collapse
You made me believe more that I can still restore my device. I thank you for the great support. I will do my best.
***EDIT: The purpose of this post was to perform a clean flash using an USB-OTG cable that was not being read in TWRP. Please see https://forum.xda-developers.com/showpost.php?p=73174128&postcount=5 of this thread to perform a ADB sideload if need be.
Hello,
I have flashed the latest FreedomOS ROM with the latest ElementalX Kernel. I had to perform a dirty flash over the OxygenOS using the latest TWRP 3.1.1-1 because when I try to mount the USB-OTG, TWRP will not mount the flash drive. TWRP is showing the USB-OTG as nothing being there. I am experiencing a few issues so I want to perform a clean flash in hopes that a clean flash will correct these issues, but as most of you are aware. If I wipe the internal memory of the phone I will be left with a paper weight. So I did some Googling and came a crossed a potential fix and that was to format the flash drive as exFAT and/or FAT32, both of which did not work. I tried different flash drives as well. So before I buy a new USB-OTG cable (which does work when booted into the ROM) I was wondering if this post (https://forum.xda-developers.com/showpost.php?p=72828325&postcount=75) from searching these forums will correct the issue? I am not sure extacly what it will do so I don't want to flash it and it causes me more issues than what I am experiencing.
Any advise or assistance would be greatly appreciated. Thank you
One thing that may affect that is that the option to mount OTG storage needs to be enabled in the stock ROM. It may be that this keeps this flag while booted but when you boot to TWRP, this flag may not be transmitted to the kernel and it may not enable OTG. I cant say thats the issue, but its certanly something to take into consideration.
dj_chapz said:
One thing that may affect that is that the option to mount OTG storage needs to be enabled in the stock ROM. It may be that this keeps this flag while booted but when you boot to TWRP, this flag may not be transmitted to the kernel and it may not enable OTG. I cant say thats the issue, but its certanly something to take into consideration.
Click to expand...
Click to collapse
I had a similar thought so I ensured the USB-OTG option in the ROM was set. I bought another USB-OTG cable as I found my self at a Staples anyhow. I tried that to no avail, so it is now quite obvious it is a software based issue. Unless I have worse luck than I thought and I have two USB-OTG cables that won't work with TWRP.... I guess for now I can research what would be better for flashing a ROM, fastboot or ADB and then read up on how to perform one or the other and hope I don't turn my shiny new phone into a paper weight. I wish I had the brain some of you guys here have. :silly:
Thank you for your time dj_chapz
llabtaem said:
I had a similar thought so I ensured the USB-OTG option in the ROM was set. I bought another USB-OTG cable as I found my self at a Staples anyhow. I tried that to no avail, so it is now quite obvious it is a software based issue. Unless I have worse luck than I thought and I have two USB-OTG cables that won't work with TWRP.... I guess for now I can research what would be better for flashing a ROM, fastboot or ADB and then read up on how to perform one or the other and hope I don't turn my shiny new phone into a paper weight. I wish I had the brain some of you guys here have. :silly:
Thank you for your time dj_chapz
Click to expand...
Click to collapse
Its REALLY hard these days to brick your phone TWRP does a great job of "protecting us from ourselves".
You can always while in TWRP use ADB sideload to push another zip if your first one fails for whatever reason.
ADB sideload should basically be your "external storage" option.
dj_chapz said:
Its REALLY hard these days to brick your phone TWRP does a great job of "protecting us from ourselves".
You can always while in TWRP use ADB sideload to push another zip if your first one fails for whatever reason.
ADB sideload should basically be your "external storage" option.
Click to expand...
Click to collapse
Hello again dj_chapz,
Thank you for this advice! I installed the Android SDK and tried to sideload the zip file but kept receiving an error about the ADB not being able to load the zip file. So after doing some searching around I came a crossed this post https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47. After doing what was stated in that post and performing a reboot of my computer I was able to sideload the ROM and Kernel (clean slate, fresh start). So again thank you for all your help and time.:good: Hopefully this fresh start will clear up some issues I was having when I did the dirty flash.
Fastboot ROM
I'm also facing the same issue, when I try to mount a SD Card/OTG, the tickbox in isn't selected.
Can this issue be solved if I flash a fastboot ROM of my device?
Please Help!
adityakulkarni11 said:
Fastboot ROM
I'm also facing the same issue, when I try to mount a SD Card/OTG, the tickbox in isn't selected.
Can this issue be solved if I flash a fastboot ROM of my device?
Please Help!
Click to expand...
Click to collapse
me too facing the same problem