Last night i was restoring goapk backup - 2012-06-01.13.43.03 . System restore was succefull. Then i installed system recovery - defy_recovery_1218_0326_signed.apk (it worked). Now i cant enter in goapk recovery. Then i enter in System recovery and chosing ,,Recovery boot,, phone boots with black screen. Tried reinstal System recovery - same result. Could somebody help me?
Problem fixed.to fix it - disable USB Debugging.
Related
Last night i was restoring goapk backup - 2012-06-01.13.43.03 . System restore was succefull. Then i installed system recovery - defy_recovery_1218_0326_signed.apk (it worked). Now i cant enter in goapk recovery. Then i enter in System recovery and chosing ,,Recovery boot,, phone boots with black screen. Tried reinstal System recovery - same result. Stock defy recovery works. Could somebody help me?
PROBLEM FIXED: just disable "USB Debugging"
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
Today I decided to root my OP2. I did all the regular procedure for rooting. Fastboot > OEM unlock > Flash TWRP 3.1 > flash SU.zip via TWRP. Now this is where the problem started, after flashing SU.zip I rebooted but it was not rebooting, the 2 white dots kept rotating for quite a long time. so I turned off the phone and flashed the SU.zip again and rebooted but still didn't worked, so I went back to TWRP booted into fast boot and flash a lower version of TWRP, Now TWRP won't even start the screen got stuck on one plus logo. so I powered off again and tried doing a normal start up but that didn't workout, so I tried to start fast boot manually (power button + volume up) but this time the screen didn't even turn on . Is there anything I could do to fix it.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
use method 2 or method 3 if you have efs backup by terminal or efs backup by spanna software zip. (P.s. dont rely on efs backup by twrp)
and if don't have efs backup then after method 2 or 3 flash oos 3.5.7 to get ur imei numbers.
Please help me, i flash my phone with twrp and suddenly flash recovery in boot, and my phone can't boot into recover, instead of recovery boot into fastboot. And i accidently change the setting in developer option to reboot when power on, now my phone can't be used, please help me solve my problem