I have an unlocked/rooted WIFI only 16GB. I changed the boot animation and restarted my device. I get the Google startup screen then nothing but black screen afterwards. I can reboot into recovery, but if I have my computer connected I can not change the options (reboot, recovery, power off, ect...) without the computer connected it seems that nothing in recovery mode seems to work.
I know that the new boot animation is my issue. My original boot animation was just renamed, but is in the same file.
How can i delete my new boot animation file and rename the original one?
Fastboot mode details...
HW Version - ER3
bootloader version - 3.34
Lock state - Unlocked
Have you tried using sdk tools to push a stock boot animation?.if you cant select any options from the bootloader screen,you can use cmd from sdk and try your luck.
Sent from my Awesome HTC One X using XDA Premium
Related
I'm on 4.1.2 stock and wanted to update to 4.2, however I can't get to the recovery. First attempts: Turn n7 off, vol down + power, etc.., boot recovery: It then switches to the google logo (and this device is unlocked), screen flashes to black, google logo again, and it starts to boot normally. I've googled the problem found some things about needing a usb connected to a computer tried it didn't work, tried using a app to boot to recovery, didn't work. I used a toolkit to flash twrp recovery (and tired cwm later on), tried to boot into recovery again both manually and with a app, same thing happened.
Anyone have any idea what is going on?
The booting into recovery bug should be fixed in 4.1.2. Have you tried booting into the bootloader by holding both volume up and down and the power button at the same time when the phone is off? From there you can use the volume button to scroll to recovery and select it with the power button. If that doesn't work then you may have other issues. The custom recoveries may not have flashed with the toolkit or may have been over written on a reboot with stock recovery. You might try flashing twrp using fastboot and rename the recovery-from-boot file. http://www.teamw.in/project/twrp2/103
I am having the same issue.
First noticed something was wrong when Android asked me to update to 4.2 (OTA). I allowed the update and the device rebooted, only to come back in 4.1.2 without any sign of the update. Then I tried to do the update manually, but I can't seem to enter recovery mode in any way.
Things I tried:
* Boot while holding volume up + volume down -> Select Recovery Mode
* Boot while holding volume up + volume down and connected to a PC -> Select Recovery Mode
* Use Quick Boot to enter Recovery Mode
* Use Rom Manager to enter Recovery Mode
* Flash ClockworkMod Recovery through Rom Manager
* Flash ClockworkMod Touch through Rom Manager
* Flash TWRP Touch Recovery through Google Nexus 7 Toolkit
Each time I try to enter the Recovey Mode it will: Show the Google logo and the open padlock symbol for a few seconds -> Screen turns off -> Google logo and the open padlock symbol again -> Nexus logo -> Booted in normal mode. Seems like something errors when attempting to enter Recovery Mode and then it just boots normally.
I attempted the method on http://www.teamw.in/project/twrp2/103. Booting while holding down volume down will boot to FASTBOOT MODE, but the secreen does not say FASTBOOT USB when connecting it to a PC. I have the USB drivers from Google Nexus 7 Toolkit installed, do I need other drivers?
EDIT: So I finally got a custom recovery installed by doing a "fastboot flash recovery" of the latest TWRP (2.3.1.1) from here: http://teamw.in/project/twrp2/103
Neither of the current CWM recoveries (6.0.1.0) would work for me.
You are not alone. Same thing has happened to me. I manually flashed the 4.2 OTA zip yesterday from CWM and while that went fine, I have been unable to re-install a custom recovery ever since. I tried flashing CWM and TWRP from toolkit multiple times. I also did a manual fastboot flash of a newly download CWM but I am getting the same results as you. Nexus 7 will not boot into a custom recovery no matter what.
On the plus side, 4.2 is working well..... Would really like to get root back though.
Menthix said:
I am having the same issue.
First noticed something was wrong when Android asked me to update to 4.2 (OTA). I allowed the update and the device rebooted, only to come back in 4.1.2 without any sign of the update. Then I tried to do the update manually, but I can't seem to enter recovery mode in any way.
Things I tried:
* Boot while holding volume up + volume down -> Select Recovery Mode
* Boot while holding volume up + volume down and connected to a PC -> Select Recovery Mode
* Use Quick Boot to enter Recovery Mode
* Use Rom Manager to enter Recovery Mode
* Flash ClockworkMod Recovery through Rom Manager
* Flash ClockworkMod Touch through Rom Manager
* Flash TWRP Touch Recovery through Google Nexus 7 Toolkit
Each time I try to enter the Recovey Mode it will: Show the Google logo and the open padlock symbol for a few seconds -> Screen turns off -> Google logo and the open padlock symbol again -> Nexus logo -> Booted in normal mode. Seems like something errors when attempting to enter Recovery Mode and then it just boots normally.
I attempted the method on http://www.teamw.in/project/twrp2/103. Booting while holding down volume down will boot to FASTBOOT MODE, but the secreen does not say FASTBOOT USB when connecting it to a PC. I have the USB drivers from Google Nexus 7 Toolkit installed, do I need other drivers?
Click to expand...
Click to collapse
Sim2 said:
EDIT: So I finally got a custom recovery installed by doing a "fastboot flash recovery" of the latest TWRP (2.3.1.1) from here: http://teamw.in/project/twrp2/103
Neither of the current CWM recoveries (6.0.1.0) would work for me.
Click to expand...
Click to collapse
That actually does work, but I just didn't have any idea what I was doing first. Got it to work now.
If you are like me:...
* Before you go into fastboot/bootloader, get CWM-SuperSU-v0.98.zip and place it on your sdcard.
* Go to http://teamw.in/project/twrp2/103
* Download openrecovery-twrp-2.3.1.1-grouper.img
* Put it in the 'put_img_files_to_flash_here' folder of Google Nexus 7 Toolkit
* Boot while holding volume up + volume down and connected to a PC
* Start Google Nexus 7 Toolkit
* Select option 11
* Type the openrecovery-twrp-2.3.1.1-grouper.img filename
* Once it is done pushing the file to the phone, boot from it
* You can now install CWM-SuperSU-v0.98.zip to get root on 4.2
Menthix said:
I am having the same issue.
First noticed something was wrong when Android asked me to update to 4.2 (OTA). I allowed the update and the device rebooted, only to come back in 4.1.2 without any sign of the update. Then I tried to do the update manually, but I can't seem to enter recovery mode in any way.
Things I tried:
* Boot while holding volume up + volume down -> Select Recovery Mode
* Boot while holding volume up + volume down and connected to a PC -> Select Recovery Mode
* Use Quick Boot to enter Recovery Mode
* Use Rom Manager to enter Recovery Mode
* Flash ClockworkMod Recovery through Rom Manager
* Flash ClockworkMod Touch through Rom Manager
* Flash TWRP Touch Recovery through Google Nexus 7 Toolkit
Each time I try to enter the Recovey Mode it will: Show the Google logo and the open padlock symbol for a few seconds -> Screen turns off -> Google logo and the open padlock symbol again -> Nexus logo -> Booted in normal mode. Seems like something errors when attempting to enter Recovery Mode and then it just boots normally.
I attempted the method on http://www.teamw.in/project/twrp2/103. Booting while holding down volume down will boot to FASTBOOT MODE, but the secreen does not say FASTBOOT USB when connecting it to a PC. I have the USB drivers from Google Nexus 7 Toolkit installed, do I need other drivers?
Click to expand...
Click to collapse
It will be of no use to you, but may encourage others I suppose. One of your options above helped me. I managed to get the CWM recovery working by reinstalling it via Rom Manager, then dropping into Recovery via Quickboot (I know it's worked before so didn't try the Rom Manager route). Then I flashed 4.2 via the CWM recovery.
?
[did u solve ur problem?>??
I have a Nexus 4 with 4.2.2. I was following this guide to root:
http://forums.androidcentral.com/nex...t-4-2-2-a.html
On step 10, after choosing recovery, my phone is stuck at a blank & black screen. If I hold down power, power + volume down, or power + volume up, it just boots back into a black screen. It vibrates as if it's rebooting but won't get out of the black screen. Any ideas?
ctopher2391 said:
I have a Nexus 4 with 4.2.2. I was following this guide to root:
http://forums.androidcentral.com/nex...t-4-2-2-a.html
On step 10, after choosing recovery, my phone is stuck at a blank & black screen. If I hold down power, power + volume down, or power + volume up, it just boots back into a black screen. It vibrates as if it's rebooting but won't get out of the black screen. Any ideas?
Click to expand...
Click to collapse
Page not found. The easiest way to root your phone is to use the chainfire auto root. You need the Google SDK package installed for the ADB commands, unlock your bootloader, then run the auto root. You can flash CWM recovery or TWRP through the Rom manager app, or Goo manager app available via playstore. It sounds like you may have soft bricked it somehow.
did you ever figure this out?
Download a recovery (CWM)
Download and install the Android SDK if you haven't already (Or at least fastboot.exe)
Paste the recovery into the folder with fastboot.exe
Navigate to the folder with fastboot.exe in CMD (Command Line)
Plug in your phone
Boot into fastboot (I'm assuming your bootloader is unlocked)
Type in fastboot flash recovery (Recovery file name EXACTLY with the file extension, which should be .img I think)
Should have a working recovery
I have been having issues getting the drivers to work on my PC for fastboot and adb so I tried using flashify app to flash my boot loader... Now my nexus starts up to the Google screen and a "Start" button appears at the top... If i click start, nothing happens... I can move it to recovery and boot into recovery fine.. I can also switch it to boot into the boot loader, and the boot loader seems to load ok... any ideas?
I have an MB525 running Slimbean. I took the battery out mid boot the other day and now it won't progress beyond the boot animation.
The system is responsive, and when connected via ADB I can make changes. Tailing logcat just shows frequent garbage collection.
What is the best way to recover this? I've booted into recovery (vol down when blue LED), and if I select Team Win Recovery - nothing happens, selecting CWM recovery just causes it to boot as 'normal' (ie stuck at boot animation).
I'm not familiar enough with the boot process on this to know where to start adb pushing files to fix this. I'm aware that I could bring it back to stock with RSDLite and start again, but considering I have root access via ADB, I was hoping that there'd be a better way to do this.
Ultimate goal is to install CM11 or Slimkat.
Hi, Guys,
I was intending to Root my One Plus 2, and I already unlocked the boot loader.
But I tried to install a recovery file (TWRP) but I couldn't, but the worst is that I deleted the all fill system
Now, thw only thing that I have is:
I turn it on and it stays on the initial boot system image (1+), but doesn't go on.~
I can activate the fastboot mode pressing the "power and +", but when I press "power and - ", nothing happens.
How can I fix this ?
Thanks
Hello,
Gratz you are a proud owner of a bricked OP2...
Just do a full recovery via this guid.
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus
Regards,
Seim
amaf1959 said:
Hi, Guys,
I was intending to Root my One Plus 2, and I already unlocked the boot loader.
But I tried to install a recovery file (TWRP) but I couldn't, but the worst is that I deleted the all fill system
Now, thw only thing that I have is:
I turn it on and it stays on the initial boot system image (1+), but doesn't go on.~
I can activate the fastboot mode pressing the "power and +", but when I press "power and - ", nothing happens.
How can I fix this ?
Thanks
Click to expand...
Click to collapse
You have fastboot then you're not bricked.
Go and install fastboot images and skip data partition.
Sent from my ONE A2005 using Tapatalk