Hi, everybody.I have a question want to know. How to flash cm13 with CM recovery and must meet gapps work well?
I always suffered failed when I flash cm13 and "NX_Gapps_M_release1.2_STD.zip" on my moto g(2013) with CM recovery, The problem is can't flash GAPPS correctly. It prompt that google service has stopped when boot the phone,it's make me can't use my phone well. But when use trwp recovery flash it, It can normally boot, and unfortunately ,I can't update my phone by CM OTA. WHen I adopt manual update, it all the same failed.So it make me must clean flash with trwp recovery, and then my all data would be lost.
How should I do?
Related
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 there
i already flashed a few phones over the last years so im not new to flashing but i never made it behind casual using custom roms.
so today i decided to flash my moto g (3g, 2012, single sim, european version) with the resurrection remix rom and gapps. before, i unlocked the bootloader via motorolas homepage (i now have the warning sign when booting up)
i followed the install instruction in resurrection remix thread and wiped my devies, flashed the rom, flashed gapps.
so somehow i ended up with a bootloop (resurrection remix logo) after flashing the zips via CWM and couldnt do anything about it.
i couldnt reboot into CWM recovery so i tried to use trwp falcon recovery and wiped everything.
i tried to install the custom rom again but it wont work. also i downloaded a stock firmware from the developers section but it didnt work either.
fastboot commands work for me, but adb doesnt (device not found) i already reinstalled motorola and adb universal drivers..
so basically im stuck at the bootloader menu. via fastboot boot recovery.img i can boot up to twrp recovery. i can't mount my devices system. i tried to install zips to my sd but it didnt work out (adb sideload doesnt work because device not found). i tried to mfastboot flash the stock in every single step (.xml.zip style) but im stuck at mfastboot flash boot boot.img (bootloader denies permission) (http://forum.xda-developers.com/showthread.php?t=2542219)
im now searching for a solution for about 6 hours (its 0600 am now) and im really frustrated.
please help me, i was never stuck in such a situation ever before
how can i fix it?
I'm with virtually the same issue.
Difference I can ADB the device. I even sideloaded others ROM but couldn't pass the boot.
Any help would be thanked.
today i managed to flash a brazil stockrom via "how to unbrick..." so i fixed my problem
but then
i tried flashing resurrection remix again (and crdroid)
i keep getting a boot loop
i dont know what im doing wrong
I own a moto g xt 1033 and installed cyaonogem mod 13, I used to recovery twrp,but he did not quit the cyaonogemmod robot image, then restarted and tried to reinstall the android back , but when the device will start it appears the image of the unlocked bootloader and restarts and it becomes infinite.
when I try to clear system cache, the TWRP error , it seems the TWRP is corrupted , what can be ?
If anyone can help me I can post a video on youtube showing defects
What TWRP version are you using? What were the steps you took to install CM and the stock ROM? What was the error that TWRP gave you?
Professor Gibbins said:
What TWRP version are you using? What were the steps you took to install CM and the stock ROM? What was the error that TWRP gave you?
Click to expand...
Click to collapse
Sorry for the delay....i using twrp 2.8.5.0, I stored in the internal storage to cyanogemcm12, It was executed wipes, install cyanogemmod, but got stuck in logo cyanogem,
I returned the recovery was made and wipes again, and install Rom XT1033 Android 4.4.4 KitKat Dual Chip, unfortunately now he does not leave the image "boot loader" unlocked).
*I have access to fastboot via adb!
*I have access to recovery!
*however after all these errors, the TWRP does not allow Wipes, and also appears error installing rom.
*When I install a rom stock fastboot , this does not seem a mistake, but goes into bootloader and is restarting without stopping
help you if I put a video on youtube?
I will record a video and share tomorrow.
Thanks
Sorry my english
Professor Gibbins said:
What TWRP version are you using? What were the steps you took to install CM and the stock ROM? What was the error that TWRP gave you?
Click to expand...
Click to collapse
i using twrp 2.8.5.0, I stored in the internal storage to cyanogemcm12, It was executed wipes, install cyanogemmod, but got stuck in logo cyanogem,
I returned the recovery was made and wipes again, and install Rom XT1033 Android 4.4.4 KitKat Dual Chip, unfortunately now he does not leave the image "boot loader" unlocked).
*I have access to fastboot via adb!
*I have access to recovery!
*however after all these errors, the TWRP does not allow Wipes, and also appears error installing rom.
*When I install a rom stock fastboot , this does not seem a mistake, but goes into bootloader and is restarting without stopping
i have link youtube
Thanks
Sorry my english
To get the phone working again, I would suggest flashing latest 5.1 version of these factory firmware images (for your exact device model) through fastboot.
To flash CM13, try using TWRP 3.0.2-0, and the latest CM13 snapshot. Note that the first boot of Cyanogenmod can take a long time (20+ minutes).
Professor Gibbins said:
To get the phone working again, I would suggest flashing latest 5.1 version of these factory firmware images (for your exact device model) through fastboot.
To flash CM13, try using TWRP 3.0.2-0, and the latest CM13 snapshot. Note that the first boot of Cyanogenmod can take a long time (20+ minutes).
Click to expand...
Click to collapse
I tried all these Step
I think TWRP is corrupt, or the fast i dont know , it installs the features, but not fixed
link my video youtube.com/watch?v=ZGgpL_JCQSY
Hi everyone
I've bought a second hand Mi 4C. The original owner had installed TWRP and LineageOS on the device.
I wanted to go back to MIUI, so I used the existing TWRP to do the usual wipes and then flash:
xiaomi.eu_multi_MI4c_V8.1.3.0.LXKCNDI_v8-5.1.zip
The ROM seems to flash correctly, however after I reboot the device it just boots back into TWRP. Basically, there's no way to boot the device "normally", it always boots to recovery!
Thinking maybe the rom was at fault, I wiped again and flashed the latest LineageOS, since I knew that was working before.
However, I then discovered that even with LineageOS the problem remained: device always starts in recovery mode!!!
How can I solve this? I'm new to Xiaomi devices, so maybe I'm missing something. I've always had Nexus phones and I've never seen a problem like this in years of flashing custom roms.
I would point torwards locked bootloader.
Maybe the volume button is stuck?
Try to go in fastboot mode and execute this:
Code:
fastboot oem device-info
If "device unlocked: False " you have to unlock bootloader or follow this guide http://en.miui.com/thread-335614-1-1.html
Hi? Did you solve this problem? My phone also keeps booting in TWRP. What i did was, get to Fastboot and typed "fastboot continue" .
Got the same. Bootloader unlocked.
i have the same issue.
I had TWRP 3.0.3-0 with the Resurrection Remix ROM. After booting into recovery and make a factory default wipe, started to boot always in recovery (TWRP). Doesn't matter if I force to reboot into system. Tried to flash the latest version of RR and nothing changed. Flashed TWRP v3.0.2 and touch screen didn't work.
Then I decided to start from the beginning, flashing the stock libra_images_6.1.7_20151221.0000.11_5.1_cn, unlock the bootloader ( fastboot oem device-info gaves me "true" unlocked), flashed TWRP 3.0.3-0, and till this point all it worked flawlessly. When I flashed the latest RR, then started the boot loop into recovery.
Any idea? Thank you very much
Latest RR 5.8.2 by AndopaX and LineageOS by HnT build with new Miui N bootloader..
You need to change TWRP base Miui N also Fw Update from Miui N..
You will get bootloop when install that roms into old Miui LP bootloader..
caxwan said:
Latest RR 5.8.2 by AndopaX and LineageOS by HnT build with new Miui N bootloader..
You need to change TWRP base Miui N also Fw Update from Miui N..
You will get bootloop when install that roms into old Miui LP bootloader..
Click to expand...
Click to collapse
Wowww! Thanks for the fast answer!
Could you help me to do that? Where can I find this TWRP base Miui N and Fw Update from MIUI N?
Thanks
korolirio said:
Wowww! Thanks for the fast answer!
Could you help me to do that? Where can I find this TWRP base Miui N and Fw Update from MIUI N?
Thanks
Click to expand...
Click to collapse
AndropaX already prepared all before build rom 5.8.2 with Miui N bootloader.
TWRP Nougat : by AndropaX
FW Update Nougat : by AndropaX
Many ways to update, I have try this one.
* Disable PIN/Pattern Lockscreen (related bug of fw nougat)
1. Boot into your old TWRP LP
2. Wipe System, Data, Dalvik and Cache
3. Install FW Update N via TWRP
4. Install new TWRP N via TWRP too
(choose install image) install to recovery
5. Reboot to new TWRP N
6. Install ROM + GAPPS via TWRP
7. Reboot to System
Yeahhhhh!!! THHHHAAAANNNKKKSSSS!!!! It works like a charm!
I have two devices where install TWRP dont work.
They are unlocked and i try many times to flash it via fastboot but booting into recovery ends in stock recovery.
Is there any solution to install TWRP or lineageos another way?
it was the issue that recovery is overwritten on stock rom start if the system has ever made an update