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
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
So, I rooted my coworkers Sprint G2 or LG LS980 using IoRoot a month ago and had TWRP installed on it. prior to doing this I had looked into what it would take to revert it to factory unrooted unmolested state. didnt seem to hard with the lgFlash tool and what not....
Well two days ago he accepted and tried to install the new OTA. he was on ZVA firmware, and I believe the new OTA was for 4.4... well the install of the OTA failed im pretty sure do to TWRP being installed instead of stock recovery. instead of stopping there and calling me he tried to fix it himself... I believe one of the things he did was to wipe the device. as in advanced wipe, select EVERYTING including system....
He gave it to me today rather pissed and asked me to fix it.
Ok, I have bee through MANY threads about reverting back to stock, and it seems I am having a serious driver issue... In my laptops device manager I can see the LS980, but it has no driver installed. I have downloaded many different versions of the LG drivers from various tutorials here and on other websites. I even tried to find them on LG.com, but no luck there.
I can get it into download mode, holding vol+ and plug in USB, but once I try to connect to it via LGMobile Support tool or LGFlash tool, they do not detect it. it tries to load three different modems, and the center one always fails. is there anyplace I can get JUST the driver, not the entire self extracting EXE files?
I was just going to copy a ROM onto the internal storage, but even using the mount tab in TWRP it will not connect to my computer.
PLease for the love of all that is sacred to XDA help me!!! I sadly do not know much about ADB... I have never really used it. at this time it is not installed and I wouldnt know what to install and how to ADB Push a rom onto the phone...
Edit, here is ONE of the tutorials I tried, but since I cannot get the proper drivers installed this hangs when I click the yellow arrow to start it....
http://forum.xda-developers.com/showthread.php?t=2432476
schollianmj said:
So, I rooted my coworkers Sprint G2 or LG LS980 using IoRoot a month ago and had TWRP installed on it. prior to doing this I had looked into what it would take to revert it to factory unrooted unmolested state. didnt seem to hard with the lgFlash tool and what not....
Well two days ago he accepted and tried to install the new OTA. he was on ZVA firmware, and I believe the new OTA was for 4.4... well the install of the OTA failed im pretty sure do to TWRP being installed instead of stock recovery. instead of stopping there and calling me he tried to fix it himself... I believe one of the things he did was to wipe the device. as in advanced wipe, select EVERYTING including system....
He gave it to me today rather pissed and asked me to fix it.
Ok, I have bee through MANY threads about reverting back to stock, and it seems I am having a serious driver issue... In my laptops device manager I can see the LS980, but it has no driver installed. I have downloaded many different versions of the LG drivers from various tutorials here and on other websites. I even tried to find them on LG.com, but no luck there.
I can get it into download mode, holding vol+ and plug in USB, but once I try to connect to it via LGMobile Support tool or LGFlash tool, they do not detect it. it tries to load three different modems, and the center one always fails. is there anyplace I can get JUST the driver, not the entire self extracting EXE files?
I was just going to copy a ROM onto the internal storage, but even using the mount tab in TWRP it will not connect to my computer.
PLease for the love of all that is sacred to XDA help me!!! I sadly do not know much about ADB... I have never really used it. at this time it is not installed and I wouldnt know what to install and how to ADB Push a rom onto the phone...
Edit, here is ONE of the tutorials I tried, but since I cannot get the proper drivers installed this hangs when I click the yellow arrow to start it....
http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
okay so have you tried the following from this thread-
If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
XxZombiePikachu said:
okay so have you tried the following from this thread-
If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY car
eful with spaces and punctuation. One wrong letter and you could nuke your phone.
Click to expand...
Click to collapse
Ok, I think its TWRP 6.1.3.3? Maybe 6.2.3.3... not sure. Phone isn't in front of me this second. As to the terminal command... do I type the word code first? Or is it just there as part of your sentance, type this terminal code..... yea, I'm a retard sometimes. Thanks for your help.
schollianmj said:
Ok, I think its TWRP 6.1.3.3? Maybe 6.2.3.3... not sure. Phone isn't in front of me this second. As to the terminal command... do I type the word code first? Or is it just there as part of your sentance, type this terminal code..... yea, I'm a retard sometimes. Thanks for your help.
Click to expand...
Click to collapse
I think you mean 2.6.3.3 but how knows maybe your from the future
I think it's just the dd... and there is another command over in the thread that ends in misc you can search it up(some people have needed to use the both, while others just the one)
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
What thread? And what's dd?
schollianmj said:
What thread? And what's dd?
Click to expand...
Click to collapse
this one and by dd I meant the command I just was too lazy to type it again
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Huh, that didn't work... Bummer. Any other ideas?
Can you still get to download mode. If so follow
http://forum.xda-developers.com/showthread.php?t=2432476
And then root with ioroot25.
Sent from my Nexus 7 using Tapatalk
secret.animal said:
Can you still get to download mode. If so follow
http://forum.xda-developers.com/showthread.php?t=2432476
And then root with ioroot25.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yea, I have been trying that method... my issue now seems to be that one of the drivers is not installing correctly. So I cannot change the device to port 41. And the app will not see my phone. When I get off work tonight and can use my laptop again I will try downloading advanced and setting that up and see if I can make it work that way. I also read the other thread that was linked last night looking for the two terminal commands to try, both the fota, and the miscellaneous command... found the commands, typed them in, and now my phone boots to the LG logo and my notification light starts scrolling through different colors. I can still get to both recovery and download mode though, so I am not giving up.
Also in that thread someone mentioned koush's generic adb drivers... I downloaded those and will try that as well.
Basically if I can just get my darn laptop to connect to this phone I think I might still have a shot at reviving it.
Multi color led makes me think, wing kernel. Like installing zvc kernel over zva system modem.
You may have to uninstall all lg drivers, and reinstall
Sent from my Nexus 7 using Tapatalk
Well it was running fine until he tapped accept on the ota so I dont know how he would have gotten the wrong kernel.... I have uninstalled the drivers a few times and reinstalled different versions. There is always one that fails when I plug in the phone. Plus I get a message on the device about mediadata unknown, or not found.... something like that. I know before he called me he tried the wipe option in twrp. I know on my galaxy s4 we were not to use the wipe data command in there, I'm thinking he did...
But I can still get to download mode so if I can get my laptop to recognise it I have faith I can lgflash tool it back to life... if I can get the drivers to cooperate...
Quick update on this... I found a tutorial on using adb and managed to sideload a rom, derp milestone 1 I believe it was, and after it completed the phone booted up just fine. My friend wanted it to be reverted back to its stock unrooted state, so I tried LG mobile something or other on my laptop... you all know, the one where you hit options then upgrade recovery and it should download and flash stick software? Well it saw the phone, and said there was no upgradeable software on it... mind you the phone still has a working twrp 2.6.3.3 on it... I don't know... I tried LG flash tool, but i can't get it to be port 41 for that to work... but at least the phone boots and runs fine now.
Still having my driver issue though. When I plug in the phone windows installs 3 drivers. One is CDC driver which always fails. No clue why.
Any ideas?
Hey guys, so after hours of trying to figure out what i've done, i need some help
I had a fully working Nexus last night. I'd unlocked, rooted it and installed a custom rom a few weeks ago and everything was fine. Tonight for some reason i decided i wanted a fresh install, and stupidly deleted the entire internal storage off, and then wiped the Nexus before realising i hadn't put the zips back on to reinstall. So the Nexus is without an OS and completely empty. I can get onto bootloader, and into recovery, but i have nothing on the Nexus to use to recover or install anything. I have backups and fresh custom rom zips on my pc but i can't get them to the Nexus. I'm also struggling to be able to do anything using Wugs Toolkit, because it keeps saying it can't find fastboot or adb depending on what options i try. And i can't turn USB debugging on because i have no OS
I tried to reinstall the adb drivers and could see the nexus internal storage on my pc for a minute but it wouldn't let me copy anything onto it. Now i can't seem to see it again. As for fastboot, it keeps saying it can't be found. So at this point i'm clueless, and googling around is confusing me more and more as i have no idea about any of that stuff. The automatic toolkit is as far as my knowledge goes
Update: i tried using the SDK to use cmd prompt to put it back to stock, but it seems to be stuck on the screen with the red, yellow, green and blue circles now?
Update #2: used an updated adb/fastboot installer, after that my Nexus was actually being seen in Wugs Toolkit. Used the flash & unroot option, and i'm back on my device =) hoping i'll be able to re-root and reinstall my custom rom with no problems now *fingers crossed*
Update #3: Yay all fixed. No idea how i did that but thank goodness that's over with. Not sure how to delete my thread, sorry
For future reference try skipping the toolkits, if you do this manually there is far less likely to be communication issues or others at that
Glad it all worked in the end!
Okay, I bought a Nexus 10 off someone, and they had already rooted the device. Bootloader is unlocked and whatnot. That's where my problems start. I can not for the life of me get fastboot or adb to see this thing.
Here's my info:
Google Nexus 10 (Samsung)
ClockworkMod Recovery 6.0.4.3
Bootloader Version: MANTALJ12a
Windows 8.1 Pro x64
Full Android SDK
Samsung drivers installed (I rooted my Galaxy Nexus without issue).
USB has a direct connection
Before I decided to format and try to install a stock .zip, I could access the tablet as a media (That's how I got the .zip on the device).
Steps to how I got here:
Flashed Cyanogenmod 10.2 or whatever. Didn't want JB, wanted Lollipop.
Pushed the (what I thought was correct) .zip to /sdcard
Booted into recovery
Formatted /system, /cache, /data, /factory
Reflashed the .zip
Failed. Miserably.
I named the .zip as something simple and just overwrote it. I wouldn't have this issue if it wasn't for that. I know I did a bad there.
But still, nothing I can do will get fastboot/adb to see the device. It makes the sounds that it's connected when I plug it in. I'm using an elevated prompt as well, but it will not pull the device. How do I get myself out of this hole? If I could push a new .zip to somewhere on /sdcard I could at least use the recovery to reflash.
Wrong device ? [emoji14]
Khaon said:
Wrong device ? [emoji14]
Click to expand...
Click to collapse
No, I was going to put it in the general help thread, may be better here since this may not be a simple question (Please prove me wrong).
Some additional things I've tried:
The NExus Root Toolkit. Removing all drivers etc. Still getting to fastboot by PWR+ VOL+ + VOL-.
Still nothing. Should I go to my wife's computer and try it there? I might do that anyways.
gothmog1065 said:
Some additional things I've tried:
The NExus Root Toolkit. Removing all drivers etc. Still getting to fastboot by PWR+ VOL+ + VOL-.
Still nothing. Should I go to my wife's computer and try it there? I might do that anyways.
Click to expand...
Click to collapse
You don't have access to have os then? How did you push your zip if you don't have access to adb?
I have seen people who couldn't get adb and fastboot working on their windows and switching to another computer solved the issues.
Ok, make sure to make a full clean of your drivers. Wug toolkit explain how to. Then install proper samsung driver and this
If it is not a hardware's problem, you should have access to fastboot & adb. You might try on another computer if possible. A clean one would be the best (i.e. never used any droid devices, etc.).
Another workaround would be to use and otg cable and an usb drive with any zip of your liking.
Another one, I had an issue long time ago, similar, I had to flash through odin in downloading mode to fix my problems.
BUT did you really deleted /factory partition? It contains various proprietary files needed for the device to work. Well concerns more devices with imei and stuff to allow 3g connection and co. Might have no incidence tho on your device's behavior.
Khaon said:
You don't have access to have os then? How did you push your zip if you don't have access to adb?
Click to expand...
Click to collapse
Sorry if I wasn't clear on this, I have 100% access to my computer. I have the Android SDK installed, and adb/fastboot commands working in command prompt. They're just not seeing the tablet.
Ok, make sure to make a full clean of your drivers. Wug toolkit explain how to. Then install proper samsung driver and this
Click to expand...
Click to collapse
Yeah, that's one of the steps I did. Followed the Wug toolkit and removed everything. Still not seeing the tablet.
If it is not a hardware's problem, you should have access to fastboot & adb. You might try on another computer if possible. A clean one would be the best (i.e. never used any droid devices, etc.).
Click to expand...
Click to collapse
Yeah, seems to be doing the same on my wife's computer (Win 7 HP, never had my phone/tablet hooked to it). I get adb/fastboot loaded and working in the command prompt, and it registers when I plug in, but neither command will "see" the tablet.
Another workaround would be to use and otg cable and an usb drive with any zip of your liking.
Another one, I had an issue long time ago, similar, I had to flash through odin in downloading mode to fix my problems.
BUT did you really deleted /factory partition? It contains various proprietary files needed for the device to work. Well concerns more devices with imei and stuff to allow 3g connection and co. Might have no incidence tho on your device's behavior.
Click to expand...
Click to collapse
It's a Wifi tablet, no cellular data and IMEI etc.
edit: As a side note, I've been thinking about reformatting my computer, though it'll be a huge pain to get it back to here as I've got to go from 7 - 8.0 - 8.1 on the upgrade paths to get it back here again.
gothmog1065 said:
Sorry if I wasn't clear on this, I have 100% access to my computer. I have the Android SDK installed, and adb/fastboot commands working in command prompt. They're just not seeing the tablet.
Click to expand...
Click to collapse
From my own experience, having similar issue with the windows drivers for adb, but eventually I fixed it. I really doubt you are screwed.
adb version output ? 1.0.32 is latest.
Yeah, that's one of the steps I did. Followed the Wug toolkit and removed everything. Still not seeing the tablet.
Click to expand...
Click to collapse
Installed universal adb drivers? Nothing shows up in the device manager?
Yeah, seems to be doing the same on my wife's computer (Win 7 HP, never had my phone/tablet hooked to it). I get adb/fastboot loaded and working in the command prompt, and it registers when I plug in, but neither command will "see" the tablet.
Click to expand...
Click to collapse
You might try odin.
Usb mtp doesn’t work from recovery?
Khaon said:
From my own experience, having similar issue with the windows drivers for adb, but eventually I fixed it. I really doubt you are screwed.
adb version output ? 1.0.32 is latest.
Installed universal adb drivers? Nothing shows up in the device manager?
?
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.32, yep latest.
I just feel like I'm missing something, maybe something stupid. HOWEVER, I'm now getting my nexus 10 to show up in device manager with a ? on it. Already tried the direct Samsung drivers, the universal drivers in the Wug toolkit.
gothmog1065 said:
Android Debug Bridge version 1.0.32, yep latest.
I just feel like I'm missing something, maybe something stupid. HOWEVER, I'm now getting my nexus 10 to show up in device manager with a ? on it. Already tried the direct Samsung drivers, the universal drivers in the Wug toolkit.
Click to expand...
Click to collapse
Did you deleted all samsung vendor, etc from the usb program, you know what i am talking about?
You can force to install drivers from device maanger, don't remember how, when installing manually, you must do some step , install from floppy or file, get inf files or so, you will get a prompt telling you it might be harmfull and it will force installation. Might be the solution?
The culprit is definitely software-sided.
Does the mount internal storage (mtp) work?
Would this be easier in Linux? I could pop open my Ubuntu VM and do this if it'd be easier?
Beyond that, are you telling me to try and install the drivers from the driver files created by the Samsung vendor .exe?
I have tried to 'mount USB storage' from recovery, but it doesn't seem to do anything. /system /cache /data /factory are all mounted ATM and nothing is showing.
You've already got more advanced advice than I can offer but when I tried to update to 5.0.1 from 4.4.4, I couldn't get my windows computer to see my device. I was trying the adb fastboot but it I couldn't get it to work.
Wug's toolkit got it all straightened out (http://forum.xda-developers.com/showthread.php?t=2015467)[*]. There was an option on his interface that asked whether the device was working properly or not (a!most missed it as a choice). Checked that box and it went through much of the process I had done (installing adb, updating drivers etc). Long story short, it worked.
Where did you see this option? The only thing I see is the Soft Brick/Bootloop option where it will install the factory again. Was it that or somewhere else?
I swear to the Android droid that I tried that before. That seems to be doing what needs to be done, holy crap thanks!
e: I would like to know, however, why fastboot/adp wouldn't work but this would without doing any of the other stuff?
gothmog1065 said:
Where did you see this option? The only thing I see is the Soft Brick/Bootloop option where it will install the factory again. Was it that or somewhere else?
I swear to the Android droid that I tried that before. That seems to be doing what needs to be done, holy crap thanks!
e: I would like to know, however, why fastboot/adp wouldn't work but this would without doing any of the other stuff?
Click to expand...
Click to collapse
You're right. I confused the heading but choosing that option got my computer and my Nexus "talking." After installing the factory image I think you can then push a cusom ROM to you Nexus (http://forums.androidcentral.com/go...acks/264619-wugs-nexus-toolkit-questions.html).
gothmog1065 said:
Where did you see this option? The only thing I see is the Soft Brick/Bootloop option where it will install the factory again. Was it that or somewhere else?
I swear to the Android droid that I tried that before. That seems to be doing what needs to be done, holy crap thanks!
e: I would like to know, however, why fastboot/adp wouldn't work but this would without doing any of the other stuff?
Click to expand...
Click to collapse
Problem solved ? I always had less issues with fastboot and adb on Linux you can install a ppa that install for you adb and fastboot
Hovewer if you are using 2.8.2.0 you will need 1.0.32 and the ppa includes 1.0.31 so only adb sideload fails.
Sent from my nexus 10
Over the weekend my Nexus 4 decided not to start. Saturday night it was working, and I hooked it up to charge. By Sunday morning it had turned off. When I restarted it, it got as far as asking for my password (encryption key), and then the four circles just danced around for hours. After letting it sit for a few days, the phone started again. But the experience made me decide it was time to update the system from Kit Kat.
So, more or less, I followed the instructions on the Team Android site. (As a new member of this forum, I'm not allowed to include the link. But Google "Update Nexus 4 to Android 6.0.1 Pure Nexus Project Marshmallow Custom ROM.") The main differences were (1) I only copied the ROM file over and (2) I used TWRP instead of CWM for the recovery. I was having trouble copying the Gapps file, so I thought it would be easier to install Marshmallow first and do the apps later.
Everything was backed up and copied around 7 PM yesterday, when I then wiped the data, did a factory reset, wiped the cache, wiped the dalvik cache, and finally started the installation. It's now almost 1 AM, and the ROM is still being flashed.
What should I do next?
Well it seems like the ROM you downloaded is a corrupt zip file.
I would like you to go to Original Development and download one of the ROMS from there, and then google opengapps, choose, ARM>6.0.1>Pico package (or any other package of your choice). I recommend Pico for your first install which is barebones google play services and Google Play store.
TWRP is perfectly compatible with most recent roms.
And for 6.0.1 , Flash the ROM and then flash GAPPS right away. After flashing, wipe dalvik/cache and then reboot.
If you have any questions, do not hesitate to post them here. good luck
EDIT: If you want Vanilla android with zero modifications, get this one:
http://forum.xda-developers.com/nexus-4/development/rom-6-0-android-marshmallow-pure-aosp-t3220900
Also, if it helps, I got 4 hours of Screen On Time on this ROM, I never got it on any other ROM so it is very light and is exactly what you would be getting on a nexus device.
mohsinkhan35 said:
Well it seems like the ROM you downloaded is a corrupt zip file.
I would like you to go to Original Development and download one of the ROMS from there, and then google opengapps, choose, ARM>6.0.1>Pico package (or any other package of your choice). I recommend Pico for your first install which is barebones google play services and Google Play store.
TWRP is perfectly compatible with most recent roms.
And for 6.0.1 , Flash the ROM and then flash GAPPS right away. After flashing, wipe dalvik/cache and then reboot.
If you have any questions, do not hesitate to post them here. good luck
EDIT: If you want Vanilla android with zero modifications, get this one:
http://forum.xda-developers.com/nexus-4/development/rom-6-0-android-marshmallow-pure-aosp-t3220900
Also, if it helps, I got 4 hours of Screen On Time on this ROM, I never got it on any other ROM so it is very light and is exactly what you would be getting on a nexus device.
Click to expand...
Click to collapse
Thanks, Mohsinkhan35. I followed the link you included and downloaded the ROM and TWRP 3.0.0-0, as the site requires. (I currently have TWRP 2.7.1.0 installed.) I was unable to download the Pico Gapp from that site, since the link seems to be broken. No problem. It's available from lots of locations.
So, as I understand it, my first step should be updating TWRP. I found instructions on how to do this at PhoneArena.com. Although written for Windows users, basically one starts the phone in bootloader mode and then uses adp commands to flash the new recovery (TWRP file).
But now Android File Transfer is not connecting to the phone. I wouldn't expect it to connect if the phone wasn't booted, as the file system is encrypted. Nonetheless, I tried this way without success. Then I tried using bootloader mode, with similar results. I then booted up in RM and got into TWRP, but AFT still doesn't see the phone. This is not altogether unexpected. If the new OS has settings and drivers to connect to my computer (a Yosemite iMac), and I've wiped the old one to make way for the new install, then how can the phone communicate with the PC?
For each of these cases (normal start, bootloader, and RM), I also tried issuing "adb devices" from a command prompt, but it's also returning nothing.
So any suggestions for the next step?
Von Neumann said:
Thanks, Mohsinkhan35. I followed the link you included and downloaded the ROM and TWRP 3.0.0-0, as the site requires. (I currently have TWRP 2.7.1.0 installed.) I was unable to download the Pico Gapp from that site, since the link seems to be broken. No problem. It's available from lots of locations.
So, as I understand it, my first step should be updating TWRP. I found instructions on how to do this at PhoneArena.com. Although written for Windows users, basically one starts the phone in bootloader mode and then uses adp commands to flash the new recovery (TWRP file).
But now Android File Transfer is not connecting to the phone. I wouldn't expect it to connect if the phone wasn't booted, as the file system is encrypted. Nonetheless, I tried this way without success. Then I tried using bootloader mode, with similar results. I then booted up in RM and got into TWRP, but AFT still doesn't see the phone. This is not altogether unexpected. If the new OS has settings and drivers to connect to my computer (a Yosemite iMac), and I've wiped the old one to make way for the new install, then how can the phone communicate with the PC?
For each of these cases (normal start, bootloader, and RM), I also tried issuing "adb devices" from a command prompt, but it's also returning nothing.
So any suggestions for the next step?
Click to expand...
Click to collapse
NEVERMIND!!!!
Experimenting with several different USB cords and ports finally yielded a good connection! Even a native USB port on the back of the iMac didn't work, and neither did some of the ports on my USB 3.0 (2.0 compatible) hub. But finally one worked, and I ran with it. Currently reinstalling my apps on the shiny new Marshmallow system!
THANKS Mohsinkhan35!!!!!
Von Neumann said:
NEVERMIND!!!!
Experimenting with several different USB cords and ports finally yielded a good connection! Even a native USB port on the back of the iMac didn't work, and neither did some of the ports on my USB 3.0 (2.0 compatible) hub. But finally one worked, and I ran with it. Currently reinstalling my apps on the shiny new Marshmallow system!
THANKS Mohsinkhan35!!!!!
Click to expand...
Click to collapse
Sorry about the late reply Von I just saw your replies, I am glad that you got it to work!!
For Future purposes, The easiest way to update TWRP is to download the .img from TWRP, put it on your phone, go to TWRP recovery, and instead of flashing .zip file, choose .img from dropdown list, then select the image file, select recovery option from the list.
Enjoy your new system! Which MarshMallow ROM did you end up flashing?
I found that MM breathe a new life into my Nexus, can't imagine going back to Lollipop, I don't know how you managed to stay with KitKat haha