I got a "failed to unmount /system error message while flashing SuperSU .zip file via TWRP. The flashing process was successful but now my phone is stuck on Blue M logo after reboot. I have cleared Dalvic cache too.
kushalchauhan98 said:
I got a "failed to unmount /system error message while flashing SuperSU .zip file via TWRP. The flashing process was successful but now my phone is stuck on Blue M logo after reboot. I have cleared Dalvic cache too.
Click to expand...
Click to collapse
Which TWRP are u using. Use Squid's TWRP. Also which android version are u on, u might have flashed the wrong version.
kushalchauhan98 said:
I got a "failed to unmount /system error message while flashing SuperSU .zip file via TWRP. The flashing process was successful but now my phone is stuck on Blue M logo after reboot. I have cleared Dalvic cache too.
Click to expand...
Click to collapse
First, use squid2's custom TWRP. Official TWRP seems to have issues.
Second, if you're on Marshmallow, there's an issue flashing SuperSU for root, leads to being stuck at the bootloader unlock screen. People have had success with this guide: http://androiding.how/root-moto-g-2014-marshmallow/
ayush rao said:
Which TWRP are u using. Use Squid's TWRP. Also which android version are u on, u might have flashed the wrong version.
Click to expand...
Click to collapse
Yeah, I'll try flashing squid's TWRP. I'm on Marshmallow and I flashed the correct version. Thanks!!
xtermmin said:
First, use squid2's custom TWRP. Official TWRP seems to have issues.
Second, if you're on Marshmallow, there's an issue flashing SuperSU for root, leads to being stuck at the bootloader unlock screen. People have had success with this guide: http://androiding.how/root-moto-g-2014-marshmallow/
Click to expand...
Click to collapse
Thank you!! I'll try that. But are you sure it will work for Moto E too?
kushalchauhan98 said:
Thank you!! I'll try that. But are you sure it will work for Moto E too?
Click to expand...
Click to collapse
Yes. Other people here have used it. It's a general Moto+Marshmallow+SuperSU issue.
xtermmin said:
First, use squid2's custom TWRP. Official TWRP seems to have issues.
Second, if you're on Marshmallow, there's an issue flashing SuperSU for root, leads to being stuck at the bootloader unlock screen. People have had success with this guide: http://androiding.how/root-moto-g-2014-marshmallow/
Click to expand...
Click to collapse
My phone is successfully rooted. Thank you so much!!!
Related
I tried TWRP but it results in error 7!
I tried flashing full zip of current system & then OTA but it still doesn't work!
Any other way to do it without wipe ?
Nobody?
TheDj408 said:
I tried TWRP but it results in error 7!
I tried flashing full zip of current system & then OTA but it still doesn't work!
Any other way to do it without wipe ?
Click to expand...
Click to collapse
relock bootloader
TheDj408 said:
I tried TWRP but it results in error 7!
I tried flashing full zip of current system & then OTA but it still doesn't work!
Any other way to do it without wipe ?
Click to expand...
Click to collapse
There is an error in the twrp version. A fix has been released update your twrp version and try again. For more details see the twrp thread.
simplyme2908 said:
There is an error in the twrp version. A fix has been released update your twrp version and try again. For more details see the twrp thread.
Click to expand...
Click to collapse
Which thread ?
TheDj408 said:
Which thread ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/red...official-twrp-3-0-2-0-recovery-redmi-t3352966
This thread was originally for Pixel-specific rooting instructions, but by now the SuperSU ZIP and TWRP are fully supported:
- Fastboot boot TWRP
- Install latest SuperSU ZIP (v2.79-SR3 at the time of writing)
Note that at this time I recommend against fastboot flashing TWRP. With the Pixel's new partition layout, the recovery files are inside the boot partition, and so is SuperSU. If you flash both, SuperSU's internal boot image backup will not be of the original boot image, but of TWRP. This means that neither the 'full unroot' option in SuperSU, nor incremental OTA update through FlashFire, will work as expected.
OR
- Use CF-Auto-Root for Pixel (not released at the time of writing, but should be released soon)
Nice work!
Hell Yeah!!! Thanks @Chainfire, your time as well as others that have made this and the bootloader unlock happen is appreciated very much.
Sent from my Pixel XL using Tapatalk
can we flash another kernel such as elementalX on top of this?
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
How does this relate?
Ker~Man said:
How does this relate?
Click to expand...
Click to collapse
because I attempted to not really thinking about that its systemless and wasnt sure if root would persist. after attempting to flash boot elementalX's kernel my device just powered off so i immediately reflashed root and all is okay now
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
I did read the readme.. so not sure what your getting at
cwalker0906 said:
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
Click to expand...
Click to collapse
chainfire said:
- If you want to use a custom kernel, simply 'fastboot boot' the root image again after flashing the custom kernel. This has been tested with a few custom kernels and found to work well so far.
Click to expand...
Click to collapse
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
lexcyn said:
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
Click to expand...
Click to collapse
okay thanks, so i guess the answer is actually yes
Thanks @Chainfire - booted and working well!
thanks..emoji..root explorer.. viper.. naptime.. titanium.. yes..
if new kernel must boot boot to root again..
Seems I cannot remount /system_root as rw (to copy Emoji font over).
marlin://system_root/system/fonts # mount -o remount,rw /system_root
mount: '/dev/block/bootdevice/by-name/system_a'->'/system_root': Device or resource busy
Edit: Nevermind, used Solid Explorer and granted it SuperUser and seemed to work. Strange.
Does anyone have the stock boot.img for the pixel xl? I don't have the data to download the full factory image.
Life is good!
Thanks to all involved, especially Chainfire.
You Rock!
Worked like a charm. Thanks @Chainfire!
Can't thank you enough. Works perfectly.
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
spunks3 said:
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
Click to expand...
Click to collapse
fastboot boot boot-to-root.img
lexcyn said:
fastboot boot boot-to-root.img
Click to expand...
Click to collapse
what about superSU?
Hi folks, i am struggling with this issue the last 2 days,
first i kinda bricked my X, i followed this guide to bring it back on
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
i made all updates available to 3.1.4... i unlocked boot loader, flashed TWRP blu_sp★rk r175 and afterwards tryed to flash latest CM13 nightly
but with no luck, i am always receiving Error 7.. does anyone has a solution to this?
thanks in advance!
Tommyr84 said:
Hi folks, i am struggling with this issue the last 2 days,
first i kinda bricked my X, i followed this guide to bring it back on
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
i made all updates available to 3.1.4... i unlocked boot loader, flashed TWRP blu_sp★rk r175 and afterwards tryed to flash latest CM13 nightly
but with no luck, i am always receiving Error 7.. does anyone has a solution to this?
thanks in advance!
Click to expand...
Click to collapse
There's no blu spark kernel for ROMs/OOS with updated bootloader . Not sure if that's what causing the error 7 but its a start. Try using. Sultans uodated twrp I don't have any issues with it.
Exodusche said:
There's no blu spark kernel for ROMs/OOS with updated bootloader . Not sure if that's what causing the error 7 but its a start. Try using. Sultans uodated twrp I don't have any issues with it.
Click to expand...
Click to collapse
hmmm.. ok, i will give it a try! Thanks, i will tell if this works out
Tommyr84 said:
hmmm.. ok, i will give it a try! Thanks, i will tell if this works out
Click to expand...
Click to collapse
V175 is a kernel
You certainly flashed BS TWRP V41.
Kéno40 said:
V175 is a kernel
You certainly flashed BS TWRP V41.
Click to expand...
Click to collapse
so i tried sultans TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23)... also flashed SuperSU.. worked like a charm!
But when i am trying to flash CM13 (cm-13.0-20161122-NIGHTLY-onyx) i still get Error 7 ...
You tried to flash TWRP for CM13 sultan rom ?
Tommyr84 said:
so i tried sultans TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23)... also flashed SuperSU.. worked like a charm!
But when i am trying to flash CM13 (cm-13.0-20161122-NIGHTLY-onyx) i still get Error 7 ...
Click to expand...
Click to collapse
Flash twrp from here
http://forum.xda-developers.com/one...al-twrp-3-0-2-0-recovery-onyx-t3471584/page10
Fap4k said:
Flash twrp from here
http://forum.xda-developers.com/one...al-twrp-3-0-2-0-recovery-onyx-t3471584/page10
Click to expand...
Click to collapse
ok, i flashed this Twrp version, same error ! Error : 7 Error installing zip file
i realy don't know which point i am missing, i downloaded the CM13 nightly fresh from the official side...
i can't be the only one who is facing this error
Update the Boot-loader first, you can follow a post found in home page of opx, u still have to use another TWRP recovery (not official) after updating bootloader. U vil get all info in the thread.
raj.ify said:
Update the Boot-loader first, you can follow a post found in home page of opx, u still have to use another TWRP recovery (not official) after updating bootloader. U vil get all info in the thread.
Click to expand...
Click to collapse
Hi, according to your post, i followed this description http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
flashed "OPXBLUpdateOOS3.1" and new TWPR afterwards "twrp-3.0.2-2_blu_spark.v41-onyx_by-engstk.img" with no error!
rebooted into recovery, tried to install "cm-13.0-20161204-NIGHTLY-onyx" ... and guess what?! ERROR 7 again!
so i am defenetly on new bootloader, i tried all 3 options from the threat above (flashed via ADB and via SD card) no problem! also got bootloader unlocked info form ADB.
everything works, till i try to flash a CM image... then i receive ERROR 7 ;(
Hey There,
I`m stuck with the same Error.
The only Recovery i can boot ist the normal TWRP Recovery.
The blu Spark TWRP Recovery, the Stock Recovery and the CM13 Nighty Onyx Recovery wont work. I get the fastboot DTB not found Error.
And I cant install any custom ROM. I Always get the Error 7, ZIP could not be installed from Z://
If i erase the Assets it boots directly in to Bootloader (without saying Fastboot Mode on the screen, but with the OnePlus Logo).
If I flash one of the CM14 versions it gives no error 7 but boots into the Bootloader as well.
I have no custom kernel installed.
My plan was to flash the CM13 Nighty Onyx Recovery but I cant get around the DTB error,
Thanks for Help.
Greetings Clon
EDIT:
I tied the BL Update from the mentioned thread above.
aaaaand: Error 7
Here is my complete error:
Code:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
[COLOR="Red"]Updater ended with ERROR: 7
Error installing zip file '/sdcard/ROMs/cm-13.0-20161122-NIGHTLY-onyx.zip'[/COLOR]
---------- Post added at 05:33 PM ---------- Previous post was at 04:56 PM ----------
Okay I have a Solution, but I dont know how I did it.
This is what I made.
1. I did a factory reset.
2. I did a factory reset. (Why not tho)
3. I restarted the recovery.
4. I did a factory reset.
5. I changed the filesystem for data partition. (It was on ext4, but I changed it to ext4 although to get Errors out or something like that.
6. I rebooted into Bootloader.
7. I flashed and booted this recovery: http://forum.xda-developers.com/devdb/project/dl/?id=20236&task=get (and got no dtb error. yay!)
8. I installed the nightly CM, and the latest gapps (and i got no error 7. yay!)
I know its a bit random but i think the error has to do something with the data partition and the filesystem....
Void your warranty!
Unofficial TWRP 3.1.0-0 Moto G5 (cedric)
Latest TWRP changelog :
New features of 3.1.1-0 (adb backup, tweaked MTP startup routines and plenty of bug fixes - for full changelog)
Download Link
twrp-3.1.1-0-cedric.img
Working/Bugs
I have just tested on 16 GB variant and all seems to be working. If something is broken lemme know.
IMPORTANT NOTE :
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well
If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Installation Guide
Make sure you have unlocked bootloader
Reboot to bootloader
fastboot flash recovery twrp-****.img (if you want permanent flash) or fastboot boot twrp-****.img (if you want temporary
boot)
XDA:DevDB Information
[Unofficial] TWRP 3.1.1-0 Moto G5, Tool/Utility for the Moto G5
Contributors
Santhosh M
Source Code: http://Using prebuilt stock kernel and hence no kernel source available
Version Information
Status: Stable
Stable Release Date: 2017-10-05
Created 2017-03-17
Last Updated 2017-10-05
Reserved
Reserved
Even though I have the plus variant, it's cool to see these features popping up.
Johny Cipeli said:
Even though I have the plus variant, it's cool to see these features popping up.
Click to expand...
Click to collapse
+1
Grt @Santhosh M
Santhosh M said:
Reserved
Click to expand...
Click to collapse
Gonna get that g5+ Bro? it would be awesome if you will be there for support too.
xt1670 model
Hi Santhosh
Will this TWRP work on Moto G5 model xt1670?
If so, can it be rooted using twrp temporary boot?
EDIT: I have tried this several time, I'm always getting stuck at boot, after the first data wipe, only solution is to install stock system again.
I have the Modem Version: M8937_8000.122.02.40R, 32GB
I'm offering to test
Thanks
Works fine for the most part, though reboot options Bootloader and Power Off doesn't work, just restarts normally.
XT1676
KawaiiNeko said:
Works fine for the most part, though reboot options Bootloader and Power Off doesn't work, just restarts normally.
XT1676
Click to expand...
Click to collapse
Plz share the procedure you had followed.
Did you able to achieve root access?
fAIyaZ said:
Plz share the procedure you had followed.
Did you able to achieve root access?
Click to expand...
Click to collapse
Unlocked bootloader, flashed twrp, factory reset, good to go. Sadly no root though.
KawaiiNeko said:
Unlocked bootloader, flashed twrp, factory reset, good to go. Sadly no root though.
Click to expand...
Click to collapse
Try phh su.
Flash it through twrp: https://superuser.phh.me/superuser.zip
Then installed the phh superuser app: https://play.google.com/store/apps/d....phh.superuser
fAIyaZ said:
Try phh su.
Flash it through twrp: https://superuser.phh.me/superuser.zip
Then installed the phh superuser app: https://play.google.com/store/apps/d....phh.superuser
Click to expand...
Click to collapse
worked perfectly! https://i.imgur.com/71G0cN2.png
I'll get my G5 16gb lunar grey tomorrow and can't wait to root
Thanks for testing out
Bootlooping
Hi guys, I got bootloop in my moto g5 after TWRP boot/install, should I open a new thread or somebody can help here?
linsspinho said:
Hi guys, I got bootloop in my moto g5 after TWRP boot/install, should I open a new thread or somebody can help here?
Click to expand...
Click to collapse
Depending on your phone version, you might need to flash system using fastboot.
KawaiiNeko said:
worked perfectly! https://i.imgur.com/71G0cN2.png
Click to expand...
Click to collapse
So i believe TWRP works as intended and root is also achieved via phh/whatever?
If all works fine for you would like you to make reply in the thread with detailed flashing instructions as i am not sure why few in thread have issues
can this version of twrp be used for POTTER version of moto G5 plus?
After installing TWRP my Phone stucks at the "Your device has been unlocked" screen. My system seems to be gone. I've downloaded the image from the other thread and tried to sideload it, but twrp says it's in the wrong format. TWRP boots fine
(Anyone who can upload a fully working NANDROID or sth like that?)
What can i do :/?
Edit: Solved. Unzipped the firmware and flashed manually via fastboot. Working fine!
But then again at the startup of the recovery, there's the encryption message. What to wipe now, that it'll work? Wiping /data ends in boot loop...
.sirhc said:
After installing TWRP my Phone stucks at the "Your device has been unlocked" screen. My system seems to be gone. I've downloaded the image from the other thread and tried to sideload it, but twrp says it's in the wrong format. TWRP boots fine
(Anyone who can upload a fully working NANDROID or sth like that?)
What can i do :/?
Edit: Solved. Unzipped the firmware and flashed manually via fastboot. Working fine!
But then again at the startup of the recovery, there's the encryption message. What to wipe now, that it'll work? Wiping /data ends in boot loop...
Click to expand...
Click to collapse
Did you tried wiping data, and formatting data? Remember that wiping /data is where your apps and settings are stored, and formatting /data/media is the massive storage... Maybe if you wipe both it would work
Enviado desde mi Moto G (5) Plus mediante Tapatalk
After
fastboot flash recovery twrp.img
I'm booting into recovery, cancel the encryption password verification, swipe to allow modification, wipe & format data -> Bootloop
Flashing system (and only system, not recovery etc) -> Phone boots normally, twrp ist gone ...
Greetings
Hi guys
Can't install any OS (tried via ADB commands and flashing custom roms via TWRP).
Whatever I try, it just boots to TWRP.
ADB commands do work because I managed to install TWRP 3.0 and 3.1 for the Moto Z Griffin
Bootloader is unlocked
This device was working fine on Stock Noughat (installed via ADB) and AOKP (installed via TWRP).
Problems began when the camera "failed to start" and in my frustration, I wiped everything via TWRP including system, so now I have no OS.
Not sure why I can't get anything to install.
Follow this guide: https://forum.xda-developers.com/showthread.php?t=3506342
Sent from my XT1650 using XDA-Developers Legacy app
grneyez said:
Follow this guide: https://forum.xda-developers.com/showthread.php?t=3506342
Sent from my XT1650 using XDA-Developers Legacy app
Click to expand...
Click to collapse
followed that guide
Had this working for months and needed to wipe so I did a factory reset and all my phone does is boot to twrp
I tried this process again and all goes good or so it seems but just boots to twrp
I tried a restore from my backup from twrp and get all the way done and it fails on "unable to wipe Fsg."
Above there is a bunch of red failed:
Could not mount /data and unable to find crypto foooter
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder
Failed to mount'/cache' (invalid argument)
failed to mount'/system'(invalid argument)
Failed to mount storage
failed to mount'/data'(invalid argument)
failed to mount'/cache'(invalid argument)
failed to mount'/data/media/twrp'(invalid argument)
unable to wipe fsg.
any ideas? right now just a brick here. i have tried flashing roms from twrp and still just boot to twrp
I'm assuming you tried to flash the stock ROM via fastboot?
If so, I'm a little at a loss here. Although since you have TWRP, try flashing the stock ROM along with its recovery following the guide linked below;
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
And grab the firmware for your device here;
https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Make sure it's the correct firmware for your device. If you updated to Nougat via an OTA, you have to flash a Nougat ROM. You may also use the one linked in the XDA article, although I can't guarantee its stability.
D13H4RD2L1V3 said:
I'm assuming you tried to flash the stock ROM via fastboot?
If so, I'm a little at a loss here. Although since you have TWRP, try flashing the stock ROM along with its recovery following the guide linked below;
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
And grab the firmware for your device here;
https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Make sure it's the correct firmware for your device. If you updated to Nougat via an OTA, you have to flash a Nougat ROM. You may also use the one linked in the XDA article, although I can't guarantee its stability.
Click to expand...
Click to collapse
Maybe it's because I haven't had my coffee yet, but is there a US 7.0 file on that site? I can only find the 6.0 version. I'm on Rodgers nougat rom I flashed a couple weeks ago and I'd like to get on the US version since I've been having apn issues
royalflush5 said:
Maybe it's because I haven't had my coffee yet, but is there a US 7.0 file on that site? I can only find the 6.0 version. I'm on Rodgers nougat rom I flashed a couple weeks ago and I'd like to get on the US version since I've been having apn issues
Click to expand...
Click to collapse
Sadly, no.
As of right now, there's only a Marshmallow-based RETUS firmware. It'll take a while for someone to post firmware that's Nougat-based for RETUS.
D13H4RD2L1V3 said:
Sadly, no.
As of right now, there's only a Marshmallow-based RETUS firmware. It'll take a while for someone to post firmware that's Nougat-based for RETUS.
Click to expand...
Click to collapse
Ah, thanks for confirming. Do you happen to know of a twrp flashable zip for retus 7.0 then?
royalflush5 said:
Ah, thanks for confirming. Do you happen to know of a twrp flashable zip for retus 7.0 then?
Click to expand...
Click to collapse
Again, there's sadly no TWRP-flashable firmware for 7.0 RETUS.
There's only one for TELUS. While it works on other XT1650-03s with unlocked BLs, can't guarantee that it's all stable.
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-unlocked-versions-t3552210
I know this thread is old but maybe this will help someone out. I had the exact same problem after a Factory Reset my phone went on a TWRP bootloop. To resolve it, just reboot into Bootloader and then select Factory Mode. My phone just started as new.
lovetatfitties said:
I know this thread is old but maybe this will help someone out. I had the exact same problem after a Factory Reset my phone went on a TWRP bootloop. To resolve it, just reboot into Bootloader and then select Factory Mode. My phone just started as new.
Click to expand...
Click to collapse
Thank you for this!!!!!!! It solved my boot loop problem too after installing stock via fastboot. Only thing that worked.
raymccoy said:
Thank you for this!!!!!!! It solved my boot loop problem too after installing stock via fastboot. Only thing that worked.
Click to expand...
Click to collapse
thanks for the Rescue same trick work for me though as i was been stuck on TWRP after flashing stock firmware via fastboot , so i manage to flash irfan v4 stock rom and booted to factory image to get it resolved , But now i want to move to complete stock without twrp as i think Oreo update is near by but i get the same issue again, Just wanna ask can u help me out with the process to go back to stock Rom
lovetatfitties said:
I know this thread is old but maybe this will help someone out. I had the exact same problem after a Factory Reset my phone went on a TWRP bootloop. To resolve it, just reboot into Bootloader and then select Factory Mode. My phone just started as new.
Click to expand...
Click to collapse
that worked for me also, but it's not a fix, its a workaround. is there an actual fix for this? I've tried the Verity_FE_patcher but that didn't work also.