I'm not new to clockwork recovery, and I have flashed many Roms on my Nexus 7........ today I did a full back up of my latest ROM and I downloaded the latest version of the bug less beast .....I let rom manager do the back up and flash......then there was an error flashing the new rom and an abort and a reboot.......no im stuck on the google screen with the little un-locked lock at the bottom of the screen......if I reboot and go into recovery it just goes back to the google screen and stays there.....any clue as what I should do ??
Search around the forums for solutions.
Use the Wugs toolkit to make your work easier.
It's not bricked its standard procedure you just need to plug it in
Sent from my ADR6425LVW using xda premium
download .zip from google and restore it to your tablet (this is full wipe)
a1exus said:
download .zip from google and restore it to your tablet (this is full wipe)
Click to expand...
Click to collapse
To manually enter recovery from the bootloader on devices prior to 4.1.2 (don't know if it was fixed. its a glitch from google in the bootloader) you must have the USB (OEM of course) connected to a USB port on the computer. Then you can boot to bootloader and use the volume buttons to enter recovery. It may take trying a few times, like connect to usb port before powering on, connect to USB port once you're in the bootloader, etc, but that's your only issue unless when you panicked you tried some other solutions.
CharliesTheMan said:
To manually enter recovery from the bootloader on devices prior to 4.1.2 (don't know if it was fixed. its a glitch from google in the bootloader) you must have the USB (OEM of course) connected to a USB port on the computer. Then you can boot to bootloader and use the volume buttons to enter recovery. It may take trying a few times, like connect to usb port before powering on, connect to USB port once you're in the bootloader, etc, but that's your only issue unless when you panicked you tried some other solutions.
Click to expand...
Click to collapse
My recovery is not working I flashed clockwork mod and something happened to the recovery.....its like it not there....there is an option for it but when I enter it it just goes back to the google screen
GCSM said:
My recovery is not working I flashed clockwork mod and something happened to the recovery.....its like it not there....there is an option for it but when I enter it it just goes back to the google screen
Click to expand...
Click to collapse
dude, i'm told you what you need to do, i had erased manually my bootloader,recover,system,data and i was able to restore w/ what i told you it worked w/out any issues
Get fastboot. plug into your computer and do these:
fastboot flash recovery recovery.img (recovery.img is whatever file you have for recovery. IMO, get the newest touch recovery from CWM and have it in the same directory as fastboot)
fastboot reboot-bootloader
From there, leave it PLUGGED IN and get back into recovery. Worked for me.
Related
hey guys i'm having some trouble. i just got the nexus (it's my first smartphone, ever) and i've tried to hit the ground running. here's what i've done to the phone so far.
i got all the drivers running on my win7 machine and also installed the android SDK folder onto C: as was described in this thread: http://forum.xda-developers.com/showthread.php?t=878786
i then unlocked the bootloader using the above guide as well. when I power on the phone using UP+POWER it says UNLOCKED.
I then proceeded to follow this guide: http://forum.xda-developers.com/showthread.php?t=875875
i used ADB to flash the clockwork crespo recovery. i then used fastboot to install Superuser.
at that point i had an unlocked bootloader, clockword recovery image and superuser permissions.
i then saw that the 2.3.1 update had been released. i wanted to learn how to tackle that so i started reading up. i noticed that people were using ROM Manager and Titanium. I got titanium and installed the BusyBox addon and it allowed me to do a full Batch Backup of all my programs, etc. i've got the 50MB or so backup folder on my PC now.
anyway, i then messed with Rom Manager. I installed the 3.0.0.0 ClockworkMod Recovery and everything went smoothly. now this is where my troubles begin.
when i go to Download ROM all i get is a Free Stuff area.
when i go to Check for ROM Updates it tells me my device isnt set up for OTA updates.
those are just minor issues.
this is the big and scary issue i have:
when i click on reboot to recovery, it takes me to the same screen that i go to when i power on with VOLUME UP+POWER. it doesnt take me to the recovery screen that i see in various youtube videos. instead, i'm at the main screen where it says UNLOCKED and i have 4 choices (reboot bootloader, recovery, reboot, power off). and on the very top in RED letters it says fastboot - no boot or img file. <-- this is the part that makes me nervous. If i manually power down the phone and boot to fastboot and click recovery, it just goes back to this same screen and says fastboot - no boot or img file. when i first rooted the phone, clicking recovery actually took me to a different screen where i was able to load up superuser.zip and install it.
did i accidetnally delete something that i wasnt supposed to? did installing ROM manager mess something up? i typically dont do anything until i confirm that i am supposed to. i think the problem is that i dont yet know how one thing i do on the phone affects another. i'm guessing when i used rom manager to update the CWmod it changed some folders/files? i dunno!
otherwise, the phone works fine and there are no glitches or hiccups or crashes. So if someone can please take a moment to just explain to me what i did wrong or what i failed to do i'd really, really appreciate it.
you don't have a recovery partition. Either flash one over manually using fastboot, or boot up and try to use ROM Manager to flash CWR.
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
yes, just follow the examples in http://forum.xda-developers.com/showthread.php?t=875875
kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.
unremarked said:
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.
Click to expand...
Click to collapse
thank you luxferro and unremarked. i did it and it works perfectly. i am now able to access clockworkmod recovery 3.0.0.0. next step is backup my existing ROM and also to figure out how to put the OTA 2.3.1 on and restore all my data
oh and unremarked: it basically said no boot or img file and thats it after i would click on recovery or reboot to recovery trhough rom manager. it was just in red at the top. but now it takes me to the ClockworkMod Recovery
Anyone else have this problem?
numus said:
Anyone else have this problem?
Click to expand...
Click to collapse
So is fastboot the problem or are you trying to boot to recovery through the bootloader. I would use ADB instead of fastboot. But if what you're asking is that you want to boot to recovery from the bootloader, just connect your USB cable to your computer and then select recovery in the bootloader.
CharliesTheMan said:
So is fastboot the problem or are you trying to boot to recovery through the bootloader. I would use ADB instead of fastboot. But if what you're asking is that you want to boot to recovery from the bootloader, just connect your USB cable to your computer and then select recovery in the bootloader.
Click to expand...
Click to collapse
Pretty sure it is fastboot... You use the volume rocker to select recovery and hit the power button... It shows the Bootscreen but doesn't go any further than that.
Edit: it says in red FASTBOOT MODE.. When i select recovery it goes tot he google screen (witht he unlock icon) and doesn't go any further than that.
numus said:
Anyone else have this problem?
Click to expand...
Click to collapse
I'm having trouble too. I have it plugged in to my laptop. When I select "Recovery" and press Power, it just reboots, and then boots into Android.
No recovery.
So I'm gonna try TWRP..
i had the same issue this is what i did
download new recovery h**p://goo.im/devs/OpenRecovery/grouper/openrecovery-twrp-2.2.1.4-grouper.img
then in fastboot
fastboot erase recovery
fastboot flash recovery name_of_recovery.img
wait 15 seconds
unplug usb cable
then use volume keys to boot in to recovery
hope this helps
so any solution at the same screen, same problem.
dj_denims said:
i had the same issue this is what i did
download new recovery h**p://goo.im/devs/OpenRecovery/grouper/openrecovery-twrp-2.2.1.4-grouper.img
then in fastboot
fastboot erase recovery
fastboot flash recovery name_of_recovery.img
wait 15 seconds
unplug usb cable
then use volume keys to boot in to recovery
hope this helps
Click to expand...
Click to collapse
You want to be in the bootloader mode and select recovery. The trick is that to do that, you have to have your Asus USB cable connected to a live usb port when you do it, and it usually works if recovery isn't damaged.
And you can also use Wug's toolkit on the computer, or if you can boot the tablet, you can use goo manager to reboot to recovery, or the Trinity kernel app, or your rom's advanced power menu.
With the USB cable attached from the computer to tablet, here's what I did:
- Went to bootloader
- Did "fastboot erase recovery"
- Did "fastboot flash recovery IMG"
- Then boot to recovery manually from the device itself via volume buttons and Power
Hasn't failed me yet when trying out different recoveries. There was some issue a while back where you had to have the USB cable hooked to your computer and Nexus 7 in order to get to recovery. Not sure if the bug still exists, but it may be worth trying with the cable in.
Also you probably have to have an unlocked bootloader (lock at bottom of Google boot screen).
dj_denims said:
i had the same issue this is what i did
download new recovery h**p://goo.im/devs/OpenRecovery/grouper/openrecovery-twrp-2.2.1.4-grouper.img
then in fastboot
fastboot erase recovery
fastboot flash recovery name_of_recovery.img
wait 15 seconds
unplug usb cable
then use volume keys to boot in to recovery
hope this helps
Click to expand...
Click to collapse
Thanks for that.
That worked for me
Does the USB port you're plugged into need to be a computer with the fastboot drivers already installed? My unit freezes up in bootloader every time I plug in any live USB cable, whether it's a computer or not. My recovery is fine, but with the bootloader constantly freezing I'm not able to install the N7 drivers on my computer, let alone input any fastboot commands. And no, I don't have access to the computer with the drivers already installed sadly.
Sent from my SGH-T989 using xda premium
Turn it off plug USB lead into PC/laptop and nexus hold volume up and down and turn it on, or it also works via my otg cable in my s3 also, its a bug..
Sent from my Nexus 7 using Tapatalk 2
a stupid bug.buoght yesterday,rooted and unlocked.downloaded 10 roms,all kernels,and now that i'm ok to begin test i tried without luck to enter recovery from fastboot (i didn't know this fact)but my cable was inserted on pc usb port...and strange it doesn't work.yestrerday via fastboot i flashed twrp recovery that i love and use also on mine gnexs.i'm on stock rom yet,and without "reboot to recovery" option in powermenu.i reflashed twrp,cwm touch (in fastboot manually)then the same but with a rootkit,no luck.i began to think i have a problem in my device and i don't know how to do because it's a secondary bug for assistance i think..and i read this post.don't even tried commands in few posts ago,already did same things an hour ago.i installed quickboot frm playstore and now i can boot on TWRP.use this for today,when i begin to test roms i'll have the powermenu option!
Sad this,i'm a bit anxious of this bug,because i soft brick gnex every 2\3 days,always trying things and stuff,kernel with modifications by me etc,and i often have to go in cwm via devices off and fastboot before...i see that my tab attacched at pc don't enter recovery from fastboot mode..and it's a problem for me.hope someone discover where is this bug and find a workaround\fix fro that.
cheers
sert00 said:
a stupid bug.buoght yesterday,rooted and unlocked.downloaded 10 roms,all kernels,and now that i'm ok to begin test i tried without luck to enter recovery from fastboot (i didn't know this fact)but my cable was inserted on pc usb port...and strange it doesn't work.yestrerday via fastboot i flashed twrp recovery that i love and use also on mine gnexs.i'm on stock rom yet,and without "reboot to recovery" option in powermenu.i reflashed twrp,cwm touch (in fastboot manually)then the same but with a rootkit,no luck.i began to think i have a problem in my device and i don't know how to do because it's a secondary bug for assistance i think..and i read this post.don't even tried commands in few posts ago,already did same things an hour ago.i installed quickboot frm playstore and now i can boot on TWRP.use this for today,when i begin to test roms i'll have the powermenu option!
Sad this,i'm a bit anxious of this bug,because i soft brick gnex every 2\3 days,always trying things and stuff,kernel with modifications by me etc,and i often have to go in cwm via devices off and fastboot before...i see that my tab attacched at pc don't enter recovery from fastboot mode..and it's a problem for me.hope someone discover where is this bug and find a workaround\fix fro that.
cheers
Click to expand...
Click to collapse
Paragraphs dude? Or at the very least, proper spacing.
On stock rooted rom, flash latest TWRP recovery. openrecovery-twrp-2.2.2.0-grouper.img
adb reboot bootloader
fastboot flash recovery openrecovery-twrp-2.2.2.0-grouper.img
Then install Rom Toolbox. Use the "Rebooter" to Reboot recovery, and you should have no issues.
..
mvmacd said:
Paragraphs dude? Or at the very least, proper spacing.
On stock rooted rom, flash latest TWRP recovery. openrecovery-twrp-2.2.2.0-grouper.img
adb reboot bootloader
fastboot flash recovery openrecovery-twrp-2.2.2.0-grouper.img
Then install Rom Toolbox. Use the "Rebooter" to Reboot recovery, and you should have no issues.
Click to expand...
Click to collapse
I did this and I still can't boot into recovery. The only way I can boot into recovery is if I use the fastboot command. The rom toolbox does not work for me.
similar problem
I have somewhat similar problem. Well, actually the problem is not very uncommon the way it looks, but usual solutions do not work.
Basically I have erased my old rom (rebooted to recovery from aokp menu) and erased my rom. I've tried mounting the device from the recovery mode, but it was not recognised on my PC. I assumed that this was an Win8 issue.
Once I've rebooted, I could no logger boot to recovery (after selecting recovery all I got was google logo). I've thought of flashing recovery via fastboot, but bootloader seams to freeze with usb cable in (no matter the cable) and resetting does not help (the way it helped others). Also I cannot fastboot at that time either as PC (neither win8 nor win7 machine can see the device).
Any ideas would be appreciated.
When the bootloader freezes with the usb cable plugged into a PC, it is a driver issue. Uninstall and reinstall the drivers. I have experienced this on a win7 x64 system.
It isn't a driver issue as the same thing happens when connecting to a charger and not the PC.
It happens on mine as well.
Well it wouldn't crash with wall charger if it was a PC driver issue.
In either case, I've actually figured out what's the problem. It seems that usb connector is not very reliable. If the it usb connection is poor, the bootloader crashes. To avoid this issue you have to bend the cable towards the screen to ensure the proper connection. It load that way just fine.
Edit: or not... probably bending just removed the connection completely...
Edit2: did not figure out what was the problem, but after playing around some more, the phone has popped up in computer manager and I was able to continue from there. After flashing the recovery (twm -> cwm), the bootloader un-froze as well.
I was running ParanoidAndroid perfectly until it crashed and not it gets stuck at the loading screen of the ROM (not the Google logo). I'm able to turn it off and get into Bootloader. From there if I choose Recovery mode, it gets stuck at Google logo.
If I plug it into the PC while in booatloader, it gets detected as "Android" but no driver (I'm sure I installed it before with the Toolkit). Toolkit just won't detect the device anymore, keeps getting stuck at the <waiting for device> command.
If I plug it into the PC while stuck at the ParanoidAndroid loading screen, I see MTP and Nexus in Device Manager but w/o drivers.
What can I do now? Any input is appreciated.
Thanks.
Bump.
Itaintrite said:
Bump.
Click to expand...
Click to collapse
Have you tried fastboot from the bootloader? Try this(assuming Windows):
-copy your recovery image of choice to your fastboot folder on your PC.
-boot to the bootloader with usb connected.
-open cmd window and navigate to fastboot folder
-type: fastboot boot insertrecoverynamehere.img
It should boot into the recovery from there. Make sure it's the same recovery you used for your latest backup.
Edit: I just read the subject line saying fastboot didn't work. Odd that it would just stop working from the bootloader like that. Have you tried manually updating the driver? Or maybe adb when it recognizes the device as MTP?
Xentar712 said:
Have you tried fastboot from the bootloader? Try this(assuming Windows):
-copy your recovery image of choice to your fastboot folder on your PC.
-boot to the bootloader with usb connected.
-open cmd window and navigate to fastboot folder
-type: fastboot boot insertrecoverynamehere.img
It should boot into the recovery from there. Make sure it's the same recovery you used for your latest backup.
Edit: I just read the subject line saying fastboot didn't work. Odd that it would just stop working from the bootloader like that. Have you tried manually updating the driver? Or maybe adb when it recognizes the device as MTP?
Click to expand...
Click to collapse
Thanks for the suggestion, but I figured out the problem. I'm such a dumbass. I forgot that last time I did this on a friend's computer. Apparently, the toolkit doesn't work properly on Windows 8 64-bit... (at least not on mine). I plugged it into a friend's laptop running W7 and was able to flash recovery again. Smooth sailing from there. Wonder what corrupted recovery.
Itaintrite said:
Thanks for the suggestion, but I figured out the problem. I'm such a dumbass. I forgot that last time I did this on a friend's computer. Apparently, the toolkit doesn't work properly on Windows 8 64-bit... (at least not on mine). I plugged it into a friend's laptop running W7 and was able to flash recovery again. Smooth sailing from there. Wonder what corrupted recovery.
Click to expand...
Click to collapse
I've never been able to cold boot my recovery - only through the goomanager app(for TWRP). I believe it's a known bug. I can only boot recovery from the bootloader when my N7 is plugged into my laptop via usb. Power or another laptop don't count. Oddly enough, It also works if I plug it into my Galaxy Nexus via USB+OTG.
Xentar712 said:
I've never been able to cold boot my recovery - only through the goomanager app(for TWRP). I believe it's a known bug. I can only boot recovery from the bootloader when my N7 is plugged into my laptop via usb. Power or another laptop don't count. Oddly enough, It also works if I plug it into my Galaxy Nexus via USB+OTG.
Click to expand...
Click to collapse
Hm, perhaps that was the problem? But I was able to cold boot into recovery after reflashing TWRP... Anyhow, I'm glad I didn't have to restore a recovery image as I haven't made a backup since the last PA update
Itaintrite said:
Hm, perhaps that was the problem? But I was able to cold boot into recovery after reflashing TWRP... Anyhow, I'm glad I didn't have to restore a recovery image as I haven't made a backup since the last PA update
Click to expand...
Click to collapse
It worked for me only once after reflashing the recovery. Never again after that. Hopefully it gets fixed soon, but until then, I carry my USB cables with me if I'm flashing new roms
Sent from my Nexus 7 using Tapatalk 2
I am trying to root my Nexus 10. This is what I did, but it ended up bricked!
I installed the Android SDK on my Windows 7 computer, and downloaded the Android USB drivers and tools.
I turned on USB debugging, and checked I could see the device with adb list devices.
I downloaded recovery-clockwork-touch-6.0.4.3-manta.img, booted the tablet into bootloader, and flashed it
Code:
fastboot oem unlock
fastboot flash recovery recovery-clockwork-touch-6.0.4.3-manta.img
That seemed to work, so I went into recovery, but recovery had all sorts of errors - it couldn't find the sdcard, or mount most of the partitions.
Rebooting stops in the animated logo, apparently for ever.
I have since tried to reload the factory image, but the computer no longer recognises the device - fastboot devices returns nothing.
Help!!!
[Later] The tablet was running the latest O/S (if I could boot it, I could tell you the number!)
Things have got worse. Now, when I go into bootloader mode, the volume keys don't do anything any more, so I can't even turn it off now
Make sure fastboot is set up properly, may need to reinstall drivers or try another computer or try another USB
http://forum.xda-developers.com/showthread.php?t=2277112
I have a feeling the recovery you flashed was corrupt in some way, did you by chance check the md5sum of the image first?
If your able to get fastboot to recognize tab
fastboot erase recovery
fastboot erase system -w
fastboot erase boot
Download latest twrp recovery
Check md5sum
fastboot flash recovery nameofrecovery.img
Then you will either need to flash stock system.img from fastboot or boot to new recovery and adb sideload a ROM
Hopefully your emmc is not to severely corrupt to all this, best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Thanks, that was pretty much what I did. The trick was to get it working in boot loader mode. I kept trying to reboot it, and in the end holding down power plus both volume up and down all at the same time for 2 beeps made it work.
Sent from my Nexus 10 using Tapatalk
nikkilocke said:
I am trying to root my Nexus 10. This is what I did, but it ended up bricked!
I installed the Android SDK on my Windows 7 computer, and downloaded the Android USB drivers and tools.
I turned on USB debugging, and checked I could see the device with adb list devices.
I downloaded recovery-clockwork-touch-6.0.4.3-manta.img, booted the tablet into bootloader, and flashed it
Code:
fastboot oem unlock
fastboot flash recovery recovery-clockwork-touch-6.0.4.3-manta.img
That seemed to work, so I went into recovery, but recovery had all sorts of errors - it couldn't find the sdcard, or mount most of the partitions.
Rebooting stops in the animated logo, apparently for ever.
I have since tried to reload the factory image, but the computer no longer recognises the device - fastboot devices returns nothing.
Help!!!
[Later] The tablet was running the latest O/S (if I could boot it, I could tell you the number!)
Things have got worse. Now, when I go into bootloader mode, the volume keys don't do anything any more, so I can't even turn it off now
Click to expand...
Click to collapse
I have the same problem, however I can't access my Nexus 10, fastboot devices and adb devices gives back an empty line, so I can't access the N10 with fastboot or adb, to lash a ROM. Factory reset from CWM doesn't work, ˛internal card can't be accessed from CWM ("E: Can't mount /sdcard).
How can I get out of this trouble? (Solutions in forums usually involve reflashing with fastboot or formatting the external SD card. These solutions don't work here...
Any idea would be highly appreciated...
Csaba
Keep trying to reboot into bootloader mode, until it works. Hold down power and both volume buttons at the same time until it beeps twice. If the volume buttons then work to change the option on the left, but fastboot devices on the pc shows nothing, try reinstalling the Google drivers on the pc (via Device Manager, update drivers, have disk). (may have missed out a step in device manager instructions, but there are plenty of Google hits on installing add drivers if you don't already know how).
Sent from my Nexus 10 using Tapatalk
nikkilocke said:
Keep trying to reboot into bootloader mode, until it works. Hold down power and both volume buttons at the same time until it beeps twice. If the volume buttons then work to change the option on the left, but fastboot devices on the pc shows nothing, try reinstalling the Google drivers on the pc (via Device Manager, update drivers, have disk). (may have missed out a step in device manager instructions, but there are plenty of Google hits on installing add drivers if you don't already know how).
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
Sorry, I don't understand what you mean.
I can get into into bootloader mode after keeping the 3 buttons (power+volume up+volume down) pushed together (after two beeps). From there I can't boot the device. (Boot gets into the Google animation forever), so as factory reset.
Also device manager doesn't see the N10, so I can't update the drivers on my PC.
Csaba
---------- Post added at 05:17 PM ---------- Previous post was at 05:00 PM ----------
ixxion said:
Sorry, I don't understand what you mean.
I can get into into bootloader mode after keeping the 3 buttons (power+volume up+volume down) pushed together (after two beeps). From there I can't boot the device. (Boot gets into the Google animation forever), so as factory reset.
Also device manager doesn't see the N10, so I can't update the drivers on my PC.
Csaba
Click to expand...
Click to collapse
After some repeated turning off and on, now I can see the N10 from the PC (also updated the USB drivers to be on the safe side).
If I enter the bootloader, fastboot sees the N10 in a normal form, if from there I go into recovery mode, adb sees the N10 in recovery mode. Should I proceed from here by using fastboot, or rather adb?
Csaba
You should just use volume up + power (or the whatever the volume rocker button closer to power key) never had it beep to get there
To both of you, follow the steps from above, so long as it isn't a hardware issue this will get you working
Sent from my Nexus 7 using XDA Premium 4 mobile app
ixxion said:
After some repeated turning off and on, now I can see the N10 from the PC (also updated the USB drivers to be on the safe side).
If I enter the bootloader, fastboot sees the N10 in a normal form, if from there I go into recovery mode, adb sees the N10 in recovery mode. Should I proceed from here by using fastboot, or rather adb?
Csaba
Click to expand...
Click to collapse
Glad you have managed to make the device visible again (it's really scary when you can't, I know from yesterday!).
Go into bootloader mode (not recovery), and follow the fastboot instructions demkantor gave earlier in the thread.
Get your factory image from https://developers.google.com/android/nexus/images#mantaray.
Get TWRP recovery from http://teamw.in/project/twrp2/128.
At least, that's how I did it.
demkantor said:
Make sure fastboot is set up properly, may need to reinstall drivers or try another computer or try another USB
http://forum.xda-developers.com/showthread.php?t=2277112
I have a feeling the recovery you flashed was corrupt in some way, did you by chance check the md5sum of the image first?
If your able to get fastboot to recognize tab
fastboot erase recovery
fastboot erase system -w
fastboot erase boot
Download latest twrp recovery
Check md5sum
fastboot flash recovery nameofrecovery.img
Then you will either need to flash stock system.img from fastboot or boot to new recovery and adb sideload a ROM
Hopefully your emmc is not to severely corrupt to all this, best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How do I check md5sum?
Use this for windows
http://www.microsoft.com/en-us/download/details.aspx?id=11533
Or terminal for Linux
md5sum nameoffile.extention
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
You should just use volume up + power (or the whatever the volume rocker button closer to power key) never had it beep to get there
To both of you, follow the steps from above, so long as it isn't a hardware issue this will get you working
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you very much. Tablet is up and running again. :good:
Now, my next question, after being unsuccessful with CWM, I tried using TWRP for rooting the tablet, however it wouldnt start.
When I go from the bootloader into recovery mode only a laying android figure is displayed with a red triangle with an exclamation mark inside.
I have USB debugging enabled. What can be the problem?
ixxion said:
Thank you very much. Tablet is up and running again. :good:
Now, my next question, after being unsuccessful with CWM, I tried using TWRP for rooting the tablet, however it wouldnt start.
When I go from the bootloader into recovery mode only a laying android figure is displayed with a red triangle with an exclamation mark inside.
I have USB debugging enabled. What can be the problem?
Click to expand...
Click to collapse
That means you don't have twrp installed. That's the stock recovery. You can download twrp and use fastboot yo flash it or try the app twrp intaller which dies or fir you
Sent from my VS980 4G using xda app-developers app
I can't get into the bootloader/fastboot mode, is there something wrong?
Note I am now on stock 4.4 (including stock recovery/kernel etc.) but previously i had custom recovery and same error.
- tried rebooting into bootloader from recovery when I had philz and/or TWRP - would just boot into the OS
- tried power + button up (i.e. reverse of booting into recovery) - same, boots into OS
- tried quick boot root app - same, boots into OS
WTF
Not hugely concerned since I could get into recovery lol but why is it I can't get into bootloader/fastboot mode? What if the OS is broken and I need to ADB something?
Note I rooted/TWRP/PHilzed and went custom for awhile, then I made my own zip using below thread and a full kdz and flashed back to stock including recovery/kernel/baseband (I wanted to go back to 100% stock).
http://forum.xda-developers.com/showthread.php?p=52207783#post52207783
Thanks
Isn't the bootloader locked on the G2? Coming from a Nexus phone, I was also looking for the option but read it wasn't currently possible to unlock it.
I know we're BL locked, I meant fastboot or download mode or whatever the mode is where you can use adb commands and/or fastboot flash recovery recovery.img if I never need to manually fix recovery for example.
wintermute000 said:
I know we're BL locked, I meant fastboot or download mode or whatever the mode is where you can use adb commands and/or fastboot flash recovery recovery.img if I never need to manually fix recovery for example.
Click to expand...
Click to collapse
You can use ADB by enabling USB debugging in developer options.
Download mode can be enabled by turning the phone off, pushing power+Volume Up and then plugging in your phone to your PC with a USB cable - I've used this twice already to recover from experimenting with recoveries and ROMs (by going back to stock following instructions here: http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/)
GenghisKhan67 said:
You can use ADB by enabling USB debugging in developer options.
Download mode can be enabled by turning the phone off, pushing power+Volume Up and then plugging in your phone to your PC with a USB cable - I've used this twice already to recover from experimenting with recoveries and ROMs (by going back to stock following instructions here: http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/)
Click to expand...
Click to collapse
also i've found the phone won't boot in to recovery if it's on mains charge (via button combo not adb/in rom apps or APM)
GenghisKhan67 said:
You can use ADB by enabling USB debugging in developer options.
Download mode can be enabled by turning the phone off, pushing power+Volume Up and then plugging in your phone to your PC with a USB cable - I've used this twice already to recover from experimenting with recoveries and ROMs (by going back to stock following instructions here: http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/)
Click to expand...
Click to collapse
Thanks, the plugging in USB cable is probably the bit I'm missing!
I know I can use ADB with USB debugging, I'm asking the question if I need to recover from softbrick and can't get into OS