[Q] I really think I'm screwed this time - One (M7) Q&A, Help & Troubleshooting

I have multiple problems so read on.
A couple weeks ago the computer stopped recognizing my verizon gnex that was rooted, unlocked and running jbsourcery 5.1 that it previously had no problems seeing. It still charges via wall and usb with original m-usb cable. I've tried numerous times to re-install the samsung driver on the computer with wug's toolkit with no luck. I've tried another samsung m-usb cable...no luck. My computer is new so no problems with usb ports (I've tried all of them) and have tried the ver 2.0 port. USB debugging is on and fastcharge is off.
My second and worst problem:
Yesterday in a fit of stupidity I restored one of my original backups ( I believe made with CWM recovery ) that turned out to be a stock. img and after restoring it OTA updated to stock JB. All my other backups were done with TWRP and it's no longer present on the phone. I tried installing BootUnlocker from play store but it says I have no root access and the phone won't flash either recovery so I'm stuck with only Fastboot ver. 9 that only wants to flash something from adb. I've exhausted my knowledge and eyes are crossed from reading forums.
I don't know if I can use something like Terminal Emulator for this or even how to use it.
If you know enough to see that I'm totally screwed...Please tell me! (I'm a big boy)
If you think you have a solution...You are a god!
If you need more info...I can provide it

earbuster said:
I have multiple problems so read on.
A couple weeks ago the computer stopped recognizing my verizon gnex that was rooted, unlocked and running jbsourcery 5.1 that it previously had no problems seeing. It still charges via wall and usb with original m-usb cable. I've tried numerous times to re-install the samsung driver on the computer with wug's toolkit with no luck. I've tried another samsung m-usb cable...no luck. My computer is new so no problems with usb ports (I've tried all of them) and have tried the ver 2.0 port. USB debugging is on and fastcharge is off.
My second and worst problem:
Yesterday in a fit of stupidity I restored one of my original backups ( I believe made with CWM recovery ) that turned out to be a stock. img and after restoring it OTA updated to stock JB. All my other backups were done with TWRP and it's no longer present on the phone. I tried installing BootUnlocker from play store but it says I have no root access and the phone won't flash either recovery so I'm stuck with only Fastboot ver. 9 that only wants to flash something from adb. I've exhausted my knowledge and eyes are crossed from reading forums.
I don't know if I can use something like Terminal Emulator for this or even how to use it.
If you know enough to see that I'm totally screwed...Please tell me! (I'm a big boy)
If you think you have a solution...You are a god!
If you need more info...I can provide it
Click to expand...
Click to collapse
wrong forum!

animaleyes76 said:
wrong forum!
Click to expand...
Click to collapse
Yeah...Sorry ...I moved it already

Related

[Q] At wits end!! Please Help.

OK folks, I know some of you are going to jump straight down my throat, but please, back off and stick to the friendly forums that this used to be where anyone would help anyone.
the story so far is that I once loved my Nexus One, I've had it since launch, I have ran Cynogen Mod 7 for a couple of years, I have had MUI roms running, I have played with various kernels, updated radio, upgraded hardware, all was going wonderfully.
the one thing I could never get was full SU!! Heck knows why!!
I then started getting random problems and downloaded the original google frf83 software and flashed the phone via update.zip using amon-ra recovery.
I thought all was well after this, as my phone received 3 OTA updates and now my phone is on...
Android 2.3.6
Baseband 32.41.00.32U_5.08.00.04
Kernel 2.6.35.7-59465-g42bad32 ([email protected] #1)
Build GRK394
I noticed that in the Status (settings) it was displaying my old sim card number, which is not the number for the sim in the phone now. his I thought was odd and that something had gone wrong.
So as most of us would do, I went to boot AmonRa recovery and it wasnt available, it had been overwritten with the default recovery; ok lets just ADB and reflash it, I hadnt used ADB for a couple of years because I did everything through AmonRa's awesome recovery!!
So off I go, install the SDK, all the appropriate packs including the USB driver, just like I did when I originally flashed the phone with the recovery image!
But an old problem came back that I hadnt even been bothered about because I always put stuff on SDcard via a card reader!!
I have had consistent problems with my nexus one for some time now in regards to the USB drivers, no matter what I do the phone will not install and I believe it could be some conflict in the device.
I am running Vista Ultimate (fully registered) and no matter what I do I cannot get the Nexus One to install. It will only display as unknown device, which is absolutely useless.
I have browsed every post and tried everything I have found, and yet nothing is working. I have used devmgmt, I have tried the roll backs, I have tried to install every driver available to get it working. I have uninstalled the device, updated drivers after fresh install attempts, I have even formatted my laptop thinking it may have had a corrupt OS and bought Vista Ultimate.
I am not a complete noob and I have been around these forums for some years, but I never thought I would have to cry out like a 4ucking Noob with such a seemingly simple problem, but it is not simple, I have done everything I can possibly find!!
I must get the USB working in order to get the recovery back, I can access my phones default recovery but it will not work when trying various roms as update.zip!!
I have tried the terminal commands on the phone to install the recovery.img but I do not have SU access and the phone point blank refuses.
I have attempted to change and remove the recovery files reffered that are causing the revert to default recovery, but shock.. I cannot delete because of insufficient permissions. I cannot ADB because the USB driver refuses to install.
So if I cannot change the files due to permissions, I cannot ADB because of USB, I cannot get to Ra's recovery because of bootfiles, I cannot use default recovery to update.zip... I am absolutely losing my mind and I'm going nuts browsing the forums for the second week running, yes I am now on day 12 of trying to fix this problem and at a complete loss...
Can someone please help??
I will even allow remote access to pc because I am that desperate to resurrect my beloved Nexus One.
I also have a Galaxy I9000 without 3 button download mode but that is an entirely different story!!
Please just someone, come to an oldskoolers rescue, and yes PAYMENT will be given to the knight in shiny armour!!
You could try on another computer which doesn't run Vista
tommert38 said:
You could try on another computer which doesn't run Vista
Click to expand...
Click to collapse
Or just use fastboot instead of adb...
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
tommert38 said:
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
Click to expand...
Click to collapse
Install the drivers for fastboot already Jeez and then read How to use android for dummies.

USB-connection (Smartflash, NVFlash, Data-transfer)

Hi,
I've search thru the forums and tried several things, but haven't found a solution.
My problem is that I no longer can make a USB-connection to my O2X.
The only thing that works in the micro-usb is charging. What I tried:
- Smartflash (power-up without battery while holding vol-)
- NVFlash (power-up without battery while holding both vol-buttons)
- Ordinary USB-connection (flash-drive)
- Cleaned it for dust
All of this was done on different windows machins (WinXP and Win7), all USB-ports and different USB-cables (inlcuding one that I know has worked before). Windows don't even show me the device.
The reason why I want to flash is that I think the current baseband (that I flashed) is not the best for my phone. So I want to try another baseband.
Do any of you have a suggestion on how to fix my phone or is the hardware toasted?
Best regards
Anders
Unable to install stock rom
DEAR MEMBERS
please help me i am running cm7.2 in my o2x and want to go back to stock rom.
i have downloaded smartflash tool and stock rom fls and bin files and done the entire procedure as mentioned in the guide
but when i press start button it asks to install odm which is not mentioned in the steps.
when i press yes nothing happens when i press no nothing happens.
please help me to get back to stock rom or else i may void my warranty.
once before i installed the stock rom by the procedure and was successful but this time i am unable
First uninstall lg software and lg usb drivers then first install LGUnitedMobileDriver_S498MA21_WHQL_ML_Ver_2.1.exe then run the SmartFlashTool_P990.exe then remove battery plug device in while holding volume down - and them try.
komunistvb said:
First uninstall lg software and lg usb drivers then first install LGUnitedMobileDriver_S498MA21_WHQL_ML_Ver_2.1.exe then run the SmartFlashTool_P990.exe then remove battery plug device in while holding volume down - and them try.
Click to expand...
Click to collapse
Thanks for your suggestion, already tried this. The problem is that Windows don't even pickup on my O2X when plugged in. No new devices in the Device Manager shows up.
aziz.chamadia said:
DEAR MEMBERS
please help me i am running cm7.2 in my o2x and want to go back to stock rom.
i have downloaded smartflash tool and stock rom fls and bin files and done the entire procedure as mentioned in the guide
but when i press start button it asks to install odm which is not mentioned in the steps.
when i press yes nothing happens when i press no nothing happens.
please help me to get back to stock rom or else i may void my warranty.
once before i installed the stock rom by the procedure and was successful but this time i am unable
Click to expand...
Click to collapse
Please don't hijack my thread!
Aduck79 said:
Thanks for your suggestion, already tried this. The problem is that Windows don't even pickup on my O2X when plugged in. No new devices in the Device Manager shows up.
Click to expand...
Click to collapse
Try going to Hardware and Sound and then Devices and Printers in the Control Panel. Maybe it'll show there.
Aduck79
You may try in a virgin PC where no USB drivers have been installed. Best would be format PC reinstalll WIN OS and try NVFLASH or SMARTFLASH after installing LG USB drivers. I have also faced similar problems and solved them in different PCs either friends or office. I somehow feel LGs drivers are badly written and not very smooth functioning. In fact I (and many others) have bricked O2X trying to upgrade to official GB updates by using LG PC suite and drivers.
This is only my suggestion. I did not had to format my PC any point of time. Don't curse me if this fails. This is only one of the trials and errors.
Maybe I should try from a Linux live-cd to check if it's windows or the phone who's acting strangely.
Sent from my LG Optimus 2X
I got the exact same problem and after searching the net there are a lot of people having the same issue too.
Don't want to sound negative but the majority never got it to run again. For some it automagically started working again.
I got it to run only on Stock Froyo, no stock GB and no ICS with all the ICS Kernels available.
The thing which helped me on Froyo was: http://forum.xda-developers.com/showpost.php?p=28985033&postcount=5
Unfortunately CM9 has no secret menu.
I once had it recognized with Jarvis Kernel on Paranoidandroid for a second and had a hotreboot. Then never again.
I'm pretty sure the PC and the LG Drivers make no difference in this case, as I got 5 different PCs running different OS for testing and they never made a difference.
Aduck79 said:
Hi,
I've search thru the forums and tried several things, but haven't found a solution.
My problem is that I no longer can make a USB-connection to my O2X.
The only thing that works in the micro-usb is charging. What I tried:
- Smartflash (power-up without battery while holding vol-)
- NVFlash (power-up without battery while holding both vol-buttons)
- Ordinary USB-connection (flash-drive)
- Cleaned it for dust
All of this was done on different windows machins (WinXP and Win7), all USB-ports and different USB-cables (inlcuding one that I know has worked before). Windows don't even show me the device.
The reason why I want to flash is that I think the current baseband (that I flashed) is not the best for my phone. So I want to try another baseband.
Do any of you have a suggestion on how to fix my phone or is the hardware toasted?
Best regards
Anders
Click to expand...
Click to collapse
I'm afraid without any USB connection at all you are pretty much out of luck I'd say
kohos said:
I got the exact same problem and after searching the net there are a lot of people having the same issue too.
Don't want to sound negative but the majority never got it to run again. For some it automagically started working again.
I got it to run only on Stock Froyo, no stock GB and no ICS with all the ICS Kernels available.
The thing which helped me on Froyo was: http://forum.xda-developers.com/showpost.php?p=28985033&postcount=5
Unfortunately CM9 has no secret menu.
I once had it recognized with Jarvis Kernel on Paranoidandroid for a second and had a hotreboot. Then never again.
I'm pretty sure the PC and the LG Drivers make no difference in this case, as I got 5 different PCs running different OS for testing and they never made a difference.
Click to expand...
Click to collapse
Does the ROM has anything to do with Smartflash- and NVflash-modes? My guess is that they have nothing to do with each other. So my problem should persist even though I try different ROMs. Correct me if I'm wrong.
I'll look into the Froyo-topic you linked to.
Strange. Now it suddenly works again. I didn't do anything from the last time. That's odd.
I don't think that the ROM specifically has to do with the problem.
Stock Froyo just happened to be the only ROM where switching USB connection modes made the device seen in device manager on Windows. (Although it required manual .inf driver clickery.)
I'm sure missing USB connectivity affects people in NVFlash as well.
In my case I can't do **** ranging from USB mass storage when booted up, ADB or NVFlash when booting.
However restoring to the Froyo nandroid makes everything working for me again.
oh oh, it looks like the same issue that i had... No PC-connection (Win/Linux) recognized the mobile via USB. No Chance to get it back to work.
I flashed back to stock (very difficult without NVFlash...) and then send it back LG Service for repearing. After three weeks i got it back. They changed the hole mainboard so i got a new IMEI but USB works now again.
zeonit said:
oh oh, it looks like the same issue that i had... No PC-connection (Win/Linux) recognized the mobile via USB. No Chance to get it back to work.
I flashed back to stock (very difficult without NVFlash...) and then send it back LG Service for repearing. After three weeks i got it back. They changed the hole mainboard so i got a new IMEI but USB works now again.
Click to expand...
Click to collapse
Yeah. It stopped working after I booted a couple of times
And it was only semi working, it didn't want to go into Smartflash-mode, only NVFlash and Flash-drive.
@aduck79,
Did you already try tonyp's modded adb drivers?
http://forum.xda-developers.com/showthread.php?t=1752074
aragorn7 said:
@aduck79,
Did you already try tonyp's modded adb drivers?
http://forum.xda-developers.com/showthread.php?t=1752074
Click to expand...
Click to collapse
Nope, as I'm quite sure that it's not a matter of drivers.
Windows don't even detect the phone. So I think that the phone doesn't present itself.
Sent from my LG Optimus 2X
Since you already tried changing cables, computers, and even windows & Linux, and since it works on and off, You're right - it isn't the rom nor the drivers. it does sound like the hardware is messed up where the cable connects.
Any chance you can get it serviced? Hope your warranty covers it.
Sent from my LG-SU660 using xda premium
Same problem, no solution
Hi,
I seem to have the same sort of problem with my phone.
I used to be able to connect my phone to my computer just fine until I upgraded it to Gingerbread. Or that is at least the last time the USB connection seemed to work.
I have looked all over the internet now to find a solution to the problem but can't find one. Hope you guys could help me on this.
My phone is an LG optimus 2x P990 with a stock ROM gingerbread 2.3.4
LGE Version LGP990-V20r
Kernel version 2.6.32.9
I've tried so far:
- rebooting phone and pc
- factory reset phone
- Use other pc's => didn't work
- Connect a samsung phone to my pc with my LG cable => did work
- uninstall and reinstall all the necessary drivers
- mass storage mode on and off
- Installed android SDK and looked for adb devices, none shown
- phone doesn't show in the computers device manager either
Although when I do connect the phone it starts charging and if I go to the tethering settings it does recognize the fact that it is connected through USB.
So why can't I get my PC to recognize the phone.
I really need it cause I would like to root my phone to install a custom ROM.
I have tried rooting it with Gingerbreak as well, but that doens't seem to work either.
Thanks for the help
I just made a recovery.log in CWM:
http://pastebin.com/yJw6LEmf
It mentions something about USB in the bottom. Maybe it's a software issue after all?
Sent from my LG Optimus 2X

[Q] O2X bricked after restoring from nandroid backup? [Linux-related]

Hi there, honored experts!
Today I got my precious Optimus Speed bricked, after I successfully restored a recent nandroid backup.
I've been happily running paranoid android for the last months, and often updated the phone with the help of goo.im manager. Today I did a full factory-reset after the CWM upgrade-process, to get rid of the old "disappearing keyboard"-bug. I backed up all my apps and data with superbackup and titanium-backup, and even created an online nandroid-backup (freshly updated nandroid-scripts and patch for my device).
After the reset I had issues to restore everything, since ti-backup often got stuck in batch-restore-processes. Because I couldn't stop the stuck process, it required me to soft-reboot the device a few times. And in the end, it failed to boot.
So I went into CWM, and restored my nandroid-backup. This went fine, and no errors were reported. But after soft-rebooting it, it only showed the LG-Logo-Screen, and nothing else happened. So I tried to get back into CWM - with no luck .
I've tried every possible key-combination I could find, and the only mode I can bring my device into is "S/W Upgrade". In this mode it is recognized by my laptop (running Linux), but rustys recovery fails, because nvflash reports:
Code:
sh ./flash-recovery-ext.sh
Nvflash started
USB device not found
even though lsusb shows:
Code:
# lsusb
Bus 001 Device 017: ID 1004:6000 LG Electronics, Inc. KU330/KU990/VX4400/VX6000
I'm fresh out of ideas - maybe one of you can help me out? Otherwise the only thing I could try now is to turn it back in where I bought it.
I'm no expert at these matters,but I can tell you from my experience because I bricked mine P990 two times and was able to bring it back to life.
In both instances I used Smartflash, found V30a ICS ROM for it and flashed it over it, and it came back to life.
But when you do this,you will have ICS bootloader and you won't be able to install PA or CM since they work on the old bootloader.
Or you can flash it to the stock Gingerbread ROM https://hotfile.com/dl/168874678/8ea13eb/NVFlash_LGP990_V20Q_EuroOpen.7z.html
And I would recommend reinstalling nv flash drivers before,just in case the error is on your computer. http://www.mediafire.com/?cdgwwgkdozht8pw
Also, try All in one kit, http://forum.xda-developers.com/showthread.php?t=2020737 maybe it will help you. I repaired my bricked phone with it a lot of times. Its very easy to use as everything is explained there.
Jasper_bin
this device is 99% unbrickable
just go ahead with the AIOT by SPYROSK (this guy is a silent killer with amazing skills)....link in my signature
it works like a magic....real magic if you read the opening post and do it properly
Thanks
Hi Obersoldat,
I'm currently on the new BL - PA has a spin for the old, and one for the new BL. Is smartflash a windows-binary? Since I currently have no access to a windows-machine :-/.
Hi Make1 and Sreeprajay,
thanks for your recommendation. I'll also hit that thanks button if it helps me solve this, but first I've got two questions:
1st: As said above, I currently have no access to a windows-machine. Therefore I wanted to try working this out with nvflash on Linux. AFAIK this should be possible, even though there would be no nice menu-system. The question is if there's a difference due to the special drivers on windows which are mentioned everywhere? I ask that, because I've successfully rooted my buddies TP-Tablet on Linux with adb, and without any special drivers (which were said to be mandatory on windows).
2nd: What am I aiming for in Spyrosks AIOT? Instantly I'd think option 2B (Change Recovery with NVFlash) might help me. As in ProgMaqs Full-Brick-Repair. Then I'd look into the batch-Scripts, and simply manually execute the needed Steps.
Ok, so I dug up my old windows-tower from the attic, soldered a power-cord that I was missing, and fired it up. Took me more than 2 hours - thats what I meant with "no access to a windows-machine".
I ran Spyrosks AIOT, but no luck . The only possible ways to save this phone, are IMHO the nvflash based methods. But nvflash on windows reports the same error: "USB device not found".
Yes - I installed the driver out of the AOIT - but it seems that it cannot be activated for my phone. I think it's not in the right state to be recognized as a device that would need that driver, so windows won't activate it.
Attached is a screenshot of how the phone appears in my Device-Manager when connected in "S/W Upgrade"-mode.
Do you still think this phone can be saved somehow? I had high hopes as I read that this phone is nearly unbrickable
Come on, please someone help me. I'm not trying to be lazy here, or have someone else do the searching/thinking for me. I just can't figure out how to solve this - propably due to a lack of experience.
I don't think this is a simple problem - but there must be a reason why that phone is said to be 99% unbrickable. I hope I'm not the other 1% in this case.
Anyone?
I would have known what to do if the pc recognized your phone when you've installed drivers because almost exact problem happened to me few days ago.
Okay, now I will suggest random things well, I'm just trying to help :/
I suppose cwm isn't working?
Then about S/W Upgrade mode, have you installed APX drivers? Because when you connect phone in S/W upgrade mode with APX drivers installed then Device manager shows no errors.
You also mentioned that you restored a backup so it means you have latest backup of your system which you wanted to use. Tell me if I'm not correct. Then full wipe of your phone will fix everything, you will just flash a new rom, do the rooting stuff again and then you can restore your backup again.
maybe its because you are on linus, try restoring a STOCK GB KDZ if you are on the old layout, if you are in the new layout use a official LG smartflash, try that on windows and use AIO Toolkit !
Hey, thanks a lot! Actually the last Tip did the Trick!
After I downloaded and installed the full LG phone suite, I was able to restore the phone with the official LG support-tool. During the installation of the PC-Suite one or two new drivers were installed, which then lead to the phone beeing correctly recognized by the Windows 7 on the PC.
So to sum that up, and clarify the questions I brought up earlier:
Can the windows Drivers do more than what the native ones on Linux?
Absolutely yes! Only the drivers which came with the PC-Suite made my PC recognize the P990, which it didn't do before. Propably even the special drivers which come with Spyrosks AIOT depend on them (correct me if thats not true).
Can I restore my bricked phone with only Spyrosks AIOT?
In my case that did not work. Even after installing the PC-Suite and its drivers (including the support-tool drivers) the nvflash based methods in spyrosks AIOT did not find my device, which was connected over USB. But LGs support-tool did, and revived the device .
Hope that helps other people in my situation. The legendary unbrickability of this thing is proven once again
Thanks to all of you (Yesyesyes - I'll hit that button right away!)

A Hot Mess, Need Help - M7, S-On, Trouble with ADB

The Whole Story:
So yesterday I successfully upgraded my HTC One M7 to Lollipop for the first time. I was very excited because the UI is awesome. However, my cellular service didn't work. I read that this is because the firmware was out of date.
In trying to update said firmware, somehow I wiped the internal storage of my device (I know...) including my backup. But that doesn't really matter that much... because while using the HTC One Toolkit I also managed to idiotically turn S-ON! So I can't get into recovery anyway...
So I've been trying to get S-Off with firewater because if I can just get into recovery I can install an older backup I have from last year and then get a new ROM and try this circus all over again in a few weeks when my brain is hopefully not dumb. And that is where I've run into trouble with adb.
In the adb console I can see my phone's serial but it always is listed as offline. In fastboot, however, it is listed fine. I have tried so so many things, but at this point I'll try and re-try anything all over again just to get this to work.
Honestly, I'm surprised this thing isn't brIcked by now with all the f--k ups I've had in the past two days.
TL; DR: I royally messed up and accidentally turned S-On. Not sure if it is related, but now adb lists my HTC as offline while fastboot seems to recognize it fine. I can also access all my files on the phone from Windows.
One thing that (I think) is an important detail is that I cannot seem to get the RSA prompt to appear when I plug my phone into Windows with debugging mode on. I have never used this computer with this phone before, so I know it isn't saved or anything (maybe it's worth clearing the RSA keys anyway?).
What I've tried so far:
-Downloaded latest drivers from HTC (2.0.7.29 from 3/3/15)
-Installed Android Studio and updated Google USB Drivers and Platform Tools
-Rebooted Computer and Phone Multiple times
-Unplugged and re plugged USB cord
-Unchecked and rechecked USB debugging
Please...Please, I desperately need people who are better at this than I am.
Youngtusk said:
The Whole Story:
So yesterday I successfully upgraded my HTC One M7 to Lollipop for the first time. I was very excited because the UI is awesome. However, my cellular service didn't work. I read that this is because the firmware was out of date.
In trying to update said firmware, somehow I wiped the internal storage of my device (I know...) including my backup. But that doesn't really matter that much... because while using the HTC One Toolkit I also managed to idiotically turn S-ON! So I can't get into recovery anyway...
So I've been trying to get S-Off with firewater because if I can just get into recovery I can install an older backup I have from last year and then get a new ROM and try this circus all over again in a few weeks when my brain is hopefully not dumb. And that is where I've run into trouble with adb.
In the adb console I can see my phone's serial but it always is listed as offline. In fastboot, however, it is listed fine. I have tried so so many things, but at this point I'll try and re-try anything all over again just to get this to work.
Honestly, I'm surprised this thing isn't brIcked by now with all the f--k ups I've had in the past two days.
TL; DR: I royally messed up and accidentally turned S-On. Not sure if it is related, but now adb lists my HTC as offline while fastboot seems to recognize it fine. I can also access all my files on the phone from Windows.
One thing that (I think) is an important detail is that I cannot seem to get the RSA prompt to appear when I plug my phone into Windows with debugging mode on. I have never used this computer with this phone before, so I know it isn't saved or anything (maybe it's worth clearing the RSA keys anyway?).
What I've tried so far:
-Downloaded latest drivers from HTC (2.0.7.29 from 3/3/15)
-Installed Android Studio and updated Google USB Drivers and Platform Tools
-Rebooted Computer and Phone Multiple times
-Unplugged and re plugged USB cord
-Unchecked and rechecked USB debugging
Please...Please, I desperately need people who are better at this than I am.
Click to expand...
Click to collapse
maybe flashing the boot.img and stock recovery of the firmware you are into will help you!
eyeyousee said:
maybe flashing the boot.img and stock recovery of the firmware you are into will help you!
Click to expand...
Click to collapse
Thanks for the tip. Does flashing a boot.img and stock recovery require adb? Currently, that is where my main setback is.
If it doesn't require adb, can you point me into the direction of the right keywords to Google to find out how to do that?

USB not working as expected under custom ROMs

Hello everybody
I'm having a problem. After ditching the first custom ROM (Pure Nexus) because Sygic App kept crashing, I wanted to go back to stock but noticed that I couldn't connect to my windows box via USB anymore. It would display the Nexus 6 device with an warning sign in device Manager. Since it had worked on stock it can't be a hardware issue.
So going stock through fastboot was out because no device was found. ADB also didn't find anything. So after going to LightROM, Sygic worked but I still can't connect via USB. The Nexus 6 is displayed in Windows Explorer but no storage underneath it. ADB still doesn't work and Wug's toolkit, as a consequence, can't work with the device either. I can't fiddle with USB options either, since LightROM doesn't pop up a USB notification and I just can't find the options in system settings.
So I'd like to flash via TWRP, which is installed, but for the life of me I can't find any of the TWRP flashable stock ROMs I see mentioned on the net. Also, there ought to be ZIP update packages since OTA doesn't work on rooted devices. Where can I find those?
Thank you
Marco2G said:
Hello everybody
I'm having a problem. After ditching the first custom ROM (Pure Nexus) because Sygic App kept crashing, I wanted to go back to stock but noticed that I couldn't connect to my windows box via USB anymore. It would display the Nexus 6 device with an warning sign in device Manager. Since it had worked on stock it can't be a hardware issue.
So going stock through fastboot was out because no device was found. ADB also didn't find anything. So after going to LightROM, Sygic worked but I still can't connect via USB. The Nexus 6 is displayed in Windows Explorer but no storage underneath it. ADB still doesn't work and Wug's toolkit, as a consequence, can't work with the device either. I can't fiddle with USB options either, since LightROM doesn't pop up a USB notification and I just can't find the options in system settings.
So I'd like to flash via TWRP, which is installed, but for the life of me I can't find any of the TWRP flashable stock ROMs I see mentioned on the net. Also, there ought to be ZIP update packages since OTA doesn't work on rooted devices. Where can I find those?
Thank you
Click to expand...
Click to collapse
If Fastboot cannot connect in the bootloader, it is nothing to do with the ROM. The ROM and bootloader are completely separate, so it is likely a USB hardware issue, or driver issue. Hardware could be PC Port, Nexus port or cable.
I recommend addressing your fastboot issue first rather than trying to work around it.
danarama said:
If Fastboot cannot connect in the bootloader, it is nothing to do with the ROM. The ROM and bootloader are completely separate, so it is likely a USB hardware issue, or driver issue. Hardware could be PC Port, Nexus port or cable.
I recommend addressing your fastboot issue first rather than trying to work around it.
Click to expand...
Click to collapse
I'm almost tempted to walk away from this whistling like I was never even here...
Even though I unlocked the device in fastboot, I completely forgot you'd have to boot into fastboot in order for that to work. As such I should have put this in the noob question thread. I do appologize for wasting your time so spectacularly.
Obviously, as soon as I did boot into fastboot, flashing stock worked like a charm.
Sorry 'bout that.
Marco2G said:
I'm almost tempted to walk away from this whistling like I was never even here...
Even though I unlocked the device in fastboot, I completely forgot you'd have to boot into fastboot in order for that to work. As such I should have put this in the noob question thread. I do appologize for wasting your time so spectacularly.
Obviously, as soon as I did boot into fastboot, flashing stock worked like a charm.
Sorry 'bout that.
Click to expand...
Click to collapse
Haha, no worries. Sometimes it is hard to see the wood for the trees.

Categories

Resources