Database Users

Attempting to repartition SD card = Device not found in recovery

Hello,
I just got my Hero this weekend and I was interested in partitioning the SD Card. I have been following a guide and when I boot into recovery(Screen that shows phone with triangle and exclamation point) the computer does not seem to see the Hero anymore.
When I plug the phone in while it is running Android the computer picks it up fine in Device manager. Once I type adb shell reboot recovery it boots into the screen the computer no longer picks it up. I have tried unplugging and replugging the USB cable while in the recovery screen but still get nothing. If I type adb devices before I run the recovery command I am able to get the serial number, once it boots into the recovery screen it no longer shows me the serial number when I type in adb devices. But this is due to it no longer being picked up once in the recovery screen.
I'm not really sure what I am doing wrong here. Can anyone help me get this issue sorted out?
I have tried it on Windows 7 and read that a lot of people had issues with the syncing so I just finished attempting it on an Windows XP machine and still get the same issue.
One more thing, when in the recovery screen the phone does not respond to the power button anymore. It seems almost like it locks up or something. The only way I can get back out of the screen is by taking the battery out and putting it back in. Is this normal?
Any help would be really appreciated!
Thank you,
Mizex

You need to root the phone and install the recovery partition first.

Mizex said:
when I boot into recovery(Screen that shows phone with triangle and exclamation point)
Click to expand...
Click to collapse
jonnythan said:
You need to root the phone and install the recovery partition first.
Click to expand...
Click to collapse
Exactly what jonnythan said. If your recovery screen shows the triangle then you haven't installed a modified recovery image yet. Follow any of the guides on this site for rooting.

Oh wow I feel dumb the guide I was following said nothing about the phone needing to be rooted. I attempted to follow a 1 click root and while attempting to do the backup step I get a message saying that it can't complete the command. According to the guide if I get this error then it means I have a patched firmware and need to downgrade to a cupcake firmware.
Anyone know of a good guide for doing the downgrade? Or can perhaps share a bit of knowledge on the error?

No Command Error

I went to update to KitKat and it was nearly done and then the "No Command" error came up. My tablet has an unlocked boot loader but isn't rooted. However it was before but I updated it from an OTA and that got rid of it. I've tried booting into recovery etc but the same thing happens.
Anyone have any advice please?

Same exact issue and set up here. Also, maybe I'm just dumb, but I can't get my tablet to turn off either. It just keeps cycling back to the "no command" screen until I do something.

tgearhar said:
Same exact issue and set up here. Also, maybe I'm just dumb, but I can't get my tablet to turn off either. It just keeps cycling back to the "no command" screen until I do something.
Click to expand...
Click to collapse
I think that both of you what you see (the "no command") is your stock recovery, if indeed you see an android with a yellow !.
If it is the case to access the menu of the stock recovery press power and tap volume up. The menu will give you the choice of rebooting your Nexus 7.

gunner1937 said:
I think that both of you what you see (the "no command") is your stock recovery, if indeed you see an android with a yellow !.
If it is the case to access the menu of the stock recovery press power and tap volume up. The menu will give you the choice of rebooting your Nexus 7.
Click to expand...
Click to collapse
I can get to the menu but when trying the reboot option, it just cycles the same way again. Back to the android with a red ! and says "No command." I also tried clearing cache and data to no avail. I was going to try using ADB to manually push the update but my computer was recently updated and now I can't get the driver installed for some reason.
I spent too much time messing around with and learning how to do things with my SIII and not enough time with this

Same deal here! Not sure what to do short of wiping and losing my info.

Same here...any advice? Not sure what happened. OTA update too.

Significa said:
Same here...any advice? Not sure what happened. OTA update too.
Click to expand...
Click to collapse
Wow, this seems to be widespread, at least somewhat. I'm in same situation. Toolkits, adb, nothing works. I thought this was a soft brick, but now I'm thinking it's toast. Probably doesn't help that I didn't have Dev options enabled along with USB Debugging. I can't even turn it off. Just bootloops after Google logo shows up twice, then to No Command error, then starts over again. I wonder what the hell is causing this. (Device was locked and unrooted)

Same boat here, even sideloaded the factory image via ADB.

[QUOTE [/QUOTE]
I was going to try using ADB to manually push the update but my computer was recently updated and now I can't get the driver installed for some reason.
If you have android-sdk-windows installed on your computer do not forget to update it through "SDK Manager.exe".

Pushing via ADB didn't work for me. That also failed.
I caved and called Google. Tech support is stumped as well.
Sent from my Nexus 5 using Tapatalk

Could this be a widespread issue? Like I don't even understand why it happened at all!
Sent from my Nexus 5 using XDA Premium 4 mobile app

I finally got mine working again!
I tried a million different things so I'm going to try and explain my process as simple as I can, I apologize in advance because I am far from an expert...
First, I tried using the method, well some of it, from this thread: http://forum.xda-developers.com/showthread.php?t=1907796
- I would suggest using this thread to get everything set up (drivers, ADB, the factory image downloaded and in the correct file location) I wasn't able to get the drivers working correctly with that route so I ended up using the toolkit to get them working but that thread helped me get all of the system files in the correct location and helped get all of the ADB stuff set up.
Once you have everything set up and your computer recognizes the tablet, (I checked that by opening a cmd prompt and using the command from the original thread above "adb devices"). As long as you see your device, I think you should be good.
From the "No Command" screen I held down Power and Volume + to get the menu to come up. I then chose the Restart option and immediately held Power and Volume -. This got me into the Fastboot Mode.
Once in Fastboot mode I went to the cmd prompt on my computer and used the following commands in this order from this post:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system -w
fastboot flash system system.img
fastboot reboot
*Make sure that all of the image files are in the proper location on your computer otherwise this step is worthless
The tablet then rebooted normally and I was able to set everything up again. Again, I am by no means an expert at all, this is just what worked for me. Try at your own risk.
I hope I covered all of the steps, I tried a million different things last night so they all kind of run together.

I ended up doing and it worked for me as well. Wiped everything though. How can I restore / reinstall my apps w/o needing to download them all again?

Two things: That guide says you must have USB Debugging enabled. Since my wife had this tablet, I did not have dev options enabled at all, including USB debug.
The other thing is that when I run the SDK Manager, nothing happens on my computer. I double click it or try Run as Admin, and a small CMD box flashes on my screen for a millesecond and disappears. That's all.

My wife's 2012 N7 is having this same problem. Unlocked bootloader, but I reflashed factory image and unrooted before giving it to her. She got the OTA last night, and now stuck at No Command.
I've subscribed to this thread, hoping that you guys will have it solved before I get home from work tonight! Would love to not have her lose all her data.
(I was kinda mad that she got the OTA last night and I haven't got it yet on my 2013 N7, but that's another gripe for another thread)

killswitch11 said:
Two things: That guide says you must have USB Debugging enabled. Since my wife had this tablet, I did not have dev options enabled at all, including USB debug.
The other thing is that when I run the SDK Manager, nothing happens on my computer. I double click it or try Run as Admin, and a small CMD box flashes on my screen for a millesecond and disappears. That's all.
Click to expand...
Click to collapse
Unfortunately I'm not sure on the SDK manager part. As far as the USB Debugging, I'm 98% sure that I did not have it enabled either. I think I did at one point but after doing several OTA upgrades, I'm sure it got unchecked.
---------- Post added at 01:34 PM ---------- Previous post was at 01:01 PM ----------
kr33mo said:
I ended up doing and it worked for me as well. Wiped everything though. How can I restore / reinstall my apps w/o needing to download them all again?
Click to expand...
Click to collapse
I don't believe there is a way. Maybe someone smarter than myself can chime in but I had to let the play store do it's thing and re-download all of mine.

tgearhar said:
I finally got mine working again!
I tried a million different things so I'm going to try and explain my process as simple as I can, I apologize in advance because I am far from an expert...
First, I tried using the method, well some of it, from this thread: http://forum.xda-developers.com/showthread.php?t=1907796
- I would suggest using this thread to get everything set up (drivers, ADB, the factory image downloaded and in the correct file location) I wasn't able to get the drivers working correctly with that route so I ended up using the toolkit to get them working but that thread helped me get all of the system files in the correct location and helped get all of the ADB stuff set up.
Once you have everything set up and your computer recognizes the tablet, (I checked that by opening a cmd prompt and using the command from the original thread above "adb devices"). As long as you see your device, I think you should be good.
From the "No Command" screen I held down Power and Volume + to get the menu to come up. I then chose the Restart option and immediately held Power and Volume -. This got me into the Fastboot Mode.
Once in Fastboot mode I went to the cmd prompt on my computer and used the following commands in this order from this post:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system -w
fastboot flash system system.img
fastboot reboot
*Make sure that all of the image files are in the proper location on your computer otherwise this step is worthless
The tablet then rebooted normally and I was able to set everything up again. Again, I am by no means an expert at all, this is just what worked for me. Try at your own risk.
I hope I covered all of the steps, I tried a million different things last night so they all kind of run together.
Click to expand...
Click to collapse
Worked for me! Thanks, I don't believe I had USB Debugging enabled either. Shame it wiped all my data though.

OK, got mine back up and running! I'll just leave what I did here in case anyone can benefit from it.
I first used Wug's Toolkit to download and install the RAW drivers. (Option #4, I believe) They were the only ones that worked for me. I followed the instructions to install them and then when it looped to the No Command screen, I held volume up and power. This got me to the menu, where I chose reboot. I then immediately held down the volume button and power to get into the bootloader screen, where it (thankfully) stopped looping. Then I unlocked the bootloader using the one-click option. Next step was to download and flash factory 4.4 image using the Soft Brick mode. Fastboot recognized my device and pushed the image. Now all is well. Close call... I've already enabled USB Debugging for my wife on this tablet so that crap doesn't happen again. She did lose all her data but she is happy to have a working tablet again instead of a $200 beer coaster.

killswitch11 said:
OK, got mine back up and running! I'll just leave what I did here in case anyone can benefit from it.
Click to expand...
Click to collapse
Worked for me as well. Really appreciate that.
Sent from my Nexus 5 using Tapatalk

killswitch11 said:
OK, got mine back up and running! I'll just leave what I did here in case anyone can benefit from it.
I first used Wug's Toolkit to download and install the RAW drivers. (Option #4, I believe) They were the only ones that worked for me. I followed the instructions to install them and then when it looped to the No Command screen, I held volume up and power. This got me to the menu, where I chose reboot. I then immediately held down the volume button and power to get into the bootloader screen, where it (thankfully) stopped looping. Then I unlocked the bootloader using the one-click option. Next step was to download and flash factory 4.4 image using the Soft Brick mode. Fastboot recognized my device and pushed the image. Now all is well. Close call... I've already enabled USB Debugging for my wife on this tablet so that crap doesn't happen again. She did lose all her data but she is happy to have a working tablet again instead of a $200 beer coaster.
Click to expand...
Click to collapse
I'll give that a go tomorrow. Missed my tablet! Hope it works!

D800 I'm sure it's bricked, just want clarification

Alright, so I'm stuck in boot loop, the only recovery I can boot into is stock, which doesn't help obviously. I can't get into download mode, and my computer doesn't detect it. Just tell me the bad news.

Have you removed the LG drivers completely and reinstalled them? How did you get into the bootloop in the first place?
Sent from my LG-D800 using XDA Premium 4 mobile app

whynottry said:
Alright, so I'm stuck in boot loop, the only recovery I can boot into is stock, which doesn't help obviously. I can't get into download mode, and my computer doesn't detect it. Just tell me the bad news.
Click to expand...
Click to collapse
Let me see.. If by download mode you mean the blue dots(circles) then - no, you're not in download mode. But if you can enter teh real download mode (it should go past the circles) then you can flash it ( you should be able to flash it).
More info please.

bender_007 said:
Let me see.. If by download mode you mean the blue dots(circles) then - no, you're not in download mode. But if you can enter teh real download mode (it should go past the circles) then you can flash it ( you should be able to flash it).
More info please.
Click to expand...
Click to collapse
There's a lot of info in his previous posts. We went through hell and back trying to fix it. Hopefully you can give some better guidance.

Art Vanderlay said:
There's a lot of info in his previous posts. We went through hell and back trying to fix it. Hopefully you can give some better guidance.
Click to expand...
Click to collapse
Damn. I've read "I CAN get into download mode and ...." :/
will look into it to help out
one question : how did you brick it ?

Let me copy paste my previous three posts.
"When I originally tried to install TWRP, I was rooted in a stock rom, or whatever you call it when you're rooted and haven't installed a rom yet. When I tried originally, I went through CWM and installed it through that, but whenever I rebooted into recovery, I got the android with the caution sign in its chest. I kept trying to install it, and eventually I believe I used the flashify app to install it(the version I believe was 2.6.3.3) and I tried to boot again and it went into a boot loop, and began making a bunch of drives. I used this http://forum.xda-developers.com/show....php?t=2582142to get me into TWRP, and it worked. Problem is, I have no roms, no backups, no download mode, and my computer only recognizes my phone as 'g2'. I tried to install adb drivers manually so that the computer would recognize it as an adb device, but it gave me error:closed, and that's where we are right now. Quite a hole I have dug myself into, huh?"
"Ok, so I went back into linux -- I have dual boot for windows 7 and ubuntu -- and for some reason adb worked there, so I was able to adb sideload a cwm .img. But of course, I got excited because I thought it would just fix it but now I'm stuck in fastboot mode, and still can't get into download mode."
"I tried it, and now it is stuck in a bootloop and isn't detected by my computer. Only thing I can boot into is stock recovery. Looks like this is the end of my G2.."
I truly do think there's nothing that can be done, just from a logical standpoint. It isn't detected by anything on the computer and can only boot stock recovery which doesn't help at all. I do appreciate the help, though.
bender_007 said:
Damn. I've read "I CAN get into download mode and ...." :/
will look into it to help out
one question : how did you brick it ?
Click to expand...
Click to collapse

Ugh..so no fastboot either :/
fastboot was good.

Hard Bricked my Verizon LG G2

Hello, I am a new member and I'm having a hard time trying to fix my phone.
Currently, I can't go into any mode. I have neither fastboot or download mode.
I also can't get into my twrp through factory reset since it tries to reboot my phone.
However, whenever it tries to reboot, I get error: Boot certification verify and the screen goes dark.
I have tried to solve it by following this thread:
http://forum.xda-developers.com/showthread.php?t=2582142 but nothing has worked so far.
Can anyone please help me?

rawtomato said:
I also can't get into my twrp through factory reset since it tries to reboot my phone.
Click to expand...
Click to collapse
By that do you mean you can't even get to the factory reset screen at all? Or you do get there but when you select the option to reset, it simply reboots at that time?

iowabowtech said:
By that do you mean you can't even get to the factory reset screen at all? Or you do get there but when you select the option to reset, it simply reboots at that time?
Click to expand...
Click to collapse
I get there and selecting reset reboots the phone. However, an error about phone ceritication verify pops up

If you have access to a Windows machine, plug it in while on that dark screen and open device manager. Does anything show up relating to Android, Qualcomm, etc? If need be, unplug it while watching device manager then replug. Is the device showing up at all and if so, what's it called?
edit: also try long pressing power for 15 seconds to turn off the device completely. Then short press power (2-3 secs) as though restarting the phone from an off state. Does it boot into the OS then or no?

iowabowtech said:
If you have access to a Windows machine, plug it in while on that dark screen and open device manager. Does anything show up relating to Android, Qualcomm, etc? If need be, unplug it while watching device manager then replug. Is the device showing up at all and if so, what's it called?
edit: also try long pressing power for 15 seconds to turn off the device completely. Then short press power (2-3 secs) as though restarting the phone from an off state. Does it boot into the OS then or no?
Click to expand...
Click to collapse
Thanks for the reply! I have tried that and my computer recognizes my phone as LGE Android Phone. It seems like I can't get into any mode at all

rawtomato said:
Thanks for the reply! I have tried that and my computer recognizes my phone as LGE Android Phone. It seems like I can't get into any mode at all
Click to expand...
Click to collapse
Hmm, that's not so good. Most of the people who've been experiencing this have accepted either willingly or unknowingly, the new vzw ota update. But others have still been able to boot into the OS normally. It's booting to system from recovery that's been the only problem for them which makes sense considering aboot and boot were updated with the ota. That will break the loki <>TWRP connection since we need a downgraded aboot (JB) and a patched kernel for proper function. Hence the secure boot error.

iowabowtech said:
Hmm, that's not so good. Most of the people who've been experiencing this have accepted either willingly or unknowingly, the new vzw ota update. But others have still been able to boot into the OS normally. It's booting to system from recovery that's been the only problem for them which makes sense considering aboot and boot were updated with the ota. That will break the loki <>TWRP connection since we need a downgraded aboot (JB) and a patched kernel for proper function. Hence the secure boot error.
Click to expand...
Click to collapse
Where should I go from here to fix my phone? Sorry for no knowledge but I am still new to rooting an android phone..

rawtomato said:
Where should I go from here to fix my phone? Sorry for no knowledge but I am still new to rooting an android phone..
Click to expand...
Click to collapse
I would hold tight for awhile and see if anybody else has a more simple plan because I do not. The only thing I can think of with no boot, no recovery, no download mode AND no bulk mode, is to try and force bulk mode as described here:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
...then use Linux to fix as described here:
http://forum.xda-developers.com/showthread.php?t=2582142
(though I would ammend those intructs slightly to include the dd writing of boot and laf also to restore download mode)
...and then use a restored download mode to return to stock using a vs980 tot as described here:
http://forum.xda-developers.com/showthread.php?t=2432476
An unfortunately long and less than simple path back to a booting phone, especially for someone new to root. Again, hopefully somebody else can offer up a better plan.

Be very careful
rawtomato said:
Where should I go from here to fix my phone? Sorry for no knowledge but I am still new to rooting an android phone..
Click to expand...
Click to collapse
I was in exact same spot, until I got into the dd / phone partitions part under Linux. AN ERROR THERE COULD BE FATAL.
Please be very careful, look for a thread on recovering from "Secure Boot Error" (havent found one specific for that yet) Alot of people had success using the Linux method, I did not (vs980) probably because of a typo (keyboard error, mine) using the dd command.
I'm not saying don't try it, I AM saying use extreme care make no keyboard errors

iowabowtech said:
I would hold tight for awhile and see if anybody else has a more simple plan because I do not. The only thing I can think of with no boot, no recovery, no download mode AND no bulk mode, is to try and force bulk mode as described here:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
...then use Linux to fix as described here:
http://forum.xda-developers.com/showthread.php?t=2582142
(though I would ammend those intructs slightly to include the dd writing of boot and laf also to restore download mode)
...and then use a restored download mode to return to stock using a vs980 tot as described here:
http://forum.xda-developers.com/showthread.php?t=2432476
An unfortunately long and less than simple path back to a booting phone, especially for someone new to root. Again, hopefully somebody else can offer up a better plan.
Click to expand...
Click to collapse
It seems like i have messed my phone up really badly.. Thank you for the ideas but yes, I will continue to look for more options for now
Edit: I have never tried the first method you showed me before but I have tried the second and the third method and did not work. Would I be able to fix it if I take it to a shop?

virginwidow said:
I was in exact same spot, until I got into the dd / phone partitions part under Linux. AN ERROR THERE COULD BE FATAL.
Please be very careful, look for a thread on recovering from "Secure Boot Error" (havent found one specific for that yet) Alot of people had success using the Linux method, I did not (vs980) probably because of a typo (keyboard error, mine) using the dd command.
I'm not saying don't try it, I AM saying use extreme care make no keyboard errors
Click to expand...
Click to collapse
Thanks for your reply but I absolutely have no idea how to get into the dd / phone part using linux. I'll continue to look for more threads close to my problem but I have no clue as of yet.

SOLVED: no boot, no recovery, no adb

Hi,
I'm using TRWP 2.8 on my nexus10. While flashing a new ROM TRWP hangs (30 Minutes) and I have to turn off the device. Now I only can start the bootloader, nothing more. I have tried to get an adb connection but no device is found. I have tried it from my mac and also from a win10 .
Is my device now dead for ever ??
Thx
harvey

harvey186 said:
Hi,
I'm using TRWP 2.8 on my nexus10. While flashing a new ROM TRWP hangs (30 Minutes) and I have to turn off the device. Now I only can start the bootloader, nothing more. I have tried to get an adb connection but no device is found. I have tried it from my mac and also from a win10 .
Is my device now dead for ever ??
Thx
harvey
Click to expand...
Click to collapse
Turn it on and let the battery run completely empty. Recharge and try again.

mr.natural said:
Turn it on and let the battery run completely empty. Recharge and try again.
Click to expand...
Click to collapse
I know this trick and I have tried it two times. But it's still the same. And by the way, I can't stop booting. Either it's booting til the "Google" is shown or when I push the volume button it's booting into the boot loader. But it never stops booting.

harvey186 said:
Hi,
I'm using TRWP 2.8 on my nexus10. While flashing a new ROM TRWP hangs (30 Minutes) and I have to turn off the device. Now I only can start the bootloader, nothing more. I have tried to get an adb connection but no device is found. I have tried it from my mac and also from a win10 .
Is my device now dead for ever ??
Thx
harvey
Click to expand...
Click to collapse
you ****ed up the partitions most likely. If you can get fastboot then restore stock firmware (fresh start that sh*t my n****). If you can't get any fastboot connection at all, try reinstalling the drivers and sh*t. If that doesn't fix it, I think you're ****ed.
heres a new one for 100$ https://www.amazon.com/gp/product/B06XNX91YB/

Galaxyninja66 said:
you ****ed up the partitions most likely. If you can get fastboot then restore stock firmware (fresh start that sh*t my n****). If you can't get any fastboot connection at all, try reinstalling the drivers and sh*t. If that doesn't fix it, I think you're ****ed.
heres a new one for 100$ https://www.amazon.com/gp/product/B06XNX91YB/
Click to expand...
Click to collapse
Thx for help. Yesterday I have found a solution. While the black boot screen which the Google shows I get a adb connection to the N10. So I was able the start 'adb reboot recovery' and the device was booting into TWRP And now I was able to flash OmniROM 7.2.1

harvey186 said:
Thx for help. Yesterday I have found a solution. While the black boot screen which the Google shows I get a adb connection to the N10. So I was able the start 'adb reboot recovery' and the device was booting into TWRP And now I was able to flash OmniROM 7.2.1
Click to expand...
Click to collapse
You can better use TWRP 3.1.1 for manta. File: https://androidfilehost.com/?fid=961840155545587690