cm-14.1-20161105-UNOFFICIAL-otterx.zip | by HashBang for Kindle Fire
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
it is otterx bootloader, do sone research. idk who is the dev?
I just installed this today after installing the otterx bootloader and recovery. I cant get past the setup screen. When I hit next it says settings has stopped. I didn't flash gapps. Have you been able to successfully pass this part?
Edit: found a fix here
Related
Hi,
I originally posted this over at android central where I was told it is not possible to root a Moto G4, so I am trying here hoping for a different answer = )
I am attempting to install Cyanogenmod on my handset using the below guide:
Install_CM_for_peregrine (looks like I can't post link but that is the name of the page on he Cyanogenmod site)
I have unlocked the handset, copied the Cyanogenmod zip file to my sdcard, booted in recovery mode and attempted to install the zip package. At this point I get an error "E:failed to verify whole-file signature". I have tried both the stable and nightly build with the same result. Also when I have attempted to install SuperSU using the same process have received the same error so I suspect it is not a corrupted file.
I believe this is being caused by the signature check and to get around this have been following the below guide to disable signature check:
tutorial-how-to-disable-signature-check.html (name of the tutorial as can't post links)
When it comes to the step "Then find a option Called "Patch To Android", I don't see this option, and from what I understand this may be due to not having my phone rooted.
I have installed Kingo ROOT to resolve this but it failed to root the handset (error 0x1C5C33 if that means anything to anybody), checking the list of phones which Kingo ROOT can root, Moto is not one of them. What are the other options?
Any advice greatly appreciated. Thanks in advance.
Get rid of kingo. Look up android doctor on YouTube for unlock, root, twrp instructions. CM has a lot of bugs and isn't ready for daily use on this device. Slim roms has released their rom, it's CM based. I've been using it for a few days, and it's running smooth. There's a thread about it with the link on here. The only problem I've had was a boot loop when I try and flash xposed and supersu. There's a built in super user access in the settings, so supersu isn't necessary.
hooks024 said:
Get rid of kingo. Look up android doctor on YouTube for unlock, root, twrp instructions. CM has a lot of bugs and isn't ready for daily use on this device. Slim roms has released their rom, it's CM based. I've been using it for a few days, and it's running smooth. There's a thread about it with the link on here. The only problem I've had was a boot loop when I try and flash xposed and supersu. There's a built in super user access in the settings, so supersu isn't necessary.
Click to expand...
Click to collapse
Phone rooted, thanks!
Now to install SlimRoms
Strange, after rooting gained the below options in Lucky Patcher:
Signature Verification Status always True
Disable .apk Signature Verification
Disable signature verification in the package manager
Patch applied for all three, but then when I restart in recovery mode and attempt to install the SlimRoms zip still getting error "E:failed to verify whole-file signature".
I didn't patch anything. Just root, installed twrp, and flashed slim rom and gapps
hooks024 said:
I didn't patch anything. Just root, installed twrp, and flashed slim rom and gapps
Click to expand...
Click to collapse
Ah I see, did not realise you install the rom via twrp. It's installed now, awesome, thanks.
I have a Moto G4 Athene (not Plus, and not Play).
I did the following:
unlocked bootloader
flashed TeamWin recovery
installed SuperSu 2.79 SR3 from TeamWin install
The phone no longer boots. Just a black screen. Flashing notification light if put on USB.
I can still get into the bootloader, and from there into TeamWin recovery, but I'm not having any luck beyond that.
Sadly, I didn't create a backup.
I tried installing LineageOS 14.1, pushing with ADB in recovery, and then installing with TeamWin. Even though I can add the file to the phone and I can run the install, a reboot returns a black screen.
Any advice? I'm afraid this isn't looking too good.
By the way, you can just work with twrp after installing that... stock recovery (fastboot adb) doesn't belong anymore. At first I would suggest that you post the details which are shown in your bootloader.
Furthermore I would recommend just to flash stock rom and testing that case.
Sent from my Moto G (4) using XDA Free mobile app
Ferwerda said:
I have a Moto G4 Athene (not Plus, and not Play).
I did the following:
unlocked bootloader
flashed TeamWin recovery
installed SuperSu 2.79 SR3 from TeamWin install
The phone no longer boots. Just a black screen. Flashing notification light if put on USB.
I can still get into the bootloader, and from there into TeamWin recovery, but I'm not having any luck beyond that.
Sadly, I didn't create a backup.
I tried installing LineageOS 14.1, pushing with ADB in recovery, and then installing with TeamWin. Even though I can add the file to the phone and I can run the install, a reboot returns a black screen.
Any advice? I'm afraid this isn't looking too good.
Click to expand...
Click to collapse
First of all, if you read their corresponding threads, you need to do the following when rooting:
- Unlock bootloader/flash TWRP (you did)
- Flash a custom kernel (Vegito or ElementalX)
- And then wipe ART/Dalvik Cache
Second, for LineageOS- you cannot dirty flash custom ROMs, EVER EVER EVER! By this I mean you have to wipe system/data/cache/dalvik etc.- you can ignore Internal Storage and the SDCard/OTG.
You may (should) have to flash the Moto G4 Nougat radio that's floating around XDA somewhere. LOS worked fine for me without doing that, but I know other ROMs require it.
Finally, as a quick heads up, all Moto G4 Plus ROMs work fine with the G4, including any stock ROMs/backups.
Edit: I heavily suggest Magisk or phh SU over SuperSU- Magisk allows you to use SnapChat and Pokemon Go, and phh's is open source.
Thanks for the responses.
I was able to restore the phone with a stock rom I found on these boards. After that, I received two OTA, one to 6.0.1 and then the current to 7.0.0.
I have the same problem than you... Can you send me the link that you use to fix it?
Ferwerda said:
Thanks for the responses.
I was able to restore the phone with a stock rom I found on these boards. After that, I received two OTA, one to 6.0.1 and then the current to 7.0.0.
Click to expand...
Click to collapse
raulcalaca said:
I have the same problem than you... Can you send me the link that you use to fix it?
Click to expand...
Click to collapse
Just flash ElementalX 1.04 kernel (after flashing SuperSu or Superuser or Magisk) when trying to root STOCK Nougat 7.0 as it's designed to thwart any root attempt.
Ferwerda said:
Thanks for the responses.
I was able to restore the phone with a stock rom I found on these boards. After that, I received two OTA, one to 6.0.1 and then the current to 7.0.0.
Click to expand...
Click to collapse
can you please give the step by step guide you followed to recover your phone!!!
I tried all methods which are there on site but each time same and only problem is coming that is my phone is not getting rooted correctly I tried so many times but when I'll check with root checker it says it's not rooted but I successfully unlocked bootloader but I can't complely root it, can someone help me?
What device do you have and what ROM are you running?
If you're rooting on the stock Motorola ROM, do you have TWRP flashed/booted, then flashed ElementalX? Afterwards, what root managers are you using? You could try magisk 16 or 15.3. However, if you've previously used SuperSU or another root manager, you may have to re-flash the original stock kernel (then flash ElementalX then root) to remove any remainders of the old root managers, else they may interfere with magisk to the point of the root not being stable.
I have Moto g4 plus XT 1643 and I tried to root with by using twrp latest version and lineage os 14.1 athene. The was working fine but my phone is still showing that this device is not rooted
MsK96918 said:
I have Moto g4 plus XT 1643 and I tried to root with by using twrp latest version and lineage os 14.1 athene. The was working fine but my phone is still showing that this device is not rooted
Click to expand...
Click to collapse
What root manager are you using? The official Lineage OS (as of Jan 2017) does not come with a root manager, you must download and flash your own. You could either use the Lineage_SU_addon (you'd want the arm variant for 14.1) or magisk or SuperSU as a root manager.
I am new in this so I don't know that much details so can you help me by giving me link so that I can go through step by step and try to do what you are saying
MsK96918 said:
I am new in this so I don't know that much details so can you help me by giving me link so that I can go through step by step and try to do what you are saying
Click to expand...
Click to collapse
1)Download the Lineage SU addon (from here https://download.lineageos.org/extras - you want the arm 14.1 zip) OR magisk (from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 ) Only download one, please and if you want to switch, you ideally want to restore your backup or dirty flash the custom ROM to restore the Lineage kernel.
2)Reboot your device to TWRP.
3)In TWRP backup your device. Keep this backup safe.
4)In TWRP, go to 'Install' and flash the package you downloaded.
5)Wipe cache and Dalvik in TWRP after the flash.
6)Reboot.
7)Verify you have root.
You may also wish to browse the Lineage 14.1 thread for our device here: https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101 Please use the search function by the page numbers to quickly search the thread for information
echo92 said:
1)Download the Lineage SU addon (from here https://download.lineageos.org/extras - you want the arm 14.1 zip) OR magisk (from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 ) Only download one, please and if you want to switch, you ideally want to restore your backup or dirty flash the custom ROM to restore the Lineage kernel.
2)Reboot your device to TWRP.
3)In TWRP backup your device. Keep this backup safe.
4)In TWRP, go to 'Install' and flash the package you downloaded.
5)Wipe cache and Dalvik in TWRP after the flash.
6)Reboot.
7)Verify you have root.
You may also wish to browse the Lineage 14.1 thread for our device here: https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101 Please use the search function by the page numbers to quickly search the thread for information
Click to expand...
Click to collapse
Thank you bro i finally rooted my device correctly . It help alot thank you once again
Hi I'm new to XDA Forums, I was searching for posts about rooting my Moto g4 Plus. I would like to know Why we should flash a kernel before flashing SuperSU or Magisk ? Nb: I just only want the root access. Not in a plan to flash a custom rom. Thanks in Advance.
vinayroffl said:
Hi I'm new to XDA Forums, I was searching for posts about rooting my Moto g4 Plus. I would like to know Why we should flash a kernel before flashing SuperSU or Magisk ? Nb: I just only want the root access. Not in a plan to flash a custom rom. Thanks in Advance.
Click to expand...
Click to collapse
The stock Motorola kernel in stock Nougat ROMs appears to have anti rooting measures included (I think DM Verity?) If you attempt to root on this stock Nougat kernel, you'll likely soft brick/bootloop your device.
A custom kernel (e.g. elementalX v2.0.1 for stock) does not have these anti rooting defences, so it's safer to root with magisk. I would recommend magisk as super SU hasn't been updated in some time.
It appears that this need to flash a custom kernel before rooting applies to Nougat stock ROMs; marshmallow stock ROMs and the Oreo soak test stock ROM appear not to require a custom kernel.
As an aside, custom kernels and root are not necessary to flash custom ROMs. The only tools you require are an unlocked bootloader and the correct TWRP. The kernels included with these custom ROMs may also have anti rooting measures disabled, so it's safer to directly root without having to use a custom kernel.
https://github.com/phhusson/treble_experimentations/wiki/Huawei-Honor-7X
I made a page on PHH wiki for treble GSI flashing. I was able to get the Lineage and AOSP working. Most features work. I am unable to test phone features as i use this to play games only. i have set up instruction to get working to a point. This is for people who have 8.0 and boot loader unlocked
shadowsiul said:
https://github.com/phhusson/treble_experimentations/wiki/Huawei-Honor-7X
I made a page on PHH wiki for treble GSI flashing. I was able to get the Lineage and AOSP working. Most features work. I am unable to test phone features as i use this to play games only. i have set up instruction to get working to a point. This is for people who have 8.0 and boot loader unlocked
Click to expand...
Click to collapse
On latest rr v18 wifi didn't work for me. I flashed rr worked ok but couldn't get gapps installed. I tried installing twrp and flashing gapps. But wouldn't boot. Also I flashed magisk ended up in a boot loop. Thought I might have bricked my device. Flashed stock recovery and did a factory reset. Still wouldn't boot. I couldn't get back into fastboot. Finally with power plus vol up and vol down took me to install update recovery. From there I held power plus vol down to get to fastboot and was about to install twrp and restore a backup of emui. Treble is definitely not for beginners. Know what your doing and do some research before you proceed.
TREBLE IS STILL VERY EXPERIMENTAL. NOT STABLE.
allrockedout said:
On latest rr v18 wifi didn't work for me. I flashed rr worked ok but couldn't get gapps installed. I tried installing twrp and flashing gapps. But wouldn't boot. Also I flashed magisk ended up in a boot loop. Thought I might have bricked my device. Flashed stock recovery and did a factory reset. Still wouldn't boot. I couldn't get back into fastboot. Finally with power plus vol up and vol down took me to install update recovery. From there I held power plus vol down to get to fastboot and was about to install twrp and restore a backup of emui. Treble is definitely not for beginners. Know what your doing and do some research before you proceed.
TREBLE IS STILL VERY EXPERIMENTAL. NOT STABLE.
Click to expand...
Click to collapse
That is very true. If you have a github account please do help edit the page so other do not possible brick their phones.
I want to have a Samsung Stock based ROM and a LOS/AOSP ROM on my phone and switch between them, but I can't get it working. I always end up on a bootloop at the S7 Edge logo.
My bootloader and modem is updated to latest version. I wanted to install Hyper ROM and LOS 16.
So I first installed Hyper ROM, downloaded the latest version of Dual Boot Patcher, open it, allow root access, go to ROMs in the app, select my System to set the kernel. Then I go to patcher section, add the LOS-zip, gapps-zip and magisk-zip (does magisk even work with this? have tried without but also no luck) and patch them as secondary. I reboot into recovery, flash patched LOS and gapps, reboot aaaand... I'm stuck at a bootloop.
This seems to happen no matter what I try, how I switch them around, also if I patch the Hyper ROM zip as primary first. Nothing seems to help. Am I doing something wrong here?