Related
In the past I've used CWM but with my new Moto G 2014 Dual SIM, I wanted to use encryption and I read that TWRP works with that, so I installed it but when I boot into it, it doesn't ask me for my password and /data is inaccessible (naturally!). I couldn't see any option to select to enter my password to decrypt it either. I flashed it with TWRP2801-titan-motog-2014.img
I understand that TWRP doesn't support Lollipop encryption yet but thought it did KitKat?
doveman said:
In the past I've used CWM but with my new Moto G 2014 Dual SIM, I wanted to use encryption and I read that TWRP works with that, so I installed it but when I boot into it, it doesn't ask me for my password and /data is inaccessible (naturally!). I couldn't see any option to select to enter my password to decrypt it either. I flashed it with TWRP2801-titan-motog-2014.img
I understand that TWRP doesn't support Lollipop encryption yet but thought it did KitKat?
Click to expand...
Click to collapse
My twrp support kitkat and lollipop encryption
http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2979149
luca020400 said:
My twrp support kitkat and lollipop encryption
http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2979149
Click to expand...
Click to collapse
Thanks, that's great. I can't get it to install though, as it shows I already have TWRP 2.8.0.1 installed and when I tap Recover Version to Install it doesn't list anything under Choose Version to Install and if I tap Install Recovery, that doesn't do anything either.
OK, I've installed it via the manual fastboot method now and it shows v2.8.3.0 but I still can't access /data. If I go to Mount and tap /data it doesn't do anything and if I tap /system it restarts TWRP, then locks itself and turns off the screen and when I press the volume buttons to turn it back on, it shows a padlock and a swipe to unlock. When I do that and check Mount, /data and /system are still not mounted.
The log screen shows:
Unable to mount /data
Unable to mount storage
Unable to mount /data/media during GUI startup
Full SELinux support is present
Failed to get default contexts and file mode for storage files
Unable to mount /data/media/TWRP/.twrps when trying to read settings file
doveman said:
Thanks, that's great. I can't get it to install though, as it shows I already have TWRP 2.8.0.1 installed and when I tap Recover Version to Install it doesn't list anything under Choose Version to Install and if I tap Install Recovery, that doesn't do anything either.
OK, I've installed it via the manual fastboot method now and it shows v2.8.3.0 but I still can't access /data. If I go to Mount and tap /data it doesn't do anything and if I tap /system it restarts TWRP, then locks itself and turns off the screen and when I press the volume buttons to turn it back on, it shows a padlock and a swipe to unlock. When I do that and check Mount, /data and /system are still not mounted.
The log screen shows:
Unable to mount /data
Unable to mount storage
Unable to mount /data/media during GUI startup
Full SELinux support is present
Failed to get default contexts and file mode for storage files
Unable to mount /data/media/TWRP/.twrps when trying to read settings file
Click to expand...
Click to collapse
Flash this one
https://s.basketbuild.com/filedl/devs?dev=luca020400&dl=luca020400/Motorola/recovery/twrp.img
The official one is bugged
luca020400 said:
Flash this one
https://s.basketbuild.com/filedl/devs?dev=luca020400&dl=luca020400/Motorola/recovery/twrp.img
The official one is bugged
Click to expand...
Click to collapse
Thanks but I get the same results with that I'm afraid.
Just checking if there's any news on this? I'm not sure where TWRP is meant to prompt for the decryption password but I haven't seen any prompt or option for that anywhere.
Hit that software update.
Wow thanks for the late news
my phone is upgrading now
Don't know if anybody else had trouble connecting their m9 with their Roku 3 before the update but the miracast feature now works with my Roku 3
Anyone have any suggestions on how to force the update? Still have not gotten the notification to download the update and I get the standard "There are no updates available for your phone" message when I got into settings and check for the update manually.
nickmgray said:
Anyone have any suggestions on how to force the update? Still have not gotten the notification to download the update and I get the standard "There are no updates available for your phone" message when I got into settings and check for the update manually.
Click to expand...
Click to collapse
If you are 100% stock update using the ota from stock recovery.
Download and read here
So I ran into a small issue. I was rooted with TWRP, and i re-flashed the system image that i created when I first installed TWRP. This took, as I was prompted to reinstall SuperSu. I did not reinstall, then flashed the stock recovery back to the phone.
All good so far.
Then I went to install the OTA, and received the error message
E:unknown command [set_err_msg]
/dev/block/bootdevice/by-name/system has been remounted R/W
reflash device to reenable OTA updates
Did my reinstall of the system image not take? As far as i could tell, everything worked properly until installing the OTA.
Thanks in advance for any help.
AaronM7 said:
So I ran into a small issue. I was rooted with TWRP, and i re-flashed the system image that i created when I first installed TWRP. This took, as I was prompted to reinstall SuperSu. I did not reinstall, then flashed the stock recovery back to the phone.
All good so far.
Then I went to install the OTA, and received the error message
E:unknown command [set_err_msg]
/dev/block/bootdevice/by-name/system has been remounted R/W
reflash device to reenable OTA updates
Did my reinstall of the system image not take? As far as i could tell, everything worked properly until installing the OTA.
Thanks in advance for any help.
Click to expand...
Click to collapse
I had this same issue and finally figured it out yesterday. The reason is because in older versions of twrp, the minute the recovery is booted it mounts system as read/write. So any backup done after that was potentially flawed.
First you need to download a system and boot image from http://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022. Note that the backup was created with a beta version of twrp so you have to modify the name of system file from system.emmc.win to system_image.emmc.win. Once this is done put it in your twrp folder.
The way i rectified the issue was to first flash the latest twrp recovery v2.8.7.0. The developer added a mount system as read only option in the mount section of twrp. Once you click on the checkbox. Go to restore the system backup, This time it will show up as a system image backup. Once restored, flash stock recovery and boot into os download the system update and it should go through without any hiccups.
Let me know if you have any questions
darll said:
I had this same issue and finally figured it out yesterday. The reason is because in older versions of twrp, the minute the recovery is booted it mounts system as read/write. So any backup done after that was potentially flawed.
First you need to download a system and boot image from http://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022. Note that the backup was created with a beta version of twrp so you have to modify the name of system file from system.emmc.win to system_image.emmc.win. Once this is done put it in your twrp folder.
The way i rectified the issue was to first flash the latest twrp recovery v2.8.7.0. The developer added a mount system as read only option in the mount section of twrp. Once you click on the checkbox. Go to restore the system backup, This time it will show up as a system image backup. Once restored, flash stock recovery and boot into os download the system update and it should go through without any hiccups.
Let me know if you have any questions
Click to expand...
Click to collapse
Thanks. I kind of figured it out by following the thread about how to take the phone back to stock for OTAs, and used fastboot to flash the system.emmc.win file (wihtout modifying it.) After that, the phone wouldn't boot properly (probably because I didn't edit the filename,) so I flashed my system backup file. That made it so I could boot. I then flashed the stock recovery and it installed just fine.
Only really outlining what I did in case anyone else has the same issues- they can do what I did to get it up and running again.
kc6wke said:
If you are 100% stock update using the ota from stock recovery.
Download and read here
Click to expand...
Click to collapse
Thanks for sharing. I've tried this method on two different stock T-Mobile M9 phones, but both return an "E: Failed to map file" error message when selecting apply from phone storage.
Any suggestions?
nickmgray said:
Thanks for sharing. I've tried this method on two different stock T-Mobile M9 phones, but both return an "E: Failed to map file" error message when selecting apply from phone storage.
Any suggestions?
Click to expand...
Click to collapse
Are you placing the ota zip on internal or external sd?
It needs to be on the internal.
kc6wke said:
Are you placing the ota zip on internal or external sd?
It needs to be on the internal.
Click to expand...
Click to collapse
It's loaded to internal storage.
Hi everyone.
Here's my build of TWRP 3.0.3-0 for Huawei P7.
Features:
Supports USB OTG, so you can use USB flash drive as external storage for backups, zip installations.
Added feature to make backup/restore of internal storage.
Added feature to make backup/restore of oeminfo partition. This partition contains info about vendor and current installed version. So in case if you want to rollback to 4.4.2, for example, or revert back your previous vendor version, you can just restore oeminfo from backup with 4.4.2 version or other vendor and flash appropriate firmware without flashing transition package, vendor and without getting "cust fail" error.
Combined with stock EMUI 3.1 recovery. In case of power-on by holding power + vol+ or rebooting into recovery by command or any 3rd party application: will boot in TWRP. In case of local update, OTA-update, factory reset from menu or "force update" (3buttons method): will boot into EMUI recovery. Thus you don't have to flash stock recovery before OTA-update, flashing official firmware or doing factory rest.
Off-mode charger updated from EMUI 3.1 (for 4.4.2)
custom.bin and cust symlinks are saved/restored (if they were exist) in case of Wipe/Format Data. So there is not gonna be "cust" issues after factory reset in TWRP.
Excluded SuperSU from build.
Enabled encrypted data support.
Screen lock by power button replaced with screen off.
Requirements:
Unlocked bootloader
Android 4.4.2 - 5.1.1
Installation:
Reboot in fastboot mode
Flash image via fastboot
Code:
fastboot flash recovery TWRP_P7-3.0.3-0.img
fastboot reboot
From TWRP: Press "Install" and select zip-archive
Notes:
Because internal storage is not a separate block device and just a subfolder of "userdata" partition, before you can make backup/restore of internal storage, first you should do Mount -> Data.
Download: TWRP_P7-3.0.3-0.img
For TWRP: TWRP_P7-3.0.3-0.zip
Previous:
Download: TWRP_P7-3.0.2-0.img
For TWRP: TWRP_P7-3.0.2-0.zip
Download: TWRP_P7-3.0.0-0.img
For TWRP: TWRP_P7-3.0.0-0.zip
Thanks for supportion the P7 devices, greate job
Is it possible, to restore 2.8.7.0-backups?
pokko said:
Is it possible, to restore 2.8.7.0-backups?
Click to expand...
Click to collapse
I can't tell you for sure about backups made by araca's 2.8.7.0 - I don't know his partition layouts and backup naming method, but if you were using my build of 2.8.7.0, then yes, you can.
Anyway, it's better to make a new backup, for any case...
Thanks . works great on my p7 especially the factory reset with cust .
can you explain how i can build similar twrp for the mate S . your help will be much appreciated
Hi !
Whenever I use 3buttons method my phone goes to EMUI recovery ,
Whenever I use 3rd party application my phone goes to TWRP recovery !
There is no update file on my storage so in both cases my phone should go to TWRP recovery ! What is the problem ? Please solve this !
andromodgod said:
can you explain how i can build similar twrp for the mate S . your help will be much appreciated
Click to expand...
Click to collapse
What do you mean by similar?
You'll have to make device tree to build TWRP. Mate S is much different from P7, so I think I couldn't help you with it.
mohammadsaa said:
Hi !
Whenever I use 3buttons method my phone goes to EMUI recovery ,
Whenever I use 3rd party application my phone goes to TWRP recovery !
There is no update file on my storage so in both cases my phone should go to TWRP recovery ! What is the problem ? Please solve this !
Click to expand...
Click to collapse
There is not any problem. 3 buttons method is used for "force update". If you want to boot into TWRP, use "power" + "vol+" instead of 3 buttons. Read the first post attentively!
@Kostyan_nsk_one question, why if internal storage is a subfolder of user data in recovery the size of internal storage partition is bigger of data partition?
complicazio said:
@Kostyan_nsk_one question, why if internal storage is a subfolder of user data in recovery the size of internal storage partition is bigger of data partition?
Click to expand...
Click to collapse
TWRP excludes /data/share folder from backup of /data folder. Thus, if you have a lot of photos, music, etc in your internal storage, its backup size will be greater than size of /data backup.
Kostyan_nsk said:
TWRP excludes /data/share folder from backup of /data folder. Thus, if you have a lot of photos, music, etc in your internal storage, its backup size will be greater than size of /data backup.
Click to expand...
Click to collapse
Well, thus if I want to do a nandroid backup I have to check data and internal storage, not only data partition because of default it's not selected internal memory
complicazio said:
Well, thus if I want to do a nandroid backup I have to check data and internal storage, not only data partition because of default it's not selected internal memory
Click to expand...
Click to collapse
It's not mandatoryly for nandroid backup. Depends on what kind of data you want to save. /data contains user applications and system settings; /data/share (i.e. internal storage) contains your personal data (screenshots, photos, music, videos, etc) if you didn't moved them to sd-card. It's up to you, what to backup and what not.
@Kostyan_nsk I appreciate your work. I have already built TWRP for my Huawei device but I am struggling to fix custom.bin and /data/cust symlink being destroyed after factory reset. I have placed the necessary code in partitions.cpp under Wipe partition block. Can you tell me which method you used to fix this?
@Kostyan_nsk When I do a backup in the internal memory then via es file Explorer goes into TWRP folder in sdcard0 (internal memory) it is empty, and if I go into the folder media / share / 0 / TWRP I find the backup. They are not the same thing? While if I do backup in the external sdcard its all ok.
Sent from my Paris using XDA-Developers mobile app
Hi,, I am new here ... i think this very nice .. do you tell me how is instal for my phone p7?
albelushi7 said:
Hi,, I am new here ... i think this very nice .. do you tell me how is instal for my phone p7?
Click to expand...
Click to collapse
Read first post
RangerP7 said:
Read first post
Click to expand...
Click to collapse
What is the first post?
I mean instal twrp!!
How?
If you mean Buckup I do this ?!!
I'm new don't forget this hhh
Think you
albelushi7 said:
What is the first post?
I mean instal twrp!!
How?
If you mean Buckup I do this ?!!
I'm new don't forget this hhh
Think you
Click to expand...
Click to collapse
First post on first page
Kostyan_nsk said:
Hi everyone.
Here's my build of TWRP 3.0.0-0 for Huawei P7.
Features:
Supports USB OTG, so you can use USB flash drive as external storage for backups, zip installations.
Added feature to make backup/restore of internal storage.
Added feature to make backup/restore of oeminfo partition. This partition contains info about vendor and current installed version. So in case if you want to rollback to 4.4.2, for example, or revert back your previous vendor version, you can just restore oeminfo from backup with 4.4.2 version or other vendor and flash appropriate firmware without flashing transition package, vendor and without getting "cust fail" error.
Combined with stock EMUI 3.1 recovery. In case of power-on by holding power + vol+ or rebooting into recovery by command or any 3rd party application: will boot in TWRP. In case of local update, OTA-update, factory reset from menu or "force update" (3buttons method): will boot into EMUI recovery. Thus you don't have to flash stock recovery before OTA-update, flashing official firmware or doing factory rest.
Off-mode charger updated from EMUI 3.1 (for 4.4.2)
custom.bin and cust symlinks are saved/restored (if they were exist) in case of Wipe/Format Data. So there is not gonna be "cust" issues after factory reset in TWRP.
Excluded SuperSU from build.
Enabled encrypted data support.
Screen lock by power button replaced with screen off.
Requirements:
Unlocked bootloader
Android 4.4.2 - 5.1.1
Installation:
Reboot in fastboot mode
Flash image via fastboot
Code:
fastboot flash recovery TWRP_P7-3.0.0-0.img
fastboot reboot
From TWRP: Press "Install" and select zip-archive
Known issues:
Because internal storage is not a separate block device and just a subfolder of "userdata" partition, before you can make backup/restore of internal storage, first you should do Mount -> Data. Otherwise you will get error, saying that TWRP can't mount "storage". So don't bother if you'll see this error.
Download: TWRP_P7-3.0.0-0.img
For TWRP: TWRP_P7-3.0.0-0.zip
Click to expand...
Click to collapse
Download ADB/FASTBOOT
Download TWRP_P7-3.0.0-0.img
And put it into the ADB / FASTBOOT folder
Install drivers of your phone
Connect your phone to your computer
Enable USB debugging on your phone
Open ADB and type:
"adb devices" (you should see now your device)
"adb reboot bootloader"
Now you should see at the bottom unlocked or locked. That means if your bootloader is unlocked. You need to unlock your bootloader to install a custom recovery.
If you see unlocked...
"fastboot flash recovery TWRP_P7-3.0.0-0.img"
That's it
Reboot your phone.
RangerP7 said:
First post on first page
Download ADB/FASTBOOT
Download TWRP_P7-3.0.0-0.img
And put it into the ADB / FASTBOOT folder
Install drivers of your phone
Connect your phone to your computer
Enable USB debugging on your phone
Open ADB and type:
"adb devices" (you should see now your device)
"adb reboot bootloader"
Now you should see at the bottom unlocked or locked. That means if your bootloader is unlocked. You need to unlock your bootloader to install a custom recovery.
If you see unlocked...
"fastboot flash recovery TWRP_P7-3.0.0-0.img"
That's it
Reboot your phone.
Click to expand...
Click to collapse
There are some nots ==
Where is ADB or link ADB/Fastboot
Where is folder Fastboot
albelushi7 said:
There are some nots ==
Where is ADB or link ADB/Fastboot
Where is folder Fastboot
Click to expand...
Click to collapse
Use the power of Google, maybe the force will be with you and you will find it
And please! inform you about flashing things on your phone. First learn how it work (your phone, bootloader, recovery, system, adb/fastboot) and after that start work...
If you are just flashing random **** on your phone without knowing what your are doing I will promise you, in less then one week you will ask for help because your phone won't start anymore...
RangerP7 said:
Use the power of Google, maybe the force will be with you and you will find it
And please! inform you about flashing things on your phone. First learn how it work (your phone, bootloader, recovery, system, adb/fastboot) and after that start work...
If you are just flashing random **** on your phone without knowing what your are doing I will promise you, in less then one week you will ask for help because your phone won't start anymore...
Click to expand...
Click to collapse
I know that
But This new for me ?
I want install this twerb ,because I think phone be better..
Just Try ?
Think you ?
After unlocking the bootloader, installing TWRP recovery and rooting my phone with SuperSU (v2.82), I was preparing to install a custom ROM (more specifically the Resurrection Remix 7.1.2.) all in all, things ended up going out of hand and I accidentally deleted my internal storage, losing every single bit of my existing ROM, not to mention the RR ROM file as well. Now when I try to wipe, I can't, it usually says "Failed to mount '/data' (Device or resource busy) and "Unable to mount storage".
I tried using ADB sideload but to no success, only the same message. What I can understand is that the previous data is gone, I tried changing the format of data, system and cache to FAT & exFAT but it still did not resolve my issue.
I'm out of options here, I don't want to have to give up this phone because of my stupidity.
I also tried flashing the LineageOS 14.1 ROM to see if anything was different, here is what it said:
Installing zip file '/sideload.package.zip'
Target: HUAWEI/EVA-L09/HWEVA:7.0/HUAWEIEVA-L09/C432B361:user/release-keys
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
detected filesystem exfat for /dev/block/bootdevice/by-name/userdata
mount: failed to mount /dev/block/bootdevice/by-name/userdata at /data: Device or resource busy
unmount of /data failed; no such volume
Patching system image unconditionally...
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Script succeeded: result was [1.000000]
Although it said succeeded it clearly did not work and I am sitting without a ROM. I'm not smart when it comes to these things please help a guy out.
(Is there a way to going back to completely stock EMUI 5.0?)
Cheers.
EMUI 5.01 requires encryption, which you obviously removed.
Search for DC Unlocker, it can probably fix it for 25 Euros
zgfg said:
EMUI 5.01 requires encryption, which you obviously removed.
Search for DC Unlocker, it can probably fix it for 25 Euros
Click to expand...
Click to collapse
I know this is awkward to ask and all, but how exactly do I go about this, I'm pretty lost and I have minimal experience with this stuff..
I never had to use it but here is their portal (with download info, prices, instructions, etc)
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
If you search on XDA or search on Google for eg XDA Huawei DC Unlocker you will find threads with first hands experience (I've seen them several tines but didn't save to Favorites)
zgfg said:
I never had to use it but here is their portal (with download info, prices, instructions, etc)
If you search on XDA or search on Google for eg XDA Huawei DC Unlocker you will find threads with first hands experience (I've seen them several tines but didn't save to Favorites)
Click to expand...
Click to collapse
I'm terribly sorry for being THIS stupid. As I'm looking into this even more, I'm conflicted about the credit amount I need, been scrolling through the list and I can't really find my problem involving firmware I suppose.
People usually buy for 15 Euros. It may help you, Chrome will automatically translate from German
https://www.android-hilfe.de/forum/...-wiederherstellung-mit-dc-phoenix.818669.html
I'm not educated about DC Unlocker but that is NOT neccesary here. You can easily repair the /data partition by flashing the stock recovery via fastboot, formatting data with that stock recovery and then flashing TWRP again. After that TWRP should be able to read the data partition again.
You can easily go back to stock completely and even restore your bootloader by doing a "rollback" to Android 6. (dload method). After that you can normally upgrade from there though EMUI to the latest version of stock.
christopherpfister said:
I'm not educated about DC Unlocker but that is NOT neccesary here. You can easily repair the /data partition by flashing the stock recovery via fastboot, formatting data with that stock recovery and then flashing TWRP again. After that TWRP should be able to read the data partition again.
You can easily go back to stock completely and even restore your bootloader by doing a "rollback" to Android 6. (dload method). After that you can normally upgrade from there though EMUI to the latest version of stock.
Click to expand...
Click to collapse
I've tried using eRecovery to format the data but to no success, I can't even use the touch screen for some reason, (I know about the volume keys, but when it comes to selecting the Wi-Fi, there is no success whatsoever). If you do know a fix for this, could you possibly walk me through this?
Hexagonal said:
I've tried using eRecovery to format the data but to no success, I can't even use the touch screen for some reason, (I know about the volume keys, but when it comes to selecting the Wi-Fi, there is no success whatsoever). If you do know a fix for this, could you possibly walk me through this?
Click to expand...
Click to collapse
UPDATE: I flashed the stock recovery image and it showed me the wipe cache partition and factory data and system reset, I tried both, only the cache one succeeded, the other one failed. I saw a post that directed you to flash boot.img, recovery.img, recovery2.img and then system.img, I did that, but I couldn't boot into my phone - the good thing is however! That I can use my touchscreen in the recovery now.
Obviously the second time booting into EMUI recovery it prompts me to 'Download latest version and recovery', I try to connect to my Wi-Fi, seems okay but then it suddenly fails. More specifically it says 'Getting package info failed'. Save me please :crying:
So this "erecovery" never worked in any way for me (the one which offers you to download the latest version).
Instead you need the normal recovery you already used. Formatting failed for me the first time too, try it again and then it will try to format "low-level" which worked for me.
Go directly into fastboot from that, flash TWRP and go directly into TWRP.
After that should be able to use /data in TWRP. As soon as you are able to start TWRP without any error messages (like "Device busy" or something) go to Wipe and then format data.
Important: check which partition type you have! For EMUI you need "f2fs" and for lineage you need "ext4". You can see and change that in TWRP under Wipe -> "change or repair filesystem".
If you have any more questions, just ask.
christopherpfister said:
So this "erecovery" never worked in any way for me (the one which offers you to download the latest version).
Instead you need the normal recovery you already used. Formatting failed for me the first time too, try it again and then it will try to format "low-level" which worked for me.
Go directly into fastboot from that, flash TWRP and go directly into TWRP.
After that should be able to use /data in TWRP. As soon as you are able to start TWRP without any error messages (like "Device busy" or something) go to Wipe and then format data.
Important: check which partition type you have! For EMUI you need "f2fs" and for lineage you need "ext4". You can see and change that in TWRP under Wipe -> "change or repair filesystem".
If you have any more questions, just ask.
Click to expand...
Click to collapse
So what you're saying is, as soon as I get my data sorted and my partition set to the right one I should be able to install the custom ROM. I could use data and even formatted it, tried installing Lineage but I must've had the storage on the wrong type, now I'm back with the same issue, I'll try to fix it and post my results here. Thank you!
Hexagonal said:
So what you're saying is, as soon as I get my data sorted and my partition set to the right one I should be able to install the custom ROM. I could use data and even formatted it, tried installing Lineage but I must've had the storage on the wrong type, now I'm back with the same issue, I'll try to fix it and post my results here. Thank you!
Click to expand...
Click to collapse
Update: It did NOT work, tried flashing LineageOS through ADB sideload, it was going fine before the bar completely filled up around 50% of the way done, it said 'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Help me, I'm begging you, at the moment I don't have an access to a microSD that has the capacity to hold the stock files to do the dload method, therefore this is my only hope.
Hexagonal said:
Update: It did NOT work, tried flashing LineageOS through ADB sideload, it was going fine before the bar completely filled up around 50% of the way done, it said 'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Help me, I'm begging you, at the moment I don't have an access to a microSD that has the capacity to hold the stock files to do the dload method, therefore this is my only hope.
Click to expand...
Click to collapse
Whats the error? Why doesn't it work? What happens when you try to boot?
christopherpfister said:
Whats the error? Why doesn't it work? What happens when you try to boot?
Click to expand...
Click to collapse
That's what I'm trying to figure out, when I try to boot in it's just stuck on a boot loop. Unfortunate..
Remember that you have to what *a while* for the first boot. Only if you see no change after 5-8 minutes or so something is definitely wrong.
Have you checked in TWRP if your /data partition is ext4?
christopherpfister said:
Whats the error? Why doesn't it work? What happens when you try to boot?
Click to expand...
Click to collapse
christopherpfister said:
Remember that you have to what *a while* for the first boot. Only if you see no change after 5-8 minutes or so something is definitely wrong.
Have you checked in TWRP if your /data partition is ext4?
Click to expand...
Click to collapse
I know, but it was flashing the Huawei logo and the unlocked bootloader warning continuously. It was set on EXT4 but as I was saying, it said script succeeded at 50%.
Hexagonal said:
'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Click to expand...
Click to collapse
That just said that /system partition is ext4. That is default even for stock I believe. You need to check for /data.
christopherpfister said:
That just said that /system partition is ext4. That is default even for stock I believe. You need to check for /data.
Click to expand...
Click to collapse
I deliberately set the data partition to EXT4 before installing
Hexagonal said:
I deliberately set the data partition to EXT4 before installing
Click to expand...
Click to collapse
Can you check in TWRP if it actually says /data is ext4?
Which lineage are you trying to install? Don't you need a vendor.zip for some of them?
/data is indeed on EXT4, and I was installing the one that was on the room section.
I have installed TWRP, in recovery when im trying to install dm_verity file i'm getting error - "unable to find boot block location". can someone help how to flash it
VineelKumar said:
I have installed TWRP, in recovery when im trying to install dm_verity file i'm getting error - "unable to find boot block location". can someone help how to flash it
Click to expand...
Click to collapse
You have to format data using the type "yes" to continue method. Then use twrp's menus to reboot back into recovery. Mount /system and /vendor in twrp then flash it. If you still have a problem, then try the 5/21/19 release of the disabler.
@Spaceminer No, that's nonsense! Data is mounted correctly and is fully unencrypted. See screenshot where you can read "Updating partition details... done" There's NO error message.
That's the first thing...
Second, there's no need to mount sth manually, the script itself will do this if necessary!
@VineelKumar Download the dm-verity-disabler.zip by Zackptg5 from
https://zackptg5.com/android.php#disverfe
This will work with your device.
WoKoschekk said:
@Spaceminer No, that's nonsense! Data is mounted correctly and is fully unencrypted. See screenshot where you can read "Updating partition details... done" There's NO error message.
That's the first thing...
Second, there's no need to mount sth manually, the script itself will do this if necessary!
@VineelKumar Download the dm-verity-disabler.zip by Zackptg5 from
https://zackptg5.com/android.php#disverfe
This will work with your device.
Click to expand...
Click to collapse
It doesn't show data as mounted. It shows the external sdcard as being mounted. And there is an error, twrp is giving error 1, and the disabler is also showing an error saying it can't find the boot block location. This means twrp isn't able to modify block devices or mount them properly. What I told him to do will fix the problem. The script doesn't mount anything correctly if twrp is not able to run the script... I know what I'm talking about. I wouldn't steer the guy wrong.
Edit: I'm definitely correct. What I said is actually mentioned in the official twrp thread for this device. It says; "If you format data (Not just factory reset) after decrypting you must reboot into recovery and format again." - direct quote from the instructions, under notes.
I flashed the same .zip with /data, /system and /vendor mounted properly and ran into the same error... (see screenshot)
To mount a device block it's not neccessary to have /data mounted.
The .zip is incompatible with Moto g6 - that's all!
WoKoschekk said:
@Spaceminer No, that's nonsense! Data is mounted correctly and is fully unencrypted. See screenshot where you can read "Updating partition details... done" There's NO error message.
That's the first thing...
Second, there's no need to mount sth manually, the script itself will do this if necessary!
@VineelKumar Download the dm-verity-disabler.zip by Zackptg5 from
https://zackptg5.com/android.php#disverfe
This will work with your device.
Click to expand...
Click to collapse
Thanks it worked fine. But for some reason the mobile was struck in boot loop(just warning message on screen saying, you have unlocked bootloader for couple of seconds and then same thing appears again), any idea how to fix it ?
VineelKumar said:
...any idea how to fix it ?
Click to expand...
Click to collapse
Yes, do it manually. The disabler.zip does two things on your device.
1.) remove dm-verity
2.) disable forceencryption of /data
The magisk.zip also removes dm-verity within the installation process. So you don't need the disabler.zip for this.
To remove forceencryption you have to follow a few simple steps which are given in my instruction below:
preparation:
You have to be on the latest stock firmware with TWRP installed and nothing else.
Boot into TWRP and format /data (do not wipe it! you must use format). Then reboot directly into TWRP!!
Now let's start to remove forceencryption.
1.) place the attached .tar.gz file in your internal storage (/sdcard)
2.) mount /vendor in the options menu and open TWRP's terminal command under advanced settings
3.) type in (or copy it from here)
Code:
tar -xvzf /sdcard/fstab.tar.gz
4.) at next boot your device will be unencrypted
Now don't reboot your device and stay in TWRP to install the magisk.zip v19.3!! That's important to flash v19.3 instead of the latest v20.3 otherwise it causes a bootloop!! I don't know why it does but you can later update Magisk without any problems through the Magisk Manager.
Magisk will now remove the dm-verity during the installation process. That's a part of the installation script of Magisk.
When the installation of Magisk has finished you can boot your device into system. Maybe it reboots one time but don't care. Also the bootanimation will take some time due to unencryption of /data. That's quite normal.
WoKoschekk said:
Yes, do it manually. The disabler.zip does two things on your device.
1.) remove dm-verity
2.) disable forceencryption of /data
...
the installation of Magisk has finished you can boot your device into system. Maybe it reboots one time but don't care. Also the bootanimation will take some time due to unencryption of /data. That's quite normal.
Click to expand...
Click to collapse
I appreciate your patience, WoKoschekk. I for one appreciate the guide and insight into the reason root must be achieved this way. I was using 20.3 and 18 the whole time. I was successful with your instructions the first time. It became stuck on boot after the initia reboot, so I pushed fstab and magisk again and it was fine. I remember that on one phone, encryption wasn't a problem if you had your pin or password. Could it be the same here provided there was no fingerprint assigned (might be the original pixel)? I'm guessing this TWRP can't decrypt? Just curious, because N/A balogna.
I'm glad to hear that!
TWRP for Moto g6 can't decrypt your data. That's the reason why you must disable forceencryption to use TWRP.
WoKoschekk said:
Code:
tar -xvzf /sdcard/fstab.tar.gz
Click to expand...
Click to collapse
I don't have a SD card, so I put the file into the TWRP folder. I then used,
Code:
tar -xvzf data/media/TWRP/fstab.tar.gz
Was that the right location?
/data/media/0 = /sdcard
/external_sd = external SD in SD-card slot
WoKoschekk said:
/data/media/0 = /sdcard
/external_sd = external SD in SD-card slot
Click to expand...
Click to collapse
Ok, I see now. Anyway all updated and rooted with your instructions, thanks.