Hi all,
I have a moto e2 LTE surnia XT1527. I have have in stock marshmallow (24.51.39.surnia_amxla.amxla.en.01) and I've been using it for quite some time. I have twrp 3.0.2 installed and working fine (I only had to flash 6.0 by hand because twrp breaks OTA).
The problem I'm having is when trying to root it. I've tried beta-supersu 2.67 and 2.71 and stable-supersu 2.65 and with them I have the same problem:
After flashing the supersu.zip, the phone stops booting and hungs in the boot loader (it vibrates, shows the 'unlocked bootloader' and that's it). I have 'fixed' the phone by flashing system.img_sparsechink files, but that only get's me the phone back without root.
How can I get root? is this a selinux issue (which would totally make sense)?
Wrong thread, this is for moto e 1st gen.
But anayway, you need to flash the zip file of supersu stable, not the beta, because the beta make changes on the boot.img for make su work
Link of the stable relase:
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
Related
So i have this brazillian xt1022 with official ota updated lollipop, which i tried to root (sorta long story), it boot looped after a complete discharge on the boot image. After it, i did the downgrade to 4.4.2 and no progress has been done, just the recovery has gone tottaly useless, it now is boot looping quickly on the no command screen . Now i do not have any access to recovery, neither to adb (obviously) and just have the fastboot. I tried flashing again the downgrade rom, but there's that gtp error about trying to downgrade. Tried to flash boot.img too.
Ps: the update command won't work since no roms i found have the android-info.txt.
Any idea about what to do? Or any official rom to send me? it has to be a lollipop rom to the things work?
Hello!
This is my first post. I've searched for hours. Visited over 200 sites and forums tried multiple things installed all available android tools you can find online and i am seriously stuck.
Setup before problem : One Plus X - Cm13 - Version 2016 - Oct - 10. This is updated from the cyanogen website and its treated as the stable version.
Downloaded the latest version which is the 15th and got stuck at bootloop. After some searching i discovered that i had to updated my bootloader as it was the same since November 2015. In the website that i got the new version i was also given the new TWRP version 3.0.2 . So i went into my recovery flashed the new bootloader , then the TWRP , then the new ROM. Mobile boots up shows completly empty fresh install CM 13 without gapps or any of my previously installed programs. Everything is still in the storage. All installation folders from the various programms i had.
My recovery mode refuses to Boot. It just stays on the one plus logo. Tried TWRP manager from the OS but the old version 2.8.7.0 refuses to be unistalled. Adb command lines : I've been trying on windows 10 , 8 , 7 with the appropriate drivers and the only thing that i can make the phone do is go to either FASTBOOT or normal boot. Flashed the TWRP multiple times and no changes what so ever. I can make the mobile show up with ADB device, Fastboot device it shows success and when i try to boot into recovery it just gets stuck. I also got the MTP package from Windows. Basically i bricked my phone within a glass. OS works but Recovery not. Fastboot is supposignly working but i see no changes.
Thank you in advance!
Install original stock recovery then 2.2.3. If you want to use ashwins cm13,cm14 from here on out and a couple other ROMs required updated bootloader. You achieve this by flashing 3.1.3 Oxygen OS. After you updated your bootloader only twrp you can use is blusparks latest v41 or Nichets twrp. On a side note 2.8.7 twrp is old 3.0.2 is latest.
Exodusche said:
Install original stock recovery then 2.2.3. If you want to use ashwins cm13,cm14 from here on out and a couple other ROMs required updated bootloader. You achieve this by flashing 3.1.3 Oxygen OS. After you updated your bootloader only twrp you can use is blusparks latest v41 or Nichets twrp. On a side note 2.8.7 twrp is old 3.0.2 is latest.
Click to expand...
Click to collapse
Thank you i managed yesterday from a program to flash twrp as kernel and was rebooted into a working twrp and fixed everything from there.
I had my Moto G rooted for a few days, borked an attempt to flash to a new rom (Carbon), had to re-flash back to stock. From this point I am no longer able to root my phone. I have tried to flash SuperSU.zip to no avail (worked originally). What happens is after an apparently successful flash of SuperSU and reboot, I get stuck in the unlocked bootloader screen. I've tried SuperSU 2.46, 2.62, 2.79 and all lead to getting stuck in the unlocked bootloader screen. I've had to reflash my stock system each time.
Why would I be able to root once but never again? The first time I did select (in TWRP) to make system files RW instead of read-only, which is what I did originally when it worked. Do I suddenly need to set the system directories as read-only now?
I have a moto G3, uk model, running MM 6.0.1 rooted with system less superSU, and want to transition to magisk, only to find a boot loop on the boot loader unlocked screen, (maybe because the boot.img I have is for lollipop 5.0.1) any idea how to replace superSU with magisk? (Ps: I have restored with my twrp backup, so I have the SUPERSU boot.img)
I am really happy with Carbon 5.1, but thought Oreo might have achieved similar stability
Problem is that after flashing .570 and .291 there is a bootloop into recovery when attempting to flash any Oreo boot.img
The crazy part - the device was bought used with D6502 in the settings, and after flashing .291 using flashtool? Baseband patch fixed connectivity issues - Then I pull out the MicroSD strip and lo and behold its actually D6503. Then any RR/Carbon/lineage Oreo boot.img throws the recovery into a bootloop
Immediately flash the 5.1 Carbon boot.img and things return to normal. A bit confusing here.
Apologize if this is dumb - but can I just install Oreo ROMs without the initial boot.img flash, or even on top of one extracted from Andro/Advanced Kernel?
Okay just pushed through it
I didn't flash the RR boot.img coming from carbon 5.1 N. Just RR 6.0 or 8.1 with gapps regular style and not a single hiccup. I forgot to download magisk and came back and the Recovery loop began
I decided well WTF let's try to flash magisk in between loops it does modify the boot.img. The loop stopped and I took my time flashing xposed 8.1 and the baseband patch.
RR 8.1 or 6.0 works beautifully without a hitch but entering recovery begins the loop. I am going to try flashing older TWRP versions or the modded 3.1.1 by the generous developer
Problem solved - Just installed TWRP recovery 3.1.1, many thanks to aboodyaiman - https://forum.xda-developers.com/xperia-z2/development/recovery-twrp-3-1-1-0-touch-recovery-t3640856. And as I suspected it was a boot.img / recovery issue. Now running on my desk for 30 minutes without a hitch in recovery and no problems with LOS / RR Oreo
Great work everyone ITT, congratulations all round