Hi, I tried installing CW recovery but I can't get in recovery mode. What I did so far:
Rooted the phone, replaced recovery.img with the one I found here (v. 4.0.0.5) then tried to access recovery mode by holding down vol+ while starting the phone, but it just continued to boot android. Then I tried v. 5.0.2.7 which I found here. Same problem. Am I doing something wrong? What else could I try?
I replaced the boot.img I used to root the phone with the original. The phone is still rooted and I managed to access the bootmenu.
Related
Hi guys,
I already rooted my hero. but when i tryin to access the recovery page it just shows me a red triangle sign.. Before i root my phone its 2.1 already. Does anyone knows how can i cont to acess the recovery page and flash a new rom?
I have the same issue with my old Hero. I have super user access but i can't open in recovery mode. If I find an answer, i"ll let you know.
Why don't you guys just try this? From my understanding it will just push SuperUser.apk and install AmonRA's 1.6.2 recovery.
Why don't you guys just try this? From my understanding it will just push and install AmonRA's 1.6.2 recovery.
Are you trying to boot into recovery by holding the home button? I had the same problem too and ended up using ROM manager which made life a lot easier.
If you managed to flash the recovery ROM then just hit "Reboot into Recovery" and then you should be able to flash a custom ROM. I had problems booting into recovery by holding the home button when powering on the phone but the "Reboot into Recovery" option in ROM manager always worked fine for me.
Hi there, Ive just been trying to get root on the phone. I flashed CWM 3.0.2.4 onto my NS (2.3.4) and now it only boots into CWM, wont boot into android. How do I get it to boot to android! No idea what to do, Ive googled the **** out of this and just get loads of conflicting stuff, none of which works!
Thanks for the help!
What is the command you used to flash CWM onto your phone?
hi i have the same problem. i have i9023 and i made:
oem unlock command and the flash recovery command.
everything was ok.
then i used superroot-user-install.bat or something like that (which was mistake on 9023 i think)
after this i can start phone with volume up+power and can go into recovery.
but if i want to reboot into system i had just google logo and litlle logo of lock down on the screen and thats all.
Stupid question: did you try yanking the battery?
I have the same problem! I'm stuck in the ClockworkMod Recovery. Rebooted the phone multiple times, no change :S
EDIT: Panic is over, fixed it
I got that problem too when i tried to root my NS, then I downloaded the stock image > extract to get the original bootimage > flash it > reboot CWM recovery > problem solved.
Hi there,
I wanted to install latest CM10.1 coming from 0526 yesterday on my Defy+.
Did a backup with TWRP first.
Then the flashing failed, so I wanted to recover from backup.
Phone now is stuck at Motorola M not booting anymore.
When I enter bootloader (vol down) and want to enter "custom recover" he just jumps back to the same menu. TWRP is not starting.
Choosing "stock recovery" is possible, but if I choose a CM10.1 zip file it's not accepted.
RSD Lite does not recognize the phone when it's in the bootloader menu or in the stock recover menu.
Help is very much appreciated, what can I do?
Thanks and best regards.
are edianKa
[Idiot mode=on]
Okay, I found out why I couldn't enter flash mode by using Vol+ when starting.
The phone powered already up when I put in the battery, so I always pushed Vol+ too late.
Pressing Vol+ WHILE inserting the battery did the trick, phone went into flash mode and I could re-flash 2.3.6 sbf using RSD lite.
[Idiot mode=off]
Still not sure why TWRP was messed up just by recovering from a TWRP-made backup...
Best regards
Same situation to me.
I opened Terminal Emulator, gained root access
then type below command to get recovery mode
# reboot recovery
Custom recovery not running
I have a similar issue.
I rooted my stock S4 and installed the proper TWRP.
Heres where my situation is a bit different from anything I have seen on the forum threads. All attempts—both hard and soft—to reboot into recovery, all direct the reboot to Odin Mode. Just to clarify I have not flashed any rom custom or stock, the only thing I have flashed has been TWRP and CWM recovery. And I only flashed CWM AFTER the Failings of TWRP.
When I attempt to boot into recovery, it flashes the blue characters then sends me into a Odin Mode loop until I hard-key the "download mode" and select restart to boot the os normally.
my phone works fine other than not being able to flash custom roms, which is a pain in the arse especially with all the s4 Bloatware.
Here's what I have done so far to help myself:
• install CWM recovery
• tried hard-key reboot recovery (power off/ press home/volume up/power)
• soft reboot recovery through both Goo, CWM and ROM Toolbox pro
• removed my sd card and tried reboot recovery
• removed battery and reboot recovery
• emulator reboot recovery
• reboot recovery both with and without usb cable
I looked into flashing stock with Odin but all tutorials i could find were of an older version and I didnt want to guess what I needed to get that to work,
Please let me know if theres anything I can do.
(Verizon) Samsung Galaxy S4 jfltevzw
I have a d802 . I had cloudy1.3 and twrp 2.7 installed with autorec. I tried to update it using
dd if=/sdcard/recoveryfilename.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
(from twrp page, with the latest img file).
But I coudn't access recovery, some error about security. Then I shutdown my phone and then it booted fine into system. I retried to access recovery but nothing.
So I decided to return to autorec, I installed it, I clicked "Flash Recovery" and now my phone doesn't boot in any way.
It show "lg security error" and then shutdown.
I can access download mode. Is there a way to fix my phone without deleting everything?
I'm sure the problem is the recovery, I was messing with it, can I bring my phone back and don't delete my configuration, photos, apps?
Thanks
I'm so happy!
I did it!!!
I managed to boot into recovery with the usual combination of keys (with the method that ask you if you want to format, but then you press power and it boot into recovery).
From there I saved everything using adb pull (Just in case). Then I dirty flashed Cloudy 1.3 and my phone is back !
I hope my experience can help someone
So I updated Magisk and my phone got stuck in bootloop. I could not get into TWRP recovery by any method. Yesterday I accidentally got into the recovery by draining the battery and pressing random combinations of buttons while connecting/disconnecting the phone with the charger. I got into recovery and flashed a custom rom on my phone. Everything worked fine until I rebooted into the recovery where I got stuck into bootloop again. Somehow I got into recovery again by the same above method and now I am wondering if the recovery is corrupted or is there something else wrong with the phone. Do I need to flash the recovery again? Is the firmware corrupted and I need to flash the firmware again? Any idea what could be the issue?