I ran XZRecovery, then chose install recovery, then it rebooted, got green led and two vibrations, and the phone is stuck there:
.... boot logo, steady green led, two vibrations several times, then blinking green led, two vibrations, and repeat..
Vol-Up will get to Philz and Vol-Down will go to TWRP, but from either recovery, the Rebooting System option will just get the phone back to the green led & two vibrations. How do I get the phone to boot into system??
It's a D6616, rooted and running fine until I got stuck in recovery boot. Any help would be much appreciated!
Solved.
I downloaded XZDualRecovery zip to the SD card, and flashed it from TWRP (could be done from Philz too). Choose System Reboot and now system boots up just fine!
Nandroid backup will be first order of business. Phew.
Note: the zip file is from XZDualRecovery (thanks @[NUT]) and the APK that I ran to get something twisted was XZRecovery. Some init file must have been stuck pointing at recovery.
Related
Hi all,
I've searched the Q&A section on this and Google, it seems we can't physically boot into the recovery like we normally would with power + volume up/down combination?
I can boot into recovery via Quick Boot -> Recovery, but I want to boot into it without booting into the OS. Imagine if your system partition got wiped or corrupted somehow and you can't boot into it. The only thing we have is fastboot which works and PROBABLY adb might work, but it will be nice to boot into recovery via a button combination.
Just checking if this is truly the case and nothing we can do about it?
During initial boot, when you see the SONY logo, hold down the Volume Down key. After 2-3 seconds, the Led indicator should blink green twice, and once purple, and after that your recovery should load up.
Have you installed a recovery? You cannot enter the stock recovery partition on Sony devices, you need to root, install a recovery (In the system partition) then boot into that.
XDA,
I am trying to root the stock rom (Cyanogen OS 12.10YOG4PAS1N0). I have thus far managed to unlock the bootloader and am now trying to install a custom recovery - here I run into some problems:
So I downloaded the latest TWRP and renamed it recovery.img - pressed 'fastboot erase recovery' and then 'fastboot flash recovery recovery.img' -all going fine.
I then unhook the phone, turn it off - press volume down and the power button to boot straight into recovery (not even booting OS) and here's where it gets interesting:
The 1+ logo appears, as if its trying to boot recovery - it hangs for 10s, then the screen goes black and it vibrates. The 1+ logo appears again and it boots straight into OS.
If I keep pressing volume down I am in a loop like this, with 1+ logo, screen black and so on.
So I never actually get into the custom recovery. And if I boot into the OS and press restart into recovery: I get stock recovery.
I've tried CWM. TWRP, Philz, the toolkit, manually - lots of things. I turned off overwrite custom recovery in the developer options - all to no avail.
I hope someone recognizes this problem and can help me out.
Thanks a million,
Michiel.
Not sure if this is your issue, but go to this thread on how to unlock bootloader, install custom recovery and root. See the note in underline at the bottom of item #2, installing the custom recovery. I was unable to get TWRP to stick until I followed this simple method.
Yes, I tried this but when I power the phone down and boot it with the powerbutton and volume button - it hangs on the OPO logo and reboots again into the OS.
Okay so I'm not new to rooting, flashing custom roms, or using custom recoveries, but this one has stumped me.
After reading and researching several poorly written/translated guides I set out to flash the Miui6_5.3.20_r827_b3wok custom rom on my Oppo Find 5 Mini. I copied the CWM for the R827 into the sd card, using Mobile Uncle MTK tools to install it. I successfully rebooted into CWM, selected the factory reset option (wiping data and cache) and then format /system and wiped the dalvik cache. I then installed the zip of the custom rom, with no errors. However, the custom rom needed a patch, specifically the "VPN-Fix by Louise - AICP v10 - R827" which acc. to the instructions were supposed to be patches BEFORE gapps.
Now the problem is that at the end of flashing that patch, it automatically reboots the phone, so I held the power button while the Oppo logo was there and booted into CWM again. I then flashed gapps, and rebooted the device.
However, I am no longer able to get into CWM, nor does the Oppo logo move/progress. Pressing Volume Down + Power to get into recovery mode turns on the phone with the text =>Recovery Mode in the bottom left, but instead of going into CWM it now just turns off the screen, vibrates, and proceeds to boot as if I never attempted to go into recovery mode in the first place.
Is this phone well and truly bricked? Fastboot mode (Volume Up + Power) just vibrates the phone and turns it off, so theres no way I can do a adb reboot or sideload. I can however copy files to and fro the microSD card via a separate card reader, if it helps.
Thanks for helping , and sorry for the long read...This really is my last hope. :crying:
Update: Okay so I went to the Oppo store and after about 40 minutes they somehow both fixed it and updated to the ColorOS with Kitkat.
OP resolved.
Thread closed.
I unlocked the bootloader on my phone, then flashed twrp. I rebooted to twrp and installed boot.img, TWRPWorkingInstaller.zip, TWRP-BLUE-FIX.zip, and Root.zip. Rebooting worked fine, but I saw that there was a newer twrp (twrp-3.2.1-3-wOOSkernel.img, so I tried installing it from twrp. The problem is that I installed it to the system image partition. After that, everything got wonky, unsurprisingly. Now, if I try to boot to twrp, it loads and I get to the first menu, but I cannot interact with it at all. Then the screen goes black and the led lights up blue. It doesn't respond to anything except shutting it down. I can hold the power button down to power off, but it reboots instead to a black screen with the blue LED. I can also boot into the bootloader. I can reflash twrp. When I restart to recovery then, I get the screen asking if I want to keep the system files locked or swipe to unlock it. The device seems to work fine for about 5 seconds from the time I get to the first twrp menu, then it doesn't respond. About 5-8 seconds later, the screen goes black and the blue led comes on. I also cannot power-off the device. If I try, it reboots.
Is there anything I can do to recover from this? I've got the stock recovery files (OnePlus6Oxygen_22_OTA_009_all_1805172226_f7d1518e0e704ca3.zip), but I can't copy them to the device because it won't boot to the OS.
Yippee38 said:
I unlocked the bootloader on my phone, then flashed twrp. I rebooted to twrp and installed boot.img, TWRPWorkingInstaller.zip, TWRP-BLUE-FIX.zip, and Root.zip. Rebooting worked fine, but I saw that there was a newer twrp (twrp-3.2.1-3-wOOSkernel.img, so I tried installing it from twrp. The problem is that I installed it to the system image partition. After that, everything got wonky, unsurprisingly. Now, if I try to boot to twrp, it loads and I get to the first menu, but I cannot interact with it at all. Then the screen goes black and the led lights up blue. It doesn't respond to anything except shutting it down. I can hold the power button down to power off, but it reboots instead to a black screen with the blue LED. I can also boot into the bootloader. I can reflash twrp. When I restart to recovery then, I get the screen asking if I want to keep the system files locked or swipe to unlock it. The device seems to work fine for about 5 seconds from the time I get to the first twrp menu, then it doesn't respond. About 5-8 seconds later, the screen goes black and the blue led comes on. I also cannot power-off the device. If I try, it reboots.
Is there anything I can do to recover from this? I've got the stock recovery files (OnePlus6Oxygen_22_OTA_009_all_1805172226_f7d1518e0e704ca3.zip), but I can't copy them to the device because it won't boot to the OS.
Click to expand...
Click to collapse
Do you have a TWRP backup from when your phone worked on an external drive?
Can you access fastboot? Just use the fastboot ROM files to reflash the OS. Or if that doesn't work try the unbrick tool.
Yeah. I can use fastboot. However, I wasn't able to get to ROM to flash. I'm not sure if I'm using the correct parameters in the command. I googled, but all I came up with was flashing custom ROMs. Where can I find the unbrick tool?
NM. Found the unbrick tool. I may try it. I'll let you know how it works.
Thanks for your help @NateDev!. The Unbrick Tool helped me fix it.
Yippee38 said:
Thanks for your help @NateDev!. The Unbrick Tool helped me fix it.
Click to expand...
Click to collapse
Glad you got it solved
So, I just decided to try and Flash the old TF101 with Katkiss 6.0.1 and Gapps, but I always get stuck on the same problem.
My TF101 is running Android 4.0.3 ICS and USB Debugging is on
I downloaded TWRP app on the transformer, as well as the latest .blob flash file through the app.
Before this, I rooted the tablet using Kingroot.apk, which worked. When I went to flash the tablet with the recovery, the app noted "Recovery Partition not found".
I tried to boot into recovery mode on my own, (Pressing Pwr + Volume down , Then hitting Volume Up), The android screen popped, up and then flashed to a fallen android with a red triangle.... The screen stays on this for a minute and then boots into the normal system. I can't even boot into recovery through ADB, using the
Code:
adb reboot recovery
, The tablet will just reboot normally, not into recovery mode.
The Device does recognize through ADB....
Is my recovery partition just non existent? Even when I just let the system though without pressing volume up, it only gives me the option of (Android) or (Erase Data). when I click erase data, ill stay on the asus loading screen indefinitely and nothing will happen until i turn it off and on.
I just cant seem to boot into TWRP for some reason, and that means I just cant install the downloaded custom ROM.
How Can I fix this and boot into TWRP? I've tried for hours and have been hung up due to the same problem each time, even after rooting.
Did you already solve that problem? I also need a solution.Thanks