Hello,
I just came from a custom ROM and flashed stock 6.0 and stock recovery, in order to send my phone into squaretrade. However, There seems to be no recovery on my phone now. When I power up, I get the boot logo and then eventually goes to my lockscreen. I try to unlock with my passcode and it just continues to loop back to the lockscreen. I shut down and try to go to recovery and there is only a screen that says "no command". I cannot seem to get adb to see my device while attached. Am I completely screwed?
Well, I used the return to stock tool and am able to set usb debugging on. However, I still don't have recovery and when I am in fastboot and check for adb devices, there are none found.
buggerritt said:
Well, I used the return to stock tool and am able to set usb debugging on. However, I still don't have recovery and when I am in fastboot and check for adb devices, there are none found.
Click to expand...
Click to collapse
When you get to the Android on his back saying "No command" press and hold Power and tap Vol Up, that should bring up the stock recovery menu.
When in fastboot, there is no adb, only fastboot... you need to use `fastboot devices`
When flashing the stock images, flash stock recovery, then start it and do a factory default, then reboot and flash the entire stock image.
Where are you getting the stock image and instructions? You should never be prompted for a passcode after flashing the stock images, the device should be a blank slate.
I forgot the stuff you reminded me of. Thank you. I'm back on track now.
Related
So I tried to update to KitKat 4.4 and was never able to get passed the loading screen. I booted into ClockworkMod Recovery and wiped everything and now the device will not go passed the Google loading screen. The device is no longer recognized when I plug into the computer and I cannot access through Wugs.
I called Google and they are sending out an RMA for this device (I did not tell them it was unlocked) and they are sending out a replacement.
Is there anyway that I can remove ClockworkMod Recovery and re-lock this device without being able to access the device through a computer?
BrianXP7 said:
Whoa, RMA's should be only used for last resort bootloader bricks! Since you still have the bootloader ("Google" logo at startup), hold Power + Volume Down to enter Fastboot mode and try reflashing the factory images. Just to be safer, use the Universal Naked Drivers and skip with bootloader image. Don't forget to have the ADB and Fastboot binaries in the same folder. I wouldn't recommend toolkits as they don't expose new users with these situations.
If you need anything else, let me know. If I completely missed on what you needed, sorry about that.
Also, just as long as the bootloader update isn't interrupted or type "fastboot erase bootloader" you should be fine without an RMA.
Click to expand...
Click to collapse
thanks for the reply.
I am able to boot in recovery mode on the device and this is recognized by Wugs as "ADB - device on". When I attempt any flash, it checks Fastboot status and I receive notification that the "Fastboot device was not found". I cannot find a compatible driver when I am in fastboot mode running on a Windows 7 x64 machine.
Any idea on how I can get this N7 to function, return to stock, or at least remove ClockworkMod and lock the bootloader so I can RMA?
I can get into fastboot. The device still boots, but obviously everything was wiped and it's stock Android. When I try to go to recovery I get a a Android emote guy with a red warning triangle.
I assume recovery is buggered? Is it correct in assuming that because I can get into fastboot I can simply flash a recovery image and hope for the best? I was trying to load CWM on it. Just want to double check before I go ahead.
The first time recovery said it flashed fine, I went into it and at the bottom it told me that sd couldn't mount, amongst other things that could not mount, including /system/ which is odd because the device is usable.
As long as you can enter fastboot mode, you can flash (factory) images onto your device's partitions.
Erovia said:
As long as you can enter fastboot mode, you can flash (factory) images onto your device's partitions.
Click to expand...
Click to collapse
Thanks just wanted to double check. Will get on it at some point.
I need some major help
My N7 2012 was stock, never rooted. I had only installed OTA updates. Yesterday, the OTA update for Lollipop appeared, and I installed it.
It worked fine for about an hour, until it suddenly rebooted. After that, it will now only boot into the launcher (Nova Launcher) for about 15 seconds, then *bam* crash, reboot. Rinse and repeat.
I've tried booting into safe mode via long-pressing on the Shutdown menu, but it apparently crashes before it can reboot, because it just boots back to Nova Launcher.
I've also tried getting it into fastboot, and I can issue fastboot commands. However, I've never unlocked the bootloader. And when I try to unlock it now, I get the screen that says "This will void your warranty are you sure?" But when I select Yes, fastboot's console says "Failed", and it remains locked.
If I go into Recovery, it just says "No commmand"
I need some help from the geniuses on this forum. To me it seems like an app running at startup is causing the crash, so if I could just get it to Safe Mode, I could figure it out and uninstall it. Hell, I'd be fine w/ a total wipe at this point. Just something to get it working again!
Thanks in advance!
Try using wugfresh's nexus toolkit to fix your issue, preferably to full wipe and reinstall lollipop again.
Didn't work
bubba949 said:
Try using wugfresh's nexus toolkit to fix your issue, preferably to full wipe and reinstall lollipop again.
Click to expand...
Click to collapse
I tried using the Nexus toolkit, using Flash to Stock/Unroot in Bootloop mode, and it didn't work. A few sections succeeded, but most of the sections said "FAILED". Even after performing this, it still wants to boot to my normal desktop, so I know it's not re-flashing a thing.
I wish I knew more about this. I can get into fastboot by going to Power+VOL- but because it won't stay on the desktop, adb commands are a no-go. Is there something in the Advanced section of the Nexus Toolkit that will let me do a reflash? I'm afraid of just poking and trying things for fear of truly bricking it.
Thanks.
Sorry just re-read your last reply didn't realise you can't do adb commands, if you get to a point when you can then below may help...
I had a similiar issue caused differently what i did was to go to this link
http://forum.xda-developers.com/showthread.php?t=1907796
Downloaded the bootloader from JWR66V the guy mentions in his thread he mentions the same issue that i had which is when i tried to flash a stock or custom rom i kept getting messages about invalidstate on bootloader then the system and userdata images would fail when i tried to install...
In the end i downloaded the stock JWR66Y rom, replaced the bootloader image with the one mentioned above, i had to flash the seperate parts of the rom as the Nexus Root Toolkit wouldn't accept the MD5 after i replaced the bootloader so make sure the recovery, the modified bootloader, system and userdata are in your SDK tools folder then i did the following in cmd...
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
Fastboot reboot
And voila it booted up and then upgraded its self and is now stock running 5.0 but its working for 2days it wasn't lol
alastria1 said:
It worked fine for about an hour, until it suddenly rebooted. After that, it will now only boot into the launcher (Nova Launcher) for about 15 seconds, then *bam* crash, reboot. Rinse and repeat.
I've tried booting into safe mode via long-pressing on the Shutdown menu, but it apparently crashes before it can reboot, because it just boots back to Nova Launcher.
Click to expand...
Click to collapse
You can try booting into Safe Mode directly from powered off state. From a reference guide here in help
bftb0 said:
[size=+1]Safe Mode Boot[/size]
From a cold start boot (press & release Power button), wait 2 seconds after the B&W Google (bootloader) splash screen appears, then press and hold Vol-Down button until the normal OS boot is fully completed (lock screen or home screen appears)
Click to expand...
Click to collapse
Sounds like something is draining the RAM. Try using the stock launcher as default.
Still crashed
dtg7 said:
You can try booting into Safe Mode directly from powered off state. From a reference guide here in help
Sounds like something is draining the RAM. Try using the stock launcher as default.
Click to expand...
Click to collapse
I didn't know that. I tried it, and I was able to boot it into safe mode doing this ... and then it crashed in 15 seconds and rebooted...
At this point, I'm considering just emailing Google, since its their update that did this.
They'll probably tell you to wipe cache partition. And by the way,
alastria1 said:
If I go into Recovery, it just says "No commmand"
Click to expand...
Click to collapse
that is a normal operation, it's supposed to say that. What you need to do to get the actual recovery menu is, with screen saying No Command, hold the power button, then click the volume Up button, them let go of power.
This will get you the recovery options, where you should scroll down to wipe Cache partition (last one I think) and select it by hitting power. Reboot into Android and see if that helped.
If not in the same recovery menu there's an option to wipe everything, factory reset. that might cure your device but it will wipe your data.
There is an adb command to pull your sdcard data off your device, but I've never tried it in stock recovery. it might work, but of course it will probably require you had turned On USB debugging.
adb pull /storage/sdcard0/ yourcomputerfolder
yourcomputerfolder being a location on your laptop, like a folder on the desktop.
try this command when in recovery, I don't think it works in bootloader. also, if it works it will only backup your regular files, not your installed apps.
if not then just do the wipe from recovery.
good luck.
Still a no go...
So, I got into the recovery menu, and did a full factory reset. After it rebooted, it went right back to Nova Launcher (with my usual wallpaper on there), and crashed as before. Getting into safe mode confirmed that it no apps were wiped. Factory reset didn't reset a thing.
Its almost like the flash memory is stuck on read-only mode. No matter what I do, nothing changes the contents of memory.
That is weird. And I suppose you can't do what 'wakers' suggested and flash the individual partitions since it probably requires an unlocked bootloader, which you already tried to unlock unsuccessfully. I'd say you were up sh-- creek without a paddle, but... Google searching, maybe there's still a tiny bit of hope:
See this discussion: http://android.stackexchange.com/qu...p-after-lollipop-flash-no-adb-and-no-fastboot
to summarize the suggestions:
- try holding the power button for over ten seconds to kind of reset... something
- try sending the command: fastboot oem lock
yes I know you never unlocked but try it anyway, it might go thru where unlock failed.
speaking of fastboot oem unlock, I know it failed but maybe you can just keep sending the command a few times, one of them might go thru.
I'd add another suggestion: carefully remove the back and carefully unplug the battery and let it sit for a while. then put it back together and try booting up.
may the force be with you.
Finally resolved
Thanks to the posters for the help. I contacted Google customer support and they're overnighting a refurb replacement for free.
Okay, to start with, I've read the other threads about this. I understand the process that *should* work:
1. Power off.
2. Then, press and hold both all Volume Down + Power buttons at the same time until the LG Logo is being displayed on your LG V20.
3. Now, release the keys and press the above combination again however, this time you should wait until recovery mode menu is displayed.
...and I've tried the version where you keep holding the Volume Down button the entire time.
So, yes, I've reached the white screen where it asks you if you want to do a factory reset. I've hit "Yes" to both questions. The problem is that it really does a factory reset then.
---
After unlocking the bootloader, I installed TWRP via fastboot:
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot
...everything went fine.
But I can't get into recovery. And since I'm waiting to have TWRP working so that I can flash root, I can't boot into recovery via an app.
What did I do wrong?
EDIT:
Okay, it looks like TWRP isn't working properly. I tried "adb reboot recovery" and that got me to a dead Android icon and a "No command" message. I have no idea why TWRP isn't working.
Haphim said:
Okay, to start with, I've read the other threads about this. I understand the process that *should* work:
1. Power off.
2. Then, press and hold both all Volume Down + Power buttons at the same time until the LG Logo is being displayed on your LG V20.
3. Now, release the keys and press the above combination again however, this time you should wait until recovery mode menu is displayed.
...and I've tried the version where you keep holding the Volume Down button the entire time.
So, yes, I've reached the white screen where it asks you if you want to do a factory reset. I've hit "Yes" to both questions. The problem is that it really does a factory reset then.
---
After unlocking the bootloader, I installed TWRP via fastboot:
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot
...everything went fine.
But I can't get into recovery. And since I'm waiting to have TWRP working so that I can flash root, I can't boot into recovery via an app.
What did I do wrong?
EDIT:
Okay, it looks like TWRP isn't working properly. I tried "adb reboot recovery" and that got me to a dead Android icon and a "No command" message. I have no idea why TWRP isn't working.
Click to expand...
Click to collapse
to confirm, have you verified you are using the correct TWRP version for your V20?
in this step "fastboot flash recovery twrp.img" is your twrp image that you saved, named twrp.img? If its not, that command won't work correctly.
usually after I flash recovery, when still in the recovery menu, i choose reboot recovery just to make sure it did stick. If it reboots back to itself, then try rebooting the device, and again confirm with manually entering recovery. Maybe overkill but it works for me LOL.
Good luck!
I am in need of big help! I made a critical error after days of trying to navigate the minefields of rooting my device. I have a LG V20 h910 and it is no one-click wonder root. It made me work for it and I finally got it. I loaded LineageOS 14.1 and all was good until the USB OTG cable from my PS4 controller did not register anymore. Damn, that was a let down, and probably led to my careless move of needing to downgrade my TWRP, saw the version I needed, forgot these are device specific, and now I'm stuck in a hard place.
Perhaps the fix is easy, but I have not found the answer after many, many searches...
I had TWRP 3.2.1-2 and needed to downgrade to 3.2.1-0 to try SuperRom (hoping it would have OTG ability). I hastily grabbed the first TWRP 3.2.1-0, threw it on the SD card, wiped everything except internal storage, and flashed the img, and did a reboot. Road block went up.
I tried getting back into recovery, did the PWR and DOWN pressing combo and got the Factory Reset screen, but after clicking "Yes" to both, instead of getting the TWRP screen, I got this error screen (attached).
I tried another idea - hooked it up USB to my PC and tried accessing it via adb/fastboot. I tried multiple drivers for my device, but no adb and no fastboot devices were ever found. The only thing that almost worked was booting phone into FASTBOOT mode by holding DOWN btn and plugging in a USB cable attached to PC. Once in FASTBOOT mode, My PC at least saw the ID for fastboot device. I tried to flash TWRP via fastboot, and it looked like it would happen, but in the end there was no phone screen response to my attempt, and the cmd window on my PC would get stuck and just hang.
Can someone please advise me on how I can fix this problem?
I have unlocked my phone, hoping to find a fix to USB external camera not being recognized. As a consequence, I am not able to update my system through OTA. Moreover, I am no longer able to enter fastboot mode. Whatever key combination I tried, my phone will do a normal boot. When I power up or I press volume - I only end up doing a normal boot or powering off. If I press all 3 keys together I get into the e-recovery boot, which fails. I have only been able to boot into TWRP after downloading a system update and choosing to install it. With this procedure, the update will not be installed, but I will boot into TWRP. From here, if I choose recovery, I do boot into fastboot, but my fastboot is not recognized by my computer, as it was before. Running either ADB or Fastboot will not reveal any device connected.
pieemme said:
I have unlocked my phone, hoping to find a fix to USB external camera not being recognized. As a consequence, I am not able to update my system through OTA. Moreover, I am no longer able to enter fastboot mode. Whatever key combination I tried, my phone will do a normal boot. When I power up or I press volume - I only end up doing a normal boot or powering off. If I press all 3 keys together I get into the e-recovery boot, which fails. I have only been able to boot into TWRP after downloading a system update and choosing to install it. With this procedure, the update will not be installed, but I will boot into TWRP. From here, if I choose recovery, I do boot into fastboot, but my fastboot is not recognized by my computer, as it was before. Running either ADB or Fastboot will not reveal any device connected.
Click to expand...
Click to collapse
When you use key combinations, you must shutdown your phone first, not reboot or you can boot into system, make sure that usb debugging is turned on, open adb and type "adb reboot bootloader".
DeathBell said:
When you use key combinations, you must shutdown your phone first, not reboot or you can boot into system, make sure that usb debugging is turned on, open adb and type "adb reboot bootloader".
Click to expand...
Click to collapse
Thanks, I followed your instructions but with no success. As soon as I plug into USB it will power on and go on with a normal system boot, no matter how quick I am in typing the command "adb reboot bootloader", which invariably returns "no devices/emulators found", or whether I press the volume - button or not. This also happens when I am in the charging screen (not sure whether this also equals power off).
pieemme said:
Thanks, I followed your instructions but with no success. As soon as I plug into USB it will power on and go on with a normal system boot, no matter how quick I am in typing the command "adb reboot bootloader", which invariably returns "no devices/emulators found", or whether I press the volume - button or not. This also happens when I am in the charging screen (not sure whether this also equals power off).
Click to expand...
Click to collapse
No, you need to boot to Android to use adb.
Is your device bricked or stuck in a bootloop or something?
DeathBell said:
No, you need to boot to Android to use adb.
Is your device bricked or stuck in a bootloop or something?
Click to expand...
Click to collapse
I wouldn’t call it properly bricked, inasmuch as it is actually doing its job. However, It does some strange things: it gets the OTA updates, but when I click on Download and Install, it restarts in the TWRP menu (which I cannot otherwise access. I have 2 TWRP apps installed, which don’t seem to be of any use: official TWRP App and TWRP Manager). When I am in the TWRP menu, I can choose to restart in the bootloader. However, once there, with the green window telling me that my phone is flashed, the phone is still not detected by ADB or Fastboot commands. I don’t know when the bootloader started to be unaccessible because I left the tinkering a couple of months ago, when I realized that nobody so far has had any success in getting a P10 Lite to work with a USB Endoscope.
pieemme said:
I wouldn’t call it properly bricked, inasmuch as it is actually doing its job. However, It does some strange things: it gets the OTA updates, but when I click on Download and Install, it restarts in the TWRP menu (which I cannot otherwise access. I have 2 TWRP apps installed, which don’t seem to be of any use: official TWRP App and TWRP Manager). When I am in the TWRP menu, I can choose to restart in the bootloader. However, once there, with the green window telling me that my phone is flashed, the phone is still not detected by ADB or Fastboot commands. I don’t know when the bootloader started to be unaccessible because I left the tinkering a couple of months ago, when I realized that nobody so far has had any success in getting a P10 Lite to work with a USB Endoscope.
Click to expand...
Click to collapse
Thats normal behaviour, when you have a custom recovery installed and do anything in the stock recovery then it boots you into the custom recovery, it should also boot to TWRP when you do factory reset in the stock recovery. And when your phone isn't detected by fastboot then its probably a adb and fastboot installation issue on your PC, type "fastboot devices" to see if it detects your device. And what do you even want to do in fastboot?
Also are you in Nougat or Oreo?
DeathBell said:
Thats normal behaviour, when you have a custom recovery installed and do anything in the stock recovery then it boots you into the custom recovery, it should also boot to TWRP when you do factory reset in the stock recovery. And when your phone isn't detected by fastboot then its probably a adb and fastboot installation issue on your PC, type "fastboot devices" to see if it detects your device. And what do you even want to do in fastboot?
Also are you in Nougat or Oreo?
Click to expand...
Click to collapse
I am not too sure to have any working recovery at all, right now. If I press all 3 buttons, I get into the Huawei recovery mode, which fails. I am on EMUI 5.1.1 (Nougat) and would like to install a stock recovery to Oreo. If I am able to get to a working bootloader mode, I would like to install this file which seems to be a stock recovery with Oreo (WARSAW L21C432B182_EU_SERVICE_ANDROIDHOST.RU.RAR). Otherwise, I will buy a MicroSD card reader and try copying this installation to the card, which, according to this video (https://www.youtube.com/watch?v=0vDgDXePAR4&feature=youtu.be) should be the last resort, if everything else fails. I would be perfectly happy to return to a working and updated standard EMUI. I'm told that if I installed the OTA version this would not be working correctly on my my phone. According to an app called Rootchecker, my phone is not properly rooted either, but there are a lot of crappy apps out there, so I don't know what to believe.
BTW: I don't believe there is any problem with my adb fastboot installation (on MacOS). It was working earlier on. When I type "fastboot devices", it returns: "waiting for any device"
pieemme said:
I am not too sure to have any working recovery at all, right now. If I press all 3 buttons, I get into the Huawei recovery mode, which fails. I am on EMUI 5.1.1 (Nougat) and would like to install a stock recovery to Oreo. If I am able to get to a working bootloader mode, I would like to install this file which seems to be a stock recovery with Oreo (WARSAW L21C432B182_EU_SERVICE_ANDROIDHOST.RU.RAR). Otherwise, I will buy a MicroSD card reader and try copying this installation to the card, which, according to this video (https://www.youtube.com/watch?v=0vDgDXePAR4&feature=youtu.be) should be the last resort, if everything else fails. I would be perfectly happy to return to a working and updated standard EMUI. I'm told that if I installed the OTA version this would not be working correctly on my my phone. According to an app called Rootchecker, my phone is not properly rooted either, but there are a lot of crappy apps out there, so I don't know what to believe.
BTW: I don't believe there is any problem with my adb fastboot installation (on MacOS). It was working earlier on. When I type "fastboot devices", it returns: "waiting for any device"
Click to expand...
Click to collapse
I still can't uderstand you. Can you boot into Android or not? And Does TWRP work? When you device is softbricked, what did you do to brick it?
At one point you say that you can access fastboot by choosing reboot to bootloader in TWRP and then you say that you have no working recovery at all.
Anyway I can't help you with the fastboot thing then and that file isn't Oreo it's an old version of Nougat, B360 and up is Oreo and also B321 witch is Oreo Beta. You can only flash image files in fastboot anyway as that file needs to be unpacked and put on the dload folder on your sd card.
When you want to get to Oreo you can either use service roms from this thread https://forum.xda-developers.com/p10-lite/development/service-rom-b362-c432-upgrade-o-o-n-o-t3813946, you need to copy the two zip files into the dload folder in your SD card. You can also use HWOTA but that wouldn't work since fastboot isn't working for whatever reason. Or when your custom recovery is working you can use HuRUpdater. But you need to be on the newest version of Nougat B210 or B209 to update as otherwise you may brick your phone.