Hi guys. I have a problem with my ze500KL. I can install only the twrp 2.8.7.7 version. But when i try to install img or zip of roms /original firmware, the twrp fails the operation , saying " error data", "unable to mount"... i have problems with wipe too. any solution?
nik91thebest said:
Hi guys. I have a problem with my ze500KL. I can install only the twrp 2.8.7.7 version. But when i try to install img or zip of roms /original firmware, the twrp fails the operation , saying " error data", "unable to mount"... i have problems with wipe too. any solution?
Click to expand...
Click to collapse
I can't understand what you mean. If you want to install stock rom from TWRP recovery, you have to modify updater-skript.
Why do you can install only the twrp recovery 2.8.7.7, when we have the twrp recovery 3.0.0.2
File img you can flash from fastboot mode. Commands:
fastboot flash system file.img
fastboot flash recovery file.img
fastboot flash boot file.img
or
fastboot boot file.img for example twrp recovery img or stock recovery img. This is command for once booting.
I want to return to original firmware , i download it from the site of asus. So, i booted twrp in fastboot mode (i tried different version of twrp, but the only that starts is the 2.8.7.7 version) using adb.
Now i am in recovery with twrp 2.8.7.7. I can push using .zip files or img files on internal storage.
But i have different problems with this recovery:
IF i use wipe function: error opening sys, could not mount, enabe to mount, ... (failed)
If i install rom or firmware with zip files: error unable to mount, unable to find partition for path.... (failed)
Adb sideload goes failed too.
What should i do???
I think that the problem is in the internal partition... I have to install using a min usb ext storage? or what????? thanks :fingers-crossed:
nik91thebest said:
I want to return to original firmware , i download it from the site of asus. So, i booted twrp in fastboot mode (i tried different version of twrp, but the only that starts is the 2.8.7.7 version) using adb.
Now i am in recovery with twrp 2.8.7.7. I can push using .zip files or img files on internal storage.
But i have different problems with this recovery:
IF i use wipe function: error opening sys, could not mount, enabe to mount, ... (failed)
If i install rom or firmware with zip files: error unable to mount, unable to find partition for path.... (failed)
Adb sideload goes failed too.
What should i do???
I think that the problem is in the internal partition... I have to install using a min usb ext storage? or what????? thanks :fingers-crossed:
Click to expand...
Click to collapse
Easiest way to fix your phone is flash stock rom from stock recovery. Stock rom put to sd card. Reboot to stock recovery and choose flash rom from sd card. New version number system must be the same or higher than installed in the phone.
Do you want to return to the lower version of Android.
http://forum.xda-developers.com/zenfone-2-laser/general/guide-downgrade-zenfone-2-laser-to-t3382172
Do you want to flash stock rom from twrp recovery.
http://forum.xda-developers.com/zen...uide-how-to-flash-stock-rom-via-twrp-t3409768
Muminek111 said:
Easiest way to fix your phone is flash stock rom from stock recovery. Stock rom put to sd card. Reboot to stock recovery and choose flash rom from sd card. New version number system must be the same or higher than installed in the phone.
Do you want to return to the lower version of Android.
http://forum.xda-developers.com/zenfone-2-laser/general/guide-downgrade-zenfone-2-laser-to-t3382172
Do you want to flash stock rom from twrp recovery.
http://forum.xda-developers.com/zen...uide-how-to-flash-stock-rom-via-twrp-t3409768
Click to expand...
Click to collapse
Stock recovery doesn't work man. The only recovery that works is the twrp 2.8.7.7. But it has problems.
nik91thebest said:
Stock recovery doesn't work man. The only recovery that works is the twrp 2.8.7.7. But it has problems.
Click to expand...
Click to collapse
Do you have Lollipop or Marshmallow and what is your version number.
For Marshmallow you need to this working twrp recovery.
https://drive.google.com/file/d/0B7F3ZXr565GkY28yUjhfRkd5MUk/view?usp=drivesdk
For Lollipop you need to this working twrp recovery.
https://drive.google.com/file/d/0B7F3ZXr565GkY1NQbUtoVzdwWEU/view?usp=drivesdk
If you haven't installed stock recovery, it's not no problem. You can it flash from fastboot mode.
i had mawshmallow. i tried but failed...
nik91thebest said:
i had mawshmallow. i tried but failed...
Click to expand...
Click to collapse
How did you flash the file twrp.img.
OK guys I've solved the problem. I moved in this way:
1) Volume up + power to go in fastboot mode
2) after installing adb and the other drivers, i've insered these commands:
fastboot erase cache
fastboot erase userdata
fastboot erase system
3) after downloading twrp version 3.0.0 (for the zenfone 2 laser), I load it using the command "fastboot boot (name file twrp).zip"
4) the recovery starts automatically. Now i downloaded the file "back2stock.zip" and the original firmware (WW, worldwide) form the official site of the Asus
5) this passage is the most important:using 7zip I've extracted the file zip of the firmware and the backtostock, then i created a new file using 7zip : in this new zip i've loaded the files inside back2stock and the files file_contentexts, system.new.dat, system.patch.dat, boot.img e system.trasfer.list inside the zip of the official firmware
6) I've loaded this new file on the phone using the command "adb push (new file name).zip /"
7) at last i have installed this file on the phone ENJOY it
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections, ligma,
* thermonuclear war, or your mom getting upset with you for being on the computer all day
Please
* Ensure you have an advanced understanding of this device before flashing it! YOU are choosing to make these modifications or your own free will.
*/
THIS GUIDE APPLIES TO JETER AND ALJETER DEVICES
FOR ALJETER DEVICE OWNERS ONLY.
there are ALOT of different variants of the aljeter so please before beginning this root method go to settings, system, about phone. look for either sw version or software channel verison and either remember what it says or write it down. me or anyone else will need this to help troubleshoot which aljeter variant you have. this will also be important to know incase you mess up and need to reflash stock firmware which those instructions are at the bottom of this guide.
The following devices have been confirmed to work on devices with Android 8 (Oreo)
XT1922-4 Model
XT1922-5 Brazilian Model
XT1922-7 Boost Mobile/ Virgin Mobile
XT1922-9 Motorola Retail
The following devices have been confirmed to work with Android 9 (pie)
XT1922-7 (Jeter) boost Mobile/ Virgin Mobile.
XT1922-3 (Aljeter)
XT1922-5 (Aljeter retbr)
Please make backups using TWRP IN CASE OF FAILURE.
Original stock firmware FOR JETER can be found here. https://mirrors.lolinet.com/firmware/moto/jeter/official/ and here FOR ALJETER https://mirrors.lolinet.com/firmware/moto/aljeter/official/
The steps listed in this process WILL wipe your userdata. If you have anything you need to save back it up first.
Prerequisite:
Unlocked bootloader.
FOR LINUX USERS. If you're using a linux distro then congrats this is all you should have to run. open command prompt and run this. "sudo apt-get install adb" without quotation marks. then follow Motorolas bootloader guide in provided link. continue to step 1 after.
FOR WINDOWS USERS.
ADB/Fastboot installed on your machine ( https://developer.android.com/studio...platform-tools ) If you have issues with commands make sure you have a current build of ADB and fastboot.
Minimal adb/fastboot v1.4.3 installer can be found here. https://androidfilehost.com/?fid=746010030569952951
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a
DECRYPTION AND BACKUP.
NOTICE
IF YOU YOU ARE USING THE 32GB MODEL OR THE 16GB MODEL AND ARE ON ANDROID 9 (PIE) PLEASE USE THE ANDROID 9 (PIE) MODEL TWRP. USERS WITH THE 16GB MODEL AND THE 32GB MODEL ON ANDROID 8 (OREO) WILL STILL NEED TO USE SEPERATE TWRPS
MAKE SURE TO SWIPE RIGHT IN TWRP TO ALLOW SYSTEM MODIFICATIONS.
Step 1.) Download and extract twrp image to the ADB/Fastboot folder on your computer.
FOR ANDROID 8 (OREO)
16gb model twrp: https://www.androidfilehost.com/?fid=6006931924117921836
32gb model twrp: https://www.androidfilehost.com/?fid=6006931924117927211
FOR ANDROID 9 (PIE)
https://www.androidfilehost.com/?fid=6006931924117921849
Step 2.) Reboot to your bootloader. You can do this by turning on your device and holding the power button and volume down button at the same time.
Step 3.) Once the device reboots to the bootloader type the following from your computer with your phone connected via USB.
Code:
fastboot boot twrp.img
Step 4.) Once TWRP boots from your computer type (it may take a bit to boot because it is trying to decrypt your userdata, but it will fail and prompt for a password. Just click cancel)
Step 5.) time to backup your stock recovery and stock boot. use these commands one at a time.
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/recovery stockrecovery.img
This will backup your stock boot and recovery images if you need to revert to stock later.
Step 6.) time to decrypt which will also format your data so make sure to make a backup. while still booted in twrp touch the "wipe" button then touch "format data", type yes and after its all done reboot to bootloader use this command.
Code:
adb reboot bootloader
CONGRATS! if you read this correctly and or didnt skim then you have successfully decrypted your device and backed up your stock recovery and stock boot.img. proceed below for root process.
ROOT PROCESS.
Step 1.) Run the following command from your computer to install the TWRP image to your device.
Code:
fastboot flash recovery twrp.img
Step 2.) Use the volume keys on the device to select boot to recovery and TWRP will boot up again. swipe right to allow modifications. IT SHOULD NOT ASK YOU FOR A PASSWORD THIS TIME IF IT DOES YOU MESSED UP DURING THE DECRYPT PROCESS
Step 3.) Follow this link to the creators site to download the disabler zip. https://zackptg5.com/android.php#disverfe download it to your ADB/Fastboot folder.
Step 4.) Download the Magisk Beta v20.0 and or the latest zip file from https://github.com/topjohnwu/Magisk/releases to your ADB/Fastboot folder. (I personally use beta so I use beta in this guide but you don't have to)
Step 5.) Run the following command to push the dm_verity force encrypt disabler and magisk zip to your device
Code:
adb push Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip /tmp
adb push Magisk-v20.0.zip /tmp
This will push the Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip and Magisk-v20.0.zip to your /tmp folder
Step 6.) Flash Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip from TWRP using the install option and navigate to the /tmp folder to select it and install it.
Step 7.) Flash Magisk-v20.0.zip from TWRP using the install option and navigate to the /tmp folder to select it and install it.
Step 8.) Reboot your device
Step 9.) Just wait for the device to boot up. might take a bit and it might seem its in a bootloop but if you followed this guide exactly as is just wait it out it took about 5-10 minutes before i got to the "lets get started" screen after updating to pie (android 9)
Step 10.) Verify Magisk Manager is installed and the root functionality works. sometimes the manager apk wont be installed so download the magisk manager apk from the provide links. click advanced to see if the boxes are unchecked. (2022 edit) If you see magisk app and magisk needs updated you can do it but I can't confirm if it's safe and what works and doesnt after
CONGRATS! IF YOU DIDNT SKIM MY GUIDE YOU SHOULD HAVE A SUCCESSFULLY ROOTED AND ENCRYPTION DISABLED DEVICE, HAVE FUN.
IF YOU MESSED UP, DIDNT PUT A COMMAND IN CORRECTLY, SKIMMED, OR ARE INA GENUINE BOOTLOOP/BRICK THIS SECTION IS FOR YOU
Step 1.) DOWNLOAD STOCK FIRMWARE HERE FOR JETER AND CERTAIN ALJETER DEVICES (from what i can tell usa variant aljeter devices are consided jeter) https://mirrors.lolinet.com/firmware/moto/jeter/official/ IF YOU REMEMBER OR WROTE DOWN YOUR SW CHANNEL VERSION THEN DOWNLOAD STOCK FIRMWARE FOR BASICALLY EVERY OTHER ALJETER DEVICE HERE. https://mirrors.lolinet.com/firmware/moto/aljeter/official/ UNZIP STOCK FIRMWARE TO YOUR ADB/FASTBOOT FOLDER TO FLASH IT. TO REVERT BACK TO STOCK YOU HAVE TO REFLASH STOCK FIRMWARE FROM THE BOOTLOADER if your device is bootlooped or bricked or not working right you have to reflash the stock firmware your device came with. PLEASE INPUT THESE COMMANDS ONE AT A TIME DO NOT DO THEM ALL AT ONCE. I KNOW ITS A HASSLE BUT IT GUARANTEES A SUCCESSFUL REFLASH. I CANNOT EMPHASIZE THIS ENOUGH
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastbot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot erase userdata
fastboot erase DDR
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot
Credits: @kwiksi1ver for making the original guide. @topjohnwu for magisk. @shimp208 for minimal adb/fastboot. @Spaceminer for providing the new twrps for 16gb and 32 gb devices, and @Zackptg5 for making the Universal DM-Verity, ForceEncrypt, Disk Quota Disablers.
QUICK NOTE/EDIT: SINCE I DO NOT OWN THIS DEVICE ANYMORE I CANNOT CONFIRM IT BUT YOU SHOULD BE ABLE TO UPDATE TO THE LATEST MAGISK 24.3 FROM THE MAGISK APP AFTER YOU INSTALL V20, AGAIN I AM NOT ABLE CONFIRM IF IT WORKS, CAUSES BOOTLOOPS, OR ANYTHING SO KEEP THAT IN MIND, but hopefully it does work for yall I've also updated the ADB commands for the disabler to reflect its latest version and I've updated the magisk link to topjohnwus GitHub as that's where all updates happen/ go first
RESERVED
In order to update the confirmed working models for this guide, if anyone that has this device with a unlocked bootloader and does root and decrypt successfully using my guide and it's not on the confirmed device list. PLEASE JUST PM ME and let me know. Please include device model number, name, and if on aljeter your software channel version.( For example. Xt1922-5 aljeter, sw channel: retbr)
following the instructions exactly gets me into a really weird bootloop where my phone boots twrp, shows some log and then reboots and does the same thing over and over
blowingoff said:
following the instructions exactly gets me into a really weird bootloop where my phone boots twrp, shows some log and then reboots and does the same thing over and over
Click to expand...
Click to collapse
I have the same issue. I used the recovery steps to go back to stock but every time i re-attempt to root/install twrp the bootloop comes back:
Also, it's failing to mount /data after Resurrection Remix wouldn't boot and it keeps giving me the unable to mount /data (invalid argument) problem. I need help badly. Can you help? Is it the TWRP's fault?
Kuntitled said:
I have the same issue. I used the recovery steps to go back to stock but every time i re-attempt to root/install twrp the bootloop comes back:
Also, it's failing to mount /data after Resurrection Remix wouldn't boot and it keeps giving me the unable to mount /data (invalid argument) problem. I need help badly. Can you help? Is it the TWRP's fault?
Click to expand...
Click to collapse
Are you encrypted? Because twrp will do that if you are. You have to use the wipe > format > type "yes" to continue method to remove encryption. Then reboot from twrp, directly back into twrp. Then it can mount /data properly, at which point you need to flash the encryption disabler. If you don't disable encryption you'll keep running into the same problem. You only have to do that once. After that you can use the regular wipe option. If you ever flash the stock vendor.img you'll need to do it again.
Also, please make sure twrp has been flashed to recovery. I don't think it'll work if you just boot through fastboot. If you followed all these instructions and magisk still refuses to install, or gives you a bootloop, then it's a ROM problem and not TWRP. Should that happen, let me know and I'll flash Resurrection remix and see if I can figure out what's going on. I've had ROMs refuse to be rooted before. Descendant ROM had this problem on some older builds.
Spaceminer said:
Are you encrypted? Because twrp will do that if you are. You have to use the wipe > format > type "yes" to continue method to remove encryption. Then reboot from twrp, directly back into twrp. Then it can mount /data properly, at which point you need to flash the encryption disabler. If you don't disable encryption you'll keep running into the same problem. You only have to do that once. After that you can use the regular wipe option. If you ever flash the stock vendor.img you'll need to do it again.
Also, please make sure twrp has been flashed to recovery. I don't think it'll work if you just boot through fastboot. If you followed all these instructions and magisk still refuses to install, or gives you a bootloop, then it's a ROM problem and not TWRP. Should that happen, let me know and I'll flash Resurrection remix and see if I can figure out what's going on. I've had ROMs refuse to be rooted before. Descendant ROM had this problem on some older builds.
Click to expand...
Click to collapse
as for me: I followed the instructions which tell us to only boot twrp during the data format and only then actually flash twrp.
but my problem is no magisk, as I always root my phone whenever i revert back to stock. it's just that decryption is not working on my xt1922-5
blowingoff said:
as for me: I followed the instructions which tell us to only boot twrp during the data format and only then actually flash twrp.
but my problem is no magisk, as I always root my phone whenever i revert back to stock. it's just that decryption is not working on my xt1922-5
Click to expand...
Click to collapse
Do it like this.
1. fastboot flash recovery twrp.img
2. Use the volume keys while still in fastboot to select "recovery" then hit the power button.
3. Hit cancel at the decryption screen when twrp boots up.
4. In TWRP select wipe > format > type "yes" to continue. Do not reboot the phone yet.
5. In twrp select reboot > recovery.
6. Once twrp boots up again, select mount and check the boxes for /data, /system, /vendor, /cache.
7. Now flash the universal encryption disabler.
8. Let it boot once, then go back into recovery and flash Magisk.
This should solve your problem.
Spaceminer said:
Do it like this.
1. fastboot flash recovery twrp.img
2. Use the volume keys while still in fastboot to select "recovery" then hit the power button.
3. Hit cancel at the decryption screen when twrp boots up.
4. In TWRP select wipe > format > type "yes"no to continue. Do not reboot the phone yet.
5. In twrp select reboot > recovery.
6. Once twrp boots up again, select mount and check the boxes for /data, /system, /vendor, /cache.
7. Now flash the universal encryption disabler.
8. Let it boot once, then go back into recovery and flash Magisk.
This should solve your problem.
Click to expand...
Click to collapse
My issue is as follows:
I had rooted my g6play months ago, back when pie came out on Ota for it. The guide I followed didn't have me disable encryption, which at the time wasn't a real big deal, with my only loss being the inability to do nandroid backups. But fast forward to now, when Resurrection Remix GSI came out, I was immediately interested as I think that rom could be a great experience.
So I decided to come here in this guide because I might as well disable encryption, right? So I flashed the new twrp and did get it to wipe and disable the encryption (in the option that has you type in yes) and proceeded to flash RR, it booted to the boot anima9and there it stayed for a good 30 minutes before I decided to try the older GSI image, maybe that one would work.
But nope, I immediately got the unable to mount /data bootloop and successfully flashed my stock rom and tried again, this time flashing the new twrp right off the bat. No avail. Now everytime i go into a freshly flashed twrp, i get no password prompt, and when i try to access the internal storage, it comes up as 0mb. Even my Linux complains that it couldn't mount my Internal storage as only the SD card shows up (weirdly enough I was able to successfully push dm verity and magisk to /temp no problem but they fail upon flashing)
Edit: gotta mention that after the first time I did the pull adb command to get the backups, the command refuses to work anymore. And also that I still have an old twrp backup stored (did that today before trying this)
Kuntitled said:
My issue is as follows:
I had rooted my g6play months ago, back when pie came out on Ota for it. The guide I followed didn't have me disable encryption, which at the time wasn't a real big deal, with my only loss being the inability to do nandroid backups. But fast forward to now, when Resurrection Remix GSI came out, I was immediately interested as I think that rom could be a great experience.
So I decided to come here in this guide because I might as well disable encryption, right? So I flashed the new twrp and did get it to wipe and disable the encryption (in the option that has you type in yes) and proceeded to flash RR, it booted to the boot anima9and there it stayed for a good 30 minutes before I decided to try the older GSI image, maybe that one would work.
But nope, I immediately got the unable to mount /data bootloop and successfully flashed my stock rom and tried again, this time flashing the new twrp right off the bat. No avail. Now everytime i go into a freshly flashed twrp, i get no password prompt, and when i try to access the internal storage, it comes up as 0mb. Even my Linux complains that it couldn't mount my Internal storage as only the SD card shows up (weirdly enough I was able to successfully push dm verity and magisk to /temp no problem but they fail upon flashing)
Edit: gotta mention that after the first time I did the pull adb command to get the backups, the command refuses to work anymore. And also that I still have an old twrp backup stored (did that today before trying this)
Click to expand...
Click to collapse
well i also couldnt make the backups, fastboot just tells me the file doesnt exist. and for the internal storage: while you are encrypted, that is how it works.
---------- Post added at 11:58 AM ---------- Previous post was at 11:42 AM ----------
blowingoff said:
well i also couldnt make the backups, fastboot just tells me the file doesnt exist. and for the internal storage: while you are encrypted, that is how it works.
Click to expand...
Click to collapse
Edit: i can not mount data, twrp says argument invalid. followed your instructions anyway and my phone still gets me to a bootloop to a "running OpenRecoveryScript" again.
blowingoff said:
well i also couldnt make the backups, fastboot just tells me the file doesnt exist. and for the internal storage: while you are encrypted, that is how it works.
---------- Post added at 11:58 AM ---------- Previous post was at 11:42 AM ----------
Edit: i can not mount data, twrp says argument invalid. followed your instructions anyway and my phone still gets me to a bootloop to a "running OpenRecoveryScript" again.
Click to expand...
Click to collapse
Go into the wipe menu, advanced wipe, check data and hit change file system. change data back to f2fs. When you guys format and don't immediately reboot straight to recovery, data sets to Auto and freaks out
Starkiller2 said:
Go into the wipe menu, advanced wipe, check data and hit change file system. change data back to f2fs. When you guys format and don't immediately reboot straight to recovery, data sets to Auto and freaks out
Click to expand...
Click to collapse
the multiple times i checked, the file system was always f2fs, but sometimes ext4
and also: Do you mean we should do that after we try to format with the format data (typing yes) option? If so, it doesn't work as the internal storage won't mount. Won't even show up on my computer
Kuntitled said:
the multiple times i checked, the file system was always f2fs, but sometimes ext4
and also: Do you mean we should do that after we try to format with the format data (typing yes) option? If so, it doesn't work as the internal storage won't mount. Won't even show up on my computer
Click to expand...
Click to collapse
If you change the file system, it'll format, even if it says it won't mount. Changing the file system will force it to format. Even if it says f2fs, hit change and select f2fs anyway.
If it doesn't, format from fastboot, boot system once then go to recovery
Starkiller2 said:
If you change the file system, it'll format, even if it says it won't mount. Changing the file system will force it to format. Even if it says f2fs, hit change and select f2fs anyway.
If it doesn't, format from fastboot, boot system once then go to recovery
Click to expand...
Click to collapse
Alright, let me work through this.
I'm currently on a stock firmware and it's working fine.
Right now i have to:
1. boot into recovery twrp
2. change the filesystem of data
3. flash recovery and boot into it
4. format data(yes option)
5.check and change the file system again
6.reboot straight back into twrp recovery from recovery
7.flash dm verity zip
8.flash magisk
9.boot
Is this correct? and as for attempting to install a GSI image again, should i attempt to flash it before the verity zip and magisk? (i'll also be flashing micro gapps) or do i let it boot into system once and then i do it? (by wiping data/dalvik/cache/system)
Kuntitled said:
Alright, let me work through this.
I'm currently on a stock firmware and it's working fine.
Right now i have to:
1. boot into recovery twrp
2. change the filesystem of data
3. flash recovery and boot into it
4. format data(yes option)
5.check and change the file system again
6.reboot straight back into twrp recovery from recovery
7.flash dm verity zip
8.flash magisk
9.boot
Is this correct? and as for attempting to install a GSI image again, should i attempt to flash it before the verity zip and magisk? (i'll also be flashing micro gapps) or do i let it boot into system once and then i do it? (by wiping data/dalvik/cache/system)
Click to expand...
Click to collapse
Let's simplify. If everything is working,
go to fastboot
Flash recovery (boot doesn't seem to be working here)
Fastboot flash recovery twrp image
Select recovery, when the decrypt menu comes up, hit cancel
Wipe menu,
Swipe to factory reset
Go back to wipe
format data, yes,
Reboot recovery
Flash disabler
Flash magisk
And yes. Boot system then GSI flash, then factory reset before magisk
---------- Post added at 01:44 PM ---------- Previous post was at 01:36 PM ----------
We'll get it figured out
Starkiller2 said:
Let's simplify. If everything is working,
go to fastboot
Flash recovery (boot doesn't seem to be working here)
Fastboot flash recovery twrp image
Select recovery, when the decrypt menu comes up, hit cancel
Wipe menu,
Swipe to factory reset
Go back to wipe
format data, yes,
Reboot recovery
Flash disabler
Flash magisk
And yes. Boot system then GSI flash, then factory reset before magisk
---------- Post added at 01:44 PM ---------- Previous post was at 01:36 PM ----------
We'll get it figured out
Click to expand...
Click to collapse
Do i check the file system for data at any point?
Kuntitled said:
Do i check the file system for data at any point?
Click to expand...
Click to collapse
Only if it won't mount
Starkiller2 said:
Only if it won't mount
Click to expand...
Click to collapse
does it matter where i flash disabler, magisk and GSI from? I've been doing it from my SD card
Kuntitled said:
does it matter where i flash disabler, magisk and GSI from? I've been doing it from my SD card
Click to expand...
Click to collapse
No that's fine
Starkiller2 said:
If you change the file system, it'll format, even if it says it won't mount. Changing the file system will force it to format. Even if it says f2fs, hit change and select f2fs anyway.
If it doesn't, format from fastboot, boot system once then go to recovery
Click to expand...
Click to collapse
Data is set to emmc file system, won't mount and filesystem won't change at all and won't format
Edit: only happens when i try to change it to f2fs, changed it to ext4 with no issues and it mounts sucessfully with ext4 but won't let me format data
I get the mkfs.f2fs -t 0 /dev/block/mmcblk0p56 error 1, unable to mount data whenever i try to change to f2fs. Has my previous failed attempt at installing GSI **** with my filesys?
Kuntitled said:
Data is set to emmc file system, won't mount and filesystem won't change at all and won't format
Edit: only happens when i try to change it to f2fs, changed it to ext4 with no issues
Click to expand...
Click to collapse
But data won't work as ext4, hence the boot loop
Try going to fastboot and typing
Fastboot -w
Then boot to recovery
---------- Post added at 02:10 PM ---------- Previous post was at 02:07 PM ----------
Kuntitled said:
Data is set to emmc file system, won't mount and filesystem won't change at all and won't format
Edit: only happens when i try to change it to f2fs, changed it to ext4 with no issues and it mounts sucessfully with ext4 but won't let me format data
I get the mkfs.f2fs -t 0 /dev/block/mmcblk0p56 error 1, unable to mount data whenever i try to change to f2fs. Has my previous failed attempt at installing GSI **** with my filesys?
Click to expand...
Click to collapse
I honestly don't see how, especially if stock is working
Is there a way to determine if I have stable oos
.13 is on both A and B?
Thanks
fastboot getvar current-slot
will return with either A / B AS active slot
fastboot --set_active=(Whatever slot your not on)
YOu just need to go to settings, check sys ver. should say OS VERSION somewhere, reboot back to fastboot mode and type above commands. You can also
fast boot boot twrp.img
with this updated official (rename to twrp.img) : https://eu.dl.twrp.me/fajita/twrp-3.3.1-0-fajita.img
permanent twrp installer zip https://eu.dl.twrp.me/fajita/twrp-installer-3.3.1-0-fajita.zip
it will boot then you can copy this zip file to internal and have twrp installed via zip on both slots, you will need to reinstall magisk after on both slots, just make sure to boot into system after you flash magisk the first time before changing slots and then flashing magisk again to inactive slot by fastboot --set_active=(desired slot) and booting twrp img and flash magisk that way..IF U INSTALL THE INSTALLER ZIP(PERM TWRP) ONLY CHANGE SLOTS IN TWRP BY CHOOSING SLOT AND THEN YOU MUST REBOOT BACK TO RECOVERY(OR SYSTEM IF YOU STILL NEED TO VERIFY OOS VER) UNLESS YOU ARE PERFORMING A CLEAN FLASH OF A NEW ROM FROM SAME OOS BASE ON BOTH SLOTS. Then you would have found under settings if you are indeed on same oos on both slots. SO BOTH SLOT A AND B HAVE desired base, you would then boot the img via fastboot boot twrp.img (RENAME TWRP-3.3.0.1-fajita.img to twrp.img) then afterbooting mount all partitions and you would wipe dalvik/cache /system and /data only, (i like to wipe internal sometimes aswell when doing clean flash to make sure device is gutless) then you can remount /system and mount usb storage and copy rom zip to internal and then flash, it will complete and you want to reboot system, it will say no os installed/areyou sure. just say yes and reboot, will boot into custom rom. then you must reboot to bootloader after booting rom once, then fastboot boot twrp.img choose opposite slot (this is the only time i choose to make another slot active while not actually doing a reboot back to recovery because i dont flash the twrp perm-installer untill after i successfully get custom on both slits to avoid recovery issues /i have had many issues before with twrp regarding slot changing and how it flashed to a/b systems with custom roms built in recoverys. so i always do it this way) mount all partitions if not already, again, wipe /system /data /dalvik. you will need to go back and remount all partitions in twrp and then recopy the rom to internal from pc with mount usb storage and then flash rom reboot. then fastboot boot twrp, and install the installer zip to retain twrp forever. if you say ever need to update rom just dirty flash on the slot your on/ reboot system after/ go back to recovery(fastboot boot twrp.img from pc because you may lose twrp-perm after flashing rom depending on rom) choose other slot via twrp in reboot section, then choose reboot system. (recovery--(only works if twrp-perm is installed, or else if you dont perfer having twrp permanently just choose reboot system, then reboot to fastboot after, and reboot twrp.img) then dirty flash on the slot we have just changes to and then rom is updated on both slots, then you may reflash twrp perm(installer).zip and then you need to flash magisk and reboot and then reboot back to recovery and change slots reboot back to recovery and flash magisk once more... YOU MUST FLASH MAGISK AFTER TWRP EVERY TIME THEN REBOOT BEFORE GOING FURTHER INTO STUFF AS ALWAYS OR YOU WILL NOT BOOT . if you want to update to open beta base if still on stock .13 on both slots use above steps instead of /custom rom/ you can be flashing the /beta rom/full ota zips/ on both slots then you will have new base of beta(whatever beta you choose) then you can flsh custom rom on top of that. if you flashed a custom rom over the .13 and wish to update to beta base instead of .13 you will need to reformst the device and lose all data unless you perform a back-up prior
Code:
*** I'm not responsible for dead sd cards, thermonuclear war, getting you fired because the alarm has failed. Your warranty is void if you continue! ***
Code:
*** Everything you read here was a success for my ATU-L21 variant of the Huawei Y6 (2018). Don't be alarmed, the files mentioned here are 100% compatible with the phone ***
Hey, dear Forum Users!
Prerequisite things:
Install HiSuite, it has the proprietary drivers needed to operate ADB and Fastboot.
You need to unlock your bootloader, get them from dc-unlocker, it's 4 euros.
You need the following:
The 2018 kernel and vendor image: https://drive.google.com/open?id=1aFTTMSArwBuF5tsJBkWJ7f_d7IQc7zyy (credits goes to Boki, @deadliestPixel on Twitter)
You need this TWRP to boot up: https://forum.xda-developers.com/huawei-y6/development/guide-backup-current-partitions-t3853831 (thanks to @leepicstitch on Twitter for finding this)
You'll need to flash this TWRP to recovery_ramdisk: https://www.mediafire.com/file/7nyab3whb6bp7r8/twrp_3.2.3_atu.rar/file
Choose a ROM that will suit your needs from this thread: https://forum.xda-developers.com/huawei-y6/development/index-list-roms-y62018-t3854167 or try other GSIs
(I recommend Resurrection Remix with gapps and su)
So if you have everything, let's do this.
Before we start everything make sure you have a microSD card that has the VENDOR.img and the system.img you downloaded.
So, we need to make a backup of our current recovery_ramdisk for later, you can follow the TWRP XDA post above to do so.
After you've done that go to fastboot and flash the older kernel with this command:
Code:
fastboot flash kernel /path/to/KERNEL.img
Flash the recovery you downloaded with
Code:
fastboot flash recovery_ramdisk /path/to/recovery.img
Now boot up that screen flasher recovery you had before. If you booted it up just reboot the phone to recovery with
Code:
adb reboot recovery
, the Y6 Prime 2018 recovery should boot up.
Now go to Install -> Change Storage -> Micro SD -> flash image -> choose the vendor.img and flash it to the VENDOR partition.
Do the same for the system.img file.
Go to the main menu and go to wipe, then wipe dalvik/art cache, cache, data, internal storage.
go to the main menu and go to reboot, then bootloader.
Now we need to flash our stock recovery_ramdisk back, because eRecovery will complain about a damaged data partition. Do a low level data format, type yes, and when the emui recovery pops up, do another data wipe.
Now, just hit reboot and the phone should boot into the ROM.
Turn off the phone and reboot back into fastboot and flash back the Y6 Prime 2018 recovery just in case if eRecovery wants to do something weird.
Now just reboot your phone and enjoy it.
If you need any help send me a DM on Twitter (@miklos_akos) or on Discord (miklos_akos#0001).
hawkhu said:
Hey, dear Forum Users!
Prerequisite things:
Install HiSuite, it has the proprietary drivers needed to operate ADB and Fastboot.
You need to unlock your bootloader, get them from dc-unlocker, it's 4 euros.
You need the following:
The 2018 kernel and vendor image: https://drive.google.com/open?id=1aFTTMSArwBuF5tsJBkWJ7f_d7IQc7zyy (credits goes to Boki, @deadliestPixel on Twitter)
You need this TWRP to boot up: https://forum.xda-developers.com/huawei-y6/development/guide-backup-current-partitions-t3853831 (thanks to @leepicstitch on Twitter for finding this)
You'll need to flash this TWRP to recovery_ramdisk: https://www.mediafire.com/file/7nyab3whb6bp7r8/twrp_3.2.3_atu.rar/file
Choose a ROM that will suit your needs from this thread: https://forum.xda-developers.com/huawei-y6/development/index-list-roms-y62018-t3854167 or try other GSIs
(I recommend Resurrection Remix with gapps and su)
So if you have everything, let's do this.
Before we start everything make sure you have a microSD card that has the VENDOR.img and the system.img you downloaded.
So, we need to make a backup of our current recovery_ramdisk for later, you can follow the TWRP XDA post above to do so.
After you've done that go to fastboot and flash the older kernel with this command:
Flash the recovery you downloaded with
Now boot up that screen flasher recovery you had before. If you booted it up just reboot the phone to recovery with , the Y6 Prime 2018 recovery should boot up.
Now go to Install -> Change Storage -> Micro SD -> flash image -> choose the vendor.img and flash it to the VENDOR partition.
Do the same for the system.img file.
Go to the main menu and go to wipe, then wipe dalvik/art cache, cache, data, internal storage.
go to the main menu and go to reboot, then bootloader.
Now we need to flash our stock recovery_ramdisk back, because eRecovery will complain about a damaged data partition. Do a low level data format, type yes, and when the emui recovery pops up, do another data wipe.
Now, just hit reboot and the phone should boot into the ROM.
Turn off the phone and reboot back into fastboot and flash back the Y6 Prime 2018 recovery just in case if eRecovery wants to do something weird.
Now just reboot your phone and enjoy it.
If you need any help send me a DM on Twitter (@miklos_akos) or on Discord (miklos_akos#0001).
Click to expand...
Click to collapse
One question, I have to flash the system.img as a vendor?... (BECAUSE YOU SAY ABOVE THAT WITH THE SYSTEM. IMG WE MADE THE SAME AS WITH THE VENDOR)
dj 77mx said:
One question, I have to flash the system.img as a vendor?... (BECAUSE YOU SAY ABOVE THAT WITH THE SYSTEM. IMG WE MADE THE SAME AS WITH THE VENDOR)
Click to expand...
Click to collapse
System.img goes to the system partition, obviously.
This worked flawlessly, the only difference is that I couldn't flash Kernel.
The ROM I used: PHH Treble 9.0 github.com/phhusson/treble_experimentations/releases/tag/v117
The steps I took:
- Factory reset phone
- Backup stock recovery_ramdisk
- Download kernel (unused) and vendor
- Boot fastboot
- Flash twrp in recovery_ramdisk
- Boot twrp
- Flash vendor, flash system
- Clean caches
- Reboot fastboot
- Flash stock recovery_ramdisk
- Reboot
erecovery did not complain, everything was ok there
Anyone tried this at atu l22 latest build?
UlysistheNewbie said:
Anyone tried this at atu l22 latest build?
Click to expand...
Click to collapse
Since the ATU-L21 and L22 is the same hardware wise it should work without any problems.
i keep either getting a black screen or vendor not mount or system not mount if not vendor ( ATU-L22 Y6 2018 )
UlysistheNewbie said:
Anyone tried this at atu l22 latest build?
Click to expand...
Click to collapse
.REPLYING--- Hey bro have you tryed flashing custom rom to the Atu-L22 with any luck?
Still trying to flash a custom system.img to my Atu-L22 after weeks of no success but flowing thru with countless amounts of tutorials, Anyone have any ideas for this phone, any help much appreciated haha?
I'm stuck in a boot splashscreen... This phone is really not easy to work with x(
edit : Narrowing it down, apparently, I don't have a vendor partition to flash the vendor to... I am starting to loose hope.
I need stock recovery_ramdisk.img . Anyone have? (Im sorry for my bad English )