Pretty sure I know the answer to this, but before I finally through in the towel or rather my Nexus 4 against the wall... I will defer to the resident experts. So, I attempt to install Liquid Smooth 4.0 and after going into TWRP I did a wipe and installed it. I was running the previous official build of Liquid Smooth. I also install gapps for Lollipop. Everything began to boot and then the phone said something to the like apps are starting and it stayed on that screen for a full 8 hours. I went back into recovery and tried to restore from my previous Liquid Smooth. Exact same thing happened. After several attempts I did the unmentionable. I did a full wipe. I know it was a dumb*ss move now. My phone does NOT connect to ANY PC. Every time the PC says device not recognized. Now I have now OS. Only TWRP. I tried sideload, but computer does not recognize device. I bought usb-otg adapter, but found out that usb-otg does not work with Nexus 4. So.... should I throw in the towel? My phone now a fancy paperweight?
Many thanks!
kjtay said:
Pretty sure I know the answer to this, but before I finally through in the towel or rather my Nexus 4 against the wall... I will defer to the resident experts. So, I attempt to install Liquid Smooth 4.0 and after going into TWRP I did a wipe and installed it. I was running the previous official build of Liquid Smooth. I also install gapps for Lollipop. Everything began to boot and then the phone said something to the like apps are starting and it stayed on that screen for a full 8 hours. I went back into recovery and tried to restore from my previous Liquid Smooth. Exact same thing happened. After several attempts I did the unmentionable. I did a full wipe. I know it was a dumb*ss move now. My phone does NOT connect to ANY PC. Every time the PC says device not recognized. Now I have now OS. Only TWRP. I tried sideload, but computer does not recognize device. I bought usb-otg adapter, but found out that usb-otg does not work with Nexus 4. So.... should I throw in the towel? My phone now a fancy paperweight?
Many thanks!
Click to expand...
Click to collapse
Under device manager, what is listed as your phone?
Ajxx16 said:
Under device manager, what is listed as your phone?
Click to expand...
Click to collapse
Unknown Device... It is worth noting that I have used Wugs Toolkit and followed every set of directions to a T. This includes a PC that that has never had my phone in it before. Followed all the steps before I even tried to connect. Also, both PC machine indicate that I have installed the most update driver.
I have zero experience with that toolkit, but have you tired every usb port on your computer and possibly another computer? Your phone is far from gone, this just sounds like a driver issue to me. Is your phone recognizable in bootloader?
I don't actually have this phone but my wife does, as well as my brother. Just the other night my wife's was showing up unrecognized, all I had to do was swap usb ports on the computer.
Ajxx16 said:
I have zero experience with that toolkit, but have you tired every usb port on your computer and possibly another computer? Your phone is far from gone, this just sounds like a driver issue to me. Is your phone recognizable in bootloader?
I don't actually have this phone but my wife does, as well as my brother. Just the other night my wife's was showing up unrecognized, all I had to do was swap usb ports on the computer.
Click to expand...
Click to collapse
I have tried all usb ports and a different usb cord. My OS is gone, so I was hoping to find some way to install a rom or stock. I am at a loss!
How about the bootloader? If you have that feature you can flash stock image
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
Volume down + power incase you didn't know.
Ajxx16 said:
How about the bootloader? If you have that feature you can flash stock image
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
Volume down + power incase you didn't know.
Click to expand...
Click to collapse
I do if I understand the term correctly. I am at the android "start" screen and underneath the android it says
Fastboot Mode
Product_Name - mako
lock state - unlocked
Now what?
Connect it to your computer, and I assume you have fastboot and adb set up correctly. In command prompt type fastboot devices and see if your phone is listed, should give the serial and say fastboot next to that
Not sure if I know how to set up adb correctly... as far as fastboot goes.. I assume that is set up correctly. Would adb work if the PC doesn't recognize my phone?
Well adb is of no use here so I wouldn't worry about it. Is fastboot recognized?
Ajxx16 said:
Well adb is of no use here so I wouldn't worry about it. Is fastboot recognized?
Click to expand...
Click to collapse
Don't mean to sound like an idiot (may be too late for that), but do you mean fastboot recognized on my PC when I plug in my phone? Or does is say fastboot on my phone? PC does not recognize my phone, but it does say fastboot enabled on my phone.
Alright so follow these instructions.
http://forum.xda-developers.com/showthread.php?t=2317790
Get that set up and in the mean time download either the 4.4.4 or 5.0 image here.
https://developers.google.com/android/nexus/images
Once you finish the adb fastboot setup, while your phone is in the boot loader screen you should be able to type into a command prompt "fastboot devices" and your device should be listed.
Ajxx16 said:
Alright so follow these instructions.
http://forum.xda-developers.com/showthread.php?t=2317790
Get that set up and in the mean time download either the 4.4.4 or 5.0 image here.
https://developers.google.com/android/nexus/images
Once you finish the adb fastboot setup, while your phone is in the boot loader screen you should be able to type into a command prompt "fastboot devices" and your device should be listed.
Click to expand...
Click to collapse
I can't get the PC to recognize the phone. The phone is in fastboot mode. It is looking mighty grim!
I'm fairly certain this is just a simple fix on the drivers on your computer, you have access to recovery and boot loader, your phone is far from gone. I'm out atm so I'll check in with ya a little later.
Ajxx16 said:
I'm fairly certain this is just a simple fix on the drivers on your computer, you have access to recovery and boot loader, your phone is far from gone. I'm out atm so I'll check in with ya a little later.
Click to expand...
Click to collapse
An easy fix, do you have a nandroid backup? Just restore it in twrp. As mentioned, you're far from bricked and sol. If you can get into the bootloader it's recoverable.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
An easy fix, do you have a nandroid backup? Just restore it in twrp. As mentioned, you're far from bricked and sol. If you can get into the bootloader it's recoverable.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Would you happen to have a link for an ADB driver he could install? Not sure of the n4 requires something specific.
Ajxx16 said:
Would you happen to have a link for an ADB driver he could install? Not sure of the n4 requires something specific.
Click to expand...
Click to collapse
I'd Google 15 second adb install xda. That'll set yo adb and fastboot on the pc and includes drivers
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I'd Google 15 second adb install xda. That'll set yo adb and fastboot on the pc and includes drivers
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Installed 15 second adb and still nothing recognized on my PC. Still have "fastboot mode" in red on my phone???
kjtay said:
Installed 15 second adb and still nothing recognized on my PC. Still have "fastboot mode" in red on my phone???
Click to expand...
Click to collapse
Open up device manager, look for the phone, right click and hit update driver, then hit let !e choose driver, then select from list, you shpuld see something along the lines of ADB interface. Select that and install and try fastboot devices in command prompt again.
Ajxx16 said:
Open up device manager, look for the phone, right click and hit update driver, then hit let !e choose driver, then select from list, you shpuld see something along the lines of ADB interface. Select that and install and try fastboot devices in command prompt again.
Click to expand...
Click to collapse
I am pretty certain I have the proper drivers installed on 3 computers. Not a single one recognizes the device. I suppose it is possible that it is a hardware issue? If I can figure a way to the computer to recognize the phone I am certain I can save it. Right NOTHING has worked.
Related
Hi
Tried to flash a new kernel and all seemed ok (flashed phones and nexus 7 few times now) when I came out of flashing I hit a bootloop, I though nothing of it and tried to restart....same issue, so next I tried to go into cw recovery, no joy, it will not show again.
I can power/vol keys to android fastboot screen with start power restart boot and so on but if I choose recovery nothing happens, I am stuck with either a bootloop or stuck on android fastboot screen and not able to move from either.
I have tried the toolkit and most other things but the problem is it cannot see my nexus 7, even after installing drivers and so on the toolkit (top right) does not list my nexus as found, because of this I cannot reflash any stock firmware/recover/reflash cwr.
Not sure how I can get around this if my pc cannot see the nexus 7.
Thanks for any help
voodoochild2008 said:
Hi
Tried to flash a new kernel and all seemed ok (flashed phones and nexus 7 few times now) when I came out of flashing I hit a bootloop, I though nothing of it and tried to restart....same issue, so next I tried to go into cw recovery, no joy, it will not show again.
I can power/vol keys to android fastboot screen with start power restart boot and so on but if I choose recovery nothing happens, I am stuck with either a bootloop or stuck on android fastboot screen and not able to move from either.
I have tried the toolkit and most other things but the problem is it cannot see my nexus 7, even after installing drivers and so on the toolkit (top right) does not list my nexus as found, because of this I cannot reflash any stock firmware/recover/reflash cwr.
Not sure how I can get around this if my pc cannot see the nexus 7.
Thanks for any help
Click to expand...
Click to collapse
try to flash recovery again via fastboot...or doesnt pc recognize divice at all?
S.R
shivasrage said:
try to flash recovery again via fastboot...
S.R
Click to expand...
Click to collapse
Hi
I cannot flash anything. On the fastboot screen I can scroll up and down powr off/start/recovery....if I choose any (apart from power off) nothing happens.
When I hook it up to my pc it cannot see it, nexus 7 toolkit also cannot see it, it does not list it as found so I cannot flash anything on to it, if I try it just says waiting for device, tried other things and same thing either waiting for device or asks if fastboot installed.
voodoochild2008 said:
Hi
I cannot flash anything. On the fastboot screen I can scroll up and down powr off/start/recovery....if I choose any (apart from power off) nothing happens.
When I hook it up to my pc it cannot see it, nexus 7 toolkit also cannot see it, it does not list it as found so I cannot flash anything on to it, if I try it just says waiting for device, tried other things and same thing either waiting for device or asks if fastboot installed.
Click to expand...
Click to collapse
f****
have you tried flashing factory image from google site.with flash all-sh?
shivasrage said:
f****
have you tried flashing factory image from google site.with flash all-sh?
Click to expand...
Click to collapse
I have a image ready but not able to flash....but what is flash all-sh? trying to search for it, is it a tool to force flash?
voodoochild2008 said:
I have a image ready but not able to flash....but what is flash all-sh? trying to search for it, is it a tool to force flash?
Click to expand...
Click to collapse
no its included in the factory image to flash all i one so it looks like for the nexus 4:
flash-all .....its a windows batch image with all included.... try this
S:R.
shivasrage said:
no its included in the factory image to flash all i one so it looks like for the nexus 4:
flash-all .....its a windows batch image with all included.... try this
S:R.
Click to expand...
Click to collapse
Thanks....but still get waiting for device, thats the problem, nothing seems to see it so I cannot flash anything to it.
You are already at the bootloader screen. Use your computer to fastboot flash a new kernel. Being able to get into recovery has nothing to do with it. You screwed it up flashing a kernel. Its likely thats all you need to fix it. Flash a new one with fastboot.
You are already at the bootloader screen. Use your computer to fastboot flash a new kernel. Being able to get into recovery has nothing to do with it. You screwed it up flashing a kernel. Its likely thats all you need to fix it. Flash a new one with fastboot.
i thought the same as you but fastboot isn recognizig N7 anymore....always wating for device....
Hemidroids said:
You are already at the bootloader screen. Use your computer to fastboot flash a new kernel. Being able to get into recovery has nothing to do with it. You screwed it up flashing a kernel. Its likely thats all you need to fix it. Flash a new one with fastboot.
Click to expand...
Click to collapse
Downloaded the fastboot exe but unsure what it needs to work as when I click on it a run box opens for like half a second and then closes, dont get a chance to read what it says, think I will have to read up on it.
[/COLOR]
voodoochild2008 said:
Downloaded the fastboot exe but unsure what it needs to work as when I click on it a run box opens for like half a second and then closes, dont get a chance to read what it says, think I will have to read up on it.
Click to expand...
Click to collapse
read this... i hope you can follwow that easily like me...
greets S.R.
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
voodoochild2008 said:
Downloaded the fastboot exe but unsure what it needs to work as when I click on it a run box opens for like half a second and then closes, dont get a chance to read what it says, think I will have to read up on it.
Click to expand...
Click to collapse
EXE? doh.......Windows.......sorry cant help.
shivasrage said:
[/COLOR]
read this... i hope you can follwow that easily like me...
greets S.R.
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Click to expand...
Click to collapse
Tried some of that already but will try again tomorrow.
Thanks for help with this and will post tomorrow if I can sort it. cheers
I hope this instructions can help you a little bit...but if it fails don´t be angry its all I can think of ...at this time ....merry christmas
S.R.
http://forum.xda-developers.com/showthread.php?p=31931117:D
Sent from my Nexus 7 using xda premium
Well after using bits of jrom flasher and nexus toolkit I got it working again, main issue was making the tablet seen, abd and fastboot would not show device.
All up and running again THANKS TO ALL WHO HELPED
voodoochild2008 said:
Well after using bits of jrom flasher and nexus toolkit I got it working again, main issue was making the tablet seen, abd and fastboot would not show device.
All up and running again THANKS TO ALL WHO HELPED
Click to expand...
Click to collapse
How did you get it to work? I have problem getting my device to be recognized. Stuck on boot loop too..
Hey man, how did you get your computer to recognize your device? Would be great to finally fix mine as this is the same exact problem -- computer doesn't recognize it even though in fastboot.
Quacker245 said:
Hey man, how did you get your computer to recognize your device? Would be great to finally fix mine as this is the same exact problem -- computer doesn't recognize it even though in fastboot.
Click to expand...
Click to collapse
I don't understand exactly what you are trying to do, sorry: you said the pc does not see the nexus, "even thought in fastboot".. If you say even thought, it seems to me that you are able to access Android itself or maybe recovery? In that case I can't see the issue.. Sorry my fault, non english mother tongue
But, if have the device soft bricked and you are able to enter ONLY the bootloader (that is what we call often fastboot), then you should start to remove the not working fastboot drivers installed into your PC: launch the nexus in fastboot mode, go to Device Manager into your PC and search for a driver with an yellow exclamation point. This issue is very common so I hope that you have it, too.. So, uninstall that driver, then unlink the nexus from your PC; after a few seconds attach it to another USB port and see if Windows install a driver (it should). If this new driver doesn't work, too, or if Windows does no install any, try this one: http://forum.xda-developers.com/showthread.php?t=1426502
Hope it helps, let us know, see you!
EDIT: also, if you still have no luck, you should find a Linux or Mac PC/laptop and download the adb/fastboot binary files for that OS; this will definitively solve your driver issue ( @#ò#@!"@# Winzozz )
brainvision said:
I don't understand exactly what you are trying to do, sorry: you said the pc does not see the nexus, "even thought in fastboot".. If you say even thought, it seems to me that you are able to access Android itself or maybe recovery? In that case I can't see the issue.. Sorry my fault, non english mother tongue
But, if have the device soft bricked and you are able to enter ONLY the bootloader (that is what we call often fastboot), then you should start to remove the not working fastboot drivers installed into your PC: launch the nexus in fastboot mode, go to Device Manager into your PC and search for a driver with an yellow exclamation point. This issue is very common so I hope that you have it, too.. So, uninstall that driver, then unlink the nexus from your PC; after a few seconds attach it to another USB port and see if Windows install a driver (it should). If this new driver doesn't work, too, or if Windows does no install any, try this one: http://forum.xda-developers.com/showthread.php?t=1426502
Hope it helps, let us know, see you!
EDIT: also, if you still have no luck, you should find a Linux or Mac PC/laptop and download the adb/fastboot binary files for that OS; this will definitively solve your driver issue ( @#ò#@!"@# Winzozz )
Click to expand...
Click to collapse
Hi sorry for not being clear. Basically I am only allowed to access the bootloader and my device is soft-bricked. I'm pretty sure I tried uninstalling and reinstalling the drivers about a year ago when I originally did it, but I'll try again and let you know. Thanks!
Hi folks,
My wife dropped her 2-week old Nexus 4 which caused part of the front glass to crack and portions of the touchscreen to be dead, so we had to send it into LG for repairs (at quite a price tag). Fine.
So we get it back, I turn it on, and it's in something called "FTM Mode" (file transfer mode, I think)? I can't seem to get it out of it.
Things I've tried:
Rebooting (have to hold the power button down for 5-10 sec).
Factory data reset (the settings are available through the notification menu in FTM Mode).
In recovery mode:
[*]Start (goes right back to FTM Mode)
[*]Power off (duh)
[*]Restart bootloader (gets me right back to the same screen)
[*]Recovery mode (gives me a little android with its stomach open, a red exclamation point, and says "No command.")
I attempted LG support, but they asked me to do a few of these (after asking me to hit the "home" button...), then told me to mail it back to them because they probably have to flash it.
So, the obvious question: how the hell can I get out of FTM Mode?
Secondary question: if none of the above worked and I do have to flash the OS, can I flash it myself to default Jellybean? Any idiot-friendly step-by-step guides out there?
Here you are! (I was the one talking to you on Reddit)
Since you can get to fastboot you can just flash the stock image files and you should be fine! The toolkit is in the original dev section but you cannot download the images from it anymore. A few people here have the images though so hopefully someone will pop up with them shortly
Sent from my Nexus 4 using Tapatalk 2
joshnichols189 said:
Here you are! (I was the one talking to you on Reddit)
Since you can get to fastboot you can just flash the stock image files and you should be fine! The toolkit is in the original dev section but you cannot download the images from it anymore. A few people here have the images though so hopefully someone will pop up with them shortly
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Haha!
I have located an image... just need to figure out the fastboot stuff. I'm not a terribly adventurous user, you see.
Depressio said:
Haha!
I have located an image... just need to figure out the fastboot stuff. I'm not a terribly adventurous user, you see.
Click to expand...
Click to collapse
No worries! You can use the toolkit without knowing fastboot, I just recommended learning it in case you ever need to flash without it. I believe after you download the toolkit there will be a folder you can place the stock image into then you can use the toolkit to flash the image from that folder. I'm not 100% what folder that is though but I believe the name makes it fairly obvious if you look for it
Sent from my Nexus 4 using Tapatalk 2
joshnichols189 said:
No worries! You can use the toolkit without knowing fastboot, I just recommended learning it in case you ever need to flash without it. I believe after you download the toolkit there will be a folder you can place the stock image into then you can use the toolkit to flash the image from that folder. I'm not 100% what folder that is though but I believe the name makes it fairly obvious if you look for it
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Unfortunately, I haven't even been able to install the bloody USB driver, so fastboot/adb can't even see the device. I've described by problem here. I think the source issue is what LG did during repairs... the device is named "Full JellyBean on Mako" instead of something like "Nexus 4", so the drivers in that post aren't being recognized by Windows as valid for the device. At least that's my guess.
OK, got it all fixed.
This post was incredibly useful. Once I got the USB drivers installed and fastboot recognizing the device (oddly, adb wasn't able to), it was extremely smooth unlocking the bootloader and flashing the image.
Thanks!
Depressio said:
OK, got it all fixed.
This post was incredibly useful. Once I got the USB drivers installed and fastboot recognizing the device (oddly, adb wasn't able to), it was extremely smooth unlocking the bootloader and flashing the image.
Thanks!
Click to expand...
Click to collapse
For future reference ADB only works in recovery and when booted into android, never in boot loader. Bit glad you got it working
Sent from my Nexus 4 using Tapatalk 2
drives
Depressio said:
OK, got it all fixed.
This post was incredibly useful. Once I got the USB drivers installed and fastboot recognizing the device (oddly, adb wasn't able to), it was extremely smooth unlocking the bootloader and flashing the image.
Thanks!
Click to expand...
Click to collapse
how did you can install the adb drivers,have same problem
ramonrecio said:
how did you can install the adb drivers,have same problem
Click to expand...
Click to collapse
plug your phone into your computer, then restart it in bootloader mode. the drivers will automatically install
same
hi,thank you,ok i can go to fastboot mode and select restart bootloader but when i hit power ,they turn off for a second and go back to fastboot mode initial page ,the pc do the sound when disconnect and connect back to usb pc,but that's it,no drivers installation ,what can i do!! this make me crazy,please help
I just got my Nexus 4 and installed SDK and drivers on PC. OK, so now I boots my phone into fastboot mode, I connected it to my PC, entered"fastboot devices" in command line, no problem, I can see the device with the ID.
But when I entered"fastboot oem unlock", the command line it says" FAILED <command write failed <Unknown error>>". And the phone stays in fastboot mode without any pop-up.
I use USB 2.0 ports on the backside of the computer. Also USB 2.0 on my laptop. None of them work.
I tried to factory set the phone, restart computer and phone, change to another computer, none of them worked. Maybe I should contact Google to ask for an exchange because mine can not be unlocked?
Any help is deeply appreciated.
Utahnewbie said:
I just got my Nexus 4 and installed SDK and drivers on PC. OK, so now I boots my phone into fastboot mode, I connected it to my PC, entered"fastboot devices" in command line, no problem, I can see the device with the ID.
But when I entered"fastboot oem unlock", the command line it says" FAILED <command write failed <Unknown error>>". And the phone stays in fastboot mode without any pop-up.
I use USB 2.0 ports on the backside of the computer. Also USB 2.0 on my laptop. None of them work.
I tried to factory set the phone, restart computer and phone, change to another computer, none of them worked. Maybe I should contact Google to ask for an exchange because mine can not be unlocked?
Any help is deeply appreciated.
Click to expand...
Click to collapse
Yeah, GOOGLE will be happy to replace your phone because you cannot unlock your bootloader!? Are u serious? Make sure USB debugging is enabled under developer options...
There is a app in the play store that unlocks bootloader for nexus 4.
Sent from my Nexus 4
myturbo1 said:
There is a app in the play store that unlocks bootloader for nexus 4.
Sent from my Nexus 4
Click to expand...
Click to collapse
It requires root access. Without being able to unlock bootloader, I can't root my N4
BigDig said:
Yeah, GOOGLE will be happy to replace your phone because you cannot unlock your bootloader!? Are u serious? Make sure USB debugging is enabled under developer options...
Click to expand...
Click to collapse
They probably would, actually. The ability to easily unlock the bootloader is a feature of Nexus devices.
BigDig said:
Make sure USB debugging is enabled under developer options...
Click to expand...
Click to collapse
Only applies to ADB, not fastboot
Have you got the latest SDK files? Have you got the latest bootloader?
Utahnewbie said:
I just got my Nexus 4 and installed SDK and drivers on PC. OK, so now I boots my phone into fastboot mode, I connected it to my PC, entered"fastboot devices" in command line, no problem, I can see the device with the ID.
But when I entered"fastboot oem unlock", the command line it says" FAILED <command write failed <Unknown error>>". And the phone stays in fastboot mode without any pop-up.
I use USB 2.0 ports on the backside of the computer. Also USB 2.0 on my laptop. None of them work.
I tried to factory set the phone, restart computer and phone, change to another computer, none of them worked. Maybe I should contact Google to ask for an exchange because mine can not be unlocked?
Any help is deeply appreciated.
Click to expand...
Click to collapse
Try nexus 4 toolkit
Try a different USB cable if you haven't already.
Sent from my Nexus 4 using xda premium
Hy There i finally got my nexus 4 two days ago, i tried to search Google about bootloader limitation if there is any? Im pretty freaked cause i previously used xperia S with bootloader impossible to unlock, due to a carrier lock.
So is there a metod to check if bootloader of my N4 is possible to unlock like in hidden menu *#*#4636#*#* wich i cheked but i dont know to what i should pay attention? or is there the other way to chek .
I know that unlocking and rooting should be possible in N4 but i hope u understand my concern cause i bought N4 trough carrier contract and a negative expirience with xperia s, thanx
grgana said:
Hy There i finally got my nexus 4 two days ago, i tried to search Google about bootloader limitation if there is any? Im pretty freaked cause i previously used xperia S with bootloader impossible to unlock, due to a carrier lock.
So is there a metod to check if bootloader of my N4 is possible to unlock like in hidden menu *#*#4636#*#* wich i cheked but i dont know to what i should pay attention? or is there the other way to chek .
I know that unlocking and rooting should be possible in N4 but i hope u understand my concern cause i bought N4 trough carrier contract and a negative expirience with xperia s, thanx
Click to expand...
Click to collapse
No, a Nexus device will ALWAYS have an unlockable bootloader.
I don't know if anyone has said this yet, but are you sure you're in fastboot mode when you type: fastboot oem unlock?
that command only works from the bootloader, not from inside recovery or when your system is booted up.
---------- Post added at 03:53 PM ---------- Previous post was at 03:51 PM ----------
Utahnewbie said:
It requires root access. Without being able to unlock bootloader, I can't root my N4
Click to expand...
Click to collapse
That's not entirely true with something like the motochopper method.
kbeezie said:
That's not entirely true with something like the motochopper method.
Click to expand...
Click to collapse
Does motochopper work on the nexus 4 bro? Cause id love to simply root without unlocking bootloader and such (im a noob) cause i used motochopper on my locked bootloader xperia tablet and so i understand it.
jimbohurt said:
Does motochopper work on the nexus 4 bro? Cause id love to simply root without unlocking bootloader and such (im a noob) cause i used motochopper on my locked bootloader xperia tablet and so i understand it.
Click to expand...
Click to collapse
Some google searches seem to suggest so, such as : http://forums.androidcentral.com/ne...hopper-root-without-unlocking-bootloader.html
And even this one in response to my own assumption that you can't without unlock (though he didn't exactly provide links, and not sure if was specific to the Nexus S and Nexus 7)
http://forum.xda-developers.com/showpost.php?p=42580735&postcount=10
As for me... I just unlocked it, easier.
kbeezie said:
Some google searches seem to suggest so, such as : http://forums.androidcentral.com/ne...hopper-root-without-unlocking-bootloader.html
And even this one in response to my own assumption that you can't without unlock (though he didn't exactly provide links, and not sure if was specific to the Nexus S and Nexus 7)
http://forum.xda-developers.com/showpost.php?p=42580735&postcount=10
As for me... I just unlocked it, easier.
Click to expand...
Click to collapse
Thanks for the response dude, when you unlocked did you use adb and stuff through android adk or did you use a toolkit?
jimbohurt said:
Thanks for the response dude, when you unlocked did you use adb and stuff through android adk or did you use a toolkit?
Click to expand...
Click to collapse
I just rebooted into the bootloader mode, hooked it up to my computer. Typed
fastboot oem unlock
There was a warning just after, accepted it.
then I downloaded the latest TWRP (2.5.0.0) for mako (Nexus 4)
fastboot flash recovery name-of-recovery.img
booted into recovery, made a backup of my Stock rom, wiped /system /data /cache, used the following while in recovery
adb push name-of-my-rom.zip /sdcard
adb push name-of-google-apps.zip /sdcard
then installed both via recovery and rebooted into the fresh new custom rom.
If I had not installed a custom rom, and I were to leave TWRP into a non-rooted stock:
TWRP would instead warn me that it doesn't appear to be rooted, and if I would like it to place SuperSu on it, it would do so, and I would reboot into the stock system, launch SuperSu where it will ask me if I would like it to reboot into recovery and install the su binary. Which it does automatically, so stock-wise that was the cleanest way for me to get rooted on stock (with an unlocked bootloader)
---------- Post added at 09:03 PM ---------- Previous post was at 08:57 PM ----------
By the way just as a recap.
fastboot works in the bootloader mode.
adb works in recovery and in normal system (with usb debugging enabled).
I apologize if this question has been answered already, but I just spent 15 minutes using the search button and could not find a response.
I just installed Matr1x v10.5 (http://forum.xda-developers.com/showthread.php?t=2007231) onto my Nexus 4 but it had JB 4.2. Based on the version notes of the thread, I assumed that it was backwards compatible with my phone and therefore installed the new version on my Nexus 4. Now every time I turn on my Nexus 4 the screen is blank. What can I do to fix this issue? Will it require a reset so that all my data is lost? Thanks.
What do you mean with '... The screen is blank'?
Can you get past the google bootanimation?
Sent from my Nexus 4 using xda app-developers app
failly said:
What do you mean with '... The screen is blank'?
Can you get past the google bootanimation?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Nope, basically once I turn it on I see the "Google" text, and then the screen goes blank as in it's black. Basically the back light is on and you can see that it's on but the background is still black.
pooq said:
Nope, basically once I turn it on I see the "Google" text, and then the screen goes blank as in it's black. Basically the back light is on and you can see that it's on but the background is still black.
Click to expand...
Click to collapse
Go into recovery and flash the stock kernel. If that doesnt work you need to do a full wipe and reflash the rom.
failly said:
What do you mean with '... The screen is blank'?
Can you get past the google bootanimation?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Chromium_ said:
Go into recovery and flash the stock kernel. If that doesnt work you need to do a full wipe and reflash the rom.
Click to expand...
Click to collapse
Theoretically, if I flash v10.0 (which accommodates JB 4.2) it should fix the issue right?
I'm at a dilemma because I do not know if there are any other ways to insert the kernel into my phone as there is no microSD option on the Nexus 4. Does anyone know how I could potentially get the file into my phone?
pooq said:
Theoretically, if I flash v10.0 (which accommodates JB 4.2) it should fix the issue right?
I'm at a dilemma because I do not know if there are any other ways to insert the kernel into my phone as there is no microSD option on the Nexus 4. Does anyone know how I could potentially get the file into my phone?
Click to expand...
Click to collapse
Can you access recovery? If yes mount your storage and you can transfer the files.
Sent from my Nexus 4 using xda app-developers app
failly said:
Can you access recovery? If yes mount your storage and you can transfer the files.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I had already tried that, but once I connected my usb into my laptop I still couldn't transfer any files over.
In the end I reset my phone to factory settings, so the display still shows "Google". Just to confirm, the reason why this logo has been displayed on my phone for a while is because it is working to restore the factory setting (e.g. OS) correct?
pooq said:
I had already tried that, but once I connected my usb into my laptop I still couldn't transfer any files over.
In the end I reset my phone to factory settings, so the display still shows "Google". Just to confirm, the reason why this logo has been displayed on my phone for a while is because it is working to restore the factory setting (e.g. OS) correct?
Click to expand...
Click to collapse
I can't tell for sure since it never happend to me but I don't think if you choose to reset your phone to factory settings it will stay at the google logo.
If you choose to reset to facory settings I think you just will boot into recovery with that an android standing with something in his belly with a loading bar.
You can try this.
1.Boot into bootloader.
2A.Flash TWRP with the fastboot command and go to step 3.
2B.Flash stock N4 image with the fastboot command and profit!
3a.Try to mount storage and transfer another rom.
3b.Restore a backup.
Hopefully this works.
Sent from my Nexus 4 using xda app-developers app
failly said:
I can't tell for sure since it never happend to me but I don't think if you choose to reset your phone to factory settings it will stay at the google logo.
If you choose to reset to facory settings I think you just will boot into recovery with that an android standing with something in his belly with a loading bar.
You can try this.
1.Boot into bootloader.
2A.Flash TWRP with the fastboot command and go to step 3.
2B.Flash stock N4 image with the fastboot command and profit!
3a.Try to mount storage and transfer another rom.
3b.Restore a backup.
Hopefully this works.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I have tried the above instructions up to step 3 because it did not work for me.
It shows the only files in my internal storage(/sdcard) are a file that says (Up A Level) and TWRP. Also, whenever I want to reboot it prompts "No OS Installed! Are you sure you wish to reboot?" At this point I am only interested in a factory reset now so that I can reinstall the initial JB 4.0 that came with the Nexus 4 and then upgrade to JB 4.3. However, whenever I do factory reset via recovery mode, I am stuck with an empty phone with the files I mentioned above.
What can I do to fix the situation? Thanks.
pooq said:
I have tried the above instructions up to step 3 because it did not work for me.
It shows the only files in my internal storage(/sdcard) are a file that says (Up A Level) and TWRP. Also, whenever I want to reboot it prompts "No OS Installed! Are you sure you wish to reboot?" At this point I am only interested in a factory reset now so that I can reinstall the initial JB 4.0 that came with the Nexus 4 and then upgrade to JB 4.3. However, whenever I do factory reset via recovery mode, I am stuck with an empty phone with the files I mentioned above.
What can I do to fix the situation? Thanks.
Click to expand...
Click to collapse
I think the reason that a factory reset won't help since there is no OS on the phone so it cannot reset something that isn't there.
And with the steps I mentioned, can you get into bootloader or does it directly boot into recovery.
Another thing you can try(I don't think it will work but I never tried it so you never know)
Download this toolkit:
http://forum.xda-developers.com/showthread.php?t=2015469
There is an option to flash to stock completly, that will maybe do the trick.
Good luck!
Sent from my Nexus 4 using xda app-developers app
failly said:
I think the reason that a factory reset won't help since there is no OS on the phone so it cannot reset something that isn't there.
And with the steps I mentioned, can you get into bootloader or does it directly boot into recovery.
Another thing you can try(I don't think it will work but I never tried it so you never know)
Download this toolkit:
http://forum.xda-developers.com/showthread.php?t=2015469
There is an option to flash to stock completly, that will maybe do the trick.
Good luck!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I can get into bootloader fine, it does not boot directly into recovery.
My Nexus 4 is already flashed with TWRP. I have installed the program from the link you provided, however, I have not used it to flash my phone again as one of the prerequisites to using the program is selecting which OS version I am using (at this point I am not using any) and want to prevent any further issues from occurring.
It seems like I can't really do anything with my phone unless I get a JB OS reinstalled, which is what I am currently struggling with. I am presently trying to find a way to copy the downloaded Nexus image files provided online into my internal storage so I can install them.
pooq said:
I can get into bootloader fine, it does not boot directly into recovery.
My Nexus 4 is already flashed with TWRP. I have installed the program from the link you provided, however, I have not used it to flash my phone again as one of the prerequisites to using the program is selecting which OS version I am using (at this point I am not using any) and want to prevent any further issues from occurring.
It seems like I can't really do anything with my phone unless I get a JB OS reinstalled, which is what I am currently struggling with.
Click to expand...
Click to collapse
Okay since you can get into bootloader thats great news!
Have you tried to manually download the nexus 4 image from google?
NOTE this are direct download links:
4.3:
https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
4.2.2:
https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
Here is an excellent guide:
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
Scenario #2 on that guide suits you!
I think this will do the trick!
Sent from my Nexus 4 using xda app-developers app
You just have to do the following :
A) flash a recovery via fastboot (fastboot flash recovery recovery.zip)
B) now go ahead and boot from your recovery, and push the rom of your choice, in case you don't have one already inside your sdcard (adb push ROM.zip /sdcard/ROM.zip)
C) flash your recently copied rom of choice to your phone. (if necessary, wipe data, cache and dalvik cache)
failly said:
Okay since you can get into bootloader thats great news!
Have you tried to manually download the nexus 4 image from google?
NOTE this are direct download links:
4.3:
https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
4.2.2:
https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
Here is an excellent guide:
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
Scenario #2 on that guide suits you!
I think this will do the trick!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I just spent a couple of hours reading through the guides (and trying them out) which led me to several other guides. To be incredibly honest, I am completely confused as there is a plethora of new information thrown at me. I have to pose several questions before I continue:
1) When you say bootloader, are you referring to the fastboot bootloader screen that pops up after holding the volume down button and the power button? I just wanted to confirm this as I am starting to feel you are referring to something different after reading several guides.
2) Is the scenario 2 guide you posted basically a method to "sideload" the JB 4.3 into the storage of my Nexus 4 so I can install it via Recovery Mode?
I tried installing the drivers but I cannot seem to do it successfully as I do not even have a starting OS for my phone in the first place. I can not access a theoretical "Developer Mode" either from when I first rooted my phone.
So basically, I do not understand how I can get the direct downloads from Google (the JB 4.3 files) and get them into the internal storage of my Nexus 4 to install the OS.
Is there a simpler way to do this? If not, here is my current progress. At the moment I am stuck at this guide (http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1) from the previous link you linked and am between C-D. I cannot get my laptop to recognize my device via fastboot devices in command prompt (D). To be honest, this is the second time I've seen this guide but could not get it working properly which is why I used the file provided at (http://forum.xda-developers.com/showthread.php?t=2015469) to root my Nexus 4.the OS[/B]. Is there a simpler way to do this? At the moment I am stuck at this guide (http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1) from the previous link you linked and am between C-D. I cannot get my laptop to recognize my device via fastboot devices in command prompt (D). To be honest, this is the second time I've seen this guide but could not get it working properly which is why I used the file provided at (http://forum.xda-developers.com/showthread.php?t=2015469) to root my Nexus 4.
Yes, the bootloader is the one where you press vol down and the power button together, that's the place where you select to go to the recovery, use fastboot.
First thing you got to do is turn on your phone on the bootloader as mentioned above. Then, assuming you downloaded this: [NEXUS 4 TOOLKIT V2.0.0] from here http://forum.xda-developers.com/showthread.php?t=1995688, open up command prompt and go to this address with "cd C:\Google_Nexus_4_ToolKit" or where you decided to install your toolkit. On windows explorer, go there and rename fastboot-toolkit or whatever it is called to fastboot to make things simpler.
Type in cmd: fastboot devices to check if it recognizes your phone.
If it doesn't; then install these drivers (you should have your device already connected via USB to your computer): https://www.dropbox.com/s/a808emeelvxkwyc/usb_driver.rar
Go to Control Panel\Hardware and Sound > Device Manager. Your phone should appear with an exclamation mark somewhere, right click it and click on update driver:
-Click on browse my computer software
-Let me pick from a list of device drivers on my computer
-Have disk
-Browse for where you downloaded the drivers I linked you to then click ok.
-You should find within the next page something that says Android Bootloader Interface, double click it and finish the installation.
After that's done, then type in fastboot devices on cmd again, it should show up now.
Then, go to here and download TWRP 2.6.0.0 http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.0.0-mako.img , that will be your recovery. After you've downloaded move it to C:\Google_Nexus_4_ToolKit to make matters easier.
NOTE: IF YOUR BOOTLOADER IS LOCKED YOU WILL HAVE TO UNLOCK IT , this can be done by typing fastboot oem unlock on command prompt
Now, simply type in this command: fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img you will now have a recovery on your device.
With the volume keys, choose to boot from the recovery. TWRP will load, while its loading, rename adb-toolkit to adb to make things easier. When its done loading, type in adb devices to see if it recognizes your phone, if it doesn't use your drivers again but this time instead of choosing Android Bootloader Interface, pick the one that says ADB.
When that's done, and it recognizes your device with the adb devices command you can now proceed to "push" or "copy/move a ROM you've downloaded in your computer towards your phone".
Of course you have to download a ROM, like Paranoid Android for example: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-3.69-20130722.zip , along with its GApps: http://goo.im/devs/paranoidandroid/roms/gapps/pa_gapps-full-4.2-20130719-signed.zip
You might have to even update your radio and bootloader in the future too, but let's leave it at that for now.
After you are done downloading the ROM of your choice, then type in these commands (assuming ADB works)
adb push pa_mako-3.69-20130722.zip /sdcard/
adb push pa_gapps-full-4.2-20130719-signed.zip /sdcard/
Having moved these two files inside your phone, now its time to flash them.
1) Go to Wipe on TWRP and simply swipe to factory reset
2) Go back and click on Install, look for pa_mako-3.69-20130722.zip and then add pa_gapps-full-4.2-20130719-signed.zip to the queue, swipe to install.
After that's done, simply reboot your phone and it should start booting up Paranoid Android and you're done. Might give you a few issues if you have an old radio and bootloader, but that can be fixed by flashing the new versions of these two in TWRP. Can be found here: https://www.copy.com/s/JniBu/4.3 files (mako) (these can be pushed via ADB like before, or you can simply download them on your phone when its working)
Hope this helps, don't think I can be more detailed.
wammie said:
Yes, the bootloader is the one where you press vol down and the power button together, that's the place where you select to go to the recovery, use fastboot.
First thing you got to do is turn on your phone on the bootloader as mentioned above. Then, assuming you downloaded this: [NEXUS 4 TOOLKIT V2.0.0] from here http://forum.xda-developers.com/showthread.php?t=1995688, open up command prompt and go to this address with "cd C:\Google_Nexus_4_ToolKit" or where you decided to install your toolkit. On windows explorer, go there and rename fastboot-toolkit or whatever it is called to fastboot to make things simpler.
Type in cmd: fastboot devices to check if it recognizes your phone.
If it doesn't; then install these drivers (you should have your device already connected via USB to your computer): https://www.dropbox.com/s/a808emeelvxkwyc/usb_driver.rar
Go to Control Panel\Hardware and Sound > Device Manager. Your phone should appear with an exclamation mark somewhere, right click it and click on update driver:
-Click on browse my computer software
-Let me pick from a list of device drivers on my computer
-Have disk
-Browse for where you downloaded the drivers I linked you to then click ok.
-You should find within the next page something that says Android Bootloader Interface, double click it and finish the installation.
After that's done, then type in fastboot devices on cmd again, it should show up now.
Then, go to here and download TWRP 2.6.0.0 http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.0.0-mako.img , that will be your recovery. After you've downloaded move it to C:\Google_Nexus_4_ToolKit to make matters easier.
NOTE: IF YOUR BOOTLOADER IS LOCKED YOU WILL HAVE TO UNLOCK IT , this can be done by typing fastboot oem unlock on command prompt
Now, simply type in this command: fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img you will now have a recovery on your device.
With the volume keys, choose to boot from the recovery. TWRP will load, while its loading, rename adb-toolkit to adb to make things easier. When its done loading, type in adb devices to see if it recognizes your phone, if it doesn't use your drivers again but this time instead of choosing Android Bootloader Interface, pick the one that says ADB.
When that's done, and it recognizes your device with the adb devices command you can now proceed to "push" or "copy/move a ROM you've downloaded in your computer towards your phone".
Of course you have to download a ROM, like Paranoid Android for example: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-3.69-20130722.zip , along with its GApps: http://goo.im/devs/paranoidandroid/roms/gapps/pa_gapps-full-4.2-20130719-signed.zip
You might have to even update your radio and bootloader in the future too, but let's leave it at that for now.
After you are done downloading the ROM of your choice, then type in these commands (assuming ADB works)
adb push pa_mako-3.69-20130722.zip /sdcard/
adb push pa_gapps-full-4.2-20130719-signed.zip /sdcard/
Having moved these two files inside your phone, now its time to flash them.
1) Go to Wipe on TWRP and simply swipe to factory reset
2) Go back and click on Install, look for pa_mako-3.69-20130722.zip and then add pa_gapps-full-4.2-20130719-signed.zip to the queue, swipe to install.
After that's done, simply reboot your phone and it should start booting up Paranoid Android and you're done. Might give you a few issues if you have an old radio and bootloader, but that can be fixed by flashing the new versions of these two in TWRP. Can be found here: https://www.copy.com/s/JniBu/4.3 files (mako) (these can be pushed via ADB like before, or you can simply download them on your phone when its working)
Hope this helps, don't think I can be more detailed.
Click to expand...
Click to collapse
The first thing I'd like to do before reporting my progress report is to thank you and failly for taking the time to help me out. You both have contributed tremendously in trying to help me out with this, so I would like to thank you both for that.
1) I had installed the sdk program and changed the adb path (following this guide http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/)
Following wammie's guide:
2) Booted into bootloader
3) Downloaded and installed NEXUS 4 TOOLKIT V2.0.0 (had used it before but it didn't work for me so I relied on a different program to root my phone). Renamed fastboot-toolkit to fastboot
4) Typed fastboot devices in in cmd, does not recognize phone
5) Uninstalled current usb drivers and installed usb drivers provided. The driver I chose to install for was titled "Android". The other ! mark was "Base System Device" which was something I had never seen before until today when I had reinstalled usb drivers
6) Typed fastboot devices in cmd again and still nothing has changed
I am unable to continue any further as fastboot does not recognize my phone when I have it under bootloader. I had downloaded all the files that were recommended in your post. I think the reason why I cannot access fastboot devices is because there is literally no OS running in my phone. I could be wrong though.
I guess I'll take a break and call it a night since I've been trying to fix this problem the past 13 hours or so. Any additional feedback and support is appreciated!
Additional Notes: I have tried this both on my laptops (Windows 8) and on my desktop PC (Windows 7)
Luckly, if windows doesn't recognize your device while in fastboot it isn't because you don't have a OS installes but because not correctly set up drivers.
I posted a link some posta ago about a toolkit:
http://forum.xda-developers.com/showthread.php?t=2015469
When opening the program at the top there is a button called full driver installation, press it and follow the instructions.
Sent from my Nexus 4 using xda app-developers app
http://i.imgur.com/sOT7FGh.png
http://i.imgur.com/WNEKb0z.png
http://i.imgur.com/vUmTDcZ.png
http://imgur.com/da7NGwB
http://i.imgur.com/bjmhXZv.png
This is what you should do when you are updating the drivers, its imperative you get those drivers working. Otherwise, you won't get access to fastboot.
Oh I would recommend using a Windows 7 PC.
Windows 8 can also do the trick but you maybe need to disable driver signature enforcement, so you better go with windows 7 for now.
Sent from my Nexus 4 using xda app-developers app
Status Update:
I had spent a whole day reformatting my Windows 7 machine and am back at it. I have made a bit more progress than before.
1) After typing in fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img in command prompt, under the "List of devices attached" it is blank (i.e. there is no device attached). http://i.imgur.com/TnyBCKS.png
2) I have successfully installed the usb driver on my PC the first time when the only explanation mark was titled "Android", however the only Android option at the moment now is labelled "Android Bootloader Interface". No such thing as ADB (or any variations including Android ADB Interface) exists.
3) In TWRP Recovery mode, I see an exclamation mark titled mako but I believe that is irrelevant. I have tried installing the drivers to this just in case but failed. I then tried it again in Bootloader mode and mako is gone and Android Device pops up again with "Android Bootloader Interface"
4) I have tried restarting my PC and repeating the above steps.
Edit:
5) The only time I see an Android Composite ADB Interfaces is when I boot normally to the "Google" screen. However, I cannot move any of my ROMS over into my phone. When I typed "adb devices" it shows a bunch of characters with offline beside it. I do not have any options to reinstall any drivers for this.
From my understanding,I should be able to access the Android Composite ADB Interface while in recovery mode, which should let me transfer my ROMs over... but the issue is I cannot access Android Composite ADB Interface while in recovery mode.
Also, is there any reason why I shouldn't use the official JB 4.3 img as the ROM I want to install on my phone?
hi; rank amateur here. i unlocked my 6p which went with no problems and then installed trwp, now it just boots to the google logo. i can get to fastboot and twrp but my linux pc no longer sees the phone. i suspect the phone is in charge mode. can i use recovery, > terminal to turn on data transfer so i can load and flash a new os? i was looking at loading a zip to a sd card but i had to order an adapter from c to type a usb. thanks
@dr1445 Have you tried a factory reset? I'm not how Linux works but if I'm remembering correctly I think Windows installed additional drivers after I unlocked the bootloader. This is a bit old but looks like people are still using might find something useful.
yes i did try a factory reset but the same result. as for the the linux pc i used it to unlock the 6p and other phones, i just need to toggle off the the charge function and click on transfer. i have a widows machine, i will give it a try, never know.
fastboot says connect cable but it also reports download mode disabled, is there away to turn it on in fastboot?
dr1445 said:
fastboot says connect cable but it also reports download mode disabled, is there away to turn it on in fastboot?
Click to expand...
Click to collapse
Make sure your fastboot is the latest and maybe try a different cable if you can.
---------- Post added at 01:39 PM ---------- Previous post was at 12:54 PM ----------
dr1445 said:
fastboot says connect cable but it also reports download mode disabled, is there away to turn it on in fastboot?
Click to expand...
Click to collapse
Mine also says download mode disabled and I can still use fastboot. So I don't think its the problem.
dr1445 said:
hi; rank amateur here. i unlocked my 6p which went with no problems and then installed trwp, now it just boots to the google logo. i can get to fastboot and twrp but my linux pc no longer sees the phone. i suspect the phone is in charge mode. can i use recovery, > terminal to turn on data transfer so i can load and flash a new os? i was looking at loading a zip to a sd card but i had to order an adapter from c to type a usb. thanks
Click to expand...
Click to collapse
You're best bet is to just flash a factory image from Google and start over, link
let's see my pc still doesn't have commo with fastboot. i found that "sideloader" works between the pc and fastboot. i was able to install lineageos 15.1 but with out the gapps at the moment. odd thing is i can not get the "developer option" with 7 taps of the build #. working on new post now. thanks all.
dr1445 said:
let's see my pc still doesn't have commo with fastboot. i found that "sideloader" works between the pc and fastboot. i was able to install lineageos 15.1 but with out the gapps at the moment. odd thing is i can not get the "developer option" with 7 taps of the build #. working on new post now. thanks all.
Click to expand...
Click to collapse
Make sure your on the latest bootloader (3.79) I know that was a must after March update for most ROMs. Also make sure fastboot is the latest here.I think your best option is written above with reflashing latest stock image from March and starting over.
happy to check the bootloader version. i get bl: angler-03.79, baseband: angler-03.85. should be good?