After installing openscript recovery TWRP 2.2.1 via goo manager and then realize the recovery could not mount system or install any zip. I then try to revert back to team rogue xm recovery 1.5.0 with sucess by installing the recovery zip in TWRP (although some error due to system unable to mount). Got pretty happy that I'm able to revert back to rogue recovery but now faces this STUCK in automatic rebooting to recovery everytime I've try to reboot. I wipes everything completed 3x and install new rom but can't ever boot pass the recovery. I have yet to revert back to stock via softbrick method and figure I should ask for help first before unroot and unlock to start from scratch. below is an image of when ever I booted my xoom. Thanks for any help.
Oh, I've search first but noon seem to have the same problem as mine.
Related
Hope some of these amazing minds at xda can help.
When i install a custom recovery image from rom manager or my computer, it works fine. In the recovery, i can successfully restart the recovery in the advanced menu. But when i reboot after installing, it dissapears.
It also does this even if i havent entered the custom recovery after i install/flash the recovery image and do a reboot. There is something going on at bootup, but im not sure what it is. My guess is the android system denies the recovery image because it does not think it has the privelages- though im probably wrong.
I have tried to do a nandroid restore and a factory reset, but it still wount work. i have tried re root twice and still nothing. But a thing i noticed when doing a nandroid restore is that it fails to find a file and skips it.
Please help, and if you cant.... try. I AM DESPERATO!
So I've been play with Android for a few years now and I love it. Got the Samsung Galaxy Note 10.1 in the fall of 2012 and had a custom rom installed not long after. Periodically I check XDA to see if there is a new custom ROM I want to try. Finally there is, OMNIRom. It says I need a recovery image that can handle the new SELinux. After poking around for an easy way to update I findout that the goo.im has a new recovery that it will install. And that's where things go south. I installed the new TWRP v2.6.3.0 via the goo.im and then reboot into the recovery. I go to flash the new ROM and it fails. I try downloading the ROM again and flashing it. It fails again. Okay, shouldn't be a problem... I'll just flash my prior rom. It too fails. Uh-oh.... If I try to boot normally, it just loads directly to the faulty TWRP. If I try to boot to the bootloader so I can use Heimdall to flash over a new recovery, it boots to TWRP....
I found a new recovery in a ZIP format finally and tried to use that, but it fails too.
Any advice? Suggestions? Please help.
Can anyone tell me how I flash a recovery to the device from a zip file? Going into CWM and flashing the TWRP recovery initially seems to work, but if I then interrupt the reboot and go straight into recovery, I still see CWM, not TWRP. I'm stuck on the CWM recovery and need TWRP to try to install the Kitkat upgrade.
Should I unzip the components first and then flash the image using fastboot, or is there another way? I'm wary of fastboot as I've already (temporarily) "bricked" the Xoom by flashing a zip instead of an image that way. None of the instructions I've read has much advice on getting round installation problems.
I'm guessing the persistent CWM was caused by my selecting (at an earlier stage) the CWM option to fix the problem of the stock recovery being reinstated at each reboot. Can this be undone? Although I've installed Xoom-Universal-Root, apps that require root access - including GooManager - also fail with an access error. It's hard to tell whether the device is now rooted or not, so if there's any method of getting further without root access, that would be great.
====================
Edit: it looks as if the instructions I saw online, which mentioned two separate TWRP recoveries, were incorrect. To get Android Kitkat 4.4 onto my Xoom I didn't need the initial TWRP recovery, only the BigPart version. Once I skipped to the BigPart recovery, the problem described above did not recur.
Hi all,
I'm trying to get root access on my OPO, so I read some information about the process.
It has CM 11S R38.
* Update recovery unchecked.
* Bootloader unlocked.
Til here everything is OK. The problem starts when I install TWRP or any other custom recovery (I've tried also with Philz CWM). After the installation (via fastboot) it says everything was correct, but when I restart in Recovery the device just "freezes" (actually is the screen which keeps with OPO Logo) and then it becomes to black screen. After this happens I have to force a soft-reset to restart system.
I've tried to roll back to the stock recovery and it works perfectly. But any time I try to flash the custom recovery again, then blackscreen...
I really want to root my device, but I need the custom recovery to install the binaries.
I would be happy if I can bypass the recovery installation, that's not compulsory for me. My plan was indeed flash the binaries and roll back to stock recovery.
Thanks in advance!:good:
ironwick said:
Hi all,
I'm trying to get root access on my OPO, so I read some information about the process.
It has CM 11S R38.
* Update recovery unchecked.
* Bootloader unlocked.
Til here everything is OK. The problem starts when I install TWRP or any other custom recovery (I've tried also with Philz CWM). After the installation (via fastboot) it says everything was correct, but when I restart in Recovery the device just "freezes" (actually is the screen which keeps with OPO Logo) and then it becomes to black screen. After this happens I have to force a soft-reset to restart system.
I've tried to roll back to the stock recovery and it works perfectly. But any time I try to flash the custom recovery again, then blackscreen...
I really want to root my device, but I need the custom recovery to install the binaries.
I would be happy if I can bypass the recovery installation, that's not compulsory for me. My plan was indeed flash the binaries and roll back to stock recovery.
Thanks in advance!:good:
Click to expand...
Click to collapse
i had issue when my recovery was always returned to stock CM recovery
- in developer options there is checkbox "Update CM recovery", have you unchecked that?
Night5talker said:
i had issue when my recovery was always returned to stock CM recovery
- in developer options there is checkbox "Update CM recovery", have you unchecked that?
Click to expand...
Click to collapse
Yes, and did not work.
But finally I managed to install Philz Recovery. So it's solved for me. :good:
I have the same problem, but I need multirom and without TWRP it doesn't work. Anyone help us?
ValoXis said:
I have the same problem, but I need multirom and without TWRP it doesn't work. Anyone help us?
Click to expand...
Click to collapse
For me TWRP works only on ColorOS but the OS doesn't boot, with 11S the OS boots but recovery doesn't boot.
Hi everyone
I have a small trouble installing the twrp custom recovery. At the moment, I have the 8.1.4 Miui with MM 6.0.1 official rom. With this, comes the MiRecovery, as you all know. So, to have the twrp recovery I flash the cwm recovery first, via MiRecovery as "update.zip". After that I swich off the phone and get again into cwm recovery. After this, I install the twrp recovery. Until here, no problem. The troubles comes now: if I swich off the phone and get into recovery it goes correctly to twrp recovery, but when I reboot to system to start the phone, if I try to get again to the recovery it comes the MiRecovery, not the twrp.
What am I doing wrong?
(I flash the cwm recovery first because renaming the zip file of the twrp as update.zip, it does not work; that's why I install first the cwm recovery).
Any help will be wellcome.
Thanks in advance.
Toni.
Hi.
It's solved. I don't know how, but now it works