Related
I know fastboot issues are probably a common thing to be asked, but I've had fastboot issues before and I've always been able to fix them. This time I just can't and I've been trying to fix it for several hours now to no avail.
I can't get my Nexus 4 to be recognized by adb in Fastboot mode. I've managed to figure out that it's definitely an issue on the Nexus 4's side, cause I can get my Nexus 7 to be recognized in fastboot mode. I've installed the latest Google drivers, uninstalled them, reinstalled them over and over again, tried installing drivers through Nexus Root Toolkit, EVERYTHING. But nothing seems to work. It recognizes fine when it's running a ROM itself. typing "adb devices" shows the device find, I can reboot into the bootloader with "adb reboot bootloader", all that works fine, but once in the bootloader it just doesn't work. I've made to sure to reinstall the drivers while in the bootloader, and nothing seems to do the trick.
What's interesting is that I did a driver test with Nexus Root Toolkit, and it actually recognized it while it was in Fastboot mode and went through the whole test successfully. It reset out of bootloader mode and booted up, so I'm confused as to how it recognized it but I can't.
I tried flashing the Kit Kat factory image through Nexus Root Toolkit, and I thought it worked, but then it gave a random error at the end and rebooted and I was still running the ROM that I flashed a few days ago.
I'm really at a loss for what I can do. Without fastboot the device is stuck on custom ROMs. Nothing seems to work. I'm honestly baffled, I can usually figure this stuff out on my own but NOTHING is working anymore.
Any ideas?
Try turning off MTP
Sent from my Nexus 4 using xda app-developers app
This is just a wild guess, but maybe its between your bootloader version and the fastboot version. Try to use the latest ADT package from Google. If you post the exact error the toolkit give might be easier to diagnose. Also when you connected the N4 in bootloader mode, what is the name of it in Device Manager? Mine is "Google Nexus 4 Bootloader Interface" under the category of "Android Device", using the latest Universal Naked Driver. If your isn't the same try reinstalling it with UND.
kboya said:
Try turning off MTP
Click to expand...
Click to collapse
Nope. Plus I don't see how that would effect it, considering the MTP/PTP is only for toggling between accessing the full storage and having the device recognized as a camera from my understanding. In bootloader mode it wouldn't even recognize which mode it's in. At least I think.
Regardless, tried it in both and it didn't work.
eksasol said:
This is just a wild guess, but maybe its between your bootloader version and the fastboot version. Try to use the latest ADT package from Google.
Click to expand...
Click to collapse
Redownloaded the whole adt package. Didn't help.
eksasol said:
If you post the exact error the toolkit give might be easier to diagnose.
Click to expand...
Click to collapse
It was kinda weird, I think it thought it was flashing the factory image but it wasn't actually doing anything. I'm pretty sure the the error was just some weird error in the program itself, it didn't really say anything usefu;.
eksasol said:
Also when you connected the N4 in bootloader mode, what is the name of it in Device Manager? Mine is "Google Nexus 4 Bootloader Interface" under the category of "Android Device", using the latest Universal Naked Driver. If your isn't the same try reinstalling it with UND.
Click to expand...
Click to collapse
"Android Bootloader Interface" under the category of "Android Device". Drivers are the official ones from Google. I don't think I've tried the Universal Naked Driver. I'll try that and report back.
Tried installing the Universal Naked USB Drivers from this thread, and got this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ashanmaril said:
Tried installing the Universal Naked USB Drivers from this thread, and got this error:
Click to expand...
Click to collapse
It means you are using Windows 8 and is trying to install an unsigned driver (not sanctioned by the almighty Microsoft). You need to restart Windows 8 into Advance Startup and press F7 at the menu to disable driver signing: http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Ah, okay. Thanks, I'll try that tomorrow. Heading to bed right now.
Sent from my Nexus 5 using Tapatalk
Ashanmaril said:
Ah, okay. Thanks, I'll try that tomorrow. Heading to bed right now.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Actually here's the link to the latest UND version which has Nexus 5 support as well: http://forum.xda-developers.com/showthread.php?t=2513339
Alright, managed to install the driver, but it still won't recognize the Nexus 4.
The driver DID manage to make adb notice my Nexus 7 in adb sideload mode so I was able to update to Kit Kat on that.
I'm really at a loss for what to do on the Nexus 4 though...
Ashanmaril said:
Alright, managed to install the driver, but it still won't recognize the Nexus 4.
The driver DID manage to make adb notice my Nexus 7 in adb sideload mode so I was able to update to Kit Kat on that.
I'm really at a loss for what to do on the Nexus 4 though...
Click to expand...
Click to collapse
stopped Reading here "I can't get my Nexus 4 to be recognized by adb in Fastboot mode". adb never Works on fastboot mode, if it Works then its a oem modified bootloader to work with that.
Adb works in Fastboot mode. That's how you flash factory images on Nexus devices.
See this video.
Sent from my Nexus 7 using Tapatalk 4
Ashanmaril said:
Adb works in Fastboot mode. That's how you flash factory images on Nexus devices.
See this video.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
facotry images use "fastboot flash partitonname file".
Example, fastboot flash system system.img or fastboot flash bootloader bootloader-mako-z30i.img
Ashanmaril said:
Adb works in Fastboot mode. That's how you flash factory images on Nexus devices.
See this video.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
No he's right, it's called bootloader mode actually and it only work with fastboot, ADB only work in custom recovery. Fastboot is the main method to flash factory image.
sent from xda premium app
Oh, shoot. Sorry, I just realized I've been calling it fastboot mode this whole time. I meant bootloader mode.
Either way, yeah. Still haven't figured out what's going on.
Ashanmaril said:
Oh, shoot. Sorry, I just realized I've been calling it fastboot mode this whole time. I meant bootloader mode.
Either way, yeah. Still haven't figured out what's going on.
Click to expand...
Click to collapse
bootloader mode where u can select between power off,rstart,start,recovery ?
Yep. Typing "adb devices" never shows the device while it's in the bootloader. It works fine when it's powered on, I can even do commands like "adb reboot bootloader" and whatnot and they work fine, but it just doesn't work in bootloader mode.
Ashanmaril said:
Yep. Typing "adb devices" never shows the device while it's in the bootloader. It works fine when it's powered on, I can even do commands like "adb reboot bootloader" and whatnot and they work fine, but it just doesn't work in bootloader mode.
Click to expand...
Click to collapse
that is fastboot mode(it dosent looks like a normal fastboot mode because google modified it)but.as i said adb never worked on dat because its disabled, if u wanna adb on dat mode, either u get another phone or install modified bootloader(im using unlocked bootloader from att lg og because i like lg logo + adb Works on dat, but u cant install any 4.4 rom or kernel :/)
But it works with all my other Nexus devices. And it used to work.
Watch the video I linked earlier. He demonstrates using adb commands in the bootloader to flash a factory image. I've done it multiple times.
Sent from my Nexus 5 using Tapatalk
Ashanmaril said:
But it works with all my other Nexus devices. And it used to work.
Watch the video I linked earlier. He demonstrates using adb commands in the bootloader to flash a factory image. I've done it multiple times.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
that is not nexus 4 + he only used FASTBOOT commands, i seriously didnt see any adb command, can u gimme the time? he showed the .imgs on folder he showed the nexus(it looked like the 10) and he done fastboot flash blablabla.
print: http://prntscr.com/24fbm0
Oh. My. Gosh.
I am so stupid.
This whole time I've been typing "adb devices" to test to see if it was recognizing the devices. I was supposed to be typing "fastboot devices"
I have no words. I tried every complex solution I could think of... And it was just me being stupid...
Sorry about that. I guess this is solved. I'm gonna go hit my head against the wall for a bit.
*****DISCLAIMER*****DISCLAIMER*****DISCLAIMER*****
If you brick your device it's a whole lot of NOT MY PROBLEM
*****DISCLAIMER*****DISCLAIMER*****DISCLAIMER*****
With that out of the way enjoy
1) Download this
https://www.androidfilehost.com/?fid=95747613655047389
2) unzip: V510_4.4.4+tools.zip
3) Install the LG drivers
4) Install LGFlashTools v1.8 (but don't run it)
5) Copy MegaLock.dll to C:\LG\LGFlashTool, This is a hidden folder so enable "hidden folders". Replace the old MegaLock.dll file if you have already installed LG Flash Tool on your computer
6) Launch LG Flash Tool
You might see a window with Korean language, just click on OK
Check the Select Manual Mode on the top
7) MAKE SURE UNDER, DEVICE MANAGER, YOUR PORT IS SET TO COM 41 FOR YOUR DEVICE.
8) Click the DLL box and choose LHV510_SVC_LGFLASHv160.dll
9) Click the S/W box and select the firmware file with .tot extension
10) Now click the Yellow arrow button on the top left of the main window
11) Boot your V510 into Download Mode. To do this power V510 completely off. Then hold Volume Up + Volume Down + plug in USB to PC (in that order)
The firmware installation will be triggered
Ignore if you see any temporary error and just wait patiently till it is finished.
I took these instructions from another post. That post ended by giving "Credit [email protected] for making a cleaner guide for the TOT Method"
It's a shame the v500 can't be converted
n0credit said:
It's a shame the v500 can't be converted
Click to expand...
Click to collapse
This might help: http://goo.gl/rPx8KK
+1 worked perfectly for me.
The only part that I had a little trouble with was changing the COM port to 41.
Windows users: you must be booted into Download Mode for the tablet to show up in Device Manager, where you change the COM port. I was trying to change the port while the tablet was booted up (normally) and it was driving me crazy.
Need some help:
tl;dr: Pretty sure I still need to flash the stock recovery, but having problems.
Coming from a rooted LG GPad GPE with TWRP installed. I followed the instructions on this thread and everything seems to have worked. I'm now unrooted, but I'm still getting "your system is up to date" when I check for an update in settings.
I think I do not have the right recovery installed, and that is why I am not getting the update. When I try to boot into recovery mode, I get the android guy on his back with a red triangle. No signs of TWRP being installed anymore.
I've tried several times to flash the stock recovery as listed in this thread: http://forum.xda-developers.com/showthread.php?t=2574639. It seems to work, but I don't think it is working properly. I also can't sideload the 5.0 file through ADB, since I need to put the device into recovery mode to do it.
---------- Post added at 02:24 PM ---------- Previous post was at 01:46 PM ----------
Nevermind. Turns out that is the stock recovery. Now my problem is I can't push the file over ADB. The ADB connection doesn't persist into recovery mode. I've followed the steps here: http://forum.xda-developers.com/showthread.php?t=2575783.
When the device is on normally, the ADB connection is fine. It shows up in the list of connected devices. When I reboot into recovery and choose "apply update from ADB" and then enter "adb devices" I get no devices connected.
In device manager, I see "LG-V510" under "other devices" but when I try to manually update the drivers to the google drivers as indicated in the post above, the computer says "Windows could not find driver software for your device."
Still need help...
mcaurilio said:
Need some help:
tl;dr: Pretty sure I still need to flash the stock recovery, but having problems.
Coming from a rooted LG GPad GPE with TWRP installed. I followed the instructions on this thread and everything seems to have worked. I'm now unrooted, but I'm still getting "your system is up to date" when I check for an update in settings.
I think I do not have the right recovery installed, and that is why I am not getting the update. When I try to boot into recovery mode, I get the android guy on his back with a red triangle. No signs of TWRP being installed anymore.
I've tried several times to flash the stock recovery as listed in this thread: http://forum.xda-developers.com/showthread.php?t=2574639. It seems to work, but I don't think it is working properly. I also can't sideload the 5.0 file through ADB, since I need to put the device into recovery mode to do it.
---------- Post added at 02:24 PM ---------- Previous post was at 01:46 PM ----------
Nevermind. Turns out that is the stock recovery. Now my problem is I can't push the file over ADB. The ADB connection doesn't persist into recovery mode. I've followed the steps here: http://forum.xda-developers.com/showthread.php?t=2575783.
When the device is on normally, the ADB connection is fine. It shows up in the list of connected devices. When I reboot into recovery and choose "apply update from ADB" and then enter "adb devices" I get no devices connected.
In device manager, I see "LG-V510" under "other devices" but when I try to manually update the drivers to the google drivers as indicated in the post above, the computer says "Windows could not find driver software for your device."
Still need help...
Click to expand...
Click to collapse
I guess I'm not quite sure what you were trying to accomplish. If it is to install TWRP. You need to use fastboot from download mode and flash your recovery there, rather than trying to use adb from the recovery itself. "Fastboot flash recovery palman.img". , where palman.img is the name of whatever recovery you want to flash.
Fairly certain I did everything correctly according to the directions. When I press the yellow arrow about how long does it take to complete the install? When i started it, little box came up said some things that I don't remember and after about 30 seconds, the little box went away and the COM41 box says Ready!! Does that mean its finished? Just dont want to unplug tablet before the process is finished and brick it. Thanks
Nevermind, figured it out. Had to unplug device and plug usb back in and that triggered it to start.
sleekmason said:
I guess I'm not quite sure what you were trying to accomplish. If it is to install TWRP. You need to use fastboot from download mode and flash your recovery there, rather than trying to use adb from the recovery itself. "Fastboot flash recovery palman.img". , where palman.img is the name of whatever recovery you want to flash.
Click to expand...
Click to collapse
No, I was trying to sideload the 5.0 upgrade. Couldn't get my adb connection to persist through to recovery mode. Finally figured it out and was able to get the tablet upgraded this morning - but I had to use the TWRP backup method. Everything seems to be good to go now though!
Correct drivers
I'm having problems getting the port changed to 41 and I think it because the drivers aren't installing correctly. Could someone confirm from the screenshot below that I'm on the right track, or maybe post a shot of what the correct driver set-up should look like? Thanks.
**Edit: Got it, I did have the wrong drivers.
I don't think you have the right drivers installed. There should be two of them and mine were both banged-out yellow, but only when in download mode and with the software running. You don't even have a ports tab to change it (or you have the wrong device).
I gave up and restored the Lollipop backup someone posted, which worked great except then I had to re-root and flash TWRP again.
-MX- said:
I'm having problems getting the port changed to 41 and I think it because the drivers aren't installing correctly. Could someone confirm from the screenshot below that I'm on the right track, or maybe post a shot of what the correct driver set-up should look like? Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
If drivers are installed correctly, you should find it under Ports(COM & LPT) expand that and LG should be there. Right click and properties and find the COM41
shawn13165 said:
If drivers are installed correctly, you should find it under Ports(COM & LPT) expand that and LG should be there. Right click and properties and find the COM41
Click to expand...
Click to collapse
Yeah, definitely wrong drivers, had to do some uninstalling/reinstalling and finally got it to work.
Colchiro said:
I don't think you have the right drivers installed. There should be two of them and mine were both banged-out yellow, but only when in download mode and with the software running. You don't even have a ports tab to change it (or you have the wrong device).
I gave up and restored the Lollipop backup someone posted, which worked great except then I had to re-root and flash TWRP again.
Click to expand...
Click to collapse
I had given up for the 4.4.4 update when it initially came out and upgraded through TWRP, but now I'm running into issues with not being able to use the external SD card from the TWRP backup of LP that was posted, so I figured I needed to give this method a shot and do it right.
Any chance we will get the 5.0 TOT file for the v510? I tried following this guide: http://forum.xda-developers.com/showthread.php?t=2220801 and also tried using wireshark to capture the path in the LG Support tool but haven't had any luck with either method.
Thanks man. This helped me restore my G Pad when I thought all hope was lost.
Thank you very much, this worked perfect!
I am sitting dead in the water with an EVGA Tegra Note 7 that can't turn on Wireless and won't let me install drivers to move further or even do a restore.
First off I am using Tomsgt Super Tool: http://forum.xda-developers.com/showthread.php?t=2627654
So my device was continuing to fail an OTA update so I was going to use this device to reinstall the basic 4.4.2. However during the process Fastboot.exe gave a failed message in Windows, but it showed fastboot after the device name. I continued to let it Restore Tegra Note 7 to Android 4.4.2 and first of all it did it way too fast and once it was finished I couldn't get the Wireless to enable. I read another person with the same problem that had to redo the process. Well I can't get past reinstalling ADB and Fastboot, now not even ADB..
I tried uninstalling the device from Windows letting it reinstall and then checking it again. No matter what I do the USB Driver Scan fails over and over. I got this issue the first time, but somehow I got it to catch the device once and install ADB.
1) Yes USB Debugging in Enabled
2) Yes Anti-Virus is Off
3) Bootloader unlocked
4) Tried Different USB Ports
So what the hell is going on here?? All I wanted to do was run a damn OTA update.. Now I have a tablet with no wireless and I obviously can't do an OTA update now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was thinking about not using the tool and doing it all manually like I used to do, but all the tool does is auto execute files/folders in specific orders, basically an elaborate .bat file. So if it is failing at ADB, it is going to fail for me manually too.
Please give me some idea of what to do. I don't see how relocking the bootloader would do anything, but aside from that it was a non-rooted stock 4.4.2 OS running.
Is there something I need to do in order to get Impactor to work?
So then I plug the device into a 9 year old laptop with Windows XP and Impactor sees the device on the first try and installs the driver (it takes 2-3 minutes). Then it finishes and I close impactor, but I get an error next saying device not found. I restart the machine and now it is exactly like my desktop, Impactor can't see the device at all.
What in the hell is going on here? If I had known all this was going to happen I would have skipped their damn OTA update that continued to fail.
BTW with XP I can prevent Windows from installing any type of driver, so I did. Should I let XP search for a driver and see what happens?
Someone throw me some ideas, you can see a full explanation of what is happening if you scroll up to my screenshot. I basically have a dead device because I wanted to use this tool to do a recovery...
Wireless refuses to turn on, it just sits there for hours if I let it.
Someone please give me guidance, I was out of the Android scene for a while and I've forgotten a lot of the tricks I used to know.
If your computer is recognizing the fastboot mode that is all you need. Forget the supertool for now.
Can you use the tablet to get into the Fastboot Protocol? It so that will put it in fastboot mode even if it doesn't look like it.
If that works, you can run TWRP or a custom recovery by using ADB and the fastboot command "fastboot boot TWRP_recover.img"
Notice the fastboot "boot", that will only run TWRP once so if you want to on your tablet for good you replace boot with "flash". fastboot flash TWRP_recover.img
You have to make sure the filename is correct with the custom recovery you downloaded.
At this point, put the update you want on your SD card, put that card in the tablet, and go to TWRP or your custom recover and upload the new software.
It sounds complicated but it isn't.
share_needles said:
If your computer is recognizing the fastboot mode that is all you need. Forget the supertool for now.
Can you use the tablet to get into the Fastboot Protocol? It so that will put it in fastboot mode even if it doesn't look like it.
If that works, you can run TWRP or a custom recovery by using ADB and the fastboot command "fastboot boot TWRP_recover.img"
Notice the fastboot "boot", that will only run TWRP once so if you want to on your tablet for good you replace boot with "flash". fastboot flash TWRP_recover.img
You have to make sure the filename is correct with the custom recovery you downloaded.
At this point, put the update you want on your SD card, put that card in the tablet, and go to TWRP or your custom recover and upload the new software.
It sounds complicated but it isn't.
Click to expand...
Click to collapse
Thanks for the suggestions, but I don't think Fastboot has completely installed on my tablet. When I hit Fastboot kernel all I get is a black flash and back to the bootloader again. I believe there is a quick message that flashes the first time I try to select Fastboot, however it's way too fast to read. When I do it again after that is when I will see a black flash, but apparently from what I have heard that is all Fastboot kernel is supposed to do??
How do I verify Fastboot is working before I flash the damn thing?
NCSUZoSo said:
Thanks for the suggestions, but I don't think Fastboot has completely installed on my tablet. When I hit Fastboot kernel all I get is a black flash and back to the bootloader again.
How do I verify Fastboot is working before I flash the damn thing?
Click to expand...
Click to collapse
That is what I was saying when I said you wouldn't even know you're in fastboot. The black-screen with message flashes for a milisecond and goes back to the same screen so it looks like nothing happened when it is actually in fastboot mode.
You can verify this by running your super tool and it will say "fastboot device"
Do you know how to use the ADB command prompt?
Using that, I flashed a custom recovery and then put the below 4.3 zip file on my SD card and going through the tablet I used the TWRP custom recovery to upload 4.3 on the tablet.
I used this old backup of 4.3:
Forum post and links: forum.xda-developers.com/showthread.php?t=2580287
Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip
FYI,
I was in your same situation and that worked for me. I could not get my computer to recognize my device in anything other than fastboot mode.
share_needles said:
That is what I was saying when I said you wouldn't even know you're in fastboot. The black-screen with message flashes for a milisecond and goes back to the same screen so it looks like nothing happened when it is actually in fastboot mode.
You can verify this by running your super tool and it will say "fastboot device"
Do you know how to use the ADB command prompt?
Using that, I flashed a custom recovery and then put the below 4.3 zip file on my SD card and going through the tablet I used the TWRP custom recovery to upload 4.3 on the tablet.
I used this old backup of 4.3:
Forum post and links: forum.xda-developers.com/showthread.php?t=2580287
Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip
FYI,
I was in your same situation and that worked for me. I could not get my computer to recognize my device in anything other than fastboot mode.
Click to expand...
Click to collapse
Can I get some official links for the newest/compatible versions of TWRP and the latest stock ROM I can install that is the most up to date (with Google Apps)?
Sorry to ask, but I am short on time most of the time and I might have an hour or so to work on it tomorrow.
Sorry I don't have official links but it would take you 10mins to find them through google. Good luck.
I have two files which I believe are correct except the TWRP file has an odd extension..
"Shaky156-TWRP-recovery.img.exe"
the other that is supposed to have GApps is: Stock-4.4.2-2.5-TegraNote7.zip
If that zip is only like 440 MB is that even possible? Can someone point me in a better direction if this sounds wrong.
Sources, TWRP: http://forum.xda-developers.com/showthread.php?t=2586432
Actually thinking about it and I bet with having things specific to img files like IMGBurn and other software it may create a .exe so it's easier to emulate it as a disk.
Do we have any good custom ROMs these days you'd suggest over stock? Are any that stable yet? If not can anyone find me a complete download if a 440MB zip is too small to have GApps in it.
I used Fastboot commands to get TWRP installed and Android is "upgrading.." now, so hopefully this will fix it.
I have the tablet up and running going into Google Play now.
I used this thread's link for the latest TWRP (2.7.1.0): http://forum.xda-developers.com/showthread.php?t=2586432
I got a completely stock version of 4.4.2 and OTA shows this as the most up to date version. I got my copy of the 4.4.2 ROM out of the Super Tool's folder that you can find here: http://forum.xda-developers.com/showthread.php?t=2627654
The tricky part to this my first time was I forgot you can open a command window inside the folder that contains TWRP/Fastboot/etc. (hold Shift and Right Click in the folder where all the data is and hit open command window)
Obviously everything came off a SD Card installed into the TN7.
answer for dummies
Hi
Is anyone able to explain how to rectify wifi being turned off constantly in basic non technical talk?
I am not a tech pro and am unsure what to do
All of the above answers are like a different language to me .
Thansks
aimeymarie said:
Hi
Is anyone able to explain how to rectify wifi being turned off constantly in basic non technical talk?
I am not a tech pro and am unsure what to do
All of the above answers are like a different language to me .
Thansks
Click to expand...
Click to collapse
Your best bet is to find someone you know who the above is not a foreign language to. I mean it could be broken down step by step as basic as possible and you may still not understand parts.
OK, first, I have searched the internet and XDA for help.
Currently, I'm stuck on The black screen with Google. It shows the unlocked Bootloader icon as well. Earlier today I was stuck in a boot with CM boot animation, but that's apparently gone now. I can fastboot, so I'm pretty sure it's recoverable. In TWRP, it says unable to mount /system, /data/ cache/ storage, basically everything. Using NRT i've flashed stock everything, which didn't work, so I tried flashing the kernel, which also didn't work, so I tried the bootloader and system, but they all result in the google splash screen. I am completely out of ideas.
Question: How do i fix it?
Edit: It stayed on the splash screen for at least 4 hours and it wasn't caused by anything I did. No ROM flashes, nothing. It was working then it wasn't.
a.child said:
OK, first, I have searched the internet and XDA for help.
Currently, I'm stuck on The black screen with Google. It shows the unlocked Bootloader icon as well. Earlier today I was stuck in a boot with CM boot animation, but that's apparently gone now. I can fastboot, so I'm pretty sure it's recoverable. In TWRP, it says unable to mount /system, /data/ cache/ storage, basically everything. Using NRT i've flashed stock everything, which didn't work, so I tried flashing the kernel, which also didn't work, so I tried the bootloader and system, but they all result in the google splash screen. I am completely out of ideas.
Question: How do i fix it?
Edit: It stayed on the splash screen for at least 4 hours and it wasn't caused by anything I did. No ROM flashes, nothing. It was working then it wasn't.
Click to expand...
Click to collapse
If you are using NRT, try to flash stock with soft-bricked/Bootloop option.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After restore, perform a wipe data/factory reset in stock recovery before booting to android.
Best of luck
joegestes said:
If you are using NRT, try to flash stock with soft-bricked/Bootloop option.
After restore, perform a wipe data/factory reset in stock recovery before booting to android.
Best of luck
Click to expand...
Click to collapse
Thanks for the help, you even edited a screenshot :') haha unfortunately, no luck. But some interesting stuff happens when I do the stock flash.
First time I tried (yesterday), I went through the instructions just how they're listed, I erased all user data and rebooted, still stuck. This time, though, I couldn't get it to boot the stock recovery. Tried pwr+Vol Up like the directions say, but it gets stuck on splash. Tried Pwr+Vol down and I could boot into TWRP which informed me that it was still unable to mount any partitions and that there was no OS installed.
Edit: Looked closer at the command prompt log from the flash and noticed it failed to write any of the images. Sending is OKAY but writing FAILED.
a.child said:
Thanks for the help, you even edited a screenshot :') haha unfortunately, no luck. But some interesting stuff happens when I do the stock flash.
First time I tried (yesterday), I went through the instructions just how they're listed, I erased all user data and rebooted, still stuck. This time, though, I couldn't get it to boot the stock recovery. Tried pwr+Vol Up like the directions say, but it gets stuck on splash. Tried Pwr+Vol down and I could boot into TWRP which informed me that it was still unable to mount any partitions and that there was no OS installed.
Edit: Looked closer at the command prompt log from the flash and noticed it failed to write any of the images. Sending is OKAY but writing FAILED.
Click to expand...
Click to collapse
Hmmm.
Its possible your cable is no good, but it could be something else like a driver issue or charging port failure.
Try using a known good, high quality data cable. Also try connecting to a different USB port on PC.
Just so I understand better.
What version of android did you attempt to flash?
Were you using NRT to flash when the flashing's failed?
Was Force Flash enabled in NRT? .......Try that.
Did you try flashing a different version of STOCK android?
Do you have Android ADB/fastboot installed on PC aside from the one in NRT?
If so, does fastboot detect your phone when running the command "fastboot devices" while in the bootloader?
Is ADB able to detect your phone when running the command "ADB devices" while in TWRP?
I'm at work now, but I'll try new cables and ports when I get home as well as the adb commands.
I was trying to flash 5.0.1 , and was running some CM12 nightly when it failed. To be clear, the ROM was working fine until it wasn't.
I was using NRT and I had force flash selected (recommended settings I think), but I'm not 100% sure post flash factory reset was checked but in the CMD log I did see it wipe and attempt to write userdata.
I have not tried a different version of stock.
I believe ADB is installed outside of NRT abd i have to manually set my path variable to C:/ADB (which screws up normal command prompt, but idk how to fix that) for NRT to work. I have a 2013 nexus 7 and used the same setup to flash PA a while back without any issues.
NRT doesn't detect my phone when displaying the splash screen, but idk about TWRP.
joegestes said:
Hmmm.
Its possible your cable is no good, but it could be something else like a driver issue or charging port failure.
Try using a known good, high quality data cable. Also try connecting to a different USB port on PC.
Just so I understand better.
What version of android did you attempt to flash?
Were you using NRT to flash when the flashing's failed?
Was Force Flash enabled in NRT? .......Try that.
Did you try flashing a different version of STOCK android?
Do you have Android ADB/fastboot installed on PC aside from the one in NRT?
If so, does fastboot detect your phone when running the command "fastboot devices" while in the bootloader?
Is ADB able to detect your phone when running the command "ADB devices" while in TWRP?
Click to expand...
Click to collapse
So the computer does not recognize a fastboot device while in TWRP, but does in the BL.
I attempted to flash 5.0 with the settings mentioned, no luck
a.child said:
So the computer does not recognize a fastboot device while in TWRP, but does in the BL.
I attempted to flash 5.0 with the settings mentioned, no luck
Click to expand...
Click to collapse
If you are absolutely certain your cable is a good one, it is possible you have a driver issue, but I doubt it.
You could try deleting/uninstalling you current ADB driver set and then install the following ADB clockworkmod universal drivers . It might help.
64bit
32bit
If you decide to install the drivers. make sure you select "Android Composite ADB Interface"
after installing the driver set
If that does not help, I am sorry to say, you are likely looking at a hardware failure of the charging port(Dock Connector &Flex Cable)
It looks easy and economical to replace. I found the part here, but you could Google around. I have no experience with the following site.
http://www.repairsuniverse.com/lg-nexus-4-e960-dock-connector-flex-cable-replacement.html
If it were my N4(still great phone), I'd replace the part and attempt to re-flash.
Best of luck.
joegestes said:
If you are absolutely certain your cable is a good one, it is possible you have a driver issue, but I doubt it.
You could try deleting/uninstalling you current ADB driver set and then install the following ADB clockworkmod universal drivers . It might help.
64bit
32bit
If you decide to install the drivers. make sure you select "Android Composite ADB Interface"
after installing the driver set
If that does not help, I am sorry to say, you are likely looking at a hardware failure of the charging port(Dock Connector &Flex Cable)
It looks easy and economical to replace. I found the part here, but you could Google around. I have no experience with the following site.
http://www.repairsuniverse.com/lg-nexus-4-e960-dock-connector-flex-cable-replacement.html
If it were my N4(still great phone), I'd replace the part and attempt to re-flash.
Best of luck.
Click to expand...
Click to collapse
Thanks for the links, I might give it a go.
I bought an original Moto x last night for $100 and I was going to root the potatoes out of it, but who knew non-nexus phones were so difficult to unlock? Damn AT&T....
I sort of suspected it was a hardware issue when I was getting nowhere with NRT, but I wanted confirmation from someone more knowledgeable than me. Any idea on the likelyhood it is something other than the port? The bit that concerns me is that TWRP was unable to mount any partitions, but then again, if i couldn't connect while in TWRP, sort of sounds like a port issue.
oh well...
a.child said:
Thanks for the links, I might give it a go.
I bought an original Moto x last night for $100 and I was going to root the potatoes out of it, but who knew non-nexus phones were so difficult to unlock? Damn AT&T....
Click to expand...
Click to collapse
LOL....That's why I mostly stick with Nexus devices. No carrier garbage, global bands, unlockable and plenty of potatoes:laugh:
a.child said:
Any idea on the likelyhood it is something other than the port?.
Click to expand...
Click to collapse
Could be a bad eMMC but I doubt that. Port failure is more likely to be the issue based on your inability to ADB devices in TWRP.
a.child said:
The bit that concerns me is that TWRP was unable to mount any partitions, but then again, if i couldn't connect while in TWRP, sort of sounds like a port issue
Click to expand...
Click to collapse
Its harder know exactly when using NRT.
That is one reason why, IMO, it is far better to use Fastboot commands to flash instead of relying on toolkit automation.(I do think NRT is the best toolkit)
My guess is NRT sends erase commands to a partition before flash attempts which then failed or sometimes, when a port goes bad,
it is intermittent, a partial flash occurs which would also explain why TWRP can,t mount a particular partition.
For ten bucks delivered on eBay its a no brainier to change out the port. It will probably fix it and if not, you'll have learned something.
joegestes said:
LOL....That's why I mostly stick with Nexus devices. No carrier garbage, global bands, unlockable and plenty of potatoes:laugh:
Could be a bad eMMC but I doubt that. Port failure is more likely to be the issue based on your inability to ADB devices in TWRP.
Its harder know exactly when using NRT.
That is one reason why, IMO, it is far better to use Fastboot commands to flash instead of relying on toolkit automation.(I do think NRT is the best toolkit)
My guess is NRT sends erase commands to a partition before flash attempts which then failed or sometimes, when a port goes bad,
it is intermittent, a partial flash occurs which would also explain why TWRP can,t mount a particular partition.
For ten bucks delivered on eBay its a no brainier to change out the port. It will probably fix it and if not, you'll have learned something.
Click to expand...
Click to collapse
Well i replaced the port and the battery and i'm having the same problem. And I did check to make sure I didn't reinstall the old port.
Guess she's dead :'(
Hmmm... You can connect in fastboot mode, right?
How about re-locking and unlocking the bootloader? It helped me several times...
You'll have to search about how to use fastboot. Connect your phone to your pc while in fastboot mode, and type this into terminal window :
fastboot oem lock
(Press enter)
(bootloader will be locked)
fastboot oem unlock
(Press enter)
(Phone's screen will display sth, use volume keys and power keys to unlock the bootloader)
(It will erase itself)
ddaggebi said:
Hmmm... You can connect in fastboot mode, right?
How about re-locking and unlocking the bootloader? It helped me several times...
You'll have to search about how to use fastboot. Connect your phone to your pc while in fastboot mode, and type this into terminal window :
fastboot oem lock
(Press enter)
(bootloader will be locked)
fastboot oem unlock
(Press enter)
(Phone's screen will display sth, use volume keys and power keys to unlock the bootloader)
(It will erase itself)
Click to expand...
Click to collapse
Thanks for the suggestion, but it didn't work. I was able to lock and unlock the bootloaded again, but it didn't have any effect.
Have you tried flashing Jellybean or kitkat stock rom by fastboot?
If that doesn't work, then the problem is within EMMC. You'll have to let her go...
ddaggebi said:
Have you tried flashing Jellybean or kitkat stock rom by fastboot?
If that doesn't work, then the problem is within EMMC. You'll have to let her go...
Click to expand...
Click to collapse
Looking at other forums, pretty sure the emmc is dead, but I'll try flashing an older version.
Hi, this is my first post.
My Device: Samsung Galaxy Note 4
Model Number: SM-N910F
Build: MMB29M.N910FXXS1DQFB
Version: N910FXXS1DQFB//N910fXXS1DQA3
Android Version: 6.0.1
Qualcomm Snapdragon 805 APQ8084
My first attempt flashing my note4 ended with a brick, now it works again, but i don't know what went wrong. I already activated developer options, but there is no "oem unlock". I read a lot on XDA Forum and it is emphasized that it is important to unlock OEM/bootloader in order to modify the device. I already know that some Note 4 devices have a locked bootloader and some don't, an i assume i haven't a locked bootloader on my device, but i'm not sure.
Can anyone confirm that my Note 4 has already an unlocked bootloader?
Older phones do not have OEM.
To verify if your bootloader is unlocked read these steps.
Open the Phone app or the Dialer.
Enter the code: *#*#7378423*#*#
This should automatically open a new window.
Tap the Service info.
Open Configuration.
You should see one of the two messages:
– Bootloader Unlocked Allowed – Yes
– Bootloader Unlocked – Yes
@Samarimama -thank you, but this doesn't work without sim-card i guess?
I'm sorry, but the code doesn't work with my sim card.
Ok, take off your SIM card and try it again.
I've tried with and without SIM card: "Invalid USSD-Code". Any other options?
Try with ADBCheck from Your PCTo check your bootloader status from your PC, you’ll need to use an ADB and fastboot tool. Until recently, you needed to download the full Software Development Kit (SDK) to get to ADB and fastboot. But now, you can get this lightweight tool separately.
Step 1: Setting Up the Command PromptWhen you install the tool, you should:
Locate the path to the ADB and fastboot folder.
Click on the Start Menu and type ‘cmd’ until the Command Prompt icon appears.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Type the path to the ADB and fastboot folder in your Command Prompt. For example:
C:UsersUsernameDownloadsADB and fastboot
Step 2: Turning on the Fastboot ModeOnce the Command Prompt is set, you should set your phone to fastboot mode. To do this:
Turn your Android phone off.
Hold the Volume Down and Power/Unlock buttons at the same time until the phone turns on again.
When it turns on, release the Power button, but hold the Volume Down key until you see the bootloader menu. It should display the little Android bot lying on its back on a dark background, with a text under it.
Connect the computer and your phone with a data cable.
Step 3: Checking the StatusNow that everything is set, you can use the Command Prompt to check the status of your bootloader. To do this, you should:
Enter the ‘./adb devices’ command into the Command Prompt to check if ADB can locate your device. This should list your phone.
Execute the ‘./adb bootloader’ command to boot into bootloader.
Once you are in the bootloader, type the ‘fastboot devices’ command in the Command Prompt and execute it. If it lists a code, that means that the system can detect your phone.
Enter the ‘fastboot oem device-info’ command and run it. It should list some device data, including the bootloader information.
Look for ‘Device Unlocked’ from the info.
If it says ‘true’ next to it, it means that your device is unlocked. If it says ‘false,’ it means that that it’s still locked.
Sometimes, you can see this information right away in the bootloader display of your Android phone.
I agree with @Samarimama . Bootloaders are usually not locked on older phones, and the option to unlock it can not be found in developer options. However, my understanding is that bootloaders could be locked on carrier tied phones, most often USA-based, but those versions are usually not F, but some other letters. Unsure about the version you have.
I do believe tho that you should try and first update the firmware on that phone, since that does not seem to be the latest version. N910FXXU12DRI2, is the latest one, i have worked with several CSC-versions of it, and have yet to encounter one with locked bootloader.
I also figure that it should not be possible to flash any custom binary on to a phone with a locked bootloader, you should just get error while trying. So if you managed to actually flash something on to your phone, it is unlikely that the bootloader on your phone is locked. Then it is rather a question of how you went about while flashing that resulted in bricking the device. And what you mean by "bricked".
It is why we need to unlock the bootloader to flash a ROM.
prkfsz said:
I agree with @Samarimama . Bootloaders are usually not locked on older phones, and the option to unlock it can not be found in developer options. However, my understanding is that bootloaders could be locked on carrier tied phones, most often USA-based, but those versions are usually not F, but some other letters. Unsure about the version you have.
I do believe tho that you should try and first update the firmware on that phone, since that does not seem to be the latest version. N910FXXU12DRI2, is the latest one, i have worked with several CSC-versions of it, and have yet to encounter one with locked bootloader.
I also figure that it should not be possible to flash any custom binary on to a phone with a locked bootloader, you should just get error while trying. So if you managed to actually flash something on to your phone, it is unlikely that the bootloader on your phone is locked. Then it is rather a question of how you went about while flashing that resulted in bricking the device. And what you mean by "bricked".
Click to expand...
Click to collapse
I got my Note 4 from a friend in Austria, but i live in Germany, so i made a reset and this is why i never knew there is a firmware update for my Note 4. I only use it in Germany, and after the reset i have N910FXXS1DQFB//N910fXXS1DQA3. Is it really neccessary to flash the newer austrian firmware? It's a bit confusing for me, excuse me for being so dumb.
Samarimama said:
Try with ADBCheck from Your PCTo check your bootloader status from your PC, you’ll need to use an ADB and fastboot tool. Until recently, you needed to download the full Software Development Kit (SDK) to get to ADB and fastboot. But now, you can get this lightweight tool separately.
Step 1: Setting Up the Command PromptWhen you install the tool, you should:
Locate the path to the ADB and fastboot folder.
Click on the Start Menu and type ‘cmd’ until the Command Prompt icon appears.
Type the path to the ADB and fastboot folder in your Command Prompt. For example:
C:UsersUsernameDownloadsADB and fastboot
Step 2: Turning on the Fastboot ModeOnce the Command Prompt is set, you should set your phone to fastboot mode. To do this:
Turn your Android phone off.
Hold the Volume Down and Power/Unlock buttons at the same time until the phone turns on again.
When it turns on, release the Power button, but hold the Volume Down key until you see the bootloader menu. It should display the little Android bot lying on its back on a dark background, with a text under it.
Connect the computer and your phone with a data cable.
Step 3: Checking the StatusNow that everything is set, you can use the Command Prompt to check the status of your bootloader. To do this, you should:
Enter the ‘./adb devices’ command into the Command Prompt to check if ADB can locate your device. This should list your phone.
Execute the ‘./adb bootloader’ command to boot into bootloader.
Once you are in the bootloader, type the ‘fastboot devices’ command in the Command Prompt and execute it. If it lists a code, that means that the system can detect your phone.
Enter the ‘fastboot oem device-info’ command and run it. It should list some device data, including the bootloader information.
Look for ‘Device Unlocked’ from the info.
If it says ‘true’ next to it, it means that your device is unlocked. If it says ‘false,’ it means that that it’s still locked.
Sometimes, you can see this information right away in the bootloader display of your Android phone.
Click to expand...
Click to collapse
ADB does not recognize my Note 4. Debugging mode is already acitivated.
Me too I have this problem with the same phone. My PCs do not recognize him
prkfsz said:
I also figure that it should not be possible to flash any custom binary on to a phone with a locked bootloader, you should just get error while trying. So if you managed to actually flash something on to your phone, it is unlikely that the bootloader on your phone is locked. Then it is rather a question of how you went about while flashing that resulted in bricking the device. And what you mean by "bricked".
Click to expand...
Click to collapse
I already had twrp on my phone and i simply panicked while flashing a rom. After that it had a permanent bootloop, after taking out batteries it was impossible to switch it on. It happened some years ago, i used recovery software, made a factory reset and it works. And I still want to install a system that is not as old as 2017. I have a lot of patience, and i will find a way - if the bootloader is unlocked. Therefore i try to figure out if Note 4 has a locked bootloader or not. You say, Note 4 is that old, it hasn't any, and because twrp was on the phone already, it is unlocked. Then it seems to be a waste of time to try to use ADB to be sure. Instead i could try to flash it right now and don't care about unlocking something that doesn't exist on Note 4.
If you can go to TWRP, install the ROM you want with your phone and flash it with Gapps.
Old Lady said:
I got my Note 4 from a friend in Austria, but i live in Germany, so i made a reset and this is why i never knew there is a firmware update for my Note 4. I only use it in Germany, and after the reset i have N910FXXS1DQFB//N910fXXS1DQA3. Is it really neccessary to flash the newer austrian firmware? It's a bit confusing for me, excuse me for being so dumb
Click to expand...
Click to collapse
You're not dumb for not knowing something.. ;-)
It's hard to say if updating is totally necessary but it's almost always recommended to update your phone to the latest firmware before flashing custom ROMs. And I would say, especially since the last made firmware seems to have been made more that a year after the firmware you actually have on your phone I would strongly recommend updating to the latest firmware. It's not difficult, you go to settings and find where you choose to update and let the phone find the latest update itself while being connected to internet.
After that, if you already have TWRP installed, which I understand you do, just try and flash the custom ROM you want. But please remember to before that back up everything you want to save from the phone. And also make a twrp backup of the phone so you can restore it if something goes wrong. And read the suggested flashing procedure several times before actually doing it so you are familiar with it. If something goes wrong go to twrp and restore it from there.
Old Lady said:
I already had twrp on my phone and i simply panicked while flashing a rom. After that it had a permanent bootloop, after taking out batteries it was impossible to switch it on. It happened some years ago, i used recovery software, made a factory reset and it works. And I still want to install a system that is not as old as 2017. I have a lot of patience, and i will find a way - if the bootloader is unlocked. Therefore i try to figure out if Note 4 has a locked bootloader or not. You say, Note 4 is that old, it hasn't any, and because twrp was on the phone already, it is unlocked. Then it seems to be a waste of time to try to use ADB to be sure. Instead i could try to flash it right now and don't care about unlocking something that doesn't exist on Note 4.
Click to expand...
Click to collapse
What do you mean "panicked while flashing a ROM"? What did you do while flashing?
It is not a serious problem.
prkfsz said:
What do you mean "panicked while flashing a ROM"? What did you do while flashing?
Click to expand...
Click to collapse
Phone showed a litte red android while flashing but nothing seemed to happen for a long time, so i disconnected phone and pc. After that my phone didn't work anymore, now everthing is fine and soon i will try it once more - without disconnecting.