So last night I rooted my phone using the All in one toolkit. Flashed hyperdrive rom and after getting everything setup I went to bed.
Some apps were kind of freezing this morning so I tried to boot into recovery and it wouldn't let me. It shows the loading recovery at the top then it just boots my phone up. The only way I can get into Recovery atm is by using the all in one toolkit. Anyone had this issue before? I wipe cache, dalvik, and fixed permissions. Still can't boot into recovery without the toolkit.
if you can get into recovery by typing adb reboot recovery in cmd then maybe your finger may be slipping when holing the buttons to boot into recovery.
bmbrad said:
So last night I rooted my phone using the All in one toolkit. Flashed hyperdrive rom and after getting everything setup I went to bed.
Some apps were kind of freezing this morning so I tried to boot into recovery and it wouldn't let me. It shows the loading recovery at the top then it just boots my phone up. The only way I can get into Recovery atm is by using the all in one toolkit. Anyone had this issue before? I wipe cache, dalvik, and fixed permissions. Still can't boot into recovery without the toolkit.
Click to expand...
Click to collapse
Hold power + volume up, right when you feel it vibrate, let go of the power.
Yeah I tried all that. I ended up having to wipe everything and flash my first back up when i rooted my phone.... Thanks for the help thought.
I have the same issue. Stock, rooted, TWRP... I can use adb reboot recovery, but using the hardware buttons doesn't work. Any help is appreciated!
Related
ok im stuck on my boot logo for my motorola droid 2. its a liberty logo, no the original M logo, ive held in x when it starts up and then it takes me to the triangle and then i hold the search button down and then it takes me to a menu saying this:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
ive already tried just rebooting it and then it does the same thing again and just gets stuck at the boot logo, so please help. thanks!
Have you tried pulling the battery out for about 15 seconds?
See if that clears it up.
with it unplugged and turned off?
Yes Sir. Unlug it and turn it off.
yes i just did that and it didnt work, its still at the boot logo, the only thing i can do is go to that recovery menu that i said about in my 1st post, but idk what to do when i get there?
Try wipe data/factory reset.
Obviously you're gonna have to tweak your settings again.
okay, is there anyway i can get my settings back like a recovery? or something
Well, you might want to head in to the Droid 2 forums to get better responses related to your phone.
Here is a link to start with.
As far as recovery goes, I don't think you have a custom recovery installed. Sounds like you have a stock phone. So, there's no way of backing your stuff up.
i have it rooted and a rom on it but nothing custom, but thanks for all your help
Zimm814 said:
i have it rooted and a rom on it but nothing custom, but thanks for all your help
Click to expand...
Click to collapse
If you have it rooted, did you ever perform a Nandroid backup ?
Do you have a non standard recovery installed?
EDIT: Sorry re-read last few post and come to conclusion that you probably don't.
sorry but doesnt rds lite 4.8 and the correct sbf file let u flash back to stock?
If your phone is rooted then you have changed your kernal.It might be a fault with the kernal.I had a similar thing happen in an SGS.It was rooted and when i flashed the kernal againh via CWM it also got stuck on the same as you.The only way to solve it was boot to download mode and flash via odin again.
So I rooted with HTC method with hboot 1.5.
I have lots of roms on it to check the speed, battery life, features of them but there has been a problem with many ROMs (MIUI, ICS alpha, Mik, Infected, Warm) all will act "wonky" after couple of days of using the rom. They will show red lines, slow downs, temporary freezes, battery would drop by 1% every 30 sec.
So, the usual thing to do is restart and BAM! They rom's logo shows up and it freezes there. Do I need a new radio update or RUU or something?
Never encountered anything close and I've been tweaking phones since the Moto Q days!
New radios might help. Are you wiping EVERYTHING before flashing?
We're comin from a pure power source.
How can I flash this new radio? Just install .zip of the file from recovery, correct?
I do "factory reset" on the twrp 2.0 recovery before I install any rom
ninten5 said:
I do "factory reset" on the twrp 2.0 recovery before I install any rom
Click to expand...
Click to collapse
I'm using twrp2 and I do
Factory reset
Wipe cache
Wipe dalvic cache
Wipe system
Factory reset (again)
Flash Rom
Reboot system.
And i never have any bootloops or stuck in HTC white screen or any issues.
Sent From My Optimized R3Dimensions
Yea. Factory reset isn't enough. I encountered that issue when doin restores on me og evo. I had to wipe cache and dalvik to get it to work.
We're comin from a pure power source.
Use cwm older 4 version as recovery.
Fastboot boot recovery.img. make sure you have a copy of it in your adb folder.
Wipe everything and flash rom
OK ill try that.
What about backup and restores, my nAndroid backups don't work
ninten5 said:
So I rooted with HTC method with hboot 1.5.
I have lots of roms on it to check the speed, battery life, features of them but there has been a problem with many ROMs (MIUI, ICS alpha, Mik, Infected, Warm) all will act "wonky" after couple of days of using the rom. They will show red lines, slow downs, temporary freezes, battery would drop by 1% every 30 sec.
So, the usual thing to do is restart and BAM! They rom's logo shows up and it freezes there. Do I need a new radio update or RUU or something?
Never encountered anything close and I've been tweaking phones since the Moto Q days!
Click to expand...
Click to collapse
Either one of two things:
your phone is defective
stop using so many apps for stuff like checking on system statuses. Just install a ROM fresh and leave it for a week with just your base essential apps like email and stuff. If the problem doesnt arise you know all your crap is causing it.
A radio update isnt going to do anything for a system issue as it is just your signal and stuff that the radio firmware would affect.
Sounds like the flash went bad due to not a full wipe or boot.img.
Twrp 2.0 is known to have its own issues.
Update: So I have infected rom installed for a couple of days, installed it using the method mentioned with wiping cache, dalvik cache, system, battery stats and guess WHAT?
It happend again, I would lose touch screen and touch button control, only way to regain control was to close screen by hitting power and waiting a few seconds and pressing it again to open the screen. Got fed up after a while and decided a battery pull, froze of Infected LOGO
Is it the way I flash the rom that is causing issues? I install the zip first with cwm 2.0 then I connect to computer and type "fastboot boot boot.img" to push the boot.img for that rom.
ninten5 said:
Update: So I have infected rom installed for a couple of days, installed it using the method mentioned with wiping cache, dalvik cache, system, battery stats and guess WHAT?
It happend again, I would lose touch screen and touch button control, only way to regain control was to close screen by hitting power and waiting a few seconds and pressing it again to open the screen. Got fed up after a while and decided a battery pull, froze of Infected LOGO
Is it the way I flash the rom that is causing issues? I install the zip first with cwm 2.0 then I connect to computer and type "fastboot boot boot.img" to push the boot.img for that rom.
Click to expand...
Click to collapse
Do this man
Get cwm 4.0 version ok now flash that then leave a copy of it in your adb folder where adb is...
Now make sure debug is on
adb reboot bootloader
fastboot boot recovery.img
Then wipe everything but not your SD card
and flash rom works this way just like the S off users use. You don't have to use flash gui or pull boot img..
So I took out twrp 2.0 recovery and put clockworkmod 5.0
I don't know why but I cant boot into the recovery without connecting my phone and pushing the .img through fastboot
Well at least two things are solved, after a restart the rom doesnt freeze and I dont have to fastboot boot.img for installing a new rom.
ninten5 said:
So I took out twrp 2.0 recovery and put clockworkmod 5.0
I don't know why but I cant boot into the recovery without connecting my phone and pushing the .img through fastboot
Well at least two things are solved, after a restart the rom doesnt freeze and I dont have to fastboot boot.img for installing a new rom.
Click to expand...
Click to collapse
cwm 4 is better for this phone dude. he said 4 not 5.
i recently rooted my phone and flashed clockwork and was running beastmode kernal on stock rom.everything was working ok i used to get little glitches here and there so i tried to restore my phone back to factory.i entered the recovery mode and wipe date/factory reset and then went on to restore the backup.everything went smooth until i reboot the phone and now the phone is stuck in the droid(eye logo) and wont past that at all and just glitches and freezes on that screen.my friend has tried to fix it but there is no communication between the phone and the computer(usb debugging must have been disabled when i wipe data/factory reset and i basically cant do anything to fix it.is there a way around this to where i can just reset the phone to factory or install a rom or something
nathan101 said:
i recently rooted my phone and flashed clockwork and was running beastmode kernal on stock rom.everything was working ok i used to get little glitches here and there so i tried to restore my phone back to factory.i entered the recovery mode and wipe date/factory reset and then went on to restore the backup.everything went smooth until i reboot the phone and now the phone is stuck in the droid(eye logo) and wont past that at all and just glitches and freezes on that screen.my friend has tried to fix it but there is no communication between the phone and the computer(usb debugging must have been disabled when i wipe data/factory reset and i basically cant do anything to fix it.is there a way around this to where i can just reset the phone to factory or install a rom or something
Click to expand...
Click to collapse
Your phone is not bricked. When the phone is stuck on the droid eye, hold the power button and the volume down key at the same time until it reboots. This will get you into bootloader mode. Press the volume down key to highlight recovery and press the power button to enter it. Once you're in recovery go ahead and restore a backup or reflash something new. Either way make sure to do a full wipe.
Sent from my HTC6435LVW using xda app-developers app
klarson said:
Your phone is not bricked. When the phone is stuck on the droid eye, hold the power button and the volume down key at the same time until it reboots. This will get you into bootloader mode. Press the volume down key to highlight recovery and press the power button to enter it. Once you're in recovery go ahead and restore a backup or reflash something new. Either way make sure to do a full wipe.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
thats what i did i restored my backup and this is what happens. and i cannot push any files over to the phone because usb debugging is not enabled so there is no communication between the phone and computer at all
boot into recovery then use "adb push <path to rom> /mnt/sdcard/" to put a rom on the sd then install. Make sure you use a boot.img that came with the rom if it has one as it may cause problems if you don't.
Edit: you will need another rom for this and I would recommend reflashing a boot.img
Jmlannan said:
boot into recovery then use "adb push <path to rom> /mnt/sdcard/" to put a rom on the sd then install. Make sure you use a boot.img that came with the rom if it has one as it may cause problems if you don't.
Edit: you will need another rom for this and I would recommend reflashing a boot.img
Click to expand...
Click to collapse
the problem im having is the phone is not being recongnized by the adb so there for i can not push anything to the phone.i have no communication with the phone at all so i cant push any files at all.im looking for a way around this
nathan101 said:
i recently rooted my phone and flashed clockwork and was running beastmode kernal on stock rom.everything was working ok i used to get little glitches here and there so i tried to restore my phone back to factory.i entered the recovery mode and wipe date/factory reset and then went on to restore the backup.everything went smooth until i reboot the phone and now the phone is stuck in the droid(eye logo) and wont past that at all and just glitches and freezes on that screen.my friend has tried to fix it but there is no communication between the phone and the computer(usb debugging must have been disabled when i wipe data/factory reset and i basically cant do anything to fix it.is there a way around this to where i can just reset the phone to factory or install a rom or something
Click to expand...
Click to collapse
USB debugging has nothing to do with ADB in recovery, recovery basically has its own kernel and ADB is always enabled. Are you saying ADB doesn't work in recovery? If so, it is probably a driver problem with your computer. Also, some phones randomly get corrupt /data/ partitions (mine used to get them until I started using DSB's stock kernel with system write) and the only way to fix it is to do a factory reset or restore a backup. This might be what happened to you. If so just do a factory restore and see if it will boot.
Perhaps reflashing recovery? Worth a try if ur still having problems, also try installing then uninstalling htcs sync app.
nathan101 said:
i recently rooted my phone and flashed clockwork and was running beastmode kernal on stock rom.everything was working ok i used to get little glitches here and there so i tried to restore my phone back to factory.i entered the recovery mode and wipe date/factory reset and then went on to restore the backup.everything went smooth until i reboot the phone and now the phone is stuck in the droid(eye logo) and wont past that at all and just glitches and freezes on that screen.my friend has tried to fix it but there is no communication between the phone and the computer(usb debugging must have been disabled when i wipe data/factory reset and i basically cant do anything to fix it.is there a way around this to where i can just reset the phone to factory or install a rom or something
Click to expand...
Click to collapse
Try restoring back to stock with the Droid DNA RUU, i had issues with it locking up and freezing and i couldnt do a thing with it. i stumbled on the RUU and followed the instructions and re-stocked it. then just root and flash again. worked for me and im now running the Battery Plus ROM and have no issues yet. good luck
Just be sure to re lock before you flash the ruu
Sent from my HTC6435LVW using xda premium
I tried to install a new theme on jasmine rom. I rebooted and phone said updating app, and remained on update app for over 5 minutes.So I rebooted and the phone remained in the jasmine boot screen. I knew I had a problem so i rebooted into recovery, did a complete wipe and installed my backup and rebooted. The phone started to reboot (Lg splash screen) and then stopped. The screen went dark and my red and blue LED lights started blinking. I tried to get back into recovery manually. I was able to get to stock recovery, hit factory reset and instead of going to TWRP, it went back to the black screen and the blinking LED lights. Same results occurred when I hit safe boot.
I also tried to get in DL mode with the volume up button. Instead, the LG splashscreen came on for less than a second, the screen went black and the blinking lights came again. I tried ADB but it won't recognize my phone. Any suggestions, or is this a goner? Thanks for your help.
So to install jasmine you had to have twrp installed. Then you said you booted into recovery and the stock recovery came up and you said yes to factory reset. that scenario of booting into stock recovery and saying yes was only the first time after installing twrp. everytime after that if I choose to boot to recovery twrp screen comes up first. Confused cause I'm nut sure if this is normal behavior with some phones that have been bumped.
rp201 said:
So to install jasmine you had to have twrp installed. Then you said you booted into recovery and the stock recovery came up and you said yes to factory reset. that scenario of booting into stock recovery and saying yes was only the first time after installing twrp. everytime after that if I choose to boot to recovery twrp screen comes up first. Confused cause I'm nut sure if this is normal behavior with some phones that have been bumped.
Click to expand...
Click to collapse
If you boot into recovery from the advanced reboot menu, it goes directly to TWRP. However, when you use the hard key combination, it goes to the stock recovery and when you select factory reset, it is supposed to go to TWRP. It doesn't. I have a new phone on the way.
I accidentally took the update from Verizon and when I went to install it I got the same thing. I would get the lg/android bout screen and then it would go to twrp. I tried to reboot, wipe everything and restore back up and nothing changed.
Then I found this post
http://forums.androidcentral.com/ge...cked-lg-g2-stuck-twrp-no-download-mode-3.html .
This saved me. When in twrp you go to the advanced tab click terminal command, then select. Just follow this directions and you might be golden.
This just worked for me and I didn't have to flash back to stock. I know this says it is for the g2, but it worked. Good luck.
Sent from my Nexus 7 using XDA Free mobile app
Bxrider117 said:
I accidentally took the update from Verizon and when I went to install it I got the same thing. I would get the lg/android bout screen and then it would go to twrp. I tried to reboot, wipe everything and restore back up and nothing changed.
Then I found this post
http://forums.androidcentral.com/ge...cked-lg-g2-stuck-twrp-no-download-mode-3.html .
This saved me. When in twrp you go to the advanced tab click terminal command, then select. Just follow this directions and you might be golden.
This just worked for me and I didn't have to flash back to stock. I know this says it is for the g2, but it worked. Good luck.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
I did the exact same thing early today and stumbled on that same thread. So relieved
jlokos said:
If you boot into recovery from the advanced reboot menu, it goes directly to TWRP. However, when you use the hard key combination, it goes to the stock recovery and when you select factory reset, it is supposed to go to TWRP. It doesn't. I have a new phone on the way.
Click to expand...
Click to collapse
So any idea what exactly went wrong here? How did a basic "theme" apparently completely bork your recovery and brick your phone??
ohlin5 said:
So any idea what exactly went wrong here? How did a basic "theme" apparently completely bork your recovery and brick your phone??
Click to expand...
Click to collapse
I have no clue what happened; Verizon sent me a new phone. I don't have a clue whether this was related to the theme, or not. It may have been an unrelated hardware issue.
My phone recently have gone into a boot loop, so I booted it into recovery and wiped it in order to reflash. But then, when I updated the TWRP recovery to the latest version, the phone stopped bootin into it. Now only the fastboot mode works, and when I try to boot into recovery, it just reboots. I am trying the twrp-3.1.1-0-kenzo on my Xiaomi Redmi Note 3 Pro. How do I make it work?
When u flashed new recovery did you try booting it using key combo before booting to system
marcukial said:
When u flashed new recovery did you try booting it using key combo before booting to system
Click to expand...
Click to collapse
Of course. That's when it just flashes the red light indicator and reboots. In fact, there is no "system" to boot into, as I wiped it clean before reflashing the recovery.
Dayita said:
My phone recently have gone into a boot loop, so I booted it into recovery and wiped it in order to reflash. But then, when I updated the TWRP recovery to the latest version, the phone stopped bootin into it. Now only the fastboot mode works, and when I try to boot into recovery, it just reboots. I am trying the twrp-3.1.1-0-kenzo on my Xiaomi Redmi Note 3 Pro. How do I make it work?
Click to expand...
Click to collapse
Why did you flash a newer version of TWRP, instead of a rom? Reflash the working twrp which was working before you wiped in order to reflash.
Sent from my Redmeme Note 3 with VoLTE disabled.
Reflash the working twrp which was working before you wiped in order to reflash.
Click to expand...
Click to collapse
I don't remember which version it was. I think, it was something 2.x.x, and I can't find anything earlier than 3.0.2 anywhere. 3.0.2-0-kenzo also does not work for me.
bro,Install twrp by this method.
https://forum.xda-developers.com/redmi-note-3/how-to/unlock-unofficially-install-zcx-twrp-t3586778
I just switched my phone on, and it booted into TWRP recovery that I installed eralier! But all the storage partitions were showing zero size, so I reformatted them and selected "reboot into recovery" option. But it did not boot into recovery, and now it is stuck on the "MI" logo and the "Volume Up + Power" key combo only makes it reboot, just like before. How do I boot into recovery?
I figured it out. The whole deal was about dead battery which caused the device to fail to boot even the recovery, even when charging. It charged up a bit, and I sucsessfully flashed the phone.